Stream: implementers
Topic: Mixing MIME types - FHIR in JSON
Gino Canessa (Feb 12 2021 at 16:21):
Hi everyone! I have an implementation question that I would love some feedback on. I've noticed that several "FHIR touching" (for lack of a better term) specifications define some sort of JSON envelope with (sometimes) a FHIR resource inside (e.g., CDS Hooks, FHIRcast, and current projects like FAST).
How are people implementing this?
As far as I can tell, developers tend towards FHIR libraries which require custom serializers and parsers (e.g., HAPI, Firely, etc.). Also as far as I can tell, those libraries do not allow for generic parsing and serializing of objects (e.g., protocol XYZ envelope object).
If people are not using FHIR libraries, FHIR JSON has some differences (small, but important!) from standard JSON... Are these differences being accounted for?
Any input would be appreciated, thanks!
Gino Canessa (Feb 16 2021 at 19:07):
bump
Last updated: Apr 12 2022 at 19:14 UTC
