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.

Emergency department use in the postpartum period: a retrospective cohort study.

Background: Visits to the emergency room (ED) by women in the postpartum period may reflect gaps in postpartum care and disparities in access to obstetric and primary care services. This study aimed to characterize the patients who visited the ED in the first year after delivery, their reasons for coming to the ED, and the care they received. Methods: The electronic health record was reviewed for all patients who delivered at University of Iowa Health Care between 2009 and 2023 and visited the ED within 365 days after delivery. Data drawn directly from the EHR included patient demographics and medical history, pregnancy and delivery information, and newborn characteristics. The charts were then reviewed manually for information regarding ED visits including time from delivery, chief complaint, diagnosis, and disposition. Results: 555 pregnancies had ED visits within one year of delivery, with a total 814 ED visits across the study sample. 46.7% of ED visits occurred in the first 30 days following delivery, and 35% of ED visits for obstetric complaints occurred in the first 2 weeks after delivery. Black patients visited the ED more often (mean=1.84 visits, SD=1.30) than white (mean=1.34, SD=0.92, p<0.001) or Hispanic patients (mean=1.35, SD=0.67, p = 0.004). The most common categories of chief complaint were obstetric (34.6%) and gastrointestinal (18.8%), while the most common categories of diagnosis were obstetric (31.8%) and immune/infectious (28.1%). Conclusions: Visits to the ED are common in the year following delivery. Almost half of these visits occur in the first 30 days after birth. The plurality of postpartum ED visits are due to obstetric complaints, especially in the first few weeks. Black women are more likely to use the ED during this period, potentially due to disparities in healthcare access. These findings suggest that some of these ED visits may be preventable, and that there is room for improvement in post-delivery follow-up, communication between patients and the obstetrics team, and access to outpatient obstetric care.

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.

Maturity in enterprise data warehouses for research operations: Analysis of a pilot study.

Enterprise data warehouses for research (EDW4R) is a critical component of National Institutes of Health Clinical and Translational Science Award (CTSA) hubs. EDW4R operations have unique needs that require specialized skills and collaborations across multiple domains which limit the ability to apply existing models of information technology (IT) performance. Because of this uniqueness, we developed a new EDW4R maturity model based on prior qualitative study of operational practices for supporting EDW4Rs at CTSA hubs. In a pilot study, respondents from fifteen CTSA hubs completed the novel EDW4R maturity index survey by rating 33 maturity statements across 6 categories using a 5-point Likert scale. Of the six categories, respondents rated workforce as most mature (4.17 [3.67-4.42]) and relationship with enterprise IT as the least mature (3.00 [2.80-3.80]). Our pilot of a novel maturity index shows a baseline quantitative measure of EDW4R functions across fifteen CTSA hubs. The maturity index may be useful to faculty and staff currently leading an EDW4R by creating opportunities to explore the index in local context and comparison to other institutions.

Selective Serotonin Reuptake Inhibitor Use in Pregnancy and Protective Mechanisms in Preeclampsia.

Depression and preeclampsia share risk factors and are bi-directionally associated with increased risk for each other. Despite epidemiological evidence linking selective serotonin reuptake inhibitors (SSRIs) in pregnancy to preeclampsia, serotonin (5-HT) and vasopressin (AVP) secretion mechanisms suggest that SSRIs may attenuate preeclampsia risk. However, there is a need to clarify the relationship between SSRIs and preeclampsia in humans to determine therapeutic potential. This retrospective cohort study included clinical data from 9558 SSRI-untreated and 9046 SSRI-treated pregnancies. In a subcohort of 233 pregnancies, early pregnancy (< 20 weeks) maternal plasma copeptin, an inert and stable AVP prosegment secreted 1:1 with AVP, was measured by enzyme-linked immunosorbent assay. Diagnoses and depression symptoms (Patient Health Questionnaire-9 [PHQ-9]) were identified via medical records review. Descriptive, univariate, and multivariate regression analyses were conducted (α = 0.05). SSRI use was associated with decreased preeclampsia after controlling for clinical confounders (depression severity, chronic hypertension, diabetes, body mass index, age) (OR = 0.9 [0.7-1.0], p = 0.05). Moderate-to-severe depression symptoms were associated with significantly higher copeptin secretion than mild-to-no depression symptoms (240 ± 29 vs. 142 ± 10 ng/mL, p < 0.001). SSRIs significantly attenuated first trimester plasma copeptin (78 ± 22 users vs. 240 ± 29 ng/ml non-users, p < 0.001). In preeclampsia, SSRI treatment was associated with significantly lower copeptin levels (657 ± 164 vs. 175 ± 134 ng/mL, p = 0.04). Interaction between SSRI treatment and preeclampsia was also significant (p = 0.04). SSRIs may modulate preeclampsia risk and mechanisms, although further studies are needed to investigate the relationships between 5-HT and AVP in depression and preeclampsia.

