Understanding enterprise data warehouses to support clinical and translational research

Understanding enterprise data warehouses to support clinical and translational research: impact, sustainability, demand management, and accessibility

OBJECTIVES

Healthcare organizations, including Clinical and Translational Science Awards (CTSA) hubs funded by the National Institutes of Health, seek to enable secondary use of electronic health record (EHR) data through an enterprise data warehouse for research (EDW4R), but optimal approaches are unknown. In this qualitative study, our goal was to understand EDW4R impact, sustainability, demand management, and accessibility.

MATERIALS AND METHODS

We engaged a convenience sample of informatics leaders from CTSA hubs (n = 21) for semi-structured interviews and completed a directed content analysis of interview transcripts.

RESULTS

EDW4R have created institutional capacity for single- and multi-center studies, democratized access to EHR data for investigators from multiple disciplines, and enabled the learning health system. Bibliometrics have been challenging due to investigator non-compliance, but one hub's requirement to link all study protocols with funding records enabled quantifying an EDW4R's multi-million dollar impact. Sustainability of EDW4R has relied on multiple funding sources with a general shift away from the CTSA grant toward institutional and industry support. To address EDW4R demand, institutions have expanded staff, used different governance approaches, and provided investigator self-service tools. EDW4R accessibility can benefit from improved tools incorporating user-centered design, increased data literacy among scientists, expansion of informaticians in the workforce, and growth of team science.

DISCUSSION

As investigator demand for EDW4R has increased, approaches to tracking impact, ensuring sustainability, and improving accessibility of EDW4R resources have varied.

CONCLUSION

This study adds to understanding of how informatics leaders seek to support investigators using EDW4R across the CTSA consortium and potentially elsewhere.

The Iowa Health Data Resource (IHDR): an innovative framework for transforming the clinical health data ecosystem

IMPORTANCE

This manuscript will be of interest to most Clinical and Translational Science Awards (CTSA) as they retool for the increasing emphasis on translational science from translational research. This effort is an extension of the EDW4R work that most CTSAs have done to deploy infrastructure and tools for researchers to access clinical data.

OBJECTIVES

The Iowa Health Data Resource (IHDR) is a strategic investment made by the University of Iowa to improve access to real-world health data. The goals of IHDR are to improve the speed of translational health research, to boost interdisciplinary collaboration, and to improve literacy about health data. The first objective toward this larger goal was to address gaps in data access, data literacy, lack of computational environments for processing Personal Health Information (PHI) and the lack of processes and expertise for creating transformative datasets.

METHODS

A three-pronged approach was taken to address the objective. The approach involves integration of an intercollegiate team of non-informatics faculty and staff, a data enclave for secure patient data analyses, and novel comprehensive datasets.

RESULTS

To date, all five of the health science colleges (dentistry, medicine, nursing, pharmacy, and public health) have had at least one staff and one faculty member complete the two-month experiential learning curriculum. Over the first two years of this project, nine cohorts totaling 36 data liaisons have been trained, including 18 faculty and 18 staff. IHDR data enclave eliminated the need to duplicate computational infrastructure inside the hospital firewall which reduced infrastructure, hardware and human resource costs while leveraging the existing expertise embedded in the university research computing team. The creation of a process to develop and implement transformative datasets has resulted in the creation of seven domain specific datasets to date.

CONCLUSION

The combination of people, process, and technology facilitates collaboration and interdisciplinary research in a secure environment using curated data sets. While other organizations have implemented individual components to address EDW4R operational demands, the IHDR combines multiple resources into a novel, comprehensive ecosystem IHDR enables scientists to use analysis tools with electronic patient data to accelerate time to science.

Linking Patient Encounters across Primary and Ancillary Electronic Health Record Systems: A Comparison of Two Approaches

Background

To achieve scientific goals, researchers often require integration of data from a primary electronic health record (EHR) system and one or more ancillary EHR systems used during the same patient care encounter. Although studies have demonstrated approaches for linking patient identity records across different EHR systems, little is known about linking patient encounter records across primary and ancillary EHR systems.

Objectives

We compared a patients-first approach versus an encounters-first approach for linking patient encounter records across multiple EHR systems.

Methods

We conducted a retrospective observational study of 348,904 patients with 533,283 encounters from 2010 to 2020 across our institution's primary EHR system and an ancillary EHR system used in perioperative settings. For the patients-first approach and the encounters-first approach, we measured the number of patient and encounter links created as well as runtime.

Results

