...

• 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

fd

VillageReach/OpenLMIS Responsibilities

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

• ATOM feed for OpenLMIS requisitions approved
• Webhook support in OpenLMIS endpoints
• ETags in OpenLMIS endpoints
• adding filters onto OpenLMIS endpoints (such as by approved date)

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

Mobile

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

...