Describe the bug
According to the FHIR spec, search on a token type should be case-insensitive if the underlying system (e.g. email) is, or generally when the underlying datatype is string:
Match is case sensitive unless the underlying semantics for the context indicate that the token should be interpreted case-insensitively (see, e.g. CodeSystem.caseSensitive). Note that matches on _id are always case sensitive. If the underlying data type is string then the search is not case sensitive.
However, e.g. for a patient with email myname@mydomain.com, {{server}}/fhir/Patient?email=myname@mydomain.com returns that patient, while {{server}}/fhir/Patient?email=Myname@mydomain.com (first letter capitalized) does not.
If adding another patient with the capitalized email, you still only get the one exactly matching the capitalization in the request.
This probably applies to other token search parameters as well.
Describe the bug According to the FHIR spec, search on a token type should be case-insensitive if the underlying system (e.g. email) is, or generally when the underlying datatype is
string:However, e.g. for a patient with email
myname@mydomain.com,{{server}}/fhir/Patient?email=myname@mydomain.comreturns that patient, while{{server}}/fhir/Patient?email=Myname@mydomain.com(first letter capitalized) does not. If adding another patient with the capitalized email, you still only get the one exactly matching the capitalization in the request.This probably applies to other token search parameters as well.
To Reproduce Steps to reproduce the behavior:
myname@mydomain.com/fhir/Patient?email=Myname@mydomain.comExpected behavior The created patient is returned.
Environment (please complete the following information):