×

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

 

Adverse Event Clinical Research Implementation Guide (PSS-2171)

Basics

Adverse Event Clinical Research Implementation Guide (PSS-2171)

1999
Ballot - STU

FHIR

FHIR Implementation Guide

Create New Standard

STU
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.



September 2023 - STU


https://github.com/HL7/fhir-ae-research-ig/tree/R4backport



Academic/Research,Association/Goverment Agency,Health Care IT,Patients,Pharmaceutical,Regulatory Agency,Vendor/Manufacturer

Flatiron; PatientLink/MyLinks


Vulcan Adverse Events; Vulcan AE



N/A

No


Organization & Realm

Universal

People

Michelle Casagni

Bret Heale

Bret Heale



Vulcan
Status & Dates

Active

Active Project (Resources assigned to pjt)

04/24/2023

09/01/2024

2024 Sep WGM/Ballot

09/01/2023

2023 Sept WGM/Ballot

Approvals

04/24/2023


Not Needed


Not Needed


Not Needed


FHIR Management Group -- Agreed -- (PSS-2174)
System Info

207586

PSS-2171

09/29/2026

Jira Project Service