Hale Insights - November 16, 2026

Hale Insights - November 16, 2026

Calendar Icon
November 16, 2026

Good morning everyone,

This week brings movement on HIPAA Privacy Rule changes and an expanded federal and state lawsuit involving digital health privacy. Federal review of the forthcoming Privacy Rule concluded, while healthcare organizations raised concerns about verifying patient-directed disclosures to third-party applications. Five additional states also joined the FTC’s case against Hims & Hers.

The five updates below cover developments announced, filed, or newly reported November 10–16. Our practical focus is on documenting authorized data sharing, monitoring workforce access, keeping breach investigations moving, and verifying that urgent security updates reach the systems people actually use.

Regulatory & Legal Updates

HIPAA Privacy Rule clears federal review as providers raise application-verification concerns (November 10–13, 2026)

What happened: On November 13, the Office of Information and Regulatory Affairs concluded its review of the HIPAA Privacy Rule addressing coordinated care, individual engagement, and regulatory burdens, recording the outcome as “Consistent with Change.” The review record does not provide a publication date or establish a compliance deadline.

Separately, a November 10 letter from CHIME and healthcare organizations urged HHS to preserve reasonable checks confirming that patients authorized third-party applications to receive their PHI. The coalition distinguished identity proofing from matching someone to the correct medical record and confirming the scope of their authorization. These are stakeholder concerns about potential final provisions, rather than confirmation of adopted requirements.

Why it matters: This is a useful preparation point for privacy, health information management, and interoperability teams. Review current workflows now, but base implementation decisions on the published rule’s actual language and applicable dates.

Recommended actions:

  • Assign an owner to monitor publication and prepare a crosswalk of changed requirements, affected workflows, and compliance dates.
  • Document how application requests establish identity, match the patient’s record, and capture the patient’s direction to disclose information.
  • Ask EHR and exchange vendors which verification steps they perform, what evidence they retain, and which decisions remain with your organization.

Sources: OIRA review record · CHIME coalition letter

Five additional states join FTC privacy lawsuit against Hims & Hers (Filed November 10, 2026)

What happened: The FTC filed an amended complaint adding Arizona, Florida, Nebraska, Ohio, and Wisconsin to its existing lawsuit against Hims & Hers. The case alleges that the telehealth company shared sensitive health information with advertising platforms despite privacy assurances and misled consumers about billing and cancellation practices. The additional states join Utah and the State of California, the latter acting through Los Angeles County Counsel.

The amended complaint adds state consumer-protection claims to the existing federal and state claims. The case remains pending; this development is an expanded lawsuit, with allegations still to be decided by the court.

Why it matters: For healthcare and digital health teams, the practical lesson is to review privacy representations alongside actual website, intake, advertising, and subscription workflows. Include marketing and product teams in that review.

Recommended actions:

  • Inventory tracking pixels, analytics tools, and advertising integrations on intake forms and condition-specific pages; test what information they transmit.
  • Compare observed data flows with privacy notices, consent language, vendor agreements, and internal approvals.
  • Walk through enrollment, payment, renewal, and cancellation as a patient would; document unclear disclosures and assign corrective actions.

Sources: FTC announcement · November 10 case filing

Breach & Incident Notices

New Premise Health reporting identifies nearly 417,000 affected people across five states (Reported November 12, 2026)

What happened: November 12 reporting identified nearly 417,000 affected individuals across five state filings concerning Premise Health’s employee-related data incident. The nationwide total remained undisclosed. This week’s development is the additional scope reporting; the company’s individual notices began earlier.

Premise Health says it discovered September 18 that an employee had misappropriated company data beginning around March 26. Potentially affected information includes identifiers, Social Security numbers, insurance information, and diagnostic or treatment details. The company revoked access, terminated the employee, and notified law enforcement. It describes the incident as unrelated to hacking or ransomware and reports no operational interruption.

Why it matters: This incident illustrates why access reviews should examine how authorized users handle information. For organizations contracting with employer-sponsored healthcare providers, the follow-up should also establish which populations, records, and notification responsibilities are involved.

Recommended actions:

  • Review bulk-download, export, printing, and external-transfer permissions for roles handling large patient datasets.
  • Test alerts for unusual access volume or transfers, and confirm that investigators can retrieve the supporting logs.
  • If affected, obtain an organization-specific impact statement and reconcile vendor notices with your own notification and employee-communication responsibilities.

Sources: November 12 scope reporting · Premise Health incident notice

Acadia Healthcare notice details email-related exposure of health and financial information (California filing reported November 13, 2026)

What happened: BreachRecord lists a November 13 California attorney general filing containing Acadia Healthcare’s notice about an email security incident. Acadia’s notice describes unauthorized access and acquisition of files during March 21–25 and on July 13, 2026. The company says its electronic health record systems were not involved and patient care continued without disruption.

Affected information included names and Social Security numbers, with additional information varying by individual, including diagnoses, medications, treatment, insurance, and financial details. Acadia offered one year of credit monitoring and identity protection. The public notice does not state an affected-person total.

Why it matters: The notice is a reminder to include email-held information in risk analysis and incident scoping. An unaffected EHR does not resolve whether sensitive patient information was exposed elsewhere.

Recommended actions:

  • Identify mailboxes and related workflows that routinely retain clinical documents, insurance records, or financial information; reduce unnecessary retention.
  • During investigations, preserve authentication, mailbox-access, forwarding-rule, and file-access evidence across every identified access period.
  • Maintain a chronology connecting discovery, data review, affected-person determinations, and notification decisions; assign privacy and legal review while technical work continues.

Sources: California attorney general filing · Acadia notification · Filing-date record

Cybersecurity & Threat Intelligence

Microsoft addresses actively exploited Outlook vulnerability (Released November 10; Canadian Cyber Centre advisory updated November 12, 2026)

What happened: Microsoft released security updates addressing CVE-2026-124194, an Outlook spoofing vulnerability it identifies as actively exploited. Microsoft explains that opening a specially crafted file in an affected version can cause a connection to an attacker-controlled location and potentially disclose authentication information. Exploitation requires user interaction; Microsoft states that the Preview Pane is not an attack vector.

The Canadian Centre for Cyber Security’s November advisory confirms that CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on November 10 and recommends applying relevant updates.

Why it matters: For healthcare teams, the operational priority is confirming coverage across clinical workstations, administrative devices, remote users, and vendor-managed environments. A deployment report should show which affected installations remain exposed.

Recommended actions:

  • Match Microsoft’s affected-product guidance against your Office inventory, including virtual desktops and infrequently connected devices.
  • Prioritize applicable updates and verify installed versions; assign owners and compensating controls for exceptions.
  • Brief the help desk and workforce on suspicious message files, and have security staff review relevant endpoint and authentication alerts for possible exploitation.

Sources: Microsoft vulnerability advisory · Canadian Centre for Cyber Security advisory

Closing Thoughts

This week’s practical message is to connect compliance decisions with evidence: who authorized a disclosure, what information a vendor receives, how employee activity is monitored, and whether remediation is complete. Use risk analysis to identify gaps, then assign owners, due dates, and verification steps that leadership can review.

For the coming week, prioritize urgent patch exceptions, notification readiness, and oversight of sensitive data outside the EHR. Keep workforce training, access controls, encryption, and vendor commitments tied to documented operating practices. Those records support clear decisions during an incident and a more defensible compliance program afterward.

‍