FHIR Chat · DocumentReference.type · inferno

Stream: inferno

Topic: DocumentReference.type


view this post on Zulip James Dinsmore (Sep 22 2021 at 13:02):

We have instances in our data where DocumentReference.type is a LOINC code but it is not a scale type of DOC (and therefore doesn't exist in the required binding of https://www.hl7.org/fhir/us/core/STU3.1.1/ValueSet-us-core-documentreference-type.html). This is causing an Inferno failure. What is the proper way to handle this? Should we replace any of these LOINC codes with UNK when generating the FHIR payload?

view this post on Zulip Yunwei Wang (Sep 22 2021 at 17:31):

According to US Core Missing Data section,

required binding strength (CodeableConcept or code datatypes):
use the appropriate “unknown” concept code from the value set if available

The valueset http://hl7.org/fhir/us/core/ValueSet/us-core-documentreference-type includes http://terminology.hl7.org/CodeSystem/v3-NullFlavor | UNK as a valid code. So you should be able to use that.


Last updated: Apr 12 2022 at 19:14 UTC