FHIR Release 3 (STU) 4

This page is part of the FHIR Specification (v3.0.2: (v4.0.1: R4 - Mixed Normative and STU 3). ) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R4 R3

4.3.1.815 4.4.1.485 Value Set http://hl7.org/fhir/ValueSet/adverse-event-causality-assess

Regulated Clinical Research Information Management Patient Care Work Group   Maturity Level : 1 Informative Draft Use Context : Any

This is a value set defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/ValueSet/adverse-event-causality-assess
Version: 4.0.1
Name: AdverseEventCausalityAssessment
Title: AdverseEventCausalityAssessment
Definition: TODO

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

Committee: Regulated Clinical Research Information Management Patient Care Work Group
OID: 2.16.840.1.113883.4.642.3.815 2.16.840.1.113883.4.642.3.840 (for OID based terminology systems)
Source Resource XML / JSON

This value set is used in the following places:

4.3.1.815.1 4.4.1.485.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.1.815.2 4.4.1.485.2 Expansion

This expansion generated 19 Apr 2017 01 Nov 2019

This value set contains 2 6 concepts

Expansion based on http://hl7.org/fhir/adverse-event-causality-assess http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess version 3.0.2 4.0.1

All codes from system http://hl7.org/fhir/adverse-event-causality-assess http://terminology.hl7.org/CodeSystem/adverse-event-causality-assess

Code Display Definition
Certain 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.
assess1 Probably-Likely assess1 placeholder 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 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.
assess2 Unlikely assess2 placeholder 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 Conditional/Classified i) Event or laboratory test abnormality; ii) More data for proper assessment needed; or iii) Additional data under examination.
Unassessable-Unclassifiable 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.

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

Level Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes For value sets, levels are under other codes, and imply that the mostly used to organize codes for user convenience, but may follow code they are under also applies system hierarchy - see Code System for further information
Source 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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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