What Orthanc is – and why a practice might be running it

Orthanc is a lightweight DICOM server: think of it as the box that accepts images from your X-ray sensors, CBCT and pan units, stores them in a standard medical format, and hands them back to whatever software your clinicians use to look at them. It’s popular precisely because it’s free, capable and easy to stand up, so it turns up in home-grown archives, imaging bridges, research setups and small vendor products – sometimes without the practice owner even knowing it’s under the hood. Even if you’ve never heard the name, the shape of the risk is familiar: it’s the same central imaging hub we described when we walked through how dental AI and imaging software talk to each other over TWAIN, DICOM and APIs. Whatever software plays that role in your office, this advisory is a prompt to go find out what it is and whether it’s current.

What the flaw actually does

The technical mechanism is an integer overflow in the math Orthanc uses to size an image buffer. When the server decodes an attacker-supplied PNG or JPEG, that miscalculation lets the code write past the end of the memory it allocated – a “heap out-of-bounds write” – and the Orthanc process crashes. The result is a denial of service: the imaging server goes down and stops answering. Two things are worth being precise about. First, this is remote but authenticated – the attacker needs valid credentials to upload the poisoned image, so it isn’t an anonymous internet drive-by. Second, it is a crash, not remote code execution and not data exfiltration; nobody is stealing patient records through this particular hole. That’s meaningfully less severe than the viewer-side flaw we covered a few weeks ago in the RadiAnt DICOM advisory, where a malicious file targeted the workstation opening it. This one targets the server that holds everything.

Why ‘just a crash’ still matters in a clinic

It’s tempting to shrug at a denial-of-service bug – no data lost, just restart the service. In a dental practice, availability is the point. The imaging server is the diagnostic record: if it’s down, the hygienist can’t pull last year’s bitewings, the dentist can’t compare a lesion over time, and a chairside CBCT you just captured may have nowhere to land. A server an attacker can crash on demand is a server that can be held down through an entire clinic day – appointment after appointment running blind – until someone traces the cause. And a repeatable crash is a gift to anyone probing your network: it’s a reliable way to disrupt operations, or a smokescreen run alongside something worse. Downtime in a health setting isn’t an inconvenience; it’s care delayed.

The real lesson: your imaging server should not face the internet

Here’s the part that outlives this specific CVE. The attack requires two things: a login, and a network path to reach the server. CISA’s own guidance leads with the fix that neutralizes both – minimize network exposure, keep imaging servers off the internet, and isolate the medical-device network from the business network with firewalls, allowing remote access only through a VPN. In other words, patch the bug, yes – but the durable defense is making sure a stranger could never reach the login page to begin with. “Authenticated” sounds reassuring until you remember how credentials actually leak: a phished password, a shared login taped to a monitor, a vendor account that never got disabled. Segmentation is what turns “an attacker with a stolen password” back into “an attacker who still can’t get to the imaging server.” It’s the same principle that stops ransomware crews at the edge, which is why we keep hammering on patched, properly configured perimeter gear – from firewalls that ransomware groups actively exploit to the practice router as a backdoor. An imaging server exposed to the open internet is a standing invitation; one sitting on a segmented internal network is a much smaller target.

What to do now

The response here is short and concrete. Inventory your imaging stack: find out whether Orthanc – or any DICOM server – is running in your practice, and which version. Patch it: if it’s Orthanc below 1.13.0, update to 1.13.0, the version that fixes CVE-2026-87020. Take it off the internet: confirm the imaging server is not reachable from outside, and if remote access is genuinely needed, put it behind a VPN, not a port forward. Segment the network: imaging and medical devices belong on their own isolated VLAN, separated from the front-office PCs and guest Wi-Fi. Tighten accounts: unique logins, least privilege, MFA where the software supports it, and prompt removal of old vendor and staff accounts. Watch it: monitoring that flags a service crashing repeatedly turns a silent, all-day outage into a same-minute alert.

What this means for your practice

CVE-2026-87020 is a modest bug with an outsized lesson. The immediate task – update Orthanc to 1.13.0 – takes minutes. The real question it raises is bigger: do you actually know where your images live, who can reach that server, and whether it’s exposed to the internet? Most practices have never mapped this, and “authenticated only” is a thin comfort when passwords are the weakest link in every office. Compudent Systems designs and manages exactly this for dental practices across Ontario: we inventory your imaging and device stack, keep DICOM servers and PACS patched, segment your network so imaging and medical devices sit safely behind the perimeter, lock down remote access, and monitor for the crashes and anomalies that signal trouble. If you’re not certain your imaging server is patched – or whether it’s quietly reachable from the internet right now – contact Compudent for an imaging and network security assessment. We’ll find out where your images live and make sure only the right people can reach them.

Sources & further reading:

• CISA – Orthanc DICOM Server (ICSMA-26-253-02)
• The HIPAA Journal – Orthanc DICOM Server Vulnerability Can Lead to Denial of Service

Related Reading

• A Booby-Trapped X-ray File: What the RadiAnt DICOM Advisory (CVE-2026-17264) Means for Dental Practices
• One Vendor Runs Your Network, Cameras, and Phones: Three Max-Severity Ubiquiti Flaws and What Your Practice Must Patch
• Where Was Your Imaging Sensor Made, and What Is It Talking To? Device Provenance Is Now a Dental Practice Security Question

The post A Poisoned Image Can Crash Your Imaging Server: The Orthanc DICOM Flaw (CVE-2026-87020) and Why Your PACS Shouldn’t Face the Internet appeared first on Compudent Systems.

What actually happened

Two details matter more than the rest. The Russian actor, tracked as GTG-20006, didn’t invent a new super-weapon; it wired an AI model into the boring, time-consuming part of an attack. Normally, when antivirus flags a malware sample, the criminals have to sit down and manually rewrite it to slip past the filter – a task that takes skill and hours. Their workflow automated that rework, tightening the loop between “we got caught” and “we’re back in.” The second case is about scale: sifting through the code of nearly two million apps to find leaked credentials is exactly the kind of tedious, high-volume grind that used to bottleneck attackers. AI removed the bottleneck. Neither is science fiction – both are ordinary attacker chores, done faster.

The honest part: the AI company caught it

It would be easy to spin this as “AI is now unstoppable.” That’s not what the report says, and pretending otherwise doesn’t help anyone plan. Anthropic detected this abuse, disrupted the campaigns and banned the accounts – and the same AI capabilities are being used by defenders to triage alerts, spot anomalies and reverse-engineer threats faster than a human team could alone. This is an arms race, not a rout. The right posture for a practice is neither panic nor denial: it’s recognizing that the economics of attacking a small business have shifted, and adjusting the defenses that depend on attackers being slow. We laid out the broader shape of this a while back in what AI-powered threats mean for dental practices; this week’s report is that forecast turning concrete.

Why this hits small practices specifically

A dental office is a soft, valuable target: a small network holding a large trove of patient health information, usually with no full-time security staff and often with a security tool that was installed once and left alone. The two things AI erodes – the attacker’s need for skill and the attacker’s need for time – are exactly the two things that used to protect a small practice. “We’re too small and too boring for a sophisticated hacker” made sense when sophistication was scarce and expensive. When a workflow can automatically retool malware and scan millions of targets, the practice down the street stops being beneath notice and starts being one entry in a very long, automated list. The attacker doesn’t need to care about you personally; they just need your defenses to be a step behind.

Where old-style defenses fall down

The defense most vulnerable to this shift is signature-based antivirus – the classic “does this file match a known-bad fingerprint?” model. It works by recognizing malware it has seen before. Malware that rewrites itself on every detection is designed precisely to never match a known fingerprint twice. That doesn’t make the old approach worthless, but it does mean a practice leaning entirely on basic antivirus is defending against last year’s problem. The same weakness applies to any “set it and forget it” tool: if nothing is watching for behavior – a workstation suddenly reaching out to an unknown server, a process trying to disable backups, credentials being read in bulk – then a threat that changes its appearance sails straight through.

What holds up in an AI-accelerated world

The good news is that the durable defenses are the ones we already recommend – AI just raises the price of skipping them. Behavior-based EDR (endpoint detection and response) watches what software does rather than what it looks like, so a self-rewriting payload still gets caught when it starts acting like ransomware. Phishing-resistant MFA blunts credential theft even when the lure is AI-polished and flawless. Disciplined patching closes the doors these tools walk through – most malware still needs an unpatched hole to land, which is why keeping current with cycles like September’s record Patch Tuesday matters more, not less. Immutable, tested backups mean a successful encryption event is a bad day instead of a closed practice. And staff awareness is still front-line: AI writes cleaner phishing, so the tells shift from bad grammar to unexpected requests and off pattern behavior – the same instinct that catches invisible-text phishing that hides from your spam filter. The through-line is simple: stop trusting tools that only recognize known-bad, and start watching behavior.

The one thing that changes the math

If attackers are automating and speeding up, the single most valuable upgrade a practice can make is moving from point-in-time security to continuous security. A firewall you bought and an antivirus you installed are snapshots; a monitored environment is a movie. When rebuilding malware is fast, the defender’s response time becomes the deciding factor – and a practice can’t watch its own network at 2 a.m. This is where the same ransomware crews we’ve tracked hitting unpatched firewalls and edge devices get stopped: not by a cleverer product, but by someone (or something) actually watching, patching on a schedule, and responding in minutes.

What this means for your practice

AI hasn’t rewritten the rules of dental-practice security – it has raised the stakes on following them. The attacks got faster and cheaper; the defenses that assume attackers are slow and unskilled got weaker. A practice running basic antivirus and hoping to stay off the radar is now defending yesterday’s threat model. The practices that stay safe will be the ones with behavior-based detection, phishing-resistant logins, tight patching, backups they’ve actually restored from, trained staff, and continuous monitoring instead of set-and-forget tools. Compudent provides exactly this layered, monitored security for dental practices across Ontario – behavior-based endpoint protection, managed patching, hardened backups, phishing-resistant MFA and round-the-clock monitoring that catches a threat by what it does, not by whether we’ve seen it before. If you’re not sure whether your current defenses would notice malware that changes its face every time it’s caught, contact Compudent for a security assessment. We’ll show you where you stand and close the gaps before an automated attacker finds them.

Sources & further reading:

• The Hacker News – Russian State-Sponsored Hackers Use Claude to Rebuild Malware After Detection
• BleepingComputer – Hackers abused Claude to extract secrets from 1.8M Android apps
• Anthropic – Threat intelligence and disruption reporting

Related Reading

• 974 Patches, Two Being Exploited Right Now: How a Dental Practice Should Read September’s Patch Tuesday
• The FBI Just Refreshed Its Medusa Ransomware Warning for Healthcare: The Real Lesson for Your Dental Practice
• Half Your Connected Devices Carry a Critical Flaw. Can Agentic AI Finally Clear the Patching Backlog?

The post When the Malware Rewrites Itself: AI-Accelerated Attacks and What They Mean for Your Practice appeared first on Compudent Systems.

What is actually breaking

