DisclosureLens
All incidentsView linkage analytics →
HHS OCRHHS OCR enforcementState AGEnforced7 records · 5 statesLifecycle stage 3 of 3: EnforcedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 records

Medical Informatics Engineering, LLC — May 2015 breach

Clustered 7 records across 6 jurisdictions: 6 filings and 1 enforcement record · filing window Jun 19, 2015 → Jul 23, 2015. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Enforced

Members

7 records

States

5

Affected · reported

3,500,000

First → last filing

Jun 19, 2015 → Jul 23, 2015

Merge confidence

100%

incident inc_4e404cfbdda94b40 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 enforcement record. The filings describe unauthorized access. Intrusion May 7, 2015–May 25, 2015, discovered May 26, 2015 — the first regulatory filing landed 24 days later. 3,500,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 5 more. Notifications rolled out on a 34-day schedule across 6 filings beginning Jun 19, 2015. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
24days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
34days

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 clocksSouth Carolina✓ SC CRA notice dueCalifornia✓ CA 60-day OK · 7dHIPAA✓ HHS report on time · 58dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

May 7, 2015breach begins
May 26, 2015discovered
notification delay · 24 days
Jun 19, 2015first filing
Jul 23, 2015most recent filing

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

Member cascade — every filing and enforcement record in this incident

  1. JUN 19NH AGNH AG noticefirst filing · no count statedday 0
  2. JUN 23MA AGMA AG notice17,156 MA residents+4d
  3. JUN 24SC AGSC AG notice10,778 SC residents+5d
  4. JUN 26CA AGCA AG noticeno count stated+7d
  5. JUL 15NH AGNH AG noticeno count stated+26d
  6. JUL 23HHS OCRHHS OCR noticestates nationwide total 3,500,000+34d
  7. MAY 23HHS OCR enforcementHHS OCR enforcement noticemost recent · no count stated+1434d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 7, 2015 – May 25, 2015
NH AG
Discovered
May 26, 2015· 19d undetected
NH AG + SC AG + CA AG +1
Data types
Authentication · Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + SC AG + CA AG +2
Attack vector
Unauthorized Access
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)

3,500,000

Sum of filed state slices

27,934· 0.8% of stated

99% 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 filing7 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 27, 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

34 days

Cadence

~1 / 6.8d

vs. multi-state median

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