Mediloop
CONNECTORS

Choose an Integration Method

Mediloop offers multiple integration methods to connect external systems, devices or applications. Choose the approach that best fits your system capabilities, technical constraints and use case.

No one-size-fits-all.
Different scenarios require different approaches. Use this guide to select the most efficient and future-proof integration method.

REST API

Standard REST endpoints for resource operations using JSON.

  • • Simple to implement
  • • Fine-grained control
  • • Wide language support
Best for

Custom applications and point-to-point integrations.

FHIR API

Healthcare interoperability using HL7® FHIR® standards.

  • • Standardized healthcare data
  • • Interoperability by design
  • • Rich ecosystem support
Best for

EHR, HIS, LIS and healthcare system integrations.

Webhooks

Real-time event notifications sent to your endpoints.

  • • Event-driven
  • • Near real-time updates
  • • Reduce polling
Best for

Real-time notifications and event-driven workflows.

Connector

Use a pre-built or custom connector to integrate non-standard systems.

  • • Protocol translation
  • • Works with legacy systems
  • • Deployed via Gateway
Best for

Devices, analyzers, proprietary or legacy systems.

Connector SDK

Build your own connector using the Mediloop Connector SDK.

  • • Maximum flexibility
  • • Support any protocol
  • • Extend Mediloop ecosystem
Best for

Vendors and partners building custom connectors.

How to decide?

Start
Does the system support FHIR natively?
Yes → Use FHIR API
Do you need real-time event notifications?
Yes → Use Webhooks
Is the system a device, analyzer or non-standard protocol?
Yes → Use a Connector
Do you want to build your own integration or protocol?
Yes → Use Connector SDK
Otherwise
Use REST API
Need help choosing?

Our integration experts can help you choose the right method for your project.

Good to know
  • • You can combine multiple methods in the same integration.
  • • All methods follow the same security, authentication and governance model.
  • • Connectors use the Connector Gateway for secure, outbound-only connectivity.