Tag Archives: medDRA

CTCAE: Common Terminology Criteria for Adverse Events

The National Cancer Institute issued the Common Terminology Criteria for Adverse Events (CTCAE) version 5.0 on November 27, 2017.

So what is CTCAE and what is it used for?

The terminology NCI CTCAE is a descriptive terminology that can be used for the declaration of adverse events (AEs). A grade scale (or severity) is provided for each term.

The oncology community has a standard classification and severity grading scale for adverse events in cancer therapy clinical trials and this is what it is described in the CTCAE reference.

The SOC (System Organ Class or Organ Class) is the highest level of the hierarchy of the
MedDRA dictionary. It is identified by a physiological or anatomical classification, etiological or a result (ex: SOC investigations for laboratory results). The terms of the CTCAE are grouped together according to the MedDRA primary SOCs. Within each SOC, the terms are listed and accompanied a description of the severity (grade).






An adverse event is an unexpected sign, symptom or disease, unexpected (this includes
biological results), associated chronologically with the use of a treatment, a procedure,
to be connected to this treatment or procedure. An IE is a unique term representing an event
specifically used for the medical report and the scientific analyzes. Each term of the CTCAE is a
MedDRA LLT level term (Low Level Term, lowest level of the hierarchy).
Grades refer to the severity of AEs. The CTCAE is divided into 5 grades, each with
unique medical description for each term, based on the following main lines:
Grade 1: Light; asymptomatic or mild symptoms; diagnosis on clinical examination only; born
not requiring treatment
Grade 2: Moderate; requiring minimal, local or non-invasive treatment; interfering with activities instrumentalities of everyday life
Grade 3: Severe or medically significant but without immediate life-threatening;
indication of hospitalization or prolongation of hospitalization; invalidating; interfering with activities elementary of everyday life
Grade 4: Life-threatening; requiring emergency care
Grade 5: Death related to AE and it is not appropriate for some AEs and therefore is not an option.
MedDRA code CTCAE v5.0 Term Grade 1 Grade 2 Grade 3 Grade 4 Grade 5 Definition
10007515 Cardiac arrest Life-threatening
consequences; urgent
intervention indicated<
Death A disorder characterized by cessation of the pumping function of the heart.

CTCAE is still the formal reporting for AEs and grading dependent upon clinician judgement of medical significance.

A copy is located here: CTCAE version 5.0.

Sources:

https://ctep.cancer.gov/protocolDevelopment/electronic_applications/docs/CTCAE_v5_Quick_Reference_8.5×11.pdf

Feature image: CTCAE-4 by Stefano Peruzzi (apple app)

Fair Use Notice: Images/logos/graphics on this page contains some copyrighted material whose use has not been authorized by the copyright owners. We believe that this not-for-profit, educational, and/or criticism or commentary use on the Web constitutes a fair use of the copyrighted material (as provided for in section 107 of the US Copyright Law).

Data Management Plan – Coding and Reconciliation

All Adverse Events and Previous/Concomitant Medication should be coded and/or approved prior and during the trial.

Before adverse event terms can be reported or analyzed, they must be grouped based on their similarities. For example, headache, mild headache and acute head should all be counted as the same kind of event. This is done by matching (or coding) the reported adverse events against a large codelist of adverse events which is also known as dictionary or thesaurus.

Test cases and other documentation associated with the testing of auto-coding should be produced/documented.  This documentation is not part of the plan. It is a product of the design process and should be filed separately in the TMF system.

In the DMP. you should document the variables and the dictionary to be used.

For Concomitant Medications, WHO drug reference list is used.  Also document the version used and if applicable, the final version of the who drug (for trials running over 6 months).

For Adverse event, MedDRA dictionary is the choice of coding method. Document the version used.

Serious Adverse Event (SAE) Reconciliation:

Indicate SAE Reconciling Approach to be used to compare SAE database (e.g. Argus) to the Clinical study| database (e.g. EDC):

  • Indicate tools to be used
  • Location of SAE data
  • Planned timing
  • Planned frequency of SAE Reconciliation activities

What to look for during reconciliation:

  • There are matched cases but minor differences such as onset date
  • Case found in the CDMS but not in the SAE system
  • Case found in the SAE system but not in the CDM system

Methods for Reconciliation:

For electronic-automatic reconciliation between systems, there are some challenges you need to identify first such as which type of data is to be reconciled and then which fields to compare. Best practice is to reconciled those considered serious according to regulatory definitions.

For manual reconciliation, reports such as SAS listings extracted from both systems with study information, subject or investigator and other key data can be used to perform manual review.  A manual comparison of the events can then assure that they are both complete and comparable.

Central Coding Anayansi Gamboa
Central Coding

No matter which method you used for reconciliation, each type of data (eg, AE, MedHist, Conmed) should document which glossaries and version were used.

When data from the clinical trial database is entered into a drug safety database for coding, the data between the two systems should be reconciled to verify the data in both systems are

identical. The processes and frequency of reconciliation should be specified.

Source:

DIA -A Model Data Management Plan StandardOperating Procedure: Results From

the DIA Clinical Data Management Community, Committee on Clinical Data Management Plan

-FAIR ;USE-
“Copyright Disclaimer Under Section 107 of the Copyright Act 1976, allowance is made for “fair use” for purposes such as criticism, comment, news reporting, teaching, scholarship, and research. Fair use is a use permitted by copyright statute that might otherwise be infringing. Non-profit, educational or personal use tips the balance in favor of fair use.”

Anayansi Gamboa has an extensive background in clinical data management as well as experience with different EDC systems including Oracle InForm, InForm Architect, Central Designer, CIS, Clintrial, Medidata Rave, Central Coding, Medrio, IBM eCOS, OpenClinica Open Source and Oracle Clinical.