Overjet
Implementation PlaybookDSO Β· Group Practice

Overjet

Step-by-step implementation guide β€” pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.

Overjet β€” Implementation Playbook (DSO)

Overjet Implementation Playbook for DSOs

Diagnostic Imaging AI: A Strategic Deployment Guide


1. Executive Summary

What Overjet Does

Overjet is an FDA-cleared dental AI platform that analyzes radiographic images in real-time, automatically detecting and quantifying dental conditions including caries, bone loss, calculus, and existing restorations. The platform overlays clinical findings directly onto X-rays with color-coded annotations and numerical measurements, providing objective, consistent diagnostic support across every provider and every location.

Why DSOs Specifically Benefit from Diagnostic Imaging AI

DSOs operate at a scale where clinical variability becomes a measurable business problem. When 50 providers across 30 locations interpret radiographs differently, you get inconsistent treatment recommendations, unpredictable case acceptance, and insurance claim denials that drain revenue cycle efficiency. Overjet addresses this by creating a standardized diagnostic baseline across your entire network.

Scale advantages unique to DSOs include:

  • Aggregate data intelligence: Cross-location analytics reveal which offices under-diagnose, which providers over-treat, and where training interventions will produce the highest ROI
  • Standardized documentation: Every diagnosis comes with AI-generated measurements and findings, creating audit-ready records that reduce malpractice exposure and accelerate insurance adjudication
  • New provider ramp-up: Associates joining any location inherit the same diagnostic support, reducing calibration time and quality variance
  • Payer negotiation leverage: Objective, AI-documented clinical findings strengthen your position in claims disputes and network contract negotiations

Expected Timeline: Decision to Full Deployment

Phase Timeline Milestone
Pre-implementation & planning Weeks 1–2 Infrastructure validated, stakeholders aligned, baselines captured
Wave 1 pilot (2–3 locations) Weeks 3–6 Pilot sites live, initial data collected
Wave 1 evaluation & refinement Week 7 Go/no-go decision for Wave 2
Wave 2 rollout (5–8 locations) Weeks 8–12 Scaled deployment, process refinement
Wave 3+ (remaining locations) Weeks 13–20 Full network deployment
Post-launch optimization Weeks 21–28 ROI validation, workflow maturation

Total timeline for 30-location DSO: 5–7 months from contract signature to full deployment

For larger portfolios (40–50 locations), add 4–6 weeks and consider a Wave 4.


2. Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Hardware Requirements per Location

☐ Workstations with minimum specs: Windows 10/11, 8GB RAM, modern multi-core processor
☐ Monitor resolution minimum 1920x1080 (dual monitors recommended for clinical workstations)
☐ Digital radiography sensors (any major brand compatible; verify specific models with Overjet)
☐ πŸ”΅ Confirm imaging hardware compatibility list with Overjet technical team

Network Requirements

☐ Minimum 25 Mbps download/10 Mbps upload per location (50/20 recommended)
☐ Stable, low-latency connection (cloud-based processing requires consistent connectivity)
☐ ⚠️ Firewall configuration to whitelist Overjet endpoints (common failure point for enterprise networks)
☐ VPN compatibility verification if locations route through central network

Software Requirements

☐ Practice Management System version compatibility check (see Integration section)
☐ Imaging software compatibility: Dexis, Dentrix Image, Patterson Imaging, XDR, Apteryx, others
☐ Browser requirements for Overjet web interface: Chrome (recommended), Edge, Firefox
☐ πŸ”΅ Request Overjet's technical requirements document for your specific PMS/imaging stack

Time estimate: 3–5 hours for IT to complete technical audit across representative locations


Enterprise-Level Requirements

Network Standards Across Locations

☐ 🟣 Decide: Centralized hosting vs. location-level cloud connection

  • Recommendation: Location-level cloud connection with centralized SSO authentication
  • Centralized routing adds latency and creates single points of failure ☐ Document current network topology across all locations
    ☐ Identify locations with known connectivity issues (prioritize infrastructure upgrades before rollout)

Identity & Access Management

☐ SSO provider identification (Okta, Azure AD, Google Workspace)
☐ πŸ”΅ Confirm Overjet SSO integration compatibility (SAML 2.0 supported)
☐ Define user role hierarchy: Super Admin (central), Location Admin, Provider, Staff
☐ Centralized credentialing workflow: how new providers get Overjet access

Data Governance

☐ 🟣 Data residency requirements confirmed (Overjet uses AWS; confirm region compliance)
☐ Data retention policy alignment with organizational standards
☐ Audit log access for compliance team

Time estimate: 4–6 hours for IT leadership to document enterprise requirements


Vendor Onboarding Steps

☐ πŸ”΅ Schedule kickoff call with Overjet implementation team (Week 1, Day 1–2)
☐ Identify and document key Overjet contacts:

  • Implementation Project Manager: _______________
  • Technical Integration Specialist: _______________
  • Customer Success Manager: _______________
  • Support escalation contact: _______________ ☐ πŸ”΅ Obtain implementation timeline from Overjet; reconcile with internal timeline
    ☐ πŸ”΅ Request access to Overjet Partner Portal / documentation resources
    ☐ Establish communication cadence: weekly implementation calls recommended
    ☐ πŸ”΅ Confirm training resource availability and schedule vendor-led training dates

Time estimate: 2–3 hours for initial vendor coordination


Data/Access Prerequisites

☐ Compile list of all PMS and imaging software login credentials (admin level)
☐ API key generation for PMS integration (if API-based integration)
☐ Historical imaging archive access (if importing historical X-rays for baseline)
☐ πŸ”΅ Provide Overjet with test environment access for integration development
☐ HIPAA-compliant secure file sharing method established for any data exchange

Time estimate: 2–4 hours to compile access requirements


Stakeholder Alignment Map

🟣 Board/Investors

  • What they need: ROI projections, competitive positioning, risk assessment
  • When to inform: Pre-decision presentation; quarterly updates post-launch
  • Approval required for: Capital expenditure, multi-year contract

🟣 C-Suite (CEO, CDO, CFO, COO)

  • CEO: Strategic alignment, market differentiation narrative
  • CDO (Chief Dental Officer): Clinical validity, standard of care implications, provider buy-in strategy
  • CFO: ROI model, contract terms, budget allocation
  • COO (you): Implementation ownership, operational integration
  • When to inform: Decision phase through full deployment
  • Approval required for: Go/no-go at each wave, resource allocation

Regional Managers

  • What they need: Location-specific rollout timelines, support expectations, escalation paths
  • When to inform: 2 weeks before their region enters active rollout
  • Role in implementation: Champion coordination, daily check-ins during go-live week

