International Patient Summary (IPS)

The warldwide staundart fur sharin key health data athort borders.

The International Patient Summary (IPS) is a warldwide staundart for a short electronic health record extract. It haulds the basic clinical facts a clinician needs tae treat a patient safely.

Leid: العربية, Български, भोजपुरी, বাংলা, Č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 warldwide staundart for a short electronic health record extract. It haulds the basic clinical facts a clinician needs tae treat a patient safely. It is designed tae be:

  • Minimal an no exhaustive. It is a sma, curated subset o a health record, no the hail record.
  • Specialty-agnostic. Onie clinician can uise it, in onie discipline.
  • Condition-independent. It is no tied tae a parteecular disease or care pathwey.
  • Implementable an international. It is biggit on global staundarts an terminologies, sae it can be uised athort kintras, leids, an IT seistems.

In short, the IPS answers ae question for a clinician wha haesnae iver met the patient: "Whit dae A need tae ken the nou tae tak tent o this body safely?"

Whit the IPS is for

Health information is uisually lockit inside a local electronic health record (EHR), a national seistem, or a vendor's product. Whan a patient seeks care somewhaur else, sic as anither hospital, region, or kintra, the treatin clinician aften haes nae access tae that history. The IPS gies iverybodie ae shared, portable summary format.

Core uise cases

Uise case Description
Unscheduled an emergency care A patient taks ill or is hurt awa frae hame, an local clinicians canna reach the patient's hame EHR. This is the original, main uise case.
Cross-border care Traivellers, migrants, cross-border warkers, an refugees cairry a summary that clinicians abroad can read.
Planned care an transitions Referrals, specialist consultations, admissions, discharges, an haundovers atween providers.
Medical tourism an mobility Patients that chuise tae get care in anither jurisdiction.
Patient empowerment Patients haud, view, an share thair ain summary frae a phone app, a portal, or a printit copy.

Whan tae uise the IPS

Uise the IPS whan somebodie wha disnae ken the patient needs a trustworthy snapshot quick, an whan the sender an receiver dinnae share an IT seistem.

Guid fits

  • Emergency an unplanned care, especially awa frae hame or athort a border. This is the uise the IPS wis designed for.
  • Cross-border exchange atween national seistems, sic as the EU's MyHealth@EU service [1] [2].
  • Patient-haudit summaries that traivellers, migrants, refugees, pilgrims, or fowk wi complex conditions cairry on a phone or on paper [3].
  • A national or regional patient summary. Mony kintras big thair ain summary as a profile o the IPS, sae it can an aw be exchanged internationally [4] [5] [6].
  • A common baseline for care transitions, sic as referrals, admissions, an discharges, whan a richer specialised document isnae available.
  • A stairtin pynt for ither datasets, sic as vaccination certificates, research data, or registries that need the same core facts [7] [8].

Puir fits

  • The hail medical record. The IPS is deliberately minimal. Uise a fou record export or a specialised document whan detail maitters.
  • Specialty-specific documents, sic as an oncology treatment summary, a maternity record, or a detailed discharge summary. These hae thair ain staundarts, that can include or reference IPS content.
  • Real-time clinical workflaws inside ae organisation. Inside a single EHR, query the live data raither than a summary snapshot.
  • Legal, billin, or insurance records. The IPS is a clinical summary, no an administrative or claims record.
  • Decisions that need guaranteed completeness. An IPS is anerly as complete an current as its source an its author. Aye confirm critical facts wi the patient whan possible.

Whit an IPS contains

An IPS document haes twa layers:

  1. A header that records wha, whit, an whan:

    • Patient: identity, demographics, an contacts.
    • Author: the body, organisation, or seistem that made the summary.
    • Custodian: the organisation responsible for keepin it.
    • Attester: wha haes verified it, if onybodie.
    • Date an time: whan it wis creatit.
  2. A clinical body organised intae sections. Sections are required, recommended, or optional.

Section Status Typical content
Medication Summary Required Current an relevant past medications, prescriptions, dosage
Allergies and Intolerances Required Drug, food, an environmental allergies; reactions an severity
Problem List Required Active diagnoses, conditions, an clinical problems
Immunizations Recommended Vaccines gien, sic as tetanus, hepatitis B, influenza, COVID-19
History of Procedures Recommended Major surgeries an invasive interventions
Medical Devices Recommended Implants an devices, sic as pacemakers, stents, prostheses
Diagnostic Results Recommended Key laboratory results, imaging reports, pathology
Vital Signs Optional Bluid pressure, hert rate, wecht, hicht, BMI
History of Past Illness Optional Resolved conditions an significant past problems
Functional Status Optional Disabilities an the abeility tae dae daily activities
Plan of Care Optional Care plans an treatment recommendations
Social History Optional Tobacco, alcohol, an ither relevant lifestyle factors
History of Pregnancy Optional Current pregnancy status an pregnancy history
Advance Directives Optional Living wills, resuscitation preferences, consent statements
Alerts Optional Safety-critical warnins that dinnae fit elsewhaur (addit in FHIR IPS STU 2)
Patient Story Optional Whit maitters tae the patient: needs, strenths, values, concerns, an preferences, in the patient's ain terms (addit in FHIR IPS STU 2)

Sayin "naething" explicitly maitters. An teem section disnae tell a clinician whether the patient haes nae allergies or whether naebodie recordit them. The IPS therefore expects explicit statements sic as "no kent allergies", "nae current medications", or "information no available".

The staundarts ahint the IPS

The IPS is a faimily o coordinatit staundarts. The ISO an CEN staundarts define whit a patient summary maun contain. The HL7 implementation guides define hou tae 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 o the abstract IPS dataset, published in 2021
CEN/TS 17288 CEN Guidance on implementin the IPS for cross-border uise
HL7 FHIR IPS Implementation Guide HL7 International The modern, API-friendly encodin an the main implementation format. STU 2 (2.0.x) addit the Alerts an Patient Story sections, allowed teem sections, clarified $summary, an muived tae the SNOMED CT IPS terminology [9].
HL7 CDA IPS Implementation Guide HL7 International The XML document-based encodin, common in existin national an European infrastructures

The wark is coordinatit throu the Joint Initiative Council for Global Health Informatics Standardization (JIC). The JIC brings thegither ISO, CEN, HL7, SNOMED International, IHE, an ithers. The IPS grew oot o a 2016 EU–US collaboration on cross-border health data an is nou supportit by govrenments an digital-health programmes warldwide.

Hou the IPS is encodit wi HL7 FHIR

In FHIR, an IPS is a single Bundle o 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 pynts:

  • Ilka section haes a human-readable narrative. A clinician can read the IPS in a plain broser, even wi nae FHIR software.
  • Ilka section an aw haes coded entries, that are structurit FHIR resources that software can process, translate, an reconcile.
  • Profiles constrain the base FHIR resources. For example, Patient (IPS) an AllergyIntolerance (IPS) define the minimum data an the "must support" elements.
  • The $summary operation (GET [base]/Patient/[id]/$summary) speirs a FHIR server tae generate an IPS for a patient on demand.
  • The IPS is signable an self-contained. A complete document can be stored, sent, signed, an verified as ae unit.

Terminologies

Shared code seistems mak an IPS readable athort leids an kintras:

Terminology Used for
SNOMED CT Problems, allergies, procedures, devices, clinical findins. A free SNOMED CT IPS Terminology subset is available for IPS uise, even in non-member kintras.
LOINC Document an section types, laboratory tests, vital signs
ATC an ither medication code seistems Medicinal products an active substances
UCUM Units o measure
ISO and HL7 value sets Kintras, leids, administrative genders, absent an unkent reasons

Acause entries are coded, a receivin seistem can shaw an IPS written in Portuguese wi English labels. The coded meanin bides the same.

Hou patients an clinicians uise an IPS

An IPS can be made by an EHR, a national health record service, a patient portal, or a personal health app. It can than be delivered in a wheen o weys:

  • System tae seistem: throu FHIR REST APIs, national infrastructures, or cross-border gateweys sic as the EU's MyHealth@EU network.
  • Patient-mediated sharin: the patient haulds the summary in a wallet or health app an shares it on demand.
  • SMART Health Links: a QR code or URL that gies a clinician time-limitit, optionally passcode-protectit access tae an encryptit IPS. The clinician can apen it in an ordinary wab broser.
  • Paper or PDF: a printit narrative rendering as a fallback whan naething else warks.

Apps sic as CommonHealth let patients gaither thair records an share an IPS throu SMART Health Links.

A typical emergency scenario:

  1. A traiveller collapses abroad.
  2. The traiveller, or a companion, shaws a QR code frae a phone.
  3. The emergency doctor scans it an sees the traiveller's medications, allergies, an active problems in seconds.
  4. The doctor avoids a dangerous drug interaction an treats the patient safely.

Principles an design chyces

  • Safety first. Content is chosen for clinical relevance, no completeness.
  • Global by default, local by extension. Kintras mak national profiles, sic as EU, Australian, or Canadian variants, that add requirements wioot braekin the international core.
  • Human-readable an machine-processable. Narrative an coded data coexist.
  • Free an apen. The HL7 IPS specifications an the IPS SNOMED CT subset are freely available tae lower barriers tae adoption.
  • Privacy an consent. Access is governed by local law an patient consent. Mechanisms sic as SMART Health Links keep the patient in control.

Hou tae uise the IPS

For patients

  1. Spier for ane. Spier yer clinic, hospital, national health portal, or health app whether it can mak an IPS or a national patient summary based on it.
  2. Check it. Read it while ye are weel. Report onything wrang or missin, especially allergies an medications.
  3. Keep it wi ye. Store it in a health app or wallet, as a SMART Health Link QR code, or as a printoot in yer traivel documents.
  4. Keep it current. Get a new ane efter a new diagnosis, a new lang-term medication, surgery, or an implant.
  5. Share it on purpose. Shaw it tae the clinician treatin ye. A SMART Health Link can expire an can require a passcode, sae ye control wha sees it an for hou lang [10].

For clinicians

  1. Check the header first. Wha wrate it, whan, an whether onybodie haes verified it. An auld or unverified summary needs mair caution.
  2. Read the required sections first: allergies, medications, an problems.
  3. Treat "no kent" differently frae "no recordit". "No kent allergies" is a clinical statement. A teem or "unkent" section isnae.
  4. Confirm critical facts wi the patient or thair companion whaniver ye can.
  5. Uise the coded data. Whaur yer seistem supports it, coded entries let the summary be shawn in yer leid an checked against drug-interaction an allergy rules.
  6. Dinnae assume completeness. The IPS is a safety nit, no a fou history.

For implementers

  1. Pick the specification. Uise the current HL7 FHIR IPS Implementation Guide (STU 2), or yer kintra's national profile o it. For CDA-based infrastructures, uise the CDA IPS guide [9] [11].
  2. Map yer data. Map local data tae the IPS profiles: Patient, AllergyIntolerance, MedicationStatement, Condition, an sae on. Maist o the wark is in this mappin.
  3. Map yer terminology. Map local codes tae SNOMED CT, LOINC, an medication code seistems. The SNOMED CT IPS Terminology is free tae uise for this purpose [12].
  4. Generate the document. Support the $summary operation, or big the Bundle an Composition yersel. Include a readable narrative for ilka section, an explicit "no kent" or "no available" statements.
  5. Validate it. Check ilka generatit document wi the FHIR Validator an a conformance test kit, sic as the Inferno IPS Test Kit [13].
  6. Sign an share it. Decide hou documents are signed, stored, an sent: an API, a document registry, a cross-border gateweay, or a SMART Health Link.
  7. Consume it safely. As a receiver, shaw the narrative even whan ye canna process ilka coded entry, keep the source an author veesible, an niver quietly merge receivit data intae the local record.
  8. Test wi ithers. Interoperate wi ither vendors an kintras at IHE an HL7 Connectathons afore gaun live.

For govrenments an health organisations

  1. Adopt a national profile that biggs on the IPS raither than a separate format, sae the national summary is international by default [4] [5] [6].
  2. Settle governance: wha can mak, update, an attest a summary, an wha answers for its accuracy.
  3. Settle terminology licensin: SNOMED CT membership, or uise o the free IPS subset.
  4. Settle identity, consent, an trust: hou patients are identified, hou consent is recordit, an whilk trust framewark, sic as MyHealth@EU or the WHO Global Digital Health Certification Network, is uised tae verify documents [1] [14].
  5. Publish whit ye hae biggit in the IPS Implementation Registry, sae ithers can lairn frae it [15].

Integratin the IPS wi healthcare seistems

An IPS is seldom a separate seistem. It is a view o data that aareadies lives in EHRs, health information exchanges, national records, an personal health apps.

Integration pattern How it works Examples
Generated by the EHR The EHR biggs an IPS frae its ain data on request, aften throu the FHIR $summary operation. EHR vendors an FHIR servers sic as HAPI FHIR, that haes an IPS generator module
National or regional record A national patient summary service stores a profile o the IPS an maks it available tae authorised providers. Canada's PS-CA, Australia's AU Patient Summary, Switzerland's electronic patient record wi CH IPS [4] [5] [6]
Cross-border gateway Ilka kintra rins a national contact pynt. It turns the hame kintra's summary intae the agreed exchange format, sends it athort the border, an the receivin kintra shaws it in the local leid. MyHealth@EU National Contact Points for eHealth [1] [2]
Regional exchange network Ministries o health exchange IPS documents throu national FHIR servers unner a shared regional guide. RACSEL's IPS-LAC an the Pan American Highway for Digital Health (PH4H) in Latin America an the Caribbean [16]
Patient-mediated The patient haulds the IPS in an app or wallet an shares it wi a QR code or a SMART Health Link. CommonHealth; the WHO trust network's IPS wark for pilgrimage [10] [14]
API-based access Apps fetch an IPS for an authorised patient ower a FHIR API. International Patient Access (IPA); US networks sic as Flexpa, that addit IPS support unner the CMS Interoperability Framework [17] [18]

Integration pynts tae plan for:

  • Document sharin: IHE profiles sic as MHD (FHIR) an XDS (document registries) store an finnd IPS documents. The IHE IPS content profiles add conformance an testin rules [11].
  • Patient identity: IHE PIXm an PDQm, or a national identifier, match the patient athort seistems.
  • Existin documents: mony seistems aareadies mak CDA, C-CDA, or national summaries. Mappin thir tae the IPS is uisually easier nor stairtin again, but check for differences in cardinality, value sets, an code seistems.
  • National profiles: a national core, sic as US Core, AU Core, CH Core, or JP Core, can differ frae the IPS. National patient summary profiles reconcile the twa [5] [6] [19].
  • Translation an display: receivers shoud render the narrative an translate coded entries uisin the codes' display names in the receiver's leid.
  • Security: uise TLS, signed documents whaur required, audit loggin (for example IHE ATNA or BALP), an access control tied tae consent.

Current adoption

The IPS haes muived frae pilots tae national an regional programmes. Status chynges quick, sae check the linked sources for the latest position.

  • IPS Implementation Registry. The IPS community keeps a public registry o implementations. In mid-2026 it listit 34 entries, frae Argentina's provider-mediated IPS-LAC project tae Vietnam's Better Health Program [15].
  • FHIR ecosystem. In the 2025 State of FHIR survey by HL7 International an Firely, 42 respondents said the IPS underpins thair national FHIR specifications, mair nor onie ither international guide [20].
  • Research. A 2025 study o IPS adoption interviewed stakeholders, wha pyntit tae better quality o care an patient safety as the main benefits [21].
Country or region Status
European Union and EEA MyHealth@EU exchanges patient summaries an ePrescriptions atween kintras. A 2026 European Commission presentation reportit 17 Member States plus Norway live, wi maist o the rest plannin tae jyne [2] [22]. The EHDS Regulation maks patient summary exchange mandatory by 2029 [23].
Canada The pan-Canadian Patient Summary (PS-CA), approvit by Canada Health Infoway in October 2022, is biggit on the IPS wi Canadian adaptations [4].
Australia The AU Patient Summary, biggit on the IPS an AU Core, is developit by HL7 Australia throu the Sparked programme [5] [24].
Switzerland CH IPS 2.0.0 (trial use) frae HL7 Switzerland biggs on the IPS an CH Core. A separate profile adds whit the Swiss electronic patient record needs [6].
United States Nae federal mandate for the IPS. The US uises US Core an USCDI. Federal agencies tak pairt in IPS wark internationally, an some networks support the IPS voluntarily [18].
Latin America and the Caribbean RACSEL ministries o health uise the regional IPS-LAC guide. In 2023, 16 kintras exchanged IPS-LAC documents at a connectathon in São Paulo [16].
Japan Researchers hae biggit an validatit an IPS-based patient summary application for common Japanese uise cases, uisin JP Core [19].
Taiwan and the Philippines A 2025 implementation report describes a cross-border personal health record uisin FHIR an alignit wi the IPS [25].
G7 In 2021 the G7 health ministers committit tae wark towards the IPS an publishit an IPS roadmap [26].
WHO The WHO Global Digital Health Certification Network includes IPS-based trust domains, sic as verifiable IPS for pilgrimage [14].

Laws, regulations, an policy by kintra an region

The IPS is a staundart, no a law. Laws decide whether a kintra maun exchange patient summaries, in whit format, an unner whit privacy rules. This is a summary, no legal advice. Aye check the current text o 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 maun wark in ilka Member State by 2029. Medical images, test results, an discharge reports follae 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]. Creatit the eHealth Network, that agreed the patient summary guidelines ahint MyHealth@EU.
European Union General Data Protection Regulation (GDPR), (EU) 2016/679 [30]. Health data is a special category. Ilka IPS exchange needs a lawfu basis an appropriate safeguards.
United States 21st Century Cures Act and the information blocking rules [31]; the voluntary CMS Interoperability Framework (2025) [17]. Nae law requires the IPS. Laws require access tae an exchange o electronic health information, uisin US Core an USCDI. IPS support is voluntary.
Canada Provincial an territorial health information laws. The federal Connected Care for Canadians Act (Bill C-72) wis introduced in 2024 but didnae pass afore Parliament wis prorogued in 2025. PS-CA is a pan-Canadian specification, no a legal requirement. Adoption is led by provinces an territories wi Canada Health Infoway [4].
United Kingdom Data (Use and Access) Act 2025 [32]. Includes pouers tae set information staundarts for health an adult social care IT. The UK hostit the 2021 G7 IPS commitment [26].
Australia My Health Records Act 2012 an the 2025 "sharing by default" amendments. The AU Patient Summary is a national specification developit throu 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 throu RACSEL an PH4H, wi Inter-American Development Bank support for a regional legal framewark [16]. IPS-LAC is the agreed regional format for cross-border exchange.
G7 Health Ministers' communiqué, Oxford, June 2021, an the G7 IPS Roadmap, December 2021 [26] [34]. A political commitment tae wark towards the IPS an patient access, no bindin law.

Pros an cons

Pros Cons
Safer unplanned care. Clinicians see allergies, medications, an problems in seconds. Anerly as guid as its source. Oot-o-date or wrang source data gies an oot-o-date or wrang summary.
Ae format, warldwide. Ae implementation serves national an cross-border needs. National variation. National profiles add rules, sae a "valid IPS" in ae kintra micht need wark tae be acceptit in anither.
Biggit on apen, mature staundarts: ISO, CEN, HL7 FHIR an CDA, SNOMED CT, an LOINC. Terminology burden. Mappin local codes tae SNOMED CT an LOINC is hard wark, an fou SNOMED CT needs a licence ayont the free IPS subset.
Readable an computable. Narrative for fowk, coded data for software an translation. Narrative an coded data can disagree if the generator is careless, an receivers micht trust the wrang ane.
Patient empowerment. Patients can haud an share thair ain summary. Privacy an consent risk. A portable summary is sensitive, an laws an consent models differ by kintra.
Free specifications an free IPS terminology lower costs [12]. Version churn. STU 1, STU 1.1, an STU 2 coexist, an the EHDS format references an earlier version [28].
Reusable for vaccination certificates, research, an registries [7] [8]. Deliberately minimal. No a replacement for fou records or specialty documents, an gaps for seicondary uise need extensions [7].
Strang backin frae govrenments, the EU, the G7, WHO, an staundarts bodies. Uneven adoption. Mony kintras an vendors are still pilotin, an patient awaurness is law.

Plans an future directions

  • EU, 2029: patient summary an ePrescription exchange operational in aw EU Member States unner the EHDS [23] [28].
  • EU, 2031: medical images, laboratory results, an discharge reports jyne the European EHR exchange format [28].
  • MyHealth@EU expansion: mair kintras jynin, an new services for laboratory results, discharge reports, an medical images [2] [22].
  • FHIR IPS STU 2 adoption: implementers muive tae the Alerts an Patient Story sections, explicit teem sections, an SNOMED CT IPS terminology [9].
  • Australia: publication o AU Patient Summary Release 1, plannit for 2026 [24].
  • IPS Best Practices Project: a community effort tae document lessons lairnt, wi wark stairtin in 2026.
  • WHO trust network: mair IPS-based trust domains for verifiable, portable health documents [14].
  • SMART Health Links: staundardised throu HL7, for patient-controlled sharin [10].
  • Latin America and the Caribbean: wider IPS-LAC exchange throu PH4H [16].
  • Research an seicondary uise: wark tae extend patient summaries for clinical research an AI, while keepin the core minimal [7].

