International Patient Summary (IPS) Implementation Guide

Template Usage Information:

• Submit template change requests to PMO@HL7.org
• For Reaffirmations, please refer to the FAQ in  Hl7 Project Scope Statement Instructions for a list of which sections and fields should be completed

1. International Patient Summary (IPS) IG

2. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

2.b. Co-sponsor Work Group(s)

2.c. Project Team

All names should have confirmed their role in the project prior to submission to the TSC.

3. Project Definition

3.a. Project Scope

The goal of this project is to refine and maintain CDA R2 and FHIR  implementation guides and the associated artifacts (e.g. resource profiles) for the International Patient Summary, extending its current scope.  

This project continues and supersedes the prior HL7 IPS project (#1087). 

The IPS project has successfully collaborated with CEN/TC 251 delivering two STU Implementation Guides (the HL7 CDA R2 IPS IG and the HL7 FHIR IPS IG) that implement the CEN EN 17269 specification.  These guides are referred to, in turn, by the CEN TS 17288 standard.

This new HL7 IPS project takes in account the inputs and the lessons learned by the current CEN/HL7 IPS and the Trillium II (http://trillium2.eu) projects:

• The IPS has been initially conceived as a document designed for a well specified purpose (emergency and unplanned care), but there are now expectations of broader use of the IPS components (FHIR profiles; CDA templates) as a core data set for additionally identified use cases.
• The cross-border services capability with its conditional requirements is an added value of the IPS; but the IPS is expected to be used also in other national, regional and local contexts.
• There are several outstanding requests for adding content for new clinical domains (e.g. dental, mental health, child health) and new information (e.g. provenance; risks; ….) to the IPS.
• There are opportunities for extending the collaboration with other SDOs (e.g. SNOMED CT; ISO)
• There are opportunities for enriching the IPS ecosystem with additional artifacts and products (e.g. FHIR Logical Models).
• The IPS needs a continuous maintenance process, implementing the eStandards principles of co-creation-governance-alignment (see http://estandards-project.eu/)

Therefore:

1. The revised IPS project will no longer be limited to the "IPS document" (the subject of the current project); but it will also develop and continuously maintain a library of IPS data blocks (the individual CDA templates or FHIR profiles that the IPS document is composed of).
   1. In fact, if the IPS document is a HL7 FHIR or CDA document that serves a well-known and specified scope, the IPS data blocks define a minimal, non-exhaustive, specialty-agnostic and condition-independent data set that might be reused beyond the IPS document scope. This library of data blocks will be expressed in term of HL7 FHIR profiles and HL7 CDA templates.
2. The revised IPS project will identify, evaluate, select, develop and maintain all the HL7 products and artifacts to be included in the IPS standard ecosystem (e.g. FHIR logical models) and it will evaluate the need for the inclusion of new domains or information:
   1. involving the appropriate domain specific HL7 WGs;
   2. cooperating with other SDOs to keep consistency in the ecosystem with the artifacts produced by the other SDOs;
   3. interacting with the main stakeholders (e.g. eHDSI; Argonaut) to capture their needs and evaluations.

It is proposed to have a continuous maintenance process for the assigned products.  The intent, in fact, is to work on the two implementation guides (CDA and FHIR) subject to continuous revision lifecycles, whose content and included artifacts will be moved from STU to Normative.

3.b. Project Need

The creation of this project stems from 2 sources:

• The need for increased patient empowerment and the promotion of individual and community health in a global environment.
• The need for an innovative ecosystem of eHealth/Health IT that supports the electronic exchange of human- and machine-readable health, clinical, medical and management information to advance the health of individuals and communities.

3.c. Security Risks

The use of validation scripts or tools presents security considerations that must be addressed.  The extent to which this will be required, and at what levels, is unknown at present.  See the HL7 Security WG Cookbook for Security Considerations (http://wiki.hl7.org/index.php?title=Cookbook_for_Security_Considerations) for further discussion.

3.d. External Drivers

Coordination among SDOs (HL7, CEN/TC 251, JIC , SNOMED Int., ISO/TC215 and possible others) and with initiatives on Patient Summary (e.g. Trillium II).

EU Dependencies:

• Alignment with the EU standardization/identification process, at least for cross border exchange of data.
• Patient Summary guidelines will be revised by the eHealth Network.

3.e. Project Objectives / Deliverables / Target Dates

3.f.   Common Names / Keywords / Aliases

• IPS
• INTERPAS (former name)

3.g. Lineage

This project replaces the IPS FHIR IG STU 1; IPS CDA R2 IG STU 1.

3.h. Project Dependencies

3.i.   HL7-Managed Project Document Repository Location

3.j.   Backwards Compatibility

3.k. External Vocabularies

4. Products (check all that apply)

5. Project Intent (check all that apply)

5.a. Ballot Type (check all that apply)

5.b. Joint Copyright

Check this box if you will be pursuing a joint copyright.  Note that when this box is checked, a Joint Copyright Letter of Agreement must be submitted to the TSC in order for the PSS to receive TSC approval.

6. Project Logistics

6.a. External Project Collaboration

This project is a cooperative action plan between a global group of SDOs, experts and stakeholders, across the public, private and academic sectors.

Collaborations:

• SDOs: CEN/TC 251, SNOMED Int., ISO/TC 215 
• Governments: United States (via ONC) and European Commission (via CEN and CEN TC251)
• European HL7 Affiliates (via ESAB and HL7 International Foundation / European Office)

COORDINATION WITH SDOs:

Because of the international nature of this initiative, coordination with global and regional SDOs is crucial.  It is expected that the project will be submitted to the Joint Initiative Council (JIC) in ISO with HL7 as the lead SDO and ISO TC215 as the secondary SDO.

Collaborating parties will have access to all project materials.

Existing content will be reviewed and evaluated for applicability as the project proceeds.

6.b. Realm

6.c. Stakeholders / Vendors / Providers

This section must be completed for projects containing items expected to be ANSI approved, as it is an ANSI requirement for all ballots

6.d. Project Approval Dates

Click here to go to HL7 Project Scope Statement Instructions#Appendix A for more information regarding this section.
Approvals are by simple majority vote of the approving body