Timing

The time between two scheduled instances, with an optional window. Timings are either a fixed reference (the anchor, usually Day 1) or relative: a duration before or after another instance.

Kind
Concrete class
Attributes
15, 8 required
NCI code
C80484

Official definition

The chronological relationship between temporal events.
Timing, CDISC USDM 4.0, NCI C80484

In practice

In a protocol document: The visit day row and the visit window row of the schedule of activities.

Attributes

15 attributes, 8 of them required by the USDM API schema and 2 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.
namerequiredstringcardinality 1The literal identifier (i.e., distinctive designation) of the timing.
labelstringcardinality 0..1The short descriptive designation for the timing.
descriptionstringcardinality 0..1A narrative representation of the chronological relationship between temporal events.
typerequiredCodecardinality 1A characterization or classification of the chronological relationship between temporal events.USDM codelist C201264, 3 values
relativeToFromrequiredCodecardinality 1The name of the reference event used to define the temporal relationship with another event.USDM codelist C201265, 4 values
valuerequiredstringcardinality 1The temporal value of the chronological relationship between temporal events.
valueLabelrequiredstringcardinality 1The short descriptive designation for the timing value.
windowLabelstringcardinality 0..1The short descriptive designation for a time period, or other type of interval, during which a temporal event may be achieved, obtained, or observed.
windowLowerstringcardinality 0..1The earliest chronological value of an allowable period of time during which a temporal event takes place.
windowUpperstringcardinality 0..1The latest chronological value of an allowable period of time during which a temporal event takes place.
relativeToScheduledInstanceIdScheduledInstanceby idcardinality 0..1A USDM relationship between the Timing and ScheduledInstance classes which identifies the scheduled instance (e.g., scheduled activity instances or scheduled decision instances) to which the timing is relative to.
relativeFromScheduledInstanceIdrequiredScheduledInstanceby idcardinality 1A USDM relationship between the Timing and ScheduledInstance classes which identifies the scheduled instance (e.g., scheduled activity instances or scheduled decision instances) to which the timing applies.
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.

Allowed values

The coded attributes of Timing that use a codelist defined by USDM, with every value in it. A file carries the code; the term is its decode.

typecodelist C201264, not extensible

CodeTermDefinition
C201356AfterA type of time point relationship that follows a point or period of time within a timeline.
C201357BeforeA type of time point relationship that comes before a point or period of time within a timeline.
C201358Fixed ReferenceA type of time point relationship that is fixed with respect to a timeline.

relativeToFromcodelist C201265, not extensible

CodeTermDefinition
C201352End to EndA timing relationship defined as the end of one event to the end of another event.
C201353End to StartA timing relationship defined as the end of one event to the start of another event.
C201354Start to EndA timing relationship defined as the start of one event to the end of another event.
C201355Start to StartA timing relationship defined as the start of one event to the start of another event.

Smallest valid Timing

The attributes a JSON file must carry for a Timing, 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.

Timing, required attributes only
{
  "id": "Timing_1",
  "name": string,
  "type": Code,
  "relativeToFrom": Code,
  "value": string,
  "valueLabel": string,
  "relativeFromScheduledInstanceId": id of ScheduledInstance,
  "instanceType": "Timing"
}

Where Timing is used

These classes hold or point to a Timing.

Example

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

Timing_1
{
  "id": "Timing_1",
  "name": "SCREENING_TIMING",
  "label": "Day -14",
  "description": "Screening is planned 14 days before Day 1.",
  "type": { "code": "C201357", "decode": "Before", … },
  "value": "P14D",
  "valueLabel": "14 days",
  "relativeToFrom": { "code": "C201355", "decode": "Start to Start", … },
  "relativeFromScheduledInstanceId": "ScheduledActivityInstance_1",
  "relativeToScheduledInstanceId": "ScheduledActivityInstance_2",
  "windowLower": "P7D",
  "windowUpper": "P7D",
  "windowLabel": "-7..+7 days",
  "instanceType": "Timing"
}

Other classes in schedule and timing:

← All 86 classes