The pattern administrators describe is consistent and unsettling. After the September update installs, a server keeps working for a while – often until the first user logs off. Then things fall apart: existing Remote Desktop sessions can no longer disconnect or log off cleanly, new connection attempts hang partway through and eventually fail, and the pool of usable sessions dwindles until nobody can get in. Restarting the server does not reliably fix it; several admins report that only a full hard reset – or removing the update – restores service. One administrator debugging a Server 2022 box found what looked like a deadlock between Remote Desktop and the Local Session Manager, with the service jamming when users log out. Microsoft has not confirmed that as the cause and says it is investigating. The important point for a practice is not the internal mechanics – it is that the failure builds up over the day and can strike after everything looked fine at 8 a.m.

Which servers are affected

The reports span every current Windows Server release: Server 2019 (update KB5122876), Server 2022 (KB5122882), and Server 2025 (KB5122871). Classic Terminal Server setups are affected too – the underlying Remote Desktop role is the common thread, not any one edition. Ordinary Windows 10 and 11 workstations are not the subject of these particular reports; this is a server problem. That distinction matters, because it means the danger is concentrated exactly where a practice can least afford it: on the one central machine the whole office depends on.

Why this hits a dental practice harder than most offices

A great many dental practices run their practice-management software – Dentrix, Eaglesoft, Open Dental, Tracker/PowerPractice and similar – on a single Windows Server, with front-desk PCs, operatory workstations and remote clinicians all connecting to it. When that connection is Remote Desktop or a terminal/session host, this bug is not a nuisance on one machine; it is a switch that can turn off charting, scheduling, imaging access and billing for everyone at once. And in a dental office, downtime is not an inconvenience measured in lost email – it is patients in the chair with no chart, a front desk that cannot see the day’s schedule, and hygienists who cannot pull up last year’s radiographs. The blast radius of a server that everyone remotes into is the entire practice. This is the same reason we keep stressing that infrastructure – the pieces everyone depends on and nobody thinks about – deserves careful change control, whether it is the server, the firewall, or the practice router that runs on its own patch calendar.

The uncomfortable part: you were just told to patch

Here is the genuine bind. This month’s record-setting September Patch Tuesday fixed roughly 970 vulnerabilities, two of which are being actively exploited right now. That is not a set of fixes to shrug off – the whole reason we urge practices to patch promptly is that attackers move fast, as the ransomware crews now hunting unpatched firewall appliances keep proving. So “just don’t install September’s updates” is bad advice: it leaves two exploited holes open on your network. But blindly installing the server update on a Remote Desktop host risks taking the office offline. The right answer is not one or the other – it is sequencing and testing, so you get the security fixes without gambling the practice’s uptime.

What your practice should do now

The path through this is deliberate rather than dramatic. 1. Know your setup. Determine whether your practice server has the Remote Desktop Services or Terminal Server role, or whether staff and remote clinicians connect to it by Remote Desktop. If they do, treat this month’s server update with extra caution. 2. Don’t patch the server blind. Apply the September cumulative update to one test or lower-risk server first and let it run through a full day – including users logging off – before rolling it out to the production practice server. 3. If you’re already broken, roll back. Where a server has already started failing, uninstalling the specific September cumulative update (KB5122876 / KB5122882 / KB5122871) is the fix administrators report works. Treat that as a temporary measure, not a permanent choice – it removes this month’s security fixes too. 4. Watch for Microsoft’s fix. Microsoft is investigating and typically ships either a Known Issue Rollback or an out-of-band update for regressions like this; re-apply the security fixes as soon as a corrected update is available. 5. Have a real rollback plan and verified backups. The practices that ride out an update like this calmly are the ones that can restore or revert quickly – which is exactly why server backups and a documented recovery process are not optional infrastructure.

What this means for your practice

This episode is a clean illustration of why patching is a managed discipline, not a checkbox. A practice needs to install security updates promptly – the exploited zero-days in this same release are proof of that – and it needs to do so without betting the whole office on an update that Microsoft is still troubleshooting. Squaring those two demands is exactly the job of professional patch management: a test ring before production, staged rollout of server updates, verified backups and a rehearsed rollback, and someone watching the vendor advisories so a known-bad update gets held and a fixed one gets applied fast. Compudent manages exactly this for dental practices across Ontario – patch scheduling and testing for your practice server, Remote Desktop and terminal-server environments, backup and recovery you can actually rely on, and monitoring so a regression like this month’s is caught before it empties your waiting room. If you run a server-based practice and you’re not certain how – or whether – your September server updates are being handled, contact Compudent for a patch-management and continuity assessment. We’ll make sure you stay both patched and open.

Sources & further reading:

• BleepingComputer – September Windows Server updates break Remote Desktop Services
• BleepingComputer – Microsoft September 2026 Patch Tuesday fixes 966 flaws, 2 zero-days

Related Reading

• 974 Patches, Two Being Exploited Right Now: How a Dental Practice Should Read September’s Patch Tuesday
• Dentrix, Eaglesoft, Open Dental: Why One Patching Policy Cannot Cover All Three
• February 2026 Patch Tuesday: Microsoft Fixes 6 Actively Exploited Zero-Day Vulnerabilities — What Dental Practices Need to Do Now

The post The Patch That Locks Out the Front Desk: September’s Windows Server Update Is Breaking Remote Desktop appeared first on Compudent Systems.

What makes this flaw different from the usual alert

Most of the security warnings a practice sees describe attacks that need several steps: a staff member has to open a phishing email, a password has to be stolen, a foothold has to be established before an attacker can move. This one skips all of that. CVE-2025-14733 is an unauthenticated remote-code-execution flaw – technically an out-of-bounds write in the firewall’s software – and it can be exploited in low-complexity attacks. In plain terms: an attacker who can reach your firewall over the internet can run their own code on it without any login, password or click from your staff. There is no foothold to establish because the firewall itself is the foothold. And the firewall is not some minor gadget – it is the internet-facing front door to your entire practice network, the device that stands between the open internet and your practice-management server, your imaging PCs and every record of patient health information you hold.

Which devices are affected

The flaw affects WatchGuard Firebox appliances running Fireware OS 11.x and later (including 11.12.4_Update1), 12.x and later (including 12.11.5), and the 2025.1 through 2025.1.3 releases. According to WatchGuard’s own advisory, a Firebox is exposed when it is configured to use the IKEv2 VPN – the feature many practices turn on so a dentist or a remote hygienist can connect securely from home. Here is the part that trips people up: WatchGuard warns that a device may still be vulnerable even if you deleted the vulnerable VPN configuration, as long as a branch-office VPN to a static gateway peer is still configured. “We turned that off ages ago” is not the same as “we are safe.” The only way to know is to check the firmware version and the current configuration directly.

Nine months, and thousands are still open

This is the uncomfortable pattern with edge devices. The internet-monitoring group Shadowserver counted roughly 115,000 exposed Fireboxes when the flaw went public in December; nine months later, nearly 9,000 remain unpatched and reachable online. Firewalls, routers and VPN appliances are the perfect ransomware target precisely because they are the devices everyone installs and then forgets – they sit in a closet, they “just work,” nobody logs in for a year, and their firmware quietly rots. This is not a WatchGuard-only failing; it is the same reason we recently had to sound the alarm about actively exploited flaws in practice routers. Attackers know these boxes are neglected, and CISA has now confirmed they are walking straight through this one. For context, this is not even the first WatchGuard flaw to draw this level of attention – an earlier Firebox vulnerability was exploited by Russian state-linked hackers two years ago. Edge devices are a permanent front line, not a one-time chore.

Why a firewall breach becomes a ransomware disaster

When an attacker compromises the firewall, they are not stuck at the edge – they are inside the perimeter, on the one device that can see and route to everything else. From there the ransomware playbook is well worn: map the internal network, reach the practice server, disable backups, encrypt patient records and imaging data, and leave a ransom note. We have watched exactly this kind of chain end badly for dental organizations when it starts with a trusted third party – the recent billing-vendor ransomware attack that put practices on a leak site is a reminder of how fast “one compromised system” becomes “our patients’ data is for sale.” A pre-authentication flaw on your own firewall removes even the need for a third party. And the fallout is not only technical: under PHIPA, a ransomware event that exposes patient information is a reportable privacy breach, with all the notification, regulatory and reputational weight that carries.

What your practice should do this week

The fix is genuinely fast – the hard part is simply doing it. 1. Find out what you have. Confirm whether your practice runs a WatchGuard Firebox and, if so, which Fireware version. If you don’t know, that uncertainty is itself the finding. 2. Upgrade the firmware now. WatchGuard released fixed Fireware versions in December; updating to a patched release closes the hole. This is a scheduled, out-of-hours job on the firewall, not a workstation reboot. 3. Retire VPN configs you don’t use. Disable IKEv2 and old branch-office VPN configurations you no longer need – but verify against WatchGuard’s advisory, because a leftover static-peer config can keep you exposed. 4. Check for signs you were already hit. WatchGuard published indicators of compromise so customers can tell whether a device was attacked before it was patched; if you were exposed for months, assume-breach and look. 5. Don’t stop at the firewall. Patch Tuesday covers Windows, but your firewall, router and phone system run on their own calendars – a complete posture patches all of them, and the machines that genuinely cannot be patched get segmented off so a perimeter breach can’t reach them. If you missed this month’s Windows update, our breakdown of September’s record Patch Tuesday shows how to prioritize.

What this means for your practice

A firewall is supposed to be the thing that protects the practice – which is exactly why a flaw in it is so serious, and why “we have a firewall” is not the same as “our firewall is current.” An unpatched edge device is worse than no firewall, because it gives you the confidence of protection while quietly serving as the attacker’s way in. The practices that stay safe are not the ones that never buy a WatchGuard; they are the ones whose firewalls, routers and VPN appliances are inventoried, monitored and patched on a schedule instead of installed and forgotten. Compudent manages edge security for dental practices across Ontario – tracking firmware across your firewall and network gear, applying critical patches like this one on a tight schedule, hardening remote-access VPNs, and checking exposed devices against advisories the moment they land. If you are not certain whether your practice firewall is patched against CVE-2025-14733 – or you’re not sure what firewall you even have – contact Compudent for an edge-security assessment. We will find out where you stand and close anything that’s still open.

Sources & further reading:

• BleepingComputer – CISA: WatchGuard RCE flaw now exploited in ransomware attacks
• WatchGuard PSIRT – CVE-2025-14733 Security Advisory (WGSA-2025-00027)
• CISA – Known Exploited Vulnerabilities Catalog (CVE-2025-14733)

Related Reading

• Ransomware Gangs Are Now Through the Front Door: What the SonicWall SMA1000 VPN Attacks Mean for Dental Practices
• The FBI Just Refreshed Its Medusa Ransomware Warning for Healthcare: The Real Lesson for Your Dental Practice
• Ransomware Is Now a Patient-Safety Issue: What a 38% Hospital Mortality Study Means for Your Dental Practice

The post Ransomware Is Now Using It: The WatchGuard Firewall Flaw Your Practice Can’t Leave Unpatched appeared first on Compudent Systems.

The four connection methods, in one map

