OpenEMR Admin Meeting Notes - 2026-03-17

:shamrock:

General update on DB changes - lots of stuff in flight, largely looking solid. We may want to integrate the DRID script into CI, since some of the changes inadvertently disrupted the upgrade process.

GHA: other projects seem to run quite a bit faster. Maybe there’s a program within GH (or some other “runs-on” path through third-party hosting) that would allow greater parallelism. I noticed the test suite on phpstan-src ran massively faster than ours does. Areas to explore: improve “collect” or the fan-out process, self-hosted, reach out to other large OSS projects, etc?

Packaging, front controller, standard configs:

  • Initial front-controller implementation by Firehed · Pull Request #9943 · openemr/openemr · GitHub is a near-working prototype
  • Largely blocked on having an opinionated webserver config that funnels requests to the front controller
  • Exploration of creating a “install validation” module in addition to standard configs
  • Communicate need to run official configs (or equivalence) in an upgrade guide
  • Discussion of trying to leverage globals.php vs new file
  • Waaaay back when (~2003), there was a front controller?
  • General consensus that we want to move forward on this. I will make some updates to that PR to bring it up to date, and explore including “official” webserver configs.

Tentative 8.0.0.2 release meeting tomorrow. Waiting to hear back on availability.

UI updates: demo next week!

2 Likes

Can we talk about CI/GitHub Actions? Subtopics:

  1. enabling auto-merge on the repo? (This would require “required checks” enabled as well.)
  2. Changing the required AI annotation rules a bit. (Replace inline AI code annotations with commit trailers · Issue #11242 · openemr/openemr · GitHub)
  3. Requesting compute – OSU OSL compute, GitHub “free enterprise”, etc.