Location-Level Office Managers

  • What they need: Detailed go-live runbook, training schedules, patient communication scripts
  • When to inform: 3–4 weeks before their location go-live
  • Role in implementation: Local logistics, staff coordination, first-line troubleshooting

Providers (Dentists, Hygienists)

  • What they need: Clinical workflow changes, AI interpretation guidance, override protocols
  • When to inform: 2–3 weeks before their location go-live
  • Role in implementation: Clinical feedback, adoption leadership

Time estimate: 2–3 hours to complete stakeholder mapping and communication plan


Baseline Metrics to Capture

⚠️ Critical: Capture these metrics BEFORE go-live. Without baselines, ROI measurement is impossible.

Clinical Metrics (per location, then aggregated)

☐ Average number of findings per FMX/BWX set (provider-documented)
☐ Caries detection rate per 100 patients
☐ Periodontal disease documentation rate
☐ Time from image capture to treatment presentation (if measurable)

Operational Metrics

☐ Case acceptance rate (treatment presented vs. treatment accepted)
☐ Average production per patient visit
☐ New patient conversion rate (exam to treatment plan acceptance)

Revenue Cycle Metrics

☐ Claim denial rate (overall and by procedure code)
☐ Average days to claim payment
☐ Percentage of claims requiring additional documentation
☐ Narrative/documentation rework rate

Provider Variance Metrics

☐ Standard deviation in findings per provider (diagnosis consistency)
☐ Treatment plan value variance across providers seeing similar patient mix

Standardizing Measurement Across Locations

☐ 🟣 Define standard reporting period (recommend: trailing 90 days pre-implementation)
☐ Create standardized data pull template for all locations
☐ ⚠️ Verify PMS report configurations are identical across locations (common issue: custom report modifications)
☐ Centralize baseline data in single dashboard/spreadsheet for cross-location comparison
☐ Assign data collection owner per region to ensure consistency

Time estimate: 8–12 hours to collect and standardize baseline metrics across all locations


3. Location Readiness Assessment

Scoring Framework

Score each location on the following factors (1 = Low readiness, 5 = High readiness):

Factor 1: IT Infrastructure Maturity

Score Criteria
1 Network frequently drops, hardware >7 years old, unsupported PMS version
2 Intermittent connectivity issues, hardware 5–7 years old, older PMS version
3 Generally stable network, hardware 3–5 years old, current PMS version
4 Reliable network with minor issues, hardware <3 years old, current PMS
5 Enterprise-grade network, modern hardware, latest PMS version, IT support available

Data to collect: Last 90-day network uptime, hardware inventory, PMS version

Factor 2: Staff Tenure and Adaptability

Score Criteria
1 >40% annual turnover, history of tech adoption resistance, no recent training
2 30–40% turnover, mixed reception to past tech changes, minimal training
3 20–30% turnover, neutral tech reception, standard training compliance
4 10–20% turnover, positive response to tech, proactive training participation
5 <10% turnover, staff actively requests new tech, training culture established

Data to collect: Turnover rate trailing 12 months, training completion rates, past tech adoption feedback

Factor 3: Patient Volume

Score Criteria
1 <150 patients/month (low impact, but useful for controlled pilot)
2 150–250 patients/month
3 250–400 patients/month (moderate volume, balanced risk/impact)
4 400–600 patients/month (high impact, requires strong support)
5 >600 patients/month (highest impact but highest riskβ€”reserve for later waves)

Note: For Wave 1 pilots, Score 3 is optimal. Score 5 locations should wait for Wave 2+.

Data to collect: Average monthly patient visits trailing 6 months

Factor 4: Existing Tech Stack Compatibility

Score Criteria
1 PMS/imaging system not on Overjet compatibility list, major integration work required
2 Compatible but requires significant configuration, multiple workarounds expected
3 Compatible with standard integration, minor configuration needed
4 Fully compatible, integration template available from Overjet
5 Fully compatible, same stack as other locations (no unique integration work)

Data to collect: PMS name/version, imaging software name/version, any custom integrations

Factor 5: Local Champion Availability

Score Criteria
1 No identified champion, leadership vacuum at location
2 Possible champion identified but lacks time/authority
3 Champion identified, willing but needs development
4 Strong champion (office manager or provider), respected by peers, has capacity
5 Exceptional champion with tech background, leadership credibility, and dedicated time

Data to collect: Regional manager nomination, interview with proposed champion


Composite Readiness Score Calculation

Formula: (IT Γ— 1.5) + (Staff Γ— 1.5) + (Volume Γ— 1.0) + (Tech Stack Γ— 1.5) + (Champion Γ— 1.5) = Composite Score

Maximum possible score: 35 points

Composite Score Readiness Tier Recommended Wave
28–35 Tier 1: High Readiness Wave 1 (pilot candidate)
21–27 Tier 2: Moderate Readiness Wave 2
14–20 Tier 3: Low Readiness Wave 3 (or remediation required)
<14 Tier 4: Not Ready Defer until remediation complete

Wave 1 Selection (2–3 locations)

Select from Tier 1 locations with these additional criteria: ☐ At least one location in each major geographic region (tests regional support capacity)
☐ Mix of practice types if your portfolio varies (GP-heavy, specialty, etc.)
☐ Avoid flagship/showcase locations (protect brand if issues arise)
☐ Champion has direct communication line to central implementation team

Wave 2 Selection (5–8 locations)

☐ All remaining Tier 1 locations
☐ Tier 2 locations with Volume Score β‰₯ 3 (maximize impact)
☐ Prioritize locations where Wave 1 champion can mentor new champions

Wave 3 Selection (remaining locations)

☐ Remaining Tier 2 locations
☐ Tier 3 locations that have completed remediation
☐ Consider pairing Tier 3 locations with experienced regional champions

Locations Requiring Remediation Before Any Wave

☐ Tier 4 locations: create remediation plan with timeline
☐ Assign remediation owner (regional manager or IT)
☐ Re-score after remediation; do not include in any wave until score β‰₯ 18

Time estimate: 4–6 hours to complete readiness scoring for all locations; 2 hours for sequence planning


4. Rollout Strategy

Wave Structure Overview

Wave # Locations Timeline Purpose
Wave 1 (Pilot) 2–3 Weeks 3–6 Validate integration, refine training, identify failure points
Evaluation β€” Week 7 Capture learnings, update playbook, go/no-go decision
Wave 2 5–8 Weeks 8–12 Scale deployment, stress-test support model
Wave 3 Remaining Weeks 13–20 Full deployment with mature processes

Buffer between waves: Minimum 1 week; extend to 2 weeks if significant issues discovered


Wave 1 Pilot Location Selection Criteria

☐ Composite readiness score β‰₯ 28
☐ Patient volume in "Goldilocks zone" (250–400/month)β€”enough for meaningful data, not so much that issues cause major disruption
☐ Champion availability: minimum 4 hours/week dedicated time during pilot
☐ Geographic diversity if DSO spans multiple regions (tests remote support capability)
☐ 🟣 Not your highest-revenue or most visible location (protect downside)
☐ Provider mix representative of broader portfolio (at least one associate, one experienced provider)
☐ Office manager tenure >1 year (institutional knowledge for troubleshooting)

Recommended: Conduct brief champion interviews before final selection; enthusiasm matters.


Detailed Wave 1 Timeline (Weeks 3–6)

Week 3: Integration & Configuration

  • Day 1–2: πŸ”΅ Overjet technical team configures integration with PMS/imaging
  • Day 3: Internal IT validates connectivity and data flow
  • Day 4–5: Test environment validation; pilot providers access system
  • ⚠️ Common issue: Firewall blocks during initial configuration

Week 4: Training & Shadow Period

  • Day 1–2: πŸ”΅ Vendor-led training for pilot location champions
  • Day 3–4: Champions shadow-train remaining staff (using train-the-trainer materials)
  • Day 5: Dry run dayβ€”process X-rays through system without using clinically

Week 5: Soft Launch

  • All appointments use Overjet; providers retain discretion on clinical decisions
  • Daily 15-minute check-in calls: champion β†’ regional manager β†’ central team
  • Real-time issue logging in shared tracker

Week 6: Stabilization & Data Collection

  • Continue daily check-ins (can reduce to 10 minutes if stable)
  • Mid-week: Initial metrics review against baseline
  • End of week: Champion debriefs with implementation team

Go/No-Go Criteria for Wave Advancement

Minimum Criteria to Advance to Wave 2

Criterion Threshold Measurement
System uptime β‰₯99% during pilot Overjet dashboard
Integration stability <3 critical errors per week by Week 6 Error logs
Training completion 100% of pilot staff trained Training tracker
Provider adoption β‰₯80% of radiographs processed through Overjet System analytics
Champion confidence Self-reported 4/5 on readiness to support peers Champion survey
Patient impact Zero patient-reported issues Office manager feedback

🟣 Go/No-Go Decision Meeting (Week 7)

Attendees: CDO, COO, Regional Managers, Implementation Lead, Overjet CSM Agenda:

  1. Pilot metrics review vs. thresholds
  2. Issue log review and resolution status
  3. Champion feedback summary
  4. Wave 2 timeline and location confirmation
  5. Decision: Go / Go with modifications / Pause

Wave 2 Timeline (Weeks 8–12)

Week 8: Preparation

  • Wave 1 champions brief Wave 2 champions (cross-location peer call)
  • πŸ”΅ Overjet configures Wave 2 location integrations
  • Training materials updated based on Wave 1 feedback

Weeks 9–10: Training & Configuration

  • Staggered go-live: 2–3 locations per week to manage support capacity
  • Wave 1 champions available for peer support calls

Weeks 11–12: Stabilization

  • Daily check-ins first week; transition to weekly by end of Week 12
  • Issue patterns documented for Wave 3 proactive mitigation

Wave 3+ Scaling Approach

By Wave 3, you should have:

  • Mature training materials refined through two iterations
  • Experienced champions who can mentor remotely
  • Standardized troubleshooting runbook
  • Predictable timeline per location

Wave 3 approach:

  • Deploy in batches of 8–10 locations per week
  • Champions onboarded via recorded training + live Q&A
  • Central support team fully owns escalation (regional managers in monitoring role)

Rollback Plan

Triggers for Rollback

  • System downtime >4 hours during patient care hours
  • Data integrity issue (e.g., X-rays not saving, patient data mismatch)
  • Provider safety concern (AI output creates clinical confusion)
  • 50% of providers request return to previous workflow

Rollback Procedure (per location)

☐ πŸ”΅ Notify Overjet support immediately; document issue
☐ Disable Overjet integration at PMS level (do not uninstall)
☐ Revert to previous imaging workflow
☐ Communicate to staff: "We are pausing the new system while we resolve [specific issue]"
☐ Document all in-flight patient records for reconciliation
☐ Schedule root cause analysis within 48 hours

Rollback Impact Isolation

  • Rollback at one location does NOT affect other locations
  • If rollback required at >50% of wave locations, pause entire wave
  • 🟣 Executive communication required within 24 hours of wave-level rollback

Time estimate for rollback: 2–4 hours to revert workflow; 24–48 hours for root cause analysis


5. Configuration & Integration (Weeks 2–3)

Practice Management System Integration

Dentrix Integration

☐ Verify Dentrix version β‰₯ G7.4 (earlier versions may require upgrade)
☐ πŸ”΅ Request Overjet Dentrix integration guide
☐ Enable HL7 or API bridge depending on version
☐ Configure patient data sync: demographics, appointment info, provider assignments
☐ ⚠️ Dentrix Ascend (cloud) requires different integration path than Dentrix G-series
☐ Test patient record matching between Dentrix and Overjet
☐ Verify image association: confirm X-rays appear under correct patient/appointment

Estimated integration time: 4–6 hours per location (less with template after Wave 1)

Eaglesoft Integration

☐ Verify Eaglesoft version β‰₯ 21.0
☐ πŸ”΅ Request Overjet Eaglesoft integration credentials and guide
☐ Patterson IT coordination may be required; initiate contact early
☐ Configure database connectivity (typically SQL-based)
☐ ⚠️ Eaglesoft imaging module version must match; update if necessary
☐ Test bidirectional data flow: patient data in, findings documented out

Estimated integration time: 5–7 hours per location

Open Dental Integration

☐ Verify Open Dental version β‰₯ 22.1
☐ Enable API access in Open Dental (Service Manager > API Keys)
☐ πŸ”΅ Provide API credentials to Overjet technical team
☐ Configure image storage path access
☐ Test FHIR/API data exchange
☐ Open Dental's open architecture typically allows faster integration

Estimated integration time: 3–5 hours per location

Other PMS Systems (Curve, Carestack, tab32, etc.)

☐ πŸ”΅ Confirm integration availability with Overjet (not all systems supported)
☐ Request specific integration documentation
☐ Plan for extended timeline if custom integration required


Imaging System Integration

Step-by-Step Process

  1. ☐ Document current imaging software at each location (brand, version)
  2. ☐ πŸ”΅ Confirm Overjet compatibility (Dexis, XDR, Apteryx, Patterson, etc.)
  3. ☐ Configure image export path or API connection
  4. ☐ Set image format standards (DICOM preferred; JPEG/PNG acceptable)
  5. ☐ Test image capture-to-Overjet workflow:
    • Capture test X-ray
    • Verify automatic upload to Overjet
    • Confirm AI analysis appears within 30 seconds
    • Verify annotation overlay displays correctly
  6. ☐ Test image storage: confirm original images preserved (Overjet analyzes copies)
  7. ☐ ⚠️ Verify sensor compatibility if using older/less common sensors

Estimated integration time: 2–3 hours per location


Test Environment Setup

☐ πŸ”΅ Request Overjet sandbox/test instance
☐ Configure one representative PMS/imaging stack in test environment
☐ Load anonymized patient data (or use synthetic data set)
☐ Conduct integration testing in sandbox before any production deployment

Test Environment Validation Checklist

☐ Patient demographic sync: verified
☐ Image upload: verified (<10 seconds for standard BWX)
☐ AI analysis return: verified (<30 seconds)
☐ Annotation display: verified (color-coded overlays visible)
☐ Findings documentation to PMS: verified (if bidirectional)
☐ User authentication (SSO): verified
☐ Role-based access: verified (provider vs. staff views)
☐ Report generation: verified
☐ Stress test: process 50+ images in sequence, monitor for degradation


Data Migration / Historical Imaging Ingestion

🟣 Decision Required: Import Historical Images?

Pros of importing:

  • Establish baseline AI analysis across patient population
  • Enable comparison of current vs. historical radiographs
  • Identify previously undiagnosed conditions

Cons of importing:

  • Significant time and cost (especially for large archives)
  • Historical images may lack metadata for proper association
  • Potential for overwhelming providers with retroactive findings

Recommendation: Do NOT import historical images in Wave 1. Evaluate as post-launch optimization.

If proceeding with historical import: ☐ Define date range for import (recommend: trailing 2 years maximum)
☐ Export images in DICOM format with patient identifiers
☐ πŸ”΅ Coordinate batch upload with Overjet (off-hours to avoid system load)
☐ Validate patient record matching post-import
☐ Create workflow for triaging retroactive findings


Security and HIPAA Compliance Verification

Enterprise-Level Checklist

☐ πŸ”΅ Execute Business Associate Agreement (BAA) with Overjet
☐ 🟣 Legal review of BAA terms
☐ Confirm Overjet SOC 2 Type II certification current
☐ Review Overjet data handling: encryption at rest (AES-256) and in transit (TLS 1.2+)
☐ Verify data center location meets organizational requirements (US-based AWS)
☐ Document data retention and deletion policies
☐ Configure access controls:

  • Minimum necessary access by role
  • Provider-level audit trails
  • Admin access limited to designated personnel ☐ Verify automatic session timeout (recommend: 15 minutes inactivity)
    ☐ Test audit log access for compliance team
    ☐ ⚠️ Confirm patient data is not used for AI training without explicit consent (Overjet policy verification)
    ☐ Document HIPAA compliance verification in implementation records

Standardized vs. Location-Specific Configuration

Standardize Centrally (Template Settings)

Setting Recommended Standard
User role definitions Provider, Hygienist, Front Desk, Admin, Super Admin
Finding categories enabled All clinical categories (caries, bone loss, calculus, etc.)
Alert thresholds Default sensitivity settings
Report templates Standard organizational template
Audit log retention 7 years (HIPAA requirement)
SSO configuration Organization-wide settings
Data export permissions Restricted to Admin/Super Admin

Allow Location-Level Customization

Setting Customization Rationale
Provider preferences (overlay colors, default views) Personal workflow efficiency
Notification settings Location-specific communication patterns
Appointment integration settings PMS-dependent configuration
Specialty-specific finding emphasis Perio-focused offices may weight differently
Local admin contact Location-specific support escalation

Time estimate: 2–3 hours to define configuration template; 30 minutes per location to apply


6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

☐ Currently employed at location (not floating staff)
☐ Tenure β‰₯ 1 year at this location
☐ Role: Office Manager, Lead Hygienist, or tech-forward Provider
☐ Demonstrated tech competence (comfortable with PMS, imaging software)
☐ Respected by peers (training will require behavior change leadership)
☐ Capacity: minimum 4 hours/week during rollout phase
☐ Communication skills: able to explain technical concepts clearly
☐ Regional manager endorsement

Champion Responsibilities

  • Complete certification training (vendor-led)
  • Deliver role-specific training to all location staff
  • Serve as first-line support during go-live week
  • Escalate unresolved issues to regional manager/central team
  • Collect staff feedback and submit weekly during rollout
  • Maintain training records for compliance

Champion Certification Process

  1. ☐ πŸ”΅ Attend vendor-led 90-minute champion certification session
  2. ☐ Complete online knowledge assessment (β‰₯85% pass threshold)
  3. ☐ Deliver mock training session observed by regional manager or central team
  4. ☐ Receive certification confirmation and training materials access
  5. ☐ Join champion community channel (Slack/Teams) for peer support

Time estimate: 4–6 hours total champion certification time


Standardized Training Materials

Centrally Created (Implementation Team)

☐ Overjet Overview Deck (10 slides): What it is, why we're implementing, what changes
☐ Role-specific training modules (see below)
☐ Day 1 Cheat Sheets (one-pagers per role)
☐ FAQ document (updated from Wave 1 questions)
☐ Video library: system walkthrough recordings
☐ Assessment quizzes per role

Champion-Customized Locally

☐ Location-specific workflow screenshots (their PMS screens)
☐ Team scheduling for training sessions
☐ Examples using anonymized local patient cases
☐ Q&A based on known staff concerns


Role-Specific Training Outlines

Dentists/Providers

Training Time: 60 minutes (live or recorded) + 30 minutes hands-on practice

Content:

  1. System overview and clinical validation (FDA clearance, evidence base)
  2. Workflow integration: where Overjet appears in the exam process
  3. Reading AI outputs:
    • Color coding explanation (red = caries, blue = bone loss, etc.)
    • Quantitative measurements interpretation
    • Confidence indicators
  4. When AI aligns vs. when to override
    • AI supports, not replaces, clinical judgment
    • Documentation when overriding AI recommendation
  5. Patient communication: using visual aids in treatment presentation
  6. Hands-on: process 5 sample cases with guidance

Common Resistance Points:

Objection Response
"I don't need AI to diagnose" "This is decision support, not decision replacement. You maintain full clinical authority."
"What if the AI is wrong?" "AI is one data point. Your expertise integrates all factors. We have clear override documentation protocols."
"This will slow me down" "Initial learning curve is 1–2 weeks. Providers report faster treatment presentations after adaptation."

Provider Day 1 Cheat Sheet:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ OVERJET PROVIDER QUICK REFERENCE                    β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ 1. Open patient chart β†’ Imaging tab                 β”‚
β”‚ 2. Capture X-ray as normal                          β”‚
β”‚ 3. AI overlay appears in ~30 seconds                β”‚
β”‚ 4. Review findings:                                 β”‚
β”‚    πŸ”΄ Red = Caries (click for depth estimate)       β”‚
β”‚    πŸ”΅ Blue = Bone loss (% measurement shown)        β”‚
β”‚    🟑 Yellow = Calculus                             β”‚
β”‚ 5. Click finding for detail; incorporate in Tx plan β”‚
β”‚ 6. To override: document clinical rationale in notesβ”‚
β”‚ 7. Use AI visuals in patient presentation           β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ STUCK? Contact: [Champion Name] x[ext] or Slack     β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Hygienists

Training Time: 45 minutes

Content:

  1. Overview: what the system does and why
  2. Hygienist-specific touchpoints:
    • Viewing AI findings before prophy/perio appointments
    • Calculus detection relevance to SRP recommendations
    • Bone loss measurements for perio charting
  3. Patient communication: explaining what the colored overlays mean
  4. Escalation: when to flag findings for provider review

Hygienist Day 1 Cheat Sheet:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ OVERJET HYGIENIST QUICK REFERENCE                   β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Before appointment:                                 β”‚
β”‚ β€’ Review patient's AI findings in imaging tab       β”‚
β”‚ β€’ Note any calculus (yellow) or bone loss (blue)    β”‚
β”‚                                                     β”‚
β”‚ During appointment:                                 β”‚
β”‚ β€’ Reference AI visuals when discussing perio status β”‚
β”‚ β€’ "The analysis helps us see areas of concern"      β”‚
β”‚                                                     β”‚
β”‚ After appointment:                                  β”‚
β”‚ β€’ Flag new findings for doctor review if needed     β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ QUESTIONS? Ask [Champion Name]                      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Front Desk / Office Manager

Training Time: 30 minutes

Content:

  1. High-level overview (no clinical detail needed)
  2. Administrative functions:
    • User account management (if admin)
    • Report access and generation
    • Basic troubleshooting: "Have you tried refreshing?"
  3. Patient communication:
    • Responding to questions about "the computer analyzing X-rays"
    • Script for patient curiosity or concern
  4. Training record maintenance (compliance tracking)

Front Desk Day 1 Cheat Sheet:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ OVERJET FRONT DESK QUICK REFERENCE                  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ What to tell patients who ask:                      β”‚
β”‚ "We use advanced imaging technology that helps our  β”‚
β”‚ doctors identify potential issues more accurately.  β”‚
β”‚ Your X-rays are still reviewed by your dentist."    β”‚
β”‚                                                     β”‚
β”‚ If system isn't working:                            β”‚
β”‚ 1. Refresh browser                                  β”‚
β”‚ 2. Check internet connection                        β”‚
β”‚ 3. Contact [Champion Name]                          β”‚
β”‚ 4. Document issue in log                            β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Training records kept in: [Location]                β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Billing/Insurance Staff

Training Time: 30 minutes

Content:

  1. How AI findings enhance documentation:
    • Objective measurements support medical necessity
    • Visual evidence for claims attachments
  2. Generating reports for claims support
  3. Expected impact on claim denials (reduction in narrative requests)
  4. No changes to coding (codes are procedure-based, not diagnostic-based)

Billing Day 1 Cheat Sheet:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ OVERJET BILLING QUICK REFERENCE                     β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ For claims requiring documentation:                 β”‚
β”‚ 1. Access patient imaging in Overjet                β”‚
β”‚ 2. Generate AI Analysis Report (Reports > Patient)  β”‚
β”‚ 3. Attach to claim as supporting documentation      β”‚
β”‚                                                     β”‚
β”‚ Key benefit: AI measurements provide objective      β”‚
β”‚ evidence of diagnosis β†’ fewer narrative requests    β”‚
β”‚                                                     β”‚
β”‚ No CDT code changes required                        β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ QUESTIONS? Ask [Champion Name] or billing lead      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Training Completion Tracking

Requirements

☐ 100% of staff trained BEFORE location go-live (no exceptions)
☐ Training completion logged in central system (LMS, spreadsheet, or Overjet dashboard)
☐ Champions verify completion daily during training week
☐ Regional manager confirms location-wide completion before go-live authorization

Tracking Template

Location Staff Name Role Training Completed Date Quiz Score Champion Sign-off
Example Jane Smith Provider βœ“ 3/15/24 92% JS

New Hire Training Protocol

☐ All new hires complete Overjet training within first 2 weeks of employment
☐ Champion delivers onboarding training or assigns recorded module
☐ Quarterly refresher available for all staff (optional but tracked)
☐ Annual recertification required for champions


7. Change Management

Executive Sponsor Communication Plan

🟣 Board/Investor Updates

Frequency: Quarterly during implementation; annually post-stabilization

Format: 1-page executive brief + 5-minute verbal update

Content Template:

OVERJET AI IMPLEMENTATION UPDATE - [Quarter/Year]

DEPLOYMENT STATUS: [X] of [Y] locations live (X%)

KEY METRICS:
β€’ Case acceptance rate: [X]% (vs. [Y]% baseline, Ξ” = [Z]%)
β€’ Claim documentation efficiency: [metric]
β€’ Provider adoption rate: [X]%

INVESTMENT STATUS:
β€’ Budget spent: $[X] of $[Y] ([Z]%)
β€’ On track / Over / Under

NEXT QUARTER PRIORITIES:
1. [Priority]
2. [Priority]

RISK STATUS: [Green/Yellow/Red]
[If Yellow/Red: Brief explanation and mitigation]

C-Suite Communication

CDO Updates:

  • Weekly during active waves
  • Clinical outcome focus: diagnostic accuracy, provider feedback, standard of care implications
  • Owns clinical escalation decisions

CFO Updates:

  • Bi-weekly during implementation; monthly post-launch
  • Focus: ROI tracking vs. projections, budget status, revenue cycle impact
  • Owns investment continuation decisions

CEO Updates:

  • Monthly summary (combine CDO/CFO inputs)
  • Focus: strategic progress, competitive positioning, major risks
  • Receives board update drafts for review

Regional Manager Briefing Guide

Pre-Rollout Briefing (2 weeks before region enters active wave)

Purpose: Equip regional managers to cascade information and support their locations

Content:

  1. Why we're doing this: Strategic context, expected benefits
  2. What's changing: Workflow overview, not technical detail
  3. Timeline for your region: Specific dates, which locations in which order
  4. Your role:
    • Champion identification and endorsement
    • Go-live week escalation availability (4 hours/week)
    • Daily check-in facilitation
    • Staff resistance response
  5. Success metrics you'll be measured on: Location adoption rate, issue resolution time, staff feedback scores
  6. Escalation paths: When to handle locally vs. escalate centrally
  7. Resources: Training materials, FAQ, champion contact list

Format: 60-minute briefing with Q&A; followed by written guide document


Staff Resistance Framework for Multi-Location Dynamics

Common Resistance Patterns

Pattern Manifestation Response Strategy
Fear of replacement "AI will take my job" Emphasize augmentation, not replacement; show how AI supports their expertise
Autonomy threat Providers feel judged by AI Frame as decision support; emphasize override authority
Workflow burden "This adds steps" Demonstrate net time savings after learning curve
Competence anxiety "I'm not good with tech" Peer support via champion; no-shame learning environment
Passive resistance Non-use without complaint Monitor adoption metrics; address directly with champions
Cross-location comparison fear "Corporate will use this to judge us" Be transparent about metrics use; emphasize improvement, not punishment

Multi-Location Dynamics

Challenge: Resistance at one location can spread to others through informal networks.

Mitigation:

  • Champions from enthusiastic locations share positive experiences in cross-location calls
  • Early wins publicized through internal channels
  • Avoid public comparison that shames low-adoption locations
  • Address resistance quickly before it becomes cultural

Escalation Path for Resistance

  1. Champion addresses with individual staff member
  2. Office manager supports champion if needed
  3. Regional manager intervenes if location-wide resistance
  4. CDO involvement if clinical leadership required
  5. 🟣 Central HR consultation if resistance becomes performance issue

Internal Marketing

Initiative Naming

Create an internal name that's memorable and positive. Examples:

  • "Vision Forward" initiative
  • "Clarity Project"
  • "[DSO Name] AI Imaging Launch"

Avoid: Generic "Overjet implementation" (sounds like a vendor project, not organizational transformation)

Momentum Building

Pre-Launch: ☐ Teaser communications 4 weeks before Wave 1: "Something new is coming..."
☐ CDO endorsement video: 2-minute explanation of clinical value
☐ FAQ page on intranet

During Rollout: ☐ Weekly "Wave Update" email with progress stats
☐ Champion spotlight: feature successful champions by name
☐ "Win of the week": share specific patient impact stories

Milestone Celebrations: ☐ Wave completion acknowledgment from CEO/CDO
☐ 50% deployment milestone: organization-wide announcement
☐ Full deployment: virtual celebration, certificates for champions

Communication Channels

  • Email for formal updates
  • Slack/Teams for peer-to-peer support and quick wins
  • Intranet for documentation and resources
  • Town halls for Q&A (one per wave)

8. Go-Live Day Runbook

Standardized Go-Live Checklist (Per Location)

Pre-Go-Live (Day Before)

☐ Champion confirms all staff training complete
☐ Technical verification: integration live, test image processed successfully
☐ Backup workflow documented (what to do if Overjet fails during patient care)
☐ Champion schedule confirmed: on-site entire first day
☐ Regional manager notified and on-call
☐ Patient communication scripts printed/distributed

Go-Live Day Hour-by-Hour Schedule

Time Activity Who
7:00 AM Champion arrives 30 mins early; system health check Champion
7:15 AM Quick team huddle: "Today's the day" encouragement Champion + Office Manager
7:30 AM First patients arrive; normal scheduling All staff
8:00 AM First X-rays processed through Overjet Provider + Tech
9:00 AM First check-in: any issues? Champion
10:00 AM Provider feedback check: comfort level? Champion
12:00 PM Midday check-in with regional manager (brief call) Champion
12:30 PM Lunch break; champion available for questions Champion
2:00 PM Afternoon check-in: system stable? Champion
4:00 PM Final hour assessment; document issues Champion
5:00 PM End-of-day debrief (15 mins); issues logged Champion + Office Manager
5:30 PM Daily summary submitted to central team Champion

Who Needs to Be On-Site or On-Call

Role Availability Contact Method
Location Champion On-site all day In-person
Office Manager On-site In-person
Regional Manager On-call, reachable within 15 mins Phone/Teams
Central Implementation Lead On-call Slack/Phone
πŸ”΅ Overjet Support On-call (confirm hours) Support portal/phone
Central IT On-call if integration issues Slack/Phone

Known Gotchas and Troubleshooting

⚠️ Common First-Day Issues

Issue Symptoms Resolution Escalation if unresolved
Images not uploading X-ray captured but doesn't appear in Overjet Refresh browser; verify network; check imaging software connection Champion β†’ Central IT
Slow AI response Analysis takes >60 seconds Check bandwidth; reduce concurrent users Central IT β†’ Overjet Support
Login failures SSO not authenticating Clear cache; try different browser; verify credentials Central IT
Incorrect patient match AI analysis appears under wrong patient Do not use; report immediately; verify PMS data sync Champion β†’ Central IT β†’ Overjet
Overlay display issues Colors not visible or annotations missing Adjust monitor brightness; try different browser; check display settings Central IT
System offline Cannot access Overjet at all Verify internet; check Overjet status page; revert to backup workflow Champion β†’ Central IT β†’ Overjet

Backup Workflow (When Overjet Is Unavailable)

  1. Capture X-rays as normal
  2. Document findings manually (pre-Overjet workflow)
  3. Log timestamp when system went down
  4. Process backlogged images when system restored (batch review)

Patient Communication Script

If patient asks about AI:

"We've implemented advanced imaging technology that helps our doctors analyze your X-rays. It highlights areas that may need attention, and then your dentist reviews everything and makes the final decisions about your care. It's an additional tool to help us provide you with the best possible treatment. Do you have any questions?"

If patient expresses concern:

"I completely understand. This technology is FDA-cleared and is used as a support tool, similar to how a second opinion works. Your dentist is always the one making clinical decisions. Your care is still personalized and based on your specific needs."

If patient asks to opt out:

"While the system automatically processes images for our team's review, your dentist is always the one making all clinical decisions. The technology simply helps us be more thorough. If you have concerns, I can have the dentist speak with you directly."


First-Week Daily Check-In Protocol

Champion β†’ Regional Manager (Daily, 10 minutes)

Format: Quick call or structured message

Template:

DAILY CHECK-IN - [Location Name] - Day [X] of Go-Live

SYSTEM STATUS: [Green/Yellow/Red]
β€’ Images processed today: [X]
β€’ System issues: [None / Brief description]

STAFF STATUS: [Green/Yellow/Red]
β€’ Any staff struggling? [Names/roles]
β€’ Training gaps identified: [None / Description]

PATIENT FEEDBACK: [None / Brief]