Strip away the marketing and dental AI connects to your imaging in one of four ways. TWAIN grabs the image at the moment of capture, inside the imaging software, the same way your sensor already talks to Dexis or Eaglesoft. DICOM is the medical-imaging interchange standard – the shared file format and network protocol that lets CBCT volumes and radiographs move between systems that were never designed to talk to each other. A cloud API, usually paired with a practice-server agent, is how most modern platforms actually work: a small service on your practice server watches the local image database and syncs studies up to the vendor’s cloud, where the AI runs. And a PMS bridge is a purpose-built integration into a practice-management system such as Dentrix, Eaglesoft, Open Dental, or Curve, so the AI’s findings surface next to the patient chart. Real products mix these – a tool might acquire by TWAIN, store by DICOM, process in the cloud, and display through a PMS bridge – but every one of them is present, and each carries different consequences.

TWAIN: catching the image at capture

TWAIN is a decades-old imaging standard that lets an application pull an image directly from a capture device – a scanner, an intraoral camera, or a dental sensor – through a standardized driver. In a dental context it is the plumbing that already sits between your sensor and your imaging software, and several AI tools reuse it. A TWAIN-based AI module effectively taps the capture stream: the instant a bitewing or an intraoral photo is exposed, a copy is handed to the AI without the assistant exporting anything. VideaHealth, for example, is commonly integrated through TWAIN-capable imaging software so that its charting engine sees images as they are acquired.

The upside is a genuinely chairside, real-time experience with no extra clicks. The limitation is that TWAIN is a local, capture-time mechanism – it is excellent for 2D radiographs and camera images at the operatory, and largely irrelevant for reprocessing an archive or for moving a 3D CBCT volume. It is also Windows-centric and driver-dependent, which is exactly the sort of detail that turns a smooth demo into a support ticket if your imaging software version and the AI’s TWAIN shim disagree.

DICOM: the standard that moves the heavy studies

DICOM (Digital Imaging and Communications in Medicine) is the interoperability backbone of medical imaging, and it matters most where dentistry gets serious about 3D. CBCT scanners produce DICOM, PACS archives store and route DICOM, and DICOM defines both a file format and network operations – store, query, retrieve – for shuttling studies between systems. When a dental AI supports DICOM, it can ingest a CBCT volume or a set of radiographs regardless of which vendor captured them, because they all speak the same container. Pearl and Diagnocat, among others, offer DICOM pathways precisely because it is the honest way to accept images from a heterogeneous fleet of scanners and archives.

For a practice, DICOM support is a strong signal of an open, standards-based tool rather than a walled garden. It is what lets you send a study out for analysis and receive a structured result back, and it is the pathway most relevant if you are ever consolidating imaging into a PACS or MiPACS-style archive. The caveat is that “supports DICOM” is a spectrum – a vendor might accept a DICOM export but not respond to a live DICOM query, so the word alone does not tell you how automated the flow will be.

Cloud APIs and the practice-server agent

The dominant pattern in 2026 is not TWAIN or a manual DICOM export at all – it is a lightweight agent installed on your practice server that watches your imaging database and quietly syncs new studies to the vendor’s cloud over an encrypted channel. The AI runs remotely, and results flow back to a web dashboard or into the chart. Overjet, VideaHealth, and Diagnocat all operate on some version of this model. It is popular for good reasons: the heavy computation lives in the vendor’s data center, updates ship without touching every workstation, and the practice avoids running GPUs on-site.

It also changes your risk profile in ways worth naming plainly. Once images leave the building, you are relying on the vendor’s encryption, retention, and access controls, and protected health information is now processed off-site – which is squarely a business-associate relationship and a governance question, not just an IT one. We cover that side in detail in our guide to PHIPA, HIPAA, and dental AI data governance. From an integration standpoint, the practical questions are which imaging databases the agent can read, how much bandwidth the sync consumes, and whether the agent is a documented, supported component or a fragile script that breaks on the next imaging-software update.

PMS bridges – and why most of them are gated

Getting the image to the AI is only half the loop; the finding has to come back to where the clinician actually works, which is the practice-management system. That is what a PMS bridge does – it surfaces AI results inside Dentrix, Eaglesoft, Open Dental, or Curve so the annotated radiograph or the automated chart entry appears next to the patient record. Open Dental, with its open developer model and API, is the friendliest of these to integrate against; the larger proprietary systems generally require a formal partnership, and this is where a hard commercial reality lives. Many PMS integrations are partner-gated: the AI vendor must be an approved integration partner of the PMS company, and you cannot simply wire the two together yourself. That gating is the single biggest determinant of whether a given AI tool will drop cleanly into your specific practice, and it is why the same product can feel effortless in one office and impossible in another. Our breakdown of Overjet’s integration and RCM workflow walks through what a mature bridge looks like in practice, and the practice-management AI guide covers the administrative side of the same plumbing.

What to check before you buy

Before committing to any dental AI, treat integration as a due-diligence checklist rather than a demo afterthought. Ask which specific method the tool uses for your modality – TWAIN for 2D chairside, DICOM for CBCT and archives, cloud agent for hands-off sync. Confirm, in writing, that it supports your imaging software and your PMS by name and version, and ask whether that integration is direct or partner-gated – and if gated, whether the partnership already exists or is “on the roadmap.” Establish where images are processed and stored, and get the business-associate or data-processing agreement before, not after. Ask how the connector behaves when the imaging software updates, since that is the most common point of quiet failure. And if there is any chance you will use more than one AI vendor over time, favour standards-based paths – DICOM and documented APIs – over proprietary bridges, because they are what keep the choice yours. Two of our imaging-side companions, on how TWAIN feeds the AI and how the image reaches Pearl by DICOM, go deeper on the two standards themselves.

The AI reading your radiographs is impressive, but the connector underneath it is what you actually live with – it determines your compliance exposure, your support burden, and your freedom to switch. If you are evaluating a dental AI platform and want a straight answer on whether it will fit your imaging software, PMS, and network before you commit, Compudent Systems can assess your environment and map the integration path – or the reasons one does not exist. That is the kind of question worth answering before the contract, not after.

Sources & further reading:

• FDA-Approved AI Solutions in Dental Imaging: A Narrative Review (PMC)
• Pearl vs. Videa vs. Overjet: what 3 AI giants accomplished in 2026 (Becker’s Dental Review)

Related Reading

• Practice-Management AI: Revenue Cycle, Claims, and Analytics
• AI Scribes for Dentistry: Bola AI vs Heidi vs Denti.AI Scribe
• Overjet in Your Practice: Integration, RCM Workflow, and Data Governance

The post How Dental AI Tools Connect to Your Imaging Software: TWAIN, DICOM, API, and PMS Bridges appeared first on Compudent Systems.

Why the number keeps breaking records – and why that is not the scary part

Microsoft has been setting monthly records all year, and the reason is structural: the company is using AI to hunt for bugs in its own code, and AI finds them faster than humans ever did. More vulnerabilities discovered is not the same as more vulnerabilities being used against you. The security industry was blunt about this. “AI-assisted vulnerability discovery in 2026 is creating larger haystacks, but it isn’t finding more needles,” said Tenable’s Satnam Narang, urging organizations to work out which flaws actually apply to them and are genuinely reachable before panicking about the total (CyberScoop, September 2026 Patch Tuesday coverage). The Zero Day Initiative’s Dustin Childs made the same point – the pile keeps growing, but there has been “no correlating spike in active exploits.” Translation for a practice: a 974-item update is not 974 times more dangerous than a normal month. It is a normal month with a much longer to-do list, and the trick is sorting the list.

The two that actually matter this month

Both of the flaws being exploited before the patch existed are privilege-escalation bugs rated CVSS 7.8. The first, CVE-2026-81963, is in the Windows Update Stack. The second, CVE-2026-85880, is in Windows Advanced Local Procedure Call (ALPC), a core piece of how Windows processes talk to each other. Neither is a remote “click a link and you’re owned” flaw. Both are the second move in an attack: an intruder who has already gotten a small foothold on a machine – through a phishing attachment, a malicious download, a stolen password – uses the bug to escalate from an ordinary user account to SYSTEM, the highest level of control on a Windows machine. Once an attacker is SYSTEM, they can disable security tools, install ransomware across the network and reach the patient data on your server. That is why local privilege escalation is never “just” local. It is the hinge between a minor incident and a practice-ending one, and it is exactly why the foothold stage – the phishing email, the invisible-text phishing that slips past your spam filter – matters so much. Patch these two first. On the practice server and any machine that touches patient records, they go on tonight or first thing tomorrow, not at the end of the month.

A priority order for everything else

After the two exploited zero-days, you are not clearing 972 items by hand – you are sorting them. As Action1’s Jack Bicer put it, at this scale “the challenge is not simply getting through the patch list but knowing what needs attention first.” A sensible order for a dental practice:

1. The two exploited zero-days – server and record-handling machines, immediately. 2. Critical-rated flaws on anything internet-facing – your firewall-adjacent server, any remote-access tool, anything a patient or vendor can reach from outside. More than one in ten of this month’s fixes are rated critical, and the internet-facing ones are where an outsider can actually touch them. 3. Reachable workstations – reception and operatory PCs that open email and browse the web, because that is where the foothold usually starts. 4. The long tail – the hundreds of fixes for components you may not even run (SQL Server features, developer tools, server roles a small practice never enabled) follow your normal monthly cycle. Most of the 974 simply do not apply to a typical office, and the ones that do are handled by letting Windows Update run on your managed schedule.

The machines you can’t just reboot at 2 p.m.

The real friction in a clinical setting is not deciding to patch – it is when. You cannot force a restart on the PC driving a CBCT or an intraoral sensor in the middle of a patient’s appointment, and some older imaging devices cannot take the latest Windows updates at all. That is a scheduling and segmentation problem, not a reason to skip the update. Imaging and operatory machines get patched in off-hours with the vendor’s blessing on the version, and the devices that genuinely cannot be patched get walled off on a segmented network so a compromise elsewhere can’t reach them. It is also worth remembering that Patch Tuesday is a Microsoft event – your other computers-in-disguise patch on their own calendars. The same month we have been reminded to patch actively exploited flaws in practice routers and to update the VoIP phone system, which is a computer too. A complete patch posture covers all of it, not just Windows.

What this means for your practice

A 974-fix Patch Tuesday is a test of process, not heroics. A practice with a managed patching program barely notices a record month: the two exploited flaws get pushed on a priority ring, the criticals follow on a tight schedule, workstations update overnight, imaging machines patch in approved off-hours windows, and the long tail rides the normal cycle – all tracked, so you can actually prove the practice is current if PHIPA ever asks. A practice without that program faces the same 974 as a wall of noise, patches nothing, and leaves the two exploited bugs sitting open for weeks. That gap is the whole game. Compudent runs managed patching for dental practices across Ontario – prioritizing the flaws that are actually being exploited, scheduling around clinical hours, version-checking updates against your imaging vendors, and keeping the audit trail that proves you stayed current. If this month’s number made you wonder whether your practice is actually keeping up, contact Compudent for a patch-posture assessment – we will tell you where you stand and what, if anything, is still sitting open.

Sources & further reading:

• Microsoft Security Response Center – September 2026 Security Updates
• CyberScoop – Microsoft discloses two actively exploited zero-days among 974 vulnerabilities
• Trend Micro Zero Day Initiative – The September 2026 Security Update Review

Related Reading

• A Fake Job Offer, a Windows Kernel Rootkit: The Lazarus Zero-Day (CVE-2026-68820) and What It Means for Your Dental Practice
• February 2026 Patch Tuesday: Microsoft Fixes 6 Actively Exploited Zero-Day Vulnerabilities — What Dental Practices Need to Do Now
• When the Malware Rewrites Itself: AI-Accelerated Attacks and What They Mean for Your Practice

The post 974 Patches, Two Being Exploited Right Now: How a Dental Practice Should Read September’s Patch Tuesday appeared first on Compudent Systems.

A different kind of AI than the imaging tools

The first thing to be clear about is a distinction that matters for how you evaluate these products. Imaging AI – Pearl, Overjet’s detection engine, VideaHealth – makes a clinical claim about a patient’s radiograph, which is why those functions carry FDA clearances and are regulated as medical devices. Revenue-cycle and analytics AI makes no clinical claim. It parses a remittance, flags a likely denial, or charts your collections trend. That is administrative software, and it is not an FDA-cleared medical device – nor should you expect it to be. The right lens is not “is it cleared” but “is it accurate, and is it handling our data responsibly,” because the value of these tools comes entirely from reading the practice-management database, and that database is full of protected health information.

Job one: automating the revenue cycle

Revenue cycle management (RCM) is the end-to-end money loop – eligibility and benefits, claim creation and submission, adjudication, payment posting, and collections. AI is now applied as a layer across that loop rather than as a single tool. As RCM vendor Zentist puts it, AI in dental billing “isn’t a single tool, it’s a layer of intelligence applied across” the cycle – most visibly in automated payment posting that reconciles payments to claims and updates ledgers without staff keying it in (Zentist, How AI Is Transforming Dental RCM). The practical effect in an office is that the repetitive, error-prone administrative work – matching an insurance payment to the right claim and the right patient, updating the ledger, spotting the underpayment – gets done faster and more consistently than a busy front desk can manage manually. For a DSO running many locations on mixed systems, that consistency is often the whole point.

Job two: claims, denials, and reading the remittance

The sharpest pain in dental billing is denials, and this is where the current crop of AI is most concentrated. Zentist’s Remit AI, for example, automates EOB/ERA parsing, payment posting, and denial management, and the company reports use across more than 3,000 practices. “EOB/ERA parsing” is the unglamorous core of it: an explanation of benefits or electronic remittance advice arrives in dozens of payer formats, and AI reads it, extracts what was paid, adjusted, and denied, and turns it into a structured action – post this, appeal that. Overjet, better known for imaging, has built payer-facing RCM workflows on the same idea of using AI to reduce claim denials and improve billing accuracy (Overjet, Dental RCM with AI). Clearinghouse-based engines such as Vyne Trellis sit in the same lane. There is also a clinical-documentation crossover worth flagging: several major carriers now have workflows to process claims that include AI-generated clinical narratives and annotated radiographs, particularly for crown, perio, and implant cases where documentation quality drives approval – which is where the billing side and the imaging side of dental AI quietly meet.

Job three: analytics that turn the PMS into a dashboard

The third category is analytics – platforms that read your PMS and surface the KPIs a practice runs on: production, collections, case acceptance, hygiene reappointment, open treatment, no-show rates. Dental Intelligence, Practice by Numbers, and Jarvis Analytics are the recognizable names here, and their pitch is the same: eliminate the manual effort that normally stops a dental team from using its own data (Practice by Numbers, Dental Practice Analytics). The “AI” in this category ranges from genuine predictive modelling – which patients are likely to lapse, which treatment is likely to be accepted – down to automated morning-huddle briefings and trend alerts. Treat the marketing accordingly: a live, reliable dashboard of your real numbers is valuable on its own, whether or not every feature is truly predictive.

The integration reality: how these tools reach your data

This is the part that determines whether any of it works in your office, and it is the part the sales demo glosses over. Revenue-cycle and analytics AI has to read the PMS, and it does so in a few well-worn ways. Analytics platforms typically use a PMS bridge or a small practice-server agent – software installed on your on-site server that syncs data out to the vendor’s cloud. Denzif’s platform survey describes exactly this pattern: syncing with Dentrix, Eaglesoft, Open Dental, and Curve via a practice-server agent. Claims and RCM tools lean more on the insurance plumbing – clearinghouse connections and EDI transactions (the 837 claim, the 835 remittance) – to move data to and from payers. The critical caveat for buyers: not every vendor supports every PMS. As one 2026 buyer’s guide notes bluntly, most AI vendors integrate with Dentrix, Eaglesoft, or Open Dental “but not always all three,” which becomes a real constraint for a DSO that has inherited mixed systems through acquisition. Before you fall for a feature list, confirm the tool supports your PMS, on your version, with a sync method your IT setup can actually host.

What this means for your practice

Practice-management AI is, for many offices, the most immediately profitable slice of the dental-AI story – vendors report figures like a 25% lift in case acceptance and an 18x return (Overjet customer data, 2026), and while those are self-reported and should be read as directional rather than guaranteed, the underlying mechanics of fewer denials and faster posting are real and measurable in your own numbers. But every one of these tools earns its keep by reading the full ledger – patient names, procedures, insurance, payments – which makes each adoption a data-governance decision as much as an operations one. The same questions we apply to clinical AI apply here: a signed business associate or PHIPA agent agreement before any data flows, encryption in transit and at rest, a clear picture of where the data is hosted and who the subprocessors are, and an installed sync agent that your network is set up to run securely. That is the review Compudent does with dental clients before an RCM or analytics platform touches the PMS – confirming the integration fits your systems and that the data flow holds up under PHIPA and HIPAA. Our breakdown of Overjet’s RCM workflow and data governance works a single platform end to end, our guide to PHIPA, HIPAA, and dental AI vendor risk lays out the compliance homework, and our look at the AI front desk covers the patient-facing end of the same back office. If you are weighing a revenue-cycle, claims, or analytics tool and want the integration and vendor-risk work done properly first, contact Compudent for a practice assessment.

Sources & further reading:

• Zentist – How AI Is Transforming Dental Revenue Cycle Management
• Overjet – Dental Revenue Cycle Management with AI
• Overjet – Dental Practice Profitability with AI
• Practice by Numbers – Dental Practice Analytics

Related Reading

• PHIPA, HIPAA, and Dental AI: PHI, Data Governance, and Vendor Risk
• How Dental AI Tools Connect to Your Imaging Software: TWAIN, DICOM, API, and PMS Bridges
• The AI Front Desk: Call Intake, Scheduling, and Voice Agents in Dentistry

The post Practice-Management AI: Revenue Cycle, Claims, and Analytics appeared first on Compudent Systems.

What eAssist is, and why the target matters

eAssist is not a household name to patients, but it is deeply embedded in the back office of the profession. It provides outsourced billing, insurance-claim management, and collections for a large network of independent dental offices – the unglamorous financial plumbing that keeps a practice’s cash flow moving. To do that work, a billing outsourcer necessarily holds a rich file on every patient it touches: names, addresses, dates of birth, insurance policy details, procedure and diagnostic codes, and outstanding balances. That is a near-complete identity-and-insurance profile, and it is exactly the kind of data extortion crews prize. It is the same lesson we drew from the 284-million-record claim against supplier McKesson: the richest targets in healthcare are increasingly not the clinics themselves but the vendors that aggregate data from thousands of them.

Concentration risk: one vendor, hundreds of practices

This is the part that should reframe how you think about outsourcing. When you hand billing to a shared service, you are trading a bit of your own attack surface for a share of a much larger, more attractive one. A single administrative platform that manages workflows for hundreds of independent clinics is a concentrated choke point – compromise it once, and the attacker walks away with downstream data spanning every practice it serves. Your office may have excellent internal security; it does not matter to the patient whose insurance file was exfiltrated from a vendor’s server. Outsourcing a task does not outsource the accountability, and it certainly does not outsource the harm.

How Direwolf operates: steal first, encrypt second

Direwolf runs the now-standard double-extortion playbook, and understanding it explains why “we have backups” is no longer a complete answer. Rather than relying only on encryption to freeze a victim’s operations, the group first exfiltrates the valuable data – corporate documents, financial ledgers, and client or patient records – and only then deploys the encryption payload. Groups like this deliberately go after backup infrastructure, too, so that clean restores are difficult and the victim is squeezed from both sides: your systems are down and your data is already gone. Even a practice or vendor that recovers its systems flawlessly from backup still faces the second threat – public release of the stolen files. That is why immutable, offline backups matter, but also why they are only half the defense; we covered the backup and retention side of this in our guide to records retention, backups, and PHIPA in Ontario. The other half is preventing the theft in the first place. This is also why the response to a vendor breach is a compliance problem as much as an IT one – much like the FBI’s refreshed Medusa ransomware warning for healthcare, the technical event and the regulatory clock start together.

The uncomfortable truth: their breach can be your notification

Here is where practice owners are most often caught off guard. Under both U.S. HIPAA and Ontario’s PHIPA, a practice remains the custodian of its patients’ health information even when a third party processes it on the practice’s behalf. If a billing vendor holding your patients’ data is breached, your obligations – notifying affected patients, and in many cases regulators – are triggered by that event, not waived by it. The vendor’s contract may make them responsible to you, but to your patients and to the regulator, the duty of care still runs through your practice. That is the entire reason a written data-protection agreement exists between a custodian and its service providers – what U.S. rules call a Business Associate Agreement and what PHIPA frames through the custodian’s obligations to bind its agents. If you have never seen that document for your billing vendor, that gap is itself a finding. We walk through the governance side of these relationships in our piece on PHI, data governance, and vendor risk.

What to do this week

Whether or not eAssist is your vendor, this listing is a prompt to act. Take these steps in order:

1. Establish your exposure. Confirm whether your practice uses eAssist directly, or works with a billing partner who in turn subcontracts to it. Downstream relationships are exactly how practices end up affected without realising they were ever connected.

2. Demand a written status update. If you are a client, contact the vendor and ask, in writing, three specific questions: was any of our patient data involved, what categories of data, and what is the notification timeline. Keep the correspondence – you may need it for your own regulatory filing.

3. Pull your agreement. Locate the data-protection or business-associate terms in your contract and read what the vendor is obligated to do on a breach, and how quickly. If no such agreement exists, treat that as an urgent gap to close regardless of this incident.

4. Prepare, do not wait. If patient data was involved, ready your own breach-notification process now rather than after the vendor’s timeline slips. Identify which patients would be affected and draft the communications so you are not starting from zero under a regulatory clock.

5. Widen the audit. eAssist is one vendor among many with access to your patient data – your practice-management cloud, imaging archive, payment processor, and marketing tools all belong on the same list. Inventory who holds what, and confirm each has a written safeguarding agreement and a track record you can point to.

The takeaway for practice IT

The eAssist listing is a clean illustration of a risk that has quietly grown as dentistry has outsourced more of its back office: your security is only as strong as the weakest vendor holding your patients’ data, and their breach lands on your desk as a compliance obligation. The fix is not to stop outsourcing – shared billing services are often more capable than a small in-house team – but to treat every vendor relationship as an extension of your own security perimeter, governed by a real agreement and a real understanding of what they hold. The practices that will handle an incident like this calmly are the ones that already know their vendor list, their contracts, and their notification duties before the leak site posts.

