TL;DR: Signing an EHR contract is not going live. Our founder signed in January and still could not see a patient nine weeks later: self-guided setup, video-library training, and paid help tiers turned the practice into its own implementation team. The test of onboarding is simple - can the team complete a real visit? Doctors deserve to know that answer before they sign.
A practice can sign for a new EHR and still be unable to see a patient in it weeks later. Our founder lived that gap. He signed up for a system used by colleagues in January. Nine weeks later, he still could not see a patient in it.
The hardest part was not learning where to click. It was discovering how much of the setup had become the practice's job.
Signing is not going live
A sales conversation can make a new system feel close. Then implementation begins: scheduling has to be configured, charting has to work, staff need to learn the steps, and someone has to answer questions when a setup decision blocks the next one.
In our founder's experience, the plan included self-guided setup. Scheduling instruction came through a video library. Live help had to be booked around an implementation consultant's other clients, and more individual training meant upgrading the package. The issue was not that videos are useless. It was that a practice trying to open its doors needed a working setup and a person who could help finish it.
Every unfinished piece had a cost in attention. The clinician was not only choosing software. He was becoming the project manager for bringing it to life.
What practices expect vs. what implementation often delivers
| What a practice expects | What implementation too often delivers |
|---|---|
| Signing means going live soon | A setup packet and a video library |
| Help when the team is stuck | Calls scheduled around other clients; more hours cost more |
| A working system | An active account and homework |
| Timeline known before signing | Timelines disclosed in welcome materials |
A product is not ready because the account is active
A login is a start, not a launch. The useful test is simpler: Can the practice schedule and complete a real visit using the workflow it agreed to buy? Can staff get an answer when they are stuck, without being sent through another lesson? If the answer is no, the implementation is still underway, whatever the account status says.
That gap matters most to a small practice. The same person seeing patients may also be deciding how the schedule, notes, orders, and follow-up should work. A long setup does not only delay the software. It competes with the care and operations the software was meant to support.
What the experience changed for us
Thyra grew out of the decision not to accept that gap as normal. Building an EHR from within a working clinical practice changes the question we ask: not "Was onboarding completed?" but "Can the team use the system to care for a patient?"
That is a standard, not a promise that every practice can switch overnight. Every practice has its own data, staff, billing needs, and dependencies. A responsible rollout has to make those visible early, put a real person on the hard parts, and say plainly what remains before a practice is ready to rely on the system.
Doctors should know what it will take to see the first patient before they sign, not find out after. That is where EHR onboarding should begin.
Frequently asked questions
How long should EHR onboarding take for a small practice?
It depends on data migration and billing needs, but a small practice should know the realistic timeline before signing, with a named person accountable for the hard parts. Weeks of self-guided setup with video-only support is a warning sign, not a norm.
What should an EHR vendor provide during onboarding?
A clear go-live plan agreed before signature, human help that is not metered by package tier, and a plain definition of ready: the practice can schedule and complete a real visit in the system.
How is Thyra's approach different?
Thyra was built inside a working clinical practice, so readiness is measured by whether the team can care for a patient, not whether onboarding checklists were completed.
