Activity

Something planned to be done or observed: a procedure, an assessment, a questionnaire, dispensing drug. Activities can be nested with childIds to form groups.

Kind
Concrete class
Attributes
15, 3 required
NCI code
C71473

Official definition

An action, undertaking, or event, which is anticipated to be performed or observed, or was performed or observed, according to the study protocol during the execution of the study.
Study Activity, CDISC USDM 4.0, NCI C71473

In practice

In a protocol document: A row in the schedule of activities.

Attributes

15 attributes, 3 of them required by the USDM API schema and 7 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 study activity.
labelstringcardinality 0..1The short descriptive designation for the study activity.
descriptionstringcardinality 0..1A narrative representation of the study activity.
notesCommentAnnotationcardinality 0..*A brief written record relevant to the activity.
definedProceduresProcedurecardinality 0..*A USDM relationship between the Activity and Procedure classes which identifies the set of defined procedures associated with the activity.
biomedicalConceptIdsBiomedicalConceptby idcardinality 0..*A USDM relationship between the Activity and BiomedicalConcept classes which identifies the set of biomedical concepts associated with the activity.
nextIdActivityby idcardinality 0..1A USDM relationship within the Activity class which identifies the activity that follows the current activity in the display order.
timelineIdScheduleTimelineby idcardinality 0..1A USDM relationship between the Activity and ScheduleTimeline classes which provides the details associated with an instance of the scheduled timeline related to the activity.
childIdsActivityby idcardinality 0..*A USDM relationship within the Activity class which identifies the set of child activities associated with an activity.
previousIdActivityby idcardinality 0..1A USDM relationship within the Activity class which identifies the activity that precedes the current activity in the display order.
bcSurrogateIdsBiomedicalConceptSurrogateby idcardinality 0..*A USDM relationship between the Activity and BiomedicalConceptSurrogate classes which identifies the set of biomedical concept surrogates associated with the activity.
bcCategoryIdsBiomedicalConceptCategoryby idcardinality 0..*A USDM relationship between the Activity and BiomedicalConceptCategory classes which identifies the set of biomedical concept categories associated with the activity.
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 Activity

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

Activity, required attributes only
{
  "id": "Activity_1",
  "name": string,
  "instanceType": "Activity"
}

Where Activity is used

These classes hold or point to a Activity.

Example

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

Activity_1
{
  "id": "Activity_1",
  "name": "INFORMED_CONSENT",
  "label": "Informed consent",
  "description": "Obtain written informed consent before any study procedure.",
  "nextId": "Activity_2",
  "instanceType": "Activity"
}

Other classes in schedule and timing:

← All 86 classes