STRATUS — Implementation Playbook (DSO)

STRATUS AI Scribe Implementation Playbook for DSOs

Strategic Deployment for 15-50 Location Networks

Executive Summary

STRATUS is an AI clinical documentation platform that converts real-time voice during patient encounters into structured, clinically accurate dental notes—eliminating manual documentation burden for hygienists and dentists. DSOs benefit uniquely from this category because AI scribes drive three enterprise-level advantages: standardization of clinical documentation across geographically dispersed locations (critical for compliance, insurance verification, and multi-location continuity of care); data aggregation that enables population health insights, treatment trending, and benchmarking across the network; and labor optimization at scale, where 15-50 locations collectively save hundreds of hours monthly in administrative time, reallocating clinical staff to patient care and revenue-generating activities. From vendor selection to full deployment across all locations, expect a realistic timeline of 4-6 months (8-10 weeks for pilot wave, 6-8 weeks for rollout waves, 2-3 weeks for stabilization and optimization per location).

Pre-Implementation Checklist

Complete these items before any pilot location goes live:

Enterprise Technical Requirements

• ☐ Confirm cloud infrastructure compatibility (STRATUS system requirements: bandwidth, server specs, uptime SLAs)
• ☐ Map existing EHR integrations (Dentrix, Eaglesoft, Open Dental, or custom platforms) and identify API dependencies
• ☐ Audit network architecture at all 15-50 locations for minimum internet bandwidth (recommend ≥25 Mbps per operatory for simultaneous voice capture)
• ☐ Establish centralized IT support protocol for end-user troubleshooting (single point of contact vs. distributed IT)
• ☐ Test audio hardware compatibility (microphones, speakers, ambient noise handling) in 2-3 representative operatories

Data & Compliance Prerequisites

• ☐ Obtain signed Business Associate Agreement (BAA) with STRATUS covering HIPAA obligations and data handling
• ☐ Audit current documentation practices across locations to identify baseline compliance gaps (incomplete notes, missing data fields)
• ☐ Establish data governance policy: where AI-generated notes live, audit trails, correction protocols, and retention
• ☐ Confirm STRATUS SOC 2 Type II compliance, encryption standards (at-rest and in-transit), and third-party security audits

Stakeholder Alignment

• ☐ Secure executive buy-in from CDO/VP Operations and Finance (ROI approval)
• ☐ Identify and brief location-level clinical champions at each site (1-2 dentists/hygienists per location who advocate internally)
• ☐ Host all-staff webinar explaining tool benefits, addressing clinician concerns about autonomy and documentation oversight
• ☐ Establish governance committee: IT lead, clinical lead, 2-3 location managers, compliance officer (meets bi-weekly during rollout)

Baseline Metrics Capture

• ☐ Document current per-location metrics: average time spent on charting per patient, note completion rates, compliance deficiencies, patient encounter cycle time
• ☐ Establish baseline patient satisfaction scores (pre-implementation survey at pilot locations)
• ☐ Record staff time allocation: % clinical time vs. administrative time per role across all locations
• ☐ Track insurance claim submission lag and denials related to documentation quality

Location Readiness Assessment

Use this Location Readiness Score (LRS) to rank your 15-50 locations and sequence rollout. Score each location 1-5 on the five factors below; aim for a composite score of ≥3.5 for Wave 1 pilots.

Scoring Logic:

• Locations scoring 4.0-5.0 → Wave 1 pilot candidates (select 2-3 diverse by geography/practice type)
• Locations scoring 3.0-3.9 → Wave 2 (early majority, after 4-week pilot validation)
• Locations scoring <3.0 → Wave 3 (fast followers, post-Wave 2 success proof points)

Rollout Strategy

Wave Structure

Wave 1: Pilot Phase (2-3 locations, Weeks 1-8)

Selection Criteria: Choose geographically diverse locations with high readiness scores; include at least one high-volume, high-tech-adoption site and one mid-sized, "average" practice to stress-test across patient demographics. Ensure clinical champions are present and engaged.

• Week 1-2: On-site setup, hardware installation, EHR integration testing, staff training (2 sessions per location)
• Week 3-4: "Soft launch" with 50% of daily appointments using STRATUS; parallel paper note-taking continues
• Week 5-6: Full launch, collect daily feedback via brief Slack/email channel; daily check-ins with location manager and clinical champion
• Week 7-8: Stabilization; measure key metrics (documentation time, staff satisfaction, note quality); conduct qualitative interviews with clinicians

Go/No-Go Criteria for Wave 2:

• ✅ ≥90% of notes generated with minimal manual correction (<2 min/note)
• ✅ Staff satisfaction ≥3.5/5 on usability survey
• ✅ EHR integration zero-failure rate for 7 consecutive days
• ✅ Patient satisfaction neutral or positive (no decrease from baseline)
• ✅ Clinical champion confirms adoption by 80%+ of clinical staff

If no-go: Extend pilot by 2 weeks, address infrastructure or training gaps, and re-assess before Wave 2 launch.

Wave 2: Early Majority (next 8-12 locations, Weeks 9-16)

• Stagger onboarding: 4 locations per week to distribute IT/support load
• Deploy "pilot location mentors": send 1-2 Wave 1 clinicians to each Wave 2 location for 2-day peer training
• Reduce on-site vendor support (leverage internal champions + centralized helpdesk)
• Monitor metrics weekly at enterprise level; flag outliers for corrective action

Wave 3: Fast Followers (remaining locations, Weeks 17-24)

• Fully self-service deployment model: centralized training library, recorded demos, self-service onboarding
• Batch hardware/software provisioning; minimal on-site vendor presence
• Leverage Wave 1 & 2 documentation, FAQs, and SOP playbooks created by governance committee

Rollback Plan

If a location experiences critical failure:

1. Pause STRATUS usage for that location; revert to manual documentation immediately (no patient impact)
2. Isolate failure (IT debugging, clinical feedback collection)
3. Remediate (configuration fix, staff retraining, or extended pilot period)
4. Restart at earlier phase (soft launch) after 5 consecutive issue-free days
5. Document failure and resolution in governance committee for DSO-wide learning

Key Metrics to Track

Track these metrics per location AND in aggregate across the DSO throughout the 6-month rollout and ongoing:

Clinical & Operational Metrics

1. Documentation Time per Patient (minutes): Target: 30% reduction within 8 weeks of go-live

   • Measure: Average time from end of patient encounter to note completion
   • Aggregate: Benchmark across locations to identify laggards and best practices

2. Note Completion Rate (%): Target: 98%+ of encounters generate complete notes without manual rework

   • Measure: % of encounters where clinician did not need to edit/correct AI-generated note
   • Flag locations <95% for training intervention

3. Clinician Time Recovery (hours/week): Target: 8-12 hours per full-time clinician

   • Measure: Hours freed from administrative tasks, reallocated to patient care or revenue-generating activities
   • Aggregate by location; calculate DSO-wide labor cost savings

4. Documentation Compliance Rate (%): Target: Increase from baseline by 15-25% within 12 weeks

   • Measure: % of encounters where STRATUS-generated notes include all required clinical data fields (diagnosis, treatment, plan)
   • Compare against pre-implementation audit baseline

Financial & Patient Metrics

5. Insurance Claim Submission Lag (days): Target: Reduce from baseline by 20%

   • Measure: Days from encounter to claim submission (faster note completion → faster billing)
   • ROI multiplier: Calculate impact on DSO cash flow and AR aging

6. Claim Denial Rate Related to Documentation (%): Target: Reduce denials by 10-15%

   • Measure: % of denied claims attributed to incomplete/unclear documentation before/after STRATUS
   • Aggregate by location and payer; prioritize high-denial payers for root cause analysis

7. Staff Satisfaction & Retention: Target: ≥4.0/5 on post-launch NPS survey; turnover neutral or improved

   • Measure: Monthly pulse survey (usability, time savings, frustration) + turnover tracking per location
   • Red flag: Any location <3.0/5 satisfaction after 4-week ramp

8. Patient Satisfaction (no decline): Target: Maintain or improve baseline NPS

   • Measure: Post-encounter satisfaction surveys; specific question on "documentation experience"
   • Ensure STRATUS does not negatively impact patient perception of care quality

Common Pitfalls & How to Avoid Them

1. **Insufficient Staff Training & Change Management**

Pitfall: Rolling out STRATUS with minimal training; clinicians view it as "IT forcing another tool" rather than a time-saving aid.

How to Avoid:

• Invest 4-6 hours per clinician in structured training (hands-on, peer-led, in their operatories)
• Create compelling "before/after" case studies from Wave 1 to show time savings + job satisfaction improvement
• Assign local champions to answer questions daily for first 2 weeks post-launch
• Frame adoption as clinician empowerment (reclaim time from charting, focus on patients), not surveillance

2. **EHR Integration Misalignment**

Pitfall: STRATUS generates notes that don't cleanly flow into your existing EHR system; notes get generated but require manual re-entry or formatting fixes.

How to Avoid:

