Harbera — Implementation Playbook (DSO)

Executive Summary

Harbera is a credentialing intelligence platform that automates provider verification, license tracking, and compliance documentation—eliminating manual spreadsheets and reducing time-to-revenue for dental practices. For DSOs managing multiple locations, Harbera centralizes credentialing workflows across the network while maintaining location-specific payer relationships and regulatory compliance.

DSO-specific benefits include: single-tenant administrative oversight of all locations, bulk provider onboarding across networks, automated renewal alerts to prevent revenue leakage, and unified reporting for multi-location compliance audits. Network-wide deployment typically achieves full adoption within 16 weeks, with revenue impact visible by week 8.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

Infrastructure & Access

• Identify your IT point-of-contact and confirm they can manage SSO/SAML integration with your existing practice management system (Dentrix, Eaglesoft, Open Dental, etc.)
• Verify all locations have stable internet connectivity (minimum 5 Mbps upload/download)
• Confirm you have at least one dedicated admin account per location (practice manager or office coordinator level)
• Audit current provider database: export full list including NPI numbers, license IDs, and payer panel statuses. This becomes your baseline dataset.

Data Audit

• Identify incomplete provider records (missing NPIs, expired licenses, unpaneled payers)
• List all active state dental boards and insurance panels your DSO contracts with
• Document any custom credentialing workflows or payer-specific requirements unique to individual locations

Stakeholder Alignment

Secure Executive Buy-In

• Frame implementation as efficiency gain for practice managers and risk mitigation for compliance officers, not as a cost center. Target metric: "3-5 hours of admin time saved per location per week."
• Present to your DSO leadership team, practice managers, and compliance lead simultaneously to prevent siloed objections
• Establish a steering committee: DSO COO/operations lead, one practice manager champion from your pilot location, compliance officer, and IT lead

Identify Champions

• Recruit 1–2 practice managers who are digitally comfortable and trusted by peers to be co-trainers
• Assign a single point-of-contact at DSO HQ to resolve escalations (this should be your compliance officer or operations manager)

Baseline Metrics to Capture

Document these before Harbera goes live:

• Revenue leakage: How many providers are currently unpaneled or have expired credentials? Estimate annual impact (typical DSO: $50K–$150K lost across multi-location network)
• Admin burden: Track hours spent on manual credentialing per location per month
• Compliance risk: Number of expired licenses or missing documentation flagged in last audit
• Payer panel lag: Average time from provider hire to first claim payment (should be 4-6 weeks; if longer, credentialing is the bottleneck)

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose your pilot site strategically:

• Medium complexity: Not your smallest location (too few providers for meaningful metrics) or your largest (too much risk). Target: 8–15 active providers
• Strong operations: Select a practice manager who is organized, responsive, and respected—they'll be your trainer for other locations
• Diverse payer mix: Ensure the location handles 3+ major insurers (Delta, United, Cigna, etc.) so you validate multi-payer workflows
• Manageable backlog: Avoid locations in crisis mode; your team needs bandwidth to learn

Configuration & Setup (Week 3)

Pre-Deployment (3 days)

• Harbera onboarding specialist conducts discovery call with your pilot practice manager and IT lead
• Review: current PMS integration points, your state board requirements, active payer panels
• Establish data-sharing agreements if pulling real-time provider data from your PMS
• Set up SSO so users log in through your existing directory (Active Directory or Google Workspace)

Launch & Initial Load (Days 4–5)

• Harbera populates the system with your exported provider dataset
• Your pilot practice manager validates 100% of records for accuracy (names, NPIs, license numbers, current payer panels)
• Flag any data gaps (missing NPIs, expired licenses) for immediate remediation—this becomes your "day one" correction queue
• Harbera configures automated rules: license renewal alerts 120 days before expiration, payer re-verification on 36-month cycles

Training Approach (Week 4)

Train-the-Trainer Model

• Conduct 2-hour in-person session with pilot practice manager + your DSO operations champion
• Walk through: adding a new provider from hire to paneling, responding to renewal alerts, generating compliance reports
• Role-play common scenarios (license denial, payer rejection, credentialing gap discovered mid-month)
• Provide 1-page quick-reference guides laminated for the front desk

Live Pilot Usage (Weeks 4–6)

• Practice manager uses Harbera for all credentialing tasks; Harbera assigned a success manager as escalation point
• Weekly 20-minute check-ins to troubleshoot and capture feedback
• Document what's working ("license renewals are now caught automatically") and what's confusing (unclear approval workflows, slow payer integrations)
• Prepare case studies: quantify time saved and revenue recovered

Scaled Rollout (Weeks 7-16)

Wave Planning

Wave 1 (Weeks 7–9): 3–4 locations

• Select locations similar to your pilot (medium size, established teams)
• Assign your pilot's practice manager as co-trainer for at least one Wave 1 location
• Deploy on a Monday to avoid weekend complications; plan for 2 days of lighter scheduling as staff onboards
• Use pilot location as a reference point when field questions ("If you're wondering how to handle X, let's jump on a call with [Pilot PM]")

Wave 2 (Weeks 10–13): 50% of remaining locations

• Stagger deployments by 1–2 weeks to avoid overwhelming your central support team
• Recruit additional champions from Wave 1 to co-train Wave 2
• Begin capturing wins from early locations in DSO-wide communications (monthly team calls, newsletters)

Wave 3 (Weeks 14–16): Final locations

• Smaller, high-risk, or operationally challenged locations deploy last
• Assign dedicated virtual support for locations showing resistance
• Full network operational by end of week 16

Change Management

Communication Cadence

• Weekly DSO all-hands: 5-minute update on rollout progress, highlight from deployed location, Q&A
• Monthly practice manager calls: Peer-to-peer sharing of best practices (e.g., "Here's how we're reducing credentialing time by batching provider onboarding")
• Escalation path: Direct line to your DSO operations lead for practice managers who feel overwhelmed

Resistance Handling

• If a location is struggling, audit their provider volume and payer complexity; simplify by deferring specialty payers to week 2
• Offer 1:1 screen-share sessions for practice managers uncomfortable with software; pair them with a peer champion, not a vendor rep
• Reframe as time for people (less admin time = more patient scheduling) rather than time replacing people

Support Infrastructure

Week 7 Onward

• Designate a "Harbera Lead" at your DSO HQ (typically your operations manager or compliance officer) to own rollout and serve as single point of escalation
• Set up a dedicated Slack channel (#harbera-implementation) for peer questions across locations
• Assign each location a secondary user (backup) trained by week 8; prevents single-point-of-failure if primary practice manager is out
• Conduct "office hours" every Thursday at 2 PM: 30-minute open Q&A with Harbera success manager + your DSO lead

ROI Tracking

Key Metrics to Measure