NATIONAL & HEALTH INFORMATION EXCHANGE CONNECTORS
Luxembourg eSanté / DSP Integration
2 of 8Connect Mediloop to national and cross-border health information exchange infrastructures using standards-based, governed adapters.
LuxembourgeSantéDSPLuxTrustFHIRIHE XDS / MHDConsent & audit
National Infrastructure
Use a Luxembourg-specific adapter rather than embedding DSP details in each application.
Patient-Centric
Respect patient rights and authorized professional access.
Secure & Compliant
Use strong trust, consent and audit controls.
Interoperable
Map Mediloop clinical resources to approved exchange profiles.
Integration Architecture
1
Your Application
HIS, EHR, clinic, practice or Mediloop app
2
Mediloop HIE Connector
Luxembourg adapter, validation, routing and monitoring
3
Trust & Access
LuxTrust / certificates / scopes / consent as required
4
Luxembourg eSanté / DSP
National services, documents and governed access
5
Authorized Care
Professionals, organizations and patients through approved channels
Authentication & Access
Register the organization/application through the applicable eSanté onboarding process
Provision required LuxTrust or other accepted trust material
Keep professional, organization and technical-client identity distinct
Store certificates/secrets in managed secret storage and rotate them
Request only scopes/purposes necessary for the approved use case
Exact authentication flows, certificates and national endpoints are connector- and onboarding-specific. Link to the approved production profile rather than hard-coding assumptions.
FHIR & Document Mapping
| Clinical concept | Mediloop representation | DSP / exchange mapping |
|---|---|---|
| Patient summary | FHIR Composition + referenced resources | Approved national summary/document profile |
| Clinical document | DocumentReference / Composition | IHE XDS/MHD metadata and payload |
| Patient identity | Patient identifiers + identity links | National identifier rules via Identity/MPI |
| Prescription | MedicationRequest | National ePrescription adapter where supported |
Use Cases
Publish documents
Share authorized clinical documents and summaries.
Retrieve shared information
Query authorized records for continuity of care.
Prescription continuity
Use supported national prescription pathways.
Discharge / CareFlow
Coordinate handoff while publishing required information.
Security & Compliance
GDPR and Luxembourg-specific legal/contractual requirements
Luxembourg data-sovereignty commitments according to deployment agreement
Patient consent and purpose controls where required
mTLS/TLS, certificate validation and trusted technical identity
Full audit trail, access history and provenance
Production only after required national testing/approval
Testing
1
Local
Mocks and FHIR/IHE fixtures
2
Connector Test
Mapping, auth and error scenarios
3
National Test
Approved eSanté test environment when available
4
Conformance
Evidence and approval requirements
5
Production
Monitored controlled rollout
Developer Integration Surface
How developers interact with this capability
Develop against the Mediloop connector/test profile; production DSP endpoints and trust material are provisioned through approved Luxembourg onboarding.
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| Mediloop HIE API | DSP connector operations | Invoke approved workflows | Connector contract |
| FHIR | Composition / DocumentReference / Patient / MedicationRequest | Clinical payload model | Standard |
| IHE | XDS/MHD and related profiles | Document exchange | Profile-based |
| Trust | LuxTrust / certificates / mTLS | Technical/professional trust | National onboarding |
Next Steps
Confirm Luxembourg use case and legal basis
Complete eSanté/organization onboarding prerequisites
Configure trust material and test endpoints
Validate FHIR/IHE mapping and audit behavior
Complete conformance and controlled production rollout