Henry Schein ONE Implementation Playbook (DSO)

Executive Summary

Henry Schein ONE is a cloud-based practice management system that centralizes patient records, scheduling, billing, and reporting across multiple locations—critical infrastructure for DSOs managing operational complexity at scale. For a 10+ location DSO, ONE eliminates data silos, enforces clinical and financial consistency, and provides real-time visibility into performance metrics that drive profitability. Without unified PM software, you're managing disparate systems, bleeding money on manual reconciliation, and losing competitive advantage in staffing and patient acquisition.

Pre-Implementation Checklist

• Audit current PM systems across all locations. Document which practices use Henry Schein (existing ONE installations, legacy Dentrix, Softdent), which use competitors (Eaglesoft, Open Dental, etc.), and which rely on hybrid setups. DSOs often inherit mismatched tech stacks; you need a clear inventory before migration planning.

• Assign a dedicated DSO implementation lead (operations director or IT manager) with authority to enforce timelines and escalate blockers across locations. This person owns the 6-month project end-to-end and reports weekly to C-suite.

• Validate data integrity in legacy systems. Run patient demographic audits, accounts receivable reconciliation, and insurance eligibility checks at each location. Garbage in = garbage out; poor source data will corrupt your ONE instance and tank adoption.

• Secure Henry Schein ONE training commitment from all stakeholders. Confirm that front desk, clinical, billing, and management staff at each location can attend live or recorded training sessions. Budget 8–12 hours per role, minimum.

• Establish integration requirements with your DSO's ancillary systems (EHR, imaging, accounting software, payroll). Determine which systems must connect to ONE via API or direct integration—e.g., if you use QuickBooks at corporate, confirm bridge integration pathways.

• Confirm internet infrastructure and device readiness across all 10+ locations. ONE is cloud-based; verify that each practice has reliable broadband (minimum 10 Mbps), sufficient devices (workstations, tablets for front desk), and updated browsers.

• Lock in your ONE subscription pricing and support tier (typically $300–$600/month per location for mid-to-large practices). Confirm whether you're purchasing through Henry Schein direct, a DSO group purchasing organization (GPO), or a reseller—volume discounts matter at 10+ seats.

Implementation Timeline

Phase 1: Discovery & Planning (Weeks 1–3)

• Week 1: Kick-off meeting with all location managers and Henry Schein One consultant. Present DSO-wide roadmap, assign roles, and explain phased rollout strategy (not all locations migrate simultaneously).
• Week 2–3: Conduct detailed system mapping at flagship or pilot location (choose a high-performing practice with engaged staff). Document current workflows, identify ONE configuration gaps, and build a location-specific template for replication.

Phase 2: Pilot & Customization (Weeks 4–8)

• Week 4–5: Deploy ONE at pilot location. Configure core settings: fee schedules, treatment codes, insurance networks, user roles, and reporting dashboards tailored to DSO KPIs.
• Week 6–7: Run parallel testing: keep legacy PM running; run ONE for 2 weeks alongside to validate data integrity and staff workflow. Identify gaps (missing procedure codes, payer-specific rules, appointment scheduling logic) and log them for Henry Schein or internal IT to resolve.
• Week 8: Go-live at pilot location after staff signs off on workflows. Dedicate on-site support for 3–5 days post-launch.

Phase 3: Staged Rollout (Weeks 9–20)

• Weeks 9–12: Migrate locations 2–4 using playbook built at pilot site. Batch similar practices (e.g., general practices first, then specialty). Run 1–2 week parallel testing at each location.
• Weeks 13–20: Continue rolling out remaining locations in cohorts of 2–3 every 2 weeks. By week 20, all 10+ locations are live on ONE.

Phase 4: Optimization & Stabilization (Weeks 21–26)

• Conduct post-go-live audits at each location: verify daily revenue reconciliation, check appointment scheduling accuracy, and confirm billing is generating claims correctly.
• Run DSO-level reporting queries to ensure corporate dashboard reflects real-time data across all locations.
• Host "One Month In" retrospectives at each location to gather feedback and document best practices for scaling within DSO.

Key Metrics to Track

1. System Adoption Rate (Target: >90% within 60 days of go-live). Measure percentage of staff actively using ONE for daily tasks (check active user logins, appointment entries, charge submissions). Locations below 75% trigger retraining.

2. Data Migration Accuracy (Target: 100% patient record integrity). Reconcile patient counts, insurance records, and A/R balances between legacy system and ONE. Flag any discrepancies >$500 or missing records for manual correction.

3. Billing Cycle Time (Target: reduction from current state to <5 business days from visit to claim submission). Track days from appointment to claim sent across ONE locations vs. legacy sites. ONE typically cuts this by 30–40%.

4. Staff Productivity Gains (Target: 10–15% reduction in front desk/billing FTE hours per location within 90 days). Measure hours spent on manual entry, insurance follow-up, and patient scheduling before and after; reinvest saved hours into patient experience or revenue cycle management.

5. Accounts Receivable Days Outstanding (Target: 40–45 days, down from industry average of 50–60). Track DSO-wide A/R aging as locations migrate to ONE. ONE's automated insurance verification and claim tracking typically reduces DSO-wide A/R by 8–12%.

6. Executive Reporting Accuracy (Target: same-day visibility into production, collections, and scheduling across all locations). Validate that DSO dashboards pull accurate, real-time data. Any lag or discrepancy between location reports and corporate roll-up signals a data sync issue.

Common Pitfalls

Pitfall 1: Underestimating customization and integration effort. Many DSOs assume ONE is "plug and play," but a 10+ location deployment requires mapping fee schedules, insurance rules, and reporting hierarchies across practices with different specialties or patient mixes. Avoid this: Budget 4–6 weeks for configuration before pilot go-live; involve a Henry Schein implementation partner, not just internal IT.

Pitfall 2: Skipping parallel testing or cutting it short. Eager to "flip the switch," practices shut down legacy systems after 3–5 days of ONE, then discover missing patient data or broken workflows. Avoid this: Run parallel testing for a full 2-week billing cycle; reconcile ONE output against legacy reports line-by-line. Only go live when finance signs off.

Pitfall 3: Inconsistent training across locations. Corporate trains location 1; location 2 gets a recorded video; location 3 relies on a peer trainer who half-remembers. Front desk at location 4 never learns ONE's insurance verification step, leading to claim rejections. Avoid this: Mandate live, role-specific training (front desk, clinical, billing) for every location. Provide printed quick-reference guides and name one "power user" per location as a post-launch support resource.

Pitfall 4: Failing to enforce data cleanup before migration. Legacy systems are full of duplicate patients, old insurance records, and incomplete demographics. Migrating this mess corrupts ONE and creates rework. Avoid this: Hire a data analyst or use Henry Schein's data migration services to scrub and validate source data 3–4 weeks before each location's go-live.

Pitfall 5: Not establishing a DSO-wide ONE governance structure. Without clear ownership of ONE maintenance, updates, and user support, locations start diverging in configuration—one practice customizes fee schedules one way, another does it differently, breaking DSO reporting. Avoid this: Assign a DSO "ONE Administrator" (0.5–1.0 FTE) to manage updates, user access, and configuration changes across all locations. Create a monthly "ONE User Council" call where location managers flag issues and share best practices.

Cost & ROI Framework

**Implementation Costs (All-