scanO — Implementation Playbook (DSO)

scanO Implementation Playbook

Patient Communication AI for Dental Service Organizations

---

1. Executive Summary

What scanO Does

scanO is an AI-powered patient communication platform that uses smartphone-based dental scanning and intelligent analysis to engage patients before, during, and after their visits. The platform enables patients to capture images of their oral health at home, which AI analyzes to identify potential concerns, driving proactive appointment scheduling and improving treatment acceptance through visual patient education.

Why DSOs Benefit from AI Patient Communication at Scale

DSOs operating 15–50 locations face a fundamental challenge: maintaining consistent patient communication quality while managing decentralized operations. AI patient communication tools like scanO deliver compounding advantages at scale:

• Standardized Patient Experience: Every patient across every location receives the same quality of AI-driven engagement, regardless of front desk staffing variations or individual office communication habits
• Centralized Data Intelligence: Aggregate patient engagement data across all locations to identify trends, benchmark performance, and allocate marketing resources based on actual patient behavior rather than anecdotal reporting
• Operational Leverage: A single configuration can serve 50 locations, but the patient engagement impact multiplies—each percentage point improvement in reactivation or case acceptance compounds across your entire patient base
• Reduced Per-Location Communication Burden: AI handles routine patient touchpoints, freeing front desk staff to focus on in-office patient experience rather than phone tag

Expected Timeline: Decision to Full Deployment

Phase	Timeline	Milestone
Pre-Implementation	Weeks 1–2	Infrastructure audit complete, stakeholders aligned
Wave 1 Pilot (3 locations)	Weeks 3–5	Pilot locations live, initial learning captured
Wave 2 Expansion (8–10 locations)	Weeks 6–9	Second wave deployed, processes refined
Wave 3 Full Deployment	Weeks 10–14	All remaining locations live
Optimization	Weeks 15–20	ROI validated, workflows optimized

Total timeline: 14–20 weeks from signed contract to full deployment across 15–50 locations, depending on IT infrastructure readiness and location count.

---

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

Technical Requirements

Hardware Requirements (Per Location)

☐ Tablets or smartphones for in-office patient scanning (minimum iOS 14+ or Android 10+) ☐ Adequate WiFi coverage in patient-facing areas (minimum 25 Mbps download, 10 Mbps upload) ☐ Display screens in operatories for patient education (recommended, not required) ☐ Staff workstations with current browser support (Chrome 90+, Safari 14+, Edge 90+)

Software Requirements

