Integration | Medplum
Medplum Integrations
Medplum's integrations are the most commonly used features of the platform, and the tools can be used to build effective robust integrations. Medplum supports three types of integrations:
- First party integrations with common medical systems
- Common medical integrations like FHIR, HL7 V2, SMART-on-FHIR and SFTP
- Custom built integrations using the SDK and Bot templates
First Party Integrations
Medplum supports the following first party integrations.
| Name | Type | Description | Documentation |
|---|---|---|---|
| Authentication and Identity | |||
| Okta | Authentication | Enable Okta SSO for Providers | Okta setup |
| Auth0 | Authentication | Enable Auth0 SSO for Providers and Patients | Auth0 account Setup |
| Google Authentication | Authentication | Enable Google SSO for Providers and Patients | Google Auth Setup |
| Entra SSO (fka Azure SSO) | Authentication | Enable Microsoft Entra SSO for Providers and Patients | Entra Auth Setup |
| reCAPTCHA | Security | Enable reCAPTCHA on patient registration | Set up reCAPTCHA |
| Clinical Systems (EHR, HIE, Labs) | |||
| Epic Systems | EHR | Read/Write via FHIR API | Epic JWT authentication |
| Health Gorilla Patient 360 | HIE | Integrated records and ADT data | Health Gorilla Integration |
| Zus Health | HIE | Integrated HIE, analytics and longitudinal care | Medplum integration |
| Health Gorilla Lab Network | Diagnostics | Lab orders and results | Health Gorilla Integration |
| Labcorp | Diagnostics | Lab orders and results | Bot and setup |
| Quest | Diagnostics | Lab orders and results | Bot and setup |
| Communications | |||
| eFax | Communications | Send and receive faxes via FHIR Communication resources | eFax Integration |
| Twilio SMS | Communications | Send and receive SMS messages via FHIR Communication resources | Twilio SMS Integration |
| Billing | |||
| Candid Health | Billing | Revenue cycle and insurance eligibility check | Candid bot |
| Data and Observability | |||
| Datadog | Observability | Application monitoring | Datadog sidecar setup |
| Sumo Logic | Observability | Application monitoring | Coming soon |
| Snowflake | Data warehouse | Synchronize data to datawarehouse | Documentation coming soon |
| Artificial Intelligence | |||
| OpenAI | AI | Large language models | Medplum AI |
| Devices and Remote Monitoring | |||
| AnyBio | Remote Monitoring | Cardiac and biosignal monitoring data as FHIR Observations | Documentation coming soon |
Common Medical Integrations
Medplum provides templates and playbooks for common medical integrations.
| Name | Type | Description | Documentation |
|---|---|---|---|
| Clinical and EHR Data | |||
| HL7 V2 | EHR | Connect to ADT ORU or other HL7 Feeds | On premise agent |
| FHIR (g)(10) | EHR | FHIR API for other EHRs | Example bot FHIR API connectivity CLI connector |
| SFTP | EHR | Synchronize data | Example bot |
| SMART-on-FHIR | EHR | SMART app launch from Medplum or another EHR | SMART App Launch |
| CDS Hooks | EHR | Contextual CDS service discovery and invocation | CDS Hooks |
| FHIRcast | Radiology | Event driven workflow for workstations | Documentation |
| Payor and Compliance | |||
| FHIR CMS 9115 | Payor | FHIR Provider directory for Payor compliance | Documentation |
| BulkFHIR | EHR/Payor | Export FHIR Data for use by partners | BulkFHIR documentation |
| Identity and Authentication | |||
| OAuth2 | Identity | Plug in any oAuth2 provider | Documentation |
| Basic Auth | Identity | Support connections via Basic Auth for legacy systems | Basic auth |
| Binary and Media | |||
| Video | Binary Files | Upload and transcode video | Documentation |
| Binary Files | Upload and access PDF | Documentation | |
| Images | Binary Files | Upload and access image files | Documentation |
Custom Built Integrations
Medplum provides building blocks for custom integrations. Any system that exposes an API (REST/FHIR), HL7, or SFTP interface can be connected to Medplum - you are not limited to a fixed catalog of vendors. Because the integration logic is built with Bots that run on your own project, you own and control it. This makes custom built integrations both flexible and portable.
| Name | Template Type | Description | Documentation |
|---|---|---|---|
| Scheduling and Payments (Bot Webhooks) | |||
| Stripe | Bot Webhooks | Synchronize payments data | Stripe bot |
| Acuity Scheduling | Bot Webhooks | Enable third party scheduling | Consuming webhooks |
| Cal.com | Bot Webhooks | Enable third party scheduling | Consuming webhooks |
| Clinical (API) | |||
| Medications | API | Prescribe and check medications | Medication related integration |
| NPPES NPI Registry | Bot API | Look up National Provider Identifier (NPI) records from the public CMS registry | NPPES Lookup Bot |
| Documents and Forms (Bot PDF) | |||
| CMS 1500 | Bot PDF | Create PDF for CMS 1500 | PDF Bot |
| Superbill | Bot PDF | Create PDF for Superbill | PDF Bot |
| Consent and E-signature (Bot Webhooks) | |||
| DocuSign | Bot Webhooks | Send documents for signature and store completed agreements | Consuming webhooks |
| Dropbox Sign | Bot Webhooks | Send documents for signature and store completed agreements | Consuming webhooks |
Integration Building Blocks and Testing
Complex integrations are built by composing bots, subscriptions, authentication and authorization and the TypeScript SDK.
- Running on localhost is useful for testing integrations
- CLI is commonly used to test connectivity to external FHIR Servers
- Integration Features and Fixes on GitHub show the code that powers many of the integrations.
- Audit and Logging Features show several security and observability integrations.
- Bot Pull Requests can be good reference material for how integrations work.
- Auth Pull Requests can also be good reference material for integration planning and learning.