Children's Hospital Colorado
Clustered 5 records across 3 jurisdictions: 4 filings and 1 enforcement record · filing window Sep 8, 2017 → Jul 27, 2020 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_9193ec7dfde24040 · merged by human · confidence 100%
Litigation Timing
Range of discovered_at dates across filings
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.
Incident timeline
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 enforcement record in this incident
- SEP 8HHS OCRHHS OCR noticefirst filing · states nationwide total 3,370operator-confirmedday 0
- JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- JUL 27HHS OCRHHS OCR noticestates nationwide total 2,553+1053d
- DEC 5HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+2645d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- —
- Discovered
- Jun 22, 2020IL AGJul 22, 2020IL AGfilings disagree on discovery
- Data types
- Health (basic) · Identity (basic) HHS OCR
- Attack vector
- Unauthorized Access 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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 14, 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
1053 days
vs. multi-state median
175.5× 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.