Lassie — Implementation Playbook (DSO)

Executive Summary

Lassie is an AI-powered revenue-cycle management platform that automates patient billing, payment posting, claim follow-up, and denial management across distributed dental practices. For DSOs specifically, Lassie eliminates the complexity of managing revenue operations across 10–100+ locations while maintaining local compliance and payer relationships.

DSOs benefit because: (1) standardized billing reduces per-location overhead by 40–60%, (2) centralized data visibility identifies systemic claim leakage, and (3) automated workflows free billing staff to focus on high-touch patient communication and problem resolution.

Expected timeline to full deployment: 16 weeks for a 10–30 location DSO; 20–24 weeks for 30+ locations.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• EHR/Practice Management System (PMS) integration: Confirm API access and data export capability. Lassie connects via HL7, REST, or flat-file exports. Schedule integration audit with your PMS vendor.
• Network & Security: Verify HIPAA-compliant hosting, VPN access if required, and firewall rules. Confirm SSO (SAML 2.0) capability for centralized DSO user management.
• Data infrastructure: Allocate secure staging environment for claims data migration. Baseline: 6–12 months of historical claims for pattern recognition training.
• Hardware/Endpoints: Minimal—browser-based platform. Confirm all staff have modern browsers (Chrome, Firefox, Safari). No specialized hardware needed.

Stakeholder Alignment

• Executive sponsor: CFO or Chief Operations Officer owns DSO-wide rollout mandate and removes blockers.
• Regional/location leaders: Schedule 30-min kickoff calls. Frame Lassie as a support tool for their billing team, not a replacement. Address job security concerns upfront.
• Billing team leads: Identify 2–3 locations with highest claim volume and lowest staff turnover (your pilot sites).
• IT/Compliance: Document data access permissions, audit trail requirements, and disaster recovery expectations.
• Payers/clearinghouses: Alert top 5–10 payers that submission format/timing may optimize. No blocking action needed, but transparency avoids surprises.

Baseline Metrics to Capture

Before Lassie goes live, establish Day 1 benchmarks:

Capture location-level data. This lets you compare pilot sites against non-pilot controls.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose 2–3 sites, not 1. Reasons:

• Validate that Lassie works across different patient mixes (pediatric, ortho, general/restorative).
• One location may have outdated PMS or billing staff resistance; a second site proves results aren't coincidental.
• Early wins at 2 locations build confidence for broader DSO adoption.

Select based on:

• Volume: 200–400 weekly claims (large enough to show impact, small enough to support manually if needed).
• Stability: Low staff turnover; experienced billing lead who can give honest feedback.
• Diversity: Mix rural + urban, or different PMS platforms if DSO uses multiple.
• Payer mix: One site with heavy PPO focus; one with Medicaid/government. Tests Lassie's adaptability.

Configuration and Setup

1. Data extraction & cleansing (Days 1–3):

   • Export 6 months of claims from PMS; map to Lassie's data model.
   • Identify and correct duplicate claims, missing patient IDs, bad payer IDs.
   • Load into Lassie sandbox for testing.

2. Payer file setup (Days 2–4):

   • Input top 20 payers for pilot locations: names, claim submission methods, EOB formats, appeal rules.
   • Test claim submission to 2–3 payers using Lassie; verify formatting and rejection handling.

3. Workflow configuration (Days 4–6):

   • Define posting rules (e.g., "If EOB code = 'Processed as Primary,' post full allowed amount").
   • Set denial thresholds (flag for manual review if claim value > $500 or denial code = "Credentialing").
   • Assign payment follow-up escalation: auto-follow at Day 15, manual review Day 30, provider escalation Day 45.

4. User access & training (Days 5–6):

   • Provision 3–4 pilot staff: billing lead, assistant, operations manager.
   • Grant role-based access (e.g., "Posting Agent" can post payments but not override; "Manager" can approve denials and adjustments).

Training Approach

• Classroom + hands-on (4 hours total):
  • 1 hour: "What Lassie does" + workflow changes.
  • 2 hours: Sandbox drill-down (post payments, acknowledge denials, submit appeals).
  • 1 hour: Troubleshooting and escalation paths.
• Shadowing: Lassie success engineer shadows pilot staff for 2–3 days post-launch; captures process quirks and quick wins.
• Weekly check-ins: 30-min calls with pilot leads to address confusion and adjust workflows.

Scaled Rollout (Weeks 7-16)

Wave Planning

• Wave 1 (Weeks 7–9): 3–5 locations. Include 1 difficult site (high Medicaid %, outdated PMS) to surface integration issues early.
• Wave 2 (Weeks 10–12): 5–8 locations. By now, you have a repeatable launch playbook; reduce per-site setup time to 2 days.
• Wave 3 (Weeks 13–16): Remaining locations. Parallel training: train 2 locations while deploying to 3 others.

Key: Stagger by 2 weeks minimum to allow support team bandwidth and prevent system bottlenecks.

Change Management

• Champions program: Designate 1 "super-user" per location. Pay a small bonus (~$500–1K per quarter) for mentoring peers and reporting system bugs.
• Resistance handling: If a location's billing lead is skeptical, invite them to a pilot site visit to see results firsthand (DSO covers travel).
• Communication cadence:
  • Week 0 (pre-launch): Email summary of Lassie benefits + FAQ.
  • Days 1–5 (go-live): Daily 15-min huddles to troubleshoot.
  • Week 2+: Weekly async updates; office hours (optional) 2x/week.
• Celebrate wins: Share early metrics in DSO all-hands. Example: "Pilot locations reduced DSO by 3.2 days; Wave 1 on track for same."

Support Infrastructure

• Tier 1 (internal): Regional operations manager fields simple questions (posting rules, payer codes). Response: <2 hours.
• Tier 2 (Lassie support): Integrated system issues, claim submission errors, payer file updates. Response: <4 hours (business hours); 24-hour turnaround for critical blocking issues.
• Escalation SLA: If claim submission fails for >100 claims, page on-call engineer immediately.
• Knowledge base: Document each location's top 3 billing scenarios (e.g., "How to post a split payment between PPO and patient"). Share via internal wiki.

ROI Tracking