Program Data MVP Proposal

Description

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

QAlity Plus - Test Management

Checklists

Activity

Brandon Bowersox-Johnson 
May 24, 2017 at 9:33 PM

Per group discussion at Sprint Planning, we agreed that this ticket (the Proposal) is done. Moving to Done.

Here is the summary of the status:

  • The Proposal v2 is finished. It was presented to the core team, and we did not get a consensus about moving forward with it—specifically, the DHIS2 aspect of the proposal was "vetoed" so the work is on hold. There were discussions about moving forward with Ona, ODK1, or other "containers" for the data in place of DHIS2.

  • In terms of next steps, we are having joint sessions with the ODK team in early June () to explore any opportunities there. The result of that might fill their backlog but might not give us an immediate solution we could build onto. After that June event, we will need to revisit Program Data as a group to decide what, if anything, we pull the trigger on at that point.

Brandon Bowersox-Johnson 
May 11, 2017 at 6:07 PM
(edited)

There is a v2 of the proposal with notes from a meeting in April 2017:

https://openlmis.atlassian.net/wiki/display/OP/Program+Data+Technical+Design+Proposal+v2

The next step is that we need to make a decision about how to proceed with a PoC (the last bullet point in the acceptance criteria).

Chongsun Ahn 
April 12, 2017 at 11:04 PM

Flagged
Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Components

Sprint

Fix versions

Priority

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