DEO — Implementation Playbook (DSO)

Executive Summary

DEO is a cloud-native practice management platform designed to unify clinical workflows, financial operations, and patient engagement across multi-location dental organizations. It consolidates patient records, billing, scheduling, and compliance in a single system while maintaining location-level autonomy. DSOs benefit uniquely because they eliminate the operational fragmentation that occurs when locations run on legacy or disconnected systems—a critical pain point when scaling from 3 to 50+ offices.

Expected timeline to full deployment: 16 weeks for a 5-10 location DSO, with earlier ROI visibility at week 8.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

Infrastructure audit:

• Confirm internet bandwidth minimum: 10 Mbps downstream, 5 Mbps upstream per location
• Validate network security: firewall review for cloud API access, VPN requirements assessment
• Identify local hardware: workstation count, printer/scanner integration points, EOB reader specs
• Assess current system exports: verify data can be extracted from legacy PMS in standard formats (CSV, HL7, or vendor-specific APIs)

Cybersecurity & Compliance:

• Audit current HIPAA controls; document gaps
• Confirm Business Associate Agreements (BAAs) are in place with DEO
• Map current backup protocols—establish new backup architecture during migration window
• Verify SSO/directory services (Active Directory, Okta) compatibility for unified authentication

Data Assessment:

• Catalog active patient records across all locations (establish deduplication rules)
• Audit outstanding claims, A/R aging (baseline for reconciliation)
• Document custom fee schedules, lab preferences, referring provider relationships
• Identify patient data quality issues—missing contact info, duplicate records, formatting inconsistencies

Stakeholder Alignment

Governance structure:

• Designate DSO Executive Sponsor (typically COO or Chief Clinical Officer)
• Form steering committee: 1 practice manager per location + IT lead + compliance officer
• Name location-level champions: front desk lead, clinical lead, back office lead per site
• Establish weekly steering committee cadence; bi-weekly location champion syncs

Expectations-setting workshop:

• Present realistic timeline; emphasize weeks 5-8 as highest disruption period
• Quantify expected training time: 8-12 hours per front desk staff, 4-6 hours per clinician
• Establish communication plan: weekly all-hands updates + daily office-level huddles during go-live
• Define decision rights: who approves workflow changes, system configuration, workaround decisions

Buy-in mechanisms:

• Tie location KPIs to system adoption (e.g., prompt entry rates, scheduling compliance)
• Highlight clinician benefits early: faster charting, reduced EOB delays, patient communication tools
• Share peer DSO case studies showing 15-20% collection improvement and 8-10 hour/week administrative savings

Baseline Metrics to Capture

Document these metrics in week 2 (before any system changes):

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Select 2-3 pilot locations using this matrix:

• Size: 4-6 FTE (mid-sized, not flagship) — large enough to stress-test workflows, small enough to iterate quickly
• Readiness: Leader openly advocates for change; front desk staff <2 years tenure (fewer legacy habits); <30% patient base over age 75 (easier digital adoption)
• Stability: No major staffing changes planned; not in middle of expansion or renovation
• Data quality: >85% complete patient records; <5% duplicate patient entries
• Geographic: Ideally 1-2 hours from DSO headquarters for hands-on support

Avoid flagship locations (highest patient volume), locations with custom integrations, or offices with staff turnover in past 3 months.

Configuration and Setup

Week 3 — Data preparation:

• Export patient data from legacy system; run deduplication algorithm (DEO's matching engine + manual review)
• Create location-specific fee schedules in DEO
• Map insurance carriers, upload current contract templates
• Set up clinician profiles with license info, specialties, hygiene/doctor schedule templates
• Configure patient communication preferences (email, SMS, preferred contact times)

Week 4 — System configuration:

• Establish recall rules aligned with clinical protocols (prophylaxis frequency, ortho intervals)
• Configure treatment plan templates for top 20 procedures (resin composite, root canal, crown, etc.)
• Set up operatory-specific schedules: block hygiene time, doctor time, treatment room rotation
• Create reporting dashboards: daily production, claim status, no-show trends
• Establish user permissions: restrict back-office staff from clinical notes, clinicians from A/R detail

Week 5 — Cutover preparation:

• Run parallel system testing: 1 week where staff enter data in both legacy and DEO
• Conduct mock go-live: after-hours training session running full patient workflow (check-in → treatment → checkout)
• Verify printer setup, e-signature workflows, patient portal account provisioning
• Load historical claims data for follow-up on denial root causes

Week 6 — Go-live:

• Monday–Wednesday: Live operations; 2 DEO on-site staff + 1 location champion on standby
• Daily standup: 15-min huddle at 12pm and 5pm to address bottlenecks, re-train on specific workflows
• Escalation pathway: Unresolved issues → DEO support within 2 hours

Scaled Rollout (Weeks 7-16)

Wave Planning

Wave 2 (Weeks 7-10): 2-3 mid-sized locations, geographically distributed Wave 3 (Weeks 11-14): 2-4 larger locations; specialty practices (ortho, pedo) implemented separately Wave 4 (Weeks 15-16): Final locations; holdouts and custom-integration sites

Each wave begins with dedicated 2-week training window before go-live.

Change Management

• Peer champions: Pilot location staff mentors Wave 2 teams (builds credibility, reduces consultant dependency)
• Role-specific training: Front desk modules differ from clinical modules; customize for roles
• Documentation: Create location-specific runbooks with screenshots of local operatories, schedule patterns
• Feedback loops: Weekly surveys on biggest friction points; prioritize fixes for next wave
• Quick wins: After go-live day 1, celebrate first electronic claim submission, first patient portal sign-up to sustain momentum

Support Infrastructure

• Dedicated Slack channel per wave for real-time troubleshooting
• 4-hour SLA on operational blockers during go-live weeks; 24-hour SLA thereafter
• Monthly lunch-and-learns: share tips, discuss system updates, celebrate adoption milestones across all locations
• Post-go-live check-ins at days 3, 7, 14, 30 to validate staff confidence and system stability

ROI Tracking

Key Metrics to Measure