How Intraoral Cameras Work with Your Dental Software

A practical guide to PMS, imaging software, imaging modules, bridges, intraoral cameras and ProDENT Capture.

An intraoral camera can show a live picture while its capture button does nothing. A photograph can also save successfully in imaging software without appearing in the practice management system. Understanding which component does which job makes both setup and troubleshooting easier.

The PMS manages the patient. Imaging software captures and stores the patient’s images. A bridge connects those systems when needed. The intraoral camera supplies the live view, and ProDENT Capture helps its physical button trigger the imaging software’s capture action.

These are different roles, not a list of programs every practice must install. Some systems combine several roles in one product.

1. Patient management and image management are different jobs

PMS stands for practice management system. It manages the patient’s broader practice record: identity, appointments, treatment information and billing. It is usually where the dental team starts by selecting a patient.

Imaging software is the environment used to acquire, view and store images for that particular patient. It may handle intraoral photographs alongside X-rays, CT scans and other image types, depending on its capabilities.

An imaging module is an imaging function inside a larger application. It may belong to a PMS or to a dedicated imaging suite. A camera or IOC module is the part that handles the intraoral camera. The word “module” describes how a function is packaged; it does not mean that a separate imaging product is always necessary.

For a concrete example, Planmeca Romexis provides an imaging environment that stores patient photographs and videos together with X-ray images. It contains imaging modules of its own.

2. A bridge connects systems; it is not the camera

When a practice uses separate patient-management and imaging applications, a bridge can connect them. A common task is to pass the selected patient’s information from the PMS and open the matching record in the imaging software.

Patient-selection connection:
PMS → bridge, when required → matching patient in imaging software

Principle Dental is a useful example. Its documented Sidexis integration uses Principle Bridge to open an existing patient in Sidexis or create the corresponding record. The camera then works with the imaging application’s supported acquisition setup.

Some integrations also return images to the PMS. Principle describes this capability for several supported imaging integrations. However, opening the right patient and transferring images back are separate capabilities. Do not assume that every bridge does both.

A PMS may display an image stored in another system rather than hold a second copy. Confirm where the original images are stored and how they are backed up. For the Principle-specific onboarding sequence, see our Bridge-first setup guide.

3. Video capture has an image path and a button-control path

In a video-capture workflow, the IOC supplies a live video stream to the application that takes the photograph. That application can be dedicated imaging software or an imaging module inside the PMS.

Here, “video capture” includes taking still photographs from the live stream. It does not necessarily mean recording a video clip.

The image path

IOC → supported video input / acquisition component → imaging software or IOC module → that patient’s image storage

The imaging application shows the preview, captures the selected image and completes its save process. A local acquisition component may be involved, depending on the software.

The physical-button path

IOC physical button → ProDENT Capture, where needed → capture action in the imaging software or IOC module

ProDENT Capture helps supported dental software respond to the camera’s physical button. It is the button-integration utility in this workflow, not the patient image archive.

The live video does not need to pass through ProDENT Capture before reaching the imaging application. The two paths work alongside each other: one carries the picture; the other tells the application when to capture it.

This separation is also reflected in Open Dental’s camera compatibility documentation, which discusses live video and button mapping separately.

A button response is not always the final save. Some applications distinguish between freezing a frame, taking a snapshot and saving it. The test is whether the completed photograph can be reopened under the correct patient.

4. Imaging software can come in several forms

Dedicated imaging software from an imaging-equipment supplier

The software supplied for an X-ray or CT system may also support an IOC. For example, Romexis supports multiple image sources and patient photo storage. The practice may therefore use one imaging environment for different kinds of patient images, with separate acquisition functions for each device.

In this arrangement, the IOC works with the imaging software; the PMS connection is a separate part of the setup. Camera support still depends on the software version, platform and available acquisition method.

An imaging or IOC module provided with the PMS

Some PMS products provide their own imaging environment, so the team does not need to move into an unrelated imaging package just to take a photograph.

Curve documents intraoral-camera capture within its Imaging workflow and requires its own local Curve Capture application for imaging devices. Praktika has a published camera-interface guide describing video-stream capture and TWAIN as two methods. That Praktika guide is historical; confirm current device settings with the provider.

Curve Capture and ProDENT Capture are not interchangeable. Curve Capture belongs to Curve’s acquisition system. ProDENT Capture helps the supported camera button operate the target dental application.

A browser-based system with a local imaging component

A cloud interface does not necessarily mean that nothing is installed on the workstation. Local software can connect the browser workflow to imaging applications or supported acquisition devices.

CareStack documents an installed CareStack Link for connecting clinical imaging software. It also offers Aeka, its cloud imaging system with intraoral-camera support. The local components required depend on which imaging configuration the practice uses; CareStack Link should not be mistaken for a complete standalone acquisition application.

The important distinction is functional: a local connector links systems, an acquisition component handles devices, and ProDENT Capture handles supported camera-button integration. One vendor may combine some of these functions in a single application.

5. TWAIN is a separate acquisition option

The video workflow above is not the only way to acquire an image. TWAIN is a long-established image-acquisition standard that links applications with imaging devices. In a TWAIN workflow, the application acquires images through a compatible device-specific TWAIN source.

Alternative acquisition path:
IOC → compatible TWAIN source → TWAIN-capable imaging software or module → that patient’s image storage

TWAIN is not the next required step after video capture, and it does not replace the PMS-to-imaging bridge. These are different layers. A TWAIN workflow may still use a bridge for patient information or image transfer; Principle explicitly provides TWAIN integration through Bridge.

ProDENT’s preference for IOC setup is a supported video-capture workflow first, with TWAIN available as a fallback when needed. We do not recommend adding a TWAIN layer simply because the physical button needs configuration.

Compatibility and reliability need checking for the exact camera, driver, operating system and application. An older standard is not automatically unreliable, and a direct connection is not automatically better. Some software providers recommend TWAIN for particular setups; Curve’s driver guidance is an example. Follow the supported configuration for the device in use.

ProDENT TWAIN and ProDENT Capture also do different jobs: TWAIN provides an acquisition option; Capture supports button operation. Ask support which package your configuration needs rather than installing both by default. The PD760 photograph above illustrates the hardware role; it does not establish TWAIN support for every PD760 variant.

6. Match the symptom to the right component

These are starting points, not guaranteed diagnoses. Use practice-approved test records and non-patient objects when checking the workflow.

When changing PMS, the camera and button settings may remain usable if the imaging application stays the same. The new patient connection and any image-return function still need testing. If the capture application changes, its video input and button configuration need checking again.

New photographs saving correctly does not prove that historical images have migrated. Keep the existing image library and access arrangements until the practice has verified both.

Get help with the right part of your setup

The most useful information to give support is:

“This is the application showing the live view. This is what happens when I press the camera button. This is where I expect the saved photograph to appear.”

Include the camera model, operating system and software versions when contacting ProDENT Support or cs@prodentshop.com. Involve your PMS or imaging provider for patient matching, system integration and storage questions. Remove patient-identifying details from screenshots.

Remember: patient management, image acquisition, physical-button control and image transfer are separate jobs. Identify the software doing each job, then configure only the components your practice actually needs.

---

Last updated: 6 September 2026. Product examples explain system roles, not universal compatibility or certification. Features depend on the camera model, operating system, software version, licensing and configured integration.