-
Notifications
You must be signed in to change notification settings - Fork 24
Composite Measure Development
Composite measures make use of multiple component measures to produce a combined score. In the most general case, a composite measure is akin to a continuous variable measure, where the measure observation for each population member is some combination of their component measure scores. However, the calculation logic involved is tedious, and a higher-level representation of the most common composite measure calculation approaches would be much simpler to work with and understand.
Based on an analysis of the example composite measures so far, the following calculation methods have been identified:
Opportunity scoring simply combines the scores from composite measures by combining the numerators and denominators for each component. In this approach, the measure score uses the same calculation logic as any proportion measure would, but the individual populations are the union of the component measure populations.
Other calculation approaches all involve a two step process where the first step involves computing the score for each patient using some formula involving component measure population criteria, and the second step involves aggregating these scores in the same way that a continuous variable measure is defined.
Note that these methods may be applied at any cross-section of the population (i.e. by Provider, by Department, by Institution, etc.)
All-or-nothing scoring includes an individual in the numerator of the composite measure if they are in the numerators of all of the component measures in which they are in the denominator.
- Denominator of composite is the union of component denominators
- Numerator of composite is 1 if all component numerators are 1, 0 otherwise
Linear scoring gives an individual a score based on the number of numerators in which they appear.
- Denominator is sum of component denominators
- Numerator is sum of component numerators
Weighted scoring gives an individual a score based on a weighted factor for each component numerator in which they appear.
- Denominator of composite is the union of component denominators
- Each component numerator is assigned some percentage weight and the score is the sum of the weights.
Rather than require measure authors to write the tedium, only require the unique inputs necessary for each calculation type.
All composite measure types would need to specify the component measures. For opportunity scoring, this is all that is required, the implicit logic appropriate for the specified measure type is applied.
Note that the measure type and "basis" (i.e. patient, encounter, procedure) must be the same for all component measures in a given composite measure.
For methods other than opportunity scoring, an aggregation method is required, which would be specified in the same way as continuous variable aggregation methods are specified.
For weighted scoring, the percentage weight of each measure is required.
These could all be represented as Continuous Variable Measures, with tooling to automatically produce the required Measure Observation function based on the Component Measures and the selected calculation method.
In this way, composite measures could be handled by implementers with the same machinery they would already be providing for consumption of CQL-based measures.
Note also that nothing prevents the use of libraries and direct CQL to write more complex composite measures. The patterns identified here would enable simple expression of what are so far the most common patterns for composites.
For representation in HQMF, the existing related document mechanism will be used to identify the component measures. In addition, a new element, "Composite Measure Scoring" must be defined to indicate what type of scoring method is being used for the composite measure. This type would have the following values:
- Opportunity
- All-or-nothing
- Linear
- Weighted
Authoring Patterns - QICore v4.1.1
Authoring Patterns - QICore v5.0.0
Authoring Patterns - QICore v6.0.0
Cooking with CQL Q&A All Categories
Additional Q&A Examples
Developers Introduction to CQL
Specifying Population Criteria