Planmeca
Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
Planmeca — Implementation Playbook (DSO)
Planmeca Diagnostic Imaging AI Implementation Playbook
A Strategic Guide for Dental Support Organizations
1. Executive Summary
What Planmeca Diagnostic Imaging AI Does
Planmeca's AI-powered diagnostic imaging platform integrates advanced machine learning algorithms with its industry-leading CBCT, panoramic, and intraoral imaging hardware to automatically detect anatomical structures, pathologies, and clinical findings. The system provides real-time analysis overlays, automated measurements, and clinical decision support that enhances diagnostic accuracy while reducing interpretation time from minutes to seconds.
Why DSOs Specifically Benefit from Diagnostic Imaging AI
Diagnostic imaging AI delivers compounding returns at scale that single practices cannot capture:
- Standardization of Clinical Quality: Ensures consistent diagnostic protocols across all 15–50 locations, reducing variability in detection rates and treatment planning regardless of individual provider experience levels
- Centralized Data Intelligence: Aggregates imaging analytics across your portfolio to identify trends, benchmark performance, and surface operational insights impossible to see at the location level
- Leverage in Vendor Negotiations: Enterprise deployment creates partnership leverage for pricing, support SLAs, and feature roadmap influence
- Accelerated Training ROI: Train once, deploy everywhere—your investment in training materials and champion development multiplies across every location
- Risk Mitigation at Scale: Consistent AI-assisted detection creates defensible documentation standards, reducing malpractice exposure across your entire organization
Expected Timeline: Decision to Full Deployment
| Phase | Timeline | Milestone |
|---|---|---|
| Pre-Implementation & Planning | Weeks 1–2 | Infrastructure audit complete, baseline metrics captured |
| Wave 1 Pilot (2–3 locations) | Weeks 3–6 | Pilot validation, lessons learned documented |
| Wave 2 Expansion (5–8 locations) | Weeks 7–12 | Scaled deployment validated |
| Wave 3 Full Deployment (remaining locations) | Weeks 13–20 | All locations live |
| Optimization & Stabilization | Weeks 21–26 | Full ROI measurement capability |
Total Timeline: 5–6 months for a 30-location DSO, with faster timelines possible for organizations with mature IT infrastructure and strong change management capabilities.
2. Pre-Implementation Checklist (Weeks 1–2)
Technical Requirements
Hardware Requirements
☐ Verify all imaging equipment is Planmeca-compatible (Planmeca ProMax 3D, Planmeca Viso, or compatible third-party sensors with TWAIN/DICOM compliance) ☐ Confirm workstation specifications at each location meet minimum requirements:
- Processor: Intel i7 (8th gen+) or AMD Ryzen 7 equivalent
- RAM: 16GB minimum, 32GB recommended
- GPU: NVIDIA GTX 1060 or higher (CUDA-enabled required for local processing)
- Storage: 500GB SSD minimum with expansion capacity
- Display: 1920x1080 minimum, medical-grade monitors recommended for diagnostic use ☐ Audit server capacity for centralized image storage (estimate 500MB–2GB per CBCT scan)
Network Requirements
☐ Minimum 100 Mbps dedicated bandwidth per location for cloud processing ⚠️ Common failure point: Shared networks with patient WiFi cause latency issues ☐ Verify firewall configurations allow outbound connections to Planmeca cloud endpoints ☐ Confirm VPN or secure tunnel capability for centralized management access ☐ Test network latency to Planmeca servers (<100ms recommended)
Software Requirements
☐ Planmeca Romexis software version 6.0 or higher at all locations ☐ Windows 10/11 Professional (LTSC builds not recommended) ☐ Current antivirus with Planmeca executable exclusions configured ☐ .NET Framework 4.8 or higher installed
Integration Requirements
☐ Document current PMS at each location (Dentrix, Eaglesoft, Open Dental, other) ☐ Verify PMS versions support Planmeca bridge integration ☐ Confirm imaging PACs/archive system compatibility (if using third-party storage) ☐ Identify any custom integrations that may conflict
Vendor Onboarding Steps 🔵
| Step | Action | Owner | Timeline |
|---|---|---|---|
| 1 | Execute enterprise Master Services Agreement (MSA) | Legal/CDO | Day 1–3 🟣 |
| 2 | Complete Business Associate Agreement (BAA) | Compliance | Day 1–3 |
| 3 | Establish dedicated Enterprise Account Manager contact | Vendor Relations | Day 3 🔵 |
| 4 | Schedule technical kickoff call with Planmeca implementation team | IT Director | Day 4–5 🔵 |
| 5 | Obtain enterprise license keys and deployment credentials | IT Director | Day 5–7 🔵 |
| 6 | Confirm support tier and escalation contacts | Operations | Day 5–7 🔵 |
| 7 | Receive access to Planmeca partner training portal | Training Lead | Day 7 🔵 |
Key Vendor Contacts to Establish
- Enterprise Account Manager (commercial relationship)
- Technical Implementation Specialist (deployment support)
- Clinical Applications Specialist (training and workflow optimization)
- Tier 2 Technical Support Lead (escalation path)
- Customer Success Manager (ongoing relationship)
Data/Access Prerequisites
☐ Create centralized admin account with enterprise-wide visibility ☐ Establish location-level admin accounts with appropriate permissions ☐ Obtain API credentials for PMS integrations (per system) ☐ 🔵 Request Planmeca cloud tenant provisioning for your organization ☐ Document current imaging archive structure and access credentials at each location ☐ Export historical imaging data inventory (volume, date ranges, file types per location) ☐ Verify DICOM compliance of historical images for potential AI retrospective analysis
Enterprise-Level Requirements
Network Standards Across Locations
☐ 🟣 Decide: Centralized cloud processing vs. edge processing at each location
- Recommendation: Hybrid model—cloud for CBCT AI analysis (higher compute), local for intraoral (lower latency) ☐ Establish minimum network SLAs for all locations (document exceptions and remediation plans) ☐ Standardize firewall rules and port configurations in central IT documentation
Centralized vs. Location-Level Hosting Decision 🟣
| Model | Pros | Cons | Recommendation |
|---|---|---|---|
| Fully Centralized | Single point of management, consistent updates | Latency concerns, single point of failure | Best for <20 locations with strong connectivity |
| Hybrid | Balances control with performance | More complex architecture | Recommended for 15–50 location DSOs |
| Fully Distributed | Best performance, location resilience | Management overhead, version drift risk | Only if network infrastructure is poor |
Identity & Access Management
☐ 🟣 Decide: SSO integration (SAML 2.0/OAuth) vs. standalone authentication
- Recommendation: SSO integration with your existing identity provider reduces credential management burden ☐ Define role-based access control (RBAC) structure:
- Enterprise Admin (central IT, 2–3 individuals)
- Regional Manager (read-only analytics, user management for region)
- Location Admin (Office Manager, local configuration)
- Clinical User (Providers, standard diagnostic access)
- Limited User (Hygienists, view-only where applicable) ☐ Establish centralized credentialing process for provider onboarding/offboarding ☐ Document license management process (how licenses move when staff transfers between locations)
Internal Stakeholder Alignment
Stakeholder Alignment Map
| Stakeholder | Role in Implementation | What They Need | Communication Frequency |
|---|---|---|---|
| Board/Investors | Approval of capital expenditure, strategic alignment | ROI projections, competitive positioning, risk mitigation | Monthly summary updates 🟣 |
| CEO | Executive sponsorship, resource allocation | Timeline, budget, strategic narrative | Bi-weekly briefings 🟣 |
| CDO | Clinical protocol approval, provider champion | Clinical workflow impact, quality metrics, liability considerations | Weekly during implementation 🟣 |
| VP Operations | Operational execution, location coordination | Detailed playbook, resource requirements, timeline | Owns implementation—daily involvement |
| CFO | Budget approval, ROI tracking | Cost breakdown, measurement framework, vendor terms | Monthly financial reviews 🟣 |
| CIO/IT Director | Technical implementation, security compliance | Technical specifications, integration requirements, support model | Daily during technical phases |
| Regional Managers | Location coordination, staff management | Location-specific timelines, training requirements, escalation paths | Weekly during their region's wave |
| Office Managers | Local execution, staff scheduling | Day-to-day playbook, training schedules, go-live checklists | Daily during location rollout |
| Lead Providers | Clinical adoption, peer influence | Clinical value proposition, workflow changes, override protocols | Weekly during training, as-needed after |
Approval Requirements by Decision Type
| Decision Type | Approval Required | Timeline to Obtain |
|---|---|---|
| Vendor contract execution | CEO + CFO + Legal | 1–2 weeks |
| Capital expenditure (hardware) | CFO + Board (if >threshold) | 2–4 weeks |
| Clinical protocol changes | CDO | 1 week |
| Data sharing/BAA | Compliance + Legal | 1 week |
| Rollout timeline and wave structure | VP Operations + CEO | 1 week |
| Location selection for Wave 1 | VP Operations + Regional Managers | 3–5 days |
Baseline Metrics to Capture ⚠️
Failure to capture baseline metrics is the #1 reason DSOs cannot demonstrate ROI. This step is non-negotiable.
Standardized Metric Definitions (Apply Uniformly Across All Locations)
| Metric | Definition | Data Source | How to Calculate |
|---|---|---|---|
| Case Acceptance Rate | % of diagnosed conditions that proceed to treatment | PMS treatment plans | (Accepted treatment $ ÷ Presented treatment $) × 100 |
| Average Diagnosis Time | Time from image capture to documented diagnosis | Timestamp analysis | Image capture timestamp to treatment plan creation timestamp |
| Radiographic Findings per Exam | Number of documented findings per imaging session | Clinical notes | Manual chart audit (sample 50 exams per location) |
| Claim Denial Rate (Imaging) | % of imaging-related claims denied on first submission | Billing system | Denied imaging claims ÷ Total imaging claims submitted |
| Retake Rate | % of images that require retaking | Imaging system logs | Retaken images ÷ Total images captured |
| CBCT Utilization Rate | % of eligible cases receiving CBCT | PMS + Imaging logs | CBCT scans ÷ Eligible case types (implant consults, endo, perio) |
| Secondary Findings Detection Rate | % of exams with incidental findings documented | Clinical notes | Chart audit—exams with documented incidental findings ÷ Total exams |
Data Collection Protocol
☐ Pull 90 days of historical data from each location (minimum) ☐ Standardize data extraction queries/reports across all PMS systems ☐ Create centralized baseline database with location identifiers ☐ Calculate location-level metrics and portfolio-wide benchmarks ☐ Identify outlier locations for investigation (may indicate data quality issues) ☐ Document any locations with incomplete data and establish collection plans
Cross-Location Comparison Framework
Create a baseline scorecard per location:
| Location | Case Accept % | Avg Dx Time | Findings/Exam | Denial Rate | Retake Rate | CBCT Util % |
|---|---|---|---|---|---|---|
| Loc 001 | ___ | ___ | ___ | ___ | ___ | ___ |
| Loc 002 | ___ | ___ | ___ | ___ | ___ | ___ |
| Portfolio Avg | ___ | ___ | ___ | ___ | ___ | ___ |
| Top Quartile | ___ | ___ | ___ | ___ | ___ | ___ |
This framework enables post-implementation comparison and identification of which locations gain the most value.
3. Location Readiness Assessment
Scoring Framework
Rate each location on the following factors using a 1–5 scale:
Factor 1: IT Infrastructure Maturity
| Score | Criteria |
|---|---|
| 1 | Network <25 Mbps, hardware >5 years old, PMS version unsupported |
| 2 | Network 25–50 Mbps, hardware 4–5 years old, PMS version outdated but functional |
| 3 | Network 50–100 Mbps, hardware 2–3 years old, PMS current version |
| 4 | Network 100+ Mbps, hardware <2 years old, PMS current, previous successful tech implementations |
| 5 | Network 200+ Mbps dedicated, latest hardware, current PMS with API experience, centralized IT support on-site |
Factor 2: Staff Tenure and Adaptability
| Score | Criteria |
|---|---|
| 1 | >40% annual turnover, no previous tech implementations, reported resistance to change |
| 2 | 25–40% turnover, one failed tech implementation, mixed technology comfort |
| 3 | 15–25% turnover, successful tech implementations with external support, average adaptability |
| 4 | 10–15% turnover, multiple successful tech implementations, proactive about learning |
| 5 | <10% turnover, staff-driven technology adoption, culture of continuous improvement |
Factor 3: Patient Volume Impact
| Score | Criteria | Risk/Reward Assessment |
|---|---|---|
| 1 | <50 patients/week | Low impact, low risk—minimal learning opportunity |
| 2 | 50–100 patients/week | Moderate impact, low risk |
| 3 | 100–150 patients/week | Good balance of impact and manageable risk |
| 4 | 150–200 patients/week | High impact, moderate risk—strong pilot candidate |
| 5 | >200 patients/week | Highest impact but highest risk—not recommended for Wave 1 |
Note: For Wave 1 pilot selection, scores of 3–4 are optimal. Very high volume locations (5) should be Wave 2 or later.
Factor 4: Existing Tech Stack Compatibility
| Score | Criteria |
|---|---|
| 1 | Non-standard PMS, proprietary imaging system, multiple legacy integrations |
| 2 | Major PMS but old version, some Planmeca hardware but older models |
| 3 | Standard PMS (Dentrix/Eaglesoft/Open Dental), mixed imaging hardware, basic integrations working |
| 4 | Standard PMS current version, majority Planmeca hardware, proven integration track record |
| 5 | Standard PMS with API, full Planmeca imaging suite, seamless existing integrations |
Factor 5: Local Champion Availability
| Score | Criteria |
|---|---|
| 1 | No identified champion, Office Manager overwhelmed, providers resistant |
| 2 | Potential champion identified but not confirmed, limited bandwidth |
| 3 | Champion identified and willing, limited prior training/leadership experience |
| 4 | Strong champion identified, previous training experience, respected by team |
| 5 | Natural leader identified, technology advocate, previous successful implementation leadership, dedicated time allocated |
Composite Readiness Score Calculation
| Factor | Weight | Rationale |
|---|---|---|
| IT Infrastructure | 25% | Technical foundation is prerequisite |
| Staff Adaptability | 25% | People factors determine adoption |
| Patient Volume | 15% | Balances learning opportunity with risk |
| Tech Stack Compatibility | 20% | Reduces integration complexity |
| Local Champion | 15% | Accelerates local adoption |
Composite Score = (IT × 0.25) + (Staff × 0.25) + (Volume × 0.15) + (TechStack × 0.20) + (Champion × 0.15)
Location Readiness Assessment Template
| Location | IT (1–5) | Staff (1–5) | Volume (1–5) | TechStack (1–5) | Champion (1–5) | Composite | Wave |
|---|---|---|---|---|---|---|---|
| Loc 001 | ___ | ___ | ___ | ___ | ___ | ___ | ___ |
| Loc 002 | ___ | ___ | ___ | ___ | ___ | ___ | ___ |
Recommended Rollout Sequence Based on Scores
Wave Assignment Criteria
| Composite Score | Wave Assignment | Rationale |
|---|---|---|
| 4.0–5.0 | Wave 1 (Pilot) | Highest readiness, lower risk of failure, best learning environment |
| 3.0–3.9 | Wave 2 | Good readiness, benefit from Wave 1 learnings |
| 2.5–2.9 | Wave 3 | Address readiness gaps identified in scoring before rollout |
| <2.5 | Remediation Required | Do not schedule until specific factors improved |
Wave 1 Selection Refinement
Beyond composite score, Wave 1 pilot locations should also meet these criteria: ☐ Geographic diversity (if relevant to your operations—different regions may have different challenges) ☐ Representative specialty mix (at least one general, one specialty if applicable) ☐ Different PMS systems represented (if your portfolio has variation) ☐ Regional manager who is supportive and available ☐ Not undergoing other major changes (renovation, leadership transition, etc.)
4. Rollout Strategy
Recommended Wave Structure
Overview
| Wave | # Locations | Timeline | Purpose |
|---|---|---|---|
| Wave 1 (Pilot) | 2–3 | Weeks 3–6 | Validate integration, training model, workflow; capture lessons |
| Wave 2 (Expansion) | 5–8 | Weeks 7–12 | Scale validated approach, stress-test support model |
| Wave 3 (Full Deployment) | Remaining | Weeks 13–20 | Efficient execution of proven playbook |
Wave 1: Pilot Phase (Weeks 3–6)
Selection Criteria for Wave 1 Locations: ☐ Composite readiness score ≥4.0 ☐ Patient volume score of 3–4 (meaningful throughput without overwhelming risk) ☐ Enthusiastic and capable local champion confirmed ☐ Office Manager tenure >1 year ☐ No major competing initiatives during pilot period ☐ Regional Manager willing to provide extra oversight ☐ 🟣 Geographic accessibility for in-person support visits (recommended for at least one pilot location)
Wave 1 Timeline:
| Week | Activities |
|---|---|
| Week 3 | 🔵 Technical installation and configuration; integration testing |
| Week 4 | Champion training; staff training; parallel workflow testing |
| Week 5 | Go-live; intensive support; daily check-ins |
| Week 6 | Stabilization; lessons learned documentation; Wave 2 refinement |
Wave 1 Success Metrics (Required for Go/No-Go Decision):
- ≥90% of imaging sessions using AI assist by end of week 2
- Zero critical integration failures lasting >4 hours
- ≥80% staff confidence rating (pulse survey)
- No patient complaints attributable to AI workflow
- Documented workflow adjustments captured and incorporated
Wave 2: Expansion Phase (Weeks 7–12)
Selection Criteria for Wave 2 Locations: ☐ Composite readiness score ≥3.0 ☐ No critical blockers identified in IT or Tech Stack factors ☐ Champion identified (may have lower experience than Wave 1) ☐ Can accommodate training schedule within timeline
Wave 2 Timeline:
| Week | Activities |
|---|---|
| Week 7 | Pre-work validation; champion training (train-the-trainer) for Wave 2 |
| Week 8–9 | Staggered installations (2–3 locations per week) 🔵 |
| Week 10 | Staff training delivery by local champions |
| Week 11 | Staggered go-lives (2–3 locations per week) |
| Week 12 | Stabilization; Wave 3 preparation |
Wave 2 Adjustments Based on Wave 1 Learnings:
- Updated training materials based on common questions
- Refined troubleshooting guides based on actual issues
- Adjusted configuration templates based on provider feedback
- Updated timeline estimates based on actual durations
Wave 3: Full Deployment (Weeks 13–20)
Wave 3 Approach:
- Deploy remaining locations in batches of 3–5 per week
- Champions from Wave 1 and 2 available as peer mentors
- Templated approach with minimal customization
- Central team shifts from hands-on support to escalation-only
Wave 3 Considerations for Lower-Readiness Locations: ☐ Pre-wave remediation activities (infrastructure upgrades, additional champion training) ☐ Extended parallel run period if staff adaptability score <3 ☐ On-site support for first 2 days of go-live if champion score <3 ☐ Weekly (vs. daily) check-ins may extend to 2 weeks for struggling locations
Go/No-Go Criteria Between Waves
Advancing from Wave 1 to Wave 2 🟣
| Criterion | Threshold | Evidence Required |
|---|---|---|
| Technical Stability | Zero unresolved critical issues | Issue log review |
| Workflow Integration | Documented workflow operating as designed | Champion sign-off |
| Staff Adoption | ≥80% staff reporting comfort with new workflow | Pulse survey results |
| Clinical Acceptance | Provider feedback neutral or positive | Provider interview or survey |
| Support Model | Vendor support responsiveness meeting SLA | Ticket response time analysis |
| Lessons Captured | Wave 1 retrospective completed | Documentation |
Decision Meeting: VP Operations + CDO + IT Director + Regional Managers involved in Wave 1
Advancing from Wave 2 to Wave 3 🟣
| Criterion | Threshold | Evidence Required |
|---|---|---|
| Technical Stability | Critical issues resolved within 24 hours | Issue log analysis |
| Train-the-Trainer Model | ≥90% of Wave 2 training delivered by champions | Training records |
| Workflow Consistency | Consistent workflow across Wave 1 and 2 locations | Workflow audit |
| Support Model Scaled | Vendor and internal support handled volume | Ticket volume and resolution metrics |
| Measurable Early Indicators | At least one leading indicator trending positive | Metrics dashboard |
Rollback Plan ⚠️
Critical for protecting patient care and organizational reputation if a wave encounters significant issues.
Rollback Triggers
| Trigger | Response | Decision Maker |
|---|---|---|
| Patient safety concern | Immediate local rollback + investigation | CDO + VP Operations |
| Critical integration failure affecting patient data | Pause wave, assess scope | IT Director + VP Operations |
| >50% of locations in a wave reporting critical issues | Pause wave, vendor escalation | VP Operations + CIO |
| Provider refusal to use system at ≥2 locations | Pause affected locations, investigate | CDO |
Rollback Procedure
- Communicate immediately to affected location(s) that parallel workflow should resume
- Document the specific issue(s) prompting rollback
- Notify vendor and engage escalation support 🔵
- Brief leadership within 24 hours (VP Operations, CDO, CEO as appropriate) 🟣
- Establish remediation plan with vendor and internal team
- Set criteria for re-engagement (what needs to be true before resuming)
- Communicate timeline to affected locations
Isolation Principle
Rollback at one location should NOT automatically trigger rollback at other locations unless:
- The issue is systemic (affecting the central platform)
- The issue is likely to occur at other locations due to shared configuration
5. Configuration & Integration (Weeks 2–3)
Step-by-Step Integration: Practice Management Systems
Dentrix Integration
| Step | Action | Owner | Est. Time |
|---|---|---|---|
| 1 | Verify Dentrix version (18.0+ required) | Location IT/Office Manager | 15 min |
| 2 | Install Planmeca Bridge module from Dentrix App Center | Central IT 🔵 | 30 min |
| 3 | Configure patient demographic sync (Name, DOB, Chart #) | Central IT | 30 min |
| 4 | Map procedure codes between Dentrix and Romexis | Clinical Lead | 1 hour |
| 5 | Test patient sync with 5–10 test patients | Local Champion | 1 hour |
| 6 | Configure automatic image attachment to patient record | Central IT | 30 min |
| 7 | Validate clinical notes integration (if applicable) | Clinical Lead | 30 min |
| 8 | ⚠️ Test in production with real patient (non-destructive test) | Local Champion | 30 min |
Eaglesoft Integration
| Step | Action | Owner | Est. Time |
|---|---|---|---|
| 1 | Verify Eaglesoft version (21.0+ required) | Location IT/Office Manager | 15 min |
| 2 | Install Planmeca Romexis TWAIN bridge | Central IT 🔵 | 45 min |
| 3 | Configure Eaglesoft > Imaging > External Imaging setup | Central IT | 30 min |
| 4 | Map patient identifiers (Account #, Chart #) | Central IT | 30 min |
| 5 | Test patient launch from Eaglesoft chart | Local Champion | 45 min |
| 6 | Configure image storage location (network path) | Central IT | 30 min |
| 7 | ⚠️ Validate image appears in patient chart post-capture | Local Champion | 30 min |
Open Dental Integration
| Step | Action | Owner | Est. Time |
|---|---|---|---|
| 1 | Verify Open Dental version (21.1+ required) | Location IT/Office Manager | 15 min |
| 2 | Configure Open Dental > Setup > Imaging Devices | Central IT | 30 min |
| 3 | 🔵 Obtain Planmeca bridge configuration file from vendor | Central IT | Varies |
| 4 | Configure bridge executable path and parameters | Central IT | 45 min |
| 5 | Test patient context launch | Local Champion | 30 min |
| 6 | Configure automatic image import path | Central IT | 30 min |
| 7 | Validate complete round-trip workflow | Local Champion | 45 min |
Imaging System Integration
Planmeca Hardware Configuration (Romexis)
| Step | Action | Owner | Est. Time |
|---|---|---|---|
| 1 | 🔵 Update Romexis to version 6.4.2+ (AI module compatible) | Planmeca Tech | 2 hours |
| 2 | 🔵 Install AI Analysis module license | Planmeca Tech | 30 min |
| 3 | Configure image acquisition defaults per modality | Clinical Lead + Planmeca | 1 hour |
| 4 | Enable AI auto-analysis on image capture | Central IT | 15 min |
| 5 | Configure AI finding sensitivity thresholds | CDO/Clinical Lead 🟣 | 1 hour |
| 6 | Set up AI report templates (what findings appear, format) | Clinical Lead | 2 hours |
| 7 | Configure cloud sync for centralized analytics | Central IT | 1 hour |
| 8 | Test complete imaging workflow (capture > AI analysis > PMS record) | Local Champion | 1 hour |
Third-Party Sensor/CBCT Integration
If locations have non-Planmeca imaging hardware:
☐ Verify DICOM compliance of third-party equipment ☐ 🔵 Confirm Planmeca AI supports the specific manufacturer/model ☐ Configure DICOM routing to Romexis ☐ ⚠️ Test AI analysis accuracy with third-party images (may have reduced feature set) ☐ Document any limitations for affected locations
Test Environment Setup
Recommended Approach: Centralized Test Environment
☐ 🔵 Request Planmeca provision a dedicated test tenant ☐ Populate with de-identified test patient data (minimum 100 records) ☐ Include representative images across modalities (PA, BW, Pano, CBCT) ☐ Configure test environment to mirror production settings ☐ Grant access to central IT team and Wave 1 champions
Validation Checklist (Execute in Test, Repeat in Production)
| Test | Expected Result | Pass/Fail |
|---|---|---|
| Patient demographic sync | Patient appears correctly in Romexis | ☐ |
| Image capture triggers AI | AI analysis appears within 30 seconds | ☐ |
| AI findings overlay display | Findings visible on image with clickable regions | ☐ |
| Findings report generation | PDF/structured report generated on demand | ☐ |
| Report attaches to PMS | Report accessible from patient chart | ☐ |
| Multiple image series | Workflow handles FMX, BWX, Pano sequentially | ☐ |
| CBCT analysis | 3D AI analysis completes within 5 minutes | ☐ |
| User permissions | Different user roles see appropriate features | ☐ |
| Concurrent users | System handles multiple simultaneous sessions | ☐ |
Data Migration / Historical Image Ingestion
Optional but high-value for retrospective analysis and AI training
Historical Image Assessment
☐ Inventory total historical images by location and modality ☐ Assess image format compatibility (DICOM, JPEG, proprietary) ☐ Estimate storage requirements for centralized ingestion ☐ 🟣 Decide: Full historical ingestion vs. forward-only vs. selective (recent 2 years)
- Recommendation: Forward-only for initial deployment; historical ingestion as Phase 2 project
If Proceeding with Historical Ingestion
☐ 🔵 Engage Planmeca data services team for migration support ☐ Export images in DICOM format where possible ☐ Map historical patient IDs to current PMS identifiers ☐ Execute batch import during off-hours ☐ Validate import accuracy (sample 5% of records) ☐ ⚠️ Do not delete source data until validation complete
Security and HIPAA Compliance Verification
Enterprise-Level HIPAA Checklist
| Requirement | Verification | Owner | Status |
|---|---|---|---|
| Business Associate Agreement (BAA) executed | Document on file | Legal | ☐ |
| Data encryption at rest (AES-256) | 🔵 Vendor confirmation | IT/Compliance | ☐ |
| Data encryption in transit (TLS 1.2+) | 🔵 Vendor confirmation | IT/Compliance | ☐ |
| Access logging enabled | Configuration verification | IT | ☐ |
| Audit log retention (6 years) | 🔵 Vendor policy confirmation | Compliance | ☐ |
| Data residency (US-based servers) | 🔵 Vendor confirmation | Compliance | ☐ |
| Breach notification procedures | Documented in BAA | Legal/Compliance | ☐ |
| User access termination process | Documented procedure | IT/HR | ☐ |
| Minimum necessary access configured | RBAC review | IT | ☐ |
| Risk assessment completed | Internal documentation | Compliance | ☐ |
Access Control Verification
☐ Verify terminated employee accounts are deactivated within 24 hours ☐ Confirm provider NPI/license validation in credentialing workflow ☐ Test that role restrictions function as configured (e.g., front desk cannot modify AI settings) ☐ Document access review schedule (quarterly recommended)
Configuration Standardization
Settings to Standardize Centrally
| Setting | Recommended Standard | Rationale |
|---|---|---|
| AI detection sensitivity | Medium (default) | Balance of sensitivity/specificity; adjust only with CDO approval |
| Findings display format | Overlay + sidebar | Consistent provider experience |
| Report template | Enterprise standard template | Consistent documentation |
| Auto-analysis trigger | On image capture | Immediate workflow integration |
| Cloud sync | Enabled | Required for centralized analytics |
| User timeout | 15 minutes | Security standard |
| Image retention | Per enterprise policy | Compliance consistency |
Settings Allowing Location Discretion
| Setting | Why Variable | Guardrails |
|---|---|---|
| Provider-specific finding display preferences | Individual workflow comfort | Must not disable AI entirely |
| Report generation timing (immediate vs. end of exam) | Workflow variation | Either option acceptable |
| Additional finding categories (specialty-specific) | Case mix differences | Additions only, not removals |
| Alert thresholds for specific conditions | Provider expertise variation | Minimum thresholds maintained |
6. Team Training Plan
Train-the-Trainer Model
Overview
Rather than centralizing all training, DSOs achieve faster deployment and better local adoption by certifying Location Champions to deliver training to their teams.
Champion Responsibilities:
- Complete comprehensive train-the-trainer certification
- Deliver role-specific training to all location staff
- Serve as first-line support for workflow questions
- Collect and escalate feedback to regional/central team
- Lead go-live day at their location
- Track training completion for their staff
Champion Selection Criteria
☐ Tenure at location ≥12 months ☐ Respected by both clinical and administrative team ☐ Demonstrated technology aptitude (not necessarily expertise) ☐ Willingness to dedicate time to implementation (estimate 10–15 hours during rollout) ☐ Available for 2-hour train-the-trainer session ☐ Able to attend office during go-live week (no PTO) ☐ Ideally: provider OR Office Manager (credibility with different audiences)
Champion Certification Process
| Step | Activity | Duration | Format |
|---|---|---|---|
| 1 | Complete Planmeca online learning modules | 2 hours | Self-paced 🔵 |
| 2 | Attend live train-the-trainer webinar | 2 hours | Virtual 🔵 |
| 3 | Practice teaching back core modules | 1 hour | Peer practice |
| 4 | Pass certification quiz (80% threshold) | 30 min | Online 🔵 |
| 5 | Receive trainer materials and presentation deck | — | Central team |
Standardized Training Materials (Centrally Developed)
Central team creates, Champions deliver locally:
Materials Package per Role
Providers (Dentists, Specialists):
- Training presentation deck (30 slides, 45-minute delivery)
- Clinical workflow video walkthrough (10 minutes)
- AI interpretation guide (how to read AI findings, confidence indicators)
- Override protocol documentation (when and how to disagree with AI)
- Day 1 cheat sheet (see below)
Hygienists:
- Training presentation deck (15 slides, 20-minute delivery)
- Hygienist touchpoint quick reference
- Patient communication script if they discuss images
- Day 1 cheat sheet
Front Desk / Office Manager:
- Training presentation deck (20 slides, 30-minute delivery)
- Administrative function guide (reporting, user management basics)
- Troubleshooting tier 1 guide
- Patient communication scripts
- Day 1 cheat sheet
Billing/Insurance Staff:
- Training presentation deck (10 slides, 15-minute delivery)
- Documentation requirements for AI-assisted diagnosis
- Code selection guidance (if AI impacts CDT code selection)
- Day 1 cheat sheet
Role-Specific Training Outlines (For Champion Delivery)
Providers (Dentists/Specialists) — 45 Minutes
Module 1: What Planmeca AI Does (10 min)
- Overview of AI detection capabilities (caries, bone loss, periapical pathology, anatomical landmarks)
- How AI complements (not replaces) clinical judgment
- Accuracy and confidence indicators explained
Module 2: Workflow Integration (15 min)
- Step-by-step: Patient seated → Image captured → AI analysis appears
- Reviewing AI findings on-screen
- Accepting, modifying, or overriding AI suggestions
- Documenting your clinical decision
Module 3: AI Interpretation Deep Dive (15 min)
- Reading confidence scores
- Understanding false positives and negatives
- When AI is most/least reliable
- Cases that require extra scrutiny
Module 4: Documentation and Liability (5 min)
- AI as clinical decision support, not autonomous diagnosis
- Documentation standards for AI-assisted findings
- Compliance with standard of care
Common Resistance Points & Responses:
| Resistance | Response |
|---|---|
| "This will slow me down" | Initial learning curve, but studies show 30% faster image review after 2 weeks |
| "I don't trust AI to diagnose" | AI doesn't diagnose—you do. It highlights areas for your review. |
| "What about liability?" | AI documentation supports your clinical decision-making. Override is always available and documented. |
| "My clinical skills are being replaced" | AI catches what you might see, plus occasional findings humans miss. Your expertise interprets and treatment plans. |
Hygienists — 20 Minutes
Module 1: AI in Your Workflow (10 min)
- When you'll see AI analysis (if acquiring images)
- What to communicate to the provider
- What NOT to communicate to patients (avoid diagnosing)
Module 2: Patient Communication (10 min)
- How to explain "the computer helps the doctor review your x-rays"
- Handling patient questions about AI
- When to defer to the provider
Common Resistance Points & Responses:
| Resistance | Response |
|---|---|
| "This isn't my job" | Your workflow doesn't change significantly. Awareness helps the whole team. |
| "Patients will ask me questions" | We'll give you scripts for common questions. Complex questions go to the provider. |
Front Desk / Office Manager — 30 Minutes
Module 1: Understanding the Technology (10 min)
- What the system does (high level)
- How it appears in the patient workflow
- What staff and patients will experience
Module 2: Administrative Functions (15 min)
- Accessing reports and usage dashboards
- Managing user accounts (if applicable)
- Basic troubleshooting (restart procedures, who to call)
Module 3: Patient Communication (5 min)
- Front desk scripts for patient questions
- Scheduling considerations (imaging appointments unchanged)
Common Resistance Points & Responses:
| Resistance | Response |
|---|---|
| "More technology to manage" | Day-to-day, it runs automatically. Admin is minimal. |
| "What if it breaks during a busy day?" | Rollback to manual workflow is simple. It's adding a layer, not replacing the core process. |
Billing/Insurance Staff — 15 Minutes
Module 1: Documentation Impact (10 min)
- How AI findings appear in clinical notes
- What documentation supports claims
- Any changes to imaging CDT codes (typically none)
Module 2: Claim Considerations (5 min)
- AI-assisted diagnosis doesn't change coding
- Documentation best practices for AI-supported treatment plans
Training Completion Tracking
Central Training Dashboard
| Location | Champion Certified | Providers Complete | Hygienists Complete | Front Desk Complete | Billing Complete | Ready for Go-Live |
|---|---|---|---|---|---|---|
| Loc 001 | ☐ | / | / | / | / | ☐ |
| Loc 002 | ☐ | / | / | / | / | ☐ |
Training Completion Requirements
- Providers: 100% completion required before location go-live
- Hygienists: 100% completion required before location go-live
- Front Desk: 100% completion required before location go-live
- Billing: Best effort; can complete within first week post-go-live
☐ Champion submits training completion attestation to Regional Manager ☐ Regional Manager verifies and updates central dashboard ☐ Central team confirms readiness before approving go-live date
Day 1 Cheat Sheets (Single Page Each)
Provider Day 1 Cheat Sheet
╔══════════════════════════════════════════════════════════════════╗
║ PLANMECA AI — PROVIDER QUICK REFERENCE ║
╠══════════════════════════════════════════════════════════════════╣
║ VIEWING AI FINDINGS ║
║ • Findings appear automatically after image capture ║
║ • Click any highlighted area to see detail ║
║ • Color coding: RED=High confidence | YELLOW=Moderate | BLUE=Low ║
║ ║
║ ACCEPTING/MODIFYING FINDINGS ║
║ • Click finding → "Accept" to confirm ║
║ • Click finding → "Modify" to adjust ║
║ • Click finding → "Dismiss" if false positive ║
║ ║
║ IMPORTANT REMINDERS ║
║ • AI is decision SUPPORT, not decision MAKER ║
║ • Your clinical judgment always takes precedence ║
║ • Document your clinical reasoning, especially if overriding ║
║ ║
║ HELP DESK ║
║ • First: Ask your Location Champion [NAME, EXTENSION] ║
║ • Second: Call IT support [NUMBER] ║
║ • Emergency: Vendor support [NUMBER] ║
╚══════════════════════════════════════════════════════════════════╝
Hygienist Day 1 Cheat Sheet
╔══════════════════════════════════════════════════════════════════╗
║ PLANMECA AI — HYGIENIST QUICK REFERENCE ║
╠══════════════════════════════════════════════════════════════════╣
║ YOUR WORKFLOW ║
║ • Acquire images as usual—AI runs automatically ║
║ • You'll see AI overlays appear—no action required from you ║
║ • Provider will review AI findings during exam ║
║ ║
║ PATIENT QUESTIONS — SAY THIS: ║
║ "Our imaging system has technology that helps the doctor ║
║ review your x-rays more thoroughly. They'll discuss anything ║
║ important with you during your exam." ║
║ ║
║ DO NOT: ║
║ • Interpret AI findings for patients ║
║ • Indicate whether AI "found something" ║
║ ║
║ SOMETHING WRONG? ║
║ • Images not capturing: Restart Romexis software ║
║ • AI not appearing: Continue as normal, notify Champion ║
║ ║
║ CHAMPION: [NAME, EXTENSION] ║
╚══════════════════════════════════════════════════════════════════╝
(Similar cheat sheets for Front Desk and Billing, tailored to their workflows)
Ongoing Training Cadence
New Hire Training
| When | What | Who Delivers | Duration |
|---|---|---|---|
| Day 1 | Include in orientation: Planmeca AI overview | Office Manager | 15 min |
| Week 1 | Complete role-specific training module | Location Champion | Per role |
| Week 1 | Supervised use of system | Champion or peer | Ongoing |
| Week 2 | Competency verification | Champion | 15 min |
Quarterly Refreshers
- 15-minute video update on any new features or workflow changes
- Distributed by central team, tracked by champions
- Required viewing with attestation
Annual Retraining
- All staff complete updated training module annually
- Incorporates lessons learned, best practices, updates
- Tracked in training dashboard
7. Change Management
Executive Sponsor Communication Plan
Board/Investor Updates 🟣
| Frequency | Content | Format | Owner |
|---|---|---|---|
| Monthly (during implementation) | Rollout status, locations live, early indicators | Email summary + dashboard link | VP Operations |
| Quarterly | Full progress report, ROI tracking, strategic narrative | Board deck (5 slides) | CEO + VP Operations |
| Ad hoc | Material issues or acceleration opportunities | Direct communication | CEO |
Key Messages for Board/Investors:
- AI investment positions the organization for competitive advantage in diagnostics
- Standardized detection improves clinical quality and reduces variation
- Data aggregation enables portfolio-level insights unavailable to independent practices
- Early indicators suggest [X% improvement in Y metric]
CEO/C-Suite Updates 🟣
| Frequency | Content | Format |
|---|---|---|
| Bi-weekly | Wave progress, blockers, resource needs | Standup meeting (15 min) |
| Weekly (during go-live weeks) | Daily status as needed | Slack/email update |
| Monthly | Consolidated progress report | Written summary |
Regional Manager Briefing Guide
Use this template to cascade rollout information to regional managers.
Pre-Wave Briefing Agenda (30 minutes)
- Overview: Which locations in this wave, timeline (5 min)
- Location Readiness: Summary of readiness scores, any concerns (5 min)
- Your Role: What Regional Manager needs to do before, during, after go-live (10 min)
- Resources: Champion contacts, support escalation, training materials (5 min)
- Q&A (5 min)
Regional Manager Responsibilities
| Phase | Responsibility |
|---|---|
| Pre-Wave | Confirm champion readiness; ensure Office Manager aware of timeline |
| During Rollout | Available for escalation; conduct daily check-in with champions in wave |
| Go-Live Week | Physically visit at least one location (if practical); available by phone |
| Post-Launch | Weekly review of location metrics; address adoption issues |
Escalation Authority
Regional Managers have authority to:
- Delay a location's go-live by up to 1 week for readiness issues
- Approve local workflow variations within guardrails
- Request additional support resources for struggling locations
Regional Managers must escalate to VP Operations:
- Requests to skip or indefinitely delay a location
- Provider resistance requiring CDO involvement
- Resource requests exceeding budget
Multi-Location Staff Resistance Framework
Anticipating Resistance Patterns
| Resistance Type | Common Manifestation | Likely Locations | Intervention |
|---|---|---|---|
| Fear of Job Loss | "Will AI replace me?" | Lower-tenure staff | Clear messaging: AI augments, doesn't replace |
| Clinical Skepticism | "AI can't diagnose like I can" | Experienced providers | Emphasize decision support; share validation data |
| Workflow Disruption | "This will slow me down" | High-volume locations | Focus on efficiency gains after learning curve |
| Technology Anxiety | "I'm not good with computers" | Older staff, high-turnover locations | Extra training time; peer buddy system |
| Change Fatigue | "Another new system" | Locations with recent changes | Acknowledge fatigue; emphasize stability post-implementation |
Intervention Toolkit
For Individual Resistance:
- Champion has 1:1 conversation to understand specific concerns
- Address concerns with tailored information (provide talking points to champions)
- If unresolved, Regional Manager conversation
- For providers: CDO peer conversation if needed
For Location-Wide Resistance:
- Office Manager and Champion assess root cause
- Regional Manager visit to reinforce commitment and address concerns
- Consider delaying go-live until addressed (not indefinitely)
- Document learnings for other locations
⚠️ Warning Signs of Systemic Resistance:
- Champion resignation or disengagement
- Office Manager actively or passively undermining
- Multiple providers at same location expressing concerns
- Staff turnover spike during rollout period
Internal Marketing
Naming the Initiative
Create a simple, memorable name for the rollout. Suggestions:
- "Clarity Initiative" (emphasizes diagnostic clarity)
- "See More" (simple, describes the value)
- "[DSO Name] AI Imaging Upgrade" (direct)
Why It Matters: A named initiative creates shared identity, easier reference in communications, and sense of progress.
Creating Momentum
| Tactic | When | Owner |
|---|---|---|
| Kickoff announcement from CEO | Week 1 | CEO |
| Champion spotlight in internal newsletter | Monthly | Marketing/Comms |
| "Go-live day" celebration (small) | Each go-live | Office Manager |
| Metrics milestones shared | Monthly | VP Operations |
| Provider testimonial video | After Wave 1 | Marketing/Comms |
Celebrating Milestones
| Milestone | Celebration | Communication |
|---|---|---|
| Wave 1 complete | Lunch/gift cards for pilot location staff | Company-wide announcement |
| 50% locations live | Mid-point celebration | CEO video message |
| 100% locations live | Full completion recognition | All-hands meeting mention; bonuses for champions |
| First ROI results | Share data widely | Board update; staff communication |
8. Go-Live Day Runbook
Standardized Go-Live Checklist (Every Location)
Pre-Go-Live (Day Before)
| Time | Action | Owner | Verify |
|---|---|---|---|
| AM | Final configuration verification | Central IT | ☐ |
| AM | Test patient workflow end-to-end | Champion | ☐ |
| Noon | Confirm all staff completed training | Champion | ☐ |
| PM | Brief entire team on tomorrow's plan | Champion | ☐ |
| PM | Verify support contact information posted | Office Manager | ☐ |
| EOD | Final system check, verify integrations active | Central IT | ☐ |
Go-Live Day: Hour-by-Hour Schedule
| Time | Activity | Who | Notes |
|---|---|---|---|
| 30 min before open | System verification—all workstations | Champion | |
| Opening | Brief team huddle (5 min) | Champion | Confirm everyone knows their role |
| First 2 hours | Champion shadows all imaging sessions | Champion | Hands-on support |
| Mid-morning | First check-in with Regional Manager | Champion | Report any issues |
| Noon | Team check-in—gather initial feedback | Champion | |
| Noon | Lunch break—Regional Manager call | Champion | Status update |
| Afternoon | Champion available for questions (not shadowing) | Champion | |
| 3 PM | Check-in with Central Team | Champion | Log issues, questions |
| End of day | Team debrief (10 min) | Champion | What worked, what didn't |
| After close | Submit Go-Live Day report | Champion | Standard form |
Who Needs to Be On-Site or On-Call
| Role | Location | Availability | Contact |
|---|---|---|---|
| Location Champion | On-site | Full day | [Mobile] |
| Office Manager | On-site | Full day | [Mobile] |
| Regional Manager | On-call (phone) | Full day | [Mobile] |
| Central IT Support | On-call (remote) | Full day | [Support line] |
| Vendor Support | On-call (remote) | Full day | [Vendor support line] 🔵 |
| VP Operations | On-call (escalation) | As needed | [Mobile] |
Known Gotchas and Troubleshooting
Common First-Day Issues
| Issue | Symptoms | Solution | Resolution Time |
|---|---|---|---|
| ⚠️ AI analysis not appearing | Image captures but no overlay | Verify AI module active; restart Romexis; check internet | 5–15 min |
| ⚠️ Slow analysis | AI overlay takes >60 seconds | Check network speed; reduce other network traffic | 5 min |
| Patient data mismatch | Wrong patient in Romexis | Verify PMS bridge launching correctly; re-launch from PMS | 2 min |
| Integration failure | Images not syncing to PMS | Restart bridge service; verify credentials | 10–20 min |
| Workstation performance | System sluggish | Close unnecessary applications; verify hardware meets spec | 5 min |
| Provider can't see findings | Blank overlay | Verify user permissions; refresh display | 5 min |
| ⚠️ Critical: System unresponsive | Romexis won't launch | Restart workstation; call IT if unresolved | 15 min; escalate |
Escalation Tiers
Tier 1: Location Champion (resolve in <15 min)
- First-line troubleshooting
- User questions and workflow support
- Basic system restarts
Tier 2: Regional Manager + Central IT (resolve in <1 hour)
- Issues Champion cannot resolve
- Configuration questions
- Multi-user or location-wide issues
Tier 3: Vendor Support 🔵 (resolve in <4 hours)
- Software bugs
- Integration failures
- Issues requiring code or backend changes
Tier 4: VP Operations + CDO (as needed)
- Decisions about workflow changes
- Provider escalations
- Decision to pause or rollback
First-Week Daily Check-In Protocol
Daily Check-In Format (Champion → Regional Manager → Central Team)
Submit by End of Each Day (Days 1–5):
LOCATION: _______________
DATE: _______________
IMAGING SESSIONS TODAY: _______________
AI ANALYSIS USED: _____ / _____ (XX%)
ISSUES ENCOUNTERED:
[ ] None
[ ] Minor (describe): _______________
[ ] Major (describe): _______________
ISSUE STATUS:
[ ] Resolved
[ ] Pending—help needed
STAFF FEEDBACK (1 = Struggling, 5 = Confident):
Providers: ___
Hygienists: ___
Front Desk: ___
PATIENT FEEDBACK:
[ ] No comments
[ ] Positive comments: _______________
[ ] Concerns: _______________
CHAMPION CONFIDENCE (1–5): ___
ANYTHING NEEDED FROM CENTRAL TEAM?
_______________
Central Team Aggregation
Central team compiles all location reports daily during go-live weeks and produces:
- Daily summary for VP Operations
- Issue tracker for unresolved items
- Trend analysis across locations
Patient Communication Script (If Patient-Facing)
Use when patients notice AI overlays or ask about the technology.
For Providers:
"You might notice some highlights on your x-ray images. We've implemented advanced imaging software that helps me review your x-rays more thoroughly. It's similar to spell-check for documents—it highlights areas for me to look at, but I make all the clinical decisions. It's just another tool to make sure we don't miss anything important for your health."
For Front Desk (if patients ask):
"Our office has upgraded to an advanced imaging system that helps our doctors review x-rays more carefully. It's part of our commitment to providing you with the best care. The doctor will explain anything they find during your appointment."
For Hygienists:
"Yes, we have new imaging technology that assists Dr. [Name] in reviewing your x-rays. They'll go over everything with you during your exam."
9. Post-Launch Optimization (Weeks 4–8)
Weekly Metrics Review Cadence
Week-by-Week Focus
| Week | Focus Area | Key Metrics | Review Owner |
|---|---|---|---|
| Week 1 | Stabilization | System uptime, usage rate, critical issues | Central IT + Champion |
| Week 2 | Adoption | Usage rate trending, staff confidence | Regional Manager + Champion |
| Week 3 | Workflow | Time-in-workflow, provider feedback | Champion + Office Manager |
| Week 4 | Early Outcomes | Case acceptance (early), patient feedback | Regional Manager |
| Week 5–6 | Optimization | Identify workflow refinements needed | VP Operations review |
| Week 7–8 | ROI Readiness | Compile metrics for 60-day review | Central Team |
30-Day Checkpoint
What "Good" Looks Like at 30 Days
| Metric | Target | Red Flag |
|---|---|---|
| AI usage rate | ≥90% of eligible imaging sessions | <70% |
| System uptime | ≥99% | <95% |
| Staff confidence (survey) | ≥4.0/5.0 average | <3.0 |
| Provider adoption | 100% of providers using regularly | Any provider refusing |
| Critical issues | Zero unresolved critical issues | >1 unresolved |
| Workflow time | No increase vs. baseline OR <10% increase | >25% increase |
| Patient complaints | Zero AI-related complaints | Multiple complaints |
30-Day Review Meeting Agenda (Per Location)
- Metrics review vs. targets (10 min)
- Champion and Office Manager qualitative feedback (10 min)
- Provider feedback summary (10 min)
- Issues and resolutions (10 min)
- Workflow refinements needed (10 min)
- Next steps and support needs (10 min)
60-Day Checkpoint: ROI Assessment Framework
ROI Measurement Framework
| Metric | Baseline (Pre-Implementation) | 60-Day Actual | % Change | Notes |
|---|---|---|---|---|
| Case Acceptance Rate | __% | __% | ___% | Primary revenue driver |
| Avg Diagnosis Time | __ min | __ min | ___% | Efficiency gain |
| Radiographic Findings/Exam | __ | __ | ___% | Detection improvement |
| Claim Denial Rate (Imaging) | __% | __% | ___% | Documentation quality |
| Retake Rate | __% | __% | ___% | Quality improvement |
| CBCT Utilization | __% | __% | ___% | Appropriate technology use |
Calculating Value
Incremental Revenue Model:
- Baseline case acceptance: ___% → 60-day acceptance: ___%
- Average treatment value: $___
- Monthly treatment presentations: ___
- Monthly incremental revenue = (New % - Old %) × Presentations × Avg Value
Efficiency Savings Model:
- Time saved per imaging session: ___ minutes
- Sessions per day: ___
- Value of provider time per minute: $___
- Monthly efficiency value = Sessions × Time Saved × Days × Value/Min
60-Day Review Report Structure 🟣
- Executive Summary: One paragraph on overall status
- Metrics Dashboard: Table above with all locations
- ROI Calculation: Estimated value created to date
- Success Stories: 2–3 specific clinical or operational wins
- Challenges and Remediations: Honest assessment of issues and how they were addressed
- Recommendations: Any proposed changes to workflow or configuration
- Next 60-Day Outlook: What to expect as deployment matures
Staff Feedback Collection
5-Question Pulse Survey (Administer at Day 7, Day 30, Day 60)
PLANMECA AI — STAFF FEEDBACK SURVEY
Location: _______________
Role: [ ] Provider [ ] Hygienist [ ] Front Desk [ ] Billing [ ] Other
Date: _______________
1. How confident do you feel using the AI imaging system?
[ ] 1 - Not confident [ ] 2 [ ] 3 - Neutral [ ] 4 [ ] 5 - Very confident
2. Has the AI system made your job easier, harder, or no change?
[ ] Much easier [ ] Somewhat easier [ ] No change [ ] Somewhat harder [ ] Much harder
3. How well did the training prepare you to use the system?
[ ] 1 - Not at all [ ] 2 [ ] 3 - Somewhat [ ] 4 [ ] 5 - Very well
4. How responsive has support been when you have questions or issues?
[ ] 1 - Very poor [ ] 2 [ ] 3 - Adequate [ ] 4 [ ] 5 - Excellent
5. What one thing would most improve your experience with the AI system?
_______________________________________________
Using Feedback Data
- Aggregate by location and role for pattern identification
- Share location-specific results with Champions and Office Managers
- Escalate consistent negative feedback to Regional Manager
- Incorporate feedback into workflow refinements and future training
Common Workflow Refinements (First 30–60 Days)
Based on typical implementation patterns, anticipate these refinements:
| Refinement | When It Arises | Action |
|---|---|---|
| AI sensitivity adjustment | Providers report too many/few findings | CDO reviews and approves sensitivity changes (centrally) 🟣 |
| Report format preferences | Providers want different information display | Add customization within approved templates |
| Workflow sequencing | AI analysis timing doesn't fit exam flow | Adjust when analysis triggers (immediate vs. on demand) |
| Integration timing | PMS sync delays cause confusion | Tune sync frequency or trigger events |
| Training gaps | Specific tasks confusing to staff | Create micro-training videos for specific topics |
| Override documentation | Providers uncertain how to document overrides | Create quick reference for override workflow |
Centralized Dashboard Structure
Location-Level Metrics (Visible to Office Manager, Champion, Regional Manager)
| Metric | Week 1 | Week 2 | Week 3 | Week 4 | Trend |
|---|---|---|---|---|---|
| Usage Rate | __% | __% | __% | __% | ↑↓→ |
| Uptime | __% | __% | __% | __% | ↑↓→ |
| Staff Confidence | ___ | ___ | ___ | ___ | ↑↓→ |
| Issues Logged | ___ | ___ | ___ | ___ | ↑↓→ |
| (Future) Case Acceptance | __% | __% | __% | __% | ↑↓→ |
Portfolio Aggregate Dashboard (Visible to Central Team, C-Suite)
| Metric | All Locations | Top Quartile | Bottom Quartile | Target |
|---|---|---|---|---|
| Usage Rate | __% | __% | __% | 95% |
| Uptime | __% | __% | __% | 99% |
| Avg Staff Confidence | ___ | ___ | ___ | 4.0+ |
| Locations Fully Live | / | — | — | 100% by Week ___ |
| ROI Indicators | ___ | ___ | ___ | Varies |
Quarterly Business Review Framework (Post Full Deployment)
| QBR Element | Content | Presenter |
|---|---|---|
| Performance Summary | Metrics vs. targets for quarter | VP Operations |
| ROI Analysis | Calculated return by location and aggregate | Finance |
| Clinical Impact | Quality metrics, detection improvements, case studies | CDO |
| Operational Insights | What's working, what needs attention | Regional Managers |
| Vendor Relationship | Support performance, product feedback, roadmap | IT Director |
| Strategic Recommendations | Proposed changes for next quarter | VP Operations + CDO |
| Board-Ready Summary | 1-page summary for board distribution | CEO |
10. Centralized vs. Localized Decision Framework
| Decision Area | Standardize Centrally | Allow Local Discretion |
|---|---|---|
| AI detection sensitivity thresholds | ✅ CDO sets enterprise defaults | ❌ Changes require CDO approval |
AI-generated implementation guide based on public vendor information. Verify specifics directly with Planmeca.