loading...| Preferred Name |
ActReason |
|
| Synonyms |
|
|
| Definitions |
<p>A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act.</p><i>Examples:</i>Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law". <p>A code specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably representable as an ActRelationship of type "has reason" linking to another Act.</p><i>Examples:</i>Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".<p>Discussion</p><p>Most reasons for acts can be clearly expressed by linking the new Act to another prior Act using an ActRelationship of type "has reason". This simply states that the prior Act is a reason for the new Act (see ActRelationship.) The prior act can then be a specific existing act or a textual explanation. This works for most cases, and the more specific the reason data is, the more should this reason ActRelationship be used instead of the reasonCode.</p><p>The reasonCode remains as a place for common reasons that are not related to a prior Act or any other condition expressed in Acts. Indicators that something was required by law or was on the request of a patient etc. may qualify. However, if that piece of legislation, regulation, or the contract or the patient request can be represented as an Act (and they usually can), the reasonCode should not be used.</p> |
|
| ID |
http://purl.bioontology.org/ontology/HL7/C1553844 |
|
| cui |
C1553844 |
|
| definition |
A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act. Examples:Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".A code specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably representable as an ActRelationship of type "has reason" linking to another Act. Examples:Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".Discussion Most reasons for acts can be clearly expressed by linking the new Act to another prior Act using an ActRelationship of type "has reason". This simply states that the prior Act is a reason for the new Act (see ActRelationship.) The prior act can then be a specific existing act or a textual explanation. This works for most cases, and the more specific the reason data is, the more should this reason ActRelationship be used instead of the reasonCode. The reasonCode remains as a place for common reasons that are not related to a prior Act or any other condition expressed in Acts. Indicators that something was required by law or was on the request of a patient etc. may qualify. However, if that piece of legislation, regulation, or the contract or the patient request can be represented as an Act (and they usually can), the reasonCode should not be used. |
|
| Has supported concept property | ||
| Has supported concept relationship | ||
| HL7 code status |
active |
|
| HL7 history item |
UPDATE: Migrated to the UTG maintenance environment and publishing tooling. |
|
| HL7 internal Id |
19925 |
|
| HL7 OID |
2.16.840.1.113883.5.8 |
|
| HL7 release date |
2019-03-20 |
|
| HL7AI |
true |
|
| HL7CC |
true |
|
| HL7MI |
true |
|
| HL7PL |
true |
|
| HL7RG |
Health Level 7 |
|
| HL7SL |
en |
|
| notation |
C1553844 |
|
| prefLabel |
ActReason |
|
| tui |
T170 |
|
| subClassOf |