Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • No offline support for now - DHIS2 has support for "intermittent connections" (based on info received from DHIS2 training); it is still uncertain at this time if it has full offline supportsince there is no requirement here, DHIS2 would be sufficient to fulfill this
  • No integrated look and feel - since there is no requirement here, DHIS2 would be sufficient to fulfill this
  • Have a form designer to support basic forms - DHIS2 does have tools to design forms, although it is unclear at this time how fully-featured forms can be made. Based on looking at the DHIS2 demo (https://play.dhis2.org/demo/dhis-web-dashboard-integration/index.html), basic forms should be possible to do
  • Have a single "admin" user for access - Since DHIS2 does have authentication support (including OAuth2) and appears to have some RBAC, it should be easy enough to create an "admin" user for OpenLMIS to use

Post-MVP Iterations

Future iterations would satisfy more of the requirements in the ideal solution. In particular,

  • Support for Informed Push should be straightforward, as it would access the same Program Data endpoint with the same criteria (facility, program, processingPeriod). See interaction diagram above.
  • Offline data capture support
    • DHIS2 (desktop client) has support for "intermittent connections" (based on info received from DHIS2 training)
    • Additionally, it appears that the client-server setup has support for connectivity interruptions measured in seconds/minutes, but not hours/days. For more complete offline support, there is an option to create an offline instance that syncs with an online server during connectivity
  • Support a complex model for role-based access control (RBAC), similar to OpenLMIS - DHIS2 appears to have RBAC, similar to how OpenLMIS is set up, so it should be possible to create mappings of users between systems