MyHealth@Eu Laboratory Report
0.0.1 - qa-preview 150

This page is part of the MyHealth@Eu Laboratory Report (v0.0.1: QA Preview) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

ValueSet: eHDSI Observation Interpretation with exceptions

Official URL: http://fhir.ehdsi.eu/laboratory/ValueSet/eHDSIObservationInterpretationWithExceptions Version: 0.0.1
Standards status: Draft Maturity Level: 1 Computable Name: EHDSIObservationInterpretationWithExceptions

This Value Set is used for a rough qualitative interpretation of the Laboratory Observation Results. It also includes exceptional values.

References

Logical Definition (CLD)

This value set includes codes based on the following rules:

 

Expansion

This value set contains 42 concepts.

CodeSystemDisplayDefinition
  OTHhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorother

**Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system).

Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc.

With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.

  UNChttp://terminology.hl7.org/CodeSystem/v3-NullFlavorun-encoded

Description: The actual value has not yet been encoded within the approved value domain.

Example: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system. Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM.

Usage Notes: If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted.

Data type properties such as original text and translations may be present when this null flavor is included.

  UNKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorunknown

**Description:**A proper value is applicable, but not known.

Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:

  1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown')
  2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)
  <http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationOff scale low

The result is below the minimum detection limit (the test procedure or equipment is the limiting factor).

Synonyms: Below analytical limit, low off scale.

  >http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationOff scale high

The result is above the maximum quantifiable limit (the test procedure or equipment is the limiting factor).

Synonyms: Above analytical limit, high off scale.

  Ahttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationAbnormal

The result or observation value is outside the reference range or expected norm (as defined for the respective test procedure).

[Note: Typically applies to non-numeric results.]

  AAhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationCritical abnormal

The result or observation value is outside a reference range or expected norm at a level at which immediate action should be considered for patient safety (as defined for the respective test procedure).

[Note: Typically applies to non-numeric results. Analogous to critical/panic limits for numeric results.]

  Bhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationBetter

The current result or observation value has improved compared to the previous result or observation value (the change is significant as defined in the respective test procedure).

[Note: This can be applied to quantitative or qualitative observations.]

  CARhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationCarrier

The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder.

  Dhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationSignificant change down

The current result has decreased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure).

  DEThttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationDetected

The measurement of the specified component / analyte, organism or clinical sign above the limit of detection of the performed test or procedure.

  Ehttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationEquivocal

The test or procedure was successfully performed, but the results are borderline and can neither be declared positive / negative nor detected / not detected according to the current established criteria.

  EXhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationoutside threshold

The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.

Example: A positive result on a Hepatitis screening test.

Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects. These concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes. Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held.

  EXPhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationExpected

This result has been evaluated in light of known contraindicators. Once those contraindicators have been taken into account the result is determined to be "Expected" (e.g., presence of drugs in a patient that is taking prescription medication for pain management).

  Hhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationHigh

The result for a quantitative observation is above the upper limit of the reference range (as defined for the respective test procedure).

Synonym: Above high normal

  HHhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationCritical high

The result for a quantitative observation is above a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure).

Synonym: Above upper panic limits.

  HUhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationSignificantly high

A test result that is significantly higher than the reference (normal) or therapeutic interval, but has not reached the critically high value and might need special attention, as defined by the laboratory or the clinician.

  HXhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationabove high threshold

The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.

Example: A positive result on a Hepatitis screening test.

Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects. These concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes. Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held.

  Ihttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationIntermediate

Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with uncertain therapeutic effect. Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm) Projects: ISO 20776-1, ISO 20776-2

[Note 1: Bacterial strains are categorized as intermediate by applying the appropriate breakpoints in a defined phenotypic test system.]

[Note 2: This class of susceptibility implies that an infection due to the isolate can be appropriately treated in body sites where the drugs are physiologically concentrated or when a high dosage of drug can be used.]

[Note 3: This class also indicates a "buffer zone," to prevent small, uncontrolled, technical factors from causing major discrepancies in interpretations.]

[Note 4: These breakpoints can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).]

  IEhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationInsufficient evidence

There is insufficient evidence that the species in question is a good target for therapy with the drug. A categorical interpretation is not possible.

[Note: A MIC with "IE" and/or a comment may be reported (without an accompanying S, I or R-categorization).]

  INDhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationIndeterminate

The specified component / analyte, organism or clinical sign could neither be declared positive / negative nor detected / not detected by the performed test or procedure.

Usage Note: For example, if the specimen was degraded, poorly processed, or was missing the required anatomic structures, then "indeterminate" (i.e. "cannot be determined") is the appropriate response, not "equivocal".

  Lhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationLow

The result for a quantitative observation is below the lower limit of the reference range (as defined for the respective test procedure).

Synonym: Below low normal

  LLhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationCritical low

