FHIR Chat · dataAbsentReason extensions · implementers

Stream: implementers

Topic: dataAbsentReason extensions


view this post on Zulip Brian Reinhold (Mar 08 2017 at 19:26):

I would like to use the dataAbsentReason extension to add NINF (negative infinity) and PINF (positive infinity) in addition to the already existing NaN. However, I do not see how I can use the extension defined at http://hl7.org/fhir/2017Jan/extension-data-absent-reason.html to indicate what these new codes mean. Usually I would have to register the URL that would explain the new codes in the extension.

Anyone know how I would add those cases and what it would look like on the wire?

view this post on Zulip Lloyd McKenzie (Mar 08 2017 at 20:07):

I thought these were excluded from the original list because they were handled within the data type. @Grahame Grieve ?

view this post on Zulip Richard Townley-O'Neill (Mar 09 2017 at 00:43):

Is this relevant?
http://hl7.org/fhir/2017Jan/extension-iso21090-nullflavor.html

view this post on Zulip Grahame Grieve (Mar 09 2017 at 03:41):

what do you want to use NINF and PINF for?

view this post on Zulip Eric Haas (Mar 09 2017 at 21:14):

We discussed this topic in the past and PINF is > detection range and NINF is < detection range as a valueQuantity. which is why they are not in the Observation Value Absent Reason. The valueset is extensible by the way so you can add local concept no covered by the existing codes.

view this post on Zulip Eric Haas (Mar 09 2017 at 21:15):

Assuming you wanted to use Observation.


Last updated: Apr 12 2022 at 19:14 UTC