Stream: social
Topic: FHIR Charset Support
Sarvesh Padwal (Jul 01 2019 at 06:46):
I have learned that FHIR has uniform charset support for UTF 8. But We can also send content in json with specific language which has UTF 16 using extension. So where is charset (UTF 8) applied?
Lloyd McKenzie (Jul 01 2019 at 14:13):
FHIR instances must be UTF-8. No exceptions. UTF-16 is not permitted. (Where did you see any indication of support for UTF-16?)
Lloyd McKenzie (Jul 01 2019 at 14:14):
(Also, this should probably have been raised under #implementers rather than #social :)
Dave deBronkart (Jul 01 2019 at 18:15):
I suspect that when @Sarvesh Padwal said "we can also send", he meant his company's products, not "we FHIR users" :-)
Sarvesh Padwal (Jul 02 2019 at 05:07):
I think I did not mention it clearly. yes FHIR instances must be UTF 8. But According to Internationalization (https://www.hl7.org/fhir/languages.html), we can send content in any language. Chinese characters are UTF 16, that means FHIR also allows content to be sent in Chinese content which is actually UTF 16. This is the reason for my confusion.
Lloyd McKenzie (Jul 02 2019 at 13:57):
My understanding is that any character that can be expressed in UTF-16 can also be represented in UTF-8. You'll just need to change the encoding.
Grahame Grieve (Jul 03 2019 at 13:45):
right. this is a confusion between Unicode and UTF-8. All unicode characters have a UTF-8 representation
Last updated: Apr 12 2022 at 19:14 UTC
