Release Notes 3.8.0 DRAFT IDEAS
Have a feature to request or suggest?
Post: Share on Talk or in the #o3-releases slack channel and mention your release goal (e.g. date or version number).
Discuss: For further verbal discussion you can also converse with the community on the weekly O3 Squad Calls or the daily - see the Community Calendar for call dates and times: om.rs/cal
Timing: Please communicate as early as possible to make sure your feature/work has enough time to be considered for the release!
Release Managers: Delete this blurb when release is nearing readiness.
🔦 Key Points
📆 Cut Date: 2026-____
📆 Release Date: 2026-____
Release Manager: ______
Key Features:
Google Summer of Code 2026: Summer of Code 2026
⑴ Patient Visit Summary Printing for OpenMRS O3
⑵ Integrate O3 with the Authentication module
⑶ Improved Appointments Calendar View
⑷ A Native O3 Frontend for the Audit Trail
⑸ Archiving Voided Data
⑹ Extend Audit Log Module
⑺ Support for horizontal scaling of OpenMRS instances
⑻ Service Queues
Program Enrolment
PIH drafted some requirements & @Dennis Kigen has picked this task
Chart Search AI Feature
Iterate, incorporate feedback from the community
Audit logging for every AI-generated suggestion accepted or rejected by clinicians
Growth Chart
Billing Features (Continuation)
Auto-generation of bills from procedure orders (extending the drug + lab pattern)
Security Improvements
Continuation
Architectural Improvements
Migration to React 19
Updating Angular Form Engine
Move from Concept UUIDs → Concept Mappings, i.e., form schema, conf schema, etc. (for compatibility)
Upgrade ESLint and Prettier packages (automatic code formatting)
Upgrade LINT rules
Creating shared packages for ESLint
Shared Config for ESLint and Prettier, Vitest
Moving from Prettier to Bio
Retrospective Data Entry (RDE)
DRC Needs include
Capturing of previous legacy/historical lab data
Capturing of previous treatments
Platform-related
@Daniel Kayiwa @Wikum Weerakutti What should we focus on in the next release
⚠️ Breaking Changes:
_______
Where to find it: Demo at o3.openmrs.org (admin/Admin123) or download here: openmrs.org/download/
👷 Contributors
Special thanks to the following community PR reviewers:
DIGI: @Ian Bacher
OpenMRS: @Dennis Kigen, @Jayasanka Weerasinghe, @nethmi, …
PIH:
Palladium:
METS:
MSF Madiro:
Template note: Reach out to @beryl; she will be the primary builder of this list.
Thank you so much to the following contributors - you make releases like this possible! Alphabetically by Organization affiliation:
CSaude:
Health IT (UoN):
ICRC:
Intellisoft:
Madiro:
Mekom:
METS:
OpenMRS Support:
Palladium-Kenya:
PIH:
UCSF:
UW ITECH DIGI:
Independent Contributors:
Thank you Translation Contributors!
[Language] updated by [contributor-name]
Contributor Metrics
# PRs included: ___
# of Orgs involved: ___
% from OpenMRS Inc. Global Support: ___%
🔦 Highlights for Implementers
Change: Brief description. |
|
Change: Brief description. |
|
Change: Brief description. |
|
📸 Example Visual Changes
🔍 Detailed Changelog
Code:
Distro RefApp
Reference Application 3.5.0 (<-- needs hyperlink like this)
Frontend Modules
Cohort Builder v4.0.3 (patch) (<-- example only)
Patient Chart v10.0.0 ⚠️ (major - breaking change) (<-- example only)
Backend Modules
Core 2.7.4 (<-- example only)
Steps to figure this out: (see also 2nd video in this Talk thread:
Backend Contributions to EMR releases: Why and How )1. Find What Backend Modules Changed: Compare previous release’s distro/pom.xml file to this one, e.g.:
Comparing 3.3.1...3.4.0-rc.2 · openmrs/openmrs-distro-referenceapplication2. Use release notes for those to figure out who contributed, e.g.
Releases · openmrs/openmrs-module-webservices.rest