GET returns 404 unless id param matches the case of the stored resource about fhir-works-on-aws-routing HOT 4 CLOSED

Hey @chrisbednarski! I am struggling to find FHIR documentation that says IDs are case-insensitive. Could you provide any documentation you have, or perhaps explain your use-case?

from fhir-works-on-aws-routing.

I haven't seen this mentioned in the spec either.

We've discovered this during our dev/validation process and the thinking is that since the IDs are guids, they're not case sensitive.

so, c9d47c75-e414-49f1-9561-e70efaa645ce is the same as C9D47C75-E414-49F1-9561-E70EFAA64BCE

Theoretically, with multiple 3rd parties connecting to an endpoint, if one uses lower case ids, another one uses upper case ids, we will end up with unexpected 404s

from fhir-works-on-aws-routing.

Yeah looking at RFC4122 spec on UUIDs

The hexadecimal values "a" through "f" are output as lower case characters and are case insensitive on input

The RFC aside, I would hope clients should assume fhir ids are case-sensitive. That said, if you have clients mixing up the IDs please let us know

from fhir-works-on-aws-routing.

We can work around this by specifying the requirement of lower case ids in our documentation. Thanks

from fhir-works-on-aws-routing.