Preferred Label : Activity Reason Code;
NCIt related terms : Activity.reasonCode;
NCIt definition : A coded value specifying the motivation, cause, or rationale of an activity.;
Alternative definition : BRIDG 3.0.3: A coded value specifying the motivation, cause, or rationale of an activity.
EXAMPLE(S): routine requirement, drug reaction, infectious disease reporting requirement,
on patient request; BRIDG 5.3: A coded value specifying the motivation, cause, or rationale of an activity.
EXAMPLE(S): routine requirement, drug reaction, infectious disease reporting requirement,
on patient request OTHER NAME(S): NOTE(S): The key difference in how this attribute
is used across the Activity subclasses is temporal and the attribute has essentially
the same meaning wherever it is used. The most likely uses of reasonCode are with
PlannedActivities, where it identifies why an activity should be done as part of the
study or experiment plan, and with PerformedActivities, where it identifies why an
activity was done. While it's possible for a DefinedActivity to have a reason, BRIDG
has no use cases for the use of this attribute in a DefinedActivity, though some may
come to harmonization in the future. Nor is it likely, based on existing use cases,
to be used much, if at all, for ScheduledActivities.;
Origin ID : C93705;
UMLS CUI : C2985905;
Semantic type(s)
- concept_is_in_subset
