Archy — Implementation Playbook (DSO)

Archy Implementation Playbook for DSOs

Practice Management AI Platform Deployment Guide

---

1. Executive Summary

What Archy Does

Archy is a cloud-native, all-in-one practice management platform built specifically for modern dental organizations. It combines scheduling, patient communication, clinical charting, treatment planning, billing, and analytics into a unified system with AI-powered automation for appointment optimization, patient engagement, insurance verification, and operational insights.

Why DSOs Benefit from AI-Powered Practice Management at Scale

For multi-location dental organizations, the compound advantages of a unified AI practice management system are transformative:

• Standardization Without Rigidity: Deploy consistent workflows, protocols, and reporting across 15–50+ locations while allowing appropriate local customization—eliminating the operational variance that plagues legacy PMS deployments
• Aggregated Intelligence: AI models improve with data volume; your collective patient interactions, scheduling patterns, and revenue cycle data train smarter predictions for appointment no-shows, treatment acceptance, and insurance optimization across your entire portfolio
• Centralized Visibility: Real-time operational dashboards replace the "spreadsheet consolidation" burden, enabling VPs of Operations to identify underperforming locations before monthly P&Ls reveal the damage
• Reduced IT Burden: Cloud-native architecture eliminates per-location server maintenance, patching, and backup management—your IT team manages one platform, not 30 separate installations
• Unified Patient Experience: Patients moving between your locations experience seamless continuity rather than re-registration and fractured records

Expected Timeline: Decision to Full Deployment

Phase	Timeline	Scope
Pre-Implementation	Weeks 1–2	Infrastructure prep, stakeholder alignment, baseline capture
Wave 1 Pilot	Weeks 3–6	2–3 pilot locations, learning capture
Wave 2 Expansion	Weeks 7–12	5–8 locations based on pilot learnings
Wave 3 Full Deployment	Weeks 13–20	Remaining locations
Optimization	Weeks 21–26	Fine-tuning, ROI validation, long-term governance

Total timeline for 25-location DSO: 5–6 months to full deployment with optimization phase

---

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

Technical Requirements

Hardware Requirements (Per Location)

Component	Minimum Specification	Recommended
Workstations	Windows 10/11 or macOS 12+, 8GB RAM, modern browser	16GB RAM, SSD storage
Displays	1920x1080 resolution	Dual monitors for clinical operatories
Tablets (if used)	iPad 9th gen+ or Android 10+ tablet	iPad Pro for provider use

Network Requirements

☐ Minimum 100 Mbps symmetrical internet per location (recommended: 250+ Mbps) ☐ Dedicated VLAN for practice management traffic (recommended) ☐ DNS configuration for Archy cloud domains ☐ Firewall rules allowing HTTPS traffic to Archy endpoints ☐ WiFi coverage assessment for tablet-based workflows ☐ Backup internet connection (4G/5G failover) for business continuity

Software Prerequisites

☐ Modern browser installed on all workstations (Chrome, Edge, Safari—latest versions) ☐ PDF viewer for document handling ☐ Current imaging software versions documented for integration compatibility ☐ Any location-specific specialty software identified

🔵 Vendor Onboarding Steps

Step	Owner	Timeline	Deliverable
Execute enterprise agreement	Legal/Vendor	Day 1–5	Signed MSA, BAA, SOW
Complete vendor security questionnaire	IT/Vendor	Day 3–7	Approved security documentation
Assign dedicated Customer Success Manager	Vendor	Day 5	Named CSM + contact info
Schedule enterprise architecture review	IT/Vendor	Day 7	Technical design document
Establish support escalation contacts	Operations/Vendor	Day 7	Tiered support contact list
Receive sandbox/test environment access	IT/Vendor	Day 10	Test credentials distributed

Key Vendor Contacts to Establish

☐ Enterprise Account Executive (strategic escalation) ☐ Customer Success Manager (day-to-day relationship) ☐ Technical Implementation Lead (integration and configuration) ☐ Enterprise Support Line (Tier 2/3 escalation path) ☐ Security/Compliance Contact (for audit requests)

Data/Access Prerequisites

Credentials and Access

☐ Admin credentials for existing PMS at each pilot location ☐ Imaging system admin access (Dexis, Carestream, Schick, etc.) ☐ 🔵 Archy enterprise admin account provisioned ☐ Identity provider admin access for SSO configuration (Okta, Azure AD, etc.) ☐ Historical data export permissions verified with current PMS vendor ☐ API documentation obtained from imaging vendors

