Dentrix Enterprise
Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
Dentrix Enterprise — Implementation Playbook (DSO)
Dentrix Enterprise Implementation Playbook
A Strategic Guide for DSO Operations Leaders
1. Executive Summary
What Dentrix Enterprise Does
Dentrix Enterprise is a centralized practice management platform designed specifically for multi-location dental organizations, providing unified patient records, standardized clinical workflows, enterprise-wide reporting, and centralized administrative control across all locations from a single database architecture.
Why DSOs Specifically Benefit
DSOs operating at scale face operational fragmentation that single-location solutions cannot address. Dentrix Enterprise delivers three critical advantages for multi-location organizations:
Scale Advantages: Centralized database architecture eliminates data silos, enabling patients to be seen seamlessly across any location while providing operations leadership with real-time visibility into performance metrics across the entire portfolio. A single configuration change propagates instantly to all locations.
Standardization: Unified procedure codes, fee schedules, clinical protocols, and reporting templates ensure consistent patient experience and operational metrics regardless of location. This standardization dramatically reduces training complexity when staff move between locations and enables meaningful cross-location performance comparisons.
Data Aggregation: Enterprise-wide reporting transforms scattered location data into actionable intelligence—aggregate production trends, normalized provider productivity comparisons, organization-wide insurance performance analytics, and predictive capacity planning become possible only with a unified data layer.
Expected Timeline
| Phase | Duration | Cumulative |
|---|---|---|
| Decision to Contract Execution | 2–4 weeks | Week 4 |
| Pre-Implementation & Planning | 2–3 weeks | Week 7 |
| Pilot Wave (2–3 locations) | 4–6 weeks | Week 13 |
| Wave 2 Expansion (5–8 locations) | 4–5 weeks | Week 18 |
| Wave 3 & Full Deployment | 6–10 weeks | Week 28 |
| Optimization & Stabilization | 8 weeks | Week 36 |
Total Timeline: 7–9 months from decision to full deployment across 15–50 locations, with ROI measurable by month 4–5.
2. Pre-Implementation Checklist (Weeks 1–2)
Technical Requirements
Hardware Standards (Per Location)
☐ Workstations: Windows 10/11 Pro, minimum 8GB RAM, SSD storage (16GB RAM recommended for clinical workstations) ☐ Server requirements validated with Henry Schein based on patient volume tier ☐ Network switches capable of supporting concurrent database connections (gigabit minimum) ☐ UPS/battery backup for server and critical workstations ☐ Barcode scanners, signature pads, and peripherals compatibility verified
Software Prerequisites
☐ Windows Server 2019 or 2022 (if on-premise components required) ☐ Microsoft SQL Server licensing confirmed (Enterprise edition for central database) ☐ Current antivirus/endpoint protection with Dentrix exclusions documented ☐ Remote desktop/access tools approved and configured for support scenarios ⚠️ Verify all existing Dentrix Ascend or Dentrix G-series versions across locations—migration paths vary significantly
Network Standards Across Locations
☐ Minimum 100 Mbps symmetric internet at each location (500 Mbps recommended for locations with 8+ operatories) ☐ Site-to-site VPN or SD-WAN connectivity to central database confirmed ☐ Latency under 50ms to central server validated ☐ Failover internet connection at high-volume locations ☐ Firewall rules documented and standardized across all locations 🔵 Request network requirements document from Henry Schein technical team
Enterprise Architecture Decisions
🟣 Decision Required: Centralized hosting vs. hybrid model
| Option | Pros | Cons |
|---|---|---|
| Fully Centralized (Cloud/Colo) | Single point of management, easier disaster recovery, consistent performance | Higher bandwidth dependency, potential latency issues |
| Hybrid (Central DB + Local Cache) | Better performance during connectivity issues | More complex architecture, higher maintenance |
☐ SSO integration requirements documented (Azure AD, Okta, or other IdP) ☐ Centralized credentialing system integration points identified ☐ Data residency and backup requirements confirmed with legal/compliance
Vendor Onboarding Steps
Key Contacts to Establish
| Role | Purpose | When Needed |
|---|---|---|
| Implementation Project Manager | Primary coordination, timeline management | Weekly throughout implementation |
| Technical Implementation Specialist | Configuration, integration, troubleshooting | During technical phases |
| Training Coordinator | Scheduling, materials, train-the-trainer | Weeks 3–6 |
| Enterprise Support Lead | Escalation path for critical issues | Post-go-live |
| Account Executive | Commercial issues, contract modifications | As needed |
🔵 Vendor Actions Required: ☐ Kickoff call scheduled within 5 business days of contract execution ☐ Implementation project plan received and reviewed ☐ Dedicated Slack/Teams channel or project portal access granted ☐ Technical environment provisioning initiated ☐ Statement of Work reviewed for scope alignment
Data & Access Prerequisites
☐ Master list of all locations with addresses, provider counts, operatory counts, and patient volumes ☐ Current PMS inventory (version numbers, database sizes, customizations) for each location ☐ Export permissions/credentials for existing patient data from legacy systems ☐ Imaging system inventory and DICOM/integration capabilities documented ☐ Insurance payer list with contracted fee schedules for all locations ☐ Provider NPI numbers, license numbers, and credentialing documentation ☐ Historical data scope decision: How many years of patient records to migrate?
🟣 Decision Required: Data migration scope
- Full historical migration (all records, all years)
- Limited migration (active patients + 2–3 years history)
- Fresh start with legacy system read-only access
Internal Stakeholder Alignment
Stakeholder Alignment Map
| Stakeholder | Role in Implementation | Communication Cadence | Key Concerns |
|---|---|---|---|
| Board/Investors | Budget approval, ROI expectations | Monthly summary | Investment justification, timeline adherence |
| CEO/COO | Executive sponsorship, escalation authority | Bi-weekly briefing | Strategic alignment, risk management |
| Chief Dental Officer | Clinical workflow approval, provider buy-in | Weekly during planning | Clinical efficiency, standard of care |
| VP of Operations | Day-to-day implementation oversight | Daily/weekly standup | Operational continuity, staff impact |
| Regional Managers | Wave coordination, location readiness | Weekly per wave | Location-specific concerns, resource allocation |
| Office Managers | Local execution, staff coordination | As needed during their wave | Training time, workflow disruption |
| Lead Providers | Clinical champion, peer influence | Monthly (more during their wave) | Chair time impact, learning curve |
| IT Director/Team | Technical implementation, support | Daily during technical phases | System stability, support burden |
Approval Requirements
🟣 Executive Approvals Needed: ☐ Budget authorization (including contingency) ☐ Timeline commitment and resource allocation ☐ Data migration scope and legacy system disposition ☐ Standardization policy (what must be uniform vs. local discretion) ☐ Go/no-go criteria for wave advancement
Baseline Metrics to Capture
⚠️ Critical: These metrics MUST be captured uniformly before any location goes live. Without consistent baselines, ROI measurement becomes impossible.
Operational Metrics (Capture 90-day average)
| Metric | Source | Measurement Method |
|---|---|---|
| Daily production per provider | Current PMS | Report export |
| Daily collections per provider | Current PMS | Report export |
| Hygiene production per hour | Current PMS | Calculated |
| Patient no-show rate | Current PMS | Appointment report |
| Same-day cancellation rate | Current PMS | Appointment report |
| New patient acquisition (monthly) | Current PMS | New patient report |
| Treatment case acceptance rate | Current PMS/manual | Treatment plans presented vs. scheduled |
Administrative Metrics
| Metric | Source | Measurement Method |
|---|---|---|
| Claim submission lag (days to submit) | Clearinghouse/PMS | Date of service to submission |
| Clean claim rate | Clearinghouse | Claims accepted without rejection |
| Days in A/R (30/60/90+ buckets) | Current PMS | Aging report |
| Insurance verification time (minutes) | Manual tracking | Time study |
| Patient check-in time (minutes) | Manual tracking | Time study |
Staff Metrics
| Metric | Source | Measurement Method |
|---|---|---|
| Provider schedule utilization | Current PMS | Scheduled hours / available hours |
| Overtime hours (weekly) | Payroll system | Payroll export |
| Staff turnover (trailing 12 months) | HR system | Headcount analysis |
Standardization Protocol
☐ Create master metric definition document with exact formulas ☐ Distribute to all office managers with collection instructions ☐ Set collection deadline 2 weeks before Wave 1 go-live ☐ Central team validates submissions for consistency ☐ Flag locations with incomplete or anomalous data for follow-up
3. Location Readiness Assessment
Scoring Framework
Each location receives a composite readiness score based on five weighted factors. This score determines wave assignment and identifies locations requiring remediation before rollout.
Factor 1: IT Infrastructure Maturity (Weight: 25%)
| Score | Criteria |
|---|---|
| 5 | All workstations meet/exceed specs, gigabit network, <30ms latency to central, redundant internet |
| 4 | All workstations meet specs, network meets minimum, one minor gap |
| 3 | 80%+ workstations meet specs, network adequate but not optimal |
| 2 | Significant hardware gaps, network upgrades required |
| 1 | Major infrastructure overhaul needed, location not ready without capital investment |
Factor 2: Staff Tenure & Adaptability (Weight: 20%)
| Score | Criteria |
|---|---|
| 5 | <10% annual turnover, documented history of successful tech adoption, staff tenure avg >3 years |
| 4 | <15% turnover, positive tech adoption history, adequate training capacity |
| 3 | 15–25% turnover, mixed tech adoption history |
| 2 | 25–40% turnover, or history of resistance to system changes |
| 1 | >40% turnover, significant resistance/change fatigue, or imminent staff transitions |
Factor 3: Patient Volume Impact (Weight: 20%)
| Score | Criteria |
|---|---|
| 5 | High volume (top quartile) + operationally stable + strong management |
| 4 | Above average volume + stable operations |
| 3 | Average volume, moderate operational complexity |
| 2 | High volume but operational instability (staff issues, provider transition) |
| 1 | Very high volume + multiple operational challenges (high risk) |
Note: High volume locations offer faster ROI but higher risk. Score reflects balance of opportunity and risk.
Factor 4: Tech Stack Compatibility (Weight: 20%)
| Score | Criteria |
|---|---|
| 5 | Currently on Dentrix product (G-series), standard imaging integration, no complex custom workflows |
| 4 | On Dentrix product, minor customizations, standard integrations |
| 3 | On different PMS but standard platform (Eaglesoft, Open Dental), straightforward migration |
| 2 | Non-standard PMS or significant customizations requiring workarounds |
| 1 | Legacy/proprietary system, complex data migration, multiple non-standard integrations |
Factor 5: Local Champion Availability (Weight: 15%)
| Score | Criteria |
|---|---|
| 5 | Tech-forward office manager + engaged lead provider, both committed to champion role |
| 4 | Strong office manager champion, provider supportive |
| 3 | Willing champion identified, but limited tech experience |
| 2 | No natural champion, will require assigned responsibility |
| 1 | Leadership actively resistant or location in management transition |
Composite Scoring & Wave Assignment
Calculation
Composite Score = (IT × 0.25) + (Staff × 0.20) + (Volume × 0.20) + (Tech × 0.20) + (Champion × 0.15)
Wave Assignment Guidelines
| Score Range | Recommended Assignment |
|---|---|
| 4.0–5.0 | Wave 1 Pilot Candidates |
| 3.5–3.9 | Wave 2 |
| 3.0–3.4 | Wave 3 |
| 2.5–2.9 | Wave 3 with remediation plan |
| <2.5 | Defer until specific issues resolved |
Sample Readiness Assessment Matrix
| Location | IT (25%) | Staff (20%) | Volume (20%) | Tech (20%) | Champion (15%) | Composite | Recommended Wave |
|---|---|---|---|---|---|---|---|
| Loc A | 5 | 4 | 4 | 5 | 5 | 4.55 | Wave 1 |
| Loc B | 4 | 4 | 5 | 4 | 4 | 4.20 | Wave 1 |
| Loc C | 4 | 3 | 3 | 5 | 4 | 3.80 | Wave 2 |
| Loc D | 3 | 3 | 4 | 3 | 3 | 3.20 | Wave 3 |
| Loc E | 2 | 2 | 3 | 2 | 2 | 2.20 | Defer—remediation required |
Recommended Rollout Sequence
Wave 1 Selection Criteria
Beyond composite score, Wave 1 pilot locations should be:
☐ Representative: Mix of practice types (general, specialty if applicable), geographic regions, and patient demographics that exist across the portfolio ☐ Manageable Risk: Not your highest-volume locations, but substantial enough to stress-test the system ☐ Learning-Optimal: Staff willing to provide detailed feedback, leadership engaged in documentation ☐ Travel-Accessible: Easy for central team to be on-site during go-live
Wave Structure Template (40-Location Example)
| Wave | Locations | Timeline | Focus |
|---|---|---|---|
| Wave 1 (Pilot) | 3 locations | Weeks 1–6 | Validate configuration, identify issues, refine training |
| Wave 2 | 8 locations | Weeks 8–12 | Scale training model, test parallel deployments |
| Wave 3A | 12 locations | Weeks 14–18 | Regional clustering (3–4 per region) |
| Wave 3B | 12 locations | Weeks 20–24 | Remaining locations |
| Wave 4 (Cleanup) | 5 locations | Weeks 26–28 | Deferred/remediated locations |
4. Rollout Strategy
Wave Structure Recommendation
Wave 1: Pilot (2–3 Locations)
Duration: 4–6 weeks per pilot location, staggered starts
Selection Criteria: ☐ Composite readiness score ≥4.0 ☐ At least one location that is operationally representative of majority of portfolio ☐ Include one location with known complexity to surface issues early ☐ Geographic diversity if portfolio is multi-regional ☐ Office manager and lead provider personally committed to feedback process
Pilot Objectives:
- Validate technical configuration works as expected
- Identify gaps in training materials
- Establish realistic productivity impact curve (expect 15–25% productivity dip in week 1)
- Document unexpected issues and workarounds
- Calibrate timeline estimates for future waves
Pilot Timeline:
| Week | Activities |
|---|---|
| Week 1 | Final hardware/network verification, local server setup if applicable, test environment validation |
| Week 2 | Data migration execution, parallel testing, staff training |
| Week 3 | Go-live day, central team on-site, intensive support |
| Week 4 | Daily check-ins, issue resolution, workflow refinement |
| Weeks 5–6 | Stabilization, productivity recovery, lessons learned documentation |
Wave 2: Controlled Expansion (5–8 Locations)
Duration: 4–5 weeks
Selection Criteria: ☐ Composite readiness score ≥3.5 ☐ Regional clustering to enable efficient training and support ☐ Mix of practice characteristics to validate broader applicability
Wave 2 Objectives:
- Validate train-the-trainer model at scale
- Test parallel deployments (2–3 locations going live same week)
- Establish regional manager oversight cadence
- Refine escalation pathways
Wave 3: Full Deployment (Remaining Locations)
Duration: 6–10 weeks depending on total location count
Approach: Deploy in regional clusters of 3–5 locations per week
Considerations: ☐ Schedule to avoid conflicts with high-volume periods (back-to-school, end-of-year insurance rush) ☐ Ensure support capacity matches deployment velocity ☐ Lower readiness score locations get more intensive support resources
Go/No-Go Criteria Between Waves
Must Pass to Advance
🟣 Executive Decision Point: Wave advancement requires formal sign-off
| Criteria | Threshold | Measurement |
|---|---|---|
| Technical stability | <2 critical incidents in final week | Incident log |
| Staff proficiency | 80% of staff complete training assessment | Training tracker |
| Productivity recovery | Within 10% of pre-go-live levels by week 4 | Production reports |
| Data integrity | Zero data migration errors identified | Audit report |
| Support burden | <15 support tickets/location/day by week 4 | Ticketing system |
Yellow Flags (Proceed with Caution)
- Productivity at 85–90% of baseline by week 4
- Training completion 70–80%
- Support tickets elevated but trending down
Red Flags (Pause and Remediate)
⚠️ Any of the following triggers a pause:
- Critical system outages affecting patient care
- Data integrity issues (lost records, incorrect patient matching)
- Provider mutiny (multiple providers refusing to use system)
- Productivity below 80% of baseline without clear recovery trajectory
Rollback Plan
If a wave fails, execute the following:
Immediate (Within 24 hours)
☐ Activate legacy system access at affected locations ☐ Communicate to staff that temporary rollback is in effect ☐ Preserve all data entered in Dentrix Enterprise during failed rollout ☐ Notify vendor support of rollback situation
Short-term (Days 1–7)
☐ Conduct root cause analysis with vendor ☐ Document specific failure points and triggers ☐ Assess whether issue is location-specific or systemic ☐ Update configuration/training based on findings
Recovery (Weeks 2–4)
☐ Develop remediation plan for affected locations ☐ If systemic issue: pause all future waves until resolved ☐ If location-specific: defer that location to later wave ☐ Re-validate go/no-go criteria before resuming
Impact Isolation
- Rollback at one location does NOT automatically affect other locations
- Centralized database architecture requires careful coordination to isolate changes
- 🔵 Vendor involvement required for any data isolation/restoration procedures
5. Configuration & Integration (Weeks 2–3)
Practice Management System Integration
Dentrix G-Series Migration Path
For locations currently on Dentrix G-series:
☐ Step 1: Export complete database backup from each location (3–8 hours depending on database size) ☐ Step 2: Run Henry Schein data conversion utility (🔵 vendor-provided tool) ☐ Step 3: Validate patient demographics, clinical notes, and treatment history in test environment ☐ Step 4: Reconcile appointment schedules and future appointments ⚠️ Step 5: Verify all document attachments and images transferred correctly—this is a common failure point ☐ Step 6: Run financial reconciliation to confirm aging, production, and collection history match
Eaglesoft Migration Path
☐ Step 1: Export patient data, financial data, and clinical records using Eaglesoft export utilities ☐ Step 2: Map Eaglesoft procedure codes to ADA/Dentrix procedure code library ☐ Step 3: Execute data transformation using vendor-provided migration tools (🔵) ⚠️ Step 4: Insurance plan mapping requires manual review—plan structures differ between systems ☐ Step 5: Validate via test environment with spot-checks on 50+ patient records ☐ Step 6: Financial reconciliation with source system reports
Open Dental Migration Path
☐ Step 1: Generate MySQL database export from Open Dental ☐ Step 2: Execute Henry Schein's Open Dental conversion process (🔵) ☐ Step 3: Map custom procedure codes and fee schedules ⚠️ Step 4: Custom forms and templates require recreation in Dentrix Enterprise—not migrated automatically ☐ Step 5: Validate imaging links and document associations ☐ Step 6: Full system test in staging environment
Imaging System Integration
Standard Integrations
| Imaging System | Integration Type | Complexity | Time Estimate |
|---|---|---|---|
| Dexis | Direct integration | Low | 2–4 hours/location |
| Schick | Direct integration | Low | 2–4 hours/location |
| Carestream | TWAIN bridge | Medium | 4–6 hours/location |
| Planmeca Romexis | API integration | Medium | 4–8 hours/location |
| i-CAT/CBCT | DICOM integration | High | 8–12 hours/location |
Integration Steps
☐ Step 1: Document current imaging workflow at each location (capture, storage, viewing) ☐ Step 2: Verify imaging software version compatibility with Dentrix Enterprise ☐ Step 3: Install Dentrix Enterprise imaging bridge/connector ☐ Step 4: Configure TWAIN or direct integration settings ☐ Step 5: Test image capture from each sensor/device type ☐ Step 6: Test image viewing and annotation workflow ☐ Step 7: Validate that historical images are accessible ☐ Step 8: Confirm that new images save to correct patient records
Test Environment Setup
Central Test Environment
☐ Deploy isolated test instance of Dentrix Enterprise (🔵 vendor provisions) ☐ Load representative sample data (anonymized if possible) ☐ Configure with production settings (fee schedules, procedure codes, etc.) ☐ Grant test access to implementation team and location champions ☐ Establish test data refresh cadence (weekly recommended during active implementation)
Per-Location Testing vs. Centralized Testing
Recommendation: Centralized test environment with location-specific configuration profiles
| Approach | Pros | Cons |
|---|---|---|
| Central test (recommended) | Single environment to manage, consistent testing, easier for central team to validate | May miss location-specific quirks |
| Per-location test | Validates exact configuration, better for complex locations | Time-consuming, harder to maintain, delays timeline |
Hybrid Approach: Use central test for standard scenarios; deploy location-specific test only for locations with score <3.5 on tech compatibility.
Validation Checklist
☐ Patient search and record retrieval ☐ Appointment scheduling and modification ☐ Treatment plan creation and acceptance workflow ☐ Insurance eligibility verification ☐ Claim creation and submission (to test clearinghouse) ☐ Payment posting (all payment types) ☐ Imaging capture and viewing ☐ Clinical note entry and template application ☐ Report generation (production, collections, aging) ☐ Multi-location patient record access ☐ Provider schedule management
Data Migration Checklist
Pre-Migration
☐ Complete data audit at each location (record counts, date ranges, anomalies) ☐ Define data scope (full history vs. active patients + X years) ☐ Create test migration timeline (at least 2 test runs before production) ☐ Establish data freeze protocol (when does legacy data entry stop?) ⚠️ ☐ Identify orphaned records, duplicate patients, and data quality issues in legacy system
Migration Execution
☐ Final legacy backup created and archived ☐ Migration scripts executed in batch sequence ☐ Real-time monitoring of migration progress ☐ Error logging and exception handling for failed records ☐ Immediate post-migration validation (record counts, financial totals)
Post-Migration Validation
☐ Spot-check patient demographics (100+ records per location) ☐ Validate financial totals match source system within tolerance (<$100 variance) ☐ Confirm insurance plan assignments ☐ Verify future appointments migrated correctly ☐ Test treatment plan history accessibility ☐ Confirm prescription history if applicable
Security & HIPAA Compliance
Enterprise HIPAA Checklist
🟣 Executive Review Required
☐ Business Associate Agreement (BAA) executed with Henry Schein ☐ Data encryption at rest confirmed (AES-256 minimum) ☐ Data encryption in transit confirmed (TLS 1.2+) ☐ Access control policy documented (role-based access) ☐ Audit logging enabled and retention period defined ☐ Backup and disaster recovery plan documented and tested ☐ Breach notification procedures aligned with organizational policy ☐ User access provisioning/deprovisioning procedures established ☐ Minimum necessary access principle enforced across roles
Access Control Configuration
| Role | Access Level | Approver |
|---|---|---|
| Central Admin | Full system configuration | VP Operations |
| Regional Manager | Read-only all locations, full access assigned region | VP Operations |
| Office Manager | Full access own location, limited cross-location | Regional Manager |
| Provider | Clinical access own location | Office Manager |
| Front Desk | Scheduling, demographics, payments | Office Manager |
| Billing | Financial access, claims, reports | Office Manager |
☐ Document all user roles and access levels ☐ Implement SSO integration with organizational IdP ☐ Configure session timeout settings (15-minute inactivity recommended) ☐ Establish password complexity requirements ☐ Enable multi-factor authentication for admin accounts
Standardized vs. Location-Specific Configuration
Standardize Centrally (Template Settings)
| Configuration Element | Why Standardize |
|---|---|
| Procedure code library | Consistent reporting, insurance mapping |
| Fee schedule structure | Centralized pricing management |
| Treatment plan templates | Consistent patient experience |
| Clinical note templates | Standard of care, compliance |
| Report templates | Cross-location comparison |
| User role definitions | Consistent access control |
| Insurance plan database | Centralized contract management |
| Appointment types | Consistent scheduling metrics |
| Billing workflows | Consistent revenue cycle |
Allow Local Discretion
| Configuration Element | Why Allow Variation |
|---|---|
| Provider-specific preferences | Workflow efficiency |
| Operatory names/assignments | Local facility layout |
| Office hours and schedule blocks | Local market needs |
| Custom reminder language | Regional preferences |
| Referral sources | Local referral networks |
| Provider production goals | Individual targets |
6. Team Training Plan
Train-the-Trainer Model
Champion Selection Criteria
Each location requires one designated champion. Ideal candidates:
☐ Currently in office manager or lead administrative role ☐ Minimum 2 years tenure at the location ☐ Demonstrated tech aptitude (quick learner, comfortable troubleshooting) ☐ Respected by peers and providers ☐ Available for 16–20 hours of central training over 2 weeks ☐ Committed to ongoing champion responsibilities for 90 days post-go-live
Champion Responsibilities
| Phase | Responsibilities |
|---|---|
| Pre-Go-Live | Complete central training, customize materials for location, coordinate training schedule |
| Go-Live Week | Lead daily huddles, provide real-time support, escalate issues |
| Weeks 2–4 | Conduct refresher training, address workflow questions, collect feedback |
| Ongoing | Train new hires, submit enhancement requests, participate in champion network |
Champion Certification Process
☐ Complete 8-hour self-paced online training (🔵 vendor-provided) ☐ Attend 4-hour live virtual session covering advanced topics ☐ Pass proficiency assessment (minimum 85% score) ☐ Complete supervised training delivery (shadow train 2 team members) ☐ Sign champion commitment acknowledging responsibilities
Role-Specific Training Outlines
Providers (Dentists/Specialists)
Training Time: 4 hours (2 hours initial + 2 hours over first week)
Training Format: Live demonstration + hands-on practice with test patients
Content Outline:
- Navigating the clinical workspace (30 min)
- Treatment planning and case presentation (45 min)
- Clinical note entry and templates (30 min)
- Image viewing and annotation (30 min)
- Provider dashboard and production tracking (15 min)
- Common scenarios walkthrough (30 min)
Common Resistance Points:
| Objection | Response |
|---|---|
| "This slows me down" | "First 2 weeks will be slower; data shows productivity returns to normal by week 3 and exceeds baseline by week 6" |
| "I liked the old system" | "Your feedback helps us configure this to work better for you; what specific workflow matters most?" |
| "I don't have time to learn this" | "We've designed training to fit around patient care; let's find 30-minute windows that work" |
Day 1 Cheat Sheet Topics:
- Login and navigation
- Patient search (3 methods)
- Opening a chart
- Entering clinical notes (quick keys)
- Creating a treatment plan
- Who to call for help
Hygienists
Training Time: 2 hours
Training Format: Shadow session with champion + guided practice
Content Outline:
- Patient check-in workflow from their workstation (15 min)
- Medical history review and update (15 min)
- Periodontal charting entry (30 min)
- Clinical note documentation (30 min)
- Image capture and viewing (20 min)
- Communicating with front desk (10 min)
Common Resistance Points:
| Objection | Response |
|---|---|
| "I'm not the techie type" | "This system is designed for clinical staff; let's take it one step at a time" |
| "Perio charting takes too long" | "Let me show you voice-activated entry—most hygienists save time after 1 week" |
Day 1 Cheat Sheet Topics:
- Pulling up your patient list
- Entering perio measurements
- Saving clinical notes
- Flagging issues for provider review
- Capturing X-rays
Front Desk / Office Manager
Training Time: 6 hours (can be split across 2–3 sessions)
Training Format: Live training + hands-on practice + workflow simulation
Content Outline:
- Patient check-in/check-out workflow (45 min)
- Appointment scheduling and management (60 min)
- Patient registration and demographics (30 min)
- Insurance verification and entry (45 min)
- Payment collection and posting (45 min)
- Daily reports and end-of-day reconciliation (45 min)
- Multi-location patient lookup (30 min)
Common Resistance Points:
| Objection | Response |
|---|---|
| "This is completely different" | "The core concepts are the same; we've just moved things around. You'll build muscle memory quickly." |
| "I'm worried I'll make mistakes" | "The system has safeguards, and we can fix anything during the first month. It's safe to practice." |
| "Scheduling looks different" | "Let's walk through your specific scenarios—show me how you schedule now and I'll show you the equivalent." |
Day 1 Cheat Sheet Topics:
- Login and home screen orientation
- Scheduling an appointment
- Checking a patient in
- Collecting and posting a payment
- Checking a patient out
AI-generated implementation guide based on public vendor information. Verify specifics directly with Dentrix Enterprise.