v3-ActMood
type: CodeSystem
node role: treeRoot
id:
  v: v3-ActMood
language:
  v: en
text:
  status:
    v: generated
  div: Generated Narrative: CodeSystem v3-ActMood Language: en Properties This code system defines the following properties for its concepts Name Code URI Type Description Specializes Specializes Coding The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric. Generalizes Generalizes Coding Inverse of Specializes. Only included as a derived relationship. internalId internalId http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id code The internal identifier for the concept in the HL7 Access database repository. status status http://hl7.org/fhir/concept-properties#status code A property that indicates the status of the concept. One of active, experimental, deprecated, or retired. deprecationDate deprecationDate http://hl7.org/fhir/concept-properties#deprecationDate dateTime The date at which a concept was deprecated. Concepts that are deprecated but not inactive can still be used, but their use is discouraged. Name:Class Name:Class http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Class code The formal name for the class clone under this code Not Selectable notSelectable http://hl7.org/fhir/concept-properties#notSelectable boolean Indicates that the code is abstract - only intended to be used as a selector for other concepts synonymCode synonymCode http://hl7.org/fhir/concept-properties#synonym code An additional concept code that was also attributed to a concept HL7 Concept Usage Notes HL7usageNotes http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes string HL7 Concept Usage Notes Concepts This case-sensitive code system http://terminology.hl7.org/CodeSystem/v3-ActMood defines the following codes in a Is-A hierarchy: Lvl Code Display Definition Deprecated internalId status deprecationDate Name:Class Not Selectable synonymCode HL7 Concept U…
url:
  v: http://terminology.hl7.org/CodeSystem/v3-ActMood
identifier:
  system:
    v: urn:ietf:rfc:3986
  value:
    v: urn:oid:2.16.840.1.113883.5.1001
version:
  v: 3.0.0
name:
  v: ActMood
title:
  v: ActMood
status:
  v: active
experimental:
  v: false
date:
  v: 2023-05-30
publisher:
  v: Health Level Seven International
contact:
  telecom:
    system:
      v: url
    value:
      v: http://hl7.org
  telecom:
    system:
      v: email
description:
  v: OpenIssue: In Ballot 2009May, a strong Negative vote was lodged against several of the concept definitions in the vocabulary used for Act.moodCode. The vote was found "Persuasive With Mod", with the understanding that M and M would undertake a detailed review of these concept definitions for a future release of the RIM.
copyright:
  v: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license
case sensitive:
  v: true
hierarchy meaning:
  v: is-a
content:
  v: complete
property:
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry
    value:
      v: antisymmetric
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity
    value:
      v: transitive
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity
    value:
      v: irreflexive
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable
    value:
      v: true
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind
    value:
      v: Specializes
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName
    value:
      v: Generalizes
  code:
    v: Specializes
  description:
    v: The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.
  type:
    v: Coding
property:
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry
    value:
      v: antisymmetric
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity
    value:
      v: transitive
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity
    value:
      v: irreflexive
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable
    value:
      v: true
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind
    value:
      v: Generalizes
  extension:
    url:
      v: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName
    value:
      v: Specializes
  code:
    v: Generalizes
  description:
    v: Inverse of Specializes. Only included as a derived relationship.
  type:
    v: Coding
property:
  code:
    v: internalId
  uri:
    v: http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id
  description:
    v: The internal identifier for the concept in the HL7 Access database repository.
  type:
    v: code
property:
  code:
    v: status
  uri:
    v: http://hl7.org/fhir/concept-properties#status
  description:
    v: A property that indicates the status of the concept. One of active, experimental, deprecated, or retired.
  type:
    v: code
property:
  code:
    v: deprecationDate
  uri:
    v: http://hl7.org/fhir/concept-properties#deprecationDate
  description:
    v: The date at which a concept was deprecated. Concepts that are deprecated but not inactive can still be used, but their use is discouraged.
  type:
    v: dateTime
property:
  code:
    v: Name:Class
  uri:
    v: http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Class
  description:
    v: The formal name for the class clone under this code
  type:
    v: code
property:
  code:
    v: notSelectable
  uri:
    v: http://hl7.org/fhir/concept-properties#notSelectable
  description:
    v: Indicates that the code is abstract - only intended to be used as a selector for other concepts
  type:
    v: boolean
property:
  code:
    v: synonymCode
  uri:
    v: http://hl7.org/fhir/concept-properties#synonym
  description:
    v: An additional concept code that was also attributed to a concept
  type:
    v: code
property:
  code:
    v: HL7usageNotes
  uri:
    v: http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes
  description:
    v: HL7 Concept Usage Notes
  type:
    v: string
