Health system cybersecurity rules after the HIPAA proposal: the 2027 outlook

The HIPAA Security Rule rewrite is still a proposal, now aimed at July 2027. Until it lands, health systems answer to OCR enforcement, New York's hospital rule, device rules and a CIRCIA rule that is overdue.

US health systems are still waiting to learn whether HIPAA's flexible security standard will become a list of named controls. As checked on November 16, 2026, that decision is still pending: the proposed rewrite of the HIPAA Security Rule has not been finalized, and its target date has moved into the second half of 2027 [4]. Meanwhile New York has its own hospital rule, device makers have premarket duties, CISA's reporting rule is overdue, and OCR keeps settling cases built on a missing risk analysis. Below is where each stands and what to plan around through 2027.

Where the HIPAA Security Rule proposal stands

HHS's Office for Civil Rights (OCR) published the proposed rule, "HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information" (90 FR 898, RIN 0945-AA22), on January 6, 2025 [1]. Comments closed on March 7, 2025 [2]. As checked on November 16, 2026, the Federal Register lists one document under that regulation identifier, the proposed rule itself, so no final rule, withdrawal or revised proposal had been published [3].

The regulatory agenda shows the slippage. The Spring 2025 Unified Agenda placed the rule at the final rule stage, with final action shown for May 2026 [5]. The 2026 agenda moved it to "Long-Term Actions", marked it economically significant and major, and shows final action for July 2027 [4]. A long-term entry is a plan, not a commitment; until a final rule takes effect, OCR enforces the current rule.

What the proposal would change

Its central move is to remove the distinction between "required" and "addressable" implementation specifications; HHS argued this would mark where the floor of protection sits without removing all of the rule's flexibility [1].

The named obligations include encryption of ePHI with limited exceptions, multi-factor authentication for access to relevant electronic information systems, a written technology asset inventory and network map reviewed at least once every 12 months, written procedures to restore critical systems and data within 72 hours of a loss, patching of critical risks within 15 calendar days where a patch is available, and penetration testing at least once every 12 months or as the risk analysis requires [1]. Covered entities would assess business associates using written verification from them, and business associates would report activation of their contingency plans within 24 hours [1]. HHS proposed the standard compliance period of 180 days after a final rule's effective date, and estimated first-year costs at about $9 billion, with about $6 billion a year in years two through five [1].

Cybersecurity rules facing US health systems, as checked on November 16, 2026
RuleWho it reachesStatus
HIPAA Security Rule update (RIN 0945-AA22)Covered entities and business associates [1]Proposed January 6, 2025; long-term action, final action shown for July 2027 [4]
HHS cybersecurity performance goalsHealth care and public health organizations [6]Voluntary [6]
CMS Promoting Interoperability security risk analysis measureEligible hospitals and critical access hospitals [9]Security risk management attestation added from the CY 2026 EHR reporting period [9]
CMS resiliency request for informationHealth care organizations, including hospitals, plans and clearinghouses [8]Questions only; comments were due June 15, 2026 [8]
FD&C Act section 524BSponsors of premarket submissions for cyber devices [10]In force since 90 days after December 29, 2022 [10]
CIRCIA reporting ruleProposed: hospitals with 100 or more beds, critical access hospitals, certain drug and device makers [13]Final rule shown for September 2026, not published [15] [14]
New York 10 NYCRR 405.46 [16]General hospitals in New York [16]Effective October 2, 2024; one year to comply, 72-hour reporting on adoption [16]

Moraph's view

We expect the final Security Rule to arrive later than July 2027 and to be narrower than the proposal. The agenda date has already slipped by more than a year, the entry has moved from the final rule stage to long-term actions, and HHS's own estimate put first-year costs at about $9 billion. Asset inventories, multi-factor authentication, encryption and documented risk management are the likeliest to survive. The fixed 72-hour restoration standard and the business associate verification duty are the ones we expect to be loosened, phased or dropped. Planning to the proposal's text costs little if the final rule is softer; waiting leaves, under the proposal, 180 days to do the work.

The voluntary goals the proposal draws on

HHS describes its health care and public health cybersecurity performance goals (CPGs) as "a voluntary subset of cybersecurity practices", split into 10 essential goals and 10 enhanced goals [6]. The essential goals include mitigating known vulnerabilities, email security, multifactor authentication, strong encryption and vendor cybersecurity requirements; the enhanced goals include asset inventory, network segmentation and centralized log collection [6]. The proposed Security Rule points to them directly: HHS said its proposed patching standard aligns with the enhanced goal on cybersecurity mitigation [1].

