Gaidge — Implementation Playbook (DSO)

Executive Summary

Gaidge is a cloud-based practice management platform designed to unify clinical scheduling, patient communications, billing workflows, and multi-location operations into a single system. For Dental Service Organizations (DSOs), Gaidge eliminates the fragmentation that occurs when multiple acquired practices operate on disparate systems, enabling standardized operations, centralized reporting, and predictable revenue cycles across the entire network.

DSOs benefit uniquely because they operate at scale with shared service centers, standardized protocols, and a need for real-time visibility across dozens of locations simultaneously. A typical DSO deployment reduces administrative overhead by 25-35%, accelerates accounts receivable by 18-22 days, and improves patient acceptance rates through unified communication workflows.

Expected timeline: 12-16 weeks to full deployment across a 10-15 location network, with first operational location live in 4-5 weeks.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• Network infrastructure: Verify all locations have minimum 10 Mbps upload/download speeds. Document VPN or firewall configurations that may restrict API integrations.
• Hardware audit: Audit existing workstations, scanners, and card readers at each location. Gaidge is browser-based (no desktop installation), but identify antiquated machines requiring replacement.
• Data migration scope: Pull a complete inventory of current PM system(s)—patient records, appointment history, billing data, insurance tables. Flag HIPAA compliance gaps in current export processes.
• Integration dependencies: Map connections to practice's current systems: billing clearinghouses, insurance verification platforms, imaging software, EHRs. Document API credentials and access permissions needed.

Stakeholder Alignment

Critical players:

• DSO Executive Sponsor: Assigns budget, removes blockers, communicates priority to locations.
• Clinical Operations Director: Defines scheduling templates, clinical workflows, and location-specific protocols.
• Billing/Revenue Cycle Lead: Owns insurance table setup, fee schedules, claim submission rules.
• IT/Technical Lead: Manages data security, user access, system integrations.
• Location Managers (pilot sites): Day-to-day champions who interface with staff.

First meeting agenda (Week 1):

• Clarify go-live commitment dates and non-negotiables.
• Establish escalation protocol and support SLAs.
• Confirm data migration cutover approach (big bang vs. parallel run).
• Identify any legacy system dependencies that must stay live during transition.

Baseline Metrics to Capture

Before Gaidge goes live, baseline the following at each location:

Timing: Capture Week 1-2 baseline; plan re-measurement at Day 30 post-go-live.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose 2-3 pilot locations that represent your DSO's diversity but are operationally ready:

• Location maturity: Pilot at locations with stable, engaged teams. Avoid your most chaotic location (too many variables) or your smoothest location (less learning).
• Patient volume: 150-300 active patients preferred—large enough to test workflows, small enough to fail safely.
• Staff turnover: Prioritize locations with consistent staff; training effectiveness suffers with high turnover.
• Technology readiness: At least one team member comfortable with browser-based systems.
• Geographic representation: If your DSO operates specialty-specific locations (ortho, endo), include at least one.

Configuration and Setup (Weeks 3-4)

Week 3: System Prep

• Gaidge team provisions test/production environments; assign user accounts to pilot staff.
• DSO IT lead completes integration setup: insurance verification API, EHR connectors, clearinghouse feeds.
• Validate data migration: run test import of patient records, insurance info, and appointment history from legacy system. Spot-check 20-30 records for accuracy.
• Customize fee schedules, insurance plan rules, and appointment types to match pilot location's protocols.

Week 4: Staff Readiness

• Conduct "train-the-trainer" session with pilot location's office manager and 1-2 key staff members (2-3 hours, hands-on).
• Create location-specific quick reference guides (1-2 pages maximum): appointment booking, treatment plan entry, patient communication templates.
• Set up "mock patient" test appointments to simulate real workflow before cutover.
• Identify "Gaidge Lead" at each pilot location—person staff can ask questions (not Gaidge vendor).

Training Approach

Tiered training:

• Tier 1 (Leads, 4 hours): Full system navigation, admin functions, troubleshooting, reporting.
• Tier 2 (Clinical staff, 2 hours): Charting, patient communication, imaging integration.
• Tier 3 (Admin staff, 3 hours): Scheduling, insurance verification, claim tracking, patient payments.

Format: Combination of live demo (with real practice data after cutover) and asynchronous video library. Conduct training 2-3 days before go-live so knowledge is fresh.

Support during pilot: Gaidge success manager + DSO IT lead on-site or available via Slack for first 3 days of go-live. Establish 2-hour huddle calls daily for first 2 weeks to surface issues early.

Scaled Rollout (Weeks 7-16)

Wave Planning

Wave 2 (Weeks 7-10): 3-4 locations

• Incorporate lessons from pilot; update training materials and quick guides.
• Roll out to geographically or operationally similar locations to pilot.

Wave 3 (Weeks 11-14): 4-5 locations

• Staff at Wave 2 locations now train Wave 3 locations (peer learning reduces vendor dependency).

Wave 4 (Weeks 15-16): Remaining locations

• Final cohort; at this point, internal DSO team is self-sufficient.

Cutover approach for each location:

• Parallel run: Run legacy + Gaidge simultaneously for 1 week (higher labor cost but reduces risk).
• Big bang: Cut over at end of business Friday, verify data integrity Monday morning before patient appointments (faster but requires bulletproof data migration).

Most DSOs succeed with parallel run for pilot + Wave 2, then big bang for Waves 3-4 once team confidence is high.

Change Management

Executive communication:

• Monthly "DSO-wide" update from sponsor on rollout progress, highlighting wins (e.g., "Pilot location reduced scheduling time by 6 hours/week").
• Transparent messaging about short-term friction (first 2-3 weeks of slower appointments) and long-term gains.

Staff incentives:

• Recognize and reward locations that achieve billing metrics first (e.g., "Week 1 claims submitted cleanly").
• Peer recognition: share efficiency gains from each wave with the next wave group.

Feedback loops:

• Weekly "Issue Log" triage call: surface bugs, training gaps, workflow conflicts. Fix or document for Gaidge team.
• Monthly retrospective with each wave's location leads: what worked, what didn't, how to optimize for next cohort.

Support Infrastructure

Establish 3-tier support structure: