Denti.AI Scribe — Implementation Playbook (DSO)

Denti.AI Scribe Implementation Playbook

A Strategic Guide for DSO Deployment

---

1. Executive Summary

What Denti.AI Scribe Does

Denti.AI Scribe is an AI-powered ambient documentation solution that listens to provider-patient conversations in real-time, automatically generating structured clinical notes, treatment narratives, and procedure documentation directly into your practice management system. It eliminates manual charting by converting natural conversation into compliant, comprehensive dental records.

Why DSOs Specifically Benefit from AI Scribes

Scale Advantages:

• A single hygienist saves 45-60 minutes daily on documentation; across 50 locations with 150+ hygienists, this translates to 112+ recovered clinical hours per day
• Documentation quality becomes consistent across your entire footprint, regardless of individual provider habits
• Training investment amortizes across all locations rather than being absorbed by a single practice

Standardization Benefits:

• Uniform note quality reduces compliance risk across all locations simultaneously
• Standardized terminology improves insurance claim accuracy at scale
• Consistent documentation supports defensibility in an increasingly litigious environment

Data Aggregation Value:

• Enterprise-wide documentation patterns reveal clinical trend insights impossible to see at the practice level
• Aggregated data supports value-based care initiatives and payor negotiations
• Cross-location benchmarking identifies documentation efficiency outliers for targeted intervention

Expected Timeline: Decision to Full Deployment

Phase	Duration	Cumulative
Pre-Implementation & Planning	2 weeks	Week 2
Wave 1 Pilot (2-3 locations)	4 weeks	Week 6
Learning Capture & Refinement	2 weeks	Week 8
Wave 2 Expansion (5-8 locations)	4 weeks	Week 12
Wave 3+ Full Rollout	6-10 weeks	Week 18-22
Post-Launch Optimization	8 weeks	Week 26-30

Total Timeline: 6-7 months from decision to full deployment and optimization across 15-50 locations

---

2. Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Hardware Requirements

☐ Microphone hardware per operatory

• Recommended: Ceiling-mounted omnidirectional microphones (vendor-certified models)
• Alternative: Provider-worn lapel microphones (backup for high-noise environments)
• Minimum: Tablet/workstation with quality built-in microphone (not recommended for production)

☐ Workstation specifications per operatory

• Windows 10/11 or macOS 12+
• Minimum 8GB RAM (16GB recommended)
• Chrome, Edge, or Safari (latest versions)
• Display resolution: 1920x1080 minimum

☐ Network requirements per location

• Minimum: 25 Mbps upload/download per location
• Recommended: 50+ Mbps with <50ms latency
• Dedicated bandwidth for clinical systems (QoS configured)
• Ethernet preferred for operatory workstations; Wi-Fi 6 acceptable

Software Requirements

☐ PMS compatibility verified (see Section 5 for specific versions) ☐ Browser extensions or desktop agent installed (per vendor specifications) ☐ Imaging software integration module (if applicable)

⏱️ Time estimate: 3-5 hours per location for technical inventory and gap assessment

---

Vendor Onboarding Steps

☐ 🔵 Execute enterprise BAA (Business Associate Agreement)

• Request DSO-specific BAA covering all current and future locations
• Legal review: 3-5 business days typical

☐ 🔵 Establish vendor contacts

Role	Purpose	Response SLA
Enterprise Account Manager	Strategic relationship, escalations	4 hours
Implementation Lead	Technical deployment, configuration	2 hours
Technical Support (Tier 1)	Day-to-day issues	1 hour
Technical Support (Tier 2)	Complex integration issues	4 hours
Customer Success Manager	Adoption metrics, optimization	24 hours

☐ 🔵 Schedule enterprise kickoff call (Week 1)

• Attendees: VP Ops, IT Director, CDO, Vendor Implementation Lead
• Agenda: Timeline alignment, technical prerequisites, pilot location selection

☐ 🔵 Obtain enterprise license documentation

• Confirm per-provider vs. per-location vs. enterprise pricing structure
• Document scaling terms for adding locations

⏱️ Time estimate: 4-6 hours total for vendor onboarding coordination

---

Data/Access Prerequisites

☐ PMS administrative credentials for integration setup

• Dentrix: Practice administrator login with API access
• Eaglesoft: System administrator credentials
• Open Dental: Central management credentials (if using Open Dental Cloud)

☐ 🔵 API keys/credentials from vendor

