Pearl — Implementation Playbook (DSO)

Pearl AI Implementation Playbook

Diagnostic Imaging Intelligence for Dental Support Organizations

---

1. Executive Summary

What Pearl Does

Pearl is an FDA-cleared AI-powered diagnostic imaging platform that analyzes dental radiographs in real-time, automatically detecting pathologies including caries, periapical lesions, calculus, and bone loss. The system integrates with existing imaging workflows to provide visual overlays and clinical annotations that support—not replace—provider diagnosis.

Why DSOs Benefit Specifically from Diagnostic Imaging AI

Scale Advantages:

• Standardized diagnostic quality across 15–50+ locations regardless of individual provider experience levels
• Centralized visibility into diagnostic patterns, enabling identification of under-diagnosis or over-diagnosis trends at specific locations
• Aggregate data insights that reveal portfolio-wide clinical opportunities (e.g., "Location 12 detects 40% fewer interproximal caries than network average—investigate")

Standardization Value:

• Reduces variability in treatment recommendations between providers, strengthening patient trust and brand consistency
• Creates defensible clinical documentation that supports treatment acceptance and reduces liability exposure
• Establishes consistent baseline for clinical quality metrics across all locations

Data Aggregation Power:

• Enterprise dashboards reveal which locations convert AI-detected findings into treatment at higher rates
• Enables evidence-based conversations with underperforming providers or locations
• Supports value-based care contracts with payers by demonstrating diagnostic rigor

Expected Timeline: Decision to Full Deployment

Phase	Timeline	Milestone
Pre-Implementation	Weeks 1–2	Technical readiness, baseline metrics, stakeholder alignment
Wave 1 Pilot	Weeks 3–6	2–3 pilot locations live, learning capture
Wave 2 Expansion	Weeks 7–10	5–8 additional locations
Wave 3 Full Deployment	Weeks 11–16	Remaining locations
Optimization	Weeks 17–24	ROI validation, workflow refinement

Total timeline: 4–6 months for full deployment across 15–50 locations

---

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

Technical Requirements

Hardware Requirements

☐ Verify minimum workstation specifications at each location:

• Processor: Intel i5 (8th gen+) or AMD equivalent
• RAM: 8GB minimum (16GB recommended)
• Display: 1920x1080 resolution minimum for overlay visibility
• Storage: 50GB available for local caching

☐ Confirm imaging sensor compatibility:

• Pearl supports most major digital sensors (Dexis, Schick, Carestream, Planmeca, Vatech)
• Document sensor make/model at each location
• ⚠️ Phosphor plate systems may require workflow modifications

☐ Network requirements per location:

• Minimum 25 Mbps upload/download (50 Mbps recommended)
• Latency under 100ms to Pearl cloud servers
• ⚠️ Locations with satellite internet or unstable connections are high-risk

Software Requirements

☐ Practice Management System (PMS) versions:

• Dentrix G6.2 or higher
• Eaglesoft 21.0 or higher
• Open Dental 22.1 or higher
• Other PMS: Confirm Pearl integration availability

☐ Imaging software compatibility:

• Confirm imaging software version at each location
• Document bridge configurations currently in use

☐ Operating system requirements:

• Windows 10 (version 1903+) or Windows 11
• macOS 10.15+ (if applicable)

Enterprise-Level Network Standards 🟣

☐ Decision required: Centralized hosting vs. location-level hosting

• Recommendation: Cloud-based centralized hosting through Pearl for simplified management
• If on-premise requirements exist (rare), document compliance constraints

☐ Standardize network configuration across locations:

• Firewall rules for Pearl endpoints (whitelist required domains)
• VPN considerations if locations use centralized networking

☐ Single Sign-On (SSO) integration:

• 🔵 Confirm Pearl SSO compatibility with your identity provider (Azure AD, Okta, Google Workspace)
• Document SSO requirements and timeline

☐ Centralized credentialing approach:

• Map provider credentials to Pearl user accounts
• Determine role-based access levels (provider, hygienist, admin)

---

Vendor Onboarding Steps

☐ 🔵 Execute Master Service Agreement (MSA) and Business Associate Agreement (BAA)

• Estimated time: 1–2 weeks including legal review

☐ 🔵 Establish key vendor contacts:

• Implementation Project Manager (primary contact)
• Technical Integration Specialist
• Enterprise Account Manager
• Support escalation path and SLAs

☐ 🔵 Schedule kickoff call with Pearl implementation team

• Attendees: VP Operations, CDO, IT Director, Pearl PM
• Agenda: Timeline confirmation, technical requirements review, pilot location selection

☐ 🔵 Request Pearl's enterprise deployment documentation:

• Integration guides for your specific PMS/imaging systems
• API documentation if custom integrations needed
• Security and compliance certifications

---

Data/Access Prerequisites

☐ Create Pearl admin accounts for central IT team (minimum 2 administrators)

☐ 🔵 Obtain API keys for PMS integrations (per location or centralized)

☐ Document imaging archive access method at each location:

• Local server storage vs. cloud imaging
• DICOM server configurations if applicable

☐ ⚠️ Verify HIPAA-compliant data transmission:

• Confirm Pearl's encryption standards (TLS 1.2+ in transit, AES-256 at rest)
• Review data residency requirements if applicable

☐ Prepare sample image sets for testing:

• Collect 10–20 representative radiographs from pilot locations
• Include variety: BWX, PAs, panos, FMX series

---

Internal Stakeholder Alignment

Stakeholder Alignment Map 🟣

Stakeholder	Role in Implementation	Communication Frequency	Key Concerns to Address
Board/Investors	Approval of investment; ROI visibility	Monthly summary	ROI timeline, competitive advantage, risk mitigation
CEO/COO	Executive sponsorship; resource allocation	Bi-weekly updates	Strategic alignment, timeline adherence, cross-functional coordination
Chief Dental Officer	Clinical validation; provider adoption	Weekly during rollout	Clinical accuracy, workflow impact, liability considerations
VP of Operations	Implementation ownership; operational coordination	Daily during active phases	Location readiness, staffing impact, timeline management
IT Director	Technical integration; support infrastructure	Daily during integration	Security, integration complexity, support burden
Regional Managers	Location coordination; local accountability	Weekly during their region's rollout	Staff burden, patient experience, performance metrics
Office Managers	Local execution; staff coordination	Daily during location go-live	Training time, workflow disruption, team resistance
Providers	Clinical adoption; workflow integration	Training sessions + ongoing	Diagnostic autonomy, time impact, professional judgment preservation

Alignment Actions

☐ 🟣 Present implementation business case to executive team

• Include: Investment cost, expected ROI, timeline, resource requirements

☐ 🟣 Obtain formal budget approval

