Disclosures Claims Reports Entities Incidents Pulse

Feed live

DisclosureLens

Structured extracts of public breach disclosures — regulator filings (SEC, HHS, state AGs, EU DPAs) alongside threat-actor leak-site claims and press reports. SEC and HHS filings render inline from the originating regulator’s public record under the fair report privilege; other sources link out to the source URL. AI-extracted with full per-record audit trail (model, prompt version, confidence).

ai_assisted: true · Article 50 disclosure on every record

Product

Disclosures feed
Pulse · analytics
Entities
Breach notifications by state

Methodology

How extraction works
Confidence & review
About the bot

Trust

Security
Self-disclosure commitment
API documentation
API keys

v0.1.0 · coverage growing weekly

PracMan, Inc. data breach (2014) · DisclosureLens

All incidents View linkage analytics →

Incident · single filing

PracMan, Inc.

One linked filing — more sources may join as they report · filing window Mar 7, 2014 → Mar 10, 2014. View entity profile → Other incidents for this victim →

Confirmed breach. Intrusion Jan 10, 2014. 1,145 individuals reported across the linked filings.

incident inc_0ae0f4608ad1474d · merge_method llm

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

HHS OCRConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity

Affected (total reported)

1,145

Data types

Health (basic)

Jurisdictions

FEDERAL

Linked filings

all HHS OCR

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

Breach window
Jan 10, 2014
When the intrusion reportedly occurred, per the linked filings
56 days
FEDERALHHS OCRFirst filing
Filed Mar 7, 2014bd_7c4a9abdedf62f27
On January 10, 2014, business associate PracMan, Inc. reported a breach to HHS affecting 1,145 individuals. The breach was caused by a technology subcontractor, MASHNet, who erroneously copied and stored computer files on an unsecured network server. The exposed information included patient demographic, clinical, and financial data, such as names, social security numbers, and diagnoses.
Affected (this filing): 1,145
HHS notified

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.