Implementation PlaybookDSO · Group Practice

QuantaPay

Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.

Contents

QuantaPay — Implementation Playbook (DSO)

QuantaPay Implementation Playbook

Revenue Cycle AI for Dental Support Organizations

1. Executive Summary

What QuantaPay Does

QuantaPay is an AI-powered revenue cycle management platform that automates insurance verification, claims submission, denial management, and payment posting across your dental organization. The system uses machine learning to predict claim outcomes, identify coding optimization opportunities, and accelerate collections while reducing manual administrative burden.

Why DSOs Benefit from Revenue Cycle AI at Scale

Revenue cycle AI delivers exponential returns for multi-location organizations. With 15–50 locations generating thousands of claims monthly, even a 2% improvement in first-pass claim acceptance or a 3-day reduction in days in A/R translates to six or seven figures annually. DSOs gain three distinct advantages:

Data Aggregation Power: QuantaPay's models improve with volume. Your 50-location claim history trains the AI to predict denials, optimize coding, and identify payer-specific patterns that single practices could never detect.
Standardization at Scale: Eliminate the revenue cycle performance variance between your best and worst-performing locations. The AI enforces consistent workflows, coding accuracy, and follow-up protocols enterprise-wide.
Centralized Visibility: Real-time dashboards expose revenue leakage, staff productivity gaps, and payer behavior patterns across your entire portfolio—enabling data-driven decisions about everything from payer contract negotiations to staffing models.

Expected Timeline: Decision to Full Deployment

Pilot Wave (2–3 locations): Weeks 1–6
Wave 2 (5–8 locations): Weeks 7–12
Wave 3+ (Remaining locations): Weeks 13–20
Full Optimization: Weeks 21–26

Total Timeline: 5–6 months for a 30-location DSO; add 4–6 weeks for each additional 15 locations.

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

Technical Requirements

Hardware Requirements per Location

☐ Workstations: Windows 10/11 or macOS 12+, minimum 8GB RAM, 256GB SSD ☐ Minimum two monitors recommended for billing staff (AI dashboard + PMS) ☐ Dedicated scanner for EOB/correspondence processing (if not already digital)

Network Requirements

☐ Minimum 50 Mbps download / 10 Mbps upload per location ☐ Stable connection (<100ms latency to QuantaPay servers) ☐ Firewall configuration to whitelist QuantaPay IP ranges and domains ☐ ⚠️ Verify VPN compatibility if locations route through central VPN

Software Requirements

☐ Practice Management System: Dentrix G7+, Eaglesoft 21+, Open Dental 22+, Denticon, or Curve (confirm specific version compatibility with vendor) ☐ Web browser: Chrome 90+ or Edge 90+ (Firefox has known dashboard rendering issues) ☐ PDF reader for EOB processing

Enterprise-Level Requirements 🟣

☐ Network Standardization Assessment: Document current network configurations across all locations; identify locations below minimum thresholds ☐ Hosting Decision: Cloud-hosted (recommended for DSOs) vs. hybrid with on-premise data caching ☐ SSO Integration: Confirm QuantaPay supports your identity provider (Okta, Azure AD, Google Workspace) ☐ Centralized Credentialing: Map how provider credentials flow from your credentialing system into QuantaPay ☐ Data Residency Requirements: Confirm compliance with any state-specific data residency requirements

Vendor Onboarding Steps

Key Contacts to Establish 🔵

☐ Implementation Manager (your primary contact for rollout): _______________ ☐ Technical Integration Specialist (API and PMS integration): _______________ ☐ Training Lead (champion certification and materials): _______________ ☐ Customer Success Manager (post-launch optimization): _______________ ☐ Escalation Contact (VP-level for executive issues): _______________

Onboarding Meetings to Schedule 🔵

☐ Kickoff Call (Week 1, Day 1–2): Introduce teams, confirm scope, validate timeline

Time estimate: 90 minutes ☐ Technical Discovery Call (Week 1, Day 3–4): Deep dive on PMS versions, integrations, network
Time estimate: 2 hours ☐ Data Migration Scoping Call (Week 1, Day 5): Historical claims data, patient demographics, payer data
Time estimate: 90 minutes ☐ Security & Compliance Review (Week 2): BAA execution, access controls, audit logging
Time estimate: 60 minutes

Data/Access Prerequisites

Credentials and Access to Gather

☐ PMS admin credentials (or create dedicated QuantaPay service account) for each location ☐ Clearinghouse login credentials (Tesia, DentalXChange, NEA, etc.) ☐ Payer portal credentials for top 10 payers by volume ☐ API keys from PMS vendor (if applicable—Open Dental, Denticon) ☐ ⚠️ Bank account information for payment posting automation (requires CFO approval)

Data Exports to Prepare

☐ 24 months of claims history export (CSV or XML format per vendor spec) ☐ Current fee schedules by payer and location ☐ Provider NPI and taxonomy codes ☐ Active patient roster with insurance information ☐ Current A/R aging report by location

Internal Stakeholder Alignment

Stakeholder Alignment Map 🟣

Stakeholder Level	Key Individuals	Role in Implementation	Required Action
Board/Investors	Board Chair, PE Partner	Approve capital expenditure; receive ROI updates	Budget approval; quarterly briefings
C-Suite	CEO, CFO, COO, CDO	Strategic sponsorship; cross-functional alignment	Executive sponsor designation; resource allocation
VP Operations	VP Ops, VP Revenue Cycle	Day-to-day implementation ownership; regional coordination	Implementation lead; vendor relationship owner
Regional Managers	Regional Directors (3–5)	Wave execution; location manager support	Champion coordination; escalation handling
Location Managers	Office Managers (15–50)	Local execution; staff coordination	Staff scheduling; go-live execution
Providers	Dentists, Specialists	Clinical workflow adaptation; coding collaboration	Training completion; workflow adoption
Billing Staff	RCM Specialists, AR Coordinators	Primary daily users; workflow transformation	Training completion; feedback provision

