NATIONAL & HEALTH INFORMATION EXCHANGE CONNECTORS

IHE Profiles & Exchange

5 of 8

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

IHEXDS / XDS-IMHDXCAPIX / PDQATNAFHIR complement

Interoperability Standards

Use well-defined IHE profiles for document, identity, query and audit patterns.

Proven & Widely Adopted

Apply profiles used across hospitals, HIEs and national infrastructures.

Multi-Domain Support

Connect documents, imaging, identity and cross-community exchange.

Complements FHIR

Combine IHE workflows with FHIR rather than treating them as competitors.

IHE Integration Architecture

Healthcare Systems

EHR/HIS, LIS, RIS/PACS, pharmacies and clinics

IHE Profiles

XDS/XDS-I, MHD, XCA, PIX/PDQ, ATNA

Mediloop Connector

Profile adapter, policy, validation and monitoring

MSIS / Identity

Terminology and identity services where appropriate

Mediloop Services

Documents, imaging refs, patient records and workflows

IHE Profiles

Profile	Primary use	Connector role
XDS / XDS-I	Document / imaging-document sharing	Registry/repository adapter
MHD	FHIR-based document sharing	FHIR/IHE bridge
XCA	Cross-community access	Community routing adapter
PIX / PDQ	Patient identity cross-reference/query	Identity & MPI integration
ATNA	Audit trail and node authentication	Security/audit integration

Integration Patterns

Publish / Register

Submit documents and metadata.

Query / Retrieve

Discover documents or identities.

Cross-Community

Query/retrieve across HIE boundaries.

FHIR + IHE

Use MHD/FHIR for modern applications while retaining IHE interoperability.

Use Cases

Clinical document sharing

Cross-organization patient identity discovery

Imaging document/manifest exchange

Audit integration for HIE transactions

Progressive modernization toward FHIR-based MHD where supported

Security & Compliance

ATNA-compatible auditing and node authentication where required

mTLS/certificate trust

Patient consent/purpose policy outside transport profile where required

Correlation IDs across IHE and Mediloop records

An IHE profile does not itself grant authorization

Code Examples

httpCopy

# Illustrative MHD-style query through Mediloop
GET /v1/connectors/hie/documents?patient=Patient/123
Authorization: Bearer <token>
X-Connector: regional-hie

Illustrative Mediloop route until the HIE API is frozen. IHE transactions follow the applicable implementation guide.

Developer Integration Surface

Surface	Operation / resource	Use	Status
IHE profile	XDS / MHD / XCA / PIX / PDQ / ATNA	Standards-based exchange	Standard/profile
FHIR	DocumentReference / Composition / Patient	Modern resource representation	Standard
Connector API	Document query/publish orchestration	App-facing abstraction	Planned/frozen per contract
Identity service	Patient cross-reference / trust	Identity context	Mediloop + national

Next Steps

Select the IHE profile

Confirm actor/transaction responsibilities

Map document/identity metadata

Run conformance and negative-path tests

Deploy with certificate, audit and monitoring controls