/
[SELV/SIIL] CCE: Capture Functionality Status of CCE

[SELV/SIIL] CCE: Capture Functionality Status of CCE

Owned by Vidya Sampath
Last updated: Apr 13, 2017 by Rachel Powers (Deactivated)


Target releaseVaccine Module
EpicCCE Domain
Document status
DRAFT
Document owner
Vidya Sampath
Technical Lead

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.

  • In settings where possible (RTM, see those reqs here) the system should be able to receive notifications/updates about CCE functionality (via interoperability considerations with RTM platforms)

  • Finally, based on the data that gets entered into the system, notifications/updates to specific personas (upstream store managers, maintenance technicians and managers, facility staff) should be possible 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

#TitleUser StoryLabelImportanceNotes
1Input Temperature and  Functionality Status manually

As a HW or logistician at a facility, I want to input the temperature and corresponding functionality status of the facility CCE so that:

  • Upstream SC personnel are aware of the status so that they can prepare the resupply order for pick-up or delivery
  • Upstream CCE maintenance personnel are aware of the status so that they can plan for repairs or replacement



SELV/SIILMust Have
2Generate 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; ColdTraceNice to Have
3Input 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:

  • Upstream CCE maintenance personnel are aware of the reason so that they know what to plan for in terms of repairs
  • Upstream EPI policy manager are aware of which CCE needs replacement or type of CCE works well
SELV/SIILMust have
4Generate 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

As an upstream logistician, I want to know when a CCE is no longer working properly so that I can plan the upcoming distribution schedule for that facility accordingly

SELV/SIILMust have

Diagrams


Dependencies

DescriptionLink
All other CCE product reqs

Open Questions

Below is a list of questions to be addressed as a result of this requirements document:

#QuestionOutcomeStatus
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?



3Is another requirement needed to be written up for inputing data from daily logs (either on paper or on the fridge tag) or does the user story #1 in this requirement capture the need?

Out of Scope

  • SMS notifications to the system from the HF in case of fridge failure (if SMS business process exists currently, the support for it is outside the system)
  • SMS notifiications from the system when fridge failure is reported either by a person manually entering the information or reported via an RTM (

Related content

OpenLMIS: the global initiative for powerful LMIS software