HomeHow it works
From first look to fully live, without the leap of faith.
You never bet the practice on an unproven system. You drive Orion on your own workflows, run it beside your current EHR with real patients, and switch only at a checkpoint you control.
Demonstration: the five weeks after your go-ahead. Setup, training, live pilot, data and billing workstreams advance week by week, with go/no-go checkpoints at weeks 3 and 5, to fully live about 35 days after the Test Drive.
Fully live about 35 days after the Test Drive, and every step before week 5 is reversible.
Your dates come from your go-ahead call.The journey
Three stages. Your legacy system stays live until you switch.
Each stage ends with something you can judge: a sandbox you've driven, claims you've watched go out, a checklist your team has finished. Nothing moves until the stage before it earned it.
1
Test Drive
Your Switch Navigator builds your real workflows in a private sandbox: your forms, fee schedules and locations, not a canned demo. Your team drives the software.
- Put a real patient through by around day 7: encouraged, never required
- $1,500, credited back in full when you switch
2
Run it live, alongside
A few providers run Orion next to your current EHR. Your old system stays the system of record, so billing and care never skip a beat.
- Zero records migrated to start
- Real patients from the first week, at your pace
3
Switch on your terms
Only when you say go, at the second of two checkpoints. Data migrates in stages with a final backfill, so nothing is left behind.
- Staged migration, then a final backfill at cutover
- A clean exit available the whole way
Your side of the work
Four roles, four short checklists.
Your team doesn't sit through a course. Each role has a brief checklist of the things that matter in their day: finishing it is the training.
Sets the go/no-go criteria at kickoff, then makes both checkpoint calls.
Runs a day of the schedule in the sandbox before a real patient ever arrives.
Sees eligibility land at booking and a claim go out from a signed note.
The moment most clinicians decide: a note drafted while they treat, signed in under two minutes.
The checklists exist to earn a verdict, not to tick boxes. They're built from the moments clinics tell us decided it for them, which is why finishing them and reaching a checkpoint are the same event.
Two go/no-go checkpoints
Two decisions, both yours.
A switch shouldn't hinge on a feeling in week five. It hinges on two moments where every role has done the work and can say plainly whether they're comfortable.
1
Is every role comfortable?
Each role's checklist is done, in the sandbox and on real visits. You're judging comfort with the daily work, not a feature list.
- Providers have signed notes Aurora drafted
- Front desk has run a full day of the schedule
- Billing has watched claims go out and payments post
2
Do you want to switch?
Config is signed off, the pilot has run a full schedule, and the migration plan is on the table. This is the only moment anything migrates.
- Every provider has worked a pilot day end to end
- Test imports verified against your own records
- A dated cutover plan you approve, or don't
Neither checkpoint is a sales call. If a role isn't comfortable, the answer is another week, or a clean exit: the Test Drive fee comes back in full.
The data plan
What moves, and when.
Migration is staged and verifiable, not a weekend leap. Nothing moves before checkpoint 2.
A test import lands in the sandbox and you verify it against your own records before anything is scheduled for real.
- Field mapping reviewed with your team
- Test import of demographics and insurance
- Sample notes and documents spot-checked
Records move in batches while your legacy system is still the system of record, so nothing depends on a single overnight cutover.
- Demographics and insurance
- Active plans of care
- Future appointments
- Historical notes, in full, searchable
- Documents and attachments
- Open A/R and claims, reconciled
One last pass catches everything written since the staged load. Then Orion becomes the system of record, and only then.
- Everything charted since the staged load
- A full note archive as PDF, belt and braces
- Your legacy system stays readable throughout
Nothing migrates before you say go. The dry run is verified by you, the staged load is reversible, and the backfill happens on the day you pick. If you stop at either checkpoint, no record has moved.
Questions, answered
How it works, FAQ.
The four questions every clinic asks on the first call.
How does Orion work?
Three stages. A guided Test Drive where a specialist builds your real workflows in a sandbox and your team drives them; a parallel pilot where Orion runs beside your current EHR, which stays the system of record; and a staged switch that happens only when you give the go-ahead at the second checkpoint. Most practices are fully live about 35 days after the Test Drive.
How long until I'm live on Orion?
Most practices are fully live about 35 days after the Test Drive. A real patient can go through Orion as early as day 7, during the Test Drive itself: encouraged, never required. Your legacy system stays the system of record until you switch.
Do I need downtime to switch?
No. Orion runs alongside your current EHR, and nothing migrates until you decide at checkpoint 2. There's no dark weekend, no batch to reconcile on Monday, and a clean exit available the whole way.
What is the Test Drive?
A guided trial in a safe, non-production sandbox where your team drives the real software with dummy data while your Switch Navigator walks each role through it. No migration. It's $1,500, credited back in full when you switch, and if you stop, you keep the Go-Live Readiness Pack.
Book a live demo
See the whole thing on your own workflows.
See it on a real PT workflow, or start with a guided Test Drive in a safe sandbox: $1,500, credited back in full when you switch.