STU 3 Candidate
This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R4 R3 R2
This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type. OpenIssue: Description copied from Concept Domain of same name. Must be corrected..
<ValueSet xmlns="http://hl7.org/fhir"> <id value="v3-ObservationValue"/> <meta> <lastUpdated value="2016-03-23T00:00:00.000+11:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p>Release Date: 2016-03-23</p> <table class="grid"> <tr> <td> <b>Level</b> </td> <td> <b>Code</b> </td> <td> <b>Display</b> </td> <td> <b>Definition</b> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_ActCoverageAssessmentObservationValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_ActCoverageAssessmentObservationValue"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td>2</td> <td>  <span style="color: grey"> <i>(_ActFinancialStatusObservationValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_ActFinancialStatusObservationValue"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    ASSET <a name="ASSET"> </a> </td> <td>asset</td> <td> Codes specifying asset indicators used to assess or establish eligibility for coverage under a policy or program. <br/> </td> </tr> <tr> <td>4</td> <td>      ANNUITY <a name="ANNUITY"> </a> </td> <td>annuity</td> <td> Indicator of annuity ownership or status as beneficiary. <br/> </td> </tr> <tr> <td>4</td> <td>      PROP <a name="PROP"> </a> </td> <td>real property</td> <td> Indicator of real property ownership, e.g., deed or real estate contract. <br/> </td> </tr> <tr> <td>4</td> <td>      RETACCT <a name="RETACCT"> </a> </td> <td>retirement investment account</td> <td> Indicator of retirement investment account ownership. <br/> </td> </tr> <tr> <td>4</td> <td>      TRUST <a name="TRUST"> </a> </td> <td>trust</td> <td> Indicator of status as trust beneficiary. <br/> </td> </tr> <tr> <td>3</td> <td>    INCOME <a name="INCOME"> </a> </td> <td>income</td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      CHILD <a name="CHILD"> </a> </td> <td>child support</td> <td> Indicator of child support payments received or provided. <br/> </td> </tr> <tr> <td>4</td> <td>      DISABL <a name="DISABL"> </a> </td> <td>disability pay</td> <td> Indicator of disability income replacement payment. <br/> </td> </tr> <tr> <td>4</td> <td>      INVEST <a name="INVEST"> </a> </td> <td>investment income</td> <td> Indicator of investment income, e.g., dividend check, annuity payment; real estate rent, investment divestiture proceeds; trust or endowment check. <br/> </td> </tr> <tr> <td>4</td> <td>      PAY <a name="PAY"> </a> </td> <td>paid employment</td> <td> Indicator of paid employment, e.g., letter of hire, contract, employer letter; copy of pay check or pay stub. <br/> </td> </tr> <tr> <td>4</td> <td>      RETIRE <a name="RETIRE"> </a> </td> <td>retirement pay</td> <td> Indicator of retirement payment, e.g., pension check. <br/> </td> </tr> <tr> <td>4</td> <td>      SPOUSAL <a name="SPOUSAL"> </a> </td> <td>spousal or partner support</td> <td> Indicator of spousal or partner support payments received or provided; e.g., alimony payment; support stipulations in a divorce settlement. <br/> </td> </tr> <tr> <td>4</td> <td>      SUPPLE <a name="SUPPLE"> </a> </td> <td>income supplement</td> <td> Indicator of income supplement, e.g., gifting, parental income support; stipend, or grant. <br/> </td> </tr> <tr> <td>4</td> <td>      TAX <a name="TAX"> </a> </td> <td>tax obligation</td> <td> Indicator of tax obligation or payment, e.g., statement of taxable income. <br/> </td> </tr> <tr> <td>3</td> <td>    LIVEXP <a name="LIVEXP"> </a> </td> <td>living expense</td> <td> Codes specifying living expense indicators used to assess or establish eligibility for coverage under a policy or program. <br/> </td> </tr> <tr> <td>4</td> <td>      CLOTH <a name="CLOTH"> </a> </td> <td>clothing expense</td> <td> Indicator of clothing expenses. <br/> </td> </tr> <tr> <td>4</td> <td>      FOOD <a name="FOOD"> </a> </td> <td>food expense</td> <td> Indicator of transportation expenses. <br/> </td> </tr> <tr> <td>4</td> <td>      HEALTH <a name="HEALTH"> </a> </td> <td>health expense</td> <td> Indicator of health expenses; including medication costs, health service costs, financial participations, and health coverage premiums. <br/> </td> </tr> <tr> <td>4</td> <td>      HOUSE <a name="HOUSE"> </a> </td> <td>household expense</td> <td> Indicator of housing expense, e.g., household appliances, fixtures, furnishings, and maintenance and repairs. <br/> </td> </tr> <tr> <td>4</td> <td>      LEGAL <a name="LEGAL"> </a> </td> <td>legal expense</td> <td> Indicator of legal expenses. <br/> </td> </tr> <tr> <td>4</td> <td>      MORTG <a name="MORTG"> </a> </td> <td>mortgage</td> <td> Indicator of mortgage amount, interest, and payments. <br/> </td> </tr> <tr> <td>4</td> <td>      RENT <a name="RENT"> </a> </td> <td>rent</td> <td> Indicator of rental or lease payments. <br/> </td> </tr> <tr> <td>4</td> <td>      SUNDRY <a name="SUNDRY"> </a> </td> <td>sundry expense</td> <td> Indicator of transportation expenses. <br/> </td> </tr> <tr> <td>4</td> <td>      TRANS <a name="TRANS"> </a> </td> <td>transportation expense</td> <td> Indicator of transportation expenses, e.g., vehicle payments, vehicle insurance, vehicle fuel, and vehicle maintenance and repairs. <br/> </td> </tr> <tr> <td>4</td> <td>      UTIL <a name="UTIL"> </a> </td> <td>utility expense</td> <td> Indicator of transportation expenses. <br/> </td> </tr> <tr> <td>2</td> <td>  ELSTAT <a name="ELSTAT"> </a> </td> <td>eligibility indicator</td> <td> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    ADOPT <a name="ADOPT"> </a> </td> <td>adoption document</td> <td> Indicator of adoption. <br/> </td> </tr> <tr> <td>3</td> <td>    BTHCERT <a name="BTHCERT"> </a> </td> <td>birth certificate</td> <td> Indicator of birth. <br/> </td> </tr> <tr> <td>3</td> <td>    CCOC <a name="CCOC"> </a> </td> <td>creditable coverage document</td> <td> Indicator of creditable coverage. <br/> </td> </tr> <tr> <td>3</td> <td>    DRLIC <a name="DRLIC"> </a> </td> <td>driver license</td> <td> Indicator of driving status. <br/> </td> </tr> <tr> <td>3</td> <td>    FOSTER <a name="FOSTER"> </a> </td> <td>foster child document</td> <td> Indicator of foster child status. <br/> </td> </tr> <tr> <td>3</td> <td>    MEMBER <a name="MEMBER"> </a> </td> <td>program or policy member</td> <td> Indicator of status as covered member under a policy or program, e.g., member id card or coverage document. <br/> </td> </tr> <tr> <td>3</td> <td>    MIL <a name="MIL"> </a> </td> <td>military identification</td> <td> Indicator of military status. <br/> </td> </tr> <tr> <td>3</td> <td>    MRGCERT <a name="MRGCERT"> </a> </td> <td>marriage certificate</td> <td> Indicator of marriage status. <br/> </td> </tr> <tr> <td>3</td> <td>    PASSPORT <a name="PASSPORT"> </a> </td> <td>passport</td> <td> Indicator of citizenship. <br/> </td> </tr> <tr> <td>3</td> <td>    STUDENRL <a name="STUDENRL"> </a> </td> <td>student enrollment</td> <td> Indicator of student status. <br/> </td> </tr> <tr> <td>2</td> <td>  HLSTAT <a name="HLSTAT"> </a> </td> <td>health status</td> <td> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    DISABLE <a name="DISABLE"> </a> </td> <td>disabled</td> <td> Indication of disability. <br/> </td> </tr> <tr> <td>3</td> <td>    DRUG <a name="DRUG"> </a> </td> <td>drug use</td> <td> Indication of drug use. <br/> </td> </tr> <tr> <td>3</td> <td>    IVDRG <a name="IVDRG"> </a> </td> <td>IV drug use</td> <td> Indication of IV drug use . <br/> </td> </tr> <tr> <td>3</td> <td>    PGNT <a name="PGNT"> </a> </td> <td>pregnant</td> <td> Non-clinical report of pregnancy. <br/> </td> </tr> <tr> <td>2</td> <td>  LIVDEP <a name="LIVDEP"> </a> </td> <td>living dependency</td> <td> Code specifying observations related to living dependency, such as dependent upon spouse for activities of daily living. <br/> </td> </tr> <tr> <td>3</td> <td>    RELDEP <a name="RELDEP"> </a> </td> <td>relative dependent</td> <td> Continued living in private residence requires functional and health care assistance from one or more relatives. <br/> </td> </tr> <tr> <td>3</td> <td>    SPSDEP <a name="SPSDEP"> </a> </td> <td>spouse dependent</td> <td> Continued living in private residence requires functional and health care assistance from spouse or life partner. <br/> </td> </tr> <tr> <td>3</td> <td>    URELDEP <a name="URELDEP"> </a> </td> <td>unrelated person dependent</td> <td> Continued living in private residence requires functional and health care assistance from one or more unrelated persons. <br/> </td> </tr> <tr> <td>2</td> <td>  LIVSIT <a name="LIVSIT"> </a> </td> <td>living situation</td> <td> Code specifying observations related to living situation for a person in a private residence. <br/> </td> </tr> <tr> <td>3</td> <td>    ALONE <a name="ALONE"> </a> </td> <td>alone</td> <td> Living alone. Maps to PD1-2 Living arrangement (IS) 00742 [A] <br/> </td> </tr> <tr> <td>3</td> <td>    DEPCHD <a name="DEPCHD"> </a> </td> <td>dependent children</td> <td> Living with one or more dependent children requiring moderate supervision. <br/> </td> </tr> <tr> <td>3</td> <td>    DEPSPS <a name="DEPSPS"> </a> </td> <td>dependent spouse</td> <td> Living with disabled spouse requiring functional and health care assistance <br/> </td> </tr> <tr> <td>3</td> <td>    DEPYGCHD <a name="DEPYGCHD"> </a> </td> <td>dependent young children</td> <td> Living with one or more dependent children requiring intensive supervision <br/> </td> </tr> <tr> <td>3</td> <td>    FAM <a name="FAM"> </a> </td> <td>live with family</td> <td> Living with family. Maps to PD1-2 Living arrangement (IS) 00742 [F] <br/> </td> </tr> <tr> <td>3</td> <td>    RELAT <a name="RELAT"> </a> </td> <td>relative</td> <td> Living with one or more relatives. Maps to PD1-2 Living arrangement (IS) 00742 [R] <br/> </td> </tr> <tr> <td>3</td> <td>    SPS <a name="SPS"> </a> </td> <td>spouse only</td> <td> Living only with spouse or life partner. Maps to PD1-2 Living arrangement (IS) 00742 [S] <br/> </td> </tr> <tr> <td>3</td> <td>    UNREL <a name="UNREL"> </a> </td> <td>unrelated person</td> <td> Living with one or more unrelated persons. <br/> </td> </tr> <tr> <td>2</td> <td>  SOECSTAT <a name="SOECSTAT"> </a> </td> <td>socio economic status</td> <td> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    ABUSE <a name="ABUSE"> </a> </td> <td>abuse victim</td> <td> Indication of abuse victim. <br/> </td> </tr> <tr> <td>3</td> <td>    HMLESS <a name="HMLESS"> </a> </td> <td>homeless</td> <td> Indication of status as homeless. <br/> </td> </tr> <tr> <td>3</td> <td>    ILGIM <a name="ILGIM"> </a> </td> <td>illegal immigrant</td> <td> Indication of status as illegal immigrant. <br/> </td> </tr> <tr> <td>3</td> <td>    INCAR <a name="INCAR"> </a> </td> <td>incarcerated</td> <td> Indication of status as incarcerated. <br/> </td> </tr> <tr> <td>3</td> <td>    PROB <a name="PROB"> </a> </td> <td>probation</td> <td> Indication of probation status. <br/> </td> </tr> <tr> <td>3</td> <td>    REFUG <a name="REFUG"> </a> </td> <td>refugee</td> <td> Indication of refugee status. <br/> </td> </tr> <tr> <td>3</td> <td>    UNEMPL <a name="UNEMPL"> </a> </td> <td>unemployed</td> <td> Indication of unemployed status. <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_AllergyTestValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_AllergyTestValue"> </a> </td> <td> Indicates the result of a particular allergy test. E.g. Negative, Mild, Moderate, Severe <br/> </td> </tr> <tr> <td>2</td> <td>  A0 <a name="A0"> </a> </td> <td>no reaction</td> <td> Description:Patient exhibits no reaction to the challenge agent. <br/> </td> </tr> <tr> <td>2</td> <td>  A1 <a name="A1"> </a> </td> <td>minimal reaction</td> <td> Description:Patient exhibits a minimal reaction to the challenge agent. <br/> </td> </tr> <tr> <td>2</td> <td>  A2 <a name="A2"> </a> </td> <td>mild reaction</td> <td> Description:Patient exhibits a mild reaction to the challenge agent. <br/> </td> </tr> <tr> <td>2</td> <td>  A3 <a name="A3"> </a> </td> <td>moderate reaction</td> <td> Description:Patient exhibits moderate reaction to the challenge agent. <br/> </td> </tr> <tr> <td>2</td> <td>  A4 <a name="A4"> </a> </td> <td>severe reaction</td> <td> Description:Patient exhibits a severe reaction to the challenge agent. <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_CoverageLimitObservationValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_CoverageLimitObservationValue"> </a> </td> <td> Description:Coded observation values for coverage limitations, for e.g., types of claims or types of parties covered under a policy or program. <br/> </td> </tr> <tr> <td>2</td> <td>  <span style="color: grey"> <i>(_CoverageLevelObservationValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_CoverageLevelObservationValue"> </a> </td> <td> Description:Coded observation values for types of covered parties under a policy or program based on their personal relationships or employment status. <br/> </td> </tr> <tr> <td>3</td> <td>    ADC <a name="ADC"> </a> </td> <td>adult child</td> <td> Description:Child over an age as specified by coverage policy or program, e.g., student, differently abled, and income dependent. <br/> </td> </tr> <tr> <td>3</td> <td>    CHD <a name="CHD"> </a> </td> <td>child</td> <td> Description:Dependent biological, adopted, foster child as specified by coverage policy or program. <br/> </td> </tr> <tr> <td>3</td> <td>    DEP <a name="DEP"> </a> </td> <td>dependent</td> <td> Description:Person requiring functional and/or financial assistance from another person as specified by coverage policy or program. <br/> </td> </tr> <tr> <td>3</td> <td>    DP <a name="DP"> </a> </td> <td>domestic partner</td> <td> Description:Persons registered as a family unit in a domestic partner registry as specified by law and by coverage policy or program. <br/> </td> </tr> <tr> <td>3</td> <td>    ECH <a name="ECH"> </a> </td> <td>employee</td> <td> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    FLY <a name="FLY"> </a> </td> <td>family coverage</td> <td> Description:As specified by coverage policy or program. <br/> </td> </tr> <tr> <td>3</td> <td>    IND <a name="IND"> </a> </td> <td>individual</td> <td> Description:Person as specified by coverage policy or program. <br/> </td> </tr> <tr> <td>3</td> <td>    SSP <a name="SSP"> </a> </td> <td>same sex partner</td> <td> 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 <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_CriticalityObservationValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_CriticalityObservationValue"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td>2</td> <td>  CRITH <a name="CRITH"> </a> </td> <td>high criticality</td> <td> Worst case result of a future exposure is assessed to be life-threatening or having high potential for organ system failure. <br/> </td> </tr> <tr> <td>2</td> <td>  CRITL <a name="CRITL"> </a> </td> <td>low criticality</td> <td> Worst case result of a future exposure is not assessed to be life-threatenin g or having high potential for organ system failure. <br/> </td> </tr> <tr> <td>2</td> <td>  CRITU <a name="CRITU"> </a> </td> <td>unable to assess criticality</td> <td> Unable to assess the worst case result of a future exposure. <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_GeneticObservationValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_GeneticObservationValue"> </a> </td> <td> Description: The domain contains genetic analysis specific observation values, e.g. Homozygote, Heterozygote, etc. <br/> </td> </tr> <tr> <td>2</td> <td>  Homozygote <a name="Homozygote"> </a> </td> <td>HOMO</td> <td> Description: An individual having different alleles at one or more loci regarding a specific character <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_ObservationMeasureScoring)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_ObservationMeasureScoring"> </a> </td> <td> Observation values used to indicate the type of scoring (e.g. proportion, ratio) used by a health quality measure. <br/> </td> </tr> <tr> <td>2</td> <td>  COHORT <a name="COHORT"> </a> </td> <td>cohort measure scoring</td> <td> 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). <br/> </td> </tr> <tr> <td>2</td> <td>  CONTVAR <a name="CONTVAR"> </a> </td> <td>continuous variable measure scoring</td> <td> 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). <br/> </td> </tr> <tr> <td>2</td> <td>  PROPOR <a name="PROPOR"> </a> </td> <td>proportion measure scoring</td> <td> 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). <br/> </td> </tr> <tr> <td>2</td> <td>  RATIO <a name="RATIO"> </a> </td> <td>ratio measure scoring</td> <td> 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). <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_ObservationMeasureType)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_ObservationMeasureType"> </a> </td> <td> Observation values used to indicate what kind of health quality measure is used. <br/> </td> </tr> <tr> <td>2</td> <td>  COMPOSITE <a name="COMPOSITE"> </a> </td> <td>composite measure type</td> <td> A measure that is composed from one or more other measures and indicates an overall summary of those measures. <br/> </td> </tr> <tr> <td>2</td> <td>  EFFICIENCY <a name="EFFICIENCY"> </a> </td> <td>efficiency measure type</td> <td> A measure related to the efficiency of medical treatment. <br/> </td> </tr> <tr> <td>2</td> <td>  EXPERIENCE <a name="EXPERIENCE"> </a> </td> <td>experience measure type</td> <td> A measure related to the level of patient engagement or patient experience of care. <br/> </td> </tr> <tr> <td>2</td> <td>  OUTCOME <a name="OUTCOME"> </a> </td> <td>outcome measure type</td> <td> A measure that indicates the result of the performance (or non-performance) of a function or process. <br/> </td> </tr> <tr> <td>2</td> <td>  PROCESS <a name="PROCESS"> </a> </td> <td>process measure type</td> <td> 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. <br/> </td> </tr> <tr> <td>2</td> <td>  RESOURCE <a name="RESOURCE"> </a> </td> <td>resource use measure type</td> <td> A measure related to the extent of use of clinical resources or cost of care. <br/> </td> </tr> <tr> <td>2</td> <td>  STRUCTURE <a name="STRUCTURE"> </a> </td> <td>structure measure type</td> <td> A measure related to the structure of patient care. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>1</td> <td>_ObservationPopulationInclusion <a name="_ObservationPopulationInclusion"> </a> <b> <i>Deprecated</i> </b> </td> <td>ObservationPopulationInclusion</td> <td> Observation values used to assert various populations that a subject falls into. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>2</td> <td>  DENEX <a name="DENEX"> </a> <b> <i>Deprecated</i> </b> </td> <td>denominator exclusions</td> <td> 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>2</td> <td>  DENEXCEP <a name="DENEXCEP"> </a> <b> <i>Deprecated</i> </b> </td> <td>denominator exceptions</td> <td> 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: <br/> Medical reasons Patient reasons System reasons </td> </tr> <tr style="background: #EFEFEF"> <td>2</td> <td>  DENOM <a name="DENOM"> </a> <b> <i>Deprecated</i> </b> </td> <td>denominator</td> <td> 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>2</td> <td>  IP <a name="IP"> </a> <b> <i>Deprecated</i> </b> </td> <td>initial population</td> <td> 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>3</td> <td>    IPP <a name="IPP"> </a> <b> <i>Deprecated</i> </b> </td> <td>initial patient population</td> <td> 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>2</td> <td>  MSRPOPL <a name="MSRPOPL"> </a> <b> <i>Deprecated</i> </b> </td> <td>measure population</td> <td> Measure population is used only in continuous variable eMeasures. It is a narrative description of the eMeasure population. (e.g., all patients seen in the Emergency Department during the measurement period). <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>2</td> <td>  NUMER <a name="NUMER"> </a> <b> <i>Deprecated</i> </b> </td> <td>numerator</td> <td> 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). <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>2</td> <td>  NUMEX <a name="NUMEX"> </a> <b> <i>Deprecated</i> </b> </td> <td>numerator exclusions</td> <td> 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.) <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_PartialCompletionScale)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_PartialCompletionScale"> </a> </td> <td/> </tr> <tr> <td>2</td> <td>  G <a name="G"> </a> </td> <td>Great extent</td> <td> Value for Act.partialCompletionCode attribute that implies 81-99% completion <br/> </td> </tr> <tr> <td>2</td> <td>  LE <a name="LE"> </a> </td> <td>Large extent</td> <td> Value for Act.partialCompletionCode attribute that implies 61-80% completion <br/> </td> </tr> <tr> <td>2</td> <td>  ME <a name="ME"> </a> </td> <td>Medium extent</td> <td> Value for Act.partialCompletionCode attribute that implies 41-60% completion <br/> </td> </tr> <tr> <td>2</td> <td>  MI <a name="MI"> </a> </td> <td>Minimal extent</td> <td> Value for Act.partialCompletionCode attribute that implies 1-20% completion <br/> </td> </tr> <tr> <td>2</td> <td>  N <a name="N"> </a> </td> <td>None</td> <td> Value for Act.partialCompletionCode attribute that implies 0% completion <br/> </td> </tr> <tr> <td>2</td> <td>  S <a name="S"> </a> </td> <td>Some extent</td> <td> Value for Act.partialCompletionCode attribute that implies 21-40% completion <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_SecurityObservationValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SecurityObservationValue"> </a> </td> <td> Observation values used to indicate security observation metadata. <br/> </td> </tr> <tr> <td>2</td> <td>  <span style="color: grey"> <i>(_SECINTOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SECINTOBV"> </a> </td> <td> Abstract security observation values used to indicate security integrity metadata. <br/> Examples: Codes conveying integrity status, integrity confidence, and provenance. <br/> </td> </tr> <tr> <td>3</td> <td>    <span style="color: grey"> <i>(_SECALTINTOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SECALTINTOBV"> </a> </td> <td> Abstract security metadata observation values used to indicate mechanism used for authorized alteration of an IT resource (data, information object, service, or system capability) <br/> </td> </tr> <tr> <td>4</td> <td>      ABSTRED <a name="ABSTRED"> </a> </td> <td>abstracted</td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      AGGRED <a name="AGGRED"> </a> </td> <td>aggregated</td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      ANONYED <a name="ANONYED"> </a> </td> <td>anonymized</td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      MAPPED <a name="MAPPED"> </a> </td> <td>mapped</td> <td> Security metadata observation value used to indicate that the IT resource semantic content has been transformed from one encoding to another. <br/> Usage Note: "MAP" code does not indicate the semantic fidelity of the transformed content. <br/> 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). <br/> Semantic fidelity of the mapped IT Resource may also be indicated using a SecurityIntegrityConfidenceObservation. <br/> </td> </tr> <tr> <td>4</td> <td>      MASKED <a name="MASKED"> </a> </td> <td>masked</td> <td> 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". <br/> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      PSEUDED <a name="PSEUDED"> </a> </td> <td>pseudonymized</td> <td> 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. <br/> 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 <br/> </td> </tr> <tr> <td>4</td> <td>      REDACTED <a name="REDACTED"> </a> </td> <td>redacted</td> <td> 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. <br/> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      SUBSETTED <a name="SUBSETTED"> </a> </td> <td>subsetted</td> <td> 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 <br/> Usage Note: This is not suitable to be used when information is removed for security reasons - see the code REDACTED for this use. <br/> </td> </tr> <tr> <td>4</td> <td>      SYNTAC <a name="SYNTAC"> </a> </td> <td>syntactic transform</td> <td> Security metadata observation value used to indicate that the IT resource syntax has been transformed from one syntactical representation to another. <br/> Usage Note: "SYNTAC" code does not indicate the syntactical correctness of the syntactically transformed IT resource. <br/> </td> </tr> <tr> <td>4</td> <td>      TRSLT <a name="TRSLT"> </a> </td> <td>translated</td> <td> Security metadata observation value used to indicate that the IT resource has been translated from one human language to another. <br/> Usage Note: "TRSLT" does not indicate the fidelity of the translation or the languages translated. <br/> The fidelity of the IT Resource translation may be indicated using a SecurityIntegrityConfidenceObservation. <br/> To indicate languages, use the Value Set:HumanLanguage (2.16.840.1.113883.1. 11.11526) <br/> </td> </tr> <tr> <td>4</td> <td>      VERSIONED <a name="VERSIONED"> </a> </td> <td>versioned</td> <td> 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 <br/> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    <span style="color: grey"> <i>(_SECDATINTOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SECDATINTOBV"> </a> </td> <td> Abstract security observation values used to indicate data integrity metadata. <br/> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      CRYTOHASH <a name="CRYTOHASH"> </a> </td> <td>cryptographic hash function</td> <td> Security metadata observation value used to indicate the mechanism by which software systems can establish that data was not modified in transit. <br/> 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. <br/> Examples: <br/> SHA-1 SHA-2 (Secure Hash Algorithm) </td> </tr> <tr> <td>4</td> <td>      DIGSIG <a name="DIGSIG"> </a> </td> <td>digital signature</td> <td> Security metadata observation value used to indicate the mechanism by which software systems use digital signature to establish that data has not been modified. <br/> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    <span style="color: grey"> <i>(_SECINTCONOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SECINTCONOBV"> </a> </td> <td> Abstract security observation value used to indicate integrity confidence metadata. <br/> Examples: Codes conveying the level of reliability and trustworthiness of an IT resource. <br/> </td> </tr> <tr> <td>4</td> <td>      HRELIABLE <a name="HRELIABLE"> </a> </td> <td>highly reliable</td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      RELIABLE <a name="RELIABLE"> </a> </td> <td>reliable</td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      UNCERTREL <a name="UNCERTREL"> </a> </td> <td>uncertain reliability</td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      UNRELIABLE <a name="UNRELIABLE"> </a> </td> <td>unreliable</td> <td> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    <span style="color: grey"> <i>(_SECINTPRVOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SECINTPRVOBV"> </a> </td> <td> Abstract security metadata observation value used to indicate the provenance of an IT resource (data, information object, service, or system capability). <br/> Examples: Codes conveying the provenance metadata about the entity reporting an IT resource. <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(_SECINTPRVABOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SECINTPRVABOBV"> </a> </td> <td> Abstract security provenance metadata observation value used to indicate the entity that asserted an IT resource (data, information object, service, or system capability). <br/> Examples: Codes conveying the provenance metadata about the entity asserting the resource. <br/> </td> </tr> <tr> <td>5</td> <td>        CLINAST <a name="CLINAST"> </a> </td> <td>clinician asserted</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a clinician. <br/> </td> </tr> <tr> <td>5</td> <td>        DEVAST <a name="DEVAST"> </a> </td> <td>device asserted</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a device. <br/> </td> </tr> <tr> <td>5</td> <td>        HCPAST <a name="HCPAST"> </a> </td> <td>healthcare professional asserted</td> <td> 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. <br/> </td> </tr> <tr> <td>5</td> <td>        PACQAST <a name="PACQAST"> </a> </td> <td>patient acquaintance asserted</td> <td> 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. <br/> </td> </tr> <tr> <td>5</td> <td>        PATAST <a name="PATAST"> </a> </td> <td>patient asserted</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a patient. <br/> </td> </tr> <tr> <td>5</td> <td>        PAYAST <a name="PAYAST"> </a> </td> <td>payer asserted</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a payer. <br/> </td> </tr> <tr> <td>5</td> <td>        PROAST <a name="PROAST"> </a> </td> <td>professional asserted</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was asserted by a professional. <br/> </td> </tr> <tr> <td>5</td> <td>        SDMAST <a name="SDMAST"> </a> </td> <td>substitute decision maker asserted</td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(_SECINTPRVRBOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SECINTPRVRBOBV"> </a> </td> <td> Abstract security provenance metadata observation value used to indicate the entity that reported the resource (data, information object, service, or system capability). <br/> Examples: Codes conveying the provenance metadata about the entity reporting an IT resource. <br/> </td> </tr> <tr> <td>5</td> <td>        CLINRPT <a name="CLINRPT"> </a> </td> <td>clinician reported</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a clinician. <br/> </td> </tr> <tr> <td>5</td> <td>        DEVRPT <a name="DEVRPT"> </a> </td> <td>device reported</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a device. <br/> </td> </tr> <tr> <td>5</td> <td>        HCPRPT <a name="HCPRPT"> </a> </td> <td>healthcare professional reported</td> <td>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.</td> </tr> <tr> <td>5</td> <td>        PACQRPT <a name="PACQRPT"> </a> </td> <td>patient acquaintance reported</td> <td> 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. <br/> </td> </tr> <tr> <td>5</td> <td>        PATRPT <a name="PATRPT"> </a> </td> <td>patient reported</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a patient. <br/> </td> </tr> <tr> <td>5</td> <td>        PAYRPT <a name="PAYRPT"> </a> </td> <td>payer reported</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a payer. <br/> </td> </tr> <tr> <td>5</td> <td>        PRORPT <a name="PRORPT"> </a> </td> <td>professional reported</td> <td> Security provenance metadata observation value used to indicate that an IT resource (data, information object, service, or system capability) was reported by a professional. <br/> </td> </tr> <tr> <td>5</td> <td>        SDMRPT <a name="SDMRPT"> </a> </td> <td>substitute decision maker reported</td> <td> 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. <br/> </td> </tr> <tr> <td>2</td> <td>  <span style="color: grey"> <i>(SECTRSTOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="SECTRSTOBV"> </a> </td> <td> Observation value used to indicate aspects of trust applicable to an IT resource (data, information object, service, or system capability). <br/> </td> </tr> <tr> <td>3</td> <td>    TRSTACCRDOBV <a name="TRSTACCRDOBV"> </a> </td> <td>trust accreditation observation</td> <td> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    TRSTAGREOBV <a name="TRSTAGREOBV"> </a> </td> <td>trust agreement observation</td> <td> Values for security trust agreement metadata observation made about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] [ISO IEC 10181-1] <br/> </td> </tr> <tr> <td>3</td> <td>    TRSTCERTOBV <a name="TRSTCERTOBV"> </a> </td> <td>trust certificate observation</td> <td> 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] <br/> 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. <br/> </td> </tr> <tr> <td>3</td> <td>    <span style="color: grey"> <i>(TRSTLOAOBV)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="TRSTLOAOBV"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(LOAAN)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="LOAAN"> </a> </td> <td> 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] <br/> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAN1 <a name="LOAAN1"> </a> </td> <td>low authentication level of assurance</td> <td> 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] <br/> 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] <br/> 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.] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAN2 <a name="LOAAN2"> </a> </td> <td>basic authentication level of assurance</td> <td> 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] <br/> 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] <br/> 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. Long-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.] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAN3 <a name="LOAAN3"> </a> </td> <td>medium authentication level of assurance</td> <td> 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] <br/> 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] <br/> 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: <br/> "soft" cryptographic token, which has the key stored on a general-purpose computer, "hard" cryptographic token, which has the key stored on a special hardware device, and "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. 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.] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAN4 <a name="LOAAN4"> </a> </td> <td>high authentication level of assurance</td> <td> 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] <br/> 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] <br/> 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. <br/> 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.] <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(LOAAP)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="LOAAP"> </a> </td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAP1 <a name="LOAAP1"> </a> </td> <td>low authentication process level of assurance</td> <td> 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] <br/> 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.] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAP2 <a name="LOAAP2"> </a> </td> <td>basic authentication process level of assurance</td> <td> 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] <br/> 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.] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAP3 <a name="LOAAP3"> </a> </td> <td>medium authentication process level of assurance</td> <td> 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] <br/> 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). <br/> 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. <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAP4 <a name="LOAAP4"> </a> </td> <td>high authentication process level of assurance</td> <td> 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] <br/> 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.] <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(LOAAS)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="LOAAS"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAS1 <a name="LOAAS1"> </a> </td> <td>low assertion level of assurance</td> <td> 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. <br/> 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.] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAS2 <a name="LOAAS2"> </a> </td> <td>basic assertion level of assurance</td> <td> 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. <br/> 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.] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAS3 <a name="LOAAS3"> </a> </td> <td>medium assertion level of assurance</td> <td> 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. <br/> 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.] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAAS4 <a name="LOAAS4"> </a> </td> <td>high assertion level of assurance</td> <td> 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. <br/> 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.] <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(LOACM)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="LOACM"> </a> </td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOACM1 <a name="LOACM1"> </a> </td> <td>low token and credential management level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOACM2 <a name="LOACM2"> </a> </td> <td>basic token and credential management level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOACM3 <a name="LOACM3"> </a> </td> <td>medium token and credential management level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOACM4 <a name="LOACM4"> </a> </td> <td>high token and credential management level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(LOAID)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="LOAID"> </a> </td> <td> Indicator of the quality or reliability in the process of ascertaining that an individual is who he or she claims to be. <br/> </td> </tr> <tr> <td>5</td> <td>        LOAID1 <a name="LOAID1"> </a> </td> <td>low identity proofing level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAID2 <a name="LOAID2"> </a> </td> <td>basic identity proofing level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAID3 <a name="LOAID3"> </a> </td> <td>medium identity proofing level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOAID4 <a name="LOAID4"> </a> </td> <td>high identity proofing level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(LOANR)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="LOANR"> </a> </td> <td> Indicator of the digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] <br/> </td> </tr> <tr> <td>5</td> <td>        LOANR1 <a name="LOANR1"> </a> </td> <td>low non-repudiation level of assurance</td> <td> Indicator of low digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] <br/> </td> </tr> <tr> <td>5</td> <td>        LOANR2 <a name="LOANR2"> </a> </td> <td>basic non-repudiation level of assurance</td> <td> Indicator of basic digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] <br/> </td> </tr> <tr> <td>5</td> <td>        LOANR3 <a name="LOANR3"> </a> </td> <td>medium non-repudiation level of assurance</td> <td> Indicator of medium digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] <br/> </td> </tr> <tr> <td>5</td> <td>        LOANR4 <a name="LOANR4"> </a> </td> <td>high non-repudiation level of assurance</td> <td> Indicator of high digital quality or reliability in the process of establishing proof of delivery and proof of origin. [Based on ISO 7498-2] <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(LOARA)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="LOARA"> </a> </td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOARA1 <a name="LOARA1"> </a> </td> <td>low remote access level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOARA2 <a name="LOARA2"> </a> </td> <td>basic remote access level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOARA3 <a name="LOARA3"> </a> </td> <td>medium remote access level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOARA4 <a name="LOARA4"> </a> </td> <td>high remote access level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>4</td> <td>      <span style="color: grey"> <i>(LOATK)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="LOATK"> </a> </td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOATK1 <a name="LOATK1"> </a> </td> <td>low token level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOATK2 <a name="LOATK2"> </a> </td> <td>basic token level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOATK3 <a name="LOATK3"> </a> </td> <td>medium token level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>5</td> <td>        LOATK4 <a name="LOATK4"> </a> </td> <td>high token level of assurance</td> <td> 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] <br/> </td> </tr> <tr> <td>3</td> <td>    TRSTMECOBV <a name="TRSTMECOBV"> </a> </td> <td>none supplied 6</td> <td> Values for security trust mechanism metadata observation made about a security architecture system component that supports enforcement of security policies. <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_SeverityObservation)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SeverityObservation"> </a> </td> <td> Potential values for observations of severity. <br/> </td> </tr> <tr> <td>2</td> <td>  H <a name="H"> </a> </td> <td>High</td> <td> Indicates the condition may be life-threatening or has the potential to cause permanent injury. <br/> </td> </tr> <tr> <td>2</td> <td>  L <a name="L"> </a> </td> <td>Low</td> <td> Indicates the condition may result in some adverse consequences but is unlikely to substantially affect the situation of the subject. <br/> </td> </tr> <tr> <td>2</td> <td>  M <a name="M"> </a> </td> <td>Moderate</td> <td> Indicates the condition may result in noticable adverse adverse consequences but is unlikely to be life-threatening or cause permanent injury. <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_SubjectBodyPosition)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_SubjectBodyPosition"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td>2</td> <td>  LLD <a name="LLD"> </a> </td> <td>left lateral decubitus</td> <td> Lying on the left side. <br/> </td> </tr> <tr> <td>2</td> <td>  PRN <a name="PRN"> </a> </td> <td>prone</td> <td> Lying with the front or ventral surface downward; lying face down. <br/> </td> </tr> <tr> <td>2</td> <td>  RLD <a name="RLD"> </a> </td> <td>right lateral decubitus</td> <td> Lying on the right side. <br/> </td> </tr> <tr> <td>2</td> <td>  SFWL <a name="SFWL"> </a> </td> <td>Semi-Fowler's</td> <td> A semi-sitting position in bed with the head of the bed elevated approximately 45 degrees. <br/> </td> </tr> <tr> <td>2</td> <td>  SIT <a name="SIT"> </a> </td> <td>sitting</td> <td> Resting the body on the buttocks, typically with upper torso erect or semi erect. <br/> </td> </tr> <tr> <td>2</td> <td>  STN <a name="STN"> </a> </td> <td>standing</td> <td> To be stationary, upright, vertical, on one's legs. <br/> </td> </tr> <tr> <td>2</td> <td>  SUP <a name="SUP"> </a> </td> <td>supine</td> <td/> </tr> <tr> <td>3</td> <td>    RTRD <a name="RTRD"> </a> </td> <td>reverse trendelenburg</td> <td> Lying on the back, on an inclined plane, typically about 30-45 degrees with head raised and feet lowered. <br/> </td> </tr> <tr> <td>3</td> <td>    TRD <a name="TRD"> </a> </td> <td>trendelenburg</td> <td> Lying on the back, on an inclined plane, typically about 30-45 degrees, with head lowered and feet raised. <br/> </td> </tr> <tr> <td>1</td> <td> <span style="color: grey"> <i>(_VerificationOutcomeValue)</i> </span> <b> <i>Abstract</i> </b> </td> <td> <a name="_VerificationOutcomeValue"> </a> </td> <td> Values for observations of verification act results <br/> Examples: Verified, not verified, verified with warning. <br/> </td> </tr> <tr> <td>2</td> <td>  ACT <a name="ACT"> </a> </td> <td>active coverage</td> <td> Definition: Coverage is in effect for healthcare service(s) and/or product(s). <br/> </td> </tr> <tr> <td>2</td> <td>  ACTPEND <a name="ACTPEND"> </a> </td> <td>active - pending investigation</td> <td> Definition: Coverage is in effect for healthcare service(s) and/or product(s) - Pending Investigation <br/> </td> </tr> <tr> <td>2</td> <td>  ELG <a name="ELG"> </a> </td> <td>eligible</td> <td> Definition: Coverage is in effect for healthcare service(s) and/or product(s). <br/> </td> </tr> <tr> <td>2</td> <td>  INACT <a name="INACT"> </a> </td> <td>inactive</td> <td> Definition: Coverage is not in effect for healthcare service(s) and/or product(s). <br/> </td> </tr> <tr> <td>2</td> <td>  INPNDINV <a name="INPNDINV"> </a> </td> <td>inactive - pending investigation</td> <td> Definition: Coverage is not in effect for healthcare service(s) and/or product(s) - Pending Investigation. <br/> </td> </tr> <tr> <td>2</td> <td>  INPNDUPD <a name="INPNDUPD"> </a> </td> <td>inactive - pending eligibility update</td> <td> Definition: Coverage is not in effect for healthcare service(s) and/or product(s) - Pending Eligibility Update. <br/> </td> </tr> <tr> <td>2</td> <td>  NELG <a name="NELG"> </a> </td> <td>not eligible</td> <td> Definition: Coverage is not in effect for healthcare service(s) and/or product(s). May optionally include reasons for the ineligibility. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>1</td> <td> <span style="color: grey"> <i>(_AnnotationValue)</i> </span> <b> <i>Abstract</i> </b> <b> <i>Deprecated</i> </b> </td> <td> <a name="_AnnotationValue"> </a> </td> <td/> </tr> <tr style="background: #EFEFEF"> <td>1</td> <td> <span style="color: grey"> <i>(_CommonClinicalObservationValue)</i> </span> <b> <i>Abstract</i> </b> <b> <i>Deprecated</i> </b> </td> <td> <a name="_CommonClinicalObservationValue"> </a> </td> <td> Description:Used in a patient care message to value simple clinical (non-lab) observations. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>1</td> <td> <span style="color: grey"> <i>(_IndividualCaseSafetyReportValueDomains)</i> </span> <b> <i>Abstract</i> </b> <b> <i>Deprecated</i> </b> </td> <td> <a name="_IndividualCaseSafetyReportValueDomains"> </a> </td> <td> 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td>1</td> <td> <span style="color: grey"> <i>(_IndicationValue)</i> </span> <b> <i>Abstract</i> </b> <b> <i>Deprecated</i> </b> </td> <td> <a name="_IndicationValue"> </a> </td> <td> 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. <br/> </td> </tr> </table> </div> </text> <url value="http://hl7.org/fhir/ValueSet/v3-ObservationValue"/> <version value="2016-03-23"/> <name value="v3 Code System ObservationValue"/> <status value="active"/> <experimental value="false"/> <publisher value="HL7, Inc"/> <contact> <telecom> <system value="other"/> <value value="http://hl7.org"/> </telecom> </contact> <date value="2016-03-23"/> <description value=" This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type. OpenIssue: Description copied from Concept Domain of same name. Must be corrected.."/> <compose> <include> <system value="http://hl7.org/fhir/v3/ObservationValue"/> </include> </compose> </ValueSet>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
© HL7.org 2011+. FHIR STU3 Candidate (v1.4.0-8139) generated on Thu, Mar 31, 2016 08:14+1100. QA Page
Links: Search |
Version History |
Table of Contents |
Compare to DSTU2 |
|
Propose a change