Pearl — Implementation Playbook (DSO)

Pearl AI Implementation Playbook for DSOs

Diagnostic Imaging AI Deployment Guide

---

1. Executive Summary

What Pearl Does

Pearl is an FDA-cleared AI-powered diagnostic imaging platform that analyzes dental radiographs in real-time to detect pathology, including caries, periapical lesions, calculus, and bone loss. The system overlays findings directly onto X-rays within your existing imaging workflow, providing objective clinical decision support that enhances diagnostic accuracy and consistency across providers.

Why DSOs Specifically Benefit from Diagnostic Imaging AI

Scale Advantages: Deploying Pearl across 15–50 locations creates a force multiplier effect—standardized diagnostic quality regardless of provider experience level, reduced inter-examiner variability, and consistent patient communication around findings.

Standardization Value: DSOs struggle with diagnostic consistency across providers. Pearl establishes an objective baseline that makes clinical oversight, peer review, and quality assurance measurable. Your CDO gains visibility into diagnostic patterns across the entire organization.

Data Aggregation Power: Enterprise-level Pearl deployment unlocks population health insights, regional disease prevalence trends, and provider performance benchmarking impossible at the single-practice level. This data feeds strategic decisions around service mix, staffing, and market expansion.

Expected Timeline: Decision to Full Deployment

DSO Size	Pilot Phase	Full Deployment	Total Timeline
15–25 locations	6–8 weeks	12–16 weeks	4–6 months
26–50 locations	8–10 weeks	16–24 weeks	6–8 months

Timeline assumes adequate IT infrastructure and reasonable staff turnover rates. Add 4–6 weeks if significant hardware upgrades required.

---

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

Technical Requirements

Hardware Requirements

☐ Workstations: Windows 10/11 (64-bit), minimum 8GB RAM (16GB recommended), Intel i5 or equivalent processor ☐ Display: Minimum 1920x1080 resolution; diagnostic monitors preferred for clinical workstations ☐ Digital radiography sensors: Verify Pearl compatibility with existing sensor brands (Dexis, Schick, Carestream, etc.) ☐ Panoramic/CBCT units: Confirm model compatibility with Pearl's Second Opinion® platform

Network Requirements

☐ Minimum 25 Mbps download/10 Mbps upload per location (50/20 Mbps recommended) ☐ Latency under 100ms to Pearl cloud infrastructure ☐ Firewall exceptions for Pearl domains (vendor provides whitelist) ☐ SSL/TLS 1.2 or higher enabled

Software Requirements

☐ Practice Management System: Verify integration availability (Dentrix, Eaglesoft, Open Dental, Denticon, Curve) ☐ Imaging software: TWAIN or DICOM compatibility verification ☐ Browser: Chrome (latest), Edge (latest) for Pearl Practice Intelligence dashboard

⚠️ Common Failure Point: Outdated imaging software versions frequently cause integration failures. Audit all locations for software currency before proceeding.

Vendor Onboarding Steps

Step	Owner	Vendor Contact	Timeline
🔵 Execute Master Services Agreement	Legal/CDO	Pearl Enterprise Sales	Day 1–3
🔵 Complete BAA for all entities	Compliance	Pearl Legal	Day 1–5
🔵 Assign dedicated Customer Success Manager	VP Ops	Pearl CS Team	Day 3
🔵 Schedule technical discovery call	IT Director	Pearl Implementation	Day 5
🔵 Obtain enterprise admin credentials	IT Director	Pearl CS	Day 7
🔵 Request API documentation	IT Director	Pearl Technical	Day 7

Key Vendor Contacts to Establish

☐ Enterprise Account Executive (strategic/contract issues) ☐ Customer Success Manager (ongoing relationship) ☐ Technical Implementation Specialist (integration) ☐ Support escalation path (Tier 1 → Tier 2 → Engineering)

Data/Access Prerequisites

☐ Centralized admin account with SSO integration (if applicable) ☐ Location-level admin accounts for each practice ☐ API keys for PMS integration (per location or enterprise-level) ☐ Imaging archive access credentials ☐ Historical image repository location and format documentation ☐ PACS/VNA access if centralized imaging storage exists

🔵 Vendor Required: Pearl will need read access to your imaging directories. Prepare file path documentation for all locations.

Enterprise-Level Requirements

Network Standards Across Locations

☐ Document current network topology for each location ☐ Identify locations requiring network upgrades ☐ Establish minimum bandwidth standards (25/10 Mbps floor) ☐ VPN vs. direct cloud connection decision 🟣 ☐ Network monitoring capability for troubleshooting

Hosting Architecture Decision 🟣

Approach	Pros	Cons	Recommended When
Centralized Cloud	Simplified management, unified updates	Single point of failure, bandwidth dependency	Locations have reliable connectivity
Hybrid	Resilience, local caching	More complex, higher maintenance	Mixed connectivity quality across locations

Recommendation: Pearl's cloud-native architecture favors centralized hosting. Request Pearl's enterprise architecture document for your specific deployment model.

Authentication & Credentialing

☐ SSO integration requirements (SAML 2.0, OAuth) ☐ Active Directory/Azure AD integration ☐ Role-based access control (RBAC) structure mapping ☐ Provider credential linking protocol (NPI, state license) ☐ Centralized user provisioning workflow

Stakeholder Alignment Map

Board/Investors 🟣

• Communication: Technology investment ROI thesis
• Decision authority: Capital expenditure approval if hardware refresh required
• Update cadence: Quarterly strategic update
• Owner: CEO

C-Suite

Role	Interest	Engagement Level
CEO	Strategic differentiation, ROI	Approve, sponsor
CDO	Clinical quality, liability	Drive adoption, set standards
CFO	Cost, ROI, revenue impact	Approve, monitor
VP Operations	Execution, workflow	Own implementation
CIO/IT Director	Technical, security	Own integration

Regional Managers

• Communication: Rollout plan, location sequencing rationale, escalation paths
• Decision authority: Local resource allocation, champion selection
• Update cadence: Weekly during rollout
• Owner: VP Operations

Location-Level Office Managers

• Communication: Timeline, training schedule, workflow changes, patient communication
• Decision authority: Local scheduling adjustments
• Update cadence: Daily during go-live week
• Owner: Regional Manager

Providers

• Communication: Clinical benefits, workflow changes, override protocols
• Decision authority: Clinical use discretion (within DSO standards)
• Update cadence: Pre-go-live training, weekly feedback loops
• Owner: CDO

Baseline Metrics to Capture BEFORE Go-Live

⚠️ Critical: These metrics must be captured identically across all locations to enable cross-location comparison post-deployment.

Clinical Metrics

☐ Caries detection rate per 100 BWX exams (by provider, by location) ☐ Average number of findings per FMX (by provider, by location) ☐ Perio diagnosis rate (% of exams with bone loss noted) ☐ Referral rate for endo/perio specialty care

Operational Metrics

☐ Average diagnosis presentation time (image capture to treatment plan delivery) ☐ Case acceptance rate (by procedure category, by provider, by location) ☐ Treatment plan value per exam ☐ Time from diagnosis to treatment start

Financial Metrics

☐ Revenue per patient visit ☐ Claim denial rate (by procedure code) ☐ Collection rate ☐ Radiograph retake rate (cost indicator)

Measurement Standardization Protocol

1. Define calculation methodology centrally (e.g., case acceptance = scheduled procedures / recommended procedures)
2. Set measurement period (recommend: trailing 90 days pre-implementation)
3. Extract from PMS using standardized reports (create report templates for each PMS platform)
4. Validate data with office managers before finalizing baseline
5. Store in centralized dashboard for post-implementation comparison

🟣 Executive Decision Required: Define acceptable data quality thresholds. If a location cannot produce reliable baseline metrics, decide whether to delay their rollout or proceed without comparison capability.

