I wanted to expose “Find Patients to Merge” functionality through REST API as part of my GSoC 2021 task.
First I wanted to try out the existing UI. However, when selecting one of these 3 fields: Given, Middle, Family Name, I receive the following SQL Exception:
I’m running OpenMRS server version: 2.4.0 Build e4adbd
We have an automated test that captures patient merge, one has to ensure that there exists two patient data set in the db instance for the action to be effective. Ideally the better way would be creating your own patient data than relying on the existing data within the server and then perform the action.
But if the test am pointing out does not capture @navareth use case, then we can have it automated if more light is thrown on the idea behind the use case. cc: @sharif
There’s a way to search for patients in ref app 2.x and selecting the first and second inputs the first and second patient ids automatically and this works perfectly at https://qa-refapp.openmrs.org/.
The legacy ui doesn’t perhaps support finding patients by name, it relies on knowing the patient ids, please go ahead and create a ticket for this @navareth in https://issues.openmrs.org/projects/LUI/issues and if you have time and desperately need this work on it.
The automated test doesn’t use the search option in ref app 2.x, @grace@christine can we can this feature in one of our workflows and include the search for patient in that instead?
The legacy UI does support finding patients by name, however, the core webapp throws an exception when trying to do so. That’s why I think creating an issue in the TRUNK project makes more sense.