Relu
Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
Relu — Implementation Playbook (DSO)
Relu AI Treatment Planning Implementation Playbook
For Dental Service Organizations (DSOs)
1. Executive Summary
What Relu Does
Relu is an AI-powered treatment planning platform that transforms 2D dental imaging (panoramic X-rays, cephalometric images, and CBCT scans) into precise 3D digital models for implant planning, orthodontic analysis, and restorative treatment design. The platform automates anatomical segmentation, nerve mapping, and bone density analysis, reducing treatment planning time from hours to minutes while standardizing clinical outputs across providers.
Why DSOs Specifically Benefit from AI Treatment Planning
Scale Advantages:
- Standardized treatment planning protocols across 15–50+ locations eliminate provider-to-provider variability that drives patient complaints and clinical inconsistencies
- Centralized quality control enables Chief Dental Officers to audit treatment plans across the entire network without site visits
- Volume pricing and enterprise licensing reduce per-seat costs by 30–50% compared to single-practice deployments
Standardization Benefits:
- Every implant case follows the same AI-assisted workflow regardless of which location or provider handles it
- Training new associates becomes faster when AI provides consistent guardrails and visual guidance
- Reduces reliance on individual provider expertise — a critical advantage given associate turnover rates
Data Aggregation Opportunities:
- Aggregate treatment planning data reveals network-wide patterns: which case types convert best, where clinical bottlenecks exist, which locations under-diagnose
- Benchmarking across locations enables identification of top performers and struggling sites
- Predictive analytics on case complexity and treatment outcomes become possible at scale
Expected Timeline: Decision to Full Deployment
| Phase | Timeline | Locations Covered |
|---|---|---|
| Pre-implementation & Pilot Prep | Weeks 1–3 | — |
| Wave 1 Pilot | Weeks 4–7 | 2–3 locations |
| Wave 1 Evaluation & Wave 2 Prep | Week 8 | — |
| Wave 2 Rollout | Weeks 9–13 | 5–8 locations |
| Wave 3 Rollout | Weeks 14–20 | Remaining locations |
| Network-wide Optimization | Weeks 21–24 | All locations |
Total Timeline: 5–6 months for a 25-location DSO; 7–8 months for 40+ locations
2. Pre-Implementation Checklist (Weeks 1–2)
Technical Requirements
Hardware Requirements (Per Location)
☐ Workstation with minimum specs: Intel i7 (10th gen+) or AMD Ryzen 7, 32GB RAM, dedicated GPU (NVIDIA GTX 1660 or better), SSD storage ☐ Minimum 2 monitors (recommended: 27" 4K for treatment planning visualization) ☐ High-resolution scanner for physical models if converting to digital workflow (if applicable)
Software Requirements
☐ Windows 10/11 Professional (64-bit) — macOS support limited; verify with vendor 🔵 ☐ Current versions of integrated PMS (Dentrix G7+, Eaglesoft 21+, Open Dental 22.1+) ☐ DICOM-compatible imaging software (Romexis, Sidexis, Carestream, or compatible alternative) ☐ Chrome or Edge browser (latest version) for cloud-based portal access
Network Requirements ⚠️
☐ Minimum 100 Mbps upload/download per location (CBCT file transfers are large) ☐ Static IP or VPN configuration for enterprise security requirements ☐ Firewall whitelist for Relu cloud endpoints (obtain list from vendor 🔵) ☐ Verify HIPAA-compliant cloud storage compliance (Relu uses AWS/Azure — confirm with your security team)
Integration Requirements
☐ PMS API access enabled and credentials documented ☐ Imaging system DICOM export configured and tested ☐ HL7/FHIR interface availability confirmed (if using enterprise health record system)
Vendor Onboarding Steps
| Step | Owner | Vendor Contact | Timeline |
|---|---|---|---|
| ☐ Execute enterprise licensing agreement 🟣 | Legal/CFO | Relu Enterprise Sales | Week 1 |
| ☐ Establish dedicated Customer Success Manager (CSM) | VP Operations | 🔵 Relu CSM Team | Week 1 |
| ☐ Schedule technical kickoff call | IT Director | 🔵 Relu Implementation Lead | Week 1 |
| ☐ Obtain enterprise admin credentials | IT Director | 🔵 Relu CSM | Week 1 |
| ☐ Review SLA and support escalation matrix | IT Director | 🔵 Relu Support | Week 1 |
| ☐ Confirm training resource availability | L&D/Training Lead | 🔵 Relu Training Team | Week 2 |
Key Contacts to Establish
- Relu Customer Success Manager: Primary relationship owner for rollout
- Relu Technical Support (Tier 1): Day-to-day troubleshooting
- Relu Implementation Engineer: Integration and configuration
- Relu Clinical Specialist: Provider training and clinical workflow design
- Relu Enterprise Account Executive: Escalation path for contractual or priority issues
Data/Access Prerequisites
☐ Enterprise admin account with multi-location management privileges ☐ SSO integration (SAML 2.0) configured with your identity provider 🔵 ⚠️ ☐ API keys generated for each PMS integration ☐ Imaging archive access credentials (PACS or local DICOM server) ☐ Historical case data export (if migrating existing treatment plans) ☐ User provisioning list: all providers, hygienists, and admin staff by location
Internal Stakeholder Alignment
Stakeholder Alignment Map 🟣
| Stakeholder Group | Role in Implementation | Communication Cadence |
|---|---|---|
| Board/Investors | Approve budget; receive ROI updates | Quarterly summary |
| C-Suite (CEO, CFO, CDO) | Strategic sponsor; final go/no-go | Bi-weekly briefings |
| VP of Operations | Implementation owner; removes blockers | Weekly standups |
| IT Director | Technical integration lead | Daily during integration |
| Regional Managers | Cascade communication; manage local adoption | Weekly during rollout |
| Office Managers | Local implementation champion | Daily during go-live |
| Providers (Dentists) | End users; clinical adoption | Training + ongoing |
| Hygienists | Secondary users; workflow integration | Training + ongoing |
| Front Desk/Billing | Administrative workflow changes | Training + ongoing |
Required Approvals Before Proceeding
☐ Budget approval from CFO 🟣 ☐ Clinical workflow approval from Chief Dental Officer 🟣 ☐ IT security approval from IT Director ☐ Legal/compliance approval (BAA executed, vendor security reviewed) 🟣 ☐ Regional manager acknowledgment of rollout timeline
Baseline Metrics to Capture ⚠️
Critical: Capture these metrics BEFORE go-live to enable ROI measurement. Standardize measurement methodology across all locations.
Clinical Metrics (Per Location)
| Metric | How to Measure | Source System |
|---|---|---|
| Implant case acceptance rate | Cases accepted ÷ Cases presented (trailing 90 days) | PMS |
| Average treatment planning time | Time from imaging to plan presentation | Manual tracking / PMS timestamps |
| Restorative case value | Average $ per restorative treatment plan | PMS |
| Case re-planning rate | % of cases requiring revised treatment plans | Manual tracking |
Operational Metrics (Per Location)
| Metric | How to Measure | Source System |
|---|---|---|
| Provider chair time per case | Minutes from patient seated to plan complete | Scheduling system |
| Imaging retake rate | % of images requiring rescan | Imaging system |
| Lab case remake rate | % of lab cases requiring redo | Lab management |
Financial Metrics (Network-Wide)
| Metric | How to Measure | Source System |
|---|---|---|
| Revenue per provider per day | Total production ÷ provider days worked | PMS |
| Claim denial rate for implant/restorative procedures | Denied claims ÷ submitted claims | RCM system |
| Lab costs as % of production | Lab expenses ÷ production | Accounting system |
Standardization Requirement: Create a baseline metrics template that every location completes using identical definitions and date ranges. Assign one analyst to validate data quality before proceeding.
Enterprise-Level Requirements
Network Standards Across Locations
☐ Verify each location meets 100 Mbps bandwidth requirement (conduct speed tests) ⚠️ ☐ Confirm firewall rules can be standardized across locations ☐ Identify locations on legacy network infrastructure requiring upgrades
Centralized vs. Location-Level Hosting Decision 🟣
| Approach | Pros | Cons | Recommendation |
|---|---|---|---|
| Fully Centralized (Cloud) | Easier updates, centralized data, lower IT burden | Requires reliable internet, latency for large files | ✅ Recommended for most DSOs |
| Hybrid (Cloud + Local Cache) | Faster local performance, offline fallback | More complex, higher IT maintenance | Consider for rural/low-bandwidth locations |
| Fully Local | Maximum speed, no internet dependency | High IT burden, difficult to standardize, no central visibility | Not recommended |
SSO Configuration
☐ Integrate Relu with your identity provider (Okta, Azure AD, Google Workspace) 🔵 ☐ Define role-based access levels: Admin, Provider, Clinical Staff, View-Only ☐ Configure automatic user provisioning/deprovisioning
Centralized Credentialing
☐ Map provider NPI numbers to Relu user accounts ☐ Configure digital signature capabilities if using Relu for patient-facing documents ☐ Establish audit trail requirements for compliance
3. Location Readiness Assessment
Scoring Framework
Score each location 1–5 on the following factors, then calculate a composite readiness score.
Factor 1: IT Infrastructure Maturity
| Score | Criteria |
|---|---|
| 5 | Fiber internet (200+ Mbps), workstations < 2 years old, current PMS version, DICOM fully configured |
| 4 | 100+ Mbps internet, workstations < 3 years old, PMS one version behind, DICOM functional |
| 3 | 50–100 Mbps internet, mixed workstation ages, PMS 2+ versions behind, DICOM requires configuration |
| 2 | 25–50 Mbps internet, most workstations > 4 years old, PMS significantly outdated |
| 1 | < 25 Mbps internet, workstations require replacement, PMS incompatible, no DICOM infrastructure |
Factor 2: Staff Tenure and Adaptability
| Score | Criteria |
|---|---|
| 5 | < 15% annual turnover, prior successful tech adoption, documented tech comfort among staff |
| 4 | 15–25% turnover, prior tech adoption with minor issues, generally positive tech attitude |
| 3 | 25–35% turnover, mixed tech adoption history, some resistant staff members |
| 2 | 35–50% turnover, prior failed tech implementations, significant resistance anticipated |
| 1 | > 50% turnover, no stable staff base, history of tech adoption failures |
Factor 3: Patient Volume
| Score | Criteria |
|---|---|
| 5 | 60+ patients/day, high case complexity, significant implant/restorative volume — maximum impact |
| 4 | 45–60 patients/day, moderate case complexity, growing specialty services |
| 3 | 30–45 patients/day, standard case mix, average complexity |
| 2 | 15–30 patients/day, lower complexity, fewer cases to benefit from AI |
| 1 | < 15 patients/day, minimal complexity, limited ROI potential |
Factor 4: Existing Tech Stack Compatibility
| Score | Criteria |
|---|---|
| 5 | PMS and imaging systems on Relu's certified integration list, prior API integrations successful |
| 4 | Primary systems compatible, minor configuration needed |
| 3 | Primary PMS compatible, imaging system requires workaround or manual DICOM export |
| 2 | PMS requires upgrade for compatibility, imaging integration unclear |
| 1 | PMS incompatible, imaging system incompatible, significant work required |
Factor 5: Local Champion Availability
| Score | Criteria |
|---|---|
| 5 | Tech-forward provider AND office manager identified, both enthusiastic, prior champion experience |
| 4 | Strong provider OR office manager champion identified, supportive leadership |
| 3 | Potential champion identified but unconfirmed, willingness uncertain |
| 2 | No obvious champion, leadership neutral or distracted by other priorities |
| 1 | No champion, leadership resistant or actively opposed |
Composite Readiness Score Calculation
Formula: (IT Score × 1.5) + (Staff Score × 1.5) + (Volume Score × 1.0) + (Tech Stack Score × 1.5) + (Champion Score × 1.5) = Total Score (out of 35)
Score Interpretation
| Composite Score | Readiness Tier | Rollout Recommendation |
|---|---|---|
| 28–35 | Tier A: High Readiness | Wave 1 candidate |
| 21–27 | Tier B: Moderate Readiness | Wave 2 candidate |
| 14–20 | Tier C: Low Readiness | Wave 3 with remediation |
| < 14 | Tier D: Not Ready | Defer until remediation complete |
Sample Location Assessment Table
| Location | IT (×1.5) | Staff (×1.5) | Volume (×1.0) | Tech (×1.5) | Champion (×1.5) | Total | Tier |
|---|---|---|---|---|---|---|---|
| Downtown Main | 5 (7.5) | 4 (6.0) | 5 (5.0) | 5 (7.5) | 5 (7.5) | 33.5 | A |
| Suburban East | 4 (6.0) | 4 (6.0) | 4 (4.0) | 4 (6.0) | 4 (6.0) | 28.0 | A |
| Northside Family | 3 (4.5) | 3 (4.5) | 4 (4.0) | 4 (6.0) | 3 (4.5) | 23.5 | B |
| Rural West | 2 (3.0) | 3 (4.5) | 2 (2.0) | 2 (3.0) | 2 (3.0) | 15.5 | C |
| New Acquisition | 1 (1.5) | 2 (3.0) | 3 (3.0) | 1 (1.5) | 1 (1.5) | 10.5 | D |
Recommended Rollout Sequence
Based on composite scores, select 2–3 Tier A locations for Wave 1, ensuring:
- At least one location represents your most common location profile (suburban GP, urban specialty, etc.)
- Geographic distribution allows regional managers to observe without excessive travel
- Champion availability is confirmed (not just assumed)
Avoid selecting ONLY your "best" locations for Wave 1 — you need learnings that transfer to more challenging sites.
4. Rollout Strategy
Wave Structure Recommendation
Wave 1: Pilot (Weeks 4–7)
- Locations: 2–3 Tier A sites
- Purpose: Validate integration, refine training, identify unexpected issues
- Duration: 4 weeks (including 2-week parallel run)
Wave 2: Expansion (Weeks 9–13)
- Locations: 5–8 Tier A/B sites
- Purpose: Scale with learnings, stress-test support capacity
- Duration: 5 weeks (including 1-week parallel run — shortened based on Wave 1 learnings)
Wave 3: Broad Rollout (Weeks 14–20)
- Locations: All remaining Tier B/C sites
- Purpose: Complete network deployment
- Duration: 6 weeks (staggered starts, 3–5 locations per week)
Wave 4: Remediation (If Needed)
- Locations: Tier D sites after infrastructure/staffing remediation
- Purpose: Bring stragglers online
- Duration: Variable
Wave 1 Pilot Location Selection Criteria 🟣
| Criterion | Why It Matters |
|---|---|
| Composite Score 28+ | Maximizes chance of smooth pilot |
| Representative case mix | Learnings must transfer to other locations |
| Strong local champion | Will own success and evangelize to peers |
| Accessible location | Regional managers and central team can visit easily |
| Not your flagship | Flagship failure creates disproportionate negative momentum |
| Manageable risk | Avoid highest-volume location initially — stakes too high |
Recommended Wave 1 Profile: 2 mid-to-high volume locations with strong champions, one slightly different from the other (e.g., one GP-focused, one with implant specialty).
Timeline Per Wave
Wave 1 Detailed Timeline
| Week | Activities |
|---|---|
| Week 4 | Integration validation, staff training, champion certification |
| Week 5 | Parallel run begins (AI + existing workflow simultaneously) |
| Week 6 | Parallel run continues, daily check-ins, issue resolution |
| Week 7 | Full cutover to Relu-primary workflow, intensive monitoring |
Wave 2–3 Timeline (Per Wave)
| Week | Activities |
|---|---|
| Week N | Champion training (virtual, based on Wave 1 certified trainers) |
| Week N+1 | Integration + configuration (can parallelize across locations) |
| Week N+2 | Parallel run (shortened to 1 week based on Wave 1 learnings) |
| Week N+3 | Full cutover + daily monitoring |
| Week N+4 | Stabilization + handoff to standard support |
Buffer Between Waves: Minimum 1 week between Wave 1 completion and Wave 2 start for retrospective and playbook updates.
Go/No-Go Criteria 🟣
Criteria to Advance from Wave 1 to Wave 2
| Criterion | Threshold | Owner |
|---|---|---|
| Integration stability | Zero critical errors in final 5 days of Wave 1 | IT Director |
| Provider adoption | 100% of Wave 1 providers using Relu for all applicable cases | CDO |
| Champion confidence | All Wave 1 champions report "confident to train others" | Training Lead |
| Patient-facing stability | Zero patient-impacting errors | VP Operations |
| Support capacity | Vendor confirms capacity for Wave 2 volume | 🔵 Relu CSM |
| Baseline metric trajectory | Positive or neutral trend in key metrics | Analytics |
Decision Meeting: Schedule 90-minute go/no-go review with VP Operations, CDO, IT Director, and Relu CSM at Wave 1 Week 7.
Rollback Plan ⚠️
Trigger Conditions for Rollback
- Critical integration failure affecting patient care
25% of providers refusing to use system after go-live
- Vendor support unable to resolve blocking issue within 48 hours
- Regulatory/compliance concern identified
Rollback Procedure
- Stop: Halt cutover at affected location(s); do not proceed to additional sites
- Revert: Return to pre-Relu workflow (imaging + manual planning)
- Preserve: Export all data from Relu; maintain for later re-integration
- Communicate: Regional manager notifies staff, VP Operations notifies C-suite
- Root Cause: Convene vendor + internal team within 24 hours
- Decision: Determine fix timeline; if > 2 weeks, pause entire rollout 🟣
Isolation Principle
A failure at one location should NOT automatically stop other locations. Evaluate each location independently unless the issue is systemic (integration, vendor-side, etc.).
5. Configuration & Integration (Weeks 2–3)
Practice Management System Integration
Dentrix Integration (Step-by-Step)
☐ Verify Dentrix version G7.3 or higher (earlier versions unsupported) ⚠️ ☐ Enable Dentrix API access via eServices portal ☐ Generate API credentials (Client ID + Secret) 🔵 ☐ Provide credentials to Relu implementation team 🔵 ☐ Configure patient demographics sync (automatic vs. on-demand) ☐ Configure treatment plan write-back settings ☐ Test patient lookup from Relu → Dentrix (10 sample patients) ☐ Test treatment plan sync from Relu → Dentrix (3 sample plans) ☐ Verify insurance eligibility data flows correctly (if applicable) ☐ Document any Dentrix-specific workflows (custom treatment codes, etc.)
Estimated Time: 4–6 hours per location (parallelizable with central IT)
Eaglesoft Integration (Step-by-Step)
☐ Verify Eaglesoft version 21 or higher ☐ Enable Patterson Fuse connection (required for API access) ☐ Generate Fuse API credentials 🔵 ☐ Configure ODBC connection as fallback for specific data types ☐ Follow Relu Eaglesoft integration guide (vendor-provided) 🔵 ☐ Test patient lookup and treatment plan sync (same as Dentrix above)
Estimated Time: 5–7 hours per location (ODBC adds complexity)
Open Dental Integration (Step-by-Step)
☐ Verify Open Dental version 22.1 or higher (API improvements critical) ☐ Enable API access in Open Dental setup ☐ Configure user permissions for API service account ☐ Generate API key 🔵 ☐ Provide API endpoint and key to Relu 🔵 ☐ Configure patient search, treatment plan, and imaging connections ☐ Test bidirectional sync (5 patients, 3 treatment plans)
Estimated Time: 3–5 hours per location (Open Dental API is cleaner)
Imaging System Integration
DICOM Configuration (Universal Steps)
☐ Verify imaging system supports DICOM export (nearly all do) ☐ Identify DICOM server/PACS location (local vs. cloud) ☐ Configure DICOM send destination (Relu DICOM receiver endpoint) 🔵 ☐ Whitelist Relu DICOM endpoint in firewall ☐ Test manual DICOM send: panoramic image → Relu ☐ Test manual DICOM send: CBCT scan → Relu ☐ Configure automatic DICOM forwarding (if desired) ⚠️ ☐ Verify image quality and metadata accuracy post-transfer
System-Specific Notes
| Imaging System | Integration Notes |
|---|---|
| Planmeca Romexis | Native DICOM export; verify export includes all required tags |
| Dentsply Sirona Sidexis | Configure DICOM node in network settings; test CBCT specifically |
| Carestream | Full DICOM compliance; may require separate config per modality |
| Dexis | Limited DICOM support on older versions; upgrade may be required ⚠️ |
| Apteryx XrayVision | DICOM export available; verify CBCT handling |
Estimated Time: 2–4 hours per location for DICOM configuration
Test Environment Setup and Validation
Enterprise Test Environment Approach (Recommended)
☐ Request dedicated Relu test/sandbox environment 🔵 ☐ Populate with de-identified patient data (10–20 cases) ☐ Connect to non-production PMS instance (if available) or test database ☐ Connect to imaging archive with sample DICOM data
Validation Checklist
| Test Case | Expected Result | Pass/Fail |
|---|---|---|
| Patient created in PMS appears in Relu within 60 seconds | Auto-sync or manual search successful | ☐ |
| CBCT uploaded to Relu, AI segmentation completes | 3D model generated within 5 minutes | ☐ |
| Panoramic image analyzed | Anatomical landmarks identified accurately | ☐ |
| Treatment plan created in Relu | Plan syncs to PMS within 2 minutes | ☐ |
| Provider digital signature applied | Signature captured and logged | ☐ |
| Audit log records all actions | Log accessible to admin | ☐ |
| Concurrent users (3+) work simultaneously | No performance degradation | ☐ |
| Network interruption during upload | Graceful failure, resume capability | ☐ |
Data Migration / Historical Data Ingestion
Decision: Migrate Historical Cases? 🟣
| Approach | Pros | Cons |
|---|---|---|
| No Migration | Faster go-live, no data cleanup | Provider frustration on existing cases |
| Selective Migration | Key cases available, manageable effort | Requires case selection criteria |
| Full Migration | Complete history in new system | Time-intensive, data quality risks |
Recommendation for DSOs: Selective migration of active treatment plans only (cases presented in last 90 days, not yet completed).
Migration Steps (If Applicable)
☐ Export active treatment plans from PMS (CSV or XML) ☐ Export associated imaging from DICOM archive ☐ Provide to Relu for import processing 🔵 ☐ Validate imported cases (10% sample audit) ☐ Provider review of migrated plans for accuracy
Security and HIPAA Compliance Verification
Enterprise-Level HIPAA Checklist
| Item | Verification Step | Owner |
|---|---|---|
| ☐ BAA executed with Relu | Confirm signed BAA on file | Legal |
| ☐ Data encryption in transit | Verify TLS 1.2+ for all connections | IT Security |
| ☐ Data encryption at rest | Confirm Relu cloud encryption (AES-256) 🔵 | IT Security |
| ☐ Access controls | Role-based access verified, principle of least privilege | IT Security |
| ☐ Audit logging | All PHI access logged with user/timestamp | IT Security |
| ☐ Data retention policy | Confirm Relu retention aligns with DSO policy | Compliance |
| ☐ Breach notification | Confirm Relu breach notification SLA (< 24 hours) 🔵 | Compliance |
| ☐ User provisioning/deprovisioning | SSO integration handles automatic deprovisioning | IT |
| ☐ Data export capability | Confirm ability to export all data if contract terminates 🔵 | Legal |
| ☐ Physical security | Confirm Relu data center certifications (SOC 2, HITRUST) 🔵 | IT Security |
Standardized vs. Location-Specific Configuration
Standardized Configuration Template (Centrally Controlled)
| Setting | Standard Value | Rationale |
|---|---|---|
| AI sensitivity thresholds | Default (vendor-recommended) | Consistency across locations |
| Treatment plan templates | DSO-standard templates | Brand consistency |
| User role definitions | 4 roles (Admin, Provider, Clinical, Read-Only) | Simplify administration |
| Audit log retention | 7 years | Compliance requirement |
| Notification settings | Email to provider + office manager | Ensure visibility |
| Quality review workflow | CDO approval for complex cases (optional) | Central oversight |
Location-Specific Configuration (Local Discretion Allowed)
| Setting | Allowed Variation | Why |
|---|---|---|
| Provider preferences | UI layout, default views | Individual workflow preference |
| Imaging device names | Match local equipment labels | Practical necessity |
| Working hours for notifications | Match local office hours | Avoid off-hours alerts |
| Specialty-specific templates | Ortho vs. implant vs. GP | Case mix varies |
| Local admin contacts | Office manager designations | Operational structure |
6. Team Training Plan
Train-the-Trainer Model
Champion Selection Criteria
Each location requires ONE certified champion responsible for local training and first-line support.
| Criterion | Minimum Requirement |
|---|---|
| Role | Provider (strongly preferred) or experienced Office Manager |
| Tenure | 12+ months at location |
| Tech comfort | Above-average (history of adopting new systems) |
| Availability | Minimum 8 hours for certification training + ongoing commitment |
| Influence | Respected by peers, positive attitude |
| Communication | Able to teach and present clearly |
Champion Certification Process 🔵
| Phase | Duration | Delivery |
|---|---|---|
| Self-paced Relu fundamentals | 2 hours | Video modules (Relu Learning Portal) |
| Live virtual training with Relu clinical specialist | 3 hours | Zoom/Teams 🔵 |
| Hands-on case practice | 2 hours | Relu sandbox environment |
| Certification assessment | 30 minutes | Online quiz + practical demo |
| Train-the-trainer methodology | 1 hour | Relu Training Team 🔵 |
Certification Requirement: Champions must score 85%+ on assessment and demonstrate successful training delivery to 1 staff member before go-live.
Champion Responsibilities
- Deliver role-specific training to all location staff
- Serve as first escalation point for questions post-go-live
- Participate in weekly champion sync calls during rollout
- Report adoption issues to regional manager
- Conduct refresher training for new hires
Role-Specific Training Outlines
Dentists/Providers
How the Tool Changes Clinical Workflow:
- Imaging is uploaded (automatic or manual) → AI processes in background
- Within 3–5 minutes, AI-generated 3D model and treatment suggestions available
- Provider reviews AI output, makes adjustments, finalizes plan
- Plan syncs to PMS; patient presentation uses AI-generated visuals
What to Expect on Screen:
- 3D anatomical model with nerve mapping, bone density visualization
- AI-suggested implant positions with safety margins highlighted
- Cephalometric analysis with automated landmark identification
- Side-by-side comparison of treatment options
How to Interpret AI Outputs:
- AI confidence scores indicate reliability (Green: high, Yellow: moderate, Red: review closely)
- Nerve proximity warnings require manual verification
- AI does NOT replace clinical judgment — it accelerates and standardizes
When to Override AI:
- Complex anatomical variations AI may not recognize
- Patient-specific factors not captured in imaging (allergies, medical history)
- Preference for alternative treatment modalities
| Training Element | Detail |
|---|---|
| Estimated Training Time | 3 hours (1 hour concepts, 2 hours hands-on) |
| Recommended Format | Live demo by champion + supervised case completion |
| Common Resistance Points | "AI will replace my judgment" (emphasize AI as tool, not replacement); "This is slower" (show time savings after learning curve); "I don't trust it" (show validation data, build confidence with low-stakes cases first) |
Day 1 Cheat Sheet: Providers
┌─────────────────────────────────────────────────────────┐
│ RELU QUICK REFERENCE — PROVIDERS │
├─────────────────────────────────────────────────────────┤
│ 1. LOG IN: SSO → Relu icon → Select patient │
│ 2. UPLOAD IMAGING: Auto-syncs OR drag-drop DICOM │
│ 3. WAIT: AI processing = 3-5 minutes │
│ 4. REVIEW: Check confidence scores (Green=trust, │
│ Yellow=verify, Red=review closely) │
│ 5. ADJUST: Click/drag implants, modify
AI-generated implementation guide based on public vendor information. Verify specifics directly with Relu.