Compudent Systems helps dental practices across the GTA and Ontario map exactly this: which third parties hold your patient data, whether each has an enforceable data-protection agreement, and what your notification obligations look like if one of them is breached. If a vendor incident has you unsure where your patients’ information actually lives, contact Compudent for a third-party risk assessment – the time to understand your exposure is before your billing company shows up on a leak site, not after.

Sources & further reading:

• Brinztech Alert – eAssist Dental Solutions Listed as Victim by Direwolf Ransomware Group
• HIPAA Journal – MCNA Dental data breach (dental-billing sector precedent)

Related Reading

• Ransomware Is Now a Patient-Safety Issue: What a 38% Hospital Mortality Study Means for Your Dental Practice
• Two Dental Groups on Leak Sites in One Week: What It Means When Your Practice’s Name Appears on a Ransomware Blog
• What a Data Breach Actually Costs a Dental Practice: The Bill Behind the Headline

The post Your Billing Company Is on a Leak Site: The eAssist/Direwolf Attack and Outsourced-RCM Risk appeared first on Compudent Systems.

The uncomfortable truth: the accountability does not leave with the data

The single most important thing to understand about both HIPAA in the United States and Ontario’s Personal Health Information Protection Act (PHIPA) is that they are built on the same principle: the practice that collects the patient’s information stays responsible for it, wherever it goes. Sending a radiograph to a cloud AI vendor does not transfer the legal duty to protect it. It extends your obligation to include that vendor’s conduct. An AI system tends to multiply the data flows that duty covers – the image or audio goes up, a result comes back, copies may be cached, logs are written, and in some architectures the data is retained to improve the model. Every one of those is a place where PHI lives, and every one of them is your responsibility to have accounted for. Good governance is not paranoia here; it is simply the mirror image of the accountability the law already assigns to you.

HIPAA: any AI vendor touching PHI is a business associate

Under HIPAA, a vendor that creates, receives, maintains, or transmits PHI on your behalf is a business associate, and you are required to have a signed business associate agreement (BAA) in place before that data changes hands. Practically every clinically useful dental AI tool meets this definition – imaging AI receives the radiograph, an AI scribe receives the consult audio, a claims or analytics tool receives the chart. There is a common and dangerous misconception that a vendor which only stores encrypted data, or which “cannot see” the content, falls outside this. It does not. The U.S. Department of Health and Human Services has been explicit that a cloud service provider handling PHI is a business associate even in a “no-view” arrangement where the data is encrypted and the provider holds no key – and a BAA is still required (HHS, Guidance on HIPAA & Cloud Computing). The relevant obligations sit at 45 C.F.R. §§ 164.308(b)(1) and 164.502(e).

AI raises the bar on what that BAA has to say. A boilerplate agreement written for a storage vendor may not authorize the way an AI platform actually moves data – to subprocessors, to a model-hosting environment, or back to the practice through a third-party integration. Health-privacy counsel now advise that the BAA should explicitly permit the contemplated upstream and downstream data flows of the AI operating environment, rather than leaving them to be inferred (Morgan Lewis, Healthcare AI Deployment). If a vendor will not sign a BAA, or will only sign one that is silent on how the AI itself uses the data, that is your answer.

PHIPA: you are the custodian, the AI tool is your agent

For an Ontario practice, the framework is PHIPA, and the vocabulary is different but the logic rhymes. Your practice is a health information custodian (HIC). A vendor that handles PHI on your behalf is your agent, and where it supplies the electronic services that let you collect, use, store, or dispose of PHI, it may specifically be an electronic service provider (ESP) – or, if it routes PHI between custodians, a health information network provider (HINP). The label matters less than the consequence: PHIPA keeps the custodian accountable for what its agents and service providers do with the information. You are expected to bind them by contract, to permit only the uses you actually authorize, and to exercise due diligence over their safeguards. An AI vendor operating as your agent is not a way to offload responsibility; it is an extension of your own compliance perimeter that you are on the hook to govern.

The cross-border question: where does the PHI actually go?

This is where Canadian practices get caught, because most of the marquee dental AI platforms are US-hosted. PHIPA does not prohibit storing or processing PHI outside Ontario or Canada – but it does require the custodian to remain accountable and to exercise real due diligence over the safeguards, transparency, and contractual controls that apply once the data leaves. Sending PHI to a US-hosted AI service also engages federal law: PIPEDA (and, for practices touching Quebec residents, Quebec’s Law 25) treats a transfer for processing as something you must handle with comparable protection and, increasingly, disclose. And there is a jurisdictional wrinkle that is easy to miss – data held by a US provider can be reachable under the US CLOUD Act regardless of where the servers physically sit, which is a real exposure most clinic owners have never modelled. None of this makes US-hosted AI off-limits. It makes three questions mandatory before adoption: in which country is the PHI stored and processed, which subprocessors and jurisdictions are in the chain, and can the vendor offer Canadian data residency if you need it?

The quiet risk: secondary use and training on your patients’ data

The compliance failure that rarely shows up in a demo is secondary use. An AI vendor may, by default, retain the images, audio, or notes you send and use them to train or refine its models. That can be entirely legitimate – de-identified data responsibly used improves the tools everyone relies on – but it is a use of PHI that you, as custodian or covered entity, have to have authorized and understood. “De-identified” is also a technical claim, not a marketing one: dental radiographs and CBCT volumes can carry embedded DICOM metadata (names, dates of birth, device identifiers) that has to be stripped properly for de-identification to mean anything. Before you sign, get a plain answer to a plain question: does the vendor use our patient data to train models, can we opt out, and if data is de-identified, exactly how? A vendor that treats that question as unreasonable is telling you something important.

A vendor-risk checklist to run before you sign

Governance for dental AI does not require a compliance department – it requires a short, repeatable checklist applied every time, translating the law above into questions a vendor can answer in writing:

• Signed agreement in place: a HIPAA BAA and/or a PHIPA agent/ESP agreement, signed before any PHI is shared – and one that names the AI-specific data flows, not a generic storage template.
• Encryption in transit and at rest: confirmed for the image, audio, or chart on the way out, in processing, and in any retained copy.
• Access controls and audit logs: role-based access on the vendor side and a log you can actually obtain that shows who or what touched the PHI.
• Data residency and subprocessors: where the data is stored and processed, the full subprocessor list, and whether a Canadian-hosted option exists.
• Retention, deletion, and training: how long PHI is kept, how it is destroyed on request or at contract end, and whether it is used for model training – with an opt-out.
• Breach notification: a contractual commitment to notify you promptly of any security incident, so you can meet your own reporting duties to the patient and the regulator.

What this means for your practice

Adopting AI in a dental practice is a genuine upgrade to care and efficiency – and it is also a moment where your responsibility for patient information quietly expands to include a new set of vendors. The practices that will look good in five years are the ones treating that as a routine, boring, documented step: identify the data flow, sign the right agreement, verify the safeguards, and keep the paper. That is exactly the review Compudent runs with dental clients before a new imaging AI, scribe, or voice agent goes anywhere near a patient record – mapping where the PHI travels, checking the BAA or PHIPA agent agreement covers what the tool actually does, and confirming the data-residency and vendor-risk picture stands up under PHIPA and HIPAA. Our breakdown of deploying Overjet with its data governance intact applies this discipline to clinical imaging AI, our guide to AI on the dental front desk covers the same questions for call intake and scheduling, and our comparison of AI scribes for dentistry shows where consult audio becomes PHI. If you are evaluating a dental AI tool and want the compliance and vendor-risk homework done properly first, contact Compudent for a practice assessment.

Sources & further reading:

• HHS – Business Associates (HIPAA)
• HHS – Guidance on HIPAA & Cloud Computing
• Morgan Lewis – Healthcare AI Deployment: Compliance Through Contracting, BAAs, and Data Governance
• Information and Privacy Commissioner of Ontario – PHIPA
• Office of the Privacy Commissioner of Canada – PIPEDA and transfers for processing

Related Reading

• Can Your Dental Practice Use ChatGPT Without Breaking HIPAA and PHIPA? A 2026 Compliance Guide
• Overjet in Your Practice: Integration, RCM Workflow, and Data Governance
• Practice-Management AI: Revenue Cycle, Claims, and Analytics

The post PHIPA, HIPAA, and Dental AI: PHI, Data Governance, and Vendor Risk appeared first on Compudent Systems.

What was actually found

The six flaws span the SSH server and client, the bandwidth-test service, X.509 certificate handling, and the WebFig management interface. CERT Polska highlighted three as the ones that matter most:

CVE-2026-67276 – SSH authentication bypass (CVSS 9.2). RouterOS did not properly verify the public keys used for SSH login; it failed to compare the entire RSA public key assigned to a user. An attacker who knew a valid username and the public modulus of that user’s key could craft a different key and log in without ever possessing the private key, inheriting that account’s privileges.

CVE-2026-86060 – SSH privilege manipulation via a crafted username (CVSS 9.2). RouterOS mishandled usernames beginning with a disallowed character during SSH login. By supplying a specially crafted username, an attacker could elevate their session to full administrative privileges.

CVE-2026-67277 – bandwidth-test memory disclosure and crash (CVSS 8.8). The bandwidth-test service let an unauthenticated connection reach a state that should only follow a successful login. Combined with a buffer-disclosure bug and an integer underflow, it enabled kernel memory leakage or a remote denial-of-service that restarts the device.

Combine the first two and you have MikroTrick: bypass authentication, then escalate to admin. Game over for that router – which, on a practice network, is the device that sees every packet between your operatory, your imaging server, and the internet.

Why a dental practice should care about a router bug

MikroTik hardware is popular in small and mid-size deployments precisely because it is capable and inexpensive – which is also why it turns up in dental offices, often installed years ago by a contractor and rarely touched since. That “set it and forget it” posture is the real exposure here. A router that owns your gateway can be used to sniff traffic, redirect DNS, pivot into your practice-management server, or sit quietly as a foothold for ransomware. This is the same lesson we walked through when the summer advisories landed – see our earlier breakdown, Is Your Practice Router a Backdoor? – except this time the flaws are being actively exploited, not just theoretically dangerous. The pattern of an internet-reachable management service becoming a live entry point is exactly what we described with the actively exploited flaw in practice phone systems: the edge device nobody thinks of as a computer is the one that gets taken.

The good news, and the catch

MikroTik’s default configuration blocks the SSH port from the internet, so a router left in its out-of-the-box state is not directly exposed to MikroTrick. The catch is how often that default gets changed. Someone opens SSH “temporarily” for remote support, adds a port-forward for a camera system, or loosens the firewall to get a stubborn service working – and the management plane ends up facing the public internet. If that describes any change ever made to your router, you are in scope. The confirmed attacks originated from a single IP address (82.192.72.4) and created a highly privileged user account named “ops” – a concrete sign to look for.

What to do right now

The fix exists and, per CERT Polska, patched devices are protected against the observed attacks. Take these steps in order:

1. Update RouterOS immediately. Fixes ship in 7.25 beta 3, 7.24.2, 7.23.4, and 6.49.21. Most devices will offer the upgrade under “Check for updates.” Do not defer this to next month’s maintenance window.

2. Get SSH off the internet. Confirm the SSH port is not reachable from untrusted networks. If you genuinely need remote management, restrict it to known trusted IPs, or – far better – close all management ports and reach the router only through a strong VPN such as WireGuard.

