NATIONAL & HEALTH INFORMATION EXCHANGE CONNECTORS

Overview

1 of 8

Connect Mediloop to national and cross-border health information exchange infrastructures using standards-based, governed adapters.

FHIRIHE XDS / XCA / MHDPIX / PDQATNAEEHRxF alignmentNational adapters

Better Continuity of Care

Access and share patient information across care settings and borders.

Standards-Based

Use IHE, FHIR and national specifications rather than proprietary exchange patterns.

Patient-Centric

Apply consent, purpose and patient-rights controls to every exchange.

Cross-Border Ready

Prepare for MyHealth@EU and evolving European interoperability requirements.

What Are National & HIE Connectors?

National & HIE connectors let Mediloop exchange health information with national, regional and cross-border infrastructures while keeping country-specific protocols, trust, consent and certification behind governed adapters.

Key Benefits

Access national patient summaries and documents through a consistent Mediloop integration layer

Exchange ePrescriptions and eDispensation information where the infrastructure supports it

Reduce duplicate integrations across hospitals, clinics, pharmacies and partners

Preserve auditability, patient rights and national trust requirements

Support gradual cross-border readiness without exposing country-specific complexity to every application

Supported Networks

Luxembourg eSanté / DSP

Country adapter

Country-specific adapter and onboarding path for Luxembourg health information exchange.

France DMP / Mon espace santé

Country adapter

French national exchange adapter with national trust and conformance requirements.

MyHealth@EU / NCPeH

Planned / staged

Cross-border exchange through national contact points for eHealth.

Regional HIEs

Adapter-based

IHE/FHIR-based regional and organization networks through configurable adapters.

Standards & Frameworks

Standard / profile	Purpose	Mediloop role
FHIR R4/R5	Clinical resource exchange	Canonical resource/API layer where applicable
IHE XDS / MHD / XCA	Document sharing / cross-community access	Protocol/profile adapters
PIX / PDQ	Patient identity query / cross-reference	Identity connector integration
ATNA	Audit and node authentication	Audit/trust integration
EEHRxF	European EHR exchange format	Future/evolving alignment; not claimed as fully deployed

Integration Architecture

External Networks

DSP, DMP, NCPeH, regional HIEs and registries

HIE Connector

Protocol adapters, trust, consent, validation and routing

MSIS

Clinical terminology normalization, mapping and provenance

Mediloop Platform

FHIR resources, patient record, documents and care workflows

Care Continuity

Hospitals, GPs, pharmacies, patients and authorized providers

Use Cases

Patient Summary

Retrieve or publish a structured patient summary.

Clinical Documents

Exchange discharge reports, results and governed documents.

ePrescription

Exchange prescription and dispensing information where supported.

Care Transitions

Coordinate discharge and cross-organization continuity workflows.

Security & Compliance

Strong system and professional identity through national trust mechanisms

Consent, legal basis and purpose-of-use checks before data release

mTLS/TLS and certificate validation where required

Tenant isolation and least-privilege scopes in Mediloop

Immutable audit/provenance and correlation IDs across connector hops

Country-specific certification and production onboarding before live exchange

Related Resources

Identity & Trust Connectors

Healthcare Systems Connectors

FHIR API documentation

Consent and authorization documentation

Developer Integration Surface

How developers interact with this capability

Applications use stable Mediloop clinical/connector contracts; country-specific endpoints, certificates and transport remain isolated inside the national adapter.

Surface	Operation / resource	Use	Status
FHIR	Patient / Composition / DocumentReference / MedicationRequest	Standardized clinical exchange	Standard
IHE	XDS / MHD / XCA / PIX / PDQ / ATNA	National or regional exchange profiles	Profile-based
National adapter	DSP / DMP / NCPeH connector	Country-specific infrastructure	Onboarding/certification required
Events	Connector status / exchange outcome	Asynchronous status	Connector-specific

Next Steps

Choose the target country/network and use case

Review national onboarding, identity and certificate prerequisites

Map source clinical data through FHIR/MSIS

Run conformance scenarios in sandbox/test environments

Complete security, operational and certification readiness before production