Colorado Department of Health Care Policy and Financing — May 2023 breach
Clustered 19 filings across 9 jurisdictions · filing window Aug 1, 2023 → Feb 20, 2024. View entity profile → Other incidents for this victim →
incident inc_046df6a8bc49460c · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
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.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- AUG 1NH AGNH AG noticefirst filing · 726 NH residentsauto-linkedday 0
- AUG 11ME AGME AG noticestates nationwide total 4,091,794operator-confirmed+10d
- AUG 11VT AGVT AG noticeno count statedauto-linked+10d
- AUG 11CA AGCA AG noticeno count statedoperator-confirmed+10d
- AUG 11MA AGMA AG notice1,655 MA residentsauto-linked+10d
- AUG 11DE AGDE AG notice324 DE residentsauto-linked+10d
- AUG 11HHS OCRHHS OCR noticestates nationwide total 4,091,794auto-linked+10d
- AUG 14SC AGSC AG notice3,683 SC residentsauto-linked+13d
- OCT 3CA AGCA AG noticeno count statedauto-linked+63d
- OCT 3ME AGME AG noticestates nationwide total 4,187,732operator-confirmed+63d
- OCT 3VT AGVT AG noticeno count statedauto-linked+63d
- OCT 3NH AGNH AG noticeno count statedoperator-confirmed+63d
- OCT 3DE AGDE AG noticeno count statedoperator-confirmed+63d
- FEB 19ME AGME AG noticestates nationwide total 4,662,668operator-confirmed+202d
- FEB 19OR AGOR AG noticestates nationwide total 4,662,668operator-confirmed+202d
- FEB 19CA AGCA AG noticeno count statedoperator-confirmed+202d
- FEB 19DE AGDE AG noticeno count statedoperator-confirmed+202d
- FEB 19VT AGVT AG noticeno count statedoperator-confirmed+202d
- FEB 20NH AGNH AG noticemost recent · 410 NH residentsoperator-confirmed+203d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- May 28, 2023 NH AG
- Discovered
- May 31, 2023DE AG + CA AGJun 13, 2023NH AG + ME AG + VT AG +3filings disagree on discovery
- Data types
- Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII NH AG + VT AG + CA AG +5
- Attack vector
- Third-Party / Supply Chain 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)
4,662,668
Sum of filed state slices
7,478· 0.2% of stated
100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
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
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Aug 10, 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
203 days
Cadence
~1 / 11.3d
vs. multi-state median
22.6× 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.