Integration
Medplum's integrations 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 |
|---|---|---|---|
| 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 |
| Labcorp | Diagnostics | Lab orders and results | Bot and setup |
| Quest | Diagnostics | Lab orders and results | Bot and setup |
| Health Gorilla | HIE/Diagnostics | Diagnostics orders - records - ADT | Bot and setup |
| Candid Health | Billing | Revenue cycle and insurance eligibility check | Candid bot |
| Particle | HIE | Read/Write from Exchanges | Open source coming soon |
| Epic Systems | EHR | Read/Write via FHIR API | Epic JWT authentication |
| Recaptcha | Security | Enable recaptcha on patient registration | Setup recaptcha |
| Datadog | Observability | Application monitoring | Datadog sidecar setup |
| Snowflake | Data warehouse | Synchonize data to datawarehouse | Documentation coming soon |
Common Medical Integrations
Medplum provides templates and playbooks for common medical integrations.
| Name | Type | Description | Documentation |
|---|---|---|---|
| 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 |
| FHIR CMS 9115 | Payor | FHIR Provider directory for Payor compliance | Documentation |
| FHIRcast | Radiology | Event driven workflow for workstations | Documentation |
| Video | Binary Files | Upload and transcode video | Documentation |
| Binary Files | Upload and access PDF | Documentation | |
| Images | Binary Files | Upload and access image files | Documentation |
| OAuth2 | Identity | Plug in any oAuth2 provider | Documentation |
| Basic Auth | Identity | Support connections via Basic Auth for legacy systems | Basic auth |
| BulkFHIR | EHR/Payor | Export FHIR Data for use by partners | BulkFHIR documentation |
| SMART-on-FHIR | EHR | SMART app launch from Medplum or another EHR | SMART App Launch |
Custom built integrations
Medplum provides building blocks for custom integrations. Some examples are below.
| Name | Template Type | Description | Documentation |
|---|---|---|---|
| Stripe | Bot Webhooks | Synchronize payments data | Stripe bot |
| CMS 1500 | Bot PDF | Create PDF for CMS 1500 | PDF Bot |
| Superbill | Bot PDF | Create PDF for Superbill | PDF Bot |
| Medications | API | Prescribe and check medications | Medication related integration |
| Accuity Scheduling | Bot Webhooks | Enable third party scheduling | Consuming webhooks |
| Cal.com | Bot Webhooks | Enable third party scheduling | 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.