HEALTH-ER

Work programme

Six work packages over twenty-four months

From requirements and architecture, through the AI components and the framework itself, to validation in operating hospitals — and the communication, exploitation and standardisation that runs alongside all of it.

work packages
6
months
24
partners
12
Member States
6

Work packages

What each one does

WP1

Project Management

Lead: OSI

Overall management of the project and consortium: coordination and decision making, technical management, legal, financial and administrative duties, quality assurance and risk management.

Tasks

  • T1.1Project coordination, decision making and conflict resolution(OSI)

    Effort and budget management, scheduling and preparation of meetings, monitoring project activities through regular bottom-up reporting, and permanent contact with the Project Officer.

  • T1.2Technical coordination(DOT)

    Scheduling, organising and leading technical activities, coordinating development flow and maintaining close dialogue with the Project Coordinator.

  • T1.3Administrative and operational management, including legal and ethical aspects(OSI)

    Correct management from a legal, ethics and security perspective, including the design and execution of the Data Management Plan.

  • T1.4Quality assurance(TRY)

    Quality control of planned actions and schedules, benchmarking of milestones, and control of quality and consistency against technical and contractual aspects.

WP2

Requirements elicitation, mapping, and architecture specification

Lead: TRY

Analysis of EU healthcare cybersecurity needs and regulations, description of the pilot infrastructures, the knowledge and capacity building plan, and the technical specification of the HEALTH-ER framework.

Tasks

  • T2.1Analysis and mapping of healthcare cybersecurity needs and challenges(TRY)

    A complete overview of EU healthcare security aspects, challenges, strategies and guidelines, classified and mapped to the design of the HEALTH-ER framework and services.

  • T2.2End users' requirements including regulatory aspects(EPBS)

    Collection of end-user requirements covering technical, operational, regulatory and legal aspects of hospitals, healthcare providers, industry partners, SMEs and medical device manufacturers.

  • T2.3Platform design and technical specifications(DOT)

    The reference architecture: core SOCaaS components, security solutions and services, and the knowledge and capacity services. Modular, scalable, flexible and interoperable, with open APIs and accessible user interfaces.

  • T2.4Knowledge and capacity building plan(EU-INSPIRE)

    Identification of key stakeholders and users, and definition of processes and tools for skills upscaling, training and awareness, mentoring and partnership building.

WP3

Innovative AI-based solutions, enablers and technical plans

Lead: DOT

Adaptation of hospital baseline tools, the AI-based attack prediction and behaviour analytics components, and the technical plans for resilience, business continuity and cost effectiveness.

Tasks

  • T3.1Adaptations for connecting the platform with hospital security systems and baseline tools(DOT)

    Identification and analysis of existing security systems and baseline tools inside the pilot hospitals, adjusted and enhanced to connect with the HEALTH-ER platform.

  • T3.2Enhanced preparedness and AI-based attack prediction for medical systems and devices(OSI)

    Behavioural models trained per system to deliver an estimated probability of anomalous behaviour, independent of the underlying protocols, data formats or architectures.

  • T3.3AI-based user and entity behaviour analytics for healthcare(OSI)

    A baseline of normal behaviour for users such as doctors, nurses and administrative staff, and for entities such as infusion pumps, EHR systems and IoT devices, with deviation detection.

  • T3.4Technical plans for enhanced resilience, business continuity and cost effectiveness(TRY)

    Structured, practical roadmaps tailored to the operational, financial and regulatory context of each healthcare provider, rather than generic templates.

WP4

Development of the HEALTH-ER framework

Lead: OSI

The information exchange block, the AI-based SOCaaS platform for monitoring, orchestration, automation and response, the training and capacity-building services, and the first release of the framework.

Tasks

  • T4.1Information exchange, CTI discovery and EU-compliant reporting(DOT)

    EU-compliant reporting, CTI sharing and collaborative threat hunting, built on widely accepted standards to ensure interoperability beyond the borders of a single Member State.

  • T4.2AI-based SOCaaS for security monitoring, orchestration, automation and response(OSI)

    The adaptive SOAR, healthcare incident-response and business-continuity playbooks, and the AI situational awareness components, orchestrated into client-specific tenants.

  • T4.3User training, knowledge and capacity building(EPBS)

    Courses and education programmes, awareness workshops, mentoring and consulting, and a cyber-range training service adjusted to the healthcare sector.

  • T4.4HEALTH-ER framework for resilient EU healthcare - first release(OSI)

    Integration and delivery of the MVP, with preliminary validation of the individual blocks before deployment in the pilots.

WP5

Validation activities and refinements towards deployment

Lead: FHRS

The evaluation methodology, prototype demonstration and validation in real hospital infrastructures, assessment for different end users, and the refinements leading to the final release.

Tasks

  • T5.1Evaluation methodology, setup and configuration of the trials(FHRS)

    Final pilot definition, mapping end-user service requirements against the developed components, and the overall validation methodology and testing protocol.

  • T5.2Prototype demonstration and validation(OSI)

    Testing and validation of the integrated platform against configuration and integration quality, functionality, and protection against security attacks.

  • T5.3Platform assessment for different end users(FPH)

    Fully operational pilots assessed for performance gains, module and system performance, results against KPIs, lessons learned, and total cost of ownership.

  • T5.4Refinements towards the final framework(OSI)

    Agile development cycles producing incremental releases informed by a continuous flow of feedback from the validation activities.

WP6

Communication, Dissemination, Exploitation and Standardisation

Lead: HOPE

The dissemination and communication strategy, the exploitation and IPR plan, and engagement with stakeholders, the European Commission, national authorities and standardisation bodies.

Tasks

  • T6.1Communication and dissemination activities(HOPE)

    The public web portal, leaflets, posters and slides, project branding, social media strategy, media content, newsletters, publications, workshops and events.

  • T6.2Impact creation and exploitation of results(EPBS)

    Market-oriented analysis, identification of exploitable results, the exploitation strategy and business models based on the Business Model Canvas, and monitoring of IPR issues.

  • T6.3Stakeholder, EC and national authority engagement and standardisation(CYS)

    A database of external institutional and domain-focused stakeholders, constant interaction, and engagement with standardisation fora to present and contribute results.

For the consortium

The deliverable register, the milestone checkpoints and the indicator tracker are maintained in the consortium area, together with the reporting templates and the documents that are not published.

Go to the consortium area →