Reporting Domain Parent Page

Owned by Vidya Sampath
Last updated: Apr 26, 2017
4 min read

This page summarizes the discussions and requirements gathered thus far for this domain.

Contents

To Do

  • Reconcile user personas
  • TALK TO TEAM: difference between "Viewing XX" and "Report on XX"? Ex – "view estimated needs for district" and "estimated needs report by district" — is it just the print option or more? comes up with all domains.
  • TALK TO TEAM: SM is LONG! think of breaking it up some more. Requisitions – SM or D/Re-S?
  • TALK TO TEAM: report back method? how is it done usually when using small cards with updates made?
  • TALK TO TEAM: Justin example of data in, data view, data report etc


Reporting Domain Overview

15 minute max. presentation providing overview (Vidya Sampath, back-up Brian Taliesin)

  • Definitions, scope of reporting and KPIs, custom reports versus set reports etc
  • Clarify that this is an intro and that throughout Day 2, you will likely also talking about reporting needs so don't worry, facilitator will make notes of this to add to discussion
  • Set stage for small group discussion by planting these questions in overview: WHY - WHO - HOW OFTEN (nice is WHAT to SEE – simple static versus dynamic troubleshoot)
    • Which KPIs are most important? 2nd? 3rd?... and which user personas need it? How often?
    • What reports are needed for each domain? and which user personas need them? How often? WHY? LOOK BACK AT REPORTING AND ANALYTICS page for definitions
    • In what format? (A PDF they view online? An email notification triggered by an event? A monthly report with a link to view on the web?)
    • In what type of representation (table, bar graph, line graph, trendlines, simple summary stat, etc)
  • Outcome :
    • Rank the KPIs and reports within the small group. 
    • Present back the top hand-full of KPIs and reports to the large group.

CCE Domain Reporting

Facilitator: Rachel Powers (Deactivated)

Name of Report/KPIDefinition; detailsWho needs itHow often
Functional status of CCEReport showing the functional status (e.g. functioning normally, experiencing issues, broken/offline) of CCE in a certain facility/zone. This can be either a snapshot during time or showing functional status over a period.

1- CCE manager,

2- DIVO & RIVO

3- EPI manager

4- Global stakeholders

1- ideal: can be run at any time

2- every period

3- quarterly

4- annually

Temperature alarmsReport showing total number of temperature alarms (high and low) that have gone off in a certain facility/zone within a predetermined period.

1- CCE manager

2- DIVO & RIVO

3- EPI manager

4- Global stakeholders

1- ideal: can be run at any time

2- every period

3- quarterly

4- annually

Available CCE storage capacityReport showing the available capacity for vaccines in each CCE within a certain facility/zone.

1- Intermediate warehouse manager

2- DIVO & RIVO

3- EPI manager

4- Global stakeholders

1- every period

2- every period

3- quarterly

4- annually

Forecasting and Estimation Domain Reporting

Facilitator: Chris Wright (Unlicensed)

Name of Report/KPIDefinition; detailsWho needs itHow often
Estimated Product Needs by facility

1 - DIVO

2 - RIVO

1 - monthly

2 - monthly

Estimated Product Needs by district

1 - DIVO

2- RIVO

1 - monthly

2 - monthly

Forecast Accuracy / Forecast Demand Ratio (DISC KPI)

SIMPLE

Calculation: (Doses consumed + wasted) / doses forecasted for this reporting period and geography

Doses consumed is derived from SM domain and not program data on monthly immunizations

1 - EPI Natl Manager

2 - Global Stakeholders (Gavi, UNICEF, etc)

3 - Intermediate Warehouse Manager

1 - Quarterly

2 - Annaully

3 - Quarterly

F A/ F D R

ADVANCED

Same calculation as above, but doses consumed is derived from program data on monthly immunizations and not from SM domainSame as abovesame as above

Distribution/Re-Supply Domain Reporting

Facilitator: Vidya Sampath; backup: Mary Jo Kochendorfer (Deactivated)

Name of Report/KPIDefinition; detailsWho needs itHow often












Stock Management Domain Reporting

Facilitator: Brandon Bowersox-Johnson

Name of Report/KPIDefinition; detailsWho needs itHow often
Item Detail Report/ Bin Card Report

for screenshot – get either v3 view or HCMIS view

As a Vaccine managing officer, in this report, I can see all the transactions for a certain item I selected and the detailed information about each transaction.



Stock Status Report ADV

for screenshot – get  HCMIS view


As a Vaccine managing officer, I can get different indispensable information on the stock status report. I can see the available stock that I have, how many of them have expired or are about to expire, how many of them are reserved for facilities, whether I am overstocked, near EOP or below EOP and much more.




Stock Status Report SIMPLE

for screenshot - get v3 view or ??

As a DIVO, I mostly use SOH report when I need to quickly check my usable stock. Other than that, I can also get other important information like AMC, MOS, GIT and ordered quantity for the items.

AMC - average monthly consumption
MOS - months of stock
GIT - goods in transit (inbound towards me)







Notes to all facilitators

  • For each report, have group pin down type of representation, type of format, persona that needs it, frequency of need for each persona – doesn't have to be exact but should be specific enough to provide general idea
  • FOCUS on what we need – long list – then rank them – we don't decide MVP — they decide MVP to present back to the plenary
  • We will have the generalizable country profiles – review with the group often to see if for both countries needs, the MVP is applicable.
  • Always ask about which unit of data capture and data view – doses or vials
  • Remind resource constraints and time constraints (software needs to be released by November!) when needed
  • Remind folks that simplicity is a beautiful thing! Getting folks to think of end user and the need to not overwhelm them with several features but the minimum necessary to do their job well is key.

Archive

The following requirements pages informed the work under this domain:


OpenLMIS: the global initiative for powerful LMIS software