The HealthVault FHIR Library is a community project started by Microsoft and Get Real Health seeking to produce an open source library for apps that utilize the HL7's FHIR Standard so they can interoperate with the data types used by HealthVault and Get Real Health’s CHBase.
MIT License
26
stars
14
forks
source link
Should we limit the transformation to a one-to-one basis? #26
Currently all Fhir resources are transformed to a single datatype and vice versa. However looking at few Fhir resources, it seems we should take a one to many approach here. Let's take the example of Procedure. It can have an observation as a property (partOf). We should ideally parse both items from the Fhir resource as two separate HealthVault items and set a relationship between them. This is just an example; if you look at the Procedure resource it self, there are a handful of references to other transformable data points.
Currently all Fhir resources are transformed to a single datatype and vice versa. However looking at few Fhir resources, it seems we should take a one to many approach here. Let's take the example of Procedure. It can have an observation as a property (partOf). We should ideally parse both items from the Fhir resource as two separate HealthVault items and set a relationship between them. This is just an example; if you look at the Procedure resource it self, there are a handful of references to other transformable data points.
Thoughts?