---

3. Location Readiness Assessment

Scoring Framework (1–5 Scale)

Factor 1: IT Infrastructure Maturity

Score	Criteria
5	Fiber internet, <2 yr old workstations, current PMS version, existing API integrations
4	Cable/high-speed internet, 2–4 yr old workstations, recent PMS updates
3	Adequate internet (25+ Mbps), functional hardware, PMS within support window
2	Marginal internet, aging workstations, PMS version 1–2 behind current
1	Unreliable connectivity, 5+ yr old hardware, legacy PMS requiring upgrade

Assessment Method: IT audit spreadsheet completed by office manager, verified by IT team remotely or on-site.

Factor 2: Staff Tenure and Adaptability

Score	Criteria
5	<10% annual turnover, previous successful tech implementations, documented training culture
4	10–20% turnover, 1+ successful tech implementation in past 2 years
3	20–30% turnover, mixed tech implementation history, stable core team
2	30–40% turnover, tech implementations have been rocky
1	>40% turnover, significant resistance to change, no recent tech adoption

Assessment Method: HR data pull + regional manager qualitative assessment.

Factor 3: Patient Volume

Score	Criteria	Risk/Impact Profile
5	Top quartile volume	Highest impact, highest risk—ideal for Wave 2/3
4	Above average volume	High impact, moderate risk
3	Average volume	Moderate impact, moderate risk—ideal for Wave 1 pilot
2	Below average volume	Lower impact, lower risk—good for pilot if other factors strong
1	Struggling volume	May indicate other issues; delay until stabilized

Note: High volume is NOT always better for early waves. Moderate volume locations with strong other factors make better pilots.

Factor 4: Existing Tech Stack Compatibility

Score	Criteria
5	PMS with proven Pearl integration, digital sensors on Pearl compatibility list, no imaging workflow conflicts
4	PMS with Pearl integration available, minor configuration needs
3	PMS integration available but not previously deployed, may require custom work
2	PMS integration exists but limited; imaging workflow changes required
1	PMS has no existing Pearl integration; would require workaround or middleware

Assessment Method: 🔵 Pearl technical team pre-assessment call (request for each location grouping by PMS/imaging stack).

Factor 5: Local Champion Availability

Score	Criteria
5	Tech-forward provider + engaged office manager both volunteered as champions
4	Either tech-forward provider OR strong office manager available and willing
3	Office manager willing but not tech-savvy; provider neutral
2	No clear champion; would need to develop one
1	Office manager or key provider actively resistant; leadership vacuum

Assessment Method: Regional manager nomination + brief call with potential champion to assess genuine interest.

Composite Scoring & Rollout Sequencing

Scoring Calculation

Factor	Weight	Rationale
IT Infrastructure	25%	Foundation—without this, nothing works
Staff Adaptability	25%	Adoption is a people problem
Tech Stack Compatibility	20%	Reduces implementation complexity
Local Champion	20%	#1 predictor of location success
Patient Volume	10%	Impact factor, but managed in wave selection

Composite Score = (IT × 0.25) + (Staff × 0.25) + (TechStack × 0.20) + (Champion × 0.20) + (Volume × 0.10)

Rollout Sequencing Recommendation

Composite Score	Wave Assignment	Rationale
4.0–5.0	Wave 1 (Pilot)	High probability of success; will generate proof points
3.5–3.9	Wave 2	Solid readiness; benefits from pilot learnings
3.0–3.4	Wave 3	May need remediation work during earlier waves
2.5–2.9	Wave 4 (if applicable)	Address infrastructure/people gaps first
<2.5	Remediation Hold	Do not deploy until score improves

Sample Location Assessment Matrix

