Difference between revisions of "IT2"

From HL7 IPS
Jump to: navigation, search
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
<html><h1>Introduction </h1>
+
=Introduction=
 +
<html>
 
                 <p>An <strong>International Patient Summary (IPS) document</strong> is an electronic health record extract containing essential healthcare information about a subject of care. As specified in EN ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic
 
                 <p>An <strong>International Patient Summary (IPS) document</strong> is an electronic health record extract containing essential healthcare information about a subject of care. As specified in EN ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic
 
                     solutions for global application beyond a particular region or country.</p>
 
                     solutions for global application beyond a particular region or country.</p>
Line 5: Line 6:
 
                 <p>The IPS document is composed by a set of robust, well-defined and potentially reusable sets of core data items (indicated as IPS library in the figure below). The tight focus of the IPS on unplanned care is in this case not a limitation, but, on the contrary, facilitates their potential re-use beyond the IPS scope.</p>
 
                 <p>The IPS document is composed by a set of robust, well-defined and potentially reusable sets of core data items (indicated as IPS library in the figure below). The tight focus of the IPS on unplanned care is in this case not a limitation, but, on the contrary, facilitates their potential re-use beyond the IPS scope.</p>
 
                 <p>
 
                 <p>
                     </html>[[File:f784fd13-e44c-4a1c-84fd-13e44cfa1cc3.png|600px]]<html>
+
                     </html>
 +
[[File:f784fd13-e44c-4a1c-84fd-13e44cfa1cc3.png|600px]]<br/>
 +
<strong><em>Figure 1: The IPS product and by-products</em></strong>
 +
<html>
 
                 </p>
 
                 </p>
                <p>
+
</html>
                    <strong>
+
==Purpose==
                        <em>Figure 1: The IPS product and by-products</em>
+
<html>
                    </strong>
