OpenEMR Project Wiki - Recent changes [en]

Board Meetings:2026-11-11

David Eschelbacher — Thu, 12 Nov 2026 11:04:49 GMT

← Older revision		Revision as of 11:04, 12 November 2026
Line 21:		Line 21:
	:''Italicized indented passages are background and clarification added after the meeting, not part of the board’s proceedings.''		:''Italicized indented passages are background and clarification added after the meeting, not part of the board’s proceedings.''

	'''PDF version:''' [https://www.open-emr.org/wiki/images/x/xx/~~OpenEMR_Foundation_Board_Meeting_Minutes_2026~~-11-11.pdf 📄 OpenEMR Foundation Board Meeting Minutes 2026-11-11.pdf]		'''PDF version:''' [https://www.open-emr.org/wiki/images/d/d6/OpenEMR_Foundation_Board_Meeting_Summary_2026-11-11.pdf 📄 OpenEMR Foundation Board Meeting Minutes 2026-11-11.pdf]

	== Call to Order ==		== Call to Order ==

File:OpenEMR Foundation Board Meeting Summary 2026-11-11.pdf

David Eschelbacher — Thu, 12 Nov 2026 11:04:09 GMT

David Eschelbacher uploaded File:OpenEMR Foundation Board Meeting Summary 2026-11-11.pdf

New page

Board Meetings:2026-11-11

David Eschelbacher — Thu, 12 Nov 2026 10:57:21 GMT

← Older revision		Revision as of 10:57, 12 November 2026
Line 1:		Line 1:
	''← [[OpenEMR Foundation Board Monthly Meeting Notes\|All Board Summaries]]''		''← [[OpenEMR Foundation Board Monthly Meeting Notes\|All Board Summaries]]''

	'''OpenEMR Foundation Board Meeting ~~Minutes~~'''		'''OpenEMR Foundation Board Meeting Summary'''

	'''Date:''' November 11, 2026		'''Date:''' November 11, 2026

	~~'''Status:''' ''Draft minutes — subject to board approval''~~

	'''Board members present:''' Steve Waite (President, Treasurer); David Eschelbacher (Vice President); Brady Miller (Secretary, Executive Director); Asher Densmore-Lynn (left during the 2028 CEHRT strategy discussion); Sherwin Gaddis; Brad Sharp.		'''Board members present:''' Steve Waite (President, Treasurer); David Eschelbacher (Vice President); Brady Miller (Secretary, Executive Director); Asher Densmore-Lynn (left during the 2028 CEHRT strategy discussion); Sherwin Gaddis; Brad Sharp.

Board Meetings:2026-11-11

David Eschelbacher — Thu, 12 Nov 2026 10:56:25 GMT

Created page with "''← All Board Summaries'' '''OpenEMR Foundation Board Meeting Minutes''' '''Date:''' November 11, 2026 '''Status:''' ''Draft minutes — subject to board approval'' '''Board members present:''' Steve Waite (President, Treasurer); David Eschelbacher (Vice President); Brady Miller (Secretary, Executive Director); Asher Densmore-Lynn (left during the 2028 CEHRT strategy discussion); Sherwin Gaddis; Brad Sharp. '''Boa..."

New page

''← [[OpenEMR Foundation Board Monthly Meeting Notes|All Board Summaries]]''

'''OpenEMR Foundation Board Meeting Minutes'''

'''Date:''' November 11, 2026

'''Status:''' ''Draft minutes — subject to board approval''

'''Board members present:''' Steve Waite (President, Treasurer); David Eschelbacher (Vice President); Brady Miller (Secretary, Executive Director); Asher Densmore-Lynn (left during the 2028 CEHRT strategy discussion); Sherwin Gaddis; Brad Sharp.

'''Board members absent:''' Ravi Kafle; Rachel Ellison.

'''Staff:''' Stephen Nielson (Director of Engineering).

'''Guests:''' Maxine Radcliffe (Open Plan IT); Pete Boyd (Founder and CEO, Open Plan IT); Jerry Padgett (OpenEMR contributor).

'''Recorder:''' David Eschelbacher.

'''Quorum:''' six of the eight directors were present at roll call, and a quorum was declared.

:''Under §4.8.1 of the Foundation’s [https://github.com/openemr/foundation-minutes/blob/master/bylaws/CURRENT.md bylaws], a majority of the directors in office — five of the current eight — constitutes a quorum, and no business may be considered at any meeting at which a quorum is not present. Delaware’s default rule ([https://delcode.delaware.gov/title8/c001/sc04/index.html DGCL §141(b)]) is also a majority of the total number of directors.''

:''Italicized indented passages are background and clarification added after the meeting, not part of the board’s proceedings.''

'''PDF version:''' [https://www.open-emr.org/wiki/images/x/xx/OpenEMR_Foundation_Board_Meeting_Minutes_2026-11-11.pdf 📄 OpenEMR Foundation Board Meeting Minutes 2026-11-11.pdf]

== Call to Order ==

* '''Opening:''' the meeting was held by video conference at the board’s regular time, 1:00 p.m. Eastern on the second Wednesday of the month. Steve Waite presided. The call-to-order time was not stated in the recording.
* '''Roll call:''' taken by Steve Waite (see Attendance). Stephen Nielson and Jerry Padgett were noted as present. Steve Waite declared a quorum.

=== Approval of the October 14, 2026 Minutes ===

* Steve Waite said he had reviewed the [https://github.com/openemr/foundation-minutes/blob/master/2026-10-14-Board.md October 14, 2026 minutes] and asked for any objections to approving them. '''Approved''' without objection (“hearing none”). No formal motion or second was stated. Steve Waite thanked Brady Miller for preparing them.

== Welcome and Opening Thoughts ==

* The meeting moved directly to roll call, with no separate opening remarks. The agenda links to the project’s [https://github.com/openemr/openemr/blob/master/CODE_OF_CONDUCT.md Code of Conduct].
* '''Guests:''' Maxine Radcliffe and Pete Boyd of Open Plan IT joined during the Governance Committee update and were welcomed.
* '''Introductions:''' Pete Boyd — Founder and CEO, Open Plan IT.

== Consent Agenda ==

''Roll call and approval of the October 14 minutes are recorded above, under Attendance and Call to Order.''

=== Governance Committee Update ===

* David Eschelbacher reported that, after several attempts, a meeting with OpenCoreEMR has been arranged for next week. The partnership negotiations continue, and the next steps will depend on that meeting. There was no further public update.

:''The Governance Committee’s main work has been negotiating a website partnership with OpenCoreEMR (OCE), OpenEMR’s largest vendor and largest code contributor ([https://github.com/openemr/foundation-minutes/blob/master/2026-10-14-Board.md October 14 minutes]). The committee is also taking on the e-prescribing partner discussion below.''

=== Treasurer’s Report ===

* '''Financial statements:''' the October 31 balance sheet and the October profit-and-loss statement are attached to the [https://community.open-emr.org/t/openemr-foundation-board-meeting-november-11-2026/27190 agenda thread]. Steve Waite said there was little activity to report this month.
* '''Open Collective:''' the agenda lists a balance of $2,362.77 ([https://opencollective.com/openemr Open Collective]).
* '''Cloud credits:''' the Foundation’s Amazon Web Services (AWS) credits appear to have run out, so it is now paying a small monthly amount for the cloud servers that host the OpenEMR demos. Steve Waite will look into renewing the credits, which the Foundation has received in the past through AWS’s open-source program and through TechSoup.

:''AWS has offered promotional credits to open-source projects since 2019, for projects under an OSI-approved license that are not dominated by a single vendor ([https://aws.amazon.com/blogs/opensource/aws-cloud-credits-for-open-source-projects-affirming-our-commitment AWS]). TechSoup, a nonprofit technology clearinghouse, separately offers eligible nonprofits AWS credits for a small administrative fee; for organizations with budgets under $10 million, $1,000 in credits valid for 12 months costs $95 ([https://page.techsoup.org/amazon-web-services-for-nonprofits TechSoup]).''

* '''ONC certification campaign payout:''' on the agenda; not discussed.

=== Trademark Application ===

* Steve Waite reported that the USPTO has issued an office action refusing registration of the application as filed. The Foundation’s attorney is preparing a response, and the Governance Committee will review its wording by e-mail before it is filed. He remains optimistic. The application covers the OpenEMR name; the logo is a separate mark that also needs to be re-established. The Foundation previously held registrations for both, which lapsed for administrative reasons.

:''An office action is the USPTO examining attorney’s letter setting out why an application cannot be registered as filed. It is not final: the applicant generally has three months to respond, with one three-month extension available for a fee, and can answer with argument and evidence. Missing the deadline abandons the application ([https://www.uspto.gov/trademarks/apply/response-time-period USPTO]).''

== Discussion Topics ==

=== OpenEMR Project Updates ===

* '''Releases:''' Brady Miller reported that OpenEMR 8.5.0 was released on October 27, and 8.6.0 is expected in about three weeks. The goal remains a monthly release.
* '''Security:''' security work continues.
* '''PR shepherding:''' to work through the pull-request queue faster, Brady has written an AI-assisted process for reviewing open PRs in batches, by subject or by author. It checks whether each PR has dealt with the automated CodeRabbit review comments, flags whether it looks ready to merge, and gives a quick review. A maintainer then decides by category: a fix that looks good can simply go in, while an architectural change or a new feature needs more thought. It is a living document, and he hopes others will use it. Many open PRs turned out to be simple fixes and easy wins, and the open PR count is back to about 280. Reviewing promptly also helps: one contributor’s FHIR test suite was merged within a day.
* '''Priorities:''' keep the monthly releases going, keep security fixes flowing, and keep PRs moving. Fixes and FHIR testing are preferred over new features, which take much more review effort.

:''The process is documented in the repository under [https://github.com/openemr/openemr/tree/master/docs/pr-shepherding docs/pr-shepherding], added on November 8 ([https://github.com/openemr/openemr/pull/15141 #15141]) and refined since. It is split into small documents so an AI agent can load only the phase it is working on: stocktake, per-PR review, and deliverables. CodeRabbit is an AI code-review service that comments on pull requests. Several contributors added FHIR API test coverage in early November (for example, [https://github.com/openemr/openemr/pull/15146 #15146]). The [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-11-03 November 3 weekly call] also discussed how to tell when an AI-reviewed PR is really ready.''

* '''The cost of AI tools:''' the project has no open-source credits from AI providers, so contributors are paying for these tools themselves. An application to Anthropic’s open-source program has had no reply. Heavy review work can use up a subscription’s limits quickly, and there was concern that subsidized subscription plans may not last. Ideas discussed:
** Choose lower-cost models deliberately. It was suggested that newer default models can use many more tokens for modest gains, and that being explicit in instructions can make up much of the difference.
** Consider other providers, or local models, although hardware able to run good local models is currently expensive.
** A shared team account would make collaboration easier, but the project cannot afford one without a nonprofit or open-source discount. In the meantime, knowledge can be shared through agent guides and skills committed to the repository.
** The cost of AI tools is something the project will need to plan for.

:''Both major providers run programs for open-source maintainers. Anthropic’s Claude for Open Source offers qualifying individual maintainers a complimentary subscription for six months. Applications are reviewed on a rolling basis, and applicants who are not approved are not notified, so silence is not a decision ([https://www.anthropic.com/claude-for-oss-terms terms]). OpenAI’s Codex for Open Source offers six months of ChatGPT Pro with Codex, plus API credits from a $1 million fund for projects that use Codex in work such as pull-request review ([https://developers.openai.com/codex/community/codex-for-oss OpenAI]). Both are aimed at individual maintainers or projects rather than at an organization-wide team account.''

=== Open Plan IT Update ===

* '''Agenda change:''' Steve Waite moved this item up and renamed it from “Ireland update” to “Open Plan IT update,” since Open Plan IT expects to attend regularly.
* '''FHIR mapping and clinical input:''' Maxine Radcliffe said the choices made in mapping clinical data to FHIR have clinical-architecture implications, and Open Plan IT expects to do some work in this area. Decisions about how things are represented will need substantial clinical input, and they must work internationally; units such as Fahrenheit and Celsius are one example. She wants to avoid duplicating work and to share what is learned. She believes many clinicians would like to contribute, if the work is visible to them.
* '''Where to discuss it:''' it was suggested that detailed discussion belongs in the Tuesday weekly community call (2:00 p.m. Eastern), while the board meeting stays on strategy. It was acknowledged that there is a gap: the project has no clinical informatics group or governance at present. Whether one should sit under the Foundation or with the technical team was left open. In the chat, Stephen Nielson noted that contributions are made through GitHub pull requests and that there is no formal team on this.
* '''Referrals:''' Jerry Padgett said he will post a forum topic introducing OpenEMR’s referral functionality: what kinds of referral are possible and how the loop is closed.
* '''Grant follow-up:''' Maxine Radcliffe and Sherwin Gaddis had planned to discuss a grant opportunity in the Netherlands. She asked to be reminded, and Sherwin Gaddis will follow up.

:''FHIR records measurements with UCUM unit codes. The US Core profile for body temperature, for example, requires the UCUM code system and a bound list of temperature units, so Celsius and Fahrenheit are both representable ([https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-body-temperature.html US Core]). Many mapping choices are clinical, not technical: which code represents a finding, which units are expected, and how local practice is captured. That is why clinical safety standards abroad, such as England’s DCB0129 and DCB0160, require named clinical oversight ([https://england.nhs.uk/long-read/national-review-of-clinical-risk-management-standardsdcb0129-and-dcb0160-supporting-information/ NHS England]). For referrals, HL7’s Bidirectional Services eReferral (BSeR) guide describes closed-loop referral exchange in FHIR ([https://www.hl7.org/fhir/us/bser/Introduction.html BSeR]). The weekly call details are [https://www.open-emr.org/wiki/index.php/OpenEMR_Once_Weekly_Conference_Call_Details on the wiki].''

=== OpenCoreEMR ===

* No representative of OpenCoreEMR was present, and there was no separate update. The negotiations are covered under the Governance Committee update.

=== 2028 CEHRT Strategy: Certified Partner Program for eRx, RTPB and ePA ===

* '''The question:''' Steve Waite introduced the item. To be certified for practices taking part in Medicare’s Promoting Interoperability program in 2028, OpenEMR will need certified e-prescribing (eRx), real-time prescription benefit (RTPB) and electronic prior authorization (ePA). These are not yet lined up, so planning should start now, beginning with eRx; the eRx vendor can probably also handle RTPB. The agenda lists three potential eRx partners: DAW Systems, Ensora and LogiCoy.
* '''Regulatory update:''' Stephen Nielson summarized ONC’s information session on the HTI-5 final rule, which takes effect on December 28. It removes a number of certification criteria, including Direct messaging and some C-CDA requirements, and reduces real-world testing reporting, while keeping the security requirements. Nothing in the eRx area puts OpenEMR’s certification at risk at the start of 2027; the eRx requirements remain on the 2028 timeline. Safety-enhanced design requirements were also simplified, so an eRx partner could do most of the certification work. A further rule, HTI-6, with FHIR-related proposals, is expected soon.
* '''Approach:''' building and certifying an eRx system in-house was not favored, and certifying with all three vendors would strain the project’s resources, so a certification partner is needed. It was noted that the existing Ensora (formerly NewCrop) integration is not currently certified for OpenEMR.
* '''LogiCoy in testing:''' a community member has had LogiCoy’s module running in testing for about two weeks. It is integrated natively: it uses OpenEMR’s existing prescription and user screens rather than a bolted-on interface, it supports the configuration needed for electronic prescribing of controlled substances (EPCS), and LogiCoy offers arrangements both for direct customers and for resellers. It was noted that LogiCoy has been taking part in community meetings and working with the community, and that it has a working product.
* '''Direction:''' the prevailing view was to move forward with LogiCoy as a certified partner, with its module potentially becoming a core module, and to work out an agreement with the Foundation through the Governance Committee. The general shape discussed included revenue sharing and responsibility for certification costs. The committee will start by setting up a meeting with LogiCoy.
* '''Non-exclusive:''' the view was that any arrangement should be non-exclusive, so that other vendors can pursue the same path. It was noted that a vendor may be less willing to fund certification without exclusivity, which will be part of the discussion.
* '''Fairness and openness:''' a question was raised about whether choosing a partner without an open call is fair to other vendors. Views differed:
** Publish the criteria for certified partners, and list approved partners publicly, while keeping individual contracts private. It was noted that directors have signed conflict-of-interest commitments, and that a public statement could make clear that no individual member benefits.
** Send a request for proposals to the vendors that have already shown interest.
** A formal request for proposals would cost time, could draw low-quality responses, and would not change the fact that one vendor has already done the work.
** Relying on a single vendor carries risk, which keeping the arrangement non-exclusive is meant to address.
* '''Outcome:''' consensus to pursue a non-exclusive certified-partner agreement with LogiCoy through the Governance Committee, starting with a meeting. No formal motion was made. Asher Densmore-Lynn left during this item; five directors remained.

:''The 2028 requirements come from two rules. HTI-4 (July 2025) updates e-prescribing, (b)(3), to NCPDP SCRIPT 2023011 alone from January 1, 2028. From the same date, any module certified for e-prescribing must also be certified for real-time prescription benefit, (b)(4), which joins the Base EHR definition. HTI-4 also added three FHIR-based prior authorization API criteria ([https://healthit.gov/wp-content/uploads/2025/08/HTI-4-Final-Rule-Overview-Fact-Sheet_508.pdf HTI-4 fact sheet]). CMS’s CY 2027 Physician Fee Schedule final rule makes the Promoting Interoperability electronic prior authorization measure optional, for bonus points, in 2027 and required from 2028, when certified technology must meet all three prior authorization criteria. It also adds a required measure for electronic prior authorization of prescription drugs from 2028 ([https://www.ama-assn.org/system/files/2027-qpp-final-rule-fact-sheet.pdf AMA fact sheet]).''

:''HTI-5 was released on October 26 and published on October 28, 2026. Thirteen changes take effect on December 28, seven on January 1, 2027, and the removal of C-CDA and Direct requirements from the transitions-of-care criterion on January 1, 2030. It removes 14 of 60 criteria, including the Direct Project criteria and C-CDA creation performance. Annual real-world testing plans are no longer required, and the proposed removals of privacy and security criteria were not finalized ([https://www.mcguirewoods.com/client-resources/alerts/2026/10/hhs-finalizes-hti-5-narrowing-health-it-certification-and-deferring-information-blocking-changes/ McGuireWoods]; [https://healthit.gov/resources/hti-5-final-rule-removals-or-revisions-of-certification-criteria/ ONC list]). OpenEMR 8’s current certification does not include e-prescribing ([https://www.open-emr.org/wiki/index.php/OpenEMR_ONC_Ambulatory_EHR_Certification_Requirements certification page]).''

:''The three eRx options: DAW Systems makes ScriptSure, an e-prescribing system that integrates with EHRs ([https://www.newswire.com/news/daw-systems-inc-scriptsure-partners-with-covermymeds-for-electronic-19166418 DAW]). Ensora eRx is the former NewCrop, now part of Ensora Health (formerly Therapy Brands) ([https://ensorahealth.com/product/erx/features Ensora]); OpenEMR’s existing NewCrop integration was built by MI-Squared ([https://open-emr.org/wiki/index.php/OpenEMR_ePrescribe OpenEMR ePrescribe]). LogiCoy states that its e-prescribing product is ONC-certified (CHPL listing 10944) and Surescripts-certified ([https://erx.logicoy.com/compliance/ LogiCoy]). The weekly calls have discussed this direction since LogiCoy’s demonstration on [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-10-13 October 13]. The [https://community.open-emr.org/t/openemr-weekly-meeting-notes-20-october-2026/27149 October 20 notes] describe the goal as “a certified (b)(3) companion product, with other options welcome as modules,” and the [https://community.open-emr.org/t/openemr-weekly-meeting-notes-27-october-2026/27164 October 27 notes] set out two paths for vendors: a community module, or certified bundling through the Foundation.''

:''On open calls: no general rule requires a private nonprofit to put a partnership out to bid. Formal competitive procurement standards (2 CFR 200.317–327) apply when an organization spends federal grant funds ([https://www.everycrsreport.com/files/2025-12-02_IF13125_3575db14c28dcdb6b80ffbf264f9a196c8651642.html CRS]). Outside that, the main safeguards are the organization’s own conflict-of-interest policy and its directors’ duty to act in its interest. A “reseller” (value-added reseller, or VAR) is a company that sells and supports another vendor’s product to its own customers.''

=== Telemetry ===

* '''Status:''' Jerry Padgett has built an app for analyzing the telemetry data, with about 15 structured queries and filters. It works from a downloaded copy of the data rather than the live data store.
* '''Three levels of release:''' the app itself, which will stay within the Foundation; the raw data; and reports generated from the data. The open question is whether to publish filtered data to the public, which would let vendors and would-be contributors see how OpenEMR is used.
* '''Concerns:''' privacy and security. For example, location data combined with version information could help someone target installations. The app’s filters can remove location detail below the country level, and the data needs further filtering before any release.
* '''Next step:''' the app will be placed in a private OpenEMR repository so that directors and maintainers can evaluate it. Whether to release filtered data publicly will be considered later. No formal motion was made.

:''Telemetry background: in March 2025 Jerry Padgett proposed an opt-in module to collect usage statistics ([https://community.open-emr.org/t/analytics-and-telemetry-data-collection-module-for-openemr/25134 forum proposal]). The [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-11-03 November 3 weekly call] asked whether the data, or reports from it, should be made public. A common way to share usage data while limiting the risk of identifying individual installations is to publish aggregate reports rather than per-installation records, since combinations of attributes such as location and version can single out an installation even when no names are included.''

== Other Business ==

* No other business was raised. Two topics not on the agenda came up within agenda items: the cost of AI tools for contributors (under OpenEMR Project Updates) and the lack of a clinical informatics group (under Open Plan IT Update).

== Decisions and Actions ==

''Recorded as decisions and directions stated in open session; actions are listed as raised, not as assigned deadlines.''

{| class="wikitable" style="width:100%;"
! style="width:18%; padding:10px 0;" | Item !! style="padding:10px 0;" | Decision / Action
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''October 14 minutes''' || style="padding:10px 0;" | Approved without objection.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''OpenCoreEMR''' || style="padding:10px 0;" | The Governance Committee will meet OpenCoreEMR next week; negotiations continue.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Cloud credits''' || style="padding:10px 0;" | Steve Waite to look into renewing AWS credits, through AWS’s open-source program or TechSoup.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Trademark''' || style="padding:10px 0;" | The attorney is preparing a response to the USPTO office action; the Governance Committee to review the wording by e-mail.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''AI tool costs''' || style="padding:10px 0;" | Raised for future consideration; no decision.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Clinical informatics''' || style="padding:10px 0;" | The gap was acknowledged. Detailed FHIR-mapping discussion to go to the Tuesday weekly call; where a clinical informatics group should sit was left open.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Referrals''' || style="padding:10px 0;" | Jerry Padgett to post a forum topic introducing OpenEMR’s referral workflow.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Netherlands grant''' || style="padding:10px 0;" | Sherwin Gaddis to follow up with Maxine Radcliffe.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''2028 CEHRT / eRx''' || style="padding:10px 0;" | Consensus to pursue a non-exclusive certified-partner agreement with LogiCoy through the Governance Committee, starting with a meeting. No formal motion.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Telemetry''' || style="padding:10px 0;" | The telemetry app to go in a private OpenEMR repository for evaluation; public release of filtered data to be considered later.
|}

== Agenda Items Not Reached ==

The meeting adjourned before these items. Some may be taken up by the Governance Committee or at the December meeting:

* Privacy Policy
* Fundraising: Sherwin’s email campaign and grant opportunity (apart from the grant follow-up noted under Open Plan IT Update)
* OpenEMR App Marketplace
* Veradigm DORN integration
* New meeting time
* Opal Partnership
* Stripe discussion
* Statement integration

== Notes ==

* '''The Governance Committee’s growing role:''' much of the Foundation’s partnership work — OpenCoreEMR, the trademark response, and now LogiCoy — runs through the Governance Committee.
* '''Published partner criteria:''' a public statement of what a certified partner must do would serve the eRx program and could also guide other partnership discussions.
* '''Clinical input:''' clinicians interested in how OpenEMR represents clinical data in FHIR are welcome on the Tuesday weekly calls.
* '''Related weekly calls:''' [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-10-13 October 13, 2026] (LogiCoy demonstration) and [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-11-03 November 3, 2026] (HTI-5, telemetry, PR review).
* Comments and corrections are welcome in the [https://community.open-emr.org/t/openemr-foundation-board-meeting-november-11-2026/27190 agenda thread on the community forum].

== End of the Open Session ==

The meeting adjourned after the Telemetry item, with the remaining agenda items not reached. The time was not stated in the recording. The next monthly board meeting is scheduled for December 9, 2026.

[[Category:OpenEMR Foundation]]

OpenEMR Foundation Board Monthly Meeting Notes

David Eschelbacher — Thu, 12 Nov 2026 10:55:02 GMT

November 11, 2026

← Older revision		Revision as of 10:55, 12 November 2026
(2 intermediate revisions by the same user not shown)
Line 44:		Line 44:
	:*;		:*;
	:*Minutes:		:*Minutes:
	:**[[~~OpenEMR Foundation~~ Board ~~Meeting Minutes~~ 2026-11-11\|OpenEMR Foundation Board Meeting ~~Minutes~~ — November 11, 2026]]		:**[[Board Meetings:2026-11-11\|OpenEMR Foundation Board Meeting Detailed Summary — November 11, 2026]]
	:*;		:*;
	:*Next meeting: December 9, 2026		:*Next meeting: December 9, 2026

OpenEMR Foundation Board Meeting Minutes 2026-11-11

David Eschelbacher — Thu, 12 Nov 2026 10:52:00 GMT

← Older revision		Revision as of 10:52, 12 November 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	''← [[OpenEMR Foundation Board Meeting ~~Minutes~~\|All ~~board minutes~~]]''		''← [[OpenEMR Foundation Board Monthly Meeting Notes\|All Board Meeting Summaries]]''

	'''OpenEMR Foundation Board Meeting ~~Minutes~~'''		'''OpenEMR Foundation Board Meeting Summary'''

	'''Date:''' November 11, 2026		'''Date:''' November 11, 2026

OpenEMR Foundation Board Meeting Minutes 2026-11-11

David Eschelbacher — Thu, 12 Nov 2026 10:49:02 GMT

Created page with "''← All board minutes'' '''OpenEMR Foundation Board Meeting Minutes''' '''Date:''' November 11, 2026 '''Status:''' ''Draft minutes — subject to board approval'' '''Board members present:''' Steve Waite (President, Treasurer); David Eschelbacher (Vice President); Brady Miller (Secretary, Executive Director); Asher Densmore-Lynn (left during the 2028 CEHRT strategy discussion); Sherwin Gaddis; Brad Sharp. '''Board membe..."

New page

''← [[OpenEMR Foundation Board Meeting Minutes|All board minutes]]''

'''OpenEMR Foundation Board Meeting Minutes'''

'''Date:''' November 11, 2026

'''Status:''' ''Draft minutes — subject to board approval''

'''Board members present:''' Steve Waite (President, Treasurer); David Eschelbacher (Vice President); Brady Miller (Secretary, Executive Director); Asher Densmore-Lynn (left during the 2028 CEHRT strategy discussion); Sherwin Gaddis; Brad Sharp.

'''Board members absent:''' Ravi Kafle; Rachel Ellison.

'''Staff:''' Stephen Nielson (Director of Engineering).

'''Guests:''' Maxine Radcliffe (Open Plan IT); Pete Boyd (Founder and CEO, Open Plan IT); Jerry Padgett (OpenEMR contributor).

'''Recorder:''' David Eschelbacher.

'''Quorum:''' six of the eight directors were present at roll call, and a quorum was declared.

:''Under §4.8.1 of the Foundation’s [https://github.com/openemr/foundation-minutes/blob/master/bylaws/CURRENT.md bylaws], a majority of the directors in office — five of the current eight — constitutes a quorum, and no business may be considered at any meeting at which a quorum is not present. Delaware’s default rule ([https://delcode.delaware.gov/title8/c001/sc04/index.html DGCL §141(b)]) is also a majority of the total number of directors.''

:''Italicized indented passages are background and clarification added after the meeting, not part of the board’s proceedings.''

'''PDF version:''' [https://www.open-emr.org/wiki/images/x/xx/OpenEMR_Foundation_Board_Meeting_Minutes_2026-11-11.pdf 📄 OpenEMR Foundation Board Meeting Minutes 2026-11-11.pdf]

== Call to Order ==

* '''Opening:''' the meeting was held by video conference at the board’s regular time, 1:00 p.m. Eastern on the second Wednesday of the month. Steve Waite presided. The call-to-order time was not stated in the recording.
* '''Roll call:''' taken by Steve Waite (see Attendance). Stephen Nielson and Jerry Padgett were noted as present. Steve Waite declared a quorum.

=== Approval of the October 14, 2026 Minutes ===

* Steve Waite said he had reviewed the [https://github.com/openemr/foundation-minutes/blob/master/2026-10-14-Board.md October 14, 2026 minutes] and asked for any objections to approving them. '''Approved''' without objection (“hearing none”). No formal motion or second was stated. Steve Waite thanked Brady Miller for preparing them.

== Welcome and Opening Thoughts ==

* The meeting moved directly to roll call, with no separate opening remarks. The agenda links to the project’s [https://github.com/openemr/openemr/blob/master/CODE_OF_CONDUCT.md Code of Conduct].
* '''Guests:''' Maxine Radcliffe and Pete Boyd of Open Plan IT joined during the Governance Committee update and were welcomed.
* '''Introductions:''' Pete Boyd — Founder and CEO, Open Plan IT.

== Consent Agenda ==

''Roll call and approval of the October 14 minutes are recorded above, under Attendance and Call to Order.''

=== Governance Committee Update ===

* David Eschelbacher reported that, after several attempts, a meeting with OpenCoreEMR has been arranged for next week. The partnership negotiations continue, and the next steps will depend on that meeting. There was no further public update.

:''The Governance Committee’s main work has been negotiating a website partnership with OpenCoreEMR (OCE), OpenEMR’s largest vendor and largest code contributor ([https://github.com/openemr/foundation-minutes/blob/master/2026-10-14-Board.md October 14 minutes]). The committee is also taking on the e-prescribing partner discussion below.''

=== Treasurer’s Report ===

* '''Financial statements:''' the October 31 balance sheet and the October profit-and-loss statement are attached to the [https://community.open-emr.org/t/openemr-foundation-board-meeting-november-11-2026/27190 agenda thread]. Steve Waite said there was little activity to report this month.
* '''Open Collective:''' the agenda lists a balance of $2,362.77 ([https://opencollective.com/openemr Open Collective]).
* '''Cloud credits:''' the Foundation’s Amazon Web Services (AWS) credits appear to have run out, so it is now paying a small monthly amount for the cloud servers that host the OpenEMR demos. Steve Waite will look into renewing the credits, which the Foundation has received in the past through AWS’s open-source program and through TechSoup.

:''AWS has offered promotional credits to open-source projects since 2019, for projects under an OSI-approved license that are not dominated by a single vendor ([https://aws.amazon.com/blogs/opensource/aws-cloud-credits-for-open-source-projects-affirming-our-commitment AWS]). TechSoup, a nonprofit technology clearinghouse, separately offers eligible nonprofits AWS credits for a small administrative fee; for organizations with budgets under $10 million, $1,000 in credits valid for 12 months costs $95 ([https://page.techsoup.org/amazon-web-services-for-nonprofits TechSoup]).''

* '''ONC certification campaign payout:''' on the agenda; not discussed.

=== Trademark Application ===

* Steve Waite reported that the USPTO has issued an office action refusing registration of the application as filed. The Foundation’s attorney is preparing a response, and the Governance Committee will review its wording by e-mail before it is filed. He remains optimistic. The application covers the OpenEMR name; the logo is a separate mark that also needs to be re-established. The Foundation previously held registrations for both, which lapsed for administrative reasons.

:''An office action is the USPTO examining attorney’s letter setting out why an application cannot be registered as filed. It is not final: the applicant generally has three months to respond, with one three-month extension available for a fee, and can answer with argument and evidence. Missing the deadline abandons the application ([https://www.uspto.gov/trademarks/apply/response-time-period USPTO]).''

== Discussion Topics ==

=== OpenEMR Project Updates ===

* '''Releases:''' Brady Miller reported that OpenEMR 8.5.0 was released on October 27, and 8.6.0 is expected in about three weeks. The goal remains a monthly release.
* '''Security:''' security work continues.
* '''PR shepherding:''' to work through the pull-request queue faster, Brady has written an AI-assisted process for reviewing open PRs in batches, by subject or by author. It checks whether each PR has dealt with the automated CodeRabbit review comments, flags whether it looks ready to merge, and gives a quick review. A maintainer then decides by category: a fix that looks good can simply go in, while an architectural change or a new feature needs more thought. It is a living document, and he hopes others will use it. Many open PRs turned out to be simple fixes and easy wins, and the open PR count is back to about 280. Reviewing promptly also helps: one contributor’s FHIR test suite was merged within a day.
* '''Priorities:''' keep the monthly releases going, keep security fixes flowing, and keep PRs moving. Fixes and FHIR testing are preferred over new features, which take much more review effort.

:''The process is documented in the repository under [https://github.com/openemr/openemr/tree/master/docs/pr-shepherding docs/pr-shepherding], added on November 8 ([https://github.com/openemr/openemr/pull/15141 #15141]) and refined since. It is split into small documents so an AI agent can load only the phase it is working on: stocktake, per-PR review, and deliverables. CodeRabbit is an AI code-review service that comments on pull requests. Several contributors added FHIR API test coverage in early November (for example, [https://github.com/openemr/openemr/pull/15146 #15146]). The [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-11-03 November 3 weekly call] also discussed how to tell when an AI-reviewed PR is really ready.''

* '''The cost of AI tools:''' the project has no open-source credits from AI providers, so contributors are paying for these tools themselves. An application to Anthropic’s open-source program has had no reply. Heavy review work can use up a subscription’s limits quickly, and there was concern that subsidized subscription plans may not last. Ideas discussed:
** Choose lower-cost models deliberately. It was suggested that newer default models can use many more tokens for modest gains, and that being explicit in instructions can make up much of the difference.
** Consider other providers, or local models, although hardware able to run good local models is currently expensive.
** A shared team account would make collaboration easier, but the project cannot afford one without a nonprofit or open-source discount. In the meantime, knowledge can be shared through agent guides and skills committed to the repository.
** The cost of AI tools is something the project will need to plan for.

:''Both major providers run programs for open-source maintainers. Anthropic’s Claude for Open Source offers qualifying individual maintainers a complimentary subscription for six months. Applications are reviewed on a rolling basis, and applicants who are not approved are not notified, so silence is not a decision ([https://www.anthropic.com/claude-for-oss-terms terms]). OpenAI’s Codex for Open Source offers six months of ChatGPT Pro with Codex, plus API credits from a $1 million fund for projects that use Codex in work such as pull-request review ([https://developers.openai.com/codex/community/codex-for-oss OpenAI]). Both are aimed at individual maintainers or projects rather than at an organization-wide team account.''

=== Open Plan IT Update ===

* '''Agenda change:''' Steve Waite moved this item up and renamed it from “Ireland update” to “Open Plan IT update,” since Open Plan IT expects to attend regularly.
* '''FHIR mapping and clinical input:''' Maxine Radcliffe said the choices made in mapping clinical data to FHIR have clinical-architecture implications, and Open Plan IT expects to do some work in this area. Decisions about how things are represented will need substantial clinical input, and they must work internationally; units such as Fahrenheit and Celsius are one example. She wants to avoid duplicating work and to share what is learned. She believes many clinicians would like to contribute, if the work is visible to them.
* '''Where to discuss it:''' it was suggested that detailed discussion belongs in the Tuesday weekly community call (2:00 p.m. Eastern), while the board meeting stays on strategy. It was acknowledged that there is a gap: the project has no clinical informatics group or governance at present. Whether one should sit under the Foundation or with the technical team was left open. In the chat, Stephen Nielson noted that contributions are made through GitHub pull requests and that there is no formal team on this.
* '''Referrals:''' Jerry Padgett said he will post a forum topic introducing OpenEMR’s referral functionality: what kinds of referral are possible and how the loop is closed.
* '''Grant follow-up:''' Maxine Radcliffe and Sherwin Gaddis had planned to discuss a grant opportunity in the Netherlands. She asked to be reminded, and Sherwin Gaddis will follow up.

:''FHIR records measurements with UCUM unit codes. The US Core profile for body temperature, for example, requires the UCUM code system and a bound list of temperature units, so Celsius and Fahrenheit are both representable ([https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-body-temperature.html US Core]). Many mapping choices are clinical, not technical: which code represents a finding, which units are expected, and how local practice is captured. That is why clinical safety standards abroad, such as England’s DCB0129 and DCB0160, require named clinical oversight ([https://england.nhs.uk/long-read/national-review-of-clinical-risk-management-standardsdcb0129-and-dcb0160-supporting-information/ NHS England]). For referrals, HL7’s Bidirectional Services eReferral (BSeR) guide describes closed-loop referral exchange in FHIR ([https://www.hl7.org/fhir/us/bser/Introduction.html BSeR]). The weekly call details are [https://www.open-emr.org/wiki/index.php/OpenEMR_Once_Weekly_Conference_Call_Details on the wiki].''

=== OpenCoreEMR ===

* No representative of OpenCoreEMR was present, and there was no separate update. The negotiations are covered under the Governance Committee update.

=== 2028 CEHRT Strategy: Certified Partner Program for eRx, RTPB and ePA ===

* '''The question:''' Steve Waite introduced the item. To be certified for practices taking part in Medicare’s Promoting Interoperability program in 2028, OpenEMR will need certified e-prescribing (eRx), real-time prescription benefit (RTPB) and electronic prior authorization (ePA). These are not yet lined up, so planning should start now, beginning with eRx; the eRx vendor can probably also handle RTPB. The agenda lists three potential eRx partners: DAW Systems, Ensora and LogiCoy.
* '''Regulatory update:''' Stephen Nielson summarized ONC’s information session on the HTI-5 final rule, which takes effect on December 28. It removes a number of certification criteria, including Direct messaging and some C-CDA requirements, and reduces real-world testing reporting, while keeping the security requirements. Nothing in the eRx area puts OpenEMR’s certification at risk at the start of 2027; the eRx requirements remain on the 2028 timeline. Safety-enhanced design requirements were also simplified, so an eRx partner could do most of the certification work. A further rule, HTI-6, with FHIR-related proposals, is expected soon.
* '''Approach:''' building and certifying an eRx system in-house was not favored, and certifying with all three vendors would strain the project’s resources, so a certification partner is needed. It was noted that the existing Ensora (formerly NewCrop) integration is not currently certified for OpenEMR.
* '''LogiCoy in testing:''' a community member has had LogiCoy’s module running in testing for about two weeks. It is integrated natively: it uses OpenEMR’s existing prescription and user screens rather than a bolted-on interface, it supports the configuration needed for electronic prescribing of controlled substances (EPCS), and LogiCoy offers arrangements both for direct customers and for resellers. It was noted that LogiCoy has been taking part in community meetings and working with the community, and that it has a working product.
* '''Direction:''' the prevailing view was to move forward with LogiCoy as a certified partner, with its module potentially becoming a core module, and to work out an agreement with the Foundation through the Governance Committee. The general shape discussed included revenue sharing and responsibility for certification costs. The committee will start by setting up a meeting with LogiCoy.
* '''Non-exclusive:''' the view was that any arrangement should be non-exclusive, so that other vendors can pursue the same path. It was noted that a vendor may be less willing to fund certification without exclusivity, which will be part of the discussion.
* '''Fairness and openness:''' a question was raised about whether choosing a partner without an open call is fair to other vendors. Views differed:
** Publish the criteria for certified partners, and list approved partners publicly, while keeping individual contracts private. It was noted that directors have signed conflict-of-interest commitments, and that a public statement could make clear that no individual member benefits.
** Send a request for proposals to the vendors that have already shown interest.
** A formal request for proposals would cost time, could draw low-quality responses, and would not change the fact that one vendor has already done the work.
** Relying on a single vendor carries risk, which keeping the arrangement non-exclusive is meant to address.
* '''Outcome:''' consensus to pursue a non-exclusive certified-partner agreement with LogiCoy through the Governance Committee, starting with a meeting. No formal motion was made. Asher Densmore-Lynn left during this item; five directors remained.

:''The 2028 requirements come from two rules. HTI-4 (July 2025) updates e-prescribing, (b)(3), to NCPDP SCRIPT 2023011 alone from January 1, 2028. From the same date, any module certified for e-prescribing must also be certified for real-time prescription benefit, (b)(4), which joins the Base EHR definition. HTI-4 also added three FHIR-based prior authorization API criteria ([https://healthit.gov/wp-content/uploads/2025/08/HTI-4-Final-Rule-Overview-Fact-Sheet_508.pdf HTI-4 fact sheet]). CMS’s CY 2027 Physician Fee Schedule final rule makes the Promoting Interoperability electronic prior authorization measure optional, for bonus points, in 2027 and required from 2028, when certified technology must meet all three prior authorization criteria. It also adds a required measure for electronic prior authorization of prescription drugs from 2028 ([https://www.ama-assn.org/system/files/2027-qpp-final-rule-fact-sheet.pdf AMA fact sheet]).''

:''HTI-5 was released on October 26 and published on October 28, 2026. Thirteen changes take effect on December 28, seven on January 1, 2027, and the removal of C-CDA and Direct requirements from the transitions-of-care criterion on January 1, 2030. It removes 14 of 60 criteria, including the Direct Project criteria and C-CDA creation performance. Annual real-world testing plans are no longer required, and the proposed removals of privacy and security criteria were not finalized ([https://www.mcguirewoods.com/client-resources/alerts/2026/10/hhs-finalizes-hti-5-narrowing-health-it-certification-and-deferring-information-blocking-changes/ McGuireWoods]; [https://healthit.gov/resources/hti-5-final-rule-removals-or-revisions-of-certification-criteria/ ONC list]). OpenEMR 8’s current certification does not include e-prescribing ([https://www.open-emr.org/wiki/index.php/OpenEMR_ONC_Ambulatory_EHR_Certification_Requirements certification page]).''

:''The three eRx options: DAW Systems makes ScriptSure, an e-prescribing system that integrates with EHRs ([https://www.newswire.com/news/daw-systems-inc-scriptsure-partners-with-covermymeds-for-electronic-19166418 DAW]). Ensora eRx is the former NewCrop, now part of Ensora Health (formerly Therapy Brands) ([https://ensorahealth.com/product/erx/features Ensora]); OpenEMR’s existing NewCrop integration was built by MI-Squared ([https://open-emr.org/wiki/index.php/OpenEMR_ePrescribe OpenEMR ePrescribe]). LogiCoy states that its e-prescribing product is ONC-certified (CHPL listing 10944) and Surescripts-certified ([https://erx.logicoy.com/compliance/ LogiCoy]). The weekly calls have discussed this direction since LogiCoy’s demonstration on [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-10-13 October 13]. The [https://community.open-emr.org/t/openemr-weekly-meeting-notes-20-october-2026/27149 October 20 notes] describe the goal as “a certified (b)(3) companion product, with other options welcome as modules,” and the [https://community.open-emr.org/t/openemr-weekly-meeting-notes-27-october-2026/27164 October 27 notes] set out two paths for vendors: a community module, or certified bundling through the Foundation.''

:''On open calls: no general rule requires a private nonprofit to put a partnership out to bid. Formal competitive procurement standards (2 CFR 200.317–327) apply when an organization spends federal grant funds ([https://www.everycrsreport.com/files/2025-12-02_IF13125_3575db14c28dcdb6b80ffbf264f9a196c8651642.html CRS]). Outside that, the main safeguards are the organization’s own conflict-of-interest policy and its directors’ duty to act in its interest. A “reseller” (value-added reseller, or VAR) is a company that sells and supports another vendor’s product to its own customers.''

=== Telemetry ===

* '''Status:''' Jerry Padgett has built an app for analyzing the telemetry data, with about 15 structured queries and filters. It works from a downloaded copy of the data rather than the live data store.
* '''Three levels of release:''' the app itself, which will stay within the Foundation; the raw data; and reports generated from the data. The open question is whether to publish filtered data to the public, which would let vendors and would-be contributors see how OpenEMR is used.
* '''Concerns:''' privacy and security. For example, location data combined with version information could help someone target installations. The app’s filters can remove location detail below the country level, and the data needs further filtering before any release.
* '''Next step:''' the app will be placed in a private OpenEMR repository so that directors and maintainers can evaluate it. Whether to release filtered data publicly will be considered later. No formal motion was made.

:''Telemetry background: in March 2025 Jerry Padgett proposed an opt-in module to collect usage statistics ([https://community.open-emr.org/t/analytics-and-telemetry-data-collection-module-for-openemr/25134 forum proposal]). The [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-11-03 November 3 weekly call] asked whether the data, or reports from it, should be made public. A common way to share usage data while limiting the risk of identifying individual installations is to publish aggregate reports rather than per-installation records, since combinations of attributes such as location and version can single out an installation even when no names are included.''

== Other Business ==

* No other business was raised. Two topics not on the agenda came up within agenda items: the cost of AI tools for contributors (under OpenEMR Project Updates) and the lack of a clinical informatics group (under Open Plan IT Update).

== Decisions and Actions ==

''Recorded as decisions and directions stated in open session; actions are listed as raised, not as assigned deadlines.''

{| class="wikitable" style="width:100%;"
! style="width:18%; padding:10px 0;" | Item !! style="padding:10px 0;" | Decision / Action
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''October 14 minutes''' || style="padding:10px 0;" | Approved without objection.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''OpenCoreEMR''' || style="padding:10px 0;" | The Governance Committee will meet OpenCoreEMR next week; negotiations continue.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Cloud credits''' || style="padding:10px 0;" | Steve Waite to look into renewing AWS credits, through AWS’s open-source program or TechSoup.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Trademark''' || style="padding:10px 0;" | The attorney is preparing a response to the USPTO office action; the Governance Committee to review the wording by e-mail.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''AI tool costs''' || style="padding:10px 0;" | Raised for future consideration; no decision.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Clinical informatics''' || style="padding:10px 0;" | The gap was acknowledged. Detailed FHIR-mapping discussion to go to the Tuesday weekly call; where a clinical informatics group should sit was left open.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Referrals''' || style="padding:10px 0;" | Jerry Padgett to post a forum topic introducing OpenEMR’s referral workflow.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Netherlands grant''' || style="padding:10px 0;" | Sherwin Gaddis to follow up with Maxine Radcliffe.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''2028 CEHRT / eRx''' || style="padding:10px 0;" | Consensus to pursue a non-exclusive certified-partner agreement with LogiCoy through the Governance Committee, starting with a meeting. No formal motion.
|- style="vertical-align:top;"
| style="padding:10px 0;" | '''Telemetry''' || style="padding:10px 0;" | The telemetry app to go in a private OpenEMR repository for evaluation; public release of filtered data to be considered later.
|}

== Agenda Items Not Reached ==

The meeting adjourned before these items. Some may be taken up by the Governance Committee or at the December meeting:

* Privacy Policy
* Fundraising: Sherwin’s email campaign and grant opportunity (apart from the grant follow-up noted under Open Plan IT Update)
* OpenEMR App Marketplace
* Veradigm DORN integration
* New meeting time
* Opal Partnership
* Stripe discussion
* Statement integration

== Notes ==

* '''The Governance Committee’s growing role:''' much of the Foundation’s partnership work — OpenCoreEMR, the trademark response, and now LogiCoy — runs through the Governance Committee.
* '''Published partner criteria:''' a public statement of what a certified partner must do would serve the eRx program and could also guide other partnership discussions.
* '''Clinical input:''' clinicians interested in how OpenEMR represents clinical data in FHIR are welcome on the Tuesday weekly calls.
* '''Related weekly calls:''' [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-10-13 October 13, 2026] (LogiCoy demonstration) and [https://www.open-emr.org/wiki/index.php/Weekly_Meetings:2026-11-03 November 3, 2026] (HTI-5, telemetry, PR review).
* Comments and corrections are welcome in the [https://community.open-emr.org/t/openemr-foundation-board-meeting-november-11-2026/27190 agenda thread on the community forum].

== End of the Open Session ==

The meeting adjourned after the Telemetry item, with the remaining agenda items not reached. The time was not stated in the recording. The next monthly board meeting is scheduled for December 9, 2026.

[[Category:OpenEMR Foundation]]

OpenEMR Foundation Board Monthly Meeting Notes

David Eschelbacher — Thu, 12 Nov 2026 10:48:24 GMT

2026

← Older revision		Revision as of 10:48, 12 November 2026
(3 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	These are summaries of the OpenEMR Foundation Board Monthly conference call. Summaries		These are summaries of the OpenEMR Foundation Board Monthly conference call.
	begin with the October 14, 2026 meeting.
			Summaries begin with the October 14, 2026 meeting.

	These are not the official minutes		These are not the official minutes

	~~The call is open to anyone in the community —~~ Second Wednesdays of Month at 10:00 AM Pacific Time		'''Second Wednesdays of Month''' -- 10:00 AM Pacific Time (1:00 PM Eastern).
	(1:00 PM Eastern). See [[OpenEMR Foundation Monthly Conference Call Details]] to join.
			See [[OpenEMR Foundation Monthly Conference Call Details]] to join.

	:''Calls are recorded and transcribed, and AI is used to produce these summaries. These notes may have mistakes		:''Calls are recorded and transcribed, and AI is used to produce these summaries. These notes may have mistakes
Line 27:		Line 29:

	== '''2026''' ==		== '''2026''' ==
			===== '''November 11, 2026''' =====
			:*Highlights:
			:**Consent agenda: six of eight directors present; October 14 minutes approved
			:**Governance Committee: meeting with OpenCoreEMR set for next week; negotiations continue
			:**Treasurer's report: little activity; AWS credits for the demo servers to be renewed
			:**Trademark: attorney preparing a response to the USPTO office action
			:**Releases: OpenEMR 8.5.0 out October 27; 8.6.0 expected in about three weeks
			:**PR review: new AI-assisted PR-shepherding process to move the queue faster
			:**AI tools: rising cost to contributors raised as a concern for the project
			:**Open Plan IT: clinical input on FHIR mapping; no clinical informatics group yet
			:**2028 certification: consensus to pursue a non-exclusive e-prescribing partnership with LogiCoy through the Governance Committee
			:**Telemetry: analysis app to go in a private repository; public release of filtered data to be considered later
			:**Not reached: privacy policy, fundraising, app marketplace, Veradigm DORN, Opal, Stripe and other items
			:*;
			:*Minutes:
			:**[[OpenEMR Foundation Board Meeting Minutes 2026-11-11\|OpenEMR Foundation Board Meeting Minutes — November 11, 2026]]
			:*;
			:*Next meeting: December 9, 2026

	===== '''October 14, 2026''' =====		===== '''October 14, 2026''' =====
	:*Highlights:		:*Highlights:

OpenEMR Once Weekly Conference Call Details

David Eschelbacher — Thu, 12 Nov 2026 10:41:24 GMT

Overview

← Older revision		Revision as of 10:41, 12 November 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	== ~~Weekly Meetings~~ ==		== '''Overview''' ==
	The OpenEMR project holds an open meeting once a week.		The OpenEMR project holds an open meeting once a week.

	'''Anyone interested is welcome to join!'''.		'''Anyone interested is welcome to join!'''

	Most meetings have no set agenda, though some do. It's simply a chance to talk through whatever's on people's minds, technical or not.		Most meetings have no set agenda, though some do. It's simply a chance to talk through whatever's on people's minds, technical or not.

	=== When ===		== '''When''' ==
	'''Every Tuesday'''		'''Every Tuesday'''

Line 26:		Line 26:
	''Because the US and Europe change clocks on different dates, the UK and Central Europe times may be an hour earlier for a few weeks in March and October/November.''		''Because the US and Europe change clocks on different dates, the UK and Central Europe times may be an hour earlier for a few weeks in March and October/November.''

	=== How to ~~join =~~==		== '''How to Join''' ==
	* '''Video:'''      https://meet.google.com/kxq-vjfr-hvs		* '''Video:'''      https://meet.google.com/kxq-vjfr-hvs
	* '''Phone:'''      Dial    +1 518-797-6169    and Enter PIN    '''355 020 960#'''		* '''Phone:'''      Dial    +1 518-797-6169    and Enter PIN    '''355 020 960#'''
Line 33:		Line 33:
	Feel free to drop in anytime.		Feel free to drop in anytime.

	=== Good to ~~know =~~==		== '''Good to Know''' ==
	* This call may be recorded. See [[#Recording and Meeting Notes\|Recording and Meeting Notes]] below.		* This call may be recorded. See [[#Recording and Meeting Notes\|Recording and Meeting Notes]] below.
	* All participants are expected to follow the [https://github.com/openemr/openemr/blob/master/CODE_OF_CONDUCT.md OpenEMR Code of Conduct].		* All participants are expected to follow the [https://github.com/openemr/openemr/blob/master/CODE_OF_CONDUCT.md OpenEMR Code of Conduct].

	== Past Meetings ==		== '''Past Meetings''' ==
	:*[[OpenEMR Weekly Conference Call Meeting Notes\|Detailed Meeting Summaries]]		:*[[OpenEMR Weekly Conference Call Meeting Notes\|Detailed Meeting Summaries]]

	== Recording and Meeting Notes ==		== '''Recording and Meeting Notes''' ==
	:Weekly conference calls are recorded.		:Weekly conference calls are recorded.
	:The recording is transcribed, and AI is used to produce a detailed written summary, which is published publicly at [[OpenEMR Weekly Conference Call Meeting Notes\|Detailed Meeting Summaries]].		:The recording is transcribed, and AI is used to produce a detailed written summary, which is published publicly at [[OpenEMR Weekly Conference Call Meeting Notes\|Detailed Meeting Summaries]].

OpenEMR Foundation Monthly Conference Call Details

David Eschelbacher — Thu, 12 Nov 2026 10:38:54 GMT

How to join

← Older revision		Revision as of 10:38, 12 November 2026
(6 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	=='''Overview'''==		=='''Overview'''==
	:The OpenEMR Foundation board has a meeting monthly and is open to the public. Anyone interested in participating is welcome. Feel free to join anytime. Minutes and of prior meetings can be found on the [[OpenEMR_Foundation__wiki_page#Meetings\|OpenEMR Foundation Wiki page]].		:The OpenEMR Foundation board has a meeting monthly and is open to the public.

			Anyone interested in participating is welcome. Feel free to join anytime.

			Minutes and of prior meetings can be found on the [[OpenEMR_Foundation__wiki_page#Meetings\|OpenEMR Foundation Wiki page]].

	=='''Meeting Date/Time'''==		=='''Meeting Date/Time'''==
	:*The meeting is once monthly and on:		The meeting is once monthly and on:
	::* Second Wednesday of the ~~month at~~ 10:00 AM ~~PST (Pacific Standard~~ Time).
			'''Second Wednesday of the Month'''

			{\| class="wikitable"
			! style="min-width: 150px;" \| Time zone
			! Meeting time
			\|-
			\| Eastern (US) \|\| 1:00 PM
			\|-
			\| Pacific (US) \|\| 10:00 AM
			\|-
			\| UK \|\| 6:00 PM
			\|-
			\| Central Europe \|\| 7:00 PM
			\|}
			<br />
			''Times are anchored to US Eastern Time.''

			''Because the US and Europe change clocks on different dates, the UK and Central Europe times may be an hour earlier for a few weeks in March and October/November.''

			== '''How to Join''' ==
			* '''Video:'''      https://meet.google.com/kxq-vjfr-hvs
			* '''Phone:'''      Dial    +1 518-797-6169    and Enter PIN    '''355 020 960#'''
			* '''Other dial-in numbers:      ''' https://tel.meet/kxq-vjfr-hvs?hs=5

	:*This call may be recorded ~~— see~~ [[~~#Recording and~~ Meeting Notes\|~~Recording and~~ Meeting ~~Notes~~]] ~~below~~.		== '''Recording and Meeting Notes''' ==
	:*'''To join the ~~video meeting~~, ~~click this link~~: ~~https://meet.google~~.~~com/kxq-vjfr-hvs'''~~		:Monthly Foundation calls are recorded.
	:*~~Otherwise~~, ~~to join by phone, dial +1 518-797-6169~~ and ~~enter this PIN: 355 020 960#~~		:The recording is transcribed, and AI is used to produce a detailed written summary, which is published publicly at [[OpenEMR Foundation Board Monthly Meeting Notes\|Detailed Board Meeting Summaries]].
	:*~~To view more phone numbers~~, ~~click this link: https://tel~~.~~meet/kxq-vjfr-hvs?hs=5~~		:By joining the call, you should expect that your contributions may appear in the published summary, attributed by name.
			:*Security details are omitted from the published summaries.
			:*If you would like something kept off the record, say so at any point during the call and we will pause.
			:*If you believe something has been misattributed or misstated, reply on the forum announcement or raise it on the next call and the wiki will be corrected.

	=='''Past Meeting Minutes'''==		=='''Past Meeting Minutes'''==
	:*[https://github.com/openemr/foundation-minutes/tree/master Past Board Meeting Minutes]		:*[https://github.com/openemr/foundation-minutes/tree/master Past Board Meeting Minutes]
	:*[[OpenEMR Foundation Board Monthly Meeting Notes\|Detailed Board Meeting Summaries]]		:*[[OpenEMR Foundation Board Monthly Meeting Notes\|Detailed Board Meeting Summaries]]

OpenEMR Once Weekly Conference Call Details

David Eschelbacher — Thu, 12 Nov 2026 10:23:39 GMT

How to join

← Older revision		Revision as of 10:23, 12 November 2026
(12 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	== Weekly Meetings ==		== Weekly Meetings ==
	The OpenEMR project holds an open meeting once a week~~, and~~ '''~~anyone~~ interested is welcome to join'''. Most meetings have no set agenda, though some do. It's simply a chance to talk through whatever's on people's minds, technical or not.		The OpenEMR project holds an open meeting once a week.

			'''Anyone interested is welcome to join!'''.

			Most meetings have no set agenda, though some do. It's simply a chance to talk through whatever's on people's minds, technical or not.

	=== When ===		=== When ===
			'''Every Tuesday'''

	{\| class="wikitable"		{\| class="wikitable"
	! Time zone !! Meeting time		! style="min-width: 150px;" \| Time zone
			! Meeting time
	\|-		\|-
	\| ~~'''~~Eastern (US)~~'''~~ \|\| ~~'''Tuesdays,~~ 2:00 PM~~'''~~		\| Eastern (US) \|\| 2:00 PM
	\|-		\|-
	\| Pacific (US) \|\| 11:00 AM		\| Pacific (US) \|\| 11:00 AM
Line 14:		Line 21:
	\| Central Europe \|\| 8:00 PM		\| Central Europe \|\| 8:00 PM
	\|}		\|}
	''Times are anchored to US Eastern Time. Because the US and Europe change clocks on different dates, the UK and Central Europe times may be an hour earlier for a few weeks in March and October/November.''		<br />
			''Times are anchored to US Eastern Time.''

			''Because the US and Europe change clocks on different dates, the UK and Central Europe times may be an hour earlier for a few weeks in March and October/November.''

	=== How to join ===		=== How to join ===
	* '''Video:''' https://meet.google.com/kxq-vjfr-hvs		* '''Video:'''      https://meet.google.com/kxq-vjfr-hvs
	* '''Phone:''' ~~dial~~ +1 518-797-6169 and ~~enter~~ PIN '''355 020 960#'''		* '''Phone:'''      Dial    +1 518-797-6169    and Enter PIN    '''355 020 960#'''
	* '''Other dial-in numbers:''' https://tel.meet/kxq-vjfr-hvs?hs=5		* '''Other dial-in numbers:      ''' https://tel.meet/kxq-vjfr-hvs?hs=5

	Feel free to drop in anytime.		Feel free to drop in anytime.

OpenEMR Weekly Conference Call Meeting Notes

David Eschelbacher — Thu, 12 Nov 2026 09:54:23 GMT

← Older revision		Revision as of 09:54, 12 November 2026
Line 3:		Line 3:

	The call is open to anyone in the community — Tuesdays at 11:00 AM Pacific Time		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.		(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.		:''Calls are recorded and transcribed, and AI is used to produce these summaries.

Weekly Meetings:2026-11-10

David Eschelbacher — Thu, 12 Nov 2026 09:46:49 GMT

← Older revision		Revision as of 09:46, 12 November 2026
Line 11:		Line 11:
	:''This closes an item carried from 11/3. OpenEMR's API documentation labels v1 scopes “deprecated but supported” and maps them to v2 internally — .read to .rs and .write to .cud — which is the mapping layer Stephen meant. Keeping it means v1 clients continue to work, while new work, such as the granular category scopes needed for FHIR writes, can target v2.''		:''This closes an item carried from 11/3. OpenEMR's API documentation labels v1 scopes “deprecated but supported” and maps them to v2 internally — .read to .rs and .write to .cud — which is the mapping layer Stephen meant. Keeping it means v1 clients continue to work, while new work, such as the granular category scopes needed for FHIR writes, can target v2.''

	'''PDF version:''' [https://www.open-emr.org/wiki/images/x/xx/OpenEMR_Weekly_Meeting_Detailed_Summary_2026-11-10.pdf 📄 OpenEMR Weekly Meeting Detailed Summary 2026-11-10.pdf]		'''PDF version:''' [https://www.open-emr.org/wiki/images/5/5f/OpenEMR_Weekly_Meeting_Detailed_Summary_2026-11-10.pdf 📄 OpenEMR Weekly Meeting Detailed Summary 2026-11-10.pdf]

	== Architecture Documents — Nearly Ready ==		== Architecture Documents — Nearly Ready ==

File:OpenEMR Weekly Meeting Detailed Summary 2026-11-10.pdf

David Eschelbacher — Thu, 12 Nov 2026 09:46:15 GMT

David Eschelbacher uploaded File:OpenEMR Weekly Meeting Detailed Summary 2026-11-10.pdf

New page

Weekly Meetings:2026-11-10

David Eschelbacher — Thu, 12 Nov 2026 09:43:40 GMT

← Older revision		Revision as of 09:43, 12 November 2026
Line 2:		Line 2:

	'''Attendees:''' Stephen Waite, Stephen Nielson, David Eschelbacher, Jerry Padgett, Simon Quigley, Prabhu Pathak (LogiCoy), Eric Stern (OCE), Seth C, Jit Chawla (ACE Health Solutions), Sherwin Gaddis, Farjad Zaghi (joined near the end).		'''Attendees:''' Stephen Waite, Stephen Nielson, David Eschelbacher, Jerry Padgett, Simon Quigley, Prabhu Pathak (LogiCoy), Eric Stern (OCE), Seth C, Jit Chawla (ACE Health Solutions), Sherwin Gaddis, Farjad Zaghi (joined near the end).

	'''Not attending:''' Brady Miller, Ansuman Nayak (LogiCoy), Michael Smith (OCE), Pedro Camellon.		'''Not attending:''' Brady Miller, Ansuman Nayak (LogiCoy), Michael Smith (OCE), Pedro Camellon.

Weekly Meetings:2026-11-10

David Eschelbacher — Thu, 12 Nov 2026 09:43:02 GMT

Created page with "''← All meeting summaries'' | Join the call '''Attendees:''' Stephen Waite, Stephen Nielson, David Eschelbacher, Jerry Padgett, Simon Quigley, Prabhu Pathak (LogiCoy), Eric Stern (OCE), Seth C, Jit Chawla (ACE Health Solutions), Sherwin Gaddis, Farjad Zaghi (joined near the end). '''Not attending:''' Brady Miller, Ansuman Nayak (LogiCoy), Michael Smith (OCE), Pedro Came..."

Show changes

OpenEMR Weekly Conference Call Meeting Notes

David Eschelbacher — Thu, 12 Nov 2026 09:42:14 GMT

2026

@@ Line 26: / Line 26: @@
 == '''2026''' ==
 ===== '''November 3, 2026''' =====
 :*Topics:

OpenEMR Foundation wiki page

Bradymiller — Wed, 11 Nov 2026 06:17:24 GMT

Bylaws

← Older revision		Revision as of 06:17, 11 November 2026
Line 15:		Line 15:

	='''Bylaws'''=		='''Bylaws'''=
	:~~Provide on request~~.		:https://github.com/openemr/foundation-minutes/blob/master/bylaws/CURRENT.md

	='''Articles of Incorporation'''=		='''Articles of Incorporation'''=

QA and Release Process

Bradymiller — Mon, 09 Nov 2026 09:44:42 GMT

Packages

← Older revision		Revision as of 09:44, 9 November 2026
(2 intermediate revisions by the same user not shown)
Line 95:		Line 95:
	:*** Ensure auto upgrade works ('''AUTOMATED ON ACCEPT TESTING''')		:*** Ensure auto upgrade works ('''AUTOMATED ON ACCEPT TESTING''')
	:*Kubernetes		:*Kubernetes
	:** Update ~~script~~ to use the new docker ('''8.3.0''')('''8.4.0''')('''8.4.1''')('''8.5.0''')		:** Update scripts (3 of them now) to use the new docker ('''8.3.0''')('''8.4.0''')('''8.4.1''')('''8.5.0''')
	:*AWS Cloud packages (PENDING)		:*AWS Cloud packages (PENDING)
	:** Updates for some packages (https://github.com/openemr/openemr-devops/pull/891) ('''8.4.1''')		:** Updates for some packages (https://github.com/openemr/openemr-devops/pull/891) (https://github.com/openemr/openemr-devops/pull/921) ('''8.4.1''')('''8.5.0''')
	:** Include the Fargate option in listings (PENDING)		:** Include the Fargate option in listings (PENDING)
	:** Include the EKS option in listings (PENDING)		:** Include the EKS option in listings (PENDING)

Professional Support

Sjpadgett — Sun, 08 Nov 2026 20:04:39 GMT

Jerry Padgett OpenEMR Development & Consulting

OpenEMR with aaPanel and LAMP stack on Linux Virtual Machine

Alfa — Sun, 08 Nov 2026 16:29:22 GMT

Add reference on how to update PHP components in aaPanel

← Older revision		Revision as of 16:29, 8 November 2026
Line 1:		Line 1:
			{{Ambox\|text=Did you return here to find out the mitigation path in aaPanel for latest discovered CVEs in PHP? Please refer to [https://www.aapanel.com/docs/Security/php-security-update-2026.html#update-php-in-aapanel this page].}}

	Using a Linux Virtual Machine is an affordable and stable method for running your own instance of OpenEMR. In this tutorial we setup and run Linux version of OpenEMR on Debian '''L'''inux having '''A'''pache, '''M'''ariaDB and '''P'''HP, hence the '''LAMP''' stack, run on that. (''Read more [https://aws.amazon.com/what-is/lamp-stack/ about LAMP stack on Amazon's AWS] knowledge base'').		Using a Linux Virtual Machine is an affordable and stable method for running your own instance of OpenEMR. In this tutorial we setup and run Linux version of OpenEMR on Debian '''L'''inux having '''A'''pache, '''M'''ariaDB and '''P'''HP, hence the '''LAMP''' stack, run on that. (''Read more [https://aws.amazon.com/what-is/lamp-stack/ about LAMP stack on Amazon's AWS] knowledge base'').

File:Information icon4.svg

Alfa — Sun, 08 Nov 2026 16:12:35 GMT

Alfa uploaded File:Information icon4.svg Information Icon is in Public domain (Received via Wikimedia Commons)

New page

== Summary ==
Information Icon is in Public domain (Received via Wikimedia Commons)

← Older revision		Revision as of 20:04, 8 November 2026
(One intermediate revision by the same user not shown)
Line 79:		Line 79:
	'''United States'''		'''United States'''

	[[File:Jerry-padgett-openemr-logo.png\|frameless\|~~260px~~\|link=https://openemr.solutions/openemr-professional-support.html\|alt=Jerry Padgett, OpenEMR Engineering]]		[[File:Jerry-padgett-openemr-logo.png\|frameless\|300px\|link=https://openemr.solutions/openemr-professional-support.html\|alt=Jerry Padgett, OpenEMR Engineering]]

	'''Principal developer for ~~at least~~ eight years.''' Major OpenEMR core project contributor (2015–present); ~~integrator~~ (2017–2019); ~~project administrator~~ (2019–2026).		'''Principal developer for the last eight years.''' Major OpenEMR core project contributor (2015–present); Integrator (2017–2019); Project Administrator (2019–2026).

	'''Selected achievements'''		'''Selected achievements'''
	* Original developer of the OpenEMR patient portal, including its patient-facing workflows and ongoing improvements.		* Original developer of the OpenEMR patient portal, including its patient-facing workflows and ongoing improvements.
	* Led and co-authored Clinical Quality Measures work for the 2022 ONC certification; contributed to ongoing C-CDA, eCQM, QRDA, and USCDI certification work.		* Led and co-authored Clinical Quality Measures work for the 2022 ONC certification; contributed to ongoing C-CDA, eCQM, QRDA, and USCDI certification work.
	* Developed the Questionnaire/Form Builder for encounter and patient-portal forms; later completed Questionnaire Manager and the FHIR SDC runtime replacing LForms.		* Developed the Questionnaire/Form Builder for encounter and patient-portal forms; later completed Assessment Questionnaires in Patient Dashboard with a Questionnaire Manager and the FHIR SDC runtime replacing LForms.
	* Developer and maintainer of the Weno eRx and Fax/SMS ~~and email~~ modules; developed and managed OpenEMR telemetry.		* Developer and maintainer of the Weno eRx and Fax/SMS/Email modules; developed and managed OpenEMR telemetry.
	* Contributed foundational and ongoing work in FHIR, REST APIs, OAuth2/SMART, billing, DICOM, and institutional-care workflows.		* Contributed foundational and ongoing work in FHIR, REST APIs, OAuth2/SMART, billing, DICOM, and institutional-care workflows.

	'''[https://openemr.solutions/ ~~VISIT WEBSITE~~ — Complete contribution history, projects & services →]'''		'''[https://openemr.solutions/ Visit Website — Complete contribution history, projects & services →]'''

	'''Certification ~~match~~:''' For every dollar donated to the OpenEMR Foundation to support certification, I will ~~give $0.75~~ discount on my fees.		'''Certification Match:''' For every dollar donated to the OpenEMR Foundation to support certification, I will match with a 60% discount on my fees.

	'''Community ~~contribution discount~~:''' 50% off development work when the resulting work is contributed back to the OpenEMR community.		'''Community Contribution Discount:''' 50% off any new development work when the resulting work is contributed back to the OpenEMR community.

	'''[https://openemr.solutions/openemr-professional-support.html View services & contact information]'''		'''[https://openemr.solutions/openemr-professional-support.html View services & contact information]'''

	----		----
	<br>		<br>