v3-ActMood
type: CodeSystem
node role: treeRoot
resource.id:
  value: v3-ActMood
resource.language:
  value: en
domain resource.text:
  narrative.status:
    value: extensions
  narrative.div: Properties Code URL Type Description 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 Coding Inverse of Specializes. Only included as a derived relationship. 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 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 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 http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Class code The formal name for the class clone under this code 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 http://hl7.org/fhir/concept-properties#synonym code An additional concept code that was also attributed to a concept HL7usageNotes http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes string HL7 Concept Usage Notes This code system http://terminology.hl7.org/CodeSystem/v3-ActMood defines the following codes: Lvl Code Display Definition Deprecated internalId status deprecationDate Name:Class Not Selectable synonymCode HL7 Concept Usage Notes 1 _ActMoodCompletionTrack ActMoodCompletionTrack These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed. 20935 active Process true 2 _ActMoodPotential potential **Definition:** A possible act. 23087 acti…
code system.url:
  value: http://terminology.hl7.org/CodeSystem/v3-ActMood
code system.identifier:
  index: 0
  identifier.system:
    value: urn:ietf:rfc:3986
  identifier.value:
    value: urn:oid:2.16.840.1.113883.5.1001
code system.version:
  value: 2.1.0
code system.name:
  value: ActMood
code system.title:
  value: ActMood
code system.status:
  value: active
code system.experimental:
  value: false
code system.date:
  value: 2019-03-20
code system.publisher:
  value: Health Level 7
code system.contact:
  index: 0
  contact detail.name:
    value: Health Level Seven
code system.description:
  value: 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.
code system.case sensitive:
  value: true
code system.hierarchy meaning:
  value: is-a
code system.content:
  value: complete
code system.property:
  index: 0
  element.extension:
    index: 0
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry
    extension.value code:
      value: antisymmetric
  element.extension:
    index: 1
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity
    extension.value code:
      value: transitive
  element.extension:
    index: 2
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity
    extension.value code:
      value: irreflexive
  element.extension:
    index: 3
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable
    extension.value boolean:
      value: true
  element.extension:
    index: 4
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind
    extension.value code:
      value: Specializes
  element.extension:
    index: 5
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName
    extension.value string:
      value: Generalizes
  code system.property.code:
    value: Specializes
  code system.property.description:
    value: 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.
  code system.property.type:
    value: Coding
code system.property:
  index: 1
  element.extension:
    index: 0
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry
    extension.value code:
      value: antisymmetric
  element.extension:
    index: 1
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity
    extension.value code:
      value: transitive
  element.extension:
    index: 2
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity
    extension.value code:
      value: irreflexive
  element.extension:
    index: 3
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable
    extension.value boolean:
      value: true
  element.extension:
    index: 4
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind
    extension.value code:
      value: Generalizes
  element.extension:
    index: 5
    extension.url:
      value: http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName
    extension.value string:
      value: Specializes
  code system.property.code:
    value: Generalizes
  code system.property.description:
    value: Inverse of Specializes. Only included as a derived relationship.
  code system.property.type:
    value: Coding
code system.property:
  index: 2
  code system.property.code:
    value: internalId
  code system.property.uri:
    value: http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id
  code system.property.description:
    value: The internal identifier for the concept in the HL7 Access database repository.
  code system.property.type:
    value: code
code system.property:
  index: 3
  code system.property.code:
    value: status
  code system.property.uri:
    value: http://hl7.org/fhir/concept-properties#status
  code system.property.description:
    value: A property that indicates the status of the concept. One of active, experimental, deprecated, or retired.
  code system.property.type:
    value: code
code system.property:
  index: 4
  code system.property.code:
    value: deprecationDate
  code system.property.uri:
    value: http://hl7.org/fhir/concept-properties#deprecationDate
  code system.property.description:
    value: The date at which a concept was deprecated. Concepts that are deprecated but not inactive can still be used, but their use is discouraged.
  code system.property.type:
    value: dateTime
