NoteSwift — Implementation Playbook (DSO)

NoteSwift Implementation Playbook

AI Scribe Deployment Guide for Dental Support Organizations

---

1. Executive Summary

What NoteSwift Does

NoteSwift is an AI-powered clinical documentation scribe that listens to provider-patient conversations in real-time, automatically generating structured clinical notes, treatment documentation, and procedure narratives directly into your practice management system. The tool eliminates manual charting, reduces after-hours documentation burden, and standardizes clinical language across your organization.

Why DSOs Specifically Benefit from AI Scribes

Scale Advantage	DSO Impact
Standardization	Uniform clinical documentation language, terminology, and formatting across 15–50+ locations creates consistency for audits, compliance reviews, and quality assurance
Data Aggregation	Centralized documentation patterns enable enterprise-wide clinical analytics—identify procedure trends, treatment planning variations, and documentation quality gaps across regions
Provider Retention	Reducing documentation burden by 60–90 minutes daily directly impacts provider satisfaction and reduces turnover at scale
Compliance at Scale	Consistent, AI-verified documentation reduces audit risk and supports defensible records across your entire portfolio
Training Efficiency	New providers onboard faster with AI-assisted documentation, reducing ramp time across high-turnover locations

Expected Timeline: Decision to Full Deployment

Phase	Duration	Milestone
Pre-Implementation	Weeks 1–2	Vendor contract, technical assessment, baseline metrics
Pilot Wave (2–3 locations)	Weeks 3–6	Go-live, stabilization, success criteria validation
Wave 2 (5–8 locations)	Weeks 7–10	Expanded rollout with refined playbook
Wave 3+ (Remaining locations)	Weeks 11–16	Full deployment
Optimization	Weeks 17–20	Performance tuning, ROI validation

Total timeline for 30-location DSO: 16–20 weeks from signed contract to full deployment

---

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

Technical Requirements

Hardware (Per Operatory)

☐ Dedicated microphone system OR tablet/mobile device with microphone capability ☐ Verify minimum device specs: iOS 14+ / Android 11+ / Windows 10+ with 8GB RAM ☐ Operatory workstation with stable internet connection (minimum 10 Mbps up/down) ☐ Secondary display recommended for note review (not required)

Software

☐ Practice Management System compatibility verified (Dentrix G7+, Eaglesoft 21+, Open Dental 22.1+) ☐ Browser requirements: Chrome 90+ or Edge 90+ for web dashboard ☐ Mobile app downloaded and license activated per provider

Network

☐ HIPAA-compliant network configuration with encryption in transit ☐ Firewall exceptions documented for NoteSwift endpoints (vendor provides list) ☐ Guest/patient WiFi segregated from clinical network ☐ ⚠️ Minimum latency requirements: <100ms to NoteSwift servers for real-time transcription

Vendor Onboarding Steps

Week	Action	Owner
Week 1, Day 1	🔵 Kick-off call with NoteSwift implementation manager	VP Ops + Vendor
Week 1, Day 2	🔵 Receive enterprise license keys and admin credentials	Vendor
Week 1, Day 3	Designate internal project lead and technical point of contact	VP Ops
Week 1, Day 4	🔵 Schedule integration planning session	IT + Vendor
Week 1, Day 5	🔵 Execute Business Associate Agreement (BAA)	Legal + Vendor

Key Vendor Contacts to Establish

☐ Implementation Manager (primary contact during rollout) ☐ Technical Integration Specialist ☐ Enterprise Support Line (dedicated for DSO accounts) ☐ Customer Success Manager (post-implementation) ☐ Executive Sponsor at NoteSwift (for escalations)

Data/Access Prerequisites

☐ PMS admin credentials for integration setup ☐ 🔵 API keys from NoteSwift (vendor provides) ☐ Provider NPI numbers for all locations ☐ Active directory or identity provider access for SSO configuration ☐ ⚠️ Historical patient data NOT required—NoteSwift operates on forward-looking documentation only ☐ Test patient records created in sandbox environment

Internal Stakeholder Alignment

🟣 Approval Required From:

☐ CEO/COO — Enterprise software commitment, budget allocation ☐ Chief Dental Officer — Clinical workflow changes, documentation standards ☐ CFO — ROI expectations, contract terms ☐ General Counsel — BAA review, data governance ☐ VP of IT — Technical architecture, security review

Informed (No Approval Needed):

☐ Regional Managers — Rollout timeline, location impact ☐ Office Managers — Training requirements, workflow changes ☐ Revenue Cycle/Billing Lead — Documentation impact on coding

