Skip to main content
Medplum Integration

Turn Medplum Appointments Into Confirmed Visits

Two‑way SMS and AI voice confirmations that write back to Medplum as native FHIR resources, so your staff stops chasing no‑shows. Setup is one command.

npx @visitconfirmed/medplum

Read the five‑minute setup walkthrough → View on GitHub →

BAA available
PHI-safe defaults
Consent + quiet hours
15–30% fewer no-shows within 30 days

Medplum Handles the Data. VisitConfirmed Handles the Follow-Through.

Medplum gives modern health tech teams a powerful FHIR-native backend. But appointment engagement still often happens through manual calls, fragmented reminder tools, or workflows that aren't tightly connected to the patient record. We've written more about why appointment reminders aren't appointment confirmations and what it takes to close the loop.

Medplum
  • FHIR source of truth
  • Patient and appointment data
  • Workflows and infrastructure
VisitConfirmed
  • Outreach automation
  • Two-way SMS confirmations
  • AI voice fallback
  • Rescheduling workflows
  • Human escalation

Built to Fit the Way Medplum Teams Already Work

Four steps from appointment creation to confirmed visit.

01

Medplum detects an upcoming appointment

A FHIR Subscription installed by npx notifies VisitConfirmed when an Appointment is created or updated.

02

VisitConfirmed reaches out automatically

VisitConfirmed reaches each patient over SMS and AI voice to confirm the visit, reschedule if needed, or flag at-risk patients before the slot is lost.

03

The workflow adapts in real time

No answer? Retry. Needs help? Escalate. Wants to reschedule? Route into the right next step.

04

Results sync back to Medplum

Confirmations, reschedules, and escalations land in Medplum as Appointment updates, Communication records, and Tasks. Your team always has the latest state.

SMS and voice work together. Patients who don't reply to a text get a follow-up phone call. The AI speaks naturally.

Built on FHIR Subscriptions

VisitConfirmed runs alongside Medplum, not in place of it. Medplum stays the source of truth; VisitConfirmed handles the outreach.

WHAT npx @visitconfirmed/medplum INSTALLS

ClientApplication

Scoped credentials VisitConfirmed uses to read appointments and write back outcomes.

AccessPolicy

Least-privilege scope: only the FHIR resources needed for confirmation workflows.

Subscription

Notifies VisitConfirmed when Appointments are created or updated, so outreach fires on real events.

Medplum
VisitConfirmed
SMS / AI Voice
Medplum

Subscription fires → VisitConfirmed reaches out → results write back as FHIR resources

Appointment Patient Communication Task FHIR Subscription AccessPolicy ClientApplication

VisitConfirmed reads appointment and patient context from Medplum, runs the outreach over SMS and AI voice, and writes results back as Communication, Appointment, and Task resources.

Setup Is One Command. The Iceberg Underneath Is Not.

Run one command. Get a full engagement engine underneath.

What you see

One command provisions a ClientApplication, AccessPolicy, and Subscription in your Medplum project.

What VisitConfirmed handles
  • AI voice conversations that handle real patient responses
  • Retry logic across channels (SMS → voice → escalation)
  • No-answer vs. wrong number vs. voicemail vs. partial confirmation
  • Timezone-aware quiet hours and consent management
  • Idempotent FHIR write-back that respects human overrides
  • Reschedules, cancellations, language preferences, caregiver routing

What Your Team Gets

Higher Show Rates

AI-driven confirmations help recover visits that would otherwise become no-shows.

Less Manual Work

Free operations staff from repetitive reminder calls and routine follow-up.

Early Risk Detection

Identify patients who are unresponsive or likely to miss before the slot is lost.

FHIR-Aligned Workflow

Keep Medplum as the source of truth while syncing outcomes back into the patient workflow.

Faster Implementation

Use lightweight integration patterns instead of rebuilding engagement tools in-house.

Human-in-the-Loop

Automation handles routine work while your staff stays in control of exceptions.

Built for Medplum-Based Health Tech Teams

If your team uses Medplum and missed appointments hurt revenue, utilization, or patient outcomes, VisitConfirmed is designed for you.

Care coordination platforms

Teams managing multi-step care journeys where every appointment matters.

Virtual care & telehealth companies

Providers running high-volume video visits who need reliable attendance.

Operations teams managing high-value appointments

Where a missed visit means lost revenue, delayed care, or wasted capacity.

Make Medplum More Actionable

One command turns appointment data into completed visits.

Frequently Asked Questions

No. Medplum stays your FHIR source of truth. VisitConfirmed runs alongside and handles patient outreach.
Running npx @visitconfirmed/medplum installs a ClientApplication, an AccessPolicy, and a FHIR Subscription in your Medplum project. The Subscription notifies VisitConfirmed when Appointments are created or updated; outcomes write back as Communication, Appointment, and Task resources.
Yes. SMS goes out first; if a patient doesn't reply, an AI voice call follows. Retries and human escalation are built in.
Outcomes write back as Communication records (the conversation thread), Appointment updates (status changes and time changes on reschedules), and Tasks (escalations for your care team).
Engineering-led digital health and care coordination teams using Medplum who want to reduce no-shows without building a full patient engagement system from scratch.