Skip to main content

Integration

iEHR's integration capabilities are among the most utilized features of the platform, offering tools to build robust and effective integrations. iEHR supports three types of integrations:

  1. First-Party Integrations: These are pre-built integrations with common medical systems.

  2. Common Medical Integrations: Templates and playbooks for standard medical integrations.

  3. Custom Built Integrations: Using the SDK and Bot templates to create tailored solutions.

iEHR system overview

First-Party Integrations

iEHR supports the following first-party integrations:

  • Okta: Enable Okta SSO for Providers. Okta setup

  • Auth0: Enable Auth0 SSO for Providers and Patients. Auth0 account setup

  • Google Authentication: Enable Google SSO for Providers and Patients. Google Auth setup

  • Azure SSO: Enable Azure SSO for Providers and Patients. Azure Auth setup

  • Labcorp: Lab orders and results. Bot and setup

  • Quest Diagnostics: Lab orders and results. Bot and setup

  • Particle: Read/Write from Exchanges.

  • Epic Systems: Read/Write via FHIR® API. Epic JWT authentication

  • Recaptcha: Enable recaptcha on patient registration. Setup recaptcha

  • Datadog: Application monitoring. Datadog sidecar setup

  • Sumo Logic: Application monitoring.

  • Snowflake: Synchronize data to data warehouse.

  • OpenAI: Large language models.

Common Medical Integrations

iEHR provides templates and playbooks for common medical integrations:

  • HL7 V2: Connect to ADT ORU or other HL7 Feeds. On premise agent

  • FHIR®: FHIR® API for other EHRs. Example bot

  • SFTP: Synchronize data. Example bot

  • FHIR® CMS 9115: FHIR® Provider directory for Payor compliance. Documentation.

  • FHIRcast: Event-driven workflow for workstations. Documentation.

  • Video: Upload and transcode video. Documentation.

  • PDF: Upload and access PDF. Documentation.

  • Images: Upload and access image files. Documentation.

  • OAuth2: Plug in any oAuth2 provider. Documentation.

  • Basic Auth: Support connections via Basic Auth for legacy systems. Basic auth.

  • BulkFHIR: Export FHIR® Data for use by partners. BulkFHIR documentation

  • SMART-on-FHIR®: SMART app launch from iEHR or another EHR. SMART App Launch.

Custom Built Integrations

iEHR provides building blocks for custom integrations. Some examples include:

  • Stripe Bot: Synchronize payments data. Stripe bot

  • Superbill Bot: Create PDF for Superbill. PDF Bot

  • Medications API: Prescribe and check medications. Medication related integration.

  • Acuity Scheduling Bot: Enable third-party scheduling. Consuming webhooks

  • Cal.com Bot: Enable third-party scheduling. Consuming webhooks

Integration Building Blocks and Testing

Complex integrations are built by composing bots, subscriptions, authentication and authorization, and the SDK. The 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.

For more detailed information, feel free to contact us at hello@iehr.ai .