14-day go-live, documented.
Most RCM implementations take 90 days because they are not implementations, they are sequential ticket queues with handoffs between strangers. We compressed every step into parallel and named a senior partner who owns the 14-day SLA in writing. Four phases. Four documented milestones. One implementation lead who does not rotate. A parallel-run safety net for the first 14 days post go-live. Senior partner sign-off on every gate.
Four phases. Documented milestones.
The 14-day SLA is real because every step is mapped to a calendar day with a named owner, a defined success criterion, and a sign-off gate. The chart to the right shows the percentage of total implementation effort allocated to each phase. EHR connect and payer setup run in parallel because they have different dependency chains. Training kicks off on Day 4 in parallel with payer setup so role completion lands by Day 11. First cycle starts Day 12 and the go-live gate fires on Day 14.
If a milestone misses for a reason inside our control, the SLA recovery is also documented: extended parallel run, expedited senior-partner escalation, and the first month of services at no charge. The accountability is in writing.
Seven capabilities. From kickoff to stable production.
Each capability runs end-to-end across the 14-day SLA plus the 14-day post go-live hyper-care window. Every gate is owned by the named implementation lead with senior-partner sign-off documented.
Day 1 connection.
Sandbox connection live on Day 1 against Epic, Cerner, athenahealth, eClinicalWorks, Greenway, NextGen, Kareo, AdvancedMD, RXNT, CentralReach. Read-only extract validates demographics, encounters, charges, claims, payments, denials. Success criteria: clean extract, zero schema errors.
Live connection matrix.
Every active payer in your mix tracked live: clearinghouse routing, 270/271 endpoint, 837 submission test, 835 ERA reception, denial-code mapping, portal credentials. The matrix is a shared document you watch in real time. No black box.
Same-day execution.
BAA chain between ASP-RCM, your covered entity, and any required EHR or clearinghouse intermediary. Standard templates with established carriers. Same-business-day execution on the standard path. Custom legal redlines tracked separately so they never block the 14-day SLA.
Role-based access, audited.
Specialist accounts provisioned by role: front-office, clinician, billing, supervisor, client director. Role-based access enforced at every screen. Credential OS multi-tenant RBAC backs every credentialing screen. Every login and access change is logged for SOC 2 and HIPAA evidence.
Three role tracks, recorded.
Front-office, clinician, billing-team. Each track has a live session, a recorded session, a written runbook, and a knowledge-check quiz. 100 percent role completion required before parallel run starts. Refresher modules ship monthly post go-live. Training is not a one-time event.
Safety net, in writing.
Days 12-14 plus 14 days post go-live: claims flow through both your existing system and ASP-RCM simultaneously. Daily reconciliation. Any divergence investigated within 4 business hours. Shadow re-promotable to primary inside 1 business hour if a systemic issue surfaces.
Two weeks post go-live.
Daily steering call. Same-day variance response. Senior partner on every escalation. First-month KPI review against baseline: cash, denials, AR aging, first-pass clean-claim rate. Exit gate is a documented stabilization scorecard with client director sign-off before standard QBR cadence begins.
Day-by-day. From kickoff to go-live.
Every phase is a defined gate with named owner, success criterion, and senior-partner sign-off. The phases below are how the 14-day SLA actually executes in calendar time.
EHR connect.
Sandbox connection on Day 1. BAA chain executes in parallel. Read-only extract on Day 2 validates demographics, encounters, charges, claims, payments, denials end-to-end. Schema verification gate fires on Day 3. Sign-off required to proceed.
Payer setup.
Every active payer: clearinghouse routing, 270/271 endpoint, 837 submission test, 835 ERA reception, denial-code mapping, portal credentials. Live connection matrix tracks stage per payer. Sign-off requires end-to-end test transactions on every payer with non-zero claim volume.
Training.
Three role tracks run in parallel: front-office, clinician, billing-team. Live sessions, recorded sessions, written runbooks, knowledge-check quizzes. Sign-off requires 100 percent role completion before the parallel run starts on Day 12.
First cycle.
Parallel run with daily reconciliation. Day 14 go-live gate: variance below threshold and steering committee sign-off. If variance is above threshold, parallel run extends by phases until resolved. Hyper-care window starts on the day of go-live.
Documented outcomes from 14-day implementation.
Across the active book. Anonymized; individual implementations vary by EHR maturity, payer mix complexity, and steering committee availability.
Frequently asked questions: Implementation.
Why a 14-day SLA when most RCM implementations take 90 days?
What does Day 1-3 EHR connect actually involve?
What does Day 4-7 payer setup involve?
What does Day 8-11 training involve?
What does Day 12-14 first cycle involve?
What is the parallel-run safety net?
Who is the dedicated implementation lead?
What does post-go-live hyper-care look like?
Implementation compounds with the stack.
A clean 14-day implementation only matters if the production engine on the other side is real. The credentialing platform, the AR engine, and the SLA matrix are the three production guarantees post go-live.
Credentialing at go-live.
HIPAA-hardened multi-tenant credentialing with PHI-at-rest encryption and per-payer enrollment tracking. Credentialing data extracts on Day 1 and feeds the AR engine’s upstream-root-cause flag from the first production cycle.
Production from Day 14.
AR triage by recoverable dollars, predicted call outcome, senior auto-routing. The AR engine runs from the first cash cycle. Specialists arrive at accounts with pre-fetched context already loaded so the first week of production is not the first week of learning.
Production guarantees.
99.9 percent uptime SLA on every production service. Quarterly DR drills. Daily encrypted backups. Status page. The implementation handoff into the production SLA is documented in the same engagement contract as the 14-day go-live.
Get the implementation playbook. Read before you sign.
The full 14-day playbook: phase-by-phase scope, named owner per gate, success criteria, SLA recovery terms, hyper-care exit scorecard, BAA chain template. Eight pages. Read it before you sign anything. A senior partner on the walkthrough call.