When a Protocol Deviation Isn’t Just a Deviation

There’s a moment in almost every clinical trial when a question surfaces that seems simple on the surface but quickly becomes more complicated the longer you sit with it.

This often begins with a message from a site, such as “Patient missed X assessment. Should this be considered a protocol deviation?” The source of this question can vary. It could be a lab, an imaging center, or a questionnaire. And in the realm of neuro-oncology or CAR-T programs, it might be a cognitive or neurologic assessment that was scheduled but not performed.

On paper, the answer seems straightforward. The protocol mandates that an assessment must occur at a specific time point, and since it didn’t happen, it’s considered a deviation. However, in real-world clinical research, nothing is ever as straightforward as it appears. And this is precisely where the role of the medical monitor transitions from being purely administrative to becoming more clinical.

The illusion of simplicity

Protocol deviations are often seen as operational issues, something the clinical team logs, categorizes, and closes out. They are labeled as minor, major, important, or non-important. However, the real question rarely revolves around the label itself. The true concern lies in whether the deviation impacts patient safety, data integrity, or the interpretation of the study.

Regulators and medical monitors must adhere to this framework, keeping it in mind whenever a deviation comes across their desk. 

A missed blood pressure measurement during a routine visit may be inconvenient, but it rarely jeopardizes the interpretability of a study. On the other hand, a missed neurologic assessment in a trial evaluating neurotoxicity presents a different conversation entirely. In such cases, context becomes crucial.

A scenario that comes up more often than people think

Let’s consider an example from a CAR-T program. A protocol mandates Neuro ICE assessments at specific intervals after infusion. These evaluations serve a crucial purpose. Neurotoxicity, particularly ICANS, is one of the key safety signals in these therapies. Monitoring neurologic status is not merely a procedural requirement; it’s essential for understanding the treatment’s safety profile.

Now, imagine a site reports that a scheduled Neuro ICE assessment was not performed. The patient was clinically stable, and no neurologic symptoms were reported. The visit took place, but the formal assessment was simply not documented.

So, what does this signify? Is it a minor deviation, a documentation issue, or something more significant? This is where experience becomes invaluable.

Why these situations are rarely black and white

When evaluating something like a missed Neuro ICE assessment, I typically consider several factors before arriving at a conclusion.

First, I examine the reasons behind the missed assessment. Was it due to a scheduling error, a misunderstanding of the protocol window, or a perception by the site that the patient was clinically stable and the evaluation unnecessary?

Second, I assess the criticality of the assessment to the study’s endpoints or safety monitoring. In CAR-T programs, neurologic monitoring is not a secondary measure; it’s directly linked to identifying ICANS and characterizing treatment risks.

Third, I evaluate the recoverability and interpretability of the missing data. If the patient had no neurologic symptoms and multiple subsequent visits documented normal status, the missed assessment may not significantly impact the interpretation of safety. However, if the missed assessment occurs during a period when neurotoxicity is most likely to occur, the absence of that data becomes more significant.

Finally, I determine whether this is an isolated incident or a recurring pattern. While a single missed assessment can occur at any site, clinical research is conducted by humans in busy hospitals with rapidly evolving patient situations. However, repeated missed neurologic assessments suggest a deeper issue, such as training gaps, operational problems, or a misunderstanding of protocol priorities. This distinction matters.

When does a deviation become “major”?

People often wonder if missed safety assessments should automatically be considered major protocol deviations. The truth is, it depends on the circumstances.

Regulatory guidance generally defines “important protocol deviations” as those that could impact participant safety or the credibility of study data. However, this definition is open to interpretation, and in practice, interpretation is unavoidable.

For instance, if a critical safety assessment is missed during a period when toxicity is most likely to occur, many medical monitors would consider it a major deviation. This is not because someone made a mistake, but because the missing data could potentially affect the study’s ability to fully characterize the risk.

On the other hand, if the deviation occurs outside a high-risk window, or if surrounding clinical information strongly suggests the patient was stable, the event may be better categorized differently. This is why deviation review should not be purely algorithmic; clinical judgment is crucial.

The part that often gets overlooked

Over the years, one thing that I’ve noticed is that teams often prioritize classifying deviations over understanding their root causes. For example, was the protocol overly complex? Did the site fully comprehend the assessment schedule? Was the required evaluation operationally challenging?

In some studies, neurologic assessments like ICE scoring are required at very specific intervals, which can be difficult to operationally implement, especially in busy inpatient settings.  

If multiple sites consistently miss the same assessment, the problem might not lie with site performance but rather with protocol design. This is where medical monitoring intersects with study strategy, as sometimes the most crucial outcome of a deviation isn’t its classification but the insights it provides into how the study is actual functioning.

The broader role of the medical monitor

These situations serve as reminders that medical monitoring goes beyond merely reviewing safety data or responding to investigator queries. 

It encompasses the crucial task of maintaining the clinical integrity of a study. This involves understanding the scientific basis of each assessment outlined in the protocol. It requires recognizing when a deviation genuinely jeopardizes the interpretability of the results, distinguishing it from the inevitable challenges encountered during the execution of trials in real patients. 

Additionally, it means providing support to sites when the protocol becomes difficult to operationalize. Effective monitoring is not adversarial; it thrives on collaboration. Sites are driven by the desire to conduct studies accurately, sponsors seek reliable data, and patients deserve trials that are thoughtfully and carefully conducted. These goals are often more aligned than people realize.

The takeaway

Protocol deviations are an inevitable part of clinical research, especially in complex studies involving real patients, real clinicians, and real-world healthcare environments. The goal isn’t to eliminate them entirely, but rather to understand them.

When deviations occur, particularly around critical safety assessments like neurologic monitoring, the question isn’t simply “Was the protocol followed?” Instead, it’s more meaningful to ask, “Does this affect patient safety or our ability to understand the therapy?”

If the answer is yes, the deviation warrants careful attention. If the answer is no, it serves as a reminder that clinical trials, like medicine itself, rarely proceed exactly as planned. This is precisely why thoughtful medical monitoring matters.

At The Medical Monitor’s Desk, these are the types of questions that arise daily. They may not have easy answers, but they require clinical judgment, experience, and context to be effectively addressed.