Glossary

Term Meaning
IPS International Patient Summary
FHIR Fast Healthcare Interoperability Resources, HL7's modern API-based staundart
CDA Clinical Document Architecture, HL7's XML document staundart
IG Implementation Guide, a set o profiles an rules for applyin a staundart
Profile A constrained version o a FHIR resource for a specific uise
SNOMED CT Systematized Nomenclature of Medicine – Clinical Terms
LOINC Logical Observation Identifiers Names and Codes
SMART Health Links A staundart for sharin health data throu a link or QR code
JIC Joint Initiative Council for Global Health Informatics Standardization

Learn mair

Resources

Thir links cover sources, specifications, software, projects, videos, beuks, an research aboot the IPS. Maist wur checked whan this page wis written. A few publisher sites block automatit checks, an thae are markit (no checked).

Official specifications an staundarts

Source repositories

National an regional adaptations

Software an tools

Organisations an projects

Community an events

Videos

Beuks

Research papers an articles

References

Numbered citations in the text, sic as [1], link tae the matchin entry ablow. The links wur checked in November 2026. Laws, adoption figures, an versions chynge, sae check the source for the current position.

  1. European Commission. "Electronic cross-border health services (MyHealth@EU)". Directorate-General for Health and Food Safety.
  2. European Commission. "My rights over my health data". Directorate-General for Health and Food Safety.
  3. World Health Organization. "Global Digital Health Certification Network".
  4. Canada Health Infoway. "What is IPS and Patient Summary? Pan-Canadian Patient Summary (PS-CA)". InfoScribe.
  5. HL7 Australia. "AU Patient Summary Implementation Guide".
  6. HL7 Switzerland. "CH IPS (R4) Implementation Guide".
  7. 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.
  8. World Health Organization. "GDHCN Trust Network: Personal Health Wallet". Continuous build.
  9. HL7 International. "International Patient Summary Implementation Guide: Changes".
  10. HL7 International. "SMART Health Cards and Links Implementation Guide".
  11. IHE International. "FHIR International Patient Summary (FIIO)". IHE Patient Care Coordination.
  12. SNOMED International. "SNOMED CT International Patient Summary Terminology".
  13. Inferno. "International Patient Summary Test Kit".
  14. World Health Organization. "WHO SMART Trust Implementation Guide".
  15. International Patient Summary project. "IPS Implementation Registry".
  16. International Patient Summary project. "IPS in the Latin America and Caribbean region".
  17. Centers for Medicare & Medicaid Services. "Interoperability Framework".
  18. Flexpa. "CMS Aligned Network". Documentation.
  19. 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.
  20. D'Amore J. "State of FHIR IPS". AMIA 2025 Annual Symposium (slides).
  21. 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.
  22. Raffaelli F. "European Health Data Space". European Commission, IHE Europe Experience Days 2026 (slides).
  23. European Commission. "European Health Data Space Regulation (EHDS)".
  24. CSIRO Sparked. "Australian Patient Summary (AU PS)".
  25. 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.
  26. G7. "G7 International Patient Summary Roadmap". UK Department of Health and Social Care, December 2021.
  27. European Union. "Regulation (EU) 2025/327 on the European Health Data Space". Official Journal of the European Union, 5 March 2025.
  28. 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.
  29. European Union. "Directive 2011/24/EU on the application of patients' rights in cross-border healthcare". Official Journal of the European Union, 2011.
  30. European Union. "Regulation (EU) 2016/679, the General Data Protection Regulation". Official Journal of the European Union, 2016.
  31. Assistant Secretary for Technology Policy (ASTP/ONC). "Information Blocking". HealthIT.gov.
  32. UK Parliament. "Data (Use and Access) Act 2025". legislation.gov.uk.
  33. 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.
  34. UK Department of Health and Social Care. "G7 patient access to health records: final report". GOV.UK, 2021.

Further reading

Thir sources arenae citit abune, but are the main references for the staundart itsel.