Clustered 3 filings across 3 jurisdictions · filed Sep 11, 2025. View entity profile → Other incidents for this victim →
incident inc_50d372fa4e364fa2 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
IN ME TN
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 5, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 7, 2025
Reported by MAINE AG filing
Franklin Dermatology Group PLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-07-05 and was reported on 2025-09-11. 1 Indiana residents were affected. 2,457 individuals affected in total.
Affected (this filing): 2,457
Franklin Dermatology Group, PLC reported a data breach to the Maine Attorney General, stating that an external system breach (hacking) occurred on July 5, 2024. The breach was discovered on February 7, 2025. One Maine resident was affected, out of a total of 2,457 individuals. The affected resident was notified in writing on September 11, 2025. The company offered 12 months of credit monitoring and identity theft recovery services.
Affected (this filing): 1
Franklin Dermatology Group, PLC reported to HHS on 2025-09-11 a Hacking/IT Incident affecting 2457 individuals. Breached information located on Network Server. Business associate was present.
Affected (this filing): 2,457
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.