3. Check the ‘Flagged’ status. The patched releases add a mechanism that, at startup, scans the configuration for known signs of tampering, disables suspicious entries, and writes a critical log entry setting the device to “Flagged.” If your log shows a Flagged entry, follow MikroTik’s Flagged-status documentation and treat the device as compromised.

4. Hunt for the indicators of compromise. Even without a Flagged marker, inspect the router for anything you do not recognise. Watch for log lines like login failure for user -2 from <ip> via ssh and user <name> added by ssh:-2@<ip>, and for that rogue “ops” account. Also review users, scripts, scheduler tasks, proxy settings, and tunnels. Importantly, the absence of a Flagged marker is not proof of safety – the mechanism catches only selected traces.

If the device was compromised, patching is not enough

This is the step practices most often get wrong. If your router shows Flagged status, an unknown “ops” user, or any of the log indicators, assume the attacker had full control – which means credentials, VPN keys, and configuration secrets that passed through or lived on that device should be considered exposed. Simply upgrading the firmware does not evict an attacker who has already planted persistence. A compromised gateway calls for a full rebuild: reset to a known-good configuration, rotate every credential and key associated with the network, and review what else on the practice LAN that router could reach. Because MikroTrick hands over an administrative session, the blast radius is your whole network, not just one box. The same containment discipline we apply to segmenting legacy imaging devices applies here in reverse: a flat network with a compromised router means nothing downstream can be trusted until it is checked.

The takeaway for practice IT

MikroTrick is a textbook reminder that the network’s plumbing is a computer too, and it needs the same patch cadence and the same “no management ports on the public internet” rule as any server. The immediate actions are simple – update RouterOS, close SSH to the outside world, check for the Flagged marker and the “ops” user – but they only help if someone actually does them, and does them now while exploitation is ongoing. If you are not certain who last looked at your practice router, what version it runs, or whether any management port is exposed, that uncertainty is the finding.

Compudent Systems handles exactly this for dental practices across the GTA and Ontario: confirming your router’s firmware and exposure, closing off remote-management ports, standing up a proper VPN for support access, and checking a device for signs of the MikroTrick indicators before they become a breach. If your network gear has been running untouched for a while, contact Compudent for a security assessment – the best time to find an exposed router is before an attacker does.

Sources & further reading:

• CERT Polska – Critical vulnerabilities in MikroTik RouterOS are being actively exploited
• MikroTik security bulletin – September 2026 vulnerability (MikroTrick)
• MikroTik ‘Flagged’ status documentation

Related Reading

• Is Your Practice Router a Backdoor? What the New MikroTik RouterOS Advisories Mean for Dental Networks
• Ransomware Gangs Are Now Through the Front Door: What the SonicWall SMA1000 VPN Attacks Mean for Dental Practices
• A Forged Login Walks Straight Into SharePoint: What the Actively Exploited CVE-2026-55040 Auth Bypass Means for Dental Practices

The post MikroTrick: Six Actively Exploited MikroTik RouterOS Flaws – Patch Your Practice Router Now appeared first on Compudent Systems.

What an “AI scribe” actually is – and its two flavours

Before comparing vendors, separate two things that both get sold as scribes. The first is structured voice-command charting: the clinician speaks measurements or findings aloud – “three, two, three, bleeding on distal” – and the software drops them into the correct fields of a perio or restorative chart in real time. It is hands-free data entry with a fixed vocabulary. The second is the ambient conversation scribe: the tool listens to the natural back-and-forth of a patient consult and generates a narrative clinical note, typically in SOAP format, that the clinician reviews and signs. One fills structured fields; the other writes prose. A few platforms now do both, which is exactly why the category is confusing. Knowing which flavour you are buying tells you what changes at the chairside and what has to connect on the back end.

Bola AI – the dental-native voice specialist

Bola AI is built for dentistry first. Its headline products are Voice Perio and Voice Restorative – structured voice-command charting – alongside an ambient AI Scribe for clinical notes. The reason it matters to a practice-IT buyer is integration: Bola writes directly into the practice-management system’s own chart. Its Voice Perio integration with Open Dental drops perio data straight into the native Open Dental Perio Chart, and it maintains a parallel integration with Dentrix, so the readings land in your system of record in real time rather than in a separate app someone has to reconcile. That native, two-way PMS write-back is the differentiator – and it is a partner-gated integration, meaning Bola works where it has built and certified a bridge, not universally. Practical note for deployment: Bola depends on approved, high-quality microphones to hit its recognition accuracy in a noisy operatory, so the hardware is part of the rollout, not an afterthought.

Heidi – the horizontal scribe borrowed from medicine

Heidi (Heidi Health) is the odd one out, and deliberately so. It is a general-purpose ambient medical scribe used across primary care, specialty clinics, telehealth and even veterinary settings – dentistry is one audience among many, not the design centre. It listens to the consult, produces a SOAP or template-based note, offers an inline “Ask Heidi” assistant, and supports multiple languages. On compliance it is strong for a horizontal tool: HIPAA compliance with a Business Associate Agreement available on its paid Practice tier, plus stated adherence to PIPEDA (relevant for Canadian practices), GDPR and NHS standards, and enterprise certifications including SOC 2 and ISO 27001. What it does not do is deep, structured dental-PMS integration. Heidi produces an excellent note; getting that note into Dentrix or Open Dental generally means an EHR sync or copy-paste workflow, not automated structured charting. For a practice that mainly wants consult notes written faster and is comfortable moving them into the chart manually, that trade may be fine. For one that wants perio numbers auto-filled, it is the wrong tool.

Denti.AI – the all-in-one dental platform

Denti.AI bundles the most into one subscription: an ambient AI Scribe, Voice Perio charting, an AI receptionist, and Auto-Chart, its FDA-cleared imaging diagnostic. It is dental-native, Health Canada licensed, holds a US patent (No. 11,389,131), and competes hard on price at an entry point around $49 – with hygienists in particular praising the five-minute hands-free perio charting. The all-in-one framing is genuinely appealing for a practice that would rather manage one vendor than four. But it also creates the single most common accuracy error buyers make, which deserves its own section.

The regulatory point everyone gets wrong

An ambient scribe that transcribes a conversation and drafts a note is a documentation tool. It makes no diagnosis, so it is generally not regulated by the FDA as a medical device, and there is no 510(k) clearance number attached to the scribe itself – for Bola’s scribe, Heidi, or Denti.AI’s scribe alike. Where this trips people up is Denti.AI. Denti.AI genuinely holds FDA clearance, but that clearance covers its Auto-Chart imaging diagnostic – automated detection of caries, periapical radiolucencies, and bone levels across panoramic and intraoral radiographs – not the scribe or the voice charting. Conflating the two, and marketing an ambient scribe as “FDA-cleared,” is exactly the kind of claim a decision-maker should refuse to take at face value. Verify what the clearance actually covers, and treat the scribe and the diagnostic as separate products with separate regulatory status even when they ship in one platform. If a vendor cannot cleanly explain which of its features is cleared and which is not, that is your answer.

PHIPA, HIPAA, and where the audio goes

Regardless of which tool you choose, the compliance exposure is the same and it is real. The consult audio, the transcript, and the generated note are all protected health information the moment the recording starts. Under Ontario’s PHIPA and under HIPAA in the US, that PHI remains your practice’s responsibility even though a vendor is processing it. You need a signed data-processing agreement – a BAA in the US, the equivalent contractual safeguards under PHIPA – covering how consult audio is stored, who can access it, how long it is retained, and what happens to it when you leave. Because most of these platforms are US-based cloud services, data residency is a live question for a Canadian practice: if your patients’ consult recordings sit on US infrastructure, you are making a cross-border PHI transfer and you remain the accountable custodian. Confirm the retention policy, the BAA or PHIPA terms, and where the data physically lives – in writing, before go-live, not from a slide.

Which one fits which practice

The choice sorts cleanly once you know what you are optimising for. If your pain is perio and restorative charting speed and you run Open Dental or Dentrix, Bola AI’s native structured write-back is the tightest fit. If you want a single dental platform covering scribing, voice charting, imaging AI and the front desk – and you keep the regulatory distinctions straight – Denti.AI is the consolidation play, and its pricing makes it easy to pilot. If your priority is fast, high-quality narrative consult notes, you value multilingual support and mature compliance certifications, and you can live with a manual path into the chart, Heidi is the strong horizontal option. In every case the deciding factors are the same two Compudent flags on any dental AI: how cleanly it integrates with your exact PMS, and whether the vendor’s data handling survives a PHIPA review.

This is the kind of evaluation Compudent Systems runs for practices across the GTA and Ontario – matching an AI scribe to your existing PMS and workflow, confirming what integrates natively versus what means re-keying, and checking that consult audio and generated notes are handled in a way that stands up under PHIPA. For the wider picture, our sister site’s plain-language look at Denti.AI covers the patient-facing side, our guide to AI on the dental front desk tackles the same integration questions for scheduling and call intake, and our breakdown of deploying Overjet applies the same discipline to clinical imaging AI. If you are weighing an AI scribe and want the integration and compliance homework done properly first, contact Compudent for a practice assessment.

Sources & further reading:

• Open Dental – Bola AI integration
• Bola AI + Dentrix integration
• Denti.AI – Dental AI Scribe, Voice Perio & Imaging
• Heidi – AI care partner for clinical practice
• Best AI Scribe for Dentists (2026) – 9 Tools Compared

Related Reading

• The AI Front Desk: Call Intake, Scheduling, and Voice Agents in Dentistry
• How Dental AI Tools Connect to Your Imaging Software: TWAIN, DICOM, API, and PMS Bridges
• Practice-Management AI: Revenue Cycle, Claims, and Analytics

The post AI Scribes for Dentistry: Bola AI vs Heidi vs Denti.AI Scribe appeared first on Compudent Systems.

The ten-year rule, and the trap inside it

The baseline most Ontario practices work from is the RCDSO recordkeeping standard: a patient’s dental record must be retained for at least ten years after the date of the last entry. For a patient who was a minor, the clock is more generous – retention runs for ten years after the day the patient reached, or would have reached, the age of majority. Radiographs are part of the clinical record, so a bitewing series taken today is subject to the same decade-plus horizon as the written chart. Financial records live under a separate schedule entirely: the Canada Revenue Agency generally expects business records to be kept for six years. So a single patient visit can spawn two overlapping retention clocks running on different timelines.

The trap is that these are minimums, expressed in years, being applied to data that lives on hardware measured in months. A ten-year retention obligation quietly assumes that the drive, the server, the backup, the imaging software, and the file format will all still exist and still be readable a decade from now. None of that is guaranteed by default. Retention is a promise your IT has to be built to keep, not a checkbox in your PMS.

PHIPA makes retention an IT obligation, not a filing habit

PHIPA is where retention stops being a College standard and becomes a legal duty about how you hold the data. As a health information custodian, a dental practice must take reasonable steps to protect personal health information against theft, loss, and unauthorized use – for the entire time it is retained, and through the moment it is destroyed. That framing matters. Every year you keep a record, you are also on the hook to keep it secure. The obligation does not pause because a chart is inactive; an archived record from 2019 carries the same protection duty as the patient you are treating this afternoon.

