Summary
Any Feature.RACE value received that maps to a unknown (eg UNKNOWN or ASKED_UNKNOWN) should not be used in comparisons. (This also extends to blocking as well, but Race is currently not being used as a blocking key, so no change is necessary).
Impact
When comparing two patient records on the feature RACE, we can not say the two records have a match on that field when both records have a value of unknown. The impact on this is we will be inflating matching scores on records with an unknown race field value.
Expected behavior
When generating feature values for a PIIRecord, specifically invoking the feature_iter function, values should only be emitted for a Feature.RACE input if the value is not UNKNOWN or ASKED_UNKNOWN.
Summary
Any Feature.RACE value received that maps to a unknown (eg UNKNOWN or ASKED_UNKNOWN) should not be used in comparisons. (This also extends to blocking as well, but Race is currently not being used as a blocking key, so no change is necessary).
Impact
When comparing two patient records on the feature RACE, we can not say the two records have a match on that field when both records have a value of unknown. The impact on this is we will be inflating matching scores on records with an unknown race field value.
Expected behavior
When generating feature values for a PIIRecord, specifically invoking the
feature_iterfunction, values should only be emitted for aFeature.RACEinput if the value is not UNKNOWN or ASKED_UNKNOWN.