DisclosureLens
Leak SiteHHS OCRState AGConfirmed6 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedvicesocietyhigh sensitivity
Merged incident · 6 filings

Barlow Respiratory Hospital — August 2021 breach

Clustered 6 filings across 4 jurisdictions · filing window Dec 30, 2021 Mar 4, 2022. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

6 filings

States

3

Affected · reported

10,761

First → last filing

Dec 30, 2021 Mar 4, 2022

Merge confidence

100%

incident inc_444327b7ce2042be · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 21, 2021–Sep 1, 2021, discovered Aug 27, 2021 — the first regulatory filing landed 125 days later (flagged late). 10,761 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 5 more. Notifications rolled out on a 64-day schedule across 5 filings beginning Dec 30, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
125days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 7d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
64days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksCalifornia CA 60-day late · 189dMassachusetts MA credit monitoring dueHIPAA HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 21, 2021breach begins
Aug 27, 2021discovered
notification delay · 125 days
Dec 30, 2021first filing
Mar 4, 2022most 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. DEC 30MA AGMA AG noticefirst filing · 2 MA residentsday 0
  2. DEC 30NH AGNH AG notice1 NH residentsday 0
  3. DEC 30HHS OCRHHS OCR noticestates nationwide total 10,761day 0
  4. DEC 30CA AGCA AG noticeno count statedday 0
  5. JAN 6Leak sitevicesociety postattacker claim · unverified+7d
  6. MAR 4CA AGCA AG noticemost recent · no count stated+64d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 21, 2021Sep 1, 2021
NH AG
Discovered
Aug 27, 2021· 6d undetected
NH AG + CA AG
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MA AG + NH AG + HHS OCR +1
Attack vector
Unauthorized Access
NH 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)

10,761

Sum of filed state slices

3· 0.0% of stated

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

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 filing5 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 22, 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

64 days

Cadence

~1 / 12.8d

vs. multi-state median

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