Present: Josh, Peter, Brandon, Mary Jo, Matt
18 Oct 2017

Reporting Deep Dive

Full Stock Availability

We drilled in on the 'Full Stock Availability' DISC indicator and its data sources.

Detail:

For the Full Stock Availability indicator
- Reporting periods exactly match requisition periods
  - But, if we can aggregate up to a coarser reporting period that's fine
    - e.g. requisition periods are monthly, starting at the first day of the month and we product reports quarterly
Locations represent a single facility
When calculating % of districts with at least X% of facilities with full stock availability
- Requisition data includes information on all health facilities in the district

JSON file with requisition data, same as what's served by the API
- useful keys for Full Availability indicator
  - period
    - start date
    - end date
  - facility location
  - stockout days
  - product ID
  - product name
  - commodity type
  - geographic zone, e.g. district
  - [latitude, longitude]
JSON data with mapping from geographic zone to region
- maybe shape files for geographic zone and region
JSON data with mapping from product to commodity
- use this to find the commodity from the product ID
JSON file stock card data, same as what's served by the API
- useful keys for Full Availability indicator
  - date
  - facility location
  - number of stock on hand
    - when this hits zero we do not have full availability for the reporting period

Possible responsibilities for OpenLMIS core team to support the reporting work:

OpenLMIS is also adding HL7 FHIR facility/location master lists. Reporting stack could use that when it becomes available.

Two different diagrams from earlier morning conversations about Mobile (black drawing from Mary Jo) and Reporting (blue drawing from Peter):