OpenEMR Weekly Conference Call Meeting Notes

From OpenEMR Project Wiki

These are summaries of the OpenEMR weekly community conference call. Summaries begin with the July 14, 2026 meeting.

The call is open to anyone in the community — Tuesdays at 11:00 AM Pacific Time (2:00 PM Eastern). See OpenEMR Once Weekly Conference Call Details to join.

Calls are recorded and transcribed, and AI is used to produce these summaries.

Security details are omitted. If something has been misattributed or misstated, please raise it on the forum or at the next call and this page will be corrected.



2026

November 3, 2026
  • Topics:
    • LogiCoy pilots, and a planned PDMP module
    • Jerry's portal rebuild — replacing the Phreeze framework — and write audits for patient-facing apps
    • FHIR as the project's busiest area; whether to retire SMART v1 scopes for new clients
    • HTI-5 final rule — what was removed and what it means for OpenEMR
    • Should telemetry data be public?
    • PR review: when is CodeRabbit really done? PR 15015 merged on the call
    • Contributor priorities, approvals, and a possible FHIR theme
  • Detailed Summary:
October 27, 2026
  • Topics:
    • OpenEMR 8.5.0 released during the call — runtime Node is gone
    • Lessons from the PHP2Shell emergency, and when to send a heads-up email
    • LogiCoy publishes its e-prescribing module on Packagist
    • DAW Systems — two paths for vendors: community module or certified bundling
    • PR 14053 review leads to a cutoff for new code in legacy files (Twig and MVC)
    • Guidance for AI agents — AGENTS.md, skills, and architecture documents
    • New contributors, the review queue, and AI triage as next week's topic
  • Detailed Summary:
