Board Meetings:2026-10-14

From OpenEMR Project Wiki

← All board minutes

OpenEMR Foundation Board Meeting Minutes

Date: October 14, 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; Sherwin Gaddis; Brad Sharp; Ravi Kafle (joined after roll call).

Board members absent: Rachel Ellison.

Staff: Stephen Nielson (Director of Engineering).

Guests: Maxine Radcliffe.

Recorder: David Eschelbacher.

Quorum: six of the eight directors were present at roll call. Ravi Kafle joined during the Governance Committee update.

Under §4.8.1 of the Foundation’s bylaws, a majority of the directors in office immediately before a meeting constitutes a quorum — five of the current eight — and no business may be considered without one. That is why the meeting waited for enough directors to arrive before starting. Delaware’s default rule (DGCL §141(b)) is also a majority of the total number of directors; bylaws may set a lower quorum, but never below one-third.
Italicized indented passages are background and clarification added after the meeting, not part of the board’s proceedings.

PDF version: 📄 OpenEMR Foundation Board Meeting Minutes 2026-10-14.pdf

Call to Order

  • Opening: the meeting was held by video conference at the board’s new 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.
  • Recording: attendees were told that the meeting was being recorded to help prepare the minutes, and directors who joined later were also given notice. No objection was raised.
  • Roll call: taken by Steve Waite (see Attendance). Stephen Nielson and Maxine Radcliffe were noted as present. Two directors were missing at roll call: Rachel Ellison and Ravi Kafle.
Several attendees are in states with differing rules on recording conversations. Florida, for example, generally requires the consent of all parties (Reporters Committee summary), so announcing a recording at the start, and again to late arrivals, is a sensible practice for a multi-state call.

Approval of the September 9, 2026 Minutes

  • Motion: to approve the September 9, 2026 minutes. Moved by Steve Waite, who said he had reviewed them. No second was stated. Approved without objection (“hearing none”).

Welcome and Opening Thoughts

  • Code of Conduct: Steve Waite asked everyone to review the project’s Code of Conduct from time to time.
OpenEMR’s Code of Conduct sets out expected and unacceptable behavior and applies in all community venues, online and in person, including one-on-one communications about community business. Its text is adapted from the Citizen Code of Conduct, which itself draws on the Django Code of Conduct and the Geek Feminism anti-harassment policy, and it is distributed under a Creative Commons Attribution-ShareAlike licence.
  • New meeting time: this was the board’s first meeting at the new time. Thanks were given to everyone for adjusting. Maxine Radcliffe, joining from Europe, noted that she could not attend at the old time, which fell in the middle of the night for her.
The change was approved at the September 9 meeting: 1:00 p.m. Eastern on the second Wednesday of each month. Earlier meetings convened at about 9:00 p.m. Eastern, which is 2:00 a.m. in Ireland during summer time. The new time is 6:00 p.m. in Ireland for most of the year.

Introductions

Because a guest was present, attendees introduced themselves:

  • Maxine Radcliffe: a nurse practitioner and clinical director for Open Plan IT (Ireland and UK), and an OpenEMR user for about eight years. Her background includes street medicine, teaching tropical nursing, and clinical informatics. She has academic links with Maynooth University, the London School of Hygiene & Tropical Medicine and other UK universities, and she regards digital health infrastructure as a public good and as public health infrastructure.
  • Stephen Nielson: Director of Engineering. He collaborates with international and European OpenEMR efforts and works to bridge them with the work in the U.S.
  • Sherwin Gaddis: one of the project’s developers, who joined the board some time ago. He shares the aim of making health-record infrastructure available to anyone who needs it.
  • Steve Waite: board president and a long-time director. He runs a small medical billing and OpenEMR development and hosting company, which gives him a view of what users need, and he is a project administrator.
  • David Eschelbacher: a physician, board-certified in internal medicine, whose practice provides home visits to homebound patients and in assisted living facilities. He has contributed changes to OpenEMR, including support for multiple addresses and phone numbers per patient for home-visit practices, and plans calendar changes for home visits. He joined the board recently and is now vice president.
  • Asher Densmore-Lynn: an e-commerce CTO and OpenEMR’s cloud engineer. He maintains the project’s Amazon (AWS) packages and Docker images, with the aim of making OpenEMR easier to deploy.
  • Brad Sharp: a developer for 20 years who works for ClaimRev, a medical claims clearinghouse. He has been on the board for about a year and has worked with OpenEMR since the company started.
  • Brady Miller: Executive Director, involved with the project for more than 20 years. He began contributing during his internal medicine residency, after comparing the open-source options of the time (OpenEMR, ClearHealth and VistA). His current focus is security, AI tooling and Docker, along with whatever else needs attention.