Baseline Metrics to Capture BEFORE Go-Live

⚠️ Critical: Capture these metrics 30 days before go-live to enable accurate ROI measurement

Metric	Definition	Collection Method	Target Source
Documentation Time per Patient	Minutes spent charting per patient encounter	Provider self-report survey (7-day sample)	Providers
After-Hours Documentation	Hours spent on notes outside clinical hours weekly	Provider self-report	Providers
Chart Completion Rate	% of charts completed same-day	PMS report	IT/Ops
Documentation Error Rate	% of charts requiring correction/amendment	Random audit of 50 charts/location	CDO Office
Provider Satisfaction Score	Documentation burden rating 1-10	Anonymous survey	HR/Ops
Patient Throughput	Patients seen per provider per day	PMS report	IT
Coding Accuracy Rate	% of procedure codes matching documentation	Billing audit	Revenue Cycle

DSO-Specific: Standardize Baseline Measurement

🟣 Executive Decision Required: Approve standardized baseline protocol

☐ Create uniform survey instrument for all locations ☐ Establish 30-day data collection window (same dates across all locations) ☐ Designate regional managers as accountable for baseline data collection ☐ Central analytics team aggregates and validates data quality ☐ ⚠️ Do NOT proceed to Wave 1 without validated baseline data from pilot locations

Enterprise-Level Requirements

Network Standards Across Locations

☐ Audit network capabilities at all locations (use vendor-provided network test tool) ☐ 🔵 Document minimum bandwidth requirements (10 Mbps sustained per concurrent user) ☐ Identify locations requiring network upgrades—flag for pre-Wave remediation ☐ Confirm VPN/SD-WAN compatibility with NoteSwift traffic

Hosting Architecture Decision

🟣 Executive Decision Required: Centralized vs. Location-Level Configuration

Option	Pros	Cons	Recommendation
Centralized Hosting	Single admin console, uniform policies, easier audit	Single point of failure, requires robust connectivity	✅ Recommended for DSOs
Location-Level	Local resilience, autonomy	Configuration drift, harder to manage	Not recommended

Single Sign-On (SSO) Configuration

☐ 🔵 NoteSwift supports SAML 2.0 and OAuth 2.0—confirm with vendor ☐ Integrate with existing identity provider (Okta, Azure AD, Google Workspace) ☐ Map user roles: Provider, Hygienist, Admin, Billing, Read-Only ☐ Test SSO in sandbox before production

Centralized Credentialing

☐ Provider roster uploaded to NoteSwift with NPI, specialty, location assignments ☐ Establish process for adding/removing providers as staffing changes ☐ Designate credentialing admin (typically HR or Ops)

Stakeholder Alignment Map

Stakeholder Level	Who	What They Need to Know	When	Communication Owner
Board/Investors	Board members	ROI thesis, timeline, risk mitigation	Pre-contract, quarterly updates	CEO
C-Suite	CEO, COO, CDO, CFO	Strategic rationale, budget, clinical impact	Week 1	VP Ops
Regional Managers	Regional Ops Directors	Location selection rationale, rollout timeline, their role	Week 1–2	VP Ops
Office Managers	Practice Managers	Training requirements, workflow changes, go-live date	Week 2–3	Regional Managers
Providers	Dentists, Hygienists	How it works, what changes, benefits	Week 3 (pre-training)	CDO + Office Managers
Support Staff	Front desk, billing	Limited impact awareness, escalation paths	Week 3	Office Managers

---

3. Location Readiness Assessment

Scoring Framework

Score each factor 1–5 per location. Composite score determines rollout wave assignment.

Factor 1: IT Infrastructure Maturity (Weight: 25%)

Score	Criteria
5	Fiber internet, <50ms latency, hardware <2 years old, current PMS version
4	Cable internet, <75ms latency, hardware <3 years old, PMS version N-1
3	DSL/cable, <100ms latency, hardware <4 years old, supported PMS version
2	Inconsistent connectivity, older hardware, PMS version requiring upgrade
1	Network issues, outdated hardware, unsupported PMS version

Assessment Method: Run NoteSwift network diagnostic tool (provided by vendor), PMS version audit, hardware inventory

Factor 2: Staff Tenure and Adaptability (Weight: 20%)

Score	Criteria
5	<15% annual turnover, previous successful tech rollout, team >2 years tenure avg
4	15–25% turnover, neutral tech adoption history, team 1–2 years tenure avg
3	25–35% turnover, mixed tech adoption, some staff resistance history
2	35–50% turnover, poor tech adoption history, significant resistance anticipated
1	>50% turnover, failed previous tech rollouts, active staff issues

Assessment Method: HR turnover data, office manager interview, previous technology adoption survey

Factor 3: Patient Volume (Weight: 20%)

Score	Criteria
5	40–60 patients/day (high impact, manageable complexity)
4	60–80 patients/day (high impact, moderate complexity)
3	25–40 patients/day (moderate impact, low risk)
2	>80 patients/day (high risk due to volume)
1	<25 patients/day (low impact, limited ROI)

Assessment Method: PMS patient volume reports (trailing 90-day average)

Factor 4: Tech Stack Compatibility (Weight: 20%)

Score	Criteria
5	Dentrix Enterprise or Open Dental, integrated imaging, cloud-enabled
4	Eaglesoft current version, standard integrations, minimal customization
3	Supported PMS with some custom workflows requiring configuration
2	Older PMS version requiring upgrade, heavy customization
1	Unsupported PMS, siloed systems, no integration capability

Assessment Method: PMS version audit, 🔵 vendor compatibility check, integration inventory

Factor 5: Local Champion Availability (Weight: 15%)

Score	Criteria
5	Tech-forward provider + engaged office manager, both willing to champion
4	Either provider or OM willing to champion, strong support from other
3	Office manager willing, providers neutral
2	No clear champion, but no active resistance
1	No champion available, or active resistance from leadership

Assessment Method: Regional manager nomination, office manager interview, provider survey

Composite Score Calculation

Factor	Weight	Location A Score	Weighted
IT Infrastructure	25%	[1-5]	[Score × 0.25]
Staff Adaptability	20%	[1-5]	[Score × 0.20]
Patient Volume	20%	[1-5]	[Score × 0.20]
Tech Compatibility	20%	[1-5]	[Score × 0.20]
Local Champion	15%	[1-5]	[Score × 0.15]
Composite Score	100%	—	[Total]

Rollout Sequence Recommendation

Composite Score	Wave Assignment	Rationale
4.0–5.0	Wave 1 (Pilot)	High readiness, low risk, ideal for proving the model
3.5–3.9	Wave 2	Strong readiness, deploy once playbook refined
3.0–3.4	Wave 3	Moderate readiness, may need pre-work
2.5–2.9	Wave 4	Requires remediation before deployment
<2.5	Defer	Address infrastructure/staffing issues first

Sample Rollout Sequence (30-Location DSO)

Wave	Locations	Timing	Selection Rationale
Wave 1	3 locations	Weeks 3–6	Highest composite scores (4.2+), geographic diversity, different PMS versions represented
Wave 2	7 locations	Weeks 7–10	Scores 3.7–4.1, apply lessons from Wave 1
Wave 3	10 locations	Weeks 11–14	Scores 3.2–3.6, scaled deployment
Wave 4	10 locations	Weeks 15–18	Remaining locations, remediation complete

---

4. Rollout Strategy

Wave Structure for DSO Deployment

Recommended Approach: Controlled Wave Rollout

Wave	Locations	Duration	Purpose
Wave 1 (Pilot)	2–3 locations	4 weeks	Validate playbook, identify issues, build internal expertise
Wave 2 (Early Majority)	5–8 locations	3 weeks	Scale with refined process, train-the-trainer activation
Wave 3 (Majority)	10–15 locations	3 weeks	Parallel deployments, regional manager ownership
Wave 4 (Remainder)	Remaining locations	2–3 weeks	Final locations, exception handling

Wave 1 Pilot Location Selection Criteria

🟣 Executive Decision Required: Final pilot location selection

Select 2–3 locations that meet ALL of the following:

☐ Composite readiness score ≥4.0 ☐ Strong local champion (provider or OM) actively engaged ☐ Manageable patient volume (40–60 patients/day ideal) ☐ Geographic proximity to central support resources (if possible) ☐ Represents your most common PMS (e.g., if 60% Dentrix, include ≥1 Dentrix location) ☐ ⚠️ NOT your highest-revenue location (avoid maximum financial risk) ☐ ⚠️ NOT a location with significant staff changes in next 90 days

Timeline Per Wave with Buffer

Week 1-2:   Pre-Implementation (all locations)
Week 3:     Wave 1 Go-Live
Week 4-5:   Wave 1 Stabilization + Optimization
Week 6:     Wave 1 Success Assessment + Wave 2 Prep
            ↓ Go/No-Go Decision Point
