dispensing:patients

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dispensing:patients [2020/06/11 10:03] – [Home store] Adrian Boonedispensing:patients [2022/12/23 08:14] (current) – [General tab] Craig Drown
Line 1: Line 1:
 {{indexmenu_n>30}} {{indexmenu_n>30}}
 ====== 10.03. Patients ====== ====== 10.03. Patients ======
 +<wrap info>Updated version 5.01</wrap>
  
-<wrap info>Updated version 4.10</wrap> +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, rather than distributing it to a customer on a customer invoice.
-<wrap info>Updated version 4.12</wrap> +
- +
-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, rather than distributing it to a customer on a customer invoice.+
  
 ===== Entering a new patient ===== ===== Entering a new patient =====
Line 18: Line 16:
 {{ :dispensing:new_patient.png?600 |}} {{ :dispensing:new_patient.png?600 |}}
  
-  * //**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 //Auto-generated patient code// preference is turned on (see [[dispensing:dispensary_mode#setting_dispensary_mode_preferences|Setting dispensary mode preferences]] for details).   * The patient code will be filled in automatically for you if the //Auto-generated patient code// preference is turned on (see [[dispensing:dispensary_mode#setting_dispensary_mode_preferences|Setting dispensary mode preferences]] for details).
Line 56: Line 54:
 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's details can only be edited in any dispensary store which is active on the same site as the home store (i.e. on their **Home site**). This ensures that a patient can only be edited in one location at a time +  * A patient's details can only be edited in any dispensary store which is active on the same site as the home store (i.e. on their **Home site**). This ensures that a patient can only be edited in one location at a time. 
-  * In version 4.10 and 4.11, a patient's //home store// cannot be changed. However, from version 4.12 it will be possible to edit the home store (if you're logged into the primary server). Doing this will make the patient's records (repeats, patient medication records and insurance policies) available to the new home site. If the patient has previous prescriptions from stores which are visible in the new home store, these will also be made available to the new home site, but will only show up in the patient's history if the //Share patient prescriptions over stores// preference is turned on (see [[dispensing:dispensary_mode#setting_dispensary_mode_preferences|]])+  * In version 4.10 and 4.11, a patient's //home store// cannot be changed. However, from version 4.12 it will be possible to edit the home store (if you're logged into the primary server). Doing this will make the patient's records (repeats, patient medication records and insurance policies) available to the new home site. If the patient has previous prescriptions from stores which are visible in the new home store, these will also be made available to the new home site, but will only show up in the patient's history if the //Share patient prescriptions over stores// preference is turned on (see [[dispensing:dispensary_mode#setting_dispensary_mode_preferences|]]). Note that you will not be able to edit a patient's details if their record is currently waiting in the sync queue to be transferred to another home store. A "Not editable pending transfer to //XX//" (where //XX// is the new home store) message will show at the bottom of the screen and all fields will be disabled if this is the case.
   * 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's records (repeats, patient medication records and insurance policies, but not their prescription history) available to the store.   * 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's records (repeats, patient medication records and insurance policies, but not their prescription history) available to the store.
Line 68: 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 negative value a patient's account can have when the payments module is activated. They will not be able to receive stock on a prescription without paying for it when they reach this limit.+**Credit limit**: This is the maximum debt that a patient's account can have when the payments module is activated. Enter as a number greater than zero. They will not be able to be dispensed a prescription without paying for it when they reach this limit.' 
 + 
 +If the payments module is not activated, the value in this field has no effect.
  
 ==== Prescriptions tab ==== ==== Prescriptions tab ====
Line 146: Line 146:
 </WRAP> </WRAP>
  
-When a patient is created, it will only be made visible in:+When a patient is created on any site, it will be made visible in:
   * Its [[dispensing:patients#home_store|home store]] (i.e. the current store), and   * Its [[dispensing:patients#home_store|home store]] (i.e. the current store), and
-  * Other dispensaries that have sync type **Active** or **Collector** on the same sync site as the [[dispensing:patients#home_store|home store]] //if// their store preference **Patients created in other stores not visible in this store** is switched ''OFF''.+  * All other stores of type "Dispensary" which have their store preference //Patients created in other stores not visible in this store// switched **OFF**.
  
-Click to view more about [[other_stuff:virtual_stores#preferences_tab|Store preferences]].+<WRAP center round Info 60%>
  
-<WRAP center round info 60%> +Data that syncs with a patient: 
-For synced systems with [[https://docs.msupply.org.nz/mobile|mSupply Mobile]] dispensaries, there will be a **Collector** copy of all the dispensaries on the central server.  Following the rules described here, if there is a dispensary **Active** on the central server, and a patient is created in it, that patient will become visible in //all// mSupply mobile dispensaries in your system //unless// the store preference **Patients created in other stores not visible in this store** is switched ''ON'' for //each// of those dispensaries.+  * Their insurance policies 
 +  * Their repeats (Note, other sites won't be able to see and use them) 
 +  * Their PMR records 
 + 
 +Data that does NOT sync: 
 +  * Transactional/prescription history 
 +  * Patient events 
 + 
 +</WRAP> 
 + 
 +<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.  
 + 
 +</WRAP>
  
-While it is not normal to have a dispensary on the central server, it is possible.  Indeed, If you had a national register of all patients, and wanted to manage their patient details centrally, and make them //all// visible to //all// mSupply mobile dispensaries, importing all patients in to such a dispensary would be a way of achieving this, provided that the store preference **Patients created in other stores not visible in this store** is switched ''OFF'' for //each// of those dispensaries.</WRAP> 
  
 Once a patient has been created in a dispensary, its store visibility can then be amended in this tab. Once a patient has been created in a dispensary, its store visibility can then be amended in this tab.
Line 173: Line 190:
 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 store// - see [[dispensing:patients#home_store|]].+Note that, from version 4.12, merging patients will be restricted to only those having the same //home site// - see [[dispensing:patients#home_store|]].
  
  
Line 180: Line 197:
 |  //  Previous:  **[[dispensing:prescription_entry |10.02. Prescription entry]]** | | Next: **[[dispensing:prescribers |10.04. Prescribers]]** //  | |  //  Previous:  **[[dispensing:prescription_entry |10.02. Prescription entry]]** | | Next: **[[dispensing:prescribers |10.04. Prescribers]]** //  |
 ---- struct data ---- ---- struct data ----
 +pagestatus.status    : 
 ---- ----
  
  • Last modified: 2020/06/11 10:03
  • by Adrian Boone