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


DG SANTE, CEF eHealth DSI, 2019

Reuse is authorised, provided the source is acknowledged.

For further information, please contact the email eHDSI Solution Provider


[3.0.0.RC] Wave 3 Release Candidate are now available.

  • Please give a look and provide feedback

eHDSI Interoperability Specifications

eHealth DSI Interoperability Specifications (2.2.0 - Wave 2 Operation Ready)

Relationship between the eHDSI requirements and eHDSI interoperability specifications:

  • The requirements are the WHATspecifications are the HOW => Specifications are describing the ways HOW to deliver what the requirements wants.

To know more on eHealth DSI Interoperability Specifications, please give a look:




"Why ?"


"What ?"


"How ?"


"Where ?"

Business Viewpoint

Information ViewpointComputational ViewpointEngineering Viewpoint



Business Analysts

Semantic Analysts

Business Analysts

Functional Analysts

Enterprise Architects


Project Managers

Business Process Experts

Business Process Experts

Semantic Analysts

Solution ArchitectsApplication Architects
ImplementableManagersInformation ModelersSystems Engineers

Application Developers

 *Source: HL7 Service-Aware Interoperability Framework (SAIF) and Enterprise Conformance Compliance Framework (ECCF) stack

  • No labels


  1. Suggestion to add in the table the analysis made by DIGIT on SMP/ICD, here is the latest draft I have. Jerome SUBIGER, could you let us know once the document is final? Thanks in advance.

  2. The following document  "D3.8.2Final National Pilot Set Up and Deployment Guide" contains some chapters related to:

    • NCP operating organisation (including incident management...)
    • Security organisation
    • Auditing organisation
    • etc.

    Maybe a new category of specification related to Operations could be included?

  3. openNCP Deployment
    Should we update it to NCPeH Deployment Guide?
  4. Dear Community,

    What 2 or 3 documents would you recommend as a good starting point to get in hand with the OpenNCP framework for a developer ?

    I was thinking of :

    Thank you very much in advance for your valuable feedbacks !

    1. Dear Antoine.chaudieres, the 3 documents listed above are the most valuable to start with the OpenNCP, in any case the column "How" of the specifications table is the best place for a technical actor.

      The eP and PS functional requirements might be also useful to get the context of the project. I assume among the read, you will need to investigate the others documents also based on the topic investigated.

      Please do not hesitate if you have any question.

  5. I would only add that, for understanding how the specs are organised, the following one would also be a good reading:

  6. Where can I find the Deployment Plan template? It is referenced in the previous version of deployment guide (2.2.0, March 2017) but the link points to the page where only the guide is available...

    It seems it is necessary for the audit!


    1. APP 1 – SDP&PPR

      (Row: Implementable; Column: Implementation)

      Did it help?

  7. The linked page CDA Implementation Guides does not include direct links to eP and PS Art Decor templates (the actual formal artifacts). Could these be added?

  8. Interoperability Specification [+]
    What do we need to do with this specification document, content might be duplicated with Business Requirement, functional and at some point also technical?
    1. Good morning Jerome SUBIGER

      Good question.

      According to my understanding, this document should describe "How the eHDSI specifications are organised".

      • And that's in fact what it is in chapter 1.

      Chapter 2 and 3 can be considered conceptual perspectives specification, and that should not overlap with any other document in the eHDSI specs package.

      Regarding 4,5 and 6, after reading i have some doubts if they don't overlap (as you mention).

      My recommendation is to keep it for now, and add as OPEN POINT (in the release notes):

      • Clear overlaps and redundant content from "Interoperability Specifications".

      Sounds good?