concept:
  code:
    v: _ActMoodCompletionTrack
  display:
    v: ActMoodCompletionTrack
  definition:
    v: These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.
  property:
    code:
      v: notSelectable
    value:
      v: true
  property:
    code:
      v: status

v: active

code:
  v: internalId
value:
  v: 20935

code:
  v: Name:Class
value:
  v: Process

code:
  v: _ActMoodPotential
display:
  v: potential
definition:
  v: **Definition:** A possible act.
property:
  code:
    v: notSelectable
  value:
    v: true
property:
  code:
    v: status
  value:
    v: active
property:
  code:
    v: internalId
  value:
    v: 23087
property:
  code:
    v: Name:Class
  value:
    v: Potential
concept:
  code:
    v: DEF
  display:
    v: definition
  definition:
    v: **Definition:** A definition of a kind of act that can occur . **OpenIssue:** The semantic constructs embodied in DEF and CRT moods seem indistinguishable, and their uses can readily be determined by the context in which these are used. Therefore, this OpenIssue has been created to declare that it is likely that ActMood.DEF will be "retired" in the future in favor of the more general ActMood.CRT.
  property:
    code:
      v: status
    value:
      v: active
  property:
    code:
      v: internalId
    value:
      v: 10198
  property:
    code:
      v: Name:Class
    value:
      v: Definition
concept:
  code:
    v: PERM
  display:
    v: permission
  definition:
    v: **Definition:** A kind of act that defines a permission that has been granted.
  property:
    code:
      v: status
    value:
      v: active
  property:
    code:
      v: internalId
    value:
      v: 21381
  property:
    code:
      v: Name:Class
    value:
      v: Permission
concept:
  code:
    v: SLOT
  display:
    v: resource slot
  definition:
    v: **Definition:** A kind of act that may occur during the specified time period.
  property:
    code:
      v: status
    value:
      v: active
  property:
    code:
      v: internalId
    value:
      v: 19168
  property:
    code:
      v: Name:Class
    value:
      v: ResourceSlot

code:
  v: EVN
display:
  v: event (occurrence)
definition:
  v: **Definition:** An act that actually happens (may be an ongoing act or a documentation of a past act).
property:
  code:
    v: status
  value:
    v: active
property:
  code:
    v: internalId
  value:
    v: 10201
property:
  code:
    v: Name:Class
  value:
    v: Event

code:
  v: INT
display:
  v: intent
definition:
  v: **Definition:** An intention or plan for an act. **>UsageNotes:** The final outcome of the intent, the act that is intended to occur, is always an event. However the final outcome may be reached indirectly via steps through other intents, such as promise, permission request, or an appointment that may lead to an actual event to occur. Alternatively, the intended act may never occur.
property:
  code:
    v: status
  value:
    v: active
property:
  code:
    v: internalId
  value:
    v: 10199
property:
  code:
    v: Name:Class
  value:
    v: Intent
concept:
  code:
    v: _ActMoodDesire
  display:
    v: desire
  definition:
    v: **Definition:** A desire to have an act occur.
  property:
    code:
      v: notSelectable
    value:
      v: true
  property:
    code:
      v: status
    value:
      v: active
  property:
    code:
      v: internalId
    value:
      v: 23088
  property:
    code:
      v: Name:Class
    value:
      v: Desire
  concept:
    code:
      v: _ActMoodActRequest
    display:
      v: act request
    definition:
      v: **Definition:** A request (or order) for an act that is part of a defined request/fulfillment cycle. **UsageNotes:** Use of an HL7 defined request/fulfillment framework is not required to use this mood code.
    property:
      code:
        v: notSelectable
      value:
        v: true
    property:
      code:
        v: status
      value:
        v: active
    property:
      code:
        v: HL7usageNotes
      value:
        v: Use of an HL7 defined request/fulfillment framework is not required to use this mood code.
    property:
      code:
        v: internalId
      value:
        v: 23089
    property:
      code:
        v: Name:Class
      value:
        v: ActRequest
    concept:
      code:
        v: ARQ
      display:
        v: appointment request
      definition:
        v: **Definition:** A request act that is specialized for the appointment scheduling request/fulfillment cycle. An appointment request is fulfilled only and completely by an appointment (APT), i.e., all that the appointment request intends is to create an appointment *(the actual act may well not happen if that is the professional decision during the appointment)*.
    concept:
      code:
        v: PERMRQ
      display:
        v: permission request
      definition:
        v: **Definition:** A request for a permission to perform the act. Typically a payer (or possibly a supervisor) is being requested to give permission to perform the act. As opposed to the RQO, the requestee is not asked to perform or cause to perform the act but only to give the permission.
    concept:
      code:
        v: RQO
      display:
        v: request
      definition:
        v: **Definition:** A request act that is specialized for an event request/fulfillment cycle. **UsageNotes:** The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event. **UsageNotes:** The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request." Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept. The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.
    concept:
      code:
        v: ORD
      display:
        v: request
      definition:
        v: **Definition:** A request act that is specialized for an event request/fulfillment cycle. **UsageNotes:** The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event. **UsageNotes:** The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request." Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept. The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.
  concept:
    code:
      v: PRP
    display:
      v: proposal
    definition:
      v: **Definition:** A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.
    property:
      code:
        v: status
      value:
        v: active
    property:
      code:
        v: internalId
      value:
        v: 16726
    property:
      code:
        v: Name:Class
      value:
        v: Proposal
    concept:
      code:
        v: RMD
      display:
        v: recommendation
      definition:
        v: **Definition:** A suggestion that an act should be performed with an acceptance of some degree of professional responsibility for the resulting act. Not an explicit request. . **UsageNotes:** Where there is no clear definition or applicable concept of "professional responsibility", RMD becomes indistinguishable from PRP. .