This is why retention and security cannot be run as separate projects. An old radiograph archive sitting on an unpatched, unmonitored server in the back room is not “just storage” – under PHIPA it is live personal health information you are legally responsible for. The same discipline that governs your active systems has to reach the archive, or the archive becomes your weakest point.

Backups: the thing that saves retention, and the thing that breaks disposal

Retention has a recoverability requirement hiding inside it. Keeping a record for ten years is meaningless if a drive failure or a ransomware event wipes it in year four. This is where a genuine backup strategy earns its place: a primary copy on the practice server, a local backup for fast recovery, and an offsite or immutable copy that a network attacker cannot reach or encrypt. The immutable copy is the part practices most often skip and most often need – it is what lets you honestly say a decade of records will still exist after a bad day. And a backup you have never restored is a hope, not a plan; we have made the case before that your backups are only as good as your last test restore, and retention is exactly the obligation that assumption is protecting.

But backups cut the other way too. When a record’s retention period ends and you securely destroy it from the live system, copies of it usually still exist inside your backup sets and archives. Truly disposing of personal health information means accounting for those copies – either through backup rotation that ages them out on a defined schedule, or through a documented policy that treats backup-resident data as protected until it expires. A disposal process that only touches the production system, and quietly leaves ten years of the same record in cold storage, is not a disposal process.

Disposal is a compliance event, not a right-click

The end of a record’s life gets almost no planning attention, and it should get a lot. Under PHIPA, personal health information must be disposed of securely, in a way that makes reconstruction impossible. For paper, that means cross-cut shredding or a bonded destruction service, not the recycling bin. For digital records, “delete” is not disposal – a deleted file is typically still recoverable until it is overwritten. Secure digital destruction means cryptographic erasure, a verified secure wipe, or physical destruction of the media, ideally paired with a certificate of destruction you can produce if you are ever asked to prove it.

That paper trail is the point. If a former patient, the College, or the Information and Privacy Commissioner asks what happened to a record, “we think it was deleted” is not an answer. A dated destruction log, tied to a retention schedule, is. Disposal done properly is auditable by design.

Why keeping everything is now a liability, not a safety net

The old instinct – keep everything forever, just in case – made sense when the risk of holding data was near zero. It is not zero anymore. Every record you retain past its required life is additional blast radius on the day you are breached: more patients to notify, more data in the dump, more exposure in the class action. When we broke down what a data breach actually costs a dental practice, the size of the exposed dataset was a direct multiplier on the bill. Data you have already destroyed – lawfully, on schedule – cannot be stolen. Retention discipline is, in that sense, a security control.

There is a format problem lurking behind all of this too. A ten-year horizon means the imaging you capture today has to remain both stored and readable long after the sensor, the workstation, and possibly the software vendor have changed. Proprietary formats, orphaned imaging applications, and un-migrated archives can leave you technically compliant on retention but practically unable to open the file – which is its own failure. Planning storage for the long haul is part of the same conversation as building imaging storage infrastructure that can grow with the practice.

What a defensible retention program looks like

Pulling it together, a dental practice that can stand behind its records handling has a few things in place. A written retention schedule that reflects the RCDSO minimums, the age-of-majority rule for minors, and the separate CRA horizon for financial records. Storage and backups – including an immutable offsite copy – engineered to keep records both recoverable and secure for the full period. A disposal process that is scheduled, secure, and logged, and that accounts for backup-resident copies rather than pretending they do not exist. And a format-migration plan so that a decade-old radiograph is not just retained but openable.

None of this is glamorous, and none of it shows up in a treatment plan. But it is the difference between a practice that can answer a records question in minutes and one that discovers, mid-audit or mid-breach, that its policy was “keep everything and hope.” If you are not sure whether your retention, backup, and disposal setup would hold up to a PHIPA review, that is exactly the kind of assessment worth doing before someone asks. Contact Compudent Systems and we will map your current records lifecycle against what Ontario actually requires – and fix the gaps before they become the story.

Sources & further reading:

• RCDSO Standards of Practice and Guidelines (Dental Recordkeeping)
• Personal Health Information Protection Act, 2004 (Ontario e-Laws)
• Information and Privacy Commissioner of Ontario – Resources
• Canada Revenue Agency – Keeping records

Related Reading

• Can Your Dental Practice Use ChatGPT Without Breaking HIPAA and PHIPA? A 2026 Compliance Guide
• From Roentgen’s Lab to Your Practice Server: How Dental X-ray Imaging Became an IT Discipline
• The First Hours After a Data Breach: What an Ontario Dental Practice Must Do Under PHIPA

The post How Long Must You Keep a Patient Chart? Records Retention, Backups, and PHIPA in Ontario appeared first on Compudent Systems.

Why the phone is the front desk’s biggest leak

The numbers the vendors cite are uncomfortable because they are broadly true. Industry figures repeated across the category – including by Y Combinator-backed Arini – put missed inbound calls at roughly a third of a typical practice’s total, even in offices with staff dedicated to the phone, while something like 80% of appointments are still booked by voice rather than through an online form. A missed call at a dental office is rarely a patient who calls back; it is a patient who dials the next practice on the list. Every unanswered ring during a busy hygiene block, a lunch break, or after 5 p.m. is a booking that quietly went to a competitor. That is the gap this software is built to close, and it is why the category has attracted real funding and moved quickly.

What “AI front desk” actually means

The label covers three distinct things, and conflating them is the first mistake a buyer makes. The first is the voice agent: a conversational AI that answers the call, understands what the patient wants, and either books, reschedules, or routes them – the closest thing to an autonomous receptionist. The second is call analytics: software that records and transcribes calls, scores them, and flags missed opportunities and unbooked callers for staff to follow up. The third is the AI scheduling assistant, which may live in chat, SMS, or web and apply dental-specific booking logic – appointment types, provider rules, block scheduling – rather than a naive calendar lookup. Many products blend two or three of these, but knowing which layer you are actually buying tells you what changes on the front desk and what does not.

The vendors, sorted by type

The market splits cleanly into dental-native platforms and repurposed generic voice AI. On the dental-native side, Arini positions itself as a full AI receptionist answering calls in under 300 milliseconds with genuine dental scheduling logic and native PMS integration; Peerlogic comes from the call-analytics direction and pairs conversation intelligence with an AI scheduling assistant; and a growing field – Dentina, TrueLark, Weave, Viva AI and newer entrants like CallSara and HeyDonto – competes on how well it plugs into existing phone systems and practice software. The generic tier is any general-purpose VoIP or voice-AI tool retrofitted onto a dental office. The distinction matters for one concrete reason: as Peerlogic and others note, the dental-specific platforms do real-time, two-way integration with major practice-management systems, while generic VoIP-based tools typically do not. For a dental practice, an agent that cannot write a confirmed appointment back into the PMS is a fancier answering machine.

How it connects to your stack

This is the part a decision-maker has to interrogate, because “integrates with your PMS” hides a lot of variation. The meaningful question is whether the tool does two-way integration – reading live availability from Dentrix, Open Dental, Eaglesoft, Curve or your platform of choice, and writing a booked, correctly-typed appointment back – or whether it merely captures an intake and hands a human a to-do. Two-way is the difference between automation and a slightly smarter voicemail. Underneath that sits the telephony layer: some products replace or front-end your phone system, others ride on top of an existing VoIP setup, and that choice determines what has to change on your network, your number porting, and your call routing.

Unlike the imaging AI covered elsewhere in this series, front-desk tools are not TWAIN or DICOM integrations – there are no radiographs moving. What moves is scheduling data, patient contact details, and call audio, over cloud APIs and telephony. That is simpler on paper, but it means the integration risk is concentrated in two places: the fidelity of the PMS write-back (a mis-typed or double-booked appointment is worse than a missed call) and the reliability of the telephony hand-off (a dropped or mis-routed patient call is a live reputational event, not a background error). Confirm both against your exact PMS and phone setup before signing, not from the vendor’s list of logos.

It is not a medical device – but PHIPA and HIPAA still apply

Here is a genuine difference from the imaging side that cuts both ways. A front-desk voice agent makes no diagnosis, so it is not a regulated medical device and carries no FDA clearance – there is no 510(k) number to check, and any vendor implying otherwise is confused or careless. That lowers one bar. It does not lower the privacy bar. The moment a patient is on the line, the call recording, the transcript, the reason for the visit, and the scheduling record are all protected health information. Under Ontario’s PHIPA and under HIPAA in the US, that PHI does not stop being your responsibility because a vendor is processing it. You need a signed data-processing agreement – a Business Associate Agreement stateside, the equivalent contractual safeguards under PHIPA – covering how call audio is stored, who can access it, how long it is retained, and what happens on termination. And because most of these platforms are US-based cloud services, data residency is a live question: if call recordings and patient details are stored on US infrastructure, your practice is making a cross-border PHI transfer and remains the accountable custodian for it. That is a decision the principal dentist should make with the terms in writing.

What to check before you buy

A clean rollout comes down to a short, unglamorous checklist. Confirm true two-way integration with your specific PMS, and ask to see it write a correctly-typed appointment, not just read availability. Establish the telephony model – does it replace your phone system or sit on top, and what does number porting involve. Get the data agreement and residency terms in writing before go-live. Decide the escalation path: what the agent does when it cannot handle a call, and how cleanly it hands a genuinely urgent patient – a swelling, a knocked-out tooth, post-op bleeding – to a human. And set expectations internally that this is an assistive front-desk tool: it books, confirms, and captures after-hours demand, but your team still owns the judgment calls and the relationships. Practices that treat it as a revenue-recovery and coverage layer are happy; practices that expect it to replace the front desk wholesale are not.

Front-desk AI is the most immediately profitable slice of dental AI precisely because the problem it solves – missed calls equal missed patients – is so measurable. It is also the slice where the integration and compliance groundwork is easiest to skip in the excitement of a slick demo. This is the kind of evaluation Compudent Systems handles for practices across the GTA and Ontario: vetting how an AI receptionist will connect to your existing PMS and phone system, what it means for your network, and whether the vendor’s handling of call recordings and patient data stands up to a PHIPA review. For the wider picture, our sister site’s field guide to AI in dentistry maps the whole landscape, and our own breakdown of deploying Overjet walks through the same integration-and-governance discipline on the clinical side. If you are weighing an AI front desk and want the technical and compliance homework done properly first, contact Compudent for a practice assessment.

Sources & further reading:

• Arini – AI receptionist for dentists (Y Combinator)
• 7 AI Assistants for Patient Scheduling Efficiency in 2026 – Peerlogic
• Best Dental AI Receptionists 2026: Compared – Avized
• 10 Best Dental AI Virtual Receptionist Tools for Clinics 2026 – CloudTalk

Related Reading

• AI Scribes for Dentistry: Bola AI vs Heidi vs Denti.AI Scribe
• Practice-Management AI: Revenue Cycle, Claims, and Analytics
• PHIPA, HIPAA, and Dental AI: PHI, Data Governance, and Vendor Risk

The post The AI Front Desk: Call Intake, Scheduling, and Voice Agents in Dentistry appeared first on Compudent Systems.

