Dental Imaging Integration Troubleshooting: When Your PMS, DEXIS, Carestream, Vatech or Romexis Stop Talking

It is ten to eight, the first patient is in the chair, and the X-ray button in the chart does nothing. Yesterday it worked. Overnight something updated, and now the imaging company says to call IT while IT says to call the imaging company.

Start by finding the last step that still works: the patient opens in the practice management software (PMS), the bridge launches imaging, the sensor captures, the image saves, the image reopens, and a second workstation sees it. The first step that fails names the layer at fault and tells you who should act next.

This guide is written for the person who has to get the operatory running again. It gives you a symptom table, a short test for each layer, the checks to run after any update, an eight-step acceptance script with a sign-off line, and a table of who owns what, so the next call you make carries evidence instead of a guess.

Map the imaging chain before troubleshooting

Map the imaging chain by writing down each product the image passes through, in order: the PMS, the bridge or program link, the imaging application, the image database or shared folder, the acquisition workstation, the network between them, and the sensor or CBCT unit. Then test each hop in that order. The first hop that fails decides who investigates next.

Most imaging workflows cross at least three vendors and two computers. A capture in operatory four can depend on the PMS on the server, an imaging service on the same server or a separate one, a shared folder, the operatory workstation, a USB port and a driver. When people say "the imaging is down", they usually mean only one of those.

THE CLINICAL IMAGING SIGNAL PATH (IDENTIFY THE FAILURE HOP)

1. 1. Patient context: PMS. The chart that holds the patient and the button that starts imaging.
2. 1. Context passer: bridge. The program link that hands the patient's ID and name to the imaging program. In Open Dental this lives under Setup, Program Links, and the path it uses "will be used by all computers connected to the database, unless a Local path override is entered on an individual machine" (Open Dental manual, accessed 21 Oct 2026).
3. 1. Viewer and acquisition: imaging application. DEXIS, CS Imaging, EzDent-i, Romexis, Sidexis, Dolphin Imaging or the PMS's own imaging module.
4. 1. Database and repository: storage. The imaging database, the image folder or share, and its permissions.
5. 1. Drivers and USB port: workstation. Windows, the capture driver, the acquisition software or agent, and the USB port or interface box.
6. 1. Physical device: sensor or CBCT. The sensor, its cable, the panoramic or cone beam unit.
7. 1. Network: the path between them. The switch port, the cable, Wi-Fi where it should be wired, and the link to the server or cloud.

Which layer is at fault? A symptom-to-layer diagnostic table

Match what staff see to the row below, run the first test, and read the result. If the test passes, the fault is further down the chain; if it fails, you have found the layer. Each row ends with who should act next and the evidence to hand them, so a ticket opens with facts, not with "imaging is broken". That ticket is the hand-off between the imaging vendor and whoever provides your dental computer support, so include the failing hop and the test result.

Two of these rows come straight from vendor documentation. Open Dental's imaging devices page says a Dexis GxTwain device needs "Dexis" in the description, "otherwise xray images are inserted into mounts in reverse order". Its Dexis bridge page lists "Could not access C:\DEXIS\DEXIS.EXE" as a path or permission problem (Open Dental manual, accessed 21 Oct 2026).

Where to go for your imaging product

• • DEXIS: bridge launches, InfoFile errors and patient-number matching. See DEXIS IT support.
• • Carestream and CS Imaging: Trophy-path launches, storage path mismatches and 3D network load. See Carestream Dental IT support.
• • Vatech EzDent-i and Ez3D-i: loader paths that change between versions. See Vatech IT support.
• • Planmeca Romexis: the bridge option set at install time and database server sizing. See Planmeca Romexis IT support.
• • Dolphin Imaging: orthodontic imaging that opens without the right patient or cannot reach its image store. See Dolphin Imaging IT support.
• • More than one product, or not sure which layer: start with practice management software and imaging support.

If imaging will not launch from the PMS