OpenEMR began as MP Pro, written by Synitech and released in 2001. It was reworked and relaunched as OpenEMR 1.3 in July 2002 and released under the GNU General Public License on SourceForge on August 13, 2002. The Pennington Firm became its primary maintainer in 2003. The OpenEMR Foundation, organized in 2019, holds the project’s ONC certification (OpenEMR history).

Roll call and approval of the September 9 minutes are recorded above, under Attendance and Call to Order.

Bylaws Amendments

  • Now in the repository: Steve Waite reported that the bylaws amendments, approved by email after the previous meeting’s discussion, have been added to the Foundation’s public minutes repository on GitHub, next to the published minutes, so that changes can be tracked over time (Amendments 1–5). He expects further changes in future.
The amendments were adopted by unanimous written consent dated September 6, 2026, and recorded in the September 9 minutes. The repository now holds the full text in effect (bylaws/CURRENT.md), a change log, and the superseded text in an archive. In summary:
''Amendment 1 (§4.7.4):' the board may act without a meeting only if all directors in office consent in writing; e-mail from a director’s address on record counts. This replaces a “consensus of a quorum” rule and conforms to DGCL §141(f), which requires the consent of all directors. Consents are filed with the minutes.'
''Amendment 2 (§5.3):' creates advisory committees, which may include non-directors, have no authority to act for the board, and must be chaired by a director who reports their recommendations. Committees under §5.1, made up of directors, may exercise delegated board authority.'
''Amendments 3–5 (§6.9, §7.1):' define the Executive Director as a volunteer board officer. The role has listed duties and needs board approval for, among other things, unbudgeted spending over $500 (or $2,500 a year with one counterparty), long or auto-renewing contracts, borrowing, and any related-party transaction. The Executive Director may not also be treasurer, is added to the authorized signatories, and “signature authority is not approval authority.”'

Governance Committee Update

  • Purpose: at Steve Waite’s request, David Eschelbacher explained for the guest that the committee’s main work has been negotiating a partnership with OpenCoreEMR (OCE).
  • Partnership tiers: the Foundation has been developing tiered website partnership (advertising) levels, each with an associated fee. The aim is to move the relationship with OCE from an informal arrangement to a formal, paid partnership. OCE’s contributions to the project were acknowledged.
  • Status: negotiations are continuing, and the committee hopes to reach a conclusion within the next few weeks. Further discussion was deferred.
  • Conflict-of-interest disclosure: Maxine Radcliffe said she may have a conflict of interest, as co-director of Open Plan IT, which also contributes to OpenEMR and would probably be interested in a presence on the website. In response, it was noted that conflicts of interest among those involved have been handled carefully within the Governance Committee, and that Open Plan IT’s contributions are also valued.
The January 14, 2026 minutes record contract negotiations with OCE “regarding use of the OpenEMR name,” and later minutes track the Governance Committee’s work on advisory committees and the bylaws amendments. OCE is an OpenEMR vendor and code contributor, so the terms of a paid partnership will also set a pattern for other vendors who want a presence on the website.
Under the IRS sample conflict-of-interest policy, an “interested person” (a director, principal officer, or member of a committee with delegated board powers) discloses the interest, leaves the deliberation, and the disinterested directors decide (summary). Bylaws §8.3 requires the board to adopt and periodically review such a policy. A guest has no vote, so a guest’s disclosure is mainly a matter of transparency, but recording disclosures in the minutes is good practice.