Week 7:     Wave 2 Go-Live
Week 8-9:   Wave 2 Stabilization
Week 10:    Wave 2 Assessment + Wave 3 Prep
            ↓ Go/No-Go Decision Point
Week 11-13: Wave 3 Go-Live (parallel deployments)
Week 14:    Wave 3 Stabilization
Week 15-17: Wave 4 Go-Live
Week 18-20: Full Deployment Optimization

Go/No-Go Criteria to Advance Between Waves

🟣 Executive Decision Required: Wave advancement approval

Must achieve ALL of the following to proceed to next wave:

Criterion	Threshold	Measurement
System Uptime	≥99% during business hours	NoteSwift dashboard
Provider Adoption	≥80% of providers using for ≥80% of patients	Usage analytics
Documentation Completion	≥90% same-day chart completion	PMS report
Training Completion	100% of staff trained	LMS/sign-off sheets
Critical Issues	Zero unresolved P1 issues	Issue tracker
Provider Satisfaction	≥7/10 average rating	Pulse survey

Amber flags (proceed with caution):

• Provider adoption 70–79%
• 1–2 unresolved P2 issues
• Provider satisfaction 5–6/10

Red flags (do not proceed):

• Any unresolved P1 issues
• Provider adoption <70%
• Provider satisfaction <5/10
• ⚠️ Any patient safety concerns

Rollback Plan

If a wave fails go/no-go criteria, execute the following:

Immediate Actions (Day 1 of Rollback): ☐ Notify NoteSwift vendor support of rollback decision ☐ Communicate to affected locations: "We're pausing to address [specific issues]" ☐ Revert to manual documentation workflows ☐ Do NOT disable NoteSwift accounts (maintain data access for troubleshooting)

Investigation Period (Days 2–7): ☐ 🔵 Joint root cause analysis with vendor ☐ Document specific failure modes ☐ Assess whether issues are location-specific or systemic ☐ Determine remediation path and timeline

Recovery Options:

Scenario	Response
Location-specific issue	Remediate that location, exclude from current wave, add to later wave
Systemic issue (vendor)	Pause all deployment, require vendor fix, revalidate in pilot
Training issue	Extend training, re-attempt in 2 weeks
Infrastructure issue	Remediate infrastructure, re-attempt when resolved

🟣 Executive Decision Required: Rollback decision and recovery path

---

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integration

Dentrix Enterprise Integration

Estimated Time: 4–6 hours (with vendor support)

☐ 🔵 Schedule integration call with NoteSwift technical team ☐ Verify Dentrix Enterprise version (G7.2+ required) ☐ Enable API access in Dentrix Enterprise Admin Console ☐ Generate API credentials in Dentrix (Admin > Integrations > API Management) ☐ 🔵 Provide API credentials to NoteSwift during integration call ☐ Configure user mapping (Dentrix User ID → NoteSwift Provider ID) ☐ Set default clinical note template locations in Dentrix ☐ ⚠️ Test write-back functionality with test patient record BEFORE production ☐ Validate procedure code mapping (ADA codes) ☐ Configure auto-attachment of notes to treatment visits

Eaglesoft Integration

Estimated Time: 3–4 hours (with vendor support)

☐ 🔵 Schedule integration call with NoteSwift technical team ☐ Verify Eaglesoft version (21.20+ required) ☐ Enable HL7/API bridge in Eaglesoft (Patterson support may be required) ☐ ⚠️ Note: Eaglesoft integration requires Patterson middleware license—confirm active ☐ 🔵 Provide Eaglesoft server credentials to NoteSwift (view-only recommended) ☐ Configure note destination (Clinical Notes module) ☐ Test bidirectional data flow with test patient ☐ Validate appointment sync accuracy

Open Dental Integration

Estimated Time: 2–3 hours (with vendor support)

☐ 🔵 Schedule integration call with NoteSwift technical team ☐ Verify Open Dental version (22.1+ required for full API support) ☐ Enable API module in Open Dental (Setup > Miscellaneous > API) ☐ Generate API key in Open Dental ☐ 🔵 Provide API key to NoteSwift ☐ Configure user permissions for API access ☐ Map procedure codes and note types ☐ Test clinical note posting to Chart module ☐ ⚠️ If using Open Dental Cloud, verify firewall exceptions with Open Dental support

Integration with Imaging/Clinical Systems