When the PMS works but imaging will not launch from it, the fault usually sits in the bridge, the workstation's copy of the bridge path, the patient-context handoff or the imaging application itself. Open the imaging program directly first. If it opens on its own, the problem is the link between the two programs, not the imaging software.

Ask these questions before anyone reinstalls anything:

• • Does the imaging application open directly outside the PMS?
• • Does the issue affect one workstation or all?
• • Did the bridge or integration configuration change?
• • Can the workstation reach the imaging database or storage?
• • Did Windows, the PMS or the imaging software update recently?
• • Was the imaging software moved, reinstalled or upgraded to a new major version on the server or on this computer?

Then work through what the vendors document for the product you use. The details below are taken from each vendor's own pages, as of 21 October 2026.

Open Dental program links in general. The Program Links window "lists all the program bridges that can be linked from Open Dental", and the "Path of file to open" is the program's executable. That path applies to every computer on the database unless a computer has a local path override. A single stale override on one workstation produces the "works everywhere except room three" pattern. Open Dental also recommends a business associate agreement with a vendor before enabling its program link. Buttons can be hidden per clinic, so a multi-clinic office should check that the button is not simply hidden for that clinic.

DEXIS from Open Dental. The bridge writes patient data to an InfoFile and launches DEXIS with it. If you see "Could not access C:\DEXIS\DEXIS.EXE", Open Dental's page points to a wrong path or a user who lacks permission on the InfoFile folder, and lists fixes such as moving the InfoFile to a folder like C:\ProgramData\Dexis\InfoFile.txt. On Open Dental Cloud, the page says the bridge can fail to launch "and there is no error message", and that the InfoFile path for Cloud users is normally C:\Temp\InfoFile.txt and "cannot be blank". For DEXIS environments, see DEXIS IT support.

Carestream (Trophy) from Open Dental. Open Dental says to "also use this bridge for some Carestream products", recommends Trophy Enhanced, and says "the storage path must be set to exactly the same value as the database location within Trophy." Its suggested test is a Windows shortcut to TW.exe with the patient folder parameter: "This simulates exactly what Open Dental is doing. If this does not work, then Open Dental will not work either." The separate Carestream bridge is "only for Carestream Ortho/OMS", and its Patient.ini path "cannot exceed 150 characters". For Carestream environments, see Carestream Dental IT support.

Vatech EzDent-i from Open Dental. The loader file differs by version: EzDent-i 2.3.6 or older uses VTEzDent-iLoader32.exe, and 3.0.0 or newer uses VTE2Loader32.exe, while VTEzBridge.exe "can also be used for either version". An upgrade across that line can leave the old path in Program Links, so the button stops working while EzDent-i opens normally from its own icon. For Vatech environments, see Vatech IT support.

Planmeca Romexis from Open Dental. The bridge uses DxStart.exe, or DxStartW_64.exe if DxStart fails. Open Dental notes that when Romexis is first installed, a custom installation with the PmBridge option enabled is needed; otherwise you "call Planmeca support for help reinstalling Romexis with the PmBridge option enabled". The bridge "can only handle Latin characters", which matters for patient names with accents. For Romexis environments, see Planmeca Romexis IT support.

Dentrix, Eaglesoft and other PMS platforms. The same logic applies: confirm the imaging program opens on its own, then compare the bridge settings in the PMS with the imaging program's current install location on a working and a failing computer. The vendor's own bridge documentation is the reference; your IT provider and the PMS vendor's support line can confirm the exact setting names for your version. For the IT environment around those platforms, see Dentrix IT support and Open Dental IT support.

Why does imaging open on the wrong patient or create a new one?

Imaging opens on the wrong patient, or creates a duplicate, when the patient ID the PMS sends does not match the ID the imaging program holds. This is a patient-safety fault, not an inconvenience: an image attached to the wrong record can be read for the wrong person. Stop capturing for that patient until the IDs match.

The bridge passes an identifier, not a face. Open Dental's Dexis bridge can send either the PatNum or the ChartNum, and its page says the "patient numbers must be identical with those in Open Dental". Its Ez3Di bridge page says: "If the patient is not recognized by Ez3Di, a new patient is created in Ez3Di." In both cases the imaging window will open without an error, which is why this failure is easy to miss (Open Dental manual, accessed 21 Oct 2026).

Signs that the ID mapping is wrong:

• • The imaging window shows a different name, birth date or chart number than the chart that launched it.
• • A patient's image history is empty in the bridge but present when you search the imaging program directly.
• • Imaging contains two records for one person, one with old images and one with new.
• • The problem started after a PMS conversion, a merge of duplicate patients, or a change in the bridge's ID setting.

What to do: confirm which ID the bridge is set to send, check one affected patient in both systems, and give the PMS and imaging vendors the two IDs side by side. Renumbering or merging patient records is a vendor-guided job; Open Dental's Dexis page, for example, says that renumbering patient IDs needs Dexis version 10 or later. The acceptance script below includes a name check for exactly this reason.

If historical images are missing or slow

Historical images are missing or slow for one of two reasons: they do not exist where the software expects them, or they exist but cannot be reached quickly. Separate the two first. Search the imaging program directly for an affected patient, then open the image folder or share from the workstation. Each result points to a different owner.

Historical images often live outside the PMS, in an imaging database or a file repository. Storage path, permissions, database or index health and network performance all matter. In Open Dental, images and documents sit in the A to Z folder (by default OpenDentImages), "typically found on the C drive of the server", in patient folders named by last name, first name and PatNum. The manual warns "do not rename or move the files, or Open Dental will not know where to find them", and says that multiple computers need the folder shared. The Data Paths setting applies to every computer on the database, with a "Path Override for this computer" available per workstation (Open Dental manual, accessed 21 Oct 2026).

The last two rows match errors Open Dental lists on its A to Z folder page, including "Could not find the path to the AtoZ folder" and an office that "upgraded to Windows 10 and can no longer access the shared OpenDentImages folder".

If the images exist but are not protected, that is a separate problem worth fixing now. The image folder or database needs to be in the backup alongside the PMS database, and a restore of both should be tested. Our dental backup and disaster recovery checklist covers that test.

If a sensor works in one operatory but not another

A sensor that works in one operatory but not another is valuable evidence, because it rules out most of the shared chain. Compare the failing room with a working one: workstation, USB port or interface, driver, acquisition software version, network port, permissions and device connection. The difference between the two rooms is usually the fault.

Work through the comparison in this order, which goes from cheapest to most expensive:

• • Test the same sensor on a known-good workstation, if the vendor's procedure allows it.
• • Check for driver differences and Device Manager warnings.
• • Look for USB or interface power delivery problems: a different port, no unpowered hub, the cable seated at both ends.
• • Confirm the acquisition software version matches the working setup.
• • Confirm the PMS device setup for that computer. In Open Dental, sensors for direct capture are set under Setup, Imaging, Devices, and a device can be tied to a computer name, so a renamed or replaced computer can lose its device.
• • Check that no other imaging or capture program is already open on that computer before you capture.

Test the driver outside the PMS before you buy anything. Open Dental's imaging devices page says "only 32-bit TWAIN drivers are supported" and describes a test with Twacker outside Open Dental. If the capture fails there too, "the issue lies with the device or the device driver": reinstall the driver, then "reach out to an IT Professional or the device manufacturer". If Twacker works but Open Dental does not, the page says to contact Open Dental Support. That one test splits the problem between the device side and the PMS side, and it costs nothing.

Cloud PMS acquisition agents. On Dentrix Ascend, image acquisition depends on a locally installed Acquisition Agent, and the Imaging 125 release notes (released 17 Dec 2025) say some new features "may require an updated acquisition agent". The offline-mode page recommends the latest agent version and warns against selecting Exit on the agent icon after an offline capture. If one room runs an older agent than the others, check that first.

Practices sometimes replace sensors, cables, hubs and ports before anyone suspects software. A capture outside the PMS, on the same computer and on a known-good computer, tells you whether hardware spend will fix anything.