concept:
  code:
    v: PRMS
  display:
    v: promise
  definition:
    v: **Definition:** A commitment to perform an act (may be either solicited or unsolicited). The committer becomes responsible to the other party for executing the act, and, as a consequence, the other party may rely on the first party to perform or cause to perform the act. **UsageNotes:** Commitments may be retracted or cancelled.
  property:
    code:
      v: status
    value:
      v: active
  property:
    code:
      v: HL7usageNotes
    value:
      v: Commitments may be retracted or cancelled.
  property:
    code:
      v: internalId
    value:
      v: 16728
  property:
    code:
      v: Name:Class
    value:
      v: Promise
  concept:
    code:
      v: APT
    display:
      v: appointment
    definition:
      v: **Definition:** An act that has been scheduled to be performed at a specific place and time.
    property:
      code:
        v: status
      value:
        v: active
    property:
      code:
        v: internalId
      value:
        v: 11626
    property:
      code:
        v: Name:Class
      value:
        v: Appointment

v: status

v: active

v: internalId

v: 11625

v: Name:Class

v: AppointmentRequest

v: status

v: active

v: internalId

v: 21382

v: Name:Class

v: PermissionRequest

v: status

v: active

v: synonymCode

v: ORD

v: HL7usageNotes

v: The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request." Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept. The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.

v: internalId

v: 19973

v: Name:Class

v: Request

v: status

v: retired

v: synonymCode

v: RQO

v: HL7usageNotes

v: The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request." Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept. The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.

v: internalId

v: 19973

v: Name:Class

v: Request

v: status

v: active

v: HL7usageNotes

v: Where there is no clear definition or applicable concept of "professional responsibility", RMD becomes indistinguishable from PRP. .

v: internalId

v: 21571

v: Name:Class

v: Recommendation

code:
  v: _ActMoodPredicate
display:
  v: ActMoodPredicate
definition:
  v: **Definition:** An act that expresses condition statements for other acts.
property:
  code:
    v: notSelectable
  value:
    v: true
property:
  code:
    v: status
  value:
    v: active
property:
  code:
    v: internalId
  value:
    v: 20936
property:
  code:
    v: Name:Class
  value:
    v: Predicate
concept:
  code:
    v: CRT
  display:
    v: criterion
  definition:
    v: ***Deprecation Comment:*** This concept This codes should no longer be used. Instead, set attribute Act.isCriterionInd to "true" and use the desired mood for your criterion. **Definition:** A condition that must be true for the source act to be considered.
  property:
    code:
      v: status
    value:
      v: deprecated
  property:
    code:
      v: deprecationDate
    value:
      v: 2010-07-12
  property:
    code:
      v: internalId
    value:
      v: 22042
  property:
    code:
      v: Name:Class
    value:
      v: Criterion
  concept:
    code:
      v: EVN.CRT
    display:
      v: event criterion
    definition:
      v: ***Deprecation Comment:*** This concept This codes should no longer be used. Instead, set attribute Act.isCriterionInd to "true" and use the desired mood for your criterion. **Definition:** A criterion (CRT) that has\_match = an event (EVN).
    property:
      code:
        v: status
      value:
        v: deprecated
    property:
      code:
        v: deprecationDate
      value:
        v: 2010-07-12
    property:
      code:
        v: internalId
      value:
        v: 10203
    property:
      code:
        v: Name:Class
      value:
        v: EventCriterion
  concept:
    code:
      v: GOL.CRT
    display:
      v: goal criterion
    definition:
      v: A criterion expressed over goals (ActMood.GOL).
    property:
      code:
        v: status
      value:
        v: retired
    property:
      code:
        v: internalId
      value:
        v: 23057
  concept:
    code:
      v: INT.CRT
    display:
      v: intent criterion
    definition:
      v: A criterion expressed over intents (ActMood.INT).
    property:
      code:
        v: status
      value:
        v: retired
    property:
      code:
        v: internalId
      value:
        v: 23054
    concept:
      code:
        v: PRMS.CRT
      display:
        v: promise criterion
      definition:
        v: A criterion expressed over promises (ActMood.PRMS).
    concept:
      code:
        v: RQO.CRT
      display:
        v: request criterion
      definition:
        v: A criterion expressed over requests or orders (ActMood.RQO).
  concept:
    code:
      v: RSK.CRT
    display:
      v: risk criterion
    definition:
      v: A criterion expressed over risks (ActMood.RSK).
    property:
      code:
        v: status
      value:
        v: retired
    property:
      code:
        v: internalId
      value:
        v: 23058
