I’m posting where my work is heading, area by area, so maintainers and other contributors can see it ahead of time and say if any of it collides with their plans. I’ll keep this topic current. The work is AI-assisted (Claude Code), and every commit says so.
So far: 23 of my PRs have merged, 18 of them in 8.5.0. Thanks to shwetanktomar (#14626, #14631, #14634), monsterlag (#14785) and unvisible789 (#14864, merged) for picking up issues I filed.
PRs below are ready for review with green checks, except three that wait only on the dev-environment start-up fix in #14883 (marked *).
Referrals, end to end
Aim: a referral made in OpenEMR goes out, is tracked until the reply comes back, and closes, using FHIR so other systems can follow it.
- Ready: #14708* (referrals as FHIR ServiceRequests), #14711 (address-book organizations as FHIR Organizations), #14669 (FHIR Task inputs, outputs and owners); #14715 is a draft that tracks each referral as a Task.
- After those: replies and referral status; linking Direct messages to their referral (#14793).
- Module: Staff Worklist’s referral tab follows what core records.
Visits that modules can react to
Aim: every visit, however it’s created, goes through the same service, so modules can start work when a visit opens (care management time, intake forms, fee sheets).
- Ready: #14876 (check-in visits through EncounterService, with their ID and save event at once).
FHIR API answers
Aim: clients get a clear error for a bad request instead of a silent empty result, and can read what OpenEMR already stores.
- Ready: #14878* (a malformed search value answers with an OperationOutcome).
- Question for core: household size, income and housing status in FHIR Patient, so SMART apps can prefill them.
Quality measures and health center reporting
Aim: OpenEMR’s eCQMs count the right records, so a health center can produce its UDS report (due to HRSA each February 15), Title X and CCBHC reports from OpenEMR.
- Ready: #14584 and #14585 (C-CDA import keeps smoking status and body weight), #14456 (the newer of two same-date lab results wins).
- Two more eCQM fixes are ready on my fork (#14671), to open in whatever grouping suits the reviewers.
- Modules: UDS Report (now with HRSA’s own edit checks and last year’s published report beside this year’s), Title X Report and CCBHC Report, moving onto one shared reporting package.
Immunizations and public health
Aim: immunization records stay correct and reach registries and syndromic surveillance.
- Ready: #14613 (HL7 export works again from its tabs), #14457 (editing an immunization keeps its own data), #14455* (an empty shot record prints).
Bringing records in
Aim: a clinic moving to OpenEMR, or receiving records, gets complete and correctly coded data.
- Module: Migration imports another EHR’s FHIR export through OpenEMR’s own services; Units Check finds unit problems.
- Question for core: a service that writes lab orders, reports and results, so imports don’t need their own SQL.
- Open issue: #14657 (C-CDA import saves vital signs without converting their units).
Billing
Aim: discounts, claims and payments go through supported code paths.
- Follow-up once the 837I CLM05 fix lands: replacement and void claims (REF*F8).
- Question for core: a
src/service for posting payments and adjustments, so a module can post a sliding-fee discount the supported way. - Modules: Sliding Fee Discount, Revenue Cycle.
Forms and questionnaires
Aim: a patient answers once, at home or in clinic, and the answers reach the chart, the measures and the staff who act on them.
- Module: Clinic Forms (screening instruments, consents and notices, many in Spanish, with accessible PDFs).
- Question for core: questionnaire answers into the portal’s existing profile review.
- Question: payers’ prior authorization APIs start in January 2027, and their documentation templates are FHIR questionnaires, which core’s runtime renders. Core, or a module?
Upgrades and CI
Aim: an upgrade produces the same database as a fresh install, and sites can check before they upgrade.
- Ready: #14502 (CI compares an upgraded database with a fresh install).
- Tool: openemr-reference (install doctor, upgrade pre-flight check, upgrade notes from each release’s source).
- Open issue: #14601 (an
openemr:doctorconsole command).
Smaller fixes: #14464 (contact services record their errors), #14459 (pharmacy import), #14495 (employer details save).
Modules are installable add-ons on Packagist, with READMEs and staff guides on GitHub; code GPL, forms and documents CC0. They run on OpenEMR 7.0 and later (some need 8.1), and their shared library follows OpenEMR’s PHP minimum (8.3, as of 8.5).
How I work: PRs with green checks; fixes in legacy files move the logic into a src/ class with a thin call, which fits the new legacy-code rule; questions for core stay questions until the review queue has room. I’ve reviewed or tested about a dozen community PRs and am glad to do more in these areas. @ me.
If any of this collides with what you’re planning, or you’d rather something go another way, please say so here.