Carestream Dental
Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
Carestream Dental — Implementation Playbook (DSO)
Carestream Dental Diagnostic Imaging AI Implementation Playbook
For Dental Service Organizations (15–50 Locations)
1. Executive Summary
What Carestream Dental Diagnostic Imaging AI Does
Carestream Dental's AI-powered diagnostic imaging platform integrates with your existing radiography workflow to automatically detect and highlight potential pathologies—including caries, periapical lesions, bone loss, and calculus—directly on digital radiographs. The system provides real-time clinical decision support, overlaying findings on 2D and 3D images with confidence scores, enabling providers to validate, override, or accept AI-assisted detections within their existing imaging workflow.
Why DSOs Specifically Benefit from Diagnostic Imaging AI
Scale Advantages:
- Standardized diagnostic protocols across 15–50 locations eliminate variability in detection rates between providers
- Centralized analytics reveal which locations are under-diagnosing and which may be over-diagnosing, enabling targeted intervention
- Bulk licensing negotiations typically yield 30–40% cost savings versus individual practice pricing
Standardization Benefits:
- AI establishes a consistent "second set of eyes" regardless of provider experience level or fatigue
- Reduces malpractice exposure by documenting AI-assisted detection at the point of care
- Creates defensible, reproducible diagnostic documentation for every patient encounter
Data Aggregation Value:
- Cross-location diagnostic pattern analysis identifies training opportunities and best practices
- Enterprise-wide trending of detection rates informs clinical quality initiatives
- Aggregated data supports value-based care contracts and payor negotiations
Expected Timeline: Decision to Full Deployment
| Phase | Timeline | Locations Covered |
|---|---|---|
| Pre-Implementation & Planning | Weeks 1–2 | N/A |
| Wave 1 Pilot | Weeks 3–6 | 2–3 locations |
| Wave 1 Optimization & Learning Capture | Weeks 7–8 | 2–3 locations |
| Wave 2 Expansion | Weeks 9–14 | 5–8 locations |
| Wave 3 Full Deployment | Weeks 15–22 | Remaining locations |
| Post-Launch Optimization | Weeks 23–30 | All locations |
Total timeline: 6–8 months for a 30-location DSO, with high-readiness organizations completing in as few as 5 months.
2. Pre-Implementation Checklist (Weeks 1–2)
Technical Requirements
Hardware Requirements
☐ Verify all imaging workstations meet minimum specifications:
- Processor: Intel Core i5 (8th gen or later) or AMD Ryzen 5 equivalent
- RAM: 16GB minimum (32GB recommended for 3D imaging)
- Storage: 500GB SSD with minimum 100GB free space
- Display: 1920x1080 resolution minimum; medical-grade monitors recommended for primary diagnostic stations
- GPU: Dedicated graphics card required for 3D CBCT AI analysis (NVIDIA GTX 1060 or better)
☐ Confirm compatible imaging equipment across locations:
- Carestream CS series sensors and panoramic units (native integration)
- Third-party sensors with TWAIN/DICOM compatibility
- CBCT units: Carestream CS 8100/8200/9600 series or DICOM-compliant alternatives
☐ ⚠️ Inventory all sensor models and firmware versions—legacy sensors may require firmware updates before AI integration
Software Requirements
☐ Document current imaging software versions at each location ☐ Verify compatibility with Carestream Dental Imaging Software v8.0 or later ☐ Confirm operating system compatibility (Windows 10 Pro 64-bit or later) ☐ 🔵 Request vendor compatibility matrix for your specific software stack
Network Requirements
☐ Minimum 100 Mbps symmetric internet connection per location (1 Gbps recommended) ☐ Latency under 50ms to Carestream cloud endpoints ☐ Firewall rules allowing outbound HTTPS (port 443) to Carestream domains ☐ ⚠️ Verify VPN configurations don't conflict with cloud connectivity
Enterprise-Level Requirements (DSO-Specific)
Network Standards Across Locations
☐ 🟣 Determine hosting model: centralized vs. location-level
- Centralized hosting: AI processing occurs in DSO data center; requires robust WAN
- Location-level hosting: AI processing at each location; requires per-site licensing
- Hybrid cloud: Processing occurs in Carestream cloud; requires reliable internet per location
☐ Document network topology for each location (MPLS, SD-WAN, direct internet) ☐ Establish minimum bandwidth standards that all locations must meet before rollout ☐ Create network remediation plan for locations below threshold
Identity and Access Management
☐ 🔵 Confirm Carestream SSO compatibility with your identity provider (Azure AD, Okta, etc.) ☐ Define role-based access control (RBAC) structure:
- Enterprise Admin (central IT)
- Regional Admin (regional managers)
- Location Admin (office managers)
- Provider (read/write clinical access)
- Viewer (read-only for auditing)
☐ Establish centralized credentialing workflow for new providers ☐ 🟣 Decide on credential ownership: central IT manages vs. locations manage their own users
Vendor Onboarding Steps
☐ 🔵 Schedule enterprise kickoff call with Carestream DSO account team (Week 1, Day 1–2)
- Attendees: VP of Operations, CDO, IT Director, Carestream Enterprise Account Manager, Implementation Lead
- Agenda: Scope confirmation, timeline review, resource allocation, communication plan
☐ 🔵 Establish key vendor contacts:
| Role | Purpose | Expected Response Time |
|---|---|---|
| Enterprise Account Manager | Strategic issues, escalations, contract matters | 4 hours |
| Implementation Project Manager | Day-to-day rollout coordination | 2 hours |
| Technical Integration Specialist | API, integration, configuration support | 4 hours |
| Tier 2 Support | Complex technical issues | Same business day |
| Clinical Applications Specialist | Provider training, workflow optimization | 24 hours |
☐ 🔵 Obtain enterprise support portal access and train internal team on ticket submission ☐ 🔵 Confirm dedicated implementation resource allocation from Carestream
Data/Access Prerequisites
☐ Compile administrator credentials for all practice management systems ☐ Document API access or HL7/DICOM integration credentials for each PMS ☐ 🔵 Request Carestream API keys and integration documentation ☐ ⚠️ Verify imaging archive access—some locations may have images stored in legacy systems requiring migration ☐ Inventory historical imaging data volume per location (for migration planning) ☐ Confirm DICOM server configurations and accessibility
Stakeholder Alignment Map
Board/Investors
| Action | Owner | Timeline |
|---|---|---|
| ☐ 🟣 Present AI investment thesis and expected ROI | CEO/CDO | Week 1 |
| ☐ 🟣 Obtain budget approval for enterprise deployment | CFO | Week 1 |
| ☐ Establish quarterly reporting cadence on AI adoption | VP Operations | Week 2 |
C-Suite
| Action | Owner | Timeline |
|---|---|---|
| ☐ 🟣 Align on diagnostic standardization objectives | CDO | Week 1 |
| ☐ 🟣 Approve change management approach and communication plan | VP Operations | Week 1 |
| ☐ Define executive sponsor responsibilities | CEO | Week 1 |
Regional Managers
| Action | Owner | Timeline |
|---|---|---|
| ☐ Brief on rollout strategy and their role in location selection | VP Operations | Week 2 |
| ☐ Identify potential pilot locations based on initial criteria | Regional Managers | Week 2 |
| ☐ Establish escalation protocols and communication cadence | VP Operations | Week 2 |
Location-Level Office Managers
| Action | Owner | Timeline |
|---|---|---|
| ☐ Communicate upcoming initiative (high-level) | Regional Managers | Week 2 |
| ☐ Request baseline metric data collection | Central Analytics | Week 2 |
| ☐ Identify potential local champions | Office Managers | Week 2 |
Providers
| Action | Owner | Timeline |
|---|---|---|
| ☐ Initial communication from CDO on clinical rationale | CDO | Week 2 |
| ☐ Address common concerns about AI in clinical decision-making | CDO | Week 2 |
| ☐ Identify provider champions for pilot locations | Regional Managers | Week 2 |
Baseline Metrics Collection
⚠️ Critical: Baseline metrics must be captured BEFORE any AI deployment to enable accurate ROI measurement.
☐ Establish standardized measurement methodology across all locations:
| Metric | Definition | Data Source | Collection Method |
|---|---|---|---|
| Case Acceptance Rate | Percentage of diagnosed treatment plans accepted by patients | PMS | Monthly report |
| Average Diagnosis Time | Time from image capture to treatment plan documentation | PMS + time tracking | Sampling study |
| Pathology Detection Rate | Number of caries, periapical lesions, etc. per 100 radiographs | PMS/Clinical notes | Chart audit |
| Missed Diagnosis Rate | Pathologies identified on subsequent visits that were present on prior images | Chart review | Retrospective audit |
| Claim Denial Rate (diagnostic codes) | Percentage of claims denied for imaging-related diagnostic codes | RCM system | Monthly report |
| Retreatment Rate | Percentage of treatments requiring retreatment within 12 months | PMS | Quarterly report |
| Patient Chair Time for Diagnosis | Average minutes from seating to diagnosis discussion | Time study | Sampling study |
☐ Designate central analytics resource to aggregate and normalize baseline data ☐ Create baseline data collection template for locations to complete ☐ ⚠️ Verify data definitions are applied consistently—"case acceptance rate" calculations vary widely ☐ Complete baseline data collection for ALL locations, regardless of rollout wave assignment ☐ Store baseline data in centralized repository for future ROI analysis
3. Location Readiness Assessment
Scoring Framework
Each location should be evaluated across five dimensions. Score each factor 1–5 using the criteria below, then calculate a composite readiness score.
Factor 1: IT Infrastructure Maturity (Weight: 25%)
| Score | Criteria |
|---|---|
| 5 | Gigabit internet, hardware <2 years old, current PMS version, centralized IT support model |
| 4 | 500 Mbps+ internet, hardware <3 years old, PMS within 1 version of current, some central IT oversight |
| 3 | 100 Mbps internet, hardware <5 years old, PMS within 2 versions of current, local IT management |
| 2 | 50 Mbps internet, hardware 5–7 years old, PMS outdated, minimal IT support |
| 1 | <50 Mbps internet, hardware >7 years old, legacy PMS, no dedicated IT support |
Factor 2: Staff Tenure and Adaptability (Weight: 20%)
| Score | Criteria |
|---|---|
| 5 | <15% annual turnover, history of successful tech adoption, team stability >3 years average tenure |
| 4 | 15–25% turnover, positive tech adoption history, 2–3 years average tenure |
| 3 | 25–35% turnover, mixed tech adoption history, 1–2 years average tenure |
| 2 | 35–50% turnover, history of tech adoption challenges, <1 year average tenure |
| 1 | >50% turnover, failed tech implementations, constant staff churn |
Factor 3: Patient Volume (Weight: 15%)
| Score | Impact Assessment | Risk Assessment | Net Score |
|---|---|---|---|
| 5 | High volume (>150 patients/day): maximum ROI potential | Higher risk if issues occur | 5 if strong other scores |
| 4 | Moderate-high volume (100–150 patients/day) | Moderate risk | Ideal for pilots |
| 3 | Moderate volume (75–100 patients/day) | Balanced risk | Good for pilots |
| 2 | Lower volume (50–75 patients/day) | Lower risk | Consider for later waves |
| 1 | Low volume (<50 patients/day) | Minimal risk | May not justify early investment |
Note: Volume scoring is contextual—high volume is advantageous only when other readiness factors are strong.
Factor 4: Existing Tech Stack Compatibility (Weight: 25%)
| Score | Criteria |
|---|---|
| 5 | Carestream imaging hardware, modern PMS with proven integrations, digital workflows established |
| 4 | Carestream imaging or fully DICOM-compliant third-party, compatible PMS, mostly digital |
| 3 | Mixed imaging equipment with DICOM capability, PMS requires minor configuration, transitioning to digital |
| 2 | Older imaging equipment requiring firmware updates, PMS integration challenges expected |
| 1 | Legacy imaging equipment without DICOM, PMS with no integration capability, predominantly paper-based |
Factor 5: Local Champion Availability (Weight: 15%)
| Score | Criteria |
|---|---|
| 5 | Tech-forward dentist owner/lead + engaged office manager, both enthusiastic about AI |
| 4 | Either strong provider champion OR strong administrative champion |
| 3 | Neutral leadership willing to support but not actively championing |
| 2 | Skeptical leadership requiring significant change management effort |
| 1 | Actively resistant leadership, history of blocking technology initiatives |
Composite Score Calculation
Composite Score = (IT × 0.25) + (Staff × 0.20) + (Volume × 0.15) + (Tech Stack × 0.25) + (Champion × 0.15)
Readiness Categories
| Composite Score | Category | Rollout Recommendation |
|---|---|---|
| 4.0 – 5.0 | High Readiness | Wave 1 candidate |
| 3.0 – 3.9 | Moderate Readiness | Wave 2 candidate |
| 2.0 – 2.9 | Lower Readiness | Wave 3 candidate with remediation |
| 1.0 – 1.9 | Not Ready | Remediation required before rollout |
Recommended Rollout Sequence
☐ Compile readiness scores for all locations (use standardized assessment template) ☐ Sort locations by composite score, high to low ☐ Identify Wave 1 candidates from high-readiness locations:
- Select 2–3 locations representing different practice profiles (general, specialty mix)
- Ensure geographic distribution if possible (tests regional support capacity)
- Confirm champion availability and commitment
☐ ⚠️ Avoid selecting only "best" locations for Wave 1—include at least one location with minor challenges to stress-test support processes ☐ Document remediation requirements for lower-readiness locations ☐ Create remediation timeline aligned with their target wave
Sample Location Assessment Output
| Location | IT Score | Staff Score | Volume Score | Tech Score | Champion Score | Composite | Wave |
|---|---|---|---|---|---|---|---|
| Springfield Main | 5 | 4 | 4 | 5 | 5 | 4.6 | 1 |
| Riverside Family | 4 | 5 | 3 | 4 | 4 | 4.05 | 1 |
| Oakwood Dental | 4 | 3 | 4 | 4 | 3 | 3.65 | 2 |
| ... | ... | ... | ... | ... | ... | ... | ... |
4. Rollout Strategy
Wave Structure Recommendation
For a 30-location DSO, we recommend the following wave structure:
| Wave | Locations | Duration | Purpose |
|---|---|---|---|
| Wave 1 (Pilot) | 2–3 locations | 4 weeks | Validate integration, refine training, identify issues |
| Learning Capture | — | 2 weeks | Document lessons, update playbooks, remediate issues |
| Wave 2 | 5–8 locations | 5 weeks | Scale validated approach, test regional support |
| Wave 3 | 8–12 locations | 5 weeks | Continue expansion with refined processes |
| Wave 4 | Remaining locations | 4–6 weeks | Complete deployment |
Wave 1 Pilot Selection Criteria
☐ 🟣 Select 2–3 pilot locations meeting ALL of the following:
- Composite readiness score ≥ 4.0
- Confirmed local champion (provider + office manager commitment)
- Geographic accessibility for vendor and central team support
- Representative of broader portfolio (at least one GP-focused, one with specialty mix)
- Not flagship or highest-revenue location (contains pilot risk if issues occur)
- Not lowest-performing location (creates confounding variables)
☐ Document selection rationale for executive reporting ☐ Secure explicit commitment from pilot location leadership
Detailed Wave Timeline
Wave 1 Timeline (Weeks 3–8)
| Week | Activities |
|---|---|
| Week 3 | 🔵 Vendor on-site installation at Pilot 1; local configuration; initial technical validation |
| Week 4 | 🔵 Vendor installation at Pilots 2–3; champion training begins |
| Week 5 | Go-live at all pilot locations; daily check-ins; intensive support |
| Week 6 | Active monitoring; first workflow refinements; staff feedback collection |
| Week 7–8 | Learning capture; metrics analysis; documentation updates; Wave 2 preparation |
Wave 2–4 Timeline (Weeks 9–22)
Subsequent waves follow a compressed timeline leveraging pilot learnings:
| Week | Wave 2 (5–8 locations) | Week | Wave 3 (8–12 locations) | Week | Wave 4 (remaining) |
|---|---|---|---|---|---|
| 9–10 | Installation & configuration | 14–15 | Installation & configuration | 19–20 | Installation & configuration |
| 11 | Go-live | 16 | Go-live | 21 | Go-live |
| 12–13 | Optimization | 17–18 | Optimization | 22 | Optimization |
Go/No-Go Criteria for Wave Advancement
☐ 🟣 Before advancing from Wave 1 to Wave 2, confirm:
| Criteria | Threshold | Status |
|---|---|---|
| Technical stability | <2 critical issues per location in final 2 weeks | ☐ Met |
| Provider adoption | 100% of providers using AI-assisted diagnosis | ☐ Met |
| Staff training completion | 100% of staff completed role-specific training | ☐ Met |
| Workflow integration | AI integrated into standard workflow (no workarounds) | ☐ Met |
| Champion confidence | Champions report readiness to support new locations | ☐ Met |
| Patient impact | Zero patient-facing issues attributable to AI deployment | ☐ Met |
☐ If any criteria not met, extend Wave 1 by 1–2 weeks and remediate ☐ Document decision rationale whether advancing or extending
Rollback Plan
Trigger conditions for rollback consideration:
- Critical system failure affecting >50% of imaging workstations
- Data integrity issues (lost images, corrupted annotations)
- HIPAA compliance breach
- Provider revolt (>50% of providers refusing to use system)
- Patient safety concern
Rollback procedure:
- Central IT disables AI functionality via configuration (immediate)
- Location reverts to pre-AI imaging workflow
- Carestream notified of issue and severity
- Root cause analysis initiated
- ⚠️ Other wave locations continue without interruption (issues are location-specific)
- Remediation plan developed before re-attempting deployment
- 🟣 Executive decision required to resume rollout
5. Configuration & Integration (Weeks 2–3)
Practice Management System Integration
Dentrix Enterprise Integration
| Step | Action | Time Estimate | Owner |
|---|---|---|---|
| 1 | ☐ Verify Dentrix Enterprise version compatibility (v22 or later required) | 30 min | Central IT |
| 2 | ☐ 🔵 Obtain Carestream-Dentrix integration module license | 1–2 days | Vendor |
| 3 | ☐ Configure Dentrix bridge settings in Carestream software | 1 hour | Central IT |
| 4 | ☐ Map provider IDs between systems | 2 hours | Central IT |
| 5 | ☐ Configure patient matching rules (patient ID, chart number) | 1 hour | Central IT |
| 6 | ☐ ⚠️ Test bi-directional patient data sync with sample records | 2 hours | Central IT |
| 7 | ☐ Verify AI findings automatically appear in patient clinical notes | 1 hour | Central IT |
| 8 | ☐ Test image access from within Dentrix interface | 30 min | Central IT |
Eaglesoft Integration
| Step | Action | Time Estimate | Owner |
|---|---|---|---|
| 1 | ☐ Confirm Eaglesoft version (v21 or later recommended) | 30 min | Central IT |
| 2 | ☐ 🔵 Request Carestream-Patterson integration documentation | 1–2 days | Vendor |
| 3 | ☐ Install Eaglesoft bridge component on imaging workstations | 1 hour/workstation | Central IT |
| 4 | ☐ Configure image storage path settings | 30 min | Central IT |
| 5 | ☐ Enable DICOM push from Carestream to Eaglesoft | 1 hour | Central IT |
| 6 | ☐ ⚠️ Test integration with live patient data in test environment | 2 hours | Central IT |
| 7 | ☐ Verify treatment plan generation from AI findings | 1 hour | Central IT |
Open Dental Integration
| Step | Action | Time Estimate | Owner |
|---|---|---|---|
| 1 | ☐ Verify Open Dental version (v21.1 or later) | 30 min | Central IT |
| 2 | ☐ Enable Open Dental API access (requires API license) | 1 hour | Central IT |
| 3 | ☐ 🔵 Obtain Carestream-Open Dental API connector credentials | 1–2 days | Vendor |
| 4 | ☐ Configure imaging module bridge settings | 1 hour | Central IT |
| 5 | ☐ Set up image storage paths and DICOM settings | 1 hour | Central IT |
| 6 | ☐ Test patient sync and image association | 2 hours | Central IT |
| 7 | ☐ ⚠️ Verify charting integration for AI findings | 1 hour | Central IT |
Imaging System Integration
☐ 🔵 Request Carestream imaging system audit for each location (sensor models, software versions) ☐ Update Carestream Imaging Software to minimum v8.0 at all locations (plan 1 hour per location) ☐ Configure AI engine connection settings:
- Cloud API endpoint URL
- Authentication credentials
- Timeout settings (recommend 30 seconds)
☐ Configure detection parameters:
- Sensitivity thresholds (start with vendor defaults)
- Detection types to enable (caries, bone loss, calculus, periapical)
- Confidence score display preferences
☐ Configure annotation display settings:
- Overlay color scheme
- Annotation persistence (session vs. saved)
- Provider-level preference allowances
☐ ⚠️ Test AI processing with sample images from each sensor type in use
Test Environment Setup
☐ Create isolated test environment (recommend cloud-based sandbox) ☐ 🔵 Request test environment credentials from Carestream ☐ Load sample patient data (anonymized production data preferred) ☐ Load sample images representing common clinical scenarios:
- Clear images with no pathology
- Images with obvious caries
- Images with early/subtle caries
- Images with periapical lesions
- Images with bone loss
- Images with calculus
- Challenging images (poor angulation, overlap)
☐ Create test scripts for each workflow scenario ☐ Document expected AI detection results for test images ☐ Execute validation testing with pilot location champions
Enterprise Configuration Standards (DSO-Specific)
Standardize Centrally (Identical Across All Locations)
| Setting | Standard Value | Rationale |
|---|---|---|
| AI detection types | All enabled (caries, periapical, bone loss, calculus) | Consistent diagnostic coverage |
| Confidence threshold for display | 60% | Balance sensitivity vs. noise |
| Annotation color scheme | Red = high confidence, Yellow = medium | Visual consistency |
| Audit logging | Enabled, 7-year retention | HIPAA compliance |
| Data transmission encryption | TLS 1.3 | Security standard |
| Session timeout | 15 minutes | Security standard |
| Automatic image analysis | Enabled | Workflow consistency |
Allow Local Discretion
| Setting | Local Decision | Guidelines |
|---|---|---|
| Provider-level sensitivity preferences | Provider can adjust ± 10% from baseline | Document overrides |
| Annotation display preferences | Providers may choose display density | Train on all options |
| Workflow integration timing | Pre-exam vs. during-exam analysis | Based on practice flow |
| Print/export formatting | Location-specific branding allowable | Within brand guidelines |
Centralized vs. Per-Location Testing
Recommendation: Hybrid approach
☐ Create centralized test environment for integration validation (one instance) ☐ Conduct technical integration testing centrally before any location rollout ☐ Create per-location test phase during installation:
- 4-hour "burn-in" period with test patients
- Verify local hardware compatibility
- Confirm network connectivity and latency
- Test local printer integration if applicable
Enterprise HIPAA Compliance Checklist
☐ 🔵 Execute Business Associate Agreement (BAA) with Carestream (if not already in place) ☐ Document data flow diagram showing PHI transmission paths ☐ Verify encryption at rest (AES-256) and in transit (TLS 1.3) ☐ Configure access controls aligned with RBAC structure ☐ Enable comprehensive audit logging ☐ Establish data retention policy aligned with state requirements ☐ Document breach notification procedures specific to AI system ☐ 🟣 Legal review of AI-assisted diagnosis liability implications ☐ Update Notice of Privacy Practices if AI processing constitutes new use of PHI ☐ Conduct security risk assessment including AI system ☐ Document minimum necessary standards for AI data access ☐ Verify Carestream's SOC 2 Type II compliance status ☐ ⚠️ Confirm data residency requirements (some states require PHI storage location disclosure)
Data Migration/Historical Data Ingestion
☐ Determine scope of historical data ingestion:
- Option A: Forward-only (AI analyzes new images only) — recommended for initial deployment
- Option B: Bulk historical analysis (AI processes historical images) — significant infrastructure requirements
☐ If Option B selected:
- Inventory historical image volume per location
- 🔵 Engage Carestream professional services for bulk processing
- Establish processing timeline (typically 1,000–5,000 images per hour)
- Plan for storage requirements of AI annotations on historical images
- 🟣 Budget approval for professional services engagement
6. Team Training Plan
Train-the-Trainer Model Overview
For DSO deployment, we recommend a cascaded training approach:
- Central Training Team (2–3 people) receives in-depth vendor training
- Location Champions (1 per location) receive training from Central Team
- Location Staff receive training from their Location Champion
This model scales efficiently while ensuring local expertise at every location.
Champion Selection Criteria
☐ Identify one champion per location meeting the following criteria:
- Current clinical or administrative role requiring daily imaging interaction
- Minimum 1 year tenure at location (stability)
- Demonstrated comfort with technology adoption
- Strong communication skills (will train peers)
- Positive influence within the team
- Available capacity for ~8 hours of training + ongoing support responsibilities
Ideal profiles:
- Lead dental assistant with imaging responsibilities
- Tech-forward hygienist
- Office manager with clinical background
Champion Responsibilities
☐ Document and communicate champion responsibilities:
- Complete champion certification training (4 hours)
- Conduct staff training at their location (4–6 hours total)
- Serve as first point of contact for staff questions
- Track training completion for all location staff
- Escalate unresolved issues to Regional Manager and Central Team
- Participate in weekly champion calls during rollout
- Provide feedback on training materials and workflow improvements
- Support new hire training on an ongoing basis
Centralized Training Materials
☐ Create standardized training assets centrally:
| Material | Format | Audience | Owner |
|---|---|---|---|
| AI Overview Video | 15-min video | All staff | Central Training Team |
| Clinical Workflow Guide | PDF + video | Providers | CDO + Central Team |
| Technical User Guide | Champions, IT | Central IT | |
| Quick Reference Cards | Single-page PDF | All staff | Central Training Team |
| FAQs Document | Champions | Central Training Team | |
| Training Completion Tracker | Spreadsheet | Champions | Central HR/Training |
☐ 🔵 Request vendor training assets and customize as needed
Role-Specific Training Outlines
Dentists/Providers Training
Training Time: 2 hours (champion-delivered) + 30 minutes hands-on practice
Module 1: AI in Clinical Context (30 minutes)
- How the AI model was trained and validated
- What the AI detects (and does not detect)
- Confidence scores: what they mean and how to interpret
- AI as decision support, not decision maker—clinical judgment remains paramount
- Medicolegal considerations: documenting AI-assisted diagnosis
Module 2: Workflow Integration (45 minutes)
- Image capture triggers AI analysis automatically
- Viewing AI findings: overlay display, findings panel, confidence indicators
- Accepting, modifying, or overriding AI findings
- Documentation workflow: how findings flow to patient record
- Patient communication: discussing AI-assisted findings
Module 3: Hands-On Practice (45 minutes)
- Practice with 10 sample cases
- Identify AI findings and compare to clinical assessment
- Practice override workflow
- Practice patient explanation scenarios
Common Resistance Points and Responses:
| Resistance | Response |
|---|---|
| "I don't need AI to tell me what I can see myself" | The AI catches what fatigue, distraction, and volume cause us to miss. Studies show 20% of early caries are missed on visual-only review. This is your safety net. |
| "What if the AI is wrong?" | You remain the clinical decision-maker. The AI presents findings; you evaluate and decide. Document your clinical reasoning when overriding. |
| "This will slow me down" | Initial slowdown of 1–2 minutes per patient typical. Within 2 weeks, most providers report time-neutral workflow. Long-term, reduced missed diagnoses save time on retreatment. |
| "My patients will think a robot is treating them" | Frame it as cutting-edge technology that gives them an extra layer of care—like a specialist reviewing every image. |
Day 1 Cheat Sheet for Providers:
┌──────────────────────────────────────────────────────────────────────┐
│ CARESTREAM AI: PROVIDER QUICK REFERENCE │
├──────────────────────────────────────────────────────────────────────┤
│ 1. Capture image as normal — AI analysis begins automatically │
│ │
│ 2. Look for colored overlays: │
│ 🔴 RED = High confidence finding (80%+) │
│
AI-generated implementation guide based on public vendor information. Verify specifics directly with Carestream Dental.