NATIONAL & HEALTH INFORMATION EXCHANGE CONNECTORS
Best Practices / APIs & SDK / Next Steps
8 of 8Connect Mediloop to national and cross-border health information exchange infrastructures using standards-based, governed adapters.
Reference ArchitectureAPI & SDK ExamplesConfigurationSecurity ChecklistResilienceGo-LiveProduction
Production Ready
Use repeatable architecture and operations.
Developer Friendly
Expose stable app-facing contracts despite national variation.
Standards Aligned
Keep FHIR/IHE/national conformance explicit.
Better Care
Make exchange reliable enough for real care workflows.
Recommended Architecture
1
Applications
Patient, doctor, pharmacy, hospital and partner apps
2
Connector Layer
National adapters + FHIR/IHE protocol adapters
3
MSIS & Identity
Clinical semantics, identity, consent and policy
4
National / EU Systems
DSP, DMP, NCPeH and HIEs
5
Operations
Monitoring, reconciliation, audit and support
API Examples
httpCopy
# Illustrative app-facing contract
GET /v1/connectors/hie/patient-summary?patientId=123
Authorization: Bearer <token>
X-Connector: fr-dmpIllustrative route only; use the versioned HIE API when frozen.
SDK Usage
typescriptCopy
import { MediloopClient } from '@mediloop/sdk';
const client = new MediloopClient({ apiKey: process.env.MEDILOOP_API_KEY! });
// Illustrative planned HIE SDK surface.
const summary = await client.hie.getPatientSummary({ connector: 'fr-dmp', patientId: 'patient-123' });SDK names are illustrative until published.
Configuration Strategy
Separate configuration by country/network/environment
Keep certs/secrets/trust stores out of app source
Version mappings and profile settings
Use feature flags for staged capabilities
Expose connector/dependency health
Do not leak country implementation into generic healthcare APIs
Security Checklist
OAuth/OIDC and/or mTLS per profile
Validate professional/organization/patient context
Enforce consent, purpose, tenant and scopes
Rotate credentials/certificates before expiry
Encrypt in transit/at rest
Audit decisions and payload lineage
Minimize data
Error Handling & Resilience
Backoff only retriable failures
Circuit breakers for unstable dependencies
Idempotency/replay protection
Dead-letter/exception workflows
Correlation IDs across all hops
Reconciliation jobs
Human review for identity/policy ambiguity
Go-Live Checklist
National/partner onboarding complete
Conformance/certification approved
Production certs/endpoints validated
Monitoring/alerts/runbooks active
Support escalation tested
Rollback/connector-disable verified
Enhanced post-go-live monitoring scheduled
Developer Integration Surface
How developers interact with this capability
The app-facing contract should remain stable while national adapters absorb country-specific protocol/trust/profile evolution.
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| HIE API | Country-neutral connector operations | Application integration | Versioned when frozen |
| FHIR API | Clinical resources | Healthcare-domain data | Existing where implemented |
| IHE / national protocols | XDS/MHD/XCA/NCPeH/etc. | External infrastructure | Adapter layer |
| SDK | Typed helper methods | Developer productivity | Published versions only |
| Events | Async status / errors | Workflow coordination | Connector-specific |
Next Steps
Pick target connector
Read identity/trust/conformance prerequisites
Build first against sandbox
Validate failures and governance
Complete certification/production onboarding
Monitor external profile changes continuously