A protocol deviation becomes a protocol violation when:

A protocol deviation becomes a protocol violation when:

• A. It is an unplanned departure from the protocol.
• B. It is manageable by site staff.
• C. It affects subject safety or data integrity.
• D. It is documented in the source notes.

Answer: (C)

The concept hinges on the impact of the unplanned change. A protocol deviation is any unplanned departure from the protocol, but it becomes a protocol violation only when that departure has the potential to affect subject safety or the integrity of the study data. If a deviation occurs but doesn’t compromise safety or data quality, it remains a deviation. Documentation or whether the issue is easily managed by site staff doesn’t by itself change it into a violation; those factors relate to handling and record-keeping, not the classification. In short, the threshold for a violation is the effect on participant safety and data integrity.

The concept hinges on the impact of the unplanned change. A protocol deviation is any unplanned departure from the protocol, but it becomes a protocol violation only when that departure has the potential to affect subject safety or the integrity of the study data. If a deviation occurs but doesn’t compromise safety or data quality, it remains a deviation. Documentation or whether the issue is easily managed by site staff doesn’t by itself change it into a violation; those factors relate to handling and record-keeping, not the classification. In short, the threshold for a violation is the effect on participant safety and data integrity.