☐ Practice Management System compatibility verified (Dentrix, Eaglesoft, Open Dental, or supported system) ☐ Current imaging software version documented ☐ Email/SMS platform identified (or confirm use of scanO's native messaging) ☐ Single Sign-On (SSO) provider identified if using centralized authentication

Network Requirements

☐ Minimum 25 Mbps bandwidth per location during peak hours ☐ Firewall rules allow outbound HTTPS to scanO domains ☐ Port 443 open for API communications ☐ ⚠️ Guest WiFi network isolated from clinical systems (common failure point)

Enterprise-Level Requirements

Network Standards Across Locations

☐ 🟣 Decide: Centralized hosting vs. location-level data residency ☐ Document network architecture variations across locations ☐ Identify locations with known connectivity issues ☐ Establish VPN requirements if central hosting selected

Authentication & Access Control

☐ 🟣 Decide: SSO integration vs. location-level credentials ☐ If SSO: Document identity provider (Okta, Azure AD, Google Workspace) ☐ Define role-based access levels (location staff, regional managers, central admins) ☐ Establish credential provisioning workflow for new hires

Centralized Credentialing

☐ Provider NPI database export for bulk configuration ☐ Location-level admin designations documented ☐ Compliance officer access requirements defined

Vendor Onboarding Steps

Step	Owner	🔵 Vendor Required	Timeline
Schedule kickoff call	Your team	Yes	Day 1
Assign dedicated implementation manager	scanO	Yes	Day 1–3
Receive sandbox environment credentials	scanO	Yes	Day 3–5
Complete security questionnaire	Your IT + scanO	Yes	Day 5–10
Execute Business Associate Agreement	Legal + scanO	Yes	Day 1–5
Establish technical support escalation contacts	Both	Yes	Day 5

Key Contacts to Establish

☐ 🔵 scanO Implementation Manager (primary day-to-day contact) ☐ 🔵 scanO Technical Support escalation contact ☐ 🔵 scanO Customer Success Manager (post-go-live relationship owner) ☐ Internal project lead (your side) ☐ IT lead for integration work ☐ Clinical champion for workflow decisions

Data/Access Prerequisites

☐ API keys generated for PMS integration ☐ Test patient records identified for sandbox testing ☐ Historical patient contact data export (email, SMS, appointment history) ☐ ⚠️ Patient communication consent flags verified in PMS (common compliance gap) ☐ Imaging archive access credentials (if integrating historical images) ☐ Patient reactivation list from past 18 months

Internal Stakeholder Alignment

Stakeholder Alignment Map

Stakeholder	Role in Implementation	Communication Cadence
Board/Investors	Approval of AI investment; ROI expectations	Monthly summary during rollout
CEO/COO	Executive sponsor; resource allocation	Weekly during pilot, bi-weekly after
Chief Dental Officer	Clinical workflow approval; provider adoption	Weekly check-ins
VP of Operations	Rollout logistics; location coordination	Daily during active waves
VP of IT	Integration approval; security sign-off	As needed, critical path
Regional Managers	Location readiness; staff coordination	Weekly during their region's rollout
Office Managers	Local implementation lead; staff training	Daily during go-live week
Providers	Workflow adoption; patient communication	Training sessions + ongoing feedback

Approval Requirements

☐ 🟣 Board/investor notification of AI initiative (if required by governance) ☐ 🟣 Executive sponsor formally assigned (recommend COO or CDO) ☐ 🟣 Budget allocation confirmed for implementation and Year 1 subscription ☐ 🟣 IT security review completed and approved ☐ 🟣 Clinical workflow changes approved by Chief Dental Officer

Baseline Metrics to Capture

⚠️ Critical: Capture these metrics BEFORE go-live. Without baselines, ROI measurement is impossible.

Patient Communication Metrics

Metric	How to Measure	Standardization Note
Patient reactivation rate	% of inactive patients (12+ months) who schedule	Define "inactive" consistently: 12 months since last visit
Appointment confirmation rate	% of appointments confirmed vs. scheduled	Measure 48 hours pre-appointment
No-show rate	% of confirmed appointments that no-show	Exclude cancellations with 24+ hour notice
Same-day cancellation rate	% cancellations within 24 hours	Document current process for filling gaps

Treatment Metrics

Metric	How to Measure	Standardization Note
Case acceptance rate	% of treatment presented that is scheduled	Define denominator: presented $ or presented procedures
Time from diagnosis to treatment start	Average days	Start counting from diagnosis entry in PMS
Treatment plan presentation rate	% of exams resulting in treatment plan	Define what constitutes a "treatment plan"

Operational Metrics

Metric	How to Measure	Standardization Note
Front desk call volume	Inbound calls per day/week	Pull from phone system if available
Average time to schedule	Hours from patient inquiry to booked appointment	Sample 30 patient journeys per location
Patient acquisition source breakdown	% from each channel	Align source codes across all locations

Cross-Location Standardization Protocol

☐ Create master metric definitions document ☐ Distribute to all office managers with examples ☐ Run 2-week baseline measurement period ☐ Validate data quality before proceeding ☐ ⚠️ Identify locations with incomplete data—may need manual sampling

---

3. Location Readiness Assessment

Scoring Framework

Score each location on the following factors using a 1–5 scale. This assessment identifies your optimal pilot locations and rollout sequence.

Factor 1: IT Infrastructure Maturity

Score	Criteria
5	Fiber internet (100+ Mbps), hardware <3 years old, current PMS version, no known connectivity issues
4	Cable internet (50+ Mbps), hardware <4 years old, PMS within 1 version of current
3	Reliable internet (25+ Mbps), hardware <5 years old, PMS within 2 versions
2	Occasional connectivity issues, older hardware requiring upgrades, outdated PMS
1	Frequent outages, hardware >5 years, PMS not on supported version list

Factor 2: Staff Tenure and Adaptability

Score	Criteria
5	Office manager tenure >3 years, <10% annual turnover, history of successful tech adoption
4	Office manager tenure 2–3 years, <20% turnover, generally positive toward technology
3	Office manager tenure 1–2 years, moderate turnover, neutral toward new tools
2	Recent office manager change, >30% turnover, some resistance to past changes
1	Leadership instability, >40% turnover, known resistance to technology initiatives

Factor 3: Patient Volume

Score	Criteria
5	High volume (150+ patients/week), significant reactivation opportunity
4	Above average volume (120–150 patients/week)
3	Average volume (80–120 patients/week)
2	Below average volume (50–80 patients/week)
1	Low volume (<50 patients/week) or new location ramping up

Note: High volume scores higher because impact is greater, but consider that very high volume during pilot = higher risk. For Wave 1, prefer 3–4 range.

Factor 4: Existing Tech Stack Compatibility

Score	Criteria
5	Dentrix Enterprise, Eaglesoft with cloud, or Open Dental—fully supported, current version
4	Supported PMS on recent version, minimal custom configurations
3	Supported PMS, some version lag, standard integrations already in place
2	Supported PMS but outdated version requiring upgrade, or non-standard imaging system
1	Unsupported PMS, complex custom integrations, or major infrastructure changes required

Factor 5: Local Champion Availability

Score	Criteria
5	Tech-forward provider AND engaged office manager, both volunteered for pilot
4	Strong office manager with tech aptitude, providers generally supportive
3	Willing office manager, neutral provider sentiment
2	No clear champion identified, but no active resistance
1	Resistance from office manager or key provider, or recent conflicts about technology

Composite Readiness Scoring

Calculate the composite score for each location:

Readiness Score = (IT × 1.2) + (Staff × 1.3) + (Volume × 0.8) + (Tech Stack × 1.0) + (Champion × 1.2)

Weighting rationale: Staff adaptability and local champion are strongest predictors of success; volume has lower weight because it's double-edged.

Composite Score	Readiness Tier	Rollout Recommendation
22–27.5	Tier 1	Wave 1 pilot candidate
16–21.9	Tier 2	Wave 2 expansion
10–15.9	Tier 3	Wave 3 with preparation
<10	Tier 4	Address prerequisites before rollout

Sample Assessment Template

Location	IT (×1.2)	Staff (×1.3)	Volume (×0.8)	Tech (×1.0)	Champion (×1.2)	Total	Tier
Location A	4 (4.8)	5 (6.5)	3 (2.4)	4 (4.0)	5 (6.0)	23.7	1
Location B	3 (3.6)	4 (5.2)	4 (3.2)	3 (3.0)	4 (4.8)	19.8	2
Location C	2 (2.4)	3 (3.9)	5 (4.0)	4 (4.0)	2 (2.4)	16.7	2
Location D	2 (2.4)	2 (2.6)	2 (1.6)	2 (2.0)	1 (1.2)	9.8	4

Recommended Rollout Sequence

Based on composite scoring:

1. Wave 1 (Pilot): Select 2–3 Tier 1 locations that represent your portfolio diversity (geography, specialty mix, patient demographics)
2. Wave 2 (Expansion): All remaining Tier 1 and Tier 2 locations (typically 8–12 locations)
3. Wave 3 (Full Deployment): Tier 3 locations with any prerequisite issues resolved
4. Deferred: Tier 4 locations—address foundational issues (infrastructure upgrades, leadership stability) before including in rollout

---

4. Rollout Strategy

Wave Structure

Recommended Wave Plan for 25-Location DSO (Example)

Wave	Locations	Timeline	Purpose
Wave 1	3	Weeks 3–5	Validate configuration, refine training, identify issues
Wave 2	8	Weeks 6–9	Scale processes, stress-test support model
Wave 3	14	Weeks 10–14	Full deployment with optimized playbook

Wave 1 Pilot Selection Criteria

Select 2–3 pilot locations that meet ALL of the following:

☐ Tier 1 readiness score (22+) ☐ Represents at least 2 geographic regions (to test regional variation) ☐ Includes at least 1 general practice and 1 specialty (if applicable) ☐ Office manager has been personally briefed and is enthusiastic ☐ At least 1 provider at each location is designated clinical champion ☐ Not a location with known operational issues (understaffing, recent incidents) ☐ Close enough to regional manager for in-person support if needed

Do NOT select: Your highest-performing location (too much risk), your newest location (too many variables), or locations where key personnel are planned to be out.

Wave Timeline with Learning Buffers

Week 3: Wave 1 locations go live
Week 4: Intensive monitoring and daily check-ins
Week 5: Learning capture—document issues, solutions, and workflow adjustments
Week 6: Go/No-Go decision for Wave 2
Week 6–7: Wave 2 locations go live (staggered over 2 weeks if >8 locations)
Week 8–9: Wave 2 monitoring period
Week 10: Go/No-Go decision for Wave 3
Week 10–14: Wave 3 locations go live (staggered as needed)

Go/No-Go Criteria

Criteria to Advance from Wave 1 to Wave 2

🟣 Executive decision required

Category	Go Criteria	No-Go Triggers
Technical Stability	System uptime >99% during pilot; no data loss incidents	Any data loss; >2 hours cumulative downtime; unresolved integration errors
User Adoption	>80% of trained staff using tool as designed	<60% adoption; active workarounds emerging; key providers refusing to use
Patient Experience	No patient complaints directly attributable to tool; positive feedback from >3 patients	Any patient complaint escalated to corporate; confusion causing appointment issues
Workflow Integration	Staff can complete workflows without constant support	Requires on-site support to function; blocking other workflows
Support Response	Vendor response within SLA; issues resolved within 24 hours	Vendor unresponsive; critical issues unresolved >48 hours

If No-Go Decision

☐ Document specific failure points ☐ 🔵 Engage scanO escalation contact for remediation plan ☐ Set remediation timeline (typically 1–2 weeks) ☐ Re-assess go/no-go after remediation ☐ 🟣 Communicate delay to executive sponsor with revised timeline

Rollback Plan

If a wave fails and must be paused:

Immediate Actions (Within 24 Hours)

1. Disable scanO patient-facing communications to prevent confusion
2. Revert to previous patient communication workflows at affected locations
3. Notify all affected office managers of temporary rollback
4. Document patient records that were created during the tool's operation
5. 🔵 Escalate to scanO implementation manager for root cause analysis

Isolation Protocol

• Rollback affects ONLY the current wave's locations
• Previously deployed waves continue operating unless systemic issue identified
• Pending waves are paused until issue resolved

Communication Template

"We've identified an issue during our [Wave X] deployment that requires additional work before proceeding. [Location names] will temporarily return to our previous communication workflows while we resolve this. This does not affect other locations. We expect to resume within [X] days and will provide an update by [date]."

Re-Deployment Criteria

☐ Root cause documented and resolved ☐ 🔵 scanO confirms fix deployed ☐ Test validation in sandbox environment ☐ 🟣 Executive sponsor approves re-deployment ☐ Affected locations re-briefed on any workflow changes

---

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integration

Dentrix Enterprise Integration

Step	Action	Owner	🔵	Time
1	Verify Dentrix Enterprise version is 2019 or later	IT Lead		15 min
2	🔵 Obtain API credentials from scanO	scanO	Yes	1–2 days
3	Configure Dentrix API access in Enterprise Manager	IT Lead		30 min
4	🔵 Enter API credentials in scanO admin portal	IT Lead + scanO	Yes	15 min
5	⚠️ Map patient data fields (ensure DOB, contact info, provider assignments align)	IT Lead		1–2 hours
6	Configure appointment type mappings	Operations		1 hour
7	Test bidirectional sync with 5 test patients	IT Lead		2 hours
8	Verify insurance information pulls correctly	IT Lead		30 min
9	🔵 scanO validates integration in sandbox	scanO	Yes	1 day

Eaglesoft Integration

Step	Action	Owner	🔵	Time
1	Verify Eaglesoft version 21.0 or later	IT Lead		15 min
2	Enable Eaglesoft API in Patterson settings	IT Lead		30 min
3	⚠️ Patterson support may need to enable API features	IT Lead		1–3 days
4	🔵 Obtain scanO integration module from vendor	scanO	Yes	1–2 days
5	Install scanO connector on Eaglesoft server	IT Lead		1 hour
6	Map patient and appointment data fields	IT Lead		1–2 hours
7	Test sync with test patient records	IT Lead		2 hours
8	🔵 scanO validates integration	scanO	Yes	1 day

Open Dental Integration

Step	Action	Owner	🔵	Time
1	Verify Open Dental version 22.1 or later	IT Lead		15 min
2	Enable API in Open Dental (Setup → Misc Setup → API)	IT Lead		15 min
3	Create API user account with appropriate permissions	IT Lead		30 min
4	🔵 Provide API endpoint and credentials to scanO	IT Lead + scanO	Yes	15 min
5	🔵 scanO configures connection	scanO	Yes	1 day
6	Map custom fields if using Open Dental customizations	IT Lead		1–2 hours
7	Test patient record sync	IT Lead		2 hours
8	Test appointment creation flow	IT Lead		1 hour

Imaging System Integration

Standard Imaging Integration Steps

Step	Action	Owner	🔵	Time
1	Document current imaging software and version	IT Lead		30 min
2	🔵 Verify imaging system is on scanO supported list	scanO	Yes	1 day
3	Export sample de-identified images for format verification	IT Lead		1 hour
4	🔵 scanO validates image format compatibility	scanO	Yes	1–2 days
5	Configure image storage path or cloud sync	IT Lead		2 hours
6	⚠️ Test image upload/retrieval with 10 test cases	IT Lead		2 hours
7	Verify AI analysis runs on uploaded images	IT Lead		1 hour
8	Configure image display in patient communication templates	Operations		1 hour

Test Environment Setup

Enterprise Test Environment Approach

🟣 Decision Required: Centralized vs. Per-Location Testing

Approach	Pros	Cons	Recommendation
Centralized Sandbox	Single environment to manage; consistent testing; easier for IT	Doesn't catch location-specific integration issues	Recommended for initial configuration
Per-Location Test	Catches location-specific issues; closer to real environment	Time-intensive; harder to coordinate	Recommended for Wave 1 pilots only

Recommended hybrid approach:

1. Build and validate core configuration in centralized sandbox (Week 2)
2. Clone configuration to Wave 1 pilot locations in test mode (Week 2–3)
3. Validate per-location specifics before each wave go-live (ongoing)

Validation Checklist

☐ Patient data syncs bidirectionally ☐ Appointment creation in scanO appears in PMS ☐ Appointment changes in PMS reflect in scanO ☐ Patient images upload and display correctly ☐ AI analysis generates results within expected timeframe ☐ Automated messages send to test phone numbers/emails ☐ Opt-out handling works correctly ☐ Provider assignments route correctly ☐ ⚠️ Edge cases: patients with multiple records, merged records, incomplete data

Data Migration / Historical Data Ingestion

Patient Communication History Import

Step	Action	Owner	🔵	Time
1	Export patient contact information from PMS (past 24 months of active + 18 months inactive)	IT Lead		2–4 hours
2	Clean data: remove deceased, do-not-contact, invalid emails/phones	Operations		2–4 hours per location
3	⚠️ Verify opt-out flags are preserved in export	Compliance		1 hour
4	Format data per scanO import template	IT Lead		2 hours
5	🔵 Submit import file to scanO	IT Lead + scanO	Yes	1 day
6	🔵 scanO processes import and provides validation report	scanO	Yes	1–3 days
7	Review validation report; resolve exceptions	IT Lead		2–4 hours

Security and HIPAA Compliance

Enterprise-Level HIPAA Checklist

☐ 🔵 Business Associate Agreement (BAA) executed with scanO ☐ 🔵 scanO SOC 2 Type II report reviewed and accepted ☐ 🟣 Data governance policy updated to include AI-processed patient data ☐ 🟣 Patient consent language reviewed by legal (if using patient-initiated scans) ☐ Access control matrix documented (who can see what) ☐ Audit logging enabled for all PHI access ☐ Data encryption verified (in transit and at rest) ☐ ⚠️ Third-party subprocessor list reviewed (scanO's vendors) ☐ Incident response plan updated to include scanO ☐ Annual security review scheduled

Per-Location Security Verification

☐ Location-level admin accounts use unique credentials ☐ Shared login accounts prohibited ☐ Workstation auto-lock configured (<10 minutes) ☐ Patient-facing tablets configured for kiosk mode only ☐ Staff trained on PHI handling in AI context

Standardized vs. Location-Specific Configuration

Standardized Configuration Template (Apply to ALL Locations)

Setting	Standard Value	Rationale
Appointment reminder timing	48 hours, 24 hours, 2 hours	Consistent patient experience
Message branding	Corporate templates	Brand consistency
Opt-out handling	Immediate removal from all automated messages	Compliance
AI analysis thresholds	Vendor defaults initially	Prevents inconsistent clinical flagging
Escalation paths	Regional manager → Central IT	Consistent support model
Reporting dashboards	Standard KPI template	Cross-location comparison
User role permissions	Standard role definitions	Security and audit consistency

Location-Specific Configuration (Customize Per Location)

Setting	Customization Allowed	Governance
Provider names/assignments	Yes—must match PMS	Office manager configures
Office hours	Yes—must be accurate	Office manager configures
Specialty-specific messaging	Yes—from approved template library	Regional manager approves
Language preferences	Yes—based on patient demographics	Office manager configures
Local phone number in messages	Yes—for patient callbacks	IT Lead configures
Appointment type availability	Yes—based on services offered	Office manager configures

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Each location requires ONE designated champion who will:

• Receive intensive training directly from scanO
• Train their own staff
• Serve as first-line support for questions
• Provide feedback to central team

Ideal Champion Profile: ☐ Office manager OR lead front desk staff with 1+ year tenure ☐ Demonstrated comfort with technology (uses current systems proficiently) ☐ Respected by clinical and administrative staff ☐ Communication skills to explain workflows clearly ☐ Available for training and ongoing support responsibilities ☐ ⚠️ NOT the busiest clinical provider (their time is needed chairside)

Champion Responsibilities

Responsibility	Time Commitment	Timing
Attend train-the-trainer session	2–3 hours	1 week before go-live
Train all location staff	4–6 hours total	Week of go-live
Daily check-ins with central team	15 min/day	First week
Answer staff questions	As needed	Ongoing
Report issues via escalation path	As needed	Ongoing
Participate in monthly champion calls	30 min	Monthly

Champion Training Delivery

🔵 scanO delivers train-the-trainer sessions (virtual or in-person)

Session structure (2–3 hours):

• Tool overview and login orientation (30 min)
• Complete walkthrough of all workflows (60 min)
• Hands-on practice with test patients (45 min)
• Training delivery techniques and materials review (30 min)
• Q&A and troubleshooting scenarios (30 min)

Standardized Training Materials

Centrally Created Materials

Material	Format	Owner
"What is scanO" 2-minute overview video	Video	🔵 scanO provides
Role-specific workflow guides	PDF	Central Ops creates with scanO input
Day 1 Cheat Sheets (by role)	Single-page PDF	Central Ops creates
Common questions FAQ	Document	Central Ops creates, champions contribute
Patient-facing FAQ	Document	Marketing creates
Training completion certification quiz	Online form	Central Ops creates

Champion-Customizable Materials

Material	What Champion Adds
Provider list and assignments	Names match local team
Office hours and contact info	Location-specific
Escalation contact list	Local + regional contacts
Location-specific tips	"Our patients often ask..."

Role-Specific Training Outlines

Dentists/Providers

Training Time: 45–60 minutes Format: Live demo with hands-on practice (champion-delivered)

Content:

1. Why we're implementing scanO (5 min)

   • Patient engagement goals
   • How this helps case acceptance

2. What you'll see differently (15 min)

   • Patient scan results appearing in workflow
   • AI analysis flags and how to interpret
   • Patient communication history visible

3. Clinical workflow changes (20 min)

   • Reviewing AI-flagged concerns before patient visit
   • Using visual aids in treatment presentation
   • ⚠️ When to override AI suggestions (and how to document)
   • Integrating home scans into examination

4. Hands-on practice (15 min)

   • Review 3 sample patient profiles
   • Practice explaining AI results to "patient" (role-play)

Common Resistance Points:

• "This will slow me down" → Show time-neutral workflow; AI prep happens before they walk in
• "I don't trust AI diagnosis" → It's a screening tool, not diagnostic; you always make the call
• "Patients won't use this" → Data shows [X]% adoption; we'll iterate based on feedback

Day 1 Cheat Sheet: Providers

┌─────────────────────────────────────────────────────┐
│ scanO Provider Quick Reference                      │
├─────────────────────────────────────────────────────┤
│ BEFORE PATIENT ARRIVES:                             │
│ • Check scanO tab for patient's home scan results   │
│ • Note any AI-flagged areas to discuss              │
│                                                     │
│ DURING EXAM:                                        │
│ • Reference scan images when explaining findings    │
│ • "I noticed in your scan from home that..."        │
│                                                     │
│ AFTER EXAM:                                         │
│ • Treatment plan syncs automatically                │
│ • Follow-up messages are automated                  │
│                                                     │
│ IF AI FLAGS SOMETHING YOU DISAGREE WITH:            │
│ • Click "Override" and select reason                │
│ • This trains the system and protects your judgment │
│                                                     │
│ QUESTIONS? → Ask [Champion Name]                    │
└─────────────────────────────────────────────────────┘

Hygienists

Training Time: 30–45 minutes Format: Live demo with practice (champion-delivered)

Content:

1. Your role in scanO workflow (10 min)

   • Understanding patient scan history
   • What AI flags mean for prophy appointments

2. In-operatory workflow (15 min)

   • Reviewing scan results with patient
   • Supporting treatment acceptance conversations
   • Capturing additional scans if requested by provider

3. Patient education (10 min)

   • Explaining home scanning to patients
   • Answering common patient questions
   • Encouraging app adoption

4. Hands-on practice (10 min)

   • Review sample patient case
   • Practice patient explanation

Common Resistance Points:

• "This isn't my job" → You're the trusted relationship; your explanation builds adoption
• "More screen time" → 30-second review; usually enhances conversation you're already having

Day 1 Cheat Sheet: Hygienists

┌─────────────────────────────────────────────────────┐
│ scanO Hygienist Quick Reference                     │
├─────────────────────────────────────────────────────┤
│ BEFORE PATIENT SITS DOWN:                           │
│ • Glance at scanO tab—any home scan submitted?      │
│ • Note areas patient may have questions about       │
│                                                     │
│ DURING CLEANING:                                    │
│ • "I see you submitted a scan—any concerns?"        │
│ • Use images to show what you're working on         │
│                                                     │
│ PATIENT DOESN'T HAVE APP YET:                       │
│ • "We have a free app that lets you scan at home"   │
│ • Hand them the instruction card                    │
│                                                     │
│ QUESTIONS? → Ask [Champion Name]                    │
└─────────────────────────────────────────────────────┘

Front Desk / Office Manager

Training Time: 60–90 minutes Format: Live demo with hands-on practice (champion-delivered)

Content:

1. Overview and your critical role (10 min)

   • Front desk is command center for patient communication
   • How scanO changes (and simplifies) patient outreach

2. Core administrative functions (30 min)

   • Dashboard overview and daily workflow
   • Patient communication status tracking
   • Appointment request handling
   • Manual message sending when needed
   • ⚠️ Opt-out management (compliance critical)

3. Reporting and monitoring (20 min)

   • Running standard reports
   • Identifying patients needing follow-up
   • Escalating technical issues

4. Patient questions (15 min)

   • Explaining the app to walk-in patients
   • Handling patient concerns about AI/privacy
   • Troubleshooting patient app issues

5. Hands-on practice (15 min)

   • Navigate dashboard
   • Process a sample appointment request
   • Run a sample report

Common Resistance Points:

• "Another system to check" → It replaces manual reactivation calls; show time savings
• "Patients will complain about messages" → Opt-out is easy; most patients appreciate reminders

Day 1 Cheat Sheet: Front Desk

┌─────────────────────────────────────────────────────┐
│ scanO Front Desk Quick Reference                    │
├─────────────────────────────────────────────────────┤
│ MORNING CHECK:                                      │
│ • Open scanO dashboard                              │
│ • Review overnight appointment requests             │
│ • Check for any failed message deliveries           │
│                                                     │
│ WHEN PATIENT CALLS ABOUT A MESSAGE:                 │
│ • "Yes, that's from our patient care system"        │
│ • "Let me check your profile..." [open in scanO]    │
│                                                     │
│ WHEN PATIENT WANTS TO OPT OUT:                      │
│ • "No problem" → Settings → Communication Prefs     │
│ • Mark opt-out → Save → Confirm with patient        │
│                                                     │
│ WHEN PATIENT HAS APP TROUBLE:                       │
│ • Check their profile for scan history              │
│ • Common fix: "Try logging out and back in"         │
│ • If stuck: "Our support can help: [number]"        │
│                                                     │
│ END OF DAY:                                         │
│ • Check for pending appointment requests            │
│ • Note any issues for champion                      │
│                                                     │
│ QUESTIONS? → Ask [Champion Name]                    │
└─────────────────────────────────────────────────────┘

Billing/Insurance Staff

Training Time: 30 minutes Format: Overview session (champion-delivered)

Content:

1. How scanO affects billing workflow (10 min)

   • Limited direct impact on billing
   • Patient communication tracking in record

2. Documentation considerations (10 min)

   • AI-flagged findings are decision support, not diagnostic codes
   • Treatment plan documentation unchanged
   • Patient communication logs available for audit

3. Edge cases (10 min)

   • Handling patient questions about AI and insurance
   • "Is this scan covered?" response: "Home scans are patient education tools, not billable services"

Day 1 Cheat Sheet: Billing

┌─────────────────────────────────────────────────────┐
│ scanO Billing Quick Reference                       │
├─────────────────────────────────────────────────────┤
│ MINIMAL DIRECT IMPACT ON YOUR WORKFLOW              │
│                                                     │
│ KEY THINGS TO KNOW:                                 │
│ • Home scans are NOT billable services              │
│ • AI analysis is decision support, not diagnosis    │
│ • Documentation in PMS unchanged                    │
│                                                     │
│ IF PATIENT ASKS ABOUT COVERAGE:                     │
│ • "The app is a free patient education tool"        │
│ • "It doesn't replace your covered exam"            │
│                                                     │
│ QUESTIONS? → Ask [Champion Name]                    │
└─────────────────────────────────────────────────────┘

Training Completion Tracking

Pre-Go-Live Training Verification

☐ All staff complete role-appropriate training ☐ All staff pass brief certification quiz (5 questions, 80% to pass) ☐ Champion signs off that location is "training complete" ☐ Training completion uploaded to central tracking sheet

Central Tracking Dashboard

Location	Champion Trained	Providers	Hygienists	Front Desk	Billing	Status
Location A	✓	3/3	4/4	2/2	1/1	Ready
Location B	✓	2/3	3/3	2/2	1/1	Pending

Rule: Location cannot go live until 100% training completion documented.

Ongoing Training Cadence

Audience	Frequency	Content
New hires	Within first week	Role-specific training (champion delivers)
All staff	Quarterly	Feature updates, workflow reminders (video)
Champions	Monthly	Champion community call (30 min)
Champions	As needed	Advanced features, troubleshooting deep-dive

---

7. Change Management

Executive Sponsor Communication Plan

Board/Investor Updates

🟣 Executive sponsor owns these communications

Milestone	Communication Format	Content
Implementation kickoff	Email update	Initiative overview, expected timeline, investment rationale
Wave 1 complete	Briefing memo	Pilot results, patient adoption, any issues encountered
Wave 2 complete	Briefing memo	Scale validation, preliminary metrics
Full deployment	Board presentation slide	Adoption metrics, early ROI indicators
90-day post-launch	ROI report	Full metrics vs. baseline, patient feedback, recommendations

Sample Investor Update Template

Subject: AI Patient Communication Initiative - [Month] Update

STATUS: [Green/Yellow/Red]

PROGRESS:
• [X] of [Y] locations now live
• [Z] patients engaged through platform
• Current phase: [Wave X]

KEY METRICS:
• Patient reactivation rate: [X]% (baseline: [Y]%)
• Appointment confirmation rate: [X]%
• Staff adoption: [X]%

NEXT MILESTONE: [Description] by [Date]

BUDGET STATUS: On track / [X]% variance

[One paragraph of context/narrative]

Regional Manager Briefing Guide

Regional managers are your force multipliers. Equip them to cascade communication and support rollout.

Pre-Rollout Briefing (2 weeks before their region's wave)

Agenda (45 minutes):

1. Strategic rationale for scanO implementation (5 min)
2. What's changing for their locations (10 min)
3. Their role during rollout (10 min)
4. Location readiness status in their region (10 min)
5. Escalation paths and support (5 min)
6. Q&A (5 min)

Materials to provide: ☐ One-pager: "What scanO Does and Why" ☐ Location readiness scores for their region ☐ Go-live schedule for their locations ☐ Champion names and contact info ☐ Escalation contact list ☐ FAQ for common staff questions

Regional Manager Responsibilities During Rollout

Responsibility	Timing
Brief office managers in advance	1 week pre-go-live
Be available on-call during go-live week	Go-live week
Conduct daily check-in with each location champion	First week
Escalate issues that champions can't resolve	As needed
Provide feedback to central team	Weekly
Celebrate wins and share best practices	Ongoing

Staff Resistance Framework for Multi-Location Dynamics

Understanding Multi-Location Resistance

Resistance patterns differ from single-practice implementations:

Pattern	How It Manifests	Mitigation
Comparison Culture	"Location X says it doesn't work"	Control the narrative; share only verified feedback; address rumors quickly
Wait-and-See	Locations delay adoption hoping they'll be forgotten	Clear accountability; publish go-live dates publicly; consequences for delays
Local Autonomy Defense	"We do things differently here"	Acknowledge local context; show flexibility within guardrails; involve in customization
Us vs. Corporate	"This is something HQ is forcing on us"	Local champions deliver training; emphasize benefits to their daily work
Pioneer Burnout	Wave 1 locations feel like guinea pigs	Thank them publicly; give them voice in shaping future waves; small perks

Resistance Response Playbook

When you hear: "This is adding work to my day." Respond with: "In the first week, yes—learning anything new takes time. By week two, [specific task] that used to take you 20 minutes will take 5. Can we check in next Tuesday to see if that's matching your experience?"

When you hear: "The patients don't want this." Respond with: "Some won't—and that's fine, it's optional. But [X]% of our pilot patients opted in, and they're booking appointments they otherwise wouldn't. Let's see how your patients respond."

When you hear: "I've seen tools like this fail before." Respond with: "Fair concern. What made those fail? [Listen.] Here's what we're doing differently this time: [specific safeguards]. If you see early signs of those problems, flag them to me immediately."

When you hear: "Why my location first?" Respond with: "Because your team is strong enough to help us get this right. Your feedback will make it work better for everyone else. That's a compliment, not a punishment."

Internal Marketing

Initiative Naming

🟣 Executive decision: Name the initiative

Name should be:

• Simple and memorable
• Connote positive patient experience
• Not mention "AI" prominently (reduces fear)
• Distinct from past failed initiatives

Examples:

• "Patient Connect"
• "Smile Link"
• "Care Bridge"
• "[DSO Name] Connect"

Creating Momentum

Tactic	Timing	Owner
CEO video message introducing initiative	Pre-launch	Executive sponsor
Countdown emails to all locations	Weekly, 3 weeks pre-Wave 1	Marketing
Champion spotlight interviews	Ongoing	Marketing
"First patient success" story shared	Within Wave 1	Champions + Marketing
Go-live day celebrations (small)	Each wave	Regional managers
Monthly "wins" newsletter	Monthly	Central Ops

Celebrating Milestones

Milestone	Recognition
Wave 1 complete	All-hands shoutout; champion recognition
First location hits 100 patient scans	Small prize; public recognition
Region completes rollout	Regional manager acknowledgment
Full deployment	CEO communication; potential bonus/gift
ROI targets achieved	Board recognition; success story publication

---

8. Go-Live Day Runbook

Standardized Go-Live Checklist

This checklist must be completed for EVERY location, regardless of wave.

T-7 Days (One Week Before)

☐ Champion confirms all staff trained (100% completion) ☐ Test environment validated; all workflows functioning ☐ Patient communication templates reviewed and approved ☐ Go-live date confirmed with office manager ☐ Regional manager notified and available on go-live day ☐ 🔵 scanO support team notified of go-live schedule

T-2 Days

☐ Configuration migrated from test to production ☐ Staff login credentials distributed and tested ☐ Day 1 Cheat Sheets printed and distributed ☐ Patient-facing materials (posters, cards) placed in office ☐ Champion confirms readiness; no concerns flagged

T-1 Day

☐ Final system check: all integrations connecting ☐ Champion briefed on go-live day support contacts ☐ ⚠️ Confirm no major appointments/events on go-live day ☐ After-hours: flip switch to "production mode"

Hour-by-Hour Go-Live Day Schedule

Time	Activity	Who
7:00 AM	Champion arrives 30 minutes early; logs in; confirms system operational	Champion
7:30 AM	Quick huddle with all staff: "Today we go live with [initiative name]"	Champion
8:00 AM	First patients arrive; begin using scanO in live workflow	All staff
8:30 AM	Champion confirms first successful patient interaction	Champion → Regional Manager
10:00 AM	Mid-morning check-in: any issues?	Champion → Regional Manager
12:00 PM	Lunch: Champion available for questions; brief team on morning observations	Champion
2:00 PM	Afternoon check-in: volume pickup, any new issues?	Champion → Regional Manager
4:30 PM	End-of-day champion huddle: document issues, wins, questions	Champion
5:00 PM	Champion submits Day 1 report to central team	Champion → Central Ops

On-Site and On-Call Support

Role	Location	Responsibility
Champion	On-site at location	First-line support; answer all questions
Regional Manager	Available by phone/video; may visit in person	Escalation for operational issues
Central IT	On-call remotely	Technical troubleshooting
🔵 scanO Support	On-call; extended hours for go-live days	Vendor-side technical issues

Response Time Expectations:

• Champion: Immediate (on-site)
• Regional Manager: Within 15 minutes
• Central IT: Within 30 minutes
• 🔵 scanO: Within 1 hour (or per SLA)

Known Gotchas and Troubleshooting

Common First-Day Issues

Issue	Symptom	Fix
⚠️ Login failures	"Invalid credentials"	Clear browser cache; try incognito; verify username spelling; password reset if needed
⚠️ Sync delay	Patient info not appearing	Wait 5 minutes (initial sync can be slow); check PMS connectivity; 🔵 contact scanO if >15 min
⚠️ Slow performance	Pages loading slowly	Check WiFi strength; reduce browser tabs; try different device
Wrong provider assignment	Messages from wrong doctor	Check provider mapping in configuration; correct and resync
Missing patients	Patient not in scanO	Search by DOB not name; check PMS for data quality issue; manual entry if urgent
Patient can't log in to app	Patient reports error	Verify correct email; resend app invitation; check spam folder

First-Week Troubleshooting Protocol

1. Champion attempts resolution (0–5 minutes)
2. If unresolved, check FAQ/knowledge base (5–10 minutes)
3. If still unresolved, escalate to regional manager (10–15 minutes)
4. Regional manager escalates to Central IT if needed
5. Central IT engages 🔵 scanO if vendor support needed
6. Document all issues for pattern identification

Patient Communication Script

Use this when patients ask about the new system:

In-Office Script

"We're excited to offer you a new way to stay connected with us! Our [initiative name] app lets you check in on your dental health between visits. If you'd like, you can even scan your teeth at home and share images with your care team. It's free, optional, and helps us take better care of you. Would you like to try it?"

Patient Questions FAQ

Q: "Why do you need pictures of my teeth?"

"It helps us spot potential concerns early, between your regular visits. It's like a check-in—completely optional—and everything is private and secure."

Q: "Will this cost me anything?"

"Nope! The app is free. It's just another way we're investing in your care."

Q: "Is my data safe?"

"Absolutely. We take privacy very seriously. The app is HIPAA-compliant and your images are only seen by our care team."

Q: "What if I don't want to use it?"

"That's totally fine. It's optional and won't affect your care at all."

First-Week Daily Check-In Protocol

Location Champion → Regional Manager

Daily (5:00 PM for first 5 days):

Report via Slack/Teams/email:

Location: [Name]
Date: [Date]
Status: 🟢 Green / 🟡 Yellow / 🔴 Red

Today's Numbers:
• Patients seen: [X]
• Patients engaged with scanO: [X]
• Issues encountered: [X]

Open Issues:
• [Issue 1 - status]
• [Issue 2 - status]

Wins:
• [Any positive moments to share]

Support Needed:
• [Any requests]

Regional Manager → Central Team

Daily (6:00 PM for first 5 days of each wave):

Aggregate report via shared dashboard:

Region: [Name]
Date: [Date]

Location Statuses:
• [Location A]: 🟢
• [Location B]: 🟡 - [brief note]

Issues Requiring Central Support:
• [Describe]

Patterns Observed:
• [Any cross-location trends]

Escalation Tiers

Tier	Who	Contact Method	When to Use
Tier 1	Location Champion	In-person, Slack	All first-line questions and issues
Tier 2	Regional Manager	Phone, Slack	Champion can't resolve; operational issues
Tier 3	Central IT	Slack channel #scanO-support, phone	Technical issues; integration problems
Tier 4	🔵 scanO Vendor Support	Support portal, phone	Vendor-side bugs; feature questions; outages

Escalation Response Time Standards:

• Tier 1 → Tier 2: If unresolved in 30 minutes
• Tier 2 → Tier 3: If unresolved in 1 hour
• Tier 3 → Tier 4: If determined to be vendor issue

---

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

Weekly Metrics Review Cadence

Week 1–2: Daily Review

• Champion submits daily status report (see Go-Live section)
• Central team reviews daily for emerging issues

Week 3–4: Transition to Weekly

• Champion submits weekly summary report
• Regional manager holds 15-minute weekly call with each location

Week 5+: Standard Weekly Cadence

• Location champion reviews dashboard every Monday
• Regional manager reviews regional rollup every Wednesday
• Central team reviews enterprise dashboard every Thursday
• Monthly all-hands review of key metrics

Metrics to Track Weekly

Metric	Target	Red Flag
Patient app adoption rate (% of active patients)	>15% by week 4	<5%
Home scans submitted	Growth week-over-week	Declining for 2+ weeks
Message delivery rate	>95%	<90%
Appointment confirmation rate	Baseline +10%	Below baseline
Staff usage (logins/interactions)	Daily usage by all front desk	<3 days/week by any staff
Patient opt-out rate	<2%	>5%
Support tickets	Declining trend	Increasing after week 2

30-Day Checkpoint

What "Good" Looks Like at Day 30

✓ 100% of staff using tool in daily workflow without assistance ✓ >10% of active patients engaged with app ✓ Appointment confirmation rate improved or stable ✓ No outstanding critical support tickets ✓ Champion confident in ongoing management ✓ Initial patient feedback trending positive

Red Flags at Day 30

⚠️ Staff still requiring daily support for basic tasks ⚠️ <5% patient adoption ⚠️ Appointment no-show rate increased ⚠️ Multiple patients complaining about over-communication ⚠️ Champion burned out or requesting removal from role ⚠️ Workarounds being used instead of intended workflows

30-Day Review Meeting Agenda

Attendees: Location champion, regional manager, central ops lead Duration: 30 minutes per location

1. Review metrics vs. targets (10 min)
2. Staff feedback summary (5 min)
3. Patient feedback summary (5 min)
4. Open issues and blockers (5 min)
5. Adjustments needed (5 min)

60-Day Checkpoint: ROI Assessment

ROI Calculation Framework

Tie back to baseline metrics captured in Pre-Implementation:

Metric	Baseline	60-Day Actual	Change	Revenue Impact
Patient reactivation rate	[X]%	[Y]%	+[Z]%	+$[A] per reactivated patient × [B] patients
Case acceptance rate	[X]%	[Y]%	+[Z]%	+$[A] average treatment value × [B] additional cases
No-show rate	[X]%	[Y]%	-[Z]%	[A] saved chair hours × $[B] per hour opportunity cost
Front desk call reduction	[X] calls/day	[Y] calls/day	-[Z]%	[A] hours saved × $[B] hourly labor cost

Cost-Benefit Summary Template

60-DAY ROI SUMMARY

Investment:
• scanO annual subscription: $[X]
• Implementation labor (internal): $[X]
• Training time cost: $[X]
• Total investment: $[X]

Returns (annualized from 60-day data):
• Reactivation revenue: $[X]
• Case acceptance revenue: $[X]
• Operational savings: $[X]
• Total returns: $[X]

Net ROI: [X]% annually
Payback period: [X] months

Staff Feedback Collection

5-Question Pulse Survey

Deploy via email or Slack at Day 30 and Day 60:

1. How easy is scanO to use in your daily workflow?
   [1-Very Difficult] [2] [3-Neutral] [4] [5-Very Easy]

2. Has scanO saved you time on patient communication tasks?
   [1-No, takes more time] [2] [3-About the same] [4] [5-Yes, saves significant time]

3. How have patients responded to scanO?
   [1-Very negative] [2] [3-Neutral] [4] [5-Very positive]

4. Do you feel adequately trained and supported?
   [1-Not at all] [2] [3-Somewhat] [4] [5-Very well supported]

5. What's one thing you'd change about scanO or how we're using it?
   [Open text]

Survey Analysis

• Aggregate by role, location, region
• Flag any location with average score <3
• Review open-text responses for patterns
• Share feedback with 🔵 scanO for product input

Common Workflow Refinements

Typical Post-Launch Adjustments

Observation	Refinement
Message timing off for patient demographics	Adjust reminder timing (earlier for elderly, later for working adults)
Too many messages	Reduce frequency; combine messages where possible
Patients confused by AI terminology	Simplify language in patient-facing content
Staff not checking dashboard regularly	Add dashboard to morning huddle routine
Certain message templates underperforming	A/B test alternatives; 🔵 request scanO optimization suggestions
Provider not using AI insights	Rebuild into workflow; add prompt to patient chart

Centralized Dashboard Structure

Enterprise-Level Metrics (All Locations Aggregated)

Metric Category	Metrics
Adoption	Total patients engaged, app downloads, scan submissions
Engagement	Messages sent, messages opened, click-through rate
Outcomes	Appointments booked via scanO, reactivations attributed, case acceptance linked to scanO engagement
Operations	Support tickets, system uptime, integration errors

Per-Location Metrics (Drill-Down)

Metric	Purpose
Patient adoption rate	Compare location performance
Staff usage frequency	Identify training gaps
Message delivery rate	Identify data quality issues
Patient opt-out rate	Spot over-communication problems
Days since last support ticket	Stability indicator

Dashboard Access Levels

Role	Access
Location Champion	Own location only
Office Manager	Own location only
Regional Manager	All locations in region + regional rollup
VP of Ops	All locations + enterprise rollup
C-Suite	Executive summary dashboard

Quarterly Business Review Framework

After full deployment stabilizes (Week 16+), conduct quarterly reviews:

QBR Agenda (90 minutes)

1. Executive Summary (10 min)

   • Overall adoption and engagement trends
   • Key wins and challenges

2. Metrics Deep Dive (20 min)

   • Quarter-over-quarter performance
   • Top and bottom performing locations
   • Benchmark against goals

3. ROI Update (15 min)

   • Cumulative ROI calculation
   • Cost trends

4. Patient and Staff Feedback (15 min)

   • Survey results
   • Anecdotal feedback themes

5. Optimization Opportunities (15 min)

   • Feature adoption gaps
   • Workflow improvements identified

6. 🔵 Vendor Roadmap Update (10 min)

   • Upcoming features
   • Integration enhancements

7. Action Items and Next Quarter Goals (5 min)

---

10. Centralized vs. Localized Decision Framework

Decision Area	Standardize Centrally	Allow Local Discretion	Notes
Platform Configuration
Core system settings	✓		Security, compliance, consistency
Message branding and templates	✓		Brand standards
AI analysis thresholds	✓		Clinical consistency
Reporting structure	✓		Cross-location comparison
User role definitions	✓		Security and audit
Local Customization
Provider names/assignments		✓	Must match local staffing
Office hours		✓	Location-specific
Appointment types offered		✓	Service mix varies
Language preferences		✓	Patient demographics vary
Workflow
Core patient communication workflow	✓		Consistency; easier support
Specialty-specific messaging		✓	From approved template library
In-office patient education process		✓	Provider preference
Training
Training curriculum	✓		Quality assurance
Training delivery timing		✓	Schedule varies
Ongoing training cadence	✓		Compliance
Support
Escalation path	✓		Clear accountability
First-line troubleshooting		✓	Champion empowerment
Data and Reporting
Metric definitions	✓		Cross-location comparison
Report access	✓		Security
Local report usage		✓	Manager autonomy

---

11. Risk Register

Risk Description	Likelihood	Impact	Mitigation Strategy	Owner
⚠️ PMS integration failures at scale	Medium	High	Validate integration at each location before go-live; maintain rollback capability; 🔵 engage scanO technical support early	IT Lead
⚠️ Staff resistance leads to low adoption	Medium	High	Train-the-trainer model with champions; change management communications; regional manager accountability	VP of Ops
Patient complaints about messaging frequency	Medium	Medium	Start conservative; monitor opt-out rates weekly; adjust quickly; clear opt-out process	Central Ops
Champion turnover disrupts location support	Medium	Medium	Document processes thoroughly; identify backup champions; rapid onboarding for replacements	Regional Managers
⚠️ Data quality issues (incorrect patient contact info)	High	Medium	Pre-migration data cleansing; ongoing data hygiene protocols; bounce monitoring	IT Lead
Vendor support responsiveness inadequate	Low	High	Document SLAs in contract; escalation paths established; regular relationship check-ins	VP of Ops + Legal
HIPAA compliance gap discovered	Low	Very High	BAA in place; security review before go-live; ongoing audit; incident response plan	Compliance Officer
Internet outage at location	Medium	Medium	Tool functions with intermittent connectivity; offline mode for critical functions; backup communication procedures	Office Managers
AI analysis accuracy concerns from providers	Medium	Medium	Clear communication that AI is decision support; easy override process; feedback loop to 🔵