Currently, the HealthConnectToFHIR mapper adds LOINC codes to each FHIR observation generated from a Health Connect Record. However, it may be useful to also add the Health Connect Record class name as a code as well, as it can facilitate mapping in the reverse direction as well as make it easier for users to understand the origin of the data when mixed with FHIR observations from other sources, such as HealthKitOnFHIR on iOS.
In addition, several Health Connect Records do not have corresponding LOINC codes, therefore providing the Health Connect Record class name is the only way to identify them.
Adds Health Connect codings to mapper
:recycle: Current situation & Problem
Currently, the HealthConnectToFHIR mapper adds LOINC codes to each FHIR observation generated from a Health Connect Record. However, it may be useful to also add the Health Connect Record class name as a code as well, as it can facilitate mapping in the reverse direction as well as make it easier for users to understand the origin of the data when mixed with FHIR observations from other sources, such as HealthKitOnFHIR on iOS.
In addition, several Health Connect Records do not have corresponding LOINC codes, therefore providing the Health Connect Record class name is the only way to identify them.
The corresponding library on iOS - HealthKitOnFHIR - also does this: https://github.com/StanfordBDHG/HealthKitOnFHIR/blob/main/Sources/HealthKitOnFHIR/Resources/HKSampleMapping.json
Release Notes
Adds the Health Connect Record class name as the second coding for each Record in the mapper.
:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: