TeamHealth Dental — Implementation Playbook (DSO)

Executive Summary

TeamHealth Dental is a dental services organization managing multiple practices across multiple states, requiring centralized scheduling coordination, hygiene productivity optimization, and patient flow standardization. DSO implementation enables unified scheduling protocols, reduced chair idle time, and real-time visibility across the entire network—critical advantages in a multi-location, multi-provider environment where fragmented systems create coordination gaps and lost revenue.

DSOs specifically benefit from unified scheduling because they eliminate inter-practice scheduling conflicts, standardize patient recall workflows, enable network-wide provider allocation, and create data infrastructure for group-level analytics that individual practices cannot achieve alone. Expected timeline to full operational deployment (all locations live and optimized): 16 weeks.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

Infrastructure & Integration

• Audit current PMS systems at each location (identify all platforms: Dentrix, Open Dental, Eaglesoft, etc.)
• Confirm broadband speeds meet minimum 25 Mbps upload/download at all locations
• Validate existing EHR/PMS API capabilities; document which systems support real-time data syncing
• Establish single sign-on (SSO) infrastructure or directory service integration plan
• Audit mobile device inventory—confirm staff can access scheduling tools on iOS/Android if needed
• Test database migration pathways for practices with legacy systems requiring data bridging

Network & Security

• Deploy unified VPN access for remote scheduling oversight
• Implement role-based access controls (RBAC) mapping to DSO org chart
• Establish data governance: who can view/edit patient scheduling across practices
• Schedule security audit before go-live (HIPAA compliance check)

Stakeholder Alignment

Executive Alignment

• Secure CFO buy-in on 90-day ROI expectations and initial platform costs
• Align on KPIs: utilization targets (target: 85%+ chair utilization), productivity per provider, patient no-show reduction
• Define IT resource allocation: identify dedicated implementation lead (0.5 FTE minimum)

Practice Leadership

• Schedule individual calls with office managers at each pilot location (Weeks 1-2)
• Present DSO-level scheduling strategy: explain how centralized scheduling serves their practice goals
• Gather 3 specific pain points from each location (bottlenecks in current scheduling)
• Create executive summary (2 pages) on implementation timeline, training, and expected wins

Clinical & Operations

• Host hygiene director roundtable: review how DSO scheduling improves their schedule consistency and patient outcomes
• Brief all providers on network-wide scheduling philosophy (avoid "this is from corporate" framing)
• Establish clinical advisory committee (1 dentist, 1 hygienist, 1 office manager) to guide configuration decisions

Baseline Metrics Capture

Scheduling Efficiency

• Chair utilization rate by location (target: establish baseline; typical DSO sees 60-75% pre-implementation)
• Average daily patient slots booked vs. available slots
• Hygiene utilization separately (often differs from operative)
• Same-day cancellation rate (% of booked appointments cancelled <24 hours before)

Financial

• Revenue per available chair hour (RPACH) by location
• Average production per provider per day
• Cost of scheduling labor (hours spent coordinating across practices)

Patient Experience

• New patient booking time (days from first call to appointment)
• Patient no-show rate
• Time-to-treatment (days from initial exam to planned procedure)

Operational

• Number of inter-practice patient transfers (identifies network inefficiency)
• Hygiene-to-dentist handoff delays
• Average scheduling staff time per 100 patient appointments

Document all baselines in a shared spreadsheet; you'll reference these in Week 12 (60-day review).

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose 2 pilot locations (not 1) to validate workflows and reduce risk. Select based on:

• Operational readiness: Practices with stable, engaged office managers and no active staffing vacancies
• Data maturity: Locations where PMS data is clean, patient records are current, and hygiene scheduling already exists (avoids confounding variables)
• Geography: Ideally 1 urban + 1 suburban OR practices in same region (simplifies weekly in-person support)
• Size diversity: If possible, choose 1 high-volume location (3+ providers) + 1 smaller location (1-2 providers)—reveals scalability issues early
• Leadership support: Practices where office manager and lead hygienist are enthusiastic (not skeptical)

Configuration & Setup

Weeks 3-4: Platform Customization

• Map DSO scheduling rules into the platform:

  • Hygiene-first booking (hygiene appointments before operative)
  • Provider lunch blocks and clinical calendar rules
  • Minimum buffer between patient types (emergency vs. routine vs. perio)
  • Insurance verification triggers before booking

• Configure patient communication:

  • Automated appointment reminders (SMS + email) at 48h, 24h, and 2h before appointment
  • Digital consent/intake forms pre-populated from existing records
  • Waitlist automation: notify patients on cancellation waitlist automatically

• Set up provider views:

  • Daily schedule view by provider
  • Weekly view showing all hygiene + operative scheduling
  • Patient detail panel (notes, insurance, last visit, outstanding treatment)

• Create reporting dashboard showing:

  • Real-time chair utilization (color-coded red/yellow/green)
  • Weekly appointments booked vs. capacity
  • No-show rate trending
  • New patient booking lag

Weeks 4-5: Data Migration & Testing

• Extract historical scheduling data from pilot location PMS (prior 6 months)
• Cleanse data: flag duplicate patient records, invalid contact info, cancelled standing appointments
• Load patient roster and existing future appointments into new platform
• Conduct dry-run: schedule 50 test patients; verify data accuracy and workflow
• Identify and fix mapping errors before staff access

Training Approach

Week 4: Train-the-Trainer (2 full days, in-person)

• Bring office manager and lead hygienist from each pilot location to central office or virtual training hub

• Hands-on modules:

  • Navigating patient search and booking screens (1.5 hours)
  • Adjusting provider availability and capacity (45 min)
  • Managing waitlists and cancellations (45 min)
  • Interpreting utilization dashboard (45 min)
  • Handling edge cases: emergency slots, insurance verification delays, split appointments

• Create practice-specific checklists (laminated card at front desk):

  • "New Patient Booking" checklist: 8 steps
  • "Schedule Adjustment" checklist: 5 steps
  • "No-Show Protocol" checklist: 4 steps

Week 5: Full Staff Training (90 min session per location)

• Deliver live training at each pilot location (avoid webinar-only model; in-person builds adoption)

• Break into groups:

  • Scheduling staff (detailed feature training): 120 min
  • Front desk/reception (basics + patient communication): 60 min
  • Providers + hygienists (what to expect; live demo of day-to-day): 45 min

• Record training for future reference and rollout phases

• Distribute quick-reference guides (1-page PDF) via email and printed posters

Week 5: Go-Live Support Plan

• Deploy "embedded support": have implementation lead on-site at each location for first 3 days of live scheduling
• Establish daily check-in calls (5-10 min) for 2 weeks post-launch
• Create Slack channel: #scheduling-support for real-time issue escalation

Scaled Rollout (Weeks 7-16)

Wave Planning

Wave 2 (Weeks 7-10): 4-6 locations Wave 3 (Weeks 11-14): Remaining locations Wave 4 (Weeks 15-16): Stabilization + optimization

For each wave, apply lessons from prior pilots:

• Adjust training based on feedback
• Refine change management if early resistance emerged
• Update configuration playbook with new edge cases discovered

Spread rollout to avoid support overload; one dedicated implementation team cannot effectively support more than 6 locations going live simultaneously.

Change Management

**Resistance Mitigation