Stream: IG creation
Topic: SNOMED code not recognised
Sarah Gaunt (Aug 23 2018 at 15:30):
I have the SNOMED code: 765107002 |Late-onset neonatal sepsis (disorder)| in my IG.
It exists in SNOMED (international) (it was added in the latest release 7/31:
I have the following in my ig.json file: "sct-edition": "http://snomed.info/sct/900000000000207008",
But I get this error from the IG Publisher:
Is the terminology server pointing to the latest version of SNOMED international?
Rob Hausam (Aug 23 2018 at 17:02):
I'm not sure. There should be a relatively straightforward way to determine this, using a query like:
http://tx.fhir.org/r4/CodeSystem/$lookup?system=http://snomed.info/sct&version=http://snomed.info/sct/900000000000207008&code=138875005
When I tried it without the version string it didn't appear to be giving the International Edition. And trying to add the version string I think I just crashed the tx server. :(
Rob Hausam (Aug 23 2018 at 18:49):
This is an example of how it should work (except that the Terminz server forces me to specify the actual version date rather than just the edition, which I didn't want to do):
http://its.patientsfirst.org.nz/RestService.svc/Terminz/CodeSystem/$lookup?system=http://snomed.info/sct&version=http://snomed.info/sct/21000210109/version/20180801&code=138875005
One of the out parameters that you get back is the designation (synonym) which includes the release info for the SNOMED CT International Edition version:
"SNOMED Clinical Terms version: 20180731 [R] (July 2018 Release)"
Grahame Grieve (Aug 23 2018 at 22:13):
@Rob Hausam what was the query that crashed the server?
Rob Hausam (Aug 24 2018 at 01:28):
I tried some others afterward (to no avail, of course), but I'm pretty sure this was the one:
http://tx.fhir.org/r4/CodeSystem/$lookup?system=http://snomed.info/sct&version=http://snomed.info/sct/900000000000207008&code=138875005
Last updated: Apr 12 2022 at 19:14 UTC
