You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
right now Bunsen creates encoder / schema for the entire set of resource elements. Realistically though FHIR servers would return a limited set of vendor specific elements and they would commonly be described in FHIR profile. I think it would simplify greatly schemas in Spark and reduce confusion for users since dataframes will contain only actual elements, support by a vendor.
The text was updated successfully, but these errors were encountered:
I think we can do this pretty easily but will need to take a closer look at how we can pull in profiles. All of our schemas and encoders are generated from the RuntimeResourceDefinition in the HAPI library. [1] So, if there is a way to get a RuntimeResourceDefinition for a given profile, we should be able to drop it right in and only the appropriate fields would be generated. I haven't worked enough with HAPI and specific profiles to have a good idea of how to put that together, but I'd presume there is a good way to do so.
right now Bunsen creates encoder / schema for the entire set of resource elements. Realistically though FHIR servers would return a limited set of vendor specific elements and they would commonly be described in FHIR profile. I think it would simplify greatly schemas in Spark and reduce confusion for users since dataframes will contain only actual elements, support by a vendor.
The text was updated successfully, but these errors were encountered: