DisclosureLens
State AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

Pharmacy Times Office of Continuing Professional Education, LLC — May 2018 breach

Clustered 7 filings across 6 jurisdictions · filing window Nov 13, 2018 Feb 6, 2019. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

128,211

First → last filing

Nov 13, 2018 Feb 6, 2019

Merge confidence

100%

incident inc_fc95df3d8d6b4e56 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion May 11, 2018–Jul 6, 2018, discovered Jul 6, 2018 — the first regulatory filing landed 130 days later (flagged late). 128,211 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 85-day schedule across 7 filings beginning Nov 13, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
130days

Discovered → first regulatory filing

Discovery variance
73days

Range of discovered_at dates across filings

Filing span
85days

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 >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 11, 2018breach begins
Jul 6, 2018discovered · members disagree
notification delay · 130 days
Nov 13, 2018first filing
Feb 6, 2019most 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 13WA AGWA AG noticefirst filing · 797 WA residentsday 0
  2. NOV 13OR AGOR AG noticestates nationwide total 128,211day 0
  3. NOV 13MA AGMA AG notice803 MA residentsday 0
  4. NOV 19NH AGNH AG notice129 NH residents+6d
  5. NOV 26CA AGCA AG noticeno count stated+13d
  6. FEB 6MT AGMT AG notice171 MT residents+85d
  7. FEB 6NH AGNH AG noticemost recent · 129 NH residents+85d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 11, 2018Jul 6, 2018
WA AG
Discovered
Jul 6, 2018WA AG + NH AG + CA AG +1Sep 17, 2018OR AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
WA AG + NH AG + CA AG +2
Attack vector
Unauthorized Access
WA 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)

128,211

Sum of filed state slices

1,900· 1.5% of stated

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

US128,211
MA803
WA797
MT171
NH129

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 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

85 days

Cadence

~1 / 14.2d

vs. multi-state median

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