The technique is called ASCII smuggling, and it does not rely on a new virus or a clever attachment. It relies on characters your screen refuses to draw. For a dental practice, where the front desk lives in its inbox and every message could plausibly be a patient, an insurer, or a supplier, that is a problem worth understanding before it lands.

What ASCII smuggling actually does

Unicode, the standard that lets your computer display every alphabet and emoji, contains a little-used range called the Tags block, running from U+E0000 to U+E007F. These are shadow copies of ordinary keyboard characters that are not meant to be shown to a reader. They take up space in the underlying data of a message, but they render as nothing at all.

Attackers exploit that gap between what is stored and what is seen. Take a word a filter might flag, such as “funding.” Insert one invisible tag character between “fun” and “ding,” and a human still reads “funding” without a flicker of difference. A security filter scanning for the literal string “funding,” however, no longer finds it. The word has been split by a character that exists in the data but not on the screen. The lure sails through, looking clean to the machine and normal to the person.

In the campaign researchers tracked, the hidden splits targeted financial keywords tied to business loans, credit lines, and advance funding, with the operation impersonating lenders and chasing small-business loan applicants. The volume was enormous and oddly corporate in its rhythm: it ran on weekdays, went quiet on weekends, and resumed on Mondays, peaking in late February before tapering off. The point is not the specific lure. The point is the delivery method, which works for any theme an attacker chooses next, including a fake insurance notice or a spoofed supplier invoice aimed squarely at a dental office.

Why the dental front desk is the target

Phishing follows the path of least resistance, and the front desk is a wide one. It is high-volume, so a receptionist processes dozens of messages an hour without time to scrutinize each. It is high-trust, because the job is to be helpful and responsive to patients and outside parties. And it is often high-turnover, so security habits reset with each new hire. Add a filter-evasion trick that makes a malicious email look ordinary to your defenses, and the last line of protection becomes a distracted human under time pressure.

The stakes are not abstract. A phished credential is rarely the end of an attack; it is the beginning. It is the doorway to your practice management system, your imaging archive, and the protected health information that PHIPA obliges you to safeguard. We have written before about how attackers turn a stolen login into session theft that quietly sidesteps multi-factor authentication, and about how a single breach translates into real dollars, downtime, and liability for a practice. ASCII smuggling simply makes the first step, getting the bait into the inbox unflagged, more reliable.

Why your existing filter may miss it

Most email security gateways were built to read text the way a person does and then match it against lists of known-bad words, domains, and patterns. That model is fast and effective against ordinary phishing. It is also precisely what invisible characters defeat, because the attacker is not hiding the malicious intent from a human; they are hiding the searchable text from the scanner.

The fix is a defense that normalizes a message before it judges it, stripping or accounting for non-printing Unicode so that “fun” plus an invisible tag plus “ding” is evaluated as “funding.” Heavy or unusual use of Unicode is itself a suspicious signal that mature filters can weigh. The question for your practice is not whether such defenses exist, but whether the specific configuration protecting your mailboxes today does this. That is a concrete thing to check rather than assume.

What a dental practice should do now

No single control stops this cleanly, so the answer is layers, each one catching what the others miss.

Confirm your email security normalizes Unicode. Ask whoever manages your mail platform, whether that is Microsoft 365, Google Workspace, or a third-party gateway, whether it strips or scores invisible and non-printing characters. If nobody can answer, that is the first gap to close.

Make stolen passwords less useful. Phishing exists to harvest credentials, so assume some will eventually leak. Phishing-resistant multi-factor authentication, ideally passkeys rather than SMS codes, limits the damage a captured password can do. Your practice website and portals are part of this too; treat them as the exposed surface they are, as we covered in how attackers forge logins into practice websites.

Give the front desk a verification habit, not just a warning. The most durable defense against a message that looks perfect is a rule that does not depend on how it looks: any request to change payment details, release records, or move money is confirmed through a known phone number, never by replying to the email. That habit neutralizes a flawless lure.

Test your response, not just your prevention. Know in advance who is called when a staff member clicks something, how a compromised account is locked, and how you would tell whether patient data was reached. A rehearsed response turns a scare into a contained incident.

The takeaway

ASCII smuggling is a reminder that attacker tradecraft keeps moving, and that a defense which only reads what a human reads will always be one trick behind. The reassuring part is that the countermeasures are not exotic. Well-configured email filtering, authentication that survives a stolen password, a front desk with a verification reflex, and a practiced response plan defeat this campaign and the next one built on the same idea. What matters is that these controls are actually in place and correctly tuned, not merely assumed.

If you are not certain whether your practice’s email security accounts for tricks like invisible-character evasion, or whether your authentication and response plans would hold up, that uncertainty is worth resolving before an attacker resolves it for you. Compudent Systems helps dental practices across the GTA and Ontario assess and harden their email security, authentication, and incident response. Contact us for a practical review of where your inbox defenses stand today.

Sources & further reading:

• Phishing Campaign Sends Millions of Emails Using Invisible Unicode to Evade Filters

Related Reading

• A ‘Half-Click’ Email Zero-Day Is Hitting Outlook Web Access. Here’s Why Dental Practices Should Care.
• They’re Calling Your Front Desk: How Voice Phishing Cracked a Healthcare Giant’s Microsoft Login
• Your Practice Website Is Part of Your Attack Surface: Hackers Are Forging Logins Into WordPress Right Now

The post Your Spam Filter Can’t See This: Invisible-Text Phishing Is Slipping Past Email Security appeared first on Compudent Systems.

What actually got cleared – and why it’s a trend, not a gadget

It helps to see this as a wave rather than a single product. The dental-dedicated MRI is the marquee item because it brings an entirely new, radiation-free modality to dentistry for soft-tissue and temporomandibular imaging. But it is landing at the same time as new FDA-cleared 3D imaging and AI-assisted detection tools that read radiographs and CBCT volumes for the clinician. The common thread across all of them is data density: MRI produces multi-image series, modern 3D units produce ever-higher-resolution volumes, and AI tools generate additional annotated derivatives of each study. None of this replaces your existing CBCT and sensors – it stacks on top of them. So the practical question for a practice isn’t “MRI, yes or no?” It is “is our infrastructure ready for imaging that is several times heavier than what we run today?” And that question deserves the same rigour as choosing which imaging modality your practice actually needs and when.

Why bigger images are an IT problem, not just a clinical win

A single 2D bitewing is a small file. A high-resolution CBCT volume is dramatically larger; an MRI series larger still; and an AI-annotated study adds yet another layer on top of the original. Individually, none of these is alarming – modern storage is cheap. The trap is the curve. Take a bigger average study size, multiply it by the number of studies your practice captures every day, and compound that across the years of retention a dental record requires, and you get an accumulation curve that climbs far faster than the gentle slope film-replacement radiography produced. Practices that sized their storage, network, and backups for 2D imaging and never revisited the assumption are the ones that get surprised – not by the first MRI scan, but by month eighteen, when the drive that was “plenty” is suddenly at ninety percent and the nightly backup no longer finishes before the team arrives.

The server and storage question

Start with where the images actually live. Many practices keep imaging on a local server or an imaging workstation acting as one, and that is perfectly workable – provided the capacity is planned against the new curve, not last year’s. The right conversation covers headroom (size for two to three years of growth, not this month’s footprint), architecture (local storage versus a proper PACS versus a hybrid that tiers older studies to cloud), and retention. Retention is not optional: under PHIPA and HIPAA, diagnostic images are part of the patient record and must be kept for years, so “we’ll delete old scans to make room” is not a storage strategy – it is a compliance problem. The goal is a storage plan that expects the growth, tiers it sensibly, and never forces a clinical-versus-capacity trade-off at the front desk.

The network and the workstation that has to open it

Big images have to travel, and then someone has to open them. On the network side, moving 3D volumes and MRI series between the modality, the server, and the operatory where the dentist reviews them puts real load on office cabling and switches that were fine when the heaviest traffic was a panoramic. On the workstation side, a review PC needs enough RAM and graphics capability to load and manipulate a large volume smoothly – a dentist rotating a CBCT or scrolling an MRI stack on an underpowered machine simply waits, and waiting at the chair is expensive. Underneath both sits the plumbing: the DICOM worklist and PACS pathways that route a study from capture to the right patient chart. When those are healthy the workflow is invisible; when they are undersized, every heavy new modality makes the stalls more obvious. The same data-flow discipline is exactly what makes AI imaging tools usable in practice, which is why integrating an AI platform like Overjet is as much an integration and data-governance project as a clinical one.

Backups and business continuity – the images are the record

Here is the part that is easy to skip and painful to relearn: the images are not a by-product of care, they are the clinical record, and larger datasets make protecting them both more important and more demanding. Bigger studies stretch backup windows – the nightly job that comfortably finished at 2 a.m. can start bleeding into the working day – and they raise the cost of whatever off-site or cloud copy you keep. That is not a reason to back up less; it is a reason to design the backup deliberately: a genuine 3-2-1 approach (multiple copies, more than one medium, at least one off-site and ideally immutable), sized for the new data volume, and – the step everyone forgets – tested restores, because a backup you have never restored is a hope, not a safeguard. This is also where new imaging meets old equipment on the same network. As you add heavier modern modalities, the aging units that cannot be updated still need containment, which is a discipline in its own right: keeping unpatchable legacy imaging devices safely segmented so the growing, valuable image store they sit beside stays protected.

The takeaway: size the IT during procurement, not after install

The single most useful habit a practice can adopt is to treat an imaging purchase as an IT project, not just a clinical one. Before the unit is ordered – not after it is bolted to the wall – ask what average study size it produces, how much daily volume that adds, whether the server has the headroom and the retention plan to absorb years of it, whether the network and review workstations can move and open the images without stalling, and how the backup window and cost change. None of these are reasons to hesitate on adopting better imaging; the diagnostic gains from radiation-free MRI and high-resolution 3D are real. They are simply the questions that separate a smooth rollout from a scramble six months later. Plan the infrastructure with the same care you plan the clinical use, and the new imaging becomes an upgrade instead of a surprise.

If your practice is weighing a new imaging modality – a dental MRI, a next-generation CBCT, or an AI platform layered on top of what you already run – and you want to know whether your server, network, and backups are ready for it, contact Compudent Systems. We help dental practices across Ontario size storage and networks for modern imaging, design PACS and backup strategies that meet PHIPA retention obligations, and make sure the infrastructure is ready before the equipment arrives – so the only surprise is how good the images look.

Sources & further reading:

• From the first dental MRI to orthodontic AI: Four FDA clearances reshaping dentistry – Oral Health Group
• Dentsply Sirona Advances Dental Imaging With MRI – Dentistry Today
• First-ever Dental Dedicated MRI Validated in Clinical Trial and Cleared by FDA for Advanced Soft-Tissue Diagnostics – Dentsply Sirona

Related Reading

• From Roentgen’s Lab to Your Practice Server: How Dental X-ray Imaging Became an IT Discipline
• FMX vs. CBCT: Which Dental Imaging Does Your Practice Actually Need, and When
• You Can’t Patch That Old Sensor or CBCT: How to Safely Keep Legacy Imaging Devices on Your Dental Network

The post The New Imaging Is Bigger Than Your Server: What Dental MRI and AI-Cleared Modalities Demand From Your Practice IT appeared first on Compudent Systems.