The HIPAA Security Rule update is still a proposed rule, not final law. HHS published it on January 6, 2025, and the current rule stays in force. Practices should keep meeting today's risk analysis, access and vendor duties while watching for a final rule.
Many articles written in 2025 described the changes as “now required.” That was never accurate. This guide separates what is proposed from what is enforceable, gives the dates with sources, and turns the proposal into checks your billing team can run today. It is written for practice owners and billing managers.
Key takeaways
- The Security Rule update was proposed on December 27, 2024 and published January 6, 2025. We found no final rule as of October 2026.
- The existing Security Rule is fully in force, including the risk analysis duty.
- Proposed items include MFA, encryption at rest, a 72-hour restore plan and annual audits.
- HIPAA penalties are tiered and adjusted yearly; the old “$1.5 million per violation” line is not accurate.
- Billing-side checks on logins, vendors and backups are worth doing now.
Where the HIPAA Security Rule update stands today
The update is still a proposal. OCR issued the notice of proposed rulemaking on December 27, 2024, and it was published in the Federal Register on January 6, 2025 (Volume 90, pages 898 to 1022, RIN 0945-AA22). Comments closed on March 7, 2025. As of mid-October 2026, we found no final rule in the sources we checked, and HHS says that the current Security Rule remains in effect while rulemaking continues. See the Federal Register notice and the HHS fact sheet.
Timing is the part that keeps moving. The HHS regulatory initiatives page lists only the proposal. Law-firm and trade-press reports from July 2026 say the regulatory agenda now points to a final rule around July 2027, later than an earlier May 2026 target (HIPAA Journal, Alston and Bird). Those are secondary reports, so treat the date as a target and not a promise.

If a final rule is published, the proposal says it would take effect 60 days later, and regulated entities would have 180 days after that effective date to comply. That is roughly eight months from publication, and the final text could differ from the proposal. A separate transition period was proposed for updating business associate agreements (Federal Register text).
Do not treat proposed requirements as current law
Multi-factor authentication, mandatory encryption at rest and the other changes below are proposals. They are not enforceable as new rules today. The existing Security Rule, including its risk analysis duty, is enforceable now.
What the Security Rule already requires
The rule in force today already asks practices and their business associates to protect electronic protected health information (ePHI) through administrative, physical and technical safeguards. HHS’s summary of the Security Rule lists the core duties, and several of them touch billing directly.
- Risk analysis and risk management. An accurate and thorough assessment of risks to ePHI, followed by steps to reduce those risks to a reasonable and appropriate level.
- Access control and authentication. Only authorized people may reach ePHI, and the system must verify that a person is who they claim to be. Role limits should match each job.
- Audit controls. Systems must record and let you examine activity, which matters when you need to know who opened or changed a claim.
- Transmission security. Technical measures against unauthorized access to ePHI sent over a network, such as claim files going to a clearinghouse.
- Contingency planning. Backups, recovery and emergency operations, so billing can continue after an outage or attack.
- Business associate contracts. Written assurances before a vendor handles ePHI, with the vendor liable directly for Security Rule violations.
- Documentation. Required policies and records are kept for six years.
The current rule also separates “required” from “addressable” implementation specifications. For an addressable item, the entity decides whether it is reasonable and appropriate. If it is, the item must be implemented. If not, the entity documents why and adopts an equivalent measure where one is reasonable. That flexibility is one of the things the proposal would narrow.
“A written policy that nobody follows protects no one. The login that can open a claim is where the risk analysis should start.”
What the proposed update would change
The proposal would turn much of today’s flexible, risk-based approach into specific mandatory controls. These items come from the HHS fact sheet; the final rule could add, drop or reword any of them.
| Topic | In force today | Proposed in the NPRM |
|---|---|---|
| Multi-factor authentication | Authentication standard; no stated MFA mandate in HHS’s summary | Required, with limited exceptions |
| Encryption | Transmission security standard; HHS’s summary does not state an encryption mandate | ePHI encrypted at rest and in transit, with limited exceptions |
| Addressable vs required | Some specifications are addressable | Optional category removed; nearly all specifications become mandatory |
| Asset inventory and network map | Not specifically required | Technology asset inventory and ePHI data-flow map, reviewed at least every 12 months |
| Restoring systems | Contingency plan with backups and recovery | Written procedures to restore certain systems and data within 72 hours |
| Compliance audit | Periodic evaluation | Compliance audit at least every 12 months |
| Vulnerability scans and penetration tests | Not specifically required | Scans every 6 months and penetration tests every 12 months |
| Business associates | Business associate agreement with written assurances | Annual written verification of technical safeguards, and notice to the covered entity within 24 hours of activating a contingency plan |
Source: HHS OCR, HIPAA Security Rule NPRM fact sheet (December 2024) and Summary of the HIPAA Security Rule.
What it means for billing and the revenue cycle
A security incident is a billing problem first. If staff cannot open the practice management system, claims do not go out, remittances cannot be posted and follow-up stops. The proposal’s 72-hour restoration idea is, in practice, a question about how long your billing can stand still.
The billing data path is wide. Patient demographics, insurance details and diagnosis and procedure codes move between your EHR, your billing team, a clearinghouse and payer portals. Each hop is a place where access, encryption and logging matter. Our guides on how clearinghouses manage medical claims and HIPAA compliance in medical billing cover the workflow detail.
Where practices usually have gaps
- Shared logins on payer portals or billing software, so the audit trail cannot say who did what.
- Former staff, temps or remote billers whose access was never removed.
- Claim exports and remittance files saved on desktops, in email or on personal drives.
- A billing vendor with ePHI access but no current business associate agreement or security review on file.
- Backups that exist but have never been tested for restoring billing data.
- Front-desk habits that expose ePHI, such as voicemail and video-call practices. See our front-desk HIPAA guidelines and HIPAA-compliant voicemail guide.

