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

Medical Review Institute of America — November 2021 breach

Clustered 28 filings across 11 jurisdictions · filing window Jan 1, 2022 → Oct 3, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

28 filings

States

11

Affected · reported

172,420

First → last filing

Jan 1, 2022 → Oct 3, 2022

Merge confidence

100%

incident inc_572e9b8ea61846cd · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 28 regulatory filings. Intrusion Nov 2, 2021–Nov 9, 2021, discovered Nov 9, 2021 — the first regulatory filing landed 53 days later (flagged late). 172,420 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 275-day schedule across 28 filings beginning Jan 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
53days

Discovered → first regulatory filing

Discovery variance
182days

Range of discovered_at dates across filings

Filing span
275days

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 clocksMaine✗ ME AG >90d · 246dOregon✗ OR AG >45dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 2, 2021breach begins
Nov 9, 2021discovered · members disagree
notification delay · 53 days
Jan 1, 2022first filing
Oct 3, 2022most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 1IL AGIL AG noticeno count statedday 0
  3. JAN 1IL AGIL AG noticeno count statedday 0
  4. JAN 7MT AGMT AG notice404 MT residents+6d
  5. JAN 7IN AGIN AG noticestates nationwide total 88+6d
  6. JAN 7ME AGME AG noticestates nationwide total 134,571+6d
  7. JAN 7WA AGWA AG notice3,225 WA residents+6d
  8. JAN 7CA AGCA AG noticeno count stated+6d
  9. JAN 7IN AGIN AG noticestates nationwide total 88+6d
  10. JAN 7HHS OCRHHS OCR noticestates nationwide total 172,420+6d
  11. JAN 7IN AGIN AG noticestates nationwide total 134,571+6d
  12. JAN 10OR AGOR AG noticeno count stated+9d
  13. JAN 10SC AGSC AG notice2,382 SC residents+9d
  14. JAN 10NH AGNH AG notice346 NH residents+9d
  15. JAN 13MA AGMA AG notice2,087 MA residents+12d
  16. JAN 18CA AGCA AG noticeno count stated+17d
  17. JAN 18ME AGME AG noticestates nationwide total 157,885+17d
  18. JAN 20HHS OCRHHS OCR noticestates nationwide total 2,406+19d
  19. JAN 21NH AGNH AG noticestates nationwide total 435+20d
  20. FEB 3CA AGCA AG noticeno count stated+33d
  21. FEB 3ME AGME AG noticestates nationwide total 171,083+33d
  22. MAR 14NH AGNH AG notice437 NH residents+72d
  23. MAY 10CA AGCA AG noticeno count stated+129d
  24. JUL 13CA AGCA AG noticeno count stated+193d
  25. JUL 13ME AGME AG noticestates nationwide total 170,014+193d
  26. JUL 16NH AGNH AG notice421 NH residents+196d
  27. JUL 16NH AGNH AG notice459 NH residents+196d
  28. OCT 3CA AGCA AG noticemost recent · no count stated+275d
  29. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 2, 2021
IN AG
Discovered
Nov 9, 2021IL AG + ME AG + WA AG +4May 10, 2022IL AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + ME AG + WA AG +5
Attack vector
Unauthorized Access
ME 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)

172,420

Sum of filed state slices

11,440· 6.6% of stated

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

US172,420
WA3,225
IN2,590
SC2,382
MA2,087
NH459
MT404
ME293

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

275 days

Cadence

~1 / 10.2d

vs. multi-state median

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