|
R&R forms needed additional data validations
Status in eLMIS: Implemented.
Status in OpenLMIS: Implemented
Priority: High priority for Tanzania, Zanzibar, Zambia
To improve data quality R&R validation process had to be enhanced further
OpenLMIS
Data validations are listed on the SOPs and were included on training manuals/sessions
| # | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|---|---|---|---|---|---|
| 1 | R&R form | As a data entry person, I would expect the R&R form to perform additional checks to ensure that I'm completing the forms in the way the SOP requires. For example, the system should not allow a line item to be skipped if that line item already have some data elements entered. | R&R form | Must have | ||
| 2 | Delete an R&R | As a data entry person, I should be able to delete a draft R&R | R&R form | Must have | ||
| 3 | Skip a period | As a data entry person, I should be able to skip a period, if the R&R for that period was not available for some reason | R&R form | Must have | Sometime a facility in-charge goes to vacation, post become vacant, or because of some other reason an R&R for the previous period is not going to be available and the data entry person needs to skip that period so that R&R for the current period can be entered | |
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 |