Clinical Decision Support Systems to Reduce Unnecessary Clostridioides difficile Testing Across Multiple Hospitals.

BACKGROUND: Inappropriate Clostridioides difficile testing has adverse consequences for patients, hospitals, and public health. Computerized clinical decision support (CCDS) systems in the electronic health record (EHR) may reduce C. difficile test ordering; however, effectiveness of different approaches, ease of use, and best fit into healthcare providers' (HCP) workflow are not well understood. METHODS: Nine academic and 6 community hospitals in the United States participated in this 2-year cohort study. CCDS (hard stop or soft stop) triggered when a duplicate C. difficile test order was attempted or if laxatives were recently received. The primary outcome was the difference in testing rates pre- and post-CCDS interventions, using incidence rate ratios (IRRs) and mixed-effect Poisson regression models. We performed qualitative evaluation (contextual inquiry, interviews, focus groups) based on a human factors model. We identified themes using a codebook with primary nodes and subnodes. RESULTS: In 9 hospitals implementing hard-stop CCDS and 4 hospitals implementing soft-stop CCDS, C. difficile testing incidence rate (IR) reduction was 33% (95% confidence interval [CI]: 30%-36%) and 23% (95% CI: 21%-25%), respectively. Two hospitals implemented a non-EHR-based human intervention with IR reduction of 21% (95% CI: 15%-28%). HCPs reported generally favorable experiences and highlighted time efficiencies such as inclusion of the patient's most recent laxative administration on the CCDS. Organizational factors, including hierarchical cultures and communication between HCPs caring for the same patient, impact CCDS acceptance and integration. CONCLUSIONS: CCDS systems reduced unnecessary C. difficile testing and were perceived positively by HCPs when integrated into their workflow and when displaying relevant patient-specific information needed for decision making.

Patient-Centered Clinical Decision Support-Where Are We and Where to Next?

Patient-centered clinical decision support (PC CDS) includes digital health tools that support patients, caregivers, and care teams in healthcare decisions that incorporate patient-centered factors related to four components: knowledge, data, delivery, and use. This paper explores the current state of each factor and how each promotes patient-centeredness in healthcare. We conducted a literature review, reviewing 175 peer-reviewed and grey literature, and eighteen key informant interviews. Findings show a need for more research on how to incorporate patient input into the guideline selection and prioritization for PC CDS, development and implementation of PC CDS tools, technical challenges for capturing patient contributed data, and optimizing PC CDS across various settings to meet patient and caregiver needs. While progress is being made in each of the four components of PC CDS, critical gaps remain.

Implementation and evaluation of an electronic health record-integrated app for postpartum monitoring of hypertensive disorders of pregnancy using patient-contributed data collection.

Remote monitoring of women experiencing hypertensive disorders of pregnancy (HDP) can provide timely life-saving data, particularly if these data are integrated into existing patient and clinical workflows. This pilot intervention of a smartphone application (app) for postpartum monitoring of hypertensive disorders integrates patient-contributed data into electronic health records (EHRs) to support monitoring and clinical decision-making. Results from the evaluation of the pilot highlight the resources needed when implementing the app, challenges for integrating an app into the EHR, and the usability and utility of the HDP monitoring app for patient and clinician users. The implementation team's key observations included the importance of a local clinical champion, more robust patient involvement and support for the remote patient monitoring program, an impetus for EHR developers to adopt data integration standards, and a need to expand the capabilities of the standards to support interventions using patient-contributed data.

The Technology Landscape of Patient-Centered Clinical Decision Support - Where Are We and What Is Needed?

Patient Centered Outcomes Research (PCOR) and health care delivery system transformation require investments in development of tools and techniques for rapid dissemination of clinical and operational best practices. This paper explores the current technology landscape for patient-centered clinical decision support (PC CDS) and what is needed to make it more shareable, standards-based, and publicly available with the goal of improving patient care and clinical outcomes. The landscape assessment used three sources of information: (1) a 22-member technical expert panel; (2) a literature review of peer-reviewed and grey literature; and (3) key informant interviews with PC CDS stakeholders. We identified ten salient technical considerations that span all phases of PC CDS development; our findings suggest there has been significant progress in the development and implementation of PC CDS but challenges remain.

