Stream: implementers
Topic: Store as XML or Jason
Rob Kr (Jul 23 2021 at 17:12):
Was testing out the FHIR plugin for Mirth Connect, which works off a database design that basically only has 1 table called "resource". Every message and operation I throw at it seems to work. Two questions: Is this a bad idea to do or should we be looking to adopt a schema like FHIRBASE, where there is a table for each resource
?
And this table, although Mirth accepts JSON and XML, stores the message as XML. Is there a disadvantage to this or would storing the JSON be preferred?
David Pyke (Jul 23 2021 at 17:16):
I'm a big believer that if it works, it works. So, if it works, go with it. And the XML vs JSON format isn't really important as FHIR innately supports both (and Turtle) so, store it in whatever works best for your use case
Lloyd McKenzie (Jul 23 2021 at 18:51):
How you store is primarily driven by how you need to query/analyze. Storing resources as a blob is a very viable strategy when the only interface accessing the data will be FHIR-based. On the other hand, if you need to perform ad-hoc query and analysis or need to expose the data over other types of interfaces, it may not work well. There's a whole stream (#storage for FHIR) dedicated to the tradeoffs of different approaches to FHIR-based persistence.
Last updated: Apr 12 2022 at 19:14 UTC
