View Source

Target release	Release name or number
Epic	Requisition - Paper Date
Document status
Priority
eLMIS Status	Not implemented
OpenLMIS Status	Not Implemented
PATH	Jenny Thompson (Unlicensed)
OpenLMIS	Mary Jo Kochendorfer (Deactivated)
JSI	Ashraf

Goals/Scope

To allow recording of the date that the facility personnel submitted paper R&Rs, to increase accountability for the reasons for late reporting. This will help identify whether delays are due to delays in facilities reporting or delays in district personnel entering the reports into the system. However given that there are plans to extend eLMIS to all ordering facilities, this feature may not be needed in future, so fills a shorter term need.

Status in eLMIS: In the eLMIS code base - not implemented in eLMIS but in implemented in VIMS

Status in OpenLMIS: Not in OpenLMIS

Priority: Low

Background

Currently in both eLMIS and in OpenLMIS, the date submitted is a system recorded date based on the date the report was entered electronically and there is no place to enter the date the facility submitted the R&R. Note: There is a feature to do this in VIMS, but in the eLMIS instance this feature is not turned on.

Assumptions

What are technical or business specific details and characteristics that should be known to explain the environment? List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).

User Stories

#	Title	User Story	Label	Importance	Notes
1	Enter date when facility submitted paper R&R	As district personnel I want to record the date that the facility personnel submitted paper R&Rs, so that I can monitor which facilities are reporting late.	Tanzania	Must have
2	Source of R&R submission	As a system submitting an Requisition, I want to update the requisition to know that I submitted the information. See the "WEB_UI"

Diagrams

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.

Dependencies

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

Open Questions

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	For Tanzania user stories: review the users, "so thats" added, review the label, and review the priority level.	Communicate the decision reached	Open, In Progress, Closed, and date of closure

Out of Scope

Gap Estimation Notes 4/11/2018

Attendees: Mary Jo, Peter, Elias, Brandon, Muhammad
Discussion: This could be done pretty easily, very similar to the "Date Stock Count Completed" feature built into version 3.
- It is a toggle admin configuration on the requisition template to show this new date field or not.
- Then the date field itself appears in a modal when the user tries to submit the R&R form.
User Story #2 is now.
Elias: In eLMIS the regular and emergency requisitions also have a way to track "walk in customers".
- They want to capture these orders differently–they are not really emergencies.
- Mary Jo: This is "pick up". This is the "direct order creation" ability. This is also known as "ad hoc".