×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

 

Adverse Event Clinical Research Implementation Guide (Jira PSS -2171)

Basics

Adverse Event Clinical Research Implementation Guide (Jira PSS -2171)

1805
Ballot - STU to Normative


FHIR Implementation Guide

Implementation Guide

Details

Adverse events (AE) are tracked and evaluated as part of the clinical research process in a research study, as the occurrence of an adverse event may surface a potential confounder or a potential side-effect of the study treatment. In the research setting, an Adverse Event is any untoward medical occurrence in a patient or clinical investigation subject administered a pharmaceutical product and which does not necessarily have a causal relationship with this treatment. An adverse event (AE) can therefore be any unintended sign (including an abnormal laboratory finding), symptom, or disease temporally associated with the use of a medicinal (investigational) product, whether or not related to the medicinal (investigational) product. These events are characterized by the need to capture cause and effect (although they might not be known at the time of the event), severity, and outcome.

The IG (one based on R4 and one on R5) will 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. This will require further profiling and extending the AdverseEvent resource to ensure appropriate representation. Therefore, allowing AE representation in systems, including EMRs 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.


There are two major domains where the AdverseEvent resource is expected to be used. One is in clinical care reported adverse events and the other is in reporting adverse events in clinical research trial management. The Clinical Research use does not correspond to 80% of core as seen by Clinical Care but is within the 80% for Clinical Research. Discussion between the two viewpoints over several years leads each time to a conclusion that there should be two distinct resources. However, since most of the attributes would have the same names, just variants of the definitions, defining 2 domain specific implementation guides for the AdverseEvent Resource seems more appropriate. Since current AE implementations are based on FHIR R4.0.1, there will be an IG based on FHIR R5.0.0 and an IG backported to R4.0.1 to support existing implementations.



https://github.com/HL7/fhir-ae-research-ig/tree/R4backport PSS: https://jira.hl7.org/browse/PSS-2171?src=confmacro





Other (specify in Misc. Notes below),N/A

Flatiron; PatientLink/MyLinks


Vulcan Adverse Events; Vulcan AE


N/A

N/A

No

2024 April: TSC approved STU Publication Request for HL7 FHIR R5 Implementation Guide: Adverse Event Clinical Research, Edition 1 for 2 years Stakeholders: Academic/Research, Association/Goverment Agency, Healthcare IT Vendors, Patients, Pharmaceutical/Biotech, Regulatory Agency, Vendor/Manufacturer
Organization & Realm

Universal

People

Michelle Casagni



Biomedical Research and Regulation Work Group

Devices Work Group; Patient Care Work Group

Status & Dates

Active

STU - Test Period/Accepting Comments

03/07/2023

05/01/2029

2029 May WGM/Ballot

05/01/2028

2028 May WGM/Ballot

2024 April: TSC approved STU Publication Request for HL7 FHIR R4 Implementation Guide: Adverse Event Clinical Research R4 Backport, Edition 1 for 2 years 2023 Sept Ballot Cycle Info: STU Ballot Results: Did not meet basic vote requirements. 15 Negatives to reconcile Document Name: HL7 FHIR Implementation Guide: Adverse Event Clinical Research R4 Backport, Release 1 2023 Sept Ballot Cycle Info: STU Ballot Results: Did not meet basic vote requirements. 18 Negatives to reconcile Document Name: HL7 FHIR Implementation Guide: Adverse Event Clinical Research, Release 1
Approvals

04/24/2023


Not Needed


All Received




System Info






09/17/2026

Anne Wizauer