FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource CodeSystem/FHIR Server from package hl7.terminology#current (93 ms)

Package hl7.terminology
Type CodeSystem
Id Id
FHIR Version R5
Source http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/CodeSystem-v3-ActMood.html
Url http://terminology.hl7.org/CodeSystem/v3-ActMood
Version 3.0.0
Status active
Date 2023-05-30
Name ActMood
Title ActMood
Experimental False
Realm uv
Authority hl7
Description 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 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.html
Content complete

Resources that use this resource

ValueSet
http://hl7.org/cda/stds/core/ValueSet/CDAActMood CDAActMood
http://hl7.org/cda/stds/core/ValueSet/CDAActMoodIntent CDAActMoodIntent
v2-0725 hl7VS-moodCodes
v3-ActMood ActMood
v3-ActMoodActRequest ActMoodActRequest
v3-ActMoodAppointment ActMoodAppointment
v3-ActMoodAppointmentRequest ActMoodAppointmentRequest
v3-ActMoodCompletionTrack ActMoodCompletionTrack
v3-ActMoodCriterion ActMoodCriterion
v3-ActMoodDefinition ActMoodDefinition
v3-ActMoodDesire ActMoodDesire
v3-ActMoodEventCriterion ActMoodEventCriterion
v3-ActMoodEventOccurrence ActMoodEventOccurrence
v3-ActMoodExpectation ActMoodExpectation
v3-ActMoodGoal ActMoodGoal
v3-ActMoodIntent ActMoodIntent
v3-ActMoodOption ActMoodOption
v3-ActMoodPermission ActMoodPermission
v3-ActMoodPermissionRequest ActMoodPermissionRequest
v3-ActMoodPotential ActMoodPotential
v3-ActMoodPredicate ActMoodPredicate
v3-ActMoodPromise ActMoodPromise
v3-ActMoodProposal ActMoodProposal
v3-ActMoodRecommendation ActMoodRecommendation
v3-ActMoodRequest ActMoodRequest
v3-ActMoodResourceSlot ActMoodResourceSlot
v3-ActMoodRisk ActMoodRisk
v3-xActMoodCompletionCriterion x_ActMoodCompletionCriterion
v3-xActMoodDefEvn x_ActMoodDefEvn
v3-xActMoodDefEvnRqo x_ActMoodDefEvnRqo
v3-xActMoodDefEvnRqoPrmsPrp x_ActMoodDefEvnRqoPrmsPrp
v3-xActMoodDocumentObservation x_ActMoodDocumentObservation
v3-xActMoodEvnOrdPrmsPrp x_ActMoodEvnOrdPrmsPrp
v3-xActMoodIntentEvent x_ActMoodIntentEvent
v3-xActMoodOrdPrms x_ActMoodOrdPrms
v3-xActMoodOrdPrmsEvn x_ActMoodOrdPrmsEvn
v3-xActMoodPermPermrq x_ActMoodPermPermrq
v3-xActMoodRequestEvent x_ActMoodRequestEvent
v3-xActMoodRqoPrpAptArq x_ActMoodRqoPrpAptArq
v3-xClinicalStatementActMood x_ClinicalStatementActMood
v3-xClinicalStatementEncounterMood x_ClinicalStatementEncounterMood
v3-xClinicalStatementExposureMood x_ClinicalStatementExposureMood
v3-xClinicalStatementObservationMood x_ClinicalStatementObservationMood
v3-xClinicalStatementProcedureMood x_ClinicalStatementProcedureMood
v3-xClinicalStatementSubstanceMood x_ClinicalStatementSubstanceMood
v3-xClinicalStatementSupplyMood x_ClinicalStatementSupplyMood
v3-xDocumentActMood x_DocumentActMood
v3-xDocumentEncounterMood x_DocumentEncounterMood
v3-xDocumentProcedureMood x_DocumentProcedureMood
v3-xDocumentSubstanceMood x_DocumentSubstanceMood

Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: CodeSystem v3-ActMood

Language: en

Properties

This code system defines the following properties for its concepts

NameCodeURITypeDescription
SpecializesSpecializesCodingThe 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.
GeneralizesGeneralizesCodingInverse of Specializes. Only included as a derived relationship.
internalIdinternalIdhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-idcodeThe internal identifier for the concept in the HL7 Access database repository.
Statusstatushttp://hl7.org/fhir/concept-properties#statuscodeA property that indicates the status of the concept. One of active, experimental, deprecated, or retired.
Deprecation DatedeprecationDatehttp://hl7.org/fhir/concept-properties#deprecationDatedateTimeThe date at which a concept was deprecated. Concepts that are deprecated but not inactive can still be used, but their use is discouraged.
Name:ClassName:Classhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-ClasscodeThe formal name for the class clone under this code
Not SelectablenotSelectablehttp://hl7.org/fhir/concept-properties#notSelectablebooleanIndicates that the code is abstract - only intended to be used as a selector for other concepts
SynonymsynonymCodehttp://hl7.org/fhir/concept-properties#synonymcodeAn additional concept code that was also attributed to a concept
HL7 Concept Usage NotesHL7usageNoteshttp://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotesstringHL7 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:

LvlCodeDisplayDefinitionDeprecatedinternalIdStatusDeprecation DateName:ClassNot SelectableSynonymHL7 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.

