You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[16:05:23] Al Amyot: Ewout, I've also noticed that on your server, "birthdate=1945-01-01" returns 1 result and "birthDate=1945-01-01" returns ALL results. I've searched the FHIR spec for references to case sensitivity/capitalization and have not managed to find whether the terms should be case-sensitive or not. Is your server's behaviour correct? If the term should be case-sensitive, should the server return an error when the wrong one is supplied?
The text was updated successfully, but these errors were encountered:
From the spec: Servers are not required to enforce case sensitivity on parameter names, though the names are case sensitive (and URLs are generally case-sensitive).
The server doesn't have to return an error for search parameters it doesn't understand. When issue #44 has been resolved, it will be more clear the server didn't take birthDate into account.
[16:05:23] Al Amyot: Ewout, I've also noticed that on your server, "birthdate=1945-01-01" returns 1 result and "birthDate=1945-01-01" returns ALL results. I've searched the FHIR spec for references to case sensitivity/capitalization and have not managed to find whether the terms should be case-sensitive or not. Is your server's behaviour correct? If the term should be case-sensitive, should the server return an error when the wrong one is supplied?
The text was updated successfully, but these errors were encountered: