International Patient Summary (IPS)
The worldwide standard for sharing key health data across borders.
The International Patient Summary (IPS) is a worldwide standard for a short electronic health record extract. It holds the basic clinical facts a clinician needs to treat a patient safely.
Language: العربية, Български, भोजपुरी, বাংলা, Čeština, Cymraeg, Dansk, Deutsch, Ελληνικά, English, Español, Eesti, Euskara, فارسی, Suomi, Français, Gaeilge, Gàidhlig, ગુજરાતી, Hausa, עברית, हिन्दी, Hrvatski, Magyar, Bahasa Indonesia, Íslenska, Italiano, 日本語, Basa Jawa, ខ្មែរ, ಕನ್ನಡ, 한국어, Lëtzebuergesch, ລາວ, Lietuvių, Latviešu, मराठी, Bahasa Melayu, Malti, Norsk bokmål, Nederlands, ਪੰਜਾਬੀ, Naijá, Polski, Português, Română, Русский, Scots, Slovenčina, Slovenščina, Svenska, Kiswahili, தமிழ், తెలుగు, ไทย, Tagalog, Türkçe, Українська, اردو, Tiếng Việt, 吴语, 粵語, 中文
The International Patient Summary (IPS) is a worldwide standard for a short electronic health record extract. It holds the basic clinical facts a clinician needs to treat a patient safely. It is designed to be:
- Minimal and non-exhaustive. It is a small, curated subset of a health record, not the full record.
- Specialty-agnostic. Any clinician can use it, in any discipline.
- Condition-independent. It is not tied to a particular disease or care pathway.
- Implementable and international. It is built on global standards and terminologies, so it can be used across countries, languages, and IT systems.
In short, the IPS answers one question for a clinician who has never met the patient: "What do I need to know right now to care for this person safely?"
Why the IPS exists
Health information is usually locked inside a local electronic health record (EHR), a national system, or a vendor's product. When a patient seeks care somewhere else, such as another hospital, region, or country, the treating clinician often has no access to that history. The IPS gives everyone one shared, portable summary format.
Core use cases
| Use case | Description |
|---|---|
| Unscheduled and emergency care | A patient falls ill or is injured away from home, and local clinicians cannot reach the patient's home EHR. This is the original, primary use case. |
| Cross-border care | Travelers, migrants, cross-border workers, and refugees carry a summary that clinicians abroad can read. |
| Planned care and transitions | Referrals, specialist consultations, admissions, discharges, and handovers between providers. |
| Medical tourism and mobility | Patients who choose to receive care in another jurisdiction. |
| Patient empowerment | Patients hold, view, and share their own summary from a phone app, a portal, or a printed copy. |
When to use the IPS
Use the IPS when someone who does not know the patient needs a trustworthy snapshot quickly, and when the sender and receiver do not share an IT system.
Good fits
- Emergency and unplanned care, especially away from home or across a border. This is the use the IPS was designed for.
- Cross-border exchange between national systems, such as the EU's MyHealth@EU service [1] [2].
- Patient-held summaries that travelers, migrants, refugees, pilgrims, or people with complex conditions carry on a phone or on paper [3].
- A national or regional patient summary. Many countries build their own summary as a profile of the IPS, so it can also be exchanged internationally [4] [5] [6].
- A common baseline for care transitions, such as referrals, admissions, and discharges, when a richer specialized document is not available.
- A starting point for other datasets, such as vaccination certificates, research data, or registries that need the same core facts [7] [8].
Poor fits
- The full medical record. The IPS is deliberately minimal. Use a full record export or a specialized document when detail matters.
- Specialty-specific documents, such as an oncology treatment summary, a maternity record, or a detailed discharge summary. These have their own standards, which can include or reference IPS content.
- Real-time clinical workflows inside one organization. Inside a single EHR, query the live data rather than a summary snapshot.
- Legal, billing, or insurance records. The IPS is a clinical summary, not an administrative or claims record.
- Decisions that need guaranteed completeness. An IPS is only as complete and current as its source and its author. Always confirm critical facts with the patient when possible.
What an IPS contains
An IPS document has two layers:
A header that records who, what, and when:
- Patient: identity, demographics, and contacts.
- Author: the person, organization, or system that produced the summary.
- Custodian: the organization responsible for maintaining it.
- Attester: who has verified it, if anyone.
- Date and time: when it was created.
A clinical body organized into sections. Sections are required, recommended, or optional.
| Section | Status | Typical content |
|---|---|---|
| Medication Summary | Required | Current and relevant past medications, prescriptions, dosage |
| Allergies and Intolerances | Required | Drug, food, and environmental allergies; reactions and severity |
| Problem List | Required | Active diagnoses, conditions, and clinical problems |
| Immunizations | Recommended | Vaccines given, such as tetanus, hepatitis B, influenza, COVID-19 |
| History of Procedures | Recommended | Major surgeries and invasive interventions |
| Medical Devices | Recommended | Implants and devices, such as pacemakers, stents, prostheses |
| Diagnostic Results | Recommended | Key laboratory results, imaging reports, pathology |
| Vital Signs | Optional | Blood pressure, heart rate, weight, height, BMI |
| History of Past Illness | Optional | Resolved conditions and significant past problems |
| Functional Status | Optional | Disabilities and the ability to perform daily activities |
| Plan of Care | Optional | Care plans and treatment recommendations |
| Social History | Optional | Tobacco, alcohol, and other relevant lifestyle factors |
| History of Pregnancy | Optional | Current pregnancy status and pregnancy history |
| Advance Directives | Optional | Living wills, resuscitation preferences, consent statements |
| Alerts | Optional | Safety-critical warnings that do not fit elsewhere (added in FHIR IPS STU 2) |
| Patient Story | Optional | What matters to the patient: needs, strengths, values, concerns, and preferences, in the patient's own terms (added in FHIR IPS STU 2) |
Explicitly saying "nothing" matters. An empty section does not tell a clinician whether the patient has no allergies or whether nobody recorded them. The IPS therefore expects explicit statements such as "no known allergies", "no current medications", or "information not available".
The standards behind the IPS
The IPS is a family of coordinated standards. The ISO and CEN standards define what a patient summary must contain. The HL7 implementation guides define how to encode it.
| Standard | Body | Role |
|---|---|---|
| EN 17269 | CEN (European Committee for Standardization) | The abstract IPS dataset, published in 2019 |
| ISO 27269 | ISO (International Organization for Standardization) | The international version of the abstract IPS dataset, published in 2021 |
| CEN/TS 17288 | CEN | Guidance on implementing the IPS for cross-border use |
| HL7 FHIR IPS Implementation Guide | HL7 International | The modern, API-friendly encoding and the primary implementation format. STU 2 (2.0.x) added the Alerts and Patient Story sections, allowed empty sections, clarified $summary, and moved to the SNOMED CT IPS terminology [9]. |
| HL7 CDA IPS Implementation Guide | HL7 International | The XML document-based encoding, common in existing national and European infrastructures |
The work is coordinated through the Joint Initiative Council for Global Health Informatics Standardization (JIC). The JIC brings together ISO, CEN, HL7, SNOMED International, IHE, and others. The IPS grew out of a 2016 EU–US collaboration on cross-border health data and is now supported by governments and digital-health programs worldwide.
How the IPS is encoded with HL7 FHIR
In FHIR, an IPS is a single Bundle of type document:
Bundle (type = document)
├── Composition ← the "table of contents": header + sections
│ type = LOINC 60591-5 "Patient summary Document"
│ section: Medication Summary (LOINC 10160-0)
│ section: Allergies (LOINC 48765-2)
│ section: Problem List (LOINC 11450-4)
│ section: ...
├── Patient
├── Practitioner / Organization (author, custodian, attester)
├── MedicationStatement / MedicationRequest + Medication
├── AllergyIntolerance
├── Condition
├── Immunization, Procedure, DeviceUseStatement, Observation, ...
└── ...
Key technical points:
- Each section has a human-readable narrative. A clinician can read the IPS in a plain browser, even with no FHIR software.
- Each section also has coded entries, which are structured FHIR resources that software can process, translate, and reconcile.
- Profiles constrain the base FHIR resources. For example, Patient (IPS) and AllergyIntolerance (IPS) define the minimum data and the "must support" elements.
- The
$summaryoperation (GET [base]/Patient/[id]/$summary) asks a FHIR server to generate an IPS for a patient on demand. - The IPS is signable and self-contained. A complete document can be stored, sent, signed, and verified as one unit.
Terminologies
Shared code systems make an IPS readable across languages and countries:
| Terminology | Used for |
|---|---|
| SNOMED CT | Problems, allergies, procedures, devices, clinical findings. A free SNOMED CT IPS Terminology subset is available for IPS use, even in non-member countries. |
| LOINC | Document and section types, laboratory tests, vital signs |
| ATC and other medication code systems | Medicinal products and active substances |
| UCUM | Units of measure |
| ISO and HL7 value sets | Countries, languages, administrative genders, absent and unknown reasons |
Because entries are coded, a receiving system can show an IPS written in Portuguese with English labels. The coded meaning stays the same.
How patients and clinicians use an IPS
An IPS can be produced by an EHR, a national health record service, a patient portal, or a personal health app. It can then be delivered in several ways:
- System to system: through FHIR REST APIs, national infrastructures, or cross-border gateways such as the EU's MyHealth@EU network.
- Patient-mediated sharing: the patient holds the summary in a wallet or health app and shares it on demand.
- SMART Health Links: a QR code or URL that gives a clinician time-limited, optionally passcode-protected access to an encrypted IPS. The clinician can open it in an ordinary web browser.
- Paper or PDF: a printed narrative rendering as a fallback when nothing else works.
Apps such as CommonHealth let patients gather their records and share an IPS through SMART Health Links.
A typical emergency scenario:
- A traveler collapses abroad.
- The traveler, or a companion, shows a QR code from a phone.
- The emergency doctor scans it and sees the traveler's medications, allergies, and active problems in seconds.
- The doctor avoids a dangerous drug interaction and treats the patient safely.
Principles and design choices
- Safety first. Content is chosen for clinical relevance, not completeness.
- Global by default, local by extension. Countries create national profiles, such as EU, Australian, or Canadian variants, that add requirements without breaking the international core.
- Human-readable and machine-processable. Narrative and coded data coexist.
- Free and open. The HL7 IPS specifications and the IPS SNOMED CT subset are freely available to lower barriers to adoption.
- Privacy and consent. Access is governed by local law and patient consent. Mechanisms such as SMART Health Links keep the patient in control.
How to use the IPS
For patients
- Ask for one. Ask your clinic, hospital, national health portal, or health app whether it can produce an IPS or a national patient summary based on it.
- Check it. Read it while you are well. Report anything wrong or missing, especially allergies and medications.
- Keep it with you. Store it in a health app or wallet, as a SMART Health Link QR code, or as a printout in your travel documents.
- Keep it current. Get a new one after a new diagnosis, a new long-term medication, surgery, or an implant.
- Share it on purpose. Show it to the clinician treating you. A SMART Health Link can expire and can require a passcode, so you control who sees it and for how long [10].
For clinicians
- Check the header first. Who wrote it, when, and whether anyone has verified it. An old or unverified summary needs more caution.
- Read the required sections first: allergies, medications, and problems.
- Treat "no known" differently from "not recorded". "No known allergies" is a clinical statement. An empty or "unknown" section is not.
- Confirm critical facts with the patient or their companion whenever you can.
- Use the coded data. Where your system supports it, coded entries let the summary be shown in your language and checked against drug-interaction and allergy rules.
- Do not assume completeness. The IPS is a safety net, not a full history.
For implementers
- Pick the specification. Use the current HL7 FHIR IPS Implementation Guide (STU 2), or your country's national profile of it. For CDA-based infrastructures, use the CDA IPS guide [9] [11].
- Map your data. Map local data to the IPS profiles:
Patient,AllergyIntolerance,MedicationStatement,Condition, and so on. Most of the work is in this mapping. - Map your terminology. Map local codes to SNOMED CT, LOINC, and medication code systems. The SNOMED CT IPS Terminology is free to use for this purpose [12].
- Generate the document. Support the
$summaryoperation, or build theBundleandCompositionyourself. Include a readable narrative for every section, and explicit "no known" or "not available" statements. - Validate it. Check every generated document with the FHIR Validator and a conformance test kit, such as the Inferno IPS Test Kit [13].
- Sign and share it. Decide how documents are signed, stored, and sent: an API, a document registry, a cross-border gateway, or a SMART Health Link.
- Consume it safely. As a receiver, show the narrative even when you cannot process every coded entry, keep the source and author visible, and never silently merge received data into the local record.
- Test with others. Interoperate with other vendors and countries at IHE and HL7 Connectathons before going live.
For governments and health organizations
- Adopt a national profile that builds on the IPS rather than a separate format, so the national summary is international by default [4] [5] [6].
- Settle governance: who may create, update, and attest a summary, and who answers for its accuracy.
- Settle terminology licensing: SNOMED CT membership, or use of the free IPS subset.
- Settle identity, consent, and trust: how patients are identified, how consent is recorded, and which trust framework, such as MyHealth@EU or the WHO Global Digital Health Certification Network, is used to verify documents [1] [14].
- Publish what you have built in the IPS Implementation Registry, so others can learn from it [15].
Integrating the IPS with healthcare systems
An IPS is rarely a separate system. It is a view of data that already lives in EHRs, health information exchanges, national records, and personal health apps.
| Integration pattern | How it works | Examples |
|---|---|---|
| Generated by the EHR | The EHR builds an IPS from its own data on request, often through the FHIR $summary operation. |
EHR vendors and FHIR servers such as HAPI FHIR, which has an IPS generator module |
| National or regional record | A national patient summary service stores a profile of the IPS and makes it available to authorized providers. | Canada's PS-CA, Australia's AU Patient Summary, Switzerland's electronic patient record with CH IPS [4] [5] [6] |
| Cross-border gateway | Each country runs a national contact point. It turns the home country's summary into the agreed exchange format, sends it across the border, and the receiving country shows it in the local language. | MyHealth@EU National Contact Points for eHealth [1] [2] |
| Regional exchange network | Ministries of health exchange IPS documents through national FHIR servers under a shared regional guide. | RACSEL's IPS-LAC and the Pan American Highway for Digital Health (PH4H) in Latin America and the Caribbean [16] |
| Patient-mediated | The patient holds the IPS in an app or wallet and shares it with a QR code or a SMART Health Link. | CommonHealth; the WHO trust network's IPS work for pilgrimage [10] [14] |
| API-based access | Apps fetch an IPS for an authorized patient over a FHIR API. | International Patient Access (IPA); US networks such as Flexpa, which added IPS support under the CMS Interoperability Framework [17] [18] |
Integration points to plan for:
- Document sharing: IHE profiles such as MHD (FHIR) and XDS (document registries) store and find IPS documents. The IHE IPS content profiles add conformance and testing rules [11].
- Patient identity: IHE PIXm and PDQm, or a national identifier, match the patient across systems.
- Existing documents: many systems already produce CDA, C-CDA, or national summaries. Mapping these to the IPS is usually easier than starting again, but check for differences in cardinality, value sets, and code systems.
- National profiles: a national core, such as US Core, AU Core, CH Core, or JP Core, can differ from the IPS. National patient summary profiles reconcile the two [5] [6] [19].
- Translation and display: receivers should render the narrative and translate coded entries using the codes' display names in the receiver's language.
- Security: use TLS, signed documents where required, audit logging (for example IHE ATNA or BALP), and access control tied to consent.
Current adoption
The IPS has moved from pilots to national and regional programs. Status changes quickly, so check the linked sources for the latest position.
- IPS Implementation Registry. The IPS community maintains a public registry of implementations. In mid-2026 it listed 34 entries, from Argentina's provider-mediated IPS-LAC project to Vietnam's Better Health Program [15].
- FHIR ecosystem. In the 2025 State of FHIR survey by HL7 International and Firely, 42 respondents said the IPS underpins their national FHIR specifications, more than any other international guide [20].
- Research. A 2025 study of IPS adoption interviewed stakeholders, who pointed to better quality of care and patient safety as the main benefits [21].
| Country or region | Status |
|---|---|
| European Union and EEA | MyHealth@EU exchanges patient summaries and ePrescriptions between countries. A 2026 European Commission presentation reported 17 Member States plus Norway live, with most of the rest planning to join [2] [22]. The EHDS Regulation makes patient summary exchange mandatory by 2029 [23]. |
| Canada | The pan-Canadian Patient Summary (PS-CA), approved by Canada Health Infoway in October 2022, is built on the IPS with Canadian adaptations [4]. |
| Australia | The AU Patient Summary, built on the IPS and AU Core, is developed by HL7 Australia through the Sparked program [5] [24]. |
| Switzerland | CH IPS 2.0.0 (trial use) from HL7 Switzerland builds on the IPS and CH Core. A separate profile adds what the Swiss electronic patient record needs [6]. |
| United States | No federal mandate for the IPS. The US uses US Core and USCDI. Federal agencies take part in IPS work internationally, and some networks support the IPS voluntarily [18]. |
| Latin America and the Caribbean | RACSEL ministries of health use the regional IPS-LAC guide. In 2023, 16 countries exchanged IPS-LAC documents at a connectathon in São Paulo [16]. |
| Japan | Researchers have built and validated an IPS-based patient summary application for common Japanese use cases, using JP Core [19]. |
| Taiwan and the Philippines | A 2025 implementation report describes a cross-border personal health record using FHIR and aligned with the IPS [25]. |
| G7 | In 2021 the G7 health ministers committed to work towards the IPS and published an IPS roadmap [26]. |
| WHO | The WHO Global Digital Health Certification Network includes IPS-based trust domains, such as verifiable IPS for pilgrimage [14]. |
Laws, regulations, and policy by country and region
The IPS is a standard, not a law. Laws decide whether a country must exchange patient summaries, in what format, and under what privacy rules. This is a summary, not legal advice. Always check the current text of the law.
| Jurisdiction | Law or policy | What it means for the IPS |
|---|---|---|
| European Union | European Health Data Space (EHDS) Regulation, (EU) 2025/327. Published 5 March 2025; in force 26 March 2025 [23] [27]. | Patient summaries are a "priority category". Exchange in the European EHR exchange format must work in every Member State by 2029. Medical images, test results, and discharge reports follow by 2031 [28]. The format for patient summaries is based on the HL7 IPS. |
| European Union | Directive 2011/24/EU on patients' rights in cross-border healthcare [29]. | Created the eHealth Network, which agreed the patient summary guidelines behind MyHealth@EU. |
| European Union | General Data Protection Regulation (GDPR), (EU) 2016/679 [30]. | Health data is a special category. Every IPS exchange needs a lawful basis and appropriate safeguards. |
| United States | 21st Century Cures Act and the information blocking rules [31]; the voluntary CMS Interoperability Framework (2025) [17]. | No law requires the IPS. Laws require access to and exchange of electronic health information, using US Core and USCDI. IPS support is voluntary. |
| Canada | Provincial and territorial health information laws. The federal Connected Care for Canadians Act (Bill C-72) was introduced in 2024 but did not pass before Parliament was prorogued in 2025. | PS-CA is a pan-Canadian specification, not a legal requirement. Adoption is led by provinces and territories with Canada Health Infoway [4]. |
| United Kingdom | Data (Use and Access) Act 2025 [32]. | Includes powers to set information standards for health and adult social care IT. The UK hosted the 2021 G7 IPS commitment [26]. |
| Australia | My Health Records Act 2012 and the 2025 "sharing by default" amendments. | The AU Patient Summary is a national specification developed through Sparked [5] [24]. |
| Switzerland | Federal Act of 19 June 2015 on the Electronic Patient Record (EPRA, SR 816.1), in force since 15 April 2017 [33]. | CH IPS includes a profile for documents in the Swiss electronic patient record [6]. |
| Latin America and the Caribbean | Regional agreements through RACSEL and PH4H, with Inter-American Development Bank support for a regional legal framework [16]. | IPS-LAC is the agreed regional format for cross-border exchange. |
| G7 | Health Ministers' communiqué, Oxford, June 2021, and the G7 IPS Roadmap, December 2021 [26] [34]. | A political commitment to work towards the IPS and patient access, not binding law. |
Pros and cons
| Pros | Cons |
|---|---|
| Safer unplanned care. Clinicians see allergies, medications, and problems in seconds. | Only as good as its source. Out-of-date or wrong source data gives an out-of-date or wrong summary. |
| One format, worldwide. One implementation serves national and cross-border needs. | National variation. National profiles add rules, so a "valid IPS" in one country may need work to be accepted in another. |
| Built on open, mature standards: ISO, CEN, HL7 FHIR and CDA, SNOMED CT, and LOINC. | Terminology burden. Mapping local codes to SNOMED CT and LOINC is hard work, and full SNOMED CT needs a license beyond the free IPS subset. |
| Readable and computable. Narrative for people, coded data for software and translation. | Narrative and coded data can disagree if the generator is careless, and receivers may trust the wrong one. |
| Patient empowerment. Patients can hold and share their own summary. | Privacy and consent risk. A portable summary is sensitive, and laws and consent models differ by country. |
| Free specifications and free IPS terminology lower costs [12]. | Version churn. STU 1, STU 1.1, and STU 2 coexist, and the EHDS format references an earlier version [28]. |
| Reusable for vaccination certificates, research, and registries [7] [8]. | Deliberately minimal. Not a replacement for full records or specialty documents, and gaps for secondary use need extensions [7]. |
| Strong backing from governments, the EU, the G7, WHO, and standards bodies. | Uneven adoption. Many countries and vendors are still piloting, and patient awareness is low. |
Plans and future directions
- EU, 2029: patient summary and ePrescription exchange operational in all EU Member States under the EHDS [23] [28].
- EU, 2031: medical images, laboratory results, and discharge reports join the European EHR exchange format [28].
- MyHealth@EU expansion: more countries joining, and new services for laboratory results, discharge reports, and medical images [2] [22].
- FHIR IPS STU 2 adoption: implementers move to the Alerts and Patient Story sections, explicit empty sections, and SNOMED CT IPS terminology [9].
- Australia: publication of AU Patient Summary Release 1, planned for 2026 [24].
- IPS Best Practices Project: a community effort to document lessons learned, with work starting in 2026.
- WHO trust network: more IPS-based trust domains for verifiable, portable health documents [14].
- SMART Health Links: standardized through HL7, for patient-controlled sharing [10].
- Latin America and the Caribbean: wider IPS-LAC exchange through PH4H [16].
- Research and secondary use: work to extend patient summaries for clinical research and AI, while keeping the core minimal [7].
Glossary
| Term | Meaning |
|---|---|
| IPS | International Patient Summary |
| FHIR | Fast Healthcare Interoperability Resources, HL7's modern API-based standard |
| CDA | Clinical Document Architecture, HL7's XML document standard |
| IG | Implementation Guide, a set of profiles and rules for applying a standard |
| Profile | A constrained version of a FHIR resource for a specific use |
| SNOMED CT | Systematized Nomenclature of Medicine – Clinical Terms |
| LOINC | Logical Observation Identifiers Names and Codes |
| SMART Health Links | A standard for sharing health data through a link or QR code |
| JIC | Joint Initiative Council for Global Health Informatics Standardization |
Learn more
- HL7 FHIR IPS Implementation Guide: https://hl7.org/fhir/uv/ips/
- IPS continuous build: https://build.fhir.org/ig/HL7/fhir-ips/
- International Patient Summary project site: https://international-patient-summary.net/
- ISO 27269 (Health informatics — International patient summary): https://www.iso.org/standard/79491.html
- SNOMED CT IPS Terminology: https://www.snomed.org/international-patient-summary-terminology
- SMART Health Links: https://docs.smarthealthit.org/smart-health-links/
Resources
These links cover sources, specifications, software, projects, videos, books, and research about the IPS. Most were checked when this page was written. A few publisher sites block automated checks, and those are marked (not checked).
Official specifications and standards
- HL7 FHIR IPS Implementation Guide, current published version is the authoritative FHIR specification.
- HL7 FHIR IPS Implementation Guide, STU 2
- HL7 FHIR IPS Implementation Guide, STU 1.1
- HL7 FHIR IPS publication history lists every published version.
- HL7 FHIR IPS continuous build is the latest unballoted work in progress.
- Structure of the International Patient Summary explains the sections and profiles.
- IPS design conventions covers must-support, absent data, and narrative.
- IPS generation and data inclusion covers
$summaryand how to select content. - HL7 CDA IPS Implementation Guide, continuous build
- HL7 CDA IPS product brief
- ISO 27269, Health informatics — International patient summary (not checked)
- ISO/TC 215 Health informatics committee (not checked)
- IHE FHIR International Patient Summary profile (FIIO)
- IHE PCC International Patient Summary supplement, 2020 (PDF)
- HL7 SMART Health Cards and Links Implementation Guide
- SMART Health Links documentation
- HL7 FHIR International Patient Access (IPA) is a sister specification for patient API access.
- HL7 FHIR R4 base specification, which the IPS builds on.
Source repositories
- HL7/fhir-ips holds the FHIR IPS IG source in FHIR Shorthand.
- HL7/cda-ips holds the CDA IPS IG source.
- hl7-eu/eps holds the HL7 Europe Patient Summary source.
- hl7ch/ch-ips holds the Swiss IPS, with a viewer and generator under development.
- GitHub topic: international-patient-summary lists community repositories.
National and regional adaptations
- HL7 Europe Patient Summary (EPS), continuous build
- AU Patient Summary (Australia), continuous build
- Trillium II IPS structure (HL7 Europe) is from the EU–US project that helped start the IPS.
- eHealth Suisse is Switzerland's competence center for digital health and its IPS adoption.
- MyHealth@EU, cross-border digital health services
- Xt-EHR Joint Action prepares the European Health Data Space formats, including the patient summary.
Software and tools
- IPS Viewer (source: jddamore/IPSviewer) is an open-source, browser-based IPS viewer.
- uwcirg/shl-ips-viewer views an IPS shared through a SMART Health Link.
- smart-on-fhir/smart-health-links is the reference implementation of SMART Health Links.
- HAPI FHIR IPS generator (source: hapifhir/hapi-fhir) is an open-source Java server module that implements
$summary. - HAPI FHIR JPA server IPS documentation
- Inferno IPS Test Kit (source: inferno-framework/ips-test-kit) is an open-source conformance test kit.
- FHIR Validator validates IPS bundles against the IG profiles.
- Simplifier: hl7.fhir.uv.ips package has the package, profiles, and examples.
- FHIR package registry
- FHIR Shorthand (FSH) School teaches the language the IPS IG is written in.
- CommonHealth is a patient app that generates an IPS and shares it through SMART Health Links.
- WHO SMART Trust is the trust framework for the WHO Global Digital Health Certification Network.
Organizations and projects
- International Patient Summary project site has news, adoption reports, and education.
- IPS for health IT developers
- HL7 International
- IHE International
- SNOMED International
- SNOMED CT IPS Terminology is a free subset for IPS use.
- LOINC (not checked)
- Joint Initiative Council for Global Health Informatics Standardization (JIC)
- Global Digital Health Partnership (GDHP)
- WHO SMART Guidelines
- WHO Global Digital Health Certification Network
Community and events
- chat.fhir.org is the FHIR community chat, which has an active IPS stream.
- HL7 FHIR Connectathons
- IHE Connectathons
Videos
- HIMSS20: IPS for computable care guidelines in 200 seconds or less (IHE International, YouTube)
- IHE International YouTube channel has Connectathon panels and IPS sessions.
- IPS project site news links to many recorded webinars, including:
- the IPS panel at the IHE North America Connectathon, 2024
- the IPS session at FHIR DevDays 2023
- Grahame Grieve on IPS and IPA, IHE Connectathon Montreux 2022
- the SNOMED CT Expo 2022 keynote
- Matthew Rahn on IPS in the GDHP
- the HL7 "Global Passport" cross-border webinar
- YouTube search: International Patient Summary
Books
- Tim Benson and Grahame Grieve, Principles of Health Interoperability: FHIR, HL7 and SNOMED CT, 4th edition, Springer, 2020. It covers FHIR, clinical summary resources, and terminology.
Research papers and articles
- Laleci Erturkmen G. B., Sinaci A. A., Namli T., Boonstra M., et al., "An assessment of the European Patient Summary for clinical research: a case study in cardiology", Frontiers in Medicine, 2024.
- Lee H., Huang J., Huang S., Chen W., et al., "Implementing a Cross-Border Next-Generation Personal Health Record in the Philippines and Taiwan: An Implementation Case Report Using Health Level 7 International Fast Healthcare Interoperability Resources", JMIR Formative Research, 2025.
- Song C., Nakayama M., "Implementation of a Patient Summary Web Application According to the International Patient Summary and Validation in Common Use Cases in Japan", Journal of Medical Systems, 2023.
- Schippers D., Spil T., Stegwee R., Folmer E., Donnelly S., "The adoption and diffusion of the International Patient Summary", Proceedings of the 58th Hawaii International Conference on System Sciences (HICSS), 2025.
- da Silva Carvalho N., Papadimitriou A., Stegwee R., Gille H., et al., "Accelerating European electronic health record exchange format (EEHRxF) implementation across Europe: a policy perspective", Frontiers in Medicine, 2025.
- Kay S., Cangioli G., Nusbaum M., "The International Patient Summary and the extensibility requirement", Studies in Health Technology and Informatics (pHealth), 2020.
- D'Amore J., Cangioli G., Hausam R., "Advancing the International Patient Summary"
- "Towards the Austrian Patient Summary", Studies in Health Technology and Informatics (dHealth).
- "Revival of the International Patient Summary (IPS)", Smile Digital Health blog.
- PubMed search: "international patient summary" for peer-reviewed literature.
References
Numbered citations in the text, such as [1], link to the matching entry below. The links were checked in November 2026. Laws, adoption figures, and versions change, so check the source for the current position.
- European Commission. "Electronic cross-border health services (MyHealth@EU)". Directorate-General for Health and Food Safety.
- European Commission. "My rights over my health data". Directorate-General for Health and Food Safety.
- World Health Organization. "Global Digital Health Certification Network".
- Canada Health Infoway. "What is IPS and Patient Summary? Pan-Canadian Patient Summary (PS-CA)". InfoScribe.
- HL7 Australia. "AU Patient Summary Implementation Guide".
- HL7 Switzerland. "CH IPS (R4) Implementation Guide".
- Laleci Erturkmen G. B., Sinaci A. A., Namli T., Boonstra M., et al. "An assessment of the European Patient Summary for clinical research: a case study in cardiology". Frontiers in Medicine, 2024. doi:10.3389/fmed.2024.1481551.
- World Health Organization. "GDHCN Trust Network: Personal Health Wallet". Continuous build.
- HL7 International. "International Patient Summary Implementation Guide: Changes".
- HL7 International. "SMART Health Cards and Links Implementation Guide".
- IHE International. "FHIR International Patient Summary (FIIO)". IHE Patient Care Coordination.
- SNOMED International. "SNOMED CT International Patient Summary Terminology".
- Inferno. "International Patient Summary Test Kit".
- World Health Organization. "WHO SMART Trust Implementation Guide".
- International Patient Summary project. "IPS Implementation Registry".
- International Patient Summary project. "IPS in the Latin America and Caribbean region".
- Centers for Medicare & Medicaid Services. "Interoperability Framework".
- Flexpa. "CMS Aligned Network". Documentation.
- Song C., Nakayama M. "Implementation of a Patient Summary Web Application According to the International Patient Summary and Validation in Common Use Cases in Japan". Journal of Medical Systems, 2023. doi:10.1007/s10916-023-01993-6.
- D'Amore J. "State of FHIR IPS". AMIA 2025 Annual Symposium (slides).
- Schippers D., Spil T., Stegwee R., Folmer E., Donnelly S. "The adoption and diffusion of the International Patient Summary". Proceedings of the 58th Hawaii International Conference on System Sciences (HICSS), 2025. doi:10.24251/hicss.2025.425.
- Raffaelli F. "European Health Data Space". European Commission, IHE Europe Experience Days 2026 (slides).
- European Commission. "European Health Data Space Regulation (EHDS)".
- CSIRO Sparked. "Australian Patient Summary (AU PS)".
- Lee H., Huang J., Huang S., Chen W., et al. "Implementing a Cross-Border Next-Generation Personal Health Record in the Philippines and Taiwan: An Implementation Case Report Using Health Level 7 International Fast Healthcare Interoperability Resources". JMIR Formative Research, 2025. doi:10.2196/56272.
- G7. "G7 International Patient Summary Roadmap". UK Department of Health and Social Care, December 2021.
- European Union. "Regulation (EU) 2025/327 on the European Health Data Space". Official Journal of the European Union, 5 March 2025.
- da Silva Carvalho N., Papadimitriou A., Stegwee R., Gille H., et al. "Accelerating European electronic health record exchange format (EEHRxF) implementation across Europe: a policy perspective". Frontiers in Medicine, 2025. doi:10.3389/fmed.2025.1648170.
- European Union. "Directive 2011/24/EU on the application of patients' rights in cross-border healthcare". Official Journal of the European Union, 2011.
- European Union. "Regulation (EU) 2016/679, the General Data Protection Regulation". Official Journal of the European Union, 2016.
- Assistant Secretary for Technology Policy (ASTP/ONC). "Information Blocking". HealthIT.gov.
- UK Parliament. "Data (Use and Access) Act 2025". legislation.gov.uk.
- eHealth Suisse. "eHealth Suisse: competence and coordination centre of the Confederation and the cantons". For the Act itself, search for SR 816.1 on Fedlex.
- UK Department of Health and Social Care. "G7 patient access to health records: final report". GOV.UK, 2021.
Further reading
These sources are not cited above, but are the primary references for the standard itself.
- ISO. "ISO 27269: Health informatics — International patient summary". 2021.
- CEN. "EN 17269: Health informatics — The International Patient Summary". 2019.
- CEN. "CEN/TS 17288: Health informatics — The International Patient Summary: Guideline for European implementation".
- HL7 International. "International Patient Summary Implementation Guide (FHIR)".
- HL7 International. "International Patient Summary Implementation Guide (CDA), continuous build".
- HL7 International. "Structure of the International Patient Summary".
- IHE International. "IHE PCC International Patient Summary supplement (PDF)". 2020.
- HL7 International. "International Patient Access (IPA)".
- HL7 Europe. "HL7 Europe Patient Summary (EPS), continuous build".
- International Patient Summary project. "international-patient-summary.net".
- Benson T., Grieve G. Principles of Health Interoperability: FHIR, HL7 and SNOMED CT. 4th edition. Springer, 2020.