Amperos — Implementation Playbook (DSO)

Executive Summary

Amperos is a revenue-cycle intelligence platform that automates claim submissions, denial management, and payment posting across fragmented practice management systems. For Dental Service Organizations managing 50+ locations with inconsistent billing workflows, Amperos eliminates manual rework, accelerates cash conversion, and provides real-time visibility into AR aging and payer performance.

DSOs benefit uniquely because they operate at scale where standardization yields exponential ROI: a 2% improvement in claim submission accuracy across 100 locations generates $500K+ in annual recovered revenue. Amperos consolidates billing operations across disparate PMS platforms, allowing DSOs to apply centralized compliance standards while reducing FTE demand in back-office roles.

Full deployment across a 50-100 location DSO: 16 weeks from kickoff to optimization phase.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

Infrastructure readiness:

• Audit all practice management systems in use (Dentrix, Eaglesoft, Open Dental, proprietary builds). Document versions and integration APIs.
• Ensure all locations have minimum 5 Mbps internet connectivity; flag any locations requiring network upgrades.
• Confirm EHR/PMS database schema compatibility with Amperos connectors. Request database read-only access credentials and test connectivity.
• Validate that single sign-on (SSO) infrastructure exists if deploying Amperos dashboard across 10+ locations; otherwise plan OAuth provisioning.

Compliance audit:

• Map current claim submission workflows to HIPAA/HITECH requirements. Document any locations with manual claim transmission (fax, email) that require remediation.
• Confirm that all payer contracts allow API-based claim submission; identify payers requiring EDI X12 837D formatting and schedule pre-setup.

Stakeholder Alignment

Create a cross-functional steering committee:

• DSO Finance Lead (owns AR targets, cash-flow forecasting)
• Chief Clinical Officer or VP of Operations (manages practice autonomy expectations)
• IT Director (oversees system integrations and security)
• Regional Manager (represents frontline practice leadership)

Hold a 90-minute alignment session covering:

• Revenue-cycle pain points at 3-5 representative locations (high-volume, high-denial practices).
• Non-negotiables: Which workflows cannot be automated? (e.g., appeals requiring clinical judgment.)
• Success metrics: Define "winning" as reduced DSO-managed days payable outstanding (DPO) vs. practice-level metrics.
• Resource commitment: Identify 1 FTE per region who will own Amperos adoption; this person must have PMS system knowledge and clinical billing credibility.

Baseline Metrics to Capture

Execute a 2-week baseline measurement period across all locations:

• Claim submission accuracy (% of claims accepted on first submission per payer)
• Days to claim transmission (from patient checkout to payer receipt)
• Denial rate (% of claims denied 30+ days post-submission)
• Days to payment posting (from EOB receipt to patient account credit)
• FTE hours spent on claim rework (denial research, resubmission, manual follow-up)

Use a standardized spreadsheet template sent to all practice billing managers; offer a $500 bonus to locations with complete, audited baseline data. This creates buy-in and ensures clean pre/post comparison.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose 3-5 pilot locations representing:

1. High-volume claims (>500/month) to surface edge cases quickly.
2. Diverse payer mix (at least 2 national carriers, 1-2 regional/regional, 1 state Medicaid program) to stress-test payer integrations.
3. Mixed PMS platforms (if your DSO uses 2+ systems, pilot both).
4. Operational readiness (billing managers with 3+ years tenure; practices with stable staff and no active turnover).
5. Geographic distribution (avoid clustering in one region; test network variability).

Critical: Do NOT pilot at your highest-revenue location. Pilot at high-volume, operationally stable locations where managed chaos won't cascade.

Configuration and Setup

Week 3: Integration build-out

• Amperos technical team provisions PMS connectors to each pilot location's database.
• Validate that claim data flows from PMS → Amperos ingestion pipeline with <2-hour latency.
• Test 50 claims in sandbox mode; ensure patient demographics, insurance eligibility, procedure codes, and fees populate correctly.
• Conduct payer connectivity audit: confirm Amperos can transmit test claims to each pilot location's top 5 payers. Document any payers requiring manual EDI setup or pre-authorization.

Week 4: Workflow mapping and customization

• For each location, document current claim submission process: Who verifies insurance? When is superbilling reviewed? Who follows up on denials?
• Configure Amperos rules engine:
  • Auto-route claims missing insurance verification to manual queue (do not auto-submit).
  • Flag high-denial procedure codes (implants, ortho) for clinical review pre-submission.
  • Auto-hold claims for out-of-network verification if patient's carrier requires pre-auth.
• Set up denial auto-categorization: Amperos learns top 10 denial reasons per location and tags them (missing docs, eligibility issues, coding errors, etc.).

Week 5: Parallel testing

• Run Amperos alongside existing workflows for 1-2 weeks with zero impact on live submission. Every claim submitted by Amperos is resubmitted by practice staff to existing channels.
• Monitor Amperos claim acceptance rates, turnaround times, and denial patterns. Adjust rules and payer configurations as needed.
• Conduct daily 15-minute huddles with pilot practice billing teams to surface friction.

Training Approach

Train in 2 cohorts to avoid practice disruption:

Billing manager bootcamp (4 hours, in-person):

• System navigation: dashboard, queue management, reporting.
• Exception handling: What to do when Amperos holds a claim? How to manually override and why.
• Denial investigation workflow: Use Amperos denial categorization to prioritize rework.
• KPI visibility: Show each manager their location's submission accuracy and days-to-payment trend live.

Practice staff lunch-and-learn (30 min, in-person + async video):

• How Amperos affects their workflow (likely minimal if implemented correctly).
• New requirement: Verify insurance eligibility in PMS before EOD (vs. after claim creation).
• Reassurance: Job roles not changing; back-office headcount decisions made at DSO level, not practice level.

Offer optional 1:1 sessions for locations with staff turnover or existing billing system anxiety.

Scaled Rollout (Weeks 7-16)

Wave Planning

Organize remaining locations into 3 waves (15-20 locations per wave) staggered 3 weeks apart:

Three weeks before each wave, send:

• Customized readiness checklist (PMS admin access, payer contract review, staff training schedule).
• Wave-specific FAQ based on pilot learnings.
• Pre-recorded training videos (reuse bootcamp content with testimonials from pilot locations).

Change Management

Establish a "DSO Revenue-Cycle Operations Center" (1 FTE lead + 1 FTE coordinator):

• Own Amperos roadmap prioritization and payer escalations.
• Conduct weekly check-ins with location billing managers (rotating schedule, 15 min each); track sentiment and early wins.
• Publish a monthly "Amperos Operations Bulletin" with:
  • Network-wide denial trends (top 5 denial codes