code system.property:
  index: 5
  code system.property.code:
    value: Name:Class
  code system.property.uri:
    value: http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Class
  code system.property.description:
    value: The formal name for the class clone under this code
  code system.property.type:
    value: code
code system.property:
  index: 6
  code system.property.code:
    value: notSelectable
  code system.property.uri:
    value: http://hl7.org/fhir/concept-properties#notSelectable
  code system.property.description:
    value: Indicates that the code is abstract - only intended to be used as a selector for other concepts
  code system.property.type:
    value: boolean
code system.property:
  index: 7
  code system.property.code:
    value: synonymCode
  code system.property.uri:
    value: http://hl7.org/fhir/concept-properties#synonym
  code system.property.description:
    value: An additional concept code that was also attributed to a concept
  code system.property.type:
    value: code
code system.property:
  index: 8
  code system.property.code:
    value: HL7usageNotes
  code system.property.uri:
    value: http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes
  code system.property.description:
    value: HL7 Concept Usage Notes
  code system.property.type:
    value: string

index: 0
code system.concept.code:
  value: _ActMoodCompletionTrack
code system.concept.display:
  value: ActMoodCompletionTrack
code system.concept.definition:
  value: These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.
code system.concept.property:
  index: 0
  code system.concept.property.code:
    value: notSelectable
  code system.concept.property.value boolean:
    value: true
code system.concept.property:
  index: 1
  code system.concept.property.code:
    value: status
  code system.concept.property.value code:
    value: active
code system.concept.property:
  index: 2
  code system.concept.property.code:
    value: internalId
  code system.concept.property.value code:
    value: 20935
code system.concept.property:
  index: 3
  code system.concept.property.code:
    value: Name:Class
  code system.concept.property.value code:
    value: Process
code system.concept.concept:
  index: 0
  code system.concept.code:
    value: _ActMoodPotential
  code system.concept.display:
    value: potential
  code system.concept.definition:
    value: **Definition:** A possible act.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: notSelectable
    code system.concept.property.value boolean:
      value: true
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 23087
  code system.concept.property:
    index: 3
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: Potential
  code system.concept.concept:
    index: 0
    code system.concept.code:
      value: DEF
    code system.concept.display:
      value: definition
    code system.concept.definition:
      value: **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.
    code system.concept.property:
      index: 0
      code system.concept.property.code:
        value: status
      code system.concept.property.value code:
        value: active
    code system.concept.property:
      index: 1
      code system.concept.property.code:
        value: internalId
      code system.concept.property.value code:
        value: 10198
    code system.concept.property:
      index: 2
      code system.concept.property.code:
        value: Name:Class
      code system.concept.property.value code:
        value: Definition
  code system.concept.concept:
    index: 1
    code system.concept.code:
      value: PERM
    code system.concept.display:
      value: permission
    code system.concept.definition:
      value: **Definition:** A kind of act that defines a permission that has been granted.
    code system.concept.property:
      index: 0
      code system.concept.property.code:
        value: status
      code system.concept.property.value code:
        value: active
    code system.concept.property:
      index: 1
      code system.concept.property.code:
        value: internalId
      code system.concept.property.value code:
        value: 21381
    code system.concept.property:
      index: 2
      code system.concept.property.code:
        value: Name:Class
      code system.concept.property.value code:
        value: Permission
  code system.concept.concept:
    index: 2
    code system.concept.code:
      value: SLOT
    code system.concept.display:
      value: resource slot
    code system.concept.definition:
      value: **Definition:** A kind of act that may occur during the specified time period.
    code system.concept.property:
      index: 0
      code system.concept.property.code:
        value: status
      code system.concept.property.value code:
        value: active
    code system.concept.property:
      index: 1
      code system.concept.property.code:
        value: internalId
      code system.concept.property.value code:
        value: 19168
    code system.concept.property:
      index: 2
      code system.concept.property.code:
        value: Name:Class
      code system.concept.property.value code:
        value: ResourceSlot
