DisclosureLens
All incidentsView linkage analytics →
HHS OCRHHS OCR enforcementState AGEnforced8 filings · 6 statesLifecycle stage 3 of 3: EnforcedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

MedEvolve — March 2018 breach

Clustered 8 filings across 6 jurisdictions · filing window Jul 10, 2018 → May 16, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Enforced

Members

8 filings

States

6

Affected · reported

230,572

First → last filing

Jul 10, 2018 → May 16, 2023

Merge confidence

100%

incident inc_b84a7399bcda4b75 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe a misconfiguration. Intrusion Mar 29, 2018–May 4, 2018, discovered May 11, 2018 — the first regulatory filing landed 60 days later. 230,572 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 1771-day schedule across 8 filings beginning Jul 10, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
51days

Range of discovered_at dates across filings

Filing span
1771days

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 clocksHIPAA✓ HHS report on timeFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 29, 2018breach begins
May 11, 2018discovered · members disagree
notification delay · 60 days
Jul 10, 2018first filing
May 16, 2023most recent filing

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

Member cascade — every filing about this breach

  1. JUL 10MT AGMT AG noticefirst filing · states nationwide total 15day 0
  2. JUL 10HHS OCRHHS OCR noticestates nationwide total 230,572day 0
  3. JUL 10NH AGNH AG notice84 NH residentsday 0
  4. JUL 10CA AGCA AG noticeno count statedday 0
  5. JUL 10MA AGMA AG notice368 MA residentsday 0
  6. JUL 27NH AGNH AG notice91 NH residents+17d
  7. JUL 30MA AGMA AG notice409 MA residents+20d
  8. MAY 16HHS OCR enforcementHHS OCR enforcement noticemost recent · no count stated+1771d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 29, 2018 – May 4, 2018
MT AG
Discovered
May 11, 2018MT AG + NH AG + CA AGJul 1, 2018HHS OCRfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + HHS OCR + NH AG +2
Attack vector
Misconfiguration
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)

230,572

Sum of filed state slices

513· 0.2% of stated

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

US230,572
MA409
NH91
MT13

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 filing8 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 Aug 21, 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

1771 days

Cadence

~1 / 253d

vs. multi-state median

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