Medplum
medplum · Developer platforms
GitHub stars
2,714Stats updated
What is Medplum?
Medplum gives healthcare teams a standards-based application foundation instead of requiring them to assemble identity, clinical storage, workflow logic, and user-interface primitives separately. Its FHIR API and TypeScript SDKs support custom products, while the provider app and Bots cover common operational and server-side needs.
Medplum is a developer platform for building healthcare applications on FHIR. It provides authentication, a clinical data repository, APIs, SDKs, an app, and server-side bots for health-data workflows.
Core capabilities
- Store and query clinical data through a FHIR-native repository
- Authenticate users with OAuth, OpenID, and SMART-on-FHIR
- Build workflows with TypeScript SDKs, React components, and server-side Bots
A FHIR-native application foundation
The clinical data repository exposes healthcare records through FHIR APIs rather than hiding them behind a product-specific model. Authentication, access controls, typed SDKs, GraphQL support, and prebuilt React components give application teams several layers at which to build.
- FHIR
- SMART-on-FHIR
- TypeScript
- React
Workflow logic and healthcare integrations
Medplum Bots run application logic on the server, while the provider app offers an out-of-the-box clinical interface. Official integration guidance covers HL7, FHIRcast, labs, prescribing, devices, and common clinical workflows, so teams can connect custom software to real care operations.
- Bots
- HL7
- FHIRcast
- clinical workflows
Where it fits
Use cases
- 01
Build a custom healthcare application
Use the FHIR repository, typed SDKs, React components, and authentication services as a shared foundation for patient, clinician, or operations software without creating a proprietary clinical data model first.
- 02
Run clinical workflows on structured records
Represent patients, encounters, observations, requests, and other healthcare concepts as FHIR resources, then use Bots and APIs to automate intake, messaging, charting, referrals, and related operational steps.
- 03
Connect an application to healthcare systems
Use SMART-on-FHIR, HL7, FHIRcast, lab, prescribing, and device integration paths to exchange data with the surrounding healthcare ecosystem while retaining a consistent application API.