DisclosureLens
HHS OCRState AGConfirmed6 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 6 filings

Valley Anesthesiology Consultants, Inc. — March 2016 breach

Clustered 6 filings across 6 jurisdictions · filed Aug 12, 2016. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 filings

States

6

Affected · reported

882,590

First → last filing

Aug 12, 2016

Merge confidence

100%

incident inc_c6e6e9bdbbe14323 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Mar 30, 2016, discovered Mar 30, 2016 — the first regulatory filing landed 135 days later (flagged late). 882,590 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
135days

Discovered → first regulatory filing

Discovery variance
75days

Range of discovered_at dates across filings

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon OR AG >45dHIPAA HHS report lateFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Mar 30, 2016breach begins
Mar 30, 2016discovered · members disagree
notification delay · 135 days
Aug 12, 2016first filing
watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 12OR AGOR AG noticefirst filing · states nationwide total 882,590day 0
  2. AUG 12MT AGMT AG notice586 MT residentsday 0
  3. AUG 12CA AGCA AG noticeno count statedday 0
  4. AUG 12MA AGMA AG notice71 MA residentsday 0
  5. AUG 12WA AGWA AG notice611 WA residentsday 0
  6. AUG 12HHS OCRHHS OCR noticemost recent · states nationwide total 882,590day 0
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 30, 2016
OR AG
Discovered
Mar 30, 2016HHS OCRJun 13, 2016OR AG + MT AG + CA AG +1filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI
MT AG + CA AG + WA AG +2
Attack vector
Unauthorized Access
MT 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)

882,590

Sum of filed state slices

1,268· 0.1% of stated

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

US882,590
WA611
MT586
MA71

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

0 days

Cadence

~1 / 0d

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