Dental sensor-bridge integration: Carestream, Dexis, Sopro, and Schick

Most dental sensors come with their own desktop software — Carestream Dental Imaging, Dexis Imaging Suite, SoproImaging, Schick CDR. The software was designed when the PMS was a separate concern from the imaging workflow. In 2026, on a modern cloud-aware PMS, that desktop layer is in the way. Sensor-bridge integration is the technical pattern that removes it.

This article is for the clinical lead or IT person evaluating how to connect existing dental sensors to a new PMS. It pairs with DICOM in the chart vs a separate viewer — read that first if you haven't.

Why the manufacturer's desktop software is in the way

The traditional flow with manufacturer software in the loop:

1. Patient is in the chair, ready for an x-ray
2. Clinician opens the imaging app on the chairside PC
3. Search by patient ID or name to load their record (in the imaging app, separate from the PMS)
4. Click capture, take the radiograph
5. Image saves to the imaging app's database/folder
6. Clinician alt-tabs back to the PMS chart
7. Manually associates the image with the visit (or skips this — it's the bottleneck)

This pattern produces four costs:

• Two windows during chair time. Mental tax of juggling two systems while a patient is in front of you.
• Misfiled images.If the imaging app's patient context lags or is wrong, the image lands in the wrong record. Known failure mode.
• License costs per workstation. Most manufacturer software licenses per machine; multi-chair clinics pay per chair.
• Image lives in the imaging app, not the chart. The chart has a reference at best. Looking up a year-old radiograph means re-opening the imaging app.

What sensor-bridge integration means

Sensor-bridge means the PMS speaks the sensor's wire protocol directly — it doesn't need the manufacturer's desktop app in the loop. The flow:

1. Clinician is in the patient's chart, in the visit context
2. Click capture in the chart UI
3. The PMS triggers the sensor (USB or sensor-bridge driver)
4. Image arrives directly in the visit, attached to the patient's record
5. Capture metadata (kV, mAs, exposure) attached automatically

Total elapsed time, capture to display: under 5 seconds.

The four major sensor families

For Singapore practice, four sensor brands cover the vast majority of installations:

Carestream Dental

CS 8100 panoramic, RVG 6200/6500 intraoral, CS 9600 CBCT. Carestream supports two integration paths: TWAIN driver (universal but limited to single-image capture) and a dedicated Carestream SDK that exposes more capabilities (multiplexed capture, sensor metadata).

For a modern PMS, the SDK path is the right one — TWAIN works but loses the metadata richness. Ask vendors specifically: do you use the Carestream SDK or just TWAIN?

Dexis

Platinum, Titanium, the newer DEXIS IS 3800 wireless. Dexis is owned by Envista (Kavo Kerr family). Integration is via the DEXIS SDK. Like Carestream, ask whether the PMS uses the SDK properly or falls back to TWAIN.

Sopro

SoproCare, SoproLife (intraoral cameras with caries detection light), Sopix (intraoral sensors). Sopro is a Acteon brand. Integration is primarily TWAIN — Sopro's ecosystem is less developed than Carestream/Dexis SDKs. For Singapore clinics with Sopro intraoral cameras, the integration is usually feature-complete but not metadata-rich.

Schick

Schick 33, Schick AE, Schick Elite. Schick (now Patterson Dental) has a vendor SDK that's well-documented. Sensor-bridge support is reliable but installation requires proper driver matching to the specific sensor model.

The fallback: DICOM C-STORE / C-FIND

For sensors not directly supported by sensor-bridge, the DICOM standard fills the gap. C-STORE pushes images from sensor software into the PMS; C-FIND retrieves images for viewing. Slower than direct sensor-bridge (3–5 seconds vs sub-second capture-to-display) but interoperable across any DICOM-compliant device.

DICOM C-STORE/C-FIND is also the right path for legacy interop — receiving images from external referrers (orthodontists, oral surgeons), pushing images to OHIF Viewer for second opinions, archiving to a PACS server.

What to ask vendors

Five questions specific to sensor-bridge claims:

• Specific sensor model support.Not just “Carestream supported” — which model? CS 8100? RVG 6200? CS 9600 CBCT? List the exact ones supported.
• SDK or TWAIN? SDK gives metadata richness; TWAIN is universal but feature-thin.
• Capture latency target. Should be under 5 seconds chairside (ideally under 2). Ask for a live demo on their sensor.
• Failure mode. What happens if the PMS is offline or the sensor disconnects mid-capture? Is there a local cache that re-syncs, or does the image disappear?
• Image storage location.PMS server (ideally cloud) or local capture buffer? Cloud storage with chair-side latency < 5 seconds is the modern default.

The annotation question

Capturing the image is half the workflow. The other half is annotating it — measurements, marks, notes that write back to the visit record. Sensor-bridge integration that captures cleanly but loses annotation context (or requires a separate viewer for annotation) is incomplete.

A working in-record imaging stack lets the clinician annotate in the chart UI, with annotations stored alongside the image and tied to the visit. Pan, zoom, rotate, ruler, pen. Each annotation event is in the audit log (relevant for audit log purposes).

What to do next

List your existing sensors by model number. For each, ask any PMS vendor under evaluation: do you bridge directly, or do you rely on the manufacturer's software? If they bridge, which protocol (SDK or TWAIN)?

See the Oralstack integrations page for current sensor-bridge coverage, or the imaging workflow for the in-record imaging story.