IntercurrentEvent

An event after treatment starts that affects how the outcome can be interpreted, with the strategy for handling it.

Kind
Concrete class
Attributes
10, 5 required
NCI code
C188815

Official definition

An event(s) occurring after treatment initiation that affects either the interpretation or the existence of the measurements associated with the clinical question of interest. (ICH E9 Addendum on Estimands)
Intercurrent Event, CDISC USDM 4.0, NCI C188815

In practice

In a protocol document: The intercurrent events column of the estimands table.

Inheritance

IntercurrentEvent is a kind of SyntaxTemplate and inherits its attributes. Wherever the model asks for a SyntaxTemplate, a IntercurrentEvent can be used.

Attributes

10 attributes, 5 of them required by the USDM API schema and 1 holding the id of another object instead of the object itself (marked by id).

AttributeTypeCard.Definition
idrequiredstringcardinality 1The identifier of this object, unique within the file.Inherited from SyntaxTemplate
namerequiredstringcardinality 1The literal identifier (i.e., distinctive designation) of the intercurrent event.Inherited from SyntaxTemplate
labelstringcardinality 0..1The short descriptive designation for the intercurrent event.Inherited from SyntaxTemplate
descriptionstringcardinality 0..1A narrative representation of the intercurrent event.Inherited from SyntaxTemplate
textrequiredstringcardinality 1An instance of structured text that represents the intercurrent event.Inherited from SyntaxTemplate
notesCommentAnnotationcardinality 0..*A brief written record relevant to the intercurrent event.Inherited from SyntaxTemplate
dictionaryIdSyntaxTemplateDictionaryby idcardinality 0..1A USDM relationship between the IntercurrentEvent and SyntaxTemplateDictionary classes which provides the set of dictionary entries related to the intercurrent event.Inherited from SyntaxTemplate
strategyrequiredstringcardinality 1A textual description of the planned strategy to manage and/or mitigate intercurrent events.
extensionAttributesExtensionAttributecardinality 0..*Extension attributes attached to this object, for information the standard does not define. Added by the API; not part of the logical model.
instanceTyperequiredstringcardinality 1The name of the class, carried by every object in a USDM JSON file. Added by the API; not part of the logical model.

Smallest valid IntercurrentEvent

The attributes a JSON file must carry for a IntercurrentEvent, and the kind of value each takes. This is the shape, with types named in place of values. Everything else in the table above is optional.

IntercurrentEvent, required attributes only
{
  "id": "IntercurrentEvent_1",
  "name": string,
  "text": string,
  "strategy": string,
  "instanceType": "IntercurrentEvent"
}

Where IntercurrentEvent is used

These classes hold or point to a IntercurrentEvent.

Example

A IntercurrentEvent from the example study. Coded values are shortened to one line.

IntercurrentEvent_1
{
  "id": "IntercurrentEvent_1",
  "name": "TREATMENT_DISCONTINUATION",
  "label": "Treatment discontinuation",
  "text": "Study intervention stopped before Week 12 for any reason.",
  "strategy": "Treatment policy",
  "instanceType": "IntercurrentEvent"
}

Other classes in objectives, endpoints and estimands:

← All 86 classes