You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When MDM has a Possible Match, the score of "no match" also added into total score.
To Reproduce
Steps to reproduce the behavior:
Setup MDM, enable trouble shooting logs
Create Patient/1 --> new GR created
Create Patient/2 such that it will be a POSSIBLE_MATCH and at least one MDM Match Field that uses a similarity algorithm does not match
Check troubleshooting log. Score for Patient/2 includes the no match similarity field score
Expected behavior
Score for Patient/2 SHOULD NOT include the no match similarity field score: "search score field that is calculated by averaging the number of matched rules against total rules checked for the Patient resource" in 7.3.1 in docs (https://hapifhir.io/hapi-fhir/docs/server_jpa_mdm/mdm_operations.html)
The text was updated successfully, but these errors were encountered:
jdar8
changed the title
Score for No Match Fields Should Not Be Included in Total Score
MDM Score for No Match Fields Should Not Be Included in Total Score
Jul 21, 2023
NOTE: Before filing a ticket, please see the following URL:
https://github.com/hapifhir/hapi-fhir/wiki/Getting-Help
Describe the bug
When MDM has a Possible Match, the score of "no match" also added into total score.
To Reproduce
Steps to reproduce the behavior:
Patient/1
--> new GR createdPatient/2
such that it will be aPOSSIBLE_MATCH
and at least one MDM Match Field that uses a similarity algorithm does not matchPatient/2
includes the no match similarity field scoreExpected behavior
Score for
Patient/2
SHOULD NOT include the no match similarity field score: "search score field that is calculated by averaging the number of matched rules against total rules checked for the Patient resource" in 7.3.1 in docs (https://hapifhir.io/hapi-fhir/docs/server_jpa_mdm/mdm_operations.html)The text was updated successfully, but these errors were encountered: