Dental Intelligence
Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
Dental Intelligence — Implementation Playbook (DSO)
Dental Intelligence Implementation Playbook
A Strategic Guide for DSO Deployment
Tool Category: Analytics & Business Intelligence
Target Audience: DSOs (15–50 Locations)
Version: 1.0
Published by: Avized.com
1. Executive Summary
What Dental Intelligence Does
Dental Intelligence is a comprehensive analytics and business intelligence platform that aggregates data from your practice management system to deliver real-time visibility into production, collections, scheduling efficiency, patient reactivation opportunities, and provider performance. It transforms fragmented operational data into actionable insights through automated reporting, goal tracking, and AI-driven recommendations that surface revenue opportunities hiding in your existing patient base.
Why DSOs Specifically Benefit from Analytics & Business Intelligence AI
At scale, Analytics & BI tools create asymmetric advantages that single practices cannot replicate:
Data Aggregation Power: With 15–50 locations feeding a centralized platform, you generate statistically significant benchmarks. A single practice can't know if their 42% hygiene reappointment rate is good—you can compare it across 47 other locations instantly.
Standardization of Performance Visibility: Regional managers and C-suite leaders gain a single source of truth. No more waiting for Office Managers to manually compile reports in different formats with inconsistent definitions.
Pattern Recognition at Portfolio Scale: AI can identify that Location #23's sudden production drop correlates with scheduling template changes, or that your highest-performing locations share specific morning huddle metrics—insights invisible at the practice level.
Operational Leverage: One centralized team can monitor and intervene across all locations using consistent KPIs, replacing the need for each location to develop its own reporting competency.
M&A Due Diligence & Integration: For growth-stage DSOs, having standardized analytics accelerates acquisition evaluation and post-close integration.
Expected Timeline: Decision to Full Deployment
| Phase | Timeline | Scope |
|---|---|---|
| Pre-Implementation & Planning | Weeks 1–2 | Central team readiness, baseline metrics |
| Wave 1 Pilot (2–3 locations) | Weeks 3–5 | Initial deployment, learning capture |
| Wave 2 Expansion (5–8 locations) | Weeks 6–9 | Refined rollout based on pilot learnings |
| Wave 3+ Full Deployment | Weeks 10–16 | Remaining locations in 8–10 location waves |
| Post-Launch Optimization | Weeks 17–20 | Stabilization, ROI validation |
Total Timeline: 16–20 weeks for a 30-location DSO, scaling linearly with additional locations.
2. Pre-Implementation Checklist (Weeks 1–2)
Technical Requirements
Hardware
☐ Verify all locations have workstations meeting minimum specs (Windows 10+ or macOS 10.14+, 8GB RAM minimum, modern browser)
☐ Confirm at least one large-format display (32"+ monitor or TV) per location for team dashboard visibility
☐ Inventory existing hardware age—flag any workstations >5 years old for potential upgrade
Estimated Time: 2–3 hours for IT to compile inventory across all locations
Software
☐ Document PMS version at each location (Dentrix, Eaglesoft, Open Dental, other)
☐ ⚠️ Verify PMS versions meet Dental Intelligence minimum compatibility requirements—outdated versions are the #1 integration blocker
☐ Confirm browser versions (Chrome 90+ recommended, Firefox 88+, Edge 90+)
☐ Document any existing BI tools to be replaced or integrated
Estimated Time: 1–2 hours for IT + Regional Managers to compile
Network
☐ Test internet speed at each location (minimum 25 Mbps download recommended)
☐ Verify firewall configurations allow HTTPS traffic to Dental Intelligence servers
☐ ⚠️ Document any locations with unreliable connectivity—these need mitigation plans
☐ Confirm VPN requirements if data must route through corporate network
Estimated Time: 3–4 hours for network assessment across all locations
Integrations
☐ 🔵 Request integration specifications from Dental Intelligence for your specific PMS versions
☐ Map data flow: PMS → Dental Intelligence (what data syncs, frequency, direction)
☐ Identify any third-party tools that will need to share data with Dental Intelligence (patient communication platforms, insurance verification tools)
Estimated Time: 2 hours with vendor support
Vendor Onboarding Steps
| Step | Action | Owner | Timeline |
|---|---|---|---|
| 1 | 🔵 Schedule kickoff call with Dental Intelligence enterprise team | VP of Operations | Day 1 |
| 2 | 🔵 Assign dedicated Customer Success Manager (CSM) and Technical Account Manager (TAM) | Vendor | Day 2 |
| 3 | Establish primary and backup contacts on both sides | Both | Day 3 |
| 4 | 🔵 Obtain access to enterprise admin portal | Vendor | Day 3 |
| 5 | 🔵 Review and sign BAA (Business Associate Agreement) | Legal + Vendor | Days 3–5 |
| 6 | 🔵 Schedule technical integration planning session | IT + Vendor TAM | Day 5 |
| 7 | Define communication cadence (weekly calls during rollout recommended) | Both | Day 5 |
Key Contacts to Establish:
| Role | Your Organization | Vendor Side |
|---|---|---|
| Executive Sponsor | VP of Operations or CDO | VP of Enterprise Accounts |
| Project Lead | Director of Operations or IT | Customer Success Manager |
| Technical Lead | IT Director/Manager | Technical Account Manager |
| Regional Liaisons | Regional Managers (1 per region) | Implementation Specialist |
| Escalation Path | CEO/COO | VP of Customer Success |
Data/Access Prerequisites
☐ 🟣 Obtain executive approval for data sharing agreement and BAA
☐ Compile PMS admin credentials for each location (or request from Office Managers)
☐ 🔵 Generate API keys if using direct API integration vs. sync agent
☐ Document any locations using on-premise servers vs. cloud-hosted PMS
☐ Identify data retention policies—how far back should historical data be imported?
☐ Confirm SSO provider if using centralized authentication (Okta, Azure AD, Google Workspace)
Estimated Time: 4–6 hours for credential compilation (delegate to Regional Managers)
Enterprise-Level Requirements
Network Standards Across Locations
☐ 🟣 Decide: Standardize minimum network specifications for all locations?
☐ Document bandwidth requirements for real-time dashboard refresh (minimal—approximately 1–2 Mbps)
☐ Establish network upgrade queue for non-compliant locations
Centralized vs. Location-Level Hosting
Dental Intelligence is cloud-hosted, so this decision is straightforward:
☐ Data flows from each location's PMS to Dental Intelligence cloud
☐ No on-premise servers required at corporate or location level
☐ 🟣 Decide: Will data sync via local agent installation or direct API?
- Agent Installation: More reliable for on-premise PMS, requires local admin access
- Direct API: Cleaner for cloud-hosted PMS, fewer moving parts
SSO (Single Sign-On)
☐ 🟣 Decide: Require SSO for Dental Intelligence access?
☐ If yes, document SSO provider and initiate integration request with vendor
☐ Define user role hierarchy (Enterprise Admin → Regional Admin → Location Admin → User)
Estimated Time: 4–6 hours for IT to compile requirements, 1–2 hours for executive decisions
Centralized Credentialing
☐ Define user provisioning workflow: Who creates accounts? Who assigns permissions?
☐ Document offboarding process: How quickly are terminated employees removed from system?
☐ ⚠️ Establish password and MFA requirements before rollout—retrofitting is painful
Internal Stakeholder Alignment
Stakeholder Alignment Map
| Stakeholder Level | Who | What They Need | Communication Frequency |
|---|---|---|---|
| Board/Investors | Board members, PE partners | High-level ROI projections, timeline, strategic rationale | Quarterly (or at milestones) |
| C-Suite | CEO, COO, CFO, CDO | Business case, resource requirements, risk assessment | Bi-weekly during rollout |
| Regional Managers | Regional VPs, District Managers | Rollout schedule for their region, training requirements, success metrics | Weekly during their wave |
| Location Office Managers | Office Managers at each location | What changes for their daily workflow, support resources, expectations | Weekly during their go-live wave |
| Providers | Dentists, specialists | How this helps them (not "more oversight"), clinical workflow impact | Before their location's go-live |
Approval Requirements
| Decision | Approver | Timing |
|---|---|---|
| 🟣 Vendor contract and pricing | CFO + CEO | Before kickoff |
| 🟣 BAA and data sharing agreement | Legal + CDO | Week 1 |
| 🟣 Rollout timeline and wave structure | VP of Operations | Week 1 |
| 🟣 Budget for hardware upgrades (if needed) | CFO | Week 2 |
| 🟣 Standardization decisions (see Section 10) | VP of Operations + CDO | Week 2 |
Baseline Metrics to Capture BEFORE Go-Live
⚠️ Critical: If you don't capture these before deployment, you cannot prove ROI. This is the most commonly skipped step and the biggest regret.
Production & Revenue Metrics
☐ Monthly production per location (rolling 6 months)
☐ Monthly collections per location (rolling 6 months)
☐ Production per provider per day
☐ Case acceptance rate (presented treatment vs. scheduled treatment)
☐ Average treatment plan value
Scheduling Metrics
☐ Schedule utilization rate (filled chair time vs. available chair time)
☐ Same-day cancellation rate
☐ No-show rate
☐ Hygiene reappointment rate (percentage of hygiene patients scheduled for next visit before leaving)
☐ Days to third next available appointment (provider and hygiene)
Patient Metrics
☐ Active patient count per location (seen in last 18 months)
☐ Unscheduled treatment value (diagnosed but not scheduled)
☐ Overdue hygiene patient count
☐ New patient volume (monthly average)
Operational Metrics
☐ Average days in AR (accounts receivable)
☐ Insurance claim denial rate (if trackable)
☐ Patient wait time (if tracked)
Standardization Across Locations
🟣 Executive Decision Required: Agree on standard definitions before measuring.
| Metric | Standard Definition to Adopt |
|---|---|
| Active Patient | Seen within 18 months (not 12 or 24) |
| Case Acceptance Rate | Scheduled treatment ÷ presented treatment value |
| Schedule Utilization | Scheduled production ÷ (available hours × hourly production goal) |
| Hygiene Reappointment | Next hygiene visit scheduled before patient leaves office |
☐ Distribute baseline data collection template to all Office Managers
☐ Set deadline for baseline submission (recommend: end of Week 2)
☐ Designate one analyst to compile and normalize data into comparison format
☐ ⚠️ Flag any locations unable to provide baseline data—may indicate reporting infrastructure gaps
Estimated Time: 3–4 hours per location to compile; 8–10 hours centrally to normalize and analyze
3. Location Readiness Assessment
Scoring Framework
Score each location on the following five factors (1–5 scale). This framework identifies which locations should go early, which need remediation, and which should be last.
Factor 1: IT Infrastructure Maturity
| Score | Criteria |
|---|---|
| 5 | Fiber internet (100+ Mbps), all workstations <3 years old, cloud-hosted PMS, IT support readily available |
| 4 | Cable internet (50+ Mbps), most workstations <4 years old, compatible PMS version, occasional IT delays |
| 3 | Internet 25–50 Mbps, mixed hardware age (some >5 years), PMS version may need update, IT support responsive but not proactive |
| 2 | Internet <25 Mbps or unreliable, majority of hardware >5 years old, PMS version outdated, IT support slow |
| 1 | Connectivity issues frequent, critical hardware failures, PMS version incompatible, no dedicated IT support |
Factor 2: Staff Tenure and Adaptability
| Score | Criteria |
|---|---|
| 5 | Office Manager >3 years tenure, staff turnover <15%, history of successful tech adoption, team embraces change |
| 4 | Office Manager >2 years tenure, staff turnover 15–25%, some tech adoption success, team generally adaptable |
| 3 | Office Manager 1–2 years tenure, staff turnover 25–35%, mixed tech adoption history, some resistance to change |
| 2 | Office Manager <1 year tenure, staff turnover 35–50%, limited tech adoption, notable resistance to change |
| 1 | Office Manager position unstable or vacant, turnover >50%, failed past tech implementations, active resistance |
Factor 3: Patient Volume
| Score | Criteria | Notes |
|---|---|---|
| 5 | Top quartile production in portfolio | Highest impact potential; higher implementation risk |
| 4 | Second quartile production | Strong impact, manageable risk |
| 3 | Third quartile production | Moderate impact, standard risk |
| 2 | Fourth quartile production | Lower impact, lower stakes for piloting |
| 1 | Significantly underperforming or turnaround situation | May have other operational priorities |
Note: High volume (Score 5) is actually moderate risk for pilots—too much at stake. Ideal pilot locations are Score 3–4.
Factor 4: Existing Tech Stack Compatibility
| Score | Criteria |
|---|---|
| 5 | Dentrix Enterprise, Eaglesoft, or Open Dental cloud; no conflicting BI tools; clean data hygiene |
| 4 | Compatible PMS version; minimal custom configurations; may have basic reporting but no BI conflicts |
| 3 | PMS compatible but requires sync agent; some custom configurations; data hygiene issues minor |
| 2 | PMS version requires upgrade for compatibility; significant custom configurations; data quality concerns |
| 1 | PMS incompatible or heavily customized; existing BI tool with contractual/political barriers; major data issues |
Factor 5: Local Champion Availability
| Score | Criteria |
|---|---|
| 5 | Tech-forward provider AND Office Manager both engaged and willing to champion; history of leading change |
| 4 | Office Manager willing to champion; providers supportive but not leading |
| 3 | Office Manager willing but stretched thin; provider support unclear |
| 2 | No clear champion identified; Office Manager skeptical but not resistant |
| 1 | Office Manager actively resistant or absent; provider opposition; no internal advocate |
Composite Readiness Score Calculation
| Factor | Weight | Rationale |
|---|---|---|
| IT Infrastructure | 25% | Foundation—without this, nothing works |
| Staff Adaptability | 25% | Adoption depends on people, not just technology |
| Patient Volume | 15% | Impact consideration, but not dominant for pilot selection |
| Tech Stack Compatibility | 20% | Integration complexity is a major risk factor |
| Local Champion | 15% | Champions accelerate adoption but aren't mandatory |
Formula: Composite Score = (IT × 0.25) + (Staff × 0.25) + (Volume × 0.15) + (Tech × 0.20) + (Champion × 0.15)
Score Interpretation:
| Composite Score | Classification | Recommendation |
|---|---|---|
| 4.0–5.0 | High Readiness | Wave 1 or 2 candidate |
| 3.0–3.9 | Moderate Readiness | Wave 2 or 3 candidate |
| 2.0–2.9 | Low Readiness | Remediate before rollout; schedule for final waves |
| 1.0–1.9 | At Risk | Significant remediation required; consider deferring |
Rollout Sequence Recommendation
Sample Readiness Assessment (20-Location Example)
| Location | IT | Staff | Volume | Tech | Champion | Composite | Wave |
|---|---|---|---|---|---|---|---|
| Location A | 5 | 4 | 3 | 4 | 5 | 4.20 | Wave 1 Pilot |
| Location B | 4 | 5 | 3 | 5 | 4 | 4.30 | Wave 1 Pilot |
| Location C | 4 | 4 | 4 | 4 | 4 | 4.00 | Wave 1 Pilot |
| Location D | 4 | 4 | 5 | 4 | 3 | 4.05 | Wave 2 |
| Location E | 4 | 3 | 4 | 5 | 4 | 3.95 | Wave 2 |
| ... | ... | ... | ... | ... | ... | ... | ... |
| Location T | 2 | 2 | 2 | 2 | 2 | 2.00 | Wave 4 + Remediation |
Wave 1 Pilot Selection Criteria:
- Composite score 4.0+ (high readiness)
- Volume score 3–4 (not highest volume—manageable stakes for learning)
- At least one location per region if you operate regionally
- ⚠️ Avoid locations with upcoming leadership changes, remodels, or other major initiatives
Estimated Time: 4–6 hours for Regional Managers to score their locations; 2–3 hours centrally to compile and analyze
4. Rollout Strategy
Recommended Wave Structure
For a 30-location DSO, the following wave structure balances learning velocity with manageable complexity:
| Wave | Locations | Duration | Cumulative Deployed |
|---|---|---|---|
| Wave 1 (Pilot) | 3 locations | 3 weeks | 3 (10%) |
| Wave 2 | 6 locations | 3 weeks | 9 (30%) |
| Wave 3 | 8 locations | 2 weeks | 17 (57%) |
| Wave 4 | 8 locations | 2 weeks | 25 (83%) |
| Wave 5 | 5 locations | 2 weeks | 30 (100%) |
Buffer Between Waves: Minimum 1 week between wave completion and next wave kickoff to capture learnings and update playbook.
Wave 1 Pilot Location Selection Criteria
Select 2–3 locations that optimize for learning, not just success:
| Criterion | Why It Matters |
|---|---|
| High readiness (Composite 4.0+) | De-risk first deployment |
| Moderate volume (Score 3–4) | Enough data to validate insights; stakes manageable |
| Representative of portfolio | At least one "typical" location (not just flagship) |
| Geographic spread | If multi-region, pilot in different regions to surface regional variations |
| Strong local champion | Pilot champions become trainers for later waves |
| Not during major transitions | Avoid locations with imminent leadership changes, renovations, acquisitions |
Timeline Per Wave (Detailed)
Wave 1 (Pilot): 3 Weeks
| Week | Activities |
|---|---|
| Week 1 | Integration setup and testing at pilot locations; champion training; baseline validation |
| Week 2 | Go-live; daily check-ins; troubleshooting; workflow calibration |
| Week 3 | Stabilization; first metrics review; lessons learned documentation |
| Buffer Week | Compile learnings; update training materials; refine configuration templates |
Waves 2–5: 2–3 Weeks Each
| Week | Activities |
|---|---|
| Week 1 | Integration setup; champion training; pre-go-live checklist |
| Week 2 | Go-live; daily check-ins (Mon–Thu); first week review |
| (Week 3 if needed) | Stabilization for complex locations |
| Buffer (3–5 days) | Quick lessons learned; prep for next wave |
Go/No-Go Criteria Between Waves
Before advancing from one wave to the next, verify:
Technical Go/No-Go
☐ Data sync functioning correctly at >95% uptime
☐ No unresolved critical integration bugs
☐ Dashboard data accuracy validated against PMS source (spot-check 5% of records)
Adoption Go/No-Go
☐ >80% of staff at pilot locations trained and actively using system
☐ Champions report team is "comfortable" or better with daily use
☐ No provider refusals to engage
Support Go/No-Go
☐ All critical support tickets resolved
☐ No recurring issues without root cause identified
☐ Support team capacity confirmed for next wave
Business Go/No-Go
☐ 🟣 Executive sponsor confirms satisfaction with pilot results
☐ No business disruptions attributable to implementation
☐ Budget for next wave confirmed (if phased investment)
Scoring: All criteria must be green or yellow with mitigation plan. Any red = pause and remediate.
Rollback Plan
If a wave encounters significant issues:
Immediate Response (Within 24 Hours)
- Convene incident response call: Central IT + Vendor TAM + affected Regional Manager
- Document all symptoms, affected locations, user reports
- Implement immediate workaround if available
Containment Decision Tree
Is the issue affecting patient care or revenue generation?
├── YES → Immediate rollback to PMS-only workflow; pause all other waves
└── NO → Is the issue affecting >50% of wave locations?
├── YES → Pause current wave; implement fix; resume when resolved
└── NO → Isolate affected locations; continue with unaffected locations
Rollback Process
- 🔵 Vendor disables real-time sync (data preserved, not lost)
- Communicate to affected locations: "Return to previous workflow pending resolution"
- Preserve all diagnostic data for root cause analysis
- ⚠️ Do NOT uninstall—maintain ability to resume quickly once resolved
Post-Rollback Requirements
☐ Root cause documented and understood
☐ Fix validated in test environment
☐ 🟣 Executive sponsor approves resumption
☐ Affected locations re-trained on any workflow changes
Key Principle: A rollback is not a failure—it's a planned safety mechanism. Build this messaging into change management.
5. Configuration & Integration (Weeks 2–3)
Step-by-Step Integration with Common PMS
Dentrix Enterprise (Most Common in DSOs)
| Step | Action | Owner | Time |
|---|---|---|---|
| 1 | 🔵 Request Dentrix integration specifications from Dental Intelligence | Vendor | Day 1 |
| 2 | Verify Dentrix version at each location (G6+ recommended, G5 supported) | IT | Day 1 |
| 3 | ⚠️ Confirm eDex API is enabled in Dentrix (Settings → Advanced → eDex) | Local IT/Office Manager | Day 2 |
| 4 | 🔵 Install Dental Intelligence sync agent on Dentrix server | Vendor + IT | Day 3 |
| 5 | Configure sync agent with location credentials | IT | Day 3 |
| 6 | 🔵 Initiate historical data pull (recommend 2 years minimum) | Vendor | Day 4 |
| 7 | Validate data accuracy: Compare 10 patients' records between Dentrix and DI | IT + Office Manager | Day 5 |
| 8 | Configure real-time sync schedule (recommend every 15 minutes) | IT + Vendor | Day 5 |
Estimated Time: 4–6 hours per location (can parallelize across IT team)
Eaglesoft
| Step | Action | Owner | Time |
|---|---|---|---|
| 1 | 🔵 Request Eaglesoft integration specifications from Dental Intelligence | Vendor | Day 1 |
| 2 | Verify Eaglesoft version (21.x+ required) | IT | Day 1 |
| 3 | Enable ODBC connection in Eaglesoft (Technical Reference → ODBC) | IT | Day 2 |
| 4 | ⚠️ Document server location—Eaglesoft local servers require direct network access | IT | Day 2 |
| 5 | 🔵 Install Dental Intelligence sync agent on location server or primary workstation | Vendor + IT | Day 3 |
| 6 | 🔵 Configure ODBC connection string with Dental Intelligence support | Vendor + IT | Day 3 |
| 7 | 🔵 Initiate historical data pull | Vendor | Day 4 |
| 8 | Validate data accuracy | IT + Office Manager | Day 5 |
Estimated Time: 5–7 hours per location (Eaglesoft integration slightly more complex)
Open Dental
| Step | Action | Owner | Time |
|---|---|---|---|
| 1 | 🔵 Request Open Dental integration specifications from Dental Intelligence | Vendor | Day 1 |
| 2 | Verify Open Dental version (18.1+ recommended) | IT | Day 1 |
| 3 | Enable Open Dental API (Setup → Misc Setup → API) | IT | Day 2 |
| 4 | Generate API key for Dental Intelligence access | IT | Day 2 |
| 5 | ⚠️ Configure API permissions (read-only for analytics; do NOT enable write) | IT | Day 2 |
| 6 | 🔵 Enter API credentials in Dental Intelligence admin portal | Vendor | Day 3 |
| 7 | 🔵 Initiate historical data pull | Vendor | Day 3 |
| 8 | Validate data accuracy | IT + Office Manager | Day 4 |
Estimated Time: 3–4 hours per location (Open Dental API is cleanest integration)
Test Environment Setup and Validation Checklist
☐ 🔵 Request test/sandbox environment from Dental Intelligence
☐ Configure test environment with anonymized sample data from 2–3 representative locations
☐ Verify all report types generate correctly
☐ Test user permission levels (Enterprise Admin, Regional Admin, Location User)
☐ Validate SSO integration in test environment before production rollout
☐ ⚠️ Confirm data refresh rates match expectations (real-time vs. batched)
☐ Test alert/notification configuration
☐ Document any discrepancies between test and production behavior
Estimated Time: 8–12 hours for IT team
Data Migration / Historical Data Ingestion
| Step | Action | Owner | Time |
|---|---|---|---|
| 1 | 🟣 Decide: How much historical data to import? (Recommend: 24–36 months) | VP Operations | 30 min |
| 2 | 🔵 Confirm vendor can support historical data volume | Vendor | Day 1 |
| 3 | Schedule historical data pull during off-hours (avoid business hours) | IT + Vendor | Day 2 |
| 4 | ⚠️ Monitor sync during initial pull—large data sets can timeout | IT | During pull |
| 5 | Validate historical data accuracy (spot-check production totals for random past months) | Finance/Ops | Day 3 |
| 6 | Document any gaps or anomalies in historical data | IT | Day 3 |
Security and HIPAA Compliance Verification
Enterprise-Level HIPAA Checklist
| Requirement | Action | Owner | Status |
|---|---|---|---|
| BAA Executed | 🔵 Signed Business Associate Agreement with Dental Intelligence | Legal + Vendor | ☐ |
| Data Encryption (Transit) | Verify TLS 1.2+ for all data transmission | IT | ☐ |
| Data Encryption (Rest) | 🔵 Confirm vendor encrypts stored data (AES-256 standard) | Vendor | ☐ |
| Access Controls | Define and implement role-based access (no shared logins) | IT | ☐ |
| Audit Logging | 🔵 Verify vendor logs all data access and exports | Vendor | ☐ |
| Data Retention Policy | Document how long data is retained in Dental Intelligence | IT + Legal | ☐ |
| Breach Notification | 🔵 Confirm vendor's breach notification timeline (must be <24 hours) | Vendor + Legal | ☐ |
| Employee Training | HIPAA reminder included in Dental Intelligence training materials | Training Team | ☐ |
| Minimum Necessary | Configure system to show only necessary data per role | IT | ☐ |
| Termination Procedures | Document process to revoke access for terminated employees | HR + IT | ☐ |
Estimated Time: 4–6 hours for compliance review; may require legal involvement
Standardized Configuration Template
Create a master configuration document that specifies settings to be identical across all locations:
Standardize Centrally (Do Not Allow Local Variation)
| Setting | Standard Value | Rationale |
|---|---|---|
| Production goals | Centrally defined per location type | Cross-location comparison requires consistent targets |
| KPI definitions | Per baseline metrics agreement | Apples-to-apples comparison |
| Report templates | Standard 5 core reports | Regional managers see consistent views |
| Alert thresholds | Standard (e.g., cancellation >15% triggers alert) | Consistent escalation triggers |
| Data refresh frequency | 15 minutes | Balance of timeliness and system load |
| User role permissions | Enterprise-defined role matrix | Security consistency |
| Dashboard layout | Standard 4-quadrant view | Training consistency |
Location-Specific Configuration (Allow Local Variation)
| Setting | Variation Allowed | Governance |
|---|---|---|
| Provider-level goals | Yes—based on individual provider productivity | Regional Manager approval |
| Morning huddle report customization | Yes—add (not remove) metrics | Office Manager discretion |
| Alert recipients | Yes—designate local recipients | Office Manager configures |
| Operating hours | Yes—reflect actual location hours | Office Manager configures |
| Specialty mix (ortho, perio, etc.) | Yes—reflects practice type | Regional Manager verifies |
Centralized vs. Per-Location Testing
Recommended Approach: Centralized test environment + per-location validation
| Testing Phase | Environment | Purpose |
|---|---|---|
| Integration Testing | Centralized test | Verify PMS connections work; debug integration issues |
| Configuration Testing | Centralized test | Validate standardized settings; test reports |
| UAT (User Acceptance) | Per-location | Office Managers validate their specific data looks correct |
| Performance Testing | Centralized + sample locations | Verify system handles full portfolio data load |
Estimated Time: 12–16 hours centralized testing; 1–2 hours per-location validation
6. Team Training Plan
Train-the-Trainer Model
For DSO deployment, a train-the-trainer model scales efficiently while maintaining quality:
Central Training Team
AI-generated implementation guide based on public vendor information. Verify specifics directly with Dental Intelligence.