HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative

HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions

Requirements: TI.5.4 Interchange Agreements (Function)

Official URL: http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.5.4 Version: 2.0.1
Standards status: Normative Active as of 2025-12-07 Computable Name: TI_5_4_Interchange_Agreements

Support the use of Interchange Agreements to specify the rules, responsibilities, expectations, and methods by which Interchange Agreement partners may exchange information.

Description I:

Systems that wish to communicate with each other must agree on certain parameters/criteria that will govern an information exchange process. Interchange agreements enable partnering systems to discover, negotiate, and utilize those parameters/criteria. A PHR-S can use this information to define how data will be exchanged between the sending and the receiving partners. Interchange services and capabilities can be discovered in an automated fashion.

Entity directories can be used to determine the address, profile, and data exchange requirements of known, and/or potential Interchange Agreement partners. Entity registries can be used to determine the security, addressing, and reliability requirements between potential Interchange Agreement partnering systems.

Criteria N:
TI.5.4#01 SHALL

The system SHALL exchange information with Interchange Agreement partners based on interoperability agreement descriptions.
TI.5.4#02 SHOULD conditional

IF an interchange agreement description specifies the use of a certain standard, THEN the system SHOULD exchange information using the standard specified by the interchange agreement description according to scope of practice, organizational policy, and/or jurisdictional law.
TI.5.4#03 MAY

The system MAY conform to function TI.3 (Registry and Directory Services) to interact with registries, and/or directories to determine the address, profile, and data exchange requirements of known, and/or potential partners.
TI.5.4#04 MAY

The system MAY analyze and present interchange service descriptions and capabilities according to scope of practice, organizational policy, and/or jurisdictional law.
TI.5.4#05 SHOULD

The system SHOULD provide the ability to manage Interchange Agreements that have been established with Interchange Agreement partners.