concept:
  code:
    v: EXPEC
  display:
    v: expectation
  definition:
    v: **Definition:** An act that is considered to have some noteworthy likelihood of occurring in the future (has\_match = event). **Examples:**Prognosis of a condition, Expected date of discharge from hospital, patient will likely need an emergency decompression of the intracranial pressure by morning. **UsageNotes:**INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with expectation, which is a prediction that something will happen in the future. GOL (goal) reflects a hope rather than a prediction. RSK (risk) reflects a potential negative event that may or may not be expected to happen.
  property:
    code:
      v: status
    value:
      v: active
  property:
    code:
      v: HL7usageNotes
    value:
      v: INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with expectation, which is a prediction that something will happen in the future. GOL (goal) reflects a hope rather than a prediction. RSK (risk) reflects a potential negative event that may or may not be expected to happen.
  property:
    code:
      v: internalId
    value:
      v: 21574
  property:
    code:
      v: Name:Class
    value:
      v: Expectation
  concept:
    code:
      v: GOL
    display:
      v: Goal
    definition:
      v: **Definition:** An expectation that is considered to be desirable to occur in the future **Examples:**Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction. **UsageNotes:** INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with goal which doesn't represent an intention to act, merely a hope for an eventual result. A goal is distinct from the intended actions to reach that goal. "I will reduce the dose of drug x to 20mg" is an intent. "I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg" is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope.
    property:
      code:
        v: status
      value:
        v: active
    property:
      code:
        v: HL7usageNotes
      value:
        v: INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with goal which doesn't represent an intention to act, merely a hope for an eventual result. A goal is distinct from the intended actions to reach that goal. "I will reduce the dose of drug x to 20mg" is an intent. "I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg" is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope.
    property:
      code:
        v: internalId
      value:
        v: 18864
    property:
      code:
        v: Name:Class
      value:
        v: Goal
  concept:
    code:
      v: RSK

v: status

v: retired

v: internalId

v: 23056

v: status

v: retired

v: internalId

v: 23055

v: risk

v: **Definition:**An act that may occur in the future and which is regarded as undesirable **Examples:**Increased risk of DVT, at risk for sub-acute bacterial endocarditis. **UsageNotes:**Note: An observation in RSK mood expresses the undesirable act, and not the underlying risk factor. A risk factor that is present (e.g. obesity, smoking, etc) should be expressed in event mood. INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen. GOL (goal) reflects a hope to achieve something. EXPEC (expectation) is the prediction of a positive or negative event. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen, and may not be expected to happen.

code:
  v: status
value:
  v: active

code:
  v: HL7usageNotes
value:
  v: Note: An observation in RSK mood expresses the undesirable act, and not the underlying risk factor. A risk factor that is present (e.g. obesity, smoking, etc) should be expressed in event mood. INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen. GOL (goal) reflects a hope to achieve something. EXPEC (expectation) is the prediction of a positive or negative event. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen, and may not be expected to happen.

code:
  v: internalId
value:
  v: 21575

code:
  v: Name:Class
value:
  v: Risk

code:
  v: OPT
display:
  v: option
definition:
  v: **Definition:** One of a set of acts that specify an option for the property values that the parent act may have. Typically used in definitions or orders to describe alternatives. An option can only be used as a group, that is, all assigned values must be used together. The actual mood of the act is the same as the parent act, and they must be linked by an actrelationship with type = OPTN.
property:
  code:
    v: status
  value:
    v: active
property:
  code:
    v: internalId
  value:
    v: 10204
property:
  code:
    v: Name:Class
  value:
    v: Option