Switching · Implementation
Four weeks, and you keep seeing patients.
Implementation is not a project you staff. It is four weeks of configuration, data migration and parallel running, with your programs operating normally throughout.
No implementation fee on Solo or Group Practice. Larger migrations with historical data are quoted separately.
What's included
Six things you no longer buy separately.
Included
ConfigurationPrograms, levels of care, note types, roles and permissions set up against how you actually operate.
Included
Data migrationActive patients, demographics, insurance, active treatment plans and open claims brought across.
Included
Payer enrollmentEDI enrollment per payer and per billing entity, started on day one because it is the longest pole.
Included
TrainingRole-based sessions — clinicians, front desk, billing, leadership — recorded so new hires get the same thing.
Included
Parallel runningBoth systems live until your team trusts the new one. You decide when to switch off, not us.
Included
A named personOne implementation contact throughout, not a ticket queue.
The four weeks
Who does what, week by week.
Programs, levels of care, note types, roles and permissions built with you.
Decide who makes configuration calls and give us your payer list.
Active patients, insurance, treatment plans and open claims imported and reconciled.
Spot-check charts against your current system and tell us what looks wrong.
Role-based sessions for clinicians, front desk, billing and leadership.
Attendance in week three is the single best predictor of a smooth go-live.
Both systems live. New work happens in ours; the old one stays available.
Book, chart and bill in the new system with the old one as a safety net.
We confirm claims and remittances are flowing before anything is decommissioned.
Cancel the systems you are retiring once you are confident, not on a date we set.
Before you commit
Five things to check first.
We would rather you find these now than three weeks into a cutover. Every one of them has delayed somebody's go-live.
Print this, or bring it to the walkthrough and we will go through it with you.
Active patients always. Whether closed episodes migrate is a cost and effort decision worth making early.
Implementation goes materially faster with one person on your side who can make configuration decisions.
Enrollment timelines vary widely, and the slowest payer sets your go-live date.
Notice periods on your existing systems should be planned around the parallel period, not before it.
Training lands best in the week before go-live, not a month ahead when nobody has a reason to remember it.
Operations
Admissions & intake
An embeddable pre-screening form on your site feeds a lead queue.
Read more →Revenue cycle
Claim scrubbing
Validation runs before the claim leaves, highlights the exact field that will get it kicked back, and says why in plain language — not a rejection code you have to look up.
Read more →Audit & compliance
Roles & permissions
A tech, a biller, a clinical director, and an owner should not see the same chart.
Read more →The longest pole is not you
Payer EDI enrollment is the slowest part of every implementation, and it is entirely outside both our control. That is why it starts on day one rather than after configuration is finished.
Bring your current contracts and renewal dates to a walkthrough and we will map the timeline against them.
Get started
Start today, or take a look first.
Create an account in minutes. Or book a 30-minute walkthrough.