NATIONAL & HEALTH INFORMATION EXCHANGE CONNECTORS
MyHealth@EU / NCPeH Integration
4 of 8Connect Mediloop to national and cross-border health information exchange infrastructures using standards-based, governed adapters.
MyHealth@EUNCPeHPatient SummaryePrescription / eDispensationEEHRxFCross-border trustPlanned / staged
European Interoperability
Connect cross-border workflows through national contact points.
Patient-Centric
Support citizens receiving care in another EU country with purpose-controlled access.
Standards-Based
Use EU specifications and standardized terminology mappings.
Future-Ready
Keep future EHDS/EEHRxF capabilities explicitly staged.
What is MyHealth@EU?
MyHealth@EU provides cross-border health-data services through National Contact Points for eHealth (NCPeH). Mediloop is designed as an adapter/orchestration layer; availability depends on country onboarding, enabled use cases and EU/national implementation timelines.
Key Benefits
One Mediloop integration pattern for multiple cross-border use cases
Common terminology/document normalization through governed semantic services
Patient/professional trust enforced at national/EU boundaries
Traceable routing and exchange outcomes
Staged support as additional MyHealth@EU services become available
How It Works
1
Source Country
Authorized clinical data
2
Source NCPeH
National validation, trust and routing
3
MyHealth@EU
Cross-border specifications and secure exchange
4
Destination NCPeH
National policy, translation and routing
5
Care Provider
Authorized cross-border care access
Key Data Flows
Patient Summary
Core use caseCross-border summary for continuity of care.
ePrescription / eDispensation
Country dependentPrescription/dispense exchange between participating countries.
Laboratory Results
Future / stagedFuture/evolving EU exchange capability.
Imaging / Reports
Future / stagedFuture/evolving exchange capability.
Standards & Specifications
| Layer | Examples | Mediloop handling |
|---|---|---|
| Clinical exchange | FHIR / EU implementation specifications | Normalize to Mediloop FHIR resources |
| Terminology | SNOMED CT, LOINC, ICD, UCUM, EU value sets | MSIS mapping + original-code preservation |
| Cross-border format | EEHRxF-aligned specifications | Staged adapter support |
| Trust | NCPeH agreements / certificates / national eID | Identity & Trust connector integration |
EU Roadmap & EHDS
Future-state transparency
EHDS and EEHRxF obligations are phased. Label each Mediloop cross-border capability as available, pilot, planned or dependent on national/EU implementation instead of implying universal production availability.
Common Use Cases
Treat an EU citizen while abroad
Retrieve an available patient summary
Receive/dispense an eligible cross-border ePrescription
Return eDispensation information
Support cross-border workers and seasonal residents
Security & Compliance
National/EU trust framework and NCPeH agreements
Purpose-based access, patient rights and minimization
Strong professional and organization authentication
Cross-border audit/provenance and correlation IDs
Country-specific retention/incident obligations
GDPR and evolving EHDS requirements
Developer Integration Surface
How developers interact with this capability
Do not integrate applications directly to each country's NCPeH; keep country/EU variation behind Mediloop's connector abstraction.
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| NCPeH adapter | MyHealth@EU exchange operation | Cross-border data exchange | Planned/staged by country |
| FHIR / EU profiles | Patient Summary / ePrescription resources | Standardized payload | Profile-specific |
| Terminology | EU/national value-set mapping via MSIS | Semantic consistency | Governed mapping |
| Events | Cross-border job/exchange status | Async workflow | Connector-specific |
Next Steps
Choose participating countries/use case
Review NCPeH onboarding/test requirements
Validate EU profile/terminology mappings
Test cross-border identity/rejection scenarios
Promote only approved country/use-case combinations