mConsent — Implementation Playbook (DSO)

mConsent Implementation Playbook

Patient Communication AI for Dental Service Organizations

---

1. Executive Summary

What mConsent Does

mConsent is a comprehensive digital patient intake and communication platform that automates patient forms, consent documentation, insurance verification, appointment reminders, and two-way messaging—eliminating paper workflows and manual data entry while ensuring real-time PMS synchronization across all locations.

Why DSOs Specifically Benefit from Patient Communication AI

Scale Advantages:

• Centralized control over patient-facing communications ensures brand consistency across 15–50+ locations
• Aggregate data on patient responsiveness, no-show rates, and form completion enables enterprise-wide benchmarking
• Single vendor contract and integration effort scales across entire portfolio without per-location overhead

Standardization:

• Uniform consent forms, intake workflows, and compliance documentation reduce legal exposure
• Consistent patient experience regardless of location increases brand equity and patient retention
• Centralized template management eliminates version control chaos across locations

Data Aggregation:

• Cross-location analytics reveal which offices excel at patient engagement and which need intervention
• Population-level insights inform marketing, staffing, and capacity planning decisions
• Unified patient communication history enables seamless patient transfers between locations

Expected Timeline: Decision to Full Deployment

Phase	Timeline	Scope
Pre-Implementation	Weeks 1–2	Vendor onboarding, baseline capture, readiness assessment
Wave 1 Pilot	Weeks 3–5	2–3 pilot locations
Wave 2 Expansion	Weeks 6–9	Next 5–8 locations
Wave 3 Full Deployment	Weeks 10–14	Remaining locations
Optimization	Weeks 15–20	Enterprise-wide refinement

Total Timeline: 14–20 weeks from contract signature to full deployment across 15–50 locations.

---

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

Technical Requirements

Hardware

☐ Verify each location has minimum 2 tablets or kiosks for patient intake (iPad 6th gen+ or Android 9.0+ recommended) ☐ Confirm front desk workstations meet minimum specs (4GB RAM, modern browser support) ☐ Assess tablet mounting or security solutions for waiting rooms ☐ Inventory existing signature pads and determine if they integrate or need replacement

Software

☐ Document current PMS version at each location (Dentrix, Eaglesoft, Open Dental, or other) ☐ Verify PMS is on a supported version for mConsent integration (check vendor compatibility matrix) ☐ Confirm operating systems are current (Windows 10+ for workstations) ☐ Document existing patient communication tools that will be replaced or integrated

Network

☐ Minimum 25 Mbps download/10 Mbps upload per location for cloud-based operations ☐ Guest WiFi network available for patient-facing tablets (isolated from clinical network) ☐ Firewall rules allow outbound HTTPS to mConsent domains ☐ VPN or dedicated connection requirements for enterprise security compliance

Integrations

☐ Confirm clearinghouse for real-time eligibility verification (if using insurance verification module) ☐ Document any existing EHR, imaging, or lab integrations that touch patient intake ☐ Identify any custom forms or workflows currently in third-party systems

Vendor Onboarding Steps 🔵

☐ 🔵 Schedule enterprise kick-off call with mConsent implementation team ☐ 🔵 Designate primary enterprise contact and backup ☐ 🔵 Request dedicated Customer Success Manager (CSM) for DSO account ☐ 🔵 Obtain access to mConsent admin portal and sandbox environment ☐ 🔵 Review enterprise SLA terms and escalation procedures ☐ 🔵 Confirm data center location and redundancy for compliance purposes ☐ 🔵 Request enterprise training materials and certification program access

Key Vendor Contacts to Establish:

• Implementation Project Manager (tactical execution)
• Customer Success Manager (ongoing relationship)
• Technical Support Tier 2 escalation contact
• Executive sponsor on vendor side (for escalation)

Data/Access Prerequisites

☐ Generate API credentials from each PMS instance (or centralized if using cloud PMS) ☐ Prepare list of all active providers with NPI numbers for insurance verification ☐ Compile current patient consent form templates (all versions used across locations) ☐ Export sample patient demographic data for integration testing ☐ Document current appointment reminder cadence and messaging ☐ Gather HIPAA authorization forms currently in use

Internal Stakeholder Alignment

🟣 Who Needs to Approve

Stakeholder	Approval Needed For	Timeline
CEO/COO	Final budget authorization, enterprise rollout timeline	Week 1
Chief Dental Officer	Clinical consent form content, provider workflow changes	Week 1
VP of Operations	Resource allocation, regional manager responsibilities	Week 1
General Counsel	BAA review, consent form legal compliance, data governance	Week 1–2
CFO	ROI targets, budget release for hardware/licensing	Week 1
CISO/IT Director	Security architecture, network requirements, SSO integration	Week 1–2

