|
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 0.0.1-current 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#0.0.1-current based on FHIR 4.0.1
. Generated 2026-02-05
Links: Table of Contents |
QA Report
| New Issue | Issues
Version History |
 |
Propose a change
|
|
web
|
github.com
|
Links: Table of Contents
|
QA Report
| New Issue
| Issues
Version History
|
|
Propose a change
|
|
web
|
github.com
|
Links: Table of Contents
|
QA Report
| New Issue
| Issues
Version History
|
|
Propose a change
|
|
web
|
profiles.ihe.net
|
Links: Table of Contents
|
QA Report
| New Issue
| Issues
Version History
|
|
Propose a change
|
|
web
|
www.ihe.net
|
Links: Table of Contents
|
QA Report
| New Issue
| Issues
Version History
|
|
Propose a change
|
|
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
|
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: Shall, Should, and May 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 origionally a segment 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
|
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 allign 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
|
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 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
|
HIE Replated retrieval of patient summary, single source/ on demand…
incorperate the iti register ondemand doccument transaction into process flow ITI-61
TODO - plantuml diagram development
|
|
web
|
profiles.ihe.net
|
See ITI TF-2x: 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
|
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
deffines the contraints applied to the Bundle Resource for this option.
|
|
web
|
profiles.ihe.net
|
The FHiR IPS Complete Option Bundle
Incorperates 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 elemnt 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 Histrory of Procedures Section 16.2.4 Missing - "Required if available, if not then a reason shall be given.", the emptyReason data elemnt 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 knowm absence of Procedure data then this May
be represented in the IPS Histrory of Procedures Section with an emptyReason of 787480003 "No known procedures" SNOMED-CT
, OR
a 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 elemnt 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 knowm absence of Device data then this May
be represented in the IPS Medical Devices Section with an emptyReason of 787480003 "No known procedures" SNOMED-CT
, OR
a 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 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 elemnt 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 knowm absence of Results data then this May
be represented in the IPS Results Section with an emptyReason of 787480003 "No known procedures" SNOMED-CT
, OR
a 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
|
profiles.ihe.net
|
The FHIR IPS ODH Option Composition
deffines the contraints applied to the Bundle Resource for this bundle.
|
