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

eHDSI Services

The eHDSI Service Blueprint provides an overarching perspective on the services planned in order to reach cross border eHealth interoperability:

eHDSI Service Offering description

SERVICE

PURPOSE

DESCRIPTION

  • Multistakeholder dissemination

Web site publicly available to any stakeholder to promote eHDSI official dissemination content (e.g. new, discover, how it works, services, communities).


  • Resolve End-Users issues

Issue driven platform to gather and track End-Users requests for assistance or support


  • Streamline stakeholders interaction and joint work

In order to boost collaborative work, the toolkit provide, at least, the following tools:

  • Knowledge Sharing through the use of wiki pages (e.g. documentation, meeting minutes, discussions, files management) and a powerful search engine to assist find content.
  • Work Orchestration by providing mechanisms to describe, assign and monitor work tasks to be performed.
  • Teleconferencing facilitating the organisation of remote meetings by providing audio, video and screen sharing.
  • Provide a clear set of policy and business requirements elicit from Regulation, Directives, Implementing acts, policies and guidelines, that drive the specification, implementation and operation


In order to be able to accurately point and trace back requirements from specifications, implementation, test and audit, there is the need for having the following instruments in place:

  • Requirements Source Blueprint
  • Requirements List
  • Requirements Management


  • Provide specifications  that enable the building of NCPeH and the Service Network


Fundamental design information that map requirements into clear indications on what is to be built.

  • Enable NCPeH Service Network establishment through automated configuration management

In order to set up and keep functional the NCPeH Service Network, there is the need for Dynamic Service Location and Capability Lookup services that allow the NCPeH to discover each other and establish trusted communication.

  • Enable MVC distribution and support MTC management

In order to achieve semantic interoperability there is the need for a common vocabulary (Master ValueSet Catalogue – English by default) to describe the clinical data. The MVC should be presented to the End-Users in the MS desired language and code systems. For that, MS should be able to translate, map and transcode (creating the Master Translation/Transcoding Catalogue MTC) according to their national policies.


  • Establish the Tests and Audit requirements that must be fulfilled to enter in the NCPeH Operational Network

Entering the Operational NCPeH Service Network (Go Live) requires a specific level of Conformance and Trust. In order to reach that level the NCPeH (organisation and technical gateway) must undergo specific Test and Audit procedures to gather evidence to fundament the Readiness Statement each MS presents to the eHN when seeking approval to Go Live.

  • Gather evidence about core and generic services performance

Performance monitoring is crucial to understand effective usage of the services and detect defects. In order to achieve performance monitoring it is needed to have in place mechanisms able to collect and report specific performance data. These services (that may come as Specifications, Software or Services) should ease the burden of MS on reporting tasks.


  • Ease MS effort by providing a jointly build NCPeH implementation

The NCPeH technical gateway is one of the core nodes in the Service Network. Since each MS need to deploy an NCPeH based on the same specifications, it was agreed between EC and MS that a reference implementation should be jointly developed, so that knowledge shared and effort distributed among the participating MS.

Service Offering > Users Perspective

Service Offering > Solution Provider Perspective


  • No labels