Target releaseRelease name or number
Epic

HCMIS

Document status
Document owner
@JSI
Technical LeadKalkidan


Goals/Scope

Background


Every supplier (Hub) will periodically (mostly monthly) receive requests from districts through mFlow. This request from mFlow appears on the approval page of HCMIS. HCMIS is the system that hubs use to manage all types of health commodities. The responsible person to manage vaccine products will find the requests that are sent from the districts when he logs in. He then processes the request following the steps on HCMIS.

Assumptions


User Stories

Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.

#TitleUser StoryLabelImportanceNotes
2Approve quantityAs a Vaccine managing officer at Hub level, I will find the specific District’s request/order on the ‘approve quantity’ section of HCMIS and analyze it. I will then permit the requested quantity, correct the quantity, or even cancel the request as appropriate.  HCMISMust Have


Print pick-listAs a Vaccine managing officer for Vaccine at Hub level, I will print a pick-list in the ‘Finalize Issue Order’ section so that I can be guided as to which batch numbers should be packed for delivery as well as the exact location of the items. I can also see the corresponding expiry date of the items that are going to be issued.HCMISMust Have


Review and finalize issueAs a Vaccine managing officer at Hub level, I will review the issue before I confirm it. If there is any correction, I will return it to the ‘approve quantity’ page and edit it again. HCMISMust Have


Print STV (Invoice)Once I finalize the issue, I will forward it to the invoicer for the STV to be printed. The invoicer will print the STV and a copy of the STV will be attached with the pick list and filed for further reference (if needed). If not, I will find any needed information from HCMIS at any time.HCMISMust Have

Dispatch

The items confirmed to be issued will go to the ‘dispatch’ page on the system. The Dispatch Officer will confirm the dispatch after checking the issues are according to:

  1. the approved quantity for the District,
  2. The information given by HCMIS (Batch, Expiry, Manufacturer).
HCMISMust Have
  1. Diagrams



  1. Dependencies


DescriptionLink
Name of story or release Link to JIRA


  1. Open Questions

Initial communication between stakeholders and the development team to help understand scope and estimates.

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

#QuestionOutcomeStatus
1(e.g. How we make users more aware of this feature?)Communicate the decision reached Open, In Progress, Closed, and date of closure
  1. Out of Scope

  2. List the features discussed which are out of scope or might be revisited in a later release.