ActClassDetectedIssue - HL7 Terminology (THO) v7.1.0

HL7 Terminology (THO)
7.1.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 7.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: ActClassDetectedIssue

Official URL: http://terminology.hl7.org/ValueSet/v3-ActClassDetectedIssue	Version: 3.0.0	Highlight text changes?
	Responsible: Health Level Seven International	Computable Name: ActClassDetectedIssue
Other Identifiers: OID:2.16.840.1.113883.1.11.20199
Copyright/Legal: 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

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

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

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Language: en

Include codes fromhttp://terminology.hl7.org/CodeSystem/v3-ActClass version 📦5.0.0 where concept is-a ALRT

Expansion

Expansion performed internally based on codesystem ActClass v5.0.0 (CodeSystem)

This value set contains 1 concepts

System	Code	Display (en)	Definition	JSON	XML
`http://terminology.hl7.org/CodeSystem/v3-ActClass`	ALRT	detected issue	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 '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. 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).