FHIR Chat · Valid datatype for LOINC answers · terminology

Stream: terminology

Topic: Valid datatype for LOINC answers


view this post on Zulip Monique van Berkum (Jun 08 2021 at 19:12):

Answers in LOINC are not necessarily code. Integer, string, and decimal should be allowed datatypes based on the datatype specified in LOINC. image.png image.png

view this post on Zulip David Pyke (Jun 08 2021 at 19:23):

You'd get better information if you asked this question in #IG creation

view this post on Zulip Rob Hausam (Jun 08 2021 at 19:29):

Might also need to try on #implementers or check with FHIR-I if it's a core Q/QR resource issue.

view this post on Zulip Monique van Berkum (Jun 08 2021 at 19:39):

Yes thank you. Will ask on IG Creation stream

view this post on Zulip Brian Postlethwaite (Jun 09 2021 at 23:54):

Or the #questionnaire stream :smile:

view this post on Zulip Brian Postlethwaite (Jun 09 2021 at 23:56):

And I suspect that the question item type was defined as choice which is what would be causing that issue.
If you want an integer, then that should be the item type.

view this post on Zulip Monique van Berkum (Jun 15 2021 at 19:27):

Thank you for the last suggestion. However, the item types were defined as integer, string and decimal.

view this post on Zulip Lloyd McKenzie (Jun 24 2021 at 20:41):

Pretty clear that this is a validator issue. It's presuming that answers are always going to be codes, which isn't necessarily the case.

view this post on Zulip Grahame Grieve (Jun 24 2021 at 20:45):

well, how do I reproduce this?

view this post on Zulip Lloyd McKenzie (Jun 24 2021 at 20:46):

It's manifesting in the SDOH IG. http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/


Last updated: Apr 12 2022 at 19:14 UTC