HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative
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
| Page standards status: Normative |
<Requirements xmlns="http://hl7.org/fhir">
<id value="PHRSFMR2-TI.5.4"/>
<meta>
<profile
value="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"/>
</meta>
<language value="en"/>
<text>
<status value="extensions"/>
<div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
<div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>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.</p>
<p>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.</p>
</div></div>
<div id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></div>
<table id="statements" class="grid dict">
<tr>
<td style="padding-left: 4px;">
TI.5.4#01
</td>
<td style="padding-left: 4px;">
SHALL
</td>
<td style="padding-left: 4px;" class="requirement">
<div><p>The system SHALL exchange information with Interchange Agreement partners based on interoperability agreement descriptions.</p>
</div>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
TI.5.4#02
</td>
<td style="padding-left: 4px;">
SHOULD
<span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<div><p>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.</p>
</div>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
TI.5.4#03
</td>
<td style="padding-left: 4px;">
MAY
</td>
<td style="padding-left: 4px;" class="requirement">
<div><p>The system MAY conform to function <a href="Requirements-PHRSFMR2-TI.3.html">TI.3</a> (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.</p>
</div>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
TI.5.4#04
</td>
<td style="padding-left: 4px;">
MAY
</td>
<td style="padding-left: 4px;" class="requirement">
<div><p>The system MAY analyze and present interchange service descriptions and capabilities according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
TI.5.4#05
</td>
<td style="padding-left: 4px;">
SHOULD
</td>
<td style="padding-left: 4px;" class="requirement">
<div><p>The system SHOULD provide the ability to manage Interchange Agreements that have been established with Interchange Agreement partners.</p>
</div>
</td>
</tr>
</table>
</div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="normative"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="ehr"/>
</extension>
<url value="http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.5.4"/>
<version value="2.0.1"/>
<name value="TI_5_4_Interchange_Agreements"/>
<title value="TI.5.4 Interchange Agreements (Function)"/>
<status value="active"/>
<date value="2025-12-07T09:26:53+00: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>
IG © 2023 EHR WG.
Package hl7.ehrs.uv.phrsfmr2#2.0.1 based on FHIR 5.0.0.
Generated
2025-12-07
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change