Pensacola Hospitalist Physicians, LLC reported to HHS on 2025-09-16 a Hacking/IT Incident affecting 6052 individuals. Breached information located on Network Server.
Affected (this filing): 6,052
Clustered 3 filings across 2 jurisdictions · filing window Sep 16, 2025 → Sep 18, 2025. View entity profile → Other incidents for this victim →
incident inc_0716ec31cbb247a5 · 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.
PHI · Health (basic) · Identity (basic)
FL NH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 22, 2025 → May 23, 2025
When the intrusion reportedly occurred, per the linked filings
Sep 11, 2025
Reported by NEW HAMPSHIRE AG filing
Pensacola Hospitalist Physicians, LLC reported to HHS on 2025-09-16 a Hacking/IT Incident affecting 6052 individuals. Breached information located on Network Server.
Affected (this filing): 6,052
Pensacola Emergency Physicians, LLC reported to HHS on 2025-09-16 a Hacking/IT Incident affecting 511 individuals. Breached information located on Network Server.
Affected (this filing): 511
Pensacola Hospitalist Physicians, LLC notified the NH AG of a third-party business associate breach. Unauthorized access occurred May 22-23, 2025. Patient data (names, DOB, diagnosis, SSN) exposed. Notification mailed Sept 18, 2025. 2 NH residents affected. Credit monitoring offered.
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.