• Software licensing (per-location or enterprise pricing)
• Implementation labor costs (internal and external)
• Training time allocation

☐ Brief regional managers on rollout timeline and their role

☐ Communicate initiative to office managers (overview, no action yet)

---

Baseline Metrics Collection ⚠️

Critical: Standardize measurement methodology across all locations before go-live so post-implementation comparison is valid.

Clinical Metrics (collect from PMS reports)

☐ Case acceptance rate by location (last 6 months)

• Calculation: Treatment accepted ÷ Treatment presented
• Segment by procedure category (restorative, perio, endo, etc.)

☐ Average diagnosis time (if measurable)

• Time from image capture to treatment plan entry

☐ Pathology detection rate by provider

• Number of caries diagnoses per 100 BWX sets
• Perio diagnoses per 100 patients seen

Operational Metrics

☐ Patient throughput per operatory per day

☐ Radiograph retake rate (if trackable)

☐ Treatment completion rate (treatment accepted vs. treatment completed)

Financial Metrics

☐ Revenue per patient visit by location

☐ Average restorative production per provider

☐ Claim denial rate (particularly for procedures requiring radiographic documentation)

Standardization Requirements 🟣

☐ Decision required: Confirm consistent reporting methodology

• Are all locations using the same PMS report templates?
• Are production numbers calculated identically (write-offs, adjustments)?

☐ Create baseline data capture template (spreadsheet or BI dashboard)

☐ Assign responsibility for baseline collection at each location

☐ Set deadline: All baseline data collected by end of Week 2

---

3. Location Readiness Assessment

Readiness Scoring Framework

Score each location on the following factors using a 1–5 scale, then calculate composite score.

Factor 1: IT Infrastructure Maturity (Weight: 25%)

Score	Criteria
5	High-speed internet (100+ Mbps), workstations <2 years old, latest PMS version, dedicated IT support
4	Adequate internet (50+ Mbps), workstations <4 years old, supported PMS version
3	Meets minimum requirements but near thresholds; occasional connectivity issues
2	Below minimum in 1–2 areas; requires upgrades before deployment
1	Significant infrastructure gaps; major investment needed

Factor 2: Staff Tenure and Adaptability (Weight: 20%)

Score	Criteria
5	Low turnover (<15%), history of successful tech adoptions, staff actively requests new tools
4	Moderate turnover (15–25%), previous tech rollouts succeeded with support
3	Average turnover (25–35%), mixed tech adoption history
2	High turnover (35–50%), past tech rollouts struggled
1	Very high turnover (>50%), resistant culture, failed previous implementations

Factor 3: Patient Volume (Weight: 20%)

Score	Criteria	Note
5	Very high volume (40+ patients/day)	High impact but requires robust support
4	High volume (30–40 patients/day)	Strong ROI potential
3	Moderate volume (20–30 patients/day)	Balanced risk/reward
2	Lower volume (10–20 patients/day)	Lower immediate impact
1	Very low volume (<10 patients/day)	Consider deprioritizing

Note: For Wave 1 pilots, moderate volume (score 3) may be preferable to reduce risk while still generating meaningful data.

Factor 4: Tech Stack Compatibility (Weight: 20%)

Score	Criteria
5	PMS and imaging system have documented Pearl integrations; same stack as other locations
4	Pearl integration available; minor configuration needed
3	Integration possible but not pre-built; may require custom work
2	Non-standard tech stack; integration uncertain
1	Incompatible systems; would require tech stack replacement

Factor 5: Local Champion Availability (Weight: 15%)

Score	Criteria
5	Tech-forward provider AND engaged office manager; both enthusiastic about AI
4	Strong champion available (either provider or manager); other is supportive
3	Potential champion identified but needs development
2	No clear champion; staff are neutral to change
1	Key staff actively resistant; no champion candidates

---

Scoring Calculation

Composite Score = (IT × 0.25) + (Staff × 0.20) + (Volume × 0.20) + (Tech × 0.20) + (Champion × 0.15)

Readiness Tiers

Tier	Score Range	Rollout Wave
High Readiness	4.0–5.0	Wave 1 candidates (pilot)
Moderate Readiness	3.0–3.9	Wave 2
Developing Readiness	2.0–2.9	Wave 3 (with remediation)
Not Ready	<2.0	Defer; address prerequisites first

---

Recommended Rollout Sequence Process

Step 1: Score All Locations

☐ Complete readiness assessment for all locations (Weeks 1–2) ☐ Enter scores into master tracking spreadsheet ☐ Rank locations by composite score

Step 2: Select Wave 1 Pilot Locations

☐ 🟣 Select 2–3 locations with:

• High readiness scores (4.0+)
• Representative characteristics (different regions, different providers, different patient demographics)
• Manageable risk profile (avoid your highest-volume flagship and newest acquisition)
• Strong local champions who will provide honest feedback

Step 3: Map Remaining Waves

☐ Assign Wave 2 locations (moderate readiness, 3.0+) ☐ Assign Wave 3 locations (remaining locations) ☐ Create remediation plans for any location scoring <2.5

---

Sample Readiness Assessment Template

Location	IT (×.25)	Staff (×.20)	Volume (×.20)	Tech (×.20)	Champion (×.15)	Composite	Wave
Oakbrook	5	4	3	5	4	4.25	1
Riverside	4	4	4	4	5	4.15	1
Downtown	4	3	5	4	3	3.85	2
Westside	3	3	3	4	3	3.20	2
Northgate	3	2	2	3	2	2.45	3 (remediate)

---

4. Rollout Strategy

Wave Structure Overview

Recommended Wave Model for 15–50 Locations

Wave	Locations	Duration	Purpose
Wave 1 (Pilot)	2–3 locations	4 weeks	Prove integration, refine training, identify issues
Wave 2	5–8 locations	3 weeks	Validate scalability, stress-test support capacity
Wave 3	Remaining locations	3–5 weeks	Full deployment using proven playbook

---

Wave 1: Pilot Locations (Weeks 3–6)

Selection Criteria for Wave 1 🟣

☐ High readiness score (4.0+) but not necessarily the highest

• Avoid locations where any failure would be highly visible to board/patients

☐ Strong local champion willing to provide detailed daily feedback

☐ Representative of broader portfolio:

• If you have multiple PMS systems, include one of each in Wave 1
• If you have urban and suburban locations, include both
• If you have varying provider tenure levels, include variety

☐ Manageable patient volume:

• High enough to generate meaningful data (20+ patients/day)
• Not so high that a disruption creates major patient experience issues

☐ Geographic accessibility for in-person support if needed

Wave 1 Timeline

Week	Activities
Week 3	Install and configure at Pilot Location 1; begin staff training
Week 3.5	Go-live at Pilot Location 1; parallel run begins
Week 4	Install/configure Pilot Locations 2–3; Location 1 daily monitoring
Week 4.5	Go-live at Pilot Locations 2–3
Week 5	All pilots in production; intensive monitoring; workflow refinements
Week 6	Wave 1 retrospective; document learnings; update playbook

Wave 1 Deliverables Before Advancing

☐ Integration validated across all pilot PMS configurations ☐ Training materials refined based on staff feedback ☐ Support escalation paths tested ☐ Baseline vs. post-go-live metrics comparison initiated ☐ Staff resistance patterns documented with solutions ☐ Go/no-go recommendation for Wave 2

---

Wave 2: Expansion (Weeks 7–10)

Selection Criteria for Wave 2

☐ Readiness score 3.0+ ☐ Prerequisites addressed from Wave 1 learnings ☐ Geographic clustering (if possible) to enable efficient regional support

Wave 2 Timeline

Week	Activities
Week 7	Install and configure Wave 2 locations (batch 1: 3–4 locations)
Week 8	Go-live batch 1; install/configure batch 2 (remaining Wave 2 locations)
Week 9	Go-live batch 2; all Wave 2 locations in production
Week 10	Stabilization; Wave 2 retrospective; final prep for Wave 3

Wave 2 Learning Capture

☐ Document any new integration issues not seen in Wave 1 ☐ Identify support capacity constraints (can central team handle 5–8 locations?) ☐ Refine training delivery model based on scale

---

Wave 3: Full Deployment (Weeks 11–16)

Approach

• Deploy to remaining locations using refined playbook
• Higher velocity: 3–5 locations per week depending on support capacity
• Champions from Wave 1–2 locations can assist as peer coaches

Timeline Factors

• Number of remaining locations
• Geographic distribution
• Support team capacity
• Holiday/seasonal considerations (avoid major schedule disruptions)

---

Go/No-Go Criteria Between Waves 🟣

Criteria to Advance to Next Wave

Category	Minimum Threshold
Technical stability	<5% system downtime; no data integrity issues; integration functioning
User adoption	>80% of providers actively using Pearl during image review
Training completion	100% of required staff trained at previous wave locations
Support capacity	Central team response time <4 hours for critical issues
Patient impact	No patient complaints directly attributable to Pearl
Workflow integration	Average image-to-treatment-plan time not increased by >2 minutes

Red Flags That Require Pause 🟣

☐ ⚠️ Critical data integrity issue (lost images, incorrect patient matching) ☐ ⚠️ Integration failure affecting >1 location ☐ ⚠️ Provider refusing to use system at >1 pilot location ☐ ⚠️ HIPAA or security incident ☐ ⚠️ Central support team overwhelmed (>24 hour response times)

---

Rollback Plan

If a Wave Fails

Immediate (Day 1–3): ☐ Convene incident response call: VP Ops, IT Director, CDO, Pearl PM ☐ Determine scope: single location vs. wave-wide issue ☐ If single location: isolate and continue wave ☐ If wave-wide: pause all rollout activity

Short-term (Week 1–2): ☐ Document failure mode in detail ☐ 🔵 Engage Pearl engineering for root cause analysis ☐ Develop remediation plan with timeline ☐ Communicate transparently with affected location staff

Rollback Mechanics (if needed): ☐ Pearl can be disabled per-location without affecting PMS or imaging ☐ Revert to pre-Pearl workflow (providers review images without AI overlay) ☐ Historical images and Pearl annotations remain accessible for continuity ☐ No data loss from Pearl → original images untouched

Recovery: ☐ Retest in controlled environment before resuming ☐ Add to risk register for future waves ☐ 🟣 Executive decision required to resume rollout

---

5. Configuration & Integration (Weeks 2–3)

Step-by-Step PMS Integrations

Dentrix Integration

☐ 🔵 Contact Pearl for Dentrix bridge installer package ☐ Verify Dentrix version (G6.2 or higher required) ☐ Back up Dentrix database before integration ☐ ⚠️ Run installer on each workstation that will access Pearl (not server-side only) ☐ Configure bridge settings:

• Enable automatic image pass-through to Pearl
• Set patient record linking preferences
• Configure provider mapping ☐ Test bidirectional communication:
• Image captured in Dentrix → appears in Pearl within 30 seconds
• Pearl findings can be viewed without leaving Dentrix workflow ☐ 🔵 Verify patient demographic sync accuracy

Eaglesoft Integration

☐ 🔵 Request Eaglesoft-specific integration documentation from Pearl ☐ Verify Eaglesoft version (21.0 or higher required) ☐ ⚠️ Note: Eaglesoft imaging module version must match PMS version ☐ Install Pearl connector following vendor guide ☐ Configure imaging workflow:

• Mount point for image files
• Automatic vs. manual image submission ☐ Test with sample images before clinical use ☐ Verify Eaglesoft Smart Doc integration if used

Open Dental Integration

☐ 🔵 Enable Pearl integration through Open Dental's Program Links ☐ Navigate to Setup → Program Links → Pearl ☐ Enter Pearl API credentials ☐ Configure image acquisition settings ☐ Test bidirectional patient/image sync ☐ ⚠️ If using Open Dental imaging module, verify bridge compatibility ☐ If using third-party imaging (XDR, Apteryx), configure both bridges

---

Imaging System Integration

Digital Sensor Integration (Dexis, Schick, Carestream)

☐ Document exact sensor model and software version at each location ☐ 🔵 Confirm Pearl supports specific sensor model ☐ Configure image routing:

• Images captured → saved to local/network folder → Pearl processes
• Or direct API integration (if supported) ☐ Test image quality and resolution pass-through ☐ Verify DICOM header preservation

Panoramic/CBCT Integration

☐ Document pan/CBCT equipment at each location ☐ Configure PACS connection if applicable ☐ 🔵 Confirm Pearl supports 3D imaging analysis for your equipment ☐ ⚠️ Note: Pearl's 3D capabilities may vary; confirm feature availability

---

Test Environment Setup

Centralized Test Environment (Recommended for DSO) 🟣

☐ Decision required: Establish centralized test instance vs. per-location testing

• Recommendation: Centralized test environment at headquarters or IT-managed location
• Reduces risk of production issues during testing
• Enables consistent test protocols

☐ 🔵 Request Pearl sandbox/test environment credentials ☐ Install test instance of PMS (matching production version) ☐ Configure imaging system simulation or import test images ☐ Document test patient records (use fictional data)

Validation Checklist

☐ Image transmission test:

• Capture test image → verify Pearl receives within 30 seconds
• Confirm image quality is not degraded

☐ AI detection test:

• Submit known images with confirmed pathology
• Verify Pearl identifies expected findings
• Document any discrepancies for vendor review

☐ User experience test:

• Provider opens patient chart → views image → sees Pearl overlay
• Confirm no added clicks vs. current workflow
• Time the workflow and compare to baseline

☐ Performance test:

• Submit 10 images rapidly (simulating busy morning)
• Verify no queuing delays or system slowdown

☐ Failover test:

• Disconnect internet → verify graceful degradation (images still viewable without Pearl)
• Reconnect → verify Pearl catches up on pending images

---

Data Migration / Historical Image Ingestion

Considerations 🟣

☐ Decision required: Will Pearl analyze historical images or only new images going forward?

Option A: New Images Only (Recommended for initial deployment)

• Simpler implementation
• No bulk processing load
• Pearl value demonstrates over time as new images accumulate

Option B: Historical Image Ingestion

• Pearl can analyze historical images to establish baseline
• Useful for identifying previously undiagnosed pathology
• ⚠️ Significant processing time and potential cost
• ⚠️ May surface "missed" diagnoses requiring careful clinical/legal handling

☐ If historical ingestion desired:

• 🔵 Request Pearl bulk processing quote and timeline
• Document image archive location and format
• Establish protocol for handling newly detected findings on old images

---

Security and HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

☐ Business Associate Agreement (BAA):

• 🔵 Execute BAA with Pearl covering all locations
• Verify BAA scope includes all planned use cases
• File executed BAA with compliance documentation

☐ Data Governance:

• Document what data is transmitted to Pearl (images, patient identifiers, clinical data)
• Confirm data minimization practices (only necessary data shared)
• 🟣 Review and approve Pearl's data retention and deletion policies

☐ Access Controls:

• Implement role-based access consistent with your HIPAA policies
• Configure automatic session timeout
• Enable audit logging for all Pearl access
• Establish user provisioning/deprovisioning workflow

☐ Encryption and Transmission:

• Verify TLS 1.2+ for all data in transit
• Confirm AES-256 encryption for data at rest
• Document encryption standards for compliance records

☐ Incident Response:

• 🔵 Obtain Pearl's breach notification procedures
• Confirm compatibility with your incident response plan
• Establish communication chain for potential security events

☐ Workforce Training:

• Include Pearl-specific items in HIPAA training updates
• Document new workflows in Privacy and Security policies

---

Configuration Standardization

Centralized Settings (Standardize Across All Locations)

Setting	Standard Value	Rationale
Detection sensitivity	Medium (default)	Balance between sensitivity and false positives
Overlay display format	Color-coded highlights	Consistent visual language
Auto-display behavior	Show on image open	Ensures providers see Pearl output
Audit logging	Enabled	Compliance and quality tracking
Session timeout	15 minutes	Security standard
User roles	Provider, Hygienist, Admin	Consistent access model

Location-Specific Settings (Allow Local Variation)

Setting	Variation Allowed	Rationale
Provider preferences	Display preferences per provider	Accommodate workflow style
Specialty focus	Adjust detection emphasis (perio, pedo, etc.)	Match practice specialty mix
Alert thresholds	Adjust notification triggers	Match local workflow
Report formatting	Minor customization	Match existing documentation style

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Each location needs one designated Pearl Champion who will:

• Attend centralized champion training
• Train their local team
• Serve as first-line support during rollout
• Provide feedback to central team

Selection Criteria: ☐ Tech-forward mindset (comfortable learning new software) ☐ Respected by clinical and admin staff ☐ Available for 4-hour champion training session ☐ Available for increased support duties during go-live week ☐ Ideally: Office Manager or senior provider

Champion Responsibilities:

• Complete champion certification training
• Deliver role-specific training to all location staff
• Monitor adoption during first 30 days
• Escalate issues to regional manager
• Participate in weekly champion calls during rollout

---

Champion Certification Training (4 hours)

Module 1: Platform Fundamentals (60 minutes)

• Pearl architecture and how it works
• What AI can and cannot do
• Clinical validation data and FDA clearance
• Live platform navigation

Module 2: Clinical Workflow Integration (60 minutes)

• Image capture → Pearl analysis → provider review workflow
• Interpreting Pearl overlays and confidence indicators
• When providers should override AI suggestions
• Documentation best practices

Module 3: Training Delivery Skills (60 minutes)

• How to train different roles (providers, hygienists, front desk)
• Handling common resistance patterns
• Using standardized training materials
• Assessing staff readiness

Module 4: Support and Escalation (60 minutes)

• Common troubleshooting scenarios
• Escalation paths and when to use them
• Feedback collection protocols
• Success metrics to track

☐ 🔵 Pearl provides champion certification training (virtual or in-person) ☐ Champions must pass certification quiz before training their teams ☐ Document certified champions per location

---

Role-Specific Training Outlines

Dentists/Providers (90 minutes)

Core Training Content:

• What Pearl detects: caries, periapical lesions, calculus, bone loss, etc.
• How to interpret visual overlays and confidence scores
• Clinical validation: sensitivity/specificity data
• Critical message: Pearl supports diagnosis, doesn't make diagnosis
• When and how to override Pearl (and documentation requirements)
• Impact on treatment planning workflow

Training Format:

• 30 minutes: Didactic overview (video or live)
• 45 minutes: Hands-on practice with sample images
• 15 minutes: Q&A and workflow customization

Common Resistance Points and Responses:

Resistance	Response
"AI will miss things"	"Pearl has 95%+ sensitivity; it's a second set of eyes, not a replacement for your clinical judgment. You remain responsible for diagnosis."
"This will slow me down"	"After the first week, most providers report no time difference. The overlay is instant—you're not waiting for results."
"I don't need help diagnosing"	"Pearl catches the 10% that even experienced providers miss, especially on busy days. Think of it as malpractice protection."
"What if I disagree with Pearl?"	"You always have final say. Document your reasoning, and you've created a defensible record showing you considered the AI input."

Day 1 Provider Cheat Sheet:

+------------------------------------------+
| PEARL PROVIDER QUICK REFERENCE           |
+------------------------------------------+
| HOW TO VIEW PEARL ANALYSIS:              |
| • Open image as normal                   |
| • Pearl overlay appears automatically    |
| • Click legend to toggle finding types   |
|                                          |
| READING THE OVERLAY:                     |
| • Red = high confidence finding          |
| • Yellow = moderate confidence           |
| • Hover for details and measurements     |
|                                          |
| IF YOU DISAGREE:                         |
| • Document your clinical reasoning       |
| • Pearl's suggestion ≠ your diagnosis    |
| • You remain the diagnosing provider     |
|                                          |
| SUPPORT:                                 |
| • Questions: [Local Champion Name]       |
| • Technical issues: [Support Number]     |
+------------------------------------------+

---

Hygienists (45 minutes)

Core Training Content:

• Overview of Pearl and how it supports the practice
• Hygienist touchpoints (if applicable):
  • Viewing Pearl findings during patient prep
  • Understanding calculus detection for scaling planning
  • Communicating findings to providers
• What hygienists should NOT do (no independent diagnosis communication to patients)

Training Format:

• 20 minutes: Overview video
• 15 minutes: Live walkthrough of hygiene-specific features
• 10 minutes: Q&A

Day 1 Hygienist Cheat Sheet:

+------------------------------------------+
| PEARL HYGIENIST QUICK REFERENCE          |
+------------------------------------------+
| YOUR ROLE WITH PEARL:                    |
| • Review images before patient arrives   |
| • Note calculus/bone loss indicators     |
| • Flag findings for provider discussion  |
|                                          |
| WHAT NOT TO DO:                          |
| • Don't diagnose to patients             |
| • Don't discuss Pearl findings with      |
|   patients before provider review        |
|                                          |
| QUESTIONS: [Local Champion Name]         |
+------------------------------------------+

---

Front Desk / Office Manager (30 minutes)

Core Training Content:

• What Pearl is and why the practice uses it
• No workflow changes for front desk (typically)
• How to respond to patient questions about AI
• Administrative features (if office manager accesses reporting)

Training Format:

• 15 minutes: Overview video
• 15 minutes: Patient communication scripts and Q&A

Patient Communication Script:

Patient asks: "Is that AI looking at my x-rays?"

"Yes! Our practice uses Pearl, which is an FDA-cleared AI that helps our doctors review your x-rays. It highlights areas that might need attention, and then your dentist reviews everything personally to make the final diagnosis. It's an extra layer of protection for you, and it helps us catch things early."

Day 1 Front Desk Cheat Sheet:

+------------------------------------------+
| PEARL FRONT DESK QUICK REFERENCE         |
+------------------------------------------+
| WHEN PATIENTS ASK ABOUT AI:              |
| "Pearl helps our doctors review x-rays.  |
| It highlights areas of interest, and     |
| your dentist makes all final decisions.  |
| It's an extra layer of care for you."    |
|                                          |
| TECHNICAL ISSUES: [Champion Name/Number] |
+------------------------------------------+

---

Billing/Insurance Staff (30 minutes)

Core Training Content:

• Pearl's impact on documentation (better radiographic documentation supports claims)
• No changes to coding practices (diagnosis codes remain provider-determined)
• How Pearl evidence can support appeals
• Potential changes in treatment presentation rates (billing may see more restorative)

Training Format:

• 20 minutes: Overview and documentation benefits
• 10 minutes: Q&A

Key Points:

• Pearl does NOT generate diagnosis codes automatically
• Pearl annotations can be included in appeal documentation
• Better documentation → fewer denials (expected outcome)

---

Training Completion Tracking

Tracking Mechanism

☐ Create training completion tracker (spreadsheet or LMS)

Location	Staff Name	Role	Training Module	Completion Date	Certified Champion Sign-off
Oakbrook	Dr. Smith	Provider	Provider Training	03/15/2025	J. Johnson
Oakbrook	M. Garcia	Hygienist	Hygienist Training	03/15/2025	J. Johnson
...	...	...	...	...	...

Completion Requirements

☐ 100% of staff trained BEFORE location go-live ☐ ⚠️ No go-live if any provider is untrained ☐ New hire training protocol: Champions train within first week of employment ☐ Annual refresher training requirement

Ongoing Training Cadence

Audience	Frequency	Content
New hires	Within 7 days of start	Role-specific training from champion
All staff	Quarterly	New features, workflow updates
Champions	Monthly (during rollout)	Best practice sharing, issue resolution
Champions	Quarterly (post-rollout)	Refresher and advanced features

---

7. Change Management

Executive Sponsor Communication Plan

Board/Investor Updates 🟣

Frequency: Monthly during rollout, quarterly post-deployment

Update Format:

PEARL AI IMPLEMENTATION: EXECUTIVE SUMMARY
[Month/Year]

STATUS: [Green/Yellow/Red]

LOCATIONS LIVE: [X] of [Total] (X%)

WAVE PROGRESS:
• Wave 1 (Pilot): Complete / In Progress / Planned
• Wave 2: Complete / In Progress / Planned
• Wave 3: Complete / In Progress / Planned

KEY METRICS (vs. Baseline):
• Case acceptance rate: [X%] → [Y%] (Δ [Z%])
• Detection rate: [X findings/100 images] → [Y]
• Provider adoption: [X%] actively using

INVESTMENT STATUS:
• Spend to date: $[X] of $[Y] budget
• ROI trajectory: [On track / Ahead / Behind]

NEXT MILESTONE: [Description] by [Date]

RISKS/ESCALATIONS: [Brief summary or "None"]

---

Regional Manager Briefing Guide

Pre-Rollout Briefing (Week 1)

Objective: Align regional managers on their role and timeline

Briefing Content:

1. Why Pearl: Strategic rationale and expected outcomes
2. What Pearl does: 3-minute demo video
3. Timeline: When their locations go live
4. Their role:
   • Ensure locations complete readiness assessment
   • Identify and approve local champions
   • Remove barriers to successful rollout
   • Escalate issues they can't resolve locally
5. How they'll be measured:
   • On-time go-live for their locations
   • Training completion rates
   • Post-launch adoption metrics

Materials to Provide: ☐ One-page initiative summary (for them to cascade to office managers) ☐ Timeline with their locations highlighted ☐ Champion selection guidance ☐ Escalation path diagram

During-Rollout Check-ins (Weekly)

Agenda:

• Location status updates
• Barriers or resistance encountered
• Support needs
• Upcoming go-lives in their region

---

Staff Resistance Framework (Multi-Location Dynamics)

Common Resistance Patterns at Scale

Pattern	Manifestation	Response Strategy
"Pilot jealousy"	Locations not in Wave 1 feel deprioritized	Frame sequence as "readiness-based, not importance-based"; communicate that all locations will be included
"Pilot cynicism"	"Let them work out the bugs" attitude	Share pilot success stories quickly; involve skeptics in feedback loops
"Not invented here"	Resistance from locations with strong local identity	Identify local champions who can translate corporate initiative to local value
"Flavor of the month"	Fatigue from previous failed initiatives	Emphasize long-term commitment; provide executive visibility to signal seriousness
"Big Brother"	Concern that AI enables surveillance of providers	Clarify that Pearl enhances diagnosis, doesn't score providers; HIPAA protections apply

Resistance Response Playbook

For Regional Managers:

1. Listen first: Understand specific concerns before responding
2. Acknowledge history: "I understand previous rollouts have been frustrating..."
3. Provide evidence: Share pilot data, peer testimonials
4. Offer support: "What do you need to feel confident going live?"
5. Escalate patterns: If same resistance appears at multiple locations, inform central team

