The aim of this Deliverable is to define the concept of Public Health Policy (PHP) and present a state-of-the-art on PHPs development, and to propose a first approach to the modelling and evaluation of PHPs that will be used in the Policy Development Toolkit (PDT) to support PHPs evaluation and development for policy-makers.
Deliverable 5.1, as a milestone of Task 5.1, is devoted to the modelling and evaluation of Public Health Policies. The present document introduces the definition of Public Health Policy after the consensus among the experts of the CrowdHEALTH project. It also defines the conceptual design and methodologies proposed for modelling PHPs. Furthermore, this document proposes a design of three components that are part of the overall architecture; specifically, these components are subsystems of the Policy Development Toolkit to be developed in Work Package 5 (WP5): The Policies’ Modelling component, the Population Identification component, and the Policy Evaluation component, which are aimed at aiding policy-makers in the creation of PHPs.
After a brief introduction of the function of this Deliverable in the CrowdHEALTH Project, Section 3 introduces a definition of what a PHP is, including state-of-the-art concepts on PHP development that cover why, what, and how they are developed and who are actively or passively affected by the PHPs. Additionally, how PHPs can be effectively evaluated and followed-up are introduced in this Section, through the definition of Key Performance Indicators (KPIs). Afterwards, state-of-the-art on PHP best practices is described in Section 4 stressing on Non-Communicable Diseases (NCDs). In Section 5, a description of the potential methodologies to be applied on PHP modelling is given, based mainly on the concepts of ontology and semantic reasoning technologies. Finally, Sections 6, 7, and 8 propose an initial approach on the modelling of PHPs and their evaluation based on the concept of KPIs. We have to take into account that application of these proposals or different alternatives are pending due to technical requirements and agreements that we will tackle through the development of this task.