Need for Improved Collection and Harmonization of Rural Maternal Healthcare Data.

Representation in data sets is critical to improving healthcare for the largest possible number of people. Unfortunately, pregnancy is a very understudied period of time. Further, the gap in available data is wide between pregnancies in urban areas versus rural areas. There are many limitations in the current data that is available. Herein, we review these limitations and strengths of available data sources. In addition, we propose a new mechanism to enhance the granularity, depth, and speed with which data is made available regarding rural pregnancy.

Implementation of a Maternal Child Knowledgebase.

To advance the application of clinical data to address maternal health we developed and implemented a Maternal Child Knowledgebase (MCK). The MCK integrates data from every pregnancy that received care at the University of Iowa Hospitals & Clinics (UIHC) and links information from the pregnancy episode to the delivery episode and between the mother and child. This knowledgebase contains integrated information regarding diagnoses, medications, mother and child vitals, hospital admissions, depression screenings, laboratory value results, and procedure information. It also collates information from the electronic health record (EPIC), the Social Security Death Index, and the Medication Administration Record into one knowledgebase. To enhance usability, we designed a custom viewer with several pre-designed queries and reports that eliminates the need for users to be proficient in SQL coding. The recent implementation of the MCK has supported multiple projects and reduced the number of Obstetrics-related data queries to the Biomedical Informatics group.

Barriers and solutions to developing and maintaining research networks during a pandemic: An example from the iELEVATE perinatal network.

Introduction: To improve maternal health outcomes, increased diversity is needed among pregnant people in research studies and community surveillance. To expand the pool, we sought to develop a network encompassing academic and community obstetrics clinics. Typical challenges in developing a network include site identification, contracting, onboarding sites, staff engagement, participant recruitment, funding, and institutional review board approvals. While not insurmountable, these challenges became magnified as we built a research network during a global pandemic. Our objective is to describe the framework utilized to resolve pandemic-related issues. Methods: We developed a framework for site-specific adaptation of the generalized study protocol. Twice monthly video meetings were held between the lead academic sites to identify local challenges and to generate ideas for solutions. We identified site and participant recruitment challenges and then implemented solutions tailored to the local workflow. These solutions included the use of an electronic consent and videoconferences with local clinic leadership and staff. The processes for network development and maintenance changed to address issues related to the COVID-19 pandemic. However, aspects of the sample processing/storage and data collection elements were held constant between sites. Results: Adapting our consenting approach enabled maintaining study enrollment during the pandemic. The pandemic amplified issues related to contracting, onboarding, and IRB approval. Maintaining continuity in sample management and clinical data collection allowed for pooling of information between sites. Conclusions: Adaptability is key to maintaining network sites. Rapidly changing guidelines for beginning and continuing research during the pandemic required frequent intra- and inter-institutional communication to navigate.

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.

Understanding enterprise data warehouses to support clinical and translational research.

OBJECTIVE: Among National Institutes of Health Clinical and Translational Science Award (CTSA) hubs, adoption of electronic data warehouses for research (EDW4R) containing data from electronic health record systems is nearly ubiquitous. Although benefits of EDW4R include more effective, efficient support of scientists, little is known about how CTSA hubs have implemented EDW4R services. The goal of this qualitative study was to understand the ways in which CTSA hubs have operationalized EDW4R to support clinical and translational researchers. MATERIALS AND METHODS: After conducting semistructured interviews with informatics leaders from 20 CTSA hubs, we performed a directed content analysis of interview notes informed by naturalistic inquiry. RESULTS: We identified 12 themes: organization and data; oversight and governance; data access request process; data access modalities; data access for users with different skill sets; engagement, communication, and literacy; service management coordinated with enterprise information technology; service management coordinated within a CTSA hub; service management coordinated between informatics and biostatistics; funding approaches; performance metrics; and future trends and current technology challenges. DISCUSSION: This study is a step in developing an improved understanding and creating a common vocabulary about EDW4R operations across institutions. Findings indicate an opportunity for establishing best practices for EDW4R operations in academic medicine. Such guidance could reduce the costs associated with developing an EDW4R by establishing a clear roadmap and maturity path for institutions to follow. CONCLUSIONS: CTSA hubs described varying approaches to EDW4R operations that may assist other institutions in better serving investigators with electronic patient data.