Approval Gates 🟣

☐ Budget Approval: Board/CFO sign-off on implementation costs and subscription ☐ Data Sharing Approval: Legal/Compliance sign-off on BAA and data flows ☐ Banking Integration Approval: CFO sign-off on payment posting automation ☐ Rollout Sequence Approval: COO sign-off on wave structure and location sequence

Baseline Metrics to Capture

⚠️ Critical: Standardize Measurement Methodology Across All Locations

Before any integration begins, establish enterprise-wide definitions and capture 90 days of baseline data:

Revenue Cycle Metrics (Capture per Location + Aggregate)

Metric	Definition	Target Benchmark	Your Baseline
Days in A/R	Average days from service to payment posting	<28 days	_______
First-Pass Claim Acceptance Rate	% of claims paid without rejection/denial	>95%	_______
Denial Rate	% of claims denied by payer	<5%	_______
Denial Appeal Success Rate	% of appealed denials overturned	>60%	_______
Clean Claim Rate	% of claims submitted without errors	>98%	_______
Collection Rate	Collections / Net Production	>98%	_______
Time to Payment Posting	Days from payment receipt to posting	<2 days	_______
Insurance Verification Time	Minutes per patient verification	<8 minutes	_______

Operational Metrics

Metric	Definition	Your Baseline
Claims Submitted per FTE per Day	Productivity measure	_______
Outstanding Claims >90 Days	Volume and dollar value	_______
Write-Off Rate	Write-offs / Gross Production	_______
Patient Responsibility Collection Rate	% of patient balances collected	_______

Data Collection Protocol

☐ Pull reports from PMS for each location using identical report parameters ☐ Export to standardized Excel template (provided by QuantaPay or created internally) ☐ ⚠️ Validate that each location calculates metrics identically (e.g., same definition of "denied" vs. "rejected") ☐ Store baseline data in centralized repository for post-launch comparison

3. Location Readiness Assessment

Scoring Framework

Score each location on the following factors (1 = significant concerns, 5 = ideal):

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

Score	Criteria
5	Fiber internet, hardware <2 years old, current PMS version, no VPN latency issues
4	Cable internet 100+ Mbps, hardware <3 years old, PMS within one version of current
3	Cable internet 50+ Mbps, hardware <4 years old, PMS within two versions
2	DSL or unreliable connection, hardware 4–5 years old, outdated PMS
1	Connection frequently drops, hardware >5 years old, legacy PMS version

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

Score	Criteria
5	Low turnover (<15%), history of successful tech adoptions, billing staff >2 years tenure
4	Moderate turnover (15–25%), one successful tech adoption, billing staff >1 year tenure
3	Average turnover (25–35%), mixed tech adoption history, stable billing lead
2	High turnover (35–50%), past tech adoption challenges, billing staff <1 year tenure
1	Very high turnover (>50%), significant resistance to change, new billing team

Factor 3: Patient Volume (Weight: 20%)

Score	Criteria
5	High volume (500+ patients/month) with stable scheduling—maximum impact potential
4	Moderate-high volume (350–500/month), predictable scheduling
3	Moderate volume (200–350/month)—good balance of impact and manageable risk
2	Lower volume (100–200/month)—limited impact but lower risk for piloting
1	Very low volume (<100/month) or highly unpredictable scheduling

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

Score	Criteria
5	PMS with native API support, same PMS as majority of portfolio, standard clearinghouse
4	PMS with QuantaPay-tested integration, compatible clearinghouse
3	PMS with documented integration path, may require custom configuration
2	PMS with limited integration history, non-standard clearinghouse
1	Legacy PMS with no API, integration will require manual workarounds

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

Score	Criteria
5	Office manager with tech implementation experience + engaged provider sponsor
4	Strong office manager willing to champion, provider supportive
3	Competent office manager, provider neutral
2	Office manager stretched thin, provider skeptical
1	No clear champion candidate, provider resistant or absent

Composite Score Calculation

Formula: (IT × 0.25) + (Staff × 0.20) + (Volume × 0.20) + (Tech Stack × 0.20) + (Champion × 0.15) = Readiness Score

Score Interpretation

Composite Score	Readiness Tier	Rollout Recommendation
4.5 – 5.0	Tier 1: Pilot Ready	Wave 1 candidate
3.5 – 4.4	Tier 2: Ready with Preparation	Wave 2 candidate
2.5 – 3.4	Tier 3: Needs Remediation	Wave 3 after specific improvements
1.0 – 2.4	Tier 4: High Risk	Address foundational issues before including

Sample Location Readiness Matrix

Location	IT (×0.25)	Staff (×0.20)	Volume (×0.20)	Tech (×0.20)	Champion (×0.15)	Composite	Tier
Midtown Plaza	5 (1.25)	4 (0.80)	4 (0.80)	5 (1.00)	5 (0.75)	4.60	1
Riverside	4 (1.00)	5 (1.00)	3 (0.60)	4 (0.80)	4 (0.60)	4.00	2
Northgate	3 (0.75)	3 (0.60)	5 (1.00)	4 (0.80)	3 (0.45)	3.60	2
Downtown	2 (0.50)	2 (0.40)	4 (0.80)	3 (0.60)	2 (0.30)	2.60	3

Recommended Rollout Sequence

Wave 1 Pilot Selection Criteria 🟣

Select 2–3 locations from Tier 1 that also meet these criteria:

☐ Geographic diversity (different regions if applicable)
☐ PMS diversity if portfolio has multiple systems (test integration with each)
☐ Mix of practice types (GP + specialty if applicable)
☐ NOT your highest-revenue locations (protect revenue during learning phase)
☐ Strong office manager willing to provide detailed feedback

Remediation Plan for Tier 3–4 Locations