What non-compliance can cost under today's penalty rules
HIPAA civil money penalties are tiered by the level of culpability, and the dollar amounts are adjusted for inflation each year. The older figure of “$1.5 million per violation” is not accurate as a general statement. The 2026 Federal Register inflation adjustment sets these amounts for 45 CFR 160.404 (Federal Register, January 28, 2026).
| Tier | Minimum per violation | Maximum per violation | Calendar-year cap, identical violations |
|---|---|---|---|
| Did not know | $145 | $73,011 | $2,190,294 |
| Reasonable cause, not willful neglect | $1,461 | $73,011 | $2,190,294 |
| Willful neglect, corrected within 30 days | $14,602 | $73,011 | $2,190,294 |
| Willful neglect, not corrected within 30 days | $73,011 | $2,190,294 | $2,190,294 |
Source: HHS, Annual Civil Monetary Penalties Inflation Adjustment, 91 Fed. Reg. (January 28, 2026). Amounts apply to penalties assessed on or after that date for violations on or after November 2, 2015.
These are maximums set in rule, not what a typical practice pays, and they do not include breach notification costs, lost billing days or state law exposure. They do show why a documented risk analysis matters. In an April 25, 2025 settlement announcement, OCR described its Risk Analysis Initiative and said it found the organization “failed to conduct an accurate and thorough risk analysis” (HHS OCR press release).
A practical plan for billing operations before any final rule
Do the work that is required now and that would also satisfy most of the proposal. It costs little to start, and nothing here depends on the final text. Our HIPAA compliance checklist for medical practices gives the full practice-wide list. Use the table below for the billing side.
| Area | Check this | Ties to |
|---|---|---|
| Risk analysis | Is there a current, written analysis that includes billing software, clearinghouse, payer portals and exports? | Required today |
| Logins | Does every biller have a unique login, and is multi-factor sign-in turned on wherever the system offers it? | Authentication today; MFA is proposed |
| Roles | Can each user reach only the claims and screens their job needs? | Access control today |
| Offboarding | Is access removed the day someone leaves, including payer portals? | Access control today |
| Data flow | Do you have a list of systems that hold ePHI and a simple map of how claims move? | Proposed asset inventory and map |
| Backups | Has anyone restored billing data from backup and timed it? | Contingency plan today; 72 hours proposed |
| Vendors | Is there a signed business associate agreement and a recent security review for every vendor that touches ePHI? | Required today; annual verification proposed |
Want a second look at your billing workflow?
Our free practice audit reviews how claims, denials and follow-up flow through your practice, so you can see where access and handoffs create risk.
Questions to ask billing vendors and software providers
Any vendor that creates, receives, maintains or transmits ePHI on your behalf is a business associate. Ask the questions below in writing and keep the answers with your risk analysis. Our guide to choosing a medical billing company covers the commercial side.
- Will you sign a Business Associate Agreement before accessing any patient data, and how do you handle subcontractors?
- Which staff can see our claims, and are logins individual with multi-factor sign-in?
- Is there an audit log that shows who viewed or changed a claim, and can we see it?
- How is data encrypted in transit and at rest?
- How and how often do you test backups, and how fast can you restore?
- How do you notify us of a security incident, and how quickly?
Be careful with phrases such as “HIPAA certified.” Judge a vendor by its written answers and contract terms, not by a badge. If you are weighing outsourced billing, our medical billing services and revenue cycle management pages describe what we offer, and the free audit is the place to start.
A system built for billing can help with the access side. A practice management system that tracks claims by stage should offer role-based permissions and an audit log, so that each claim has a named owner and a record of who touched it. Specialty practices with unusual billing flows can start from our specialty billing pages.
How to track the rule without chasing every headline
Rely on primary sources. Check the HHS OCR HIPAA regulatory initiatives page and the Federal Register entry for RIN 0945-AA22 (the rule’s docket number). A final rule will appear in the Federal Register with an effective date and a compliance date. Until then, headlines that say a requirement is “now in effect” should be read as claims to verify.
Set a calendar reminder to review the status every quarter, and update your risk analysis whenever you add a system, vendor or remote billing arrangement. Keep a short note of what you checked and when. That record is useful whatever the final rule says.
Our recommendations
- Run or refresh your risk analysis. Include billing software, the clearinghouse, payer portals and anywhere claim files are exported. Date it, sign it and store it with your policies.
- Remove shared logins. Give every biller a unique login and turn on multi-factor sign-in wherever a system offers it. This is good practice now and would match the proposal.
- Tighten roles and offboarding. Limit each user to the screens and claims their job needs, and remove access the day someone leaves.
- Map where ePHI lives. List each system and file location that holds patient and claim data, and sketch how data moves between them.
- Test a billing restore. Restore a copy of billing data from backup, time it and write down the gaps. The 72-hour idea is a useful benchmark even before it is a rule.
- Collect vendor assurances in writing. Confirm a signed Business Associate Agreement and ask the security questions above for every vendor that touches ePHI.
Give every claim an owner and a record of who touched it.
Our portal tracks claims by stage with an assigned owner, with role-based permissions and an audit log. It supports good access practice, but it does not replace your risk analysis.
See how the RCM Finder portal works · Create a portal account
Disclosure: RCM Finder builds and sells this portal. It is a practice management system, not an EHR.
Bottom line
The HIPAA Security Rule update may tighten requirements, but your obligations already exist and billing is where much ePHI moves. Start with a risk analysis, unique logins and vendor assurances. If you want a second reader on how claims flow through your practice, see our revenue cycle management service and ask for the free audit.
Frequently asked questions
Is the proposed HIPAA Security Rule update final?
No. As of October 2026 we found no final rule in the sources we checked. HHS published the proposal on January 6, 2025, comments closed March 7, 2025, and HHS says the current Security Rule remains in effect. Reports from July 2026 point to a possible final rule around July 2027, which is a target only.
Is multi-factor authentication required under HIPAA right now?
HHS’s summary of the current rule does not name a multi-factor mandate. The January 2025 proposal would require it with limited exceptions. The current rule does require authentication and access controls, so using multi-factor sign-in is sensible now, but check your own risk analysis.
When would practices have to comply if the rule is finalized?
The proposal says a final rule would take effect 60 days after publication, with compliance 180 days after the effective date, plus a separate transition for business associate agreements. That is about eight months from publication. The final text could change those periods.
What is the maximum HIPAA penalty?
It depends on the tier and the year. Under the January 28, 2026 inflation adjustment, per-violation amounts run from $145 to $73,011 for the first three tiers, up to $2,190,294 for willful neglect not corrected within 30 days, with a $2,190,294 calendar-year cap for identical violations.
Does a small practice need to do anything before a final rule?
Yes. The risk analysis, access control, audit control, contingency plan and business associate agreement duties apply to practices of every size today. Starting with the billing-side checks in this article also puts you closer to the proposal if it is finalized.
Does my billing company have to follow the Security Rule?
Yes. A billing company that handles ePHI for you is a business associate and is directly liable for Security Rule violations. You still need a written business associate agreement and should ask about its safeguards.
Get your free practice audit
Tell us about your practice. We will contact you using the details you give.
- A review of your recent claims, denials and A/R aging
- Where your front desk and prior authorizations slow payment
- A prioritized fix list you keep, whether or not you hire us
Pricing is quoted after the audit, based on your volume and the services you choose. Prefer to talk? Call +1 (302) 556-2288.
Sources
- HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (NPRM) — HHS OCR via Federal Register (2025)
- HIPAA Security Rule NPRM fact sheet — HHS OCR (2024)
- Summary of the HIPAA Security Rule — HHS OCR (2026 (accessed 2026-10-17))
- HIPAA regulatory initiatives — HHS OCR (2025)
- Annual Civil Monetary Penalties Inflation Adjustment — HHS via Federal Register (2026)
- OCR Risk Analysis Initiative settlement announcement — HHS Press Room (2025)
- Final Rule Implementing HIPAA Security Rule Updates Edges Closer — HIPAA Journal (secondary) (2026)
- HHS delays HIPAA Security Rule to 2027 — Alston and Bird (secondary) (2026)
Disclaimer: This article is educational and is not legal or compliance advice. The proposed rule may change before it is finalized, and requirements and penalty amounts are updated over time. Check current HHS, Federal Register and legal counsel guidance for your situation.