Integration · Medplum
Recupra + Medplum: outreach agents on top of your own FHIR server.
Medplum is a FHIR server you control, hosted or self-hosted. Recupra connects to whichever server URL you run, reads the Slot inventory your build publishes, and writes Appointments back through the same API.
No call. No credit card. Plug-and-play setup in 5 minutes.
The integration
How Recupra works with Medplum
Medplum is the developer-first choice for teams building their own clinical application on a compliant FHIR backend. Clinics running it usually have engineering in-house and are wary of tools that need a data export.
Recupra needs none. It authenticates as an OAuth client against your Medplum server, reads Patient, Practitioner, Appointment, and Slot, and writes appointments back. If you self-host, you point Recupra at your own server URL rather than the hosted one.
What frees a slot in Medplum
- Cancelled
- No-show (optional)
A status without a label triggers a recovery call by default. The ones marked optional stay off until you turn them on.
Medplum at a glance
- Who runs it
- Teams who built their own patient experience on open-source infrastructure
- Open times
- Read from the vendor's open-slot API
- Cancellation reaches us
- Daily sweep, up to 24 hours
- Authentication
- OAuth 2.0 client credentials
Side by side
You built the platform. Recupra is the headcount you did not want to hire.
What a Medplum team already has
Medplum users are builders. They picked open-source, FHIR-native infrastructure precisely so they could own the patient experience rather than accept a vendor's, and they usually have bots, subscriptions, and their own scheduling logic running already.
Anything Recupra does could, in principle, be built on that foundation. Medplum would not stop you.
Why teams do not build this one
The build is not the scheduling logic, which you have. It is the voice agent: telephony, latency, interruption handling, a model that stays inside a clinical guardrail, and the operational work of tuning it against real calls every week.
That is a product, not a feature. Recupra plugs into the FHIR resources you already maintain and leaves the rest of your stack exactly as it is.
Vocabulary
Recupra speaks Medplum
Your agent uses the words your staff already use, so nothing on a call sounds translated.
- Schedule → Provider calendar
- The FHIR resource Recupra reads availability against.
- Slot → Open time
- Read directly, so an offer matches what your own app would show.
- Appointment → Booking
- Written back as FHIR, so your app sees it without a sync step.
- Bot → Your automation
- Whatever you already run stays untouched beside Recupra.
Setup
Connecting Medplum takes one sitting
- 01
Create a client application in Medplum
Medplum issues a client ID and secret from its admin console. Recupra uses them for machine-to-machine access and never asks for a clinician's login.
- 02
Give Recupra your server URL
Use api.medplum.com for the hosted service, or your own host if you self-host. Recupra treats both identically, so a self-hosted deployment is not a special case.
- 03
Confirm the access policy
Recupra reads Patient, Practitioner, Appointment, and Slot, and writes Appointment. Scope the client to exactly that if your build restricts access by resource type.
On the phone
The call your own app cannot make
A patient stops responding in-app. Notifications keep landing and nothing changes, because the patient is not opening the app.
- Agent
Hi, this is the clinic checking in. It has been a while since your last visit and I wanted to see how you are doing.
- Patient
I have been meaning to book, honestly. I keep missing the reminders.
- Agent
Then let me just book it with you now. There is Tuesday at ten or Wednesday at four thirty.
- Agent
Tuesday at ten. It will show up in the app straight away.
The agents
Every agent runs on Medplum
The roster does not change per EHR. Whichever system you run, you choose which of these to turn on.
Waitlist Agent
A slot frees up and the agent calls the best-matched patient from your list, then books them in.
No-Show Agent
A patient misses a visit and the agent calls inside your window, finds out why, and reschedules.
Reminder Agent
Upcoming visits are confirmed on the channel each patient answers, so the miss surfaces early.
Intake Agent
A new inquiry gets a call back in minutes, qualified and booked into a real opening.
Follow-Up Agent
A patient who leaves without the next visit in their plan booked is called while the plan is still open.
Reactivation Agent
Dormant patients get a warm check-in calibrated to their care history, not a sales pitch.
Admin Agent
Reschedules, hours, and routine questions are resolved on the inbound line without staff.
The platform
Outcome-based, HIPAA-compliant, no migration
Recupra runs a diagnostic on your real clinic data, shows where revenue is leaking in dollars, and lets you activate the agents you want, paying only when they recover real revenue. See the outcome-based pricing, read how it works, or compare every EHR integration.
Medplum stays the system of record. Recupra never migrates your data.
Medplum FAQ
Frequently asked questions
Does Recupra work with self-hosted Medplum?
Yes. You give Recupra your own server URL instead of the hosted one. Nothing else about the integration changes.
What FHIR resources does Recupra need?
Read access to Patient, Practitioner, Appointment, and Slot, and write access to Appointment. Scope the client application to that set if your access policy is restrictive.
Does Recupra move any data out of Medplum?
No migration happens. Medplum stays the system of record, and Recupra reads what it needs for an outreach decision and writes the resulting appointment back.
See what Recupra recovers on Medplum.
Connect your EHR and Recupra shows you exactly where revenue is leaking, on your real data. No call, no credit card.