When a patient needs care away from home — in another hospital, another region, or another country — the clinician in front of them rarely has access to their full record. The International Patient Summary (IPS) answers a narrower, more achievable question: what is the minimal set of facts a clinician needs to treat someone safely, anywhere?
What problem the IPS solves
The IPS is deliberately minimal and non-exhaustive, and specialty-agnostic. It is not the whole record; it is the essentials — enough to support unplanned and cross-border care. That constraint is what makes it realistic to implement across very different national systems.
Two representations: CDA and FHIR
The IPS is published as an HL7 standard in two aligned representations: a document-oriented HL7 CDA form and a resource-oriented HL7 FHIR form. That duality is deliberate — it lets organisations exchange a persistent, signed clinical document where that is what they need, while also enabling granular, API-based access where that fits better. The underlying clinical content is the same.
What's in it
At its core the IPS carries the sections a clinician reaches for first: known allergies and intolerances, current medications, and active problems, alongside supporting information such as immunisations, results, and relevant history. Coded terminologies make those entries computable rather than free text, which is what allows a receiving system to reason about them.
Adopting it
For a national programme, the value of starting from the IPS is that you inherit a coherent, internationally reviewed baseline instead of designing a summary from scratch — then constrain and extend it for local needs. That is precisely the kind of transition, from an international specification to a maintainable national one, where a computable approach pays off.
The IPS will not replace a full electronic health record, and it is not meant to. Its power is in being small enough to actually deploy, and standard enough to be understood on the other side.