• OAuth tokens for SSO integration
• API endpoint documentation
• Webhook configuration parameters

☐ Provider roster export (all locations)

• NPI numbers, license numbers, specialties
• PMS provider IDs for each system

☐ User directory export for SSO mapping

• Email addresses for all clinical staff
• Role designations (provider, hygienist, assistant, admin)

☐ Network access configuration

• Firewall whitelist for vendor endpoints
• Proxy configuration (if applicable)
• SSL certificate verification requirements

⏱️ Time estimate: 8-12 hours for central IT to compile prerequisites

---

Internal Stakeholder Alignment

🟣 Stakeholder Alignment Map

Stakeholder	Role in Implementation	Engagement Level	Key Concerns
Board/Investors	Approval of capital expenditure, ROI expectations	Informed (monthly)	Financial return, competitive positioning
CEO	Strategic sponsor, resource allocation	Accountable	Enterprise risk, timeline
CDO (Chief Dental Officer)	Clinical workflow approval, provider adoption	Responsible	Clinical accuracy, provider acceptance
VP of Operations	Implementation owner, cross-functional coordination	Responsible	Timeline, budget, operational disruption
CFO	Budget approval, ROI validation	Consulted	Cost structure, measurable savings
IT Director	Technical integration, security, infrastructure	Responsible	Security, integration, support burden
Regional Managers	Wave execution, local escalations	Responsible	Location readiness, staff management
Office Managers	Local implementation, daily operations	Responsible	Workflow changes, staff training
Providers (Dentists)	End users, clinical validation	Consulted	Time savings, note quality
Hygienists	End users (if in scope)	Informed	Workflow changes

Approval Requirements

☐ 🟣 Board/Investor notification of AI investment (if >$X threshold per your governance) ☐ 🟣 C-suite approval for enterprise license agreement ☐ 🟣 CDO sign-off on clinical workflow changes ☐ 🟣 IT Director approval of security and compliance requirements ☐ Regional manager acknowledgment of rollout timeline and responsibilities

⏱️ Time estimate: 1-2 weeks for full stakeholder alignment cycle

---

Baseline Metrics (Capture BEFORE Go-Live)

⚠️ Critical: Standardize measurement methodology across all locations

Metric Category	Specific Metric	Measurement Method	Frequency
Documentation Time	Minutes per patient note (provider-reported)	Time study sampling (10 patients/provider)	Weekly average
Documentation Time	End-of-day charting time (minutes after last patient)	Office manager tracking	Daily log
Revenue Cycle	Claim denial rate (documentation-related)	RCM system report	Monthly
Revenue Cycle	Average days to claim submission	PMS report	Monthly
Revenue Cycle	Incomplete chart rate at end of day	PMS audit	Weekly
Clinical Productivity	Patients seen per provider per day	PMS scheduling report	Weekly average
Clinical Productivity	Hygiene production per hour	PMS report	Monthly
Staff Satisfaction	Provider satisfaction (1-10 scale)	Anonymous survey	Baseline + monthly
Compliance	Chart audit pass rate	Random chart sampling (5%)	Monthly

Cross-Location Standardization Requirements

☐ Create standardized data dictionary defining each metric precisely ☐ Establish common reporting cadence (weekly/monthly) across all locations ☐ Implement uniform time study protocol for documentation timing ☐ Deploy identical survey instrument for staff satisfaction baseline ☐ Designate regional manager responsibility for data collection verification

⏱️ Time estimate: 2 weeks to establish baseline across all locations ⚠️ Common failure point: Inconsistent baseline measurement makes ROI calculation unreliable

---

Enterprise-Level Requirements

Network Standards Across Locations

☐ Minimum bandwidth certification per location (document in readiness assessment) ☐ QoS policy deployment prioritizing AI scribe traffic ☐ Firewall rules templated for consistent deployment ☐ Network monitoring extended to track AI scribe connectivity

Hosting Architecture Decision

Option	Pros	Cons	Recommendation
Centralized (Cloud)	Single management point, uniform updates, easier compliance	Internet dependency, latency in some regions	✅ Recommended for most DSOs
Distributed (Edge)	Lower latency, works during internet outages	Complex management, inconsistent versions	Consider only for locations with poor connectivity

☐ 🟣 Document hosting architecture decision and rationale

Single Sign-On (SSO) Configuration

☐ Verify vendor SSO compatibility (SAML 2.0, OAuth 2.0, or specific IdPs) ☐ Map SSO user groups to Denti.AI Scribe roles ☐ Configure provisioning workflow (auto-provisioning vs. manual) ☐ Test SSO in staging environment before production deployment

