Distinct Count Aggregation for measures allows count-oriented measures to avoid the double-counting problem. This would most typically happen in cases such as:
Distinct Count measures use a special dimension that is otherwise hidden from end users. During measure loads, PMF uses the special dimension to differentiate the counted values and ensure no double-counting when summing values that match along that dimension.
The following steps explain how to set up Distinct Count measures.
The New Dimension panel opens.
Note: The Distinct Count setting is non-destructive, so you can disable and re-enable it to see the differences in how measure data is processed.
For more information on how to use the Dimension Loader, see the PMF Administration Guide.
For example, for the Hospital Event example mentioned previously, you might load all of your patient IDs into this dimension. During Distinct Count processing, PMF would check to see if a patient ID was re-used during any higher level Time aggregation, and prevent that patient from being counted more than once.
For example, you would not see the drop-down of the dimension on the Analysis Designer, the Measure Entry panel, or the drop-downs for Gadget Preferences.
Note: Currently, the Distinct Count capability requires you to use Fixed Targets, not loaded. In the previous example, note that Alternate Time Summary is active, and the Time Summary drop-down is set to Most Recent. Since flags can change to on or off during any time period, setting this to Most Recent enables PMF to always display the most current state within the desired Time level.
In the example above, which is a Flag type Distinct Count measure, note the Edit on ACTUAL_NUMERATOR, which points to the proper field and sets the value to 1 if the KPI_5 flag field contains Y.