tab32
Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
tab32 — Implementation Playbook (DSO)
tab32 Implementation Playbook for DSOs
Cloud-Native Practice Management with Integrated AI
1. Executive Summary
What tab32 Does tab32 is a cloud-native, all-in-one practice management platform that consolidates patient scheduling, clinical charting, imaging, billing, patient engagement, and analytics into a single system. Its AI capabilities span automated appointment optimization, patient communication, treatment acceptance predictions, and real-time business intelligence—all accessible from any location through a unified dashboard.
Why DSOs Specifically Benefit from Cloud-Native Practice Management AI At scale, DSOs face compounding inefficiencies: fragmented PMS instances across locations, inconsistent data structures, manual reporting consolidation, and inability to benchmark performance across the portfolio. tab32's cloud architecture eliminates server maintenance at each site, enables real-time cross-location analytics, and standardizes workflows without requiring physical IT presence. The AI layer transforms this aggregated data into actionable insights—predicting patient no-shows, identifying revenue leakage patterns, and surfacing operational anomalies across 15–50 locations simultaneously. This is infrastructure consolidation and intelligence amplification in one deployment.
Expected Timeline: Decision to Full Deployment
- 15–25 locations: 16–20 weeks
- 25–40 locations: 20–28 weeks
- 40–50 locations: 28–36 weeks
Timeline assumes 3-wave rollout structure with 2-week buffers between waves for learning capture.
2. Pre-Implementation Checklist (Weeks 1–2)
Technical Requirements
Network Standards Across Locations
☐ Minimum 100 Mbps download / 20 Mbps upload per location (200/50 recommended for high-volume sites)
☐ Confirm ISP redundancy or failover plan for business-critical connectivity
☐ Document current network topology at each location (router model, firewall rules, VPN configurations)
☐ Verify all locations can access tab32's cloud endpoints (whitelist required domains)
☐ ⚠️ Audit Wi-Fi coverage in clinical areas—dead zones will create workflow friction
Hardware Requirements Per Location
| Device Type | Minimum Spec | Recommended |
|---|---|---|
| Workstations | Windows 10/11 or macOS 12+, 8GB RAM, i5 equivalent | 16GB RAM, SSD |
| Monitors | 1920x1080 resolution | Dual monitors for clinical staff |
| Tablets (if used) | iPad 6th gen+ or Android 9+ | iPad Pro for imaging review |
| Scanners | TWAIN-compatible for document import | Manufacturer-certified |
| Imaging Sensors | DICOM-compatible (verify specific model compatibility with tab32) | — |
☐ Estimated time: 3–5 hours per location for hardware audit
☐ 🔵 Request tab32's hardware compatibility matrix for imaging sensors
Centralized vs. Location-Level Hosting Decision
🟣 Executive Decision Required
tab32 is cloud-hosted by default, but decisions needed:
- Data residency: Confirm acceptable cloud regions for PHI storage
- Single tenant vs. multi-tenant: Enterprise agreements may include dedicated infrastructure
- Backup/DR requirements: Verify tab32's RPO/RTO meets organizational requirements
☐ Document decision in enterprise architecture review
☐ Estimated time: 1–2 hours executive review
SSO and Identity Management
☐ Confirm identity provider (Okta, Azure AD, Google Workspace, etc.)
☐ 🔵 Request tab32 SSO integration documentation and test credentials
☐ Define user provisioning workflow (manual vs. SCIM automated)
☐ Map role hierarchy: Corporate Admin → Regional Admin → Location Admin → Staff
☐ ⚠️ Verify SSO supports MFA requirements per compliance policies
Estimated time: 4–8 hours for IT to configure and test
Centralized Credentialing
☐ Compile provider NPI numbers, state licenses, DEA numbers for all locations
☐ Determine payer credentialing workflow integration (tab32 RCM module or external)
☐ Establish provider onboarding/offboarding protocol that includes tab32 access
Vendor Onboarding Steps
☐ 🔵 Execute enterprise BAA (Business Associate Agreement)
☐ 🔵 Complete Master Services Agreement with DSO-specific SLAs
☐ 🔵 Obtain dedicated Customer Success Manager contact
☐ 🔵 Obtain Technical Account Manager contact
☐ 🔵 Obtain escalation path contacts (Tier 2/3 support, executive sponsor)
☐ 🔵 Schedule enterprise kickoff call (all stakeholders)
☐ 🔵 Obtain access to tab32 Partner Portal / Admin Console
☐ 🔵 Request enterprise-tier training materials and certification program details
Key Contacts to Establish
| Role | Name | Phone | Response SLA | |
|---|---|---|---|---|
| Customer Success Manager | ||||
| Technical Account Manager | ||||
| Implementation Lead | ||||
| Tier 2 Support | ||||
| Executive Escalation |
Estimated time: 2–4 hours for contract execution; 1 hour for kickoff scheduling
Data/Access Prerequisites
From Current PMS Vendor(s)
☐ Request data export capabilities and formats from each existing PMS
☐ ⚠️ Confirm licensing allows data extraction (some vendors restrict)
☐ Identify historical data scope: How many years of patient records to migrate?
☐ Document imaging archive locations (local servers, cloud, PACS)
☐ Compile API credentials or export permissions for each system
🟣 Executive Decision Required: Define data migration scope
- Full historical records vs. active patients only
- Imaging migration vs. archive access approach
- Financial/billing history depth
Access Credentials Needed Per Location
☐ Admin credentials for current PMS
☐ Imaging system admin access
☐ Clearinghouse login credentials
☐ Patient engagement platform credentials (if separate)
☐ Accounting system integration credentials (QuickBooks, NetSuite, etc.)
Estimated time: 1–2 hours per location to gather; 4–8 hours corporate IT for enterprise systems
Internal Stakeholder Alignment
Stakeholder Alignment Map
| Stakeholder Level | Key Individuals | Role in Implementation | Communication Cadence |
|---|---|---|---|
| Board/Investors | Board Chair, PE partners | Approve budget, monitor ROI | Monthly summary |
| C-Suite | CEO, COO, CFO, CDO | Strategic direction, resource allocation, go/no-go | Weekly during rollout |
| Regional Managers | Regional VPs/Directors | Cascade communication, manage location concerns | Bi-weekly during rollout |
| Location Office Managers | Office Managers (15–50) | Day-to-day implementation, staff coordination | Daily during go-live week |
| Providers | Dentists, Specialists | Clinical workflow adoption, AI output interpretation | Training + go-live support |
| Clinical Staff | Hygienists, Assistants | Workflow execution | Training + go-live support |
| Administrative Staff | Front desk, Billing | Administrative workflow execution | Training + go-live support |
Approval Gates
☐ 🟣 Board approval of budget and timeline
☐ 🟣 C-suite sign-off on rollout strategy and wave structure
☐ 🟣 CDO approval of clinical workflow changes
☐ 🟣 CFO approval of ROI framework and success metrics
☐ Regional manager acknowledgment of pilot location selection
☐ Location manager commitment to champion responsibilities
Estimated time: 2–3 weeks for full alignment; begin parallel with technical prep
Baseline Metrics to Capture
Standardized Measurement Protocol
⚠️ Critical: Metrics must be measured identically across all locations to enable valid cross-location comparison post-implementation.
Operational Metrics (Per Location)
| Metric | Measurement Method | Capture Period | Target Source |
|---|---|---|---|
| Average patients per day | PMS daily schedule report | 30 days pre-launch | Current PMS |
| Average chair time per procedure | Time-stamp analysis or manual sample | 2-week sample | Current PMS/manual |
| Schedule utilization rate | Scheduled hours / available hours | 30 days | Current PMS |
| No-show rate | No-shows / scheduled appointments | 90 days | Current PMS |
| Same-day cancellation rate | Same-day cancels / scheduled | 90 days | Current PMS |
| New patient acquisition | New patient count / month | 90 days | Current PMS |
Financial Metrics (Per Location)
| Metric | Measurement Method | Capture Period | Target Source |
|---|---|---|---|
| Production per provider per day | Total production / provider days | 90 days | Current PMS |
| Collections rate | Collections / production | 90 days | Current PMS/accounting |
| Treatment acceptance rate | Accepted $ / presented $ | 90 days | Current PMS |
| Average case value | Total production / completed cases | 90 days | Current PMS |
| Days in A/R | Aging report snapshot | Point-in-time | Current PMS |
| Claim denial rate | Denied claims / submitted claims | 90 days | Clearinghouse |
| Time to payment | Claim submission to payment receipt | 90 days | Clearinghouse/PMS |
Staff Efficiency Metrics
| Metric | Measurement Method | Capture Period | Target Source |
|---|---|---|---|
| Phone answer rate | Answered / total calls | 30 days | Phone system |
| Average call handle time | Phone system report | 30 days | Phone system |
| Patient check-in time | Arrival to seated (sample) | 2-week sample | Manual/observation |
| End-of-day close time | Last patient checkout to staff departure | 2-week sample | Manual |
☐ Create standardized data collection template distributed to all locations
☐ Assign regional manager accountability for metric collection compliance
☐ Set deadline for all baseline data: 1 week before Wave 1 go-live
☐ Store baseline data in centralized repository (not in PMS being replaced)
Estimated time: 4–6 hours per location for data extraction; 8–12 hours central team for template creation and aggregation
3. Location Readiness Assessment
Scoring Framework
Rate each location 1–5 on the following factors. Calculate composite score as weighted average.
Factor 1: IT Infrastructure Maturity (Weight: 25%)
| Score | Criteria |
|---|---|
| 5 | Fiber internet 500+ Mbps, all workstations <3 years old, modern router with managed firewall |
| 4 | Cable/fiber 200+ Mbps, most workstations <4 years old, business-grade networking |
| 3 | 100+ Mbps, mixed workstation ages, consumer-grade but reliable networking |
| 2 | 50–100 Mbps, several workstations >5 years old, inconsistent connectivity |
| 1 | <50 Mbps, outdated hardware, frequent network issues |
Factor 2: Staff Tenure and Adaptability (Weight: 20%)
| Score | Criteria |
|---|---|
| 5 | Low turnover (<15%/year), previous successful tech implementations, team actively requests improvements |
| 4 | Moderate turnover (15–25%), has adopted new systems before, generally positive attitude |
| 3 | Average turnover (25–35%), mixed results with previous tech changes |
| 2 | Higher turnover (35–50%), resistance to recent changes, training gaps |
| 1 | High turnover (>50%), active resistance to technology, minimal training completion history |
Factor 3: Patient Volume (Weight: 15%)
Note: Higher volume increases both impact and implementation risk
| Score | Criteria |
|---|---|
| 5 | Moderate-high volume (60–80 patients/day)—optimal for impact with manageable complexity |
| 4 | Moderate volume (40–60 patients/day)—good for pilot with lower risk |
| 3 | Lower volume (<40 patients/day)—limited impact but low risk for testing |
| 2 | Very high volume (80–100/day)—high impact but significant go-live risk |
| 1 | Extremely high volume (>100/day)—recommend later wave due to disruption risk |
Factor 4: Existing Tech Stack Compatibility (Weight: 25%)
| Score | Criteria |
|---|---|
| 5 | Currently on tab32 or cloud-native PMS; all imaging DICOM-compliant; modern integrations |
| 4 | Mainstream PMS (Dentrix, Eaglesoft, Open Dental) with standard configurations |
| 3 | Mainstream PMS with customizations that may require migration attention |
| 2 | Legacy PMS with limited export capabilities; imaging compatibility concerns |
| 1 | Custom/proprietary PMS; significant data extraction challenges; incompatible imaging |
Factor 5: Local Champion Availability (Weight: 15%)
| Score | Criteria |
|---|---|
| 5 | Identified tech-forward Office Manager + Provider both willing to champion |
| 4 | One strong champion (either OM or provider) with full commitment |
| 3 | Potential champion identified but needs development/support |
| 2 | No clear champion but leadership is supportive |
| 1 | No champion and leadership is skeptical |
Composite Score Calculation
Formula: (IT × 0.25) + (Staff × 0.20) + (Volume × 0.15) + (Tech Stack × 0.25) + (Champion × 0.15)
Score Interpretation
| Composite Score | Readiness Tier | Wave Recommendation |
|---|---|---|
| 4.0–5.0 | High Readiness | Wave 1 candidate |
| 3.0–3.9 | Moderate Readiness | Wave 2 candidate |
| 2.0–2.9 | Lower Readiness | Wave 3 or remediation first |
| <2.0 | At Risk | Remediate before including in rollout |
Location Assessment Template
| Location | IT (1-5) | Staff (1-5) | Volume (1-5) | Tech (1-5) | Champion (1-5) | Composite | Wave |
|---|---|---|---|---|---|---|---|
| Location A | |||||||
| Location B | |||||||
| etc. |
☐ Complete assessment for all locations
☐ Review scores with Regional Managers for validation
☐ 🟣 Present wave assignments to C-suite for approval
☐ Communicate wave assignments to location managers
Estimated time: 1–2 hours per location for assessment; 2–4 hours central analysis
4. Rollout Strategy
Recommended Wave Structure
For a 15–50 location DSO, deploy in 3–4 waves:
Wave 1: Pilot (2–3 Locations)
Duration: 4 weeks go-live + 2 weeks stabilization
Purpose: Validate playbook, identify issues, train internal implementation team
Selection Criteria for Wave 1:
- Composite readiness score ≥4.0
- Geographically accessible for on-site support
- Strong local champion (score 4–5)
- Representative of portfolio mix (ideally: 1 GP-focused, 1 higher-specialty mix)
- ⚠️ Avoid flagship locations—pilot friction shouldn't impact highest-profile sites
- ⚠️ Avoid locations with leadership changes in next 90 days
Wave 2: Expansion (5–8 Locations)
Duration: 3 weeks go-live + 2 weeks stabilization
Purpose: Scale validated approach, stress-test central support capacity
Selection Criteria:
- Composite readiness score ≥3.5
- Regional clustering to optimize support logistics
- Mix of volume levels to test workflow variations
Wave 3: Broad Deployment (Remaining Locations)
Duration: 2–3 weeks per cluster of 5–8 locations
Purpose: Complete deployment with proven playbook
Approach:
- Further sub-divide Wave 3 into clusters based on geography
- Parallel deployments possible once central team is proficient
Wave 4 (If Needed): Remediation Locations
Duration: Varies
Purpose: Address locations requiring infrastructure upgrades before deployment
Timeline Per Wave
| Phase | Wave 1 | Wave 2 | Wave 3 |
|---|---|---|---|
| Configuration & Integration | Week 1–2 | Week 8–9 | Week 14–16 |
| Training | Week 2–3 | Week 9–10 | Week 16–18 |
| Soft Launch / Parallel Run | Week 3–4 | Week 10–11 | Week 18–19 |
| Full Go-Live | Week 4 | Week 11 | Week 19 |
| Stabilization | Week 5–6 | Week 12–13 | Week 20–21 |
| Wave Review / Go/No-Go | Week 7 | Week 14 | Week 22 |
Total estimated timeline for 25-location DSO: 22 weeks
Buffer between waves: 2 weeks minimum
Go/No-Go Criteria Between Waves
Mandatory Criteria (All Must Pass)
☐ No unresolved Severity 1 issues from previous wave
☐ Data integrity validated—patient records, financial data, imaging all accessible
☐ Staff competency verified—all roles can perform core workflows without assistance
☐ Patient-facing functions operational—scheduling, reminders, check-in
☐ Billing functions operational—claims submitting, payments posting
Performance Criteria (Thresholds)
| Metric | Green (Proceed) | Yellow (Proceed with Caution) | Red (Hold) |
|---|---|---|---|
| Staff satisfaction | >70% positive | 50–70% positive | <50% positive |
| System uptime | >99% | 97–99% | <97% |
| Avg support tickets/location/week | <10 | 10–20 | >20 |
| Daily close completion | 100% on time | 95% on time | <95% on time |
| Provider workflow completion rate | >90% | 80–90% | <80% |
🟣 Executive Decision Required: Go/No-Go approval from COO and CDO before advancing waves
Rollback Plan
Triggers for Rollback Consideration
- Severity 1 issue unresolved >48 hours affecting patient care
- Data loss or integrity corruption
- Integration failure preventing billing/claims for >24 hours
- Staff unable to perform basic functions after 72 hours
Rollback Procedure (Per Location)
- 🟣 Executive approval to rollback
- Notify tab32 support (capture all logs, document issue)
- Re-enable previous PMS access (maintain licenses during transition period)
- Communicate to staff: rollback messaging script
- Resume previous workflows
- Document failure mode for root cause analysis
- Do not proceed with subsequent waves until resolved
Critical Safeguard
⚠️ Maintain parallel access to previous PMS for minimum 30 days post-go-live per location. Do not terminate legacy PMS contracts until stabilization is confirmed.
Estimated time for rollback execution: 4–8 hours per location
5. Configuration & Integration (Weeks 2–3)
Practice Management System Integration
Migrating FROM Dentrix
☐ Export patient demographic data (Dentrix > Letters > Patient Data Export)
☐ Export clinical data via eClinicalWorks bridge or third-party extraction tool
☐ ⚠️ Dentrix does not provide native full database export—verify extraction tool licensing
☐ 🔵 Provide extracted data to tab32 migration team in specified format
☐ 🔵 tab32 performs data mapping and transformation
☐ Validate sample records (minimum 50 patients) before full migration
☐ Reconcile patient counts: source system vs. tab32
☐ Verify procedure history, treatment plans, and clinical notes
Estimated time: 8–16 hours per location depending on data volume
Migrating FROM Eaglesoft
☐ Use Patterson Data Extraction utility (may require Patterson engagement)
☐ Export patient demographics, ledger history, treatment history
☐ ⚠️ Eaglesoft image integration requires separate imaging migration
☐ 🔵 Provide extracted data to tab32 in specified format
☐ Validate sample records before full migration
☐ Reconcile financial balances: current A/R must match
Estimated time: 8–16 hours per location
Migrating FROM Open Dental
☐ Use Open Dental's native database export (MySQL backup)
☐ Export patient data, procedures, ledger, imaging pointers
☐ ⚠️ Open Dental is most migration-friendly—leverage direct database access
☐ 🔵 Provide database backup to tab32 migration team
☐ Validate sample records
☐ Verify custom fields and procedure codes mapped correctly
Estimated time: 4–8 hours per location
Imaging System Integration
DICOM-Compatible Systems (Most Sensors)
☐ Verify sensor model on tab32 compatibility list
☐ 🔵 Obtain tab32 DICOM bridge configuration settings
☐ Configure sensor to output to tab32 DICOM endpoint
☐ Test capture workflow: acquire image → verify appears in patient chart
☐ Validate image quality matches previous system
☐ Configure image categories and naming conventions
Proprietary Imaging Systems (Dexis, Carestream, etc.)
☐ 🔵 Confirm tab32 integration availability for specific system
☐ Install tab32 imaging bridge software (if required)
☐ Configure bridge connection to imaging server
☐ ⚠️ Some integrations require imaging vendor cooperation—initiate early
☐ Test round-trip: capture in imaging software → view in tab32
☐ Verify annotation and measurement tools functional
Historical Image Migration
🟣 Executive Decision Required: Migrate historical images or maintain archive access?
Option A: Full Migration
☐ Export images from legacy system in DICOM or JPEG format
☐ 🔵 Provide to tab32 for ingestion with patient record linking
☐ Validate sample images post-migration
☐ Estimated time: 8–24 hours per location depending on archive size
Option B: Archive Access (Maintain Legacy for History)
☐ Keep legacy imaging viewer accessible for historical images
☐ New images captured directly in tab32
☐ Document access procedure for staff
☐ Plan future migration when practical
☐ Estimated time: 2–4 hours per location for documentation
Test Environment Setup
Enterprise Approach (Recommended for DSOs)
☐ 🔵 Request dedicated enterprise sandbox environment from tab32
☐ Configure sandbox with representative sample data (anonymized production data subset)
☐ Mirror enterprise SSO configuration in sandbox
☐ Establish test user accounts for each role type
☐ Document test environment access credentials in secure system
Validation Checklist (Perform in Test Environment First)
☐ Patient search and record retrieval
☐ Appointment scheduling (single, recurring, multi-provider)
☐ Clinical charting (perio, hard tissue, progress notes)
☐ Treatment planning and case presentation
☐ Image capture and viewing
☐ Claim creation and submission (test clearinghouse)
☐ Payment posting and ledger updates
☐ Patient communication (email, SMS, appointment reminders)
☐ Report generation (daily, monthly, custom)
☐ User permission enforcement by role
☐ SSO login and logout
☐ Multi-location user access (corporate user switching locations)
Estimated time for test environment validation: 16–24 hours central IT/implementation team
Security and HIPAA Compliance Verification
Enterprise-Level HIPAA Checklist
☐ 🔵 Execute Business Associate Agreement (BAA) with tab32
☐ Verify tab32 SOC 2 Type II certification current
☐ 🔵 Request tab32 security documentation package (penetration test results, security architecture)
☐ Verify data encryption at rest (AES-256 or equivalent)
☐ Verify data encryption in transit (TLS 1.2+)
☐ Confirm data center physical security certifications
☐ Verify backup procedures and disaster recovery capabilities
☐ 🟣 Compliance officer sign-off on security posture
Access Control Configuration
☐ Define role-based access control (RBAC) matrix across organization
☐ Configure permission levels in tab32 matching RBAC matrix
☐ Implement minimum necessary access principle
☐ Configure automatic session timeout (15 minutes recommended)
☐ Enable audit logging for PHI access
☐ Configure access alerts for unusual patterns (if available)
Data Governance
☐ Document data retention policies and configure in tab32
☐ Establish procedure for patient data deletion requests (HIPAA right to access)
☐ Configure user access review process (quarterly recommended)
☐ Document breach response procedure including tab32's role
Estimated time for security review: 8–16 hours compliance/IT team
Standardized vs. Location-Specific Configuration
Standardized Configuration Template (Apply to ALL Locations)
| Setting Category | Standardized Configuration |
|---|---|
| Appointment types | Master list of appointment types with standard durations |
| Procedure codes | Unified CDT code list with standard fees (regional variations allowed) |
| Clinical note templates | Organization-approved templates for consistency |
| Permission roles | Standardized role definitions |
| Patient communication templates | Approved email/SMS templates |
| Report definitions | Standardized KPI reports for cross-location comparison |
| Insurance plans | Master payor list with standard configurations |
| SSO configuration | Unified identity provider integration |
| Audit settings | Consistent logging and retention |
Location-Specific Configuration (Allow Variation)
| Setting Category | Local Discretion Allowed |
|---|---|
| Provider schedules | Each location sets provider availability |
| Fee schedules | Regional PPO fee variations |
| Specialty-specific templates | Specialty locations may need additional templates |
| Operatory setup | Number and naming of operatories |
| Local payor additions | Location-specific contracted payors |
| Lab preferences | Local lab integrations |
☐ Create master configuration template document
☐ 🔵 Work with tab32 to clone configuration across locations
☐ Document deviation approval process for location-specific needs
Estimated time: 16–24 hours to create templates; 2–4 hours per location to apply
6. Team Training Plan
Train-the-Trainer Model
Champion Selection Criteria
Each location requires one designated champion. Ideal candidates:
☐ Office Manager or senior front desk with ≥2 years tenure
☐ Demonstrated technology proficiency
☐ Strong communication skills—respected by clinical and admin staff
☐ Available for 8–12 hours of champion training
☐ Committed to ongoing support responsibility post-launch
☐ Ideally: enthusiasm for the change (not just compliance)
Backup Champion: Identify a secondary contact per location for continuity
Champion Responsibilities
Pre-Launch:
- Complete champion certification program
- Configure location-specific settings with central team
- Schedule and coordinate staff training sessions
- Prepare location for go-live (hardware, network, signage)
Go-Live:
- First point of contact for location staff questions
- Daily check-in with central implementation team
- Document issues and escalate appropriately
- Support struggling staff members
Post-Launch:
- Onboard new hires to tab32
- Conduct quarterly refresher training
- Funnel feature requests and feedback to central team
Champion Certification Program
Module 1: Platform Fundamentals (2 Hours)
☐ System architecture overview
☐ Navigation and user interface
☐ Enterprise vs. location settings
☐ Common workflows overview
Module 2: Clinical Workflows (2 Hours)
☐ Patient check-in process
☐ Clinical charting deep-dive
☐ Treatment planning and presentation
☐ Imaging workflows
☐ AI features: detection, treatment suggestions
Module 3: Administrative Workflows (2 Hours)
☐ Scheduling mastery
☐ Insurance and billing
☐ Patient communications
☐ Reporting and analytics
Module 4: Troubleshooting and Support (1 Hour)
☐ Common issues and resolutions
☐ When to escalate vs. self-resolve
☐ Support ticket creation
☐ Resource locations (knowledge base, documentation)
Module 5: Training Delivery (1 Hour)
☐ Adult learning principles (brief)
☐ Role-specific training delivery techniques
☐ Handling resistance
☐ Competency verification methods
🔵 Champion certification delivered by tab32 in cohorts across waves
☐ Certification assessment required before champion status granted
☐ Certification must be complete ≥1 week before location go-live
Estimated time: 8 hours per champion
Role-Specific Training Outlines
These outlines are designed for champions to deliver locally, customized to location context.
Providers (Dentists/Specialists)
Training Duration: 2 hours initial + 30-minute follow-up after 1 week
Format: Live demo with hands-on practice; small groups (2–4 providers max)
Content:
- Login and patient selection (10 min)
- Clinical charting interface—navigation, inputs, voice options if available (30 min)
- AI-assisted features: treatment detection, radiograph analysis (30 min)
- Treatment planning workflow and patient presentation (20 min)
- Imaging capture and annotation (15 min)
- Progress notes and documentation (10 min)
- Q&A and hands-on practice (20 min)
Common Resistance Points:
- "This will slow me down" → Demonstrate efficiency gains; acknowledge 2-week learning curve
- "I don't trust AI diagnoses" → Clarify AI assists, does not replace; all decisions remain with provider
- "My current system works fine" → Focus on portfolio benefits; acknowledge individual adjustment
Day 1 Cheat Sheet for Providers:
TAB32 PROVIDER QUICK REFERENCE
─────────────────────────────────
☐ LOGIN: [URL] → SSO with your org credentials
☐ FIND PATIENT: Search bar top-right, type last name
☐ OPEN CHART: Click patient name → Clinical tab
☐ CHARTING: Click tooth → select condition or procedure
☐ AI ASSIST: Yellow highlights = AI-detected findings → review, accept/dismiss
☐ TREATMENT PLAN: Click "+ Treatment" → select procedures → Save
☐ NOTES: Progress Notes tab → use template or free text → Sign
☐ IMAGING: Imaging tab → Acquire → select sensor → capture
☐ HELP: Click "?" icon or contact [Champion Name] at [extension]
Hygienists
Training Duration: 1.5 hours initial
Format: Live demo with hands-on practice
Content:
- Login and schedule review (10 min)
- Patient check-in verification and medical history review (15 min)
- Periodontal charting workflow (30 min)
- Intraoral imaging capture if applicable (15 min)
- Documentation and handoff to provider (10 min)
- Hands-on practice (10 min
AI-generated implementation guide based on public vendor information. Verify specifics directly with tab32.