VideaHealth
Step-by-step implementation guide β pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
VideaHealth β Implementation Playbook (DSO)
VideaHealth Implementation Playbook
Diagnostic AI Imaging for Dental Support Organizations
Prepared for: VPs of Operations, Chief Dental Officers, and Regional Managers Organization Profile: DSOs with 15β50 Locations Publication: Avized.com Vendor Resource Library
1. Executive Summary
What VideaHealth Does
VideaHealth is an FDA-cleared dental AI platform that analyzes radiographic images in real-time to detect caries, calculus, bone loss, and other pathologies with diagnostic accuracy that matches or exceeds clinical specialists. The platform integrates with existing imaging systems and practice management software to overlay AI-detected findings directly onto X-rays at the point of care, providing dentists with a consistent second read on every image.
Why DSOs Specifically Benefit from Diagnostic AI
DSOs operating at scale face a fundamental challenge: diagnostic variability across dozens of providers undermines care quality consistency, case acceptance rates, and defensibility against audits. VideaHealth addresses this through:
- Standardization at Scale: Every radiograph across every location receives the same AI analysis, eliminating provider-to-provider diagnostic variation and establishing an objective baseline for clinical quality metrics
- Data Aggregation for Strategic Insight: Centralized dashboards reveal patterns invisible at the practice levelβidentifying under-diagnosing locations, tracking case acceptance trends across regions, and benchmarking provider performance against network-wide standards
- Audit Defense and Risk Mitigation: AI-documented findings create a defensible clinical record, reducing malpractice exposure and providing evidence during payer audits
- Scalable Training Infrastructure: New associate dentists receive immediate AI support, accelerating their ramp to full productivity while maintaining diagnostic standards
Expected Timeline: Decision to Full Deployment
| Phase | Duration | Milestone |
|---|---|---|
| Pre-Implementation | Weeks 1β2 | Technical readiness, stakeholder alignment, baseline metrics captured |
| Pilot Wave (2β3 locations) | Weeks 3β6 | Initial deployment, learning capture, workflow refinement |
| Wave 2 (5β8 locations) | Weeks 7β10 | Scaled deployment with validated playbook |
| Wave 3+ (Remaining locations) | Weeks 11β18 | Full network deployment |
| Optimization | Weeks 19β24 | Post-deployment refinement, ROI validation |
Total Timeline: 4β6 months for a 30-location DSO, with faster timelines achievable for organizations with mature IT infrastructure and strong change management capabilities.
2. Pre-Implementation Checklist (Weeks 1β2)
Technical Requirements
Hardware Requirements per Location
β Workstations with minimum specifications:
- Windows 10/11 (64-bit) or macOS 11+
- 8GB RAM minimum (16GB recommended)
- Modern processor (Intel i5/AMD Ryzen 5 or better, manufactured 2018+)
- Dedicated graphics card recommended for optimal rendering
- Dual monitors recommended for clinical workflow optimization
β Network requirements:
- Minimum 25 Mbps download / 10 Mbps upload per location
- Latency under 100ms to VideaHealth cloud servers
- Stable connection (99%+ uptime required for real-time analysis)
β Imaging equipment compatibility verification:
- Digital sensors (Dexis, Schick, Carestream, Gendex, or compatible)
- Panoramic units with digital output
- CBCT integration (if applicableβconfirm with vendor)
Software Requirements
β Compatible Practice Management System:
- Dentrix (version G6.2+)
- Eaglesoft (version 19+)
- Open Dental (version 19.1+)
- Other PMSβconfirm compatibility with VideaHealth π΅
β Compatible Imaging Software:
- Dexis (version 9+)
- Carestream (CS Imaging)
- Apteryx XrayVision
- Patterson Imaging
- Other imaging systemsβconfirm compatibility π΅
β Browser requirements for web-based dashboard:
- Chrome (latest), Firefox (latest), Edge (latest)
- Pop-up blockers disabled for VideaHealth domains
Enterprise-Level Network Standards (DSO-Specific)
β Standardized firewall rules across all locations allowing VideaHealth endpoints β VPN requirements clarified (VideaHealth operates via secure cloudβVPN typically not required) β SSL certificate requirements for enterprise security policies β Data residency confirmation (US-based servers for HIPAA compliance)
Hosting Architecture Decision π£
β Determine centralized vs. location-level hosting model:
| Option | Pros | Cons | Recommendation |
|---|---|---|---|
| Cloud-hosted (Standard) | No local infrastructure, automatic updates, consistent experience | Requires reliable internet | Recommended for most DSOs |
| Hybrid | Some local processing, reduced latency | More complex management | Consider for rural locations with connectivity issues |
SSO and Centralized Credentialing
β Determine SSO integration requirements:
- Okta, Azure AD, or other identity provider
- SAML 2.0 or OAuth 2.0 compatibility confirmed π΅ β Role-based access control structure defined:
- Provider (full clinical access)
- Office Manager (reports + settings)
- Regional Manager (multi-location dashboards)
- Corporate Admin (enterprise configuration) β Credential provisioning workflow established with HR systems
Vendor Onboarding Steps
Key Contacts to Establish π΅
β Account Executive: [Name, email, phone]βcommercial relationship, escalations β Implementation Manager: [Name, email, phone]βtechnical deployment lead β Technical Support Tier 1: [Support portal, phone]βday-to-day issues β Customer Success Manager: [Name, email]βpost-go-live optimization β Executive Sponsor (Vendor side): [Name]βfor escalations requiring VP+ involvement
Onboarding Kickoff Activities π΅
β Schedule enterprise onboarding call (typically 60β90 minutes) β Complete vendor security questionnaire β Execute Business Associate Agreement (BAA) β Receive enterprise admin credentials for configuration portal β Access training portal and documentation library β Establish dedicated Slack channel or Teams channel for implementation (if offered)
Data/Access Prerequisites
β Admin credentials for each Practice Management System instance β Admin credentials for imaging software across locations β API keys or integration credentials (obtained from PMS/imaging vendors) β Historical imaging archive access (if pursuing retrospective analysis) β Test patient records created in sandbox environment for validation β Network diagrams for each location (to identify firewall/connectivity issues)
Stakeholder Alignment Map
Board/Investors π£
Why they care: Capital allocation, competitive positioning, risk management What they need to know: Investment amount, expected ROI timeline, competitive implications Decision rights: Approve capital expenditure if above threshold Communication cadence: Quarterly updates via CEO/CFO
β Prepare investment memo with:
- Total contract value and per-location economics
- ROI projections tied to case acceptance and diagnostic consistency
- Competitive landscape (which competitors are deploying AI?)
- Risk factors and mitigation strategies
C-Suite π£
| Role | Primary Interest | Decision Rights | Communication Cadence |
|---|---|---|---|
| CEO | Strategic positioning, investor narrative | Final go/no-go | Bi-weekly during implementation |
| CFO | Budget, ROI, contract terms | Budget approval | Weekly cost/progress updates |
| CDO/CMO | Clinical quality, provider adoption, liability | Clinical protocol approval | Weekly during pilot, bi-weekly after |
| CIO/CTO | Integration, security, IT capacity | Technical architecture approval | Daily during integration, weekly ongoing |
| COO | Operations, rollout logistics, staffing | Rollout sequence approval | Daily during implementation |
β Executive kickoff meeting scheduled (all C-suite, 60 minutes) β Decision matrix documented: who approves what at each phase β Escalation protocol established for cross-functional conflicts
Regional Managers
Why they care: Location performance, staff workload, change fatigue What they need to know: Timeline, their role, location selection rationale Decision rights: Input on location sequencing, local adaptation within guidelines Communication cadence: Weekly during implementation
β Regional manager briefing deck prepared β Input collected on location readiness and local dynamics β Champions identified with regional manager validation
Location-Level Office Managers
Why they care: Day-to-day operations, staff morale, patient experience What they need to know: Go-live date, training plan, escalation contacts Decision rights: Limitedβprimarily execution of corporate plan Communication cadence: Daily during go-live week, weekly otherwise
β Office manager information packet prepared β Go-live date communicated 4+ weeks in advance β Training schedule confirmed with each location
Providers (Dentists, Hygienists)
Why they care: Clinical workflow, diagnostic authority, liability What they need to know: How AI supports (not replaces) their judgment, training plan Decision rights: Individual workflow preferences within corporate guidelines Communication cadence: Direct training sessions, feedback channels post-launch
β Clinical advisory group formed (3β5 influential providers) β Provider FAQ document developed β Malpractice/liability guidance from legal counsel β οΈ
Baseline Metrics to Capture BEFORE Go-Live β οΈ
Critical: Without baseline metrics, ROI cannot be demonstrated. Capture these BEFORE any location goes live.
Clinical Metrics (Per Location)
| Metric | How to Measure | Target Source |
|---|---|---|
| Case acceptance rate | Presented treatment $ accepted / Presented treatment $ total | PMS reports |
| Caries detection rate | Caries diagnoses / Total radiographs taken | PMS + clinical notes |
| Treatment plan value (average) | Average $ per treatment plan presented | PMS reports |
| Radiograph retake rate | Retakes / Total radiographs | Imaging software logs |
| Time from image capture to diagnosis | Timestamp analysis | PMS or manual sampling |
Operational Metrics (Per Location)
| Metric | How to Measure | Target Source |
|---|---|---|
| Average appointment duration | Schedule data analysis | PMS |
| Hygiene-to-doctor handoff rate | % of hygiene appointments with doctor exam | PMS |
| Same-day treatment acceptance | Treatment completed same day as diagnosis | PMS |
Financial Metrics (Per Location)
| Metric | How to Measure | Target Source |
|---|---|---|
| Production per provider | Monthly production by provider | PMS/Accounting |
| Collection rate | Collections / Production | Accounting |
| Insurance claim denial rate (treatment-related) | Denied claims / Total claims | Billing system |
Enterprise Standardization Requirements β οΈ
β Standardize measurement methodology across all locations:
- Same date ranges for baseline period (recommend: 90 days pre-implementation)
- Same definitions for each metric (create glossary)
- Same data extraction process (create SOP)
- Same reporting format (create template)
β Designate metric owner at corporate level responsible for data integrity β Validate data quality before accepting baseline numbers (spot-check 3β5 locations) β Document any known data issues that may affect comparability
3. Location Readiness Assessment
Scoring Framework
Rate each location on the following factors using a 1β5 scale. Sum the weighted scores to produce a composite readiness score.
Factor 1: IT Infrastructure Maturity (Weight: 25%)
| Score | Criteria |
|---|---|
| 5 | Network consistently exceeds requirements (50+ Mbps), workstations <2 years old, PMS current version, prior successful integrations |
| 4 | Network meets requirements reliably, workstations 2β3 years old, PMS within one version of current |
| 3 | Network meets minimum requirements, workstations 3β4 years old, PMS may need minor upgrade |
| 2 | Network inconsistent, workstations 4β5 years old, PMS requires upgrade before integration |
| 1 | Network unreliable, workstations >5 years old, major infrastructure investment required |
Factor 2: Staff Tenure and Adaptability (Weight: 20%)
| Score | Criteria |
|---|---|
| 5 | Low turnover (<10% annually), staff has adopted 2+ new technologies in past 2 years, documented training history |
| 4 | Moderate turnover (10β20%), at least one recent technology adoption, generally positive toward change |
| 3 | Average turnover (20β30%), mixed history with technology changes, will require standard change management |
| 2 | Higher turnover (30β40%), struggled with past technology changes, significant change management needed |
| 1 | High turnover (>40%), history of failed technology implementations, extensive intervention required |
Factor 3: Patient Volume (Weight: 15%)
| Score | Criteria |
|---|---|
| 5 | High volume (500+ patients/month), sufficient scale to demonstrate impact quickly, experienced staff can handle complexity |
| 4 | Above average volume (350β500), good balance of impact and manageable risk |
| 3 | Average volume (200β350), moderate impact potential, standard risk profile |
| 2 | Below average volume (100β200), limited impact potential but also lower risk |
| 1 | Low volume (<100), minimal impact but may be useful for low-risk learning |
Note: For pilot locations, moderate volume (score 3β4) may be preferable to very high volume (score 5) to reduce risk.
Factor 4: Existing Tech Stack Compatibility (Weight: 25%)
| Score | Criteria |
|---|---|
| 5 | PMS and imaging software on VideaHealth's certified compatibility list, prior integrations functioning well |
| 4 | PMS compatible, imaging software compatible, no known integration conflicts |
| 3 | PMS compatible, imaging software requires minor configuration, or vice versa |
| 2 | Either PMS or imaging software requires upgrade or workaround for compatibility |
| 1 | Significant compatibility issues, custom development or system replacement needed |
Factor 5: Local Champion Availability (Weight: 15%)
| Score | Criteria |
|---|---|
| 5 | Tech-forward provider or OM actively volunteering to lead, prior experience championing change, respected by team |
| 4 | Willing and capable champion identified, positive attitude, good standing with team |
| 3 | Potential champion identified but needs development, or champion is willing but not highly influential |
| 2 | No clear champion, will need to assign someone who may not be naturally inclined |
| 1 | No viable champion, key personnel resistant, leadership vacuum at location |
Composite Score Calculation
| Factor | Weight | Location Score (1β5) | Weighted Score |
|---|---|---|---|
| IT Infrastructure | 25% | ___ | ___ |
| Staff Adaptability | 20% | ___ | ___ |
| Patient Volume | 15% | ___ | ___ |
| Tech Compatibility | 25% | ___ | ___ |
| Champion Availability | 15% | ___ | ___ |
| TOTAL | 100% | ___ / 5.0 |
Readiness Tier Classification
| Composite Score | Tier | Rollout Recommendation |
|---|---|---|
| 4.0β5.0 | Green β High Readiness | Wave 1 or Wave 2 candidate |
| 3.0β3.9 | Yellow β Moderate Readiness | Wave 2 or Wave 3, may need targeted remediation |
| 2.0β2.9 | Orange β Low Readiness | Wave 3 or later, requires pre-work before deployment |
| Below 2.0 | Red β Not Ready | Do not schedule until remediation complete |
Recommended Rollout Sequence
Based on composite scores, sequence locations as follows:
Wave 1 Selection Criteria (2β3 Locations)
- Composite score 4.0+ AND
- Represents portfolio diversity (urban/suburban, different regions if applicable)
- Not your highest-volume location (manage risk) AND
- Strong, engaged champion confirmed AND
- Regional manager supportive and available
Wave 2 Selection Criteria (5β8 Locations)
- Composite score 3.5+ AND
- Any remediation items from Wave 1 learnings already addressed AND
- Champions identified and trained
Wave 3+ Selection Criteria (Remaining Locations)
- All remaining locations scoring 3.0+
- Red-tier locations receive remediation plans and are re-scored before scheduling
Sample Location Readiness Matrix
| Location | IT (25%) | Staff (20%) | Volume (15%) | Compatibility (25%) | Champion (15%) | Composite | Tier | Recommended Wave |
|---|---|---|---|---|---|---|---|---|
| Phoenix Main | 4 | 4 | 5 | 5 | 4 | 4.35 | Green | Wave 1 |
| Scottsdale | 5 | 3 | 4 | 4 | 5 | 4.20 | Green | Wave 1 |
| Tempe | 3 | 4 | 3 | 4 | 3 | 3.50 | Yellow | Wave 2 |
| Mesa | 2 | 3 | 4 | 3 | 2 | 2.75 | Orange | Wave 3 (after IT upgrade) |
4. Rollout Strategy
Wave Structure Overview
| Wave | Locations | Duration | Purpose |
|---|---|---|---|
| Wave 1 (Pilot) | 2β3 | Weeks 3β6 | Validate playbook, identify issues, refine workflows |
| Wave 2 | 5β8 | Weeks 7β10 | Scale validated approach, train champions at scale |
| Wave 3 | 8β12 | Weeks 11β14 | Continue expansion with proven methodology |
| Wave 4+ | Remaining | Weeks 15β18 | Complete deployment |
Adjust wave sizes based on your total location count and internal capacity.
Wave 1 (Pilot) Detailed Plan
Selection Criteria for Pilot Locations π£
β High readiness score (4.0+) β minimize technical risk β Engaged, credible champion β learnings will influence the network β Moderate volume β enough activity to validate, not so much that issues cause major disruption β Geographic/demographic diversity β ensure learnings transfer to other locations β Regional manager with bandwidth to support closely β NOT your flagship location β if something goes wrong, reputational risk is contained
Pilot Timeline (Weeks 3β6)
Week 3: Integration & Configuration
- Day 1β2: Technical integration with PMS and imaging π΅
- Day 3β4: Test environment validation
- Day 5: Configuration finalization
Week 4: Training & Soft Launch
- Day 1β2: Champion training (in-depth, 4β6 hours) π΅
- Day 3β4: Champion-led staff training
- Day 5: Soft launch (limited operatories/providers)
Week 5: Full Location Go-Live
- Full go-live at pilot locations
- Daily check-ins with champions
- Rapid issue resolution
Week 6: Stabilization & Learning Capture
- Issue resolution
- Workflow refinement
- Documentation of learnings
- Go/no-go assessment for Wave 2
Pilot Success Metrics
β Technical stability: <5% system errors or downtime β User adoption: >90% of radiographs analyzed through VideaHealth β User satisfaction: >70% positive feedback from providers β Workflow integration: No appointments running >10 minutes over due to AI β No patient complaints attributable to AI implementation
Go/No-Go Criteria for Wave Advancement π£
Before advancing from any wave to the next, the following criteria must be met:
Technical Readiness
| Criterion | Threshold | Evidence Required |
|---|---|---|
| System uptime | >99% during business hours | Vendor dashboard or internal monitoring |
| Integration stability | <2 critical errors per location per week | Support ticket log |
| Performance speed | AI overlay appears in <5 seconds | Spot-check timing |
Operational Readiness
| Criterion | Threshold | Evidence Required |
|---|---|---|
| Staff trained | 100% of required staff completed training | Training completion log |
| Workflow documentation | Updated SOPs published | Document review |
| Champion confidence | Champion self-assesses ready to support independently | Champion attestation |
Clinical Readiness
| Criterion | Threshold | Evidence Required |
|---|---|---|
| Provider adoption | >80% of providers using AI daily | Usage analytics |
| Provider feedback | No unresolved clinical concerns | Provider survey |
| Patient safety | Zero patient safety incidents | Incident log |
Go/No-Go Decision Meeting π£
β Scheduled 3 business days before next wave start β Attendees: COO, CDO/CMO, CIO, Implementation Lead, Vendor Implementation Manager β Decision documented with rationale β If "No-Go": Remediation plan with target re-assessment date
Timeline Per Wave with Buffer
| Phase | Wave 1 | Wave 2 | Wave 3 | Wave 4+ |
|---|---|---|---|---|
| Integration & Configuration | 5 days | 3 days (parallel) | 3 days | 2 days |
| Training | 3 days | 2 days | 2 days | 2 days |
| Go-Live + Stabilization | 7 days | 5 days | 5 days | 5 days |
| Buffer between waves | 5 days | 4 days | 3 days | N/A |
| Total wave duration | 20 days | 14 days | 13 days | 9 days |
Buffer time is critical for incorporating learnings. Do not compress. β οΈ
Rollback Plan
Triggers for Rollback Consideration π£
- Critical system outage lasting >4 hours during business hours
- Integration failure causing PMS data corruption or loss
- Provider refusal rate >40% after training and support interventions
- Patient safety incident with AI as contributing factor
- Pattern of diagnostic errors not caught by providers
Rollback Procedure
Immediate (within 2 hours of trigger): β Regional Manager notified β Vendor support escalated to highest tier π΅ β Location reverts to pre-AI workflow (disable VideaHealth overlay) β Staff notified via champion β Patient-facing communication prepared if needed
Same Day: β COO and CDO/CMO notified β Root cause investigation initiated β Rollback formally documented β Impact assessment completed
Within 48 Hours: β Executive briefing with root cause and remediation plan π£ β Decision: remediate and re-deploy, delay wave, or broader pause β Communication cascade to all stakeholders
Isolation Principle
Rollback at one location does not automatically pause other locations or waves unless:
- Root cause is systemic (affects all locations)
- Root cause is unknown and could affect other locations
- Executive decision to pause for organizational reasons
5. Configuration & Integration (Weeks 2β3)
Integration with Practice Management Systems
Dentrix Integration π΅
Prerequisites: β Dentrix version G6.2 or higher installed β Dentrix Ascend API access enabled (for Ascend customers) β Local admin credentials available β Current Dentrix backup verified
Step-by-Step Process:
β Verify version compatibility β Open Dentrix β Help β About Dentrix β Confirm version G6.2+
- Time: 5 minutes
β Enable API access (if not already enabled) π΅
- Contact Henry Schein for API credentials
- May require support call; allow 24β48 hours
- Time: 1β2 business days
β Install VideaHealth connector π΅
- VideaHealth implementation team provides installer
- Run installer as administrator
- Follow prompts for server connection
- Time: 15β30 minutes per workstation
β Configure practice settings
- Map provider IDs between Dentrix and VideaHealth
- Configure patient record sync preferences
- Set imaging storage paths
- Time: 30β45 minutes per location
β Test integration β οΈ
- Create test patient in Dentrix
- Capture test radiograph
- Verify image appears in VideaHealth within 30 seconds
- Verify AI analysis appears
- Verify analysis data writes back to Dentrix (if bidirectional)
- Time: 30 minutes
β Validate with 5 real patients (non-production first if possible)
- Time: 2 hours
Eaglesoft Integration π΅
Prerequisites: β Eaglesoft version 19 or higher installed β Patterson Technology Center support contact available β Local admin credentials available β Current Eaglesoft backup verified
Step-by-Step Process:
β Verify version compatibility β Open Eaglesoft β Help β About β Confirm version 19+
- Time: 5 minutes
β Confirm imaging integration type
- Patterson Imaging direct integration, or
- Third-party imaging software bridge
- Time: 10 minutes
β Request API credentials π΅
- Contact Patterson Technology Center
- Submit API access request
- Allow 2β5 business days
- Time: 2β5 business days
β Install VideaHealth connector π΅
- Provided by VideaHealth implementation team
- Install on server and workstations as directed
- Time: 30β45 minutes per location
β Configure mapping
- Provider mapping
- Operatory mapping (if used for routing)
- Image type mapping
- Time: 30β45 minutes
β Test and validate (same as Dentrix above) β οΈ
- Time: 2β3 hours
Open Dental Integration π΅
Prerequisites: β Open Dental version 19.1 or higher β Open Dental API enabled (Service Manager β API β Enable) β API key generated
Step-by-Step Process:
β Verify version β Open Dental β Help β About
- Time: 5 minutes
β Enable API and generate key
- Setup β Advanced Setup β API
- Generate new API key for VideaHealth
- Time: 15 minutes
β Configure FHIR/API settings π΅
- VideaHealth may require specific FHIR endpoints
- Follow vendor documentation for Open Dental specifics
- Time: 30 minutes
β Install VideaHealth connector π΅
- Time: 20β30 minutes
β Map imaging preferences
- Open Dental supports multiple imaging bridges; confirm active bridge
- Configure X-Ray bridge settings to work with VideaHealth
- Time: 30 minutes
β Test and validate β οΈ
- Time: 2 hours
Integration with Imaging Systems π΅
Dexis Integration
Prerequisites: β Dexis version 9 or higher β Dexis Imaging Suite Administrator credentials β Network path to image storage verified
Step-by-Step Process:
β Verify Dexis version and image format
- Confirm DICOM or compatible image format
- Time: 10 minutes
β Configure image export/watch folder (if applicable)
- VideaHealth may monitor a folder for new images, or
- Direct integration via Dexis API
- Time: 20β30 minutes
β Install VideaHealth imaging connector π΅
- Integrates with Dexis viewer to overlay AI findings
- Time: 30 minutes
β Test with sample images
- Capture FMX, BWX, PA images
- Verify AI analysis appears within 5 seconds
- Time: 30 minutes
Other Imaging Systems
- Carestream CS Imaging: Similar folder watch or API integration π΅
- Patterson Imaging: Integrates via Eaglesoft connection π΅
- Apteryx XrayVision: API integration available π΅
- Planmeca Romexis: Confirm compatibility with vendor π΅
Test Environment Setup and Validation Checklist
Centralized Test Environment (Recommended for DSO) π£
β Create centralized sandbox environment with:
- Test PMS instance (or isolated database)
- Test imaging folder with sample radiographs
- Test patient records (de-identified or synthetic)
- Access for IT, implementation lead, and select champions
β Validation Checklist (complete before ANY location goes live):
| Test Case | Expected Result | Pass/Fail | Tester | Date |
|---|---|---|---|---|
| New image capture triggers AI analysis | Analysis appears in <5 seconds | |||
| AI findings visible in viewer | Overlay appears on radiograph | |||
| Findings documented in PMS | Treatment codes suggested or chart note added | |||
| Multiple images in sequence | All images analyzed without queue backup | |||
| Large FMX (18+ images) | All images analyzed within 60 seconds | |||
| Provider accepts AI finding | Finding incorporated into treatment plan | |||
| Provider dismisses AI finding | Dismissal logged, no impact on original image | |||
| System offline/network loss | Graceful failure, clear error message, recovery | |||
| End-of-day data sync | All day's analyses accessible in dashboard | |||
| PHI handling | No PHI visible in logs, data encrypted |
Data Migration / Historical Data Ingestion
Retrospective Analysis (Optional)
VideaHealth can analyze historical radiographs to identify potentially missed pathology. This is optional but valuable for quality assurance.
Decision Required π£: Enable retrospective analysis? (Y/N)
If Yes: β Identify scope:
- All patients seen in last 12 months? 24 months?
- All image types or BWX/PA only?
- All locations or pilot locations only?
β Data preparation:
- Export historical images in supported format
- Maintain patient ID linkage for re-integration
- De-identify if sending to vendor for batch processing π΅
β Review workflow:
- How will historical findings be surfaced to providers?
- What is the callback protocol for patients with newly identified pathology?
- Who is responsible for outreach?
β Compliance review:
- Legal review of patient communication for retrospective findings β οΈ
- Documentation requirements for findings not addressed at time of original radiograph
Estimated Time: 2β4 weeks depending on volume, parallel with deployment
Security and HIPAA Compliance Verification Checklist
Enterprise-Level HIPAA Checklist
Business Associate Agreement (BAA) β BAA executed with VideaHealth π΅ β BAA reviewed by legal counsel β BAA terms align with your existing compliance framework β BAA covers all services (cloud hosting, support, analytics) β Breach notification terms acceptable (typically 24β72 hour requirement)
Data Governance β Data classification: PHI handled appropriately β Data residency: Confirm data stored in US (or acceptable jurisdiction) β Data retention: Align with your retention policies β Data deletion: Process for data deletion upon contract termination β Data ownership: Your organization retains ownership of all data β οΈ
Access Controls β Role-based access control implemented β Minimum necessary access principle applied β Individual user accounts (no shared credentials) β SSO integrated (if applicable) β Multi-factor authentication enabled for admin accounts β Access logging enabled β Regular access reviews scheduled (quarterly recommended)
Technical Safeguards β Data encrypted in transit (TLS 1.2+) β Data encrypted at rest (AES-256 or equivalent) β Penetration testing performed (request results from vendor) π΅ β SOC 2 Type II certification (request report) π΅ β HIPAA attestation letter (request from vendor) π΅
Audit and Monitoring β Audit logs capture access and changes β Logs retained for minimum 6 years (HIPAA requirement) β Regular security reviews by vendor (request evidence) π΅ β Incident response plan documented (obtain from vendor) π΅
Standardized Configuration Template (DSO)
The following settings should be identical across all locations to ensure consistency:
Standardize Centrally
| Setting | Standard Value | Rationale |
|---|---|---|
| AI sensitivity threshold | [Vendor default or adjusted based on pilot] | Consistent detection standards |
| Finding categories enabled | Caries, calculus, bone loss, periapical lesions | Consistent scope of analysis |
| Confidence score display | Show confidence percentage | Transparency for providers |
| Automatic documentation | Enabled | Consistent charting support |
| Alert thresholds | [Define] | Consistent escalation |
| Dashboard access by role | [Define per role matrix] | Consistent RBAC |
| Data retention | [Align with corporate policy] | Compliance |
Allow Local Discretion
| Setting | Allowed Variation | Rationale |
|---|---|---|
| Overlay color scheme | Provider preference | Personal ergonomics |
| Notification sound | On/off per provider | Personal preference |
| Secondary review workflow | Per provider workflow | Accommodate workflow variation |
| Training scheduling | Within corporate timeline | Local scheduling flexibility |
6. Team Training Plan
Train-the-Trainer Model Overview
Structure
Corporate Implementation Team
β
Regional Training Leads
β
Location Champions
β
Location Staff (by role)
Champion Selection Criteria
β Role: Provider (preferred) or Office Manager β Tenure: 1+ years at the location β Tech aptitude: Demonstrated comfort with clinical technology β Influence: Respected by peers, opinion leader β Availability: Capacity to dedicate 4β6 hours to training, ongoing support β Attitude: Positive about AI, willing advocate
Champion Responsibilities
- Complete intensive champion certification training (4β6 hours) π΅
- Deliver role-specific training to location staff
- Serve as first point of contact for location questions
- Participate in weekly champion calls during rollout
- Provide feedback on training materials and workflows
- Escalate unresolved issues to regional manager/central team
- Maintain training completion records for their location
Champion Certification Process π΅
β Complete online self-paced modules (2 hours) β Attend live virtual training session (2 hours) β Pass certification quiz (80% threshold) β Complete observed training delivery with feedback β Receive champion certification
Standardized Training Materials (Created Centrally)
β Champion Certification Course β online modules + live session β Provider Training Deck β 45-minute presentation + demo β Hygienist Training Deck β 20-minute presentation β Front Desk Training Deck β 20-minute presentation β Billing Staff Training Deck β 15-minute presentation β Day 1 Cheat Sheets β one-page quick reference per role β FAQ Document β 20+ common questions with answers β Video Library β short how-to videos for key tasks (3β5 minutes each) β Troubleshooting Guide β common issues and solutions
Role-Specific Training Outlines
Dentists/Providers
Estimated Training Time: 45β60 minutes Recommended Format: Live demo (in-person or video call) + hands-on practice Delivered By: Champion (after champion certification)
Training Outline:
What is VideaHealth (5 min)
- FDA clearance and clinical validation
- AI as decision support, not replacement
- Liability framework (AI assists, dentist decides)
How it integrates with your workflow (10 min)
- When AI analysis appears (automatic on image capture)
- What you'll see on screen (overlay, confidence scores)
- Where findings are documented
Interpreting AI outputs (15 min) β οΈ
- Reading confidence scores
- Understanding detection categories (caries, calculus, bone loss)
- Viewing AI annotations on radiographs
- Distinguishing high-confidence vs. borderline findings
When to accept, modify, or override AI (10 min) β οΈ
- AI as second opinion, not final diagnosis
- Documentation when overriding AI finding
- When to seek additional imaging or consultation
Hands-on practice (10 min)
- Process 3β5 sample radiographs with AI
- Practice accepting/dismissing findings
- Practice documentation workflow
Common Resistance Points & Responses:
| Resistance | Response |
|---|---|
| "AI will miss things I catch" | "AI is a safety net, not a replacement. It catches what you might miss on a busy dayβyou still make all decisions." |
| "This will slow me down" | "After initial learning curve (~1 week), most providers report no additional time and some report faster diagnosis." |
| "What if AI is wrong and I'm liable?" | "You remain the diagnostician. AI is a tool like a second opinion. Document your clinical reasoning when you disagree with AI." |
| "I don't need a computer telling me what to do" | "This is decision support, like a lab test. You order labs but still make the diagnosis. AI is similar." |
Day 1 Cheat Sheet β Providers
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β VIDEAHEALTH PROVIDER QUICK REFERENCE β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β π· CAPTURE: Take radiograph as normal β
β β
β β±οΈ WAIT: AI analysis appears in 3β5 seconds β
β β
β ποΈ REVIEW: Look for colored overlays indicating findings β
β β’ RED = High confidence finding β
β β’ YELLOW = Moderate confidence, review recommended β
β β’ Hover over finding to see confidence % and category β
β β
β β
ACCEPT: Click finding to accept and add to treatment plan β
β β
β β DISMISS: Click X to dismiss finding (will be logged) β
β β
β π DOCUMENT: AI findings auto-populate in chart notes β
β β
β π HELP: Contact [Champion Name] or call [Support Number] β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Hygienists
Estimated Training Time: 20β30 minutes Recommended Format: Live demo (in-person or video call) Delivered By: Champion
Training Outline:
Overview of VideaHealth (5 min)
- What it does and why the practice is implementing it
- Their role in the workflow
Hygienist touchpoints (10 min)
- Radiographs captured during hygiene appointments trigger AI analysis
- Findings visible before doctor exam
- What hygienists can/should communicate vs. what waits for doctor
Patient communication (5 min)
- How to explain AI to curious patients
- What NOT to say (avoid diagnostic language)
- Script for patient questions
Escalation (5 min)
- What to do if AI shows high-confidence finding
- How to flag for doctor review
- Technical issue escalation
Common Resistance Points & Responses:
| Resistance | Response |
|---|---|
| "Patients will ask me what the AI found" | "You can say: 'The AI helps us make sure we don't miss anything. Dr. [Name] will review the findings with you.'" |
| "What if I see something concerning?" | "Flag it for the doctor as you would any clinical concern. AI is an additional input, not a change to your protocols." |
Day 1 Cheat Sheet β Hygienists
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β VIDEAHEALTH HYGIENIST QUICK REFERENCE β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β π· CAPTURE: Take radiographs per normal protocol β
β β
β β±οΈ AI activates automatically β no action needed β
β β
β π YOU MAY SEE: AI overlays on radiographs before doctor reviews β
β β
β π£οΈ PATIENT ASKS ABOUT AI? Say: β
β "We use AI to help ensure we catch everything. β
β Dr. [Name] will review and explain the findings." β
β β
β β οΈ SEE SOMETHING CONCERNING? Flag for doctor as usual. β
β β
β π TECHNICAL ISSUES? Contact [Champion Name] β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Front Desk / Office Manager
Estimated Training Time: 20β30 minutes Recommended Format: Video call or in-person with hands-on Delivered By: Champion
Training Outline:
Why VideaHealth (5 min)
- Practice benefits (quality, consistency, patient safety)
- No change to front desk clinical responsibilities
Administrative functions (10 min)
- Dashboard access (if applicable)
- Report generation
- User account support (password resets, access issues)
Patient communication (5 min)
- Responding to patient questions about AI
- Scheduling considerations (typically none)
- Consent process (if applicable) β οΈ
Troubleshooting basics (5 min)
- Common issues and first-line responses
- When to escalate to champion or IT
Day 1 Cheat Sheet β Front Desk
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β VIDEAHEALTH FRONT DESK QUICK REFERENCE β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β π YOUR ROLE: Minimal changes β support the clinical team β
β β
β π£οΈ PATIENT ASKS ABOUT AI? Say: β
β "We use AI technology to help our doctors provide the best care. β
β It's like having a second expert review every X-ray." β
β β
β βοΈ PATIENT CONSENT: [Insert practice-specific protocol] β
β β
β π REPORTS: Access dashboard at [URL] for usage reports β
β β
β π ISSUES? Contact [Champion Name] at [ext/phone] β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Billing/Insurance Staff
Estimated Training Time: 15β20 minutes Recommended Format: Video call or recorded video Delivered By: Champion or Billing Supervisor
Training Outline:
Impact on coding (5 min)
- AI does not change CDT codes used
- AI-detected findings documented same as provider-detected findings
- No separate billing for AI analysis (included in diagnostic codes)
Impact on documentation (5 min)
- AI findings integrated into clinical notes
- Supports claim documentation for medical necessity
- May reduce denials for diagnostic procedures
Claims and denials (5 min) β οΈ
- No specific claims language for AI
- If asked by payer: "AI-assisted radiograph analysis" is acceptable
- AI documentation may strengthen appeals
Day 1 Cheat Sheet β Billing
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β VIDEAHEALTH BILLING QUICK REFERENCE β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β π΅ CODING: No changes to CDT codes. Bill diagnosis as normal. β
β β
β π DOCUMENTATION: AI findings auto-documented in clinical notes. β
β Use this to support medical necessity. β
β β
β β PAYER ASKS ABOUT AI? Say: β
β "We use FDA-cleared AI-assisted radiograph analysis." β
β β
β π APPEALS: AI documentation may strengthen denial appeals. β
β β
β π QUESTIONS? Contact [Champion Name] β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Training Completion Tracking
Training Record Template (Per Location)
| Staff Name | Role | Training Module | Completion Date | Champion Verification | Notes |
|---|---|---|---|---|---|
| β | |||||
| β |
Pre-Go-Live Training Requirement β οΈ
No location may go live until: β 100% of providers trained and verified β 100% of hygienists trained and verified β 100% of front desk staff trained and verified β Champion certified and verified β Training completion report submitted to central team
Training Completion Dashboard (Central)
β Create centralized view showing:
- % trained by location
- % trained by role
- Overdue training (not complete 48 hours before go-live)
- Training satisfaction scores (from post-training survey)
Ongoing Training Cadence
New Hires
β Champion delivers training within first week of employment β Training completion logged in central system β New hire completes certification quiz before accessing VideaHealth
Refresher Training
β Quarterly "office hours" webinar (optional, recorded) β Annual mandatory refresher (30 minutes, online) β Triggered refresher if performance metrics decline
Feature Updates
β Vendor notifies of feature updates 2+ weeks in advance π΅ β Central team reviews and creates update training materials β Champions cascade training to locations β Major updates may require go/no-go assessment before deployment π£
7. Change Management
Executive Sponsor Communication Plan
Board/Investor Updates π£
Frequency: Quarterly (align with board meetings), plus ad-hoc for major milestones
Update Format:
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β BOARD UPDATE: AI DIAGNOSTIC IMAGING IMPLEMENTATION β
β Prepared by: [CDO/COO] Date: [MM/DD/YYYY] β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β EXECUTIVE SUMMARY (3 sentences) β
β [Progress summary, key metrics, outlook] β
β β
β KEY METRICS β
β β’ Locations Live: X/Y (Z%) β
β β’ Provider Adoption Rate: X% β
β β’ Case Acceptance Change: +X% vs. baseline β
β β’ Patient Feedback: X% positive β
β β
β COMPETITIVE POSITIONING β
β [How this positions us vs. competitors] β
β β
β FINANCIAL IMPACT (if measurable) β
β β’ Estimated additional revenue: $X β
β β’ ROI trajectory: on track / ahead / behind β
β β
β RISKS AND MITIGATIONS β
β [Top 2β3 risks and what we're doing] β
β β
β NEXT QUARTER MILESTONES β
β β’ [Milestone 1] β
β β’ [Milestone 2] β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
CEO/CFO Updates π£
Frequency: Bi-weekly during active deployment, monthly during optimization
Update Format: Email or dashboard snapshot with:
- Location status (on track / at risk / delayed)
- Budget status (on budget / variance explanation)
- Top 3 issues requiring executive attention
- Key decisions needed this period
Regional Manager Briefing Guide
Purpose: Enable regional managers to confidently communicate the rollout to their locations and support implementation.
Briefing Deck Contents (Created by Central Team)
- Why We're Implementing AI Diagnostics (strategic rationale)
- What This Means for Your Region (timeline, locations, expectations)
- Your Role in the Rollout (responsibilities checklist)
- How to Support Your Champions (coaching guide)
- How to Handle Resistance (objection responses)
- Escalation Paths (when to escalate, to whom)
- FAQ for Common Questions (provider and staff questions)
- Key Dates and Milestones (region-specific calendar)
Regional Manager Responsibilities
β Attend central briefing session (60 minutes) β Brief each location's Office Manager 2+ weeks before their go-live β Validate champion selection at each location β Join weekly champion calls during active deployment in their region β Escalate unresolved issues to COO/Implementation Lead β Report regional status weekly
Staff Resistance Framework for Multi-Location Dynamics
Common Resistance Patterns and Interventions
| Pattern | Symptom | Root Cause | Intervention |
|---|---|---|---|
| "Skeptical Provider" | Provider refuses to use AI or openly criticizes | Fear of replacement, threat to expertise, past negative tech experience | One-on-one meeting with CDO/CMO; address concerns directly; show clinical validation data; offer to shadow successful provider at pilot location |
| "Change Fatigue" | Staff going through the motions but not engaged | Too many initiatives, burnout | Acknowledge fatigue; show how this is different; reduce other initiatives if possible; emphasize long-term workflow improvement |
| "Location Island" | One location resists while others adopt | Weak local leadership, cultural isolation, unaddressed grievances | Regional manager intervention; identify local concerns; create location-specific action plan; consider champion change |
| "Silent Resistance" | Low adoption numbers without overt objection | Passive non-compliance, workflow workarounds | Data-driven conversation; identify specific blockers; remove friction points; consider incentives |
| "Influencer Opposition" | One respected provider or OM undermines adoption | Influence network dynamics | Direct executive engagement; address concerns at peer level; co-opt as advisor if possible; last resort: work around them |
Escalation Protocol for Resistance
- Champion-level response (first 48 hours): Champion has direct conversation, identifies concerns
- Office Manager involvement (if unresolved): OM reinforces expectations, documents concerns
- Regional Manager intervention (if escalating): RM visits location, coaches OM/champion
- Central team engagement (if pattern emerges): Implementation lead and CDO/CMO develop location-specific plan
- Executive intervention (if critical): COO/CEO communicates expectations π£
Internal Marketing
Initiative Naming
β Create a branded initiative name that's:
- Memorable and positive
- Doesn't over-promise (avoid "AI will diagnose for you")
- Connects to company values
Example Names:
- "DiagnostiCare AI Initiative"
- "Project ClearView"
- "Second Look" (emphasizes AI as supportive)
Creating Momentum
β Launch announcement from CEO (video or email) β Town hall with Q&A (all-hands or regional) β Intranet/internal site with updates, FAQ, champion spotlights β Swag (optional): "Early Adopter" stickers, t-shirts for champions
Celebrating Milestones
| Milestone | Recognition |
|---|---|
| Champion certified | Certificate, recognition in company newsletter |
| Location goes live | Team shout-out, small celebration (lunch, etc.) |
| Wave completed | Regional manager announcement, executive acknowledgment |
| Full deployment | Company-wide celebration, success story publication |
| ROI milestone achieved | Executive case study, potential for industry publication |
8. Go-Live Day Runbook
Hour-by-Hour Schedule (Per Location)
Day Before Go-Live
| Time | Activity | Owner | Completed |
|---|---|---|---|
| 4:00 PM | Final system check (connectivity, integration working) | Champion | β |
| 4:30 PM | Confirm all staff completed training | Champion | β |
| 5:00 PM | Pre-go-live champion huddle call with central team | Central IT | β |
| 5:30 PM | Send go-live reminder to all location staff | Champion | β |
Go-Live Day
| Time | Activity | Owner | Completed |
|---|---|---|---|
| 7:00 AM | Champion arrives early, confirms systems operational | Champion | β |
| 7:15 AM | Brief morning huddle with all staff (5 min) | Champion | β |
| 7:30 AM | First patients of the day | Providers | β |
| 7:30β8:30 AM | Champion shadows first 3β5 radiograph captures | Champion | β |
| 8:30 AM | Quick pulse check with providers (any issues?) | Champion | β |
| 10:00 AM | Midmorning check-in call with central team | Champion + Central | β |
| 12:00 PM | Lunch breakβchampion reviews any logged issues | Champion | β |
| 12:30 PM | Midday pulse check with staff | Champion | β |
| 2:00 PM | Afternoon check-in call with central team | Champion + Central | β |
| 4:30 PM | End-of-day staff huddle (10 min)βwhat worked, what didn't | Champion | β |
| 5:00 PM | Champion submits Day 1 report to regional manager | Champion | β |
| 5:30 PM | Central team aggregates all location reports | Central Team | β |
Who Needs to Be On-Site or On-Call
On-Site
| Role | Requirement |
|---|---|
| Champion | On-site entire go-live day, shadowing and troubleshooting |
| Office Manager | On-site (normal workday) |
| All providers | On-site (normal schedule) |
On-Call
| Role | Availability | Contact Method |
|---|---|---|
| Regional Manager | 7 AM β 6 PM, 15-minute response | Cell phone |
| Central Implementation Lead | 7 AM β 6 PM, 15-minute response | Cell/Slack |
| Central IT Support | 7 AM β 6 PM, 30-minute response | Support ticket + phone |
| VideaHealth Support | Per SLA (typically 24/7 for critical) π΅ | Support portal + emergency line |
Known Gotchas and Troubleshooting β οΈ
Issue: AI Overlay Not Appearing
Symptoms: Radiograph captured but no AI analysis overlay appears First-Line Troubleshooting:
- β Wait 10 seconds (may be processing)
- β Refresh the imaging viewer
- β Check internet connectivity (speedtest.net)
- β Restart imaging software
- β Restart workstation if above steps fail
Escalation Trigger: Issue persists after workstation restart Escalation Path: Champion β Central IT β VideaHealth Support π΅
Issue: Slow AI Processing (>10 seconds)
Symptoms: AI analysis taking longer than expected First-Line Troubleshooting:
- β Check network speed (should be >25 Mbps)
- β Check if other workstations experiencing same issue
- β If network-wide, check router/switch status
- β If single workstation, restart workstation
Escalation Trigger: Processing time consistently >15 seconds Escalation Path: Champion β Central IT (network team)
Issue: Integration Error / Patient Mismatch
Symptoms: AI analysis appears on wrong patient or fails to link First-Line Troubleshooting:
- β Verify correct patient selected in PMS
- β Verify correct patient selected in imaging software
- β Re-capture image with patient verified
- β Log incident for investigation
Escalation Trigger: Repeat occurrence with same patient or multiple patients β οΈ Escalation Path: Champion β Central IT β VideaHealth Support π΅
PATIENT SAFETY NOTE: If wrong patient linkage occurred, follow PHI incident protocol.
Issue: Provider Disagreement with AI Finding
Symptoms: Provider believes AI finding is incorrect This is NOT a technical issue. Correct response:
- Provider documents their clinical reasoning in chart
- Provider dismisses AI finding in system
- Dismissal is logged for quality review
- No escalation needed unless pattern emerges
Issue: Patient Questions About AI
Symptoms: Patient curious or concerned about AI involvement Response Script:
"We use an FDA-cleared AI system that helps our doctors by providing a second analysis of your X-rays. It's like having a specialist review every image. Our dentist still makes all decisions about your careβthe AI is just a helpful tool to make sure nothing is missed."
If patient objects to AI:
"We understand. If you prefer, we can note in your chart that you'd like your radiographs reviewed only by our clinical team. The AI analysis will still occur for quality purposes, but the findings won't be shared with you directly."
Consult legal counsel if patients request that AI not be used at all. β οΈ
Standardized Go-Live Checklist (All Locations Must Complete)
Pre-Go-Live (Complete Day Before)
β All staff training verified complete β Champion certified β System connectivity tested β Integration tested with 3+ test images β Day 1 schedule reviewedβno unusual complexity β Champion has Day 1 Cheat Sheets printed for all staff β Champion has escalation contacts confirmed
Go-Live Day (Complete Throughout Day)
β Morning huddle completed β First 3 radiographs successfully analyzed β No critical system errors in first 2 hours β Midmorning check-in completed β Afternoon check-in completed β End-of-day huddle completed β Day 1 report submitted
Day 1 Report Template
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β DAY 1 GO-LIVE REPORT β
β Location: _______________ Date: _______________ β
β Champion: _______________ β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β OVERALL STATUS: [ ] GREEN [ ] YELLOW [ ] RED β
β β
β RADIOGRAPHS ANALYZED TODAY: ____ β
β SYSTEM ERRORS/ISSUES: ____ β
β β
β PROVIDER FEEDBACK: β
β ___________________________________________________________________ β
β ___________________________________________________________________ β
β β
β STAFF FEEDBACK: β
β ___________________________________________________________________ β
β ___________________________________________________________________ β
β β
β ISSUES TO ESCALATE: β
β 1. ______________________________________________________________ β
β 2. ______________________________________________________________ β
β β
β SUPPORT NEEDED: β
β ___________________________________________________________________ β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
First-Week Daily Check-In Protocol
Daily Champion Check-In (Days 1β5)
Frequency: Daily, 15 minutes Participants: Champion, Regional Manager (or delegate) Platform: Phone or video call
Agenda:
- Status: Green/Yellow/Red (1 min)
- Volume: Radiographs analyzed yesterday (1 min)
- Issues: Any system or workflow issues (5 min)
- Feedback: Provider and staff sentiment (3 min)
- Support needs: Anything needed from central (3 min)
- Next steps: Actions before tomorrow's call (2 min)
Central Team Daily Sync (Days 1β5)
Frequency: Daily, 30 minutes Participants: Implementation Lead, IT Support Lead, Regional Managers (dial-in) Time: End of business day
Agenda:
- Roll call of live locationsβstatus summary
- Critical issues requiring immediate action
- Patterns emerging across locations
- Vendor escalations in progress π΅
- Plan for tomorrow
Escalation Tiers
| Tier | Who | Handles | Response Time |
|---|---|---|---|
| Tier 1 | Location Champion | Workflow questions, first-line troubleshooting | Immediate |
| Tier 2 | Regional Manager | Unresolved location issues, staff conflict, process questions | Within 2 hours |
| Tier 3 | Central |
AI-generated implementation guide based on public vendor information. Verify specifics directly with VideaHealth.