We are planning to use barcode scanners to search for previously registered patients through printed barcode labels.
The patient search of the registration module allows to search for patients. However it requires a ‘decomposed’ patient id without the Identifier prefix (like GAN or SEM in your test data). So while the full ID is SEM123456 in the search box only accepts 123456. This makes sense for manual data entry, but when scanning the barcode, it will enter the full ID including this prefix.
Other search boxes, e.g. within the clinic module, work fine as they accept a full ID.
But it would be really nice to have this on the ID search too, as this jump right into the patient (as the IDs are unique). With the name search there is the additional step to choose the patient from the result list.
On this note, are identifier prefixes required in Bahmni? Is there any
way to get rid of the source prefix altogether (and have the associated
select list next to the text box hidden if it is not relevant)?
Identifier prefixes are not really required in Bahmni. They were introduced to make things easier to a registration clerk, primarily to save time.
There is no way to currently get rid of the source prefix, but it will definitely be useful to be able to configure the search page to not use a prefix dropdown.
The approach you have taken is to find out the identifier prefix that is selected from drop down and replace the same thing from the patientSearch value.This works fine only if there is one identifier source used always.
Lets say if the barcode scanner needs to search by both “GAN” and “SEM”, there is a problem with search.
Scenario 1: Drop down value is “GAN” and Searching with “GAN200070” works fine.
Scenario 2: Drop down value is changed to “SEM” and searching with “GAN200070” doesn’t work.
That would be good If the approach is generic enough to use available identifier sources and not just depend on the value of drop down
One will have the ability to search by Full identifier in patient registration search from 0.83v of Bahmni.
Thanks @mogoodrich for implementing the functionality and contributing to Bahmni…