20935activeProcesstrue
2  _ActMoodPotential potential

Definition: A possible act.

23087activePotentialtrue
3    DEF definition

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.

10198activeDefinition
3    PERM permission

Definition: A kind of act that defines a permission that has been granted.

21381activePermission
3    SLOT resource slot

Definition: A kind of act that may occur during the specified time period.

19168activeResourceSlot
2  EVN event (occurrence)

Definition: An act that actually happens (may be an ongoing act or a documentation of a past act).

10201activeEvent
2  INT intent

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.

10199activeIntent
3    _ActMoodDesire desire

Definition: A desire to have an act occur.

23088activeDesiretrue
4      _ActMoodActRequest act request

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.

23089activeActRequesttrueUse of an HL7 defined request/fulfillment framework is not required to use this mood code.
5        ARQ appointment request

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).

11625activeAppointmentRequest
5        PERMRQ permission request

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.

21382activePermissionRequest
5        RQO request

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.

19973activeRequestORDThe 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.
5        ORD request

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.

19973retiredRequestRQOThe 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.
4      PRP proposal

Definition: A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.

16726activeProposal
5        RMD recommendation

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. .

21571activeRecommendationWhere there is no clear definition or applicable concept of "professional responsibility", RMD becomes indistinguishable from PRP. .
3    PRMS promise

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.

16728activePromiseCommitments may be retracted or cancelled.
4      APT appointment

Definition: An act that has been scheduled to be performed at a specific place and time.

11626activeAppointment
1_ActMoodPredicate ActMoodPredicate

Definition: An act that expresses condition statements for other acts.

20936activePredicatetrue
2  CRT criterion

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.

Deprecated22042deprecated2010-07-12Criterion
3    EVN.CRT event criterion

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).

Deprecated10203deprecated2010-07-12EventCriterion
3    GOL.CRT goal criterion

A criterion expressed over goals (ActMood.GOL).

23057retired
3    INT.CRT intent criterion

A criterion expressed over intents (ActMood.INT).

23054retired
4      PRMS.CRT promise criterion

A criterion expressed over promises (ActMood.PRMS).

23056retired
4      RQO.CRT request criterion

A criterion expressed over requests or orders (ActMood.RQO).

23055retired
3    RSK.CRT risk criterion

A criterion expressed over risks (ActMood.RSK).

23058retired
2  EXPEC expectation

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.

