User that wants to take advantage of versioning cannot use a generic mechanism for reading structure definitions alike other resources.
SELECT fhir_read_resource('{"resourceType": "STRUCTUREDEFINITION", "id": "Patient"}');
returns only the content of resource column and the structure definitions loaded initially don't contain meta sections.
So to take advantage of versioning, reading of structure definitions has to be implemented differently than all other resources or fhirbase user has to add a custom migration
Could we add the meta sections to the preloaded StructureDefinitions ?
User that wants to take advantage of versioning cannot use a generic mechanism for reading structure definitions alike other resources.
SELECT fhir_read_resource('{"resourceType": "STRUCTUREDEFINITION", "id": "Patient"}'); returns only the content of resource column and the structure definitions loaded initially don't contain meta sections. So to take advantage of versioning, reading of structure definitions has to be implemented differently than all other resources or fhirbase user has to add a custom migration
Could we add the meta sections to the preloaded StructureDefinitions ?