EHR HAND-OFF · HOW IT IS BUILT
Where the chart begins: defining the hand-off stage
Every practice has a moment when a person stops being an inquiry and becomes a patient. Most practices have never named it, which is why the intake system and the EHR disagree about who is active and the front desk types the same details twice. Here is how the moment is defined, and what crosses it.
THE SHORT ANSWER
Why the moment needs a name
Without a defined hand-off, the same person is half in two systems. The intake tool thinks they are an inquiry because nobody closed the card. The EHR thinks they are a patient because someone made a chart. The reminder for the first session goes out from one, the intake paperwork from the other, and when the person calls with a question the front desk checks both. Naming the stage fixes this by making the transition an event: before it, the intake system owns the relationship; after it, the EHR does, and the intake system keeps only what it needs to run reminders and reactivation.
What is in the record that crosses
- Contact details and the preferred language, so the chart is created in the right language the first time.
- The inquiry source, so the referral report and the chart agree about where the person came from.
- The messaging consent record: timestamp, text version, language. The practice will want this later and it belongs with the person.
- The appointment: date, time, clinician, location.
- The intake form answers, exactly as submitted, in the language they were submitted in.
That record is exportable on every plan in a structured format the front desk can work from. Nothing is re-typed from a text thread, because the thread was never where the information lived; the form was.
The therapy example: SimplePractice
Most therapy practices we talk to run SimplePractice, which is a good EHR with a genuinely good Spanish client portal. It does not publish a write API. That means no vendor can honestly claim to push a new client into it automatically, and any vendor that does is describing a workaround they would rather not explain. So the hand-off for a SimplePractice practice is the record above, created once by the coordinator at the consult-booked stage, after which the portal takes over and does what it does well. That is a fifteen-second task done properly rather than a five-minute one done from three windows.
Where integration is real, it is scoped
Some practice-management systems, particularly in dental, expose supported connections. Where they do, integration work at the Group tier defines exactly what moves, in which direction, and what stays behind, and that scope is confirmed in writing before the practice commits. The reason for the ceremony is the next section.
The boundary
The platform we build on publishes what its HIPAA module covers. Third-party connections, including EHR connectors, are not on the published list. We treat every integration as outside the BAA boundary until the provider says otherwise in writing, which means patient information is not routed through one on assumption. The hand-off is designed so that this is not a limitation: the intake system holds the minimum, the clinical record lives in the EHR under the practice’s own agreement with that vendor, and the crossing is a deliberate act rather than a background sync nobody can describe.
A vendor who says “we integrate with everything” is either describing a Zapier recipe or has not read their platform’s BAA. Ask which.
What stays behind, and for how long
After the hand-off the intake system keeps the contact, the language tag, the consent record, and the appointment history, because reminders, rescheduling, and reactivation run on those. It does not keep clinical notes, because it never had them. Retention on messages, call recordings, and transcripts is a setting agreed at onboarding rather than a default of forever.
Questions we get asked about this
What is in the hand-off record?
Contact details and language, the inquiry source, the messaging consent record, the appointment, and the intake form answers as submitted. It is exportable on every plan and the chart is created from it once.
Do you write into SimplePractice or TherapyNotes?
No. Neither publishes a write API, and we will not claim a connection that does not exist. The hand-off for those practices is the record above, created by the coordinator at the consult-booked stage.
When is integration real?
Where a system exposes a supported connection, mostly in dental. Integration work at the Group tier defines what moves and in which direction, confirmed in writing before the practice commits.
Is an integration covered by the BAA?
The platform does not state that third-party connections are inside its HIPAA module coverage, so we treat every integration as outside the boundary and do not route patient information through one on assumption.
Related
Tell us which system is on the other side.
Name your EHR on a 30-minute consultation and get a plain answer about what moves, what does not, and what it costs.