DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
HHS OCRConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 2 filings

Philips Respironics

Clustered 2 filings across 1 jurisdiction · filed Apr 16, 2024. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge80%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

5,576

First → last filing

Apr 16, 2024

Merge confidence

80%

incident inc_e12a12d353b84fc6 · merged by llm · confidence 80%

Confirmed breach. One breach, 2 legal records. 5,576 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Incident timeline

? — ?breach window unknown
Apr 16, 2024first filing
—watching for filings

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

  1. APR 16HHS OCRHHS OCR noticefirst filing · states nationwide total 1,338day 0
  2. APR 16HHS OCRHHS OCR noticemost recent · states nationwide total 5,576day 0
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
—
Data types
PHI · Health (basic) · Identity (basic)
HHS OCR
Attack vector
Unauthorized Access
HHS OCR
Response
Notified HHS · Notified affected individuals · Notified the media
HHS OCR

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

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 filing2 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
llm
Confidence
0.80 · below the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (80% 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

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.