Core Apps: Patient Search should support a configurable search handler
Description
Currently, the patient search widget provided by coreapps has a hard-coded search algorithm, which is just based on hitting the “patient” endpoint in the webservices module.
However, the webservices module supports the ability to configure different search handlers for a given resource, and to specify which of these should be used for a given request based on the s=handlerId special property.
It would be useful to add the ability to configure the coreapps module to utilize a specific search handler, if an implementation wishes to augment the default patient search algorithm provided.
Activity
Show:
Mike Seaton January 28, 2025 at 3:09 PM
Follow-up fix to the above fix here:
FYI
Mike Seaton November 7, 2024 at 3:21 PM
Fix committed here:
Mike Seaton November 7, 2024 at 3:16 PM
Edited
Our smoke tests caught the fact that this was breaking. I have a new PR out to fix this:
This introduces a new global property in the coreapps module named coreapps.patientSearchHandler. By default, this will delegate to the patientByIdentifier` search handler, which is the current behavior. An implementer can then change this to a different search handler id, which will change the patient search implementation to use that instead.
Currently, the patient search widget provided by coreapps has a hard-coded search algorithm, which is just based on hitting the “patient” endpoint in the webservices module.
However, the webservices module supports the ability to configure different search handlers for a given resource, and to specify which of these should be used for a given request based on the
s=handlerIdspecial property.It would be useful to add the ability to configure the coreapps module to utilize a specific search handler, if an implementation wishes to augment the default patient search algorithm provided.