CODEWITHSUNDEEP
case-sensitivecamelcasinghl7-fhirhapi-fhir
Stef Heyenrath
Stef Heyenrath

Reputation: 9820

HL7-Fhir : are search query parameters case-sensitive or always lowercase?

Question 1]
When checking the reference implementation example at : http://fhirtest.uhn.ca

I see that the search for http://fhirtest.uhn.ca/baseDstu2/Patient?namE=Meier returns and error message like:

{
    "resourceType":"OperationOutcome",
    "issue":[
        {
            "severity":"error",
            "diagnostics":"Invalid request: The FHIR endpoint on this server does not know how to handle GET operation[Patient] with parameters [[namE]]"
        }
    ]
}

Is this defined in the Fhir specification or is it up to the server how to deal with this?

(I found some question/response for REST API here: Should a REST API be case sensitive or non case sensitive?)


Question 2]
What about camel-cased properties like "referencedOrganization", should the query parameter also be lower-cased and look like : http://fhirtest.uhn.ca/baseDstu2/Patient?referencedorganization=abc

Upvotes: 0

Views: 1241

Answers (2)

Lloyd McKenzie
Lloyd McKenzie

Reputation: 6793

Link is here: http://hl7.org/fhir/dstu2/search.html#conformance "Servers are not required to enforce case sensitivity on parameter names, though the names are case sensitive (and URLs are generally case-sensitive)."

Longer names can be separated with dashes.

Upvotes: 1

Grahame Grieve
Grahame Grieve

Reputation: 3586

  1. parameters are specified to be case sensitive though since servers can choose to support their own additional parameters, servers can choose not to enforce case sensitivity

  2. the query parameter doesn't have be the same as a property name. The list of parameter names that are defined in the standard comes after the resource (e.g. here: http://hl7.org/fhir/patient.html#search)

Upvotes: 1

Related Questions