Keywords

Clinical trial, Electronic health record, Literature review

 

Authors

  1. Johnson, Elizabeth A. MS-CRM, BSN, RN
  2. Carrington, Jane M. PhD, RN, FAAN

Abstract

Clinical trials have become commonplace as a treatment option. As clinical trial participants are integrated into all healthcare delivery settings, organizations are tasked with sustaining specific care regimens with appropriate documentation and maintenance of participant protections within electronic health records. Our aim was to identify the common elements necessary for electronic health record integration of clinical research for optimal trial conduct and participant management. Review of literature was conducted utilizing PubMed and CINAHL to identify relevant publications that described use of the electronic health record to directly support trial conduct, with a total of 15 publications ultimately meeting inclusion criteria. Three thematic groupings emerged that categorized common aspects of clinical research integration: functional, structural, and procedural components. These components include technological requirements (platform/system), regulatory and legal compliance, and stakeholder involvement with clinical trial procedures (recruitment of participants). Without a centralized means of providing clinicians with current treatment and adverse event management information, participant injury or likelihood of withdrawal will increase. Further research is required to develop an optimal model of research-related integration within commercial electronic health records.

 

Article Content

Clinical trials have become commonplace as a treatment option. Clinical trial participants are integrated into all aspects of healthcare delivery-from hospital, urgent, and primary care-and organizations are tasked with appropriate documentation and maintenance of human subject protections within electronic health records (EHRs). Clinical trial research information will affect EHR progress notes, provider orders, nursing assessments, and care, along with ancillary discipline utilization, depending on the drug or device, study or observational research data capture.

 

Background

Clinical trials provide a unique opportunity across a spectrum of indications for access to novel therapeutics, which may or may not translate to individual benefit but will definitively advance medical science. Clinical trial protocols are designed with procedures for participant retention, which includes care management outside of research visits. The challenge facing care providers beyond the clinical trial site is managing the participant while adhering to the protocol. Few options exist for other providers to know that the patient is participating in a clinical trial and, second, to know what prescribed medications, for example, are contraindicated according to the protocol.

 

While EHRs were initially designated for use in capturing clinical patient procedures for billing purposes, the same core system functions of procedure tracking may also be used for clinical trial participant management.1 Challenges are encountered when ancillary providers collect information relevant to trial conduct due to lack of data capture standardization within the EHR.2 Different trial sponsors may require specific data elements to be included within the EHR that EHR platforms may not be able to incorporate. For example, one trial sponsor may require electrocardiograms to be uploaded within the EHR, whereas an EHR may accommodate only numerical measurements rather than the full visual output. Cowie et al1 summarized the present-day abilities of EHRs to support clinical trials, namely, feasibility assessments, performance improvement, guidance adherence, safety surveillance, pharmacovigilance, and hypothesis generation, whereas emerging areas of EHR support for clinical trials include patient recruitment and point-of-care randomization.2 Feasibility assessments allow the organization to review a census of the targeted patient population to evaluate its ability to conduct the trial, whereas performance improvement metrics, such as participant retention and cited deviations from the protocol, may support optimal trial conduct for present and future studies. Oversight entities, such as the US Food and Drug Administration, publish guidance to describe optimal trial conduct. Optimal trial conduct includes adequate informed consent of the participant, safety surveillance of participant adverse events and investigational product effects, pharmacovigilance, and evaluation of primary and secondary outcomes (hypothesis generation) that is in alignment with real-world prescription expectations.

 

The integration of clinical trials within a common clinical platform accessible to both clinical and research personnel has been piloted by two key, European-based projects: IntegrIT in Sweden and the five-country initiative Electronic Health Record for Clinical Research (EHR4CR). The ability to centralize communication among clinicians and researchers requires significant stakeholder engagement and technological resources to capture all pertinent aspects of trial conduct that may affect clinical care. With both IntegrIT and EHR4CR, interoperability was undertaken with standardization of data fields in mind such that any provider would be able to interpret information in a streamlined fashion within the EHR, supporting operational efficiency for both research and clinical spaces. Both projects are highlighted here for their optimal platform proposals and industry excitement surrounding initial feasibility and pilot efforts.

 

IntegrIT Project

The IntegrIT project was conducted in Sweden as a means of facilitating clinical research across health systems, EHRs, and providers throughout the country via the Health Information Exchange (HIE) platform.3 Through redirection of requests between separate health information systems, such as EHRs, the HIE platform acts as the "Grand Central Station" of information, a conduit of centralized communication.3 Clinical research processes, such as contacts, informed consent, and clinical trial information, would be made available to providers while facilitating a more efficient means of recruitment across participating centers. A 2-year project, usability testing of IntegrIT has been completed and the next stage is testing in a clinical research environment.3

 

Electronic Health Record for Clinical Research Project

A pan-European initiative, EHR4CR, shares the desire to increase awareness of clinical research information and usability of research-related tools within the EHR. Faced with limitations, such as language barriers, differing national regulations, and inconsistency in documentation practices, the EHR4CR team developed a scalable, platform-based approach to interoperability between EHR systems and clinical research systems.4 An unprecedented display of stakeholder engagement backed this initiative, with 34 academic and private industry partners across five European countries.4 Via this project, key commonalities between systems were extrapolated (standardization of documentation, data capture, and security requirements) to not only support integration of clinical research within the EHR but ultimately enhance trial conduct through the availability of data regardless of institution.

 

While clinical management is the routine function of the EHR, structuring EHRs to include research-related information will support optimal patient care to incorporate protocol limitations and prevent research participant withdrawal from trials. Lack of appropriate capture of information can result in protocol deviations, participant injury, and federal or research sponsor citations for noncompliance. In a survey of US-based health centers, only 8% of respondents affirmed integration of clinical and research-related data within the EHR.4,5 Our aim is to identify the common elements necessary for EHR integration of clinical research, including structural, functional, and procedural core requirements for optimal trial conduct and participant management.

 

METHODS

Review of literature was conducted from May 3, 2018, to July 25, 2018, utilizing PubMed and CINAHL, to identify relevant publications that described use of the EHR to directly support conduct of a research trial. Search restrictions included human subject research, English language, peer-reviewed publications, and randomized controlled trials (RCTs). Date range was not initially limited to encompass early EHR integration perspectives; however, relevance was thoroughly examined if the date of publication was older than 10 years. Reference lists of pivotal literature were reviewed for additional publications. Search terms included "integration" AND "EHR" AND "RCT," "EHR" AND "RCT" AND "organization and administration" OR "management" OR "disease management" OR "disease" AND "management" OR "disease management."

 

The PubMed search yielded 150 initial articles, while CINAHL yielded two articles. Discarded articles included case studies, abstracts, and articles that were solely based on clinical pathway support or clinical decision making that were non-research related.

 

Inclusion and Exclusion Criteria

The following inclusion and exclusion criterion were used to guide this review of literature. Inclusion criteria for the review of literature were as follows: direct alignment to research-related EHR applications including global clinical trials, randomized clinical trials, human subject research, all populations (pediatric and adult), peer reviews, drug and device protocols, all indications, and full-text publications. Papers were excluded if they were case studies, clinical pathway support literature that did not have direct EHR research utilization, clinical decision frameworks that did not have direct EHR research utilization, abstract only, editorial publications with no tie-in to trial-related data, and preclinical or animal research.

 

Selection of Studies

As part of inclusion criteria review, publication titles and abstracts were screened for relevance; the full text of articles was reviewed for research questions, methods, findings, and research setting. Thirty-five publications were initially identified for a thorough inclusion criteria review, with 15 publications ultimately selected (Table 1).

  
Table 1 - Click to enlarge in new windowTable 1 Summary of Included Studies Highlighting Clinical Trial Integration Within the EHR

RESULTS

Fifteen papers were reviewed and organized by thematic groupings. These groupings were then reviewed with 100% agreement by the authors. Common themes arose as to the integration of EHRs: structural components, functional necessities, and procedural requirements. Articles in the structural grouping focused on the technological foundation required to support clinical trials within the EHR, whereas articles in the functional and procedural groups highlighted the financial considerations, legal obligations, and stakeholder engagement that are necessary for optimal integration (Figure 1).

  
Figure 1 - Click to enlarge in new windowFIGURE 1. Thematic groupings referencing integration aspects for clinical trial management within EHRs.

Structural Grouping

One of the key technological needs in support of clinical trials is a means of alerting the system user to clinical trial information, whether patient eligibility or active screening status. Schreiweis et al6 reviewed five hospital sites in Germany, observing variability in use of system notifications (visually conveyed as red flags) for clinical trial participation and separate workflow for documentation of recruitment status. The system notifications (flags) allowed the end user to distinguish trial management from clinical management. Sites ranged from data input via demographic or status assessment forms to relying on nursing dialogue or Excel tables.6 None of the EHR systems supported the management of trials within standard installation parameters or provided a way to determine patient recruitment.6

 

A common limitation of current EHR systems includes the inability to reuse clinical data to screen potential clinical trial participants. Similar to the Schreiweis et al6 review of German university hospitals, Girardeau et al7 reviewed the EHR4CR platform-an attempt at sharing data and interoperability among European network users-and found lack of foundation for clinical trial information within current platforms. As part of the EHR4CR initiative, investigators first defined a base set of terminologies that would standardize data in the hope that eligibility criteria could then be normalized.7

 

The standardization of language will support not only the identification of potential clinical trial participants but also the completeness of data for clinical trial capture, specifically for industry-funded trials. Healthcare systems could maximize the use of normalized clinical terminologies and common data elements, thus building efficiencies within the EHR to perform clinical trial procedures such as adverse event reporting, prescreening, and feasibility assessment. Bruland et al8 stated that industry sponsors have a bank of forms and data sets that are similar among clinical trials, which could be a launching point for EHR platform design with clinical trials as a focal point. A platform design would require attention to standardization of data input by the user, rather than the free text capabilities currently seen with EHR technology. As Bruland et al8 report, 133 data elements were identified that were most frequently used in clinical trials, ranging from vital signs to demographic information. Expanding the volume of common data elements, standardizing terminology, and supportive documentation design within the EHR are all critical technological, structural components to optimal clinical trial integration.

 

Functional Grouping

The articles in the functional grouping highlight the need for fiscal feasibility objectives and clinical trial duties that would be best served via integration within the EHR. The European EHR4CR project targeted the fiscal feasibility via cost-benefit assessment of common clinical trial scenarios: protocol feasibility assessment, patient identification for recruitment, and clinical study execution.9 While theoretical in nature, given that the EHR4CR is not in use at the time of writing, EHR4CR tackled cost-benefit analysis of oncology clinical trial integration in the EHR, one of the costlier therapeutic areas for patient care. Beresniak et al9 estimated the cost-benefit of the EHR4CR platform for late-phase oncology trials to be 110.9 million euros, including potential fees for service and reduction of cycle time (commercial benefits). Overall, a platform such as EHR4CR has the potential to reduce time from study design to enrollment opening, identify potential patients to accelerate recruitment, and reduce resources required for data entry.9

 

Much of the literature surrounding EHR integration of clinical trials is produced in Europe, such as the work of Gulliford et al,12 who examined the process by which clinical trials could be conducted using the EHR. Based in the United Kingdom, the authors reviewed cluster trial performance using EHRs with primary care practices that were operating via the Clinical Practice Research Datalink.12 While conducting clinical trials is possible from a functional standpoint (standardized eligibility criteria, database, or connected sites), the authors noted the process was time-consuming from a legal aspect with research governance approvals.12

 

Legal implications of clinical trial integration were thoroughly discussed, as well as a point of generalized concern regarding integration of clinical trial participant information and allowing a wider distribution of data. One survey noted that privacy, legal implications, and public relations ramifications were stated as concerns by more than 80% of respondents.19 The EHR4CR project addressed this aspect of healthcare informatics integration via Doods et al,10 who stated it was possible to use a uniform platform, such as EHR4CR, while complying with local data protection regulations. Permission was obtained by ethics committees and varying data controllers associated with 11 university hospitals to support use of de-identified EHR data.10

 

Source data verification (SDV) and overall monitoring of clinical data is another aspect of the functionality of the EHR as it pertains to trial conduct. Source data verification can account for almost one-quarter of an industry trial study budget.11 Industry is presently divided in its use of 100% SDV versus risk-based monitoring, which is structured to verify data by specific triggers (such as volume or data critical to endpoint analysis). Andersen et al11 found, after surveying 3 million data fields with 100% SDV, it would take a review of 370 data points to find one unspecified error. This finding further supports the shift to remote monitoring or risk-based models, leaning on the data from EHRs to be accurate and review to be efficient. The potential cost savings to industry and at the site (time and effort required to host monitors on-site) align with other articles in the review as to the benefit of EHR-clinical trial integration.

 

Procedural Grouping

Although the focus of EHR integration is on the technology, institution staff and clinicians will be the daily users and thus must be at the forefront of integration discussion. An average of 30 separate clinicians may view the patient chart within the EHR per patient stay (3 to 5 days).15 Issues such as usability, necessary functionality, and workflow assimilation are all discussed by articles in the procedural grouping. Efficiencies for the management of clinical trial information and conduct of studies equate to maximization of participant recruitment potential. With many clinicians and specialists viewing information about a patient-and potential clinical trial participant-integration of clinical trial information may be another tool for collaboration among providers.

 

While not a new concept, automation of participant eligibility is discussed as a facet of clinical trial integration within the EHR. Manual review of potential participants is time-intensive and limits the breadth of patients who may be reviewed. Ni et al13 reviewed the eligibility criteria of 55 oncology clinical trials while comparing EHR clinical information and, using an eligibility screening (ES) algorithm, found that automating the ES reduced clinician workload by 90%. Standardization of nomenclature for the Ni et al13 ES algorithm was achieved with the support of medical dictionaries and codes for clinical terms. When tested against an oncologist chart review, the physician identified 29 potential participants, whereas the ES algorithm identified 34 participants.13 Harnessing the potential of adaptive ES algorithms within the EHR makes it possible to reach more potential participants while reducing burden on providers.

 

The LIFT Diabetes trial, as described by Effoe et al,14 demonstrates the game-changing difference between conventional recruitment methods (eg, mass mailings) versus EHR-led recruitment. With early, brisk-paced recruitment as a reliable indicator of overall clinical trial enrollment success, employing the EHR (and, in that study, referrals) as a way to recruit participants resulted in improved identification and retention of participants compared to laborious methods such as mass mailings and community health screening events.14

 

Reducing burden and effort in identifying clinical trial participants can save money. Industry-sponsored trials do not reimburse sites for time and effort in the participant identification process, highlighting the need to identify participants via EHR. As Penberthy et al20 found at Virginia Commonwealth University, research personnel may spend from 3.4 to 8.8 hours per participant on identifying, screening, and enrolling a patient in a clinical trial. The time and effort convert to approximately $129 USD per patient for an observational trial versus $336 USD for a phase I enrollment.20

 

As clinical trial participants become increasingly common and RCT protocol design includes ancillary discipline support (ophthalmology, surgery, dentistry), the need to capture participant information in the EHR will increase. Without a centralized means of providing clinicians with current therapies, adverse event information, concomitant medications, and impending procedures, participant injury or withdrawal will be a greater possibility. The American Society of Clinical Oncology stressed that, regardless of the EHR selected for use in oncology RCTs, the system must be interoperable to allow information exchange between departments and providers, preventing missing information that can lead to costly errors and participant safety lapses.2 The first step may very well be data normalization and shared vocabulary management, as implemented by the Mayo Clinic.18 Data comparability and consistency support accuracy and facilitate integration of clinical trial data within the EHR or data warehouses.18

 

Discussion centered on clinician alerts pertaining to clinical trial participants, either concerning recruitment or practice-related information. Benthin et al17 noted the variability in the use of alerts within EHRs. Of 38 institutions surveyed as part of the National Institute of Health-funded Clinical Trial Network for the Prevention and Early Treatment of Acute Lung Injury, 57% of the sites noted use of alerts, but only 59% of these sites evaluated the alerts for accuracy or validity.17 Furthermore, only 41% of sites used alerts for both clinical decision support and research; 29% used them only for research-related purposes.17 Query cycle time was reported as less than 1 hour, but still not immediate.17 Computerized decision support systems are similar to alert systems, while already integrated in most EHRs. Moja et al16 have launched an RCT assessing the use of MediDSS to improve care of oncology patients. Based on the rationale that data aggregation can support more sophisticated care plans and thus optimize patient outcomes, the use of this technology pertains to clinical trials, for example to manage adverse events and identify trends.16

 

CONCLUSIONS

While literature focusing on clinical trial integration within the EHR is limited in nature, work is in progress on solutions for interoperability and clinical trial support within the EHR. Articles in this review provided a full view of the issues at hand with integration, such as technological limitations, legal implications, and stakeholder feedback. Standardization of data capture and presence of clinical trial information within EHRs enhance trial conduct and support institution efficiencies just as with routine clinical operations. Clinical trial participants provide their time, effort, and course of treatment to advance scientific understanding of a disease or affliction. As a population, these participants deserve recognition in EHRs to ensure the same protections as nonclinical trial participants. Likewise, patients within a system should be provided the opportunity to participate in clinical trials regardless of whether their provider is research focused, through the use of identification alerts within the EHR. Establishing clinical trial information within EHRs sends a message: these participants are invaluable, assisting the progress of medicine and, with their data, the ability to improve therapeutics.

 

References

 

1. Cowie MR, Blomster JI, Curtis LH, et al. Electronic health records to facilitate clinical research. Clinical Research in Cardiology. 2017;106(1): 1-9. doi:. [Context Link]

 

2. Kanas G, Morimoto L, Mowat F, O'Malley C, Fryzek J, Nordyke R. Use of electronic medical records in oncology outcomes research. ClinicoEconomucs and Outcomes Research. 2010;2: 1-14. [Context Link]

 