Centralized Credentialing

☐ Create central user administration model

• Who can create/modify/deactivate users?
• Regional vs. central control boundaries ☐ Establish role-based access control (RBAC) template
• Provider role: Full documentation access
• Hygienist role: Limited to hygiene notes
• Admin role: Reporting access only ☐ Define de-provisioning workflow for terminated employees

⏱️ Time estimate: 1-2 weeks for enterprise architecture decisions and SSO setup

---

3. Location Readiness Assessment

Scoring Framework

Score each factor 1-5 per location. Total possible score: 25 points.

Factor 1: IT Infrastructure Maturity (1-5)

Score	Criteria
5	Fiber internet >100 Mbps, hardware <2 years old, PMS current version, existing audio/video equipment
4	Cable internet >50 Mbps, hardware <3 years old, PMS within 1 version of current
3	Internet 25-50 Mbps, hardware 3-4 years old, PMS 2+ versions behind but supported
2	Internet <25 Mbps, hardware 4-5 years old, PMS requires upgrade for integration
1	Internet unreliable, hardware >5 years, PMS unsupported version

Factor 2: Staff Tenure and Adaptability (1-5)

Score	Criteria
5	Turnover <10%, previous successful tech rollout, staff actively requests new technology
4	Turnover 10-20%, successful tech adoption history, generally positive toward change
3	Turnover 20-30%, mixed tech adoption history, neutral toward change
2	Turnover 30-40%, recent failed tech rollout, some resistance to change
1	Turnover >40%, no successful tech adoptions, active resistance to change

Factor 3: Patient Volume (1-5) — Impact Potential

Score	Criteria
5	Top 20% of locations by patient volume (highest impact potential)
4	60-80th percentile
3	40-60th percentile
2	20-40th percentile
1	Bottom 20% (lowest impact, but also lowest risk for pilot)

Note: For Wave 1 pilots, consider locations scoring 2-3 on volume (representative but not your highest-stakes locations).

Factor 4: Existing Tech Stack Compatibility (1-5)

Score	Criteria
5	PMS with native Denti.AI integration, modern imaging system, existing integrations working well
4	PMS with API integration available, compatible imaging system
3	PMS requires middleware, some manual steps required
2	PMS integration challenging but possible, custom development needed
1	PMS unsupported, major infrastructure changes required

Factor 5: Local Champion Availability (1-5)

Score	Criteria
5	Tech-forward provider + engaged office manager, both committed to championing
4	One strong champion identified (provider or office manager)
3	Potential champion identified but not yet committed
2	No obvious champion, would need to develop/recruit
1	Leadership skeptical or resistant, no champion possible

---

Readiness Assessment Template

Location	IT Score	Staff Score	Volume Score	Tech Stack Score	Champion Score	Total	Recommended Wave
Example: Main St	4	5	3	4	5	21	Wave 1 (Pilot)
Example: Oak Ave	3	3	4	3	3	16	Wave 2
Example: Downtown	2	2	5	2	2	13	Wave 3

Rollout Wave Recommendations

Total Score	Readiness Tier	Recommended Wave
21-25	High Readiness	Wave 1 (Pilot) — 2-3 locations
16-20	Moderate Readiness	Wave 2 — 5-8 locations
11-15	Lower Readiness	Wave 3 — Requires prep work
≤10	Not Ready	Hold — Address infrastructure/staffing first

⚠️ Common failure point: Selecting highest-volume locations for Wave 1. Instead, prioritize high readiness + moderate volume for pilots.

---

4. Rollout Strategy

Wave Structure Recommendation

Recommended Wave Model for 15-50 Locations

Wave	Locations	Duration	Purpose
Wave 1 (Pilot)	2-3	4 weeks	Validate integration, refine training, identify issues
Learning Capture	—	2 weeks	Document lessons, adjust playbook, prepare Wave 2
Wave 2	5-8	4 weeks	Scale validation, regional diversity test
Wave 3	8-15	4 weeks	Accelerated rollout with proven playbook
Wave 4+	Remaining	4-6 weeks	Complete deployment

---

Wave 1 Pilot Selection Criteria

Select 2-3 locations meeting these criteria:

☐ Composite readiness score ≥20 (from assessment above) ☐ Moderate patient volume (40-60th percentile) — representative but not highest stakes ☐ Geographic/demographic diversity — at least one urban and one suburban if possible ☐ PMS diversity — if you run multiple PMS platforms, include at least two in Wave 1 ☐ Strong local champion confirmed — provider or office manager who will actively engage ☐ Regional manager capacity — their region isn't in the middle of other major initiatives

🟣 Wave 1 Selection Decision Template

Candidate Location	Readiness Score	Volume %ile	PMS	Champion	RM Capacity	Select?

---

Timeline Per Wave

Wave 1 Detailed Timeline (4 Weeks)

Week	Activities
Week 1	Technical setup, integration testing, champion training
Week 2	Staff training, parallel run begins (AI + manual documentation)
Week 3	Full go-live, daily monitoring, issue resolution
Week 4	Stabilization, metrics collection, feedback gathering

Learning Capture Period (2 Weeks)

Week	Activities
Week 5	Compile Wave 1 feedback, document integration issues, quantify early metrics
Week 6	Update training materials, refine configuration template, prepare Wave 2 locations

Wave 2+ Timeline (4 Weeks per Wave)

Same structure as Wave 1, but:

• Champions trained by central team + Wave 1 champions
• Faster technical setup due to templated configuration
• Reduced parallel run period (3-5 days vs. full week)

---

Go/No-Go Criteria for Wave Advancement

🟣 Wave 1 → Wave 2 Go/No-Go

Criterion	Go	No-Go
Technical Stability	<2 critical issues open, all P1s resolved	>2 critical issues OR any unresolved P1
Integration Success	>95% of notes syncing to PMS correctly	<95% sync success rate
Provider Adoption	>80% of providers using daily	<80% adoption
Documentation Quality	Chart audit pass rate ≥90%	Chart audit pass rate <90%
Staff Sentiment	No more than 1 formal complaint per location	Multiple formal complaints
Baseline Comparison	Documentation time ≥20% reduction	No measurable improvement

Decision meeting: Schedule for end of Week 6 with VP Ops, CDO, IT Director, Regional Managers of pilot locations.

Wave 2 → Wave 3 Go/No-Go

Same criteria as above, plus:

• Wave 2 results replicate Wave 1 results
• No net-new integration issues emerged
• Training-the-trainer model validated (champions successfully trained their teams)

---

Rollback Plan

When to Trigger Rollback

• Critical patient safety concern (documentation errors affecting care)

• 20% provider refusal to use system after 2 weeks

• Integration failure causing data loss or corruption
• Unresolved P1 issues for >48 hours with no vendor ETA

Rollback Procedure

Per-Location Rollback:

1. Regional manager makes rollback recommendation to VP Ops
2. 🟣 VP Ops approves rollback decision
3. IT disables AI scribe integration at that location
4. Office manager communicates return to manual documentation
5. Vendor account manager notified immediately
6. Root cause analysis initiated within 24 hours

Full Wave Rollback:

1. If >50% of wave locations trigger individual rollback, escalate to full wave
2. 🟣 C-suite briefed on wave rollback
3. All wave locations return to manual documentation
4. Full wave retrospective before proceeding

Key principle: Rollback at one location does not automatically stop other locations in the wave. Assess each location independently unless systemic issue identified.

---

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integrations

Dentrix (Henry Schein)

Prerequisites: ☐ Dentrix G7.2 or higher (G7.4+ recommended) ☐ eServices enabled ☐ API access configured in Dentrix Office Manager

Integration Steps:

1. ☐ 🔵 Obtain Denti.AI Scribe API connector from vendor (Dentrix-specific module)
2. ☐ In Dentrix Office Manager, navigate to Setup → Integration Settings
3. ☐ Enable third-party clinical note integration
4. ☐ Generate API authentication token
5. ☐ 🔵 Provide token to Denti.AI implementation team
6. ☐ Configure note template mapping:
   • Map Denti.AI note types to Dentrix clinical note categories
   • Set default note format preferences
7. ☐ Test single patient note creation
8. ☐ Verify bidirectional sync (patient demographics flowing to AI scribe)
9. ☐ 🔵 Vendor validates production readiness

⏱️ Time estimate: 4-6 hours per location ⚠️ Common failure point: API token expiration settings — set to maximum or configure auto-refresh

---

Eaglesoft (Patterson)

Prerequisites: ☐ Eaglesoft 21.20 or higher ☐ Advanced Imaging module active (if integrating with imaging) ☐ Administrator access to Integration settings