October 20, 2026
  • Topics:
    • Release 8.5.0 — branch this weekend, release the following week
    • Inferno now running in CI; API test coverage expanding to FHIR
    • E-prescribing — goal of a certified (b)(3) companion product; Ensora, Weno, LogiCoy, and DAW Systems
    • SMART on FHIR as the long-term model for e-prescribing integrations
    • Keeping the architecture coherent amid a flood of AI-generated PRs
    • AI agents in practice — scoped credentials and no PHI
    • Speeding up the logging engine (issue #2119)
    • Simon's PRs ready for review (not reached)
  • Detailed Summary:
October 13, 2026
  • Topics:
    • LogiCoy demos a Surescripts-connected e-prescribing module for OpenEMR
    • ONC (b)(3) e-prescribing certification — a possible path back, and the 2027–2028 deadlines
    • What a partnership, onboarding, and billing would look like
    • PR 13795 — LBF statements module to come into core
    • Core vs. module vs. separate package — a working rule
    • FHIR writes — an alert when enabling write-capable apps, instead of a global setting
    • A standing PR review slot in the weekly call
  • Detailed Summary:
October 6, 2026
  • Topics:
    • CCDA conversion to PHP nearly complete — Node leaving the runtime
    • FHIR writes — agreed to gate them off by default for 8.5
    • Confidential vs. public clients, and how write access is granted
    • Should procedures and record modification be writable?
    • Jerry's three-phase audit plan for patient-facing apps
    • Deprecating multisite and subdirectory installs — migration guide to be drafted
    • Telemetry shows users moving from XAMPP to WSL and Docker
  • Detailed Summary:
September 29, 2026
  • Topics:
    • The pull request backlog — 265 open and how to scale review
    • FHIR write APIs, patient-submitted data, and legal liability
    • How to extend OpenEMR — a preferred order from SMART on FHIR down to core
    • The permission model — ACLs, FHIR scopes, consent, and policy merging
    • Upgrading from 7 to 8 — practical advice
    • AI sandboxing approaches compared
    • Testing, and the case for API-first features
    • Deprecation decisions to revisit
  • Detailed Summary:
September 22, 2026
  • Topics:
    • Simon Quigley's open pull requests and the client's upstream-first approach
    • Release 8.4.1 — first patch release through the automation
    • Architectural themes ahead — Doctrine, templating, front controller, sessions
    • Why OpenEMR can't set HttpOnly session cookies (issue #2556)
    • Module system 1.0 scope and upgrade stability
    • A version-scoped workaround list for operators who can't upgrade yet
    • E-prescribing — Weno pharmacy coverage and DoseSpot
    • Two separate modules pages, and making third-party modules discoverable
    • Project website refresh and fundraising from support providers
    • Schematron moved from Node to PHP
  • Detailed Summary:
September 15, 2026
  • Topics:
    • New participant Simon Quigley, and his two open pull requests
    • Module policy — what belongs in core versus Packagist
    • Bundling third-party code, and the module registry idea
    • PR 13795 (LBF statements) — decision deferred to next week
    • Doctrine, schema drift, and static analysis visibility
    • Layout-based forms and the telemetry gap
    • Release — patient search and encounter form fixes
    • Vendor upgrade experience and module event registration
    • Payment processor abstraction
  • Detailed Summary:
September 8, 2026
  • Topics:
    • Release 8.4 — branch cut and the Inferno false-pass problem
    • Meeting moved to Google Meet; dropping the release call
    • Vendor hooks for preserving customizations across container upgrades
    • AWS image strategy — retiring Standard, keeping Express and ECS
    • Front controller status and performance work going upstream
    • Deptrac and static analysis for code quality enforcement
    • Node to PHP — Schematron, CCDA, and CQM
    • AI sandboxing and containment
  • Detailed Summary:
September 1, 2026
  • Topics:
    • Moving the weekly call to the foundation's Google Workspace
    • Business development — inpatient RFI assessment and where OpenEMR fits
    • PR 13706 — code set import automation, and the move to testable services
    • ICD-10 mid-year updates
    • Security process and workload
    • Release status and the 8.3 calendar bug
  • Detailed Summary:
August 25, 2026
  • Topics:
    • Introductions — Ian McDonald and Luis M. Santos
    • HL7 V2 to FHIR pipeline work and internationalization
    • Contract opportunity and vendor collaboration
    • DICOM/PACS viewer gap and the OHIF project
    • External IDP PR and the module-first position
    • Front controller, webroot deprecation, and the demo farm
    • Test data — demo database, Synthea, and openemr-cmd
    • Proposed file integrity and backup/upgrade modules
    • SBOM tooling, the customization problem, and module discovery
    • Release cadence reconciliation deferred
  • Detailed Summary:
August 18, 2026
  • Topics:
    • backup.php — whether to restore it to core, and better alternatives
    • Telemetry, the XAMPP dead end, and the Docker migration path
    • New attendee Bobby Anchanattu — external IDP and AI integration
    • PHI, business associate agreements, and LLM vendors
    • Sinch fax module and the case for a generic document interface
    • Module system status, front controller, and demo farm blockers
    • Release and Docker items
  • Detailed Summary:
August 11, 2026
  • Topics:
    • Meeting recording and summary conventions
    • Proposed removal of backup.php and documenting proper backup practice
    • Fax/SMS module — core vs. third-party, and provider testing accounts
    • Core/module coupling tracking issues (12222, 12221, 12217)
    • FlySystem and consistent document handling
    • Module ecosystem, publishing customizations, and forum organization
    • Release branch cut and rolling integration
  • Detailed Summary:
August 4, 2026
  • Topics:
    • The public CVE disclosure and what it says about severity inflation
    • PR 13374 (OAuth client ID in the audit log)
    • ACL gaps for AI agents and system credential grants
    • The future of backup.php
    • Neil Kimber's GAI modernization experiment
    • Release call moved to next week
  • Detailed Summary:
July 28, 2026
  • Topics:
    • Release 8.3.0 and semantic versioning under ONC constraints
    • Front controller: current state, benefits, and why adoption must be universal
    • Proposed enforcement path — PHPStan rule, soft deprecation, hard failure
    • Web server configuration impact for operators
    • Multisite deprecation
    • Demo farm and Docker front controller configuration
    • Docker refactor — consolidating to a single Compose file with profiles
    • NSF I-Corps update
  • Detailed Summary:
July 28, 2026
  • Topics:
    • Release automation complete; security release strategy and disclosure timing
    • Reporter recognition and the CVE/GHSA credit question
    • Downstream update obligations and what blocks version upgrades
    • CI and test infrastructure funding for embargoed security work
    • Getting users to update: admin warnings, webinars, and culture change
    • Module architecture — async vs. sync and the plugin migration path
    • Front controller as the prerequisite for the plugin system
    • NSF I-Corps program accepted; interview window August 3–13
  • Detailed Summary:
July 14, 2026
  • Topics:
    • Presentation: SDOH referral project (Char Miller)
    • The gap for community-based organizations and closed-loop referral
    • OpenEMR Care Sphere — four-phase plan from NSF I-Corps through SBIR
    • OpenEMR architecture and schema documentation
    • Open question: SDOH as a custom module or in core
  • Detailed Summary:
Retrieved from "https://www.open-emr.org/wiki/index.php?title=OpenEMR_Weekly_Conference_Call_Meeting_Notes&oldid=38026"