Data Inventory (Per Location)

☐ Patient demographic records count ☐ Historical appointment data (volume and date range) ☐ Treatment history records ☐ Insurance/payer information ☐ Outstanding claims and A/R data ☐ Document/imaging archive size estimate

Stakeholder Alignment

🟣 Stakeholder Alignment Map

Stakeholder Level	Who	Role in Implementation	Communication Cadence
Board/Investors	Board members, PE partners	Approve initiative, expect ROI reporting	Monthly summary, quarterly business review
C-Suite	CEO, CFO, COO, CDO	Strategic sponsors, resource allocation, go/no-go authority	Bi-weekly steering committee
VP Operations	VP Ops, VP Clinical	Day-to-day executive sponsors, decision authority	Weekly implementation call
Regional Managers	RMs covering pilot regions	Cascade communication, remove local blockers	Weekly standup, daily during go-live
Location Office Managers	OMs at each location	Local implementation leads, staff coordination	Daily during rollout wave
Providers	Dentists, specialists	Clinical validation, workflow approval	Training sessions + 1:1 feedback
Clinical Staff	Hygienists, assistants	End users, workflow feedback	Training + pulse surveys
Administrative Staff	Front desk, billing, insurance	End users, workflow feedback	Training + pulse surveys

Approval Gates

☐ 🟣 Board notification of AI practice management initiative ☐ 🟣 C-suite approval of budget and timeline ☐ 🟣 CDO approval of clinical workflow changes ☐ VP Operations sign-off on rollout sequence ☐ IT sign-off on security and architecture requirements ☐ Legal/Compliance approval of BAA and data governance

Baseline Metrics Capture

⚠️ Critical: Capture These BEFORE Go-Live

Standardized measurement methodology must be established so cross-location comparison is valid post-implementation.

Operational Metrics (Per Location)

Metric	Measurement Method	Capture Period
Daily patient volume	PMS appointment report	90-day average
No-show rate	(No-shows / Total scheduled) × 100	90-day average
Same-day cancellation rate	(Same-day cancels / Total scheduled) × 100	90-day average
Schedule utilization	(Filled slots / Available slots) × 100	90-day average
Average patient wait time	Check-in to chair time	30-day sample

Financial Metrics (Per Location)

Metric	Measurement Method	Capture Period
Case acceptance rate	(Accepted treatment $ / Presented treatment $) × 100	90-day average
Production per provider per day	Total production / Provider days worked	90-day average
Collections ratio	Collections / Production	90-day average
Days in A/R	Accounts receivable / (Annual revenue / 365)	Current snapshot
Claim denial rate	(Denied claims / Total claims) × 100	90-day average
First-pass claim acceptance	(Clean claims / Total claims) × 100	90-day average

Staff Efficiency Metrics (Per Location)

Metric	Measurement Method	Capture Period
Insurance verification time	Average minutes per verification	30-day sample
Scheduling call handle time	Average call duration	30-day sample
Recall effectiveness	(Patients scheduled / Recall attempts) × 100	90-day average
Treatment plan documentation time	Average minutes per plan	30-day sample

Standardization Protocol for Baseline Capture

☐ Create centralized baseline capture spreadsheet with locked formulas ☐ Assign regional managers to validate data from their locations ☐ Schedule all baseline data pulls for same date range across locations ☐ Verify PMS report definitions are consistent (e.g., what counts as "production") ☐ Store baseline data in secured shared location with version control ☐ Sign-off from each office manager confirming data accuracy

Enterprise-Level Requirements

Network Standards Across Locations

☐ Document minimum bandwidth requirements and verify compliance at each location ☐ Standardize firewall rules template for Archy access ☐ Assess VPN requirements for centralized administration ☐ Plan for locations with substandard internet (upgrade timeline or workarounds)

Hosting Architecture Decision

🟣 Decision Required: Centralized vs. Location-Level Configuration

Approach	Pros	Cons	Recommended When
Fully Centralized	Maximum standardization, easiest reporting	Less local flexibility, requires robust change management	Highly standardized DSO, single specialty
Hub and Spoke	Regional flexibility, faster local decisions	More complex to manage, potential drift	Multi-regional DSO, specialty mix
Federated	Maximum local autonomy, specialty accommodation	Hardest to maintain consistency, reporting complexity	Highly heterogeneous portfolio, recent acquisitions

