HL7.TERMINOLOGY\ObservationQualityMeasureAttribute

This page is part of the HL7 Terminology (v2.0.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: ObservationQualityMeasureAttribute

Summary

Defining URL:

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

Version:

2.0.0

Name:

ObservationQualityMeasureAttribute

Status:

Active as of 2014-03-26

Definition:

Codes used to define various metadata aspects of a health quality measure.

OID:

2.16.840.1.113883.1.11.20366 (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 _ObservationQualityMeasureAttribute

Expansion

This value set contains 32 concepts

Expansion based on ActCode v2.1.0 (CodeSystem)

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

Lvl	Code	Display	Definition
0	_ObservationQualityMeasureAttribute	ObservationQualityMeasureAttribute	Codes used to define various metadata aspects of a health quality measure.
1	AGGREGATE	aggregate measure observation	Indicates that the observation is carrying out an aggregation calculation, contained in the value element.
1	CMPMSRMTH	composite measure method	Indicates what method is used in a quality measure to combine the component measure results included in an composite measure.
1	CMPMSRSCRWGHT	component measure scoring weight	An attribute of a quality measure describing the weight this component measure score is to carry in determining the overall composite measure final score. The value is real value greater than 0 and less than 1.0. Each component measure score will be multiplied by its CMPMSRSCRWGHT and then summed with the other component measures to determine the final overall composite measure score. The sum across all CMPMSRSCRWGHT values within a single composite measure SHALL be 1.0. The value assigned is scoped to the composite measure referencing this component measure only.
1	COPY	copyright	Identifies the organization(s) who own the intellectual property represented by the eMeasure.
1	CRS	clinical recommendation statement	Summary of relevant clinical guidelines or other clinical recommendations supporting this eMeasure.
1	DEF	definition	Description of individual terms, provided as needed.
1	DISC	disclaimer	Disclaimer information for the eMeasure.
1	FINALDT	finalized date/time	The timestamp when the eMeasure was last packaged in the Measure Authoring Tool.
1	GUIDE	guidance	Used to allow measure developers to provide additional guidance for implementers to understand greater specificity than could be provided in the logic for data criteria.
1	IDUR	improvement notation	Information on whether an increase or decrease in score is the preferred result (e.g., a higher score indicates better quality OR a lower score indicates better quality OR quality is within a range).
1	ITMCNT	items counted	Describes the items counted by the measure (e.g., patients, encounters, procedures, etc.)
1	KEY	keyword	A significant word that aids in discoverability.
1	MEDT	measurement end date	The end date of the measurement period.
1	MSD	measurement start date	The start date of the measurement period.
1	MSRADJ	risk adjustment	The method of adjusting for clinical severity and conditions present at the start of care that can influence patient outcomes for making valid comparisons of outcome measures across providers. Indicates whether an eMeasure is subject to the statistical process for reducing, removing, or clarifying the influences of confounding factors to allow more useful comparisons.
1	MSRAGG	rate aggregation	Describes how to combine information calculated based on logic in each of several populations into one summarized result. It can also be used to describe how to risk adjust the data based on supplemental data elements described in the eMeasure. (e.g., pneumonia hospital measures antibiotic selection in the ICU versus non-ICU and then the roll-up of the two). Open Issue: The description does NOT align well with the definition used in the HQMF specfication; correct the MSGAGG definition, and the possible distinction of MSRAGG as a child of AGGREGATE.
1	MSRIMPROV	health quality measure improvement notation	Information on whether an increase or decrease in score is the preferred result. This should reflect information on which way is better, an increase or decrease in score.
1	MSRJUR	jurisdiction	The list of jurisdiction(s) for which the measure applies.
1	MSRRPTR	reporter type	Type of person or organization that is expected to report the issue.
1	MSRRPTTIME	timeframe for reporting	The maximum time that may elapse following completion of the measure until the measure report must be sent to the receiver.
1	MSRSCORE	measure scoring	Indicates how the calculation is performed for the eMeasure (e.g., proportion, continuous variable, ratio)
1	MSRSET	health quality measure care setting	Location(s) in which care being measured is rendered Usage Note: MSRSET is used rather than RoleCode because the setting applies to what is being measured, as opposed to participating directly in the health quality measure documantion itself).
1	MSRTOPIC	health quality measure topic type
1	MSRTP	measurement period	The time period for which the eMeasure applies.
1	MSRTYPE	measure type	Indicates whether the eMeasure is used to examine a process or an outcome over time (e.g., Structure, Process, Outcome).
1	RAT	rationale	Succinct statement of the need for the measure. Usually includes statements pertaining to Importance criterion: impact, gap in care and evidence.
1	REF	reference	Identifies bibliographic citations or references to clinical practice guidelines, sources of evidence, or other relevant materials supporting the intent and rationale of the eMeasure.
1	SDE	supplemental data elements	Comparison of results across strata can be used to show where disparities exist or where there is a need to expose differences in results. For example, Centers for Medicare & Medicaid Services (CMS) in the U.S. defines four required Supplemental Data Elements (payer, ethnicity, race, and gender), which are variables used to aggregate data into various subgroups. Additional supplemental data elements required for risk adjustment or other purposes of data aggregation can be included in the Supplemental Data Element section.
1	STRAT	stratification	Describes the strata for which the measure is to be evaluated. There are three examples of reasons for stratification based on existing work. These include: (1) evaluate the measure based on different age groupings within the population described in the measure (e.g., evaluate the whole \[age 14-25\] and each sub-stratum \[14-19\] and \[20-25\]); (2) evaluate the eMeasure based on either a specific condition, a specific discharge location, or both; (3) evaluate the eMeasure based on different locations within a facility (e.g., evaluate the overall rate for all intensive care units and also some strata include additional findings \[specific birth weights for neonatal intensive care units\]).
1	TRANF	transmission format	Can be a URL or hyperlinks that link to the transmission formats that are specified for a particular reporting program.
1	USE	notice of use	Usage notes.

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

Author

Custodian

Comment

2020-05-06

revise