View Source

Target release	Release name or number
Epic	Reporting - Feedback Report
Document status
Priority
eLMIS Status	Implemented in Zambia
OpenLMIS Status	Not Implemented
PATH	Jenny Thompson (Unlicensed)
OpenLMIS	Mary Jo Kochendorfer (Deactivated)
JSI	Ashraf

Goals/Scope

Focuses on some of the reports and analysis reports that Zambia users highlighted as most useful:

This report is built at the facility level based on facility level data per program.
This report includes a period filter
- Per per period and program, this report shows a list of products, the beginning balance, quantity received, dispensed, adjustments, physical count, amc, Quantity Approved, Quantity Supplied
- This report is solely based on requisition information
This report includes an Emergency Order Point and Maximum Stock Level
ENHANCEMENT: We could add a column for Quantity Requested that shows the difference between the Quantity Requests vs Quantity Approved to show the entire life cycle.

Status in eLMIS: In eLMIS Zambia

Status in OpenLMIS: Not implemented

Priority: High priority

Background

This report is used by facilities to show how much quantity of each product was requested and how much was supplied

Assumptions

This report is run by the Health Facility in charge.

User Stories

Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.

#	Title	User Story
1	Facility In Charge	Quality Assurance: Want to make sure that the physical count and calculated order quantity hasn't been tempered with.
2	Facility In Charge	I want to compare the amount that was requested and the quantity that was supplied
3	Facility In Charge	I want to see substituted products, i.e. Amoxycillin pack size 100 vs 1000

Diagrams

OpenLMIS > Reporting - Feedback Report > image2018-8-28_15-5-2.png

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
2
3
4
5
6

Out of Scope

List the features discussed which are out of scope or might be revisited in a later release.