Treasurer’s Report

  • Financial statements: Steve Waite posted the September 2026 and third-quarter 2026 profit-and-loss statements and the September 30 balance sheet to the agenda thread. Finances are steady. It was pointed out that the two profit-and-loss files appeared to be mislabeled, and Steve Waite will correct them.
  • Open Collective: the balance is over $2,000. The figure in the thread had not been updated, but the Open Collective page shows the current amount.
OpenEMR’s Open Collective is hosted by Open Source Collective, a nonprofit fiscal host that handles accounting, payments and tax reporting for open-source projects and charges 10% of funds raised (Open Source Collective). On October 14, 2026, the page showed a balance of $2,157.19 and $15,974.91 raised in total.
  • ONC certification campaign payout: Steve Waite proposed beginning to repay Stephen Nielson and Jerry Padgett for their past work on OpenEMR’s ONC certification update for 2025 (the HTI-1 updates), which the Foundation’s certification fundraising campaign was intended to cover. He suggested about $1,500 a month, an amount the budget can comfortably absorb: $1,200 to Stephen Nielson and $300 to Jerry Padgett.
  • Support and flexibility: support was expressed, with the point that the amount can be raised, lowered or paused as finances change.
  • Affordability: it was noted that, apart from campaign income, the quarter was roughly break-even with a slight loss, and that adding $1,500 a month might be difficult without more revenue. David Eschelbacher asked how long the Foundation’s assets would last at the current rate with the payments added. In reply, it was said that payments would be stopped or reduced if assets fell to an uncomfortable level, that the board can revisit the matter each month, and that assets are currently at a good level. It was also argued that starting with a very low amount would stretch repayment over too many years.
  • Priorities: questions were raised about whether reserves should first cover possible legal costs, including those connected with the ongoing negotiations, and whether pursuing ONC e-prescribing certification, criterion (b)(3), should take priority as a way to bring in revenue. Steve Waite replied that future expenses cannot be predicted, that new initiatives need their own fundraising, and that repayment was overdue and should begin, even slowly.
  • Campaign income: Steve Waite noted that the Zeffy campaign accounts for essentially all of the period’s net income, citing $14,400 raised through the campaign and net income of $13,400 for the period.

Motion: to begin payment for past ONC certification work at $1,200 a month to Stephen Nielson and $300 a month to Jerry Padgett — paid on the 15th of each month, “automatic for the next three months,” after which the board will review it. Moved by Steve Waite; seconded Brady Miller. Carried, 7–0, by roll call: David Eschelbacher, Steve Waite, Asher Densmore-Lynn, Brad Sharp, Sherwin Gaddis, Brady Miller and Ravi Kafle in favor; Rachel Ellison absent.

The board decided in October 2025 to run a donation drive to pay for the ONC development work (minutes). The Zeffy campaign had a $200,000 goal, and the April 8, 2026 minutes record $54,265 raised by then. Zeffy charges nonprofits no fees and is funded by optional contributions from donors (Zeffy). OpenEMR 8 was certified on January 30, 2026 (CHPL listing 11757) and released on February 11 (certification page).
HTI-1, ONC’s rule finalized in December 2023, replaced year-themed certification editions, made USCDI v3 the new data baseline, and required updates to 15 certification criteria by December 31, 2025, including the standardized FHIR API, (g)(10) (HTI-1 overview; deadlines).

Trademark Application

  • Still pending: Steve Waite reported that the application is still pending at the U.S. Patent and Trademark Office (USPTO). The USPTO’s response will go to the Foundation’s attorney, who will then update the board. When he last checked the USPTO’s public search, the application had not yet been assigned to an examining attorney. Last time, he noted, it took about five months for the USPTO to act.