Challenges and opportunities for advancing patient-centered clinical decision support: findings from a horizon scan.

OBJECTIVE: We conducted a horizon scan to (1) identify challenges in patient-centered clinical decision support (PC CDS) and (2) identify future directions for PC CDS. MATERIALS AND METHODS: We engaged a technical expert panel, conducted a scoping literature review, and interviewed key informants. We qualitatively analyzed literature and interview transcripts, mapping findings to the 4 phases for translating evidence into PC CDS interventions (Prioritizing, Authoring, Implementing, and Measuring) and to external factors. RESULTS: We identified 12 challenges for PC CDS development. Lack of patient input was identified as a critical challenge. The key informants noted that patient input is critical to prioritizing topics for PC CDS and to ensuring that CDS aligns with patients' routine behaviors. Lack of patient-centered terminology standards was viewed as a challenge in authoring PC CDS. We found a dearth of CDS studies that measured clinical outcomes, creating significant gaps in our understanding of PC CDS' impact. Across all phases of CDS development, there is a lack of patient and provider trust and limited attention to patients' and providers' concerns. DISCUSSION: These challenges suggest opportunities for advancing PC CDS. There are opportunities to develop industry-wide practices and standards to increase transparency, standardize terminologies, and incorporate patient input. There is also opportunity to engage patients throughout the PC CDS research process to ensure that outcome measures are relevant to their needs. CONCLUSION: Addressing these challenges and embracing these opportunities will help realize the promise of PC CDS-placing patients at the center of the healthcare system.

The technical landscape for patient-centered CDS: progress, gaps, and challenges.

Supporting healthcare decision-making that is patient-centered and evidence-based requires investments in the development of tools and techniques for dissemination of patient-centered outcomes research findings via methods such as clinical decision support (CDS). This article explores the technical landscape for patient-centered CDS (PC CDS) and the gaps in making PC CDS more shareable, standards-based, and publicly available, with the goal of improving patient care and clinical outcomes. This landscape assessment used: (1) a technical expert panel; (2) a literature review; and (3) interviews with 18 CDS stakeholders. We identified 7 salient technical considerations that span 5 phases of PC CDS development. While progress has been made in the technical landscape, the field must advance standards for translating clinical guidelines into PC CDS, the standardization of CDS insertion points into the clinical workflow, and processes to capture, standardize, and integrate patient-generated health data.

Integrating a Patient Engagement App into an Electronic Health Record-Enabled Workflow Using Interoperability Standards.

BACKGROUND: Patient use of mobile health applications is increasing. To promote patient-centered care, data from these apps must be integrated into clinician workflows within the electronic health record (EHR). Health Level 7 Fast Healthcare Interoperability Resources (FHIR) offers a standards-based application programming interface (API) that may support such integration. OBJECTIVE: We aimed to use interoperability standards to integrate a patient mobile application (coronavirus 2019 [COVID-19] Tracker) with an EHR. The COVID-19 Tracker engages patients by sending introductory and reminder text messages, collecting vital signs and symptom data from COVID-19 patients, and providing actionable guidance if concerning issues are identified. This case report explored the use of FHIR APIs to integrate the app into EHR-enabled clinical workflows. METHODS: The authors used notes from project meetings and from semistructured discussions among the application development team to track the design and implementation processes. Seven points of integration between the application and the EHR were identified, and approaches using FHIR to perform these integrations were delineated. RESULTS: Although this clinical decision support integration project benefited from its standards-based approach, many challenges were encountered. These were due to (1) partial implementation of the FHIR standard in the EHR, particularly, components needed for patient engagement applications; (2) limited experience with the adoption of FHIR standards; and (3) gaps in the current FHIR standard. Alternative approaches, often not based on interoperability standards, were developed to overcome these limitations. CONCLUSION: Despite the challenges encountered due to the early stages of FHIR development and adoption, FHIR standards provide a promising mechanism for overcoming longstanding barriers and facilitating the integration of patient engagement apps with EHRs. To accelerate the integration of apps into clinical workflows, additional components of the FHIR standard must be implemented within the EHR and other clinical systems. Continued expansion of available FHIR resources will help with tighter workflow integration.

