Short answer: no software is “HIPAA compliant” on its own, and OpenEMR does not claim to be. HIPAA applies to the practice (and its business associates), not to a program. What OpenEMR gives you is a set of features the HIPAA Security Rule expects to exist: per-user access control, audit logging, multi-factor login, password rules and encryption of stored documents. Whether your clinic is compliant depends on how you host it, configure it, patch it and run it. The US Department of Health and Human Services (HHS) states plainly that it does not recognise private “certifications” for the Security Rule. Facts below were checked on 19 November 2026 against hhs.gov, open-emr.org and the OpenEMR GitHub repository. Status: Not tested yet. We read the official documentation; we have not audited an OpenEMR installation. This is general information, not legal advice. HIPAA is US law; clinics in the UK, Canada and the EU follow their own data-protection rules.
OpenEMR and HIPAA at a glance
| Question | Answer (checked 19 November 2026) |
|---|---|
| Current stable version | 8.5.0 (changelog dated 26 October 2026) |
| Licence | Free, open source (GPL v3) |
| Server requirements for 8.5.0 | PHP 8.3+, MariaDB 10.11+ or MySQL 8.4+; users work in a web browser |
| What the project says about HIPAA | Its home page calls the access control “HIPAA-friendly”; it does not call the software “HIPAA compliant” |
| ONC certification | “OpenEMR 8” certified on 30 January 2026, including the 170.315(d) privacy and security criteria |
| Security fixes in the latest release | 8.5.0 lists 84 fixes linked to GitHub security advisories: 6 Critical, 32 High, 45 Medium, 1 Low |
| Dental chart in core | No. The official feature list names an eye module as its specialty module, not a dental one |
| Who is responsible for HIPAA | The practice and its business associates (hosting provider, IT contractor) |
Our catalogue page for OpenEMR covers installation options and what the project offers out of the box.
Why “HIPAA compliant software” is the wrong question
HHS answers this directly in its FAQ on Security Rule certification: there is no requirement to “certify” compliance, and HHS “does not endorse or otherwise recognize private organizations’ ‘certifications'” (HHS FAQ).
The HHS summary of the Security Rule applies it to health plans, clearinghouses, any health care provider that transmits health information electronically in connection with a standard transaction (sending electronic claims is the usual trigger for a dental office), and their business associates. It is deliberately “technology neutral”: it does not name products. It requires administrative, physical and technical safeguards, and above all a risk analysis that you perform and document.
What OpenEMR provides, and what the clinic must still do
Technical safeguards from the HHS summary, mapped to settings on the OpenEMR wiki:
| Security Rule safeguard | What OpenEMR documents | What the clinic still has to do |
|---|---|---|
| Access control | Fine-grained per-user access control lists and role-based menus | Give each person their own account and only the access their role needs; remove leavers promptly |
| Authentication | Multi-factor login with TOTP or U2F keys; strong-password, minimum-length and expiry settings | MFA is enrolled per user; the wiki does not describe a switch that forces it for everyone, so make it a written policy and check enrolment |
| Brute-force protection | “Maximum Failed Login Attempts” locks a user out after repeated failures | Set a number: the wiki says 0 (no limit) is the default |
| Audit controls | Audit logging for patient records, scheduling, orders, security administration, backups and queries; optional audit log encryption | Turn on the categories you need and actually review the logs on a schedule |
| Integrity and stored data | Encryption of items stored on the drive (and on CouchDB if used); upload white list for file types | The setting covers stored items, not the database itself; protect the database server and disks separately |
| Transmission security | Securing guide: allow HTTPS only and open only port 443 | Install a valid TLS certificate and keep the server off the open internet unless you need remote access |
| Contingency plan | Built-in backup tools; note that they do not back up documents stored in CouchDB | Keep an off-site copy and test a restore |
The hardening steps the project itself recommends
The Securing OpenEMR wiki page (last edited January 2023, so read it alongside current release notes) lists the operator’s tasks:
- Remove
setup.phpand the other setup and upgrade scripts after installation, or block access to them. - Block direct web access to
sites/*/documents, where patient files live. - Serve the application over HTTPS only and turn off plain HTTP.
- Turn on “Enable Encryption of Items Stored on Drive” and “Secure Upload Files with White List”.
- Enforce strong passwords, password expiry and multi-factor authentication.
- Give the database user rights only to the OpenEMR database, set a root password, and protect any phpMyAdmin access.
- Run a supported PHP version and install the most recent patch after every install or upgrade.
The last point matters more than usual right now. The 8.5.0 release notes list 84 security fixes, six rated Critical; the first describes a front-office account escalating to read the whole database. If your server runs an older version, upgrading is part of your HIPAA risk management, not an optional extra.
Hosting, cloud and the business associate agreement
If OpenEMR runs on a cloud server or a hosting company manages it, that provider stores ePHI on your behalf. HHS guidance on HIPAA and cloud computing says such a provider is a business associate and you must sign a business associate agreement (BAA) with it. This applies even if the provider stores only encrypted data and has no key.
The OpenEMR home page describes its AWS “Express Plus” package as built on HIPAA-eligible AWS services, designed to support a HIPAA-compliant deployment “when properly configured”, including a BAA with AWS. Even the project’s own cloud package puts configuration and the BAA on you.
What ONC certification does and does not mean
The OpenEMR wiki lists an ONC Health IT certification for “OpenEMR 8”, dated 30 January 2026, covering criteria that include the 170.315(d) privacy and security set (authentication, auditable events and related items). ONC certification tests that the software has those capabilities. The wiki adds that the certification “does not represent an endorsement” by HHS. It says nothing about your policies, risk analysis, hosting or training. The earlier OpenEMR 7.0 certification was retired on 27 February 2026, so practices relying on certification for US programmes need version 8 or later.
Risk analysis: the part no software does for you
The HHS summary makes risk analysis the base of every other safeguard: identify where ePHI lives, what threatens it, and what you have done about it, then review it when anything changes. The OpenEMR wiki’s own Security Assessment and Privacy Assessment pages (written in 2014) say the same. For a small practice, HHS and ONC publish a free Security Risk Assessment Tool aimed at small and medium providers. Their note is the honest summary of this whole topic: using the tool “is neither required by nor guarantees compliance”.
Limitations
- Some wiki pages are old (2014–2023). Setting names can change between versions; check them in your own Administration menu.
- HHS has published proposed changes to the Security Rule. Its summary page describes the rule currently in effect; check the status before you rely on details.
- OpenEMR has no dental chart in core. A dental practice either builds custom forms or chooses a different system, which changes the risk picture.
Who should use OpenEMR, and who should not
OpenEMR suits a US clinic that has, or pays for, someone to run a Linux or Docker server, patch it promptly and document a risk analysis. It is a poor fit for a practice that wants a vendor to take over security, or one that needs a dental odontogram without customisation. For alternatives, GNU Health has a dentistry package with an FDI odontogram, and Bahmni is a free hospital system built on OpenMRS where dental units use custom forms. Our free dental EHR software hub compares the options.
FAQ
Is OpenEMR HIPAA compliant?
No software is. OpenEMR provides access control, audit logging, multi-factor login and encryption of stored documents. Compliance depends on your configuration, hosting, BAAs, risk analysis and staff policies.
Is OpenEMR safe?
It is actively maintained and publishes security advisories on GitHub; 8.5.0 fixed 84 reported issues. It is as safe as the server, version and settings you run. Old, unpatched installs are the main risk.
Is OpenEMR really free?
Yes. The software is free under GPL v3. You still pay for your own server or hosting and for any outside administration you need.
Is OpenEMR open source?
Yes. The source code is public on GitHub under GPL v3, and security issues can be reported privately through GitHub or to the project’s security team.
Does running OpenEMR in Docker make it HIPAA compliant?
No. Docker is only a way to install it. HTTPS, backups, access control, patching and a BAA with any cloud host are still required.
Editorial team, dentiit.com. Checked 19 November 2026. Not legal advice.
Last updated: 19 November 2026 · DentIIT editorial team. Licence, version and platform details are checked against each developer's official documentation; none of the tools listed here should be treated as a certified medical device unless its vendor says so.