Before including in later waves: ☐ Upgrade internet connection to minimum threshold ☐ Ensure PMS is updated to compatible version ☐ Identify or develop local champion (may require OM coaching) ☐ Address staff turnover issues or wait for team stability

4. Rollout Strategy

Recommended Wave Structure

Wave 1: Pilot (Weeks 1–6)

Locations: 2–3 Tier 1 locations Duration: 6 weeks (2 weeks prep, 1 week go-live, 3 weeks stabilization)

Purpose:

Validate integration assumptions
Identify workflow gaps not discovered in testing
Train first cohort of champions who become peer mentors
Establish realistic performance expectations

Selection Criteria for Wave 1: ☐ Highest readiness scores (4.5+) ☐ Represents different PMS if portfolio has mix ☐ Different geographic regions (tests support coverage) ☐ Not top 3 revenue generators (protect revenue during learning) ☐ Office managers excited to participate (not voluntold)

Wave 2: Expansion (Weeks 7–12)

Locations: 5–8 Tier 1 and high Tier 2 locations Duration: 6 weeks (1 week prep, 1 week staggered go-live, 4 weeks stabilization)

Purpose:

Validate scalability of support model
Test champion training cascade
Stress test vendor support capacity
Refine playbook based on Wave 1 learnings

Wave 3+: Scale (Weeks 13–20)

Locations: Remaining Tier 2 and remediated Tier 3 locations Duration: 8 weeks (1 week prep per cohort, staggered go-lives, 4 weeks stabilization)

Purpose:

Execute refined, proven playbook
Champions from earlier waves mentor new locations
Focus shifts from implementation to optimization

Timeline Per Wave

Wave 1 Detailed Timeline

Week	Activities
Week 1	Integration testing, champion training, staff training scheduling
Week 2	Staff training completion, parallel run prep, go-live readiness review
Week 3	Go-live (stagger across 3 days: Mon/Wed/Fri)
Week 4	Daily check-ins, troubleshooting, workflow adjustments
Week 5	Twice-weekly check-ins, performance tracking begins
Week 6	Wave 1 retrospective, go/no-go decision for Wave 2

Wave 2+ Timeline (Compressed Based on Learnings)

Week	Activities
Week 1	Champion certification, integration validation, staff training
Week 2	Go-live (stagger 2 locations per day)
Weeks 3–4	Stabilization, daily then twice-weekly check-ins
Week 5–6	Performance validation, go/no-go for next wave

Go/No-Go Criteria 🟣

Advance to Next Wave When:

☐ >90% of staff at current wave locations have completed training ☐ Clean claim rate at pilot locations ≥95% ☐ No unresolved critical integration bugs ☐ Average daily claims processing time meets or beats baseline ☐ No more than 2 "red" status locations (see status framework in Section 12) ☐ Champion survey satisfaction score >4.0/5.0 ☐ Vendor confirms support capacity for additional locations

⚠️ Pause Criteria (Red Flags):

☐ Integration failure affecting >20% of claims at any location ☐ Staff productivity dropped >30% vs. baseline after Week 2 ☐ Vendor support response time exceeding SLA for >3 consecutive days ☐ Security incident or HIPAA concern identified ☐ >50% of billing staff requesting to return to old workflow

Rollback Plan

Tier 1 Issues (Continue with Caution)

Examples: Minor integration bugs, isolated user errors, performance slightly below target

Document issue
Work with vendor for patch/fix
Do not pause rollout

Tier 2 Issues (Pause Wave, Investigate)

Examples: Systematic integration failures at multiple locations, claims processing delays >48 hours, staff unable to complete core tasks

Immediate Actions:

☐ Halt further go-lives for affected wave
☐ Daily war room calls with vendor (30 minutes, 9 AM)
☐ Document affected locations and specific symptoms
☐ Isolate: Is this a vendor issue, integration issue, or training issue?

Resolution Path:

If resolved within 5 business days: Resume rollout
If >5 days: Executive decision to continue investigation or rollback

Tier 3 Issues (Full Rollback)

Examples: Data integrity issues, HIPAA breach, claims submitted incorrectly to payers

Rollback Protocol:

☐ 🟣 Immediately notify executive sponsor and legal/compliance
☐ Disable QuantaPay integration at all affected locations
☐ Revert to pre-QuantaPay workflow (ensure staff retained training on legacy process)
☐ Document all affected claims for manual review and correction
☐ Conduct root cause analysis with vendor before any future rollout
☐ Do not disrupt locations not yet live—they continue operating normally

5. Configuration & Integration (Weeks 2–3)

Step-by-Step Integration by PMS

Dentrix (G7+) Integration 🔵

Time Estimate: 4–6 hours per location

☐ Step 1: Create Dentrix service account with appropriate permissions

User role: Practice Administrator
Enable API access in Dentrix settings (Office Manager > Administrative Setup)

☐ Step 2: Install QuantaPay Dentrix Connector 🔵

Download from QuantaPay implementation portal
Run installer on Dentrix server (requires admin rights)
Enter license key provided by QuantaPay

☐ Step 3: Configure connector settings

Map provider IDs to QuantaPay provider records
Set claim extraction frequency (real-time recommended)
Configure payment posting preferences

☐ Step 4: Test connection

Submit test claim through Dentrix → verify appears in QuantaPay within 5 minutes
Post test payment in QuantaPay → verify reflects in Dentrix within 5 minutes
⚠️ Verify insurance eligibility responses populate correctly

☐ Step 5: Enable production mode (requires QuantaPay sign-off) 🔵

Eaglesoft (21+) Integration 🔵

Time Estimate: 4–6 hours per location

☐ Step 1: Enable Eaglesoft API module

Contact Patterson support to enable API access 🔵
Obtain API credentials from Patterson

☐ Step 2: Configure QuantaPay Eaglesoft bridge

Enter API credentials in QuantaPay admin panel
Map procedure codes (Eaglesoft to ADA)
Configure provider and facility mappings