Location	IT (25%)	Staff (25%)	Tech (20%)	Champion (20%)	Volume (10%)	Composite	Wave
Phoenix Central	5	4	5	5	3	4.55	1
Scottsdale North	4	4	4	4	4	4.00	1
Tempe Main	4	3	4	3	5	3.60	2
Mesa East	3	3	3	4	3	3.20	3
Tucson Downtown	2	2	3	2	4	2.40	Hold

⚠️ Common Failure Point: Don't let enthusiasm override readiness. A failed pilot location damages the entire rollout narrative. Select Wave 1 locations that will succeed.

---

4. Rollout Strategy

Wave Structure Recommendation

For DSOs with 15–25 Locations

Wave	Locations	Duration	Buffer	Cumulative %
Wave 1 (Pilot)	2–3	4 weeks	2 weeks	10–15%
Wave 2	5–7	4 weeks	1 week	40–50%
Wave 3	7–10	4 weeks	1 week	85–100%
Wave 4 (Cleanup)	Remaining	2–3 weeks	—	100%

For DSOs with 26–50 Locations

Wave	Locations	Duration	Buffer	Cumulative %
Wave 1 (Pilot)	3–4	4 weeks	2 weeks	8–10%
Wave 2	6–10	4 weeks	2 weeks	25–30%
Wave 3	10–15	4 weeks	1 week	55–65%
Wave 4	10–15	4 weeks	1 week	85–95%
Wave 5 (Cleanup)	Remaining	2–3 weeks	—	100%

Wave 1 Pilot Selection Criteria

Select 2–4 locations that meet ALL of the following:

☐ Composite readiness score ≥ 4.0 ☐ Identified champion available and committed ☐ Represents typical location profile (not your flagship or most unique location) ☐ Geographic proximity (enables in-person support if needed) ☐ PMS diversity representation (if you run multiple PMS platforms, include at least one of each in pilot) ☐ Provider mix representation (include at least one location with newer associates, not just senior partners)

🟣 Executive Decision: Balance "sure wins" with representation. A pilot that only includes your best locations won't surface issues you'll hit at scale.

Timeline Per Wave

Wave 1 Detailed Timeline (6 weeks total)

Week 1: Pre-Go-Live

• Day 1–2: Champion training (on-site or virtual intensive)
• Day 3–4: Technical integration verification
• Day 5: Staff training (all roles)

Week 2: Go-Live

• Day 1: Launch with full vendor support
• Days 2–5: Daily check-ins with champion

Weeks 3–4: Stabilization

• Twice-weekly check-ins
• Workflow refinement
• Issue documentation

Weeks 5–6: Assessment

• Metrics comparison vs. baseline
• Staff feedback collection
• Go/no-go decision for Wave 2
• Lessons learned documentation

Buffer (2 weeks)

• Process refinement
• Training material updates
• Champion certification for Wave 2 support

Waves 2+ Condensed Timeline (5 weeks per wave)

Pilot learnings allow compression:

• Week 1: Champion training + integration verification + staff training
• Week 2: Go-live
• Weeks 3–4: Stabilization
• Week 5: Assessment + go/no-go for next wave
• Buffer: 1–2 weeks

Go/No-Go Criteria

Criteria to Advance from Wave 1 to Wave 2 🟣

Criteria	Threshold	Status
System uptime	≥99% during pilot period
Integration stability	Zero critical integration failures
Staff training completion	100% of required roles trained
Champion confidence	Champion rates readiness ≥8/10
Provider adoption	≥80% of providers using in workflow
Patient-facing issues	Zero patient complaints related to AI
Net Promoter (internal)	Staff NPS ≥0 (not negative)

All criteria must be met to proceed. Any critical failure requires remediation and extended pilot.

Escalation Path for Go/No-Go Decision

1. Implementation team recommendation → VP Operations
2. VP Operations decision for Wave 2
3. CDO input required if clinical concerns raised
4. CEO notification if Wave 1 fails 🟣

Rollback Plan

Triggers for Wave Rollback

• Critical integration failure affecting patient care
• Data security incident

• 25% provider refusal to use system

