DentXcel.ai — Implementation Playbook (DSO)

DentXcel.ai Implementation Playbook

Diagnostic Imaging AI for Dental Service Organizations

---

1. Executive Summary

What DentXcel.ai Does

DentXcel.ai is a diagnostic imaging AI platform that analyzes dental radiographs in real-time to detect pathology, measure bone loss, identify caries, and flag anomalies that may be missed during manual review. The system integrates directly with existing imaging workflows and provides AI-assisted findings as an overlay or secondary opinion to support clinical decision-making.

Why DSOs Specifically Benefit

Diagnostic imaging AI delivers outsized value at DSO scale for three core reasons:

1. Standardization of Diagnostic Quality: With providers of varying experience levels across 15–50 locations, AI creates a consistent diagnostic baseline. Every radiograph receives the same algorithmic scrutiny regardless of which provider reviews it, reducing diagnostic variability and associated liability exposure.

2. Data Aggregation for Strategic Insight: Centralized imaging analytics enable identification of patterns invisible at the practice level—detecting undertreated populations, benchmarking diagnostic rates across providers, and identifying training gaps by region or location.

3. Operational Leverage: Training and calibrating one AI system that deploys to 50 locations is fundamentally more efficient than attempting to standardize diagnostic protocols through human training alone. The marginal cost of each additional location approaches zero once the infrastructure exists.

Expected Timeline: Decision to Full Deployment

Phase	Timeline
Pre-Implementation & Planning	Weeks 1–2
Pilot Wave (2–3 locations)	Weeks 3–6
Wave 2 Expansion (5–8 locations)	Weeks 7–12
Wave 3 Full Deployment (remaining locations)	Weeks 13–20
Total: Decision to Full Deployment	18–22 weeks

Note: Timeline assumes a 30-location DSO. Scale appropriately for larger portfolios.

---

2. Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Hardware Requirements

☐ Workstations with minimum 8GB RAM, quad-core processor (verify at each location) ☐ Monitors capable of displaying diagnostic-quality images (minimum 1920x1080 resolution) ☐ Digital sensors compatible with DentXcel.ai integration (verify sensor models against vendor compatibility list) 🔵

Software Requirements

☐ Operating system: Windows 10/11 or macOS 11+ (varies by integration path) ☐ Practice Management System version verification (minimum versions listed in Section 5) ☐ Imaging software version verification ☐ Chrome, Edge, or Safari browser (latest version) for web-based dashboard access

Network Requirements

☐ Minimum 50 Mbps upload/download speed at each location ☐ Stable internet connection with <100ms latency to DentXcel.ai cloud servers ☐ Firewall exceptions documented for DentXcel.ai endpoints 🔵 ☐ VPN compatibility confirmed if locations connect through centralized network

Enterprise-Level Requirements (DSO-Specific)

Network Standards Across Locations

☐ Document current network topology for all locations ☐ Identify locations with substandard connectivity (flag for infrastructure upgrade) ☐ Establish minimum network SLA requirements for AI tool performance ☐ 🟣 Decide: Centralized hosting (images route through corporate) vs. location-level hosting (direct cloud connection)

Identity & Access Management

☐ SSO integration requirements documented (SAML 2.0, OAuth 2.0, or proprietary) 🔵 ☐ Active Directory or identity provider compatibility confirmed ☐ Centralized credentialing workflow designed:

• Who provisions new user accounts?
• What role-based access levels exist?
• How are terminated employees removed? ☐ Multi-factor authentication requirements defined

Data Governance

☐ Data residency requirements documented (U.S. data centers confirmed with vendor) 🔵 ☐ Data retention policies aligned with organizational standards ☐ Audit logging requirements specified

Vendor Onboarding Steps

☐ 🔵 Execute Master Services Agreement (MSA) and Business Associate Agreement (BAA) ☐ 🔵 Establish primary vendor contacts:

• Implementation Project Manager
• Technical Integration Specialist
• Customer Success Manager
• Support escalation contacts (Tier 1, 2, 3) ☐ 🔵 Schedule kickoff call with vendor implementation team ☐ 🔵 Obtain vendor implementation playbook and timeline ☐ 🔵 Request access to vendor training portal and documentation ☐ 🔵 Confirm SLA terms: uptime guarantees, support response times, escalation procedures

Time Estimate: 3–5 business days for contract execution, 1 day for kickoff scheduling

Data/Access Prerequisites

☐ Compile list of all PMS system credentials (admin-level access required for integration) ☐ Compile list of all imaging software credentials ☐ 🔵 Request API keys or integration credentials from vendor ☐ Document imaging archive locations (local storage, cloud, hybrid) ☐ ⚠️ Verify historical image file formats are compatible (DICOM, proprietary formats) ☐ Determine historical data ingestion scope (6 months, 12 months, all available)

Internal Stakeholder Alignment

Stakeholder Alignment Map

Stakeholder Level	Who	Role in Implementation	Communication Cadence
Board/Investors	Board members, PE partners	🟣 Approve investment, receive ROI updates	Monthly summary
C-Suite	CEO, CDO, VP Ops, CFO, CTO/IT Director	🟣 Executive sponsorship, strategic decisions, resource allocation	Weekly during rollout
Regional Managers	Regional Directors, Area Managers	Cascade communication, monitor location progress, troubleshoot blockers	Weekly during active waves
Location Office Managers	Practice Managers	Local implementation lead, staff coordination, workflow integration	Daily during go-live week
Providers	Dentists, Specialists	Clinical adoption, workflow integration, feedback	Training + daily during go-live
Clinical Staff	Hygienists, Assistants	Workflow adaptation, image capture protocols	Training + as needed
Administrative Staff	Front desk, Billing	Patient communication, documentation workflows	Training + as needed

Required Approvals Before Proceeding

☐ 🟣 CFO/Finance approval of total cost of ownership (licensing, integration, training, ongoing) ☐ 🟣 CDO clinical endorsement of AI-assisted diagnostic workflow ☐ 🟣 CTO/IT Director approval of technical architecture and security requirements ☐ 🟣 VP Operations approval of rollout timeline and resource allocation ☐ Board notification (approval if required by governance structure)

Time Estimate: 5–10 business days depending on approval cycles

Baseline Metrics to Capture BEFORE Go-Live

⚠️ Critical: Without baseline metrics, ROI measurement is impossible. Capture these BEFORE any location goes live.

Clinical Metrics

Metric	How to Capture	Standardization Notes
Average pathology detection rate per 100 radiographs	Manual chart audit (sample 50 patients per location)	Use standardized audit form across all locations
Caries detection rate	PMS diagnostic code analysis (D0120, D0150, D0210, D0270-D0277)	Ensure coding consistency across locations
Periodontal disease diagnosis rate	PMS diagnostic code analysis	Standardize perio charting protocols
Re-treatment rate (fillings that become RCTs within 24 months)	Historical claims analysis	Requires consistent historical data

Operational Metrics

Metric	How to Capture	Standardization Notes
Average diagnosis time per radiograph set	Time study (sample 20 appointments per location)	Use consistent methodology
Case acceptance rate	PMS treatment planning reports	Ensure treatment plan documentation is consistent
Time from imaging to treatment plan presentation	Workflow observation	Sample across provider types

Financial Metrics

Metric	How to Capture	Standardization Notes
Claim denial rate for diagnostic procedures	Claims analysis by procedure code	90-day lookback minimum
Average revenue per patient visit	PMS financial reports	Segment by visit type
Diagnostic imaging revenue per location	PMS financial reports	Monthly trend for 6+ months

Standardized Measurement Protocol

☐ Create standardized data collection templates for all metrics ☐ Assign data collection responsibility (central team vs. location) ☐ Set data collection deadline (minimum 2 weeks before first go-live) ☐ Validate data quality before accepting baseline ☐ Store baseline data in centralized location for post-launch comparison

