Moving from MD Integrations to Lithos, without missing a refill
MD Integrations: clinician and clinical-workflow API for custom-built patient journeys. If you’ve outgrown that setup on states, categories, economics or control, this is how the switch works while your patients keep getting care.
Three things to line up first
Your data export
Request a complete export of charts and care plans from MD Integrations early. Formats and timing are the step that slips in every migration.
Your contract terms
Check notice periods, data-return obligations and any exclusivity language before you commit to dates.
Your patient map
A state-by-state count of active patients and their refill dates. It becomes your cutover schedule.
Three phases, no big bang
Every well-run infrastructure switch follows the same shape, whatever you're moving from.
Parallel-run in the sandbox
Your flows run on Lithos while MD Integrations keeps serving patients. Nothing moves until you've seen intake, visits and fulfillment work end to end.
Records come across
Charts and care plans transfer into Lithos. Our licensed providers review incoming patients and re-establish prescriptions, timed against refill dates so nothing lapses.
Cut over by state
Move one market, watch a full refill cycle, then roll the rest in waves. Patients stay in your app and your brand the whole time.
What changes, and what doesn't
| Item | How it moves | What patients see |
|---|---|---|
| Charts and history | Transferred as data ahead of each wave, checked against a sample export first | Nothing |
| Prescriptions | Re-established by a licensed provider after chart review, not ported | Their next refill arrives on time |
| Patient experience | Doesn’t move: your brand, your funnel, your app | Nothing |
| Pharmacy | Routed to your pharmacy partners or ours, state by state | Shipping updates as before |
Switching from MD Integrations
Can’t find yours? We’re happy to walk through your program.
Will our patients notice anything?
That is the design goal. Patients stay in your app and your brand throughout; what changes is the infrastructure behind it. Cutting over state by state contains any issue to one market.
Do prescriptions transfer automatically?
No. Prescriptions aren’t ported as data. As each patient moves, a licensed provider reviews their chart and re-establishes the prescription, the clinically clean way to switch prescribers, timed so refills aren’t interrupted.
How long does moving off MD Integrations take?
Weeks, not a year. Most teams cut over their first state soon after kickoff, then roll the remaining states at their own pace. Your refill calendar sets the tempo, and we commit to dates on the first call.
What happens to our data if we ever leave Lithos?
The same thing we help you do now, in reverse: you own all patient and operational data and can export it via API at any time.
For the full risk register (refill gaps, prior-auth continuity, patient communications), read our switching guide or how migrations work on Lithos.
Plan your move off MD Integrations
Book a call and we'll map your states, waves and dates with you. You can start parallel-running in the sandbox right away. On the call:
- Your patient map and refill calendar
- Data export and record transfer
- A cutover plan with dates