Page tree
Skip to end of metadata
Go to start of metadata

1) Change Proposal Details:

Link to the change proposal history: Change Proposals Registry.

The Change Proposal has been approved by eHOMB on and it has to be implemented for Wave 4.

  • OpenNCP Technical Workgroup comments on the Change Proposal content.

2) International Search Mask Use Case:

Solution Profider - Functional Assessment

The existing document Identity Management Specification already contains information relative to the patient identity traits (especially chapters 3 and 5). Therefore, Solution Provider do not think there is a need for a new normative document for the implementation of the International Search Mask.

Performing the update of the Identity Management Specification may also give the opportunity to review and better differentiate the identity traits from the patient demographic data.

2.1) Patient Identification:

2.2) Clinical Documentation Identification:

3) Business Requirements:

eHDSI Requirements Catalog: https://ec.europa.eu/cefdigital/wiki/x/fp5UAw

  • OpenNCP Technical Workgroup should review the Business Requirements and the Functional and Non-Functional Requirements.

4) Technical Design:

Solution Provider - Technical Assessment

Implementing the change proposal would mainly affect the IHE XCPD profile and SAML assertions. It has to be noted as well that any impact on the SMP file will also impact the SMP service.

Solution Provider does not currently agree with the proposed technical solution and the Technical Workgroup should have the opportunity to discuss about and decide the final solution.

SP can mention 3 points to review in the current change proposal:

  • The “friendlyName” attribute seems to relate to the eSens period of the project, and might be removed from the final implementation. There is a possibility for an “original name” attribute which would correspond to an attribute in the patient original language.
  • The “label” attribute should not mention translation with the Master Value Set Catalog, as identification of a patient and translation of information are two diametrically different notions, which do not relate to the same application components.
  • An exhaustive list of all expected attribute patterns will be required to perform the technical implementation.

If the Change Proposal is adopted, it will affect all the Member States of the corresponding wave, as both NCP-A and B sides must be updated to authorize the new XSD format. Solution Provider support the change proposal, with the aforementioned comments.

eHDSI Specifications Documents impacted:

5) Technical Implementation:

5.1) International Search Mask schema:

<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://ec.europa.eu/sante/ehncp/ism"
           elementFormDefault="qualified" targetNamespace="http://ec.europa.eu/sante/ehncp/ism">

    <!-- Root Element defining the International Search Mask - Identity Traits -->
    <xs:element name="searchFields">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="country" type="country"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>

    <!-- Identification of the eHNCP providing its cross border traits (ISO Country Code of NCP_A) -->
    <xs:complexType name="country">
        <xs:sequence>
            <xs:element name="patientSearch" type="patientSearch"/>
            <xs:element name="documentSearch" type="documentSearch"/>
        </xs:sequence>
        <xs:attribute name="code" type="xs:string" use="required"/>
        <xs:attribute name="friendlyName" type="xs:string"/>
        <xs:attribute name="label" type="xs:string"/>
    </xs:complexType>

    <xs:complexType name="patientSearch">
        <xs:sequence>
            <xs:element ref="id" maxOccurs="unbounded"/>
            <xs:element ref="textField" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element ref="birthDate" minOccurs="0"/>
            <xs:element ref="sex" minOccurs="0"/>
        </xs:sequence>
        <xs:attribute name="scope" type="scope" default="0" />
    </xs:complexType>

    <xs:complexType name="documentSearch">
        <xs:sequence>
            <xs:element name="documentId" type="id"/>
            <xs:element name="pinCode" type="id"/>
        </xs:sequence>
        <xs:attribute name="friendlyName" type="xs:string"/>
        <xs:attribute name="label" type="xs:string"/>
        <xs:attribute name="mandatory" type="xs:boolean" default="false" />
    </xs:complexType>

    <!-- Patient element - LivingSubjectID -->
    <xs:complexType name="id">
        <xs:attribute name="domain" type="xs:string" use="required"/>
        <xs:attribute name="format" type="xs:string"/>
        <xs:attribute name="min" type="xs:integer"/>
        <xs:attribute name="max" type="xs:integer"/>
        <xs:attribute name="friendlyName" type="xs:string"/>
        <xs:attribute name="label" type="xs:string" use="required"/>
        <xs:attribute name="scope" type="scope" default="0" />
        <xs:attribute name="mandatory" type="xs:boolean" default="false" />
    </xs:complexType>

    <!-- Patient element - LivingSubjectBirthTime -->
    <xs:complexType name="birthDate">
        <xs:attribute name="min" type="xs:integer"/>
        <xs:attribute name="max" type="xs:integer"/>
        <xs:attribute name="friendlyName" type="xs:string"/>
        <xs:attribute name="label" type="xs:string"/>
        <xs:attribute name="scope" type="scope" default="0" />
        <xs:attribute name="mandatory" type="xs:boolean" default="false" />
    </xs:complexType>

    <!-- Deprecated Element -->
    <xs:complexType name="field">
        <xs:attribute name="min" type="xs:integer"/>
        <xs:attribute name="max" type="xs:integer"/>
        <xs:attribute name="friendlyName" type="xs:string"/>
        <xs:attribute name="label" type="xs:string"/>
        <xs:attribute name="scope" type="scope" default="0" />
        <xs:attribute name="mandatory" type="xs:boolean" default="false" />
    </xs:complexType>

    <!-- Patient element - LivingSubjectGender -->
    <xs:complexType name="sex">
        <xs:attribute name="min" type="xs:integer"/>
        <xs:attribute name="max" type="xs:integer"/>
        <xs:attribute name="friendlyName" type="xs:string"/>
        <xs:attribute name="label" type="xs:string"/>
        <xs:attribute name="scope" type="scope" default="0" />
        <xs:attribute name="mandatory" type="xs:boolean" default="false" />
    </xs:complexType>

    <!-- Patient element  generic Identity Traits- LivingSubjectName, PatientAddress -->
    <xs:complexType name="textField">
        <xs:attribute name="min" type="xs:integer"/>
        <xs:attribute name="max" type="xs:integer"/>
        <xs:attribute name="friendlyName" type="xs:string"/>
        <xs:attribute name="label" type="xs:string"/>
        <xs:attribute name="scope" type="scope" default="0" />
        <xs:attribute name="mandatory" type="xs:boolean" default="false" />
    </xs:complexType>

    <xs:simpleType name="scope">
        <xs:restriction base="xs:integer">
            <xs:enumeration value="0"/><!-- PS and eP -->
            <xs:enumeration value="1"/><!-- PS -->
            <xs:enumeration value="2"/><!-- eP -->
        </xs:restriction>
    </xs:simpleType>

    <xs:element name="id" type="id"/>
    <xs:element name="textField" type="textField"/>
    <xs:element name="birthDate" type="birthDate"/>
    <xs:element name="sex" type="sex"/>
    <xs:element name="field" type="field"/>