• Conduct pre-pilot deep-dive with EHR vendor and STRATUS on API integration specifics
• Run 1-week parallel testing at pilot location: STRATUS notes vs. manual notes side-by-side to validate EHR data capture
• Establish clear data ownership: who corrects formatting errors, where do exceptions live, escalation path for failed integrations
• If custom EHR: allocate IT resources for custom API work 4 weeks before Wave 1 launch

3. **Inconsistent Metrics Tracking Across Locations**

Pitfall: Different locations measure "documentation time" or "note completion rate" differently; DSO-level dashboard becomes unreliable, hampering decisions.

How to Avoid:

• Define metrics in writing before Wave 1 launch (exactly how to measure, data sources, submission cadence)
• Deploy centralized Excel/Tableau dashboard where location managers submit weekly metrics by standard template
• Audit baseline metrics at all locations 2 weeks pre-pilot (create apples-to-apples starting point)
• Governance committee validates data quality monthly; flag outliers for verification

4. **Pilot Location Over-Commitment**

Pitfall: Pilot locations are asked to "do everything perfectly" while managing normal patient flow; staff burnout, feedback quality suffers, and Wave 2 decision is based on a distorted success signal.

How to Avoid:

• Explicitly scope pilot: "We will focus on documenting patient encounters accurately and measuring time savings; new reporting features come post-Wave 1"
• Reduce administrative burden during pilot (coverage for meetings, reduced meeting load for champions)
• Limit pilot to single clinician per location initially (2-3 days), then expand to full staff after 5-day success checkpoint
• Set realistic expectations: "We expect 20% of encounters to need minor corrections in Week 1-2; this is normal"

5. **Network Bandwidth & Uptime Underestimation**

Pitfall: Wave 1 launch hits unexpected internet outages or latency; clinicians cannot use STRATUS, revert to manual notes, and lose faith in the rollout.

How to Avoid:

• Conduct pre-launch network stress test: simulate simultaneous voice capture from 10+ operatories at each pilot location
• Upgrade internet to 25+ Mbps minimum at all rollout locations 2 weeks before their launch (not during)
• Establish failover protocol: if STRATUS unavailable, automatic switch to manual documentation (no patient impact)
• ISP SLA requirement: 99.5%+ uptime; DSO covers cost if location's existing ISP cannot meet it

6. **Delayed ROI Realization Due to Scope Creep**

Pitfall: Post-Wave 1, stakeholders request added features (integration with practice management system, specialty-specific templates, AI-driven patient communication) that consume IT resources and delay rollout.

How to Avoid:

• Lock "MVP" (minimum viable product) scope before Wave 1 launch: STRATUS voice capture → EHR note creation, end of story
• Route all feature requests to a formal backlog reviewed quarterly by governance committee; require business case + DSO-wide prioritization
• Communicate to all stakeholders: "Phase 1 is core documentation; Phase 2 (months 7-12) explores advanced analytics and workflow optimization"
• Track scope creep metrics: % of meetings discussing out-of-scope requests; flag for stakeholder re-alignment if >20%

Cost/ROI Framework

Enterprise Cost Model

Per-Location Implementation Costs:

• STRATUS software license: ~$2,000-5,000/month per location (varies by patient volume; typically $0.80-1.50 per encounter)
• Hardware (microphones, audio equipment, minor IT upgrades): ~$1,500-3,000 per location (one-time)
• Onsite training & integration (vendor): ~$2,000-4,000 per location (one-time)
• Total per-location, Year 1: ~$35,000-65,000 (software + hardware + implementation)

Enterprise Aggregate (25-location DSO example):

• Year 1 investment: ~$1.1M-1.6M (assuming 25 locations, phased rollout allows 6-month average cost)
• Year 2+ (fully deployed): ~$750K-$1.2M annually (software license + minimal ongoing support)

Licensing Optimization:

• Negotiate volume discount with STRATUS at 15+ location threshold (typically 10-15% off per-location rate)
• Consider enterprise license model if available: flat fee for DSO + per-encounter overage vs. per-location licensing

ROI Calculation Framework

Primary ROI Drivers (per location):

1. Labor Savings (Largest Impact)

   • Clinician time recovery: 8-12 hours/week per FTE × avg. labor cost ($65/hour) = $2,600-$3,900/week per location
   • For 25-location DSO: ~$3.25M-$4.9M annually in recovered labor (assuming 2 clinical FTEs per location)
   • Conservative assumption: 40% utilization of recovered time on revenue-generating activities (cleanings, exams, treatment planning)

2. Insurance Claim Processing & Collections Improvement

   • Claim submission lag reduced 20% → improved cash flow, faster AR aging
   • Denials related to documentation reduced 10-15% → assume 2% of current denial volume × average claim value ($