While the patients-first approach linked 43% of patients and 49% of encounters, the encounters-first approach linked 98% of patients and 100% of encounters. The encounters-first approach was 20 times faster than the patients-first approach for linking patients and 33% slower for linking encounters.

Conclusion

Findings suggest that common patient and encounter identifiers shared among EHR systems via automated interfaces may be clinically useful but not "research-ready" and thus require an encounters-first linkage approach to enable secondary use for scientific purposes. Based on our search, this study is among the first to demonstrate approaches for linking patient encounters across multiple EHR systems. Enterprise data warehouse for research efforts elsewhere may benefit from an encounters-first approach.

Automated identification of unstandardized medication data: a scalable and flexible data standardization pipeline using RxNorm on GEMINI multicenter hospital data

Objective

Patient data repositories often assemble medication data from multiple sources, necessitating standardization prior to analysis. We implemented and evaluated a medication standardization procedure for use with a wide range of pharmacy data inputs across all drug categories, which supports research queries at multiple levels of granularity.

Methods

The GEMINI-RxNorm system automates the use of multiple RxNorm tools in tandem with other datasets to identify drug concepts from pharmacy orders. GEMINI-RxNorm was used to process 2 090 155 pharmacy orders from 245 258 hospitalizations between 2010 and 2017 at 7 hospitals in Ontario, Canada. The GEMINI-RxNorm system matches drug-identifying information from pharmacy data (including free-text fields) to RxNorm concept identifiers. A user interface allows researchers to search for drug terms and returns the relevant original pharmacy data through the matched RxNorm concepts. Users can then manually validate the predicted matches and discard false positives. We designed the system to maximize recall (sensitivity) and enable excellent precision (positive predictive value) with efficient manual validation. We compared the performance of this system to manual coding (by a physician and pharmacist) of 13 medication classes.

Results

Manual coding was performed for 1 948 817 pharmacy orders and GEMINI-RxNorm successfully returned 1 941 389 (99.6%) orders. Recall was greater than 0.985 in all 13 drug classes, and the F1-score and precision remained above 0.90 in all drug classes, facilitating efficient manual review to achieve 100% precision. GEMINI-RxNorm saved time substantially compared with manual standardization, reducing the time taken to review a pharmacy order row from an estimated 30 to 5 s and reducing the number of rows needed to be reviewed by up to 99.99%.

Discussion and Conclusion

GEMINI-RxNorm presents a novel combination of RxNorm tools and other datasets to enable accurate, efficient, flexible, and scalable standardization of pharmacy data. By facilitating efficient manual validation, the GEMINI-RxNorm system can allow researchers to achieve near-perfect accuracy in medication data standardization.

The IMPACT framework and implementation for accessible in silico clinical phenotyping in the digital era

Clinical phenotyping is often a foundational requirement for obtaining datasets necessary for the development of digital health applications. Traditionally done via manual abstraction, this task is often a bottleneck in development due to time and cost requirements, therefore raising significant interest in accomplishing this task via in-silico means. Nevertheless, current in-silico phenotyping development tends to be focused on a single phenotyping task resulting in a dearth of reusable tools supporting cross-task generalizable in-silico phenotyping. In addition, in-silico phenotyping remains largely inaccessible for a substantial portion of potentially interested users. Here, we highlight the barriers to the usage of in-silico phenotyping and potential solutions in the form of a framework of several desiderata as observed during our implementation of such tasks. In addition, we introduce an example implementation of said framework as a software application, with a focus on ease of adoption, cross-task reusability, and facilitating the clinical phenotyping algorithm development process.

Enhancing an enterprise data warehouse for research with data extracted using natural language processing

Objective

This study aims to develop a generalizable architecture for enhancing an enterprise data warehouse for research (EDW4R) with results from a natural language processing (NLP) model, which allows discrete data derived from clinical notes to be made broadly available for research use without need for NLP expertise. The study also quantifies the additional value that information extracted from clinical narratives brings to EDW4R.

Materials and methods

Clinical notes written during one month at an academic health center were used to evaluate the performance of an existing NLP model and to quantify its value added to the structured data. Manual review was utilized for performance analysis. The architecture for enhancing the EDW4R is described in detail to enable reproducibility.

Results

Two weeks were needed to enhance EDW4R with data from 250 million clinical notes. NLP generated 16 and 39% increase in data availability for two variables.

Discussion

Our architecture is highly generalizable to a new NLP model. The positive predictive value obtained by an independent team showed only slightly lower NLP performance than the values reported by the NLP developers. The NLP showed significant value added to data already available in structured format.

