FR2 - Revision history

Kheitmann at 17:41, 27 January 2026

2026-01-27T17:41:02Z

Kheitmann at 17:08, 27 January 2026

2026-01-27T17:08:09Z

Kheitmann at 14:56, 12 August 2024

2024-08-12T14:56:09Z

Kheitmann at 14:20, 6 August 2024

2024-08-06T14:20:21Z

Kheitmann at 13:56, 6 August 2024

2024-08-06T13:56:27Z

Kheitmann at 13:38, 6 August 2024

2024-08-06T13:38:50Z

Kheitmann: Created page with "

Functional requirements and high-level use cases

The International Patient Summary, i.e. a “specialty-agnostic, condition-independent" summary,..."

2024-08-06T13:38:43Z

Created page with "<h1>Functional requirements and high-level use cases </h1> The International Patient Summary, i.e. a “specialty-agnostic, condition-independent" summary,..."

New page

<h1>Functional requirements and high-level use cases </h1>
The International Patient Summary, i.e. a “specialty-agnostic, condition-independent" summary, was initially designed for cross-border unscheduled care, but its actual adoption is not limited to this usage scenario.
Patient summary initiatives are currently in various stages of development in different parts of the world. A summary of the most recent initiatives and experiences across the world can be found in the <a href="https://international-patient-summary.net/implementations-across-the-globe/" rel="noopener noreferrer nofollow"
>https://international-patient-summary.net/implementations-across-the-globe/</a>.
As mentioned there are several options in terms of creation, sharing and usage of an IPS. For example:
<ol>
<li>
An IPS can be created when requested and used before, during, or after a care episode; or can be asynchronously generated and made available for future usage (e.g. store and retrieve).
</li>
<li>
The IPS can be retrieved using a document exchange infrastructure; transported by the patient; or shared using cloud-services.
</li>
<li>
The IPS may be subject of a transformation process that may include syntactical conversions, coded concept mappings and coded concept designation or free text translations. This transformation process may be performed in the creation phase, during the transmission, or after the IPS has been received, possibly using an external service.
</li>
<li>
Finally, the received CDA may be used in different ways. For example, displayed using a common CDA stylesheet; display the extracted relevant information; incorporated into the receiver’s EHR. Alternatively, a specialized viewer may be adopted to enable the display of the translated content.
</li>
</ol>
Moreover, for cross-jurisdiction exchange, the IPS could be used as:
<ol>
<li>
shared format among jurisdictions (case A), where jurisdictions originate and use IPS conforming documents unaltered.
</li>
<li>
pivot document among existing summaries / data formats (case B). For example, the IPS is used as intermediate format between the US C-CDA CCD (please note that the CCD scope differs from that of the IPS) and the European eHDSI Patient Summary for a Transatlantic Patient Summary exchange.
</li>
<li>
mixed mode (Case C), where either the originator or the consumer is expected to use an IPS conforming document.
</li>
</ol>

<img src="/exist/apps/api/project/hl7ips-/blob/ef1da671-dbb9-43ed-9da6-71dbb9a3ede8" alt="File:IPS cases.png"/>



Figure: Examples of IPS usage


An International Patient Summary may:
<ol>
<li>
be the result of automatic assembly (assembled IPS) or of a human summarization act (human curated IPS)
</li>
<li>
have one or more EHR sources
</li>
<li>
document information from a single or multiple jurisdictions/organizations
</li>
<li>
aggregate input from a single or multiple encounters.
</li>
</ol>
A clear determination of such contextual information raises the trustworthiness of the received IPS and helps the appropriate usage of its content by the receiver .
Most of these aspects are related to data provenance introduced in * to be checked ==>
<a href="https://wiki.international-patient-summary.net/index.php?title=IPS_implementationguide_1#Relationships_with_other_projects_and_guidelines" rel="noopener noreferrer nofollow">section 1.8</a> and further detailed in * to be checked ==>
<a href="https://wiki.international-patient-summary.net/index.php?title=IPS_implementationguide_1#Provenance" rel="noopener noreferrer nofollow">section 4.11</a>.
Finally, there are several technical infrastructures and services that may be designed to support these requirements.
That said, it is out of scope of this standard to:
<ul>
<li>

give indications about solutions and strategies for the IPS creation, sharing, syntactical and semantic mapping, translation, and use.

</li>
<li>
Provide guidance on how to determine the relevance of data for their inclusion in a IPS.
</li>
<li>
Define selection or composition rules for facing potential inconsistencies from multiple sources in case of automatic collection.
</li>
<li>
Impose constraints on the possible active Patient Summaries. Many jurisdictions require that only one active Patient Summary for unscheduled care is made available, but this is an implementation choice.
</li>
</ul>
</content>

@@ Line 1: / Line 1: @@
-<html><h1>Functional requirements and high-level use cases </h1>
+=Functional requirements and high-level use cases=
                  <p>The International Patient Summary, i.e. a “specialty-agnostic, condition-independent" summary, was initially designed for cross-border unscheduled care, but its actual adoption is not limited to this usage scenario.</p>
                  <p>Patient summary initiatives are currently in various stages of development in different parts of the world. A summary of the most recent initiatives and experiences across the world can be found in the <a href="https://international-patient-summary.net/implementations-across-the-globe/" rel="noopener noreferrer nofollow"

@@ Line 54: / Line 54: @@
                  </ol>
                  <p>A clear determination of such contextual information raises the trustworthiness of the received IPS and helps the appropriate usage of its content by the receiver .</p>
-                 <p>Most of these aspects are related to data provenance introduced in <em>* to be checked ==&gt;</em>
+                 <p>Most of these aspects are related to data provenance introduced in
-                     <a href="https://wiki.international-patient-summary.net/index.php?title=IPS_implementationguide_1#Relationships_with_other_projects_and_guidelines" rel="noopener noreferrer nofollow">section 1.8</a> and further detailed in <em>* to be checked ==&gt;</em>
+                     <a href="https://wiki.international-patient-summary.net/index.php?title=IPS_implementationguide_2#Provenance" rel="noopener noreferrer nofollow">Chapter 5: Provenance</a>.</p>
                  <p>Finally, there are several technical infrastructures and services that may be designed to support these requirements.</p>
                  <p>That said, <strong>it is out of scope of this standard to:</strong></p>

@@ Line 31: / Line 31: @@
                  </ol>
                  <p>
-                     <img src="/exist/apps/api/project/hl7ips-/blob/ef1da671-dbb9-43ed-9da6-71dbb9a3ede8" alt="File:IPS cases.png"/>
+                     </html>[[File:ef1da671-dbb9-43ed-9da6-71dbb9a3ede8.png]]<html>
                  </p>
                  <p>

@@ Line 1: / Line 1: @@
-<h1>Functional requirements and high-level use cases </h1>
+<html><h1>Functional requirements and high-level use cases </h1>
                  <p>The International Patient Summary, i.e. a “specialty-agnostic, condition-independent" summary, was initially designed for cross-border unscheduled care, but its actual adoption is not limited to this usage scenario.</p>
                  <p>Patient summary initiatives are currently in various stages of development in different parts of the world. A summary of the most recent initiatives and experiences across the world can be found in the <a href="https://international-patient-summary.net/implementations-across-the-globe/" rel="noopener noreferrer nofollow"
@@ Line 75: / Line 75: @@
                      </li>
                  </ul>

← Older revision		Revision as of 13:38, 6 August 2024
Line 75:		Line 75:
	</li>		</li>
	</ul>		</ul>
−	~~</content>~~

@@ Line 6: / Line 6: @@
                  <ol>
                      <li>
-                         <p>An IPS can be created when requested and used before, during, or after a care episode; or can be asynchronously generated and made available for future usage (e.g. store and retrieve).</p>
+                         An IPS can be created when requested and used before, during, or after a care episode; or can be asynchronously generated and made available for future usage (e.g. store and retrieve).
                      </li>
                      <li>
-                         <p>The IPS can be retrieved using a document exchange infrastructure; transported by the patient; or shared using cloud-services.</p>
+                         The IPS can be retrieved using a document exchange infrastructure; transported by the patient; or shared using cloud-services.
                      </li>
                      <li>
-                         <p>The IPS may be subject of a transformation process that may include syntactical conversions, coded concept mappings and coded concept designation or free text translations. This transformation process may be performed in the creation phase, during the transmission, or after the IPS has been received, possibly using an external service.</p>
+                         The IPS may be subject of a transformation process that may include syntactical conversions, coded concept mappings and coded concept designation or free text translations. This transformation process may be performed in the creation phase, during the transmission, or after the IPS has been received, possibly using an external service.
                      </li>
                      <li>
-                         <p>Finally, the received CDA may be used in different ways. For example, displayed using a common CDA stylesheet; display the extracted relevant information; incorporated into the receiver’s EHR. Alternatively, a specialized viewer may be adopted to enable the display of the translated content.</p>
+                         Finally, the received CDA may be used in different ways. For example, displayed using a common CDA stylesheet; display the extracted relevant information; incorporated into the receiver’s EHR. Alternatively, a specialized viewer may be adopted to enable the display of the translated content.
                      </li>
                  </ol>
@@ Line 21: / Line 21: @@
                  <ol>
                      <li>
-                         <p>shared format among jurisdictions (case A), where jurisdictions originate and use IPS conforming documents unaltered.</p>
+                         shared format among jurisdictions (case A), where jurisdictions originate and use IPS conforming documents unaltered.
                      </li>
                      <li>
-                         <p>pivot document among existing summaries / data formats (case B). For example, the IPS is used as intermediate format between the US C-CDA CCD (please note that the CCD scope differs from that of the IPS) and the European eHDSI Patient Summary for a Transatlantic Patient Summary exchange.</p>
+                         pivot document among existing summaries / data formats (case B). For example, the IPS is used as intermediate format between the US C-CDA CCD (please note that the CCD scope differs from that of the IPS) and the European eHDSI Patient Summary for a Transatlantic Patient Summary exchange.
                      </li>
                      <li>
-                         <p>mixed mode (Case C), where either the originator or the consumer is expected to use an IPS conforming document.</p>
+                         mixed mode (Case C), where either the originator or the consumer is expected to use an IPS conforming document.
                      </li>
                  </ol>
@@ Line 41: / Line 41: @@
                  <ol>
                      <li>
-                         <p>be the result of automatic assembly (assembled IPS) or of a human summarization act (human curated IPS)</p>
+                         be the result of automatic assembly (assembled IPS) or of a human summarization act (human curated IPS)
                      </li>
                      <li>
-                         <p>have one or more EHR sources</p>
+                         have one or more EHR sources
                      </li>
                      <li>
-                         <p>document information from a single or multiple jurisdictions/organizations</p>
+                         document information from a single or multiple jurisdictions/organizations
                      </li>
                      <li>
-                         <p>aggregate input from a single or multiple encounters.</p>
+                         aggregate input from a single or multiple encounters.
                      </li>
                  </ol>
@@ Line 60: / Line 60: @@
                  <p>That said, <strong>it is out of scope of this standard to:</strong></p>
                  <ul>
-                     <li>
+                     <li><strong>give indications about solutions and strategies for the IPS creation, sharing, syntactical and semantic mapping, translation, and use.</strong></li>
-                        <p>
+                    <li>Provide guidance on how to determine the relevance of data for their inclusion in a IPS.
                      </li>
-                     <li>
+                     <li>Define selection or composition rules for facing potential inconsistencies from multiple sources in case of automatic collection.
                      </li>
-                     <li>
+                     <li>Impose constraints on the possible active Patient Summaries. Many jurisdictions require that only one active Patient Summary for unscheduled care is made available, but this is an implementation choice.
                      </li>
                  </ul>
 </html>