Integration Steps:

1. ☐ 🔵 Request Eaglesoft bridge configuration from Denti.AI
2. ☐ Install Denti.AI Scribe bridge utility on Eaglesoft server
3. ☐ Configure bridge connection settings:
   • Server address
   • Port number
   • Authentication credentials
4. ☐ Map provider IDs between systems
5. ☐ Configure clinical note destination (procedure notes vs. clinical notes)
6. ☐ Test with sample appointment
7. ☐ Verify note appears in correct patient record
8. ☐ Test multi-provider scenario
9. ☐ 🔵 Vendor signs off on integration health

⏱️ Time estimate: 6-8 hours per location ⚠️ Common failure point: Bridge service must auto-start on server reboot — verify in Services

---

Open Dental

Prerequisites: ☐ Open Dental 22.1 or higher ☐ API module enabled (may require additional Open Dental license) ☐ HTTPS configured for API access

Integration Steps:

1. ☐ Enable Open Dental API module in Setup → Program Links
2. ☐ Generate API key with clinical note permissions
3. ☐ 🔵 Provide API key and instance URL to Denti.AI
4. ☐ Configure note type mappings
5. ☐ Set up procedure code associations (AI scribe can suggest codes)
6. ☐ Test patient demographic sync
7. ☐ Test clinical note creation
8. ☐ Verify appointment data flowing correctly
9. ☐ Configure webhook for real-time appointment notifications (optional but recommended)

⏱️ Time estimate: 3-5 hours per location (cleanest integration)

---

Imaging System Integration (If Applicable)

Supported Imaging Systems:

• Dexis
• Carestream
• Apteryx XrayVision
• Sidexis

General Integration Steps:

1. ☐ Verify imaging system version compatibility with vendor
2. ☐ Configure file path access for image retrieval (if on-premise)
3. ☐ 🔵 Enable cloud connector if cloud-based imaging
4. ☐ Test image association with clinical notes
5. ☐ Verify AI can reference images during note generation

⏱️ Time estimate: 2-3 hours per location

---

Test Environment Setup

Centralized Test Environment (Recommended for DSOs)

☐ 🔵 Request staging environment from Denti.AI

• Mirrors production configuration
• Isolated from live patient data
• Available for each wave's pre-deployment testing

☐ Create test patient records (10-15 synthetic patients per PMS instance)

☐ Develop standard test scenarios:

Test Case	Steps	Expected Result
New patient exam	Start recording, conduct mock exam, end recording	Structured note in PMS within 2 minutes
Treatment planning	Discuss recommended treatment, end recording	Treatment plan note with suggested codes
Hygiene recall	Conduct mock prophy appointment	Hygiene note with perio findings
Multi-provider handoff	Hygienist starts, dentist completes exam	Single consolidated note with both provider entries
Correction scenario	Intentionally speak unclear findings, use correction voice command	Note corrects appropriately

☐ Validation checklist per test scenario:

• Note created successfully
• Note associated with correct patient
• Note associated with correct provider
• Clinical content accurate
• Terminology appropriate
• Note format matches template

---

Data Migration/Historical Data

Denti.AI Scribe typically does not require historical data migration, as it generates new documentation going forward. However:

☐ Provider preference import (if available)

• Previous note templates
• Preferred terminology
• Commonly used phrases

☐ Existing smart phrases or macros — can inform AI voice command configuration

☐ Patient allergy/alert data — verify sync so AI can reference during documentation

---

Security & HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

☐ 🔵 Business Associate Agreement (BAA) executed

• Covers all current locations
• Includes provisions for adding future locations
• Specifies breach notification timeline
• Defines data handling and destruction obligations

☐ Data governance documentation:

• Where is audio data processed? (In transit? At rest?)
• How long is audio retained?
• Where are completed notes stored?
• Who has access to raw audio vs. completed notes?

☐ Access control verification:

• SSO correctly limits access to appropriate roles
• Audit logging enabled for all user actions
• Session timeout configured per security policy
• MFA enabled for administrative access

☐ Encryption verification:

• TLS 1.2+ for data in transit
• AES-256 for data at rest
• End-to-end encryption for audio streams

☐ Vendor security validation:

• SOC 2 Type II report reviewed
• HIPAA compliance attestation on file
• Penetration test results (within 12 months)
• Incident response plan documented

☐ 🟣 Legal/compliance sign-off on security documentation

⏱️ Time estimate: 1-2 weeks for full security review and approval