The USPTO reports average first-action pendency of 4.45 months in the first half of fiscal 2026, down from 5.6 months in fiscal 2025, and aims for four months by fiscal 2028 (USPTO). Earlier minutes record a June 2026 motion approving about $600 for an attorney to respond to a correction request (June minutes), and a new application filed through the attorney by August (August minutes). The agenda’s “USTPO” is the USPTO.

Discussion Topics

OpenEMR Project Updates

  • OpenEMR 8.4.1: Brady Miller reported that 8.4.1 was released on September 20, mainly as a bug-fix release. It was the first time the project used its upgrade-based release mechanism for a patch-sized release instead of the older patch mechanism; the project now issues only upgrade-mechanism releases.
Recent releases, from the release tags and changelog: 8.2.0 (July 8), 8.3.0 (August 18), 8.4.0 (September 13) and 8.4.1 (September 20). The 8.4.1 changelog lists back-ported fixes to billing, auditing, the portal and the eye form. In the past, OpenEMR shipped “patches” applied on top of an installed version; delivering fixes as ordinary point releases lets every fix go through the same automated release and upgrade path.
  • Next release: expected in about a week, two at most. The plan is monthly releases, but this one may slip a week to let more security work land and to allow time to stabilize the new work, particularly FHIR write.
  • Node services removed: FHIR write capability has been added, and the Node.js services that generated C-CDA documents, ran Schematron validation, and calculated clinical quality measures (QRDA) have been removed, so the project no longer needs that infrastructure. Brady credited Jerry Padgett with this work. With so much change landing, he described the codebase as “a tiny bit unstable” for now.