Time Estimate: 1–2 weeks for baseline data collection across all target locations

---

3. Location Readiness Assessment

Readiness Scoring Framework

Score each location on the following factors using a 1–5 scale. This produces a composite readiness score that drives rollout sequencing.

Factor 1: IT Infrastructure Maturity

Score	Criteria
5	Network >100 Mbps, hardware <2 years old, latest PMS version, digital sensors
4	Network 50–100 Mbps, hardware 2–4 years old, PMS within 1 version of current
3	Network 25–50 Mbps, hardware 4–5 years old, PMS within 2 versions
2	Network 10–25 Mbps, hardware 5–7 years old, outdated PMS requiring upgrade
1	Network <10 Mbps, hardware >7 years old, legacy PMS, analog imaging still in use

Assessment Method: IT inventory audit, network speed tests, software version verification

Factor 2: Staff Tenure and Adaptability

Score	Criteria
5	<15% annual turnover, staff with tech training history, enthusiastic about innovation
4	15–25% turnover, moderate tech comfort, open to change
3	25–35% turnover, basic tech skills, neutral toward change
2	35–50% turnover, limited tech skills, resistant to workflow changes
1	>50% turnover, significant tech skill gaps, actively resistant to new tools

Assessment Method: HR turnover data, manager assessment, past technology adoption history

Factor 3: Patient Volume

Score	Criteria	Risk/Impact Notes
5	Top quartile volume	Highest impact potential, highest risk if issues occur
4	Second quartile volume	Strong impact, moderate risk
3	Third quartile volume	Moderate impact and risk
2	Fourth quartile volume	Lower impact, good for cautious testing
1	Lowest volume or startup location	Minimal impact, may not generate meaningful data

Assessment Method: PMS patient count and appointment data

Factor 4: Existing Tech Stack Compatibility

Score	Criteria
5	PMS and imaging system both on DentXcel.ai certified integration list, cloud-based
4	PMS on certified list, imaging requires minor configuration
3	PMS on certified list, imaging requires custom integration work
2	PMS requires workaround, imaging on certified list
1	Both PMS and imaging require custom integration or replacement

Assessment Method: Cross-reference vendor compatibility documentation 🔵

Factor 5: Local Champion Availability

Score	Criteria
5	Tech-forward provider AND engaged office manager, both eager to lead
4	Strong champion in one role (provider or manager), other is supportive
3	Potential champion identified but not yet engaged
2	No obvious champion, but no active resistance
1	No champion available, or key personnel actively resistant

Assessment Method: Regional manager assessment, direct conversations with location leadership

Composite Scoring & Rollout Sequencing

Scoring Template

Location	IT Infra (1-5)	Staff (1-5)	Volume (1-5)	Tech Stack (1-5)	Champion (1-5)	Total (5-25)
Location A
Location B
...

Recommended Rollout Sequence by Score

Composite Score	Rollout Recommendation
21–25	Wave 1 Pilot candidate
17–20	Wave 2 candidate
13–16	Wave 3 candidate
9–12	Wave 3 (late) with additional preparation
5–8	Defer until remediation complete

Wave 1 Pilot Selection Criteria

Wave 1 locations should meet ALL of the following:

• ☐ Composite score ≥20
• ☐ IT Infrastructure score ≥4 (minimize technical risk)
• ☐ Champion score ≥4 (maximize adoption support)
• ☐ Volume score = 3 (representative but not highest-risk)
• ☐ Geographic diversity (if DSO spans multiple regions, include representation)
• ☐ Practice type representation (GP, specialty mix mirrors portfolio)

⚠️ Common Mistake: Selecting only the "best" locations for Wave 1 creates an unrepresentative pilot. Include one location with minor challenges to test escalation paths.

---

4. Rollout Strategy

Recommended Wave Structure

For a DSO with 15–50 locations, we recommend a three-wave rollout structure:

Wave	Locations	Duration	Purpose
Wave 1: Pilot	2–3 locations	4 weeks	Validate integration, refine training, identify issues
Wave 2: Expansion	5–8 locations	4–5 weeks	Scale proven approach, stress-test support capacity
Wave 3: Full Deployment	Remaining locations	5–8 weeks	Complete rollout with refined playbook

Wave 1 Selection Criteria

Select 2–3 locations that together meet these criteria:

☐ High readiness (composite score ≥20): Minimizes technical risk during proof-of-concept ☐ Manageable risk: Mid-tier patient volume (avoid highest-volume locations until process is proven) ☐ Representative: At least one GP-focused location and one specialty or mixed location ☐ Geographic accessibility: At least one location near central IT/operations for on-site support if needed ☐ Enthusiastic leadership: Office manager and lead provider are genuine champions, not just compliant

Timeline Per Wave

Wave 1 Timeline (Weeks 3–6)

Week	Activities
Week 3	Final configuration, test environment validation, champion training
Week 4	Go-live at Location 1, daily check-ins, issue documentation
Week 5	Go-live at Locations 2–3, continued monitoring, workflow adjustments
Week 6	Wave 1 retrospective, playbook refinements, Wave 2 preparation

Wave 2 Timeline (Weeks 7–12)

Week	Activities
Week 7	Wave 2 champion training, configuration replication
Weeks 8–9	Staggered go-live (2–3 locations per week)
Weeks 10–11	Monitoring, optimization, support capacity assessment
Week 12	Wave 2 retrospective, final playbook for Wave 3

Wave 3 Timeline (Weeks 13–20)

Week	Activities
Weeks 13–14	Wave 3 champion training (may run in parallel cohorts)
Weeks 15–19	Staggered go-live (3–5 locations per week depending on support capacity)
Week 20	Final retrospective, transition to steady-state support

Go/No-Go Criteria Between Waves

⚠️ Do not advance to the next wave until all criteria are met.

Wave 1 → Wave 2 Go/No-Go Criteria

Criterion	Go	No-Go
Integration stability	Zero critical integration failures in Week 2 of any pilot location	Any critical failure unresolved >24 hours
Provider adoption	≥80% of providers using tool for ≥80% of radiograph reviews	<60% provider adoption
Support capacity	All Tier 1 issues resolved within SLA	>20% of issues breaching SLA
Training effectiveness	≥90% of staff complete training, ≥80% pass competency check	<80% training completion
Clinical workflow	No significant patient flow disruption	Appointment delays >15 minutes attributed to tool

🟣 Executive Decision Point: Wave advancement requires VP Operations and CDO sign-off.

Wave 2 → Wave 3 Go/No-Go Criteria

Same criteria as above, plus:

Criterion	Go	No-Go
Scalability validation	Support team managed all Wave 2 locations without backlog	Support backlog growing
Champion model	Champions successfully delivered training independently	Champions required excessive central support
Cross-location consistency	Workflows and configuration consistent across Wave 2	Significant location-to-location variation

Rollback Plan

If a wave fails to meet go/no-go criteria, execute the following:

Immediate (Within 24 hours of no-go determination): ☐ Halt all pending go-lives in current wave ☐ Notify all stakeholders (executive sponsors, regional managers, scheduled locations) ☐ Preserve current state at live locations (do not revert unless critical)

Within 48 hours: ☐ Root cause analysis with vendor and internal teams 🔵 ☐ Document specific failure points and contributing factors ☐ Assess scope: Is this a systemic issue or location-specific?

Within 1 week: ☐ 🟣 Present remediation plan to executive sponsors ☐ Revise timeline with realistic remediation buffer ☐ Communicate revised timeline to all stakeholders

Rollback Principles:

• Locations already live should remain live unless the tool creates patient safety risk
• Pausing a wave does not automatically revert completed locations
• Budget for 2–4 week delay per failed wave advancement

