HL7 Terminology (THO)
5.2.0 - Publication
This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/v3-PopulationInclusionObservationType | Version: 2.0.0 | |||
Active as of 2014-03-26 | Computable Name: PopulationInclusionObservationType | |||
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.20476 |
Observation types for specifying criteria used to assert that a subject is included in a particular population.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v3-ActCode
where concept is-a _PopulationInclusionObservationType
This value set contains 10 concepts
Expansion based on ActCode v8.0.1 (CodeSystem)
Level | Code | System | Display | Definition |
1 | _PopulationInclusionObservationType | http://terminology.hl7.org/CodeSystem/v3-ActCode | PopulationInclusionObservationType | Observation types for specifying criteria used to assert that a subject is included in a particular population. |
2 | DENEX | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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. |
2 | DENEXCEP | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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:
|
2 | DENOM | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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. |
2 | IPOP | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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). |
3 | IPPOP | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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. |
2 | MSROBS | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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:
|
2 | MSRPOPL | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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. |
2 | MSRPOPLEX | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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). |
2 | NUMER | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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). |
2 | NUMEX | http://terminology.hl7.org/CodeSystem/v3-ActCode | 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 |
System | 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 | Author | Custodian | Comment |
2022-10-18 | revise | Marc Duteau | TSMG | Fixing missing metadata; up-349 |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |
2014-03-26 | revise | Vocabulary (Woody Beeler) (no record of original request) | 2014T1_2014-03-26_001283 (RIM release ID) | Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26 |