Adverse Event Clinical Research, published by HL7 International / Biomedical Research and Regulation. This guide is not an authorized publication; it is the continuous build for version 1.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-ae-research-ig/ and changes regularly. See the Directory of published versions

Background and Workflow

Background

Adverse Event (AE) data capture and standardization is a challenge in real world data systems. There are variations in the definitions, workflows, and data requirements across the use cases for patient monitoring, clinical intervention, regulatory safety reporting requirements and clinical trials monitoring.

The Vulcan Adverse Event project was initiated in October 2021 to model the data elements to support the workflow for collecting and reporting serious and non-serious AEs in clinical research to meet the need of regulatory requirements. The goal of this project is to leverage Electronic Health Records (EHR) and other types of real-world data (RWD), such as Personal Health Records (PHR), as electronic source to collect adverse events that occur during clinical trials. In this project, the team leveraged the HL7 FHIR standard identifying gaps between data elements in EHRs, clinical research artifacts. and other existing standards such as:

• FDA E2B(R3) Electronic Transmission of Individual Case Safety Reports Implementation Guide
• CDISC FHIR Mapping to AE
• ICH Harmonised Tripartite Guideline Clinical Safety Data Management: Definitions and Standards for Expedited Reporting E2A
• Clinical Data Acquisition Standards Harmonization Implementation Guide for Human Clinical Trials Version 2.2 (Final)
• FDA Safety Reporting Requirements for investigational new drug (IND) and bioavailability (BA) and bioequivalence (BE) studies under 21 CFR 312.32, 312.64(b), and 320.31(d)(3).
• MedWatch the FDA safety information and adverse event reporting program

Workflow

This IG will allow clinical trial AE representation in systems, including EHRs and PHRs, transmitted via FHIR to other systems; removing the need to transcribe AE data into secondary clinical trial management systems and improving efficiency for health authority reporting. The following workflows are examples to demonstrate the potential use of this AE profile in the clinical research spectrum via FHIR.

Pre-Market

The following image shows a notional workflow for collecting and reporting adverse events and serious adverse events (SAE) for pre-market clinical trials. The dotted line represents a future vision of data flow using FHIR which will most likely be covered by a separate MedWatch IG that builds upon this IG.

Example scenarios: Pre-market clinical trial reporting of serious adverse events (SAE) using FHIR and utilized as part of clinical decision support actions within a clinical research trial setting.

• Adverse event is captured in EHR by Clinical Investigator and sent to Clinical Trial Management System, then sent to Sponsor or FDA.
• Patient records adverse event in a patient facing FHIR app that contains the MedWatch 3500B questionnaire. The data is sent from the patient FHIR app to the Clinical Investigator or Sponsor for inclusion in their reporting to the FDA.

Post-Market

The following image shows a notional workflow for collecting and reporting adverse events, post-market. The dotted line represents a future vision of data flow using FHIR which will most likely be covered by a separate MedWatch IG that builds upon this IG.

Example scenarios: Postmarketing adverse event reporting using FHIR for safety surveillance.

• Patient records adverse event that is sent to FDA
• Provider records adverse event in EHR that is sent to FDA
• Manufacturer (via call center) records adverse event and sends to FDA