Custom Search Parameters in HAPI FHIR

[cou...@googlemail.com]

Hi,

I am currently exploring the recent functionality in 2.3-SNAPSHOT for custom search parameters as described here:

https://smilecdr.com/blog/20170208_custom_search_parameters

I can get this example to work. However, this does not seem to work if I try to use Dstu2 structures and endpoints. The code runs but provides the following exception:

Exception in thread "main" ca.uhn.fhir.rest.server.exceptions.InvalidRequestException: HTTP 400 Bad Request: Unknown search parameter "eyecolour". Value search parameters for this search are: [_id, _language, active, address, address-city, address-country, address-postalcode, address-state, address-use, animal-breed, animal-species, birthdate, careprovider, deathdate, deceased, email, family, gender, given, identifier, language, link, name, organization, phone, phonetic, telecom]

I would be hugely grateful if someone could confirm that this should work with Dstu2 as it does for Dstu3.

Thanks very much for any help that you can give,

Best, Phil.

[James Agnew]

Hi Phil,

Yup, unfortunately these are only implemented for DSTU3 servers so far. We're planning on doing DSTU2 also, but it hasn't happened yet. Happy to offer pointers if anyone wants to volunteer to help speed it up!

Cheers,

James

--
You received this message because you are subscribed to the Google Groups "HAPI FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hapi-fhir+unsubscribe@googlegroups.com.
To post to this group, send email to hapi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hapi-fhir/baac9702-bf72-4e62-a55c-981e876ab632%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[cou...@googlemail.com]

Hi James,

OK, thanks. We are tied into DSTU2 for now due to the use of other tools, such as Forge and Simplifier, that do not currently support DSTU3. A huge thank you for your work on custom search parameters, this is key for our project that involves working with profiles. Do you have a rough idea when this functionality might be implemented for DSTU2? Depending on the complexity of the task we could take a look, if you would be happy to provide some initial guidance/ pointers.

Thanks again, Phil.

On Wednesday, 8 March 2017 17:50:50 UTC, James Agnew wrote:

Hi Phil,

Yup, unfortunately these are only implemented for DSTU3 servers so far. We're planning on doing DSTU2 also, but it hasn't happened yet. Happy to offer pointers if anyone wants to volunteer to help speed it up!

Cheers,

James

On Tue, Mar 7, 2017 at 12:31 PM, couchpa via HAPI FHIR <hapi...@googlegroups.com> wrote:

Hi,

I am currently exploring the recent functionality in 2.3-SNAPSHOT for custom search parameters as described here:

https://smilecdr.com/blog/20170208_custom_search_parameters

I can get this example to work. However, this does not seem to work if I try to use Dstu2 structures and endpoints. The code runs but provides the following exception:

Exception in thread "main" ca.uhn.fhir.rest.server.exceptions.InvalidRequestException: HTTP 400 Bad Request: Unknown search parameter "eyecolour". Value search parameters for this search are: [_id, _language, active, address, address-city, address-country, address-postalcode, address-state, address-use, animal-breed, animal-species, birthdate, careprovider, deathdate, deceased, email, family, gender, given, identifier, language, link, name, organization, phone, phonetic, telecom]

I would be hugely grateful if someone could confirm that this should work with Dstu2 as it does for Dstu3.

Thanks very much for any help that you can give,

Best, Phil.

--
You received this message because you are subscribed to the Google Groups "HAPI FHIR" group.

To unsubscribe from this group and stop receiving emails from it, send an email to hapi-fhir+...@googlegroups.com.

[ca...@alis-sol.com.br]

Hi Phil,

I was following this thread on the same hopes as you and am dropping by to tell you the good news James gave me in another thread:

"You would be able to accomplish this with a custom search parameter which indexes this field, so it is possible to solve this problem, except that custom search parameters are not supported in DSTU2 in HAPI's JPA server (only DSTU3 / R4). The final bit of good news though is that someone has agreed to fund development of that feature, and I believe this work is actually scheduled to start next week. So we'll be implementing this by the next release (and probably in a snapshot build before then too)."

Cheers,

Carlos