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

Steps to be performed by the NCPeH configuring the NCPeH TG in production environment



1) Request TLS Certificate for Production Environment

Request the services of the CEF eDelivery PKI according to the (eDelivery)(PKI for eHealth)(SOD)(1.00) for production environment and follow the process of:

  • Certificate request (by NCPeH)
  • Certificate approval (by eHDSI Owner)
  • Certificate retrieval (by NCPeH)
2) Request Digital Signature Certificate for Production Environment

3) Set up of the NCPeH TG: Add Certificates to the NCPeH TG Key Store

Set up NCPeH TG for SMP
1) (NCP-A) Request TLS Certificate info registration in SMP
  • Send an email request to the eHDSI Central Service Desk:
    • The NCPeH should provide to eHDSI Central Service Desk the public part of TLS certificate (CS-C1) received by the European Commission under the CEF PKI. This certificate will allow the support to retrieve the following information from the attribute DN (CN, O, C and Serial Number). The preferred format would be a PEM encoded file.
  • SMP administrator should create the Service Group of the MS
2) (NCP-A) REGISTER - upload information to SMP Sever
  • Before uploading any configuration file, the NCPeH might need to request to the eHDSI Central Service Desk a default Trust store including the public part of the SMP Server Signature Certificate (and its issuer chain) and also for the SML endpoints.
3) (NCP-B) Set up NCPeH TG for SMP
  •  Sync international patient search masks
Set up NCPeH TG for CTS

1) Request user Credentials

Personal Data Protection

The personal data of the CTS users are processed in accordance with REGULATION (EU) 2018/1725 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data.

In order to request user CTS credentials for the NCPeH, please send a mail to the eHDSI Central Service Desk as follows:

  • Sender: the main contact point for the country NCPeH (person officially authorized by eHMSEG representative for the Jurisdictional Domain to be in charge)
  • Recipient:
  • Subject: CTS Credentials for Production Environment (XX - Country code)
  • Content:
    • Jurisdictional domain → ONLY the first time the NCPeH enters production environment - the name of the official institution / organization to run the NCPeH
    • First name, Last name and Email address of the user.
    • User(s) Role(s):
      • [MANDATORY] Terminology Author / Curator → Country Terminology Responsible
      • [MANDATORY] Terminology Translator → Country Terminology Translator
      • Terminology Mapper → Country Terminology Mapper (Transcoder)
      • [MANDATORY] Terminology User → NCPeH (TSAM-SYNC) (please provide a functional mailbox for this user)
    • Language(s) the NCPeH is going to use
    • Please confirm that your national NCPeH is compliant with the licensing conditions required to use SNOMED CT (for more information on the Conditions and Terms of Use of the Code Systems employed in the MVC, please check this page)
  • Follow up:
    • Once the user credentials are created, each user will receive an automatic email containing an activation link in order to activate the account and set a password.
2) Content Preparation
  • Please make sure you are using UTF-8 for excel files.
  • Take care not to trim zeros in the beginning of codes when exporting and/or saving the file
  • Load Translations
    • Login to the Production Environment of CTS and download the translations from there
    • Fill in the XLS file (MVC 2.2.2)
    • Login to the Production Environment of CTS and upload the downloaded translations there

      If the MS Terminology responsible would like to re-use the translations available in Acceptance Environment, the MTC should be downloaded from Acceptance Environment but before the upload into the Production Environment, the Unique Identifier for each ValueSet should be updated (Row B:4) according to the official eHDSI MVC published. The file attached is providing the list of ValueSet and their Unique Identifier eHDSI-MVC-2.2.2-ValueSet_UID.
  • Load Transcodings
    • Load National Code Systems (submit a request to Solution Provider -
    • Load Mappings
      • Solution Provider will verify if the mapping can use a similar pattern as Translations (export from Acceptance, redefine the UID, and upload to Production).
  • Approve MTC
  • Sync (download) MTC to NCPeH TG
  • Run TSAM-Exporter (for Country-Bs using the CDA Display Tool)


According to the test plan defined in the Test Framework: eHDSI Production Environment Testing

  • Apply to perform the test session by submitting email to eHDSI Central Service Desk:
    • Inform the eHDSI Central Service Desk for the time-frame when the NCPeH wants to perform the Production Environment Testing
    • The eHDSI Central Service Desk should acknowledge by a return email the conditions for the test, and namely:
    → Partners the NCPeH need to perform the tests with
    → Any other particular aspect relevant to your NCPeH readiness criteria


  1. Network Configurations:

    • Set up host name
    • Define you NCPeH TESTA IP address
    • Configure firewalls to accept incoming and outgoing communications with specific partners
    1. Please add this information as a very first step, even before the certificates.

  2. In the SMP part, please indicate which certificate is meant here, TLS or User (Signature).

    1. Dear Konstantin HYPPÖNEN

      As far as I can understand, this comment has already been clarified in the instructions provided in the page.

      • Regarding the SMP, we are speaking of the TLS certificate.

      Could you please confirm if that is the case (comment clarification already present)?

      Thank you for your time and attention

  3. Thank you to Evelina RUSEVA for drawing my attention to this specific page!  Previously, we were cooking Go Live according to our own recipes.  On a more serious note: we would like to see MVC 3.0.0 here, thanks.