Conclusion

Given the value added by data extracted using NLP, it is important to enhance EDW4R with these data to enable research teams without NLP expertise to benefit from value added by NLP models.

Bridging the gap: A library-based collaboration to enhance data skills for clinical researchers

Introduction

Enterprise data warehouses (EDWs) serve as foundational infrastructure in a modern learning health system, housing clinical and other system-wide data and making it available for research, strategic, and quality improvement purposes. Building on a longstanding partnership between Northwestern University's Galter Health Sciences Library and the Northwestern Medicine Enterprise Data Warehouse (NMEDW), an end-to-end clinical research data management (cRDM) program was created to enhance clinical data workforce capacity and further expand related library-based services for the campus.

Methods

The training program covers topics such as clinical database architecture, clinical coding standards, and translation of research questions into queries for proper data extraction. Here we describe this program, including partners and motivations, technical and social components, integration of FAIR principles into clinical data research workflows, and the long-term implications for this work to serve as a blueprint of best practice workflows for clinical research to support library and EDW partnerships at other institutions.

Results

This training program has enhanced the partnership between our institution's health sciences library and clinical data warehouse to provide support services for researchers, resulting in more efficient training workflows. Through instruction on best practices for preserving and sharing outputs, researchers are given the tools to improve the reproducibility and reusability of their work, which has positive effects for the researchers as well as for the university. All training resources have been made publicly available so that those who support this critical need at other institutions can build on our efforts.

Conclusions

Library-based partnerships to support training and consultation offer an important vehicle for clinical data science capacity building in learning health systems. The cRDM program launched by Galter Library and the NMEDW is an example of this type of partnership and builds on a strong foundation of past collaboration, expanding the scope of clinical data support services and training on campus.

Nonspecific deidentification of date-like text in deidentified clinical notes enables reidentification of dates

To facilitate the secondary usage of electronic health record data for research, the University of California, San Francisco (UCSF) recently implemented a clinical data warehouse including, among other data, deidentified clinical notes and reports, which are available to UCSF researchers without Institutional Review Board approval. For deidentification of these notes, most of the Health Insurance Portability and Accountability Act identifiers are redacted, but dates are transformed by shifting all dates for a patient back by the same random number of days. We describe an issue in which nonspecific (ie, excess) transformation of nondate, date-like text by this deidentification process enables reidentification of all dates, including birthdates, for certain patients. This issue undercuts the common assumption that excess deidentification is a safe tradeoff to protect patient privacy. We present this issue as a caution to other institutions that may also be considering releasing deidentified notes for research.

Challenges and recommendations for high quality research using electronic health records

Harnessing Real World Data is vital to improve health care in the 21st Century. Data from Electronic Health Records (EHRs) are a rich source of patient centred data, including information on the patient's clinical condition, laboratory results, diagnoses and treatments. They thus reflect the true state of health systems. However, access and utilisation of EHR data for research presents specific challenges. We assert that using data from EHRs effectively is dependent on synergy between researchers, clinicians and health informaticians, and only this will allow state of the art methods to be used to answer urgent and vital questions for patient care. We propose that there needs to be a paradigm shift in the way this research is conducted - appreciating that the research process is iterative rather than linear. We also make specific recommendations for organisations, based on our experience of developing and using EHR data in trusted research environments.

Relative Incidence of Emergency Department Visits After Treatment for Prostate Cancer with Radiation Therapy or Radical Prostatectomy

PURPOSE

Side effect profiles play an important role in treatment decisions for localized prostate cancer. Emergency department (ED) visits, which may be due to side effects from treatment, can be measured in real-world, structured, electronic health record (EHR) data. The goal of this study was to determine whether treatments for localized prostate cancer are associated with ED visits, as a measure of side effects, using EHR data.

METHODS AND MATERIALS

We used a self-controlled case series study (SCCS) design, including patients treated at an urban academic medical center with radiation therapy (RT) or radical prostatectomy (RP) for prostate cancer between 2011 and 2020 who had visits documented for ≥ 6 months before and after treatment and ≥1 ED visit. We estimated relative incidences (RI) of ED visits, comparing incidence in the exposed and unexposed periods, with the exposed period being between start of treatment and 1 month after completion, and the unexposed period consisting of all other documented time.

RESULTS

Among men who had at least one ED visit and after adjusting for age, there were higher rates of ED visits after RP (RI 20.4, 95% confidence interval [CI] 15.4-27.0, p<0.001), RT overall (RI 2.4, CI 1.7-3.4, p<0.001), intensity modulated radiation therapy with high dose-rate brachytherapy (HDR) (RI 3.4, CI 1.7-6.8, p<0.001) or stereotactic body radiation therapy boost (RI 7.1, CI 3.4-14.8, p < 0.001), and HDR alone (RI 16.3, CI 7.2-36.9, p<0.001), compared to unexposed time. The number needed to harm to result in an ED visit was less for RP (17, CI 13-23) than RT overall (43, CI 25-126), but varied by RT modality.

CONCLUSIONS

In summary, relative rates of ED visits vary by treatment type, suggesting differing severities of side effects. These data may aid in selecting treatments and demonstrate the feasibility of using the SCCS study design on ED visits in real-world, structured EHR data to better understand side effects of treatment.

Using informatics to advance translational science: Environmental scan of adaptive capacity and preparedness of Clinical and Translational Science Award Program hubs

As the USA and the rest of the world raced to fight the COVID-19 pandemic, years of investments from the National Center for Advancing Translational Sciences allowed for informatics services and resources at CTSA hubs to play a significant role in addressing the crisis. CTSA hubs partnered with local and regional partners to collect data on the pandemic, provide access to relevant patient data, and produce data dashboards to support decision-making. Coordinated efforts, like the National COVID Cohort Collaborative (N3C), helped to aggregate and harmonize clinical data nationwide. Even with significant informatics investments, some CTSA hubs felt unprepared in their ability to respond to the fast-moving public health crisis. Many hubs were forced to quickly evolve to meet local needs. Informatics teams expanded critical support at their institutions which included an engagement platform for clinical research, COVID-19 awareness and education activities in the community, and COVID-19 data dashboards. Continued investments in informatics resources will aid in ensuring that tools, resources, practices, and policies are aligned to meet local and national public health needs.

Understanding enterprise data warehouses to support clinical and translational research: enterprise information technology relationships, data governance, workforce, and cloud computing

OBJECTIVE

Among National Institutes of Health Clinical and Translational Science Award (CTSA) hubs, effective approaches for enterprise data warehouses for research (EDW4R) development, maintenance, and sustainability remain unclear. The goal of this qualitative study was to understand CTSA EDW4R operations within the broader contexts of academic medical centers and technology.

MATERIALS AND METHODS

We performed a directed content analysis of transcripts generated from semistructured interviews with informatics leaders from 20 CTSA hubs.

RESULTS

Respondents referred to services provided by health system, university, and medical school information technology (IT) organizations as "enterprise information technology (IT)." Seventy-five percent of respondents stated that the team providing EDW4R service at their hub was separate from enterprise IT; strong relationships between EDW4R teams and enterprise IT were critical for success. Managing challenges of EDW4R staffing was made easier by executive leadership support. Data governance appeared to be a work in progress, as most hubs reported complex and incomplete processes, especially for commercial data sharing. Although nearly all hubs (n = 16) described use of cloud computing for specific projects, only 2 hubs reported using a cloud-based EDW4R. Respondents described EDW4R cloud migration facilitators, barriers, and opportunities.

DISCUSSION

Descriptions of approaches to how EDW4R teams at CTSA hubs work with enterprise IT organizations, manage workforces, make decisions about data, and approach cloud computing provide insights for institutions seeking to leverage patient data for research.

CONCLUSION

Identification of EDW4R best practices is challenging, and this study helps identify a breadth of viable options for CTSA hubs to consider when implementing EDW4R services.

Establishing a research informatics program in a public healthcare system: a case report with model documents

While much is known about governance models for research informatics programs in academic medical centers and similarly situated cancer centers, community and public health systems have been less well-characterized. As part of implementing an enterprise research governance framework, leaders in the Los Angeles County Department of Health Services established a research informatics program, including research data warehousing. The strategy is focused on high-priority, patient-centered research that leverages the investment in health IT and an efficient, sustained contribution from 2 affiliated Clinical Translational Sciences Institutes. This case study describes the foundational governance framework and policies that were developed. We share the results of several years of planning, implementation, and operations of an academically funded research informatics service core embedded in a large, multicenter county health system. We include herein a Supplementary Appendix of governance documents that may serve as pragmatic models for similar initiatives.

Migrating a research data warehouse to a public cloud: challenges and opportunities

Objective

Clinical research data warehouses (RDWs) linked to genomic pipelines and open data archives are being created to support innovative, complex data-driven discoveries. The computing and storage needs of these research environments may quickly exceed the capacity of on-premises systems. New RDWs are migrating to cloud platforms for the scalability and flexibility needed to meet these challenges. We describe our experience in migrating a multi-institutional RDW to a public cloud.

Materials and Methods

This study is descriptive. Primary materials included internal and public presentations before and after the transition, analysis documents, and actual billing records. Findings were aggregated into topical categories.

Results

Eight categories of migration issues were identified. Unanticipated challenges included legacy system limitations; network, computing, and storage architectures that realize performance and cost benefits in the face of hyper-innovation, complex security reviews and approvals, and limited cloud consulting expertise.

Discussion

Cloud architectures enable previously unavailable capabilities, but numerous pitfalls can impede realizing the full benefits of a cloud environment. Rapid changes in cloud capabilities can quickly obsolete existing architectures and associated institutional policies. Touchpoints with on-premise networks and systems can add unforeseen complexity. Governance, resource management, and cost oversight are critical to allow rapid innovation while minimizing wasted resources and unnecessary costs.

Conclusions

Migrating our RDW to the cloud has enabled capabilities and innovations that would not have been possible with an on-premises environment. Notwithstanding the challenges of managing cloud resources, the resulting RDW capabilities have been highly positive to our institution, research community, and partners.

The OneFlorida Data Trust: a centralized, translational research data infrastructure of statewide scope

The OneFlorida Data Trust is a centralized research patient data repository created and managed by the OneFlorida Clinical Research Consortium ("OneFlorida"). It comprises structured electronic health record (EHR), administrative claims, tumor registry, death, and other data on 17.2 million individuals who received healthcare in Florida between January 2012 and the present. Ten healthcare systems in Miami, Orlando, Tampa, Jacksonville, Tallahassee, Gainesville, and rural areas of Florida contribute EHR data, covering the major metropolitan regions in Florida. Deduplication of patients is accomplished via privacy-preserving entity resolution (precision 0.97-0.99, recall 0.75), thereby linking patients' EHR, claims, and death data. Another unique feature is the establishment of mother-baby relationships via Florida vital statistics data. Research usage has been significant, including major studies launched in the National Patient-Centered Clinical Research Network ("PCORnet"), where OneFlorida is 1 of 9 clinical research networks. The Data Trust's robust, centralized, statewide data are a valuable and relatively unique research resource.

Improving Research Patient Data Repositories from a Health Data Industry Viewpoint (Preprint)

Organizational, administrative, and educational challenges in establishing and sustaining biomedical data science infrastructures lead to the inefficient use of Research Patient Data Repositories (RPDRs). The challenges, including but not limited to deployment, sustainability, cost optimization, collaboration, governance, security, rapid response, reliability, stability, scalability, and convenience, restrict each other and may not be naturally alleviated through traditional hardware upgrades or protocol enhancements. This article attempts to borrow data science thinking and practices in the business realm, which we call the data industry viewpoint, to improve RPDRs.

Research Integrated Network of Systems (RINS): a virtual data warehouse for the acceleration of translational research

OBJECTIVE

Integrated, real-time data are crucial to evaluate translational efforts to accelerate innovation into care. Too often, however, needed data are fragmented in disparate systems. The South Carolina Clinical & Translational Research Institute at the Medical University of South Carolina (MUSC) developed and implemented a universal study identifier-the Research Master Identifier (RMID)-for tracking research studies across disparate systems and a data warehouse-inspired model-the Research Integrated Network of Systems (RINS)-for integrating data from those systems.

MATERIALS AND METHODS

In 2017, MUSC began requiring the use of RMIDs in informatics systems that support human subject studies. We developed a web-based tool to create RMIDs and application programming interfaces to synchronize research records and visualize linkages to protocols across systems. Selected data from these disparate systems were extracted and merged nightly into an enterprise data mart, and performance dashboards were created to monitor key translational processes.

RESULTS

Within 4 years, 5513 RMIDs were created. Among these were 726 (13%) bridged systems needed to evaluate research study performance, and 982 (18%) linked to the electronic health records, enabling patient-level reporting.

DISCUSSION

Barriers posed by data fragmentation to assessment of program impact have largely been eliminated at MUSC through the requirement for an RMID, its distribution via RINS to disparate systems, and mapping of system-level data to a single integrated data mart.

CONCLUSION

By applying data warehousing principles to federate data at the "study" level, the RINS project reduced data fragmentation and promoted research systems integration.