Dental Imaging Integration: A Developer's Guide to X-Ray and Imaging Data

The Growing Importance of Dental Imaging Data

Dental imaging generates an enormous volume of clinical data every day. A single practice captures periapical radiographs, bitewing series, panoramic images, cephalometric films, and increasingly, cone-beam computed tomography (CBCT) scans. Across the industry, billions of dental images are captured annually, each one containing diagnostic information that drives treatment decisions.

Historically, this imaging data has been locked inside proprietary software silos. Dexis stores images in its own database. Cliniview maintains a separate archive. OneView keeps its own repository. Accessing imaging data programmatically — to feed an AI model, populate a patient portal, or aggregate across multiple locations — has required custom integrations with each vendor's SDK, file system conventions, and database schemas.

That is changing. The rise of AI-powered diagnostic tools, cloud-based clinical decision support, and multi-location DSO platforms has created strong demand for standardized, programmatic access to imaging data. Developers building dental applications need a consistent way to query imaging records regardless of which capture hardware or software a practice uses. That is exactly what an imaging integration API provides.

Supported Imaging Platforms

CRMBridge currently supports three major dental imaging platforms, with additional integrations on the roadmap:

• Dexis (v9 and v10): The market leader in digital radiography. Dexis sensors and software are deployed in tens of thousands of practices across North America. Their platform captures intraoral radiographs, integrates with most major PMS platforms, and stores images in a proprietary database format. The CRMBridge integration supports both the legacy v9 architecture and the current v10 platform.
• OneView Imaging: A comprehensive image capture and management solution that supports both 2D and 3D imaging workflows. OneView is known for its sensor-agnostic approach, allowing practices to use hardware from multiple manufacturers within a single software interface. The platform provides robust image enhancement and measurement tools alongside its capture capabilities.
• Cliniview Imaging: KaVo Kerr's imaging workflow solution, widely used in practices that run KaVo or Kerr imaging hardware. Cliniview handles both 2D intraoral and panoramic radiographs as well as 3D CBCT volumes. Its tight integration with KaVo hardware makes it a common choice for practices that have standardized on the KaVo ecosystem.

Each of these platforms stores imaging data differently — different database schemas, file structures, and metadata conventions. The CRMBridge Imaging API normalizes these differences into a single, consistent data model so your application code does not need to account for platform-specific variations.

What Imaging Data Can You Access?

The Imaging API provides access to structured metadata and analysis results associated with dental images. Here is what you can retrieve:

Connecting to Imaging Data via API

Accessing imaging data follows the same authentication and request pattern as all CRMBridge API endpoints. Authenticate once, then query imaging records by patient, date range, or image type.

# Step 1: Authenticate with CRMBridge
POST https://api.crmbridge.ai/v1/auth
Content-Type: application/json

{
  "api_key": "your_api_key",
  "api_secret": "your_api_secret"
}

# Response: bearer token for subsequent requests
{
  "token": "eyJhbGciOiJIUzI1NiIs...",
  "expires_in": 3600
}

# Step 2: Retrieve imaging records for a patient
GET https://api.crmbridge.ai/v1/locations/loc_001/patients/pat_2287/imaging
Authorization: Bearer {token}

# Response: normalized imaging metadata
{
  "patient_id": "pat_2287",
  "imaging_platform": "dexis_v10",
  "total_images": 42,
  "studies": [
    {
      "study_id": "img_study_0891",
      "study_date": "2026-03-14",
      "type": "bitewing_series",
      "description": "4BW - Horizontal",
      "provider": "Dr. Sarah Chen",
      "images": [
        {
          "image_id": "img_10442",
          "type": "bitewing",
          "tooth_association": ["#2", "#3", "#4", "#5"],
          "captured_at": "2026-03-14T09:22:14Z",
          "dicom_uid": "1.2.840.113619.2.55.3.412..."
        },
        {
          "image_id": "img_10443",
          "type": "bitewing",
          "tooth_association": ["#12", "#13", "#14", "#15"],
          "captured_at": "2026-03-14T09:22:38Z",
          "dicom_uid": "1.2.840.113619.2.55.3.413..."
        }
      ],
      "ai_analysis": {
        "engine": "CariesDetectPro",
        "findings": [
          {
            "tooth": "#3",
            "finding": "interproximal_caries",
            "surface": "mesial",
            "confidence": 0.87,
            "severity": "early"
          }
        ],
        "bone_loss": {
          "detected": true,
          "regions": ["#2-distal", "#3-mesial"],
          "measurement_mm": 2.1
        }
      }
    }
  ]
}

The response includes structured metadata for every imaging study associated with the patient. Each study contains individual image records with tooth associations, DICOM identifiers, and any AI analysis results that have been generated by the imaging platform's diagnostic engine.

Key Use Cases for Imaging Integration

Programmatic access to imaging data opens up application categories that were previously impractical to build without deep, vendor-specific integrations:

AI-Powered Diagnostic Support

Feed radiograph metadata and AI analysis results into machine learning models for caries detection, periodontal disease staging, and endodontic pathology identification. By pulling structured findings from the imaging platform's built-in AI engine, your application can present diagnostic suggestions alongside the clinical image without needing to process raw pixel data directly.

Clinical Decision Support

Combine imaging findings with treatment plan data from the PMS to generate richer clinical recommendations. For example, if imaging AI detects early interproximal caries on tooth #3 and the PMS shows no restorative treatment planned for that tooth, your application can flag the discrepancy for the clinician's review.

Patient Education

Pull imaging records into patient-facing applications to support treatment explanations. When a patient can see which teeth have findings and understand the AI confidence scores behind a recommendation, treatment acceptance rates improve. Imaging metadata lets you build visual timelines showing how a condition has progressed across multiple visits.

Quality Assurance

Automate image quality checks by analyzing capture metadata — exposure parameters, sensor positioning consistency, and retake rates. Practices and DSOs can identify operators who may benefit from additional training and track quality metrics across providers and locations over time.

Multi-Location Image Archival

For dental service organizations managing dozens or hundreds of locations, the imaging API enables centralized image cataloging without requiring every location to run the same imaging software. Aggregate imaging metadata from Dexis at one location, OneView at another, and Cliniview at a third into a single, searchable archive.

Architecture Considerations

Before building on the imaging API, there are several architectural decisions and constraints to understand:

Image data vs. image metadata. The CRMBridge Imaging API provides structured metadata and analysis results, not raw image pixel data. You receive capture details, tooth associations, DICOM identifiers, and AI findings. If your application needs the actual image bytes (for rendering radiographs in a viewer, for example), you use the DICOM UIDs returned by the API to retrieve images from the practice's DICOM server or imaging platform directly. This separation keeps API payloads small and avoids transmitting large binary files through the REST layer.

HIPAA considerations for imaging data. Dental radiographs are protected health information. DICOM headers often contain patient name, date of birth, and other identifiers embedded in the file metadata. When your application stores or transmits imaging metadata, ensure you are handling it under a BAA with appropriate encryption in transit (TLS 1.2+) and at rest. If you are aggregating imaging data across locations, your data architecture must account for access controls that restrict queries to authorized personnel and locations.

Combining imaging with PMS clinical data. The most powerful applications merge imaging metadata with clinical records from the practice management system. A treatment plan from Dentrix or Eaglesoft, combined with AI caries detection results from the imaging platform, gives your application a complete clinical picture. CRMBridge uses consistent patient identifiers across both imaging and PMS endpoints, making cross-referencing straightforward.