FHIR International Patient Summary
0.0.1-current - ci-build

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

## FHIR International Patient Summary Profile Home

Official URL: https://profiles.ihe.net/PCC/FIIO/ImplementationGuide/ihe.pcc.fiio | Version: 0.0.1-current
Draft as of 2026-02-06 | Computable Name: IHE_PCC_FIIO

This IPS profile uses the Health Level 7's FHIR International Patient Summary (IPS) that realizes the CEN EN 17269 IPS dataset to profile additional implementation options that can be incorporated into the IPS document. This is a Content Module profile that defines these additional Implementation options.

Significant Changes, Open and Closed Issues

### Organization of This Guide

This guide is organized into the following sections:

1. Volume 1:
   1. Introduction
   2. Actors, Transactions, and Content
   3. Actor Options
   4. Actor Required Groupings
   5. Overview
   6. Security Considerations
   7. Cross Profile Considerations
2. Volume 3: Metadata and Content
   1. ​FHIR Content Modules
3. Other
   1. Test Plan
   2. Changes to Other IHE Specifications
   3. Download and Analysis

See also the Table of Contents and the index of Artifacts defined as part of this implementation guide.

### Conformance Expectations

IHE uses the normative words: Shall, Should, and May according to standards conventions.

#### Must Support

The use of `mustSupport` in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor shall populate the elements marked with MustSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors should handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.