☐ Step 3: Set data sync parameters

Historical data import: 24 months (overnight batch)
Real-time sync for new claims and payments

☐ Step 4: Test bidirectional data flow

Create new appointment with insurance → verify QuantaPay verifies eligibility
Process claim in Eaglesoft → verify QuantaPay tracks
⚠️ Test write-back of eligibility data to Eaglesoft

☐ Step 5: Production activation 🔵

Open Dental (22+) Integration 🔵

Time Estimate: 3–4 hours per location

☐ Step 1: Enable Open Dental API

Navigate to Setup > Advanced > API
Generate API key with appropriate permissions
⚠️ Ensure "Enable API" checkbox is checked

☐ Step 2: Configure QuantaPay connection

Enter Open Dental API endpoint and key
Test connection (should return practice name)

☐ Step 3: Map data fields

Provider NPI mapping
Insurance plan matching
Fee schedule alignment

☐ Step 4: Enable real-time claim sync

Configure webhook for claim status updates
Set payment posting automation level (manual review vs. auto-post)

☐ Step 5: Test and activate 🔵

Clearinghouse Integration 🔵

Time Estimate: 2–3 hours (one-time)

☐ Step 1: Confirm clearinghouse compatibility

Primary supported: Tesia, DentalXChange, NEA, Availity
⚠️ If using non-standard clearinghouse, confirm with QuantaPay before proceeding

☐ Step 2: Configure EDI connection

Provide clearinghouse submitter ID
Configure SFTP or API credentials
Set payer ID mappings (QuantaPay provides standard payer table)

☐ Step 3: Test claim submission flow

Submit test batch to clearinghouse sandbox
Verify acknowledgment receipt in QuantaPay
Process ERA/835 test file through QuantaPay

Test Environment Setup

Test Environment Validation Checklist

☐ Patient Data

Create 5 test patients with different insurance scenarios:
- Commercial PPO
- Commercial HMO/DHMO
- Medicaid
- Medicare (if applicable)
- Dual-coverage patient

☐ Claim Scenarios to Test

Test Scenario	Expected Result	Pass/Fail
Clean claim submission	Accepted by clearinghouse <5 min	☐
Claim with missing info	Flagged by QuantaPay before submission	☐
Duplicate claim detection	Alert generated, submission blocked	☐
Prior authorization required	PA workflow triggered	☐
ERA/835 processing	Payment auto-posted correctly	☐
Patient eligibility check	Response within 30 seconds	☐
Denial prediction	High-risk claims flagged	☐

☐ Integration Validation

PMS → QuantaPay data sync within 5 minutes
QuantaPay → PMS payment posting accurate to penny
No duplicate records created in either system

Data Migration

Historical Data Ingestion Steps 🔵

Time Estimate: 2–5 days depending on data volume

☐ Step 1: Export historical claims data

24 months minimum recommended
Include: claim ID, DOS, procedure codes, billed amount, paid amount, denial codes, payer ID

☐ Step 2: Export patient and insurance data

Active patients with insurance on file
Insurance plan details and group numbers

☐ Step 3: 🔵 Submit data package to QuantaPay

Use secure file transfer (SFTP provided by QuantaPay)
⚠️ Do not email PHI data

☐ Step 4: 🔵 QuantaPay validates and ingests data

Review data quality report
Address any mapping errors or data gaps

☐ Step 5: Verify historical data in QuantaPay dashboard

Spot-check 10 random claims against PMS records
Verify denial rate calculations match your baseline metrics

Enterprise Configuration 🟣

Standardized Configuration Template

The following settings should be identical across all locations:

Setting Category	Standard Value	Notes
User roles and permissions	[Your standard role matrix]	Define: Admin, Billing Specialist, Billing Manager, Read-Only
Auto-posting thresholds	Auto-post if variance <$5	Higher variances require manual review
Denial categories	[Standard taxonomy]	Use QuantaPay default or customize enterprise-wide
Workflow stages	[Standard pipeline]	Submission → Pending → Paid/Denied → Follow-up → Resolved
Report schedules	Daily/weekly on same cadence	Enables cross-location comparison
Alert thresholds	Denial rate >7%, Claims >45 days	Triggers escalation
SSO configuration	[Your IdP]	Enforce SSO; disable local passwords

Location-Specific Configuration (Allowable Variance)

Setting Category	Local Discretion Allowed	Notes
Provider preferences	Yes	Individual providers may have coding preferences
Fee schedules	Yes	Varies by payer contract per location
Payer mix weighting	Yes	AI model can weight location-specific payer behavior
Working hours	Yes	For scheduling automated processes
Local report recipients	Yes	Office manager and regional manager

Security and HIPAA Compliance

Enterprise HIPAA Checklist 🟣

☐ Business Associate Agreement

BAA executed with QuantaPay ✓ Signed by: _______________ Date: ___
BAA covers all locations under master agreement

☐ Data Encryption

Data encrypted in transit (TLS 1.2+) ✓
Data encrypted at rest (AES-256) ✓
Confirm encryption certificate validity

☐ Access Controls

SSO enforced for all users
Role-based access control configured
Minimum necessary standard applied (users see only their location unless regional+)
MFA enabled for admin accounts

☐ Audit Logging

All PHI access logged and reviewable
Logs retained per your retention policy (minimum 6 years)
Access logs exportable for compliance audits

☐ Data Governance

Data retention period confirmed: _____ years
Data deletion process documented
Data portability confirmed (can export data if contract ends)

☐ Incident Response

QuantaPay breach notification policy reviewed (<24 hours notification)
Internal incident response plan updated to include QuantaPay

☐ Vendor Security Review

SOC 2 Type II report reviewed ✓
Penetration test results reviewed (if available)
Security questionnaire completed

6. Team Training Plan

Train-the-Trainer Model

Overview

Central team trains 1 champion per location → Champions train their local team → Central team provides ongoing support and certification verification.

Benefits:

Scalable across 15–50+ locations
Local champions understand their team's dynamics
Builds internal expertise for ongoing optimization
Reduces vendor dependency for training

Champion Selection Criteria

Ideal Champion Profile: ☐ Office manager or senior billing specialist ☐ 1+ year tenure at location ☐ History of successful tech adoption ☐ Strong communication skills (will train others) ☐ Time availability (expect 8–12 hours for training + certification) ☐ Willing, not voluntold

Champion Responsibilities:

Complete champion certification (4–6 hours)
Deliver role-specific training to all staff at location (4–8 hours)
Serve as first point of contact for staff questions during rollout
Participate in daily/weekly check-ins with central team
Provide feedback to improve training and process
Onboard new hires to QuantaPay (ongoing)

Champion Certification Program 🔵

Delivered By: QuantaPay Training Lead + Central Operations Team Format: Virtual instructor-led + hands-on lab Duration: 6 hours (can be split across 2 days)

Certification Curriculum:

Module	Duration	Content
Module 1: System Overview	45 min	QuantaPay architecture, data flows, key screens
Module 2: Daily Billing Workflow	90 min	Eligibility verification, claim submission, denial management
Module 3: Payment Processing	60 min	ERA processing, auto-posting, reconciliation
Module 4: Reporting & Analytics	45 min	Dashboard navigation, key metrics, report generation
Module 5: Troubleshooting	45 min	Common issues, escalation paths, vendor support process
Module 6: Training Delivery Skills	60 min	How to train adult learners, managing resistance, Q&A techniques

Certification Requirements: ☐ Complete all modules ☐ Pass assessment quiz (80% minimum) ☐ Demonstrate competency in hands-on lab ☐ Receive certification badge 🔵

Role-Specific Training Outlines (For Champions to Deliver)

Dentists/Providers

Training Time: 30 minutes Format: 15-minute live demo + 15-minute Q&A Trainer: Champion (with CDO endorsement messaging)

Content:

What Changes (5 minutes)
- Insurance eligibility now verified in real-time before/during appointment
- Treatment plan estimates will be more accurate (AI-predicted coverage)
- You will see a "coverage confidence score" on the treatment screen
What You Need to Do (10 minutes)
- Review AI-flagged cases before signing off on treatment

AI-generated implementation guide based on public vendor information. Verify specifics directly with QuantaPay.

Implementation Playbook — DSO · Group Practice

QuantaPay

avized.com

Generated May 28, 2026

AI-generated guide based on public vendor information. Verify specifics directly with QuantaPay.

QuantaPay — Implementation Playbook (DSO)

QuantaPay Implementation Playbook

Revenue Cycle AI for Dental Support Organizations

1. Executive Summary

What QuantaPay Does

Why DSOs Benefit from Revenue Cycle AI at Scale

Data Aggregation Power: QuantaPay's models improve with volume. Your 50-location claim history trains the AI to predict denials, optimize coding, and identify payer-specific patterns that single practices could never detect.
Standardization at Scale: Eliminate the revenue cycle performance variance between your best and worst-performing locations. The AI enforces consistent workflows, coding accuracy, and follow-up protocols enterprise-wide.
Centralized Visibility: Real-time dashboards expose revenue leakage, staff productivity gaps, and payer behavior patterns across your entire portfolio—enabling data-driven decisions about everything from payer contract negotiations to staffing models.

Expected Timeline: Decision to Full Deployment

Pilot Wave (2–3 locations): Weeks 1–6
Wave 2 (5–8 locations): Weeks 7–12
Wave 3+ (Remaining locations): Weeks 13–20
Full Optimization: Weeks 21–26

Total Timeline: 5–6 months for a 30-location DSO; add 4–6 weeks for each additional 15 locations.

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

Technical Requirements

Hardware Requirements per Location

Network Requirements

Software Requirements

Enterprise-Level Requirements 🟣

Vendor Onboarding Steps

Key Contacts to Establish 🔵

Onboarding Meetings to Schedule 🔵

☐ Kickoff Call (Week 1, Day 1–2): Introduce teams, confirm scope, validate timeline

Time estimate: 90 minutes ☐ Technical Discovery Call (Week 1, Day 3–4): Deep dive on PMS versions, integrations, network
Time estimate: 2 hours ☐ Data Migration Scoping Call (Week 1, Day 5): Historical claims data, patient demographics, payer data
Time estimate: 90 minutes ☐ Security & Compliance Review (Week 2): BAA execution, access controls, audit logging
Time estimate: 60 minutes

Data/Access Prerequisites

Credentials and Access to Gather

Data Exports to Prepare

Internal Stakeholder Alignment

Stakeholder Alignment Map 🟣

Stakeholder Level	Key Individuals	Role in Implementation	Required Action
Board/Investors	Board Chair, PE Partner	Approve capital expenditure; receive ROI updates	Budget approval; quarterly briefings
C-Suite	CEO, CFO, COO, CDO	Strategic sponsorship; cross-functional alignment	Executive sponsor designation; resource allocation
VP Operations	VP Ops, VP Revenue Cycle	Day-to-day implementation ownership; regional coordination	Implementation lead; vendor relationship owner
Regional Managers	Regional Directors (3–5)	Wave execution; location manager support	Champion coordination; escalation handling
Location Managers	Office Managers (15–50)	Local execution; staff coordination	Staff scheduling; go-live execution
Providers	Dentists, Specialists	Clinical workflow adaptation; coding collaboration	Training completion; workflow adoption
Billing Staff	RCM Specialists, AR Coordinators	Primary daily users; workflow transformation	Training completion; feedback provision

Approval Gates 🟣

Baseline Metrics to Capture

⚠️ Critical: Standardize Measurement Methodology Across All Locations

