Hi everyone
I’m Raj, a GSoC 2026 contributor with OpenMRS. I’d love to share what I’ve been building and hear your thoughts.
The project: Native O3 Frontend for the Audit Trail
OpenMRS already records a detailed audit trail through the auditlogweb module (built on Hibernate Envers) — but until now there hasn’t been a native way to see that history inside OpenMRS 3. My project brings it into the O3 UI, so we can answer the question that matters most in a medical record system: who changed what, and when.
I built two microfrontends:
1. Admin Audit Log Dashboard (esm-admin-auditlog-app)
A system-wide view under System Administration → Manage audit logs:
-
Filter by entity type, user, and date range
-
Colour-coded event tags — Created, Updated, Deleted
-
Expand any row to see the exact field-level changes (previous value → new value)
-
Server-side pagination, shareable filter URLs, and a search-first view so you’re never flooded with noise
2. Patient Audit History tab (esm-patient-audit-history-app)
The same history, scoped to a single patient, as a new Audit History tab in the patient chart:
-
Every change to that patient, with the same colour-coded tags
-
Field-level diffs, plus the related records that changed in the same action
-
Loads gracefully even when the audit backend isn’t available, so it never breaks the chart
Why it matters
Together, these give administrators and clinicians clear visibility into the history of any record — supporting accountability, patient safety, and compliance — right inside the tools they already use, without anyone having to dig into the database.
Blog posts (my journey through the program)
Pull requests
Demos
I’d be really grateful for any feedback — on the UX, the component design, naming, accessibility, or anything I could do better. Please do take a look at the PRs and demos and let me know your thoughts. @dennis @jayasanka @nethmi @ibacher
A big thank you to my mentors @olewandowski and @manojll , and to the wider OpenMRS community for all the guidance and support.
Regards Raj