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

Infomation

DG SANTE, CEF eHealth DSI, 2019

Reuse is authorised, provided the source is acknowledged.

For further information, please contact the email eHDSI Solution Provider

Matrix of eHDSI Requirements, Functional Specifications and Technical Bindings


Relationship between the eHDSI Requirements, Functional Specifications and Technical Bindings:

  • The Business and Solution Requirements describe WHAT is required from the eHDSI infrastructure.
  • The Functional Specifications describe WHAT is required from a software application/component part of the eHDSI architecture, independently of the technology used (technology agnostic specifications).
  • The Frameworks and Technical Bindings describe the ways HOW to deliver what the functional specifications require (how the specified functionalities are implemented within eHDSI).

The below table provides an overview of the eHDSI requirements, functional specifications and technical bindings and the link between them for understandability and traceability purposes.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

#Business Requirements

Solution Requirements (Functional and Non-functional Requirements)

Functional Specifications

Frameworks and Technical Bindings

eHN/eHDSI Guidelines
1

PS Use Case

eP/eD Use Case





2

01. Ensure Health Professional (HP) Identification, Authentication and Authorization

01.01. Uniquely identify and authenticate the Health Professional (HP) in Country of treatment



301.02. Authorize Health Professional (HP) according to assigned roles and profiles
402. Ensure Patient Identification

02.01. Uniquely identify the Patient



503. Create and apply policies and procedures to ensure trust between countries


03.01. Manage Incidents, Problems and Support services












603.02. Manage the changes to the cross-border services
703.03. Assess and validate the cross-border services
803.04. Education, training and awareness among citizens of the cross-border services
904. Ensure lawful processing of personal and health data


04.01. Identify the applicable legal basis, the controller(s) and processor(s) of the personal and health data and their responsibilities




1004.02. Identify the controller(s) and processor(s) of the personal and health data and their responsibilities
1104.03. Inform patients about their rights as concerns the protection of their personal and health data
1204.04. Ensure compliance of the eHDSI central services with the applicable data protection provisions
1305. Make Patient Summary available to HP

05.01. Create the eHDSI Patient Summary content
1405.02. Transcode, translate and exchange cross-border the Patient Summary
1505.03. Display the Patient Summary to the Health Professional

1606. Make ePrescription available to HP

06.01. Create the eHDSI ePrescription(s) content


1706.02. Transcode, translate and exchange cross-border the ePrescription
1806.03. Display the ePrescription to the Health Professional

1907. Handle Dispensation of medicine and Substitution07.03. Inform Country of affiliation about the dispensed medicine07.04. Option to discard a previously performed dispensation07.01. Create the eHDSI eDispensation content
2007.02. Inform Country of affiliation about the dispensed medicine
2107.03. Inform Country of affiliation about the dispensed medicine
2207.04. Option to discard a previously performed dispensation
2308. Ensure high quality information (structured, equivalent, understandable) is exchanged between countries

08.01. Ensure structured and coded information is exchanged between countries
2408.02. Ensure equivalent information is exchanged between countries


2508.03. Ensure understandable information is exchanged between countries


2609. Ensure the security, performance, traceability and auditability of the services, data and systems




09.01. Ensure confidentiality of the services, data and systems




2709.02. Ensure the integrity of the exchanged data

2809.03. Ensure service availability

2909.04. Ensure and monitor service performance


3009.05. Ensure traceability of the exchanged data


3109.06. Ensure auditability of the exchanged data

3210. Ensure the non-repudiation of the exchanged data10.01. Handle the non-repudiation mechanism



 

Responsibilities

Policy

"Why ?"

Content

"What ?"

Behaviour

"How ?"

Implementation

"Where ?"

Business Viewpoint

Information ViewpointComputational ViewpointEngineering Viewpoint

Conceptual

Stakeholders

Business Analysts

Semantic Analysts

Business Analysts

Functional Analysts

Enterprise Architects

Logical

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

2 Comments

  1. Title of the Solution Requirement Nr. 04.02. in Matrix should be probably  -"Identify the controller(s) and processor(s) of the personal and health data and their responsibilities".

    There is two times the same requirement title - under 04.02. and 04.03. thank you for correction (smile)

    1. Thank you Eva, the update has been done (smile)