If CBCT or 3D imaging is slow, treat file size seriously

CBCT and 3D imaging is slow when storage, the network link or the viewing workstation cannot keep up with study size. Planmeca roughly estimates 9 MB per 2D image and 50 MB to 1 GB per 3D image. A cloud PMS does not remove local imaging infrastructure if rendering or the image database stays local.

The vendors put numbers on this. Planmeca's Romexis requirements page gives a "rough estimate" of about 9 MB per 2D image and 50 MB to 1 GB per 3D image, and recommends 2 x 1 TB RAID1 storage for a 3D server. Carestream's CS Imaging 8 requirements (SMA75 Ed07, May 2026) call for 100 Mb/s networking for 2D when the image database is on another computer, and 1 Gb/s when 3D volumes are present. On Dentrix Ascend, the Imaging 125 release notes list, under Fixes, an issue where "if the acquisition agent is not running, you cannot download a 3D volume", a reminder of how much 3D work depends on the local agent. (Vendor pages, accessed 21 Oct 2026.)

For the computers and servers behind these numbers, our guide to dental software system requirements goes through each platform's published requirements.

What should you check after a PMS, imaging or Windows update?

After any PMS, imaging or Windows update, check three things before the first patient: that each bridge path still points at the current imaging program, that the imaging service or acquisition agent is running, and that a test capture saves to the right patient. Then run the full acceptance script on every operatory that captures images.

Updates are one of the usual triggers behind "it worked yesterday". The release notes usually tell you in advance, if someone reads the right section. Open Dental's version 26.2 release notes are a clear example. Version 26.2 "was released as beta on 08/06/2026", and under Program Links they list, as of 21 October 2026:

• • "New bridge for Allied Star Connect"
• • "New imaging bridge to OrthoComposite"
• • "Removed support for Suni, an imaging solution that was only compatible with earlier versions of the Imaging Module"
• • "Removed the Ez3D-i Bridge due to compatibility issues"
• • "TigerView is compatible with Open Dental Cloud"

The same notes add "a new method to the latency test tool to measure average latency" and "new standalone tools to back up and restore MariaDB databases". Because 26.2 is a beta, the list can still change; check the current notes for the version you are installing. An office that relied on the Ez3D-i bridge and updates past it loses that button, even though the 2D EzDent-i bridge is a separate program link.

It is not only the PMS. Planet DDS publishes a knowledge-base article titled "Denticon Bridge is not functioning after updating to version 4.4 of Sidexis Imaging Solution": an imaging-side update broke the bridge while the PMS did not change. And a Vatech upgrade from EzDent-i 2.x to 3.x changes the loader file the bridge must call, as described above.

After-update checklist

If any line fails, stop there and send the result, the versions and a screenshot to the owner named in the responsibility table below.

Does a cloud PMS remove local imaging work?

No. A cloud PMS moves the chart off your server, but sensors, capture drivers and often the imaging software still run on the operatory computers. The bridge has to reach from the cloud session to local software, which adds a component to install, update and test. Plan the imaging test before a cloud move, not after it.

What the vendors say, as of 21 October 2026:

• • Open Dental Cloud requires that "ODCloudClient must be installed on a Windows machine to bridge to third-party softwares (such as imaging software…)", and lists 20 Mbps down and 10 Mbps up. Its integrations page says the listed integrations "are expected to work within Open Dental Cloud. Not all integrations have been tested." The imaging list includes Apteryx, Carestream, Dexis, DTX Studio, EzDenti, MiPACS, Planmeca, Romexis Bridge, Sirona Sidexis, TigerView, Trophy (Enhanced), VixWin and XVWeb Apteryx.
• • Open Dental's cloud differences page says the A to Z folder "is not stored locally", so imports come from the local workstation, and that in the Imaging Module "Video Capture is not available" and "Import Automatically is not available".
• • Open Dental's cloud page also says "the local computers that access the Open Dental Cloud are still fully managed by the practice or their IT."
• • Dentrix Ascend lists Windows 10 (64-bit) or 11, with 11 recommended; 8 GB RAM minimum and 16 GB recommended; 50 Mbps down and 10 Mbps up assuming 10 logons at one location; and TWAIN 1.9 or later for scanners. It notes that "single-image transfers, but not multiple-image transfers, are supported." Acquisition depends on the locally installed Acquisition Agent.