Recommendation: Hub and spoke model with strong central standards for 15–50 location DSOs

Identity and Access Management

☐ 🔵 Confirm Archy SSO compatibility with your identity provider ☐ Map organizational roles to Archy permission levels ☐ Define role-based access control (RBAC) schema ☐ Plan for de-provisioning workflow (terminations, transfers) ☐ Establish privileged access governance for enterprise admins

Centralized Credentialing

☐ Inventory all provider credentials (NPI, licenses, insurance credentialing) ☐ Determine single source of truth for credential data ☐ Plan credential data synchronization with Archy ☐ Establish re-credentialing workflow in new system

---

3. Location Readiness Assessment

Scoring Framework

Rate each factor 1–5 for each location, where:

• 1 = Significant barriers, remediation required
• 2 = Below standard, risks present
• 3 = Meets minimum requirements
• 4 = Above average, likely smooth adoption
• 5 = Exceptional, strong candidate for pilot

Factor 1: IT Infrastructure Maturity

Score	Network Speed	Hardware Age	Current PMS Version
1	<25 Mbps	>7 years	3+ versions behind
2	25–50 Mbps	5–7 years	2 versions behind
3	50–100 Mbps	3–5 years	1 version behind
4	100–250 Mbps	1–3 years	Current version
5	>250 Mbps + backup	<1 year	Current + optimized

Weight: 25%

Factor 2: Staff Tenure and Adaptability

Score	Turnover Rate	Tech Comfort	Training History
1	>60% annual	Resistant, frequent issues	No tech training completed
2	40–60% annual	Reluctant adopters	Minimal training engagement
3	25–40% annual	Average comfort	Standard training completed
4	15–25% annual	Comfortable, seek efficiency	Proactive training participants
5	<15% annual	Tech-forward, advocates	Champions of previous implementations

Weight: 20%

Factor 3: Patient Volume

Score	Daily Patient Volume	Risk/Reward Profile
1	<15 patients/day	Low impact potential
2	15–25 patients/day	Manageable pilot scale
3	25–35 patients/day	Good pilot balance
4	35–50 patients/day	High impact, moderate risk
5	>50 patients/day	Highest impact, higher risk

Weight: 15%

⚠️ Note: For pilot selection, moderate volume (score 3) is often ideal—high enough to generate meaningful data, low enough to manage issues.

Factor 4: Existing Tech Stack Compatibility

Score	PMS Compatibility	Imaging System	Other Integrations
1	Unsupported/legacy PMS	Proprietary/closed system	Multiple conflicting systems
2	Limited integration available	Older version, limited API	Some integration conflicts
3	Standard integration path	Supported system	Manageable integrations
4	Well-supported PMS	Modern, API-friendly	Clean tech stack
5	Archy-optimized or new install	Fully compatible, tested	Minimal integrations needed

Weight: 25%

Factor 5: Local Champion Availability

Score	Champion Presence	Champion Authority	Champion Bandwidth
1	No identifiable champion	N/A	N/A
2	Potential champion, reluctant	Limited influence	Overloaded currently
3	Willing champion identified	Moderate influence	Can allocate some time
4	Enthusiastic champion	Strong team influence	Bandwidth allocated
5	Multiple champions (provider + admin)	Decision-making authority	Dedicated implementation time

Weight: 15%

Composite Readiness Score Calculation

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

Composite Score	Readiness Tier	Rollout Recommendation
4.0–5.0	Tier 1 – Pilot Ready	Candidate for Wave 1
3.0–3.9	Tier 2 – Ready	Wave 2 after pilot learnings applied
2.0–2.9	Tier 3 – Conditional	Wave 3 with remediation plan
1.0–1.9	Tier 4 – Not Ready	Defer until remediation complete

Readiness Assessment Template

Location	IT (1–5)	Staff (1–5)	Volume (1–5)	Tech (1–5)	Champion (1–5)	Composite	Tier
Location A
Location B
...

Recommended Rollout Sequence Logic

Wave 1 Selection Criteria (2–3 locations)

Select locations that have:

• Composite score ≥4.0
• Enthusiastic, available champion (score ≥4)
• Representative of broader portfolio (don't pick only urban or only specialty)
• Manageable patient volume for controlled learning (score 2–3 preferred)
• Geographic proximity if on-site support is planned
• Relationship strength with regional manager

Wave 2 Criteria (5–8 locations)

• Composite score ≥3.0
• Any remediation items from Wave 1 assessment addressed
• Regional clustering for efficient support (if applicable)
• Mix of high-volume (to test at scale) and moderate-volume locations

Wave 3 Criteria (remaining locations)

• All Tier 3 locations with completed remediation plans
• Tier 4 locations only after infrastructure/staffing upgrades verified
• Acquisition integrations or recent de novos

---

4. Rollout Strategy

Wave Structure Recommendation

Wave Architecture for 25-Location DSO

Wave	Timing	# Locations	Duration	Purpose
Wave 1 (Pilot)	Weeks 3–6	2–3	4 weeks	Validate playbook, capture learnings, build case studies
Buffer 1	Week 7	—	1 week	Learning synthesis, playbook refinement
Wave 2 (Expansion)	Weeks 8–13	6–8	6 weeks	Scale validated approach, regional diversity
Buffer 2	Week 14	—	1 week	Further refinement, prepare for acceleration
Wave 3 (Completion)	Weeks 15–20	Remaining (12–14)	6 weeks	Full deployment, leverage trained trainers
Optimization	Weeks 21–26	All	6 weeks	Fine-tuning, ROI validation

Wave 1 Pilot Location Selection

🟣 Executive Decision: Pilot Location Selection

Selection Framework:

Criterion	Weight	Scoring Guidance
Readiness Score	30%	Composite score from assessment
Strategic Importance	20%	Not highest revenue (too risky) or lowest (not representative)
Champion Quality	20%	Ideal: Provider champion + admin champion
Representative Mix	15%	At least one urban, one suburban or mix of specialties
Support Accessibility	15%	Consider travel for on-site support if needed

Recommended Pilot Profile:

• 1 location with highest readiness score (proves the model)
• 1 location with moderate readiness score (tests the support model)
• 1 location that represents a common archetype in your portfolio

Timeline Per Wave

Wave 1 Detailed Timeline (4 weeks)

Week	Activities
Week 3	Configuration, data migration, champion training
Week 4	Staff training, parallel workflows, soft launch
Week 5	Go-live, intensive support, daily check-ins
Week 6	Stabilization, issue resolution, user feedback capture

Wave 2/3 Timeline (6 weeks per wave, multiple locations)

Week	Activities
Week 1–2	Configuration, data migration, champion certification
Week 3	Staff training (champions deliver)
Week 4	Go-live for first subset (stagger 2–3 per week)
Week 5	Go-live for second subset, support for first
Week 6	Stabilization, handoff to standard support

Go/No-Go Criteria Between Waves

Advancing from Wave 1 to Wave 2

🟣 Executive Decision Gate

Criterion	Go Threshold	Measurement
System Stability	<2 critical issues unresolved	Issue tracker
User Adoption	>85% staff completing core workflows in Archy	System usage logs
Data Integrity	Zero data loss or corruption incidents	QA validation
Integration Function	All integrations passing validation tests	Integration test suite
Champion Confidence	Champions rate readiness ≥4/5 to train others	Champion survey
Staff Sentiment	>60% positive on pulse survey	5-question survey

⚠️ No-Go Triggers:

• Any HIPAA compliance concern unresolved
• Data migration errors affecting patient records
• System downtime >4 hours during business hours
• Provider refusal to use system (>1 provider)

Rollback Plan

Wave-Level Rollback Protocol

If a wave fails to meet go/no-go criteria:

1. Immediate (24 hours)

   • Pause remaining go-lives in current wave
   • Revert affected locations to previous PMS access
   • Ensure patient data remains accessible
   • Notify all stakeholders via escalation tree

2. Short-term (48–72 hours)

   • Root cause analysis with vendor
   • Impact assessment across locations
   • Revised timeline proposal
   • 🟣 Executive briefing on path forward

3. Resolution (1–2 weeks)

   • Remediation plan with vendor
   • Pilot re-validation at 1 location
   • Adjusted training or configuration
   • Revised go/no-go criteria if needed

Location-Level Isolation

• Failed locations can be rolled back independently
• Other wave locations can proceed if issues are location-specific
• Shared infrastructure issues require full wave pause

---

5. Configuration & Integration (Weeks 2–3)

Step-by-Step PMS Integration

🔵 Migrating from Dentrix Enterprise

Step	Owner	Duration	Details
1. Data export coordination	IT + Vendor	2–3 days	Schedule export during low-volume period
2. Export configuration	IT	1 day	Configure Dentrix export parameters per Archy spec
3. Data extraction	IT	4–8 hours	Run extraction scripts, validate completeness
4. Secure transfer	IT + Vendor	2–4 hours	Encrypted transfer to Archy import environment
5. Data mapping review	Vendor + IT	1 day	Review field mappings, flag exceptions
6. Trial import	Vendor	2–3 days	Import to test environment
7. Validation	Office Manager + IT	1–2 days	Verify sample records, run reconciliation reports
8. Production import	Vendor + IT	4–8 hours	Final import during scheduled downtime
9. Post-import validation	Office Manager	1 day	Comprehensive validation checklist

🔵 Migrating from Eaglesoft

Step	Owner	Duration	Details
1. Patterson coordination	IT + Patterson	3–5 days	Request data export assistance
2. Database backup	IT	2 hours	Full SQL backup before any changes
3. Export script execution	IT	4–6 hours	Run Archy-provided export routines
4. Image archive export	IT	Variable	Export images from Eaglesoft imaging
5–9	(Same as Dentrix steps 4–9)

🔵 Migrating from Open Dental

Step	Owner	Duration	Details
1. MySQL access configuration	IT	2–4 hours	Configure read access for export
2. API key generation	IT	1 hour	Generate Open Dental API credentials
3. Direct database export	IT + Vendor	3–4 hours	Use Archy migration toolkit
4. Image path mapping	IT	2–3 hours	Map Open Dental image storage to Archy format
5–9	(Same as Dentrix steps 4–9)

⚠️ Common Failure Points in PMS Migration:

• Historical procedure codes that don't map to current CDT codes
• Patient records with incomplete demographic data
• Insurance plan configurations that vary between locations
• Custom fields in old PMS that have no Archy equivalent
• Archived/inactive patient handling

Step-by-Step Imaging System Integration

🔵 Dexis Integration

☐ Verify Dexis version compatibility (Dexis 10+ required) ☐ Install Archy bridge component on imaging workstations ☐ Configure Dexis to write to shared network location ☐ Configure Archy to poll/read from shared location ☐ Test image acquisition → Archy patient record flow ☐ Validate image quality and metadata retention ☐ Confirm bi-directional patient selection (Archy → Dexis)

🔵 Carestream Integration

☐ Verify Carestream version and module compatibility ☐ Configure Carestream DICOM export settings ☐ Set up Archy DICOM listener endpoint ☐ Map patient identifiers between systems ☐ Test intraoral, pano, and CBCT workflows ☐ Validate DICOM metadata preservation

🔵 Generic Imaging (TWAIN/WIA)

☐ Install Archy image capture driver ☐ Configure default image settings (resolution, format) ☐ Test capture workflow from each operatory ☐ Validate image storage and retrieval

Test Environment Setup

Centralized Test Environment Architecture

🟣 Recommended Approach: Single enterprise test environment with location-specific data sandboxes

Environment Structure:

ARCHY-TEST (Enterprise Test)
├── TEST-Location-A (Pilot 1 data subset)
├── TEST-Location-B (Pilot 2 data subset)
├── TEST-Location-C (Pilot 3 data subset)
└── TEST-Training (Synthetic data for training)

Validation Checklist

Data Migration Validation

☐ Patient count reconciliation (source vs. destination) ☐ Provider record validation ☐ Appointment history spot check (20 random patients) ☐ Treatment history spot check (20 random patients) ☐ Insurance plan configuration verification ☐ Document/attachment migration verification ☐ Account balance reconciliation

Integration Validation

☐ Imaging system bidirectional test ☐ Real-time eligibility check test ☐ Claim submission test (use test payer) ☐ ERA/EOB import test ☐ Patient communication test (SMS, email) ☐ Online scheduling test (if applicable)

User Access Validation

☐ SSO authentication flow test ☐ Role-based access verification (each role type) ☐ Permission boundary testing ☐ Audit log generation verification

Security and HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

Requirement	Verification Method	Owner	Status
🔵 BAA executed	Legal confirmation	Legal	☐
Data encryption at rest	Vendor attestation	IT/Vendor	☐
Data encryption in transit (TLS 1.2+)	Technical validation	IT	☐
Access logging enabled	Audit log review	IT	☐
Unique user authentication	SSO configuration	IT	☐
Automatic logoff configured	Settings verification	IT	☐
PHI backup procedures documented	Vendor documentation	IT/Vendor	☐
Disaster recovery plan reviewed	Vendor documentation	IT	☐
Workforce training documentation	Training records	HR/Compliance	☐
Breach notification procedures	Vendor policy review	Compliance/Vendor	☐

Data Governance Requirements

☐ Data retention policies configured ☐ Patient record amendment procedures documented ☐ PHI access request fulfillment workflow established ☐ Cross-location data access rules defined ☐ Third-party data sharing controls configured

Standardized vs. Location-Specific Configuration

🟣 Configuration Governance Template

Configuration Area	Standardize Centrally	Local Discretion Allowed	Notes
User Roles & Permissions	✓		Role definitions consistent across org
Fee Schedules		✓	May vary by market/payer mix
Procedure Code Mapping	✓		CDT codes universal
Appointment Types	✓ (core set)	✓ (custom additions)	Core types mandatory, custom allowed
Scheduling Templates		✓	Provider preferences vary
Patient Communication Templates	✓	✓ (tone adjustments)	Brand messaging consistent
Insurance Payer Setup	✓		Centralize payer configurations
Reporting Dashboards	✓	✓ (custom views)	Standard KPIs plus local views
Clinical Protocols	✓		CDO-approved standards
Treatment Plan Templates	✓		Clinical standardization
Alert Thresholds	✓		Consistent escalation triggers
Working Hours		✓	Location hours vary
Provider Preferences		✓	Chair time, assistant pairing

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Criterion	Minimum Requirement	Ideal Profile
Tenure	>1 year at location	>2 years
Role	Office Manager or Lead Provider	OM + Provider pair
Tech Aptitude	Proficient with current PMS	Early adopter, troubleshooter
Communication	Can explain complex topics	Respected peer, patient instructor
Availability	Can dedicate 15–20 hrs for certification	Can dedicate 25+ hrs
Influence	Peers seek their guidance	Informal leader

Champion Responsibilities

Pre-Go-Live

• Complete Archy Champion Certification (8–12 hours)
• Master all workflows relevant to their location
• Deliver staff training sessions
• Configure location-specific settings with central support
• Validate data migration accuracy

Go-Live Week

• Serve as primary on-site support
• Escalate issues via defined protocol
• Document workarounds and lessons learned
• Lead daily huddles on Archy adoption

Post-Go-Live

• Onboard new hires to Archy
• Deliver quarterly refresher training
• Participate in champion network calls
• Provide feedback to central team

🔵 Champion Certification Program

Module	Duration	Format	Assessment
Archy Platform Fundamentals	2 hours	Self-paced video	Quiz (80% pass)
Scheduling & Patient Flow	2 hours	Live demo + sandbox	Practical exercise
Clinical Workflow	2 hours	Live demo + sandbox	Practical exercise
Billing & Insurance	2 hours	Live demo + sandbox	Practical exercise
Reporting & Analytics	1 hour	Self-paced + live Q&A	Quiz (80% pass)
Training Delivery Skills	1.5 hours	Live facilitation workshop	Peer practice session
Support & Escalation	0.5 hours	Self-paced	Acknowledgment

Certification Timeline: Champions must complete certification at least 5 business days before their location's staff training begins.

Standardized Training Materials (Created Centrally)

☐ Role-specific training slide decks ☐ Workflow demonstration videos (screen recordings) ☐ Hands-on exercise guides with sandbox logins ☐ Quick reference cards (laminated, monitor-ready) ☐ FAQ documents by role ☐ Common error resolution guide

Role-Specific Training Outlines

Providers (Dentists, Specialists)

Training Duration: 3 hours Format: 2 hours live demonstration + 1 hour hands-on with trainer support Delivery: Champion-led, with vendor support available

Topic	Duration	Key Points
Dashboard Overview	15 min	Daily schedule view, patient alerts, task list
Patient Chart Navigation	30 min	Odontogram, treatment history, imaging access
Treatment Planning	45 min	Creating plans, phasing,