code system.concept.concept:
  index: 1
  code system.concept.code:
    value: EVN
  code system.concept.display:
    value: event (occurrence)
  code system.concept.definition:
    value: **Definition:** An act that actually happens (may be an ongoing act or a documentation of a past act).
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 10201
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: Event
code system.concept.concept:
  index: 2
  code system.concept.code:
    value: INT
  code system.concept.display:
    value: intent
  code system.concept.definition:
    value: **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.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 10199
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: Intent
  code system.concept.concept:
    index: 0
    code system.concept.code:
      value: _ActMoodDesire
    code system.concept.display:
      value: desire
    code system.concept.definition:
      value: **Definition:** A desire to have an act occur.
    code system.concept.property:
      index: 0

value: notSelectable

value: true

index: 1
code system.concept.property.code:
  value: status
code system.concept.property.value code:
  value: active

index: 2
code system.concept.property.code:
  value: internalId
code system.concept.property.value code:
  value: 23088

index: 3
code system.concept.property.code:
  value: Name:Class
code system.concept.property.value code:
  value: Desire

index: 0
code system.concept.code:
  value: _ActMoodActRequest
code system.concept.display:
  value: act request
code system.concept.definition:
  value: **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.
code system.concept.property:
  index: 0
  code system.concept.property.code:
    value: notSelectable
  code system.concept.property.value boolean:
    value: true
code system.concept.property:
  index: 1
  code system.concept.property.code:
    value: status
  code system.concept.property.value code:
    value: active
code system.concept.property:
  index: 2
  code system.concept.property.code:
    value: HL7usageNotes
  code system.concept.property.value string:
    value: Use of an HL7 defined request/fulfillment framework is not required to use this mood code.
code system.concept.property:
  index: 3
  code system.concept.property.code:
    value: internalId
  code system.concept.property.value code:
    value: 23089
code system.concept.property:
  index: 4
  code system.concept.property.code:
    value: Name:Class
  code system.concept.property.value code:
    value: ActRequest
code system.concept.concept:
  index: 0
  code system.concept.code:
    value: ARQ
  code system.concept.display:
    value: appointment request
  code system.concept.definition:
    value: **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)*.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 11625
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: AppointmentRequest
code system.concept.concept:
  index: 1
  code system.concept.code:
    value: PERMRQ
  code system.concept.display:
    value: permission request
  code system.concept.definition:
    value: **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.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 21382
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: PermissionRequest
code system.concept.concept:
  index: 2
  code system.concept.code:
    value: RQO
  code system.concept.display:
    value: request
  code system.concept.definition:
    value: **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.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: synonymCode
    code system.concept.property.value code:
      value: ORD
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: HL7usageNotes
    code system.concept.property.value string:
      value: 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.
  code system.concept.property:
    index: 3
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 19973
  code system.concept.property:
    index: 4
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: Request
code system.concept.concept:
  index: 3
  code system.concept.code:
    value: ORD
  code system.concept.display:
    value: request
  code system.concept.definition:
    value: **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.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: retired
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: synonymCode
    code system.concept.property.value code:
      value: RQO
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: HL7usageNotes
    code system.concept.property.value string:
      value: 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.
  code system.concept.property:
    index: 3
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 19973
  code system.concept.property:
    index: 4
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: Request

index: 1
code system.concept.code:
  value: PRP
code system.concept.display:
  value: proposal
code system.concept.definition:
  value: **Definition:** A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.
code system.concept.property:
  index: 0
  code system.concept.property.code:
    value: status
  code system.concept.property.value code:
    value: active
code system.concept.property:
  index: 1
  code system.concept.property.code:
    value: internalId
  code system.concept.property.value code:
    value: 16726
code system.concept.property:
  index: 2
  code system.concept.property.code:
    value: Name:Class
  code system.concept.property.value code:
    value: Proposal
code system.concept.concept:
  index: 0
  code system.concept.code:
    value: RMD
  code system.concept.display:
    value: recommendation
  code system.concept.definition:
    value: **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. .
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: HL7usageNotes
    code system.concept.property.value string:
      value: Where there is no clear definition or applicable concept of "professional responsibilityâ€?, RMD becomes indistinguishable from PRP. .
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 21571
  code system.concept.property:
    index: 3
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: Recommendation

