| 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 Petty | dispensing:patients [2025/04/07 13:42] (current) – [Home store] Adrian Boone |
|---|
| <wrap info>Updated version 4.10</wrap> | <wrap info>Updated version 4.10</wrap> |
| <wrap info>Updated version 4.12</wrap> | <wrap info>Updated version 4.12</wrap> |
| | <wrap info>Updated version 7.13</wrap> |
| |
| 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|]]). 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. | * 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 central 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 central 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. |
| |
| ===== The patient detail window tabs ===== | ===== The patient detail window tabs ===== |
| **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 ==== |
| |
| <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: |
| <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> |