---

Internal Marketing

Initiative Naming

☐ 🟣 Decision required: Create branded internal name for Pearl rollout

Options:

• Clinical focus: "Precision Imaging Initiative"
• Patient focus: "Enhanced Care Program"
• Technology focus: "Imaging Intelligence Rollout"
• Simple: "Pearl Implementation"

Recommendation: Name should be memorable, positive, and easy to reference in communications.

Creating Momentum

Pre-Launch (Weeks 1–2): ☐ Announcement email from CEO/COO explaining "why" behind initiative ☐ Video message from CDO endorsing clinical value ☐ FAQ document addressing common concerns

During Rollout: ☐ Weekly "Pearl Progress" email to all staff

• Locations gone live this week
• Quick win stories from the field
• Upcoming locations ☐ Recognition for location champions ☐ Photo/video from successful go-lives

Celebrating Milestones: ☐ Wave 1 completion celebration (virtual town hall, recognition) ☐ 50% deployment milestone ☐ 100% deployment celebration ☐ Share patient success stories (with appropriate permissions)

Sample Internal Communications Calendar

Week	Communication	Audience	Channel
Week 1	CEO announcement	All staff	Email + video
Week 2	CDO clinical endorsement	Providers	Video
Week 3	Wave 1 go-live announcement	All staff	Email
Week 4	First success story	All staff	Email + Slack/Teams
Weekly	Pearl Progress update	All staff	Email
Monthly	Metrics dashboard	Managers +	Internal portal

---

8. Go-Live Day Runbook

Hour-by-Hour Go-Live Schedule

Day Before Go-Live

Time	Activity	Owner
AM	Final system check: verify integration active	Local Champion + Central IT
AM	Confirm all staff have completed training	Local Champion
PM	Review go-live runbook with office manager	Local Champion
PM	Pre-position troubleshooting documentation	Local Champion
EOD	Send reminder to all location staff	Office Manager

Go-Live Day

Time	Activity	Owner
30 min before opening	Arrive early; verify Pearl is operational	Local Champion
15 min before	Brief morning huddle: "Today Pearl is live"	Office Manager
Opening	First patient with Pearl: Champion shadows provider	Local Champion
First 2 hours	Champion floats between operatories; available for questions	Local Champion
Midday	Check-in call with Central Team (15 min)	Champion + Central
Afternoon	Continue shadowing; document any issues	Local Champion
30 min before close	End-of-day debrief with providers and staff	Local Champion
EOD	Submit Day 1 report to Regional Manager	Local Champion

---

Support Coverage

Who Needs to Be On-Site or On-Call

Role	Location	Availability
Local Champion	On-site all day	100% dedicated to Pearl support
Office Manager	On-site	Available for escalations
Lead Provider	On-site	First provider to use Pearl; provide feedback
Central IT	On-call	Available via phone/Slack within 15 min
Regional Manager	On-call	Available for non-technical escalations
🔵 Pearl Support	On-call	Available per SLA (confirm priority support for go-live days)

---

Known Gotchas and Troubleshooting

Common First-Day Issues

Issue	Symptom	Troubleshooting Steps
⚠️ Images not appearing in Pearl	Image captured but no Pearl overlay	1. Verify network connectivity 2. Check bridge service running 3. Confirm image file path correct 4. Restart Pearl connector
⚠️ Slow analysis	Pearl takes >30 sec to analyze	1. Check network speed 2. Verify not processing backlog 3. Contact Pearl support if persists
⚠️ Incorrect patient match	Pearl findings show on wrong patient	1. Verify patient selected in PMS before capture 2. Check patient demographic sync 3. Escalate to Central IT
Overlay not displaying	Analysis complete but no visual overlay	1. Check display settings in Pearl 2. Verify overlay layer enabled 3. Check monitor resolution
Login issues	Provider can't access Pearl	1. Verify credentials 2. Reset password 3. Check SSO integration
Provider overload	Provider confused by new workflow	1. Champion shadows and guides 2. Refer to cheat sheet 3. Allow extra time between patients AM

Escalation Decision Tree

Issue Identified
      ↓
Can Champion resolve in 5 min?
      ↓
  YES → Resolve and document
   NO → Contact Central IT
           ↓
   Central IT resolves in 15 min?
           ↓
      YES → Resume workflow
       NO → 🔵 Contact Pearl Support
               ↓
      Pearl resolves in 30 min?
               ↓
          YES → Resume workflow
           NO → Escalate to Regional Manager
                  → Consider temporary workaround
                  → Document for post-mortem

---

Patient Communication Script

If patient asks about AI during visit:

Provider script: "You may notice some colored highlights on your x-rays. That's Pearl, an FDA-cleared AI system that helps me review your images. It highlights areas that might need attention, but I review everything personally and make all the diagnostic decisions. It's like having a second expert looking at your x-rays with me—an extra layer of care for you."

If patient expresses concern:

"I completely understand. The AI never makes decisions—I do. It just helps ensure I don't miss anything. Your images are protected by the same privacy standards as all your health records. Would you like me to explain more about how it works?"

---

Standardized Go-Live Checklist (Every Location)

Pre-Go-Live (Day Before)

☐ Integration verified and tested ☐ All staff training confirmed complete ☐ Support contacts posted in clinical area ☐ Troubleshooting guide printed and accessible ☐ Champion schedule cleared for go-live support ☐ Morning huddle reminder scheduled

Go-Live Day

☐ Champion arrives 30 min before opening ☐ System operational verification ☐ Morning huddle completed ☐ First patient captured with Pearl ☐ Midday check-in call completed ☐ End-of-day debrief held ☐ Day 1 report submitted

Go-Live +1 Day

☐ Morning check-in with champion (any overnight issues?) ☐ Review Day 1 issues and resolutions ☐ Identify any workflow adjustments needed

---

First-Week Daily Check-In Protocol

Champion → Central Team (Daily, 10 minutes)

Format: Structured Slack message or brief call

Template:

LOCATION: [Name]
DATE: [Day X of go-live]
IMAGES ANALYZED TODAY: [X]
ISSUES ENCOUNTERED: [List or "None"]
STAFF FEEDBACK: [Summary]
SUPPORT NEEDED: [Request or "None"]
CONFIDENCE LEVEL: [Green/Yellow/Red]

Escalation Tiers

Tier	Owner	Response Time	Issue Types
1	Local Champion	Immediate	User questions, minor workflow issues
2	Regional Manager	30 minutes	Staff resistance, resource constraints
3	Central IT	15 minutes	Technical issues, integration problems
4	🔵 Pearl Support	Per SLA	System-level issues, bugs, outages
5	VP Operations	1 hour	Critical failures, go/no-go decisions

---

9. Post-Launch Optimization (Weeks 4–8)

