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