B. Prepare Re-Supply Order for Delivery or Pick-Up
Goals
Add text here
Background
This page captures the workflows from the supplier (RIVO or DIVO) stand-point, after s/he has decided how much to allocate or issue. These workflows support tasks such as viewing pick list, viewing load amounts for delivery, confirming shipment, generating proof of delivery documentation, etc.
User Stories
| # | Title | User Story | Label | Importance | Notes | JIRA Ticket |
|---|---|---|---|---|---|---|
| 1 | Pick List | Basic pick list that shows
| Allocation + Del SC Allocation + PU SC Requisition + Del SC Requisition + PU SC | Next Up Votes: 5 | ||
| 2 | Advanced pick list | Advanced pick list that shows
| Allocation + Del SC Allocation + PU SC Requisition + Del SC Requisition + PU SC | Next Up Votes: 2 | ||
| 3 | Confirm shipment RIVO to DIVO | This was identified as a workflow but no specific stories apart from a note that this is regardless of whether RIVO drops off or DIVO picks-up – the confirmation is to say got the order and we have what you need – pending further discussion | Allocation + Del SC Allocation + PU SC Requisition + Del SC Requisition + PU SC | Next | ||
| 4 | Confirm shipment DIVO to HF | SMS notification to HF to say shipment ready (most of use in delivery transport model when shipment is ready and on its way) | Allocation + Del SC Requisition + Del SC | Next | ||
| 5 | Shipment dispatch notification | Goods in Transit notification when DIVO logs on to OpenLMIS | Allocation + Del SC Requisition + Del SC Requisition + PU SC | Next Up Votes: 5 | This story also shows up under notifications; need to decide which one to delete to avoid duplication | |
| 6 | View HF status | View whether HF is open during planned visit time/date | Allocation + Del SC Requisition + Del SC | Next | VS: I think this is totally out of scope | |
| 7 | Electronic POD RIVO to DIVO | Generate electronic POD Applicable only when both nodes (supplier and receiver) have openLMIS | Allocation + Del SC Allocation + PU SC Requisition + Del SC Requisition + PU SC | MVP | ||
| 8 | Print elec POD RIVO to DIVO | Print-option (button, tab etc) exists to print official looking electronic POD even though both sites have OpenLMIS | Allocation + Del SC Allocation + PU SC Requisition + Del SC Requisition + PU SC | Next Up Votes: 10 | ||
| 9 | Print PoD DIVO to HF | Print POD if receiver site does not have OpenLMIS | Allocation + Del SC Allocation + PU SC Requisition + Del SC Requisition + PU SC | MVP | I know Josh did the MVP line under time constraints so may not have seen the overlap so — if the option exists for this to be MVP, when can't the printing of the elec POD also be folded into MVP? | |
| 10 | Record HF visit observations | Record delivery visit observations:
| Allocation + Del SC Requisition + Del SC | Next Up Votes: 11 (see notes) | Entire workflow that supports the supplier's workflow at HF site did not make MVP cut but received 11 votes up |
Assumptions
- insert
Diagrams
Dependencies
insert
Open Questions
Below is a list of questions to be addressed as a result of the vaccine workshop:
| Question | Outcome | |
|---|---|---|
Out of Scope
Out of scope for this feature OR potentially saving for future development.