Ray Medical — Implementation Playbook (DSO)

Executive Summary

Ray Medical operates a multi-location diagnostic imaging network delivering CT, MRI, ultrasound, and X-ray services to patients and referring physicians across regional markets. As a DSO model, Ray Medical centralizes administrative operations, billing, scheduling, and compliance functions while maintaining clinical autonomy at individual imaging centers.

DSOs provide diagnostic imaging practices with critical operational leverage: consolidated billing reduces A/R days by 30-40%, centralized credentialing accelerates new location launches by 8-12 weeks, and unified scheduling algorithms improve equipment utilization by 15-25%. For Ray Medical, DSO implementation eliminates duplicate administrative spending, standardizes clinical workflows, and creates scalability for rapid market expansion.

Expected Timeline: 16 weeks to full operational deployment across a 4-location pilot network, with ongoing optimization continuing through month 6.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• EHR/Imaging PACS Integration: Confirm all pilot locations run compatible PACS systems (or budget for unified upgrade). Ray Medical must decide: single PACS instance or federated architecture with master patient indexing.
• Billing System Consolidation: Audit current billing vendors at each location. Plan cutover to single DSO billing platform (or tier-1 integration if legacy systems stay). Document all custom claim rules and payer contracts.
• Network Infrastructure: Ensure 100+ Mbps connectivity at all locations for PACS data sync and real-time scheduling. Test failover protocols for imaging data backup.
• Identity Management: Select single SSO provider (Okta, Azure AD) for unified credential access across locations. Plan rollout for 200+ users across clinical, admin, and support staff.
• Data Warehouse: Establish centralized analytics platform to aggregate scheduling, billing, and utilization metrics from all locations.

Stakeholder Alignment

• Physician Leadership: Secure buy-in from radiologist groups at each location. Address autonomy concerns explicitly—clinical decisions remain local; administrative standardization increases their margin.
• Practice Managers: Interview existing managers at each location. Identify champions who understand both local operations and willingness to adopt centralized processes. Plan role transitions (some may move to hub roles; others manage local operations under new guidelines).
• IT Leadership: Designate a DSO IT Director responsible for platform strategy. Ensure existing IT staff at locations are looped into planning (they will own local implementation).
• Payer Relations & Compliance: Brief Chief Compliance Officer and contracting team on DSO model—consolidated credentialing, single tax ID for billing, and unified audit trails reduce regulatory risk.

Baseline Metrics to Capture (Week 2)

Before any changes, document:

• Billing & Revenue: Current A/R days, claim denial rate, days-to-first-payment per location.
• Scheduling & Utilization: Equipment downtime hours/week, same-day scheduling percentage, no-show rate, average exam turnaround time.
• Staffing: Staff turnover rate, onboarding time for new technologists, vacation/sick coverage gaps.
• Clinical: Refer-back rates (exams requiring repeat imaging), average report turnaround time, referring physician satisfaction scores.
• Cost Structure: Current spend on billing, HR, compliance, IT per location; administrative FTE allocation.

These become your control baseline for ROI measurement.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Select 2 locations for simultaneous pilot (avoid sequential pilots—you need parallel data). Choose locations that:

• Represent operational diversity (e.g., one high-volume urban center, one mid-size suburban); avoid outliers.
• Have supportive practice leadership and willing IT staff.
• Are geographically proximate (easier hands-on support during launch).
• Have clean billing histories (avoid locations with compliance issues that complicate transition).

Exclude: Locations undergoing facility renovation, recently acquired, or operating legacy systems without upgrade path.

Configuration and Setup

Week 3–4: System Build

• Deploy unified scheduling system (e.g., Medidata, Athenahealth) in pilot locations. Run parallel scheduling for 1-2 weeks (old system + new system) to catch discrepancies.
• Integrate PACS with central analytics; validate real-time data flow.
• Establish master patient index (MPI) linking patients across locations.
• Configure billing platform with all payer contracts, fee schedules, and denial rules from both locations.

Week 5: Go-Live Preparation

• Conduct full data migration test: patient records, insurance verification, pending claims, physician profiles.
• Run billing parallel processing for 3-5 days before cutover (process 10% of claims through new system; validate accuracy).
• Establish daily reconciliation checklist: claims submitted vs. claims received, schedule integrity, PACS connectivity.

Training Approach

• Front Desk/Scheduling Staff (2-hour session): Hands-on scheduling system demo; teach new patient verification process (centralized insurance checks). Test 20 sample bookings before go-live.
• Billing/Administrative (3-hour session): Claims workflow in new system, payer portal changes, denial appeals process. Pair each admin person with a DSO billing specialist for first week.
• Radiologists & Technologists (1-hour session): Show PACS integration and report routing changes. Emphasize: clinical workflow does not change.
• IT Staff (Full-day workshop): System architecture, troubleshooting protocols, escalation procedures, backup/recovery procedures.

Deliver training 3 days before cutover; provide recorded videos for staff who miss live sessions.

Scaled Rollout (Weeks 7-16)

Wave Planning

Roll out remaining locations in two waves of 1 location each (Weeks 7–10 and 11–14), with 1-week buffer for learning from each wave before next.

Week 7–10: Wave 2 (Location 3)

• Apply learnings from pilot (bugs fixed, new training content added).
• Assign pilot location staff to mentor Wave 2 teams (cross-location knowledge transfer).

Week 11–14: Wave 3 (Location 4)

• By now, DSO operations are normalized; use full-scale playbook without modifications.

Week 15–16: Optimization Sprint

• Address any lingering integration issues.
• Fine-tune scheduling algorithms based on utilization patterns across all 4 locations.
• Begin planning for 5th location (proof of scalability).

Change Management

• Weekly All-Hands Calls (Fridays, 15 min): Communicate wins from pilot, address concerns. Celebrate early wins (e.g., "scheduling cut booking time by 2 days").
• Local Site Champions: Designate a champion at each location (practice manager or respected tech) to field questions and escalate issues daily.
• Resistance Navigation: Expect pushback from staff comfortable with old systems. Acknowledge this directly: "Change is hard. Here's why it's worth it" + show data from pilot locations on workload reduction.
• Issue Resolution SLA: All operational issues resolved within 24 hours during first 4 weeks; escalation path clear (local champion → DSO Operations Manager → CTO).

Support Infrastructure

• DSO Operations Hub (Centralized Team):

  • Director of DSO Operations (1 FTE)
  • Billing Manager (1 FTE, oversees all locations)
  • Scheduling Coordinator (1 FTE, monitors utilization)
  • IT Support Lead (1 FTE, on-call for system issues)

• On-Site Support During Rollout:

  • Assign one DSO staff member to each location for first 2 weeks post-go-live (8am–5pm). Role: answer questions, solve workflow issues in real-time.

• Help Desk: Establish single help desk number/ticketing system for all operational questions. Staff with rotating DSO team members (provides exposure to operations across locations).

ROI Tracking

Key Metrics to Measure