HHS's health sector cybersecurity strategy set out a route from voluntary to binding goals. It said HHS would seek new authority and funding from Congress to support hospital investment and, in the long term, to impose financial consequences on hospitals; that CMS would propose new cybersecurity requirements for hospitals through Medicare and Medicaid; and that OCR would begin a Security Rule update in spring 2024 [7].

CMS: questions and attestations, not conditions

The CMS part of that plan has not appeared as a proposed condition of participation. As checked on November 16, 2026, a Federal Register search for CMS documents since January 1, 2024 that cite 42 CFR part 482 and mention cybersecurity returns only the FY 2025 IPPS proposed and final rules, whose cybersecurity discussion concerns the Promoting Interoperability Program, not the conditions of participation [21]. What CMS has done is narrower. The FY 2026 IPPS final rule, effective October 1, 2025, requires eligible hospitals and critical access hospitals in the Medicare Promoting Interoperability Program to attest "yes" to having conducted security risk management, as well as security risk analysis, beginning with the EHR reporting period in CY 2026 [9].

In its April 14, 2026 proposed rule on interoperability standards and prior authorization for drugs (CMS-0062-P), CMS included a request for information titled "Increasing Health Care Resiliency" [8]. It asked whether CMS should make effective cybersecurity practices regulatory requirements, how clearinghouse enrollment affects resilience, how to switch clearinghouses when one is attacked, and what barriers small and rural providers face [8]. Comments were due June 15, 2026 [8].

Medical devices: section 524B is already law

Section 524B of the Federal Food, Drug, and Cosmetic Act took effect 90 days after its enactment on December 29, 2022 [10]. Sponsors of premarket submissions for a "cyber device" (software, internet connectivity, characteristics that could be vulnerable) must submit a postmarket vulnerability plan with coordinated disclosure, maintain secure development and patching processes, and provide a software bill of materials [10]. FDA's final guidance, current as of February 3, 2026, supersedes the version issued June 27, 2025 and sets out FDA's recommendations on section 524B [11]. The duty falls on manufacturers, but hospitals can ask for the resulting software bill of materials and vulnerability plan in purchasing contracts.

CIRCIA: a second federal reporting clock, still waiting

CIRCIA requires covered entities to report covered cyber incidents to CISA within 72 hours and ransom payments within 24 hours [13], but reports are not required until CISA's final rule takes effect [12]. CISA's proposed rule of April 4, 2024 would reach the health sector through entities that own or operate a hospital with 100 or more beds or a critical access hospital, manufacture listed essential drugs, or manufacture Class II or Class III devices [13].

The 2026 Unified Agenda showed the final rule for September 2026 [15]. As checked on November 16, 2026, the Federal Register lists only the proposed rule, a comment period extension and a correction under the rule's identifier [14]. CISA's page says it continues to work on the final rule, that multiple funding lapses affected its rulemaking, and that it held four town hall meetings between June 15 and June 18, 2026 [12].

Enforcement is moving faster than rulemaking

OCR does not need the new rule to bring cases. On June 18, 2026, OCR said its settlement with the Spencer Gifts employee health plan was its 20th ransomware enforcement action and the 14th in its Risk Analysis Initiative; the plan paid $450,000 and agreed to a two-year corrective action plan [18]. On October 29, 2026, OCR announced a settlement with Lehigh Valley Health Network that it called its 22nd ransomware enforcement action; the health system paid $800,000 and agreed to a three-year corrective action plan [19]. OCR's list of potential violations began with failing to conduct an accurate and thorough risk analysis and failing to review information system activity records [19]. Both cases rest on the current rule's risk analysis standard, which CMS also cites in its Promoting Interoperability measure [9].

Moraph's view

OCR's settlements are the best guide to what a health system will be asked for in 2027. The cases settle older breaches under the current rule, and they open with the risk analysis. Between the two releases above, OCR moved from its 20th to its 22nd ransomware action in about four months. We expect that pace of several a year to continue whatever happens to the rulemaking. The risk records a hospital attests to for CMS are the records OCR will read after a breach.

New York has already written its own rule

New York's Department of Health adopted 10 NYCRR 405.46, Hospital Cybersecurity Requirements, for all general hospitals, effective October 2, 2024 [16]. Hospitals had one year from the effective date to comply, except that the duty to notify the department as promptly as possible and no later than 72 hours after determining that a cybersecurity incident occurred took effect on adoption [16]. The rule requires, among other things, a cybersecurity program, risk-based policies, a designated Chief Information Security Officer, testing, third-party service provider policies, identity and access management and an incident response plan [16]. The department estimated initial program costs of $250,000 to $10 million, and ongoing annual costs from $50,000 to $200,000 for small hospitals up to about $2 million for large ones [16]. It has published a mapping of the rule to NIST frameworks and the Health Industry Cybersecurity Practices [17].

Moraph's view