• Sustained system performance issues (>4 hours cumulative downtime in any week)

Rollback Procedure

Immediate (within hours):

1. Disable Pearl overlay in imaging software
2. Notify regional manager and VP Operations
3. Document incident details
4. 🔵 Contact Pearl emergency support

Short-term (within 24 hours):

1. Staff communication: "Temporary pause for optimization"
2. Patient communication script if needed
3. Root cause analysis initiation

Recovery:

1. Resolve root cause with Pearl
2. Test fix in isolated environment
3. Re-deploy with additional monitoring
4. Extended stabilization period before resuming wave progression

⚠️ Key Principle: A single location rollback does NOT stop the entire wave. Isolate the failing location, continue with others, and address the issue in parallel.

---

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integrations

Dentrix Integration

Prerequisites: ☐ Dentrix G7.5 or higher (G8 recommended) ☐ ePrescribe module enabled ☐ Document Center active ☐ Valid Dentrix support agreement

Step-by-Step Integration:

1. ☐ 🔵 Obtain Pearl Dentrix integration package from Pearl support
2. ☐ Backup Dentrix database before any installation
3. ☐ Install Pearl Bridge Service on Dentrix server (15 min)
4. ☐ Configure bridge service with Pearl API credentials
5. ☐ Map Dentrix user accounts to Pearl user accounts
6. ☐ Configure auto-launch settings for Pearl with image capture
7. ☐ ⚠️ Test with sample patient (use designated test patient record)
8. ☐ Verify findings transfer to clinical notes
9. ☐ Configure Document Center auto-filing for Pearl reports
10. ☐ Test with 5 different providers to verify user mapping

Estimated time: 2–3 hours per location (experienced IT); 4–5 hours (first-time deployment)

Eaglesoft Integration

Prerequisites: ☐ Eaglesoft 21.20 or higher ☐ Smart Image module installed ☐ API access enabled (Patterson support call may be required)

Step-by-Step Integration:

1. ☐ 🔵 Request Pearl Eaglesoft integration installer
2. ☐ Verify Patterson API access is active
3. ☐ ⚠️ Disable Eaglesoft Smart Image AI features to prevent conflict
4. ☐ Install Pearl integration service
5. ☐ Configure TWAIN bridge settings
6. ☐ Map user credentials
7. ☐ Test sensor trigger → Pearl capture → Eaglesoft display flow
8. ☐ Configure clinical notes integration
9. ☐ Verify patient data sync (name, DOB, chart number)
10. ☐ Test treatment planning workflow impact

Estimated time: 3–4 hours per location

⚠️ Common Failure Point: Patterson API access often requires escalation. Start this process 2 weeks before planned integration.

Open Dental Integration

Prerequisites: ☐ Open Dental version 22.1 or higher ☐ API key generated in Open Dental (Setup → Advanced Setup → API) ☐ Direct database access credentials (if using on-premise)

Step-by-Step Integration:

1. ☐ Generate Open Dental API key with appropriate permissions
2. ☐ 🔵 Provide API key to Pearl implementation team
3. ☐ Install Pearl Open Dental bridge
4. ☐ Configure webhook endpoints (if using cloud sync)
5. ☐ Map user accounts via Pearl admin console
6. ☐ Test image capture → Pearl analysis → Open Dental display
7. ☐ Configure treatment plan integration
8. ☐ Set up procedure code mapping for Pearl-detected findings
9. ☐ Test with multiple image types (BWX, PA, Pano)
10. ☐ Verify audit trail logging

Estimated time: 2–3 hours per location (Open Dental's open architecture simplifies integration)

Denticon (Cloud) Integration

Prerequisites: ☐ Denticon Enterprise license ☐ Admin access to Denticon ☐ 🔵 Pearl-Denticon integration enabled (contact Planet DDS)

Step-by-Step Integration:

1. ☐ 🔵 Planet DDS enables Pearl integration in Denticon backend
2. ☐ Configure Pearl API credentials in Denticon admin
3. ☐ Map provider credentials
4. ☐ Configure image routing rules
5. ☐ Test cloud-to-cloud image transfer
6. ☐ Verify latency (target: <3 seconds from capture to analysis)
7. ☐ Configure treatment plan integration
8. ☐ Test multi-location user access

Estimated time: 1–2 hours per location (cloud-to-cloud simplifies process)

Imaging System Integration

Sensor/Direct Digital Radiography

Sensor Brand	Integration Method	Notes
Dexis	TWAIN, native integration	Full support, direct capture
Schick	TWAIN	Verify TWAIN driver version
Carestream	TWAIN, DICOM	Preferred: DICOM for advanced features
Gendex	TWAIN	Test capture timing
XDR	TWAIN	May require driver update

Standard Sensor Integration Steps:

1. ☐ Document current imaging software and sensor model
2. ☐ Install/verify TWAIN drivers (current versions)
3. ☐ Configure Pearl as TWAIN device destination
4. ☐ Test single image capture
5. ☐ Test FMX sequence capture
6. ☐ Test BWX set capture
7. ☐ Verify image quality transmission (no compression artifacts)
8. ☐ Confirm patient data association

Panoramic/CBCT Integration

Equipment	Integration Method	Pearl Capability
Planmeca	DICOM	Pano analysis, CBCT limited
Carestream	DICOM	Full pano support
Dentsply Sirona	DICOM	Pano analysis
i-CAT	DICOM	Pano analysis
CBCT General	DICOM	Limited—2D analysis of exports

⚠️ Note: Pearl's primary strength is 2D radiograph analysis. CBCT integration is evolving—confirm current capabilities with Pearl before setting expectations.

Pano/CBCT Integration Steps:

1. ☐ Enable DICOM export on imaging equipment
2. ☐ Configure DICOM send to Pearl endpoint
3. ☐ 🔵 Provide equipment model and DICOM settings to Pearl
4. ☐ Test single pano transmission
5. ☐ Verify patient data in DICOM header transfers correctly
6. ☐ Configure auto-send vs. manual send workflow
7. ☐ Test image display in Pearl Practice Intelligence

Test Environment Setup

Centralized Test Environment (Recommended for DSOs)

☐ Establish dedicated test tenant in Pearl (separate from production) ☐ Create test patient records (minimum 10 with varied conditions) ☐ Configure test environment to mirror production settings ☐ Develop standard test cases:

• Single PA capture
• 4BW set capture
• FMX capture
• Pano capture
• Multi-user simultaneous use
• Network interruption recovery

Validation Checklist

☐ Image capture triggers Pearl analysis ☐ Analysis completes in <10 seconds for 2D radiographs ☐ Findings overlay displays correctly on image ☐ Findings summary transfers to PMS clinical notes ☐ Provider can accept/modify/reject findings ☐ Patient record correctly associated ☐ Audit trail captures provider decisions ☐ System recovers gracefully from network interruption ☐ Multiple providers can analyze simultaneously ☐ Reports generate correctly

Historical Data Ingestion

🟣 Decision Required: Will you import historical images for Pearl analysis?

Approach	Pros	Cons	Recommendation
No historical import	Faster deployment, cleaner baseline	No retrospective analysis	Recommended for initial deployment
Selective import (12 months)	Enables comparison studies	Moderate effort, storage costs	Consider after stabilization
Full archive import	Complete historical analysis	High effort, diminishing returns	Not recommended initially

If Historical Import Desired:

1. ☐ Document image archive location and format
2. ☐ Calculate storage volume (GB/TB)
3. ☐ 🔵 Engage Pearl professional services for migration planning
4. ☐ Establish patient matching protocol (chart number, name, DOB)
5. ☐ Plan batch import schedule (off-hours recommended)
6. ☐ Define success criteria for import validation

Security and HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

☐ Business Associate Agreement (BAA)

• 🔵 Execute BAA with Pearl (covers all entities)
• Verify BAA terms align with your security requirements
• Document BAA in compliance repository

☐ Data Governance

• Document what PHI Pearl accesses (images, patient demographics)
• Map data flow: capture → transmission → Pearl cloud → storage → return
• Verify Pearl's data retention policy aligns with your requirements
• Confirm data deletion protocols

☐ Access Controls

• Implement role-based access control (RBAC)
• Configure SSO integration
• Enable multi-factor authentication (MFA) for admin accounts
• Document user provisioning/deprovisioning procedures
• Establish quarterly access review cadence

☐ Transmission Security

• Verify TLS 1.2+ for all data transmission
• Confirm encryption at rest (AES-256 or equivalent)
• Document network security requirements

☐ Audit Logging

• Verify Pearl audit logs capture required events
• Configure log retention (minimum 6 years for HIPAA)
• Establish log review procedures

☐ Incident Response

• Document Pearl's breach notification procedures
• Establish communication protocol with Pearl security team
• Test incident response escalation path

☐ Risk Assessment

• Add Pearl to organizational risk assessment
• Document risk treatment decisions
• Schedule annual review

🔵 Vendor Required: Request Pearl's SOC 2 Type II report and HIPAA compliance documentation.

Enterprise Configuration Standards

Standardized Configuration Template

Settings to Standardize Centrally:

Setting	Standard Value	Rationale
Detection sensitivity	Medium (default)	Consistent diagnostic thresholds
Pathology categories enabled	All categories ON	Comprehensive screening
Auto-overlay display	Enabled	Consistent provider experience
Clinical note integration	Enabled	Documentation compliance
Report format	Standard DSO template	Unified patient communication
User timeout	15 minutes	HIPAA compliance
Audit logging	Full	Compliance requirement
Alert thresholds	Per CDO specification	Clinical governance

Location-Specific Configuration Allowed

Setting	Local Discretion	Rationale
Provider-specific preferences	Yes (within bounds)	Provider workflow accommodation
Specialty emphasis	Yes	Endo vs. GP vs. Pedo different needs
Patient communication scripts	Yes (from approved templates)	Local patient population
Monitor display preferences	Yes	Hardware variability
Report printer settings	Yes	Equipment differences

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Select one primary champion per location, with a backup champion identified:

Required Characteristics: ☐ Minimum 12 months tenure at location ☐ Demonstrated technology aptitude (successful adoption of previous tech) ☐ Respected by clinical and admin staff ☐ Available for 6–8 hours initial training ☐ Committed to ongoing champion responsibilities ☐ Communication skills to train others

Ideal Champion Profiles (in priority order):

1. Tech-forward associate dentist with teaching inclination
2. Senior hygienist with influence and tech comfort
3. Engaged office manager with clinical understanding
4. Lead dental assistant with peer respect

Not Recommended:

• Newest staff members (insufficient credibility)
• Providers with historical tech resistance (will undermine)
• Staff with planned departures within 6 months

Champion Responsibilities

During Rollout:

• Complete champion certification training
• Conduct staff training at their location
• Serve as first-line support for questions
• Document issues and feedback
• Participate in daily check-ins during go-live week
• Provide weekly feedback to central team

Ongoing:

• Train new hires
• Conduct quarterly refresher sessions
• Escalate unresolved issues
• Share best practices with other champions
• Participate in monthly champion calls

Champion Certification Training

Duration: 6–8 hours (can be split across two days)

Format: Live virtual or in-person with Pearl trainer + internal implementation team

Curriculum:

Module	Duration	Content
Pearl Platform Overview	1 hr	Product capabilities, AI fundamentals, evidence base
Clinical Workflow Deep Dive	2 hrs	Image capture, analysis, interpretation, documentation
Hands-On Practice	2 hrs	Guided practice with sample cases, edge cases
Training Delivery Skills	1 hr	How to train