Stedi — Implementation Playbook (DSO)

Executive Summary

Stedi is a data infrastructure platform that automates EDI (Electronic Data Interchange) and supply chain document processing, transforming unstructured data into actionable insights across your network. For Dental Service Organizations (DSOs), this means eliminating manual claims processing, vendor onboarding delays, and supply chain visibility gaps across multiple locations with a single unified system.

DSOs benefit uniquely because they operate a federated model—multiple clinical locations, centralized procurement, and varied vendor compliance requirements create fragmentation that Stedi is purpose-built to solve. Rather than implementing separate solutions per location, DSOs deploy once and scale instantly across the entire network.

Expected deployment timeline: 12-16 weeks to full production across 5-50 locations, with ROI typically realized by week 8.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

Infrastructure:

• Secure, HIPAA-compliant data environment (Stedi handles this, but verify your network can support encrypted API endpoints)
• VPN or direct connect capability for practices still using legacy on-premise systems
• Minimum 99.5% uptime SLA confirmation from your IT team
• Active Directory or SSO integration readiness (required for multi-location access control)

Data Audit:

• Map all incoming document types (claims, eligibility requests, remittance advice, supply orders)
• Document current error rates and manual intervention touchpoints
• Identify data sources: vendor portals, email, EDI files, manual entry systems
• Catalog all downstream systems requiring integration (practice management, accounting, inventory)

Compliance Verification:

• Confirm HIPAA Business Associate Agreement (BAA) status with Stedi
• Audit current vendor compliance requirements across all locations
• Document any state-specific regulatory mandates (especially around telehealth claims)

Stakeholder Alignment

Executive Sponsor (Required):

• Designate a C-suite owner (typically COO or CFO) who owns implementation timeline and budget
• Monthly steering committee with representation from clinical, operations, and finance
• Clear decision rights for scope changes and trade-offs

Operational Champions (One per location type):

• Practice manager responsible for day-to-day processing
• IT contact for technical issues
• Finance/billing lead for claims reconciliation
• Supply chain manager for procurement workflows

Communication Plan:

• Weekly 15-minute huddles with location leads
• Monthly all-hands overview with ROI progress
• Dedicated Slack channel for troubleshooting

Baseline Metrics to Capture (Before Day One)

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose 2-3 pilot sites, not 1. Single-location pilots fail because they don't expose network complexity. Select:

1. High-volume location (largest patient base, highest claims volume)

   • Generates fastest ROI signal
   • Staff experienced in problem-solving
   • Can absorb implementation friction

2. Technically mature location (good IT hygiene, early adopters)

   • Reduces technical risk
   • Provides reference team for others
   • Can troubleshoot integration issues independently

3. Complex workflow location (multiple insurance types, high supply variance)

   • Proves system handles edge cases
   • De-risks full rollout complexity
   • Generates strongest business case for skeptics

Avoid: New locations, practices with IT turnover, or those already in crisis mode.

Configuration and Setup

Week 3: Sandbox Environment

• Stedi team provisions isolated test environment
• Import 30 days of historical claims and documents
• Run parallel processing (old + Stedi side-by-side) to validate accuracy
• Location team creates mapping rules for vendor-specific formats

Week 4: Integration Testing

• Connect practice management system via API
• Validate claim submission, eligibility checks, remittance import
• Test failure scenarios (vendor down, malformed data, timeout handling)
• Establish escalation runbook for <15 min manual remediation threshold

Week 5: Go-Live Preparation

• Run 1 full week of parallel processing
• Document all edge cases (cash patients, out-of-network, claim denials)
• Create location-specific training videos (show their actual workflows)
• Brief all staff; emphasize this reduces their manual work, not their job

Week 6: Go-Live + Monitoring

• Switch to production on a Monday morning (not Friday)
• Stedi + location IT pair on all processing for first 3 days
• Daily standups to review error logs and adjust rules
• Capture before/after metrics for ROI case study

Scaled Rollout (Weeks 7-16)

Wave Planning

Weeks 7-8 (Wave 1): 5-8 locations

• Select mix of location types (large, small, specialty practices)
• Each gets 1 dedicated Stedi onboarding engineer + your pilot team mentor
• Compress setup to 2 weeks (parallel not required if pilot proved stable)
• Target: 90%+ processing automation by day 14

Weeks 9-11 (Wave 2): 8-12 locations

• Proven playbook; minimal customization required
• Self-service setup with async Stedi support
• Peer mentoring from Wave 1 locations
• Target: All locations at >85% automation

Weeks 12-16 (Wave 3): Remaining locations

• Fully automated onboarding for standard configurations
• Custom workflows get 1 week of dedicated support
• Post-deployment: 30-day optimization phase per location

Change Management

Staff Resistance Mitigation:

• Reframe: Stedi eliminates errors and weekend work, not jobs
• Create "automation ambassador" role (billing staff who learn the system first and train peers)
• Celebrate early wins publicly (e.g., "$12K in claims processed error-free this week")
• Establish "ask me anything" office hours for 4 weeks post-launch

Process Updates:

• Document new workflows (which documents go where, how to handle exceptions)
• Update job descriptions to reflect higher-value work (analysis, vendor negotiation, patient service)
• Establish monthly "process kaizen" meetings to refine rules based on error patterns

Support Infrastructure

Tier 1 (First 2 hours):

• Location IT + operations manager—consult playbook, check Stedi dashboard, attempt fix

Tier 2 (2-24 hours):

• Designated operations lead + Stedi support engineer—debug integration, adjust rules

Tier 3 (Escalation):

• Your implementation sponsor + Stedi product team—resolve systemic issues

Knowledge Base:

• Maintain internal wiki with location-specific troubleshooting
• Record video walkthroughs for common tasks (how to manually process exception claims, how to override vendor rules)
• Monthly "what we learned" session with all locations

ROI Tracking

Key Metrics

1. Processing Automation Rate: % of documents processed without manual intervention

   • Stedi target: >90% across network
   • Value: $8-15/claim saved in labor

2. Claims Processing Time: Days from submission to remittance

   • Target: Reduce by 50% (e.g., 8 days → 4 days)
   • Value: Faster cash flow, fewer patient calls

3. Vendor Onboarding Time: Weeks to activate new supplier

   • Target: 60% reduction
   • Value: Supply chain agility

4. Exception Rate: % of submissions requiring manual rework

   • Target: <5%
   • Value: Predictability and quality

30/60/90 Day Benchmarks

Day 30 (Pilot locations):

• 70%+ automation rate achieved
• <10% exception rate (learning phase acceptable