Stream: IG creation
Topic: New SNOMED CT release on tx.fhir.org?
Kirstine Rosenbeck Gøeg (Aug 17 2021 at 12:58):
I have just updated my implementation guides with SNOMED CT codes from the latest release of SNOMED CT (2021-07-31). However tx.fhir.org does not recognize the codes. I expect that is because the new release is not yet on the terminology server.... It is not critical, so don't rush, but can you say something about when the update is expected?
Grahame Grieve (Aug 17 2021 at 13:00):
which edition?
Rob Hausam (Aug 17 2021 at 13:01):
@Kirstine Rosenbeck Gøeg I'm going to get the International Edition updated soon - I'm hoping to do that today.
Kirstine Rosenbeck Gøeg (Aug 17 2021 at 13:52):
That is great @Rob Hausam - @Grahame Grieve I am using the international edition so far - I am guessing Denmark is too small, for the Danish edition to be supported - it would be great though. Thanks again and best regards :-)
Rob Hausam (Aug 17 2021 at 14:37):
@Kirstine Rosenbeck Gøeg If you can let me know where and how to get the Danish Edition distribution (legally, of course), we should be able to include it.
Rob Hausam (Aug 17 2021 at 21:41):
FYI - the SNOMED CT International Edition has been updated to release 20210731 on tx.fhir.org.
Kirstine Rosenbeck Gøeg (Aug 18 2021 at 11:39):
@Rob Hausam I am asking SNOMED International and my NRC about the specifics. What are you doing with the other editions? using nlm-distribution files or going through SNOMED International MLDS?
Rob Hausam (Aug 18 2021 at 12:43):
@Kirstine Rosenbeck Gøeg That sounds good. So far I've signed up and download the releases from each national service - except Sweden where I've worked with Daniel Karlsson and he has provided the files (which hopefully I will be finally able to process and load soon). I'm happy to work with whatever arrangement works best on your end.
Kirstine Rosenbeck Gøeg (Aug 24 2021 at 11:32):
Hi @Rob Hausam. I still get errors for new concepts in my implementation guide. For example for this concept: https://browser.ihtsdotools.org/?perspective=full&conceptId1=1144798005&edition=MAIN/2021-07-31&release=&languages=en
Which gives the following error:
Unable to find code 1144798005 in http://snomed.info/sct (version http://snomed.info/sct/731000124108/version/20210301); The code "1144798005" is not valid in the system http://snomed.info/sct; The code provided (http://snomed.info/sct#1144798005) is not valid in the value set 'All codes known to the system' (from http://tx.fhir.org/r4) for 'http://snomed.info/sct#1144798005'
(Example from this profile: http://build.fhir.org/ig/hl7dk/KL-dk-tools/branches/main/StructureDefinition-KLToolsCarePainVRS.html)
It seems that tx.fhir.org does not choose the latest release, even though my system is set to a version-less uri: http://snomed.info/sct
BTW: The Danish NRC is processing my request for having the Danish release on tx.fhri.org.
Rob Hausam (Aug 24 2021 at 11:52):
@Kirstine Rosenbeck Gøeg Give it a try again now and see if it is working better for you. I reconfigured the default setting, and now when SNOMED CT is queried without specifying an edition/version, the server should (hopefully) choose the 20210731 International Edition as the default.
Rob Hausam (Aug 24 2021 at 11:54):
And thanks for working on getting approval for us to host the Danish Edition - appreciate it!
Kirstine Rosenbeck Gøeg (Aug 24 2021 at 12:39):
@Rob Hausam It is working now with the 20210731 International Edition. Thanks!
Kirstine Rosenbeck Gøeg (Aug 31 2021 at 07:42):
Hi @Rob Hausam . I have now discussed licensing etc. with the Danish NRC and SNOMED International. The Danish NRC is satisfied with the wording of the international license agreement, and therefore HL7 international may use the Danish extension without further agreements being made. Practically, the HL7 international representative that holds the international license (that would be you Rob?) should log into MLDS (https://mlds.ihtsdotools.org/), and request the Danish extension through the website. The Danish NRC knows that the request is under way, so I expect a swift approval. Will this procedure work for you?
You should note that the Danish SNOMED CT extension have Danish descriptions for most concepts, but that the current politic is to only translate new concepts if they are being used in Denmark.
Rob Hausam (Aug 31 2021 at 11:25):
Thanks, @Kirstine Rosenbeck Gøeg I think this should be able to work, but I have some things to work out with SNOMED International regarding my MLDS account first. Currently my account isn't in a usable state, as my primary license for SNOMED CT personally is directly through the US NLM, and SNOMED International hasn't approved other access for me through MLDS. I've just sent an email to SNOMED International to see if they can give me the needed permissions to make this work for the Danish extension, and I'll let you know when and what I hear back from them on that.
Rob Hausam (Aug 31 2021 at 22:38):
@Kirstine Rosenbeck Gøeg My MLDS account is now fully activated and I've submitted the request for access to the Danish extension content. We will need to combine the extension with the appropriate version of the full International Edition snapshot (based on the module dependencies) to form a "Danish edition" for loading the content on tx.fhir.org. Sometimes there can be a few issues with that (e.g. if the extension alters some of the International edition content?), but hopefully the process of combining the content will go smoothly.
Rob Hausam (Nov 08 2021 at 05:06):
@Kirstine Rosenbeck Gøeg @Jens Villadsen I did get the approval of my MLDS request for the Danish extension a while ago. But there were some issues with the importing, and as you know the previous attempt at loading the Danish extension content on tx.fhir.org unfortunately for some reason missed including most or all of the Danish content. But after working out some further issues with the import code, I've now loaded a new version of the SNOMED CT Danish extension - and this one should have all of the Danish descriptions (at least they seem to be there on my spot check). Please check it out and let me know if you see any further issues. I did end up finding that it was necessary to exclude the der2_ciRefset_QuantityRefsetSnapshot_DK1000005_20210930.txt file from the import, because presently the import code doesn't recognize the concrete domain 'number' value in that Quantity refset. I expect that's not really an issue right now, though, as there is only 1 row in that file (I assume it's mostly experimental at this point?). Eventually we will need to address this, though, as concrete domains become more widely used (beyond only some of the drug extensions).
Jens Villadsen (Nov 08 2021 at 22:12):
well - warnings are gone now ;)
Last updated: Apr 12 2022 at 19:14 UTC
