An integrated web application for decision support and automation of EHR workflow: a case study of current challenges to standards-based messaging and scalability from the EMBED trial.

Computerized clinical decision support (CDS) faces challenges to interoperability and scalability. Centralized, web-based solutions offer a mechanism to share the cost of CDS development, maintenance, and implementation across practices. Data standards have emerged to facilitate interoperability and rapid integration of such third-party CDS. This case report describes the challenges to implementation and scalability of an integrated, web-based CDS intervention for EMergency department-initiated BuprenorphinE for opioid use Disorder which will soon be evaluated in a trial across 20 sites in five healthcare systems. Due to limitations of current standards, security concerns, and the need for resource-intensive local customization, barriers persist related to centralized CDS at this scale. These challenges demonstrate the need and importance for future standards to support two-way messaging (read and write) between electronic health records and web applications, thus allowing for more robust sharing across health systems and decreasing redundant, resource-intensive CDS development at individual sites.

Implementation of a Clinical Decision Support System for Children With Minor Blunt Head Trauma Who Are at Nonnegligible Risk for Traumatic Brain Injuries.

STUDY OBJECTIVE: To determine the effect of providing risk estimates of clinically important traumatic brain injuries and management recommendations on emergency department (ED) outcomes for children with isolated intermediate Pediatric Emergency Care Applied Research Network clinically important traumatic brain injury risk factors. METHODS: This was a secondary analysis of a nonrandomized clinical trial with concurrent controls, conducted at 5 pediatric and 8 general EDs between November 2011 and June 2014, enrolling patients younger than 18 years who had minor blunt head trauma. After a baseline period, intervention sites received electronic clinical decision support providing patient-level clinically important traumatic brain injury risk estimates and management recommendations. The following primary outcomes in patients with one intermediate Pediatric Emergency Care Applied Research Network risk factor were compared before and after clinical decision support: proportion of ED computed tomography (CT) scans, adjusted for age, time trend, and site; and prevalence of clinically important traumatic brain injuries. RESULTS: The risk of clinically important traumatic brain injuries was known for 3,859 children with isolated findings (1,711 at intervention sites before clinical decision support, 1,702 at intervention sites after clinical decision support, and 446 at control sites). In this group, pooled CT proportion decreased from 24.2% to 21.6% after clinical decision support (odds ratio 0.86; 95% confidence interval 0.73 to 1.01). Decreases in CT use were noted across intervention EDs, but not in controls. The pooled adjusted odds ratio for CT use after clinical decision support was 0.73 (95% confidence interval 0.60 to 0.88). Among the entire cohort, clinically important traumatic brain injury was diagnosed at the index ED visit for 37 of 37 (100%) patients before clinical decision support and 32 of 33 patients (97.0%) after clinical decision support. CONCLUSION: Providing specific risks of clinically important traumatic brain injury through electronic clinical decision support was associated with a modest and safe decrease in ED CT use for children at nonnegligible risk of clinically important traumatic brain injuries.

Use of Traumatic Brain Injury Prediction Rules With Clinical Decision Support.

OBJECTIVES: We determined whether implementing the Pediatric Emergency Care Applied Research Network (PECARN) traumatic brain injury (TBI) prediction rules and providing risks of clinically important TBIs (ciTBIs) with computerized clinical decision support (CDS) reduces computed tomography (CT) use for children with minor head trauma. METHODS: Nonrandomized trial with concurrent controls at 5 pediatric emergency departments (PEDs) and 8 general EDs (GEDs) between November 2011 and June 2014. Patients were <18 years old with minor blunt head trauma. Intervention sites received CDS with CT recommendations and risks of ciTBI, both for patients at very low risk of ciTBI (no Pediatric Emergency Care Applied Research Network rule factors) and those not at very low risk. The primary outcome was the rate of CT, analyzed by site, controlling for time trend. RESULTS: We analyzed 16 635 intervention and 2394 control patients. Adjusted for time trends, CT rates decreased significantly (P < .05) but modestly (2.3%-3.7%) at 2 of 4 intervention PEDs for children at very low risk. The other 2 PEDs had small (0.8%-1.5%) nonsignificant decreases. CT rates did not decrease consistently at the intervention GEDs, with low baseline CT rates (2.1%-4.0%) in those at very low risk. The control PED had little change in CT use in similar children (from 1.6% to 2.9%); the control GED showed a decrease in the CT rate (from 7.1% to 2.6%). For all children with minor head trauma, intervention sites had small decreases in CT rates (1.7%-6.2%). CONCLUSIONS: The implementation of TBI prediction rules and provision of risks of ciTBIs by using CDS was associated with modest, safe, but variable decreases in CT use. However, some secular trends were also noted.

