Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:mobile:user_guide:vaccine [2021/04/11 03:01] – [Step 1: Select the correct sensor] Craig Drown | en:mobile:user_guide:vaccine [2024/02/19 23:47] (current) – [Temperature Breaches] Adam Dewey | ||
---|---|---|---|
Line 38: | Line 38: | ||
Approved sensors can be purchased directly from the manufacturer or reseller online. | Approved sensors can be purchased directly from the manufacturer or reseller online. | ||
+ | |||
+ | ==== Adding Sensors ==== | ||
+ | The first time you use the Vaccine module, there will be no sensors connected to your device. | ||
+ | {{ : | ||
+ | |||
+ | Tap '' | ||
+ | |||
+ | <WRAP center round important 95%> | ||
+ | Please make sure that you have an approved mSupply temperature sensor. | ||
+ | </ | ||
+ | |||
+ | We recommend you keep the sensor close when you are adding or editing it within mSupply Mobile. | ||
+ | If you are using a brand new sensor, press the top of the sensor until it flashes to turn it on. | ||
+ | |||
+ | == Step 1: Select the correct sensor == | ||
+ | When you tap **Add Sensor**, your device will scan and list any sensors that can be connected by Bluetooth. | ||
+ | {{ : | ||
+ | |||
+ | If you tap the **BLINK** button, the LED light for that sensor will flash. | ||
+ | |||
+ | When you are sure that you have the correct sensor, tap **Connect** for that sensor. | ||
+ | |||
+ | == Step 2: Sensor Thresholds == | ||
+ | Firstly, some definitions: | ||
+ | * __Consecutive__ means a single event where the temperature stays over (or under) the threshold for the whole time. So if you have a threshold of 8 degrees, and a consecutive breach time of 10 minutes, then a breach that lasts for 6 minutes, then drops under the threshold for 2 minutes, then breaches again for 6 minutes is __not__ a consecutive breach, but the 2 x 6 minute breaches are added to the cumulative breach records. | ||
+ | * __Cumulative__ means adding together the total time over a certain temperature for a series of breaches. | ||
+ | |||
+ | Now we can set the temperature breach conditions for the sensor. | ||
+ | |||
+ | * Hot Consecutive | ||
+ | * A breach will be displayed when the sensor logs a temperature above this value for longer than the specified time. Using the '' | ||
+ | |||
+ | * Cold Consecutive | ||
+ | * A breach will be displayed when the sensor logs a temperature below this value for longer than the specified time. Using the '' | ||
+ | |||
+ | * Hot Cumulative | ||
+ | * A breach will be displayed when the sensor logs a temperature above this value for longer than the total specified time specified (total time is calculated as the sum of all breach times). Using the '' | ||
+ | |||
+ | * Cold Cumulative | ||
+ | * A breach will be displayed when the sensor logs a temperature below this value for longer than the total specified time specified (total time is calculated as the sum of all breach times). Using the '' | ||
+ | |||
+ | {{ : | ||
+ | <wrap center round tip 95%> | ||
+ | TIP: It is possible to **long press** the +/- buttons to change the values faster. | ||
+ | </ | ||
+ | |||
+ | Tap '' | ||
+ | Tap '' | ||
+ | Tap '' | ||
+ | |||
+ | == Step 3: Sensor connection == | ||
+ | In this final step you need to enter: | ||
+ | ***Sensor Name**: enter a new name for the sensor. This is the name which will appear within mSupply mobile. You should choose a name to make it easy to identify the sensor. | ||
+ | ***Sensor Code**: enter a short name code for the sensor. You should choose a code that is unique for each sensor. | ||
+ | |||
+ | <wrap center round tip 95%> | ||
+ | TIP: For reporting purposes, we recommend that you do not use special characters such as “-, +, *” etc in either the Sensor Name or Sensor Code fields. | ||
+ | </ | ||
+ | |||
+ | ***Logging Interval**: using the '' | ||
+ | ***Start Logging**: Use the '' | ||
+ | |||
+ | When setting the schedule for the first temperature log, allow sufficient time for the sensor to be placed in its desired location and adjust to the location’s temperature. 20 minutes should be sufficient in most situations. | ||
+ | |||
+ | |||
+ | {{ : | ||
+ | |||
+ | Tap **Connect** to complete sensor setup and add the sensor to mSupply mobile. | ||
+ | |||
+ | Tap **Back** if you wish to return to Step 2 and edit the sensor thresholds (temperature breach conditions). | ||
+ | |||
+ | Tap **Cancel** if you no longer want to add the sensor. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | <WRAP center round tip 60%> | ||
+ | We recommend that each device should be linked to a maximum of six sensors. Each sensor should only be linked to one device. | ||
+ | </ | ||
+ | |||
+ | ==== Edit Sensor ==== | ||
+ | To edit sensor details, you can tap on the ‘’cog’’ icon on the mSupply Vaccine home page (above screenshot) or on the Sensor Detail screen. | ||
+ | Screenshot | ||
+ | |||
+ | All __sensor threshold__ and __sensor connection__ details are editable except for the start Logging date and time. Simply tap on the field that you wish to end and make changes. | ||
+ | |||
+ | {{ : | ||
+ | No changes will be made until you tap '' | ||
+ | |||
+ | <WRAP center round info 60%> | ||
+ | NOTE: Depending on your proximity to the sensor and the Bluetooth capabilities of your device, changes can take a few minutes. | ||
+ | </ | ||
+ | |||
+ | === Pausing Sensor Downloads === | ||
+ | The edit screen also allows you to '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | === Replacing a Sensor === | ||
+ | Tapping '' | ||
+ | {{ : | ||
+ | From the list, select the replacement sensor. | ||
+ | |||
+ | === Deleting a Sensor === | ||
+ | Tap '' | ||
+ | {{ : | ||
===== Using the Vaccine module ===== | ===== Using the Vaccine module ===== | ||
Line 61: | Line 167: | ||
* If the breach icon (an orange triangle with an exclamation) does show for a row, this signals that the stock line has had a temperature breach. Tapping the icon will bring up a graph of the temperature breach. In the example below, the fridge seems to be broken, probably not a good idea to use this batch! | * If the breach icon (an orange triangle with an exclamation) does show for a row, this signals that the stock line has had a temperature breach. Tapping the icon will bring up a graph of the temperature breach. In the example below, the fridge seems to be broken, probably not a good idea to use this batch! | ||
{{ : | {{ : | ||
- | |||
=== Supplier Requisitions === | === Supplier Requisitions === | ||
Line 131: | Line 236: | ||
</ | </ | ||
- | === Adding Sensors | + | === Temperature Breaches |
- | The first time you use the Vaccine module, there will be no sensors connected to your device. | + | |
- | {{ : | + | |
- | Tap '' | + | Temperature breaches are displayed on the graph as warning icons. |
- | <WRAP center round important 95%> | + | As of February 2024 it is not possible |
- | Please make sure that you have an approved mSupply temperature sensor. | + | |
- | </ | + | |
- | We recommend you keep the sensor close when you are adding or editing it within mSupply Mobile. | + | However, note that this functionality is now available in Open mSupply: See https://docs.msupply.foundation/ |
- | If you are using a brand new sensor, press the top of the sensor until it flashes to turn it on. | + | |
- | == Step 1: Select the correct sensor == | + | |
- | When you tap **Add Sensor**, your device will scan and list any sensors | + | |
- | {{ : | + | |
- | + | ||
- | If you tap the **BLINK** button, the LED light for that sensor will flash. | + | |
- | + | ||
- | When you are sure that you have the correct sensor, tap **Connect** for that sensor. | + | |
- | + | ||
- | == Step 2: Sensor Thresholds == | + | |
- | Firstly, some definitions: | + | |
- | * __Consecutive__ means a single event where the temperature stays over (or under) the threshold for the whole time. So if you have a threshold of 8 degrees, and a consecutive breach time of 10 minutes, then a breach that lasts for 6 minutes, then drops under the threshold for 2 minutes, then breaches again for 6 minutes is __not__ a consecutive breach, but the 2 x 6 minute breaches are added to the cumulative breach records. | + | |
- | * __Cumulative__ means adding together the total time over a certain temperature for a series of breaches. | + | |
- | |||
- | Now we can set the temperature breach conditions for the sensor. | ||
- | |||
- | * Hot Consecutive | ||
- | * A breach will be displayed when the sensor logs a temperature above this value for longer than the specified time. Using the '' | ||
- | |||
- | * Cold Consecutive | ||
- | * A breach will be displayed when the sensor logs a temperature below this value for longer than the specified time. Using the '' | ||
- | |||
- | * Hot Cumulative | ||
- | * A breach will be displayed when the sensor logs a temperature above this value for longer than the total specified time specified (total time is calculated as the sum of all breach times). Using the '' | ||
- | |||
- | * Cold Cumulative | ||
- | * A breach will be displayed when the sensor logs a temperature below this value for longer than the total specified time specified (total time is calculated as the sum of all breach times). Using the '' | ||
- | |||
- | {{ : | ||
- | <WRAP center round tip 60%> | ||
- | TIP: It is possible to **long press** the +/- buttons to change the values faster. | ||
- | </ | ||
- | |||
- | Tap '' | ||
- | Tap '' | ||
- | Tap '' | ||
- | |||
- | == Step 3: Sensor connection == | ||
- | In this final step you need to enter: | ||
- | ***Sensor Name**: enter a new name for the sensor. This is the name which will appear within mSupply mobile. You should choose a name to make it easy to identify the sensor. | ||
- | ***Sensor Code**: enter a short name code for the sensor. You should choose a code that is unique for each sensor. | ||
- | |||
- | <WRAP center round tip 60%> | ||
- | TIP: For reporting purposes, we recommend that you do not use special characters such as “-, +, *” etc in either the Sensor Name or Sensor Code fields. | ||
- | </ | ||
- | |||
- | ***Logging Interval**: using the '' | ||
- | ***Start Logging**: using the '' | ||
- | |||
- | <WRAP center round tip 60%> | ||
- | TIP: When setting the schedule for the first temperature log, allow sufficient time for the sensor to be placed in its desired location and adjust to the location’s temperature. | ||
- | </ | ||
- | |||
- | {{ : | ||
- | |||
- | Tap '' | ||
- | Tap '' | ||
- | |||
- | {{ : | ||
- | |||
- | Tap '' | ||
- | |||
- | <WRAP center round important 60%> | ||
- | Important: We recommend that each device should be linked to a maximum of six sensors. Each sensor should only be linked to one device. | ||
- | </ | ||
- | |||
- | === Edit Sensor === | ||
- | To edit sensor details, you can tap on the ‘’cog’’ icon on the mSupply Vaccine home page (above screenshot) or on the Sensor Detail screen. | ||
- | Screenshot | ||
- | |||
- | All __sensor threshold__ and __sensor connection__ details are editable except for the start Logging date and time. Simply tap on the field that you wish to end and make changes. | ||
- | |||
- | {{ : | ||
- | No changes will be made until you tap '' | ||
- | |||
- | <WRAP center round info 60%> | ||
- | NOTE: Depending on your proximity to the sensor and the Bluetooth capabilities of your device, changes can take a few minutes. | ||
- | </ | ||
- | |||
- | == Pausing Sensor Downloads == | ||
- | The edit screen also allows you to '' | ||
- | |||
- | {{ : | ||
- | |||
- | == Replacing a Sensor == | ||
- | Tapping '' | ||
- | {{ : | ||
- | From the list, select the replacement sensor. | ||
- | |||
- | == Deleting a Sensor == | ||
- | Tap '' | ||
- | {{ : | ||
| // | | // | ||