</xs:schema
<?xml version="1.0" encoding="utf-8"?>
<searchFields>
  <country code="str1234" friendlyName="str1234" label="str1234">
    <patientSearch scope="0">
      <id domain="str1234" format="str1234" min="1234" max="1234" friendlyName="str1234" label="str1234" scope="0" mandatory="true" />
      <textField min="1234" max="1234" friendlyName="str1234" label="str1234" scope="0" mandatory="true" />
      <birthDate min="1234" max="1234" friendlyName="str1234" label="str1234" scope="0" mandatory="true" />
      <sex min="1234" max="1234" friendlyName="str1234" label="str1234" scope="0" mandatory="true" />
    </patientSearch>
    <documentSearch friendlyName="str1234" label="str1234" mandatory="true">
      <documentId domain="str1234" format="str1234" min="1234" max="1234" friendlyName="str1234" label="str1234" scope="0" mandatory="true" />
      <pinCode domain="str1234" format="str1234" min="1234" max="1234" friendlyName="str1234" label="str1234" scope="0" mandatory="true" />
    </documentSearch>
  </country>
</searchFields>

5.2) OpenNCP implementation:


5.3) OpenNCP Technical Components impacted:

The table below is presenting all the OpenNCP components part of the Reference Implementation, the aim is to highlight clearly which component would be impacted and updated by the CP.


Assertion Validator

Audit Manager

CDA Display Tool

CDAUtils

TSAM Exporter

XSLTransformer




Configuration Manager
Yes
Consent Manager

Data Model
Yes
Default Policy Manager
Yes
Non Repudiation

eADC

OpenATNA



Common Components

Configuration Init

Configuration Utility

Database Initializer

Discovery Client

Yes

Yes

Yes

Yes

Gateway
Yes
Remote Validation

Portals

OpenNCP Portal

OpenNCP Web Portal

Yes

Yes

OpenStork

Protocol Terminators

WS Server

Client Connector

Client Connector Consumer

Common Interfaces

Yes

Yes

Yes

Yes

Security Manager

Transformation Manager

TRC STS

TRC STS

TRC STS Client

Yes

Yes

TSAM

TSAM Synchronizer

Utillity

6) References:

eHDSI Specifications: https://ec.europa.eu/cefdigital/wiki/x/30QZAg

IHE Technical Framework (Revision 9):

Volume 1: ftp://ftp.ihe.net/DocumentPublication/Archive/ITInfrastructure/2012/Published/IHE_ITI_TF_Rev9.0_Vol1_FT_2012-08-31.pdf

Volume 2a: ftp://ftp.ihe.net/DocumentPublication/Archive/ITInfrastructure/2012/Published/IHE_ITI_TF_Rev9.0_Vol2a_FT_2012-08-31.pdf

Volume 2b: ftp://ftp.ihe.net/DocumentPublication/Archive/ITInfrastructure/2012/Published/IHE_ITI_TF_Rev9.0_Vol2b_FT_2012-08-31.pdf

Volume 2x: ftp://ftp.ihe.net/DocumentPublication/Archive/ITInfrastructure/2012/Published/IHE_ITI_TF_Rev9.0_Vol2x_FT_2012-08-31.pdf

Volume 3: ftp://ftp.ihe.net/DocumentPublication/Archive/ITInfrastructure/2012/Published/IHE_ITI_TF_Rev9.0_Vol3_FT_2012-08-31.pdf

  • No labels