Weekly Metrics Review Cadence

Meeting Structure

Attendees: VP Operations, CDO (optional), IT Director, Regional Managers (rotating based on active locations)

Frequency: Weekly during rollout, bi-weekly post-full deployment

Duration: 30 minutes

Agenda:

1. Deployment status (5 min)
2. Key metrics review (10 min)
3. Issues and escalations (10 min)
4. Decisions needed (5 min)

---

Metrics to Track

Clinical Metrics (Per Location and Aggregate)

Metric	Baseline	Week 4 Target	Week 8 Target	Measurement Source
Case acceptance rate	[X%]	+3%	+5%	PMS production report
Findings per 100 images	[X]	Tracking	Stable baseline	Pearl analytics
Treatment conversion rate	[X%]	+5%	+10%	PMS
Radiograph retake rate	[X%]	-10%	-20%	PMS/imaging system

Operational Metrics

Metric	Baseline	Week 4 Target	Week 8 Target	Measurement Source
Pearl active usage rate	N/A	>90%	100%	Pearl analytics
Average image analysis time	N/A	<10 sec	<10 sec	Pearl analytics
Support ticket volume	N/A	Decreasing	<5/week/location	Support system

Financial Metrics

Metric	Baseline	Week 4 Target	Week 8 Target	Measurement Source
Revenue per patient	[X]	Tracking	+3-5%	PMS
Restorative production	[X]	+5%	+10%	PMS
Claim denial rate	[X%]	Tracking	-10%	Billing system

---

30-Day Checkpoint

What "Good" Looks Like

☐ >90% provider active usage (viewing Pearl output on majority of images) ☐ Case acceptance rate stable or improved ☐ No critical technical issues unresolved ☐ Support ticket volume decreasing week-over-week ☐ No staff turnover attributed to Pearl ☐ Patient feedback neutral to positive

Red Flags ⚠️

☐ Provider usage <70% (not using Pearl on most images) ☐ Case acceptance rate decreased >5% ☐ Open critical technical issues >7 days ☐ Support ticket volume increasing ☐ Multiple staff complaints to HR ☐ Patient complaints related to AI

30-Day Checkpoint Actions

☐ Review metrics dashboard ☐ Conduct provider feedback interviews (15 min each, 3 providers per region) ☐ Identify locations needing intervention ☐ Document workflow refinements adopted ☐ Update training materials based on learnings ☐ 🟣 Prepare 30-day executive summary

---

60-Day Checkpoint: ROI Assessment

ROI Assessment Framework

Step 1: Calculate Incremental Revenue

• Baseline restorative production (6-month average pre-Pearl)
• Post-Pearl restorative production (60-day run rate annualized)
• Delta = Incremental revenue attributable to improved detection

Step 2: Calculate Cost Savings

• Reduced claim denials (fewer write-offs)
• Reduced retakes (labor and materials)
• Time savings (if measurable)

Step 3: Calculate Total Investment

• Pearl licensing fees (annual)
• Implementation costs (internal labor, training time)
• Infrastructure upgrades (if any)

Step 4: Calculate ROI

ROI = (Incremental Revenue + Cost Savings - Total Investment) / Total Investment

60-Day ROI Report Template

PEARL ROI ASSESSMENT: 60-DAY CHECKPOINT
[Date]

DEPLOYMENT STATUS: [X] of [X] locations live

REVENUE IMPACT:
• Baseline production (pre-Pearl): $[X] per location/month
• Current production (post-Pearl): $[X] per location/month
• Incremental revenue (annualized): $[X]

COST IMPACT:
• Claim denial reduction: $[X] saved
• Efficiency gains: $[X] estimated value
• Total cost savings: $[X]

INVESTMENT:
• Software licensing: $[X]/year
• Implementation costs: $[X]
• Total investment: $[X]

ROI CALCULATION:
• Year 1 projected ROI: [X%]
• Payback period: [X months]

QUALITATIVE BENEFITS:
• [List: standardization, risk reduction, etc.]

RECOMMENDATION:
• [Continue / Expand / Adjust / Pause]

---

Staff Feedback Collection

5-Question Pulse Survey (Monthly)

Send to all location staff; takes 2 minutes to complete.

1. How often do you use Pearl in your daily work?

   • Every patient / Most patients / Sometimes / Rarely / Never

2. Pearl makes my job:

   • Much easier / Somewhat easier / No change / Somewhat harder / Much harder

3. I trust Pearl's analysis:

   • Strongly agree / Agree / Neutral / Disagree / Strongly disagree

4. What's the biggest challenge with Pearl?

   • [Open text]

5. What would make Pearl more valuable for you?

   • [Open text]

Feedback Analysis and Action

☐ Analyze survey results by role and location ☐ Identify patterns in open-text responses ☐ Create action items for recurring issues ☐ Share "you said, we did" summary showing responses to feedback

---

Common Workflow Refinements (Weeks 4–8)

Based on typical post-launch learnings:

Refinement	Trigger	Implementation
Adjust overlay settings	Providers report "too busy" visuals	Reduce overlay opacity; toggle certain finding types
Modify when Pearl triggers	Unnecessary analysis on non-diagnostic images	Exclude certain image types from auto-analysis
Update patient scripts	Staff struggling with patient questions	Revise communication templates; re-train
Streamline documentation	Providers want faster note integration	Enable auto-populate to clinical notes
Refine provider training	New providers joining locations	Update onboarding to include Pearl from Day 1

---

Centralized Dashboard Structure (DSO)

Per-Location Metrics View

Metric	Current	Trend	vs. Network Avg	Status
Pearl usage rate	92%	↑	+4%	🟢
Case acceptance	68%	↑	+2%	🟢
Findings/100 images	24	→	-3	🟡
Production/patient	$245	↑	+$12	🟢
Support tickets	2	↓	-1	🟢

Aggregate Network View

Metric	Network Average	Range (Low-High)	Target
Pearl usage rate	89%	78%–98%	95%
Case acceptance	66%	54%–78%	70%
Findings/100 images	27	18–34	N/A (tracking)
Production/patient	$233	$198–$284	$250
Support tickets/location	3.2	0–8	<5

Dashboard Tools

☐ 🟣 Decision required: Dashboard platform

• Pearl's built-in analytics
• Integration with existing BI tool (Tableau, Power BI)
• Custom dashboard build

---

Quarterly Business Review Framework (Post-Full Deployment)

QBR Structure (90 minutes)

Attendees: C-suite, CDO, VP Operations, Regional Managers, Pearl Account Manager

Agenda:

1. Executive Summary (10 min)

   • Key wins this quarter
   • Primary challenges
   • Strategic recommendations

2. Performance Review (30 min)

   • Network-wide metrics vs. targets
   • Location-level performance (highlight top/bottom performers)
   • ROI update

