Objectives:Although there is increased awareness of patient and public involvement (PPI) among health technology assessment (HTA) organizations, evaluations of PPI initiatives are relatively scarce. Our objective as members of Health Technology Assessment International's (HTAi's) Patient and Citizen Involvement Group (PCIG) was to advance understanding of the range of evaluation strategies adopted by HTA organizations and their potential usefulness.Methods:In March 2016, a survey was sent to fifty-four HTA organizations through the International Network of Agencies for Health Technology Assessment (INAHTA) and contacts of members of HTAi's PCIG. Respondents were asked about their organizational structure; how patients and members of the public are involved; whether and how PPI initiatives have been evaluated, and, if so, which facilitators and challenges to evaluation were found and how results were used and disseminated.Results:Fifteen (n= 15) programs from twelve countries responded (response rate 27.8 percent) that involved patients (14/15) and members of the public (10/15) in HTA activities. Seven programs evaluated their PPI activities, including participant satisfaction (5/7), process (5/7) and impact evaluations (4/7). Evaluation results were used to improve PPI activities, identify education and training needs, and direct strategic priorities. Facilitators and challenges revolved around the need for stakeholder buy-in, sufficient resources, senior leadership, and including patients in evaluations.Conclusions:A small but diverse set of HTA organizations evaluate their PPI activities using a range of strategies that reflect the range of rationales and approaches to PPI in HTA. It will be important for HTA organizations to draw on evaluation theories and methods.
Although patient preferences have been studied broadly for marketed products or around the time of submission to authorities and launch, patient preference studies have rarely been used during the early drug development phases. In this paper, we formulate three hypotheses supporting the use of patient preference studies in early product development: (1) integration of the patient perspective into the development process from phase 1 onwards will result in healthcare solutions with outcomes that best address patients' needs; (2) a structured process to build patient-based evidence involving partnerships between patients and other key stakeholders will improve alignment of development activities with the needs of patients; (3) quantitative patient preference research built on robust qualitative insights is necessary to strengthen development decisions in the interests of patients. To illustrate such a structured process, we describe qualitative insights research (social media analysis and online bulletin boards) and quantitative patient preference studies in dry eye disease and non-alcoholic steatohepatitis conducted during early product development by a pharmaceutical company to generate patient-based evidence. The outputs from such early patient preference studies are being used to inform patient reported outcome strategies, clinical development strategies, product design and delivery features, and form the basis for early dialog with regulators, health technology assessment (HTA) bodies and payers to ensure focus and alignment on patient-relevant endpoints. Furthermore, to discuss and theoretically substantiate our hypotheses, we review how different groups and organizations are working to embrace fully the patient perspective in product development and healthcare decision-making. The hypotheses are commensurate with the general trend toward patient-centered healthcare and the activities initiated by regulators, HTA agencies, and patient organizations. We advocate that all healthcare players should actively contribute to aligning on best practices concerning choice of methodologies and engage in multi-stakeholder dialog along the entire product development chain, to realize health technologies that best meet the needs of patients.
Background: Patient blood management (PBM) describes a set of evidence-based practices to optimize medical and surgical patient outcomes by clinically managing and preserving a patient’s own blood. This concepts aims to detect and treat anemia, minimize the risk for blood loss and the need for blood replacement for each patient through a coordinated multidisciplinary care process. In combination with blood loss, anemia is the main driver for transfusion and all three are independent risk factors for adverse outcomes including morbidity and mortality. Evidence demonstrates that PBM significantly improves outcomes and safety while reducing cost by macroeconomic magnitudes. Despite its huge potential to improve healthcare systems, PBM is not yet adopted broadly. The aim of this study is to analyze the collective experiences of a diverse group of PBM implementors across countries reflecting different healthcare contexts and to use these experiences to develop a guidance for initiating and orchestrating PBM implementation for stakeholders from diverse professional backgrounds.Methods: Semi-structured interviews were conducted with 1–4 PBM implementors from 12 countries in Asia, Latin America, Australia, Central and Eastern Europe, the Middle East, and Africa. Responses reflecting the drivers, barriers, measures, and stakeholders regarding the implementation of PBM were summarized per country and underwent qualitative content analysis. Clustering the resulting implementation measures by levels of intervention for PBM implementation informed a PBM implementation framework.Results: A set of PBM implementation measures were extracted from the interviews with the implementors. Most of these measures relate to one of six levels of implementation including government, healthcare providers, funding, research, training/education, and patients/public. Essential cross-level measures are multi-stakeholder communication and collaboration.Conclusion: The implementation matrix resulting from this research helps to decompose the complexity of PBM implementation into concrete measures on each implementation level. It provides guidance for diverse stakeholders to design, initiate and develop strategies and plans to make PBM a national standard of care, thus closing current practice gaps and matching this unmet public health need.
1 September 2019 in Value in Health Regional Issues
Countries with expanding healthcare coverage (CEHCs) increasingly use external reference pricing (ERP) for pharmaceuticals. The ERP policies must aim to optimize efficiency, minimize disturbances, and maximize access to effective therapies for all patients. This research aims to deduce best practices for prudent ERP regulations from past experiences and currently applied policies and to guide policymakers in CEHCs in implementing robust ERP policies. The literature was reviewed for methods and effects of ERP for pharmaceuticals. Pharmaceutical pricing experts from Asia, the Middle East, Russia, and South Africa were surveyed for current approaches to ERP in their respective countries. Key determinants of ERP relate to scope, number, and choice of reference countries; price definitions; computation rules; frequency; and stringency of applying ERP. The scarce evidence shows that ERP seems to lead to narrower price windows with the risk of reducing prices in high-price countries and raising prices in low-price countries. Moreover, launch delays and indirect price effects are often observed. The ERP policies in CEHCs are often applied in isolation, not always in a consistent and transparent manner, neglecting its indirect effects. Policymakers should consider a set of requirements when introducing ERP, including clear definitions and decision criteria in full transparency. External reference pricing should inform and serve as a benchmark for pricing decisions, rather than being used as the sole pricing mechanism. External reference pricing is primarily a tool to support decisions regarding on-patent pharmaceuticals, and for off-patent products, competition may prove more effective in reducing prices than ERP.