Thursday, January 28, 2010

BW 706 Tracey's 1st blog

The guidance I reviewed is the Guidance for Clinical Investigators, Sponsors, and IRBs: Adverse Event Reporting To IRBs –Improving human Subject Protection. This is a final guidance that was released in January 2009. The guidance can be found online at http://www.fda.gov/downloads/Drugs/GuidanceComplianceRegulatoryInformation/Guidances/UCM079753.pdf . The target audience is anyone working on clinical trials of drugs, biological products or devices at investigative sites (ie, clinical investigator, and clinical research coordinator), IRBs, or sponsors (ie, clinical research scientist, pharmacovigilence department, site monitor). This guidance was written to clarify the requirements for reporting adverse events (AEs) that occur during clinical trials to the IRBs as outlined in Title 21 of the Code of Federal Regulations (CFR) part 56 (IRBs), part 312 (Investigation New Drug Application), and part 812 (Investigational Device Exemptions).
The primary purpose of the IRB is to protect the human subject participating in a clinical trial. To do this they evaluate the trial before it starts and during its conduct. To monitor subject safety they must be given the appropriate safety information such as reported AEs. However, even in the safest clinical trial many AEs occur and most do not constitute a safety signal. Prior to the guidance there was a lack of clarity regarding what types of AEs the FDA expected to be reported to IRBs. As a result, the volume of AEs reported to IRBs was overwhelming and thus, it was difficult for them to effectively evaluate significant safety issues.
In general, it is recommended that all unanticipated AEs reported during the clinical trials be reported to the IRB. The guidance defines an unanticipated AE as an event that is unexpected, serious, or would require a safety related change in the protocol or informed consent form (ICF). This is especially true if the event meets these criteria and is considered by the investigator to be related, or potentially related, to the drug, biological produce or device being studies.
In most cases a single occurrence of an event does not constitute an unanticipated event. For multicenter trials the sponsor is able to evaluate whether the event is unanticipated because they have the ability to review data from all study subjects. Therefore, it is recommended that the individual investigators conducting the study rely on the sponsor to report unanticipated AEs to the IRB. The sponsor would also be responsible for reporting a AE that was determined to be unanticipated to all participating investigators. Of course there are exceptions to every rule. Some events, such as liver damage, are considered serious events that are uncommon in the non-study population. It takes only one occurrence of an event like this to send up a red flag and be considered unanticipated. It is recommended in the guidance that these types of events be reported to the IRB even if it is the first time it occurred in the study.
In general, the guidance is very helpful although it does create a concern. While on one hand it makes sense that the sponsor, being the party that has access to all of the data, should be responsible for assessing if a AE is unanticipated. However, on the other hand, if a sponsor is inclined to hide unfavorable outcomes this reporting strategy opens the process up to bias and under reporting.

4 comments:

  1. Hey Tracey,
    Great first attempt.
    Things you did well:
    1. I really like your impact section at the end.
    2. You have worked to simplify the blog, you should continue to do that.
    3. You stuck to the outline as provided, which is good. Feel free to break the rules if you ever feel that you need to.
    4. You seem to have put in a lot of effort, and actually went first. Both of which I commend you for.
    My recommendations for the next blog:
    1. Simplify the language a bit more. You seem to have done quite a bit, but a little bit more would probably be better.
    2. Cut back on the abbreviations. Remember, the blog is for the lay audience who may not know as much as you do. e.g. IRB (I believe that almost everyone in class knows that it stands for Institutional review board, but a new reader may not. The first time you use an abbreviation, remember to provide the full form as well.
    3. More use of paragraphs: Your first section seems to do a lot of citing (which is good). It would be great if you could cut it into paragraphs and make it easier to read. Relatedly:
    4. Paragraph headings. It may be easier for you if you consider using paragraph headings since you wont need introductory sentences as much.
    5. I recommend that you not start the blog posting with "The guidance I reviewed is...". Potentially, something more like "The Guidance for Clinical Investigators, Sponsors, and IRBs: Adverse Event Reporting To IRBs –Improving human Subject Protection was released in January 2009, as a final guidance. The guidance..." The point being, while I do realize that you are blogging for the purpose of the assignment, readers to the blog need not know that.

    I realize that the suggested changes, especially keeping the topic simple, is difficult especially since it is relatively complex material that requires years of experience and/or education to understand. But, I am confident that you guys can handle the challenge. If you have any questions, please email or call me.
    Thank you again Tracey for writing the first blog.

    ReplyDelete
  2. Hi Tracey,
    Thanks for your bravery in posting the first blog. I found this very helpful.
    Did you cut and paste from a Word document? -- I'm a naif when it comes to blogging.
    Thanks again,
    Stefan

    ReplyDelete
  3. Hi Stefan,

    I too am naif when it comes to blogging! I did cut and past from a Word document. I find it is easier to construct my thoughts and I lean very heavily on spell check.

    Tracey

    ReplyDelete
  4. Dear everyone,
    Just as an FYI: You guys are all doing great with the blog postings.
    Darshan

    ReplyDelete