FHIR Chat · Missing ICU Status LOINC Code · terminology

Stream: terminology

Topic: Missing ICU Status LOINC Code


view this post on Zulip David Pyke (Jan 18 2021 at 15:17):

I"m getting the following error on IG build:

The code "95420-6" is not valid in the system http://loinc.org; The code provided (http://loinc.org#95420-6) is not valid in the value set 'All codes known to the system' (from http://tx.fhir.org/r4) for 'http://loinc.org#95420-6'

However, https://loinc.org/95420-6/ exists. So, how do I/we/you/they get this added?

view this post on Zulip David Pyke (Jan 18 2021 at 15:21):

I also get a lot of warnings about other missing codes, but this is the only error. The rest are COVID tests and I'm assuming they haven't been added yet.

view this post on Zulip Robert McClure (Jan 18 2021 at 16:28):

@David Pyke Can you confirm that another code that was introduced with the current 2.69 release is not causing an error? Likely another COVID-19 code?

view this post on Zulip David Pyke (Jan 18 2021 at 16:29):

Can you link me to the codes that were added with 2.69?

view this post on Zulip Robert McClure (Jan 18 2021 at 16:32):

Many of these here such as 95418-0

view this post on Zulip David Pyke (Jan 18 2021 at 16:35):

Yes, I have almost all of those in my ValueSets, I get a bunch of warnings but this is the only error

view this post on Zulip David Pyke (Jan 18 2021 at 16:37):

qa.txt Has all the details

view this post on Zulip Robert McClure (Jan 18 2021 at 18:58):

@Grahame Grieve @Rob Hausam

view this post on Zulip Grahame Grieve (Jan 19 2021 at 11:26):

I don't know. When was it added?

view this post on Zulip Rob Hausam (Jan 19 2021 at 13:40):

@David Pyke We haven't updated the server to LOINC 2.69 yet. I'll do that this morning.

view this post on Zulip Rob Hausam (Jan 19 2021 at 17:31):

Unfortunately, there's a problem with the import for LOINC 2.69. I'm investigating.

view this post on Zulip David Pyke (Jan 25 2021 at 12:53):

Has the problem been fixed?

view this post on Zulip David Pyke (Jan 28 2021 at 16:11):

I still seem to be getting these errors, is there a step I'm missing?

view this post on Zulip Rob Hausam (Jan 29 2021 at 06:11):

No, it hasn't been fixed yet - but it should be soon. I've had to do some other work to be able to find and fix the error in the import, which I'm now about to attempt to do.

view this post on Zulip David Pyke (Mar 18 2021 at 15:28):

I'm still seeing this error, as well

view this post on Zulip Rob Hausam (Mar 18 2021 at 15:31):

The same answer here, of course - still need to resolve the LOINC 2.69 import bug.

view this post on Zulip Rob Hausam (Mar 18 2021 at 15:32):

I'll try it again today - maybe it will magically work this time. :)

view this post on Zulip David Pyke (Mar 22 2021 at 13:40):

And did it? This is worrisome that we don't have the COVID codes loaded with so many projects using them

view this post on Zulip Rob Hausam (Mar 22 2021 at 22:06):

Well, I didn't quite get to it "today" (Thurs. 18th). Let me see if I can try it now - during the Vocab call. :)

view this post on Zulip Rob Hausam (Mar 22 2021 at 22:27):

@David Pyke The issue is still there (no surprise). It's choking on an issue with "order/obs" and the value 'Y' (which I believe likely hasn't been in the data previously - and I assume is intentional?). This is still going to require a (likely fairly small?) code change in the importer to resolve (hopefully we will be able to get that done soon - I agree it's certainly a priority).

view this post on Zulip Rob Reynolds (Apr 05 2021 at 12:25):

@Rob Hausam Did this get fixed? I'm getting the same error for a different LOINC Code that is also included in 2.69 (https://loinc.org/96315-7/):

The code "96315-7" is not valid in the system http://loinc.org

image.png

view this post on Zulip Rob Hausam (Apr 05 2021 at 13:39):

@Rob Reynolds Unfortunately, this hasn't been fixed yet. @Max Masnick has also been asking about it (here). I thought I might be able to work around the problem by massaging the LOINC source data, but when I looked at that there seems to be nothing in the data that would be causing this error that can be adjusted. So it's looking like the code does really need to be fixed, and I need to get back to fixing the one blocker in my environment for compiling the Pascal source so that I can do that. I'll see if I can take another look at that today and hopefully can make some progress on it.

view this post on Zulip Rob Reynolds (Apr 05 2021 at 16:21):

@Rob Hausam Thank you for the update! Good luck with fixing your environment. I hate those kinds of issues.

view this post on Zulip Rob Reynolds (Apr 07 2021 at 11:19):

@Rob Hausam To quote @Yan Heras (from the UTG thread https://jira.hl7.org/browse/UP-175?focusedCommentId=185035&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-185035)

[W]e are planning to start the publication process for the Data Exchange for Quality Measure IG (http://build.fhir.org/ig/HL7/davinci-deqm/) very soon. Our only remaining QA errors are generated by needing this new ActCode and also a new valid LOINC code for gaps in care report that we requested for this IG is not recognized by the IG publisher. So this is an immediate blocker for us.

Given that, thoughts on the likelihood of it being fixed soon? I know this has been an issue for months and it's being tracked by a number of other folks who are also experiencing issues with it, so... just trying to plan as best as we can for the above.

view this post on Zulip Rob Reynolds (May 04 2021 at 12:09):

@Rob Hausam It's fixed!!! Woot!!!

view this post on Zulip Rob Hausam (May 04 2021 at 12:31):

Yes, I was able finally to get that done!


Last updated: Apr 12 2022 at 19:14 UTC