15.2 Deviation Classification and Resolution

Deviation Classification and Resolution

A departure from protocol instructions that does not significantly affect the subject's rights, safety, or well-being, nor compromise the completeness, evaluability, or scientific integrity of primary study endpoints.

• Common Examples: A low-impact timing deviation after evaluating the particular protocol requirement; an isolated low-impact omission, after evaluation against the protocol; a diary omission must remain honestly recorded.
• Management: Documented on the site's Protocol Deviation Tracking Log; evaluated for recurring patterns during routine monitoring.

Major Protocol Deviation (Protocol Violation)

A significant departure from the protocol that compromises subject safety, infringes upon subject rights, or compromises the scientific integrity and evaluability of critical trial endpoints.

• Common Examples: Enrolling a subject who violated core inclusion/exclusion criteria (e.g., exclusionary baseline QT prolongation or abnormal hepatic enzymes); administering the wrong investigational product dosage or expired drug; performing protocol assessments using an outdated or unapproved informed consent version; failing to obtain re-consent following an IRB-approved amendment containing vital safety updates; missing mandatory safety monitoring (e.g., cardiac telemetry in a high-risk trial).
• Management: Immediate notification to the PI and sponsor medical monitor; documented on the tracking log; formal root cause analysis; execution of an enforceable CAPA plan; reporting to the IRB/IEC in accordance with institutional reporting policies.

Important deviations and serious noncompliance

Terms such as minor, major, violation and serious breach are not a single universal hierarchy across all sponsors and jurisdictions. Apply the trial's classification method and evaluate actual or potential impact on rights, safety and result reliability. A one-day delay could be important for a critical timed endpoint and low impact for another assessment. Repeated low-impact deviations can reveal a significant system failure.

E6(R3) calls for appropriate action, root-cause evaluation and remediation when noncompliance significantly affects or could significantly affect participants or reliability. Notify relevant parties under applicable requirements. Specific national serious-breach reporting deadlines are outside ACRP's examination reference scope; do not import a universal seven-day rule.

The CRA's Deviation Lifecycle: Identification, Logging & Escalation

During every on-site and remote monitoring encounter, the CRA executes a systematic review to identify undocumented deviations:

1. Cross-System Triangulation: Comparing electronic health records (EHR), EDC data entries, pharmacy temperature logs, central laboratory requisition slips, and appointment books to detect unrecorded visit delays, missed procedures, or unapproved concomitant medications.

2. Logging Standards: Document deviations through the applicable process with specific data attributes: Subject ID, Protocol Version, Specific Protocol Section Violated, Date of Occurrence, Date of Site Detection, Date of CRA Verification, Deviation Classification (Minor vs Major), Description of Event, Root Cause Category, and CAPA Tracking Number.

3. Escalation Pathways: Major deviations must be escalated to the sponsor's Clinical Project Manager (CPM) and Medical Monitor within timelines stipulated in the trial's Monitoring Plan under the plan, with urgent risk communicated promptly.

Documenting a deviation from discovery to resolution

Record the required assessment, actual activity and timing, affected participants, evidence, impact assessment and responsible follow-up. Distinguish occurrence, detection, site awareness and monitor discovery dates. Each answers a different question. If an eligibility result is missing, establish whether the test was performed, whether the result was available before enrolment, and whether a qualified investigator reviewed it. Do not replace an unknown fact with a reassuring guess.

The monitor should communicate urgent risks promptly rather than waiting for a routine report. Work with the investigator and sponsor to evaluate participant care, reportability and data consequences. The CRA should not decide a participant's treatment independently or erase inconvenient data. A retrospective note can document what is known but cannot make an unperformed assessment occur in the past.

Track the action to objective evidence of completion and evaluate recurrence. Refer a systemic issue for root-cause analysis and CAPA; retain the original finding, the site's response and the sponsor's review. Updating a tracking status to closed is the end of the record only when the agreed action and effectiveness requirements are supported.

A revised document must reach controlled practice

A protocol amendment changes the authorised plan for a clinical trial. It can affect objectives, procedures, eligibility, product use, safety monitoring, data collection or participant burden. For a CRA, successful change control means more than collecting an approval letter: the right people must use the right version at the right time, with appropriate consent and operational support.

Identify the amendment, rationale and affected activities. Determine required sponsor agreement, IRB/IEC review and authority action under applicable requirements. ACRP's exam emphasises the international process rather than a country-specific portal or waiting period. Do not assume that calling a change administrative makes it low risk; assess its content and apply the actual framework.

Official sources

Checked October 18, 2026: ICH E6(R3), Principles and Annex 1, ACRP CCRA Exam Content Outline.