IHE profiles — XDS, PIX/PDQ
IHE doesn't write standards; it writes recipes for using them. The layer that answers 'we both support HL7, so why doesn't it work?' — and the reason regional exchanges function at all.
In one line
IHE (Integrating the Healthcare Enterprise) writes no standards. It writes recipes for using them — precise specifications of which standard to use, in which role, for which transaction — and that turns out to be the missing layer nobody expected to need.
The problem IHE solves
Two vendors say "we support HL7." They connect. It doesn't work.
Both were telling the truth. A standard is a large box of possibilities, and they each picked different things from it. This is the same disease as FHIR without profiles and CDA without C-CDA: standards define what's possible; interoperability requires agreeing what's actual.
IHE's insight was that this agreement is a distinct artefact deserving its own discipline. An IHE profile names the actors (Document Source, Document Consumer, Registry) and the transactions between them, and pins down exactly which standard, which version, which options. Two systems that implement the same profile work together — not because they support the same standard, but because they made the same choices.
The three you'll actually meet
XDS — Cross-Enterprise Document Sharing. The architecture behind most regional and national document exchanges. A Registry holds metadata about documents; Repositories hold the documents themselves; a Consumer queries the registry, then fetches from the repository. The separation is the clever part: the index is central, the documents stay where they were created. No giant national vault — the same federated instinct behind ABDM's consent manager. XDS-I extends it to imaging.
PIX — Patient Identifier Cross-referencing. Hospital A calls her MRN 4471. Hospital B calls her 88123. PIX maintains the cross-reference so a query in one domain can find her in the other. It's the MPI problem, formalised across organisations.
PDQ — Patient Demographics Query. "Find me patients matching this name and date of birth." The lookup that populates a registration screen without re-typing.
Underneath: PIX and PDQ don't invent a wire format. They specify HL7 v2 (or FHIR, in the modern PIXm/PDQm variants). That's IHE's whole nature — it is a layer of agreements, not code.
The Connectathon — the part worth stealing
IHE's most under-appreciated contribution isn't a document. It's the Connectathon: vendors physically bring their systems to one place and are made to interoperate, against each other, under supervision, with results published.
That is testing as a social institution rather than a technical one — and it works for a reason worth naming: a specification is a hypothesis until two independent implementations meet. Everything else is a vendor's claim about their own software.
Any national programme building an exchange — ABDM's certification milestones included — is reinventing some version of this idea. The ones that skip it discover their spec was ambiguous after the money is spent.
Where it stands now
IHE profiles are heavily used in Europe and in national imaging and document exchanges worldwide; XDS underpins a great deal of infrastructure that quietly works. IHE has also published FHIR-based profiles (MHD, PIXm, PDQm) as the field moved.
The honest read: XDS is document-era architecture, and greenfield projects increasingly start FHIR-native. But an enormous installed base runs on it, and the concept — that standards need profiles, and profiles need a connectathon — is the durable lesson, not the XML.