AnnexMed — Implementation Playbook (DSO)

Executive Summary

AnnexMed is a healthcare staffing and practice management platform that streamlines credential verification, scheduling, payroll integration, and compliance tracking for healthcare providers. For Dental Service Organizations (DSOs), AnnexMed eliminates fragmented provider data across multiple locations and centralizes revenue-cycle visibility across the enterprise. DSOs specifically benefit because they operate multiple locations with complex payroll structures, variable provider schedules, and regulatory requirements that demand standardized processes without sacrificing location autonomy.

Expected deployment timeline: 16 weeks to full operational capacity across a 5-15 location DSO, with measurable DSO improvements by week 8.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

System Infrastructure

• Verify API connectivity to existing EHR/Practice Management System (Dentrix, Eaglesoft, Open Dental, etc.)
• Confirm single sign-on (SSO) capability via Active Directory or Okta
• Audit current data schemas for provider credentials, license status, and scheduling
• Allocate dedicated IT resource (minimum 4 hours/week) for integration support
• Establish secure data migration pathway for 12+ months of historical payroll/scheduling records

Network & Access

• Confirm bandwidth capacity at all locations (minimum 10 Mbps upload for real-time sync)
• Test VPN/remote access for satellite office staff
• Document all firewall rules that may block cloud platform connectivity

Stakeholder Alignment

Secure written commitment from these groups before proceeding:

Kickoff Meeting Deliverable: Create a DSO Steering Committee (8-10 people) that meets bi-weekly through week 16.

Baseline Metrics to Capture

Before implementation begins, establish a measurement baseline for each location:

• DSO-wide provider credentialing cycle time (average days from hire to activated status)
• License compliance gaps (% of providers with expired credentials across DSO)
• Payroll processing time (days from timesheet entry to paycheck)
• Scheduling inefficiency (% of open shifts, overtime as % of labor spend)
• Accounts receivable aging (% of claims >60 days outstanding)
• Compliance audit failure rate (deficiencies per CMS/state review)
• Provider turnover by location (identify high-churn practices)

Document these in a shared spreadsheet; you'll measure against these at 30/60/90 days.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose 2-3 pilot locations that represent your DSO's operational diversity:

Ideal Pilot Profile:

• Mid-sized practice (8-12 providers; not the largest, not the smallest)
• Operational stability (no leadership turnover in past 6 months)
• Digital readiness (already using cloud-based scheduling or EHR; not paper-dependent)
• Geographic spread (one urban, one suburban if possible; tests different IT infrastructure)
• Willing early adopters (practice manager interested in innovation, not resistant)

Avoid:

• Locations currently in transition (merger, relocation, leadership change)
• Practices with legacy systems that require custom API work
• High-staff-turnover locations (noise in adoption metrics)

Configuration and Setup

Week 3: Data Preparation

• Extract historical provider credentialing records from existing system
• Validate license/DEA/malpractice data for accuracy
• Map existing payroll codes to AnnexMed taxonomy
• Create test data sets (5-10 mock providers per location)

Week 4: AnnexMed Configuration

• Set up DSO-level organizational hierarchy (corporate office → regions → locations)
• Configure provider credential templates (state-specific requirements)
• Integrate with payroll system (test bi-directional sync)
• Establish compliance rules (license renewal alerts, background check triggers)
• Set user roles: DSO Administrator, Location Manager, Finance, Provider

Week 5: Data Migration & Testing

• Migrate pilot location data (clean data first; validate post-migration)
• Run parallel testing: old system + AnnexMed running simultaneously for 2 weeks
• Identify discrepancies; reconcile before go-live
• Test all integrations: EHR, payroll, credentialing database

Week 6: Go-Live (Pilot)

• Cut over on a Monday; have support team on standby all week
• Run both systems in parallel for first week (safety net)
• Daily check-ins with pilot practice managers
• Capture feedback and log issues in shared tracker

Scaled Rollout (Weeks 7-16)

Wave Planning

After pilot success (defined as: 80%+ user adoption, zero critical errors, positive provider feedback), execute two more waves:

Wave 2 (Weeks 7-10): 3-5 Medium Locations

• Benefit from pilot learnings; reduce setup time to 2 weeks per location
• Roll out on staggered schedule (Monday each week) to avoid support bottlenecks

Wave 3 (Weeks 11-16): Remaining Locations

• Largest, most complex locations go last
• DSO operations team (not AnnexMed) leads setup; AnnexMed provides escalation only
• Target final go-live by end of week 16

Change Management

Provider & Staff Communication:

• Month 1: "What's changing and why" email + FAQs (address compensation, scheduling access)
• Week of Go-Live: In-person 20-minute training at each location (demonstrate 3 most-used features)
• Ongoing: Monthly DSO-wide office hours (open Q&A with AnnexMed product team)

Resistance Mitigation:

• Identify "super-users" at each location early; train them as peer advocates
• Address compensation accuracy concerns immediately (payroll errors kill adoption)
• Create a "feedback loop" where location managers see their suggestions implemented

Support Infrastructure

Staffing:

• Dedicate 1 FTE DSO Operations Lead (point person for all locations; interfacing with AnnexMed support)
• Designate 1 Location "Champion" per practice (15-20 hours/month during waves 2-3)
• AnnexMed provides: dedicated implementation manager + technical support (email, phone, Slack)

Escalation Path:

1. Location champion → AnnexMed Knowledge Base
2. Practice manager → DSO Operations Lead (internal troubleshooting)
3. DSO Operations Lead → AnnexMed Support Engineer (technical issues, integrations)

Knowledge Base:

• Centralized wiki/Sharepoint with location-specific setup docs
• Video library (2-3 min screencasts on common tasks)
• Weekly "how-to" digest emailed to all managers

ROI Tracking

Key Metrics to Measure

Revenue Cycle Efficiency:

• Credentialing cycle time (target: 30% reduction by week 12)
• Claims denial rate (target: 5-10% reduction via compliance verification)
• AR aging (target: 8% improvement in <30-day claims)

Operational Cost Savings:

• Payroll processing labor hours (target: 40% reduction)
• Compliance audit deficiencies (target: 60% fewer findings)
• Provider scheduling optimization (target: 15% reduction in overtime hours)

Adoption & Engagement:

• % of providers actively using portal (target: 75%+ by week 12)
• % of locations with 95%+ data accuracy (target: all by week 16)
• Support ticket volume (should rise in weeks 3-6, then decline as users self-serve)

30/60/90 Day Benchmarks