NATIONAL & HEALTH INFORMATION EXCHANGE CONNECTORS
France DMP / Mon espace santé Integration
3 of 8Connect Mediloop to national and cross-border health information exchange infrastructures using standards-based, governed adapters.
FranceDMPMon espace santéPro Santé ConnectPatient identityFHIR / IHEANS conformance
French Ecosystem Adapter
Isolate French national specifics behind a dedicated adapter.
Professional Trust
Use approved professional and organization trust mechanisms.
Identity-Aware
Resolve patient identity through applicable French identity rules.
Conformance-Driven
Treat national conformance/certification as part of production onboarding.
Integration Architecture
1
HIS / Application
Clinical source or Mediloop application
2
France Connector
National adapter, validation and exchange orchestration
3
Identity & Trust
Professional, organization and patient checks
4
DMP / Mon espace santé
Approved French national exchange services
5
Care & Patient Access
Authorized professionals and patient-facing services
Identity & Trust
Use the approved French professional identity mechanism for the target workflow
Resolve and validate patient identity through applicable national services/rules
Validate organization/facility identity and context
Keep authentication separate from Mediloop permissions/scopes and patient-access policy
Record source identifiers and identity provenance
Documents & Clinical Data
Documents
Discharge reports, summaries and approved document types.
FHIR resources
Use FHIR internally and map to the national profile where supported.
Medication information
Connect prescription/medication workflows to applicable French services.
Care continuity
Integrate national access into hospital/community workflows.
Consent & Patient Rights
Evaluate permitted purpose and access context before exchange
Apply national patient-rights/access rules
Minimize data to the authorized purpose
Expose audit/access history where appropriate
Handle revocation, denial and insufficient-authority responses explicitly
Testing & Conformance
1
Sandbox
Approved test environments and identities
2
Profile Tests
Exchange and identity profiles
3
Security
Certificates, scopes, logging and protection
4
Approval
Required conformance/certification
5
Go Live
Monitored production and support ownership
Error Handling
| Failure | Expected behavior | Recovery |
|---|---|---|
| Identity mismatch | Do not exchange patient data | Resolve identity / human review |
| Unauthorized professional | Reject clearly | Re-authenticate / verify status |
| National endpoint unavailable | Retry only when safe | Backoff + operational alert |
| Profile validation failure | Quarantine payload | Correct mapping and resubmit with correlation ID |
Developer Integration Surface
How developers interact with this capability
Healthcare software integrates to stable Mediloop connector/FHIR surfaces while French national protocols, trust and conformance remain adapter responsibilities.
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| National adapter | France DMP / Mon espace santé connector | Country-specific exchange | Onboarding required |
| Identity | Pro Santé Connect / national identity services | Professional/patient trust | National service |
| FHIR / IHE | Approved profiles | Payload/exchange standards | Profile-specific |
| Mediloop events | Exchange status / failures | Application workflow | Connector schema |
Next Steps
Confirm exact French service/data flow
Complete organization/professional identity prerequisites
Implement approved national mapping
Run sandbox/conformance scenarios
Go live only after security/certification gates