TOP ISSUE TODAY: [Description or "None"]

SUPPORT NEEDED: [None / Specific request]

Regional Manager β†’ Central Team (Daily, end of day)

  • Aggregates location check-ins
  • Flags any yellow/red locations
  • Documents emerging patterns across wave

Escalation Tiers

Tier Scope Response Time Who
Tier 0 Self-resolve with cheat sheet Immediate Staff member
Tier 1 Location champion can resolve <15 minutes Champion
Tier 2 Regional manager coordination needed <2 hours Regional Manager
Tier 3 Central IT or implementation team <4 hours Central Team
Tier 4 πŸ”΅ Vendor support required Per SLA (confirm) Overjet Support
Tier 5 Executive escalation (system-wide issue) <1 hour CDO/COO

9. Post-Launch Optimization (Weeks 4–8)

Weekly Metrics Review Cadence

Week 1–4 (Post Go-Live): Weekly Review

Who: Implementation lead, regional managers, champions (rotating) When: Every Friday, 30 minutes Focus:

  • System stability and uptime
  • Adoption rate (% of X-rays processed through Overjet)
  • Issue log review
  • Staff feedback themes
  • Early clinical outcome signals

Week 5–8: Bi-weekly Review

Who: Implementation lead, CDO, regional managers When: Every other Friday, 45 minutes Focus:

  • Comparative metrics vs. baseline
  • Cross-location performance
  • Training effectiveness
  • Early ROI indicators

Metrics to Track

Per Location

Metric Target (by Day 30) Red Flag
AI processing adoption β‰₯90% of eligible X-rays <70%
System uptime β‰₯99.5% <98%
Average AI response time <30 seconds >60 seconds
Support tickets opened <5/week >15/week
Staff satisfaction (survey) β‰₯4.0/5.0 <3.0/5.0

Clinical Outcome Indicators

Metric Baseline Day 30 Target Day 60 Target
Findings per BWX set (AI-identified) [Baseline] Establish new normal Stable
Case acceptance rate [Baseline] β‰₯5% improvement β‰₯10% improvement
Treatment plan value presented [Baseline] Stable or increasing β‰₯5% increase

Revenue Cycle Indicators

Metric Baseline Day 60 Target
Claim denial rate [Baseline] β‰₯10% reduction
Documentation rework requests [Baseline] β‰₯20% reduction
Days to claim payment [Baseline] β‰₯5% improvement

30-Day Checkpoint

What "Good" Looks Like

β˜‘ β‰₯90% AI processing adoption across all live locations
β˜‘ Zero major system outages (>1 hour) in past 2 weeks
β˜‘ Provider satisfaction β‰₯4.0/5.0 on utility rating
β˜‘ At least one documented clinical catch (AI identified finding provider confirmed)
β˜‘ Champions report minimal daily support requests
β˜‘ No rollbacks required

Red Flags Requiring Intervention

⚠️ <70% adoption at any location (investigate immediately)
⚠️ Provider bypass behavior (not using AI despite policy)
⚠️ >10 support tickets/week per location
⚠️ Staff satisfaction <3.0/5.0
⚠️ Pattern of system issues during peak hours

30-Day Intervention Protocol

  1. Identify root cause (survey, interviews, data analysis)
  2. Determine if training, technical, or change management issue
  3. Deploy targeted intervention:
    • Training gap β†’ champion re-training session
    • Technical issue β†’ escalate to vendor
    • Change resistance β†’ regional manager coaching conversation
  4. Re-measure in 2 weeks
  5. 🟣 If unresolved after intervention, executive escalation

60-Day Checkpoint: ROI Assessment

ROI Assessment Framework

ROI Component Baseline Current Change Financial Impact
Case acceptance rate X% X% +X% $[Y] incremental revenue
Average production per patient $X $X +$X $[Y] Γ— [patients]
Claim denial rate X% X% -X% $[Y] saved in rework
Documentation time per claim X mins X mins -X mins [X] hours Γ— $[Y] hourly cost
New patient conversion X% X% +X% $[Y] per new patient value

Calculating Net ROI

Monthly Incremental Revenue
  + Monthly Cost Savings
  - Monthly Overjet Subscription Cost
  - Monthly Support/Training Cost
  = Net Monthly ROI

Annualized: Net Monthly ROI Γ— 12
Payback Period: Total Implementation Cost Γ· Net Monthly ROI

Staff Feedback Collection

5-Question Pulse Survey (Deploy at Day 30 and Day 60)

  1. On a scale of 1–5, how useful is Overjet in your daily work? (1 = Not useful, 5 = Extremely useful)

  2. How has Overjet affected your workflow efficiency? (1 = Significantly slower, 3 = No change, 5 = Significantly faster)

  3. How confident are you in using Overjet correctly? (1 = Not confident, 5 = Very confident)

  4. How would you rate the support you've received for Overjet? (1 = Poor, 5 = Excellent)

  5. What's one thing that would improve your Overjet experience? (Open text)

Distribution: Email or embedded in Overjet dashboard Anonymity: Anonymous by default; identify by location only Response target: β‰₯70% response rate per location


Common Workflow Refinements (First Month)

Based on typical DSO deployments, expect these adjustments:

Refinement Trigger Solution
Adjust AI overlay display time Providers report overlays appear too fast/slow Configure display duration in settings
Modify notification settings Too many/few alerts Champion adjusts per provider preferences
Refine patient communication script Patient questions not covered Update script based on actual questions received
Streamline report generation Billing requests faster access Create bookmarked report shortcuts
Add specialty-specific finding emphasis Perio offices want bone loss prioritized Champion customizes view preferences
Revise training for specific workflow New hires follow different path Update training module

Centralized Dashboard Structure

Executive View (Aggregated)

Metric All Locations Wave 1 Wave 2 Wave 3
Locations live X of Y X X X
Overall adoption rate X% X% X% X%
System health [Status] β€” β€” β€”
Avg. findings per patient X.X X.X X.X X.X
Case acceptance rate X% X% X% X%
Active support tickets X X X X

Location Detail View

Location Adoption Uptime Findings/Pt Case Accept Staff Score Status
Site A 94% 99.8% 2.3 72% 4.2 🟒
Site B 78% 99.5% 2.1 68% 3.8 🟑
Site C 65% 99.2% 1.9 65% 3.1 πŸ”΄

Dashboard Tool Options

  • Power BI (if existing Microsoft ecosystem)
  • Tableau (if existing Salesforce ecosystem)
  • Google Data Studio (cost-effective option)
  • πŸ”΅ Overjet built-in analytics (confirm capabilities with vendor)

Quarterly Business Review Framework (Post Full Deployment)

QBR Structure (90 minutes)

