Meeting Notes & Next Steps
...
- Next steps:
- Define 3-4 very specific problems
- Talk post with tags to ask community about the pain points they're running into w/ reporting & analytics; Technical leads - respond in thread and dig into technical points as much as possibleAs-needed: Follow-up calls with technical leads for teams that reply in Talk
- Weekly check-ins together; next week come back together with the requirements we've heard and document these on a public squad kick-off call & talk post to announce (like this one)
- Doodle with possible times for squad to meet on regular basis - timing that works for others
- Need big enough source of demo/aggregate data that MySql cannot handle - Ampath demo data - Allan to talk to JJ to see about getting Bashir access
- Grace connect with Dimitri
| Page Properties | |||||||
|---|---|---|---|---|---|---|---|
|
High-Level Requirements
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:
- 10 metrics from PEPFAR MER Indicators
- Viral Load Indicators: e.g. Ampath project to consider other metrics in correlation with VL; PVLIs (Pt Viral Load Indicators)
- Getting data out of OMRS is challenging - Mekom's DB Sync work looking at that
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.
Assumptions
User Stories
| Title | User Story | Importance | Notes | |
|---|---|---|---|---|
| 1 | ||||
| 2 |
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|