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 *
Active Squads
- 1 O3: Billing Module for small sites
- 2 O3: RDE Enhancement in-Chart (Retrospective Data Entry)
- 3 O3: Inventory / Stock & Commodity Mgmt for small sites
- 4 Content Packages Squad
- 5 O3: IPD Support V1: Ward & ADT Workflows
- 6 O3: React Form Engine
- 7 O3: Labs (v2)
- 8 O3 Interoperability and integrations at Facility Level
- 9 O3 Print Feature -Patient ID Stickers
- 10 O3: OPD Clinical Note
- 11 O3: Dispensing (v1)
- 12 O3: Appointments & Queues (v2)
- 13 O3: Icons & Pictograms (Epic)
- 14 O3: OPD Home Page Dashboard
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 Aug 29, 2024 | O3: Billing Module for small sites | Lead: @Gilbert Muthee , @JONATHAN AJAL ODORA With: @Antony Ojwang PalladiumMETSUCSF-TAP |
| Adding to EMR distro (O3 RefApp) | Pilot deployed in Kenya | Started by METS in August hackathon in Uganda; dev work further ongoing since Jan workshop in Kenya. Leveraging this previous OMRS module. Dependency note: the Billing app requires Stock Management, because | |||||
Warming Up Jul 24, 2024 | O3: RDE Enhancement in-Chart (Retrospective Data Entry) | Lead: @Paul Adams MEKOM Interested: PIH | User Testing of new designs done in June |
| Status: Design review done w PIH July 7; Hand-over to Mekom for Dev done July 24 About: This updated UI makes it more clear what visit someone would be in when editing information or entering retrospective info. | ||||||
Very Active
Aug 29, 2024 | O3: Inventory / Stock & Commodity Mgmt for small sites | Lead: @Samuel Lubwama With: @Hadijah Kyampeire METSPalladiumUCSF-TAP Interested: UW DIGI |
| Meeting: Stock Squad weekly on Tuesdays | Needs some tooling and config tweaks | Adding to EMR distro (O3 RefApp) | Pilot deployed in Kenya
Aiming to get to released in Uganda. | 80% done. Backend is ready; addressing OWA dependencies; aiming for first release as part of next RefApp release. Finishing inventory connection to Dispensing UX; multi-drug flows & multi-location filtering. Updated styling for cross-EMR consistency. | |||
ActiVE Aug 29, 2024 | Content Packages Squad | Lead: @Ian Bacher UW DIGI UCSF-TAP | Documentation (WIP) SDK work: 50% done |
|
|
| Introduces a new content.properties file and tooling to add these into your distro.properties file. Work also happening to make 1st content package (HIV Treatment) more configurable (Epic here). | ||||
Active Aug 29, 2024 | O3: IPD Support V1: Ward & ADT Workflows | Lead: @Fiona Anderson With: @Paul Adams PIH Mekom Interested: MSF, METS, UCSF, UW DIGI |
|
| User testing done in March in Sierra Leone (PIH). MSF: Testing mockups; plan to get user validation at site visits in Iraq. Daily standups at 9am EDT; led by Chi Bong Dependency: Adding to RefApp requires adding EMR API to O3 RefApp | ||||||
Active Aug 29, 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 | Updated release including big library change: In progress 🐛 Ongoing bug fixes as discovered | Successful roll out in production sites across Uganda/METS. Now: focused on PIH needs. Note: Next major release to include substantial library change (migrate from Formik to RHF).
| |||||
Warming Up Aug 29, 2024 | IPS Squad | Lead: @Reagan patrick Makoba UW DIGI |
|
| EPIC |
|
|
|
| ||
Warming Up Aug 29, 2024 | O3: MPI/CR Integration (within Search and Registration) & O3: Client Verification / duplicate check | Lead: @Samuel Male @Reagan patrick Makoba UW DIGI Interested: Palladium
|
|
|
Side note: Need to check against the Verification / duplicate check workflow Ampath working on; Much progress made during February AMPATH O3 Hackathon | ||||||
Active Aug 29, 2024 | O3: Labs (v2) | Lead: @Casey Iiams-Hauser & @Wamathaga Kamau UCSF-TAPUW DIGIMETSVolunteers Interested: MSF, PIH | Early designs here |
Need to confirm automated testing plan
| Bug fixes ongoing | Lab order Next: 12 Video overview of what has been done, as of July 2024: Video here | |||||
Active Aug 20, 2024 | O3 Interoperability and integrations at Facility Level(distro-his) | UCSF-TAPMETSMEKOMMSF Lead: @Eudson Bambo & @Romain Buisson& @Michael Bontyes | & |
| dev-his.openmrs.org server setup in progress Question: What’s happening now in August to create a clear plan where people would transition from HIS-Lite modules to actual ERP systems? | ||||||
Active Aug 29, 2024 | O3 Print Feature -Patient ID Stickers(Epic) | Lead: @Michael Bontyes & @Joshua Nsereko MSF Interested: PIH |
|
UI Improvements ongoing | MSF team tested beta release with printers! | Goal: Print patient ID stickers, and later others eg Lab stickers, discharge paperwork, etc. Testing with both thermal printers (for patient ID stickers) and regular printers (eg A4 labels for Lab) | |||||
Active Aug 22, 2024 | O3: OPD Clinical Note(Generic OPD Form) | UCSF-TAPMETS Lead: @Wamathaga Kamau |
|
|
|
| General purpose detailed SOAP note is the current focus. | ||||
Cooling Down Aug 19, 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. As of Aug 22, adding support related to power down-times. | ||||||
Cooling DOwn Aug 29, 2024 | O3: Appointments & Queues (v2) | Lead: @Fiona Anderson With: @Mark Goodrich @Chi Bong Ho 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. Some review of changes needed for integration with Stock Management. | ||||||
Emerging Interest Areas | |||||||||||
Cooling Down May 23, 2024 | O3: Icons & Pictograms (Epic) | Lead: @Grace Potma and @Paul Adams |
| ||||||||
Warming Up | O3: RDE Bulk Data Entry ("Fast Data Entry") enhancements | Lead: _____ Interested: ICRC, Palladium | |||||||||
No Longer Active Aug 20, 2024 | O3: OPD Home Page Dashboard | UCSF-TAPMETS Lead: @Laureen Omare |
Planned for beta.20 release |
| |||||||
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 | |||||||
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 | ||||||||||
| 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. |