7.1 Ethics Reporting, Approval Status and Version Control
Key Takeaways
E6(R3) continuing review intervals are appropriate to participant risk.
A submission receipt is not proof that the intended document version is approved.
Approval problems require prompt clarification and a participant-protection plan.
Ethics Reporting, Approval Status and Version Control
Under ICH E6(R3), an investigator should not implement any deviation from, or changes to, the protocol without agreement by the sponsor and prior review and documented approval from the IRB/IEC of an amendment, except to remove an immediate hazard or for permitted purely logistical/administrative changes under applicable requirements. For substantive changes, obtain the appropriate ethics review and consent actions under the applicable framework and approved implementation plan.
Continuing oversight and loss of approval
E6(R3) requires continuing review at intervals appropriate to risk. It does not prescribe the old universal annual interval. Follow the committee's approval conditions and applicable requirements, tracking dates, progress updates, safety information and amendment decisions.
If approval expires, is suspended or is withdrawn, promptly establish the status with the investigator, sponsor and ethics committee. Do not assume a grace period or continue new enrolment without valid approval. Protect existing participants through an appropriate medically supervised transition; stopping treatment abruptly can itself cause harm. Document permitted care, notifications and the conditions for resumption. A monitor cannot retroactively extend ethical approval.
Prompt Reporting Requirements to the IRB/IEC
Investigators are legally and ethically obligated to submit timely reports to the IRB/IEC regarding events that may affect participant safety:
-
New information affecting participant risk: An event constitutes a UPIRTSO if it meets three distinct criteria: (1) it is unexpected in nature, severity, or frequency; (2) it is related or possibly related to participation in the research; and (3) it suggests that the research places subjects or others at a greater risk of harm than was previously known or recognized.
-
Protocol Deviations Implemented to Eliminate Immediate Hazards: When an investigator implements a change to eliminate an immediate hazard without prior IRB approval (e.g., immediately unblinding a patient or lowering a drug dose due to unexpected toxicities), document the action and rationale and promptly communicate through the relevant investigator/sponsor/IRB process, including an amendment or authority notification as appropriate under applicable requirements.
-
Serious Adverse Events (SAEs): Reported according to the IRB's specific written standard operating procedures (SOPs), typically focusing on events that are serious, unexpected, and related.
-
Non-Compliance: Any serious or continuing non-compliance with GCP, institutional policies, or IRB determinations.
CRA Verification Responsibilities for IRB Oversight
During site qualification, initiation, and interim monitoring visits, the CRA conducts rigorous source verification of IRB records in the Investigator Site File (ISF):
Tip
CRA Best Practice on Version Synchronization: Whenever the sponsor issues a revised protocol or ICF, check the date stamped on the IRB approval letter against the date the revised document was placed into clinical use at the site. A classic audit finding occurs when a site receives IRB approval on May 1 but continues consenting new subjects with the outdated ICF version until July because the coordinator failed to print the newly approved document.
Reconstructing a submission from the site file
Suppose the approval letter lists protocol version 3 and consent version 2, while the coordinator says consent version 3 was approved in the same meeting. Review the actual submission package, attachments, decision and subsequent correspondence. Determine whether the discrepancy is an incomplete letter, a missing decision or use of an unapproved form. Do not infer approval merely because the documents share a similar date.
The responsible investigator/sponsor function should seek clarification from the committee and assess any affected consent encounters. Preserve the original documents and correspondence; do not edit the committee's letter to make its version list match the binder. If approval is confirmed through a proper correction or clarification, retain that evidence with the historical sequence. If it is not confirmed, evaluate the participant-rights and compliance consequences and required follow-up.
When multiple sites rely on one ethics body, also confirm the scope of the decision and any local conditions. Central review does not automatically establish every site's activation status. A local institutional requirement can remain outstanding even though the protocol has a favourable central opinion. Keep permission, site readiness and actual implementation dates distinguishable in tracking and reports.
This example illustrates why an approval tracker needs a link to evidence and a responsible reviewer. A green status cell without a correct version and scope can hide a real protection gap. Timely reconciliation allows the site to resolve the issue before further use, rather than discovering it only during an inspection after many participants have been affected.
Official sources
Checked October 18, 2026: ICH E6(R3), Principles and Annex 1, WMA Declaration of Helsinki, 2024, ICH E11(R1).
An approval letter lists consent version 2, while staff use version 3. What should the CRA verify?
Assume all versions are covered because the trial title matches.
Edit the committee letter to say version 3.
Wait until close-out to ask about the discrepancy.
The actual submission, decision and clarification evidence for version 3, plus any affected participant consequences.
Sections you finish are checked off in the contents.