Meeting Notes & Next Steps
- Squad model: Product Team in discovery & requirements gathering
- Reporting & Analytics squad. Name? Ideally refers to tangible, releaseable value.
- Next steps:
- 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 possible
- As-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
High-Level Requirements
Goals
- Pick one concrete problem to solve
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 |
|---|---|