Before any integration begins, establish enterprise-wide definitions and capture 90 days of baseline data:

Revenue Cycle Metrics (Capture per Location + Aggregate)

Metric	Definition	Target Benchmark	Your Baseline
Days in A/R	Average days from service to payment posting	<28 days	_______
First-Pass Claim Acceptance Rate	% of claims paid without rejection/denial	>95%	_______
Denial Rate	% of claims denied by payer	<5%	_______
Denial Appeal Success Rate	% of appealed denials overturned	>60%	_______
Clean Claim Rate	% of claims submitted without errors	>98%	_______
Collection Rate	Collections / Net Production	>98%	_______
Time to Payment Posting	Days from payment receipt to posting	<2 days	_______
Insurance Verification Time	Minutes per patient verification	<8 minutes	_______

Operational Metrics

Metric	Definition	Your Baseline
Claims Submitted per FTE per Day	Productivity measure	_______
Outstanding Claims >90 Days	Volume and dollar value	_______
Write-Off Rate	Write-offs / Gross Production	_______
Patient Responsibility Collection Rate	% of patient balances collected	_______

Data Collection Protocol

3. Location Readiness Assessment

Scoring Framework

Score each location on the following factors (1 = significant concerns, 5 = ideal):

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

Score	Criteria
5	Fiber internet, hardware <2 years old, current PMS version, no VPN latency issues
4	Cable internet 100+ Mbps, hardware <3 years old, PMS within one version of current
3	Cable internet 50+ Mbps, hardware <4 years old, PMS within two versions
2	DSL or unreliable connection, hardware 4–5 years old, outdated PMS
1	Connection frequently drops, hardware >5 years old, legacy PMS version

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

Score	Criteria
5	Low turnover (<15%), history of successful tech adoptions, billing staff >2 years tenure
4	Moderate turnover (15–25%), one successful tech adoption, billing staff >1 year tenure
3	Average turnover (25–35%), mixed tech adoption history, stable billing lead
2	High turnover (35–50%), past tech adoption challenges, billing staff <1 year tenure
1	Very high turnover (>50%), significant resistance to change, new billing team

Factor 3: Patient Volume (Weight: 20%)

Score	Criteria
5	High volume (500+ patients/month) with stable scheduling—maximum impact potential
4	Moderate-high volume (350–500/month), predictable scheduling
3	Moderate volume (200–350/month)—good balance of impact and manageable risk
2	Lower volume (100–200/month)—limited impact but lower risk for piloting
1	Very low volume (<100/month) or highly unpredictable scheduling

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

Score	Criteria
5	PMS with native API support, same PMS as majority of portfolio, standard clearinghouse
4	PMS with QuantaPay-tested integration, compatible clearinghouse
3	PMS with documented integration path, may require custom configuration
2	PMS with limited integration history, non-standard clearinghouse
1	Legacy PMS with no API, integration will require manual workarounds

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

Score	Criteria
5	Office manager with tech implementation experience + engaged provider sponsor
4	Strong office manager willing to champion, provider supportive
3	Competent office manager, provider neutral
2	Office manager stretched thin, provider skeptical
1	No clear champion candidate, provider resistant or absent

Composite Score Calculation

Formula: (IT × 0.25) + (Staff × 0.20) + (Volume × 0.20) + (Tech Stack × 0.20) + (Champion × 0.15) = Readiness Score

Score Interpretation

Composite Score	Readiness Tier	Rollout Recommendation
4.5 – 5.0	Tier 1: Pilot Ready	Wave 1 candidate
3.5 – 4.4	Tier 2: Ready with Preparation	Wave 2 candidate
2.5 – 3.4	Tier 3: Needs Remediation	Wave 3 after specific improvements
1.0 – 2.4	Tier 4: High Risk	Address foundational issues before including

Sample Location Readiness Matrix

Location	IT (×0.25)	Staff (×0.20)	Volume (×0.20)	Tech (×0.20)	Champion (×0.15)	Composite	Tier
Midtown Plaza	5 (1.25)	4 (0.80)	4 (0.80)	5 (1.00)	5 (0.75)	4.60	1
Riverside	4 (1.00)	5 (1.00)	3 (0.60)	4 (0.80)	4 (0.60)	4.00	2
Northgate	3 (0.75)	3 (0.60)	5 (1.00)	4 (0.80)	3 (0.45)	3.60	2
Downtown	2 (0.50)	2 (0.40)	4 (0.80)	3 (0.60)	2 (0.30)	2.60	3

Recommended Rollout Sequence

Wave 1 Pilot Selection Criteria 🟣

Select 2–3 locations from Tier 1 that also meet these criteria:

☐ Geographic diversity (different regions if applicable)
☐ PMS diversity if portfolio has multiple systems (test integration with each)
☐ Mix of practice types (GP + specialty if applicable)
☐ NOT your highest-revenue locations (protect revenue during learning phase)
☐ Strong office manager willing to provide detailed feedback

Remediation Plan for Tier 3–4 Locations

4. Rollout Strategy

Recommended Wave Structure

Wave 1: Pilot (Weeks 1–6)

Locations: 2–3 Tier 1 locations Duration: 6 weeks (2 weeks prep, 1 week go-live, 3 weeks stabilization)

Purpose:

Validate integration assumptions
Identify workflow gaps not discovered in testing
Train first cohort of champions who become peer mentors
Establish realistic performance expectations

Wave 2: Expansion (Weeks 7–12)

Locations: 5–8 Tier 1 and high Tier 2 locations Duration: 6 weeks (1 week prep, 1 week staggered go-live, 4 weeks stabilization)

Purpose:

Validate scalability of support model
Test champion training cascade
Stress test vendor support capacity
Refine playbook based on Wave 1 learnings

Wave 3+: Scale (Weeks 13–20)

Locations: Remaining Tier 2 and remediated Tier 3 locations Duration: 8 weeks (1 week prep per cohort, staggered go-lives, 4 weeks stabilization)