---

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integration

Dentrix Integration

Prerequisites: ☐ Dentrix version G7.3 or higher (version G8+ recommended) ☐ Dentrix Imaging module active ☐ Admin credentials for Dentrix

Step-by-Step Integration:

1. ☐ 🔵 Request DentXcel.ai Dentrix integration package from vendor
2. ☐ Install DentXcel.ai connector service on Dentrix server (Time: 30 minutes)
3. ☐ Configure connector with Dentrix database connection string
4. ☐ ⚠️ Test database connectivity (common failure: firewall blocking local connections)
5. ☐ Map Dentrix patient ID field to DentXcel.ai patient identifier
6. ☐ Configure procedure code mapping for diagnostic codes
7. ☐ Set up automatic image routing from Dentrix Imaging to DentXcel.ai
8. ☐ Configure AI findings write-back to Dentrix clinical notes (if enabled)
9. ☐ Test end-to-end with sample patient record
10. ☐ Verify HIPAA audit logging captures all data exchanges

Time Estimate: 2–3 hours per location (first location may take 4–5 hours)

Eaglesoft Integration

Prerequisites: ☐ Eaglesoft version 21 or higher ☐ Active Patterson Imaging integration ☐ Admin credentials for Eaglesoft

Step-by-Step Integration:

1. ☐ 🔵 Confirm Eaglesoft compatibility with vendor (specific version dependencies exist)
2. ☐ Install DentXcel.ai bridge application on imaging workstation
3. ☐ Configure TWAIN or proprietary imaging pathway
4. ☐ ⚠️ Map image capture workflow (common failure: dual-save creating duplicate images)
5. ☐ Configure patient context passing from Eaglesoft to DentXcel.ai
6. ☐ Set up findings integration (SmartDoc or clinical notes, depending on version)
7. ☐ Test with live image capture
8. ☐ Verify no impact on existing imaging workflows

Time Estimate: 3–4 hours per location

Open Dental Integration

Prerequisites: ☐ Open Dental version 22.1 or higher ☐ API access enabled (Open Dental API key required) ☐ Open Dental Imaging configured

Step-by-Step Integration:

1. ☐ Generate Open Dental API key (Setup → Security → API)
2. ☐ 🔵 Provide API key to DentXcel.ai for cloud configuration
3. ☐ Configure webhook for image capture events
4. ☐ Map patient identifiers (PatNum to DentXcel.ai patient ID)
5. ☐ Set up image routing pathway (cloud or local folder watch)
6. ☐ ⚠️ Test patient context synchronization (common failure: timezone mismatches causing patient mismatch)
7. ☐ Configure findings posting to patient clinical notes
8. ☐ Validate end-to-end workflow

Time Estimate: 2–3 hours per location (Open Dental typically has cleaner API integration)

Imaging System Integration

Digital Sensor Integration

1. ☐ Document sensor manufacturer and model at each location
2. ☐ 🔵 Verify sensor compatibility with DentXcel.ai (request compatibility matrix from vendor)
3. ☐ Configure image capture pathway:
   • Direct integration: Sensor software sends images directly to DentXcel.ai
   • Folder watch: Images saved to monitored folder, DentXcel.ai pulls automatically
   • API trigger: PMS triggers DentXcel.ai to retrieve image after capture
4. ☐ Set image quality parameters (resolution, bit depth)
5. ☐ ⚠️ Validate image orientation (common failure: mirrored or rotated images causing AI errors)
6. ☐ Test with FMX series to verify all images process correctly

CBCT Integration (If Applicable)

1. ☐ Document CBCT unit manufacturer and software version
2. ☐ 🔵 Confirm DentXcel.ai CBCT analysis capability and compatibility
3. ☐ Configure DICOM export pathway
4. ☐ Set up automated DICOM push to DentXcel.ai endpoints
5. ☐ Configure patient matching for DICOM studies
6. ☐ Validate 3D reconstruction compatibility
7. ☐ Test with sample CBCT study

Time Estimate: CBCT integration 4–6 hours per location due to DICOM complexity

Test Environment Setup

Centralized Test Environment (Recommended for DSO)

☐ 🔵 Request dedicated test tenant from DentXcel.ai ☐ Configure test tenant with production-equivalent settings ☐ Load sample patient data (de-identified from production or vendor-provided) ☐ Assign test environment access to IT team and select champions ☐ Document test environment limitations vs. production

Test Environment Validation Checklist

☐ Patient context passes correctly from PMS to DentXcel.ai ☐ Images route to AI engine within acceptable latency (<3 seconds) ☐ AI analysis completes within acceptable time (<10 seconds for single image) ☐ Findings display correctly in DentXcel.ai interface ☐ Findings write-back to PMS (if configured) ☐ User authentication works via SSO ☐ Role-based permissions restrict access appropriately ☐ Audit logs capture all actions

Data Migration / Historical Image Ingestion

⚠️ Historical data ingestion is optional but valuable for establishing baseline comparisons.

1. ☐ Define ingestion scope (recommendation: 12 months of images for established locations)
2. ☐ Export images from current archive:
   • Document file format (DICOM, JPEG, PNG, proprietary)
   • Preserve patient linkage metadata
3. ☐ 🔵 Coordinate bulk upload with vendor (may require dedicated ingestion pipeline)
4. ☐ Validate patient matching for historical images
5. ☐ Mark historical images appropriately (do not mix with prospective AI analysis)
6. ☐ Document any images that failed ingestion and root cause

Time Estimate: Historical ingestion varies widely—plan for 1–2 weeks of background processing

Configuration Standardization (DSO-Specific)

Standardize Centrally

Setting	Standardized Value	Rationale
AI sensitivity threshold	Vendor default (adjust based on pilot data)	Consistent diagnostic baseline
Pathology categories displayed	All available	Complete clinical picture
Alert/notification thresholds	Critical findings only	Reduce alert fatigue
User role definitions	Standardized RBAC matrix	Consistent permissions
Audit log retention	7 years	HIPAA compliance
Image compression settings	Lossless	Diagnostic quality

Allow Local Discretion

Setting	Local Discretion	Rationale
Display layout preferences	Yes	Provider workflow preferences vary
Alert notification recipients	Yes	Local champion assignment varies
Specialty-specific modules	Yes	Specialty mix differs by location
Provider-specific AI trust calibration	Yes	Individual provider preferences

Configuration Template Process

1. ☐ Create "gold standard" configuration in test environment
2. ☐ Document all settings in configuration template
3. ☐ 🔵 Work with vendor to enable configuration export/import
4. ☐ Version control configuration template
5. ☐ Assign configuration manager (single owner for template updates)

Security and HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

☐ 🔵 Business Associate Agreement (BAA) executed and on file ☐ Verify encryption in transit (TLS 1.2 or higher) ☐ Verify encryption at rest (AES-256 or equivalent) ☐ 🔵 Request SOC 2 Type II report from vendor (or equivalent) ☐ Document data flow: where does PHI travel and where is it stored? ☐ Confirm data residency requirements are met (U.S.-based servers) ☐ Access control verification:

• Unique user identification
• Emergency access procedure
• Automatic logoff
• Audit controls ☐ Verify audit log completeness and accessibility ☐ Document minimum necessary access (no broader access than required) ☐ Confirm secure user authentication (SSO + MFA) ☐ 🟣 Legal/compliance review of data governance terms

Per-Location Security Verification

☐ Workstations have current antivirus/endpoint protection ☐ Workstation access requires authentication ☐ Physical security appropriate (no public access to imaging workstations) ☐ Staff trained on security/privacy requirements ☐ No unauthorized data export capabilities (USB disabled if required by policy)

---

