HL7.TERMINOLOGY\PopulationInclusionObservationType

This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: PopulationInclusionObservationType

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-PopulationInclusionObservationType

Version:

2.0.0

Name:

PopulationInclusionObservationType

Status:

Active as of 2014-03-26

Definition:

Observation types for specifying criteria used to assert that a subject is included in a particular population.

OID:

2.16.840.1.113883.1.11.20476 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Include codes from http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a _PopulationInclusionObservationType

Expansion

This value set contains 10 concepts

Expansion based on ActCode v5.0.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v3-ActCode

Lvl	Code	Display	Definition
0	_PopulationInclusionObservationType	PopulationInclusionObservationType	Observation types for specifying criteria used to assert that a subject is included in a particular population.
1	DENEX	denominator exclusions	Criteria which specify subjects 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.
1	DENEXCEP	denominator exceptions	Criteria which specify the removal of a subject, 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: * Medical reasons * Patient (or subject) reasons * System reasons
1	DENOM	denominator	Criteria for specifying the entities to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). The denominator can be the same as the initial population, or it may be a subset of the initial population to further constrain it 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.
1	IPOP	initial population	Criteria for specifying the entities to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs).
2	IPPOP	initial patient population	Criteria for specifying the patients to be evaluated by a specific quality measure, based on a shared common set of 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.
1	MSROBS	measure observation	Defines the observation to be performed for each patient or event in the measure population. Measure observations for each case in the population are aggregated to determine the overall measure score for the population. Examples: * the median time from arrival in the Emergency Room to departure * the median time from decision to admit to a hospital to the actual admission for Emergency Room patients
1	MSRPOPL	measure population	Criteria for specifying the measure population as a narrative description (e.g., all patients seen in the Emergency Department during the measurement period). This is used only in continuous variable eMeasures.
1	MSRPOPLEX	measure population exclusions	Criteria for specifying subjects who should be removed from the eMeasure's Initial Population and Measure Population. Measure Population Exclusions are used in Continuous Variable measures to help narrow the Measure Population before determining the value(s) of the continuous variable(s).
1	NUMER	numerator	Criteria for specifying the processes or outcomes expected for each patient, procedure, or other unit of measurement defined in the denominator for proportion measures, or related to (but not directly derived from) the denominator for ratio measures (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).
1	NUMEX	numerator exclusions	Criteria for specifying 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). Numerator Exclusions are used only in ratio eMeasures.

Explanation of the columns that may appear on this page:

Level

A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies

Source

The source of the definition of the code (when the value set draws in codes defined elsewhere)

Code

The code (used as the code in the resource instance)

Display

The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application

Definition

An explanation of the meaning of the concept

Comments

Additional notes about how to use the code

History

Date

Action

Custodian

Author

Comment

2020-05-06

revise