Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Background and strategic fit

One of the key opportunities for greater collaboration within the OpenMRS community is around reporting through ETL (Extract, Transform, and Load). This was underscored during discussions at OMRS19. It’s difficult to do modern analytics on OpenMRS data. The manual process of designing and developing ETL queries is time-consuming, complex, and is being tackled one implementation at a time.

Goals

  • Pick one concrete problem to solve
  • An output that is general, that most implementations can use. (Since inputs are so different by organization.)

3-4 Specific Problems/Use Cases to tackle with intermediate data handling:

  1. 10 metrics from PEPFAR MER Indicators
  2. Viral Load Indicators: e.g. Ampath project to consider other metrics in correlation with VL; PVLIs (Pt Viral Load Indicators)
  3. Getting data out of OMRS is challenging - Mekom's DB Sync work looking at that 
  4. ...?


Jira Locations
Technical Leads
Product Manager
Launch Plan


User Stories 

  • ...

Questions

  • ...

Not Doing

  • No labels