index: 1
code system.concept.code:
  value: PRMS
code system.concept.display:
  value: promise
code system.concept.definition:
  value: **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.
code system.concept.property:
  index: 0
  code system.concept.property.code:
    value: status
  code system.concept.property.value code:
    value: active
code system.concept.property:
  index: 1
  code system.concept.property.code:
    value: HL7usageNotes
  code system.concept.property.value string:
    value: Commitments may be retracted or cancelled.
code system.concept.property:
  index: 2
  code system.concept.property.code:
    value: internalId
  code system.concept.property.value code:
    value: 16728
code system.concept.property:
  index: 3
  code system.concept.property.code:
    value: Name:Class
  code system.concept.property.value code:
    value: Promise
code system.concept.concept:
  index: 0
  code system.concept.code:
    value: APT
  code system.concept.display:
    value: appointment
  code system.concept.definition:
    value: **Definition:** An act that has been scheduled to be performed at a specific place and time.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 11626
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: Appointment

index: 1
code system.concept.code:
  value: _ActMoodPredicate
code system.concept.display:
  value: ActMoodPredicate
code system.concept.definition:
  value: **Definition:** An act that expresses condition statements for other acts.
code system.concept.property:
  index: 0
  code system.concept.property.code:
    value: notSelectable
  code system.concept.property.value boolean:
    value: true
code system.concept.property:
  index: 1
  code system.concept.property.code:
    value: status
  code system.concept.property.value code:
    value: active
code system.concept.property:
  index: 2
  code system.concept.property.code:
    value: internalId
  code system.concept.property.value code:
    value: 20936
code system.concept.property:
  index: 3
  code system.concept.property.code:
    value: Name:Class
  code system.concept.property.value code:
    value: Predicate
code system.concept.concept:
  index: 0
  code system.concept.code:
    value: CRT
  code system.concept.display:
    value: criterion
  code system.concept.definition:
    value: ***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.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: deprecated
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: deprecationDate
    code system.concept.property.value date time:
      value: 2010-07-12
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: internalId
    code system.concept.property.value code:
      value: 22042
  code system.concept.property:
    index: 3
    code system.concept.property.code:
      value: Name:Class
    code system.concept.property.value code:
      value: Criterion
  code system.concept.concept:
    index: 0
    code system.concept.code:
      value: EVN.CRT
    code system.concept.display:
      value: event criterion
    code system.concept.definition:
      value: ***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).
    code system.concept.property:
      index: 0
      code system.concept.property.code:
        value: status
      code system.concept.property.value code:
        value: deprecated
    code system.concept.property:
      index: 1
      code system.concept.property.code:
        value: deprecationDate
      code system.concept.property.value date time:
        value: 2010-07-12
    code system.concept.property:
      index: 2
      code system.concept.property.code:
        value: internalId
      code system.concept.property.value code:
        value: 10203
    code system.concept.property:
      index: 3
      code system.concept.property.code:
        value: Name:Class
      code system.concept.property.value code:
        value: EventCriterion
  code system.concept.concept:
    index: 1
    code system.concept.code:
      value: GOL.CRT
    code system.concept.display:
      value: goal criterion
    code system.concept.definition:
      value: A criterion expressed over goals (ActMood.GOL).
    code system.concept.property:
      index: 0
      code system.concept.property.code:
        value: status
      code system.concept.property.value code:
        value: retired
    code system.concept.property:
      index: 1
      code system.concept.property.code:
        value: internalId
      code system.concept.property.value code:
        value: 23057
  code system.concept.concept:
    index: 2
    code system.concept.code:
      value: INT.CRT
    code system.concept.display:
      value: intent criterion
    code system.concept.definition:
      value: A criterion expressed over intents (ActMood.INT).
    code system.concept.property:
      index: 0
      code system.concept.property.code:
        value: status
      code system.concept.property.value code:
        value: retired
    code system.concept.property:
      index: 1
      code system.concept.property.code:
        value: internalId
      code system.concept.property.value code:
        value: 23054
    code system.concept.concept:
      index: 0
      code system.concept.code:
        value: PRMS.CRT
      code system.concept.display:
        value: promise criterion
      code system.concept.definition:
        value: A criterion expressed over promises (ActMood.PRMS).
      code system.concept.property:
        index: 0
      code system.concept.property:
        index: 1
    code system.concept.concept:
      index: 1
      code system.concept.code:
        value: RQO.CRT
      code system.concept.display:
        value: request criterion
      code system.concept.definition:
        value: A criterion expressed over requests or orders (ActMood.RQO).
      code system.concept.property:
        index: 0
      code system.concept.property:
        index: 1
  code system.concept.concept:
    index: 3
    code system.concept.code:
      value: RSK.CRT
    code system.concept.display:
      value: risk criterion
    code system.concept.definition:
      value: A criterion expressed over risks (ActMood.RSK).
    code system.concept.property:
      index: 0
      code system.concept.property.code:
        value: status
      code system.concept.property.value code:
        value: retired
    code system.concept.property:
      index: 1
      code system.concept.property.code:
        value: internalId
      code system.concept.property.value code:
        value: 23058
