DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed14 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 14 filings

Medical Eye Services, Inc. — May 2023 breach

Clustered 14 filings across 8 jurisdictions · filing window Nov 14, 2023 → Feb 1, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

14 filings

States

8

Affected · reported

664,824

First → last filing

Nov 14, 2023 → Feb 1, 2024

Merge confidence

100%

incident inc_f7745c9cfc784721 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. The filings describe unauthorized access. Intrusion May 28, 2023–May 31, 2023, discovered Aug 23, 2023 — the first regulatory filing landed 83 days later (flagged late). 664,824 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 79-day schedule across 14 filings beginning Nov 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
83days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
79days

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 clocksOregon✗ OR AG >45dMaine✗ ME AG >90d · 161dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 28, 2023breach begins
Aug 23, 2023discovered
notification delay · 83 days
Nov 14, 2023first filing
Feb 1, 2024most 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. NOV 14HHS OCRHHS OCR noticefirst filing · states nationwide total 377,931day 0
  2. NOV 14CA AGCA AG noticeno count statedday 0
  3. NOV 14MT AGMT AG notice2,692 MT residentsday 0
  4. NOV 14OR AGOR AG noticestates nationwide total 346,828day 0
  5. NOV 15MA AGMA AG notice2,433 MA residents+1d
  6. NOV 15ME AGME AG noticestates nationwide total 346,828+1d
  7. NOV 15WA AGWA AG notice35,746 WA residents+1d
  8. NOV 17MA AGMA AG notice1,955 MA residents+3d
  9. NOV 17ME AGME AG noticestates nationwide total 664,824+3d
  10. NOV 17OR AGOR AG noticestates nationwide total 664,824+3d
  11. NOV 20NH AGNH AG notice436 NH residents+6d
  12. JAN 30CA AGCA AG noticeno count stated+77d
  13. JAN 31ME AGME AG noticestates nationwide total 2,743+78d
  14. FEB 1MA AGMA AG noticemost recent · 14 MA residents+79d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 28, 2023 – May 31, 2023
CA AG
Discovered
Aug 23, 2023· 87d undetected
CA AG + MT AG + OR AG +3
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + WA AG + CA AG +4
Attack vector
Unauthorized Access
HHS OCR

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)

664,824

Sum of filed state slices

41,516· 6.2% of stated

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

US664,824
WA35,746
MT2,692
MA2,433
NH436
ME209

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 filing14 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
Reviewed
operator-reviewed Aug 23, 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

79 days

Cadence

~1 / 6.1d

vs. multi-state median

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