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 V3ObservationValue { 059 060 /** 061 * Codes specify the category of observation, evidence, or document used to assess for services, e.g., discharge planning, or to establish eligibility for coverage under a policy or program. The type of evidence is coded as observation values. 062 */ 063 _ACTCOVERAGEASSESSMENTOBSERVATIONVALUE, 064 /** 065 * Code specifying financial indicators used to assess or establish eligibility for coverage under a policy or program; e.g., pay stub; tax or income document; asset document; living expenses. 066 */ 067 _ACTFINANCIALSTATUSOBSERVATIONVALUE, 068 /** 069 * Codes specifying asset indicators used to assess or establish eligibility for coverage under a policy or program. 070 */ 071 ASSET, 072 /** 073 * Indicator of annuity ownership or status as beneficiary. 074 */ 075 ANNUITY, 076 /** 077 * Indicator of real property ownership, e.g., deed or real estate contract. 078 */ 079 PROP, 080 /** 081 * Indicator of retirement investment account ownership. 082 */ 083 RETACCT, 084 /** 085 * Indicator of status as trust beneficiary. 086 */ 087 TRUST, 088 /** 089 * Code specifying income indicators used to assess or establish eligibility for coverage under a policy or program; e.g., pay or pension check, child support payments received or provided, and taxes paid. 090 */ 091 INCOME, 092 /** 093 * Indicator of child support payments received or provided. 094 */ 095 CHILD, 096 /** 097 * Indicator of disability income replacement payment. 098 */ 099 DISABL, 100 /** 101 * Indicator of investment income, e.g., dividend check, annuity payment; real estate rent, investment divestiture proceeds; trust or endowment check. 102 */ 103 INVEST, 104 /** 105 * Indicator of paid employment, e.g., letter of hire, contract, employer letter; copy of pay check or pay stub. 106 */ 107 PAY, 108 /** 109 * Indicator of retirement payment, e.g., pension check. 110 */ 111 RETIRE, 112 /** 113 * Indicator of spousal or partner support payments received or provided; e.g., alimony payment; support stipulations in a divorce settlement. 114 */ 115 SPOUSAL, 116 /** 117 * Indicator of income supplement, e.g., gifting, parental income support; stipend, or grant. 118 */ 119 SUPPLE, 120 /** 121 * Indicator of tax obligation or payment, e.g., statement of taxable income. 122 */ 123 TAX, 124 /** 125 * Codes specifying living expense indicators used to assess or establish eligibility for coverage under a policy or program. 126 */ 127 LIVEXP, 128 /** 129 * Indicator of clothing expenses. 130 */ 131 CLOTH, 132 /** 133 * Indicator of transportation expenses. 134 */ 135 FOOD, 136 /** 137 * Indicator of health expenses; including medication costs, health service costs, financial participations, and health coverage premiums. 138 */ 139 HEALTH, 140 /** 141 * Indicator of housing expense, e.g., household appliances, fixtures, furnishings, and maintenance and repairs. 142 */ 143 HOUSE, 144 /** 145 * Indicator of legal expenses. 146 */ 147 LEGAL, 148 /** 149 * Indicator of mortgage amount, interest, and payments. 150 */ 151 MORTG, 152 /** 153 * Indicator of rental or lease payments. 154 */ 155 RENT, 156 /** 157 * Indicator of transportation expenses. 158 */ 159 SUNDRY, 160 /** 161 * Indicator of transportation expenses, e.g., vehicle payments, vehicle insurance, vehicle fuel, and vehicle maintenance and repairs. 162 */ 163 TRANS, 164 /** 165 * Indicator of transportation expenses. 166 */ 167 UTIL, 168 /** 169 * Code specifying eligibility indicators used to assess or establish eligibility for coverage under a policy or program eligibility status, e.g., certificates of creditable coverage; student enrollment; adoption, marriage or birth certificate. 170 */ 171 ELSTAT, 172 /** 173 * Indicator of adoption. 174 */ 175 ADOPT, 176 /** 177 * Indicator of birth. 178 */ 179 BTHCERT, 180 /** 181 * Indicator of creditable coverage. 182 */ 183 CCOC, 184 /** 185 * Indicator of driving status. 186 */ 187 DRLIC, 188 /** 189 * Indicator of foster child status. 190 */ 191 FOSTER, 192 /** 193 * Indicator of status as covered member under a policy or program, e.g., member id card or coverage document. 194 */ 195 MEMBER, 196 /** 197 * Indicator of military status. 198 */ 199 MIL, 200 /** 201 * Indicator of marriage status. 202 */ 203 MRGCERT, 204 /** 205 * Indicator of citizenship. 206 */ 207 PASSPORT, 208 /** 209 * Indicator of student status. 210 */ 211 STUDENRL, 212 /** 213 * Code specifying non-clinical indicators related to health status used to assess or establish eligibility for coverage under a policy or program, e.g., pregnancy, disability, drug use, mental health issues. 214 */ 215 HLSTAT, 216 /** 217 * Indication of disability. 218 */ 219 DISABLE, 220 /** 221 * Indication of drug use. 222 */ 223 DRUG, 224 /** 225 * Indication of IV drug use . 226 */ 227 IVDRG, 228 /** 229 * Non-clinical report of pregnancy. 230 */ 231 PGNT, 232 /** 233 * Code specifying observations related to living dependency, such as dependent upon spouse for activities of daily living. 234 */ 235 LIVDEP, 236 /** 237 * Continued living in private residence requires functional and health care assistance from one or more relatives. 238 */ 239 RELDEP, 240 /** 241 * Continued living in private residence requires functional and health care assistance from spouse or life partner. 242 */ 243 SPSDEP, 244 /** 245 * Continued living in private residence requires functional and health care assistance from one or more unrelated persons. 246 */ 247 URELDEP, 248 /** 249 * Code specifying observations related to living situation for a person in a private residence. 250 */ 251 LIVSIT, 252 /** 253 * Living alone. Maps to PD1-2 Living arrangement (IS) 00742 [A] 254 */ 255 ALONE, 256 /** 257 * Living with one or more dependent children requiring moderate supervision. 258 */ 259 DEPCHD, 260 /** 261 * Living with disabled spouse requiring functional and health care assistance 262 */ 263 DEPSPS, 264 /** 265 * Living with one or more dependent children requiring intensive supervision 266 */ 267 DEPYGCHD, 268 /** 269 * Living with family. Maps to PD1-2 Living arrangement (IS) 00742 [F] 270 */ 271 FAM, 272 /** 273 * Living with one or more relatives. Maps to PD1-2 Living arrangement (IS) 00742 [R] 274 */ 275 RELAT, 276 /** 277 * Living only with spouse or life partner. Maps to PD1-2 Living arrangement (IS) 00742 [S] 278 */ 279 SPS, 280 /** 281 * Living with one or more unrelated persons. 282 */ 283 UNREL, 284 /** 285 * Code specifying observations or indicators related to socio-economic status used to assess to assess for services, e.g., discharge planning, or to establish eligibility for coverage under a policy or program. 286 */ 287 SOECSTAT, 288 /** 289 * Indication of abuse victim. 290 */ 291 ABUSE, 292 /** 293 * Indication of status as homeless. 294 */ 295 HMLESS, 296 /** 297 * Indication of status as illegal immigrant. 298 */ 299 ILGIM, 300 /** 301 * Indication of status as incarcerated. 302 */ 303 INCAR, 304 /** 305 * Indication of probation status. 306 */ 307 PROB, 308 /** 309 * Indication of refugee status. 310 */ 311 REFUG, 312 /** 313 * Indication of unemployed status. 314 */ 315 UNEMPL, 316 /** 317 * Indicates the result of a particular allergy test. E.g. Negative, Mild, Moderate, Severe 318 */ 319 _ALLERGYTESTVALUE, 320 /** 321 * Description:Patient exhibits no reaction to the challenge agent. 322 */ 323 A0, 324 /** 325 * Description:Patient exhibits a minimal reaction to the challenge agent. 326 */ 327 A1, 328 /** 329 * Description:Patient exhibits a mild reaction to the challenge agent. 330 */ 331 A2, 332 /** 333 * Description:Patient exhibits moderate reaction to the challenge agent. 334 */ 335 A3, 336 /** 337 * Description:Patient exhibits a severe reaction to the challenge agent. 338 */ 339 A4, 340 /** 341 * Observation values that communicate the method used in a quality measure to combine the component measure results included in an composite measure. 342 */ 343 _COMPOSITEMEASURESCORING, 344 /** 345 * Code specifying that the measure uses all-or-nothing scoring. All-or-nothing scoring places an individual in the numerator of the composite measure if and only if they are in the numerator of all component measures in which they are in the denominator. 346 */ 347 ALLORNONESCR, 348 /** 349 * Code specifying that the measure uses linear scoring. Linear scoring computes the fraction of component measures in which the individual appears in the numerator, giving equal weight to each component measure. 350 */ 351 LINEARSCR, 352 /** 353 * Code specifying that the measure uses opportunity-based scoring. In opportunity-based scoring the measure score is determined by combining the denominator and numerator of each component measure to determine an overall composite score. 354 */ 355 OPPORSCR, 356 /** 357 * Code specifying that the measure uses weighted scoring. Weighted scoring assigns a factor to each component measure to weight that measure's contribution to the overall score. 358 */ 359 WEIGHTSCR, 360 /** 361 * Description:Coded observation values for coverage limitations, for e.g., types of claims or types of parties covered under a policy or program. 362 */ 363 _COVERAGELIMITOBSERVATIONVALUE, 364 /** 365 * Description:Coded observation values for types of covered parties under a policy or program based on their personal relationships or employment status. 366 */ 367 _COVERAGELEVELOBSERVATIONVALUE, 368 /** 369 * Description:Child over an age as specified by coverage policy or program, e.g., student, differently abled, and income dependent. 370 */ 371 ADC, 372 /** 373 * Description:Dependent biological, adopted, foster child as specified by coverage policy or program. 374 */ 375 CHD, 376 /** 377 * Description:Person requiring functional and/or financial assistance from another person as specified by coverage policy or program. 378 */ 379 DEP, 380 /** 381 * Description:Persons registered as a family unit in a domestic partner registry as specified by law and by coverage policy or program. 382 */ 383 DP, 384 /** 385 * Description:An individual employed by an employer who receive remuneration in wages, salary, commission, tips, piece-rates, or pay-in-kind through the employeraTMs payment system (i.e., not a contractor) as specified by coverage policy or program. 386 */ 387 ECH, 388 /** 389 * Description:As specified by coverage policy or program. 390 */ 391 FLY, 392 /** 393 * Description:Person as specified by coverage policy or program. 394 */ 395 IND, 396 /** 397 * Description:A pair of people of the same gender who live together as a family as specified by coverage policy or program, e.g., Naomi and Ruth from the Book of Ruth; Socrates and Alcibiades 398 */ 399 SSP, 400 /** 401 * A clinical judgment as to the worst case result of a future exposure (including substance administration). When the worst case result is assessed to have a life-threatening or organ system threatening potential, it is considered to be of high criticality. 402 */ 403 _CRITICALITYOBSERVATIONVALUE, 404 /** 405 * Worst case result of a future exposure is assessed to be life-threatening or having high potential for organ system failure. 406 */ 407 CRITH, 408 /** 409 * Worst case result of a future exposure is not assessed to be life-threatening or having high potential for organ system failure. 410 */ 411 CRITL, 412 /** 413 * Unable to assess the worst case result of a future exposure. 414 */ 415 CRITU, 416 /** 417 * Concepts representing whether a person does or does not currently have a job or is not currently in the labor pool seeking employment. 418 */ 419 _EMPLOYMENTSTATUS, 420 /** 421 * Individuals who, during the last week: a) did any work for at least 1 hour as paid or unpaid employees of a business or government organization; worked in their own businesses, professions, or on their own farms; or b) were not working, but who have a job or business from which the individual was temporarily absent because of vacation, illness, bad weather, childcare problems, maternity or paternity leave, labor-management dispute, job training, or other family or personal reasons, regardless of whether or not they were paid for the time off or were seeking other jobs. 422 */ 423 EMPLOYED, 424 /** 425 * Persons not classified as employed or unemployed, meaning those who have no job and are not looking for one. 426 */ 427 NOTINLABORFORCE, 428 /** 429 * Persons who currently have no employment, but are available for work and have made specific efforts to find employment. 430 */ 431 UNEMPLOYED, 432 /** 433 * Description: The domain contains genetic analysis specific observation values, e.g. Homozygote, Heterozygote, etc. 434 */ 435 _GENETICOBSERVATIONVALUE, 436 /** 437 * Description: An individual having different alleles at one or more loci regarding a specific character 438 */ 439 HOMOZYGOTE, 440 /** 441 * Observation values used to indicate the type of scoring (e.g. proportion, ratio) used by a health quality measure. 442 */ 443 _OBSERVATIONMEASURESCORING, 444 /** 445 * A measure in which either short-term cross-section or long-term longitudinal analysis is performed over a group of subjects defined by a set of common properties or defining characteristics (e.g., Male smokers between the ages of 40 and 50 years, exposure to treatment, exposure duration). 446 */ 447 COHORT, 448 /** 449 * A measure score in which each individual value for the measure can fall anywhere along a continuous scale (e.g., mean time to thrombolytics which aggregates the time in minutes from a case presenting with chest pain to the time of administration of thrombolytics). 450 */ 451 CONTVAR, 452 /** 453 * A score derived by dividing the number of cases that meet a criterion for quality (the numerator) by the number of eligible cases within a given time frame (the denominator) where the numerator cases are a subset of the denominator cases (e.g., percentage of eligible women with a mammogram performed in the last year). 454 */ 455 PROPOR, 456 /** 457 * A score that may have a value of zero or greater that is derived by dividing a count of one type of data by a count of another type of data (e.g., the number of patients with central lines who develop infection divided by the number of central line days). 458 */ 459 RATIO, 460 /** 461 * Observation values used to indicate what kind of health quality measure is used. 462 */ 463 _OBSERVATIONMEASURETYPE, 464 /** 465 * A measure that is composed from one or more other measures and indicates an overall summary of those measures. 466 */ 467 COMPOSITE, 468 /** 469 * A measure related to the efficiency of medical treatment. 470 */ 471 EFFICIENCY, 472 /** 473 * A measure related to the level of patient engagement or patient experience of care. 474 */ 475 EXPERIENCE, 476 /** 477 * A measure that indicates the result of the performance (or non-performance) of a function or process. 478 */ 479 OUTCOME, 480 /** 481 * A measure that evaluates the change over time of a physiologic state observable that is associated with a specific long-term health outcome. 482 */ 483 INTERMOM, 484 /** 485 * A measure that is a comparison of patient reported outcomes for a single or multiple patients collected via an instrument specifically designed to obtain input directly from patients. 486 */ 487 PROPM, 488 /** 489 * A measure which focuses on a process which leads to a certain outcome, meaning that a scientific basis exists for believing that the process, when executed well, will increase the probability of achieving a desired outcome. 490 */ 491 PROCESS, 492 /** 493 * A measure that assesses the use of one or more processes where the expected health benefit exceeds the expected negative consequences. 494 */ 495 APPROPRIATE, 496 /** 497 * A measure related to the extent of use of clinical resources or cost of care. 498 */ 499 RESOURCE, 500 /** 501 * A measure related to the structure of patient care. 502 */ 503 STRUCTURE, 504 /** 505 * Observation values used to assert various populations that a subject falls into. 506 */ 507 _OBSERVATIONPOPULATIONINCLUSION, 508 /** 509 * Patients who should be removed from the eMeasure population and denominator before determining if numerator criteria are met. Denominator exclusions are used in proportion and ratio measures to help narrow the denominator. 510 */ 511 DENEX, 512 /** 513 * Denominator exceptions are those conditions that should remove a patient, procedure or unit of measurement from the denominator only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures. Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories: 514 515 516 Medical reasons 517 Patient reasons 518 System reasons 519 */ 520 DENEXCEP, 521 /** 522 * It can be the same as the initial patient population or a subset of the initial patient population to further constrain the population for the purpose of the eMeasure. Different measures within an eMeasure set may have different Denominators. Continuous Variable eMeasures do not have a Denominator, but instead define a Measure Population. 523 */ 524 DENOM, 525 /** 526 * The initial population refers to all entities to be evaluated by a specific quality measure who share a common set of specified characteristics within a specific measurement set to which a given measure belongs. 527 */ 528 IP, 529 /** 530 * The initial patient population refers to all patients to be evaluated by a specific quality measure who share a common set of specified characteristics within a specific measurement set to which a given measure belongs. Details often include information based upon specific age groups, diagnoses, diagnostic and procedure codes, and enrollment periods. 531 */ 532 IPP, 533 /** 534 * Measure population is used only in continuous variable eMeasures. It is a narrative description of the eMeasure population. 535(e.g., all patients seen in the Emergency Department during the measurement period). 536 */ 537 MSRPOPL, 538 /** 539 * Numerators are used in proportion and ratio eMeasures. In proportion measures the numerator criteria are the processes or outcomes expected for each patient, procedure, or other unit of measurement defined in the denominator. In ratio measures the numerator is related, but not directly derived from the denominator (e.g., a numerator listing the number of central line blood stream infections and a denominator indicating the days per thousand of central line usage in a specific time period). 540 */ 541 NUMER, 542 /** 543 * Numerator Exclusions are used only in ratio eMeasures to define instances that should not be included in the numerator data. (e.g., if the number of central line blood stream infections per 1000 catheter days were to exclude infections with a specific bacterium, that bacterium would be listed as a numerator exclusion.) 544 */ 545 NUMEX, 546 /** 547 * PartialCompletionScale 548 */ 549 _PARTIALCOMPLETIONSCALE, 550 /** 551 * Value for Act.partialCompletionCode attribute that implies 81-99% completion 552 */ 553 G, 554 /** 555 * Value for Act.partialCompletionCode attribute that implies 61-80% completion 556 */ 557 LE, 558 /** 559 * Value for Act.partialCompletionCode attribute that implies 41-60% completion 560 */ 561 ME, 562 /** 563 * Value for Act.partialCompletionCode attribute that implies 1-20% completion 564 */ 565 MI, 566 /** 567 * Value for Act.partialCompletionCode attribute that implies 0% completion 568 */ 569 N, 570 /** 571 * Value for Act.partialCompletionCode attribute that implies 21-40% completion 572 */ 573 S, 574 /** 575 * Observation values used to indicate security observation metadata. 576 */ 577 _SECURITYOBSERVATIONVALUE, 578 /** 579 * Abstract security observation values used to indicate security integrity metadata. 580 581 582 Examples: Codes conveying integrity status, integrity confidence, and provenance. 583 */ 584 _SECINTOBV, 585 /** 586 * Abstract security metadata observation values used to indicate mechanism used for authorized alteration of an IT resource (data, information object, service, or system capability) 587 */ 588 _SECALTINTOBV, 589 /** 590 * Security metadata observation values used to indicate the use of a more abstract version of the content, e.g., replacing exact value of an age or date field with a range, or remove the left digits of a credit card number or SSN. 591 */ 592 ABSTRED, 593 /** 594 * Security metadata observation values used to indicate the use of an algorithmic combination of actual values with the result of an aggregate function, e.g., average, sum, or count in order to limit disclosure of an IT resource (data, information object, service, or system capability) to the minimum necessary. 595 */ 596 AGGRED, 597 /** 598 * Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) by used to indicate the mechanism by which software systems can strip portions of the resource that could allow the identification of the source of the information or the information subject. No key to relink the data is retained. 599 */ 600 ANONYED, 601 /** 602 * Security metadata observation value used to indicate that the IT resource semantic content has been transformed from one encoding to another. 603 604 605 Usage Note: "MAP" code does not indicate the semantic fidelity of the transformed content. 606 607 To indicate semantic fidelity for maps of HL7 to other code systems, this security alteration integrity observation may be further specified using an Act valued with Value Set: MapRelationship (2.16.840.1.113883.1.11.11052). 608 609 Semantic fidelity of the mapped IT Resource may also be indicated using a SecurityIntegrityConfidenceObservation. 610 */ 611 MAPPED, 612 /** 613 * Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) by indicating the mechanism by which software systems can make data unintelligible (that is, as unreadable and unusable by algorithmically transforming plaintext into ciphertext) such that it can only be accessed or used by authorized users. An authorized user may be provided a key to decrypt per license or "shared secret". 614 615 616 Usage Note: "MASKED" may be used, per applicable policy, as a flag to indicate to a user or receiver that some portion of an IT resource has been further encrypted, and may be accessed only by an authorized user or receiver to which a decryption key is provided. 617 */ 618 MASKED, 619 /** 620 * Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability), by indicating the mechanism by which software systems can strip portions of the resource that could allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject. 621 622 623 Rationale: Personal data which has been processed to make it impossible to know whose data it is. Used particularly for secondary use of health data. In some cases, it may be possible for authorized individuals to restore the identity of the individual, e.g.,for public health case management. Based on ISO/TS 25237:2008 Health informatics—Pseudonymization 624 */ 625 PSEUDED, 626 /** 627 * Security metadata observation value used to indicate the mechanism by which software systems can filter an IT resource (data, information object, service, or system capability) to remove any portion of the resource that is not authorized to be access, used, or disclosed. 628 629 630 Usage Note: "REDACTED" may be used, per applicable policy, as a flag to indicate to a user or receiver that some portion of an IT resource has filtered and not included in the content accessed or received. 631 */ 632 REDACTED, 633 /** 634 * Metadata observation used to indicate that some information has been removed from the source object when the view this object contains was constructed because of configuration options when the view was created. The content may not be suitable for use as the basis of a record update 635 636 637 Usage Note: This is not suitable to be used when information is removed for security reasons - see the code REDACTED for this use. 638 */ 639 SUBSETTED, 640 /** 641 * Security metadata observation value used to indicate that the IT resource syntax has been transformed from one syntactical representation to another. 642 643 644 Usage Note: "SYNTAC" code does not indicate the syntactical correctness of the syntactically transformed IT resource. 645 */ 646 SYNTAC, 647 /** 648 * Security metadata observation value used to indicate that the IT resource has been translated from one human language to another. 649 650 651 Usage Note: "TRSLT" does not indicate the fidelity of the translation or the languages translated. 652 653 The fidelity of the IT Resource translation may be indicated using a SecurityIntegrityConfidenceObservation. 654 655 To indicate languages, use the Value Set:HumanLanguage (2.16.840.1.113883.1.11.11526) 656 */ 657 TRSLT, 658 /** 659 * Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) which indicates that the resource only retains versions of an IT resource for access and use per applicable policy 660 661 662 Usage Note: When this code is used, expectation is that the system has removed historical versions of the data that falls outside the time period deemed to be the effective time of the applicable version. 663 */ 664 VERSIONED, 665 /** 666 * Abstract security observation values used to indicate data integrity metadata. 667 668 669 Examples: Codes conveying the mechanism used to preserve the accuracy and consistency of an IT resource such as a digital signature and a cryptographic hash function. 670 */ 671 _SECDATINTOBV, 672 /** 673 * Security metadata observation value used to indicate the mechanism by which software systems can establish that data was not modified in transit. 674 675 676 Rationale: This definition is intended to align with the ISO 22600-2 3.3.19 definition of cryptographic checkvalue: Information which is derived by performing a cryptographic transformation (see cryptography) on the data unit. The derivation of the checkvalue may be performed in one or more steps and is a result of a mathematical function of the key and a data unit. It is usually used to check the integrity of a data unit. 677 678 679 Examples: 680 681 682 683 SHA-1 684 SHA-2 (Secure Hash Algorithm) 685 */ 686 CRYTOHASH, 687 /** 688 * Security metadata observation value used to indicate the mechanism by which software systems use digital signature to establish that data has not been modified. 689 690 691 Rationale: This definition is intended to align with the ISO 22600-2 3.3.26 definition of digital signature: Data appended to, or a cryptographic transformation (see cryptography) of, a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g., by the recipient. 692 */ 693 DIGSIG, 694 /** 695 * Abstract security observation value used to indicate integrity confidence metadata. 696 697 698 Examples: Codes conveying the level of reliability and trustworthiness of an IT resource. 699 */ 700 _SECINTCONOBV, 701 /** 702 * Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be very high. 703 */ 704 HRELIABLE, 705 /** 706 * Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be adequate. 707 */ 708 RELIABLE, 709 /** 710 * Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be uncertain. 711 */ 712 UNCERTREL, 713 /** 714 * Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be inadequate. 715 */ 716 UNRELIABLE, 717 /** 718 * Abstract security metadata observation value used to indicate the provenance of an IT resource (data, information object, service, or system capability). 719 720 721 Examples: Codes conveying the provenance metadata about the entity reporting an IT resource. 722 */ 723 _SECINTPRVOBV, 724 /** 725 * Abstract security provenance metadata observation value used to indicate the entity that asserted an IT resource (data, information object, service, or system capability). 726 727 728 Examples: Codes conveying the provenance metadata about the entity asserting the resource. 729 */ 730 _SECINTPRVABOBV, 731 /** 732 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a clinician. 733 */ 734 CLINAST, 735 /** 736 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a device. 737 */ 738 DEVAST, 739 /** 740 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a healthcare professional. 741 */ 742 HCPAST, 743 /** 744 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a patient acquaintance. 745 */ 746 PACQAST, 747 /** 748 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a patient. 749 */ 750 PATAST, 751 /** 752 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a payer. 753 */ 754 PAYAST, 755 /** 756 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a professional. 757 */ 758 PROAST, 759 /** 760 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a substitute decision maker. 761 */ 762 SDMAST, 763 /** 764 * Abstract security provenance metadata observation value used to indicate the entity that reported the resource (data, information object, service, or system capability). 765 766 767 Examples: Codes conveying the provenance metadata about the entity reporting an IT resource. 768 */ 769 _SECINTPRVRBOBV, 770 /** 771 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a clinician. 772 */ 773 CLINRPT, 774 /** 775 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a device. 776 */ 777 DEVRPT, 778 /** 779 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a healthcare professional. 780 */ 781 HCPRPT, 782 /** 783 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a patient acquaintance. 784 */ 785 PACQRPT, 786 /** 787 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a patient. 788 */ 789 PATRPT, 790 /** 791 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a payer. 792 */ 793 PAYRPT, 794 /** 795 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a professional. 796 */ 797 PRORPT, 798 /** 799 * Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a substitute decision maker. 800 */ 801 SDMRPT, 802 /** 803 * Observation value used to indicate aspects of trust applicable to an IT resource (data, information object, service, or system capability). 804 */ 805 SECTRSTOBV, 806 /** 807 * Values for security trust accreditation metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework. 808 */ 809 TRSTACCRDOBV, 810 /** 811 * Values for security trust agreement metadata observation made about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] 812[ISO IEC 10181-1] 813 */ 814 TRSTAGREOBV, 815 /** 816 * Values for security trust certificate metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1] 817 818 For example, a Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. A particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. Another example is Cross Certification with Federal Bridge. 819 */ 820 TRSTCERTOBV, 821 /** 822 * Values for security trust assurance metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol. 823 */ 824 TRSTLOAOBV, 825 /** 826 * The value assigned as the indicator of the digital quality or reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 827 828 For example, the degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 829 */ 830 LOAAN, 831 /** 832 * Indicator of low digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 833 834 The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 835 836 Low authentication level of assurance indicates that the relying party may have little or no confidence in the asserted identity's validity. Level 1 requires little or no confidence in the asserted identity. No identity proofing is required at this level, but the authentication mechanism should provide some assurance that the same claimant is accessing the protected transaction or data. A wide range of available authentication technologies can be employed and any of the token methods of Levels 2, 3, or 4, including Personal Identification Numbers (PINs), may be used. To be authenticated, the claimant must prove control of the token through a secure authentication protocol. At Level 1, long-term shared authentication secrets may be revealed to verifiers. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 837 */ 838 LOAAN1, 839 /** 840 * Indicator of basic digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 841 842 The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 843 844 Basic authentication level of assurance indicates that the relying party may have some confidence in the asserted identity's validity. Level 2 requires confidence that the asserted identity is accurate. Level 2 provides for single-factor remote network authentication, including identity-proofing requirements for presentation of identifying materials or information. A wide range of available authentication technologies can be employed, including any of the token methods of Levels 3 or 4, as well as passwords. Successful authentication requires that the claimant prove through a secure authentication protocol that the claimant controls the token. Eavesdropper, replay, and online guessing attacks are prevented. 845Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Approved cryptographic techniques are required. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 846 */ 847 LOAAN2, 848 /** 849 * Indicator of medium digital quality or reliability of the digital reliability of verification and validation of the process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 850 851 The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 852 853 Medium authentication level of assurance indicates that the relying party may have high confidence in the asserted identity's validity. Level 3 is appropriate for transactions that need high confidence in the accuracy of the asserted identity. Level 3 provides multifactor remote network authentication. At this level, identity-proofing procedures require verification of identifying materials and information. Authentication is based on proof of possession of a key or password through a cryptographic protocol. Cryptographic strength mechanisms should protect the primary authentication token (a cryptographic key) against compromise by the protocol threats, including eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks. A minimum of two authentication factors is required. Three kinds of tokens may be used: 854 855 856 "soft" cryptographic token, which has the key stored on a general-purpose computer, 857 "hard" cryptographic token, which has the key stored on a special hardware device, and 858 "one-time password" device token, which has symmetric key stored on a personal hardware device that is a cryptographic module validated at FIPS 140-2 Level 1 or higher. Validation testing of cryptographic modules and algorithms for conformance to Federal Information Processing Standard (FIPS) 140-2, Security Requirements for Cryptographic Modules, is managed by NIST. 859 860 Authentication requires that the claimant prove control of the token through a secure authentication protocol. The token must be unlocked with a password or biometric representation, or a password must be used in a secure authentication protocol, to establish two-factor authentication. Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Approved cryptographic techniques are used for all operations. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 861 */ 862 LOAAN3, 863 /** 864 * Indicator of high digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 865 866 The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 867 868 High authentication level of assurance indicates that the relying party may have very high confidence in the asserted identity's validity. Level 4 is for transactions that need very high confidence in the accuracy of the asserted identity. Level 4 provides the highest practical assurance of remote network authentication. Authentication is based on proof of possession of a key through a cryptographic protocol. This level is similar to Level 3 except that only “hard� cryptographic tokens are allowed, cryptographic module validation requirements are strengthened, and subsequent critical data transfers must be authenticated via a key that is bound to the authentication process. The token should be a hardware cryptographic module validated at FIPS 140-2 Level 2 or higher overall with at least FIPS 140-2 Level 3 physical security. This level requires a physical token, which cannot readily be copied, and operator authentication at Level 2 and higher, and ensures good, two-factor remote authentication. 869 870 Level 4 requires strong cryptographic authentication of all parties and all sensitive data transfers between the parties. Either public key or symmetric key technology may be used. Authentication requires that the claimant prove through a secure authentication protocol that the claimant controls the token. Eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks are prevented. Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Strong approved cryptographic techniques are used for all operations. All sensitive data transfers are cryptographically authenticated using keys bound to the authentication process. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 871 */ 872 LOAAN4, 873 /** 874 * The value assigned as the indicator of the digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] 875 */ 876 LOAAP, 877 /** 878 * Indicator of the low digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] 879 880 Low authentication process level of assurance indicates that (1) long-term shared authentication secrets may be revealed to verifiers; and (2) assertions and assertion references require protection from manufacture/modification and reuse attacks. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 881 */ 882 LOAAP1, 883 /** 884 * Indicator of the basic digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] 885 886 Basic authentication process level of assurance indicates that long-term shared authentication secrets are never revealed to any other party except Credential Service Provider (CSP). Sessions (temporary) shared secrets may be provided to independent verifiers by CSP. Long-term shared authentication secrets, if used, are never revealed to any other party except Verifiers operated by the Credential Service Provider (CSP); however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. In addition to Level 1 requirements, assertions are resistant to disclosure, redirection, capture and substitution attacks. Approved cryptographic techniques are required. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 887 */ 888 LOAAP2, 889 /** 890 * Indicator of the medium digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] 891 892 Medium authentication process level of assurance indicates that the token can be unlocked with password, biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication. Long-term shared authentication secrets are never revealed to any party except the Claimant and Credential Service Provider (CSP). 893 894 Authentication requires that the Claimant prove, through a secure authentication protocol, that he or she controls the token. The Claimant unlocks the token with a password or biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication (through proof of possession of a physical or software token in combination with some memorized secret knowledge). Long-term shared authentication secrets, if used, are never revealed to any party except the Claimant and Verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. In addition to Level 2 requirements, assertions are protected against repudiation by the Verifier. 895 */ 896 LOAAP3, 897 /** 898 * Indicator of the high digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2] 899 900 High authentication process level of assurance indicates all sensitive data transfer are cryptographically authenticated using keys bound to the authentication process. Level 4 requires strong cryptographic authentication of all communicating parties and all sensitive data transfers between the parties. Either public key or symmetric key technology may be used. Authentication requires that the Claimant prove through a secure authentication protocol that he or she controls the token. All protocol threats at Level 3 are required to be prevented at Level 4. Protocols shall also be strongly resistant to man-in-the-middle attacks. Long-term shared authentication secrets, if used, are never revealed to any party except the Claimant and Verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. Approved cryptographic techniques are used for all operations. All sensitive data transfers are cryptographically authenticated using keys bound to the authentication process. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 901 */ 902 LOAAP4, 903 /** 904 * The value assigned as the indicator of the high quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. 905 */ 906 LOAAS, 907 /** 908 * Indicator of the low quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. 909 910 Assertions and assertion references require protection from modification and reuse attacks. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 911 */ 912 LOAAS1, 913 /** 914 * Indicator of the basic quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. 915 916 Assertions are resistant to disclosure, redirection, capture and substitution attacks. Approved cryptographic techniques are required for all assertion protocols. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 917 */ 918 LOAAS2, 919 /** 920 * Indicator of the medium quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. 921 922 Assertions are protected against repudiation by the verifier. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 923 */ 924 LOAAS3, 925 /** 926 * Indicator of the high quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes. 927 928 Strongly resistant to man-in-the-middle attacks. "Bearer" assertions are not used. "Holder-of-key" assertions may be used. RP maintains records of the assertions. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.] 929 */ 930 LOAAS4, 931 /** 932 * Indicator of the digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and its binding to an identity. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 933 */ 934 LOACM, 935 /** 936 * Indicator of the low digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and its binding to an identity. Little or no confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include weak identity binding to tokens and plaintext passwords or secrets not transmitted across a network. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 937 */ 938 LOACM1, 939 /** 940 * Indicator of the basic digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and its binding to an identity. Some confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Verification must prove claimant controls the token; token resists online guessing, replay, session hijacking, and eavesdropping attacks; and token is at least weakly resistant to man-in-the middle attacks. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 941 */ 942 LOACM2, 943 /** 944 * Indicator of the medium digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and it’s binding to an identity. High confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Ownership of token verifiable through security authentication protocol and credential management protects against verifier impersonation attacks. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 945 */ 946 LOACM3, 947 /** 948 * Indicator of the high digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and it’s binding to an identity. Very high confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Verifier can prove control of token through a secure protocol; credential management supports strong cryptographic authentication of all communication parties. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 949 */ 950 LOACM4, 951 /** 952 * Indicator of the quality or reliability in the process of ascertaining that an individual is who he or she claims to be. 953 */ 954 LOAID, 955 /** 956 * Indicator of low digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires that a continuity of identity be maintained but does not require identity proofing. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 957 */ 958 LOAID1, 959 /** 960 * Indicator of some digital quality or reliability in the process of ascertaining that that an individual is who he or she claims to be. Requires identity proofing via presentation of identifying material or information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 961 */ 962 LOAID2, 963 /** 964 * Indicator of high digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires identity proofing procedures for verification of identifying materials and information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 965 */ 966 LOAID3, 967 /** 968 * Indicator of high digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires identity proofing procedures for verification of identifying materials and information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 969 */ 970 LOAID4, 971 /** 972 * Indicator of the digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] 973 */ 974 LOANR, 975 /** 976 * Indicator of low digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] 977 */ 978 LOANR1, 979 /** 980 * Indicator of basic digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] 981 */ 982 LOANR2, 983 /** 984 * Indicator of medium digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] 985 */ 986 LOANR3, 987 /** 988 * Indicator of high digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] 989 */ 990 LOANR4, 991 /** 992 * Indicator of the digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization’s security controls. [Based on NIST SP 800-63-2] 993 */ 994 LOARA, 995 /** 996 * Indicator of low digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization’s security controls. [Based on NIST SP 800-63-2] 997 */ 998 LOARA1, 999 /** 1000 * Indicator of basic digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization’s security controls. [Based on NIST SP 800-63-2] 1001 */ 1002 LOARA2, 1003 /** 1004 * Indicator of medium digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization’s security controls. [Based on NIST SP 800-63-2] 1005 */ 1006 LOARA3, 1007 /** 1008 * Indicator of high digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization's security controls. [Based on NIST SP 800-63-2] 1009 */ 1010 LOARA4, 1011 /** 1012 * Indicator of the digital quality or reliability of single and multi-token authentication. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 1013 */ 1014 LOATK, 1015 /** 1016 * Indicator of the low digital quality or reliability of single and multi-token authentication. Permits the use of any of the token methods of Levels 2, 3, or 4. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 1017 */ 1018 LOATK1, 1019 /** 1020 * Indicator of the basic digital quality or reliability of single and multi-token authentication. Requires single factor authentication using memorized secret tokens, pre-registered knowledge tokens, look-up secret tokens, out of band tokens, or single factor one-time password devices. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 1021 */ 1022 LOATK2, 1023 /** 1024 * Indicator of the medium digital quality or reliability of single and multi-token authentication. Requires two authentication factors. Provides multi-factor remote network authentication. Permits multi-factor software cryptographic token. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 1025 */ 1026 LOATK3, 1027 /** 1028 * Indicator of the high digital quality or reliability of single and multi-token authentication. Requires token that is a hardware cryptographic module validated at validated at Federal Information Processing Standard (FIPS) 140-2 Level 2 or higher overall with at least FIPS 140-2 Level 3 physical security. Level 4 token requirements can be met by using the PIV authentication key of a FIPS 201 compliant Personal Identity Verification (PIV) Card. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011] 1029 */ 1030 LOATK4, 1031 /** 1032 * Values for security trust mechanism metadata observation made about a security architecture system component that supports enforcement of security policies. 1033 */ 1034 TRSTMECOBV, 1035 /** 1036 * Potential values for observations of severity. 1037 */ 1038 _SEVERITYOBSERVATION, 1039 /** 1040 * Indicates the condition may be life-threatening or has the potential to cause permanent injury. 1041 */ 1042 H, 1043 /** 1044 * Indicates the condition may result in some adverse consequences but is unlikely to substantially affect the situation of the subject. 1045 */ 1046 L, 1047 /** 1048 * Indicates the condition may result in noticable adverse adverse consequences but is unlikely to be life-threatening or cause permanent injury. 1049 */ 1050 M, 1051 /** 1052 * Contains codes for defining the observed, physical position of a subject, such as during an observation, assessment, collection of a specimen, etc. ECG waveforms and vital signs, such as blood pressure, are two examples where a general, observed position typically needs to be noted. 1053 */ 1054 _SUBJECTBODYPOSITION, 1055 /** 1056 * Lying on the left side. 1057 */ 1058 LLD, 1059 /** 1060 * Lying with the front or ventral surface downward; lying face down. 1061 */ 1062 PRN, 1063 /** 1064 * Lying on the right side. 1065 */ 1066 RLD, 1067 /** 1068 * A semi-sitting position in bed with the head of the bed elevated approximately 45 degrees. 1069 */ 1070 SFWL, 1071 /** 1072 * Resting the body on the buttocks, typically with upper torso erect or semi erect. 1073 */ 1074 SIT, 1075 /** 1076 * To be stationary, upright, vertical, on one's legs. 1077 */ 1078 STN, 1079 /** 1080 * supine 1081 */ 1082 SUP, 1083 /** 1084 * Lying on the back, on an inclined plane, typically about 30-45 degrees with head raised and feet lowered. 1085 */ 1086 RTRD, 1087 /** 1088 * Lying on the back, on an inclined plane, typically about 30-45 degrees, with head lowered and feet raised. 1089 */ 1090 TRD, 1091 /** 1092 * Values for observations of verification act results 1093 1094 1095 Examples: Verified, not verified, verified with warning. 1096 */ 1097 _VERIFICATIONOUTCOMEVALUE, 1098 /** 1099 * Definition: Coverage is in effect for healthcare service(s) and/or product(s). 1100 */ 1101 ACT, 1102 /** 1103 * Definition: Coverage is in effect for healthcare service(s) and/or product(s) - Pending Investigation 1104 */ 1105 ACTPEND, 1106 /** 1107 * Definition: Coverage is in effect for healthcare service(s) and/or product(s). 1108 */ 1109 ELG, 1110 /** 1111 * Definition: Coverage is not in effect for healthcare service(s) and/or product(s). 1112 */ 1113 INACT, 1114 /** 1115 * Definition: Coverage is not in effect for healthcare service(s) and/or product(s) - Pending Investigation. 1116 */ 1117 INPNDINV, 1118 /** 1119 * Definition: Coverage is not in effect for healthcare service(s) and/or product(s) - Pending Eligibility Update. 1120 */ 1121 INPNDUPD, 1122 /** 1123 * Definition: Coverage is not in effect for healthcare service(s) and/or product(s). May optionally include reasons for the ineligibility. 1124 */ 1125 NELG, 1126 /** 1127 * Concepts that describe an individual's typical arrangement of working hours for an occupation. 1128 */ 1129 _WORKSCHEDULE, 1130 /** 1131 * A person who is scheduled for work during daytime hours (for example between 6am and 6pm) on a regular basis. 1132 */ 1133 DS, 1134 /** 1135 * Consistent Early morning schedule of 13 hours or less per shift (between 2 am and 2 pm) 1136 */ 1137 EMS, 1138 /** 1139 * A person who is scheduled for work during evening hours (for example between 2pm and midnight) on a regular basis. 1140 */ 1141 ES, 1142 /** 1143 * Scheduled for work during nighttime hours (for example between 9pm and 8am) on a regular basis. 1144 */ 1145 NS, 1146 /** 1147 * Scheduled for work times that change periodically between days, and/or evenings, and includes some night shifts. 1148 */ 1149 RSWN, 1150 /** 1151 * Scheduled for work days/times that change periodically between days, but does not include night or evening work. 1152 */ 1153 RSWON, 1154 /** 1155 * Shift consisting of two distinct work periods each day that are separated by a break of a few hours (for example 2 to 4 hours) 1156 */ 1157 SS, 1158 /** 1159 * Shifts of 17 or more hours. 1160 */ 1161 VLS, 1162 /** 1163 * Irregular, unpredictable hours scheduled on a short notice (for example, less than 2 day notice): inconsistent schedule, on-call, as needed, as available. 1164 */ 1165 VS, 1166 /** 1167 * AnnotationValue 1168 */ 1169 _ANNOTATIONVALUE, 1170 /** 1171 * Description:Used in a patient care message to value simple clinical (non-lab) observations. 1172 */ 1173 _COMMONCLINICALOBSERVATIONVALUE, 1174 /** 1175 * This domain is established as a parent to a variety of value domains being defined to support the communication of Individual Case Safety Reports to regulatory bodies. Arguably, this aggregation is not taxonomically pure, but the grouping will facilitate the management of these domains. 1176 */ 1177 _INDIVIDUALCASESAFETYREPORTVALUEDOMAINS, 1178 /** 1179 * Indicates the specific observation result which is the reason for the action (prescription, lab test, etc.). E.g. Headache, Ear infection, planned diagnostic image (requiring contrast agent), etc. 1180 */ 1181 _INDICATIONVALUE, 1182 /** 1183 * added to help the parsers 1184 */ 1185 NULL; 1186 public static V3ObservationValue fromCode(String codeString) throws FHIRException { 1187 if (codeString == null || "".equals(codeString)) 1188 return null; 1189 if ("_ActCoverageAssessmentObservationValue".equals(codeString)) 1190 return _ACTCOVERAGEASSESSMENTOBSERVATIONVALUE; 1191 if ("_ActFinancialStatusObservationValue".equals(codeString)) 1192 return _ACTFINANCIALSTATUSOBSERVATIONVALUE; 1193 if ("ASSET".equals(codeString)) 1194 return ASSET; 1195 if ("ANNUITY".equals(codeString)) 1196 return ANNUITY; 1197 if ("PROP".equals(codeString)) 1198 return PROP; 1199 if ("RETACCT".equals(codeString)) 1200 return RETACCT; 1201 if ("TRUST".equals(codeString)) 1202 return TRUST; 1203 if ("INCOME".equals(codeString)) 1204 return INCOME; 1205 if ("CHILD".equals(codeString)) 1206 return CHILD; 1207 if ("DISABL".equals(codeString)) 1208 return DISABL; 1209 if ("INVEST".equals(codeString)) 1210 return INVEST; 1211 if ("PAY".equals(codeString)) 1212 return PAY; 1213 if ("RETIRE".equals(codeString)) 1214 return RETIRE; 1215 if ("SPOUSAL".equals(codeString)) 1216 return SPOUSAL; 1217 if ("SUPPLE".equals(codeString)) 1218 return SUPPLE; 1219 if ("TAX".equals(codeString)) 1220 return TAX; 1221 if ("LIVEXP".equals(codeString)) 1222 return LIVEXP; 1223 if ("CLOTH".equals(codeString)) 1224 return CLOTH; 1225 if ("FOOD".equals(codeString)) 1226 return FOOD; 1227 if ("HEALTH".equals(codeString)) 1228 return HEALTH; 1229 if ("HOUSE".equals(codeString)) 1230 return HOUSE; 1231 if ("LEGAL".equals(codeString)) 1232 return LEGAL; 1233 if ("MORTG".equals(codeString)) 1234 return MORTG; 1235 if ("RENT".equals(codeString)) 1236 return RENT; 1237 if ("SUNDRY".equals(codeString)) 1238 return SUNDRY; 1239 if ("TRANS".equals(codeString)) 1240 return TRANS; 1241 if ("UTIL".equals(codeString)) 1242 return UTIL; 1243 if ("ELSTAT".equals(codeString)) 1244 return ELSTAT; 1245 if ("ADOPT".equals(codeString)) 1246 return ADOPT; 1247 if ("BTHCERT".equals(codeString)) 1248 return BTHCERT; 1249 if ("CCOC".equals(codeString)) 1250 return CCOC; 1251 if ("DRLIC".equals(codeString)) 1252 return DRLIC; 1253 if ("FOSTER".equals(codeString)) 1254 return FOSTER; 1255 if ("MEMBER".equals(codeString)) 1256 return MEMBER; 1257 if ("MIL".equals(codeString)) 1258 return MIL; 1259 if ("MRGCERT".equals(codeString)) 1260 return MRGCERT; 1261 if ("PASSPORT".equals(codeString)) 1262 return PASSPORT; 1263 if ("STUDENRL".equals(codeString)) 1264 return STUDENRL; 1265 if ("HLSTAT".equals(codeString)) 1266 return HLSTAT; 1267 if ("DISABLE".equals(codeString)) 1268 return DISABLE; 1269 if ("DRUG".equals(codeString)) 1270 return DRUG; 1271 if ("IVDRG".equals(codeString)) 1272 return IVDRG; 1273 if ("PGNT".equals(codeString)) 1274 return PGNT; 1275 if ("LIVDEP".equals(codeString)) 1276 return LIVDEP; 1277 if ("RELDEP".equals(codeString)) 1278 return RELDEP; 1279 if ("SPSDEP".equals(codeString)) 1280 return SPSDEP; 1281 if ("URELDEP".equals(codeString)) 1282 return URELDEP; 1283 if ("LIVSIT".equals(codeString)) 1284 return LIVSIT; 1285 if ("ALONE".equals(codeString)) 1286 return ALONE; 1287 if ("DEPCHD".equals(codeString)) 1288 return DEPCHD; 1289 if ("DEPSPS".equals(codeString)) 1290 return DEPSPS; 1291 if ("DEPYGCHD".equals(codeString)) 1292 return DEPYGCHD; 1293 if ("FAM".equals(codeString)) 1294 return FAM; 1295 if ("RELAT".equals(codeString)) 1296 return RELAT; 1297 if ("SPS".equals(codeString)) 1298 return SPS; 1299 if ("UNREL".equals(codeString)) 1300 return UNREL; 1301 if ("SOECSTAT".equals(codeString)) 1302 return SOECSTAT; 1303 if ("ABUSE".equals(codeString)) 1304 return ABUSE; 1305 if ("HMLESS".equals(codeString)) 1306 return HMLESS; 1307 if ("ILGIM".equals(codeString)) 1308 return ILGIM; 1309 if ("INCAR".equals(codeString)) 1310 return INCAR; 1311 if ("PROB".equals(codeString)) 1312 return PROB; 1313 if ("REFUG".equals(codeString)) 1314 return REFUG; 1315 if ("UNEMPL".equals(codeString)) 1316 return UNEMPL; 1317 if ("_AllergyTestValue".equals(codeString)) 1318 return _ALLERGYTESTVALUE; 1319 if ("A0".equals(codeString)) 1320 return A0; 1321 if ("A1".equals(codeString)) 1322 return A1; 1323 if ("A2".equals(codeString)) 1324 return A2; 1325 if ("A3".equals(codeString)) 1326 return A3; 1327 if ("A4".equals(codeString)) 1328 return A4; 1329 if ("_CompositeMeasureScoring".equals(codeString)) 1330 return _COMPOSITEMEASURESCORING; 1331 if ("ALLORNONESCR".equals(codeString)) 1332 return ALLORNONESCR; 1333 if ("LINEARSCR".equals(codeString)) 1334 return LINEARSCR; 1335 if ("OPPORSCR".equals(codeString)) 1336 return OPPORSCR; 1337 if ("WEIGHTSCR".equals(codeString)) 1338 return WEIGHTSCR; 1339 if ("_CoverageLimitObservationValue".equals(codeString)) 1340 return _COVERAGELIMITOBSERVATIONVALUE; 1341 if ("_CoverageLevelObservationValue".equals(codeString)) 1342 return _COVERAGELEVELOBSERVATIONVALUE; 1343 if ("ADC".equals(codeString)) 1344 return ADC; 1345 if ("CHD".equals(codeString)) 1346 return CHD; 1347 if ("DEP".equals(codeString)) 1348 return DEP; 1349 if ("DP".equals(codeString)) 1350 return DP; 1351 if ("ECH".equals(codeString)) 1352 return ECH; 1353 if ("FLY".equals(codeString)) 1354 return FLY; 1355 if ("IND".equals(codeString)) 1356 return IND; 1357 if ("SSP".equals(codeString)) 1358 return SSP; 1359 if ("_CriticalityObservationValue".equals(codeString)) 1360 return _CRITICALITYOBSERVATIONVALUE; 1361 if ("CRITH".equals(codeString)) 1362 return CRITH; 1363 if ("CRITL".equals(codeString)) 1364 return CRITL; 1365 if ("CRITU".equals(codeString)) 1366 return CRITU; 1367 if ("_EmploymentStatus".equals(codeString)) 1368 return _EMPLOYMENTSTATUS; 1369 if ("Employed".equals(codeString)) 1370 return EMPLOYED; 1371 if ("NotInLaborForce".equals(codeString)) 1372 return NOTINLABORFORCE; 1373 if ("Unemployed".equals(codeString)) 1374 return UNEMPLOYED; 1375 if ("_GeneticObservationValue".equals(codeString)) 1376 return _GENETICOBSERVATIONVALUE; 1377 if ("Homozygote".equals(codeString)) 1378 return HOMOZYGOTE; 1379 if ("_ObservationMeasureScoring".equals(codeString)) 1380 return _OBSERVATIONMEASURESCORING; 1381 if ("COHORT".equals(codeString)) 1382 return COHORT; 1383 if ("CONTVAR".equals(codeString)) 1384 return CONTVAR; 1385 if ("PROPOR".equals(codeString)) 1386 return PROPOR; 1387 if ("RATIO".equals(codeString)) 1388 return RATIO; 1389 if ("_ObservationMeasureType".equals(codeString)) 1390 return _OBSERVATIONMEASURETYPE; 1391 if ("COMPOSITE".equals(codeString)) 1392 return COMPOSITE; 1393 if ("EFFICIENCY".equals(codeString)) 1394 return EFFICIENCY; 1395 if ("EXPERIENCE".equals(codeString)) 1396 return EXPERIENCE; 1397 if ("OUTCOME".equals(codeString)) 1398 return OUTCOME; 1399 if ("INTERM-OM".equals(codeString)) 1400 return INTERMOM; 1401 if ("PRO-PM".equals(codeString)) 1402 return PROPM; 1403 if ("PROCESS".equals(codeString)) 1404 return PROCESS; 1405 if ("APPROPRIATE".equals(codeString)) 1406 return APPROPRIATE; 1407 if ("RESOURCE".equals(codeString)) 1408 return RESOURCE; 1409 if ("STRUCTURE".equals(codeString)) 1410 return STRUCTURE; 1411 if ("_ObservationPopulationInclusion".equals(codeString)) 1412 return _OBSERVATIONPOPULATIONINCLUSION; 1413 if ("DENEX".equals(codeString)) 1414 return DENEX; 1415 if ("DENEXCEP".equals(codeString)) 1416 return DENEXCEP; 1417 if ("DENOM".equals(codeString)) 1418 return DENOM; 1419 if ("IP".equals(codeString)) 1420 return IP; 1421 if ("IPP".equals(codeString)) 1422 return IPP; 1423 if ("MSRPOPL".equals(codeString)) 1424 return MSRPOPL; 1425 if ("NUMER".equals(codeString)) 1426 return NUMER; 1427 if ("NUMEX".equals(codeString)) 1428 return NUMEX; 1429 if ("_PartialCompletionScale".equals(codeString)) 1430 return _PARTIALCOMPLETIONSCALE; 1431 if ("G".equals(codeString)) 1432 return G; 1433 if ("LE".equals(codeString)) 1434 return LE; 1435 if ("ME".equals(codeString)) 1436 return ME; 1437 if ("MI".equals(codeString)) 1438 return MI; 1439 if ("N".equals(codeString)) 1440 return N; 1441 if ("S".equals(codeString)) 1442 return S; 1443 if ("_SecurityObservationValue".equals(codeString)) 1444 return _SECURITYOBSERVATIONVALUE; 1445 if ("_SECINTOBV".equals(codeString)) 1446 return _SECINTOBV; 1447 if ("_SECALTINTOBV".equals(codeString)) 1448 return _SECALTINTOBV; 1449 if ("ABSTRED".equals(codeString)) 1450 return ABSTRED; 1451 if ("AGGRED".equals(codeString)) 1452 return AGGRED; 1453 if ("ANONYED".equals(codeString)) 1454 return ANONYED; 1455 if ("MAPPED".equals(codeString)) 1456 return MAPPED; 1457 if ("MASKED".equals(codeString)) 1458 return MASKED; 1459 if ("PSEUDED".equals(codeString)) 1460 return PSEUDED; 1461 if ("REDACTED".equals(codeString)) 1462 return REDACTED; 1463 if ("SUBSETTED".equals(codeString)) 1464 return SUBSETTED; 1465 if ("SYNTAC".equals(codeString)) 1466 return SYNTAC; 1467 if ("TRSLT".equals(codeString)) 1468 return TRSLT; 1469 if ("VERSIONED".equals(codeString)) 1470 return VERSIONED; 1471 if ("_SECDATINTOBV".equals(codeString)) 1472 return _SECDATINTOBV; 1473 if ("CRYTOHASH".equals(codeString)) 1474 return CRYTOHASH; 1475 if ("DIGSIG".equals(codeString)) 1476 return DIGSIG; 1477 if ("_SECINTCONOBV".equals(codeString)) 1478 return _SECINTCONOBV; 1479 if ("HRELIABLE".equals(codeString)) 1480 return HRELIABLE; 1481 if ("RELIABLE".equals(codeString)) 1482 return RELIABLE; 1483 if ("UNCERTREL".equals(codeString)) 1484 return UNCERTREL; 1485 if ("UNRELIABLE".equals(codeString)) 1486 return UNRELIABLE; 1487 if ("_SECINTPRVOBV".equals(codeString)) 1488 return _SECINTPRVOBV; 1489 if ("_SECINTPRVABOBV".equals(codeString)) 1490 return _SECINTPRVABOBV; 1491 if ("CLINAST".equals(codeString)) 1492 return CLINAST; 1493 if ("DEVAST".equals(codeString)) 1494 return DEVAST; 1495 if ("HCPAST".equals(codeString)) 1496 return HCPAST; 1497 if ("PACQAST".equals(codeString)) 1498 return PACQAST; 1499 if ("PATAST".equals(codeString)) 1500 return PATAST; 1501 if ("PAYAST".equals(codeString)) 1502 return PAYAST; 1503 if ("PROAST".equals(codeString)) 1504 return PROAST; 1505 if ("SDMAST".equals(codeString)) 1506 return SDMAST; 1507 if ("_SECINTPRVRBOBV".equals(codeString)) 1508 return _SECINTPRVRBOBV; 1509 if ("CLINRPT".equals(codeString)) 1510 return CLINRPT; 1511 if ("DEVRPT".equals(codeString)) 1512 return DEVRPT; 1513 if ("HCPRPT".equals(codeString)) 1514 return HCPRPT; 1515 if ("PACQRPT".equals(codeString)) 1516 return PACQRPT; 1517 if ("PATRPT".equals(codeString)) 1518 return PATRPT; 1519 if ("PAYRPT".equals(codeString)) 1520 return PAYRPT; 1521 if ("PRORPT".equals(codeString)) 1522 return PRORPT; 1523 if ("SDMRPT".equals(codeString)) 1524 return SDMRPT; 1525 if ("SECTRSTOBV".equals(codeString)) 1526 return SECTRSTOBV; 1527 if ("TRSTACCRDOBV".equals(codeString)) 1528 return TRSTACCRDOBV; 1529 if ("TRSTAGREOBV".equals(codeString)) 1530 return TRSTAGREOBV; 1531 if ("TRSTCERTOBV".equals(codeString)) 1532 return TRSTCERTOBV; 1533 if ("TRSTLOAOBV".equals(codeString)) 1534 return TRSTLOAOBV; 1535 if ("LOAAN".equals(codeString)) 1536 return LOAAN; 1537 if ("LOAAN1".equals(codeString)) 1538 return LOAAN1; 1539 if ("LOAAN2".equals(codeString)) 1540 return LOAAN2; 1541 if ("LOAAN3".equals(codeString)) 1542 return LOAAN3; 1543 if ("LOAAN4".equals(codeString)) 1544 return LOAAN4; 1545 if ("LOAAP".equals(codeString)) 1546 return LOAAP; 1547 if ("LOAAP1".equals(codeString)) 1548 return LOAAP1; 1549 if ("LOAAP2".equals(codeString)) 1550 return LOAAP2; 1551 if ("LOAAP3".equals(codeString)) 1552 return LOAAP3; 1553 if ("LOAAP4".equals(codeString)) 1554 return LOAAP4; 1555 if ("LOAAS".equals(codeString)) 1556 return LOAAS; 1557 if ("LOAAS1".equals(codeString)) 1558 return LOAAS1; 1559 if ("LOAAS2".equals(codeString)) 1560 return LOAAS2; 1561 if ("LOAAS3".equals(codeString)) 1562 return LOAAS3; 1563 if ("LOAAS4".equals(codeString)) 1564 return LOAAS4; 1565 if ("LOACM".equals(codeString)) 1566 return LOACM; 1567 if ("LOACM1".equals(codeString)) 1568 return LOACM1; 1569 if ("LOACM2".equals(codeString)) 1570 return LOACM2; 1571 if ("LOACM3".equals(codeString)) 1572 return LOACM3; 1573 if ("LOACM4".equals(codeString)) 1574 return LOACM4; 1575 if ("LOAID".equals(codeString)) 1576 return LOAID; 1577 if ("LOAID1".equals(codeString)) 1578 return LOAID1; 1579 if ("LOAID2".equals(codeString)) 1580 return LOAID2; 1581 if ("LOAID3".equals(codeString)) 1582 return LOAID3; 1583 if ("LOAID4".equals(codeString)) 1584 return LOAID4; 1585 if ("LOANR".equals(codeString)) 1586 return LOANR; 1587 if ("LOANR1".equals(codeString)) 1588 return LOANR1; 1589 if ("LOANR2".equals(codeString)) 1590 return LOANR2; 1591 if ("LOANR3".equals(codeString)) 1592 return LOANR3; 1593 if ("LOANR4".equals(codeString)) 1594 return LOANR4; 1595 if ("LOARA".equals(codeString)) 1596 return LOARA; 1597 if ("LOARA1".equals(codeString)) 1598 return LOARA1; 1599 if ("LOARA2".equals(codeString)) 1600 return LOARA2; 1601 if ("LOARA3".equals(codeString)) 1602 return LOARA3; 1603 if ("LOARA4".equals(codeString)) 1604 return LOARA4; 1605 if ("LOATK".equals(codeString)) 1606 return LOATK; 1607 if ("LOATK1".equals(codeString)) 1608 return LOATK1; 1609 if ("LOATK2".equals(codeString)) 1610 return LOATK2; 1611 if ("LOATK3".equals(codeString)) 1612 return LOATK3; 1613 if ("LOATK4".equals(codeString)) 1614 return LOATK4; 1615 if ("TRSTMECOBV".equals(codeString)) 1616 return TRSTMECOBV; 1617 if ("_SeverityObservation".equals(codeString)) 1618 return _SEVERITYOBSERVATION; 1619 if ("H".equals(codeString)) 1620 return H; 1621 if ("L".equals(codeString)) 1622 return L; 1623 if ("M".equals(codeString)) 1624 return M; 1625 if ("_SubjectBodyPosition".equals(codeString)) 1626 return _SUBJECTBODYPOSITION; 1627 if ("LLD".equals(codeString)) 1628 return LLD; 1629 if ("PRN".equals(codeString)) 1630 return PRN; 1631 if ("RLD".equals(codeString)) 1632 return RLD; 1633 if ("SFWL".equals(codeString)) 1634 return SFWL; 1635 if ("SIT".equals(codeString)) 1636 return SIT; 1637 if ("STN".equals(codeString)) 1638 return STN; 1639 if ("SUP".equals(codeString)) 1640 return SUP; 1641 if ("RTRD".equals(codeString)) 1642 return RTRD; 1643 if ("TRD".equals(codeString)) 1644 return TRD; 1645 if ("_VerificationOutcomeValue".equals(codeString)) 1646 return _VERIFICATIONOUTCOMEVALUE; 1647 if ("ACT".equals(codeString)) 1648 return ACT; 1649 if ("ACTPEND".equals(codeString)) 1650 return ACTPEND; 1651 if ("ELG".equals(codeString)) 1652 return ELG; 1653 if ("INACT".equals(codeString)) 1654 return INACT; 1655 if ("INPNDINV".equals(codeString)) 1656 return INPNDINV; 1657 if ("INPNDUPD".equals(codeString)) 1658 return INPNDUPD; 1659 if ("NELG".equals(codeString)) 1660 return NELG; 1661 if ("_WorkSchedule".equals(codeString)) 1662 return _WORKSCHEDULE; 1663 if ("DS".equals(codeString)) 1664 return DS; 1665 if ("EMS".equals(codeString)) 1666 return EMS; 1667 if ("ES".equals(codeString)) 1668 return ES; 1669 if ("NS".equals(codeString)) 1670 return NS; 1671 if ("RSWN".equals(codeString)) 1672 return RSWN; 1673 if ("RSWON".equals(codeString)) 1674 return RSWON; 1675 if ("SS".equals(codeString)) 1676 return SS; 1677 if ("VLS".equals(codeString)) 1678 return VLS; 1679 if ("VS".equals(codeString)) 1680 return VS; 1681 if ("_AnnotationValue".equals(codeString)) 1682 return _ANNOTATIONVALUE; 1683 if ("_CommonClinicalObservationValue".equals(codeString)) 1684 return _COMMONCLINICALOBSERVATIONVALUE; 1685 if ("_IndividualCaseSafetyReportValueDomains".equals(codeString)) 1686 return _INDIVIDUALCASESAFETYREPORTVALUEDOMAINS; 1687 if ("_IndicationValue".equals(codeString)) 1688 return _INDICATIONVALUE; 1689 throw new FHIRException("Unknown V3ObservationValue code '"+codeString+"'"); 1690 } 1691 public String toCode() { 1692 switch (this) { 1693 case _ACTCOVERAGEASSESSMENTOBSERVATIONVALUE: return "_ActCoverageAssessmentObservationValue"; 1694 case _ACTFINANCIALSTATUSOBSERVATIONVALUE: return "_ActFinancialStatusObservationValue"; 1695 case ASSET: return "ASSET"; 1696 case ANNUITY: return "ANNUITY"; 1697 case PROP: return "PROP"; 1698 case RETACCT: return "RETACCT"; 1699 case TRUST: return "TRUST"; 1700 case INCOME: return "INCOME"; 1701 case CHILD: return "CHILD"; 1702 case DISABL: return "DISABL"; 1703 case INVEST: return "INVEST"; 1704 case PAY: return "PAY"; 1705 case RETIRE: return "RETIRE"; 1706 case SPOUSAL: return "SPOUSAL"; 1707 case SUPPLE: return "SUPPLE"; 1708 case TAX: return "TAX"; 1709 case LIVEXP: return "LIVEXP"; 1710 case CLOTH: return "CLOTH"; 1711 case FOOD: return "FOOD"; 1712 case HEALTH: return "HEALTH"; 1713 case HOUSE: return "HOUSE"; 1714 case LEGAL: return "LEGAL"; 1715 case MORTG: return "MORTG"; 1716 case RENT: return "RENT"; 1717 case SUNDRY: return "SUNDRY"; 1718 case TRANS: return "TRANS"; 1719 case UTIL: return "UTIL"; 1720 case ELSTAT: return "ELSTAT"; 1721 case ADOPT: return "ADOPT"; 1722 case BTHCERT: return "BTHCERT"; 1723 case CCOC: return "CCOC"; 1724 case DRLIC: return "DRLIC"; 1725 case FOSTER: return "FOSTER"; 1726 case MEMBER: return "MEMBER"; 1727 case MIL: return "MIL"; 1728 case MRGCERT: return "MRGCERT"; 1729 case PASSPORT: return "PASSPORT"; 1730 case STUDENRL: return "STUDENRL"; 1731 case HLSTAT: return "HLSTAT"; 1732 case DISABLE: return "DISABLE"; 1733 case DRUG: return "DRUG"; 1734 case IVDRG: return "IVDRG"; 1735 case PGNT: return "PGNT"; 1736 case LIVDEP: return "LIVDEP"; 1737 case RELDEP: return "RELDEP"; 1738 case SPSDEP: return "SPSDEP"; 1739 case URELDEP: return "URELDEP"; 1740 case LIVSIT: return "LIVSIT"; 1741 case ALONE: return "ALONE"; 1742 case DEPCHD: return "DEPCHD"; 1743 case DEPSPS: return "DEPSPS"; 1744 case DEPYGCHD: return "DEPYGCHD"; 1745 case FAM: return "FAM"; 1746 case RELAT: return "RELAT"; 1747 case SPS: return "SPS"; 1748 case UNREL: return "UNREL"; 1749 case SOECSTAT: return "SOECSTAT"; 1750 case ABUSE: return "ABUSE"; 1751 case HMLESS: return "HMLESS"; 1752 case ILGIM: return "ILGIM"; 1753 case INCAR: return "INCAR"; 1754 case PROB: return "PROB"; 1755 case REFUG: return "REFUG"; 1756 case UNEMPL: return "UNEMPL"; 1757 case _ALLERGYTESTVALUE: return "_AllergyTestValue"; 1758 case A0: return "A0"; 1759 case A1: return "A1"; 1760 case A2: return "A2"; 1761 case A3: return "A3"; 1762 case A4: return "A4"; 1763 case _COMPOSITEMEASURESCORING: return "_CompositeMeasureScoring"; 1764 case ALLORNONESCR: return "ALLORNONESCR"; 1765 case LINEARSCR: return "LINEARSCR"; 1766 case OPPORSCR: return "OPPORSCR"; 1767 case WEIGHTSCR: return "WEIGHTSCR"; 1768 case _COVERAGELIMITOBSERVATIONVALUE: return "_CoverageLimitObservationValue"; 1769 case _COVERAGELEVELOBSERVATIONVALUE: return "_CoverageLevelObservationValue"; 1770 case ADC: return "ADC"; 1771 case CHD: return "CHD"; 1772 case DEP: return "DEP"; 1773 case DP: return "DP"; 1774 case ECH: return "ECH"; 1775 case FLY: return "FLY"; 1776 case IND: return "IND"; 1777 case SSP: return "SSP"; 1778 case _CRITICALITYOBSERVATIONVALUE: return "_CriticalityObservationValue"; 1779 case CRITH: return "CRITH"; 1780 case CRITL: return "CRITL"; 1781 case CRITU: return "CRITU"; 1782 case _EMPLOYMENTSTATUS: return "_EmploymentStatus"; 1783 case EMPLOYED: return "Employed"; 1784 case NOTINLABORFORCE: return "NotInLaborForce"; 1785 case UNEMPLOYED: return "Unemployed"; 1786 case _GENETICOBSERVATIONVALUE: return "_GeneticObservationValue"; 1787 case HOMOZYGOTE: return "Homozygote"; 1788 case _OBSERVATIONMEASURESCORING: return "_ObservationMeasureScoring"; 1789 case COHORT: return "COHORT"; 1790 case CONTVAR: return "CONTVAR"; 1791 case PROPOR: return "PROPOR"; 1792 case RATIO: return "RATIO"; 1793 case _OBSERVATIONMEASURETYPE: return "_ObservationMeasureType"; 1794 case COMPOSITE: return "COMPOSITE"; 1795 case EFFICIENCY: return "EFFICIENCY"; 1796 case EXPERIENCE: return "EXPERIENCE"; 1797 case OUTCOME: return "OUTCOME"; 1798 case INTERMOM: return "INTERM-OM"; 1799 case PROPM: return "PRO-PM"; 1800 case PROCESS: return "PROCESS"; 1801 case APPROPRIATE: return "APPROPRIATE"; 1802 case RESOURCE: return "RESOURCE"; 1803 case STRUCTURE: return "STRUCTURE"; 1804 case _OBSERVATIONPOPULATIONINCLUSION: return "_ObservationPopulationInclusion"; 1805 case DENEX: return "DENEX"; 1806 case DENEXCEP: return "DENEXCEP"; 1807 case DENOM: return "DENOM"; 1808 case IP: return "IP"; 1809 case IPP: return "IPP"; 1810 case MSRPOPL: return "MSRPOPL"; 1811 case NUMER: return "NUMER"; 1812 case NUMEX: return "NUMEX"; 1813 case _PARTIALCOMPLETIONSCALE: return "_PartialCompletionScale"; 1814 case G: return "G"; 1815 case LE: return "LE"; 1816 case ME: return "ME"; 1817 case MI: return "MI"; 1818 case N: return "N"; 1819 case S: return "S"; 1820 case _SECURITYOBSERVATIONVALUE: return "_SecurityObservationValue"; 1821 case _SECINTOBV: return "_SECINTOBV"; 1822 case _SECALTINTOBV: return "_SECALTINTOBV"; 1823 case ABSTRED: return "ABSTRED"; 1824 case AGGRED: return "AGGRED"; 1825 case ANONYED: return "ANONYED"; 1826 case MAPPED: return "MAPPED"; 1827 case MASKED: return "MASKED"; 1828 case PSEUDED: return "PSEUDED"; 1829 case REDACTED: return "REDACTED"; 1830 case SUBSETTED: return "SUBSETTED"; 1831 case SYNTAC: return "SYNTAC"; 1832 case TRSLT: return "TRSLT"; 1833 case VERSIONED: return "VERSIONED"; 1834 case _SECDATINTOBV: return "_SECDATINTOBV"; 1835 case CRYTOHASH: return "CRYTOHASH"; 1836 case DIGSIG: return "DIGSIG"; 1837 case _SECINTCONOBV: return "_SECINTCONOBV"; 1838 case HRELIABLE: return "HRELIABLE"; 1839 case RELIABLE: return "RELIABLE"; 1840 case UNCERTREL: return "UNCERTREL"; 1841 case UNRELIABLE: return "UNRELIABLE"; 1842 case _SECINTPRVOBV: return "_SECINTPRVOBV"; 1843 case _SECINTPRVABOBV: return "_SECINTPRVABOBV"; 1844 case CLINAST: return "CLINAST"; 1845 case DEVAST: return "DEVAST"; 1846 case HCPAST: return "HCPAST"; 1847 case PACQAST: return "PACQAST"; 1848 case PATAST: return "PATAST"; 1849 case PAYAST: return "PAYAST"; 1850 case PROAST: return "PROAST"; 1851 case SDMAST: return "SDMAST"; 1852 case _SECINTPRVRBOBV: return "_SECINTPRVRBOBV"; 1853 case CLINRPT: return "CLINRPT"; 1854 case DEVRPT: return "DEVRPT"; 1855 case HCPRPT: return "HCPRPT"; 1856 case PACQRPT: return "PACQRPT"; 1857 case PATRPT: return "PATRPT"; 1858 case PAYRPT: return "PAYRPT"; 1859 case PRORPT: return "PRORPT"; 1860 case SDMRPT: return "SDMRPT"; 1861 case SECTRSTOBV: return "SECTRSTOBV"; 1862 case TRSTACCRDOBV: return "TRSTACCRDOBV"; 1863 case TRSTAGREOBV: return "TRSTAGREOBV"; 1864 case TRSTCERTOBV: return "TRSTCERTOBV"; 1865 case TRSTLOAOBV: return "TRSTLOAOBV"; 1866 case LOAAN: return "LOAAN"; 1867 case LOAAN1: return "LOAAN1"; 1868 case LOAAN2: return "LOAAN2"; 1869 case LOAAN3: return "LOAAN3"; 1870 case LOAAN4: return "LOAAN4"; 1871 case LOAAP: return "LOAAP"; 1872 case LOAAP1: return "LOAAP1"; 1873 case LOAAP2: return "LOAAP2"; 1874 case LOAAP3: return "LOAAP3"; 1875 case LOAAP4: return "LOAAP4"; 1876 case LOAAS: return "LOAAS"; 1877 case LOAAS1: return "LOAAS1"; 1878 case LOAAS2: return "LOAAS2"; 1879 case LOAAS3: return "LOAAS3"; 1880 case LOAAS4: return "LOAAS4"; 1881 case LOACM: return "LOACM"; 1882 case LOACM1: return "LOACM1"; 1883 case LOACM2: return "LOACM2"; 1884 case LOACM3: return "LOACM3"; 1885 case LOACM4: return "LOACM4"; 1886 case LOAID: return "LOAID"; 1887 case LOAID1: return "LOAID1"; 1888 case LOAID2: return "LOAID2"; 1889 case LOAID3: return "LOAID3"; 1890 case LOAID4: return "LOAID4"; 1891 case LOANR: return "LOANR"; 1892 case LOANR1: return "LOANR1"; 1893 case LOANR2: return "LOANR2"; 1894 case LOANR3: return "LOANR3"; 1895 case LOANR4: return "LOANR4"; 1896 case LOARA: return "LOARA"; 1897 case LOARA1: return "LOARA1"; 1898 case LOARA2: return "LOARA2"; 1899 case LOARA3: return "LOARA3"; 1900 case LOARA4: return "LOARA4"; 1901 case LOATK: return "LOATK"; 1902 case LOATK1: return "LOATK1"; 1903 case LOATK2: return "LOATK2"; 1904 case LOATK3: return "LOATK3"; 1905 case LOATK4: return "LOATK4"; 1906 case TRSTMECOBV: return "TRSTMECOBV"; 1907 case _SEVERITYOBSERVATION: return "_SeverityObservation"; 1908 case H: return "H"; 1909 case L: return "L"; 1910 case M: return "M"; 1911 case _SUBJECTBODYPOSITION: return "_SubjectBodyPosition"; 1912 case LLD: return "LLD"; 1913 case PRN: return "PRN"; 1914 case RLD: return "RLD"; 1915 case SFWL: return "SFWL"; 1916 case SIT: return "SIT"; 1917 case STN: return "STN"; 1918 case SUP: return "SUP"; 1919 case RTRD: return "RTRD"; 1920 case TRD: return "TRD"; 1921 case _VERIFICATIONOUTCOMEVALUE: return "_VerificationOutcomeValue"; 1922 case ACT: return "ACT"; 1923 case ACTPEND: return "ACTPEND"; 1924 case ELG: return "ELG"; 1925 case INACT: return "INACT"; 1926 case INPNDINV: return "INPNDINV"; 1927 case INPNDUPD: return "INPNDUPD"; 1928 case NELG: return "NELG"; 1929 case _WORKSCHEDULE: return "_WorkSchedule"; 1930 case DS: return "DS"; 1931 case EMS: return "EMS"; 1932 case ES: return "ES"; 1933 case NS: return "NS"; 1934 case RSWN: return "RSWN"; 1935 case RSWON: return "RSWON"; 1936 case SS: return "SS"; 1937 case VLS: return "VLS"; 1938 case VS: return "VS"; 1939 case _ANNOTATIONVALUE: return "_AnnotationValue"; 1940 case _COMMONCLINICALOBSERVATIONVALUE: return "_CommonClinicalObservationValue"; 1941 case _INDIVIDUALCASESAFETYREPORTVALUEDOMAINS: return "_IndividualCaseSafetyReportValueDomains"; 1942 case _INDICATIONVALUE: return "_IndicationValue"; 1943 default: return "?"; 1944 } 1945 } 1946 public String getSystem() { 1947 return "http://terminology.hl7.org/CodeSystem/v3-ObservationValue"; 1948 } 1949 public String getDefinition() { 1950 switch (this) { 1951 case _ACTCOVERAGEASSESSMENTOBSERVATIONVALUE: return "Codes specify the category of observation, evidence, or document used to assess for services, e.g., discharge planning, or to establish eligibility for coverage under a policy or program. The type of evidence is coded as observation values."; 1952 case _ACTFINANCIALSTATUSOBSERVATIONVALUE: return "Code specifying financial indicators used to assess or establish eligibility for coverage under a policy or program; e.g., pay stub; tax or income document; asset document; living expenses."; 1953 case ASSET: return "Codes specifying asset indicators used to assess or establish eligibility for coverage under a policy or program."; 1954 case ANNUITY: return "Indicator of annuity ownership or status as beneficiary."; 1955 case PROP: return "Indicator of real property ownership, e.g., deed or real estate contract."; 1956 case RETACCT: return "Indicator of retirement investment account ownership."; 1957 case TRUST: return "Indicator of status as trust beneficiary."; 1958 case INCOME: return "Code specifying income indicators used to assess or establish eligibility for coverage under a policy or program; e.g., pay or pension check, child support payments received or provided, and taxes paid."; 1959 case CHILD: return "Indicator of child support payments received or provided."; 1960 case DISABL: return "Indicator of disability income replacement payment."; 1961 case INVEST: return "Indicator of investment income, e.g., dividend check, annuity payment; real estate rent, investment divestiture proceeds; trust or endowment check."; 1962 case PAY: return "Indicator of paid employment, e.g., letter of hire, contract, employer letter; copy of pay check or pay stub."; 1963 case RETIRE: return "Indicator of retirement payment, e.g., pension check."; 1964 case SPOUSAL: return "Indicator of spousal or partner support payments received or provided; e.g., alimony payment; support stipulations in a divorce settlement."; 1965 case SUPPLE: return "Indicator of income supplement, e.g., gifting, parental income support; stipend, or grant."; 1966 case TAX: return "Indicator of tax obligation or payment, e.g., statement of taxable income."; 1967 case LIVEXP: return "Codes specifying living expense indicators used to assess or establish eligibility for coverage under a policy or program."; 1968 case CLOTH: return "Indicator of clothing expenses."; 1969 case FOOD: return "Indicator of transportation expenses."; 1970 case HEALTH: return "Indicator of health expenses; including medication costs, health service costs, financial participations, and health coverage premiums."; 1971 case HOUSE: return "Indicator of housing expense, e.g., household appliances, fixtures, furnishings, and maintenance and repairs."; 1972 case LEGAL: return "Indicator of legal expenses."; 1973 case MORTG: return "Indicator of mortgage amount, interest, and payments."; 1974 case RENT: return "Indicator of rental or lease payments."; 1975 case SUNDRY: return "Indicator of transportation expenses."; 1976 case TRANS: return "Indicator of transportation expenses, e.g., vehicle payments, vehicle insurance, vehicle fuel, and vehicle maintenance and repairs."; 1977 case UTIL: return "Indicator of transportation expenses."; 1978 case ELSTAT: return "Code specifying eligibility indicators used to assess or establish eligibility for coverage under a policy or program eligibility status, e.g., certificates of creditable coverage; student enrollment; adoption, marriage or birth certificate."; 1979 case ADOPT: return "Indicator of adoption."; 1980 case BTHCERT: return "Indicator of birth."; 1981 case CCOC: return "Indicator of creditable coverage."; 1982 case DRLIC: return "Indicator of driving status."; 1983 case FOSTER: return "Indicator of foster child status."; 1984 case MEMBER: return "Indicator of status as covered member under a policy or program, e.g., member id card or coverage document."; 1985 case MIL: return "Indicator of military status."; 1986 case MRGCERT: return "Indicator of marriage status."; 1987 case PASSPORT: return "Indicator of citizenship."; 1988 case STUDENRL: return "Indicator of student status."; 1989 case HLSTAT: return "Code specifying non-clinical indicators related to health status used to assess or establish eligibility for coverage under a policy or program, e.g., pregnancy, disability, drug use, mental health issues."; 1990 case DISABLE: return "Indication of disability."; 1991 case DRUG: return "Indication of drug use."; 1992 case IVDRG: return "Indication of IV drug use ."; 1993 case PGNT: return "Non-clinical report of pregnancy."; 1994 case LIVDEP: return "Code specifying observations related to living dependency, such as dependent upon spouse for activities of daily living."; 1995 case RELDEP: return "Continued living in private residence requires functional and health care assistance from one or more relatives."; 1996 case SPSDEP: return "Continued living in private residence requires functional and health care assistance from spouse or life partner."; 1997 case URELDEP: return "Continued living in private residence requires functional and health care assistance from one or more unrelated persons."; 1998 case LIVSIT: return "Code specifying observations related to living situation for a person in a private residence."; 1999 case ALONE: return "Living alone. Maps to PD1-2 Living arrangement (IS) 00742 [A]"; 2000 case DEPCHD: return "Living with one or more dependent children requiring moderate supervision."; 2001 case DEPSPS: return "Living with disabled spouse requiring functional and health care assistance"; 2002 case DEPYGCHD: return "Living with one or more dependent children requiring intensive supervision"; 2003 case FAM: return "Living with family. Maps to PD1-2 Living arrangement (IS) 00742 [F]"; 2004 case RELAT: return "Living with one or more relatives. Maps to PD1-2 Living arrangement (IS) 00742 [R]"; 2005 case SPS: return "Living only with spouse or life partner. Maps to PD1-2 Living arrangement (IS) 00742 [S]"; 2006 case UNREL: return "Living with one or more unrelated persons."; 2007 case SOECSTAT: return "Code specifying observations or indicators related to socio-economic status used to assess to assess for services, e.g., discharge planning, or to establish eligibility for coverage under a policy or program."; 2008 case ABUSE: return "Indication of abuse victim."; 2009 case HMLESS: return "Indication of status as homeless."; 2010 case ILGIM: return "Indication of status as illegal immigrant."; 2011 case INCAR: return "Indication of status as incarcerated."; 2012 case PROB: return "Indication of probation status."; 2013 case REFUG: return "Indication of refugee status."; 2014 case UNEMPL: return "Indication of unemployed status."; 2015 case _ALLERGYTESTVALUE: return "Indicates the result of a particular allergy test. E.g. Negative, Mild, Moderate, Severe"; 2016 case A0: return "Description:Patient exhibits no reaction to the challenge agent."; 2017 case A1: return "Description:Patient exhibits a minimal reaction to the challenge agent."; 2018 case A2: return "Description:Patient exhibits a mild reaction to the challenge agent."; 2019 case A3: return "Description:Patient exhibits moderate reaction to the challenge agent."; 2020 case A4: return "Description:Patient exhibits a severe reaction to the challenge agent."; 2021 case _COMPOSITEMEASURESCORING: return "Observation values that communicate the method used in a quality measure to combine the component measure results included in an composite measure."; 2022 case ALLORNONESCR: return "Code specifying that the measure uses all-or-nothing scoring. All-or-nothing scoring places an individual in the numerator of the composite measure if and only if they are in the numerator of all component measures in which they are in the denominator."; 2023 case LINEARSCR: return "Code specifying that the measure uses linear scoring. Linear scoring computes the fraction of component measures in which the individual appears in the numerator, giving equal weight to each component measure."; 2024 case OPPORSCR: return "Code specifying that the measure uses opportunity-based scoring. In opportunity-based scoring the measure score is determined by combining the denominator and numerator of each component measure to determine an overall composite score."; 2025 case WEIGHTSCR: return "Code specifying that the measure uses weighted scoring. Weighted scoring assigns a factor to each component measure to weight that measure's contribution to the overall score."; 2026 case _COVERAGELIMITOBSERVATIONVALUE: return "Description:Coded observation values for coverage limitations, for e.g., types of claims or types of parties covered under a policy or program."; 2027 case _COVERAGELEVELOBSERVATIONVALUE: return "Description:Coded observation values for types of covered parties under a policy or program based on their personal relationships or employment status."; 2028 case ADC: return "Description:Child over an age as specified by coverage policy or program, e.g., student, differently abled, and income dependent."; 2029 case CHD: return "Description:Dependent biological, adopted, foster child as specified by coverage policy or program."; 2030 case DEP: return "Description:Person requiring functional and/or financial assistance from another person as specified by coverage policy or program."; 2031 case DP: return "Description:Persons registered as a family unit in a domestic partner registry as specified by law and by coverage policy or program."; 2032 case ECH: return "Description:An individual employed by an employer who receive remuneration in wages, salary, commission, tips, piece-rates, or pay-in-kind through the employeraTMs payment system (i.e., not a contractor) as specified by coverage policy or program."; 2033 case FLY: return "Description:As specified by coverage policy or program."; 2034 case IND: return "Description:Person as specified by coverage policy or program."; 2035 case SSP: return "Description:A pair of people of the same gender who live together as a family as specified by coverage policy or program, e.g., Naomi and Ruth from the Book of Ruth; Socrates and Alcibiades"; 2036 case _CRITICALITYOBSERVATIONVALUE: return "A clinical judgment as to the worst case result of a future exposure (including substance administration). When the worst case result is assessed to have a life-threatening or organ system threatening potential, it is considered to be of high criticality."; 2037 case CRITH: return "Worst case result of a future exposure is assessed to be life-threatening or having high potential for organ system failure."; 2038 case CRITL: return "Worst case result of a future exposure is not assessed to be life-threatening or having high potential for organ system failure."; 2039 case CRITU: return "Unable to assess the worst case result of a future exposure."; 2040 case _EMPLOYMENTSTATUS: return "Concepts representing whether a person does or does not currently have a job or is not currently in the labor pool seeking employment."; 2041 case EMPLOYED: return "Individuals who, during the last week: a) did any work for at least 1 hour as paid or unpaid employees of a business or government organization; worked in their own businesses, professions, or on their own farms; or b) were not working, but who have a job or business from which the individual was temporarily absent because of vacation, illness, bad weather, childcare problems, maternity or paternity leave, labor-management dispute, job training, or other family or personal reasons, regardless of whether or not they were paid for the time off or were seeking other jobs."; 2042 case NOTINLABORFORCE: return "Persons not classified as employed or unemployed, meaning those who have no job and are not looking for one."; 2043 case UNEMPLOYED: return "Persons who currently have no employment, but are available for work and have made specific efforts to find employment."; 2044 case _GENETICOBSERVATIONVALUE: return "Description: The domain contains genetic analysis specific observation values, e.g. Homozygote, Heterozygote, etc."; 2045 case HOMOZYGOTE: return "Description: An individual having different alleles at one or more loci regarding a specific character"; 2046 case _OBSERVATIONMEASURESCORING: return "Observation values used to indicate the type of scoring (e.g. proportion, ratio) used by a health quality measure."; 2047 case COHORT: return "A measure in which either short-term cross-section or long-term longitudinal analysis is performed over a group of subjects defined by a set of common properties or defining characteristics (e.g., Male smokers between the ages of 40 and 50 years, exposure to treatment, exposure duration)."; 2048 case CONTVAR: return "A measure score in which each individual value for the measure can fall anywhere along a continuous scale (e.g., mean time to thrombolytics which aggregates the time in minutes from a case presenting with chest pain to the time of administration of thrombolytics)."; 2049 case PROPOR: return "A score derived by dividing the number of cases that meet a criterion for quality (the numerator) by the number of eligible cases within a given time frame (the denominator) where the numerator cases are a subset of the denominator cases (e.g., percentage of eligible women with a mammogram performed in the last year)."; 2050 case RATIO: return "A score that may have a value of zero or greater that is derived by dividing a count of one type of data by a count of another type of data (e.g., the number of patients with central lines who develop infection divided by the number of central line days)."; 2051 case _OBSERVATIONMEASURETYPE: return "Observation values used to indicate what kind of health quality measure is used."; 2052 case COMPOSITE: return "A measure that is composed from one or more other measures and indicates an overall summary of those measures."; 2053 case EFFICIENCY: return "A measure related to the efficiency of medical treatment."; 2054 case EXPERIENCE: return "A measure related to the level of patient engagement or patient experience of care."; 2055 case OUTCOME: return "A measure that indicates the result of the performance (or non-performance) of a function or process."; 2056 case INTERMOM: return "A measure that evaluates the change over time of a physiologic state observable that is associated with a specific long-term health outcome."; 2057 case PROPM: return "A measure that is a comparison of patient reported outcomes for a single or multiple patients collected via an instrument specifically designed to obtain input directly from patients."; 2058 case PROCESS: return "A measure which focuses on a process which leads to a certain outcome, meaning that a scientific basis exists for believing that the process, when executed well, will increase the probability of achieving a desired outcome."; 2059 case APPROPRIATE: return "A measure that assesses the use of one or more processes where the expected health benefit exceeds the expected negative consequences."; 2060 case RESOURCE: return "A measure related to the extent of use of clinical resources or cost of care."; 2061 case STRUCTURE: return "A measure related to the structure of patient care."; 2062 case _OBSERVATIONPOPULATIONINCLUSION: return "Observation values used to assert various populations that a subject falls into."; 2063 case DENEX: return "Patients who should be removed from the eMeasure population and denominator before determining if numerator criteria are met. Denominator exclusions are used in proportion and ratio measures to help narrow the denominator."; 2064 case DENEXCEP: return "Denominator exceptions are those conditions that should remove a patient, procedure or unit of measurement from the denominator only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures. Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories:\r\n\n \n Medical reasons\n Patient reasons\n System reasons"; 2065 case DENOM: return "It can be the same as the initial patient population or a subset of the initial patient population to further constrain the population for the purpose of the eMeasure. Different measures within an eMeasure set may have different Denominators. Continuous Variable eMeasures do not have a Denominator, but instead define a Measure Population."; 2066 case IP: return "The initial population refers to all entities to be evaluated by a specific quality measure who share a common set of specified characteristics within a specific measurement set to which a given measure belongs."; 2067 case IPP: return "The initial patient population refers to all patients to be evaluated by a specific quality measure who share a common set of specified characteristics within a specific measurement set to which a given measure belongs. Details often include information based upon specific age groups, diagnoses, diagnostic and procedure codes, and enrollment periods."; 2068 case MSRPOPL: return "Measure population is used only in continuous variable eMeasures. It is a narrative description of the eMeasure population. \n(e.g., all patients seen in the Emergency Department during the measurement period)."; 2069 case NUMER: return "Numerators are used in proportion and ratio eMeasures. In proportion measures the numerator criteria are the processes or outcomes expected for each patient, procedure, or other unit of measurement defined in the denominator. In ratio measures the numerator is related, but not directly derived from the denominator (e.g., a numerator listing the number of central line blood stream infections and a denominator indicating the days per thousand of central line usage in a specific time period)."; 2070 case NUMEX: return "Numerator Exclusions are used only in ratio eMeasures to define instances that should not be included in the numerator data. (e.g., if the number of central line blood stream infections per 1000 catheter days were to exclude infections with a specific bacterium, that bacterium would be listed as a numerator exclusion.)"; 2071 case _PARTIALCOMPLETIONSCALE: return "PartialCompletionScale"; 2072 case G: return "Value for Act.partialCompletionCode attribute that implies 81-99% completion"; 2073 case LE: return "Value for Act.partialCompletionCode attribute that implies 61-80% completion"; 2074 case ME: return "Value for Act.partialCompletionCode attribute that implies 41-60% completion"; 2075 case MI: return "Value for Act.partialCompletionCode attribute that implies 1-20% completion"; 2076 case N: return "Value for Act.partialCompletionCode attribute that implies 0% completion"; 2077 case S: return "Value for Act.partialCompletionCode attribute that implies 21-40% completion"; 2078 case _SECURITYOBSERVATIONVALUE: return "Observation values used to indicate security observation metadata."; 2079 case _SECINTOBV: return "Abstract security observation values used to indicate security integrity metadata.\r\n\n \n Examples: Codes conveying integrity status, integrity confidence, and provenance."; 2080 case _SECALTINTOBV: return "Abstract security metadata observation values used to indicate mechanism used for authorized alteration of an IT resource (data, information object, service, or system capability)"; 2081 case ABSTRED: return "Security metadata observation values used to indicate the use of a more abstract version of the content, e.g., replacing exact value of an age or date field with a range, or remove the left digits of a credit card number or SSN."; 2082 case AGGRED: return "Security metadata observation values used to indicate the use of an algorithmic combination of actual values with the result of an aggregate function, e.g., average, sum, or count in order to limit disclosure of an IT resource (data, information object, service, or system capability) to the minimum necessary."; 2083 case ANONYED: return "Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) by used to indicate the mechanism by which software systems can strip portions of the resource that could allow the identification of the source of the information or the information subject. No key to relink the data is retained."; 2084 case MAPPED: return "Security metadata observation value used to indicate that the IT resource semantic content has been transformed from one encoding to another.\r\n\n \n Usage Note: \"MAP\" code does not indicate the semantic fidelity of the transformed content.\r\n\n To indicate semantic fidelity for maps of HL7 to other code systems, this security alteration integrity observation may be further specified using an Act valued with Value Set: MapRelationship (2.16.840.1.113883.1.11.11052).\r\n\n Semantic fidelity of the mapped IT Resource may also be indicated using a SecurityIntegrityConfidenceObservation."; 2085 case MASKED: return "Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) by indicating the mechanism by which software systems can make data unintelligible (that is, as unreadable and unusable by algorithmically transforming plaintext into ciphertext) such that it can only be accessed or used by authorized users. An authorized user may be provided a key to decrypt per license or \"shared secret\".\r\n\n \n Usage Note: \"MASKED\" may be used, per applicable policy, as a flag to indicate to a user or receiver that some portion of an IT resource has been further encrypted, and may be accessed only by an authorized user or receiver to which a decryption key is provided."; 2086 case PSEUDED: return "Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability), by indicating the mechanism by which software systems can strip portions of the resource that could allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject.\r\n\n \n Rationale: Personal data which has been processed to make it impossible to know whose data it is. Used particularly for secondary use of health data. In some cases, it may be possible for authorized individuals to restore the identity of the individual, e.g.,for public health case management. Based on ISO/TS 25237:2008 Health informatics—Pseudonymization"; 2087 case REDACTED: return "Security metadata observation value used to indicate the mechanism by which software systems can filter an IT resource (data, information object, service, or system capability) to remove any portion of the resource that is not authorized to be access, used, or disclosed.\r\n\n \n Usage Note: \"REDACTED\" may be used, per applicable policy, as a flag to indicate to a user or receiver that some portion of an IT resource has filtered and not included in the content accessed or received."; 2088 case SUBSETTED: return "Metadata observation used to indicate that some information has been removed from the source object when the view this object contains was constructed because of configuration options when the view was created. The content may not be suitable for use as the basis of a record update\r\n\n \n Usage Note: This is not suitable to be used when information is removed for security reasons - see the code REDACTED for this use."; 2089 case SYNTAC: return "Security metadata observation value used to indicate that the IT resource syntax has been transformed from one syntactical representation to another. \r\n\n \n Usage Note: \"SYNTAC\" code does not indicate the syntactical correctness of the syntactically transformed IT resource."; 2090 case TRSLT: return "Security metadata observation value used to indicate that the IT resource has been translated from one human language to another. \r\n\n \n Usage Note: \"TRSLT\" does not indicate the fidelity of the translation or the languages translated.\r\n\n The fidelity of the IT Resource translation may be indicated using a SecurityIntegrityConfidenceObservation.\r\n\n To indicate languages, use the Value Set:HumanLanguage (2.16.840.1.113883.1.11.11526)"; 2091 case VERSIONED: return "Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) which indicates that the resource only retains versions of an IT resource for access and use per applicable policy\r\n\n \n Usage Note: When this code is used, expectation is that the system has removed historical versions of the data that falls outside the time period deemed to be the effective time of the applicable version."; 2092 case _SECDATINTOBV: return "Abstract security observation values used to indicate data integrity metadata.\r\n\n \n Examples: Codes conveying the mechanism used to preserve the accuracy and consistency of an IT resource such as a digital signature and a cryptographic hash function."; 2093 case CRYTOHASH: return "Security metadata observation value used to indicate the mechanism by which software systems can establish that data was not modified in transit.\r\n\n \n Rationale: This definition is intended to align with the ISO 22600-2 3.3.19 definition of cryptographic checkvalue: Information which is derived by performing a cryptographic transformation (see cryptography) on the data unit. The derivation of the checkvalue may be performed in one or more steps and is a result of a mathematical function of the key and a data unit. It is usually used to check the integrity of a data unit.\r\n\n \n Examples: \n \r\n\n \n SHA-1\n SHA-2 (Secure Hash Algorithm)"; 2094 case DIGSIG: return "Security metadata observation value used to indicate the mechanism by which software systems use digital signature to establish that data has not been modified. \r\n\n \n Rationale: This definition is intended to align with the ISO 22600-2 3.3.26 definition of digital signature: Data appended to, or a cryptographic transformation (see cryptography) of, a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g., by the recipient."; 2095 case _SECINTCONOBV: return "Abstract security observation value used to indicate integrity confidence metadata.\r\n\n \n Examples: Codes conveying the level of reliability and trustworthiness of an IT resource."; 2096 case HRELIABLE: return "Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be very high."; 2097 case RELIABLE: return "Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be adequate."; 2098 case UNCERTREL: return "Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be uncertain."; 2099 case UNRELIABLE: return "Security metadata observation value used to indicate that the veracity or trustworthiness of an IT resource (data, information object, service, or system capability) for a specified purpose of use is perceived to be or deemed by policy to be inadequate."; 2100 case _SECINTPRVOBV: return "Abstract security metadata observation value used to indicate the provenance of an IT resource (data, information object, service, or system capability).\r\n\n \n Examples: Codes conveying the provenance metadata about the entity reporting an IT resource."; 2101 case _SECINTPRVABOBV: return "Abstract security provenance metadata observation value used to indicate the entity that asserted an IT resource (data, information object, service, or system capability).\r\n\n \n Examples: Codes conveying the provenance metadata about the entity asserting the resource."; 2102 case CLINAST: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a clinician."; 2103 case DEVAST: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a device."; 2104 case HCPAST: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a healthcare professional."; 2105 case PACQAST: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a patient acquaintance."; 2106 case PATAST: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a patient."; 2107 case PAYAST: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a payer."; 2108 case PROAST: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a professional."; 2109 case SDMAST: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a substitute decision maker."; 2110 case _SECINTPRVRBOBV: return "Abstract security provenance metadata observation value used to indicate the entity that reported the resource (data, information object, service, or system capability).\r\n\n \n Examples: Codes conveying the provenance metadata about the entity reporting an IT resource."; 2111 case CLINRPT: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a clinician."; 2112 case DEVRPT: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a device."; 2113 case HCPRPT: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a healthcare professional."; 2114 case PACQRPT: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a patient acquaintance."; 2115 case PATRPT: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a patient."; 2116 case PAYRPT: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a payer."; 2117 case PRORPT: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a professional."; 2118 case SDMRPT: return "Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a substitute decision maker."; 2119 case SECTRSTOBV: return "Observation value used to indicate aspects of trust applicable to an IT resource (data, information object, service, or system capability)."; 2120 case TRSTACCRDOBV: return "Values for security trust accreditation metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework."; 2121 case TRSTAGREOBV: return "Values for security trust agreement metadata observation made about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1]\n[ISO IEC 10181-1]"; 2122 case TRSTCERTOBV: return "Values for security trust certificate metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1]\r\n\n For example, a Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. A particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. Another example is Cross Certification with Federal Bridge."; 2123 case TRSTLOAOBV: return "Values for security trust assurance metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol."; 2124 case LOAAN: return "The value assigned as the indicator of the digital quality or reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2]\r\n\n For example, the degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies]"; 2125 case LOAAN1: return "Indicator of low digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] \r\n\n The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] \r\n\n Low authentication level of assurance indicates that the relying party may have little or no confidence in the asserted identity's validity. Level 1 requires little or no confidence in the asserted identity. No identity proofing is required at this level, but the authentication mechanism should provide some assurance that the same claimant is accessing the protected transaction or data. A wide range of available authentication technologies can be employed and any of the token methods of Levels 2, 3, or 4, including Personal Identification Numbers (PINs), may be used. To be authenticated, the claimant must prove control of the token through a secure authentication protocol. At Level 1, long-term shared authentication secrets may be revealed to verifiers. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2126 case LOAAN2: return "Indicator of basic digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] \r\n\n The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies]\r\n\n Basic authentication level of assurance indicates that the relying party may have some confidence in the asserted identity's validity. Level 2 requires confidence that the asserted identity is accurate. Level 2 provides for single-factor remote network authentication, including identity-proofing requirements for presentation of identifying materials or information. A wide range of available authentication technologies can be employed, including any of the token methods of Levels 3 or 4, as well as passwords. Successful authentication requires that the claimant prove through a secure authentication protocol that the claimant controls the token. Eavesdropper, replay, and online guessing attacks are prevented. \nLong-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Approved cryptographic techniques are required. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2127 case LOAAN3: return "Indicator of medium digital quality or reliability of the digital reliability of verification and validation of the process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] \r\n\n The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] \r\n\n Medium authentication level of assurance indicates that the relying party may have high confidence in the asserted identity's validity. Level 3 is appropriate for transactions that need high confidence in the accuracy of the asserted identity. Level 3 provides multifactor remote network authentication. At this level, identity-proofing procedures require verification of identifying materials and information. Authentication is based on proof of possession of a key or password through a cryptographic protocol. Cryptographic strength mechanisms should protect the primary authentication token (a cryptographic key) against compromise by the protocol threats, including eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks. A minimum of two authentication factors is required. Three kinds of tokens may be used:\r\n\n \n \"soft\" cryptographic token, which has the key stored on a general-purpose computer, \n \"hard\" cryptographic token, which has the key stored on a special hardware device, and \n \"one-time password\" device token, which has symmetric key stored on a personal hardware device that is a cryptographic module validated at FIPS 140-2 Level 1 or higher. Validation testing of cryptographic modules and algorithms for conformance to Federal Information Processing Standard (FIPS) 140-2, Security Requirements for Cryptographic Modules, is managed by NIST.\n \n Authentication requires that the claimant prove control of the token through a secure authentication protocol. The token must be unlocked with a password or biometric representation, or a password must be used in a secure authentication protocol, to establish two-factor authentication. Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Approved cryptographic techniques are used for all operations. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2128 case LOAAN4: return "Indicator of high digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] \r\n\n The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies]\r\n\n High authentication level of assurance indicates that the relying party may have very high confidence in the asserted identity's validity. Level 4 is for transactions that need very high confidence in the accuracy of the asserted identity. Level 4 provides the highest practical assurance of remote network authentication. Authentication is based on proof of possession of a key through a cryptographic protocol. This level is similar to Level 3 except that only “hard� cryptographic tokens are allowed, cryptographic module validation requirements are strengthened, and subsequent critical data transfers must be authenticated via a key that is bound to the authentication process. The token should be a hardware cryptographic module validated at FIPS 140-2 Level 2 or higher overall with at least FIPS 140-2 Level 3 physical security. This level requires a physical token, which cannot readily be copied, and operator authentication at Level 2 and higher, and ensures good, two-factor remote authentication.\r\n\n Level 4 requires strong cryptographic authentication of all parties and all sensitive data transfers between the parties. Either public key or symmetric key technology may be used. Authentication requires that the claimant prove through a secure authentication protocol that the claimant controls the token. Eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks are prevented. Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Strong approved cryptographic techniques are used for all operations. All sensitive data transfers are cryptographically authenticated using keys bound to the authentication process. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2129 case LOAAP: return "The value assigned as the indicator of the digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]"; 2130 case LOAAP1: return "Indicator of the low digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]\r\n\n Low authentication process level of assurance indicates that (1) long-term shared authentication secrets may be revealed to verifiers; and (2) assertions and assertion references require protection from manufacture/modification and reuse attacks. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2131 case LOAAP2: return "Indicator of the basic digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]\r\n\n Basic authentication process level of assurance indicates that long-term shared authentication secrets are never revealed to any other party except Credential Service Provider (CSP). Sessions (temporary) shared secrets may be provided to independent verifiers by CSP. Long-term shared authentication secrets, if used, are never revealed to any other party except Verifiers operated by the Credential Service Provider (CSP); however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. In addition to Level 1 requirements, assertions are resistant to disclosure, redirection, capture and substitution attacks. Approved cryptographic techniques are required. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2132 case LOAAP3: return "Indicator of the medium digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]\r\n\n Medium authentication process level of assurance indicates that the token can be unlocked with password, biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication. Long-term shared authentication secrets are never revealed to any party except the Claimant and Credential Service Provider (CSP).\r\n\n Authentication requires that the Claimant prove, through a secure authentication protocol, that he or she controls the token. The Claimant unlocks the token with a password or biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication (through proof of possession of a physical or software token in combination with some memorized secret knowledge). Long-term shared authentication secrets, if used, are never revealed to any party except the Claimant and Verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. In addition to Level 2 requirements, assertions are protected against repudiation by the Verifier."; 2133 case LOAAP4: return "Indicator of the high digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]\r\n\n High authentication process level of assurance indicates all sensitive data transfer are cryptographically authenticated using keys bound to the authentication process. Level 4 requires strong cryptographic authentication of all communicating parties and all sensitive data transfers between the parties. Either public key or symmetric key technology may be used. Authentication requires that the Claimant prove through a secure authentication protocol that he or she controls the token. All protocol threats at Level 3 are required to be prevented at Level 4. Protocols shall also be strongly resistant to man-in-the-middle attacks. Long-term shared authentication secrets, if used, are never revealed to any party except the Claimant and Verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. Approved cryptographic techniques are used for all operations. All sensitive data transfers are cryptographically authenticated using keys bound to the authentication process. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2134 case LOAAS: return "The value assigned as the indicator of the high quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes."; 2135 case LOAAS1: return "Indicator of the low quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.\r\n\n Assertions and assertion references require protection from modification and reuse attacks. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2136 case LOAAS2: return "Indicator of the basic quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.\r\n\n Assertions are resistant to disclosure, redirection, capture and substitution attacks. Approved cryptographic techniques are required for all assertion protocols. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2137 case LOAAS3: return "Indicator of the medium quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.\r\n\n Assertions are protected against repudiation by the verifier. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2138 case LOAAS4: return "Indicator of the high quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.\r\n\n Strongly resistant to man-in-the-middle attacks. \"Bearer\" assertions are not used. \"Holder-of-key\" assertions may be used. RP maintains records of the assertions. [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"; 2139 case LOACM: return "Indicator of the digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and its binding to an identity. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2140 case LOACM1: return "Indicator of the low digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and its binding to an identity. Little or no confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include weak identity binding to tokens and plaintext passwords or secrets not transmitted across a network. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2141 case LOACM2: return "Indicator of the basic digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and its binding to an identity. Some confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Verification must prove claimant controls the token; token resists online guessing, replay, session hijacking, and eavesdropping attacks; and token is at least weakly resistant to man-in-the middle attacks. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2142 case LOACM3: return "Indicator of the medium digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and it’s binding to an identity. High confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Ownership of token verifiable through security authentication protocol and credential management protects against verifier impersonation attacks. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2143 case LOACM4: return "Indicator of the high digital quality or reliability of the activities performed by the Credential Service Provider (CSP) subsequent to electronic authentication registration, identity proofing and issuance activities to manage and safeguard the integrity of an issued credential and it’s binding to an identity. Very high confidence that an individual has maintained control over a token that has been entrusted to him or her and that that token has not been compromised. Characteristics include: Verifier can prove control of token through a secure protocol; credential management supports strong cryptographic authentication of all communication parties. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2144 case LOAID: return "Indicator of the quality or reliability in the process of ascertaining that an individual is who he or she claims to be."; 2145 case LOAID1: return "Indicator of low digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires that a continuity of identity be maintained but does not require identity proofing. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2146 case LOAID2: return "Indicator of some digital quality or reliability in the process of ascertaining that that an individual is who he or she claims to be. Requires identity proofing via presentation of identifying material or information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2147 case LOAID3: return "Indicator of high digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires identity proofing procedures for verification of identifying materials and information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2148 case LOAID4: return "Indicator of high digital quality or reliability in the process of ascertaining that an individual is who he or she claims to be. Requires identity proofing procedures for verification of identifying materials and information. [Based on Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2149 case LOANR: return "Indicator of the digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2]"; 2150 case LOANR1: return "Indicator of low digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2]"; 2151 case LOANR2: return "Indicator of basic digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2]"; 2152 case LOANR3: return "Indicator of medium digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2]"; 2153 case LOANR4: return "Indicator of high digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2]"; 2154 case LOARA: return "Indicator of the digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization’s security controls. [Based on NIST SP 800-63-2]"; 2155 case LOARA1: return "Indicator of low digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization’s security controls. [Based on NIST SP 800-63-2]"; 2156 case LOARA2: return "Indicator of basic digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization’s security controls. [Based on NIST SP 800-63-2]"; 2157 case LOARA3: return "Indicator of medium digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization’s security controls. [Based on NIST SP 800-63-2]"; 2158 case LOARA4: return "Indicator of high digital quality or reliability of the information exchange between network-connected devices where the information cannot be reliably protected end-to-end by a single organization's security controls. [Based on NIST SP 800-63-2]"; 2159 case LOATK: return "Indicator of the digital quality or reliability of single and multi-token authentication. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2160 case LOATK1: return "Indicator of the low digital quality or reliability of single and multi-token authentication. Permits the use of any of the token methods of Levels 2, 3, or 4. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2161 case LOATK2: return "Indicator of the basic digital quality or reliability of single and multi-token authentication. Requires single factor authentication using memorized secret tokens, pre-registered knowledge tokens, look-up secret tokens, out of band tokens, or single factor one-time password devices. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2162 case LOATK3: return "Indicator of the medium digital quality or reliability of single and multi-token authentication. Requires two authentication factors. Provides multi-factor remote network authentication. Permits multi-factor software cryptographic token. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2163 case LOATK4: return "Indicator of the high digital quality or reliability of single and multi-token authentication. Requires token that is a hardware cryptographic module validated at validated at Federal Information Processing Standard (FIPS) 140-2 Level 2 or higher overall with at least FIPS 140-2 Level 3 physical security. Level 4 token requirements can be met by using the PIV authentication key of a FIPS 201 compliant Personal Identity Verification (PIV) Card. [Electronic Authentication Guideline - Recommendations of the National Institute of Standards and Technology, NIST Special Publication 800-63-1, Dec 2011]"; 2164 case TRSTMECOBV: return "Values for security trust mechanism metadata observation made about a security architecture system component that supports enforcement of security policies."; 2165 case _SEVERITYOBSERVATION: return "Potential values for observations of severity."; 2166 case H: return "Indicates the condition may be life-threatening or has the potential to cause permanent injury."; 2167 case L: return "Indicates the condition may result in some adverse consequences but is unlikely to substantially affect the situation of the subject."; 2168 case M: return "Indicates the condition may result in noticable adverse adverse consequences but is unlikely to be life-threatening or cause permanent injury."; 2169 case _SUBJECTBODYPOSITION: return "Contains codes for defining the observed, physical position of a subject, such as during an observation, assessment, collection of a specimen, etc. ECG waveforms and vital signs, such as blood pressure, are two examples where a general, observed position typically needs to be noted."; 2170 case LLD: return "Lying on the left side."; 2171 case PRN: return "Lying with the front or ventral surface downward; lying face down."; 2172 case RLD: return "Lying on the right side."; 2173 case SFWL: return "A semi-sitting position in bed with the head of the bed elevated approximately 45 degrees."; 2174 case SIT: return "Resting the body on the buttocks, typically with upper torso erect or semi erect."; 2175 case STN: return "To be stationary, upright, vertical, on one's legs."; 2176 case SUP: return "supine"; 2177 case RTRD: return "Lying on the back, on an inclined plane, typically about 30-45 degrees with head raised and feet lowered."; 2178 case TRD: return "Lying on the back, on an inclined plane, typically about 30-45 degrees, with head lowered and feet raised."; 2179 case _VERIFICATIONOUTCOMEVALUE: return "Values for observations of verification act results\r\n\n \n Examples: Verified, not verified, verified with warning."; 2180 case ACT: return "Definition: Coverage is in effect for healthcare service(s) and/or product(s)."; 2181 case ACTPEND: return "Definition: Coverage is in effect for healthcare service(s) and/or product(s) - Pending Investigation"; 2182 case ELG: return "Definition: Coverage is in effect for healthcare service(s) and/or product(s)."; 2183 case INACT: return "Definition: Coverage is not in effect for healthcare service(s) and/or product(s)."; 2184 case INPNDINV: return "Definition: Coverage is not in effect for healthcare service(s) and/or product(s) - Pending Investigation."; 2185 case INPNDUPD: return "Definition: Coverage is not in effect for healthcare service(s) and/or product(s) - Pending Eligibility Update."; 2186 case NELG: return "Definition: Coverage is not in effect for healthcare service(s) and/or product(s). May optionally include reasons for the ineligibility."; 2187 case _WORKSCHEDULE: return "Concepts that describe an individual's typical arrangement of working hours for an occupation."; 2188 case DS: return "A person who is scheduled for work during daytime hours (for example between 6am and 6pm) on a regular basis."; 2189 case EMS: return "Consistent Early morning schedule of 13 hours or less per shift (between 2 am and 2 pm)"; 2190 case ES: return "A person who is scheduled for work during evening hours (for example between 2pm and midnight) on a regular basis."; 2191 case NS: return "Scheduled for work during nighttime hours (for example between 9pm and 8am) on a regular basis."; 2192 case RSWN: return "Scheduled for work times that change periodically between days, and/or evenings, and includes some night shifts."; 2193 case RSWON: return "Scheduled for work days/times that change periodically between days, but does not include night or evening work."; 2194 case SS: return "Shift consisting of two distinct work periods each day that are separated by a break of a few hours (for example 2 to 4 hours)"; 2195 case VLS: return "Shifts of 17 or more hours."; 2196 case VS: return "Irregular, unpredictable hours scheduled on a short notice (for example, less than 2 day notice): inconsistent schedule, on-call, as needed, as available."; 2197 case _ANNOTATIONVALUE: return "AnnotationValue"; 2198 case _COMMONCLINICALOBSERVATIONVALUE: return "Description:Used in a patient care message to value simple clinical (non-lab) observations."; 2199 case _INDIVIDUALCASESAFETYREPORTVALUEDOMAINS: return "This domain is established as a parent to a variety of value domains being defined to support the communication of Individual Case Safety Reports to regulatory bodies. Arguably, this aggregation is not taxonomically pure, but the grouping will facilitate the management of these domains."; 2200 case _INDICATIONVALUE: return "Indicates the specific observation result which is the reason for the action (prescription, lab test, etc.). E.g. Headache, Ear infection, planned diagnostic image (requiring contrast agent), etc."; 2201 default: return "?"; 2202 } 2203 } 2204 public String getDisplay() { 2205 switch (this) { 2206 case _ACTCOVERAGEASSESSMENTOBSERVATIONVALUE: return "ActCoverageAssessmentObservationValue"; 2207 case _ACTFINANCIALSTATUSOBSERVATIONVALUE: return "ActFinancialStatusObservationValue"; 2208 case ASSET: return "asset"; 2209 case ANNUITY: return "annuity"; 2210 case PROP: return "real property"; 2211 case RETACCT: return "retirement investment account"; 2212 case TRUST: return "trust"; 2213 case INCOME: return "income"; 2214 case CHILD: return "child support"; 2215 case DISABL: return "disability pay"; 2216 case INVEST: return "investment income"; 2217 case PAY: return "paid employment"; 2218 case RETIRE: return "retirement pay"; 2219 case SPOUSAL: return "spousal or partner support"; 2220 case SUPPLE: return "income supplement"; 2221 case TAX: return "tax obligation"; 2222 case LIVEXP: return "living expense"; 2223 case CLOTH: return "clothing expense"; 2224 case FOOD: return "food expense"; 2225 case HEALTH: return "health expense"; 2226 case HOUSE: return "household expense"; 2227 case LEGAL: return "legal expense"; 2228 case MORTG: return "mortgage"; 2229 case RENT: return "rent"; 2230 case SUNDRY: return "sundry expense"; 2231 case TRANS: return "transportation expense"; 2232 case UTIL: return "utility expense"; 2233 case ELSTAT: return "eligibility indicator"; 2234 case ADOPT: return "adoption document"; 2235 case BTHCERT: return "birth certificate"; 2236 case CCOC: return "creditable coverage document"; 2237 case DRLIC: return "driver license"; 2238 case FOSTER: return "foster child document"; 2239 case MEMBER: return "program or policy member"; 2240 case MIL: return "military identification"; 2241 case MRGCERT: return "marriage certificate"; 2242 case PASSPORT: return "passport"; 2243 case STUDENRL: return "student enrollment"; 2244 case HLSTAT: return "health status"; 2245 case DISABLE: return "disabled"; 2246 case DRUG: return "drug use"; 2247 case IVDRG: return "IV drug use"; 2248 case PGNT: return "pregnant"; 2249 case LIVDEP: return "living dependency"; 2250 case RELDEP: return "relative dependent"; 2251 case SPSDEP: return "spouse dependent"; 2252 case URELDEP: return "unrelated person dependent"; 2253 case LIVSIT: return "living situation"; 2254 case ALONE: return "alone"; 2255 case DEPCHD: return "dependent children"; 2256 case DEPSPS: return "dependent spouse"; 2257 case DEPYGCHD: return "dependent young children"; 2258 case FAM: return "live with family"; 2259 case RELAT: return "relative"; 2260 case SPS: return "spouse only"; 2261 case UNREL: return "unrelated person"; 2262 case SOECSTAT: return "socio economic status"; 2263 case ABUSE: return "abuse victim"; 2264 case HMLESS: return "homeless"; 2265 case ILGIM: return "illegal immigrant"; 2266 case INCAR: return "incarcerated"; 2267 case PROB: return "probation"; 2268 case REFUG: return "refugee"; 2269 case UNEMPL: return "unemployed"; 2270 case _ALLERGYTESTVALUE: return "AllergyTestValue"; 2271 case A0: return "no reaction"; 2272 case A1: return "minimal reaction"; 2273 case A2: return "mild reaction"; 2274 case A3: return "moderate reaction"; 2275 case A4: return "severe reaction"; 2276 case _COMPOSITEMEASURESCORING: return "CompositeMeasureScoring"; 2277 case ALLORNONESCR: return "All-or-nothing Scoring"; 2278 case LINEARSCR: return "Linear Scoring"; 2279 case OPPORSCR: return "Opportunity Scoring"; 2280 case WEIGHTSCR: return "Weighted Scoring"; 2281 case _COVERAGELIMITOBSERVATIONVALUE: return "CoverageLimitObservationValue"; 2282 case _COVERAGELEVELOBSERVATIONVALUE: return "CoverageLevelObservationValue"; 2283 case ADC: return "adult child"; 2284 case CHD: return "child"; 2285 case DEP: return "dependent"; 2286 case DP: return "domestic partner"; 2287 case ECH: return "employee"; 2288 case FLY: return "family coverage"; 2289 case IND: return "individual"; 2290 case SSP: return "same sex partner"; 2291 case _CRITICALITYOBSERVATIONVALUE: return "CriticalityObservationValue"; 2292 case CRITH: return "high criticality"; 2293 case CRITL: return "low criticality"; 2294 case CRITU: return "unable to assess criticality"; 2295 case _EMPLOYMENTSTATUS: return "_EmploymentStatus"; 2296 case EMPLOYED: return "Employed"; 2297 case NOTINLABORFORCE: return "Not In Labor Force"; 2298 case UNEMPLOYED: return "Unemployed"; 2299 case _GENETICOBSERVATIONVALUE: return "GeneticObservationValue"; 2300 case HOMOZYGOTE: return "HOMO"; 2301 case _OBSERVATIONMEASURESCORING: return "ObservationMeasureScoring"; 2302 case COHORT: return "cohort measure scoring"; 2303 case CONTVAR: return "continuous variable measure scoring"; 2304 case PROPOR: return "proportion measure scoring"; 2305 case RATIO: return "ratio measure scoring"; 2306 case _OBSERVATIONMEASURETYPE: return "ObservationMeasureType"; 2307 case COMPOSITE: return "composite measure type"; 2308 case EFFICIENCY: return "efficiency measure type"; 2309 case EXPERIENCE: return "experience measure type"; 2310 case OUTCOME: return "outcome measure type"; 2311 case INTERMOM: return "intermediate clinical outcome measure"; 2312 case PROPM: return "intermediate clinical outcome measure"; 2313 case PROCESS: return "process measure type"; 2314 case APPROPRIATE: return "appropriate use process measure"; 2315 case RESOURCE: return "resource use measure type"; 2316 case STRUCTURE: return "structure measure type"; 2317 case _OBSERVATIONPOPULATIONINCLUSION: return "ObservationPopulationInclusion"; 2318 case DENEX: return "denominator exclusions"; 2319 case DENEXCEP: return "denominator exceptions"; 2320 case DENOM: return "denominator"; 2321 case IP: return "initial population"; 2322 case IPP: return "initial patient population"; 2323 case MSRPOPL: return "measure population"; 2324 case NUMER: return "numerator"; 2325 case NUMEX: return "numerator exclusions"; 2326 case _PARTIALCOMPLETIONSCALE: return "PartialCompletionScale"; 2327 case G: return "Great extent"; 2328 case LE: return "Large extent"; 2329 case ME: return "Medium extent"; 2330 case MI: return "Minimal extent"; 2331 case N: return "None"; 2332 case S: return "Some extent"; 2333 case _SECURITYOBSERVATIONVALUE: return "SecurityObservationValue"; 2334 case _SECINTOBV: return "security integrity"; 2335 case _SECALTINTOBV: return "alteration integrity"; 2336 case ABSTRED: return "abstracted"; 2337 case AGGRED: return "aggregated"; 2338 case ANONYED: return "anonymized"; 2339 case MAPPED: return "mapped"; 2340 case MASKED: return "masked"; 2341 case PSEUDED: return "pseudonymized"; 2342 case REDACTED: return "redacted"; 2343 case SUBSETTED: return "subsetted"; 2344 case SYNTAC: return "syntactic transform"; 2345 case TRSLT: return "translated"; 2346 case VERSIONED: return "versioned"; 2347 case _SECDATINTOBV: return "data integrity"; 2348 case CRYTOHASH: return "cryptographic hash function"; 2349 case DIGSIG: return "digital signature"; 2350 case _SECINTCONOBV: return "integrity confidence"; 2351 case HRELIABLE: return "highly reliable"; 2352 case RELIABLE: return "reliable"; 2353 case UNCERTREL: return "uncertain reliability"; 2354 case UNRELIABLE: return "unreliable"; 2355 case _SECINTPRVOBV: return "provenance"; 2356 case _SECINTPRVABOBV: return "provenance asserted by"; 2357 case CLINAST: return "clinician asserted"; 2358 case DEVAST: return "device asserted"; 2359 case HCPAST: return "healthcare professional asserted"; 2360 case PACQAST: return "patient acquaintance asserted"; 2361 case PATAST: return "patient asserted"; 2362 case PAYAST: return "payer asserted"; 2363 case PROAST: return "professional asserted"; 2364 case SDMAST: return "substitute decision maker asserted"; 2365 case _SECINTPRVRBOBV: return "provenance reported by"; 2366 case CLINRPT: return "clinician reported"; 2367 case DEVRPT: return "device reported"; 2368 case HCPRPT: return "healthcare professional reported"; 2369 case PACQRPT: return "patient acquaintance reported"; 2370 case PATRPT: return "patient reported"; 2371 case PAYRPT: return "payer reported"; 2372 case PRORPT: return "professional reported"; 2373 case SDMRPT: return "substitute decision maker reported"; 2374 case SECTRSTOBV: return "security trust observation"; 2375 case TRSTACCRDOBV: return "trust accreditation observation"; 2376 case TRSTAGREOBV: return "trust agreement observation"; 2377 case TRSTCERTOBV: return "trust certificate observation"; 2378 case TRSTLOAOBV: return "trust assurance observation"; 2379 case LOAAN: return "authentication level of assurance value"; 2380 case LOAAN1: return "low authentication level of assurance"; 2381 case LOAAN2: return "basic authentication level of assurance"; 2382 case LOAAN3: return "medium authentication level of assurance"; 2383 case LOAAN4: return "high authentication level of assurance"; 2384 case LOAAP: return "authentication process level of assurance value"; 2385 case LOAAP1: return "low authentication process level of assurance"; 2386 case LOAAP2: return "basic authentication process level of assurance"; 2387 case LOAAP3: return "medium authentication process level of assurance"; 2388 case LOAAP4: return "high authentication process level of assurance"; 2389 case LOAAS: return "assertion level of assurance value"; 2390 case LOAAS1: return "low assertion level of assurance"; 2391 case LOAAS2: return "basic assertion level of assurance"; 2392 case LOAAS3: return "medium assertion level of assurance"; 2393 case LOAAS4: return "high assertion level of assurance"; 2394 case LOACM: return "token and credential management level of assurance value)"; 2395 case LOACM1: return "low token and credential management level of assurance"; 2396 case LOACM2: return "basic token and credential management level of assurance"; 2397 case LOACM3: return "medium token and credential management level of assurance"; 2398 case LOACM4: return "high token and credential management level of assurance"; 2399 case LOAID: return "identity proofing level of assurance"; 2400 case LOAID1: return "low identity proofing level of assurance"; 2401 case LOAID2: return "basic identity proofing level of assurance"; 2402 case LOAID3: return "medium identity proofing level of assurance"; 2403 case LOAID4: return "high identity proofing level of assurance"; 2404 case LOANR: return "non-repudiation level of assurance value"; 2405 case LOANR1: return "low non-repudiation level of assurance"; 2406 case LOANR2: return "basic non-repudiation level of assurance"; 2407 case LOANR3: return "medium non-repudiation level of assurance"; 2408 case LOANR4: return "high non-repudiation level of assurance"; 2409 case LOARA: return "remote access level of assurance value"; 2410 case LOARA1: return "low remote access level of assurance"; 2411 case LOARA2: return "basic remote access level of assurance"; 2412 case LOARA3: return "medium remote access level of assurance"; 2413 case LOARA4: return "high remote access level of assurance"; 2414 case LOATK: return "token level of assurance value"; 2415 case LOATK1: return "low token level of assurance"; 2416 case LOATK2: return "basic token level of assurance"; 2417 case LOATK3: return "medium token level of assurance"; 2418 case LOATK4: return "high token level of assurance"; 2419 case TRSTMECOBV: return "none supplied 6"; 2420 case _SEVERITYOBSERVATION: return "SeverityObservation"; 2421 case H: return "High"; 2422 case L: return "Low"; 2423 case M: return "Moderate"; 2424 case _SUBJECTBODYPOSITION: return "_SubjectBodyPosition"; 2425 case LLD: return "left lateral decubitus"; 2426 case PRN: return "prone"; 2427 case RLD: return "right lateral decubitus"; 2428 case SFWL: return "Semi-Fowler's"; 2429 case SIT: return "sitting"; 2430 case STN: return "standing"; 2431 case SUP: return "supine"; 2432 case RTRD: return "reverse trendelenburg"; 2433 case TRD: return "trendelenburg"; 2434 case _VERIFICATIONOUTCOMEVALUE: return "verification outcome"; 2435 case ACT: return "active coverage"; 2436 case ACTPEND: return "active - pending investigation"; 2437 case ELG: return "eligible"; 2438 case INACT: return "inactive"; 2439 case INPNDINV: return "inactive - pending investigation"; 2440 case INPNDUPD: return "inactive - pending eligibility update"; 2441 case NELG: return "not eligible"; 2442 case _WORKSCHEDULE: return "_WorkSchedule"; 2443 case DS: return "daytime shift"; 2444 case EMS: return "early morning shift"; 2445 case ES: return "evening shift"; 2446 case NS: return "night shift"; 2447 case RSWN: return "rotating shift with nights"; 2448 case RSWON: return "rotating shift without nights"; 2449 case SS: return "split shift"; 2450 case VLS: return "very long shift"; 2451 case VS: return "variable shift"; 2452 case _ANNOTATIONVALUE: return "AnnotationValue"; 2453 case _COMMONCLINICALOBSERVATIONVALUE: return "common clinical observation"; 2454 case _INDIVIDUALCASESAFETYREPORTVALUEDOMAINS: return "Individual Case Safety Report Value Domains"; 2455 case _INDICATIONVALUE: return "IndicationValue"; 2456 default: return "?"; 2457 } 2458 } 2459 2460 2461} 2462