code system.concept.concept:
  index: 1
  code system.concept.code:
    value: EXPEC
  code system.concept.display:
    value: expectation
  code system.concept.definition:
    value: **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.
  code system.concept.property:
    index: 0
    code system.concept.property.code:
      value: status
    code system.concept.property.value code:
      value: active
  code system.concept.property:
    index: 1
    code system.concept.property.code:
      value: HL7usageNotes
    code system.concept.property.value string:
      value: 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.
  code system.concept.property:
    index: 2
    code system.concept.property.code:
      value: internalId

value: status

value: retired

value: internalId

value: 23056

value: status

value: retired

value: internalId

value: 23055

value: 21574

index: 3
code system.concept.property.code:
  value: Name:Class
code system.concept.property.value code:
  value: Expectation

index: 0
code system.concept.code:
  value: GOL
code system.concept.display:
  value: Goal
code system.concept.definition:
  value: **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.
code system.concept.property:
  index: 0
  code system.concept.property.code:
    value: status
  code system.concept.property.value code:
    value: active
code system.concept.property:
  index: 1
  code system.concept.property.code:
    value: HL7usageNotes
  code system.concept.property.value string:
    value: 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.
code system.concept.property:
  index: 2
  code system.concept.property.code:
    value: internalId
  code system.concept.property.value code:
    value: 18864
code system.concept.property:
  index: 3
  code system.concept.property.code:
    value: Name:Class
  code system.concept.property.value code:
    value: Goal

index: 1
code system.concept.code:
  value: RSK
code system.concept.display:
  value: risk
code system.concept.definition:
  value: **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 system.concept.property:
  index: 0
  code system.concept.property.code:
    value: status
  code system.concept.property.value code:
    value: active
code system.concept.property:
  index: 1
  code system.concept.property.code:
    value: HL7usageNotes
  code system.concept.property.value string:
    value: 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 system.concept.property:
  index: 2
  code system.concept.property.code:
    value: internalId
  code system.concept.property.value code:
    value: 21575
code system.concept.property:
  index: 3
  code system.concept.property.code:
    value: Name:Class
  code system.concept.property.value code:
    value: Risk

index: 2
code system.concept.code:
  value: OPT
code system.concept.display:
  value: option
code system.concept.definition:
  value: **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.
code system.concept.property:
  index: 0
  code system.concept.property.code:
    value: status
  code system.concept.property.value code:
    value: active
code system.concept.property:
  index: 1
  code system.concept.property.code:
    value: internalId
  code system.concept.property.value code:
    value: 10204
code system.concept.property:
  index: 2
  code system.concept.property.code:
    value: Name:Class
  code system.concept.property.value code:
    value: Option