fhir-data-pipes
fhir-data-pipes copied to clipboard
google
Document current parquet schema for the sql-on-FHIR v1 and come up with a plan to standardize it with the community
Currently the parquet schema that is implemented by fhir-data-pipes and the Pathing for extensions is different. Discuss in the FHIR community and come to consensus on a common schema.
One update here is that there has been some discussions in the community for this standardization and here is a draft document in which various issues are being discussed.
One issue that I recently had to deal with was again around the way that we (i.e., Bunsen) deal with extensions. I had a Parquet file that was generated from an R4 Condition resource but without any extra extension StructureDefinitions. Then I was reading it in another pipeline which had --structureDefinitionsPath set to r4-us-core-definitions. This was causing a strange ArrayIndexOutOfBoundsException where the root cause was the extra assertedDate in the US-Core version which was expected but not present in the input Parquet file.
We will experiment with the new proposed schema which is extension independent.