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

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

ValueSet: ActDetectedIssueManagementCode

Official URL: http://terminology.hl7.org/ValueSet/v3-ActDetectedIssueManagementCode Version: 2.0.0
Active as of 2014-03-26 Computable Name: ActDetectedIssueManagementCode
Other Identifiers: : urn:oid:2.16.840.1.113883.1.11.16695

Codes dealing with the management of Detected Issue observations

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)

This value set includes codes based on the following rules:

This value set excludes codes based on the following rules:

 

Expansion

This value set contains 24 concepts

Expansion based on ActCode v6.1.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v3-ActCode

CodeDisplayDefinition
  _ActAdministrativeDetectedIssueManagementCodeActAdministrativeDetectedIssueManagementCodeCodes dealing with the management of Detected Issue observations for the administrative and patient administrative acts domains.
  _AuthorizationIssueManagementCodeAuthorization Issue Management Code
  EMAUTHemergency authorization overrideUsed to temporarily override normal authorization rules to gain access to data in a case of emergency. Use of this override code will typically be monitored, and a procedure to verify its proper use may be triggered when used.
  21authorization confirmed**Description:** Indicates that the permissions have been externally verified and the request should be processed.
  1Therapy AppropriateConfirmed drug therapy appropriate
  19Consulted SupplierConsulted other supplier/pharmacy, therapy confirmed
  2Assessed PatientAssessed patient, therapy is appropriate
  22appropriate indication or diagnosis**Description:** The patient has the appropriate indication or diagnosis for the action to be taken.
  23prior therapy documented**Description:** It has been confirmed that the appropriate pre-requisite therapy has been tried.
  3Patient ExplanationPatient gave adequate explanation
  4Consulted Other SourceConsulted other supply source, therapy still appropriate
  5Consulted PrescriberConsulted prescriber, therapy confirmed
  6Prescriber Declined ChangeConsulted prescriber and recommended change, prescriber declined
  7Interacting Therapy No Longer Active/PlannedConcurrent therapy triggering alert is no longer on-going or planned
  14Supply AppropriateConfirmed supply action appropriate
  15ReplacementPatient's existing supply was lost/wasted
  16Vacation SupplySupply date is due to patient vacation
  17Weekend SupplySupply date is intended to carry patient over weekend
  18Leave of AbsenceSupply is intended for use during a leave of absence from an institution.
  20additional quantity on separate dispense**Description:** Supply is different than expected as an additional quantity has been supplied in a separate dispense.
  8Other Action TakenOrder is performed as issued, but other action taken to mitigate potential adverse effects
  10Provided Patient EducationProvided education or training to the patient on appropriate therapy use
  11Added Concurrent TherapyInstituted an additional therapy to mitigate potential negative effects
  12Temporarily Suspended Concurrent TherapySuspended existing therapy that triggered interaction for the duration of this therapy
  13Stopped Concurrent TherapyAborted existing therapy that triggered interaction.
  9Instituted Ongoing Monitoring ProgramArranged to monitor patient for adverse effects
  _ActFinancialDetectedIssueManagementCodeActFinancialDetectedIssueManagementCodeCodes dealing with the management of Detected Issue observations for the financial acts domain.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code

History

DateActionCustodianAuthorComment
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.