Tesia Clearinghouse — Implementation Playbook (DSO)

Executive Summary

Tesia Clearinghouse is a revenue-cycle management platform that automates claim submission, adjudication tracking, denial management, and payment posting across multiple payers and practice locations. It consolidates fragmented billing workflows into a centralized clearinghouse that reduces claim processing times by 40-60% and improves first-pass acceptance rates by 25-35%.

Why DSOs Benefit Specifically: Dental Service Organizations managing 8-50+ locations face exponential complexity in revenue-cycle standardization. Tesia eliminates manual claim workarounds by enforcing consistent submission logic, real-time visibility across all locations, and centralized appeals management. DSOs capture $80K-$150K in annual recovery per location through faster payment cycles and denial prevention alone.

Expected Timeline: 16 weeks to full deployment across all locations (pilot + scaled rollout), with productivity gains measurable by week 4.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• EHR/Practice Management Integration: Confirm API connectivity or EDI file export capability with your primary PMS (Dentrix, Eaglesoft, Open Dental, Curve, etc.). Tesia requires patient demographics, procedure codes, insurance eligibility, and fee schedules in standardized format.
• Network Bandwidth: Minimum 5 Mbps upload capacity at each location for daily batch submissions; 25 Mbps recommended for real-time submissions.
• User Device Specifications: Windows 10/11 or macOS 11+ for workstations; iOS/Android for mobile claim monitoring. No specialized hardware required.
• Data Security Audit: Conduct HIPAA compliance review of current claim storage, transmission, and staff access protocols. Tesia's implementation requires encryption protocols and access role definitions before go-live.
• Payer Database Alignment: Audit all active insurance contracts (primary, secondary, tertiary). Map payer identifiers in your PMS to Tesia's payer registry. Identify non-standard payers requiring manual submission.

Stakeholder Alignment

• DSO Leadership: Obtain commitment on deployment timeline, budget allocation ($40K-$80K for DSO with 20+ locations), and staffing model (centralized vs. hybrid).
• Location Administrators: Schedule 30-minute sessions with office managers at pilot sites to understand current pain points, claim denial patterns, and staff turnover in billing roles.
• Billing Teams: Conduct survey of 8-12 staff across locations to identify workflow barriers—e.g., "How much time do you spend on rework claims weekly?" (Target: quantify baseline chaos.)
• IT Department: Assign primary contact for PMS integration, network troubleshooting, and security clearance.
• Payer Relationship Manager: Flag any payers with submission requirements that differ from Tesia's standard 837i format; identify payers requiring prior clearance for clearinghouse submission.

Baseline Metrics to Capture

Document these metrics across all locations before pilot begins:

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose 2-3 pilot locations that balance representativeness with readiness:

• Volume: Select one high-volume location (600+ claims/month) to stress-test the system.
• Payer Mix: Prioritize practices with 8+ active payers; avoid locations with only 2-3 payers.
• Billing Maturity: Choose a location with structured billing workflows and engaged staff (not the "broken" office; you'll need advocates).
• Geography: If multi-state, include at least one location outside your primary state to test state-specific compliance.
• Clinical Mix: Prefer ortho/endo/perio practices over general practices initially—higher claim complexity reveals integration gaps faster.

Configuration and Setup

Week 3:

• Complete PMS integration testing in sandbox environment. Run 50 sample claims through Tesia to validate patient data mapping, fee schedule accuracy, and claim submission logic.
• Configure payer submission rules: set submission windows (e.g., "submit 2 days after treatment"), set clearinghouse vs. direct-submission routing by payer, and define secondary/tertiary claim logic.
• Create staff access roles: designate claim submission supervisors, denial management leads, and analytics viewers. Avoid giving all staff full permissions.

Week 4:

• Run parallel processing: submit claims via both current workflow AND Tesia simultaneously for 2 weeks. Compare acceptance rates, EOB turnaround, and data accuracy.
• Load 90 days of historical claims into Tesia's denial engine for analysis. Identify top 10 denial reasons at pilot locations.
• Configure Tesia's mobile app; test push notifications for new EOBs and denials at target locations.

Week 5-6:

• Conduct UAT (user acceptance testing) with 6-8 billing staff from pilot locations. Run simulated workflows: submit claim → receive EOB → manage denial → post payment.
• Document any bugs, integration gaps, or workflow misalignments. Prioritize fixes by impact.

Training Approach

• Cohort-Based: Schedule 90-minute instructor-led sessions for each pilot location (separate morning/evening to accommodate schedules).
• Hands-On Labs: Allocate 60% of training to live system navigation; 40% to policy review (when to use Tesia, when to use manual submission).
• Role-Specific Modules:
  • Billing Staff: Claim submission, status tracking, basic troubleshooting.
  • Office Managers: Dashboard monitoring, staff performance reports, escalation protocols.
  • Providers: High-level overview; understanding patient statements accuracy.
• Certification: Require all operators to pass 15-question quiz before production access.
• Documentation: Create laminated quick-reference cards for front-desk staff (insurance verification workflow changes, if any).

Scaled Rollout (Weeks 7-16)

Wave Planning

Waves 2-3 (Weeks 7-10): Roll out to 6-10 locations in parallel based on readiness. Stagger go-live dates by 3-5 days to prevent simultaneous support load.

Waves 4-5 (Weeks 11-16): Deploy remaining locations in groups of 5-8. Prioritize high-AR locations and those with highest staff turnover (to lock in efficiency gains before turnover event).

Change Management

• Weekly Rollout Calls: 30-minute syncs with office managers at newly launched locations to surface issues in real-time.
• Quick Wins: Highlight success metrics weekly—e.g., "Location X reduced denials by 18% in Week 1."
• Resistance Handling: Identify vocal skeptics early; assign them as peer champions. Staff resistance often stems from fear of job displacement; clarify that Tesia shifts work from rework to prevention/analytics.
• Cutover Decisions: Decide go/no-go 48 hours before each location launch. Pause rollout if previous wave shows >15% claim rejection rate or >4 hours/day unplanned support.

Support Infrastructure

• Tier 1 (On-Site): Designate one staff member per location as Tesia super-user. Provide 1:1 coaching calls twice weekly for first 3 weeks.
• Tier 2 (DSO Central): Hire or assign 1.5 FTE dedicated Tesia administrators at DSO HQ. Responsibilities: PMS troubleshooting, payer submission rule updates, denial analytics, staff onboarding.
• **Tier