During our Technical Action Committee (TAC) kickoff meetings, @mseaton asked the perfect question:
What are we doing?
This wasn’t just a the right question for the TAC group; it’s a great question for OpenMRS. With a growing community, expanding opportunities, constrained resources, an aging codebase, and a variety of incompatible frontends, it’s more important than ever for us to have a shared vision of what we are doing.
We started out by enumerating potential areas of focus for TAC:
- Platform maintenance (Library updates, Performance issues, Memory leaks, Security)
- API curation (REST documentation, FHIR API, Road Map for API)
- Architecture (Microservices, Cloud support, CDS, Switching to PostgreSQL, Forms support)
- Vertical solutions (HIV, TB, NCD, Maternal Child Health, Retrospective data entry, …)
- Mobile OpenMRS (Android & iOS clients, progressive web applications)
- Integration (OCL, SMS, Lab, Pharmacy, Inventory, HR, DHIS2, smart devices, …)
- UI Strategy (Web Framework 3.0 road map, migrating from OWAs, UX design framework, patient-facing UIs)
- Reporting (ETL)
- Community tooling (SDK, migration to OpenMRS, or between OpenMRS versions, packaging artifacts, Docker images)
- Strategic Decisions (EMR platform/middleware vs “full” EMR, harvesting from existing efforts)
Early goals for TAC will be to refine this list and prioritize some areas for which we can produce artifacts (Talk posts, blog posts, white papers, or project plans) that the community can use to align our efforts.
For more details, read the notes or listen to the recording.