3. Hagglund M, Duncan TS, Kai-Larsen K, Hedlin G, Krakau I. IntegrIT-towards utilizing the Swedish national health information exchange platform for clinical research. Studies in Health Technology and Informatics. 2017;235: 146-150. doi:. [Context Link]

 

4. De Moor G, Sundgren M, Kalra D, et al. Using electronic health records for clinical research: the case of the EHR4CR project. Journal of Biomedical. 2015;53: 162-173. doi:. [Context Link]

 

5. Turisco F, Keogh D, Stubbs C, Glaser J, Crowley WF Jr. Current status of integrating information technologies into the clinical research enterprise within US academic health centers: strategic value and opportunities for investment. Journal of Investigative Medicine. 2005;53(8): 425-433. doi:. [Context Link]

 

6. Schreiweis B, Trinczek B, Kopcke F, et al. Comparison of electronic health record system functionalities to support the patient recruitment process in clinical trials. International Journal of Medical Informatics. 2014;83(11): 860-868. doi:. [Context Link]

 

7. Girardeau Y, Doods J, Zapletal E, et al. Leveraging the EHR4CR platform to support patient inclusion in academic studies: challenges and lessons learned. BMS Medical Research Methodology. 2017;17(1): 36. doi:. [Context Link]

 

8. Bruland P, McGilchrist M, Zapletal E, et al. Common data elements for secondary use of electronic health record data for clinical trial execution and serious adverse event reporting. BMS Medical Research Methodology. 2016;16: 159. doi:. [Context Link]

 

9. Beresniak A, Schmidt A, Proeve J, et al. Cost-benefit assessment of using electronic health records data for clinical research versus current practices: contribution of the Electronic Health Records for Clinical Research (EHR4CR) European project. Contemporary Clinical Trials. 2016;46: 85-91. doi:. [Context Link]

 

10. Doods J, Bache R, McGilchrist M, et al. Piloting the EHR4CR platform across Europe. Methods of Information in Medicine. 2014;53(4): 264-268. doi:. [Context Link]

 

11. Andersen JR, Byrjalsen I, Bihlet A, et al. Impact of source data verification on data quality in clinical trials: an empirical post hoc analysis of three phase 3 randomized clinical trials. British Journal of Clinical Pharmacology. 2015;79(4): 660-668. doi:. [Context Link]

 

12. Gulliford MC, van Staa TP, McDermott L, et al. Cluster randomized trials utilizing primary care electronic health records: methodological issues in design, conduct, and analysis (eCRT study). Trials. 2014;15: 220. doi:. [Context Link]

 

13. Ni Y, Wright J, Perentesis J, et al. Increasing the efficiency of trial-patient matching: automated clinical trial eligibility pre-screening for pediatric oncology patients. BMC Medical Informatics and Decision Making. 2015;15: 28. doi:. [Context Link]

 

14. Effoe VS, Katula JA, Kirk JK, et al. The use of electronic medical records for recruitment in clinical trials: findings from the Lifestyle Intervention for Treatment of Diabetes trial. Trials. 2016;17(1): 496. doi:. [Context Link]

 

15. Vawdrey DK, Wilcox LG, Collins S, et al. Awareness of the care team in electronic health records. Applied Clinical Informatics. 2011;2(4): 395-405. doi:. [Context Link]

 

16. Moja L, Passardi A, Capobussi M, et al. Implementing an evidence-based computerized decision support system linked to electronic health records to improve care for cancer patients: the ONCO-CODES study protocol for a randomized controlled trial. Implementation Science. 2016;11(1): 153. doi:. [Context Link]

 

17. Benthin C, Pannu S, Khan A, Gong M; NHLBI Prevention and Early Treatment of Acute Lung Injury (PETAL) Network. The nature and variability of automated practice alerts derived from electronic health records in a U.S. nationwide critical care research network. Annals of the American Thoracic Society. 2016;13(10): 1784-1788. doi:. [Context Link]

 

18. Chute CG, Beck SA, Fisk TB, Mohr DN. The Enterprise Data Trust at Mayo Clinic: a semantically integrated warehouse of biomedical data. Journal of the American Medical Informatics Association: JAMIA. 2010;17(2): 131-135. doi:. [Context Link]

 

19. PricewaterhouseCoopers. Transforming healthcare through secondary use of health data. http://www.pwc.com/us/en/healthcare/publications/secondary-health-data.jhtml. Accessed June 2, 2018. [Context Link]

 

20. Penberthy LT, Dahman BA, Petkov VI, DeShazo JP. Effort required in eligibility screening for clinical trials. Journal of Oncology Practice. 2012;8(6): 365-370. doi:. [Context Link]