Stream: pascal
Topic: tx.fhir.org hosting multiple SNOMED CT editions
Rob Hausam (Mar 12 2020 at 06:46):
Moving the discussion from terminology to here. @Grahame Grieve Probably I misinterpreted your post in the COVID-19 topic:
just list them in the ini file in order - first is default for the edition when referenced with out a version e.g.
nameX=type: snomed; source: [cache file 1]; default: true nameY=type: snomed; source: [cache file 2]
'nameX' and 'nameY are obviously different, but I thought they would need to be the same in order to indicate that the rows belong to the same edition. When I did it that way, though, the server didn't like it (wouldn't start):
sintl= type: snomed; source: d:\data\snomed_20200309_intl.cache; default: true sintl= type: snomed; source: d:\data\snomed_20200131_intl.cache sintl= type: snomed; source: d:\data\snomed_20190731_intl.cache
So how should it be?
Grahame Grieve (Mar 12 2020 at 08:00):
the name there only has meaning locally to differentiate the lines, so they must be different
Rob Hausam (Mar 12 2020 at 13:08):
ok, that makes sense
so the indication that it is a version of the "International Edition" is encoded within the cache file itself, then?
it makes sense that it could be since that information is specified when the cache is generated (but otherwise that wasn't obvious)
Grahame Grieve (Mar 12 2020 at 20:50):
encoded within the cache file itself
yes
Rob Hausam (Mar 13 2020 at 02:37):
The SNOMED CT International Edition 20200309, 20200131 and 20190731 versions are being simultaneously hosted on tx.fhir.org now. It appears to be working correctly and has resolved the issue that I had with the expansion content and version declaration for the SNOMED GPS value sets in IPS! We could add more versions if we need to, but this is all that I need or know that are needed right now so that's what I've done to this point.
Last updated: Apr 12 2022 at 19:14 UTC