Attendees: CDO, COO, CFO, Regional Managers, Overjet CSM

Agenda:

  1. Performance Overview (20 mins)

    • System health and uptime
    • Adoption metrics by region
    • Clinical outcome trends
  2. ROI Analysis (20 mins)

    • Revenue impact
    • Cost savings
    • Comparison to projections
  3. Clinical Impact Deep Dive (15 mins)

    • Case studies: high-value catches
    • Provider variance analysis
    • Standard of care implications
  4. Challenges and Solutions (15 mins)

    • Top issues from quarter
    • Root cause analysis
    • Resolutions implemented
  5. Optimization Opportunities (10 mins)

    • Feature adoption gaps
    • Workflow refinement candidates
    • πŸ”΅ Overjet roadmap preview (vendor input)
  6. Next Quarter Priorities (10 mins)

    • Agreed actions
    • Success metrics
    • Resource requirements

10. Centralized vs. Localized Decision Framework

Decision Area Standardize Centrally Allow Local Discretion Rationale
Overjet subscription and licensing βœ“ Enterprise pricing; central budget
SSO and authentication βœ“ Security consistency
User role definitions βœ“ Compliance and audit trail
Core finding categories enabled βœ“ Clinical standardization
HIPAA compliance settings βœ“ Regulatory requirement
Audit log retention βœ“ Legal requirement
Report templates (base) βœ“ Brand and documentation consistency
Integration architecture βœ“ IT support efficiency
Training materials (core) βœ“ Message consistency
Go-live checklist βœ“ Quality assurance
Champion selection βœ“ Local knowledge of staff
Training scheduling βœ“ Operational flexibility
Provider overlay preferences βœ“ Personal workflow
Finding display priorities βœ“ Specialty mix variation
Patient communication script (wording) βœ“ Local patient demographics
Check-in timing βœ“ Schedule variation
Report customization (additions) βœ“ Local clinical preferences
Feedback collection method βœ“ Team dynamics
🟣 Exception to any centralized policy βœ“ Requires COO/CDO approval

11. Risk Register

Risk ID Risk Description Likelihood (1-5) Impact (1-5) Risk Score Mitigation Strategy Owner
R1 Integration failure with legacy PMS versions at some locations 3 4 12 Pre-implementation compatibility audit; upgrade path for incompatible systems Central IT
R2 Provider resistance reduces adoption below viable threshold 3 5 15 CDO engagement; train-the-trainer model; peer success stories; clear override protocols CDO + Regional Managers
R3 Network connectivity issues at rural locations cause system unreliability 4 3 12 Bandwidth assessment pre-rollout; defer problematic locations; offline fallback workflow Central IT
R4 ⚠️ Champion turnover mid-implementation 3 4 12 Identify backup champion per location; cross-train 2 staff members; champion documentation requirements Regional Manager
R5 AI findings create malpractice liability concerns 2 5 10 Legal review pre-launch; clear documentation protocols for override; provider training on AI limitations CDO + Legal
R6 πŸ”΅ Vendor support response time exceeds SLA during critical rollout 2 4 8 SLA confirmation in contract; escalation contacts established; internal first-line troubleshooting capacity Implementation Lead
R7 Patient privacy concern or HIPAA incident 2 5 10 BAA execution; compliance audit; staff training on data handling; breach response plan Compliance + IT
R8 Budget overrun due to extended timeline or additional integration work 3 3 9 Fixed-price contract where possible; contingency budget (15%); strict scope management CFO
R9 Cross-location comparison creates unhealthy competition or morale issues 3 3 9 Frame metrics for improvement, not judgment; private location-level feedback; celebrate all progress CDO + HR
R10 Overjet pricing increase at renewal 2 3 6 Multi-year contract consideration; market comparison; ROI documentation for negotiation leverage CFO

Risk Score Key: 1–8 = Low (monitor), 9–15 = Medium (active mitigation), 16–25 = High (executive attention)


12. Executive Reporting Template

Monthly Rollout Status Report

═══════════════════════════════════════════════════════════════════
           OVERJET IMPLEMENTATION: MONTHLY STATUS REPORT
                        [MONTH YEAR]
═══════════════════════════════════════════════════════════════════

EXECUTIVE SUMMARY
━━━━━━━━━━━━━━━━━
Overall Status: [🟒 On Track / 🟑 Minor Delays / πŸ”΄ At Risk]

Locations Deployed: [X] of [Y] ([Z]%)
This Month: [X] locations went live
Next Month: [X] locations planned

DEPLOYMENT PROGRESS
━━━━━━━━━━━━━━━━━━━
[Progress bar visual or simple tracker]
Wave 1: β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ Complete (3/3)
Wave 2: β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘ In Progress (5/8)
Wave 3: β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘ Pending (0/19)

KEY METRICS
━━━━━━━━━━━
| Metric                    | Target | Actual | Status |
|---------------------------|--------|--------|--------|
| Average adoption rate     | 90%    | [X]%   | [🟒/🟑/πŸ”΄] |
| System uptime             | 99.5%  | [X]%   | [🟒/🟑/πŸ”΄] |
| Staff satisfaction        | 4.0    | [X]    | [🟒/🟑/πŸ”΄] |
| Case acceptance rate Ξ”    | +5%    | [X]%   | [🟒/🟑/πŸ”΄] |

FINANCIAL STATUS
━━━━━━━━━━━━━━━━
Budget spent: $[X] of $[Y] ([Z]%)
On track: [Yes/No]
Variance explanation: [If applicable]

Early ROI indicators: [Brief statement]

LOCATION STATUS SUMMARY
━━━━━━━━━━━━━━━━━━━━━━━
🟒 Performing well: [X] locations
🟑 Minor issues, action in progress: [X] locations
πŸ”΄ Significant issues, escalated: [X] locations

[If any πŸ”΄]: Root cause: [Brief]. Resolution: [Brief].

RISKS AND ISSUES
━━━━━━━━━━━━━━━━
| Issue | Impact | Status | Owner |
|-------|--------|--------|-------|
| [Description] | [High/Med/Low] | [Open/In Progress/Resolved] | [Name] |

NEXT MONTH PRIORITIES
━━━━━━━━━━━━━━━━━━━━━
1. [Priority]
2. [Priority]
3. [Priority]

DECISIONS NEEDED
━━━━━━━━━━━━━━━━
[List any decisions requiring executive input]

═══════════════════════════════════════════════════════════════════
Report prepared by: [Name]
Distribution: CEO, CDO, CFO, COO, Board [as applicable]
═══════════════════════════════════════════════════════════════════

Red/Yellow/Green Status Framework

Location-Level Status

AI-generated implementation guide based on public vendor information. Verify specifics directly with Overjet.