Shared Practices — Implementation Playbook (DSO)

Executive Summary

Shared Practices is a cloud-based practice management platform that centralizes clinical scheduling, patient communications, billing, and reporting across multiple locations and providers. For Dental Service Organizations (DSOs), it replaces fragmented point solutions with a unified operational backbone that standardizes workflows while maintaining local autonomy.

Why DSOs benefit: DSOs operate under inherent tension—corporate standardization versus practice independence. Shared Practices solves this by enforcing consistent KPIs and compliance across locations while allowing customization at the practice level. A 15-location DSO typically manages 5-7 disconnected systems; Shared Practices consolidates these into a single source of truth, reducing administrative overhead by 25-35% and accelerating billing cycles by 3-5 days.

Expected timeline: 16 weeks from contract signature to full deployment across a typical 10-15 location DSO, with 4 weeks pre-implementation, 4 weeks pilot, and 8 weeks scaled rollout.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• Infrastructure audit: Verify all locations have minimum 25 Mbps internet (symmetrical preferred). DSOs often have legacy broadband; budget $2,000-5,000 per underperforming location for fiber/dedicated upgrades.
• Device inventory: Confirm desktop/tablet availability for front desk, clinical, and billing staff. Shared Practices runs on iPad (clinical charting), Windows/Mac desktops, and Android tablets. Identify 20% device refresh need.
• EHR integration points: Map current EHR (Dentrix, Eaglesoft, Open Dental, Curve) to Shared Practices. Integration happens via HL7 feeds or API; allow 2 weeks for IT vendor coordination.
• Historical data migration: Establish 12-month patient/clinical/financial data pull from legacy systems. Shared Practices team provides templates; DSO IT must validate data quality (expect 5-8% cleanup required).
• Single sign-on (SSO): If your DSO uses Okta, Azure AD, or Google Workspace, configure SAML integration now. This prevents password proliferation and accelerates onboarding.

Stakeholder Alignment

• Executive sponsorship: DSO CEO/COO must publicly commit to Shared Practices as the unified system-of-record. Without top cover, practice managers will hold onto legacy systems.
• Clinical council: Dentists and hygienists often resist scheduling changes. Establish a 5-person clinical advisory group (mix of high-volume and resistant practitioners) to vet workflows before rollout.
• Finance sign-off: Shared Practices changes insurance verification, patient billing, and AR aging protocols. CFO and billing director must review and approve new workflows.
• IT resource allocation: Assign one FTE IT lead as Shared Practices champion. This person owns integration, troubleshooting, and local IT support escalation.

Baseline Metrics to Capture

Record these before pilot starts—you'll compare against them at 90 days:

• Operational: Appointment scheduling time per patient, front-desk labor hours/location, daily report generation time.
• Clinical: Chart completion lag (hours between appointment and signed note), radiograph upload rates.
• Financial: Days sales outstanding (DSO average), insurance verification rate, claim denial rate, patient payment collection rate.
• Staff: Help desk tickets per 100 staff, staff training hours, system downtime incidents.

Create a shared spreadsheet tracked by the Shared Practices PM; this becomes your ROI proof point.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose your pilot practice strategically:

• Size: 3-5 providers, 8-12 staff. Large enough to test workflows, small enough to manage risk.
• Tech readiness: Select a practice with decent IT infrastructure and a supportive manager. Avoid your most resistant location.
• Complexity: Ideal pilot has mix of general dentistry, specialty referrals, and insurance/cash-pay patients. Avoid single-provider, cash-only practices.
• Stability: No planned staff turnover, recent office renovations, or ownership transitions during pilot.
• Geography: If multi-state DSO, choose a pilot within your strongest compliance jurisdiction (e.g., most active dental board).

Anti-pattern: Choosing your flagship location. High-volume practices have zero tolerance for downtime and become defensive about change. Pilots require patience.

Configuration and Setup (3 weeks)

Week 3: Build-out

• Shared Practices team configures treatment codes, fee schedules, insurance payers (download from national database, customize locally).
• Practice manager maps clinical roles to system permissions (who can verify insurance, write off balances, access payroll).
• Create appointment templates by provider, factoring in treatment time, hygiene cycles, and buffer zones.

Week 4: Data migration

• Historical 12-month data loads into Shared Practices; validate 100% of active patients appear in system.
• Shared Practices team runs reconciliation: appointment count, charge count, payment count should match legacy system ±2%.
• Fix discrepancies (missing insurance, orphaned charges, duplicate records).

Week 5: Parallel run

• Staff use both legacy system and Shared Practices simultaneously. New appointments go into both; billing processed via legacy system only.
• This 1-week overlap lets staff acclimate without breaking revenue cycle.
• IT support team shadows all users; capture questions/friction points.

Training Approach

Role-based training (not full-group):

• Front desk (4 hours over 2 days): Patient check-in, appointment confirmation, insurance verification, payment posting.
• Clinical staff (3 hours over 2 days): Chart navigation, radiograph upload, prescription entry, referral routing.
• Billing (8 hours over 3 days): Claim submission, payment reconciliation, patient statements, aging analysis.
• Providers (2 hours): Chart review, signature workflows, reporting dashboard overview.

Deliver training in shifts to maintain coverage. Use practice's conference room, not Shared Practices' webinar (too passive). Shared Practices provides recorded sessions; staff watch async if they miss live.

Documentation: Shared Practices team creates 2-3 page quick-start guides for each role (screenshots, numbered steps). Laminate and post at workstations.

Scaled Rollout (Weeks 7-16)

Wave Planning

Deploy in 2-3 waves, staggered by 2 weeks:

• Wave 1 (Weeks 7-9): 3-4 locations. Choose geographically proximate practices and those with strong IT/management.
• Wave 2 (Weeks 10-12): 4-5 locations. Include 1 "resistant" practice to normalize change.
• Wave 3 (Weeks 13-16): Remainder, including any high-complexity locations.

Each wave follows the 3-week pilot playbook: build-out, migration, parallel run.

Parallel resources: Dedicate Shared Practices success manager to waves 1-2; DSO IT lead takes the lead on wave 3.

Change Management

• Weekly DSO all-hands call: CEO reviews progress, celebrates pilot wins, answers concerns.
• Practice-level huddles: Weekly 15-min stand-ups at each location during rollout week. Focus: today's blockers, quick wins.
• Super-user program: Identify 1-2 early adopters per practice; offer them 4 hours of advanced training and direct Shared Practices support line. They become peer mentors.
• Communication cadence: Email summary every Friday (what worked, what's next) and a town hall video monthly.

Resistance playbook: When a practice pushes back (common in week 2 of their rollout), acknowledge it, don't dismiss. Pair them with a super-user from a successful prior wave for a 30-min call.

Support Infrastructure

• Shared Practices support: Tiered phone/chat/email support. Assign your DSO IT lead as primary contact (they ticket issues, escalate to Shared Practices).
• Local IT coverage: Each practice has 1 staff member trained as "system admin" (password resets, device troubleshooting, local network issues).
• Escalation path: Practice admin → DSO IT lead → Shared Practices support (SLA: critical issue response within 4