Problem with Search Parameters

[KMCGit]

• We are facing an issue with the Microsoft FHIR Open Source server, where the majority of our entities have operational search parameters. While others only have some search parameters operational, and not all that are found within the code and/or Capability Statement

• We are also facing an issue in that a Search Parameter found on a Hapi Server, is not present/operational in the Microsoft FHIR version (ex. "questionnaire" on /QuestionnaireResponse)

• What could be the cause/reason for the first issue? What would be the best way to solve the second issue?

[brendankowitz]

Hi @KMCGit, do you mind providing some examples of the above. We do have some currently unsupported search parameters which you can check here: https://github.com/microsoft/fhir-server/blob/main/src/Microsoft.Health.Fhir.Core/Data/R4/unsupported-search-parameters.json

You can get QuestionnaireResponse.questionnaire working by using a custom search parameter (with a name such as questionnaireUri) typed as a uri. We currently don't have the Canonical=>Reference search type converter.

[KMCGit]

@brendankowitz Thanks for the response to the issue. Since originally posting, I did come across the Unsupported Search Parameters, and noticed it there.

One of the examples we are facing issues with, while being in the Capability Statement, is the Search Parameter QuestionnaireResponse.patient returning an error that it is not supported. In fact, all of the resource-specific Search Params for QuestionnaireResponse are non-functional with the not supported error. (We have tried Azure deployment via COSMOS + SQL for R4 and above, and all versions face this issue)

Regarding the Custom Search Parameter suggestion: The Microsoft Fhir Server is recognizing/returning that a Search Parameter by S.P. ID QuestionnaireResponse-questionnaire already exists on the server.

I have tried to PUT/POST/DELETE this Search Parameter to no success. If that is the case, how could we have a custom Search Parameter that uses "?questionnaire" exactly as typed? Since it is being reserved by QuestionnaireResponse-questionnaire, and that cannot be removed from the server, nor its search name "questionnaire" used twice?

(We would need it to be used exactly as QuestionnaireResponse?questionnaire= , otherwise we will not be compliant with a targeted FHIR Implementation guide)

Your help and response is greatly appreciated. Thanks and have a great day.

[brendankowitz]

Added a suggested workaround for using a custom search parameter here: #1873 (comment)

[KMCGit]

Thanks for that reply, it was very helpful. (I posted a reply on the issue).

I was still curious as to why QuestionnaireResponse-patient is currently not operational. It is contained within the Capability Statement, but does not work when used in a request, and does not appear in a $reindex operation.

("questionnaire" was missing from Capability Statement and non-operational, "patient" is present in the Capability Statement but is non-operational. Would it be best to open as a new issue?)

Any guidance/answer to this issue would also be extremely valuable.

[brendankowitz]

To get a better understanding, would you be able to provide me an example request and response of what you're seeing?

[KMCGit]

Hi Brendan,

I discovered that the Patient parameter is working as intended based off of "subject" reference. I was also able to implement the definition for the "questionnaire" search parameter / work around.

The last issue that we are attempting to overcome is overwriting, or deleting, the QuestionnaireResponse-questionnaire search parameter, as to post the work around with the "questionnaire" code. Is there any possible way to accomplish this?

Once again, thanks for your time.

[EXPEkesheth]

@KMCGit - We do not provide capability to override built-in search parameters, that are provisioned with FHIR service. You can create custom search parameters per use case need, as Brendan mentioned above.