Cloud PMS imaging checklist

If you are weighing the move itself, our guide to replacing a dental server or moving to the cloud covers the decision, and planning a dental PMS migration cutover covers the go-live.

Post-change imaging acceptance script

Prove it by running one real workflow end to end and writing down the result: select a test patient in the PMS, launch imaging through the bridge, capture, save, reopen, then open the same image from a second workstation. Any server migration, PMS migration, workstation replacement, Windows upgrade, imaging update or network redesign should trigger this script.

The eight steps are short. Run them on every operatory that captures images, not only one, because a single stale path or driver passes in one room and fails in the next.

Imaging acceptance sign-off sheet

Print one sheet per change and keep it with the office's IT records.

A sheet like this turns "it seems fine" into evidence. When something breaks next month, the last passing sheet shows what changed since.

Who owns the problem? Use the responsibility matrix

The layer that failed decides who owns the fix. The PMS vendor owns its bridge settings and licensing, the imaging vendor owns its software, database and devices, your IT provider owns the computers, storage, network and backups, and the practice owns workflow acceptance. The test results above tell you which one to call first.

A clean split lets each party act on evidence instead of pointing at the other. It also keeps the proprietary parts with the companies that build them.

Vendor responsibility table: who acts and what they need

Legend Networking supports the IT environment around DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, and around Dentrix, Eaglesoft, Open Dental and Archy. What your own agreement covers when a fault sits in a vendor's layer is worth confirming in writing with any IT provider before you need it.

What happens when you add an operatory or acquire a practice with different imaging?

Adding an operatory or acquiring a practice with different imaging hardware is a change like any other: the new room or office has to pass the same acceptance script before it captures on patients. The difference is that you may have two imaging products, two ID schemes and two image stores to reconcile.

Before the first capture in a new room or newly acquired office:

• • List every imaging product, version and device in use, and which PMS bridges each one.
• • Check that each product appears in your PMS's bridge list and, for a cloud PMS, its integration list.
• • Decide where images will be stored, and how historical images will be reached or converted.
• • Agree which patient ID the bridge will send, before any images are captured.
• • Run the eight-step script on every new capture station and keep the sign-off sheet.

For groups, this is the same discipline across many offices; the owner page for practice management software and imaging support covers the IT side of mixed imaging environments.

What to ask your IT provider

Use these questions with your current IT provider, or with any provider you are considering. The answers show whether someone owns the imaging chain or only the computers around it.

1. 1. Which imaging products, versions and bridges do we run today, and where is that written down?
2. 1. Where are our images stored, and is that store in the backup with the PMS database? When was the last restore of images tested?
3. 1. Who reads the PMS and imaging release notes before an update, and who decides when it is installed?
4. 1. After an update, who runs the acceptance script, on which operatories, and where is the sign-off kept?
5. 1. When a sensor fails in one room, what is the first test you run, and do you run it before suggesting new hardware?
6. 1. If the fault is in the PMS or imaging vendor's layer, what evidence do you collect, and what does our agreement say about working with the vendor?
7. 1. Is every capture station wired, and does the network meet the imaging vendor's published figures for 3D?
8. 1. If we move to a cloud PMS, how will the bridge client or acquisition agent be installed, updated and tested on each computer?

About this guide

Written by Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.

Legend Networking: served over 3,500 practices since 2004 · in-house engineers; no outsourced first-level triage · 4.8 rating · 173 Google reviews.

Vendor details on this page are quoted from each vendor's own documentation as accessed on 21 October 2026; versions change, so check the current page for your version before you act.