HIPAA-Compliant EHR for Optometrists: 2026 Compliance Checklist
A HIPAA-compliant eye care EHR is one whose vendor signs a business associate agreement and whose software supports the safeguards you must apply: risk analysis, unique logins, audit logs, backups and encryption. HHS proposed a stricter Security Rule in January 2025, with mandatory encryption and MFA, but as of October 2026 it is not final.
On this page
- Why HIPAA compliance matters for an eye care practice
- What the HIPAA Security Rule requires today
- What the proposed HIPAA Security Rule update would change
- Questions to ask an EHR vendor before you sign
- Features that reduce compliance risk
- Common HIPAA mistakes in optometry practices
- How the main optometry EHR platforms compare on security
A HIPAA-compliant EHR does not make an optometry practice compliant on its own. HIPAA binds your practice, and it binds your EHR vendor as your business associate. The software has to support the safeguards the law requires, and the vendor has to sign a business associate agreement (BAA). This guide covers the rules that apply today, the Security Rule update HHS has proposed but not finalised, and the questions to ask any vendor before you sign.
Why HIPAA compliance matters for an eye care practice
An optometry record holds more than a prescription. It holds diagnoses, medications, insurance details, and retinal and OCT images, all of it protected health information. Eye care software is a target like any other. In December 2021 an intruder gained access to the myCare Integrity EHR run by Eye Care Leaders, an eye care software vendor. The practices that used it then filed their own breach reports with the HHS Office for Civil Rights (OCR), and by June 2022 the reported total passed 2 million people. The breach happened at the vendor, but each practice had to notify its own patients.
Civil penalties come from a federal table that HHS adjusts for inflation every year. Under the 2025 figures in 45 CFR 102.3, they start at $145 per violation when you could not have known about it. They reach $2,190,294 for willful neglect left uncorrected, which is also the calendar-year cap for identical violations.
What the HIPAA Security Rule requires today
The current Security Rule (45 CFR Part 164, Subpart C) is the rule in force. Three parts of it matter most when you choose or audit an EHR.
- Risk analysis: You must assess the risks to the electronic patient data you hold. This is a required specification, but the rule sets no fixed interval. Review it when you change systems, open a location or add remote access. HHS and ONC publish a free Security Risk Assessment Tool sized for small practices.
- Business associate agreement: A vendor that stores or handles patient data for you must sign a BAA before you share any data. The BAA must require the vendor to report breaches to you. Under 45 CFR 164.410, a business associate must do so without unreasonable delay and no later than 60 calendar days after it discovers a breach.
- Technical and contingency safeguards: Audit controls that record activity in systems holding patient data are required. So are unique user IDs, a data backup plan and a disaster recovery plan. Automatic logoff and encryption are "addressable".
"Addressable" does not mean optional. You must implement the safeguard, or document why it is not reasonable for your practice and what you do instead. A modern cloud EHR should encrypt data and log idle users off by default, which removes the need to justify a gap.
What the proposed HIPAA Security Rule update would change
On 6 January 2025, HHS published a notice of proposed rulemaking to rewrite the Security Rule. Comments closed on 7 March 2025. As of October 2026 it is still a proposal, not a final rule, so none of it is enforceable yet. If HHS finalises it as proposed, it would:
- remove the split between "required" and "addressable" safeguards, so the specifications become mandatory;
- require encryption of all electronic patient data at rest and in transit, with limited exceptions;
- require multi-factor authentication (MFA) on systems that hold patient data;
- require a written technology asset inventory and network map, kept current;
- require network segmentation, so an intruder on one device cannot reach every system;
- require vulnerability scans at least every six months and a penetration test at least every 12 months;
- require written procedures to restore critical systems and data within 72 hours of a loss;
- require a compliance audit against the rule at least every 12 months;
- require written confirmation from each business associate, at least every 12 months, that it has deployed the required technical safeguards.
On timing, the 2026 Unified Agenda entry for RIN 0945-AA22 moves the rule to "long-term actions" and projects final action for July 2027. The Spring 2025 agenda had projected May 2026. The proposal says a final rule would take effect 60 days after publication, with compliance due 180 days after that. Agenda dates are not binding: HHS could finalise sooner, change the text or withdraw it.
The practical answer: comply with the current rule, and buy for the proposed one. An EHR you sign for now will likely still be running when a final rule arrives, so encryption and MFA should come standard rather than as paid add-ons.
Questions to ask an EHR vendor before you sign
- Encryption: Is patient data encrypted at rest and in transit, including images and backups? AES-256 at rest and TLS 1.2 or later in transit are the answers you want to hear.
- MFA: Can you require multi-factor authentication for every user, including remote access?
- Audit logs: Does the system log every view, change and export of a record, and can you run that report yourself?
- Access roles: Can you limit front-desk staff to scheduling and billing, and keep clinical notes to clinicians?
- BAA: Will the vendor sign a BAA, and does it bind subcontractors such as the cloud host?
- Breach notification: How quickly will the vendor tell you about a breach? The law allows up to 60 days, so ask for a shorter window in the contract.
- Data location and recovery: In which country is your data stored, how often is it backed up, and how fast can it be restored?
- Independent evidence: Can the vendor share a current SOC 2 Type II report or an equivalent audit? A SOC 2 report is a voluntary attestation, not proof of HIPAA compliance, but it shows controls were tested over time.
- Breach history: Has the vendor or any of its products had a reportable breach in the last three years? OCR lists breaches affecting 500 or more people on its public breach portal.
- Exit terms: Will the vendor return all of your data, images included, in a usable format if you leave?
Features that reduce compliance risk
Beyond the minimum, some features remove whole categories of mistake:
- Integrated image storage: Retinal photographs, OCT scans and visual fields sit in the EHR with the same protections as clinical notes, not in a shared folder or a personal cloud drive.
- Secure in-system messaging: Messages between staff and patients stay inside the system instead of personal email or text.
- E-prescribing with EPCS: Where your state lets optometrists prescribe controlled substances, DEA rules require identity proofing and two-factor authentication to sign those prescriptions.
- Built-in risk assessment tools: Some platforms include questionnaires that help you record gaps and fixes between formal reviews.
Common HIPAA mistakes in optometry practices
The most common errors are ordinary ones: clinical details sent by unencrypted text or email, patient images saved to personal cloud accounts such as Google Photos or Dropbox, shared logins at the front desk, and front-desk staff with full access to clinical records. Your EHR should make these mistakes hard by design, not just by policy. If your current system allows all of them, it is time to reassess.
How the main optometry EHR platforms compare on security
RevolutionEHR, Compulink Advantage, Eyefinity EHR, MaximEyes and iMedicWare are five of the optometry EHR platforms we have reviewed. Any of them that hosts your patient data is a business associate and must sign a BAA, so get it in writing before go-live.
Published security evidence varies. Eyefinity says its cloud practice management software, including Eyefinity Encompass, has held SOC 2 Type 2 since April 2023, with annual audits. We could not find a current public SOC 2 statement from the other four, which does not mean they lack one. Ask each vendor for its latest report under a non-disclosure agreement, and compare what each audit actually covered.
Our recommendation: shortlist only vendors that sign a BAA, support MFA and encrypt data at rest by default, then run your own risk analysis on the system you choose. If you are still comparing platforms, start with our comparison of optometry EHR software. If you are deciding where your data should live, read cloud versus server-based EHR next.