6. Team Training Plan

Train-the-Trainer Model (DSO Approach)

Champion Selection Criteria

Each location should have one designated champion who will deliver training to their team. Ideal champion profile:

☐ Role: Office Manager or Lead Hygienist (someone with daily presence and peer influence) ☐ Tenure: Minimum 12 months at location (understands local workflows) ☐ Tech comfort: History of successful technology adoption ☐ Communication skills: Able to explain concepts clearly to diverse team ☐ Availability: Bandwidth to dedicate 10–15 hours during implementation

Alternative: Tech-forward provider who is enthusiastic about the tool can serve as clinical champion, partnered with office manager for operational champion duties.

Champion Responsibilities

1. Complete central training program (8–10 hours)
2. Pass competency verification
3. Customize training materials for local context (1–2 hours)
4. Schedule and deliver training to all location staff (4–6 hours)
5. Provide go-live week support
6. Serve as first-tier support for staff questions
7. Report issues to regional manager/central team
8. Train new hires on DentXcel.ai

Champion Training Program

Delivery Method: Virtual instructor-led training (VILT) via Zoom/Teams 🔵

Duration: 8 hours total (four 2-hour sessions)

Session	Topic	Duration
1	Platform overview, navigation, account setup	2 hours
2	Clinical workflow integration, interpreting AI findings	2 hours
3	Troubleshooting, escalation paths, common issues	2 hours
4	Train-the-trainer methodology, delivering role-specific training	2 hours

Champion Certification: ☐ Complete all four sessions ☐ Pass written assessment (≥80% score) ☐ Complete observed training delivery (shadow presentation) ☐ Receive certification before location go-live

Standardized Training Materials

Created Centrally

☐ Training slide decks (role-specific versions) ☐ Video library (screen recordings of key workflows) ☐ Day 1 cheat sheets (one-page quick reference per role) ☐ FAQ document ☐ Troubleshooting guide ☐ Patient communication scripts ☐ Competency assessment quizzes

Customized Locally by Champions

☐ Location-specific workflow notes (e.g., where the tool fits in your operatory flow) ☐ Provider-specific preferences (if allowed by configuration) ☐ Local escalation contacts ☐ Training schedule adjusted for location staffing patterns

Role-Specific Training Outlines

Dentists/Providers

Training Duration: 90 minutes

Training Format: Live demonstration with hands-on practice

Core Content:

1. What DentXcel.ai detects and how it presents findings (20 min)
2. Interpreting AI findings: confidence levels, annotation overlays (20 min)
3. Integrating AI into diagnostic workflow: when to review, how to validate (20 min)
4. When to override or dismiss AI findings: clinical judgment remains primary (15 min)
5. Documentation: how findings integrate with charting (15 min)

Common Resistance Points & Responses:

Resistance	Response
"I don't need AI to tell me how to diagnose"	"The AI is a second set of eyes, not a replacement for your judgment. It catches what humans sometimes miss, like subtle interproximal caries."
"This will slow me down"	"After the first week, most providers report it adds <30 seconds per image series. The time saved on missed pathology callbacks exceeds this."
"What if the AI is wrong?"	"You always retain final diagnostic authority. The AI is trained on millions of images but flags for your review—it doesn't diagnose patients, you do."

Day 1 Cheat Sheet: Providers

┌─────────────────────────────────────────────────────────────┐
│ DentXcel.ai Quick Reference - PROVIDERS                     │
├─────────────────────────────────────────────────────────────┤
│ 1. ACCESS: [Button/menu location in your PMS]               │
│                                                             │
│ 2. WORKFLOW:                                                │
│    • Image captured → AI analyzes automatically (5-10 sec)  │
│    • Review AI findings overlay on image                    │
│    • Validate/dismiss findings as clinically appropriate    │
│    • Document in chart                                      │
│                                                             │
│ 3. FINDING TYPES:                                           │
│    🔴 High confidence pathology (review