Flagged
Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Josh Zamor
Josh Zamor(Deactivated)Reporter
Josh Zamor
Josh Zamor(Deactivated)Story Points
8
Components
Sprint
None
Fix versions
Priority
Time Assistant
Time Assistant
Created April 12, 2017 at 2:44 AM
Updated May 24, 2017 at 9:33 PM
Resolved May 24, 2017 at 8:46 PM
Program Data needs a quick proposal document that:
more accurately defines what a potential systems interaction between OpenLMIS and DHIS2 would look like assuming program data was captured in DHIS2
component diagram of a Program Data Service
take a deeper look at DHIS2 apis for associating a Program Data form with, for example: Program, Processing Period, Facility, etc. Attempt to show how this works for forms not collected through Requisition workflows - e.g. Inf. Push
proposes an MVP using DHIS2 that leverages as much of DHIS2 as possible to demonstrate to community the sort of benefit we get. Lightly suggest how future strategy/customizations might help address known community desires (offline data collection, mobile collection, seamless capture within OpenLMIS, etc)
Acceptance Criteria:
write proposal document (wiki) with diagrams as needed for the above
meet with Josh and Darius to help refine
pitch final proposal to leads in Seattle
help define next steps: a PoC