The phrase is not plain English. It is a regulatory term of art, defined by the Office for Human Research Protections (OHRP) with a specificity that transforms a vague concept into a testable, three-part determination. Not every bad outcome is an unanticipated problem. Not every serious adverse event is an unanticipated problem. Not every unexpected event is an unanticipated problem. An event must satisfy all three prongs of the OHRP definition simultaneously before it qualifies -- and understanding this distinction is, in my view, the single most important analytical skill the regulatory coordinator brings to IRB safety reporting.

In Lesson 1, you built the classification framework: four categories of information the IRB requires. You learned that unanticipated problems are Category 1. But knowing the category exists is not the same as knowing how to determine whether a specific event belongs in it. That determination is what this lesson teaches.

And here is the complication I need to prepare you for up front: the OHRP framework is clear. IRBs' interpretation of that framework is not uniform. Some IRBs apply the three-part test precisely as OHRP defined it. Others layer their own requirements on top, requiring reports of events that would not meet the OHRP definition at all. The RC managing a multi-IRB portfolio must navigate this interpretive diversity -- and that navigation requires understanding both the canonical definition and its real-world variations.

The phrase is not plain English. It is a regulatory term of art, defined by the Office for Human Research Protections (OHRP) with a specificity that transforms a vague concept into a testable, three-part determination. Not every bad outcome is an unanticipated problem. Not every serious adverse event is an unanticipated problem. Not every unexpected event is an unanticipated problem. An event must satisfy all three prongs of the OHRP definition simultaneously before it qualifies -- and understanding this distinction is, in my view, the single most important analytical skill the regulatory coordinator brings to IRB safety reporting.

In Lesson 1, you built the classification framework: four categories of information the IRB requires. You learned that unanticipated problems are Category 1. But knowing the category exists is not the same as knowing how to determine whether a specific event belongs in it. That determination is what this lesson teaches.

And here is the complication I need to prepare you for up front: the OHRP framework is clear. IRBs' interpretation of that framework is not uniform. Some IRBs apply the three-part test precisely as OHRP defined it. Others layer their own requirements on top, requiring reports of events that would not meet the OHRP definition at all. The RC managing a multi-IRB portfolio must navigate this interpretive diversity -- and that navigation requires understanding both the canonical definition and its real-world variations.