| Target release | Release name or number |
|---|---|
| Epic | HCMIS |
| Document status | |
| Document owner | @JSI |
| Technical Lead | @Kalkidan |
|
When products/items are issued to Hubs from the Central Medical Store, the STV/invoice number will automatically sync to the ‘Receive’ page on HCMIS. Here, the Warehouse Manager at the Hub can see all the invoice lists that are coming to his/her hub. She/he will select the specific invoice number under which the item they want to receive is found. Then, she/he will receive the item following the steps on HCMIS.
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.
| # | Title | User Story | Label | Importance | Notes |
|---|---|---|---|---|---|
| 1 | Short identifier for the story | Describe the user and what they are trying to achieve As a ______ I want/need to ________ so that I _______. - High level acceptance criteria | Relevant labels to distinguish source. From which system, or which country? | Must Have, Nice to Have |
|
| 2 | Receive product | As a Warehouse Manager at Hub level, I will go to the ‘Receive’ page on HCMIS and select the specific invoice/STV number that I want.
Step 1 - The list of items that are sent to my hub under that invoice number will be displayed. Step 2 - Then, I will insert the actual quantity of the items that I received against the invoiced quantity. Step 3 - After that, I will select the warehouse and the exact location that I will store the received products in and send it to the Stock and Distribution Officer for confirmation. | HCMIS | Must Have |
|
| Confirm receive | As a Stock and Distribution Officer at Hub level, I will check all the details of the items before I finalize the receipt like manufacturer, unit, expiry date, batch and store. If there is something that needs to be corrected, I will return it to the Warehouse Manager for editing. If everything is correct, I will confirm the receipt and print GRNF. |
Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
| Description | Link |
|---|---|
| Name of story or release | Link to JIRA |
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:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | (e.g. How we make users more aware of this feature?) | Communicate the decision reached | Open, In Progress, Closed, and date of closure |
