FHIR Chat · Required bindings and data absent reason

Stream: implementers

Topic: Required bindings and data absent reason

James Butler (Aug 31 2016 at 22:25):

We are producing AllergyIntolerance resources from ADT messages, and we're trying to work out what to do with reaction.severity if we can't map to one of the required codes. We'd like to provide an extension containing the original unmapped value, and a reason code explaining that it couldn't be mapped, and the natural place to put this is in the (otherwise empty) severity element itself.
However the definitions of required binding and the absent reason extension seem to conflict a little - first, it's not clear whether we're allowed to have a code with a required binding and no value, and second, whether data-absent-reason can or should be applied to elements with a minimum cardinality of zero.
Any thoughts?

Eric Haas (Sep 01 2016 at 00:26):

Yes and yes. This is valid:

<severity>
        <extension url="http://hl7.org/fhir/StructureDefinition/data-absent-reason">
            <valueCode value="unsupported"/>
        </extension>
    </severity>

James Butler (Sep 01 2016 at 00:28):

Excellent, thanks. I might put in a request to change the wording of required - "To be conformant, instances of this element SHALL include a code from the specified value set" would seem to preclude it.

Eric Haas (Sep 01 2016 at 00:40):

The binding refers to the code to use in the element. I think that part is clear. What I did notice is that there isn't really a data absent reason code that describes your use case of "can't map it ". ( there was a STU3 change in this valueset that I was not aware of) Should be 'OTH'

James Butler (Sep 01 2016 at 00:44):

To me, the "...SHALL include a code from..." implies that you can't have a severity with no code.

Richard Townley-O'Neill (Sep 01 2016 at 01:11):

Lee Surprenant (Sep 20 2017 at 16:44):

I'd like to revive this old thread. Based on http://build.fhir.org/terminologies.html#code, I'm wondering if its allowed to set data-absent-reason for a CodeableConcept element with a required binding (required via a profile). It seems like not to me due to the following statement "at least one Coding element SHALL be present".

Grahame Grieve (Sep 20 2017 at 23:21):

I think you can have the extension, but you still need to have a coding

Dhivakar Siddhu (Jun 03 2021 at 07:42):

Hey, I want to do data absent reason for Formulary coverageplan status & mode, both are datatype of "code". Any suggestions how to do that?

Lloyd McKenzie (Jun 03 2021 at 14:46):

You can't. If an element has type 'code', that means it has a required binding. If an element has a required binding in order to include the element, you MUST have a value from the specified value set. If the element is mandatory, then you can't include the containing element. If the containing element is the resource, then you can't create an instance that conforms to the profile.

Lloyd McKenzie (Jun 03 2021 at 14:47):

If you think there are mandatory elements that aren't reasonable to populate, then please provide that as feedback to the IG authors using the 'propose a change' link. In the interim, you'll need to decide whether to be non-conformant or to suppress some of your data.

Rey Limosenero (Jun 07 2021 at 13:33):

We are also trying to conform fhir standards on null values especially dates . can anybody help?

Yunwei Wang (Jun 07 2021 at 13:39):

Can you be more specific?

Rey Limosenero (Jun 07 2021 at 13:53):

ah yes, we are getting nulls on 1..1 fields. ex issued in the diagnosticreport profile. so we want to implement the dataabsentreason "unknown". but can't find the snippet for the implementation.

Yunwei Wang (Jun 07 2021 at 14:01):

Which IG are you implementing? DiagnosticReport.issued in base FHIR is optional.

Justin Miller (Jun 07 2021 at 14:03):

Hello Yunwei, we are implementing USCore and specifically US Core DiagnosticReport Lab

Rey Limosenero (Jun 07 2021 at 14:09):

Also we are using FHIR r4

Lloyd McKenzie (Jun 07 2021 at 14:38):

JSON or XML?

Justin Miller (Jun 07 2021 at 14:41):

Json

Lloyd McKenzie (Jun 07 2021 at 14:50):

"_issued": {
"extension":[
{
"url":"http://hl7.org/fhir/StructureDefinition/data-absent-reason",
"valueCode":"unknown"
}
]
}

Yunwei Wang (Jun 07 2021 at 14:52):

US Core has a very specific guidance on missing data for required non-coded element: http://hl7.org/fhir/us/core/general-guidance.html#missing-data

For non-coded data elements, use the DataAbsentReason Extension in the data type
Use the code unknown - The value is expected to exist but is not known.

Look @Lloyd McKenzie 's code segment :point_up:

Rey Limosenero (Jun 07 2021 at 15:17):

@Lloyd McKenzie thanks, but we are figuring out how to do that in the code. We are using hapifhir and a code snippet would be really useful. :)

Lloyd McKenzie (Jun 07 2021 at 15:52):

That you might need to ask on #hapi

Rey Limosenero (Jun 08 2021 at 14:14):

Thanks! we figured it out

Last updated: Apr 12 2022 at 19:14 UTC

Main menu

FHIR Chat · Required bindings and data absent reason · implementers