DisclosureLens
HHS OCRState AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 5 filings

Pediatric Home Respiratory Services, LLC — November 2024 breach

Clustered 5 filings across 5 jurisdictions · filing window Jan 6, 2025 → Jan 7, 2025 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

42,967

First → last dated filing

Jan 6, 2025 → Jan 7, 2025

Merge confidence

100%

incident inc_a15613bfd96940b3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Nov 1, 2024–Nov 8, 2024, discovered Nov 1, 2024. 42,967 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
6days

Range of discovered_at dates across filings

Filing span
1days

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

Incident timeline

Nov 1, 2024breach begins
Nov 1, 2024discovered · members disagree
Jan 6, 2025first dated filing
Jan 7, 2025most recent dated filing

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 about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 6HHS OCRHHS OCR noticefirst filing · states nationwide total 41,792day 0
  3. JAN 7MA AGMA AG notice1 MA residents+1d
  4. JAN 7IN AGIN AG noticestates nationwide total 42,967+1d
  5. JAN 7MT AGMT AG noticemost recent · 14 MT residents+1d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 1, 2024
IN AG
Discovered
Nov 1, 2024IL AGNov 7, 2024MT AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · PHI
HHS OCR + MA AG + MT AG
Attack vector
Unauthorized Access
HHS OCR

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)

42,967

Sum of filed state slices

17· 0.0% of stated

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

US42,967
MT14
IN2
MA1

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

1 days

Cadence

~1 / 0.3d

vs. multi-state median

6.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.