[mFlow/HCMIS] HCMIS VRF Processing/Issue (Hub to District)
Target release | |
---|---|
Epic | Routine Immunization |
Document status | DRAFT |
Document owner | @JSI |
Technical Lead | Kalkidan |
Goals/Scope
Background
Every supplier (Hub) will receive periodical (mostly monthly) requests from districts through mFlow. This request from mFlow will appear on HCMIS. HCMIS is the warehouse management system that PFSA 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
Title | User Story | Label | Importance | Notes | |
---|---|---|---|---|---|
1 | Approve quantity | As a Vaccine managing officer at Hub level, I will check the specific District’s request/order on HCMIS and analyze it. I will then permit or correct the quantity accordingly or even cancel when needed. | HCMIS | Must have | |
2 | Print Pick-list | As a Vaccine managing officer for Vaccine at Hub level, I will print a pick-list so that I can be guided as to which batch numbers should be packed for delivery. Acceptance Criteria:
| HCMIS | Must have | |
3 | Finalize Issue | As a Vaccine managing officer at Hub level, I will review and finalize the issue before I print it. If there is any correction, I will return it to approval page and edit it again. When I finish checking, I will print the STV. | HCMIS | Must have | |
4 | Issuing to District (Electronically) | As a Vaccine managing officer at Hub level, I will finalize the transaction on HCMIS by Issuing the request. I will print STV from the system, attach it with the pick list and file it for further reference (if needed). If not, I will find any needed information from HCMIS at any time. | HCMIS | Must have | |
5 | Issuing to District (Physically) | As a Vaccine managing officer at Hub level, I have to make sure the issues are according to:
| N/A |
OpenLMIS: the global initiative for powerful LMIS software