All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed4 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 4 filings

Sarah D. Culbertson Memorial Hospital — March 2023 breach

Clustered 4 filings across 3 jurisdictions · filing window Oct 21, 2023 → Jan 4, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

not comparable

First → last filing

Oct 21, 2023 → Jan 4, 2024

Merge confidence

100%

incident inc_23d49ebba9ac493b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Mar 27, 2023–Mar 30, 2023, discovered Mar 30, 2023 — the first regulatory filing landed 205 days later. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 75-day schedule across 4 filings beginning Oct 21, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

205days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

75days

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 clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 27, 2023breach begins

Mar 30, 2023discovered

notification delay · 205 days

Oct 21, 2023first filing

Jan 4, 2024most recent filing

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

Member cascade — every filing about this breach

OCT 21NH AGNH AG noticefirst filing · 2 NH residentsauto-linkedday 0
NOV 21MT AGMT AG notice10 MT residents+31d
NOV 21MA AGMA AG notice14 MA residentsauto-linked+31d
JAN 4NH AGNH AG noticemost recent · 5 NH residentsauto-linked+75d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 27, 2023 – Mar 30, 2023
Discovered: Mar 30, 2023· 3d undetected
Data types: Financial account · Identity (basic) · Government ID · PII
Attack vector: Unauthorized Access

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

Affected residents by state

per-state reported counts

MA14

MT10

NH5

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing4 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
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

75 days

Cadence

~1 / 25d

vs. multi-state median

9.4× 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.