Corrigendum: Research IT maturity models for academic health centers: Early development and initial evaluation.

[This corrects the article DOI: 10.1017/cts.2018.339.].

Dissemination and continuous improvement of a CTSA-based software platform, SPARCRequest©, using an open source governance model.

SPARCRequest© (Services, Pricing, & Application for Research Centers) is a web-based research management system that provides a modular and adaptable "electronic storefront" for research-related services. Developed by the South Carolina Clinical & Translational Research Institute at the Medical University of South Carolina, it was released as open source (OS) code in 2014. The adoption of SPARCRequest© accelerated in 2016, when, to ensure responsiveness to the needs of partners, its governance also became open. This governance model enables OS partners to suggest and prioritize features for new releases. As a result, the software code has become more modularized and can be easily customized to meet the diverse needs of adopting hubs. This article describes innovative aspects of the OS governance model, including a multi-institutional committee structure to set strategic vision, make operational decisions, and develop technical solutions; a virtual roadmap that ensures transparency and aligns adopters with release-based goals; and a business process model that provides a robust voting mechanism for prioritizing new features while also enabling fast-paced bug fixes. OS software evolves best in open governance environments. OS governance has made SPARCRequest© more responsive to user needs, attracted more adopters, and increased the proportion of code contributed by adopters.

Sustainability considerations for clinical and translational research informatics infrastructure.

A robust biomedical informatics infrastructure is essential for academic health centers engaged in translational research. There are no templates for what such an infrastructure encompasses or how it is funded. An informatics workgroup within the Clinical and Translational Science Awards network conducted an analysis to identify the scope, governance, and funding of this infrastructure. After we identified the essential components of an informatics infrastructure, we surveyed informatics leaders at network institutions about the governance and sustainability of the different components. Results from 42 survey respondents showed significant variations in governance and sustainability; however, some trends also emerged. Core informatics components such as electronic data capture systems, electronic health records data repositories, and related tools had mixed models of funding including, fee-for-service, extramural grants, and institutional support. Several key components such as regulatory systems (e.g., electronic Institutional Review Board [IRB] systems, grants, and contracts), security systems, data warehouses, and clinical trials management systems were overwhelmingly supported as institutional infrastructure. The findings highlighted in this report are worth noting for academic health centers and funding agencies involved in planning current and future informatics infrastructure, which provides the foundation for a robust, data-driven clinical and translational research program.

Research IT maturity models for academic health centers: Early development and initial evaluation.

This paper proposes the creation and application of maturity models to guide institutional strategic investment in research informatics and information technology (research IT) and to provide the ability to measure readiness for clinical and research infrastructure as well as sustainability of expertise. Conducting effective and efficient research in health science increasingly relies upon robust research IT systems and capabilities. Academic health centers are increasing investments in health IT systems to address operational pressures, including rapidly growing data, technological advances, and increasing security and regulatory challenges associated with data access requirements. Current approaches for planning and investment in research IT infrastructure vary across institutions and lack comparable guidance for evaluating investments, resulting in inconsistent approaches to research IT implementation across peer academic health centers as well as uncertainty in linking research IT investments to institutional goals. Maturity models address these issues through coupling the assessment of current organizational state with readiness for deployment of potential research IT investment, which can inform leadership strategy. Pilot work in maturity model development has ranged from using them as a catalyst for engaging medical school IT leaders in planning at a single institution to developing initial maturity indices that have been applied and refined across peer medical schools.

A comparative study of Eya1 and Eya4 protein function and its implication in branchio-oto-renal syndrome and DFNA10.

