Stream: ibm
Topic: Search module design
Lee Surprenant (Jan 29 2020 at 19:38):
Currently, to extend the server with custom search parameters, we support the reading of a per-tenant Bundle of SearchParameters from the tenant config folder. We have a guide that outlines how this works at https://ibm.github.io/FHIR/guides/FHIRSearchConfiguration
Lee Surprenant (Jan 29 2020 at 19:39):
However, starting in version 4.0.0 we have a new fhir-registry component and this is how you extend the server with IG-specific artifacts like StructureDefinitions and ValueSets. The guide for that is at https://ibm.github.io/FHIR/guides/FHIRValidationGuide
Lee Surprenant (Jan 29 2020 at 19:40):
Many IGs (like us-core) also define their own search parameters, and it seems like we should support those from fhir-search as well. Question: what would it take to deprecate our config-driven mechanism in favor of a new fhir-registry-based approach?
Lee Surprenant (Jan 29 2020 at 19:42):
One challenge would be "how to keep our dynamic config behavior" where we have a cached version of the config resource available which will reload the resource if it changes on disk. @John Timm does the registry support (or at least enable) similar behavior yet?
Lee Surprenant (Jan 29 2020 at 19:46):
Another challenge would be building/maintaining the SearchParameter.code -> SearchParameter map. Instead of lazy-loading the SearchParameter resources by uri, I think we'd want to ask the fhir-registry to give us ALL the SearchParameters up front, so that we could build the map.
John Timm (Jan 30 2020 at 16:55):
One challenge would be "how to keep our dynamic config behavior" where we have a cached version of the config resource available which will reload the resource if it changes on disk. John Timm does the registry support (or at least enable) similar behavior yet?
@Lee Surprenant We do not support this behavior in the FHIRRegistry
Lee Surprenant (Jan 30 2020 at 18:08):
How about the "ask the fhir-registry to give us ALL the SearchParameters" behavior?
Lee Surprenant (Jan 30 2020 at 18:08):
is it only retrieve by uri ?
Paul Bastide (Jan 31 2020 at 00:53):
is the FHIR Registry multitenant?
Paul Bastide (Jan 31 2020 at 00:53):
or relies on the consumer to have specific profile urls?
John Timm (Mar 11 2020 at 21:17):
@Paul Bastide The FHIR registry component does not currently support multi-tenancy
John Timm (Mar 11 2020 at 21:20):
the registry is currently populated using the ServiceLoader
Paul Bastide (Mar 12 2020 at 12:23):
John Timm said:
the registry is currently populated using the ServiceLoader
I think we covered this on another thread - not sure. thanks for the followup
Lee Surprenant (Mar 12 2020 at 12:39):
I think it means we'd have our work cut out for us to shift the existing search support over to using the registry
Last updated: Apr 12 2022 at 19:14 UTC
