$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Target release
EpicRequisition- ??
Document status
DRAFTED
PriorityHIGH
eLMIS StatusImplemented
PATH 
OpenLMIS 
JSI Ashraf Islam (Unlicensed)

Goals/Scope

R&R forms needed additional data validations

Status in eLMIS: Implemented.

Status in OpenLMIS: ?

Priority: High priority for Tanzania, Zanzibar, Zambia

Background

To improve data quality R&R validation process had to be enhanced further

  • Do not allow a product to be skipped, if that line item had any data elements entered such as – opening balance, issues, etc.

Assumptions

Data validations are listed on the SOPs and were included on training manuals/sessions

User Stories

#TitleUser StoryLabelImportanceNotesJIRA 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 formMust have

















Diagrams


Dependencies

DescriptionLink


Open Questions

Below is a list of questions to be addressed as a result of this requirements document:

#QuestionOutcomeStatus
1


Out of Scope

  • No labels