Who Needs to Be Informed

Stakeholder	Communication Type	Timing
Board/Investors	High-level initiative briefing	Before public announcement
Regional Managers	Detailed rollout plan and responsibilities	Week 2
Office Managers (all locations)	Initial awareness, timeline expectations	Week 2
Providers (all locations)	Brief overview, "what's coming"	Week 2–3
Front desk staff	Initial awareness	Week 3+ (closer to their wave)

Baseline Metrics to Capture ⚠️

⚠️ Common Failure Point: Organizations that skip baseline measurement cannot prove ROI—this is the #1 cause of stakeholder dissatisfaction post-implementation.

Patient Communication Metrics (Capture at ALL locations)

☐ Current no-show rate (last 90 days) ☐ Same-day cancellation rate (last 90 days) ☐ Patient form completion time (time-motion study at 3 representative locations) ☐ Patient check-in time (arrival to seated in chair) ☐ Paper form error rate (incomplete fields, illegible entries) ☐ Appointment confirmation response rate (if currently measured)

Operational Metrics

☐ Front desk FTE hours spent on manual data entry per week ☐ Insurance verification time per patient ☐ Time to process new patient intake (start to complete) ☐ Consent form compliance rate (all required signatures obtained) ☐ Patient complaint rate related to communication/paperwork

Financial Metrics

☐ Revenue per patient visit (average) ☐ New patient acquisition cost ☐ Insurance claim denial rate related to eligibility or demographic errors ☐ Collection rate at time of service

Standardization Protocol for Cross-Location Comparison

1. Use identical 90-day lookback period (specify exact dates)
2. Pull data from PMS using standardized report templates
3. Document any location-specific anomalies (new location, recent staffing changes)
4. Store all baseline data in centralized repository with location identifiers
5. Assign data validation to regional managers before submission

Enterprise-Level Requirements

Network Standards Across Locations

☐ 🟣 Decide: Centralized internet egress vs. location-level direct access ☐ Document minimum bandwidth requirements in operations standards ☐ Establish firewall whitelist policy for mConsent domains ☐ Configure network monitoring for mConsent traffic patterns

Centralized vs. Location-Level Hosting

☐ 🟣 Decision required: mConsent is cloud-hosted; determine if data segregation by region is required ☐ Confirm data residency requirements (US-only, specific states) ☐ Document backup and disaster recovery expectations

Single Sign-On (SSO)

☐ 🔵 Request SAML/SSO integration specifications from mConsent ☐ Configure identity provider (Okta, Azure AD, etc.) integration ☐ Define role-based access control (RBAC) structure:

• Enterprise Admin (full access, all locations)
• Regional Manager (access to region's locations)
• Office Manager (single location)
• Front Desk (limited to patient-facing functions)
• Provider (clinical workflow only)

Centralized Credentialing

☐ Establish provider master list with NPI, DEA, state licenses ☐ Configure automatic provider deactivation workflow for terminations ☐ Define process for adding new providers to mConsent across locations

---

3. Location Readiness Assessment

Scoring Framework

Score each location on the following factors (1 = lowest readiness, 5 = highest readiness):

Factor 1: IT Infrastructure Maturity

Score	Criteria
5	Fiber internet (100+ Mbps), hardware <2 years old, PMS on latest version, existing tablets
4	High-speed internet (50+ Mbps), hardware <3 years old, PMS within 1 version of current
3	Adequate internet (25+ Mbps), hardware <5 years old, PMS supported but not current
2	Marginal internet (10–25 Mbps), hardware aging (5+ years), PMS version requires upgrade
1	Unreliable internet, outdated hardware, PMS version not supported

Factor 2: Staff Tenure and Adaptability

Score	Criteria
5	Low turnover (<10%/year), staff has adopted 2+ new technologies in past 2 years, proactive about learning
4	Moderate turnover (10–20%/year), successful with 1 recent technology adoption
3	Average turnover (20–30%/year), mixed technology adoption history
2	High turnover (30–50%/year), struggled with recent technology changes
1	Very high turnover (>50%/year), resistant to technology, recent failed implementations

Factor 3: Patient Volume

Score	Criteria
5	High volume (60+ patients/day) — maximum impact potential
4	Above average (45–60 patients/day)
3	Average (30–45 patients/day) — balanced impact/risk
2	Below average (15–30 patients/day)
1	Low volume (<15 patients/day) — minimal impact but also minimal learning

Note: For Wave 1 pilots, a score of 3 is often optimal—enough volume to validate but not so high that issues cause major disruption.

Factor 4: Existing Tech Stack Compatibility

Score	Criteria
5	PMS is Dentrix, Eaglesoft, or Open Dental (latest versions); no conflicting patient communication tools
4	Supported PMS, minor integration complexity, 1 overlapping tool to sunset
3	Supported PMS, moderate integration work required, 2+ tools to sunset
2	Supported PMS but older version requiring upgrade; complex existing tech stack
1	Unsupported PMS, requires manual workarounds, or major tech stack conflicts

Factor 5: Local Champion Availability

Score	Criteria
5	Tech-forward Office Manager + engaged lead provider, both committed to championing
4	Strong Office Manager OR engaged provider willing to champion
3	Willing Office Manager, neutral provider support
2	No clear champion, but no active resistance
1	No champion available, or key staff actively resistant

Composite Score Calculation

Composite Score	Rollout Recommendation
22–25	Wave 1 Candidate — Ideal pilot location
18–21	Wave 2 Candidate — Strong foundation, minor gaps
14–17	Wave 3 Candidate — Needs preparation work before rollout
10–13	Wave 4/Delayed — Significant remediation required first
5–9	Not Ready — Address foundational issues before including

Readiness Assessment Template

Location	IT Infra (1-5)	Staff (1-5)	Volume (1-5)	Tech Stack (1-5)	Champion (1-5)	Total	Wave
Example: Main St	4	4	3	5	5	21	Wave 1
Example: Oakwood	3	3	4	4	3	17	Wave 2
Example: Riverside	2	2	5	3	2	14	Wave 3

Rollout Sequence Recommendation

1. Wave 1 (Pilot): Select 2–3 locations scoring 20+ with diverse characteristics:

   • Include at least 1 high-volume and 1 moderate-volume location
   • Include geographic diversity if relevant (different regions)
   • Prioritize locations with strongest champions

2. Wave 2: Locations scoring 18–21, grouped by region for efficient support

3. Wave 3: Remaining locations scoring 14–17, with remediation tasks completed during Wave 2

4. Exception Handling: Locations scoring <14 require individualized remediation plans before rollout

---

4. Rollout Strategy

Wave Structure

Recommended Wave Design

Wave	Locations	Duration	Purpose
Wave 1	2–3 pilot sites	Weeks 3–5	Validate integration, training model, and identify issues
Wave 2	5–8 locations	Weeks 6–9	Scale with learnings, stress-test support model
Wave 3	Remaining locations	Weeks 10–14	Full deployment with proven playbook

Wave 1 Pilot Selection Criteria

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

☐ Composite readiness score of 20+ ☐ Office Manager willing to provide daily feedback during pilot ☐ Patient volume of 30–50/day (enough to validate, not so high that issues are catastrophic) ☐ Geographic accessibility for potential on-site support ☐ Represents at least 2 different PMS configurations (if applicable) ☐ Not currently undergoing other major changes (construction, provider transitions)

🟣 Executive Decision Required: Final pilot location selection should be approved by VP of Operations and regional managers.

Timeline Per Wave

Wave 1 Detailed Timeline:

• Week 3, Days 1–2: Configuration and integration completion
• Week 3, Days 3–5: Staff training (champions + full team)
• Week 4, Day 1: Go-live
• Week 4–5: Intensive monitoring and daily check-ins
• Week 5, Day 5: Wave 1 retrospective and go/no-go decision for Wave 2

Wave 2 Detailed Timeline:

• 3–5 days buffer after Wave 1 go/no-go (learning integration)
• 2 days per location for configuration (can parallelize with dedicated resources)
• 1 day per location for training (champions deliver)
• Staggered go-lives (2–3 locations per day maximum)
• 2-week intensive monitoring period

Wave 3 Detailed Timeline:

• 3–5 days buffer after Wave 2 stabilization
• Configuration and training parallelized across remaining locations
• Go-lives in batches of 3–5 locations per day
• 2-week stabilization period

Go/No-Go Criteria

Criteria to Advance from Wave 1 to Wave 2 🟣

Criterion	Threshold for "Go"	Measurement
Technical stability	<3 critical bugs, none unresolved	Vendor issue tracker
Integration integrity	100% PMS sync accuracy	Audit 50 patient records
Staff adoption	80%+ forms completed digitally	mConsent dashboard
Patient experience	No increase in complaints	Office manager report
Champion confidence	Champions report "ready to train others"	Champion survey
Support load	Vendor can support 3x location count	Vendor confirmation

Decision Meeting: Schedule 2-hour retrospective at end of Wave 1 with:

• Regional managers of pilot locations
• Champions from pilot locations
• VP of Operations
• Vendor CSM

🟣 VP of Operations makes final go/no-go decision with input from CDO on clinical workflow impacts.

Criteria to Advance from Wave 2 to Wave 3

Same criteria as above, plus:

• Train-the-trainer model validated (champions successfully trained their teams)
• Regional support model tested (regional managers can handle escalations)
• No systemic issues appearing across multiple locations

Rollback Plan ⚠️

⚠️ Common Failure Point: Organizations without a rollback plan panic when issues arise and make inconsistent decisions across locations.

Rollback Triggers

• Critical bug affecting patient safety or significant data integrity
• PMS integration failure causing lost appointments or patient data

• 50% of forms failing to sync after 24 hours

• Multiple patient complaints about experience (>5 in single day at single location)

Rollback Procedure (Per Location)

1. Immediate (0–1 hour):

   • Champion notifies regional manager
   • Revert to paper forms (pre-printed backups should be maintained)
   • Disable mConsent tablets in waiting area
   • Notify patients verbally: "We're experiencing technical difficulties with our digital check-in"

2. Short-term (1–24 hours):

   • Regional manager notifies central IT and vendor
   • Maintain paper backup operations
   • Document all issues for vendor troubleshooting
   • Vendor provides root cause analysis

3. Decision Point (24–48 hours):

   • 🟣 VP of Operations decides: resume, extend rollback, or pause wave
   • If resuming: vendor provides fix and validation
   • If pausing: communicate to all locations in current wave

4. Cross-Wave Isolation:

   • Issues at one location do not automatically roll back other locations
   • Issues at 2+ locations in same wave trigger wave-level review
   • Future waves proceed only after root cause resolution

---

5. Configuration & Integration (Weeks 2–3)

Step-by-Step PMS Integration

Dentrix Integration 🔵

Estimated Time: 2–4 hours per location

1. ☐ Verify Dentrix version (G7+ required; G6.2 supported with limitations)
2. ☐ 🔵 Request Dentrix API credentials from mConsent
3. ☐ Enable Dentrix eServices API (if not already active)
4. ☐ 🔵 Configure mConsent connector with Dentrix practice ID
5. ☐ Map patient demographic fields (verify field naming conventions)
6. ☐ Configure appointment type mappings
7. ☐ Enable real-time sync (vs. batch)
8. ☐ Test patient creation → verify appears in Dentrix within 30 seconds
9. ☐ Test appointment pull → verify mConsent displays correct schedule
10. ☐ Test form completion → verify data writes to Dentrix patient record

⚠️ Common Issue: Dentrix multi-location databases require server-level configuration. Engage Dentrix support if running centralized database.

Eaglesoft Integration 🔵

Estimated Time: 2–4 hours per location

1. ☐ Verify Eaglesoft version (v21+ recommended)
2. ☐ 🔵 Obtain Eaglesoft HL7 or API bridge documentation from mConsent
3. ☐ Install mConsent connector on Eaglesoft server
4. ☐ Configure database connection string
5. ☐ Map patient fields and appointment types
6. ☐ Enable bidirectional sync
7. ☐ Test new patient creation
8. ☐ Test existing patient lookup
9. ☐ Test form data write-back

⚠️ Common Issue: Eaglesoft firewall settings may block connector. Whitelist mConsent connector process.

Open Dental Integration 🔵

Estimated Time: 1–3 hours per location

1. ☐ Verify Open Dental version (20.1+ required)
2. ☐ Enable Open Dental API access (Setup → Misc → API)
3. ☐ 🔵 Generate API key and provide to mConsent
4. ☐ Configure mConsent with Open Dental database connection
5. ☐ Map custom patient fields (Open Dental allows extensive customization)
6. ☐ Test integration using Open Dental test patient
7. ☐ Verify form responses populate appropriate fields

Open Dental Advantage: Most flexible integration; custom fields map easily.

Imaging & Clinical System Integration

mConsent primarily handles patient communication and intake. Imaging integration is typically indirect (patient records sync via PMS). However, if capturing imaging consent or patient photography:

☐ 🔵 Configure imaging consent forms within mConsent ☐ Verify patient ID linking between mConsent and imaging system ☐ Test that signed imaging consent appears in patient chart before imaging appointment

Test Environment Setup and Validation Checklist

Centralized Test Environment (Recommended for DSO)

1. ☐ 🔵 Request dedicated mConsent sandbox instance from vendor
2. ☐ Connect sandbox to PMS test database (NOT production)
3. ☐ Create 10 test patients with varied scenarios:
   • New patient (never seen)
   • Returning patient (existing record)
   • Patient with insurance (verify eligibility testing)
   • Patient without insurance
   • Minor patient (guardian consent testing)
   • Patient with complex medical history
   • Patient requiring translation/accessibility features
   • Patient with prior incomplete forms
4. ☐ Test complete patient journey for each scenario
5. ☐ Document any issues with screenshots and steps to reproduce

Validation Checklist (Must Pass Before Production)

Test	Expected Result	Pass/Fail
New patient completes intake form	Record created in PMS with all fields populated
Existing patient updates info	PMS record updated, no duplicate created
Insurance verification	Eligibility returned within 30 seconds
E-signature on consent	Signature stored, timestamp recorded, PDF generated
Appointment reminder sent	Patient receives SMS/email at configured time
Patient responds to reminder	Response logged, appointment status updated
Form partially completed, resumed	Patient can continue where they left off
Tablet loses connectivity	Graceful error, data preserved for later sync

Data Migration & Historical Data Ingestion

mConsent primarily captures forward-looking data. Historical migration considerations:

☐ 🟣 Decide: Import existing consent forms as PDFs? (typically not recommended—complex and low value) ☐ Import existing patient communication preferences from PMS ☐ Import appointment history (if switching from another reminder system) ☐ 🔵 Provide mConsent with existing patient contact list for initial sync

Security and HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

☐ 🔵 Obtain executed Business Associate Agreement (BAA) from mConsent ☐ Document data flow: patient device → mConsent cloud → PMS ☐ Verify encryption in transit (TLS 1.2+) and at rest (AES-256) ☐ Confirm mConsent SOC 2 Type II certification current ☐ Document data retention policies (how long are forms stored?) ☐ Verify patient data deletion process (HIPAA right to amendment/deletion) ☐ Configure audit logging and review sample audit trail ☐ 🟣 Legal review of data governance and breach notification procedures ☐ Document data backup and disaster recovery procedures

Access Control Checklist

☐ Implement SSO integration (see Pre-Implementation) ☐ Configure role-based access for each user type ☐ Disable local password authentication (SSO only) ☐ Enable MFA for admin accounts ☐ Document user provisioning and de-provisioning process ☐ Test access termination (user removed from identity provider → immediate mConsent lockout)

DSO Configuration Standards

Standardized Configuration Template (Identical Across All Locations)

Setting	Standard Value	Rationale
Consent form content	Enterprise-approved templates only	Legal consistency
Appointment reminder timing	72h, 24h, 2h before	Patient experience consistency
SMS sender name	[DSO Brand Name]	Brand recognition
Email template branding	Corporate logo, colors	Brand consistency
Form timeout	30 minutes	Security standard
Data retention	7 years	Compliance standard
Insurance verification	Enabled	Revenue cycle optimization
Patient portal branding	Corporate standard	Brand consistency
HIPAA acknowledgment	Enterprise standard form	Legal requirement

Location-Specific Configuration (Allowed Variation)

Setting	Local Discretion Allowed	Boundaries
Office-specific welcome message	Yes	Must use approved tone/language
Provider bios/photos	Yes	Office manager maintains
Office hours	Yes	Required for accurate scheduling
Specialty-specific consent forms	Yes	Must be approved by legal
Language preferences	Yes	Add languages as needed from approved list
Recall/recare timing	Yes	Within enterprise min/max range
Local office contact info	Yes	Required for accuracy

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Select 1 champion per location who meets MOST of the following:

☐ Office Manager, lead hygienist, or front desk lead (authority to guide team) ☐ Minimum 1 year tenure at location ☐ Demonstrated comfort with technology (uses smartphone apps, navigates PMS easily) ☐ Respected by peers (recommendations followed) ☐ Available for 4–6 hours of certification training ☐ Willing to be first point of contact for location's questions ☐ Patient and capable of teaching others

Ideal Champion Profile: Office Manager who is tech-comfortable and has strong relationships with both front desk staff and providers.

Champion Responsibilities

1. Before Go-Live:

   • Complete mConsent champion certification (4–6 hours)
   • Customize training delivery for their location's specific needs
   • Train all location staff (providers, hygienists, front desk)
   • Verify all staff complete training before go-live

2. Go-Live Week:

   • Be present for go-live day
   • Serve as first point of contact for staff questions
   • Escalate unresolved issues to regional manager
   • Conduct end-of-day debrief with team

3. Ongoing:

   • Train new hires within 48 hours of start date
   • Provide refresher training quarterly
   • Communicate new features to team
   • Submit enhancement requests to central team

Champion Certification Program 🔵

Duration: 4–6 hours (can be split across 2 days)

Delivery: Virtual instructor-led training by mConsent + recorded modules for reference

Curriculum:

1. ☐ mConsent platform overview (30 min)
2. ☐ Complete patient intake workflow—hands-on (45 min)
3. ☐ Consent form management (30 min)
4. ☐ Appointment reminder configuration (30 min)
5. ☐ Two-way messaging and patient communication (30 min)
6. ☐ Troubleshooting common issues (45 min)
7. ☐ Training others—how to deliver role-specific training (30 min)
8. ☐ Certification quiz (30 min; must score 80%+)

☐ 🔵 Schedule certification sessions with mConsent (recommend 2 weeks before Wave 1 go-live)

Standardized Training Materials

Centrally-Created Materials

Material	Creator	Purpose
Training slide deck (per role)	Central team + mConsent	Consistent messaging
Day 1 cheat sheets (per role)	Central team	Quick reference
FAQ document	Central team	Common questions
Video walkthroughs	mConsent	On-demand reference
Training completion tracker	Central team	Compliance verification

Champion-Customized Materials

Material	Champion Responsibility
Location-specific screenshots	Add local examples
Provider-specific workflows	Adapt to individual preferences
Local FAQ additions	Address location-specific questions

Role-Specific Training Outlines

Providers (Dentists, Specialists)

Training Time: 30–45 minutes Format: In-office demo during lunch or team meeting + Day 1 cheat sheet Trainer: Champion (with provider lead previewing content)

Content:

1. How patient information appears before appointment (5 min)

   • Where to view completed intake forms
   • Medical history summary view
   • Alerts/flags for critical information

2. Consent documentation (10 min)

   • Reviewing signed consents
   • Requesting additional consents mid-visit
   • Provider attestation workflows

3. Patient communication (10 min)

   • Viewing patient messages
   • When to respond vs. delegate to front desk
   • Post-visit communication workflows

4. Override and manual entry (5 min)

   • When digital intake is unavailable
   • How to flag data quality issues

5. Q&A (10 min)

Common Resistance Points:

• "This slows me down" → Show time saved by pre-populated info; emphasize legibility
• "I don't trust patient-entered data" → Show verification flags; note liability protection of signed forms
• "Just give me paper" → Note compliance requirements and reduced chart prep time

Provider Day 1 Cheat Sheet:

┌─────────────────────────────────────────────────────────────┐
│ mConsent Quick Reference – Providers                        │
├─────────────────────────────────────────────────────────────┤
│ 1. View patient intake:      [PMS] → Patient → mConsent tab │
│ 2. Review consents:          Look for green ✓ = signed      │
│ 3. Missing consent?          Ask front desk to send via     │
│                              tablet                          │
│ 4. Flag data concern:        Click "?" icon → add note      │
│ 5. Need help?                Ask [Champion Name]            │
│ 6. Urgent tech issue?        Call [Regional Manager Phone]  │
└─────────────────────────────────────────────────────────────┘

Hygienists

Training Time: 20–30 minutes Format: In-office demo + hands-on practice Trainer: Champion

Content:

1. Viewing patient health history updates (10 min)

   • Where to find completed medical history
   • Identifying changes since last visit
   • Alerts for antibiotic premedication, etc.

2. Patient check-in verification (5 min)

   • Confirming patient completed intake
   • Requesting missing forms before seating patient

3. Chairside communication (10 min)

   • Showing patients their own records
   • Capturing additional consent if needed

Common Resistance Points:

• "I don't check in patients" → Emphasize knowing patient status before seating
• "This is front desk's job" → Clarify hygienists can verify, reducing chair time wasted

Hygienist Day 1 Cheat Sheet:

┌─────────────────────────────────────────────────────────────┐
│ mConsent Quick Reference – Hygienists                       │
├─────────────────────────────────────────────────────────────┤
│ 1. Before seating patient:   Check green ✓ = forms done     │
│ 2. Forms incomplete?         Point patient to kiosk         │
│ 3