A telehealth platform or EHR migration should preserve responsibility for every open patient case, prescription, and refill request. Moving software does not by itself transfer prescribing authority, move a prescription between pharmacies, or create a new clinician-patient relationship. Those questions need the responsible clinical and pharmacy teams.
Start by separating the technology change from any change in medical group, pharmacy, or payment provider. The more relationships that change together, the more explicit the handoff plan must become.
Define what is changing
Write a scope statement that names the source and destination systems and every participating entity. State whether clinicians remain the same, whether pharmacies remain the same, and which records will move.
Assign a migration lead, a clinical lead, a pharmacy contact, a payments lead, and a patient-support owner. One person can hold several roles in a small operation, but the responsibilities should still be documented separately.
Use the data export checklist to establish the record scope. Do not schedule a final cutover around an untested assumption that all required history will arrive in a usable format.
Create an EHR migration checklist of open work
Classify patients by the work that remains, not just by an account status such as “active.” Someone with a completed order has a different transition need from someone awaiting a clinician response.
| Open item | Main transition risk | Required handoff |
|---|---|---|
| Incomplete intake | Patient must restart or loses answers | Secure continuation plan |
| Awaiting clinical review | Case disappears between queues | Named reviewing team |
| Awaiting patient information | Outstanding request is forgotten | Message and follow-up history |
| Prescription sent | Destination assumes it was not sent | Pharmacy acknowledgment and reference |
| Refill requested | Duplicate or missed review | Current clinical status and owner |
| Shipped order | Support loses visibility | Tracking and delivery exception access |
This inventory is an operational recommendation, not a determination of whether any individual prescription may legally be transferred or renewed.
Agree clinical and pharmacy responsibilities
If the medical group changes, the receiving team should determine what it needs before assuming care. That may include record review, patient communication, or an additional encounter. Do not promise that every patient can continue automatically.
HHS advises verifying patient location and addressing applicable cross-state licensure. A destination platform’s national availability does not resolve whether a particular clinician can deliver the intended service to a particular patient.
If a pharmacy changes, involve the pharmacists and prescribers in determining the correct process. Verify licensing through the relevant boards; FDA provides a state-board lookup resource. Platform routing rules should support the authorized process, not substitute for it.
Choose cutover cohorts around operational risk
Start with a manageable set of cases whose requirements are understood. Keep unresolved or time-sensitive cases in an explicitly owned queue until their transition is ready. Do not hide them by excluding them from the migration dashboard.
For each cohort, establish:
- The date and time the destination becomes the working system.
- Which team monitors the source queue afterward.
- How late-arriving messages and pharmacy updates are handled.
- Which billing system owns the next service period.
- Who can stop the rollout if records or workflows do not reconcile.
Use the subscription migration plan for billing boundaries. A clinical transition and a billing transition may need different schedules.
Communicate what patients need to do
Explain the practical changes: the login address, support contact, access to past information, and any action required before the next service. Avoid vague messages that suggest nothing changes when the provider relationship or payment process is different.
Keep sensitive details out of broad email subject lines and routine notifications. Direct patients to an authenticated channel for information that requires it. Give support staff an approved explanation for common scenarios, including a patient who cannot access the new portal.
Communications should also distinguish a technology problem from a clinical question. Support can help with account access; the clinical team should handle concerns about treatment continuity or the suitability of a refill.
Reconcile before retiring the old platform
Compare source and destination open-case counts, then investigate differences at record level. Check that every unresolved item has an owner, deadline, and accessible history. Verify that pharmacy acknowledgments and patient messages continue to reach the right team.
Use the refill workflow guide to test recurring care after cutover. Keep a documented recovery plan, but do not blindly restore an old database over new clinical actions. Recovery must account for what happened after the transition began.
The provider-network evaluation guide can help confirm that the receiving team has the capacity and escalation support the plan assumes.
Frequently asked questions
Do active prescriptions automatically move with patient records?
No. Historical data and prescription handling are separate. The applicable prescriber, pharmacist, and legal requirements determine what action is needed for each situation.
Can we migrate everyone on the same day?
That may be possible for a limited change, but it should follow testing and a case-level readiness assessment. A single date is not evidence that every patient is ready.
When can the old platform be closed?
After open work is reconciled, required history remains available, and contractual and record-retention obligations are addressed. Keep a named owner for late-arriving information during the transition.
What should stop a rollout?
Unexplained missing records, ambiguous clinical responsibility, duplicate billing risk, or lost pharmacy updates are reasons to pause expansion and resolve the affected workflow before moving additional cases.
