Program Data Collection

Description

Approach to support Program Data variability with forms and fields.

Support user-friendly customized data collection forms.

  • needs to be able to to be injected into requisitions

  • collect outside of the cycle

  • offline data collection

Our Goals for Program Data are:

  • Support user-friendly customization of data collection forms by implementors.

  • Collect this custom data form in the same process as requisitions.

  • Future: Collect program data with any process/cycle (not just during requisitions).

  • Future: Expose collected data to reporting warehouse

  • Support offline web tools and mobile tools (broader than just Program Data).

Version 3 must have: Regimens (similar to v2? Need this for ARV right away in 3.0 release). To achieve this we identified 4 options:

  • Integrate ODK into OpenLMIS for Program Data functionality; plus leverage ODK for mobile support (if possible).

  • Build Program Data in OpenLMIS in Java (without ODK).

  • Build Regimens in a more hard-coded way, just for Malawi needs. Wait while ODK matures (its data model is currently changing). (Would we need Equipment too?)

  • Work on a Cordova/cross-platform mobile app solution with OpenLMIS.

  • Use Excel. Or Support ONA?

WRT to Requisitions and "Regimens": The first cut of OpenLMIS intimately associated a program reporting mechanism - Regimens - with Requisitions. In 3.0, we do want the "Regimens" functionality to be there in one way or another (TBD). In 3.x, we still want an such an association, but with more flexibility. This epic also contains some of those original "R&R" requirements, to associate program data collection with Requisitions, which helps keep the Requisition epic better focused. For now, we'll continue with the "Regimen" term but this may change.

Query issues in this epic

Activity

Show:
Brandon Bowersox-Johnson
November 6, 2016, 4:56 AM

NOTES from November 2016 scope/estimation session:

Our Goals for Program Data are:

  • Support user-friendly customization of data collection forms by implementors.

  • Collect this custom data form in the same process as requisitions.

  • Future: Collect program data with any process/cycle (not just during requisitions).

  • Future: Expose collected data to reporting (which kind?)

  • Support offline tools and mobile tools (broader than just Program Data).

Version 3.0 must have: Regimens (similar to v2? Need this for ARV right away in 3.0 release). To achieve this we identified 4 options:

  • Integrate ODK into OpenLMIS for Program Data functionality; plus leverage ODK for mobile support (if possible).

  • Build Program Data in OpenLMIS in Java (without ODK).

  • Build Regimens in a more hard-coded way, just for Malawi needs. Wait while ODK matures (its data model is currently changing). (Would we need Equipment too?)

  • Work on a Cordova/cross-platform mobile app solution with OpenLMIS.

  • Use Excel. Or Support ONA?

please proceed with setting up a December meeting to continue exploring ODK and Program Data.

Assignee

Unassigned

Reporter

Jake Watson