Purpose:

Execute refined, proven playbook
Champions from earlier waves mentor new locations
Focus shifts from implementation to optimization

Timeline Per Wave

Wave 1 Detailed Timeline

Week	Activities
Week 1	Integration testing, champion training, staff training scheduling
Week 2	Staff training completion, parallel run prep, go-live readiness review
Week 3	Go-live (stagger across 3 days: Mon/Wed/Fri)
Week 4	Daily check-ins, troubleshooting, workflow adjustments
Week 5	Twice-weekly check-ins, performance tracking begins
Week 6	Wave 1 retrospective, go/no-go decision for Wave 2

Wave 2+ Timeline (Compressed Based on Learnings)

Week	Activities
Week 1	Champion certification, integration validation, staff training
Week 2	Go-live (stagger 2 locations per day)
Weeks 3–4	Stabilization, daily then twice-weekly check-ins
Week 5–6	Performance validation, go/no-go for next wave

Go/No-Go Criteria 🟣

Advance to Next Wave When:

⚠️ Pause Criteria (Red Flags):

Rollback Plan

Tier 1 Issues (Continue with Caution)

Examples: Minor integration bugs, isolated user errors, performance slightly below target

Document issue
Work with vendor for patch/fix
Do not pause rollout

Tier 2 Issues (Pause Wave, Investigate)

Examples: Systematic integration failures at multiple locations, claims processing delays >48 hours, staff unable to complete core tasks

Immediate Actions:

☐ Halt further go-lives for affected wave
☐ Daily war room calls with vendor (30 minutes, 9 AM)
☐ Document affected locations and specific symptoms
☐ Isolate: Is this a vendor issue, integration issue, or training issue?

Resolution Path:

If resolved within 5 business days: Resume rollout
If >5 days: Executive decision to continue investigation or rollback

Tier 3 Issues (Full Rollback)

Examples: Data integrity issues, HIPAA breach, claims submitted incorrectly to payers

Rollback Protocol:

☐ 🟣 Immediately notify executive sponsor and legal/compliance
☐ Disable QuantaPay integration at all affected locations
☐ Revert to pre-QuantaPay workflow (ensure staff retained training on legacy process)
☐ Document all affected claims for manual review and correction
☐ Conduct root cause analysis with vendor before any future rollout
☐ Do not disrupt locations not yet live—they continue operating normally

5. Configuration & Integration (Weeks 2–3)

Step-by-Step Integration by PMS

Dentrix (G7+) Integration 🔵

Time Estimate: 4–6 hours per location

☐ Step 1: Create Dentrix service account with appropriate permissions

User role: Practice Administrator
Enable API access in Dentrix settings (Office Manager > Administrative Setup)

☐ Step 2: Install QuantaPay Dentrix Connector 🔵

Download from QuantaPay implementation portal
Run installer on Dentrix server (requires admin rights)
Enter license key provided by QuantaPay

☐ Step 3: Configure connector settings

Map provider IDs to QuantaPay provider records
Set claim extraction frequency (real-time recommended)
Configure payment posting preferences

☐ Step 4: Test connection

Submit test claim through Dentrix → verify appears in QuantaPay within 5 minutes
Post test payment in QuantaPay → verify reflects in Dentrix within 5 minutes
⚠️ Verify insurance eligibility responses populate correctly

☐ Step 5: Enable production mode (requires QuantaPay sign-off) 🔵

Eaglesoft (21+) Integration 🔵

Time Estimate: 4–6 hours per location

☐ Step 1: Enable Eaglesoft API module

Contact Patterson support to enable API access 🔵
Obtain API credentials from Patterson

☐ Step 2: Configure QuantaPay Eaglesoft bridge

Enter API credentials in QuantaPay admin panel
Map procedure codes (Eaglesoft to ADA)
Configure provider and facility mappings

☐ Step 3: Set data sync parameters

Historical data import: 24 months (overnight batch)
Real-time sync for new claims and payments

☐ Step 4: Test bidirectional data flow

Create new appointment with insurance → verify QuantaPay verifies eligibility
Process claim in Eaglesoft → verify QuantaPay tracks
⚠️ Test write-back of eligibility data to Eaglesoft

☐ Step 5: Production activation 🔵

Open Dental (22+) Integration 🔵

Time Estimate: 3–4 hours per location

☐ Step 1: Enable Open Dental API

Navigate to Setup > Advanced > API
Generate API key with appropriate permissions
⚠️ Ensure "Enable API" checkbox is checked

☐ Step 2: Configure QuantaPay connection

Enter Open Dental API endpoint and key
Test connection (should return practice name)

☐ Step 3: Map data fields

Provider NPI mapping
Insurance plan matching
Fee schedule alignment

☐ Step 4: Enable real-time claim sync

Configure webhook for claim status updates
Set payment posting automation level (manual review vs. auto-post)

☐ Step 5: Test and activate 🔵

Clearinghouse Integration 🔵

Time Estimate: 2–3 hours (one-time)

☐ Step 1: Confirm clearinghouse compatibility

Primary supported: Tesia, DentalXChange, NEA, Availity
⚠️ If using non-standard clearinghouse, confirm with QuantaPay before proceeding

☐ Step 2: Configure EDI connection

Provide clearinghouse submitter ID
Configure SFTP or API credentials
Set payer ID mappings (QuantaPay provides standard payer table)

☐ Step 3: Test claim submission flow

Submit test batch to clearinghouse sandbox
Verify acknowledgment receipt in QuantaPay
Process ERA/835 test file through QuantaPay

Test Environment Setup

Test Environment Validation Checklist

☐ Patient Data

Create 5 test patients with different insurance scenarios:
- Commercial PPO
- Commercial HMO/DHMO
- Medicaid
- Medicare (if applicable)
- Dual-coverage patient

☐ Claim Scenarios to Test