21574activeExpectationINT (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.
3    GOL Goal

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.

18864activeGoalINT (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.
3    RSK risk

**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.

21575activeRiskNote: 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.
2  OPT option

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.

10204activeOption

Source

{
  "resourceType" : "CodeSystem",
  "id" : "v3-ActMood",
  "language" : "en",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><p class=\"res-header-id\"><b>Generated Narrative: CodeSystem v3-ActMood</b></p><a name=\"v3-ActMood\"> </a><a name=\"hcv3-ActMood\"> </a><a name=\"v3-ActMood-en-US\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Language: en</p></div><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class=\"grid\"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>Specializes</td><td>Specializes</td><td/><td>Coding</td><td>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.</td></tr><tr><td>Generalizes</td><td>Generalizes</td><td/><td>Coding</td><td>Inverse of Specializes. Only included as a derived relationship.</td></tr><tr><td>internalId</td><td>internalId</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id</td><td>code</td><td>The internal identifier for the concept in the HL7 Access database repository.</td></tr><tr><td>Status</td><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>code</td><td>A property that indicates the status of the concept. One of active, experimental, deprecated, or retired.</td></tr><tr><td>Deprecation Date</td><td>deprecationDate</td><td>http://hl7.org/fhir/concept-properties#deprecationDate</td><td>dateTime</td><td>The date at which a concept was deprecated. Concepts that are deprecated but not inactive can still be used, but their use is discouraged.</td></tr><tr><td>Name:Class</td><td>Name:Class</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Class</td><td>code</td><td>The formal name for the class clone under this code</td></tr><tr><td>Not Selectable</td><td>notSelectable</td><td>http://hl7.org/fhir/concept-properties#notSelectable</td><td>boolean</td><td>Indicates that the code is abstract - only intended to be used as a selector for other concepts</td></tr><tr><td>Synonym</td><td>synonymCode</td><td>http://hl7.org/fhir/concept-properties#synonym</td><td>code</td><td>An additional concept code that was also attributed to a concept</td></tr><tr><td>HL7 Concept Usage Notes</td><td>HL7usageNotes</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes</td><td>string</td><td>HL7 Concept Usage Notes</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/v3-ActMood</code> defines the following codes in a Is-A hierarchy:</p><table class=\"codes\"><tr><td><b>Lvl</b></td><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>Deprecated</b></td><td><b>internalId</b></td><td><b>Status</b></td><td><b>Deprecation Date</b></td><td><b>Name:Class</b></td><td><b>Not Selectable</b></td><td><b>Synonym</b></td><td><b>HL7 Concept Usage Notes</b></td></tr><tr><td>1</td><td style=\"white-space:nowrap\">_ActMoodCompletionTrack<a name=\"v3-ActMood-_ActMoodCompletionTrack\"> </a></td><td>ActMoodCompletionTrack</td><td><div><p>These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.</p>\n</div></td><td/><td>20935</td><td>active</td><td/><td>Process</td><td>true</td><td/><td/></tr><tr><td>2</td><td style=\"white-space:nowrap\">��_ActMoodPotential<a name=\"v3-ActMood-_ActMoodPotential\"> </a></td><td>potential</td><td><div><p><strong>Definition:</strong> A possible act.</p>\n</div></td><td/><td>23087</td><td>active</td><td/><td>Potential</td><td>true</td><td/><td/></tr><tr><td>3</td><td style=\"white-space:nowrap\">����DEF<a name=\"v3-ActMood-DEF\"> </a></td><td>definition</td><td><div><p><strong>Definition:</strong> A definition of a kind of act that can occur .</p>\n<p><strong>OpenIssue:</strong> 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 &quot;retired&quot; in the future in favor of the more general ActMood.CRT.</p>\n</div></td><td/><td>10198</td><td>active</td><td/><td>Definition</td><td/><td/><td/></tr><tr><td>3</td><td style=\"white-space:nowrap\">����PERM<a name=\"v3-ActMood-PERM\"> </a></td><td>permission</td><td><div><p><strong>Definition:</strong> A kind of act that defines a permission that has been granted.</p>\n</div></td><td/><td>21381</td><td>active</td><td/><td>Permission</td><td/><td/><td/></tr><tr><td>3</td><td style=\"white-space:nowrap\">����SLOT<a name=\"v3-ActMood-SLOT\"> </a></td><td>resource slot</td><td><div><p><strong>Definition:</strong> A kind of act that may occur during the specified time period.</p>\n</div></td><td/><td>19168</td><td>active</td><td/><td>ResourceSlot</td><td/><td/><td/></tr><tr><td>2</td><td style=\"white-space:nowrap\">��EVN<a name=\"v3-ActMood-EVN\"> </a></td><td>event (occurrence)</td><td><div><p><strong>Definition:</strong> An act that actually happens (may be an ongoing act or a documentation of a past act).</p>\n</div></td><td/><td>10201</td><td>active</td><td/><td>Event</td><td/><td/><td/></tr><tr><td>2</td><td style=\"white-space:nowrap\">��INT<a name=\"v3-ActMood-INT\"> </a></td><td>intent</td><td><div><p><strong>Definition:</strong> An intention or plan for an act.</p>\n<p><strong>&gt;UsageNotes:</strong> 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.</p>\n</div></td><td/><td>10199</td><td>active</td><td/><td>Intent</td><td/><td/><td/></tr><tr><td>3</td><td style=\"white-space:nowrap\">����_ActMoodDesire<a name=\"v3-ActMood-_ActMoodDesire\"> </a></td><td>desire</td><td><div><p><strong>Definition:</strong> A desire to have an act occur.</p>\n</div></td><td/><td>23088</td><td>active</td><td/><td>Desire</td><td>true</td><td/><td/></tr><tr><td>4</td><td style=\"white-space:nowrap\">������_ActMoodActRequest<a name=\"v3-ActMood-_ActMoodActRequest\"> </a></td><td>act request</td><td><div><p><strong>Definition:</strong> A request (or order) for an act that is part of a defined request/fulfillment cycle.</p>\n<p><strong>UsageNotes:</strong> Use of an HL7 defined request/fulfillment framework is not required to use this mood code.</p>\n</div></td><td/><td>23089</td><td>active</td><td/><td>ActRequest</td><td>true</td><td/><td>Use of an HL7 defined request/fulfillment framework is not required to use this mood code.</td></tr><tr><td>5</td><td style=\"white-space:nowrap\">��������ARQ<a name=\"v3-ActMood-ARQ\"> </a></td><td>appointment request</td><td><div><p><strong>Definition:</strong> 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 <em>(the actual act may well not happen if that is the professional decision during the appointment)</em>.</p>\n</div></td><td/><td>11625</td><td>active</td><td/><td>AppointmentRequest</td><td/><td/><td/></tr><tr><td>5</td><td style=\"white-space:nowrap\">��������PERMRQ<a name=\"v3-ActMood-PERMRQ\"> </a></td><td>permission request</td><td><div><p><strong>Definition:</strong> 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.</p>\n</div></td><td/><td>21382</td><td>active</td><td/><td>PermissionRequest</td><td/><td/><td/></tr><tr><td>5</td><td style=\"white-space:nowrap\">��������RQO<a name=\"v3-ActMood-RQO\"> </a></td><td>request</td><td><div><p><strong>Definition:</strong> A request act that is specialized for an event request/fulfillment cycle.</p>\n<p><strong>UsageNotes:</strong> 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.</p>\n<p><strong>UsageNotes:</strong> The concepts of a &quot;request&quot; and an &quot;order&quot; 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. &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; 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 &quot;request.&quot;</p>\n<p>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 &quot;local&quot; 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.</p>\n<p>The critical distinction here, is the difference between this concept and an &quot;intent&quot;, 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.</p>\n</div></td><td/><td>19973</td><td>active</td><td/><td>Request</td><td/><td>ORD</td><td>The concepts of a &quot;request&quot; and an &quot;order&quot; 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. &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; 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 &quot;request.&quot; 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 &quot;local&quot; 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 &quot;intent&quot;, 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.</td></tr><tr style=\"background-color: #ffeeee\"><td>5</td><td style=\"white-space:nowrap\">��������ORD<a name=\"v3-ActMood-ORD\"> </a></td><td>request</td><td><div><p><strong>Definition:</strong> A request act that is specialized for an event request/fulfillment cycle.</p>\n<p><strong>UsageNotes:</strong> 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.</p>\n<p><strong>UsageNotes:</strong> The concepts of a &quot;request&quot; and an &quot;order&quot; 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. &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; 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 &quot;request.&quot;</p>\n<p>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 &quot;local&quot; 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.</p>\n<p>The critical distinction here, is the difference between this concept and an &quot;intent&quot;, 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.</p>\n</div></td><td/><td>19973</td><td>retired</td><td/><td>Request</td><td/><td>RQO</td><td>The concepts of a &quot;request&quot; and an &quot;order&quot; 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. &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; 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 &quot;request.&quot; 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 &quot;local&quot; 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 &quot;intent&quot;, 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.</td></tr><tr><td>4</td><td style=\"white-space:nowrap\">������PRP<a name=\"v3-ActMood-PRP\"> </a></td><td>proposal</td><td><div><p><strong>Definition:</strong> A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.</p>\n</div></td><td/><td>16726</td><td>active</td><td/><td>Proposal</td><td/><td/><td/></tr><tr><td>5</td><td style=\"white-space:nowrap\">��������RMD<a name=\"v3-ActMood-RMD\"> </a></td><td>recommendation</td><td><div><p><strong>Definition:</strong> 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. .</p>\n<p><strong>UsageNotes:</strong> Where there is no clear definition or applicable concept of &quot;professional responsibility&quot;, RMD becomes indistinguishable from PRP. .</p>\n</div></td><td/><td>21571</td><td>active</td><td/><td>Recommendation</td><td/><td/><td>Where there is no clear definition or applicable concept of &quot;professional responsibility&quot;, RMD becomes indistinguishable from PRP. .</td></tr><tr><td>3</td><td style=\"white-space:nowrap\">����PRMS<a name=\"v3-ActMood-PRMS\"> </a></td><td>promise</td><td><div><p><strong>Definition:</strong> 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.</p>\n<p><strong>UsageNotes:</strong> Commitments may be retracted or cancelled.</p>\n</div></td><td/><td>16728</td><td>active</td><td/><td>Promise</td><td/><td/><td>Commitments may be retracted or cancelled.</td></tr><tr><td>4</td><td style=\"white-space:nowrap\">������APT<a name=\"v3-ActMood-APT\"> </a></td><td>appointment</td><td><div><p><strong>Definition:</strong> An act that has been scheduled to be performed at a specific place and time.</p>\n</div></td><td/><td>11626</td><td>active</td><td/><td>Appointment</td><td/><td/><td/></tr><tr><td>1</td><td style=\"white-space:nowrap\">_ActMoodPredicate<a name=\"v3-ActMood-_ActMoodPredicate\"> </a></td><td>ActMoodPredicate</td><td><div><p><strong>Definition:</strong> An act that expresses condition statements for other acts.</p>\n</div></td><td/><td>20936</td><td>active</td><td/><td>Predicate</td><td>true</td><td/><td/></tr><tr style=\"background-color: #ffeeee\"><td>2</td><td style=\"white-space:nowrap\">��CRT<a name=\"v3-ActMood-CRT\"> </a></td><td>criterion</td><td><div><p><em><strong>Deprecation Comment:</strong></em> This concept This codes should no longer be used. Instead, set attribute Act.isCriterionInd to &quot;true&quot; and use the desired mood for your criterion.</p>\n<p><strong>Definition:</strong> A condition that must be true for the source act to be considered.</p>\n</div></td><td>Deprecated</td><td>22042</td><td>deprecated</td><td>2010-07-12</td><td>Criterion</td><td/><td/><td/></tr><tr style=\"background-color: #ffeeee\"><td>3</td><td style=\"white-space:nowrap\">����EVN.CRT<a name=\"v3-ActMood-EVN.46CRT\"> </a></td><td>event criterion</td><td><div><p><em><strong>Deprecation Comment:</strong></em> This concept This codes should no longer be used. Instead, set attribute Act.isCriterionInd to &quot;true&quot; and use the desired mood for your criterion.</p>\n<p><strong>Definition:</strong> A criterion (CRT) that has_match = an event (EVN).</p>\n</div></td><td>Deprecated</td><td>10203</td><td>deprecated</td><td>2010-07-12</td><td>EventCriterion</td><td/><td/><td/></tr><tr style=\"background-color: #ffeeee\"><td>3</td><td style=\"white-space:nowrap\">����GOL.CRT<a name=\"v3-ActMood-GOL.46CRT\"> </a></td><td>goal criterion</td><td><div><p>A criterion expressed over goals (ActMood.GOL).</p>\n</div></td><td/><td>23057</td><td>retired</td><td/><td/><td/><td/><td/></tr><tr style=\"background-color: #ffeeee\"><td>3</td><td style=\"white-space:nowrap\">����INT.CRT<a name=\"v3-ActMood-INT.46CRT\"> </a></td><td>intent criterion</td><td><div><p>A criterion expressed over intents (ActMood.INT).</p>\n</div></td><td/><td>23054</td><td>retired</td><td/><td/><td/><td/><td/></tr><tr style=\"background-color: #ffeeee\"><td>4</td><td style=\"white-space:nowrap\">������PRMS.CRT<a name=\"v3-ActMood-PRMS.46CRT\"> </a></td><td>promise criterion</td><td><div><p>A criterion expressed over promises (ActMood.PRMS).</p>\n</div></td><td/><td>23056</td><td>retired</td><td/><td/><td/><td/><td/></tr><tr style=\"background-color: #ffeeee\"><td>4</td><td style=\"white-space:nowrap\">������RQO.CRT<a name=\"v3-ActMood-RQO.46CRT\"> </a></td><td>request criterion</td><td><div><p>A criterion expressed over requests or orders (ActMood.RQO).</p>\n</div></td><td/><td>23055</td><td>retired</td><td/><td/><td/><td/><td/></tr><tr style=\"background-color: #ffeeee\"><td>3</td><td style=\"white-space:nowrap\">����RSK.CRT<a name=\"v3-ActMood-RSK.46CRT\"> </a></td><td>risk criterion</td><td><div><p>A criterion expressed over risks (ActMood.RSK).</p>\n</div></td><td/><td>23058</td><td>retired</td><td/><td/><td/><td/><td/></tr><tr><td>2</td><td style=\"white-space:nowrap\">��EXPEC<a name=\"v3-ActMood-EXPEC\"> </a></td><td>expectation</td><td><div><p><strong>Definition:</strong> An act that is considered to have some noteworthy likelihood of occurring in the future (has_match = event).</p>\n<p>**Examples:**Prognosis of a condition, Expected date of discharge from hospital, patient will likely need an emergency decompression of the intracranial pressure by morning.</p>\n<p>**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.</p>\n</div></td><td/><td>21574</td><td>active</td><td/><td>Expectation</td><td/><td/><td>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.</td></tr><tr><td>3</td><td style=\"white-space:nowrap\">����GOL<a name=\"v3-ActMood-GOL\"> </a></td><td>Goal</td><td><div><p><strong>Definition:</strong> An expectation that is considered to be desirable to occur in the future</p>\n<p>**Examples:**Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction.</p>\n<p><strong>UsageNotes:</strong> 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. &quot;I will reduce the dose of drug x to 20mg&quot; is an intent. &quot;I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg&quot; is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope.</p>\n</div></td><td/><td>18864</td><td>active</td><td/><td>Goal</td><td/><td/><td>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. &quot;I will reduce the dose of drug x to 20mg&quot; is an intent. &quot;I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg&quot; is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope.</td></tr><tr><td>3</td><td style=\"white-space:nowrap\">����RSK<a name=\"v3-ActMood-RSK\"> </a></td><td>risk</td><td><div><p>**Definition:**An act that may occur in the future and which is regarded as undesirable</p>\n<p>**Examples:**Increased risk of DVT, at risk for sub-acute bacterial endocarditis.</p>\n<p>**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.</p>\n</div></td><td/><td>21575</td><td>active</td><td/><td>Risk</td><td/><td/><td>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.</td></tr><tr><td>2</td><td style=\"white-space:nowrap\">��OPT<a name=\"v3-ActMood-OPT\"> </a></td><td>option</td><td><div><p><strong>Definition:</strong> 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.</p>\n</div></td><td/><td>10204</td><td>active</td><td/><td>Option</td><td/><td/><td/></tr></table></div>"
  },
  "url" : "http://terminology.hl7.org/CodeSystem/v3-ActMood",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.5.1001"
    }
  ],
  "version" : "3.0.0",
  "name" : "ActMood",
  "title" : "ActMood",
  "status" : "active",
  "experimental" : false,
  "date" : "2023-05-30",
  "publisher" : "Health Level Seven International",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://hl7.org"
        },
        {
          "system" : "email",
          "value" : "hq@HL7.org"
        }
      ]
    }
  ],
  "description" : "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" : "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.html",
  "caseSensitive" : true,
  "hierarchyMeaning" : "is-a",
  "content" : "complete",
  "property" : [
    {
      "extension" : [
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry",
          "valueCode" : "antisymmetric"
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity",
          "valueCode" : "transitive"
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity",
          "valueCode" : "irreflexive"
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable",
          "valueBoolean" : true
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind",
          "valueCode" : "Specializes"
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName",
          "valueString" : "Generalizes"
        }
      ],
      "code" : "Specializes",
      "description" : "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" : "Coding"
    },
    {
      "extension" : [
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry",
          "valueCode" : "antisymmetric"
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity",
          "valueCode" : "transitive"
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity",
          "valueCode" : "irreflexive"
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable",
          "valueBoolean" : true
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind",
          "valueCode" : "Generalizes"
        },
        {
          "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName",
          "valueString" : "Specializes"
        }
      ],
      "code" : "Generalizes",
      "description" : "Inverse of Specializes. Only included as a derived relationship.",
      "type" : "Coding"
    },
    {
      "code" : "internalId",
      "uri" : "http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id",
      "description" : "The internal identifier for the concept in the HL7 Access database repository.",
      "type" : "code"
    },
    {
      "code" : "status",
      "uri" : "http://hl7.org/fhir/concept-properties#status",
      "description" : "A property that indicates the status of the concept. One of active, experimental, deprecated, or retired.",
      "type" : "code"
    },
    {
      "code" : "deprecationDate",
      "uri" : "http://hl7.org/fhir/concept-properties#deprecationDate",
      "description" : "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" : "dateTime"
    },
    {
      "code" : "Name:Class",
      "uri" : "http://terminology.hl7.org/CodeSystem/utg-concept-properties#rim-Class",
      "description" : "The formal name for the class clone under this code",
      "type" : "code"
    },
    {
      "code" : "notSelectable",
      "uri" : "http://hl7.org/fhir/concept-properties#notSelectable",
      "description" : "Indicates that the code is abstract - only intended to be used as a selector for other concepts",
      "type" : "boolean"
    },
    {
      "code" : "synonymCode",
      "uri" : "http://hl7.org/fhir/concept-properties#synonym",
      "description" : "An additional concept code that was also attributed to a concept",
      "type" : "code"
    },
    {
      "code" : "HL7usageNotes",
      "uri" : "http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes",
      "description" : "HL7 Concept Usage Notes",
      "type" : "string"
    }
  ],
  "concept" : [
    {
      "code" : "_ActMoodCompletionTrack",
      "display" : "ActMoodCompletionTrack",
      "definition" : "These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.",
      "property" : [
        {
          "code" : "notSelectable",
          "valueBoolean" : true
        },
        {
          "code" : "status",
          "valueCode" : "active"
        },
        {
          "code" : "internalId",
          "valueCode" : "20935"
        },
        {
          "code" : "Name:Class",
          "valueCode" : "Process"
        }
      ],
      "concept" : [
        {
          "code" : "_ActMoodPotential",
          "display" : "potential",
          "definition" : "**Definition:** A possible act.",
          "property" : [
            {
              "code" : "notSelectable",
              "valueBoolean" : true
            },
            {
              "code" : "status",
              "valueCode" : "active"
            },
            {
              "code" : "internalId",
              "valueCode" : "23087"
            },
            {
              "code" : "Name:Class",
              "valueCode" : "Potential"
            }
          ],
          "concept" : [
            {
              "code" : "DEF",
              "display" : "definition",
              "definition" : "**Definition:** A definition of a kind of act that can occur .\r\n\r\n**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" : "status",
                  "valueCode" : "active"
                },
                {
                  "code" : "internalId",
                  "valueCode" : "10198"
                },
                {
                  "code" : "Name:Class",
                  "valueCode" : "Definition"
                }
              ]
            },
            {
              "code" : "PERM",
              "display" : "permission",
              "definition" : "**Definition:** A kind of act that defines a permission that has been granted.",
              "property" : [
                {
                  "code" : "status",
                  "valueCode" : "active"
                },
                {
                  "code" : "internalId",
                  "valueCode" : "21381"
                },
                {
                  "code" : "Name:Class",
                  "valueCode" : "Permission"
                }
              ]
            },
            {
              "code" : "SLOT",
              "display" : "resource slot",
              "definition" : "**Definition:** A kind of act that may occur during the specified time period.",
              "property" : [
                {
                  "code" : "status",
                  "valueCode" : "active"
                },
                {
                  "code" : "internalId",
                  "valueCode" : "19168"
                },
                {
                  "code" : "Name:Class",
                  "valueCode" : "ResourceSlot"
                }
              ]
            }
          ]
        },
        {
          "code" : "EVN",
          "display" : "event (occurrence)",
          "definition" : "**Definition:** An act that actually happens (may be an ongoing act or a documentation of a past act).",
          "property" : [
            {
              "code" : "status",
              "valueCode" : "active"
            },
            {
              "code" : "internalId",
              "valueCode" : "10201"
            },
            {
              "code" : "Name:Class",
              "valueCode" : "Event"
            }
          ]
        },
        {
          "code" : "INT",
          "display" : "intent",
          "definition" : "**Definition:** An intention or plan for an act.\r\n\r\n**>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" : "status",
              "valueCode" : "active"
            },
            {
              "code" : "internalId",
              "valueCode" : "10199"
            },
            {
              "code" : "Name:Class",
              "valueCode" : "Intent"
            }
          ],
          "concept" : [
            {
              "code" : "_ActMoodDesire",
              "display" : "desire",
              "definition" : "**Definition:** A desire to have an act occur.",
              "property" : [
                {
                  "code" : "notSelectable",
                  "valueBoolean" : true
                },
                {
                  "code" : "status",
                  "valueCode" : "active"
                },
                {
                  "code" : "internalId",
                  "valueCode" : "23088"
                },
                {
                  "code" : "Name:Class",
                  "valueCode" : "Desire"
                }
              ],
              "concept" : [
                {
                  "code" : "_ActMoodActRequest",
                  "display" : "act request",
                  "definition" : "**Definition:** A request (or order) for an act that is part of a defined request/fulfillment cycle.\r\n\r\n**UsageNotes:** Use of an HL7 defined request/fulfillment framework is not required to use this mood code.",
                  "property" : [
                    {
                      "code" : "notSelectable",
                      "valueBoolean" : true
                    },
                    {
                      "code" : "status",
                      "valueCode" : "active"
                    },
                    {
                      "code" : "HL7usageNotes",
                      "valueString" : "Use of an HL7 defined request/fulfillment framework is not required to use this mood code."
                    },
                    {
                      "code" : "internalId",
                      "valueCode" : "23089"
                    },
                    {
                      "code" : "Name:Class",
                      "valueCode" : "ActRequest"
                    }
                  ],
                  "concept" : [
                    {
                      "code" : "ARQ",
                      "display" : "appointment request",
                      "definition" : "**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)*.",
                      "property" : [
                        {
                          "code" : "status",
                          "valueCode" : "active"
                        },
                        {
                          "code" : "internalId",
                          "valueCode" : "11625"
                        },
                        {
                          "code" : "Name:Class",
                          "valueCode" : "AppointmentRequest"
                        }
                      ]
                    },
                    {
                      "code" : "PERMRQ",
                      "display" : "permission request",
                      "definition" : "**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.",
                      "property" : [
                        {
                          "code" : "status",
                          "valueCode" : "active"
                        },
                        {
                          "code" : "internalId",
                          "valueCode" : "21382"
                        },
                        {
                          "code" : "Name:Class",
                          "valueCode" : "PermissionRequest"
                        }
                      ]
                    },
                    {
                      "code" : "RQO",
                      "display" : "request",
                      "definition" : "**Definition:** A request act that is specialized for an event request/fulfillment cycle.\r\n\r\n**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.\r\n\r\n**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.\"\r\n\r\nThus, 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.\r\n\r\nThe 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.",
                      "property" : [
                        {
                          "code" : "status",
                          "valueCode" : "active"
                        },
                        {
                          "code" : "synonymCode",
                          "valueCode" : "ORD"
                        },
                        {
                          "code" : "HL7usageNotes",
                          "valueString" : "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" : "internalId",
                          "valueCode" : "19973"
                        },
                        {
                          "code" : "Name:Class",
                          "valueCode" : "Request"
                        }
                      ]
                    },
                    {
                      "code" : "ORD",
                      "display" : "request",
                      "definition" : "**Definition:** A request act that is specialized for an event request/fulfillment cycle.\r\n\r\n**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.\r\n\r\n**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.\"\r\n\r\nThus, 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.\r\n\r\nThe 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.",
                      "property" : [
                        {
                          "code" : "status",
                          "valueCode" : "retired"
                        },
                        {
                          "code" : "synonymCode",
                          "valueCode" : "RQO"
                        },
                        {
                          "code" : "HL7usageNotes",
                          "valueString" : "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" : "internalId",
                          "valueCode" : "19973"
                        },
                        {
                          "code" : "Name:Class",
                          "valueCode" : "Request"
                        }
                      ]
                    }
                  ]
                },
                {
                  "code" : "PRP",
                  "display" : "proposal",
                  "definition" : "**Definition:** A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.",
                  "property" : [
                    {
                      "code" : "status",
                      "valueCode" : "active"
                    },
                    {
                      "code" : "internalId",
                      "valueCode" : "16726"
                    },
                    {
                      "code" : "Name:Class",
                      "valueCode" : "Proposal"
                    }
                  ],
                  "concept" : [
                    {
                      "code" : "RMD",
                      "display" : "recommendation",
                      "definition" : "**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. .\r\n\r\n**UsageNotes:** Where there is no clear definition or applicable concept of \"professional responsibility\", RMD becomes indistinguishable from PRP. .",
                      "property" : [
                        {
                          "code" : "status",
                          "valueCode" : "active"
                        },
                        {
                          "code" : "HL7usageNotes",
                          "valueString" : "Where there is no clear definition or applicable concept of \"professional responsibility\", RMD becomes indistinguishable from PRP. ."
                        },
                        {
                          "code" : "internalId",
                          "valueCode" : "21571"
                        },
                        {
                          "code" : "Name:Class",
                          "valueCode" : "Recommendation"
                        }
                      ]
                    }
                  ]
                }
              ]
            },
            {
              "code" : "PRMS",
              "display" : "promise",
              "definition" : "**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.\r\n\r\n**UsageNotes:** Commitments may be retracted or cancelled.",
              "property" : [
                {
                  "code" : "status",
                  "valueCode" : "active"
                },
                {
                  "code" : "HL7usageNotes",
                  "valueString" : "Commitments may be retracted or cancelled."
                },
                {
                  "code" : "internalId",
                  "valueCode" : "16728"
                },
                {
                  "code" : "Name:Class",
                  "valueCode" : "Promise"
                }
              ],
              "concept" : [
                {
                  "code" : "APT",
                  "display" : "appointment",
                  "definition" : "**Definition:** An act that has been scheduled to be performed at a specific place and time.",
                  "property" : [
                    {
                      "code" : "status",
                      "valueCode" : "active"
                    },
                    {
                      "code" : "internalId",
                      "valueCode" : "11626"
                    },
                    {
                      "code" : "Name:Class",
                      "valueCode" : "Appointment"
                    }
                  ]
                }
              ]
            }
          ]
        }
      ]
    },
    {
      "code" : "_ActMoodPredicate",
      "display" : "ActMoodPredicate",
      "definition" : "**Definition:** An act that expresses condition statements for other acts.",
      "property" : [
        {
          "code" : "notSelectable",
          "valueBoolean" : true
        },
        {
          "code" : "status",
          "valueCode" : "active"
        },
        {
          "code" : "internalId",
          "valueCode" : "20936"
        },
        {
          "code" : "Name:Class",
          "valueCode" : "Predicate"
        }
      ],
      "concept" : [
        {
          "code" : "CRT",
          "display" : "criterion",
          "definition" : "***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.\r\n\r\n**Definition:** A condition that must be true for the source act to be considered.",
          "property" : [
            {
              "code" : "status",
              "valueCode" : "deprecated"
            },
            {
              "code" : "deprecationDate",
              "valueDateTime" : "2010-07-12"
            },
            {
              "code" : "internalId",
              "valueCode" : "22042"
            },
            {
              "code" : "Name:Class",
              "valueCode" : "Criterion"
            }
          ],
          "concept" : [
            {
              "code" : "EVN.CRT",
              "display" : "event criterion",
              "definition" : "***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.\r\n\r\n**Definition:** A criterion (CRT) that has\\_match = an event (EVN).",
              "property" : [
                {
                  "code" : "status",
                  "valueCode" : "deprecated"
                },
                {
                  "code" : "deprecationDate",
                  "valueDateTime" : "2010-07-12"
                },
                {
                  "code" : "internalId",
                  "valueCode" : "10203"
                },
                {
                  "code" : "Name:Class",
                  "valueCode" : "EventCriterion"
                }
              ]
            },
            {
              "code" : "GOL.CRT",
              "display" : "goal criterion",
              "definition" : "A criterion expressed over goals (ActMood.GOL).",
              "property" : [
                {
                  "code" : "status",
                  "valueCode" : "retired"
                },
                {
                  "code" : "internalId",
                  "valueCode" : "23057"
                }
              ]
            },
            {
              "code" : "INT.CRT",
              "display" : "intent criterion",
              "definition" : "A criterion expressed over intents (ActMood.INT).",
              "property" : [
                {
                  "code" : "status",
                  "valueCode" : "retired"
                },
                {
                  "code" : "internalId",
                  "valueCode" : "23054"
                }
              ],
              "concept" : [
                {
                  "code" : "PRMS.CRT",
                  "display" : "promise criterion",
                  "definition" : "A criterion expressed over promises (ActMood.PRMS).",
                  "property" : [
                    {
                      "code" : "status",
                      "valueCode" : "retired"
                    },
                    {
                      "code" : "internalId",
                      "valueCode" : "23056"
                    }
                  ]
                },
                {
                  "code" : "RQO.CRT",
                  "display" : "request criterion",
                  "definition" : "A criterion expressed over requests or orders (ActMood.RQO).",
                  "property" : [
                    {
                      "code" : "status",
                      "valueCode" : "retired"
                    },
                    {
                      "code" : "internalId",
                      "valueCode" : "23055"
                    }
                  ]
                }
              ]
            },
            {
              "code" : "RSK.CRT",
              "display" : "risk criterion",
              "definition" : "A criterion expressed over risks (ActMood.RSK).",
              "property" : [
                {
                  "code" : "status",
                  "valueCode" : "retired"
                },
                {
                  "code" : "internalId",
                  "valueCode" : "23058"
                }
              ]
            }
          ]
        },
        {
          "code" : "EXPEC",
          "display" : "expectation",
          "definition" : "**Definition:** An act that is considered to have some noteworthy likelihood of occurring in the future (has\\_match = event).\r\n\r\n**Examples:**Prognosis of a condition, Expected date of discharge from hospital, patient will likely need an emergency decompression of the intracranial pressure by morning.\r\n\r\n**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" : "status",
              "valueCode" : "active"
            },
            {
              "code" : "HL7usageNotes",
              "valueString" : "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" : "internalId",
              "valueCode" : "21574"
            },
            {
              "code" : "Name:Class",
              "valueCode" : "Expectation"
            }
          ],
          "concept" : [
            {
              "code" : "GOL",
              "display" : "Goal",
              "definition" : "**Definition:** An expectation that is considered to be desirable to occur in the future\r\n\r\n**Examples:**Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction.\r\n\r\n**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" : "status",
                  "valueCode" : "active"
                },
                {
                  "code" : "HL7usageNotes",
                  "valueString" : "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" : "internalId",
                  "valueCode" : "18864"
                },
                {
                  "code" : "Name:Class",
                  "valueCode" : "Goal"
                }
              ]
            },
            {
              "code" : "RSK",
              "display" : "risk",
              "definition" : "**Definition:**An act that may occur in the future and which is regarded as undesirable\r\n\r\n**Examples:**Increased risk of DVT, at risk for sub-acute bacterial endocarditis.\r\n\r\n**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.",
              "property" : [
                {
                  "code" : "status",
                  "valueCode" : "active"
                },
                {
                  "code" : "HL7usageNotes",
                  "valueString" : "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" : "internalId",
                  "valueCode" : "21575"
                },
                {
                  "code" : "Name:Class",
                  "valueCode" : "Risk"
                }
              ]
            }
          ]
        },
        {
          "code" : "OPT",
          "display" : "option",
          "definition" : "**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" : "status",
              "valueCode" : "active"
            },
            {
              "code" : "internalId",
              "valueCode" : "10204"
            },
            {
              "code" : "Name:Class",
              "valueCode" : "Option"
            }
          ]
        }
      ]
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.