Fortune Billing Solutions — Implementation Playbook (DSO)

Executive Summary

Fortune Billing Solutions provides comprehensive revenue-cycle management (RCM) and billing services to multi-location medical practices, dental groups, and surgical centers. As a Dental Service Organization (DSO) or physician practice group, you operate under a federated model where individual locations maintain clinical autonomy while standardizing back-office operations. DSOs benefit uniquely from centralized billing implementation because: (1) they eliminate billing variance across locations, (2) they create economies of scale in staffing and software, and (3) they establish enforceable compliance standards across networked entities.

Expected Timeline: 16 weeks to full operational deployment across a 5-10 location DSO; ongoing optimization through month 6.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• Network Infrastructure: Verify HIPAA-compliant VPN connectivity and bandwidth (minimum 25 Mbps upload/download per location). Test connection stability before go-live.
• Hardware: Procure 2-3 dedicated workstations per pilot location (not shared clinical terminals). Ensure printers are networked and HIPAA-compliant.
• Software Stack: Confirm integrations between your EHR/PMS, your practice management system, and Fortune's platform. Map data flows for claims, patient demographics, and insurance eligibility.
• Backup & Disaster Recovery: Establish daily backup protocols and test failover procedures before Week 3.

Stakeholder Alignment

• Clinical Leadership: Schedule meetings with location medical/dental directors to clarify that billing changes do NOT affect clinical workflows. This reduces resistance and misconception.
• Practice Managers: These are your change champions. Create a DSO Billing Committee with 1 representative per location plus central finance/compliance leads.
• Billing/Front Desk Staff: Conduct a "current-state" meeting documenting existing claim submission processes, denial management workflows, and patient communication templates. Document manual workarounds—they'll need to be replaced, not preserved.
• IT/Compliance: Confirm access controls, audit logging requirements, and any regulatory mandates (state-specific insurance regulations, Medicaid compliance).

Baseline Metrics to Capture

Before any system touches a claim, establish your starting position:

Store these in a shared spreadsheet; these become your Week 12 and Week 16 comparison points.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose your pilot site strategically:

• Volume: 200-400 claims/month (large enough to validate workflows, small enough to contain risk)
• Leadership: Practice manager/office administrator who is receptive to change and present on-site daily
• Diversity: If DSO spans multiple specialties (e.g., pediatric dentistry + orthodontics), select one that represents your complexity
• Stability: Avoid locations in flux (recent ownership change, leadership turnover, staffing gaps)
• Pain Points: Preferably a location experiencing high denial rates or slow collections—quick wins build momentum

Avoid: Selecting your largest revenue location first. Pilot success depends on learning, not maximizing immediate ROI.

Configuration and Setup

Week 3 - Data Prep & System Build:

• Work with Fortune's onboarding team to extract and cleanse your location's historical data (last 90 days of claims, patient demographics, fee schedules).
• Map your payer contracts into Fortune's system. Missing payers = claims sent to wrong addresses = immediate failure.
• Configure claim templates for your top 10 payers (e.g., United, Aetna, Medicaid) with correct routing, coding rules, and submission methods.
• Set up user roles (biller, supervisor, provider, patient portal user). Limit access by principle of least privilege.

Week 4 - Parallel Running:

• Run Fortune's system alongside your existing process for 2 weeks. Continue submitting claims via your old method.
• Input a subset of new claims (50-75/week) into Fortune to validate workflows and outputs.
• Reconcile: Do Fortune's submitted claims match your manual submissions? Investigate any discrepancies before full cutover.

Week 5-6 - Controlled Cutover:

• Week 5: Stop manual claims entry; route 100% of new claims through Fortune.
• Week 6: Run reports comparing Fortune submissions to prior week's volume, accuracy, and timeliness. If clean claim rate is ≥92%, you're ready to scale.

Training Approach

• Just-in-time training: Avoid lecture-style training 6 weeks before go-live; staff forgets. Train 5-7 days before cutover.
• Modular sessions:
  • Billing staff (90 min): Claim entry, eligibility verification, submission process, exception handling.
  • Front desk (45 min): Patient eligibility checks, co-pay collection, insurance verification.
  • Supervisors (120 min): Reporting, denial management, daily reconciliation, escalation paths.
• Hands-on labs: Each participant enters 3-5 sample claims under supervisor observation. Certification: 95% accuracy on mock claims.
• Cheat sheets: Create laminated, location-specific quick-reference guides (not 50-page manuals).

Scaled Rollout (Weeks 7-16)

Wave Planning

Deploy in 2-3 waves by location size/complexity:

Stagger go-lives by 2-3 weeks to prevent support bottleneck. Fortune assigns a dedicated implementation lead to your DSO; they cannot support 10 simultaneous cutover crises.

Change Management

• Weekly DSO Committee Meetings: Discuss blockers, celebrate wins, review metrics.
• Communication Cadence: Email blast to all staff 2 weeks pre-cutover, 1 week pre-cutover, and day-of go-live.
• Resistance Patterns: Expect billing staff to say "this is slower than before" (true for 2-3 weeks—the learning curve is real). Counter with: "Your denial rate dropped 18%, and rework hours fell 8 hours/week by week 8." Quantify benefit.
• Clinical Staff Skepticism: Emphasize zero impact on patient care or clinical workflows. Partner with a respected clinician to vouch for non-disruption.

Support Infrastructure

• Hotline: Designate a single Tier-1 support contact at your DSO HQ (not multiple numbers leading to confusion). This person triages issues and escalates to Fortune.
• Escalation Path: Tier-1 → Tier-2 (Fortune Implementation Lead) → Tier-3 (Fortune Engineering) with defined SLAs (critical issues: 2-hour response).
• Weekly Office Hours: Schedule 60-minute open forum calls with all go-live locations during weeks 7-12. Batch common questions; avoid one-off support.
• Peer Network: Connect billing managers across locations via a shared Slack channel. Peer-to-peer learning is faster than waiting for official channels.

ROI Tracking

Key Metrics to Measure

Track these weekly during rollout; monthly thereafter:

1. DSO (Days Sales Outstanding): Target ≥10% improvement by week 16. (e.g., from 48 to 42 days)
2. **Clean Claim Rate