Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Target releaseVaccine Module
Epic

OLMIS-432 - Getting issue details... STATUS

Document status
DRAFT
Document owner
Designer

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 ( OLMIS-571 - Getting issue details... STATUS ) for the vaccine module and requires a full set of user stories to support development. 
  • 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

#TitleUser StoryLabelImportanceNotes
1Parse RTM temperature output
SELVMust 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. 


Open Questions

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


QuestionOutcome
1Does 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.

  • No labels