International Patient Summary (IPS) IG (PSS In Confluence)

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).

a. 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:

a. involving the appropriate domain specific HL7 WGs;

b. cooperating with other SDOs to keep consistency in the ecosystem with the artifacts produced by the other SDOs;

c. 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.'