ePHIJournal · Vol. 01 · The Independent Practice Issue

The Proposed HIPAA Security Rule

What independent practices need to know now: risk analysis, inventories and workforce training.

November 2026 · Regulatory information checked November 3, 2026 · Read the full issue

REGULATORY STATUS | PROPOSED — NOT CURRENT LAW · HHS PLANNED FINAL ACTION: JULY 2027

Current HIPAA rules remain in effect. Check the live HHS agenda and Federal Register for changes before relying on the NPRM details in this dated issue. View official HHS agenda

The January 2025 HIPAA Security Rule proposal would make many cybersecurity expectations more explicit, documented and recurring. For small practices, the question is how to prepare responsibly without treating proposals as current law.

1. Risk analysis: a more detailed record

Today, the Security Rule requires an accurate and thorough analysis of risks to ePHI. The law does not prescribe one universal annual interval for an entirely new SRA. An analysis must remain accurate as the environment changes. OCR’s guidance describes risk analysis as the first step in a continuing management process. The NPRM proposes a more specific written assessment addressing technology inventories, network maps, reasonably anticipated threats, vulnerabilities, likelihood and risk levels. It also proposes review, verification and updating at least every 12 months and when relevant changes occur. That is a recurring review obligation—not necessarily a requirement to buy a brand-new assessment each year.

2. Technology inventory and network map

ePHI does not reside only in the EHR. It may pass through desktops, laptops, billing portals, backup systems, document scanners, secure messaging systems and cloud vendors. The NPRM would require a documented inventory and network map showing relevant systems and ePHI movement, maintained on an ongoing basis and reviewed at least annually. An office manager can begin by asking for a list of systems and vendors that create, receive, maintain or transmit ePHI, who administers them, where backups live and when access was last reviewed.

3. Security awareness training

The current Security Rule requires a workforce security awareness and training program, including management, but no universal annual frequency. Separately, the Privacy Rule requires appropriate workforce training on privacy policies and procedures, including training on relevant policy changes. The proposed Security Rule would require security awareness training generally at least once every 12 months, based on workforce role, with additional timing and change-related requirements. Course completion alone cannot substitute for the practice’s own procedures and responsibilities.

Why this deserves attention now

These proposals do not impose a current compliance deadline. They do, however, reveal the level of documentation, coordination and evidence HHS was considering. Practices that cannot identify their systems, document risks or demonstrate training have an actionable starting point today.

4. Annual compliance audits

The current Security Rule requires periodic technical and nontechnical evaluations. The NPRM would add a documented Security Rule compliance audit at least every 12 months. This is different from an SRA: a risk analysis studies threats and vulnerabilities to ePHI; a compliance audit tests conformity with applicable regulatory requirements.

5. Technical safeguards and testing

The proposal would generally remove the distinction between required and addressable implementation specifications, subject to limited exceptions. It would also make more explicit demands involving multifactor authentication, encryption of ePHI at rest and in transit, network segmentation, configuration controls, vulnerability scanning at least every six months and penetration testing at least annually. Under today’s Rule, an “addressable” specification is not optional. The practice must evaluate it and either implement it or document an appropriate permitted alternative. The future rule could narrow those choices, but no one should describe those proposed specifics as currently mandatory merely because they appear in the NPRM.

6. Incident response and recovery

Current rules already require security incident procedures and contingency planning. The proposal would add more prescribed written procedures, testing and restoration expectations, including restoration of certain critical systems and data within 72 hours following specified loss events. A physician office should already know whom to call if its EHR becomes unavailable, how to preserve evidence, how downtime care proceeds, what backups are available and who assesses notification obligations. Those questions matter whether the rule is amended or not.

A realistic plan for a small practice

  • Review the last documented SRA against the practice’s actual technology and workflows.
  • Inventory systems and vendors that handle ePHI; ask who owns access controls, backup testing and log review.
  • Establish an appropriate workforce training and documentation process.
  • Separate gaps under current law from possible future changes, then prioritize existing obligations first.

The HHS Unified Agenda lists final action planned for July 2027. A final rule could differ materially from the proposal and carry future compliance dates. Preparation should be based on verified present requirements and prudent operational improvements, not an invented countdown.

See also: HIPAA: Today vs. Proposed and ePHIShield’s Security Rule changes reference page.

Scroll to Top