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 [2021/05/10 14:16] – [Entering a new patient] Gary Willettsdispensing:patients [2022/12/23 08:14] (current) – [General tab] Craig Drown
Line 3: Line 3:
 <wrap info>Updated version 5.01</wrap> <wrap info>Updated version 5.01</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.+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.
  
 ===== Entering a new patient ===== ===== Entering a new patient =====
Line 66: 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 144: 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.
  • Last modified: 2021/05/10 14:16
  • by Gary Willetts