Goals/Scope
Vaccines are completely reliant on a properly functioning CCE in order to remain potent and safe to use.
OpenLMIS should be able to capture the functionality status of CCE – working, working intermittently, not working at all, as well as record information for what could be causing the failure.
This information is then used to: 1) determine which locations can store vaccines and which cannot; 2) plan for which locations need maintenance work; 3) plan for which locations need replacement of equipment; and 4) if the data allows for disaggregation by reason for non-functioning or by equipment type, the indicator and trend can also be used to assess performance of particular types of models of CCE in the field to figure out which ones to purchase in the future.
Finally, in order to aide doing all of the above, the system should be able to receive notifications (SMS?) about CCE functionality as well as send notifications to specific personas (upstream store managers, maintenance technicians and managers, facility staff) when functionality is affected.
Background
Personas needing this functionality:
- Health worker at a facility
- Logistician visiting a facility with distribution order
- Storage manager preparing an order for pickup or distribution
- CCE maintenance technician who has to fix CCE
- CCE maintenance coordinator who has to plan repair schedules
- EPI policy manager who has to determine which CCE to replace and what type of CCE to order
Assumptions
User Stories
| # | Title | User Story | Label | Importance | Notes |
|---|---|---|---|---|---|
| 1 | Input Functionality Status manually | As a HW or logistician at a facility, I want to input the functional status of the facility CCE so that:
| SELV/SIIL | Must Have | |
| 2 | Generate functionality status from RTM devices | As a sub-national store manager, I want to see the functional status of a CCE from RTM devices so that I can plan the pick-up or delivery order As a CCE maintenance planner, I want to see the functional status of a CCE from RTM devices so that I can plan the schedule for repair or replacement | RTM; Nexleaf; ColdTrace | Nice to Have | |
| 3 | Input reasons for failure or improper function manually | As a HW or logistician at a facility, I want to input the reason for improper functionality of the facility CCE so that:
| |||
| 4 | Generate notifications depending on functionality | As a HW at a facility, I want to know when a CCE is no longer working properly so that I can move the products stored within it As a HW at a facility, I want to send a notification to the system when a CCE is no longer working properly so that upstream managers can take corrective action As an upstream CCE personnel, I want to know when a CCE is no longer working properly so that I can plan a repair or replacement schedule As an upstream store manager, I want to know when a CCE is no longer working properly so that I can plan the upcoming order for that store accordingly |
Diagrams
Dependencies
| Description | Link |
|---|---|
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | What falls under the category of equipment? Refrigerators/passive storage devices such as cold boxes/freezers/walk-in cold rooms? | ||
| 2 | This requirement says the system should report functionality – how much of the reporting comes from someone inputing “yes working/not working/maybe working” versus an automatic report that pulls data from temperature logs coming into the system via RTM, fridge log tags, or daily written logs? That is, which one takes precedence if both options available? |
Out of Scope