...
| Page Properties | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals
- The goals of this requirements page is to document the user stories specifically related to the "Create CCE Catalog" feature. This feature fits within the CCE Reporting and Management epic (
) for the vaccine module and requires a full set of user stories to support development.Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-571 - While very high-level features were outlined for inclusion in the vaccine module, this page and its sister requirements pages will be used to capture information, stories, background, and processes for the much more specific features.
- Scope: This feature should include stories on:
- System processes around RTM communicating with OpenLMIS
- System processes around generating temperature alarms (SMS, email, system alert)
- System processes around recording & tracking of alarm instances
- User processes around resolving alarms
- Configuration of related to "Temperature Alarm for RTM"
- ...
- Out of scope for this feature:
- Managing SMS sending from RTM
- Directly monitoring temperature
- Configuring RTM device settings
- ...
Country Background
Are there any country-specific details about this feature that should be noted?
Assumptions
- The user who sets the CCE catalog is not the same user who adds the equipment info per facility
- One high-level catalog will encompass all CCE used within the health system (no separate catalogs for each district)
- ...
User Stories
| # | Title | User Story | Label | Importance | Notes |
|---|---|---|---|---|---|
| 1 | Parse RTM temperature output | SELV | Must Have | ||
| 2 | |||||
| 3 | |||||
| 4 | |||||
| 5 | ... | ... | ... |
Business Process Mapping
Include any mockups, diagrams or visual designs relating to these requirements. Each feature should have a corresponding business process map to show SOPs related to that functionality.
Gliffy imageAttachmentId att111943090 name RTM monitoring diagramAttachmentId att111943086
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome | |
|---|---|---|
| 1 | Does OpenLMIS need to calculate the alarms itself based on data from the RTM, or should the RTM let OpenLMIS know that there is an alarm? (Which system decides that there should be an alarm?) | |
| 2 | ||
| 3 |
Not Doing
Out of scope for this feature OR potentially saving for future development.