Test Scenario	Expected Result	Pass/Fail
Clean claim submission	Accepted by clearinghouse <5 min	☐
Claim with missing info	Flagged by QuantaPay before submission	☐
Duplicate claim detection	Alert generated, submission blocked	☐
Prior authorization required	PA workflow triggered	☐
ERA/835 processing	Payment auto-posted correctly	☐
Patient eligibility check	Response within 30 seconds	☐
Denial prediction	High-risk claims flagged	☐

☐ Integration Validation

PMS → QuantaPay data sync within 5 minutes
QuantaPay → PMS payment posting accurate to penny
No duplicate records created in either system

Data Migration

Historical Data Ingestion Steps 🔵

Time Estimate: 2–5 days depending on data volume

☐ Step 1: Export historical claims data

24 months minimum recommended
Include: claim ID, DOS, procedure codes, billed amount, paid amount, denial codes, payer ID

☐ Step 2: Export patient and insurance data

Active patients with insurance on file
Insurance plan details and group numbers

☐ Step 3: 🔵 Submit data package to QuantaPay

Use secure file transfer (SFTP provided by QuantaPay)
⚠️ Do not email PHI data

☐ Step 4: 🔵 QuantaPay validates and ingests data

Review data quality report
Address any mapping errors or data gaps

☐ Step 5: Verify historical data in QuantaPay dashboard

Spot-check 10 random claims against PMS records
Verify denial rate calculations match your baseline metrics

Enterprise Configuration 🟣

Standardized Configuration Template

The following settings should be identical across all locations:

Setting Category	Standard Value	Notes
User roles and permissions	[Your standard role matrix]	Define: Admin, Billing Specialist, Billing Manager, Read-Only
Auto-posting thresholds	Auto-post if variance <$5	Higher variances require manual review
Denial categories	[Standard taxonomy]	Use QuantaPay default or customize enterprise-wide
Workflow stages	[Standard pipeline]	Submission → Pending → Paid/Denied → Follow-up → Resolved
Report schedules	Daily/weekly on same cadence	Enables cross-location comparison
Alert thresholds	Denial rate >7%, Claims >45 days	Triggers escalation
SSO configuration	[Your IdP]	Enforce SSO; disable local passwords

Location-Specific Configuration (Allowable Variance)

Setting Category	Local Discretion Allowed	Notes
Provider preferences	Yes	Individual providers may have coding preferences
Fee schedules	Yes	Varies by payer contract per location
Payer mix weighting	Yes	AI model can weight location-specific payer behavior
Working hours	Yes	For scheduling automated processes
Local report recipients	Yes	Office manager and regional manager

Security and HIPAA Compliance

Enterprise HIPAA Checklist 🟣

☐ Business Associate Agreement

BAA executed with QuantaPay ✓ Signed by: _______________ Date: ___
BAA covers all locations under master agreement

☐ Data Encryption

Data encrypted in transit (TLS 1.2+) ✓
Data encrypted at rest (AES-256) ✓
Confirm encryption certificate validity

☐ Access Controls

SSO enforced for all users
Role-based access control configured
Minimum necessary standard applied (users see only their location unless regional+)
MFA enabled for admin accounts

☐ Audit Logging

All PHI access logged and reviewable
Logs retained per your retention policy (minimum 6 years)
Access logs exportable for compliance audits

☐ Data Governance

Data retention period confirmed: _____ years
Data deletion process documented
Data portability confirmed (can export data if contract ends)

☐ Incident Response

QuantaPay breach notification policy reviewed (<24 hours notification)
Internal incident response plan updated to include QuantaPay

☐ Vendor Security Review

SOC 2 Type II report reviewed ✓
Penetration test results reviewed (if available)
Security questionnaire completed

6. Team Training Plan

Train-the-Trainer Model

Overview

Central team trains 1 champion per location → Champions train their local team → Central team provides ongoing support and certification verification.

Benefits:

Scalable across 15–50+ locations
Local champions understand their team's dynamics
Builds internal expertise for ongoing optimization
Reduces vendor dependency for training

Champion Selection Criteria

Champion Responsibilities:

Complete champion certification (4–6 hours)
Deliver role-specific training to all staff at location (4–8 hours)
Serve as first point of contact for staff questions during rollout
Participate in daily/weekly check-ins with central team
Provide feedback to improve training and process
Onboard new hires to QuantaPay (ongoing)

Champion Certification Program 🔵

Delivered By: QuantaPay Training Lead + Central Operations Team Format: Virtual instructor-led + hands-on lab Duration: 6 hours (can be split across 2 days)

Certification Curriculum:

Module	Duration	Content
Module 1: System Overview	45 min	QuantaPay architecture, data flows, key screens
Module 2: Daily Billing Workflow	90 min	Eligibility verification, claim submission, denial management
Module 3: Payment Processing	60 min	ERA processing, auto-posting, reconciliation
Module 4: Reporting & Analytics	45 min	Dashboard navigation, key metrics, report generation
Module 5: Troubleshooting	45 min	Common issues, escalation paths, vendor support process
Module 6: Training Delivery Skills	60 min	How to train adult learners, managing resistance, Q&A techniques

Certification Requirements: ☐ Complete all modules ☐ Pass assessment quiz (80% minimum) ☐ Demonstrate competency in hands-on lab ☐ Receive certification badge 🔵

Role-Specific Training Outlines (For Champions to Deliver)

Dentists/Providers

Training Time: 30 minutes Format: 15-minute live demo + 15-minute Q&A Trainer: Champion (with CDO endorsement messaging)

Content:

What Changes (5 minutes)
- Insurance eligibility now verified in real-time before/during appointment
- Treatment plan estimates will be more accurate (AI-predicted coverage)
- You will see a "coverage confidence score" on the treatment screen
What You Need to Do (10 minutes)
- Review AI-flagged cases before signing off on treatment