Stream: terminology
Topic: Getting QA error related to old SNOMED SCT-AU version
Rob Eastwood (Nov 12 2020 at 22:27):
On a profile that fixes a value to a specific SNOMED term, the following error is being raised via IG Publisher:
Unable to find code 1500551000168103 in http://snomed.info/sct (version http://snomed.info/sct/32506021000036107/version/20200831)
The IG correctly declares the Australian edition, but the version reported by the QA error is from an old release, 20200831. The code was added in a release after this date (on a regular monthly releases schedule - see here).
Therefore, the question is - what is the process for the IG Publisher build process to get access to later releases of SNOMED SCT-AU?
Grahame Grieve (Nov 12 2020 at 22:29):
ask, and @Rob Hausam or I have to get around to updating to a later version
Rob Eastwood (Nov 12 2020 at 22:31):
Thanks @Grahame Grieve - just ask here or is there a ticket to be logged somewhere?
Grahame Grieve (Nov 12 2020 at 22:38):
we don't really have a formal process, but we should. @Rob Hausam ?
Rob Hausam (Nov 12 2020 at 22:44):
@Rob Eastwood Yeah, we should have a process. Right now the process is to ask me, and make sure that we have an accessible source. I do have access to the Australian edition, and I've updated it before. So it shouldn't be a problem - and I did have it in mind to do soon, but the squeaky wheel does sometimes tend to get the grease. :)
Rob Eastwood (Nov 12 2020 at 23:49):
Thanks @Grahame Grieve and @Rob Hausam - that's great, if the update could be put on the todo list. It's not urgent mind you, but nice to have a clean QA report.
And with our regular monthly SCT-AU releases (page linked above), we'll need to get into the habit of asking here for an update, so that we can get access to the latest content.
Thanks again :+1:
Rob Hausam (Nov 13 2020 at 01:26):
Every 6 months updates of the major SNOMED editions are probably pretty manageable. But as you're noting, that's not necessarily going to be sufficient, especially if we need to keep up with drug extensions, which really do need to be updated monthly. But if we're going to even think about being able to provide anything like that level of support we're going to need resources for it. So we're going to have to give some significant thought to what we want to do and how to do it.
Rob Eastwood (Nov 13 2020 at 03:53):
Thanks @Rob Hausam that makes sense.
Rob Eastwood (Jun 29 2021 at 02:26):
Hello @Rob Hausam - I am working with HL7 Australia on cleaning up QA errors on their Australian Base IG, and there are a couple related to validating newly added SNOMED codes against an old version of SNOMED (as per the original post above). The errror is:
Unable to find code 1515311000168102 in http://snomed.info/sct (version http://snomed.info/sct/32506021000036107/version/20200831); The code "1515311000168102" is not valid in the system http://snomed.info/sct; The code provided (http://snomed.info/sct#1515311000168102) is not valid in the value set 'All codes known to the system' (from http://tx.fhir.org/r4) for 'http://snomed.info/sct#1515311000168102'
This particular code was added to SNOMED in Dec 2020 but the publisher is still validating with a Aug 2020 version.
May I ask you to assist in getting the SNOMED version updated. And if further information is needed, or if I should be bothering someone else, please let me know.
thank you
Rob Hausam (Jun 29 2021 at 02:46):
@Rob Eastwood You're right that the version of the Australian edition on tx.fhir.org is still 20200831, so it does need to be updated to the latest one. I've put it in the queue and I'll try to get that done over the next couple of days by the end of the month, if possible.
Rob Eastwood (Jun 29 2021 at 21:58):
Fantastic, thank you @Rob Hausam
Rob Hausam (Jul 06 2021 at 07:45):
@Rob Eastwood The SNOMED CT Australian Edition has been updated to the 20210630 version. It should be good, but please check it out and verify that it's working ok.
Rob Eastwood (Jul 06 2021 at 23:47):
Rob Hausam said:
Rob Eastwood The SNOMED CT Australian Edition has been updated to the 20210630 version. It should be good, but please check it out and verify that it's working ok.
Thank you very much @Rob Hausam - that is wonderful; and I can confirm that the above mentioned errors are now eliminated.
Last updated: Apr 12 2022 at 19:14 UTC
