ArticleTrials2024
Streamlining electronic reporting of serious adverse events (SAEs) using the REDCap data collection system: the eSAE Project.
Article in Trials, 2024. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 2 papers.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
2 citing papers in PubMed.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
4 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
backgroundIt is essential that electronic data collection (EDC) systems are both compliant with regulations and the principles of Good Clinical Practice (GCP) to allow for the timely and accurate reporting of data including safety data. For clinical trials of investigational medicinal products (CTIMPs), investigators must immediately report to the sponsor any serious adverse event (SAE) that occurs in a site for which they are responsible. It is therefore expected that sponsors provide systems for timely review and reporting should a SAE be classified as a suspected unexpected serious adverse reaction (SUSAR). Challenges arise when data related to adverse events (AEs) needs to be re-entered for SAEs; this can be prone to error and may delay reporting. Additionally, recognising what has changed from an initial SAE report when an investigator responds to queries raised can cause errors.
methodA multi-disciplinary working group came together from a UK academic clinical trials unit (CTU) to establish if an electronic system could be created in the unit's open-source EDC system-REDCap, to manage SAEs in an efficient way.
resultsA module has been created in REDCap to facilitate electronic SAE reporting: enabling an AE form to automatically trigger an SAE form for any AE which is also a SAE, prepopulating relevant fields of the SAE form, reducing the risk of delay and error when entering data into the SAE form. The system has also been developed with an embedded code to allow for instant visual recognition of any data updated following reporting to allow the sponsor to immediately review and resolve SAEs in a timely manner, complying with UK regulatory reporting. This functionality 'The eSAE Project' is now an active project for all of our new trials where data collection is undertaken using the REDCap system.
conclusionThe eSAE Project coded into REDCap offers a unique way of populating SAE forms with information already entered in the initial AE forms as applicable, coupled with highlighting any updates during the lifetime of the SAE for sponsors to identify any new information that needs to be reassessed to process and report the SAE.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.