Screening Consolidated Clinical Document Architecture (CCDA) Documents for Sensitive Data Using a Rule-Based Decision Support System.

BACKGROUND: The Centers for Medicare & Medicaid Services' Stage 2 final rule requires that eligible hospitals provide a visit summary electronically at transitions of care in order to qualify for "meaningful use" incentive payments. However, Massachusetts state law and Federal law prohibit the transmission of documents containing "sensitive" data unless there is a new patient consent for each transmission. OBJECTIVES: To describe the implementation and evaluation of a rule-based decision support system used to screen transition of care documents for sensitive data. METHODS: We implemented a rule-based document screening system to identify transition of care documents that might contain sensitive data. The transmission of detected documents is withheld until a new patient consent is obtained. The documents that were flagged as containing sensitive data were reviewed in two different time periods to verify that the decision support system was not missing documents or withholding more documents than necessary. RESULTS: The rule-based screening system has been in regular production use for the past 18 months. During the first evaluation period, 3% of 5,841 documents were identified as containing sensitive data (true-positive rate of 44%). After additional enhancements to the rules, the system was evaluated a second time and 4.5% of 6,935 documents were identified as containing sensitive data (true-positive rate of 98.4%). CONCLUSION: The analysis of the system demonstrates that production rules can be used to automatically screen the content of transition of care documents for sensitive data. The utilization of the rule-based decision support system enabled our hospitals to achieve meaningful use and, at the same time, remain compliant with state and federal laws.

Clinical Decision Support for a Multicenter Trial of Pediatric Head Trauma: Development, Implementation, and Lessons Learned.

INTRODUCTION: For children who present to emergency departments (EDs) due to blunt head trauma, ED clinicians must decide who requires computed tomography (CT) scanning to evaluate for traumatic brain injury (TBI). The Pediatric Emergency Care Applied Research Network (PECARN) derived and validated two age-based prediction rules to identify children at very low risk of clinically-important traumatic brain injuries (ciTBIs) who do not typically require CT scans. In this case report, we describe the strategy used to implement the PECARN TBI prediction rules via electronic health record (EHR) clinical decision support (CDS) as the intervention in a multicenter clinical trial. METHODS: Thirteen EDs participated in this trial. The 10 sites receiving the CDS intervention used the Epic(®) EHR. All sites implementing EHR-based CDS built the rules by using the vendor's CDS engine. Based on a sociotechnical analysis, we designed the CDS so that recommendations could be displayed immediately after any provider entered prediction rule data. One central site developed and tested the intervention package to be exported to other sites. The intervention package included a clinical trial alert, an electronic data collection form, the CDS rules and the format for recommendations. RESULTS: The original PECARN head trauma prediction rules were derived from physician documentation while this pragmatic trial led each site to customize their workflows and allow multiple different providers to complete the head trauma assessments. These differences in workflows led to varying completion rates across sites as well as differences in the types of providers completing the electronic data form. Site variation in internal change management processes made it challenging to maintain the same rigor across all sites. This led to downstream effects when data reports were developed. CONCLUSIONS: The process of a centralized build and export of a CDS system in one commercial EHR system successfully supported a multicenter clinical trial.

Use of a remote clinical decision support service for a multicenter trial to implement prediction rules for children with minor blunt head trauma.

