Goals/Scope
Electronic submissions from eLMIS Facility edition needs to be separately tracked
Status in eLMIS: Implemented.
Status in OpenLMIS: ?
Priority: High priority for Zambia
Background
eLMIS Facility edition are being rolled out across the country in 270 high volume facilities. That means there are still other facilities who will submit manually enter the R&R in eLMIS using the web interface. The REST API based submission protocol needs to be enhanced to track electronic submissions separate from web-based submissions. Electronic submission does bring some workflow changes.
Assumptions
Facility edition will submit electronic R&R
User Stories
| # | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|---|---|---|---|---|---|
| 1 | REST API | As an district supervisor I should be able to see whether a facility submitted R&R electronically or through the web interface | R&R | Must have | See Figure 1. Note that facility do have the option to resort to manual submission to eLMIS in case the connectivity issues | |
| 2 | REST API | As a facility edition user in a health facility I should be able to submit a current period R&R even if the prior period was not yet finalized | R&R | Must have | Some unforeseen situation can arise where the supervisor has not yet approved the prior period R&R and the time came for this period's R&R to be submitted. Or, some other similar situation | |
| 3 | REST API | As a facility edition user I want to be able to skip the initiate and authorize phases and submit directly | R&R | Must have | A typical R&R goes through stages of INITIATE, AUTHORIZE, & SUBMIT. However an electronic submission from Facility edition needs to combine all three into one REST API call. | |
Diagrams
Figure 1: Submission source is displayed
Dependencies
| Description | Link |
|---|---|
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 |