Enforced5 filings · 4 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 5 filings

Inmediata Health Group — May 2016 breach

Clustered 5 filings across 4 jurisdictions · filing window Apr 30, 2019 → Dec 10, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Enforced

Members

5 filings

States

Affected · reported

1,565,338

First → last filing

Apr 30, 2019 → Dec 10, 2024

Merge confidence

100%

incident inc_21d7fde2519640e6 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe an accidental exposure. Intrusion May 1, 2016–Jan 31, 2019, discovered Jan 1, 2018 — the first regulatory filing landed 484 days later (flagged late). 1,565,338 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 2051-day schedule across 5 filings beginning Apr 30, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

484days

Discovered → first regulatory filing

Discovery variance

365days

Range of discovered_at dates across filings

Filing span

2051days

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 clocksCalifornia✗ CA 60-day late · 111dHIPAA✗ HHS report lateOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 1, 2016breach begins

Jan 1, 2018discovered · members disagree

notification delay · 484 days

Apr 30, 2019first filing

Dec 10, 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

APR 30CA AGCA AG noticefirst filing · no count statedauto-linkedday 0
APR 30MT AGMT AG notice983 MT residentsday 0
MAY 7HHS OCRHHS OCR noticestates nationwide total 1,565,338operator-confirmed+7d
JUN 3OR AGOR AG noticeno count statedauto-linked+34d
DEC 10HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+2051d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jan 22, 2019
Discovered: Jan 1, 2018HHS OCRJan 1, 2019CA AG + MT AG + OR AGfilings disagree on discovery
Data types: Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Misconfiguration

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)

1,565,338

Sum of filed state slices

983· 0.1% 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 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: human
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Sep 6, 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

2051 days

Cadence

~1 / 512.8d

vs. multi-state median

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