In Bahmni, we are trying to use Patient Matching Module. When we create a strategy with a few fields as Should Match, It is not sent to the server from the client side javascript (We arrived at this conclusion by looking at this part of the code ).
However in the UI at-least one field has to be selected as Should Match. We are wondering how is Should Match considered in Matching Patients.
@sid, I don’t think many people have experience with that module, but hopefully some do and can answer! (I personally have not used the module, or looked at the code.)
I assume you have read the documentation wiki page. (This says you have to specify at least one Must and at least one Should.)
It might help if you could share an example of the strategy that you created, and whether running the matching algorithm behaved as you expected or not…
@darius, Here I have given an example strategy that we tried to create.
What we tried:
Must Match : (Identifier) Old Identification Number
Should Match: (Patient) Gender, (Address) City / Village, (Address) District
The error message we got:
A javascript error has occurred: Proxy ErrorThe full stacktrace for this error can usually be found in your server’s error logs.
It turns out that there are a few people actively working on this module as we speak.
In particular, Andrew Martin and @sgrannis are refreshing this module to make it more compatible with later versions of OpenMRS, and I believe are also adding new features.
Hi All! Sid - looks like you might have switched the “must match” and “should match” fields. The National Identifier generally is a “Must Match”, the others are better configured as “Should Match.” Give that a try.