Allele variants of EYA1 and EYA4, two members of the vertebrate Eya gene family, underlie two types of inherited human deafness, branchio-oto-renal (BOR) syndrome and DFNA10, respectively. To clarify how mutations in these two genes and their encoded proteins impact the normal biology of hearing, we completed a number of functional studies using the yeast-two-hybrid system. We verified that bait constructs of the homologous region ( Eya1HR and Eya4HR) interact with Six1 prey constructs, although no interaction with Dach1 prey was demonstrable. To compare interaction affinities, we evaluated alpha-galactosidase activity after cotransformation of Eya1HR/Six1 and Eya4HR/Six1 and found that the latter interaction was weaker. By immunofluorescence staining, we showed Eya4HR localization to the cytoplasm. After coexpression of Six1, Eya4HR was translocated to the nucleus. Results with Eya1HR were similar. Translation of mutant constructs ( Eya4HR(R564X) and Eya1HR(R539X)) could not be demonstrated. Using dual Eya-containing constructs (with two wild-type alleles or wild-type and mutant alleles), we confirmed no translation of the mutant allele, even if the mutation was nontruncating. These results are consistent with clinical data and implicate haploinsufficiency as the cause of BOR syndrome and DFNA10.

Transcription of the Salmonella invasion gene activator, hilA, requires HilD activation in the absence of negative regulators.

Salmonella enterica serovar Typhimurium causes human gastroenteritis and a systemic typhoid-like infection in mice. Infection is initiated by entry of the bacteria into intestinal epithelial cells and is mediated by a type III secretion system that is encoded by genes in Salmonella pathogenicity island 1. The expression of invasion genes is tightly regulated by environmental conditions such as oxygen and osmolarity, as well as by many bacterial factors. The hilA gene encodes an OmpR/ToxR family transcriptional regulator that activates the expression of invasion genes in response to both environmental and genetic regulatory factors. HilD is an AraC/XylS regulator that has been postulated to act as a derepressor of hilA expression that promotes transcription by interfering with repressor binding at the hilA promoter. Our research group has identified four genes (hilE, hha, pag, and ams) that negatively affect hilA transcription. Since the postulated function of HilD at the hilA promoter is to counteract the effects of repressors, we examined this model by measuring hilA::Tn5lacZY expression in strains containing negative regulator mutations in the presence or absence of functional HilD. Single negative regulator mutations caused significant derepression of hilA expression, and two or more negative regulator mutations led to very high level expression of hilA. However, in all strains tested, the absence of hilD resulted in low-level expression of hilA, suggesting that HilD is required for activation of hilA expression, whether or not negative regulators are present. We also observed that deletion of the HilD binding sites in the chromosomal hilA promoter severely decreased hilA expression. In addition, we found that a single point mutation at leucine 289 in the C-terminal domain of the alpha subunit of RNA polymerase leads to very low levels of hilA::Tn5lacZY expression, suggesting that HilD activates transcription of hilA by contacting and recruiting RNA polymerase to the hilA promoter.

Opioids bind to the amino acids 84 to 118 of UDP-glucuronosyltransferase UGT2B7.

The UDP-glucuronosyltransferase UGT2B7 is an important human UGT isoform that catalyzes the conjugation of many endogenous and exogenous compounds, among them opioids, resulting in the formation of D-glucuronides. The binding site of the aglycone is located in the N-terminal half of the protein. Using NMR analysis, we demonstrate that the opioid binding site in UGT2B7 is within the 84 to 118 N-terminal amino acids. Three maltose binding protein-UGT2B7 fusion proteins, 2B7F3 and 2B7F4 incorporating the amino acids 24 to 118 and 24 to 96 of UGT2B7, respectively, and 2B7F5 incorporating amino acids 84 to 118 of UGT2B7 were expressed in Escherichia coli and purified by affinity chromatography. NMR analysis showed that morphine was bound to the fusion protein 2B7F3 with a K(D) value similar to the K(D) values obtained for the previously produced fusion proteins, which included amino acids 24 to 180. Morphine did not bind to 2B7F4, but it did bind to 2B7F5. Both NMR 1-D spectra and NOESY experiments indicated that the 2B7F5 protein was mediating magnetization transfer within the morphine. These results allowed us to predict and model a binding site within the amino acids 96 to 101 of UGT2B7. A mutant fusion protein 2B7F3 with the substitution D99A was produced, and the NMR spectroscopy analysis of the protein supported the model. A marked reduction of morphine binding was observed when the charged aspartate was substituted with alanine.