Mediloop
HEALTHCARE SYSTEMS CONNECTORS

Overview

1 of 9

Connect Mediloop with Hospital Information Systems (HIS), Electronic Health Records (EHR/EMR), departmental systems and clinical platforms using secure, standards-based interoperability across the care continuum.

HIS / EHRHL7 v2FHIR R4 / R4BIHE ProfilesREST APIsDocumentsOrders & ResultsCare Continuity
Architecture Overview
External Healthcare Systems
Hospital Information Systems (HIS)
Electronic Health Records (EHR / EMR)
Departmental systems — LIS, RIS, PACS, pharmacy
National / regional platforms — DSP, DMP, HIE
Third-party care platforms and portals
Connector Protocol Layer
HL7 v2 — ADT, ORM, OML, ORU, SIU
FHIR RESTful APIs — R4 / R4B resources
CDA / C-CDA document exchange
IHE profiles — PIX/PDQ, MHD, XDS-b
Transport — TLS 1.2+, mTLS, VPN, secure file exchange
Mediloop Connector & MSIS
Receive, validate and acknowledge
Transform and map to canonical resources
Identity resolution and reconciliation
Terminology normalization and provenance
Retries, observability and audit
Mediloop Platform
Patient and encounter record
Scheduling and calendars
Clinical orders and results
Documents and longitudinal record
CareFlow transitions and notifications
What You Can Integrate
ADT & patient management

Admissions, transfers, discharges, demographics, merges and encounter context.

Scheduling

Appointments, slots, clinician/room/equipment availability and cancellations.

Orders & results

Laboratory, imaging, cardiology and other diagnostic orders/results.

Clinical documents

CDA/C-CDA, PDF, FHIR DocumentReference and structured Composition resources.

Medications, allergies & diagnoses

Longitudinal medication lists, allergies/intolerances and problem lists.

Care transitions

Admission packages, discharge summaries, care plans, tasks and follow-up coordination.

Core Capabilities
Standards-based exchange

HL7 v2, FHIR, CDA/C-CDA and IHE patterns.

Bidirectional synchronization

Inbound and outbound workflows with acknowledgements, reconciliation and events.

Semantic interoperability

MSIS normalization, terminology mapping and source-provenance retention.

Governed by design

Tenant context, consent, authorization, audit and secure transport.

Resilient integration

Idempotency, retries, DLQs, correlation IDs and health monitoring.

Modernization ready

Use APIs, SDKs and connectors to progressively replace legacy capabilities.

Standards & Protocols
Standard / protocolPrimary role
HL7 v2Legacy and enterprise event/message exchange — ADT, SIU, ORM/OML, ORU, ACK
FHIR R4 / R4BModern RESTful exchange for Patient, Encounter, Appointment, ServiceRequest, Observation, DiagnosticReport, documents and medications
CDA / C-CDAStructured clinical documents and discharge summaries
IHE profilesPatient identity, document sharing and cross-enterprise exchange
REST / Webhooks / SDKMediloop-native application integration, orchestration and event-driven workflows
Developer Integration Surface
How to read this section
FHIR resources and HL7/IHE operations are standards-based integration surfaces. Mediloop REST routes shown here are documentation contracts and must remain marked planned until the corresponding backend route is implemented and production-approved.
SurfaceOperation / resourceUseStatus
FHIRPatient, Encounter, Appointment, ServiceRequest, Observation, DiagnosticReport, DocumentReference, MedicationRequest, AllergyIntolerance, ConditionBuild or modernize clinical workflows against standards-based resourcesFHIR surface
HL7 v2ADT / SIU / ORM / OML / ORU / ACKConnect existing HIS/EHR/interface engines without requiring immediate replacementProtocol operation
IHE / CDAMHD / XDS-style document exchange, CDA/C-CDAEnterprise and cross-organizational document sharingProfile / document
REST / SDKHealthcare connector orchestration, mapping, status and eventsMediloop-native integration and modernization façadePlanned contract
Common Use Cases
Connect an existing hospital HIS to Mediloop without replacing it
Add FHIR capabilities to a legacy EHR while keeping current clinical workflows
Synchronize patient/encounter/scheduling data across hospital and Mediloop apps
Route diagnostic orders and results to departmental systems
Exchange discharge documents and trigger CareFlow coordination
Progressively replace proprietary modules with versioned Mediloop APIs and SDKs
Modernization Path
1
Assess
Inventory legacy modules, interfaces and standards
2
Connect
Introduce connectors around existing systems
3
Normalize
Map data through FHIR and MSIS
4
Replace incrementally
Move selected capabilities to Mediloop APIs/SDKs
5
Run side-by-side
Reconcile until confidence and parity are reached
6
Cut over
Retire legacy capability when ready