DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed11 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcontihigh sensitivity
Merged incident · 11 records

Rehoboth McKinley Christian Health Care Services — January 2021 breach

Clustered 11 records across 10 jurisdictions: 10 filings and 1 leak-site claim · filed May 19, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 records

States

10

Affected · reported

209,280

First → last dated filing

May 19, 2021

Merge confidence

100%

incident inc_15f22ff9e09a47ab · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 21, 2021–Feb 5, 2021, discovered Feb 16, 2021. 209,280 individuals reported across the linked filings. Data reported: Government ID, Financial account, Authentication, and 6 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
92days

Range of discovered_at dates across filings

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Jan 21, 2021breach begins
Feb 16, 2021discovered · members disagree
May 19, 2021first dated filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. FEB 1Leak siteconti postfirst record · attacker claim · unverifiedday 0
  3. MAY 19ME AGME AG noticestates nationwide total 209,280+107d
  4. MAY 19OR AGOR AG noticestates nationwide total 209,280+107d
  5. MAY 19MA AGMA AG notice438 MA residents+107d
  6. MAY 19WA AGWA AG notice1,186 WA residents+107d
  7. MAY 19MT AGMT AG notice386 MT residents+107d
  8. MAY 19IN AGIN AG noticestates nationwide total 209,280+107d
  9. MAY 19HHS OCRHHS OCR noticestates nationwide total 207,195+107d
  10. MAY 19NH AGNH AG notice79 NH residents+107d
  11. MAY 19CA AGCA AG noticemost recent · no count stated+107d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 21, 2021
ME AG
Discovered
Feb 16, 2021WA AG + MT AG + NH AG +1Apr 30, 2021ME AG + OR AGMay 19, 2021IL AGfilings disagree on discovery
Data types
Authentication · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
ME AG + MA AG + WA AG +4
Attack vector
Unauthorized Access
ME 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)

209,280

Sum of filed state slices

2,644· 1.3% of stated

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

US209,280
WA1,186
IN550
MA438
MT386
NH79
ME5

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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 statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

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