The result for a quantitative observation is below a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure).

Synonym: Below lower panic limits.

  LUhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationSignificantly low

A test result that is significantly lower than the reference (normal) or therapeutic interval, but has not reached the critically low value and might need special attention, as defined by the laboratory or the clinician.

  LXhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationbelow low threshold

The numeric observation/test result is interpreted as being below the low threshold value for a particular protocol within which the result is being reported.

Example: A Total White Blood Cell Count falling below a protocol-defined threshold value of 3000/mm^3

Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L). The only apparent significant difference is their reference to use in protocols for exclusion of study subjects. These concepts/codes were proposed by RCRIM for use in the CTLaboratory message. They were submitted and approved in the November 2005 Harmonization cycle in proposal "030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455". However, this proposal was not fully implemented in the vocabulary. The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes. Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response. It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held.

  Nhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationNormal

The result or observation value is within the reference range or expected norm (as defined for the respective test procedure).

[Note: Applies to numeric or non-numeric results.]

  NCLhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationNo CLSI defined breakpoint

Use when not enough clinical trial data published by the Clinical and Laboratory Standards Institutes (CLSI) is available to establish the breakpoints for susceptible / intermediate and resistant.

  NDhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationNot detected

The presence of the specified component / analyte, organism or clinical sign could not be determined within the limit of detection of the performed test or procedure.

  NEGhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationNegative

An absence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure.

[Note: Negative does not necessarily imply the complete absence of the specified item.]

  NRhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationNon-reactive

An absence finding used to indicate that the specified component / analyte did not react measurably with the reagent.

  NShttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationNon-susceptible

A category used for isolates for which only a susceptible interpretive criterion has been designated because of the absence or rare occurrence of resistant strains. Isolates that have MICs above or zone diameters below the value indicated for the susceptible breakpoint should be reported as non-susceptible.

NOTE 1: An isolate that is interpreted as non-susceptible does not necessarily mean that the isolate has a resistance mechanism. It is possible that isolates with MICs above the susceptible breakpoint that lack resistance mechanisms may be encountered within the wild-type distribution subsequent to the time the susceptible-only breakpoint is set.

NOTE 2: For strains yielding results in the "nonsusceptible" category, organism identification and antimicrobial susceptibility test results should be confirmed.

Synonym: decreased susceptibility.

  POShttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationPositive

A presence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure.

  Rhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationResistant

Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic failure. Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm) Projects: ISO 20776-1, ISO 20776-2

[Note 1: Bacterial strains are categorized as resistant by applying the appropriate breakpoints in a defined phenotypic test system.]

[Note 2: This breakpoint can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).]

  RRhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationReactive

A presence finding used to indicate that the specified component / analyte reacted with the reagent above the reliably measurable limit of the performed test.

  Shttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationSusceptible

Bacterial strain inhibited by in vitro concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic success. Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm) Synonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2

[Note 1: Bacterial strains are categorized as susceptible by applying the appropriate breakpoints in a defined phenotypic system.]

[Note 2: This breakpoint can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).]

  Uhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationSignificant change up

The current result has increased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure).

  UNEhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationUnexpected

This result has been evaluated in light of known contraindicators. Once those contraindicators have been taken into account the result is determined to be "Unexpected" (e.g., presence of non-prescribed drugs in a patient that is taking prescription medication for pain management).

  Whttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationWorse

The current result or observation value has degraded compared to the previous result or observation value (the change is significant as defined in the respective test procedure).

[Note: This can be applied to quantitative or qualitative observations.]

  WRhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationWeakly reactive

A weighted presence finding used to indicate that the specified component / analyte reacted with the reagent, but below the reliably measurable limit of the performed test.

  SYN-Rhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationSynergy - resistant

A category for isolates where the bacteria (e.g. enterococci) are not susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent). This is predictive that this combination therapy will not be effective.

Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside.

Open Issue: The print name of the code is very general and the description is very specific to a pair of classes of agents, which may lead to confusion of these concepts in the future should other synergies be found.

  SDDhttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationSusceptible-dose dependent

A category that includes isolates with antimicrobial agent minimum inhibitory concentrations (MICs) that approach usually attainable blood and tissue levels and for which response rates may be lower than for susceptible isolates.

Reference: CLSI document M44-A2 2009 "Method for antifungal disk diffusion susceptibility testing of yeasts; approved guideline - second edition" - page 2.

  SYN-Shttp://terminology.hl7.org/CodeSystem/v3-ObservationInterpretationSynergy - susceptible

A category for isolates where the bacteria (e.g. enterococci) are susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent). This is predictive that this combination therapy will be effective.

Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside.

Open Issue: The print name of the code is very general and the description is very specific to a pair of classes of agents, which may lead to confusion of these concepts in the future should other synergies be found.


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