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/08/02 00:44] – [Visibility for patients created on a synced system] Chris Pettydispensing:patients [2022/12/23 08:14] (current) – [General tab] Craig Drown
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 149: Line 151:
  
 <WRAP center round Info 60%> <WRAP center round Info 60%>
- 
-Use caution with the store pref //Patients created in other stores not visible in this store//. Read more here: [[other_stuff:virtual_stores#preferences_tab|Store preferences]].  
  
 Data that syncs with a patient: Data that syncs with a patient:
Line 165: Line 165:
 <WRAP center round important 60%> <WRAP center round important 60%>
  
-Use caution with the store pref //Patients created in other stores not visible in this store//. It does not scale well on large systems if it is turned **OFF** for many stores, it causes exponential sync traffic:+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   * (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.   * Initialising a site with 3 dispensaries with the pref off will require syncing 100k patients, and 300k visibility records.
-  * It does not include transactional data, which likewise would not scale. +  * It does not include prescription data. If it did it'd only add to the above. 
  
 </WRAP> </WRAP>
  • Last modified: 2021/08/02 00:44
  • by Chris Petty