DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 8 filings

Morris Hospital & Healthcare Centers — April 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Aug 17, 2023 → Aug 23, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

256,568

First → last filing

Aug 17, 2023 → Aug 23, 2023

Merge confidence

100%

incident inc_8c7082aa72254651 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Apr 4, 2023, discovered Apr 4, 2023 — the first regulatory filing landed 135 days later (flagged late). 256,568 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 4 more. Notifications rolled out on a 6-day schedule across 8 filings beginning Aug 17, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
135days

Discovered → first regulatory filing

Discovery variance
77days

Range of discovered_at dates across filings

Filing span
6days

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; no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 60-day late · 135dVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 58dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Apr 4, 2023breach begins
Apr 4, 2023discovered · members disagree
notification delay · 135 days
Aug 17, 2023first filing
Aug 23, 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. AUG 17MA AGMA AG noticefirst filing · 50 MA residentsday 0
  2. AUG 17CA AGCA AG noticeno count statedday 0
  3. AUG 17VT AGVT AG noticeno count statedday 0
  4. AUG 17MT AGMT AG notice61 MT residentsday 0
  5. AUG 17HHS OCRHHS OCR noticestates nationwide total 256,568day 0
  6. AUG 17IN AGIN AG noticestates nationwide total 24,894day 0
  7. AUG 17ME AGME AG noticestates nationwide total 248,943day 0
  8. AUG 23NH AGNH AG noticemost recent · 37 NH residents+6d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 4, 2023
CA AG
Discovered
Apr 4, 2023CA AG + VT AG + MT AG +1Jun 20, 2023ME AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI
MA AG + CA AG + VT AG +4
Attack vector
Unauthorized Access
CA 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)

256,568

Sum of filed state slices

1,839· 0.7% of stated

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

US256,568
IN1,666
MT61
MA50
NH37
ME25

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 filing8 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

6 days

Cadence

~1 / 0.9d

vs. multi-state median

1.3× faster

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.