C-CDA (Consolidated Clinical Document Architecture) is the HL7 standard for clinical summary documents exchanged between systems. Schematron is a rule-based validator used to check C-CDA documents. QRDA (Quality Reporting Document Architecture) is the format for reporting electronic clinical quality measures: Category I for patient-level and Category III for aggregate reports. The code history shows the sequence: Schematron moved to PHP on September 22 (#14005), C-CDA generation on October 7 (#13983) with the Node service retired on October 8 (#14470), and quality-measure calculation on October 11 (#14469) with its Node service retired on October 13 (#14524). Per the October 6 weekly call, Node now remains only as a build-time tool for front-end packages, which means one less runtime to patch and smaller Docker images.
  • Security: Brady is spending much of his time on vulnerability reports received through GitHub Security Advisories. Their volume has surged across open-source projects as AI tools are used to find flaws. He is also proactively hardening and regression-testing the API and authorization layers, including FHIR, since certified FHIR endpoints are publicly listed and the API now supports writes. He expects the security push to continue for another six to nine months.
A GitHub Security Advisory (GHSA) is GitHub’s private channel for reporting and coordinating the fix of a vulnerability before it is published; OpenEMR lists published advisories in its release changelog. The surge is industry-wide. FIRST forecasts about 66,000 CVEs in 2026, with AI-assisted discovery as the main driver (Help Net Security), and the Spring project went from about 6.5 security reports a month to 482 in April 2026 (Spring). ONC requires developers of certified FHIR APIs to publish the service base URLs of their customers’ endpoints, and ONC’s Lantern project checks them daily (ONC), so certified endpoints are discoverable by design.
  • Pull request volume: AI-assisted contributions have sharply increased the number of pull requests, and Brady said they are generally of good quality. He merged about 60–70 mostly small PRs in the past week, and the open PR count is back to about 300, after he had brought it down to 230–240. At least 20 commits landed in a single day earlier in the week. He described the work as having shifted from code development to “code project management.”
The main branch’s history bears this out: 20 commits on October 12, 26 on October 13, and about 70 in the week of October 7–13. The October 13 weekly call set a goal of keeping open PRs below 300 and giving priority to small PRs.
  • FHIR write — questions from Maxine Radcliffe: she asked where FHIR write is documented (its scopes and the data mapping, or “ontology”), and what clinical review it has had. The responses:
    • It is presented as experimental for now. The endpoints are listed in the project’s Swagger API documentation, and the scopes are defined in the code base.
    • Writes are available only with user-level scopes, not patient or system scopes. Jerry Padgett is working on auditing.
    • It is comprehensive enough to import Synthea synthetic patient data through FHIR, which is used for testing, but it is not complete; some Observation endpoints are not yet in. It should not be used casually in production by anyone who does not understand it.
    • At the user level, write access is comparable to what a logged-in user can already do. Importing data that must be audited, or letting patients write, would be more complex.
    • Maxine Radcliffe stressed that data-model and terminology choices become clinically significant, and asked about clinical oversight and ownership of them. It was agreed to continue the discussion outside the board meeting.
SMART on FHIR scopes have three prefixes (HL7 SMART App Launch): patient/ gives access to data about the patient in context; user/ to data the signed-in user can access; and system/ to a backend client acting without a user. The permission letters c, r, u, d and s stand for create, read, update, delete and search. ONC’s standardized API criterion, (g)(10), requires read access (test method), so FHIR write goes beyond what certification requires. OpenEMR’s FHIR README documents scopes and links to the Swagger documentation.
Synthea is MITRE’s open-source (Apache-2.0) synthetic patient generator, which produces realistic but fictitious records in FHIR and C-CDA formats (Synthea). Related weekly-call decisions: on October 6 the group agreed to keep FHIR writes off by default; on October 13 this became a prominent alert when an administrator enables a client that requests write scopes (#14509), with system clients unable to get write scopes at all. Vital-signs Observation writes were added on October 3 (#14217).
Maxine Radcliffe’s question reflects how health IT is governed in the UK. In England, standards DCB0129 (for manufacturers) and DCB0160 (for deploying organizations) require clinical risk management overseen by a named Clinical Safety Officer (NHS England). Clinical review of how data is mapped to coded terminologies is part of that work. OpenEMR has no equivalent formal process, so this may be a useful topic for the community.

OpenCoreEMR

  • Steve Waite skipped the separate OpenCoreEMR update. The partnership negotiations were covered in the Governance Committee update.

eRx — LogiCoy

  • Background: Steve Waite noted LogiCoy’s presentation on the October 13 weekly community call. He proposed referring the matter to the Governance Committee — “not authorize, just refer” — to consider what steps are needed toward some kind of partnership that recognizes what LogiCoy would like to do together with the Foundation.
  • Discussion: support was expressed for moving ahead. Given the time available, Steve Waite did not want a long discussion, and said he hopes the committee’s current work with OpenCoreEMR will wrap up first so that this can have its full attention.
  • Outcome: the board agreed to refer the LogiCoy partnership question to the Governance Committee. No formal motion was made.
LogiCoy was founded in California in 2009 by engineers who had built OpenESB at Sun Microsystems (About). It offers a standalone e-prescribing application and an e-prescribing API. It states that it is ONC-certified (CHPL listing 10944), certified by Surescripts, compliant with the DEA’s rules for electronic prescribing of controlled substances, and uses ID.me for identity proofing (Compliance). On the October 13 call, LogiCoy demonstrated a module that plugs into OpenEMR and connects directly to Surescripts.
OpenEMR 8’s current certification does not include e-prescribing, (b)(3) (certification page). Under HTI-4, (b)(3) moves to NCPDP SCRIPT 2023011 after a transition ending December 31, 2027, and from January 1, 2028, modules certified to (b)(3) must also certify to real-time prescription benefit, (b)(4) (HTI-4 key dates). E-prescribing is a required measure in the 2026 MIPS Promoting Interoperability category (2026 measures). The HTI-5 proposed rule (December 2025) would remove or revise many other criteria; as of its last update it had not been finalized (HTI-5). The board discussed partnering with an eRx vendor for ONC purposes at its August and September meetings.

Telemetry and Privacy Policy

  • Telemetry: not discussed; deferred.
  • Privacy policy: Steve Waite noted that the privacy policy on the website is out of date and needs to be aligned across the website, the forum and the Foundation’s other public-facing properties. The Foundation has little data on who visits its sites and relies on others to tell it how it is doing. The privacy policy will need to state what analytics are used. Deferred to the November meeting.
Telemetry background: in March 2025 Jerry Padgett proposed an opt-in module to collect usage statistics such as menu-click totals and general location (forum proposal). The January 2026 minutes record that he built a tool to query the data and that a committee would decide who can access it. On the October 6 weekly call, telemetry showed Windows users moving from XAMPP to WSL and Docker, and it was noted that multisite use is not tracked.
On analytics and visitors from different places: in the EU, analytics cookies generally need prior opt-in consent. In the UK, since February 5, 2026, the Data (Use and Access) Act 2025 allows analytics cookies used only for statistical purposes without consent, provided users are informed and can object. In the U.S., ordinary analytics needs no opt-in consent (summary). A policy that covers both the website and the forum will need to reflect whichever tools each one uses.

Fundraising: Email Campaign and Grant Opportunity

  • Email campaign: deferred to the next meeting.
  • Grant opportunity: Sherwin Gaddis said he has decided to take on fundraising and grant writing because the opportunities are there. To apply for a grant he sees as low-hanging fruit (about $50,000), he needs documentation he does not have access to, and approval to apply. He also intends to take over grant applications in general and build a pipeline of applications as opportunities arise. Approval to go ahead was given in the meeting; no formal motion was made.
  • Documents: Sherwin’s e-mail of September 30 lists the documents needed. Those mentioned were the IRS determination letter, the current board leadership, governance documents and the conflict-of-interest policy, financial statements and Form 990 filings, and evidence of ONC certification. Most are already in the Foundation’s shared folder or publicly available; missing items are to be added to the shared folder so that everything is in one place.
  • European funding: Maxine Radcliffe noted that several significant European grants could be pursued, including Horizon Europe programs, particularly in connection with the FHIR write work, and that academic institutions in Ireland and the UK have substantial funds for open-source health projects. How to approach them depends on which entity applies. Sherwin Gaddis welcomed working together. It was noted that the grant under discussion appears to require a strong European dimension, so it would probably need to be pursued through a partnership with European collaborators rather than by the U.S. Foundation directly. Sherwin’s e-mail is to be forwarded to Maxine Radcliffe.
  • Future agenda: it was suggested that grant applications become an agenda item separate from fundraising, and that future meetings discuss Ireland and possible mechanisms for European funding.
An IRS determination letter confirms an organization’s 501(c)(3) status and is a standard grant requirement. Form 990 is the annual information return: organizations with gross receipts normally of $50,000 or less may file the 990-N e-Postcard, those under $200,000 in receipts and $500,000 in assets may file the 990-EZ, and failing to file for three consecutive years revokes exemption automatically (thresholds). Bylaws Article 10 already requires the Foundation to make its Forms 990 and 1023, bylaws, conflict-of-interest policy and financial statements “widely available” on its website, free of charge.
Most Horizon Europe programs require at least three partners from three different EU member states or associated countries. The United States is not an associated country, so U.S. entities can take part but receive EU funding only in special cases, such as when the call allows it or the Commission judges the U.S. partner essential (Horizon Europe participation). This is why a European entity or partner usually leads.

OpenEMR App Marketplace

  • Ravi Kafle reported that the marketplace is still in progress. Sherwin Gaddis had earlier offered to collaborate, and Ravi plans to reconnect with him in a week or so to plan the set of applications. He hopes to give a short demo at next month’s meeting. Steve Waite suggested that a weekly community call might give it more time than the crowded board agenda, and Ravi said he intends to start attending the Tuesday calls.
The weekly community call is open to anyone, on Tuesdays at 11:00 a.m. Pacific (2:00 p.m. Eastern) (call details). The marketplace has been on the board agenda since at least May 2026 (May minutes).

Veradigm DORN Integration

  • Steve Waite reported that things have been quiet. Veradigm has not responded about a lab connection explored earlier, and the Foundation may contact Veradigm again to ask whether it is ready for testing. Brad Sharp has not heard anything either.
DORN is Veradigm’s Diagnostic Ordering and Results Network. It gives an EHR access to hundreds of laboratory and radiology partners through one API integration instead of separate point-to-point interfaces, and offers vendors a revenue-share model (Veradigm). The integration has appeared on board agendas since at least October 2025.

Ireland Update

  • Presentation: Maxine Radcliffe reported that she presented the previous day at an Engineers Ireland event where OpenEMR was a central focus. There is strong interest in Ireland in using OpenEMR as the core of an open-source medical record for the whole country, or more widely. The professor leading the effort had appeared on the national news and national radio the previous Thursday, and the event drew industry leaders and senior academic clinicians.
  • Funding: she urged a strategic look at funding, whether money flows to the Foundation directly or pays for engineering capacity, such as a director of engineering and junior developers.
  • Other avenues: religious orders that run clinics internationally without an EHR have expressed interest. At the University of Oxford, the Bennett Institute, known for open data work, has developers interested in helping and access to significant funding, and senior academics could help secure funding.
  • Follow-up: Maxine Radcliffe invited questions by e-mail and offered to help with grant funding. Steve Waite said the board would follow up.
Engineers Ireland, founded in 1835 as the Institution of Civil Engineers of Ireland, is Ireland’s professional body for engineers (history). Ireland has no national electronic health record. The Government approved the HSE’s preliminary business case in April 2025, and in February 2026 cleared procurement to begin shortlisting electronic patient record suppliers (Computer Weekly). Maynooth University’s Digital Health Spine Living Lab, built on OpenEMR, was publicly launched in 2024 with Stephen Waite’s public support (Maynooth).
The Bennett Institute for Applied Data Science, part of Oxford’s Nuffield Department of Primary Care Health Sciences, combines software developers, clinicians and academics. It publishes its code openly and runs OpenSAFELY, a secure analytics platform for NHS records, and OpenPrescribing (Bennett Institute). Maxine Radcliffe also noted, in her introduction, the alignment between OpenSAFELY and OpenEMR.

New Meeting Time

  • This was the first meeting at the new time; the item was noted as done. See the note under Welcome and Opening Thoughts.

Opal Partnership

  • Stephen Nielson reported on his conversation with John Kildea of Opal. Opal is trying to set up a vendor partnership in Canada to unlock more grant funding, because the grants favor local Canadian companies delivering OpenEMR. The prospective partners have extensive experience in healthcare and open source but are new to OpenEMR, and are assessing what is involved in running and managing an EMR in a regulated environment. The Foundation is waiting to hear whether they will stay engaged. Stephen Nielson has also been trying to connect Steve Waite with them.
Opal is a patient portal app developed at the Research Institute of the McGill University Health Centre, launched clinically in 2018. MUHC support ended in December 2024, when Quebec moved to a province-wide proprietary EHR, and Opal was released as open-source software in 2025. John Kildea directs the Opal Health Informatics Group, which formed a strategic partnership with the OpenEMR Foundation in April 2025 and is seeking vendor and foundation partners (Canadian Healthcare Technology).

Stripe Discussion

  • Steve Waite reported that Stripe has been in touch again and is still asking for figures. A rough estimate will be prepared and sent to see their response.

Statement Integration

  • On the agenda (Steve Waite believed it related to billing), but skipped.

Other Business

Meeting Recording and AI-Assisted Minutes

  • Brady Miller, as Secretary, normally prepares the minutes. Asked whether the regular minutes would continue alongside the recording, David Eschelbacher offered to send Brady an AI-assisted summary of the recording, to use as the minutes or as input to them. The board agreed to prepare a draft from the recording alongside the usual minutes and decide later which to use. Attendees complimented the detailed summaries of the weekly community calls.
Bylaws §6.6 makes the Secretary responsible for keeping, “or caus[ing] to be kept,” the minutes of all meetings, and allows the Secretary, with board approval, to appoint a director to help. Under §10.4(b), board minutes are open to the public once the board accepts them. Hence the “draft” label on these minutes.

A European Presence

  • During introductions, it was mentioned that discussions have included either launching a sister organization in Europe or Maxine Radcliffe joining this board, and that approval to pursue a sister organization had already been received. Now that the meeting time suits European participants, working together within the existing board may make sense. This will be a conversation for the board.
Other U.S.-born open-source foundations have created European entities: the Eclipse Foundation set up Eclipse Foundation AISBL in Brussels in 2020 (Eclipse), and the Linux Foundation launched Linux Foundation Europe, also in Brussels, in September 2022 (Linux Foundation). A European entity can apply directly for EU funding (see the Horizon Europe note above), at the cost of a second organization to govern. Adding directors to the existing board is simpler: bylaws §4.1 allows up to fifteen directors, elected by a majority of the board (§4.4).

Decisions and Actions

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

Item Decision / Action
September 9 minutes Approved without objection.
ONC certification payout Motion carried 7–0: $1,200 a month to Stephen Nielson and $300 a month to Jerry Padgett, paid on the 15th of each month starting this month, automatic for three months, then reviewed by the board.
Bylaws Amendments 1–5 are now tracked in the public foundation-minutes repository.
eRx — LogiCoy Referred to the Governance Committee to consider steps toward a possible partnership, ideally after the current OpenCoreEMR work concludes. No formal motion.
Grant application Sherwin Gaddis given approval to proceed (no formal motion). Documents listed in his September 30 e-mail to be gathered in the shared folder. His e-mail to be forwarded to Maxine Radcliffe for the European angle.
Future agenda items Grant applications as a separate item; Ireland and mechanisms for European funding; Telemetry, Privacy Policy and the fundraising email campaign deferred to November.
FHIR write Maxine Radcliffe’s questions on documentation and clinical review to be continued outside the board meeting.
App marketplace Ravi Kafle plans to reconnect with Sherwin Gaddis; a demo may follow at a board meeting or a weekly call.
Veradigm DORN Veradigm may be contacted again about readiness for testing.
Stripe A rough estimate of the requested figures to be prepared and sent.
Opal Awaiting word on whether the prospective Canadian vendor partners will stay engaged.
Trademark Awaiting USPTO action; the attorney will update the board.

Agenda Items Not Reached

  • OpenCoreEMR: skipped as a separate item; the negotiations were covered in the Governance Committee update.
  • Telemetry: deferred to November.
  • Privacy Policy: briefly introduced; full discussion deferred to November.
  • Fundraising email campaign: deferred to the next meeting. The grant opportunity was discussed.
  • Statement Integration: skipped.

Notes

  • A common thread: many items came back to how the Foundation funds its commitments. The payout, the reserve for possible legal costs, the hoped-for partnership revenue, eRx certification, U.S. and European grants, and the Stripe figures all draw on the same small budget. The three-month review built into the payout motion gives the board a natural point to look at them together.
  • Funding follows local entities: the Ireland, Horizon Europe and Opal items share a pattern. Funders in Europe and Canada favor local organizations, so international growth may depend on local partners or entities. That links the European-presence discussion to the grant pipeline.
  • FHIR write and clinical review: Maxine Radcliffe’s questions connect to the weekly-call decisions on gating FHIR writes. Community members with clinical-safety or terminology experience would be valuable reviewers as the feature matures.
  • Related weekly calls: October 6, 2026 (Node services, FHIR write gate, telemetry) and October 13, 2026 (LogiCoy, PR volume, FHIR write alert).
  • Comments and corrections are welcome in the agenda thread on the community forum.

End of the Open Session

The open session concluded after the Statement Integration item. The time was not stated in the recording. The next monthly board meeting is scheduled for November 11, 2026.