CureMint — Implementation Playbook (DSO)

Executive Summary

CureMint is a cloud-native practice management platform purpose-built for multi-location dental organizations, enabling unified scheduling, patient records, financial management, and clinical workflows across dispersed locations. DSOs benefit uniquely because they eliminate the complexity of managing siloed practice software across acquired practices while maintaining local autonomy and operational flexibility. A full DSO deployment (8–15 locations) typically reaches productivity parity in 12–16 weeks, with ROI materialization beginning at week 8.

Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Infrastructure & Connectivity

• Audit current internet bandwidth at each location (minimum 25 Mbps recommended; 50+ for high-volume centers)
• Confirm network stability and backup connectivity (4G failover strongly advised)
• Validate that existing hardware meets minimum specs: clinical workstations (4GB RAM minimum), front desk systems (8GB RAM, modern OS)
• Ensure compliance infrastructure exists: HIPAA-compliant servers, encrypted backups, audit logging capability

Data Migration Prerequisites

• Export patient databases from legacy systems (identify format: Dentrix, Eaglesoft, Open Dental, spreadsheets, paper records)
• Document custom fields, codes, and workflows unique to each practice
• Perform data quality audit: identify duplicate patient records, missing contact info, inactive accounts
• Calculate data volume: DSO with 12 locations typically holds 150k–400k patient records; plan migration bandwidth accordingly

Stakeholder Alignment

Executive Sponsorship

• Secure DSO leadership (COO/CTO) as executive sponsor—this prevents scope creep and resource conflicts
• Establish steering committee: practice owners, IT director, operations lead, clinical champion
• Define success criteria explicitly: schedule cycle time reduction (target 20%), claims processing acceleration (target 15%), staff satisfaction baseline

Practice-Level Buy-In

• Conduct listening sessions at 2–3 pilot locations; document concerns (workflow disruption, learning curve, job security fears)
• Identify clinical and administrative champions at each location—these become your change agents during rollout
• Create a simple one-page value proposition specific to dentistry: "3 fewer minutes per patient check-in" resonates better than "unified data architecture"

Baseline Metrics to Capture

Before implementing, establish these measurements across all locations:

Pilot Wave (Weeks 3–6)

Location Selection Criteria

Choose 2–3 locations for pilot (not just the easiest; include one medium-complexity site):

• Clinical Volume: 1,500–3,000 patient visits/month (large enough to stress-test, small enough to control)
• Tech Readiness: At least one staff member computer-comfortable; willingness to document workarounds
• Leadership Stability: Practice manager/owner committed for full 16-week timeline
• Data Quality: Avoid the most fragmented practice initially; avoid the most advanced (they'll resist standardization)
• Geographic Spread: If possible, pilot in different regions to test connectivity variability

Avoid: Selecting only your flagship location (creates false confidence) or a struggling location (confounds variables).

Configuration and Setup

Week 3: Discovery & Configuration

• Conduct full-day configuration workshops at each pilot location
• Map current workflows: patient intake, appointment scheduling, insurance verification, treatment planning, payment collection
• Configure CureMint templates to match existing processes (don't force change yet—match, then optimize)
• Set up insurance fee schedules (bulk upload or manual entry for top 20 carriers)
• Configure user roles: hygienist, front desk, dentist, billing, admin; test permission inheritance across locations

Week 4: Data Migration

• Perform soft migration (shadow mode): run CureMint parallel to legacy system for 1 week
• Identify data mapping gaps in real-time; reconcile duplicate patient records
• Test appointment imports; run sample batch reconciliation
• Validate all patient photos, X-rays, and clinical notes transferred correctly
• Perform rollback drill so teams practice reverting if critical issues arise

Week 5: Live Cutover

• Go-live on Tuesday (not Monday; gives buffer for emergency fixes)
• Maintain legacy system for 48 hours in read-only mode as safety net
• Establish war room: CureMint implementation team on-site at each location for 3 days
• Document every workflow deviation and issue in shared log; fix high-priority items same-day

Week 6: Stabilization

• Reduce on-site support to 4 hours daily; move to remote check-ins
• Conduct team retrospectives: what broke, what worked, what surprised us
• Gather feedback on scheduling, patient intake, clinical note templates
• Prepare standardization recommendations for rollout wave (week 7+)

Training Approach

Structured Role-Based Training (4–6 hours per location)

• Front Desk (3 hours): Patient check-in, appointment booking, insurance eligibility, payment posting
• Clinical Staff (2 hours): Treatment notes, clinical photography, prescription generation, perio charting
• Billing/Admin (4 hours): Insurance claims, aging reports, collections workflow, reporting/analytics
• Practice Manager (6 hours): Staff scheduling, reporting, compliance audits, backup procedures

Delivery Format

• Live demonstration (not slides); staff follows along on their workstations
• Hands-on practice with 5–10 realistic patient scenarios per role
• Job aid cards (laminated, pocket-sized) for top 5 daily workflows
• Video library (5–10 minute clips per feature) available for reference; accessible offline

Scaled Rollout (Weeks 7–16)

Wave Planning

Wave 2 (Weeks 7–10): 3–4 locations

• Select locations 30% operationally similar to pilot; avoid clustering geographically to spread support load
• Reuse pilot training materials; reduce on-site support to 48 hours (not 3 days)

Wave 3 (Weeks 11–14): Remaining 40–60% of portfolio

• Compress timeline further; 24-hour on-site support + 10 days remote check-ins
• Empower practice managers to lead peer training (use champion model)

Wave 4 (Weeks 15–16): Tail locations

• Smallest, lowest-complexity practices; mostly self-service with daily phone support

Change Management

Weekly Standups (30 minutes, all locations)

• Share top 3 adoption blockers; solve live if possible
• Celebrate wins: "Midtown location reduced check-in time 18%"
• Normalize struggle: "Week 2 is always hardest; we've seen this everywhere"

Resistance Mitigation

• Acknowledge fears explicitly: job security, skill obsolescence (address via career development)
• Involve skeptics in solution design: "What would make this easier for your team?"
• Track adoption by behavior, not sentiment: clock when staff move from "aided by trainer" to "self-sufficient"

Stabilization Metrics

• Staff efficiency: tracking time-to-task improvements weekly
• Patient satisfaction: CSAT scores for check-in and clinical experience
• Clinical accuracy: error rates in treatment codes, diagnosis entry

Support Infrastructure

Tiered Support Model

Self-Service Knowledge Base

• Searchable video library (5-minute clips ke