Dental & Healthcare

Ohio's Keep Smiling Dental Group Says Patient Files, Including X-Rays and Clinical Notes, Were Accessed or Taken in a Late-Summer Network Incident: A Patient-Records Checklist for Dental and Medical Practices

Keep Smiling Dental Group in Beavercreek, Ohio says files were accessed or taken from its network between Aug. 29 and Sept. 5, 2026, including dental records, insurance and billing details, and some Social Security numbers. A server, access and monitoring checklist for dental and medical practices.

Keep Smiling Dental Group, a family dental practice with two offices in Beavercreek, Ohio, says certain files were "accessed or taken" from its network between August 29 and September 5, 2026, and that the information involved can include dental records, X-rays, treatment plans, clinical notes, insurance and billing details, and for a limited number of people, Social Security numbers. The practice first spotted the activity on September 7 after what it calls a "network disruption." It has now finished reviewing the files and is working to notify the people involved. For any dental or medical office that keeps charts, imaging and billing on one local server, the notice is a good reason to check what an intruder could reach in a week.

What Keep Smiling Dental Group has said

In a Notice of Data Event posted on its website, the practice says it "recently experienced a network disruption involving certain computer systems and files," took steps to confirm the security of its systems and opened an investigation. That investigation "confirmed the disruption was the result of a cybersecurity incident and that certain files were accessed or taken from the KSDG network between August 29, 2026 and September 5, 2026." The practice says it first identified related activity on September 7, 2026.

According to the notice, the information involved "varies by individual, but may include: name, patient ID, date of birth or age, contact information (such as address, phone number, or email address), dental insurance information, dental account and billing information (such as account balances and treatment charges), dental records (including X-rays, treatment plans, and clinical notes), medical history, and appointment or schedule information." It adds that "for a limited number of individuals, Social Security number may also have been involved."

The practice says it is not aware of any identity theft or fraud tied to the event. It says it has added "server-wide security enhancements and additional phishing-awareness training" for staff, reviewed its security policies, and reported the event to the FBI. It also warns patients that it "will never ask you for your Social Security number, banking information, or passwords by email or text message." HIPAA Journal reported the notice on November 13, 2026.

What we are not claiming: The practice has not said how the attacker got in, who was behind it, or how many patients are affected, and we are not guessing. Its mention of new phishing-awareness training does not tell us phishing was the way in. We are not saying this was ransomware, that any files were encrypted, that a ransom was demanded or paid, or that patient data has been published. The practice says it is not aware of any misuse. Social Security numbers were involved only for a limited number of people, according to the notice.

Why this matters to dental and medical practices

A small practice's server often holds everything in one place: the practice-management database, the imaging archive, scanned insurance cards, billing exports and years of old charts. In this case the practice says files were accessed or taken over about a week, from August 29 to September 5, before it identified the activity on September 7, and the review and notification work is still under way more than two months later. That pattern is common. The intrusion is quiet, the cleanup is loud, and most of the cost comes from working out whose records were in the files and writing to every one of them.

The details in this notice, such as X-rays, clinical notes and account balances, are the details patients care about most. Under HIPAA, losing them also means breach analysis, notification and documentation, even when no one ever misuses the data. The best protection is to make the server harder to reach, keep less on it, and make sure someone notices quickly when files start moving.

What to do this week

  1. Know what lives on your practice server. List where your practice-management database, imaging, scanned documents and billing exports are stored, including copies on front-desk PCs and in email. You cannot protect, or later review, files you didn't know you had.
  2. Lock down remote access. Require multi-factor authentication on every remote-access tool, VPN and Microsoft 365 account, including vendor and imaging-support logins. Remove accounts for former staff and vendors you no longer use.
  3. Limit who can open what. Front-desk accounts rarely need the whole imaging archive, and nobody needs to browse the server as an administrator day to day. Separate admin accounts from everyday logins.
  4. Watch for files leaving. Make sure your endpoint protection or managed detection actually alerts a person on unusual outbound transfers and new remote tools, including at night and on weekends. A week is a long time for nobody to look.
  5. Keep logs long enough to answer "what was touched." File-access and sign-in logs that roll over after a few days leave investigators assuming the worst, which means more letters.
  6. Prepare your front desk for calls and fake messages. Patients may call after any breach in the news. Give staff a short script, and remind everyone that the practice never asks patients for passwords or Social Security numbers by text or email.
  7. Write down who you call. Keep your cyber insurer's hotline, breach counsel, your IT provider and your HIPAA privacy officer on one page, and check whether your policy requires its own panel vendors.

The takeaway for IT decision-makers

For a dental or medical practice, most breach costs come after the attacker leaves: reviewing files, notifying patients and answering questions. Use MFA on every way in, give each account only the access it needs, make sure someone watches for files leaving, and keep the logs that show what was touched. Those steps make an intrusion harder and the cleanup shorter.

Sources

One accountable technology partner.

Tell us what's slowing your team down. We'll show you exactly how we'd fix it — no pressure, no jargon.

Book a Free Consultation
Book a Free Consultation