Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dispensing:patients [2020/06/11 09:43] – [Home store] Adrian Boone | dispensing:patients [2022/12/23 08:14] (current) – [General tab] Craig Drown | ||
---|---|---|---|
Line 1: | Line 1: | ||
{{indexmenu_n> | {{indexmenu_n> | ||
====== 10.03. Patients ====== | ====== 10.03. Patients ====== | ||
- | <wrap info> | + | <wrap info> |
- | In mSupply, patients are a type of name. They are a special form of customer that have first names, last names, genders and dates of birth. You also dispense stock to a patient on a prescription, | + | In mSupply, patients are a type of name. They are a special form of customer that can have first names, last names, genders and dates of birth. You dispense stock to a patient on a prescription, |
===== Entering a new patient ===== | ===== Entering a new patient ===== | ||
Line 16: | Line 16: | ||
{{ : | {{ : | ||
- | * //**Code**// and //**Last**// are the only required fields but all applicable fields should be completed so that it is easier to recognise the patient next time. | + | * **Code** and **Last** are the only required fields but all applicable fields should be completed so that it is easier to recognise the patient next time. Please note that if there are non-printable characters before or after the **First**, **Last** or **Code** they will be removed. Any non-printable characters in the **First**, **Last** or **Code** (and spaces in the **Code**) will be replaced with an underscore ('' |
* The patient code will be filled in automatically for you if the // | * The patient code will be filled in automatically for you if the // | ||
Line 48: | Line 48: | ||
==== Home store ==== | ==== Home store ==== | ||
+ | |||
+ | <wrap info> | ||
+ | <wrap info> | ||
As of version 4.10, you'll notice that at the top of the details window is the **Home store**. For new patients, the home store is the store the patient was created in; for previously existing patients the version upgrade will assign the home store to be the store where the patient was most recently issued a prescription. | As of version 4.10, you'll notice that at the top of the details window is the **Home store**. For new patients, the home store is the store the patient was created in; for previously existing patients the version upgrade will assign the home store to be the store where the patient was most recently issued a prescription. | ||
- | * A patient' | + | * A patient' |
- | * Currently, a patient' | + | * In version 4.10 and 4.11, a patient' |
* You can create prescriptions for a patient in any store they are visible in, not just their home store, but repeats can only be processed in any dispensary store on the home site. | * You can create prescriptions for a patient in any store they are visible in, not just their home store, but repeats can only be processed in any dispensary store on the home site. | ||
* If you're on the primary server, you can make a patient visible in other stores (just like any other type of name) - doing this will make the patient' | * If you're on the primary server, you can make a patient visible in other stores (just like any other type of name) - doing this will make the patient' | ||
Line 63: | Line 66: | ||
**Hold do not issue**: If this is checked then no stock can be dispensed to the patient | **Hold do not issue**: If this is checked then no stock can be dispensed to the patient | ||
- | **Credit limit**: This is the maximum | + | **Credit limit**: This is the maximum |
+ | |||
+ | If the payments module is not activated, the value in this field has no effect. | ||
==== Prescriptions tab ==== | ==== Prescriptions tab ==== | ||
Line 136: | Line 141: | ||
=== Visibility for patients created on a synced system === | === Visibility for patients created on a synced system === | ||
+ | |||
<WRAP center round tip 60%> | <WRAP center round tip 60%> | ||
- | Remember that in a synced system, | + | Remember that in a synced system, |
</ | </ | ||
- | When a patient is created, it will only be made visible in: | + | When a patient is created |
- | * It’s | + | * Its [[dispensing: |
- | * Other dispensaries that have sync type **Active** or **Collector** on the same sync site of the [[dispensing: | + | * All other stores of type " |
- | Click to view more about [[other_stuff: | + | <WRAP center round Info 60%> |
- | <WRAP center round info 60%> | + | Data that syncs with a patient: |
- | For synced systems | + | |
+ | | ||
+ | | ||
- | While it is not normal to have a dispensary on the Primary server, it is possible. | + | Data that does NOT sync: |
- | + | | |
- | Once a patient has been created in a dispensary, it's store visibility can then be amended in this tab. | + | * Patient events |
+ | </ | ||
+ | <WRAP center round important 60%> | ||
+ | While it can be used to make all patients visible across all dispensary stores across all sync sites, use caution with the store pref //Patients created in other stores not visible in this store//. Doing so does not scale well on large systems if it is turned **OFF** for many stores as it causes exponential data growth and sync traffic: | ||
+ | * (50 stores) x (100,000 patients) = 5 million visibility records | ||
+ | * Initialising a site with 3 dispensaries with the pref off will require syncing 100k patients, and 300k visibility records. | ||
+ | * It does not include prescription data. If it did it'd only add to the above. | ||
+ | </ | ||
+ | Once a patient has been created in a dispensary, its store visibility can then be amended in this tab. | ||
===== Merging patients while dispensing ===== | ===== Merging patients while dispensing ===== | ||
+ | |||
+ | <wrap info> | ||
+ | |||
While dispensing, you may observe that a patient has been inadvertently entered twice. For example: | While dispensing, you may observe that a patient has been inadvertently entered twice. For example: | ||
Line 170: | Line 189: | ||
Here you need to decide which record should be kept, and which one should be merged, and check the appropriate radio buttons. This combines the information in the record to be merged with the information in the record to be kept. | Here you need to decide which record should be kept, and which one should be merged, and check the appropriate radio buttons. This combines the information in the record to be merged with the information in the record to be kept. | ||
+ | |||
+ | Note that, from version 4.12, merging patients will be restricted to only those having the same //home site// - see [[dispensing: | ||
Line 176: | Line 197: | ||
| // Previous: | | // Previous: | ||
---- struct data ---- | ---- struct data ---- | ||
+ | pagestatus.status | ||
---- | ---- | ||