If using integrated imaging (Dexis, Carestream, etc.):

☐ Assess whether NoteSwift needs to reference imaging data (typically no—scribe function only) ☐ If imaging references needed in notes, configure image viewer shortcut integration ☐ 🔵 Verify with NoteSwift if your imaging system has available integration

If using separate clinical systems: ☐ Document existing workflows for cross-referencing ☐ Determine if NoteSwift notes will reference external system data ☐ Configure copy/paste or manual reference workflow if integration not available

Test Environment Setup

Estimated Time: 2–3 hours per location

☐ Create sandbox/test environment in PMS (clone of production or dedicated test database) ☐ Create 10 test patient records with realistic scenarios:

• New patient comprehensive exam
• Recall/hygiene visit
• Restorative procedure (crown, filling)
• Emergency visit
• Perio patient ☐ 🔵 Request NoteSwift sandbox tenant/credentials ☐ Complete 5 end-to-end tests per scenario type ☐ Validate notes appear correctly in PMS ☐ Test note editing/amendment workflow ☐ ⚠️ Do NOT proceed to production without successful validation of ALL scenarios

Validation Checklist

Test Case	Expected Result	Pass/Fail
New patient exam dictation	Full note appears in PMS within 60 seconds	☐
Treatment codes mentioned	Codes suggested/auto-populated accurately	☐
Provider identification	Correct provider attributed to note	☐
Patient identification	Correct patient chart updated	☐
Note editing	Edits save correctly to PMS	☐
Multiple operatories	Concurrent sessions don't cross-contaminate	☐
Network interruption	Graceful recovery, no data loss	☐

Data Migration/Historical Data

NoteSwift Note: AI scribes typically do NOT require historical data migration—they operate on forward-looking documentation only.

☐ Confirm with vendor: historical data requirements = NONE ☐ If clinical templates exist, provide to NoteSwift for template training ☐ Export current clinical note templates from PMS for reference ☐ 🔵 Share any custom terminology, abbreviations, or specialty-specific language

Security and HIPAA Compliance Verification

Pre-Go-Live Security Checklist

☐ 🔵 Business Associate Agreement (BAA) fully executed ☐ Verify NoteSwift SOC 2 Type II certification (request report if not provided) ☐ Confirm data encryption: in-transit (TLS 1.2+) and at-rest (AES-256) ☐ Review data retention policy with vendor ☐ Confirm data residency (US-only servers for HIPAA) ☐ Verify audit logging capabilities ☐ Test user access controls (role-based permissions) ☐ Confirm vendor's breach notification procedures ☐ ⚠️ Document all compliance items in your HIPAA risk assessment

DSO-Specific: Enterprise HIPAA Checklist

☐ 🟣 Legal review of BAA for enterprise terms ☐ Centralized access control management via SSO ☐ Audit log aggregation to central security console ☐ Data governance policy updated to include AI documentation tools ☐ Staff training on AI-specific HIPAA considerations (voice data handling) ☐ Incident response plan updated to include NoteSwift-specific scenarios ☐ Annual security review cadence with vendor established

DSO-Specific Configuration

Standardized Configuration Template (Identical Across All Locations)

Setting	Standard Value	Rationale
Note format/template	[DSO standard template]	Consistency for audits, training
Procedure code mapping	ADA standard codes	Billing consistency
Auto-save interval	30 seconds	Data protection
Session timeout	15 minutes	HIPAA compliance
Audit log retention	7 years	Legal/compliance requirement
User role definitions	Provider, Hygienist, Admin, Billing, Read-Only	Consistent access control
Default note template	[DSO clinical note template]	Documentation standardization
Alert/notification settings	[Standard notification rules]	Consistent user experience

Location-Specific Configuration (May Vary)

Setting	Local Discretion Allowed	Rationale
Provider preferences	Yes	Individual workflow optimization
Microphone sensitivity	Yes	Room acoustics vary
Specialty-specific templates	Yes	Perio, ortho, oral surgery variations
Appointment type mapping	Yes	Local scheduling conventions
Custom abbreviations	Limited (with approval)	Provider efficiency

Testing Approach

Recommended: Centralized Test Environment

☐ Deploy single enterprise test tenant ☐ Configure all location variations in test environment ☐ Conduct integration testing centrally before location deployment ☐ Distribute validated configuration to locations ☐ Location-level validation testing (2 hours per location)

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Each location requires 1 designated champion who will:

• Receive advanced training directly from NoteSwift
• Train and support their local team
• Serve as first-line troubleshooting contact
• Provide feedback to central team

Ideal Champion Profile: ☐ Office Manager OR senior clinical team member ☐ Tech-comfortable (uses smartphone apps, adapts to new software easily) ☐ Strong communication skills ☐ Respected by clinical staff ☐ Will be at location for ≥12 months ☐ Available for 4-hour training + ongoing 2 hours/week support duties

Champion Responsibilities

Phase	Responsibility	Time Commitment
Pre-Launch	Complete advanced training, prepare local materials	4 hours
Launch Week	Train all staff, provide real-time support	8–10 hours
Weeks 2–4	Daily check-ins with staff, troubleshooting	5 hours/week
Ongoing	New hire training, refreshers, escalation	2 hours/week

Champion Certification Process

☐ 🔵 Complete NoteSwift Champion Training (4 hours, vendor-led) ☐ Pass certification quiz (80% minimum) ☐ Complete 3 supervised training sessions ☐ Sign champion agreement acknowledging responsibilities ☐ Added to Champion communication channel (Slack/Teams)

Standardized Training Materials

Created Centrally (Do Not Modify):

• Training slide deck (vendor-provided + DSO customization)
• Quick reference cards per role
• Video library (NoteSwift basics, PMS integration, troubleshooting)
• Certification quiz
• FAQ document

Champion Customizes Locally:

• Schedule training sessions around local patient schedule
• Adapt examples to local procedures/specialties
• Add location-specific troubleshooting (e.g., network quirks)

Role-Specific Training Outlines

Dentists/Providers

Training Time: 90 minutes (60 min group + 30 min individual practice) Format: Live demo with hands-on practice

Session Outline:

Time	Topic
0–15 min	Why AI scribes, ROI for providers (reduced after-hours work)
15–35 min	How NoteSwift works: demo of live transcription
35–50 min	Workflow integration: when to start/stop, where notes appear
50–65 min	Reviewing and editing AI-generated notes
65–80 min	Hands-on practice with test patients
80–90 min	Q&A, address concerns

Common Resistance Points:

Objection	Response
"AI can't capture my clinical judgment"	"You review and approve every note—AI does the typing, you do the thinking"
"I'm faster with my current method"	"Give it 2 weeks—providers typically save 60–90 minutes daily"
"What about patient privacy?"	"HIPAA-compliant, encrypted, BAA in place—same protections as your PMS"
"What if it makes mistakes?"	"Review workflow catches errors before signing—similar to reviewing a note from a human scribe"

Day 1 Cheat Sheet for Providers:

╔══════════════════════════════════════════════════════╗
║           NOTESWIFT PROVIDER QUICK REFERENCE          ║
╠══════════════════════════════════════════════════════╣
║ START SESSION: Tap patient name → "Start Scribe"     ║
║ SPEAK NORMALLY: No special commands needed            ║
║ KEY PHRASES:                                          ║
║   • "Chief complaint is..."                          ║
║   • "On examination, I note..."                      ║
║   • "Treatment plan includes..."                     ║
║   • "Patient consented to..."                        ║
║ END SESSION: Tap "Complete" when finished            ║
║ REVIEW: Note appears in PMS within 60 seconds        ║
║ EDIT: Click note, make changes, save                 ║
║ SIGN: Approve note like any other clinical note      ║
║ ⚠️ NEVER dictate with wrong patient selected         ║
║ HELP: Ask [Champion Name] or call [Support Number]   ║
╚══════════════════════════════════════════════════════╝

Hygienists

Training Time: 45 minutes Format: Group session with demo

Session Outline:

Time	Topic
0–10 min	Overview: what NoteSwift is, how it helps providers
10–25 min	Hygienist touchpoints: when to start session (if applicable), perio charting integration
25–35 min	Handoff workflow: what to communicate to provider about session status
35–45 min	Troubleshooting basics, who to contact for help

Day 1 Cheat Sheet for Hygienists:

╔══════════════════════════════════════════════════════╗
║          NOTESWIFT HYGIENIST QUICK REFERENCE          ║
╠══════════════════════════════════════════════════════╣
║ YOUR ROLE: [Start session/Handoff to provider]        ║
║ IF STARTING SESSION:                                  ║
║   • Confirm correct patient selected                  ║
║   • Tap "Start Scribe" before beginning              ║
║   • Speak clearly during perio exam                   ║
║ IF PROVIDER STARTS:                                   ║
║   • No action needed from you                        ║
║ HANDOFF: Tell provider