New York is the closest preview of a final federal rule. Its hospitals already run a named security officer, risk-based policies, third-party controls and a 72-hour state reporting clock. If the HIPAA rule is finalized close to the proposal, a New York hospital starts with a smaller gap than a peer in a state without such a rule. For a multi-state system, a map of its New York controls against the federal proposal is a ready-made gap analysis for the day a final rule appears.

What Change Healthcare changed, on the record

In its frequently asked questions on the Change Healthcare attack, OCR said it opened investigations of Change Healthcare and UnitedHealth Group because of the attack's unprecedented impact on patient care and privacy, and that its interest in their partners was secondary, and reminded those partners of their business associate agreement and breach notification duties [20]. On July 31, 2025, Change Healthcare notified OCR that approximately 192.7 million individuals had been affected [20]. The CMS request for information does not name Change Healthcare, but its clearinghouse questions address the same dependence on one intermediary [8]. Neither document is a rule: in official sources, the policy aftermath so far is investigation and inquiry, not new obligations.

What this means for you

  • Hospitals and health systems: Use the proposal's named controls as the planning baseline rather than waiting for final text, since the proposal would allow 180 days after a final rule's effective date [1]. Keep the risk analysis and risk management records current and specific: CMS requires attestations to both [9], and OCR's ransomware settlements open with the risk analysis [19].
  • Small and rural providers: Start with the 10 essential performance goals, which HHS published as voluntary [6]. CMS has asked what barriers small and rural providers face [8], and HHS's strategy tied upfront funding for low-resourced hospitals to new authority from Congress [7], so plan without counting on that money.
  • Business associates: Expect covered entities to ask for written verification of safeguards, and prepare to report contingency plan activation within 24 hours, as the proposal would require [1]. OCR's Change Healthcare guidance reminded partners of business associate agreement and breach notification duties [20]; clearinghouses should also watch the CMS resiliency questions [8].
  • Medical device makers: Section 524B already requires a postmarket vulnerability plan, secure processes and a software bill of materials for cyber devices [10], and FDA's February 2026 guidance sets out what to submit [11]. Makers of Class II and Class III devices would also be covered by CISA's proposed CIRCIA rule [13].
  • Compliance officers at New York hospitals: Map incident triggers across the state's 72-hour report to the Department of Health [16], HIPAA breach notification, and CIRCIA's 72-hour and 24-hour reports once that rule takes effect [13] [12], so one incident does not miss a clock.

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 70% Open

    HHS will not publish a final HIPAA Security Rule under RIN 0945-AA22 in the Federal Register on or before July 31, 2027.

    How we will check: A Federal Register search for RIN 0945-AA22 shows no document of type Rule published on or before July 31, 2027.

    Basis: The rule's final action date moved from May 2026 in the Spring 2025 agenda [5] to July 2027 in the 2026 agenda, where it is listed as a long-term action [4]; the only document under the RIN is the proposed rule [3].

  2. P2 By Confidence 55% Open

    CISA will publish the CIRCIA final reporting rule in the Federal Register on or before December 31, 2027.

    How we will check: A Federal Register search for RIN 1670-AA04 shows a document of type Rule published on or before December 31, 2027.

    Basis: The rule was at the final rule stage with a September 2026 date in the 2026 agenda, a date that has passed, [15]; CISA says it continues to work on it after town halls in June 2026 [12]; no final rule had been published as of November 16, 2026 [14].

  3. P3 By Confidence 75% Open

    CMS will not publish a proposed or final rule adding cybersecurity requirements to the hospital conditions of participation (42 CFR part 482) on or before December 31, 2027.

    How we will check: No Federal Register document from CMS published on or before December 31, 2027 proposes or adopts a cybersecurity requirement in 42 CFR part 482.

    Basis: HHS's strategy said CMS would propose hospital cybersecurity requirements and tied enforcement to new authority from Congress [7]; CMS's 2026 step was a request for information, not a proposal [8], and as checked on November 16, 2026 no CMS document amending part 482 had proposed cybersecurity requirements [21].

  4. P4 By Confidence 75% Open

    OCR will announce its 26th or later ransomware enforcement action on or before December 31, 2027.

    How we will check: An OCR press release dated on or before December 31, 2027 describes a settlement or civil money penalty as OCR's 26th or higher-numbered ransomware enforcement action.

    Basis: OCR numbered its 20th ransomware enforcement action on June 18, 2026 [18] and its 22nd on October 29, 2026 [19].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

Spotted an error? Tell us and we will check it and correct the piece where needed.

  • HIPAA Security Rule
  • OCR enforcement
  • CIRCIA
  • FDA section 524B
  • CMS
  • New York 10 NYCRR 405.46
  • hospital cybersecurity
  • Change Healthcare