DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRSEC 8-KState AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

HCA Healthcare Inc. — June 2023 breach

Clustered 11 filings across 11 jurisdictions · filing window Jul 10, 2023 → Aug 31, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

11,270,000

First → last filing

Jul 10, 2023 → Aug 31, 2023

Merge confidence

100%

incident inc_139038c5976d49e2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe hacking. Intrusion Jun 1, 2023–Jul 5, 2023, discovered Jul 5, 2023 — the first regulatory filing landed 5 days later (flagged late). 11,270,000 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 52-day schedule across 11 filings beginning Jul 10, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
5days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
52days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster.

Regulatory clocksOregon✗ OR AG >45dHIPAA✓ HHS notifiedWashington✓ WA AG ≤30dCalifornia✓ CA 60-day OK · 30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 1, 2023breach begins
Jul 5, 2023discovered
notification delay · 5 days
Jul 10, 2023first filing
Aug 31, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 10SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUL 14DE AGDE AG noticeno count stated+4d
  3. JUL 31HHS OCRHHS OCR noticestates nationwide total 11,270,000+21d
  4. AUG 1WA AGWA AG notice7,500 WA residents+22d
  5. AUG 1CA AGCA AG noticeno count stated+22d
  6. AUG 28NH AGNH AG noticeno count stated+49d
  7. AUG 28ID AGID AG noticeno count stated+49d
  8. AUG 29MT AGMT AG notice1,700 MT residents+50d
  9. AUG 29MA AGMA AG notice17,000 MA residents+50d
  10. AUG 30OR AGOR AG noticeno count stated+51d
  11. AUG 31SC AGSC AG noticemost recent · 322,000 SC residents+52d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 1, 2023
DE AG
Discovered
Jul 5, 2023· 34d undetected
DE AG + WA AG + CA AG +5
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
SEC 8-K + DE AG + WA AG +6
Attack vector
Unauthorized Access
DE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

11,270,000

Sum of filed state slices

348,200· 3.1% of stated

97% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US11,270,000
SC322,000
MA17,000
WA7,500
MT1,700

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

52 days

Cadence

~1 / 5.2d

vs. multi-state median

6.5× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.