OBJECTIVE: To evaluate the architecture, integration requirements, and execution characteristics of a remote clinical decision support (CDS) service used in a multicenter clinical trial. The trial tested the efficacy of implementing brain injury prediction rules for children with minor blunt head trauma. MATERIALS AND METHODS: We integrated the Epic(®) electronic health record (EHR) with the Enterprise Clinical Rules Service (ECRS), a web-based CDS service, at two emergency departments. Patterns of CDS review included either a delayed, near-real-time review, where the physician viewed CDS recommendations generated by the nursing assessment, or a real-time review, where the physician viewed recommendations generated by their own documentation. A backstopping, vendor-based CDS triggered with zero delay when no recommendation was available in the EHR from the web-service. We assessed the execution characteristics of the integrated system and the source of the generated recommendations viewed by physicians. RESULTS: The ECRS mean execution time was 0.74 ±0.72 s. Overall execution time was substantially different at the two sites, with mean total transaction times of 19.67 and 3.99 s. Of 1930 analyzed transactions from the two sites, 60% (310/521) of all physician documentation-initiated recommendations and 99% (1390/1409) of all nurse documentation-initiated recommendations originated from the remote web service. DISCUSSION: The remote CDS system was the source of recommendations in more than half of the real-time cases and virtually all the near-real-time cases. Comparisons are limited by allowable variation in user workflow and resolution of the EHR clock. CONCLUSION: With maturation and adoption of standards for CDS services, remote CDS shows promise to decrease time-to-trial for multicenter evaluations of candidate decision support interventions.

Leveraging the NLM map from SNOMED CT to ICD-10-CM to facilitate adoption of ICD-10-CM.

OBJECTIVE: Develop and test web services to retrieve and identify the most precise ICD-10-CM code(s) for a given clinical encounter. Facilitate creation of user interfaces that 1) provide an initial shortlist of candidate codes, ideally visible on a single screen; and 2) enable code refinement. MATERIALS AND METHODS: To satisfy our high-level use cases, the analysis and design process involved reviewing available maps and crosswalks, designing the rule adjudication framework, determining necessary metadata, retrieving related codes, and iteratively improving the code refinement algorithm. RESULTS: The Partners ICD-10-CM Search and Mapping Services (PI-10 Services) are SOAP web services written using Microsoft's.NET 4.0 Framework, Windows Communications Framework, and SQL Server 2012. The services cover 96% of the Partners problem list subset of SNOMED CT codes that map to ICD-10-CM codes and can return up to 76% of the 69,823 billable ICD-10-CM codes prior to creation of custom mapping rules. DISCUSSION: We consider ways to increase 1) the coverage ratio of the Partners problem list subset of SNOMED CT codes and 2) the upper bound of returnable ICD-10-CM codes by creating custom mapping rules. Future work will investigate the utility of the transitive closure of SNOMED CT codes and other methods to assist in custom rule creation and, ultimately, to provide more complete coverage of ICD-10-CM codes. CONCLUSIONS: ICD-10-CM will be easier for clinicians to manage if applications display short lists of candidate codes from which clinicians can subsequently select a code for further refinement. The PI-10 Services support ICD-10 migration by implementing this paradigm and enabling users to consistently and accurately find the best ICD-10-CM code(s) without translation from ICD-9-CM.

Taking advantage of continuity of care documents to populate a research repository.

OBJECTIVE: Clinical data warehouses have accelerated clinical research, but even with available open source tools, there is a high barrier to entry due to the complexity of normalizing and importing data. The Office of the National Coordinator for Health Information Technology's Meaningful Use Incentive Program now requires that electronic health record systems produce standardized consolidated clinical document architecture (C-CDA) documents. Here, we leverage this data source to create a low volume standards based import pipeline for the Informatics for Integrating Biology and the Bedside (i2b2) clinical research platform. We validate this approach by creating a small repository at Partners Healthcare automatically from C-CDA documents. MATERIALS AND METHODS: We designed an i2b2 extension to import C-CDAs into i2b2. It is extensible to other sites with variances in C-CDA format without requiring custom code. We also designed new ontology structures for querying the imported data. RESULTS: We implemented our methodology at Partners Healthcare, where we developed an adapter to retrieve C-CDAs from Enterprise Services. Our current implementation supports demographics, encounters, problems, and medications. We imported approximately 17 000 clinical observations on 145 patients into i2b2 in about 24 min. We were able to perform i2b2 cohort finding queries and view patient information through SMART apps on the imported data. DISCUSSION: This low volume import approach can serve small practices with local access to C-CDAs and will allow patient registries to import patient supplied C-CDAs. These components will soon be available open source on the i2b2 wiki. CONCLUSIONS: Our approach will lower barriers to entry in implementing i2b2 where informatics expertise or data access are limited.

A highly scalable, interoperable clinical decision support service.

