HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ActClassDetectedIssue - XML Representation

(back to description)

Raw xml

Source view


<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-ActClassDetectedIssue"/>
  <language value="en"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><h2>ActClassDetectedIssue</h2><div><p>An observation identifying a potential adverse outcome as a result of an Act or combination of Acts.</p>
<p><em>Examples:</em> Detection of a drug-drug interaction; Identification of a late-submission for an invoice; Requesting discharge for a patient who does not meet hospital-defined discharge criteria.</p>
<p><em>Discussion:</em> This class is commonly used for identifying 'business rule' or 'process' problems that may result in a refusal to carry out a particular request. In some circumstances it may be possible to 'bypass' a problem by modifying the request to acknowledge the issue and/or by providing some form of mitigation.</p>
<p><em>Constraints:</em> the Act or Acts that may cause the the adverse outcome are the target of a subject ActRelationship. The subbtypes of this concept indicate the type of problem being detected (e.g. drug-drug interaction) while the Observation.value is used to repesent a specific problem code (e.g. specific drug-drug interaction id).</p>
</div><ul><li>Include codes from <a href="CodeSystem-v3-ActClass.html"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a> where concept  is-a  <a href="CodeSystem-v3-ActClass.html#v3-ActClass-ALRT">ALRT</a></li></ul></div>
  </text>
  <url value="http://terminology.hl7.org/ValueSet/v3-ActClassDetectedIssue"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.1.11.20199"/>
  </identifier>
  <version value="2.0.0"/>
  <name value="ActClassDetectedIssue"/>
  <title value="ActClassDetectedIssue"/>
  <status value="active"/>
  <date value="2014-03-26T00:00:00-04:00"/>
  <description
               value="An observation identifying a potential adverse outcome as a result of an Act or combination of Acts.

*Examples:* Detection of a drug-drug interaction; Identification of a late-submission for an invoice; Requesting discharge for a patient who does not meet hospital-defined discharge criteria.

*Discussion:* This class is commonly used for identifying &#39;business rule&#39; or &#39;process&#39; problems that may result in a refusal to carry out a particular request. In some circumstances it may be possible to &#39;bypass&#39; a problem by modifying the request to acknowledge the issue and/or by providing some form of mitigation.

*Constraints:* the Act or Acts that may cause the the adverse outcome are the target of a subject ActRelationship. The subbtypes of this concept indicate the type of problem being detected (e.g. drug-drug interaction) while the Observation.value is used to repesent a specific problem code (e.g. specific drug-drug interaction id)."/>
  <immutable value="true"/>
  <compose>
    <include>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActClass"/>
      <filter>
        <property value="concept"/>
        <op value="is-a"/>
        <value value="ALRT"/>
      </filter>
    </include>
  </compose>
</ValueSet>