+
The goal of this Implementation Guide is to specify how to represent in HL7 CDA the International Patient Summary (IPS). An alternative representation as templated HL7 FHIR R2 is also provided ( see the <a href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=483" rel="noopener noreferrer nofollow">hl7.org site</a> ). The initial focus of the International Patient Summary (IPS) was the unplanned care across national borders. This specification can be used and be useful also in local applications and be supportive of planned care.
                </p>
+
</html>
                <h2>Purpose</h2>
+
== Scope ==
                <p>The goal of this Implementation Guide is to specify how to represent in HL7 CDA the International Patient Summary (IPS). An alternative representation as templated HL7 FHIR R2 is also provided ( see the <a href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=483" rel="noopener noreferrer nofollow">hl7.org site</a> ). The initial focus of the International
+
<html>
                    Patient Summary (IPS) was the unplanned care across national borders. This specification can be used and be useful also in local applications and be supportive of planned care.</p>
 
                <h2>Scope</h2>
 
 
                 <p>As specified in EN ISO 27269, the IPS dataset is a <strong><em>“minimal, non-exhaustive set of data elements required for the international patient summary”</em></strong>. A Patient Summary is defined by ISO/TR 12773-1:2009 as a “Health record extract comprising a standardized collection of clinical and contextual information (retrospective, concurrent, prospective) that
 
                 <p>As specified in EN ISO 27269, the IPS dataset is a <strong><em>“minimal, non-exhaustive set of data elements required for the international patient summary”</em></strong>. A Patient Summary is defined by ISO/TR 12773-1:2009 as a “Health record extract comprising a standardized collection of clinical and contextual information (retrospective, concurrent, prospective) that
 
                     provides a snapshot in time of a subject of care’s health information and healthcare.”</p>
 
                     provides a snapshot in time of a subject of care’s health information and healthcare.”</p>
Line 24: Line 26:
 
                 <p>The following picture provides an overview of the current IPS content.</p>
 
                 <p>The following picture provides an overview of the current IPS content.</p>
 
                 <p>
 
                 <p>
</html>[[File:de56fc54-5c7f-491c-96fc-545c7f191ca7.png]]<html>
+
</html>
                </p>
+
[[File:De56fc54-5c7f-491c-96fc-545c7f191ca7.png|600px]]<br/>
                <p>
+
<strong><em>Figure 2: The IPS composition</em></strong>
                    <strong>
+
 
                        <em>Figure 2: The IPS composition</em>
+
==Project Background and relationships with other projects==
                    </strong>
+
 
                </p>
+
Details on the project background and relationships with other projects are available in the <html><a href="https://international-patient-summary.net/" rel="noopener noreferrer nofollow">IPS Website</a></html>.
                <h2>Project Background and relationships with other projects</h2>
+
 
                <p>Details on the project background and relationships with other projects are available in the <a href="https://international-patient-summary.net/" rel="noopener noreferrer nofollow">IPS Website</a>.</p>
+
==Ballot Status of the Document==
                <h2>Ballot Status of the Document</h2>
+
<html>
 
                 <p>This Implementation Guide is STU with the intention to go normative.</p>
 
                 <p>This Implementation Guide is STU with the intention to go normative.</p>
 
                 <h2>Audience</h2>
 
                 <h2>Audience</h2>
Line 40: Line 42:
 
                 <ul>
 
                 <ul>
 
                     <li>
 
                     <li>
                         <p>Citizens who want to carry or access their healthcare data for emergency or unplanned care purposes.</p>
+
                         Citizens who want to carry or access their healthcare data for emergency or unplanned care purposes.
 
                     </li>
 
                     </li>
 
                 </ul>
 
                 </ul>
Line 46: Line 48:
 
                 <ul>
 
                 <ul>
 
                     <li>
 
                     <li>
                         <p>Policy makers such as healthcare payers or government agencies.</p>
+
                         Policy makers such as healthcare payers or government agencies.
 
                     </li>
 
                     </li>
 
                     <li>
 
                     <li>
                         <p>Healthcare information governance authorities and regulatory bodies.</p>
+
                         Healthcare information governance authorities and regulatory bodies.
 
                     </li>
 
                     </li>
 
                 </ul>
 
                 </ul>
Line 55: Line 57:
 
                 <ul>
 
                 <ul>
 
                     <li>
 
                     <li>
                         <p>Healthcare providers that offer unscheduled and emergency care.</p>
+
                         Healthcare providers that offer unscheduled and emergency care.
 
                     </li>
 
                     </li>
 
                     <li>
 
                     <li>
                         <p>Healthcare providers that populate regional and national patient summaries.</p>
+
                         Healthcare providers that populate regional and national patient summaries.
 
                     </li>
 
                     </li>
 
                 </ul>
 
                 </ul>
Line 64: Line 66:
 
                 <ul>
 
                 <ul>
 
                     <li>
 
                     <li>
                         <p>Vendors of EHR systems for unplanned care management, personal health records and mobile health data applications.</p>
+
                         Vendors of EHR systems for unplanned care management, personal health records and mobile health data applications.
 
                     </li>
 
                     </li>
 
                     <li>
 
                     <li>
                         <p>System integrators.</p>
+
                         System integrators.
 
                     </li>
 
                     </li>
 
                     <li>
 
                     <li>
                         <p>Organizations that manage regional and national patient summaries.</p>
+
                         Organizations that manage regional and national patient summaries.
 
                     </li>
 
                     </li>
 
                 </ul>
 
                 </ul>
                <h2>Reading Publication Artifacts</h2>
+
</html>
 +
 
 +
==Reading Publication Artifacts==
 +
<html>
 
                 <p>A reading guide is available that explains the formalism used to express the publication artifacts, i.e. template meta data and template design. For convenience the guide is included in the appendix. (see section "How to read the table view for templates")</p>
 
                 <p>A reading guide is available that explains the formalism used to express the publication artifacts, i.e. template meta data and template design. For convenience the guide is included in the appendix. (see section "How to read the table view for templates")</p>
 
</html>
 
</html>

Latest revision as of 14:50, 12 August 2024

Introduction

An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care. As specified in EN ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country.

The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant.

The IPS document is composed by a set of robust, well-defined and potentially reusable sets of core data items (indicated as IPS library in the figure below). The tight focus of the IPS on unplanned care is in this case not a limitation, but, on the contrary, facilitates their potential re-use beyond the IPS scope.

F784fd13-e44c-4a1c-84fd-13e44cfa1cc3.png
Figure 1: The IPS product and by-products

Purpose

The goal of this Implementation Guide is to specify how to represent in HL7 CDA the International Patient Summary (IPS). An alternative representation as templated HL7 FHIR R2 is also provided ( see the hl7.org site ). The initial focus of the International Patient Summary (IPS) was the unplanned care across national borders. This specification can be used and be useful also in local applications and be supportive of planned care.

Scope

As specified in EN ISO 27269, the IPS dataset is a “minimal, non-exhaustive set of data elements required for the international patient summary”. A Patient Summary is defined by ISO/TR 12773-1:2009 as a “Health record extract comprising a standardized collection of clinical and contextual information (retrospective, concurrent, prospective) that provides a snapshot in time of a subject of care’s health information and healthcare.”

‘Minimal’ reflects the ideas of ‘summary’ and the need to be concise, but also alludes to the existence of a core set of data elements that all health care professionals can use; it is intended to be a specialty agnostic and condition independent set. It does not imply that all the items in the data set will be used in every summary. It is also possible to refine the extract from a record such that the content of the summary is more relevant to a particular condition (e.g. asthma) but no asthma-specific elements will be specified in this standard. The IPS Document or IPS can be extended by non-IPS standard condition-specific data. ‘Non-exhaustive’ recognizes that the ideal data set is not closed, and is likely to be extended, not just in terms of requirement evolution, but also pragmatically in instances of use. [EN ISO 27269].

Furthermore the scope of the IPS is global. Although this is a major challenge, this implementation guide takes various experiences and newer developments into account to address, as far as possible, global feasibility.

The following picture provides an overview of the current IPS content.

De56fc54-5c7f-491c-96fc-545c7f191ca7.png
Figure 2: The IPS composition

Project Background and relationships with other projects

Details on the project background and relationships with other projects are available in the IPS Website.

Ballot Status of the Document

This Implementation Guide is STU with the intention to go normative.

Audience

The audience for this Implementation Guide includes:

Public

  • Citizens who want to carry or access their healthcare data for emergency or unplanned care purposes.

Regulatory

  • Policy makers such as healthcare payers or government agencies.
  • Healthcare information governance authorities and regulatory bodies.

Clinical

  • Healthcare providers that offer unscheduled and emergency care.
  • Healthcare providers that populate regional and national patient summaries.

Technical

  • Vendors of EHR systems for unplanned care management, personal health records and mobile health data applications.
  • System integrators.
  • Organizations that manage regional and national patient summaries.

Reading Publication Artifacts

A reading guide is available that explains the formalism used to express the publication artifacts, i.e. template meta data and template design. For convenience the guide is included in the appendix. (see section "How to read the table view for templates")