OBJECTIVE: To create a clinical decision support (CDS) system that is shareable across healthcare delivery systems and settings over large geographic regions. MATERIALS AND METHODS: The enterprise clinical rules service (ECRS) realizes nine design principles through a series of enterprise java beans and leverages off-the-shelf rules management systems in order to provide consistent, maintainable, and scalable decision support in a variety of settings. RESULTS: The ECRS is deployed at Partners HealthCare System (PHS) and is in use for a series of trials by members of the CDS consortium, including internally developed systems at PHS, the Regenstrief Institute, and vendor-based systems deployed at locations in Oregon and New Jersey. Performance measures indicate that the ECRS provides sub-second response time when measured apart from services required to retrieve data and assemble the continuity of care document used as input. DISCUSSION: We consider related work, design decisions, comparisons with emerging national standards, and discuss uses and limitations of the ECRS. CONCLUSIONS: ECRS design, implementation, and use in CDS consortium trials indicate that it provides the flexibility and modularity needed for broad use and performs adequately. Future work will investigate additional CDS patterns, alternative methods of data passing, and further optimizations in ECRS performance.

A pilot study of distributed knowledge management and clinical decision support in the cloud.

OBJECTIVE: Implement and perform pilot testing of web-based clinical decision support services using a novel framework for creating and managing clinical knowledge in a distributed fashion using the cloud. The pilot sought to (1) develop and test connectivity to an external clinical decision support (CDS) service, (2) assess the exchange of data to and knowledge from the external CDS service, and (3) capture lessons to guide expansion to more practice sites and users. MATERIALS AND METHODS: The Clinical Decision Support Consortium created a repository of shared CDS knowledge for managing hypertension, diabetes, and coronary artery disease in a community cloud hosted by Partners HealthCare. A limited data set for primary care patients at a separate health system was securely transmitted to a CDS rules engine hosted in the cloud. Preventive care reminders triggered by the limited data set were returned for display to clinician end users for review and display. During a pilot study, we (1) monitored connectivity and system performance, (2) studied the exchange of data and decision support reminders between the two health systems, and (3) captured lessons. RESULTS: During the six month pilot study, there were 1339 patient encounters in which information was successfully exchanged. Preventive care reminders were displayed during 57% of patient visits, most often reminding physicians to monitor blood pressure for hypertensive patients (29%) and order eye exams for patients with diabetes (28%). Lessons learned were grouped into five themes: performance, governance, semantic interoperability, ongoing adjustments, and usability. DISCUSSION: Remote, asynchronous cloud-based decision support performed reasonably well, although issues concerning governance, semantic interoperability, and usability remain key challenges for successful adoption and use of cloud-based CDS that will require collaboration between biomedical informatics and computer science disciplines. CONCLUSION: Decision support in the cloud is feasible and may be a reasonable path toward achieving better support of clinical decision-making across the widest range of health care providers.

Using a service oriented architecture approach to clinical decision support: performance results from two CDS Consortium demonstrations.

The Clinical Decision Support Consortium has completed two demonstration trials involving a web service for the execution of clinical decision support (CDS) rules in one or more electronic health record (EHR) systems. The initial trial ran in a local EHR at Partners HealthCare. A second EHR site, associated with Wishard Memorial Hospital, Indianapolis, IN, was added in the second trial. Data were gathered during each 6 month period and analyzed to assess performance, reliability, and response time in the form of means and standard deviations for all technical components of the service, including assembling and preparation of input data. The mean service call time for each period was just over 2 seconds. In this paper we report on the findings and analysis to date while describing the areas for further analysis and optimization as we continue to expand our use of a Services Oriented Architecture approach for CDS across multiple institutions.

Creating shareable decision support services: an interdisciplinary challenge.

Creating shareable decision support services is a complex task requiring effort from multiple interdisciplinary role players with a wide variety of experience and expertise. The CDS Consortium research project has developed such a service, defining a multi-layer representation of knowledge and building upon an architectural service design created at Partners Health Care, and is demonstrating its use in both a local and an external institutional setting. The process was iterative, and we encountered unexpected requirements based on decisions made at various points. We report in this paper on challenges we faced while pursuing this research: knowledge representation and modeling, data interchange and standards adoption, the process of getting agreement on content, logistics of integrating into a system that already has multiple CDS interventions, legal issues around privacy and access, inter-team communication and organization.

Laying the groundwork for enterprise-wide medical language processing services: architecture and process.

A systematic and standard process for capturing information within free-text clinical documents could facilitate opportunities for improving quality and safety of patient care, enhancing decision support, and advancing data warehousing across an enterprise setting. At Partners HealthCare System, the Medical Language Processing (MLP) services project was initiated to establish a component-based architectural model and processes to facilitate putting MLP functionality into production for enterprise consumption, promote sharing of components, and encourage reuse. Key objectives included exploring the use of an open-source framework called the Unstructured Information Management Architecture (UIMA) and leveraging existing MLP-related efforts, terminology, and document standards. This paper describes early experiences in defining the infrastructure and standards for extracting, encoding, and structuring clinical observations from a variety of clinical documents to serve enterprise-wide needs.

The adequacy of ICNP version 1.0 as a representational model for electronic nursing assessment documentation.

OBJECTIVES: The purpose of this study was to evaluate the adequacy of the International Classification of Nursing Practice (1) (ICPN) Version 1.0 as a representational model for nursing assessment documentation. DESIGN AND MEASUREMENTS: To identify representational requirements of nursing assessments, the authors mapped key concepts and semantic relations extracted from standardized and local nursing admission assessment documentation forms/templates and inpatient admission assessment records to the ICNP. Next, they expanded the list of ICNP semantic relations with those obtained from the admission assessment forms/templates. The expanded ICNP semantic relations were then validated against the semantic relations identified from an additional set of admission assessment records and a set of 300 randomly selected North American Nursing Diagnosis Association defining characteristic phrases. The concept coverage of the ICNP was evaluated by mapping the concepts extracted from these sources to the ICNP concepts. The UMLS Methathesaurus was then used to map concepts without exact matches to other American Nursing Association (ANA) recognized terminologies. RESULTS: The authors found that along with the 30 existing ICNP semantic relations, an additional 17 are required for the ICNP to function as a representational model for nursing assessment documentation. Eight hundred and five unique assessment concepts were extracted from all sources. Forty-three percent of these unique assessment concepts had exact matches in the ICNP. An additional 20% had matches in the ICNP classified as narrower, broader, or "other." Of the concepts without exact matches in the ICNP, 81% had exact matches found in other ANA recognized terminologies. CONCLUSIONS: The broad concept coverage and the logic-based structure of the ICNP make it a flexible and robust standard. The ICNP provides a framework from which to capture and reuse atomic level data to facilitate evidence-based practice.

Enhancing clinical problem lists through data mining and natural language processing.

The availability of timely, accurate, comprehensive, and coded clinical problem lists is essential for supporting a range of healthcare activities. Evidence and experience suggest, however, that problem lists are frequently out-of-date, sometimes omit clinically important problems, and contain uncoded entries. Here, we describe a study being performed at Partners HealthCare System to explore automated techniques for enhancing existing problem lists.

Early experiences in evolving an enterprise-wide information model for laboratory and clinical observations.

As Electronic Healthcare Records become more prevalent, there is an increasing need to ensure unambiguous data capture, interpretation, and exchange within and across heterogeneous applications. To address this need, a common, uniform, and comprehensive approach for representing clinical information is essential. At Partners HealthCare System, we are investigating the development and implementation of enterprise-wide information models to specify the representation of clinical information to support semantic interoperability. This paper summarizes our early experiences in: (1) defining a process for information model development, (2) reviewing and comparing existing healthcare information models, (3) identifying requirements for representation of laboratory and clinical observations, and (4) exploring linkages to existing terminology and data standards. These initial findings provide insight to the various challenges ahead and guidance on next steps for adoption of information models at our organization.

Representing nursing assessment documentation with ICNP.

The purpose of this study was to identify key concepts and semantic relations necessary to represent standardized and local patient assessment items in an electronic documentation system and to evaluate the degree to which coverage of both are represented by ICNP. A total of 805 unique assessment concepts were identified. Forty-three percent had exact matches in ICNP, and an additional 20% had matches in the ICNP classified as narrower, broader or other.

Challenges in creating an enterprise clinical rules service.

At Partners HealthCare, we are engaged in developing and implementing a strategy for our Clinical Decision Support systems and services that will enable CDS to be made available across the enterprise, allow development of consistent standards of care regardless of where a patient presents, and permit migration of current CDS functions to a supportable and scalable model. We report here on progress toward these goals, describe steps taken and proposed, and consider remaining challenges.