View Source

Target release	Release name or number
Epic	Reporting - Adjustment Summary
Document status
Priority
eLMIS Status	Implemented
OpenLMIS Status	Not implemented
PATH	Amanda BenDor (Unlicensed)
OpenLMIS	Mary Jo Kochendorfer (Deactivated)
JSI	Ashraf Islam (Unlicensed)

Goals/Scope

Displays adjustment in stock of products indicating the adjustment type like Transfer In, Transfer Out, Expired, Damaged etc) in the selected period

Status in eLMIS: Implemented.

Status in OpenLMIS: Not implemented

Priority: High priority for Tanzania, Zanzibar, Zambia

Background

Use:

District and up for management, supervision, etc. and facilities would also use but have the information on the stock cards
looking at expiries, losses, etc.
key for accountability, especially during audits

The adjustment report shows:

facility type,
facility name,
supplying facility
product
adjustment type
period
adjustments

Parameters:

program
schedule
year
period (which can be an A / B / C quarter period)
Adjustment Type
Geographic Zone (district, region, country)
Facility
Product

Assumptions

In this story user means or one of the following, Health Facility incharge, DMO, Community and Regional Management Team (C/RHMT), Logistics officer/Advisors, Senior level decision maker, M&E officer/Advisor etc

User Stories

#	Title	User Story	Label	Importance
1	View data	As a user, I need to be able to view adjustment data and get a sense what type adjustment occurred at facility level	Reports	Must have for TZ, ZnZ, ZM
2	Export reports to Excel	As a user, I need to be able to export all reports and analysis reporting results into Excel so that I can process the data more and analyze it in Excel.	Reports	Must have for TZ, ZnZ, ZM
3	Print reports with headings and logs	As a user, I need to be able to print reports with customized headings and logos so that I can file the report for future references	Reports	Must have for TZ, ZnZ, ZM

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

Out of Scope

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