Potential Uses of Blockchain Technology for Outcomes Research on Opioids.

The scale and severity of the opioid epidemic call for innovative, multipronged solutions. Research and development is key to accelerate the discovery and evaluation of interventions that support pain and substance use disorder management. In parallel, the use and integration of blockchain technology within research networks holds the potential to address some of the unique challenges facing opioid research. This paper discusses the applications of blockchain technology and illustrates potential ways in which it could be applied to strengthen the validity of outcomes research on the opioid epidemic. We reviewed published and gray literature to identify useful applications of blockchain, specifically those that address the challenges faced by opioid research networks and programs. We then convened a panel of experts to discuss the strengths, limitations, and feasibility of each application. Blockchain has the potential to address some of the issues surrounding health data management, including data availability, data sharing and interoperability, and privacy and security. We identified five primary applications of blockchain to opioids: clinical trials and pharmaceutical research, incentivizing data donation and behavior change, secure exchange and management of e-prescriptions, supply chain management, and secondary use of clinical data for research and public health surveillance. The published literature was limited, leading us to rely on gray literature, which was also limited in its discussion of the technical aspects of implementation. The technical expert panel provided additional context and an assessment of feasibility that was lacking in the literature. Research on opioid use and misuse is challenging because of disparate data stored across different systems, data and system interoperability issues, and legal requirements. These areas must be navigated to make data accessible, timely, and useful to researchers. Blockchain technologies have the potential to act as a facilitator in this process, offering a more efficient, secure, and privacy-preserving solution for data exchange. Among the 5 primary applications, we found that clinical trial research, supply chain management, and secondary use of data had the most examples in practice and the potential effectiveness of blockchain. More discussions and studies should focus on addressing technical questions concerning scalability and tackling practical concerns such as cost, standards, and governance around the implementation of blockchain in health care. Policy concerns related to balancing the need for data accessibility that also protects patient privacy and autonomy in revoking consent should also be examined.

Application Programming Interfaces in Health Care: Findings from a Current-State Sociotechnical Assessment.

OBJECTIVE: Interest in application programming interfaces (APIs) is increasing as key stakeholders look for technical solutions to interoperability challenges. We explored three thematic areas to assess the current state of API use for data access and exchange in health care: (1) API use cases and standards; (2) challenges and facilitators for read and write capabilities; and (3) outlook for development of write capabilities. METHODS: We employed four methods: (1) literature review; (2) expert interviews with 13 API stakeholders; (3) review of electronic health record (EHR) app galleries; and (4) a technical expert panel. We used an eight-dimension sociotechnical model to organize our findings. RESULTS: The API ecosystem is complicated and cuts across five of the eight sociotechnical model dimensions: (1) app marketplaces support a range of use cases, the majority of which target providers' needs, with far fewer supporting patient access to data; (2) current focus on read APIs with limited use of write APIs; (3) where standards are used, they are largely Fast Healthcare Interoperability Resources (FHIR); (4) FHIR-based APIs support exchange of electronic health information within the common clinical data set; and (5) validating external data and data sources for clinical decision making creates challenges to provider workflows. CONCLUSION: While the use of APIs in health care is increasing rapidly, it is still in the pilot stages. We identified five key issues with implications for the continued advancement of API use: (1) a robust normative FHIR standard; (2) expansion of the common clinical data set to other data elements; (3) enhanced support for write implementation; (4) data provenance rules; and (5) data governance rules. Thus, while APIs are being touted as a solution to interoperability challenges, they remain an emerging technology that is only one piece of a multipronged approach to data access and use.

Application Programming Interfaces (APIs) in Health Care: Findings from a Current-State Assessment.

Interest in application programming interfaces (APIs) as a means to increase health data access and exchange among patients, health care providers, and payers has become an important area for development. In an effort to better understand the various contexts in which APIs can be applied, we explored different use cases. While APIs and our collective understanding of the best ways to implement and use them continue to develop, in the coming years the use of proprietary and standards-based APIs could be key to the sustainability of applied clinical informatics research, as well as associated improvements in patient engagement, clinical decision making, efficiency, quality and safety of the healthcare delivery system.