A single-specialty eye care practice with a handful of Central Florida locations doesn't sound like a prime hacking target. No 10,000-employee hospital system, no household-name insurer, no Wall Street attention. Just doctors who see patients, bill insurance, and go home. That's exactly why it got hit.

What actually happened

Florida Retina Center, an ophthalmology practice with multiple locations around Orlando, discovered unauthorized access to its internal network on January 30, 2026. A forensic investigation ran for months and confirmed in May that an outside party had gotten into systems holding patient and staff records. By the time notification letters went out, the practice was reporting that 13,652 people (patients and employees both) had names, dates of birth, Social Security numbers, driver's license numbers, and medical information exposed.

To the practice's credit, the response reads like the textbook version: contain the network, bring in outside forensics, notify law enforcement, mail notification letters, and offer a year of free credit monitoring and identity theft protection. Nobody dragged their feet, and as of the public reporting, there's no confirmed misuse of the data. That's the good news. The less good news is the timeline: nearly four months between discovery and confirmation, and that gap is not unusual, it's close to normal. Figuring out exactly what an attacker touched, in a system nobody built with a forensic audit trail in mind, takes time. If you're picturing this process happening smoothly while you're also trying to run a practice and see patients, you should picture it less smoothly than that.

Why this matters beyond one eye care practice

Here's the detail that should get a small practice's attention more than the headline number: the exposed data included employee records, not just patient charts. Staff Social Security numbers and personal details sat in the same breached environment as patient data. Practice owners tend to build their entire mental model of "what we need to protect" around the exam room and the EHR. Payroll files, HR records, and old onboarding paperwork rarely make that list, and attackers don't care which folder they're in, only whether it's reachable.

The other number worth sitting with: IBM's 2026 Cost of a Data Breach Report put the average healthcare breach at $6.64 million, which, yes, is actually down from $7.42 million the year before, and healthcare has now held the dubious title of "most expensive industry to get breached in" for thirteen years running. That average is dragged up by giant health systems, so don't read it as "this will cost us $6 million." Read it as: the base rate of expensive breaches in this industry hasn't budged in over a decade, across every practice size, because the mix of insurance billing data, Social Security numbers, and medical history is simply worth more on the black market than almost anything else a small business holds.

What this means if you're a South Florida practice

None of this requires you to be a retina specialist, or in Orlando, or any particular size. If you're a small or mid-size specialty practice in Palm Beach, Broward, or Miami-Dade, and increasingly as UpsiteGroup extends its HIPAA-focused support into Martin and St. Lucie counties too, you're carrying the exact same mix of data this practice had: patient SSNs and insurance details on one side, employee personnel files on the other, both usually sitting on the same network with the same (or weaker) protections. A four-doctor office doesn't get a discount on attacker interest just because it's smaller than a hospital. If anything, it gets a discount on IT budget and incident-response planning, which is the actual reason small practices keep showing up in these reports. Attackers aren't impressed by your square footage. They're impressed by how long it takes you to notice them.

Practical takeaways

A few concrete things worth checking this month, none of which require a six-figure budget:

  • Separate your employee and HR data from your general network share the same way you'd separate patient charts; not because HR data is the main target, but because "everything reachable from one compromised login" is exactly the problem that turned this into a 13,652-person breach instead of a much smaller one.
  • Ask whoever manages your network (us or otherwise) how you'd actually detect unauthorized access today. If the honest answer is "we'd notice when something looks weird," that's not a detection plan, that's luck with a name.
  • Write down who gets called in the first 24 hours of a suspected breach: forensics, legal counsel, your cyber insurance carrier, and anyone handling patient notification. Florida Retina Center clearly had this ready. Plenty of practices don't, and improvising incident response while also running a medical office is a genuinely bad way to spend a week.
  • Check whether your cyber insurance policy actually covers a breach of this size and shape, specifically, employee data mixed with patient data, before you need the answer rather than after.

None of this guarantees you won't end up in a report like this one someday. It does mean that if you do, the story reads a lot more like "contained quickly, handled well" and a lot less like "nobody noticed for months."

"Not sure where your practice stands?" If you're evaluating a new EHR or want a second opinion on your current one's security configuration, we're glad to help you think it through.