FHIR Chat · SNOMED findings in Observation.code · terminology

Stream: terminology

Topic: SNOMED findings in Observation.code


view this post on Zulip Simone Heckmann (Sep 30 2021 at 20:31):

We are currently considering to create a profile with
Observation.code = SNOMED: 116149007 (Disability percentage (finding))
Observation.valueQuantity = 10-100 {percent}

However, the Guidance on Observation.code says:

If a SNOMED CT concept code is used, the expression SHOULD represent a 363787002 (Observable entity(Observable entity)) or 386053000 (Evaluation procedure(evaluation procedure))

Can using the code 116149007 be recommended here? Or should we look for alternatives?

view this post on Zulip Grahame Grieve (Sep 30 2021 at 22:56):

presumably the grounds for this on the snomed side is that disability percentage is an estimate taken from multiple observables? Where as we would use Observation for that?

The problem for us is that most Findings belong in Condition, but not this one.

Anyway, the answer to the question is, use the right code - this one, and use Observation. And the SHOULD rule will need to get clarified somehow

view this post on Zulip Robert McClure (Oct 01 2021 at 01:32):

I'd agree that LOINC does not have this and it is fine to use the SNOMED CT code. The SHOULD is correct, it's not a SHALL. @Simone Heckmann You right to raise the question and you've got an answer.

view this post on Zulip Lin Zhang (Oct 06 2021 at 16:09):

Need to submit a proposal for a new loinc code to the LOINC Committee.

view this post on Zulip Rob Hausam (Oct 06 2021 at 23:20):

@Lin Zhang I assume you may want to discuss the request here? And then you would need to make the request to the HTA, and they will communicate with LOINC and pass the request on to them. That's how it should work.

view this post on Zulip Lin Zhang (Oct 07 2021 at 01:30):

@Rob Hausam Thanks, Rob. Just my comment.

IMO, SCT Findings are not good choices for the Obs.code element.

view this post on Zulip Rob Hausam (Oct 07 2021 at 02:13):

Sorry, @Lin Zhang. I didn't go back to the top of the thread and refresh my recollection of the context.


Last updated: Apr 12 2022 at 19:14 UTC