[Feature Request]Support for "prefer" header about fhir-works-on-aws-search-es HOT 3 CLOSED

Hi @vvedantham ,

Thanks for reaching out! I'll take this request back to the team.

Thanks,
Yanyu

from fhir-works-on-aws-search-es.

Hi @vvedantham,

Sadly we'll not be prioritizing this feature at the current point. If you're interested in implementing it yourself, here're the rough steps of how it could work:

• Update interface package so the header can be passed into search package
• Update the routing package to parse and pass the header
• Update search package to respect the prefer header - search for InvalidSearchParameterError in the package and decide which ones should be ignored

Hope this helps!

Thanks,
Yanyu

from fhir-works-on-aws-search-es.

FHIR Works on AWS has been moved to maintenance mode. While in maintenance, we will not add any new features to this solution. All security issues should be reported directly to AWS Security at [email protected]. If you are new to this solution, we advise you to explore using HealthLake, which is our managed service for building FHIR based transactional and analytics applications. You can get started by contacting your AWS Account team. If you are an existing customer
of FHIR Works on AWS, and have additional questions or need immediate help, please reach out to [email protected] or contact your AWS Account team.

from fhir-works-on-aws-search-es.