Squad Dashboard
What is a Squad? A squad is a group of community members working autonomously on specific, discrete solutions to a shared problem(s). Our strongly recommended guideline is that Squads should have 2 or more Implementing Organizations working on them, as we have found this consistently yields (1) more generalizable, re-useable solutions, and (2) successfully co-maintained code. Further history on the OpenMRS Squad model here.
(For things that are still "really nice to know and should be visible at some level even though there is not quite 2 implementing orgs working on it", we'll track these as Epics here too, within reason.)
* SHARE ON SCREEN REGULARLY AT O3 MEETINGS *
Status & Date last updated here | Squad or Mini/ Feature Squad | Who | 1: Individual Discovery | 2: Sharing Interest
| 3: Requirements & Design Shared
| 4: Prioritization & Planning | 5: Development
| 6: Testing
| 7: Release
| 8: Deploy & Evaluate
| Other Notes or Key Points |
---|---|---|---|---|---|---|---|---|---|---|---|
Very Active Apr 30, 2024 | O3: React Form Engine | Lead: @Samuel Male & @Eudson Bambo UCSF-TAP OMRS INC METS MEKOM UW DIGI Interested: PIH | Discussions on group O3 Squad call | Aiming for RefApp readiness within May | Angular Parity Feature Tracker here METS rolling out trial in production week of April 30
| ||||||
Very Active Apr 25, 2024 | O3: Billing Module for small sites | Lead: @Antony Ojwang & @Jacinta Gichuhi With: @Gilbert Muthee PalladiumMETSUCSF-TAP |
| Pilot deployed in Kenya | Started by METS in August hackthon in Uganda; Development now further ongoing during Jan workshop in Kenya. Leveraging this previous OMRS module
| ||||||
Very Active
Apr 25, 2024 | O3: Inventory / Stock & Commodity Mgmt for small sites | Lead: @Samuel Lubwama & @Keziah Muiruri With: @Eudson Bambo METSPalladiumUCSF-TAP Interested: UW DIGI | | Pilot deployed in Kenya | Backend is ready; pending addressing OWA dependencies; aiming for first release as part of next RefApp release. | ||||||
Very Active Apr 25, 2024 | O3: Appointments & Queues (v2) | Lead: @Fiona Anderson With: @Paul Adams PIHPalladium Interested: METS, UCSF-TAP, ICRC, MSF | Slack: #appointments-and-queues Config redesign of tables |
Bug fixes | Functional Spec and Gap Analysis with current implementation | ||||||
Active Apr 25, 2024 | O3: Labs (v2) | Lead: @Casey Iiams-Hauser & @Wamathaga Kamau UCSF-TAPUW DIGIMETS Interested: MSF, PIH | Early designs here |
|
Auto-tests underway | Plan: Order Status coming to RefApp in beta.19 (April)! |
| ||||
Active Apr 25, 2024 | O3: Dispensing (v1) | Lead: @Mark Goodrich PIHUCSF-TAP |
| RefApp V1 of Dispensing now live in Sierra Leone | Pilot launched in PIH Sierra Leone OPD site Oct 2023. | ||||||
Warming Up Apr 30, 2024 | Content Packages Squad | Lead: @Romain Buisson UCSF-TAP MEKOM UW DIGI MSF |
|
|
|
|
|
| |||
Active Apr 29, 2024 | O3 Interoperability and integrations at Facility Level | UCSF-TAPMETSMEKOMMSF Lead: @Eudson Bambo & @Romain Buisson& @Michael Bontyes |
| Next: | |||||||
Warming Up Apr 25, 2024 | O3: IPD Support V1: Ward & ADT Workflows | Lead: @Paul Adams PIH Mekom Interested: MSF, METS, UCSF, UW DIGI |
| Designs in Zeplin
| Requirements alignment ongoing btwn PIH and Mekom Mekom expects development to start ~ end of March MSF: Testing mockups; getting user validation at site visits in Iraq | ||||||
Active Apr 25, 2024 | O3: OPD Home Page Dashboard | UCSF-TAPMETS Lead: @Laureen Omare |
Planned for beta.19 release |
| |||||||
Active Mar 7, 2024 | O3: OPD Clinical Note (Generic OPD Form) | UCSF-TAPMETS Lead: @Wamathaga Kamau |
| Talk Thread |
| ||||||
No Recent Activity Mar 28, 2024 | Offline Mode for Community Outreach (external app connection) | Lead: ____ (TBD; ICRC) ICRCMSfAmpathPIH | Notes from Feb 27 exploratory discussion (roundtable, needs, next steps) | ICRC-MSF/Madiro looking into options | |||||||
On Hold Apr 25, 2024 | O3: MPI/CR Integration (within Search and Registration) & O3: Client Verification / duplicate check workflow (Epic) | Lead: @Samuel Male UW DIGI UCSF-TAP Palladium Lead: @Donald Kibet , support and adaptation by @Dennis Kigen
|
Epic for Client Registry Module → Dan & Sam to link up TODO: 1 pager format for UI consensus | Currently Paused while RFE Hackathon is the focus for orgs | |||||||
Done Mar 28, 2024 | O3: Icons (Epic) | Lead: @Grace Potma and @Paul Adams | |||||||||
Stalled Mar 28, 2024 | O3: RDE Enhancement in-Chart (Retrospective Data Entry) | Lead: _____ PIH MEKOM | Design updates in progress for pst | ||||||||
Emerging Interest Areas | |||||||||||
Warming Up Mar 28, 2024 | O3 Print Feature - Patient ID Stickers | MSF is looking to print patient identification stickers, and later potentially other content of the EMR such as Lab stickers, discharge paperwork, etc. | (Early days) Lead: @Michael Bontyes & ? |
| |||||||
O3: Enhance Login Page Configurability | Lead: @Jayasanka Weerasinghe | Where: Epic | |||||||||
Warming Up | O3: RDE Bulk Data Entry ("Fast Data Entry") enhancements | Lead: _____ Interested: ICRC, Palladium | |||||||||
Warming Up | O3 User Guide | Lead: _____TBD | (Early days) MSF METS Faimer? PIH? Mekom? | ||||||||
O3: UI for esm Module Management (similar to OMOD one) | Already in the API! | Early Days METS? | Later, could content also be loaded this way? E.g. "Add NCD Template"? "UG-EMR content package"? | ||||||||
eReferrals | KenyaEMR team has an eReferral and cross-facility record data population flow they'd like to add to O3 RefApp. - Cmty Showcase Nov 2023 | (Early days) Palladium | |||||||||
O3 Feature: Encounter & Visit Workflow UI | (Early days) PIHPALLADIUM | ||||||||||
Built-in Reports Visualizer | METS has an iteration that leverages JS tools that could be adapted into O3 RefApp. - Cmty Showcase Nov 2023 | (Early days) METS | |||||||||
MAR: Medication Admin Record | (Early days) UW DIGI | ||||||||||
| Bed Management (IPD) |
|
|
|
|
|
|
|
|
| Note: METS has an iteration that leverages Bahmni Bed Mgmt backend module that could be adapted into O3 RefApp. - Cmty Showcase Nov 2023. Data model of Bahmni Bed Management seems like one to follow; build in OpenMRS |
| O3 Modular Implementations | Lead: _____TBD MSF |
|
|
|
|
|
|
| How to best organise modularity and configuration of OpenMRS 3 modules and Docker images across implementations - especially in the context of the growing momentum of the O3 squads and collaborative features. |