Unattributed Code Systems

Copyright Fragment

This fragment is available on download.html

This publication includes IP covered under the following statements.

Copyright and Registered Trademark Uses

External References

Type Reference Content
web profiles.ihe.net
web profiles.ihe.net
web github.com FHIR International Patient Summary, published by IHE Patient Care Coordination Committee. This guide is not an authorized publication; it is the continuous build for version 1.0.0-comment built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/PCC.FIIO/ and changes regularly. See the Directory of published versions
web www.ihe.net IG © 2021+ IHE Patient Care Coordination Committee . Package ihe.pcc.fiio#1.0.0-comment based on FHIR 4.0.1 . Generated 2026-03-05
Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web github.com Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web github.com Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web profiles.ihe.net Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web www.ihe.net Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web tel:+310688632663 +31 0688632663
web tel:+310610543759 +31 0610543759
web tel:+310614656370 telecom : +31 0614656370 , fax: (555) 123-4567
web tel:+16305712670 telecom : +1 6305712670
web tel:+33253848811 telecom : +33 253848811 , +33 346082142 , IhePcc@example.com
web tel:+33346082142 telecom : +33 253848811 , +33 346082142 , IhePcc@example.com
web tel:+43054376846 telecom : +43 054376846 , +43 190840858 , IhePcc@example.com
web tel:+43190840858 telecom : +43 054376846 , +43 190840858 , IhePcc@example.com
web tel:+395449150748 +39 5449150748
web en.wikipedia.org Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ).
web wiki.ihe.net This is a metadata field from XDS/MHD .
web github.com The source code for this Implementation Guide can be found on th IHE PCC GitHub
web www.iso.org ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
Show Usage
web ucum.org The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Show Usage
web profiles.ihe.net IHE uses the normative words: "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" according to standards conventions .
web profiles.ihe.net The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z .
web www.ihe.net This profile was originally a segment of the IHE International Patient Summary (IPS) Rev 1.2 Trial Implementation Profile , which combined the profiling of both the HL7 FHIR International Patient Summary Implementation Guide and the HL7 CDA International Patient Summary Implementation Guide for conformance testing at the IHE Connectathons.
web github.com IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted to the Patient Care Coordination Public Comment form .
web www.ihe.net IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted to the Patient Care Coordination Public Comment form .
web github.com As issues are submitted they will be managed at FHIR International Patient Summary GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web wiki.ihe.net As issues are submitted they will be managed at FHIR International Patient Summary GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web www.ihe.net As issues are submitted they will be managed at FHIR International Patient Summary GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web www.iso.org FIPS_001: Review of the synergy between the HL7 Implementation Guide requirements and the ISO 27269:2025: Health informatics — International Patient Summary are inconsistent in their requirements and implications for expressing the following sections: Immunizations, Results, Devices, and procedures. Primarily there are written implications in the ISO IPs that indicate the absence of these sections imply that there are no relevant entries to report. In this case systems that do not support the data in or generation of that section MUST be able to indicate that the section or information in the section is Not Supported in a Data absent reason. This profile further constrains the Data Absent Reason requirements to explicitly reflect when data is not available for inclusion, as distinguished from mediated relevant information. IHE has put forward comments to HL7 for alignment in future updates. IHE has also put in requests to ISO to further clarify data absent expectations and meaning. IHE has submitted a comment to ISO TC215 to provide more clarity surrounding missing data. Should updates be made, we will re-visit the volume 3 6.1.x.4 FHIR IPS Composition/Bundle Section Components of this document. (10/08/2025)
web www.iso.org FIPS_023: There is an identified gap in the HL7 FHIR IPS Implementation Guide. To properly align with the ISO 27269:2025: Health informatics — International Patient Summary standard, HL7 needs to require the support of the emptyReason data element in the following sections: Immunizations, History of Procedures, Medical Devices, and Results. IHE has opened a Jira ticket to HL7 to resolve this issue.
web profiles.ihe.net Editor, add the following new or modified actors to the IHE Technical Frameworks General Introduction Appendix A :
web profiles.ihe.net Editor, add the following new or modified transactions to the IHE Technical Frameworks General Introduction Appendix B :
web profiles.ihe.net Editor, add the following new or modified terms to the IHE Technical Frameworks General Introduction Appendix D :
web profiles.ihe.net The following test plans are generated for the content testing of the IPS. The testing events encourages testing paired with a transport. For education on what transports can be used for IPS documents please refer to the HIE Whitepaper
web profiles.ihe.net This section defines the actors, transactions, and/or content modules in this implementation guide. General definitions of actors are given in the Technical Frameworks General Introduction Appendix A . IHE Transactions can be found in the Technical Frameworks General Introduction Appendix B . Both appendices are located at https://profiles.ihe.net/GeneralIntro/ .
web profiles.ihe.net This section defines the actors, transactions, and/or content modules in this implementation guide. General definitions of actors are given in the Technical Frameworks General Introduction Appendix A . IHE Transactions can be found in the Technical Frameworks General Introduction Appendix B . Both appendices are located at https://profiles.ihe.net/GeneralIntro/ .
web profiles.ihe.net This section defines the actors, transactions, and/or content modules in this implementation guide. General definitions of actors are given in the Technical Frameworks General Introduction Appendix A . IHE Transactions can be found in the Technical Frameworks General Introduction Appendix B . Both appendices are located at https://profiles.ihe.net/GeneralIntro/ .
web profiles.ihe.net IPS Content Creator
web profiles.ihe.net IPS Content Consumer
web profiles.ihe.net The IPS Content Creator creates the FHIR IPS Content , FHIR IPS ODH , or FHIR IPS Complete in accordance to the Implementation option selected. The IPS Content Creator then shares it using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net The IPS Content Creator creates the FHIR IPS Content , FHIR IPS ODH , or FHIR IPS Complete in accordance to the Implementation option selected. The IPS Content Creator then shares it using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net The IPS Content Creator creates the FHIR IPS Content , FHIR IPS ODH , or FHIR IPS Complete in accordance to the Implementation option selected. The IPS Content Creator then shares it using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net The IPS Content Creator creates the FHIR IPS Content , FHIR IPS ODH , or FHIR IPS Complete in accordance to the Implementation option selected. The IPS Content Creator then shares it using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net The IPS Content Consumer consumes the FHIR IPS Content , FHIR IPS ODH , or FHIR IPS Complete in accordance to the Implementation option selected. The IPS Content Consumer obtains the IPS document using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net The IPS Content Consumer consumes the FHIR IPS Content , FHIR IPS ODH , or FHIR IPS Complete in accordance to the Implementation option selected. The IPS Content Consumer obtains the IPS document using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net The IPS Content Consumer consumes the FHIR IPS Content , FHIR IPS ODH , or FHIR IPS Complete in accordance to the Implementation option selected. The IPS Content Consumer obtains the IPS document using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net The IPS Content Consumer consumes the FHIR IPS Content , FHIR IPS ODH , or FHIR IPS Complete in accordance to the Implementation option selected. The IPS Content Consumer obtains the IPS document using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net This option defines the International Patient Summary modeled by HL7, where all of the optional sections(e.g., Advanced Directives, Functional Status, History of Past Illnesses, History of Pregnancy, Plan of Care, Social History, and Vital Signs) will become Must Support sections. The processing requirements placed on the Content Creators for producing a Complete FHIR IPS Document is detailed in the IPS Complete Option . This option specifies that the following sections defined as optional in the HL7 FHIR IPS Composition Have a New optionality of Must Support. This applies to the following sections:
web profiles.ihe.net Content Creators implementing this option shall create Occupational Data for Health information that complies with the Occupational Data for Health IG as entries to the Social History Section. The details are defined in the ODH Option .
web profiles.ihe.net The Content Consumer implementing this option shall be able to discretely import all relevant content provided by the Content Creator as defined by the IPS Complete Option .
web profiles.ihe.net See ITI TF-2: Appendix Z.8 "Mobile Security Considerations"
web profiles.ihe.net Health Information Exchange: Enabling Document Sharing Health Information Exchange Using IHE Profiles White Paper IHE Document Sharing Health Information Exchange .
web profiles.ihe.net Consider the IHE Sharing of IPS (sIPS) for methods of exchanging the HL7 International Patient Summary (IPS) , using IHE Document Sharing Health Information Exchange .
web profiles.ihe.net Consider the IHE Sharing of IPS (sIPS) for methods of exchanging the HL7 International Patient Summary (IPS) , using IHE Document Sharing Health Information Exchange .
web profiles.ihe.net Detailed descriptions of these transactions can be found in IHE ITI TF-2 .
web wiki.ihe.net The Patient Care Coordination registry of OIDs is located here
web www.iso.org ISO 27269:2025: Health informatics — International Patient Summary
web www.regenstrief.org LOINC
web profiles.ihe.net The FHIR IPS ODH Option Bundle defines the constraints applied to the Bundle Resource for this option.
web profiles.ihe.net The FHiR IPS Complete Option Bundle Incorporates the Complete Testing option for IPS. This Structure definition binds the Complete Option Composition to the bundle, where all optional sections (e.g., Advanced Directives, Functional Status, History of Past Illnesses, History of Pregnancy, Plan of Care, Social History, and Vital Signs) are now Must Support sections.
web www.iso.org In order to support the meanings of Absent Data described by ISO 27269:2025: Health informatics — International Patient Summary Standard Immunization Section 17.2.4 Missing: "These two situations should be explicitly documented in the IPS section: — known absence of vaccinations; — no information available about vaccinations", the emptyReason data element SHOULD Be supported for this section. Open issue FIPS_023 documents the misalignment between the HL7 and ISO Standard.
web www.iso.org In order to support the meanings of Absent Data described by ISO 27269:2025: Health informatics — International Patient Summary Standard History of Procedures Section 16.2.4 Missing - "Required if available, if not, then a reason shall be given.", the emptyReason data element SHOULD Be supported for this section. Open issue FIPS_023 documents the misalignment between the HL7 and ISO Standard.
web r4.fhir.space If there is a known absence of Procedure data, then this MAY be represented in the IPS History of Procedures Section with an emptyReason of data-absent-reason of not-applicable, OR Represented in the Procedure Entry as a Procedure Code of 787480003 "No known procedures". A Content Creator SHALL support at least one of these approaches.
web www.iso.org In order to support the meanings of Absent Data described by ISO 27269:2025: Health informatics — International Patient Summary Standard Medical Devices Section 18.2.4 Missing - "If missing, then the reason should be declared", the emptyReason data element SHOULD Be supported for this section. Open issue FIPS_023 documents the misalignment between the HL7 and ISO Standard.
web r4.fhir.space If there is a known absence of Device data, then this MAY be represented in the IPS Medical Devices Section with a data-absent-reason of not-applicable, OR Represented in the Procedure Entry as Medical Devices Code of 787483001 "No known device use". A Content Creator SHALL support at least one of these approaches.
web www.iso.org In order to support the meanings of Absent Data described by ISO 27269:2025: Health informatics — International Patient Summary Standard Lab Results Section 2.2.2.4 Missing "The implication is that no findings or results have been observed that are relevant to the present summary.", the emptyReason data element SHOULD Be supported for this section. Open issue FIPS_023 documents the misalignment between the HL7 and ISO Standard.
web r4.fhir.space If there is a known absence of Results data, then this MAY be represented in the IPS Results Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web www.ihe.net The following concepts have not been profiled in FHIR, but are defined in the IHE Patient Care Coordination Technical Framework, Volume 2 Section 6.3.4.24 Social History Observation 1.3.6.1.4.1.19376.1.5.3.1.4.13.4. These can be modeled using the FHIR Observation Resource.
web r4.fhir.space If there is a known absence of Advanced Directives, then this MAY be represented in the IPS Advanced Directives Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web profiles.ihe.net The FHIR IPS ODH Option Composition defines the constraints applied to the Bundle Resource for this bundle.
web r4.fhir.space If there is a known absence of Advanced Directives, then this SHOULD be represented in the IPS Advanced Directives Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web r4.fhir.space If there is a known absence of Functional Status information, then this SHOULD be represented in the IPS Functional Status Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web r4.fhir.space If there is a known absence of relevant past problems, then this SHOULD be represented in the IPS History of Past Illness Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web r4.fhir.space If there is a known absence of pregnancy information, then this SHOULD be represented in the IPS History of Pregnancy Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web r4.fhir.space If there is a known absence of Social History, then this SHOULD be represented in the IPS Social History Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web r4.fhir.space If there is a known absence of Vital Signs, then this SHOULD be represented in the IPS Vital Signs Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web r4.fhir.space If there is a known absence of Alerts, then this SHOULD be represented in the IPS Alerts Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.
web r4.fhir.space If there is a known absence of Patient Story information, then this SHOULD be represented in the IPS Patient Story Section with a data-absent-reason of not-applicable, OR Represented by the omission of the section. A Content Creator SHALL support at least one of these approaches.

Internal Images

tree-filter.png
tree-filter.png