---

Standardized Configuration Template

Settings to Standardize Centrally (Identical Across All Locations)

Setting Category	Specific Settings
Note Format	Template structure, section headers, required fields
Terminology	Approved abbreviations, standardized perio charting notation
Procedure Codes	CDT code suggestions mapping
Compliance	Audit logging, retention periods, access roles
Voice Commands	Standard correction commands, note finalization phrases
Integration	PMS connection parameters (per PMS type)

Settings Allowing Local Discretion

Setting Category	Specific Settings
Provider Preferences	Individual provider voice profiles, preferred phrases
Specialty Adjustments	Specialty-specific templates (ortho, pedo, endo if applicable)
Hardware Configuration	Microphone placement, volume levels
Workflow Timing	When note generation triggers (end of appointment vs. real-time)

☐ Create master configuration document for central IT ☐ Create local configuration guide for location champions ☐ 🟣 CDO approves standardized terminology and note format

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Each location requires one trained champion. Selection criteria:

Criterion	Weight	Evaluation
Tech comfort level	30%	Has adopted previous technology quickly
Influence with team	25%	Respected by peers, can drive adoption
Availability	20%	Not overwhelmed with other responsibilities
Communication skills	15%	Can explain concepts clearly to others
Willingness	10%	Actively volunteered or enthusiastic when asked

Ideal champion profile: Office manager or lead hygienist with 2+ years tenure at location.

Alternative: Tech-forward associate dentist (though schedule constraints may limit availability).

Champion Responsibilities

1. Complete certification training (4-6 hours)
2. Deliver staff training at their location
3. Serve as first point of contact for daily questions
4. Escalate unresolved issues to regional manager
5. Collect staff feedback weekly during first month
6. Attend weekly champion sync calls during rollout

🔵 Champion Certification Training (Vendor-Delivered)

Module	Duration	Format	Content
System Overview	1 hour	Virtual live	Architecture, capabilities, limitations
Hands-On Practice	2 hours	Virtual live	Using the system end-to-end
Troubleshooting	1 hour	Virtual live	Common issues and resolution
Training Delivery	1 hour	Virtual live	How to train their team
Certification Quiz	30 min	Self-paced	Minimum 85% to certify
Practice Sessions	1 hour	Self-paced	Record and submit sample notes

⏱️ Total champion training time: 6-7 hours

---

Role-Specific Training Outlines

For Champions to Deliver Locally:

---

**Dentists/Providers Training**

Estimated Training Time: 60-90 minutes Format: Live demonstration + hands-on practice

Module 1: Workflow Changes (20 min)

• How the tool listens to your appointment
• When to start/stop recording (voice command or button)
• Natural conversation is the input — no need to speak differently
• Real-time note preview on screen

Module 2: Interpreting AI Outputs (25 min)

• Understanding the note structure generated
• Confidence indicators (if available)
• Where AI may need correction

Module 3: Making Corrections and Overrides (20 min)

• Voice commands for corrections ("correction: change X to Y")
• Manual editing before finalizing
• When to override vs. when to regenerate

Module 4: Hands-On Practice (20-30 min)

• Record a mock appointment
• Review generated note
• Make corrections
• Finalize and sync to PMS

Common Resistance Points:

Objection	Response
"This will take longer than typing"	"Initial learning curve is 2-3 days. Providers typically see time savings by day 5."
"AI can't understand dental terminology"	"System is trained on dental-specific vocabulary. Demo specific terms now."
"I don't trust it to be accurate"	"You review and approve every note before it saves. You remain in control."
"My patients will feel recorded"	"Patients are informed via consent, and many prefer it to seeing you typing."

Day 1 Cheat Sheet: Providers

DENTI.AI SCRIBE — PROVIDER QUICK REFERENCE

START RECORDING: Say "Begin documentation" OR click green mic icon
STOP RECORDING: Say "End documentation" OR click red stop icon

VOICE COMMANDS:
• "Correction: [old text] to [new text]" — Fix specific words
• "Delete last sentence" — Remove most recent statement
• "Add to plan: [text]" — Insert into treatment plan section
• "Patient education given for [topic]" — Add standard education note

BEFORE FINALIZING:
☐ Review note in preview pane
☐ Verify all procedures documented
☐ Confirm treatment plan accuracy
☐ Check for any highlighted uncertainty markers

FINALIZE: Click "Approve & Sync" OR say "Finalize note"

NEED HELP? Contact