AdverseEventCausalityAssessment - HL7 Terminology (THO) v6.5.0

HL7 Terminology (THO)
6.5.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 6.5.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: AdverseEventCausalityAssessment

Official URL: http://terminology.hl7.org/ValueSet/adverse-event-causality-assess			Version: 1.0.1
Active as of 2024-04-24	Maturity Level: 1	Responsible: Health Level Seven International	Computable Name: AdverseEventCausalityAssessment
Other Identifiers: OID:2.16.840.1.113883.4.642.3.840
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

Codes for the assessment of whether the entity caused the event.

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)

Last updated: 2024-04-24 00:00:00+0000

Profile: Shareable ValueSet

Include all codes defined in http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess version 📦1.0.1

Expansion

Expansion performed internally based on codesystem AdverseEventCausalityAssessment v1.0.1 (CodeSystem)

This value set contains 6 concepts

Code	System	Display	Definition
certain	http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess	Certain	i) Event or laboratory test abnormality, with plausible time relationship to drug intake; ii) Cannot be explained by disease or other drugs; iii) Response to withdrawal plausible (pharmacologically, pathologically); iv) Event definitive pharmacologically or phenomenologically (i.e. an objective and specific medical disorder or a recognized pharmacological phenomenon); or v) Re-challenge satisfactory, if necessary.
probably-likely	http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess	Probably/Likely	i) Event or laboratory test abnormality, with reasonable time relationship to drug intake; ii) Unlikely to be attributed to disease or other drugs; iii) Response to withdrawal clinically reasonable; or iv) Re-challenge not required.
possible	http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess	Possible	i) Event or laboratory test abnormality, with reasonable time relationship to drug intake; ii) Could also be explained by disease or other drugs; or iii) Information on drug withdrawal may be lacking or unclear.
unlikely	http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess	Unlikely	i) Event or laboratory test abnormality, with a time to drug intake that makes a relationship improbable (but not impossible); or ii) Disease or other drugs provide plausible explanations.
conditional-classified	http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess	Conditional/Classified	i) Event or laboratory test abnormality; ii) More data for proper assessment needed; or iii) Additional data under examination.
unassessable-unclassifiable	http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess	Unassessable/Unclassifiable	i) Report suggesting an adverse reaction; ii) Cannot be judged because information is insufficient or contradictory; or iii) Data cannot be supplemented or verified.

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

Date

Action

Custodian

Author

Comment

2023-11-14

revise