Statement N:

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.

 Actors:
ehr 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 dependent conditional SHOULD

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 dependent 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.
<status value="active"/> <date value="2025-04-04T11:42:51+11:00"/> <publisher value="EHR WG"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/ehr"/> </telecom> </contact> <description value="Support the use of Interchange Agreements to specify the rules, responsibilities, expectations, and methods by which Interchange Agreement partners may exchange information."/> <purpose value="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."/> <statement> <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <key value="PHRSFMR2-TI.5.4-01"/> <label value="TI.5.4#01"/> <conformance value="SHALL"/> <conditionality value="false"/> <requirement value="The system SHALL exchange information with Interchange Agreement partners based on interoperability agreement descriptions."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <key value="PHRSFMR2-TI.5.4-02"/> <label value="TI.5.4#02"/> <conformance value="SHOULD"/> <conditionality value="true"/> <requirement value="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."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <key value="PHRSFMR2-TI.5.4-03"/> <label value="TI.5.4#03"/> <conformance value="MAY"/> <conditionality value="false"/> <requirement value="The system MAY conform to function [TI.3](Requirements-PHRSFMR2-TI.3.html) (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."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <key value="PHRSFMR2-TI.5.4-04"/> <label value="TI.5.4#04"/> <conformance value="MAY"/> <conditionality value="false"/> <requirement value="The system MAY analyze and present interchange service descriptions and capabilities according to scope of practice, organizational policy, and/or jurisdictional law."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <key value="PHRSFMR2-TI.5.4-05"/> <label value="TI.5.4#05"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="The system SHOULD provide the ability to manage Interchange Agreements that have been established with Interchange Agreement partners."/> </statement> </Requirements>