Florida Retina Center 2026 Data Breach
The Florida Retina Center 2026 data breach was a security incident targeting the practice's network environment. According to the organization's official notice, it detected the event on or about 30 January 2026.
Exposed Data Types
1 sensitive5- Medical information
- Names
- Dates of birth
- Social security numbers
- Driver's license numbers
About This Breach
An unauthorized third party attempted to infiltrate the network, and a review completed on 19 May found that some personal information may have been accessed or acquired. The public notice was issued on 26 May.
HHS/OCR lists 13,652 affected people for Saurabh N. Patel, M.D. – Florida Retina Center and classifies the event as a hacking or IT incident involving a network server. The federal entry carries an 11 May report date, while the organization's notice says its review concluded on 19 May. The sources do not explain that sequence, and the public records do not provide a confirmed access start or end date.
What information may have been involved?
The official notice lists names, dates of birth, Social Security numbers, driver's license numbers, and medical information as possible fields. The combination varied by person; it does not follow that every category applied to all 13,652 people or was definitely acquired. Because the public notice does not divide medical information into narrower fields, each recipient's letter remains the authority for person-specific scope.
Organization response and safe next steps
Florida Retina Center said it secured the network, investigated with a specialist forensic response firm, and enhanced technical safeguards. At the notice date, it had received no reports of information misuse or related identity theft, and it offered potentially affected people twelve months of credit monitoring and identity protection. People whose letter lists an identity number can review credit reports, while those whose letter lists medical information can check patient portals, insurance statements, and medical bills for unfamiliar entries. Unexpected messages should be verified through the practice's current official channel without using links in the message.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
