001package org.hl7.fhir.r4.model.codesystems; 002 003/*- 004 * #%L 005 * org.hl7.fhir.r4 006 * %% 007 * Copyright (C) 2014 - 2019 Health Level 7 008 * %% 009 * Licensed under the Apache License, Version 2.0 (the "License"); 010 * you may not use this file except in compliance with the License. 011 * You may obtain a copy of the License at 012 * 013 * http://www.apache.org/licenses/LICENSE-2.0 014 * 015 * Unless required by applicable law or agreed to in writing, software 016 * distributed under the License is distributed on an "AS IS" BASIS, 017 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 018 * See the License for the specific language governing permissions and 019 * limitations under the License. 020 * #L% 021 */ 022 023 024/* 025 Copyright (c) 2011+, HL7, Inc. 026 All rights reserved. 027 028 Redistribution and use in source and binary forms, with or without modification, 029 are permitted provided that the following conditions are met: 030 031 * Redistributions of source code must retain the above copyright notice, this 032 list of conditions and the following disclaimer. 033 * Redistributions in binary form must reproduce the above copyright notice, 034 this list of conditions and the following disclaimer in the documentation 035 and/or other materials provided with the distribution. 036 * Neither the name of HL7 nor the names of its contributors may be used to 037 endorse or promote products derived from this software without specific 038 prior written permission. 039 040 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 041 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 042 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 043 IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 044 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 045 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 046 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, 047 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 048 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 049 POSSIBILITY OF SUCH DAMAGE. 050 051*/ 052 053// Generated on Wed, Jan 30, 2019 16:19-0500 for FHIR v4.0.0 054 055 056import org.hl7.fhir.exceptions.FHIRException; 057 058public enum V3ObservationInterpretation { 059 060 /** 061 * Codes that specify interpretation of genetic analysis, such as "positive", "negative", "carrier", "responsive", etc. 062 */ 063 _GENETICOBSERVATIONINTERPRETATION, 064 /** 065 * 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. 066 */ 067 CAR, 068 /** 069 * 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. 070 071 072 073 Deprecation Comment: 074 This code is currently the same string as the print name for this concept and is inconsistent with the conventions being used for the other codes in the coding system, as it is a full word with initial capitalization, rather than an all upper case mnemonic. The recommendation from OO is to deprecate the code "Carrier" and to add "CAR" as the new active code representation for this concept. 075 */ 076 CARRIER, 077 /** 078 * Interpretations of change of quantity and/or severity. At most one of B or W and one of U or D allowed. 079 */ 080 _OBSERVATIONINTERPRETATIONCHANGE, 081 /** 082 * 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). 083 084 [Note: This can be applied to quantitative or qualitative observations.] 085 */ 086 B, 087 /** 088 * The current result has decreased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure). 089 */ 090 D, 091 /** 092 * The current result has increased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure). 093 */ 094 U, 095 /** 096 * 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). 097 098 [Note: This can be applied to quantitative or qualitative observations.] 099 */ 100 W, 101 /** 102 * Technical exceptions resulting in the inability to provide an interpretation. At most one allowed. Does not imply normality or severity. 103 */ 104 _OBSERVATIONINTERPRETATIONEXCEPTIONS, 105 /** 106 * The result is below the minimum detection limit (the test procedure or equipment is the limiting factor). 107 108 Synonyms: Below analytical limit, low off scale. 109 */ 110 LESS_THAN, 111 /** 112 * The result is above the maximum quantifiable limit (the test procedure or equipment is the limiting factor). 113 114 Synonyms: Above analytical limit, high off scale. 115 */ 116 GREATER_THAN, 117 /** 118 * A valid result cannot be obtained for the specified component / analyte due to the presence of anti-complementary substances in the sample. 119 120 121 122 Deprecation Comment: 123 This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. 124 */ 125 AC, 126 /** 127 * There is insufficient evidence that the species in question is a good target for therapy with the drug. A categorical interpretation is not possible. 128 129 [Note: A MIC with "IE" and/or a comment may be reported (without an accompanying S, I or R-categorization).] 130 */ 131 IE, 132 /** 133 * A result cannot be considered valid for the specified component / analyte or organism due to failure in the quality control testing component. 134 135 136 137 Deprecation Comment: 138 This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. 139 */ 140 QCF, 141 /** 142 * A valid result cannot be obtained for the specified organism or cell line due to the presence of cytotoxic substances in the sample or culture. 143 144 145 146 Deprecation Comment: 147 This code is being deprecated to match the status in V2 Table 0078 "Interpretation Codes. 148 */ 149 TOX, 150 /** 151 * Interpretation of normality or degree of abnormality (including critical or "alert" level). Concepts in this category are mutually exclusive, i.e., at most one is allowed. 152 */ 153 _OBSERVATIONINTERPRETATIONNORMALITY, 154 /** 155 * The result or observation value is outside the reference range or expected norm (as defined for the respective test procedure). 156 157 [Note: Typically applies to non-numeric results.] 158 */ 159 A, 160 /** 161 * 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). 162 163 [Note: Typically applies to non-numeric results. Analogous to critical/panic limits for numeric results.] 164 */ 165 AA, 166 /** 167 * 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). 168 169 Synonym: Above upper panic limits. 170 */ 171 HH, 172 /** 173 * 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). 174 175 Synonym: Below lower panic limits. 176 */ 177 LL, 178 /** 179 * The result for a quantitative observation is above the upper limit of the reference range (as defined for the respective test procedure). 180 181 Synonym: Above high normal 182 */ 183 H, 184 /** 185 * 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.[Note: This level is situated between 'H' and 'HH'.] 186 187 188 Deprecation Comment: The code 'H>' is being deprecated in order to align with the use of the code 'HU' for "Very high" in V2 Table 0078 "Interpretation Codes". 189 190 [Note: The use of code 'H>' is non-preferred, as this code is deprecated and on track to be retired; use code 'HU' instead. 191 */ 192 H_, 193 /** 194 * 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. 195 */ 196 HU, 197 /** 198 * The result for a quantitative observation is below the lower limit of the reference range (as defined for the respective test procedure). 199 200 Synonym: Below low normal 201 */ 202 L, 203 /** 204 * 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.[Note: This level is situated between 'L' and 'LL'.] 205 206 207 Deprecation Comment: The code 'L<' is being deprecated in order to align with the use of the code 'LU' for "Very low" in V2 Table 0078 "Interpretation Codes". 208 209 [Note: The use of code 'L<' is non-preferred, as this code is deprecated and on track to be retired; use code 'LU' instead. 210 */ 211 L_, 212 /** 213 * 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. 214 */ 215 LU, 216 /** 217 * The result or observation value is within the reference range or expected norm (as defined for the respective test procedure). 218 219 [Note: Applies to numeric or non-numeric results.] 220 */ 221 N, 222 /** 223 * Interpretations of anti-microbial susceptibility testing results (microbiology). At most one allowed. 224 */ 225 _OBSERVATIONINTERPRETATIONSUSCEPTIBILITY, 226 /** 227 * 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) 228Projects: ISO 20776-1, ISO 20776-2 229 230 [Note 1: Bacterial strains are categorized as intermediate by applying the appropriate breakpoints in a defined phenotypic test system.] 231 232 [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.] 233 234 [Note 3: This class also indicates a "buffer zone," to prevent small, uncontrolled, technical factors from causing major discrepancies in interpretations.] 235 236 [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).] 237 */ 238 I, 239 /** 240 * 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. 241 242 243 244 Deprecation Comment: 245 This antimicrobial susceptibility test interpretation concept is recommended by OO to be deprecated as it is no longer recommended for use in susceptibility testing by CLSI (reference CLSI document M100-S22; Vol. 32 No.3; CLSI Performance Standards for Antimicrobial Susceptibility Testing; Twenty-Second Informational Supplement. Jan 2012). 246 */ 247 MS, 248 /** 249 * 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. 250 */ 251 NCL, 252 /** 253 * 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. 254 255 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. 256 257 NOTE 2: For strains yielding results in the "nonsusceptible" category, organism identification and antimicrobial susceptibility test results should be confirmed. 258 259 Synonym: decreased susceptibility. 260 */ 261 NS, 262 /** 263 * Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic failure. 264Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm) 265Projects: ISO 20776-1, ISO 20776-2 266 267 [Note 1: Bacterial strains are categorized as resistant by applying the appropriate breakpoints in a defined phenotypic test system.] 268 269 [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).] 270 */ 271 R, 272 /** 273 * 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. 274 275 276 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. 277 278 279 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. 280 */ 281 SYNR, 282 /** 283 * Bacterial strain inhibited by in vitro concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic success. 284Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm) 285Synonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2 286 287 [Note 1: Bacterial strains are categorized as susceptible by applying the appropriate breakpoints in a defined phenotypic system.] 288 289 [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).] 290 */ 291 S, 292 /** 293 * 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. 294 295 Reference: CLSI document M44-A2 2009 "Method for antifungal disk diffusion susceptibility testing of yeasts; approved guideline - second edition" - page 2. 296 */ 297 SDD, 298 /** 299 * 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. 300 301 302 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. 303 304 305 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. 306 */ 307 SYNS, 308 /** 309 * 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. 310 311 312 313 Deprecation Comment: 314 This antimicrobial susceptibility test interpretation concept is recommended by OO to be deprecated as it is no longer recommended for use in susceptibility testing by CLSI (reference CLSI document M100-S22; Vol. 32 No.3; CLSI Performance Standards for Antimicrobial Susceptibility Testing; Twenty-Second Informational Supplement. Jan 2012). 315 */ 316 VS, 317 /** 318 * The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported. 319 320 321 Example: A positive result on a Hepatitis screening test. 322 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. 323These 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. 324Members 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. 325 */ 326 EX, 327 /** 328 * The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported. 329 330 331 Example: A positive result on a Hepatitis screening test. 332 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. 333 */ 334 HX, 335 /** 336 * 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. 337 338 Example: A Total White Blood Cell Count falling below a protocol-defined threshold value of 3000/mm^3 339 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. 340 */ 341 LX, 342 /** 343 * Hold for Medical Review 344 345 346 Usage Note: This code is not intended for use in V3 artifacts. It is included in the code system to maintain alignment with the V2 Table 0078 "Interpretation Codes." 347 */ 348 HM, 349 /** 350 * Interpretations of the presence or absence of a component / analyte or organism in a test or of a sign in a clinical observation. In keeping with laboratory data processing practice, these concepts provide a categorical interpretation of the "meaning" of the quantitative value for the same observation. 351 */ 352 OBSERVATIONINTERPRETATIONDETECTION, 353 /** 354 * The specified component / analyte, organism or clinical sign could neither be declared positive / negative nor detected / not detected by the performed test or procedure. 355 356 357 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". 358 */ 359 IND, 360 /** 361 * 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. 362 */ 363 E, 364 /** 365 * An absence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure. 366 367 [Note: Negative does not necessarily imply the complete absence of the specified item.] 368 */ 369 NEG, 370 /** 371 * 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. 372 */ 373 ND, 374 /** 375 * A presence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure. 376 */ 377 POS, 378 /** 379 * The measurement of the specified component / analyte, organism or clinical sign above the limit of detection of the performed test or procedure. 380 */ 381 DET, 382 /** 383 * Interpretation of the observed result taking into account additional information (contraindicators) about the patient's situation. Concepts in this category are mutually exclusive, i.e., at most one is allowed. 384 */ 385 OBSERVATIONINTERPRETATIONEXPECTATION, 386 /** 387 * 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). 388 */ 389 EXP, 390 /** 391 * 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). 392 */ 393 UNE, 394 /** 395 * Interpretation qualifiers in separate OBX segments 396 397 398 Usage Note: This code is not intended for use in V3 artifacts. It is included in the code system to maintain alignment with the V2 Table 0078 "Interpretation Codes." 399 */ 400 OBX, 401 /** 402 * Interpretations of the presence and level of reactivity of the specified component / analyte with the reagent in the performed laboratory test. 403 */ 404 REACTIVITYOBSERVATIONINTERPRETATION, 405 /** 406 * An absence finding used to indicate that the specified component / analyte did not react measurably with the reagent. 407 */ 408 NR, 409 /** 410 * A presence finding used to indicate that the specified component / analyte reacted with the reagent above the reliably measurable limit of the performed test. 411 */ 412 RR, 413 /** 414 * 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. 415 */ 416 WR, 417 /** 418 * added to help the parsers 419 */ 420 NULL; 421 public static V3ObservationInterpretation fromCode(String codeString) throws FHIRException { 422 if (codeString == null || "".equals(codeString)) 423 return null; 424 if ("_GeneticObservationInterpretation".equals(codeString)) 425 return _GENETICOBSERVATIONINTERPRETATION; 426 if ("CAR".equals(codeString)) 427 return CAR; 428 if ("Carrier".equals(codeString)) 429 return CARRIER; 430 if ("_ObservationInterpretationChange".equals(codeString)) 431 return _OBSERVATIONINTERPRETATIONCHANGE; 432 if ("B".equals(codeString)) 433 return B; 434 if ("D".equals(codeString)) 435 return D; 436 if ("U".equals(codeString)) 437 return U; 438 if ("W".equals(codeString)) 439 return W; 440 if ("_ObservationInterpretationExceptions".equals(codeString)) 441 return _OBSERVATIONINTERPRETATIONEXCEPTIONS; 442 if ("<".equals(codeString)) 443 return LESS_THAN; 444 if (">".equals(codeString)) 445 return GREATER_THAN; 446 if ("AC".equals(codeString)) 447 return AC; 448 if ("IE".equals(codeString)) 449 return IE; 450 if ("QCF".equals(codeString)) 451 return QCF; 452 if ("TOX".equals(codeString)) 453 return TOX; 454 if ("_ObservationInterpretationNormality".equals(codeString)) 455 return _OBSERVATIONINTERPRETATIONNORMALITY; 456 if ("A".equals(codeString)) 457 return A; 458 if ("AA".equals(codeString)) 459 return AA; 460 if ("HH".equals(codeString)) 461 return HH; 462 if ("LL".equals(codeString)) 463 return LL; 464 if ("H".equals(codeString)) 465 return H; 466 if ("H>".equals(codeString)) 467 return H_; 468 if ("HU".equals(codeString)) 469 return HU; 470 if ("L".equals(codeString)) 471 return L; 472 if ("L<".equals(codeString)) 473 return L_; 474 if ("LU".equals(codeString)) 475 return LU; 476 if ("N".equals(codeString)) 477 return N; 478 if ("_ObservationInterpretationSusceptibility".equals(codeString)) 479 return _OBSERVATIONINTERPRETATIONSUSCEPTIBILITY; 480 if ("I".equals(codeString)) 481 return I; 482 if ("MS".equals(codeString)) 483 return MS; 484 if ("NCL".equals(codeString)) 485 return NCL; 486 if ("NS".equals(codeString)) 487 return NS; 488 if ("R".equals(codeString)) 489 return R; 490 if ("SYN-R".equals(codeString)) 491 return SYNR; 492 if ("S".equals(codeString)) 493 return S; 494 if ("SDD".equals(codeString)) 495 return SDD; 496 if ("SYN-S".equals(codeString)) 497 return SYNS; 498 if ("VS".equals(codeString)) 499 return VS; 500 if ("EX".equals(codeString)) 501 return EX; 502 if ("HX".equals(codeString)) 503 return HX; 504 if ("LX".equals(codeString)) 505 return LX; 506 if ("HM".equals(codeString)) 507 return HM; 508 if ("ObservationInterpretationDetection".equals(codeString)) 509 return OBSERVATIONINTERPRETATIONDETECTION; 510 if ("IND".equals(codeString)) 511 return IND; 512 if ("E".equals(codeString)) 513 return E; 514 if ("NEG".equals(codeString)) 515 return NEG; 516 if ("ND".equals(codeString)) 517 return ND; 518 if ("POS".equals(codeString)) 519 return POS; 520 if ("DET".equals(codeString)) 521 return DET; 522 if ("ObservationInterpretationExpectation".equals(codeString)) 523 return OBSERVATIONINTERPRETATIONEXPECTATION; 524 if ("EXP".equals(codeString)) 525 return EXP; 526 if ("UNE".equals(codeString)) 527 return UNE; 528 if ("OBX".equals(codeString)) 529 return OBX; 530 if ("ReactivityObservationInterpretation".equals(codeString)) 531 return REACTIVITYOBSERVATIONINTERPRETATION; 532 if ("NR".equals(codeString)) 533 return NR; 534 if ("RR".equals(codeString)) 535 return RR; 536 if ("WR".equals(codeString)) 537 return WR; 538 throw new FHIRException("Unknown V3ObservationInterpretation code '"+codeString+"'"); 539 } 540 public String toCode() { 541 switch (this) { 542 case _GENETICOBSERVATIONINTERPRETATION: return "_GeneticObservationInterpretation"; 543 case CAR: return "CAR"; 544 case CARRIER: return "Carrier"; 545 case _OBSERVATIONINTERPRETATIONCHANGE: return "_ObservationInterpretationChange"; 546 case B: return "B"; 547 case D: return "D"; 548 case U: return "U"; 549 case W: return "W"; 550 case _OBSERVATIONINTERPRETATIONEXCEPTIONS: return "_ObservationInterpretationExceptions"; 551 case LESS_THAN: return "<"; 552 case GREATER_THAN: return ">"; 553 case AC: return "AC"; 554 case IE: return "IE"; 555 case QCF: return "QCF"; 556 case TOX: return "TOX"; 557 case _OBSERVATIONINTERPRETATIONNORMALITY: return "_ObservationInterpretationNormality"; 558 case A: return "A"; 559 case AA: return "AA"; 560 case HH: return "HH"; 561 case LL: return "LL"; 562 case H: return "H"; 563 case H_: return "H>"; 564 case HU: return "HU"; 565 case L: return "L"; 566 case L_: return "L<"; 567 case LU: return "LU"; 568 case N: return "N"; 569 case _OBSERVATIONINTERPRETATIONSUSCEPTIBILITY: return "_ObservationInterpretationSusceptibility"; 570 case I: return "I"; 571 case MS: return "MS"; 572 case NCL: return "NCL"; 573 case NS: return "NS"; 574 case R: return "R"; 575 case SYNR: return "SYN-R"; 576 case S: return "S"; 577 case SDD: return "SDD"; 578 case SYNS: return "SYN-S"; 579 case VS: return "VS"; 580 case EX: return "EX"; 581 case HX: return "HX"; 582 case LX: return "LX"; 583 case HM: return "HM"; 584 case OBSERVATIONINTERPRETATIONDETECTION: return "ObservationInterpretationDetection"; 585 case IND: return "IND"; 586 case E: return "E"; 587 case NEG: return "NEG"; 588 case ND: return "ND"; 589 case POS: return "POS"; 590 case DET: return "DET"; 591 case OBSERVATIONINTERPRETATIONEXPECTATION: return "ObservationInterpretationExpectation"; 592 case EXP: return "EXP"; 593 case UNE: return "UNE"; 594 case OBX: return "OBX"; 595 case REACTIVITYOBSERVATIONINTERPRETATION: return "ReactivityObservationInterpretation"; 596 case NR: return "NR"; 597 case RR: return "RR"; 598 case WR: return "WR"; 599 default: return "?"; 600 } 601 } 602 public String getSystem() { 603 return "http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation"; 604 } 605 public String getDefinition() { 606 switch (this) { 607 case _GENETICOBSERVATIONINTERPRETATION: return "Codes that specify interpretation of genetic analysis, such as \"positive\", \"negative\", \"carrier\", \"responsive\", etc."; 608 case CAR: return "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."; 609 case CARRIER: return "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.\r\n\n \n \n Deprecation Comment: \n This code is currently the same string as the print name for this concept and is inconsistent with the conventions being used for the other codes in the coding system, as it is a full word with initial capitalization, rather than an all upper case mnemonic. The recommendation from OO is to deprecate the code \"Carrier\" and to add \"CAR\" as the new active code representation for this concept."; 610 case _OBSERVATIONINTERPRETATIONCHANGE: return "Interpretations of change of quantity and/or severity. At most one of B or W and one of U or D allowed."; 611 case B: return "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).\r\n\n [Note: This can be applied to quantitative or qualitative observations.]"; 612 case D: return "The current result has decreased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure)."; 613 case U: return "The current result has increased from the previous result for a quantitative observation (the change is significant as defined in the respective test procedure)."; 614 case W: return "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).\r\n\n [Note: This can be applied to quantitative or qualitative observations.]"; 615 case _OBSERVATIONINTERPRETATIONEXCEPTIONS: return "Technical exceptions resulting in the inability to provide an interpretation. At most one allowed. Does not imply normality or severity."; 616 case LESS_THAN: return "The result is below the minimum detection limit (the test procedure or equipment is the limiting factor).\r\n\n Synonyms: Below analytical limit, low off scale."; 617 case GREATER_THAN: return "The result is above the maximum quantifiable limit (the test procedure or equipment is the limiting factor).\r\n\n Synonyms: Above analytical limit, high off scale."; 618 case AC: return "A valid result cannot be obtained for the specified component / analyte due to the presence of anti-complementary substances in the sample.\r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 \"Interpretation Codes."; 619 case IE: return "There is insufficient evidence that the species in question is a good target for therapy with the drug. A categorical interpretation is not possible.\r\n\n [Note: A MIC with \"IE\" and/or a comment may be reported (without an accompanying S, I or R-categorization).]"; 620 case QCF: return "A result cannot be considered valid for the specified component / analyte or organism due to failure in the quality control testing component.\r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 \"Interpretation Codes."; 621 case TOX: return "A valid result cannot be obtained for the specified organism or cell line due to the presence of cytotoxic substances in the sample or culture.\r\n\n \n \n Deprecation Comment: \n This code is being deprecated to match the status in V2 Table 0078 \"Interpretation Codes."; 622 case _OBSERVATIONINTERPRETATIONNORMALITY: return "Interpretation of normality or degree of abnormality (including critical or \"alert\" level). Concepts in this category are mutually exclusive, i.e., at most one is allowed."; 623 case A: return "The result or observation value is outside the reference range or expected norm (as defined for the respective test procedure).\r\n\n [Note: Typically applies to non-numeric results.]"; 624 case AA: return "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).\r\n\n [Note: Typically applies to non-numeric results. Analogous to critical/panic limits for numeric results.]"; 625 case HH: return "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).\r\n\n Synonym: Above upper panic limits."; 626 case LL: return "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).\r\n\n Synonym: Below lower panic limits."; 627 case H: return "The result for a quantitative observation is above the upper limit of the reference range (as defined for the respective test procedure).\r\n\n Synonym: Above high normal"; 628 case H_: return "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.[Note: This level is situated between 'H' and 'HH'.]\r\n\n \n Deprecation Comment: The code 'H>' is being deprecated in order to align with the use of the code 'HU' for \"Very high\" in V2 Table 0078 \"Interpretation Codes\".\r\n\n [Note: The use of code 'H>' is non-preferred, as this code is deprecated and on track to be retired; use code 'HU' instead."; 629 case HU: return "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."; 630 case L: return "The result for a quantitative observation is below the lower limit of the reference range (as defined for the respective test procedure).\r\n\n Synonym: Below low normal"; 631 case L_: return "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.[Note: This level is situated between 'L' and 'LL'.]\r\n\n \n Deprecation Comment: The code 'L<' is being deprecated in order to align with the use of the code 'LU' for \"Very low\" in V2 Table 0078 \"Interpretation Codes\".\r\n\n [Note: The use of code 'L<' is non-preferred, as this code is deprecated and on track to be retired; use code 'LU' instead."; 632 case LU: return "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."; 633 case N: return "The result or observation value is within the reference range or expected norm (as defined for the respective test procedure).\r\n\n [Note: Applies to numeric or non-numeric results.]"; 634 case _OBSERVATIONINTERPRETATIONSUSCEPTIBILITY: return "Interpretations of anti-microbial susceptibility testing results (microbiology). At most one allowed."; 635 case I: return "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)\nProjects: ISO 20776-1, ISO 20776-2\r\n\n [Note 1: Bacterial strains are categorized as intermediate by applying the appropriate breakpoints in a defined phenotypic test system.]\r\n\n [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.]\r\n\n [Note 3: This class also indicates a \"buffer zone,\" to prevent small, uncontrolled, technical factors from causing major discrepancies in interpretations.]\r\n\n [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).]"; 636 case MS: return "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.\r\n\n \n \n Deprecation Comment: \n This antimicrobial susceptibility test interpretation concept is recommended by OO to be deprecated as it is no longer recommended for use in susceptibility testing by CLSI (reference CLSI document M100-S22; Vol. 32 No.3; CLSI Performance Standards for Antimicrobial Susceptibility Testing; Twenty-Second Informational Supplement. Jan 2012)."; 637 case NCL: return "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."; 638 case NS: return "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.\r\n\n 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. \r\n\n NOTE 2: For strains yielding results in the \"nonsusceptible\" category, organism identification and antimicrobial susceptibility test results should be confirmed.\r\n\n Synonym: decreased susceptibility."; 639 case R: return "Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic failure.\nReference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm) \nProjects: ISO 20776-1, ISO 20776-2\r\n\n [Note 1: Bacterial strains are categorized as resistant by applying the appropriate breakpoints in a defined phenotypic test system.]\r\n\n [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).]"; 640 case SYNR: return "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. \r\n\n \n 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.\r\n\n \n 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."; 641 case S: return "Bacterial strain inhibited by in vitro concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic success.\nReference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm)\nSynonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2\r\n\n [Note 1: Bacterial strains are categorized as susceptible by applying the appropriate breakpoints in a defined phenotypic system.]\r\n\n [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).]"; 642 case SDD: return "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.\r\n\n Reference: CLSI document M44-A2 2009 \"Method for antifungal disk diffusion susceptibility testing of yeasts; approved guideline - second edition\" - page 2."; 643 case SYNS: return "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. \r\n\n \n 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.\r\n\n \n 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."; 644 case VS: return "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.\r\n\n \n \n Deprecation Comment: \n This antimicrobial susceptibility test interpretation concept is recommended by OO to be deprecated as it is no longer recommended for use in susceptibility testing by CLSI (reference CLSI document M100-S22; Vol. 32 No.3; CLSI Performance Standards for Antimicrobial Susceptibility Testing; Twenty-Second Informational Supplement. Jan 2012)."; 645 case EX: return "The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.\n\r\n\n Example: A positive result on a Hepatitis screening test.\n 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.\nThese 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.\nMembers 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."; 646 case HX: return "The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.\n\r\n\n Example: A positive result on a Hepatitis screening test.\n 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."; 647 case LX: return "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.\r\n\n Example: A Total White Blood Cell Count falling below a protocol-defined threshold value of 3000/mm^3\n 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."; 648 case HM: return "Hold for Medical Review\r\n\n \n Usage Note: This code is not intended for use in V3 artifacts. It is included in the code system to maintain alignment with the V2 Table 0078 \"Interpretation Codes.\""; 649 case OBSERVATIONINTERPRETATIONDETECTION: return "Interpretations of the presence or absence of a component / analyte or organism in a test or of a sign in a clinical observation. In keeping with laboratory data processing practice, these concepts provide a categorical interpretation of the \"meaning\" of the quantitative value for the same observation."; 650 case IND: return "The specified component / analyte, organism or clinical sign could neither be declared positive / negative nor detected / not detected by the performed test or procedure.\r\n\n \n 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\"."; 651 case E: return "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."; 652 case NEG: return "An absence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure.\r\n\n [Note: Negative does not necessarily imply the complete absence of the specified item.]"; 653 case ND: return "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."; 654 case POS: return "A presence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure."; 655 case DET: return "The measurement of the specified component / analyte, organism or clinical sign above the limit of detection of the performed test or procedure."; 656 case OBSERVATIONINTERPRETATIONEXPECTATION: return "Interpretation of the observed result taking into account additional information (contraindicators) about the patient's situation. Concepts in this category are mutually exclusive, i.e., at most one is allowed."; 657 case EXP: return "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)."; 658 case UNE: return "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)."; 659 case OBX: return "Interpretation qualifiers in separate OBX segments\r\n\n \n Usage Note: This code is not intended for use in V3 artifacts. It is included in the code system to maintain alignment with the V2 Table 0078 \"Interpretation Codes.\""; 660 case REACTIVITYOBSERVATIONINTERPRETATION: return "Interpretations of the presence and level of reactivity of the specified component / analyte with the reagent in the performed laboratory test."; 661 case NR: return "An absence finding used to indicate that the specified component / analyte did not react measurably with the reagent."; 662 case RR: return "A presence finding used to indicate that the specified component / analyte reacted with the reagent above the reliably measurable limit of the performed test."; 663 case WR: return "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."; 664 default: return "?"; 665 } 666 } 667 public String getDisplay() { 668 switch (this) { 669 case _GENETICOBSERVATIONINTERPRETATION: return "GeneticObservationInterpretation"; 670 case CAR: return "Carrier"; 671 case CARRIER: return "Carrier"; 672 case _OBSERVATIONINTERPRETATIONCHANGE: return "ObservationInterpretationChange"; 673 case B: return "Better"; 674 case D: return "Significant change down"; 675 case U: return "Significant change up"; 676 case W: return "Worse"; 677 case _OBSERVATIONINTERPRETATIONEXCEPTIONS: return "ObservationInterpretationExceptions"; 678 case LESS_THAN: return "Off scale low"; 679 case GREATER_THAN: return "Off scale high"; 680 case AC: return "Anti-complementary substances present"; 681 case IE: return "Insufficient evidence"; 682 case QCF: return "Quality control failure"; 683 case TOX: return "Cytotoxic substance present"; 684 case _OBSERVATIONINTERPRETATIONNORMALITY: return "ObservationInterpretationNormality"; 685 case A: return "Abnormal"; 686 case AA: return "Critical abnormal"; 687 case HH: return "Critical high"; 688 case LL: return "Critical low"; 689 case H: return "High"; 690 case H_: return "Significantly high"; 691 case HU: return "Significantly high"; 692 case L: return "Low"; 693 case L_: return "Significantly low"; 694 case LU: return "Significantly low"; 695 case N: return "Normal"; 696 case _OBSERVATIONINTERPRETATIONSUSCEPTIBILITY: return "ObservationInterpretationSusceptibility"; 697 case I: return "Intermediate"; 698 case MS: return "moderately susceptible"; 699 case NCL: return "No CLSI defined breakpoint"; 700 case NS: return "Non-susceptible"; 701 case R: return "Resistant"; 702 case SYNR: return "Synergy - resistant"; 703 case S: return "Susceptible"; 704 case SDD: return "Susceptible-dose dependent"; 705 case SYNS: return "Synergy - susceptible"; 706 case VS: return "very susceptible"; 707 case EX: return "outside threshold"; 708 case HX: return "above high threshold"; 709 case LX: return "below low threshold"; 710 case HM: return "Hold for Medical Review"; 711 case OBSERVATIONINTERPRETATIONDETECTION: return "ObservationInterpretationDetection"; 712 case IND: return "Indeterminate"; 713 case E: return "Equivocal"; 714 case NEG: return "Negative"; 715 case ND: return "Not detected"; 716 case POS: return "Positive"; 717 case DET: return "Detected"; 718 case OBSERVATIONINTERPRETATIONEXPECTATION: return "ObservationInterpretationExpectation"; 719 case EXP: return "Expected"; 720 case UNE: return "Unexpected"; 721 case OBX: return "Interpretation qualifiers in separate OBX segments"; 722 case REACTIVITYOBSERVATIONINTERPRETATION: return "ReactivityObservationInterpretation"; 723 case NR: return "Non-reactive"; 724 case RR: return "Reactive"; 725 case WR: return "Weakly reactive"; 726 default: return "?"; 727 } 728 } 729 730 731} 732