The main use case for me to base a persistance layer on FHIR, is in case of analytical purpose. One can base it’s anaystics programs on FHIR and profiles. Have you heard of any similar project ?
Sure a resource (say specimen https://www.hl7.org/fhir/specimen.html ) would be represented as multiple tables (specimen, collection, processing, container). Recursive table is not incompatible with csv, or RDBMS table. By example specimen has the parent that point to an other specimen. In a RDBMS representation, the foreign key parent would point to the same table (called recursive table).
Can you please share a resource example that would be a problem in such relational representation ?
Do you mean JSON is a better choice ? A resource would be a JSON object instead of X tables. But that’s all the benefits isn’t ?
In my understanding, a set resource is always associated with a set of profiles. So any system that would exploit that set of resource would base on profiles. This does not solve all the backward compatibility problems, but many of them. A persistance layer based on FHIR would be defined with a set of profiles.
Thanks a lot