3. Clinical Impact (15 min)

   • Case studies of Pearl-detected pathology
   • Provider feedback themes
   • Quality improvements

4. Operational Review (15 min)

   • Support ticket trends
   • Training completion for new hires
   • Integration stability

5. Product Roadmap (10 min) 🔵

   • Pearl's upcoming features
   • Expansion opportunities (CBCT, specialties)

6. Action Planning (10 min)

   • Decisions needed
   • Priorities for next quarter

---

10. Centralized vs. Localized Decision Framework

Decision Area	Standardize Centrally	Allow Local Discretion	Rationale
Software version	✅		Ensures supportability and consistency
Security settings	✅		Compliance requires uniformity
User role definitions	✅		Consistent access control model
Integration configuration	✅		Reduces support complexity
Training curriculum	✅		Ensures consistent competency
Metrics tracked	✅		Enables cross-location comparison
Escalation paths	✅		Clear accountability
Go-live process	✅		Replicable, predictable rollout
Detection sensitivity	✅ (with exceptions)		Default setting; adjust only with CDO approval
Overlay display preferences		✅	Provider workflow preference
Alert thresholds		✅	Match local workflow and volume
Training delivery schedule		✅	Accommodate local patient schedules
Patient communication scripts	✅ (template)	✅ (personalization)	Consistent messaging with local style
Champion selection		✅	Local manager knows team best
Go-live day timing		✅	Avoid local conflicts (holidays, events)
Feedback collection method		✅	Match existing feedback culture

---

11. Risk Register

Risk	Description	Likelihood	Impact	Mitigation Strategy	Owner
⚠️ Provider resistance	Providers refuse to use Pearl or actively work around it	Medium	High	Strong change management; peer champion model; link usage to performance expectations	CDO
⚠️ Integration failure	Pearl fails to integrate with one or more PMS systems	Medium	High	Extensive Wave 1 testing; vendor escalation path; rollback plan	IT Director
Network instability	Poor internet at certain locations causes latency or failures	Medium	Medium	Pre-assessment identifies issues; infrastructure upgrades for at-risk locations	IT Director
Staff turnover during rollout	Champions or key staff leave mid-implementation	Medium	Medium	Train backup champions; document processes; rapid onboarding for replacements	Regional Managers
Vendor support capacity	Pearl support overwhelmed during mass deployment	Low	High	Stagger go-lives; negotiate enhanced support SLA for rollout period	VP Operations
False positive overload	Too many false positives erode provider trust	Low	High	Monitor precision metrics; adjust sensitivity settings; feedback to vendor	CDO
HIPAA incident	Data breach or privacy violation during implementation	Low	Critical	BAA in place; security testing; incident response plan; cyber insurance	Compliance Officer
Patient backlash	Patients uncomfortable with AI analyzing their images	Low	Medium	Patient communication scripts; opt-out process if legally required	CDO
Scope creep	Adding features or locations beyond original plan	Medium	Medium	Strict change control; phase future requests to post-deployment	VP Operations
Budget overrun	Implementation costs exceed projections	Low	Medium	Detailed upfront budgeting; contingency reserve; vendor pricing lock	CFO
Champion burnout	Local champions overwhelmed during go-live	Medium	Medium	Limit go-live support to 1 week intense; regional backup support	Regional Managers
🔵 Vendor stability	Pearl experiences business disruption	Low	High	Evaluate vendor financial health; data export capabilities; contingency plan	VP Operations

---

12. Executive Reporting Template

Monthly Rollout Status Report

Report Header

PEARL IMPLEMENTATION: MONTHLY STATUS REPORT
Reporting Period: [Month Year]
Report Date: [Date]
Prepared By: [VP Operations]

Deployment Summary

┌─────────────────────────────────────────────────────────────────┐
│ OVERALL STATUS: [🟢 Green / 🟡 Yellow / 🔴 Red]                  │
├─────────────────────────────────────────────────────────────────┤
│ LOCATIONS LIVE: [X] of [Total] ([X%])                           │
│ STAFF TRAINED: [X] of [X] ([X%])                                │
│ BUDGET UTILIZED: $[X] of $[X] ([X%])                            │
│ TIMELINE STATUS: [On track / X days ahead / X days behind]      │
└─────────────────────────────────────────────────────────────────┘

Wave Status

Wave	Locations	Target Go-Live	Actual Status	Status
Wave 1	3	Week 6	Week 6 ✓	🟢
Wave 2	7	Week 10	Week 9 ✓	🟢
Wave 3	25	Week 16	In progress (18 live)	🟡

Per-Location Status (Red/Yellow/Green)

Location	Wave	Go-Live Date	Usage Rate	Issues	Status
Oakbrook	1	03/01	96%	None	🟢
Riverside	1	03/05	92%	None	🟢
Downtown	2	03/20	78%	Provider adoption	🟡
Westside	2	03/22	65%	Integration issue	🔴
...	...	...	...	...	...

Key Metrics (Network Aggregate)

Metric	Baseline	Current	Change	Target	Status
Case acceptance rate	62%	67%	+5%	+5%	🟢
Production/patient	$228	$241	+$13	+$10	🟢
Pearl usage rate	N/A	84%	N/A	90%	🟡
Support tickets/week	N/A	12	Decreasing	<10	🟡

Issues and Risks

Issue	Severity	Status	Owner	Resolution Target
[Description]	High/Med/Low	Open/In Progress/Resolved	[Name]	[Date]

Decisions Needed 🟣

1. [Decision description and options]
2. [Decision description and options]

Next Month Priorities

1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

---

Board-Ready Summary Format

One-Page Executive Brief

═══════════════════════════════════════════════════════════════════
               PEARL AI DIAGNOSTIC IMAGING: BOARD SUMMARY
                              [Quarter/Date]
═══════════════════════════════════════════════════════════════════

WHY WE'RE DOING THIS
• Standardize diagnostic quality across [X] locations
• Increase case acceptance through objective AI-supported findings
• Reduce clinical liability through enhanced documentation
• Competitive differentiation in AI-forward patient care

WHERE WE ARE
• [X] of [X] locations live ([X%])
• [X] months into [X]-month implementation
• [Budget status: on track / X% over / X% under]

WHAT WE'RE SEEING
• Case acceptance: [baseline]% → [current]% ([delta]% improvement)
• Revenue per patient: $[baseline] → $[current] ($[delta] improvement)
• Annualized revenue impact: ~$[X] (projected)
• Provider satisfaction: [summary]

ROI STATUS
• Total investment to date: $[X]
• Projected first-year return: $[X]
• Expected payback period: [X] months
• Tracking: [Ahead of / On pace / Behind] projections

RISKS
• [Top risk and mitigation - one line]

NEXT MILESTONE