top of page

Work Plan

The workplan is analysed in this section. The overall work plan is defined in the PERT diagram below. One important feature of the workplan is to ensure the proper implementation of content of the new regulation for the EHDS. This has been one of the main points in the conception of the overall work plan that has two main groups of work packages. 1. Work packages 1 to 4 that have a horizontal view of the project dealing with issues such as project management and technical project management (WP1), dissemination and education (WP2), evaluation (WP3) and sustainability governance and assessment (WP4). 2. Work packages 5 to 9 that deals with the specific requirements and technical specifications than need to be in place for the adoption of the new regulation by the MS. WP5 will define the general requirements for the adoption of the EEHRxF in EHRs to be used in the European DSM. WP6 will provide technical documentation to allow and enforce the adoption of patient summaries and ePrecription/eDispensation specifications in EHRs across Europe. WP7 will define the needed technical documentation so that the new documents of the EEHRxF, as defined in the X-eHealth project and already adopted for implementation within Myhealth@EU services, can be included in EHR products and solutions in Europe. WP8 will prepare the technical documentation (means of verifications, checklists, conformity assessment assertions) so that the certification/labelling processes can be adopted by MS across Europe in full conformance with the requirements of the regulation. WP9 will provide groundwork to define use cases and technical specification for the implementation of cross border telemedicine services. In the work packages below several terms are used. A short set of definitions are provided. A requirement is a statement of what the software should do. It is a high-level description of a feature or functionality that the software should provide to the user. Requirements are usually written from the perspective of the end-user or the customer and are used to capture the stakeholders' needs and expectations. A specification, on the other hand, is a detailed description of how the software should be built to meet the requirements. It outlines the design, functionality, and performance criteria of the software. A specification is a technical document that provides a clear understanding of how the software should behave, what inputs it should accept, and what outputs it should produce. In summary, a requirement defines what the software should do, while a specification defines how it should be done. Requirements provide the foundation for the software development process, while specifications provide the blueprint for building the software. Implementation guides for interoperability in healthcare are documents that provide detailed instructions on how to implement interoperability solutions between different healthcare systems and technologies considering integration profiles and international specifications that can be verified and tested.

bottom of page