Stream: IG creation
Topic: National SNOMED CT codes and ig publisher
Richard Townley-O'Neill (Aug 28 2018 at 05:02):
When I run the ig publisher it is raising errors for SNOMED CT-AU (Australian extension) codes. Is this a limitation of the publisher?
Example from a qa.html file
| Path | Severity | Message |
|---|---|---|
| Immunization/immunization-example0: Immunization.vaccineCode.coding | error | unable to find code 830851000168105 in http://snomed.info/sct |
Richard Townley-O'Neill (Aug 28 2018 at 06:09):
@Grahame Grieve ?
Grahame Grieve (Aug 28 2018 at 06:18):
have you specified Australian Snomed in the IG set up?
Richard Townley-O'Neill (Aug 28 2018 at 06:30):
Where can I find how to do that?
Richard Townley-O'Neill (Aug 28 2018 at 06:41):
Found it.
ig.json file, first line.
I have specified Australian snomed.
Richard Townley-O'Neill (Aug 28 2018 at 06:51):
Problem is still there.
Robert McClure (Aug 29 2018 at 01:41):
@Richard Townley-O'Neill I hope I'm not understanding the issue, but let me clarify that per SNOMED Int requirements to HTA, only SCT international, and not realm-specific, concepts can be in international (universal) IGs. So either you are creating a realm-specific IG, and therefor the IG must be published by the realm, or you need to change the codes to those found in the international core.
Richard Townley-O'Neill (Aug 29 2018 at 01:42):
I'm creating a realm-specific IG.
Brett Esler (Aug 31 2018 at 01:04):
This is same problem as reported in the AU Base IG - many QA errors that were validated as ok in previous IG builder versions
Brett Esler (Sep 07 2018 at 06:35):
@Grahame Grieve Was there any light on this one?
Brett Esler (Sep 07 2018 at 06:35):
"sct-edition": "http://snomed.info/sct/32506021000036107", is defined
Brett Esler (Apr 01 2019 at 23:29):
coming back around to this one - getting SNOMED terms not found in qa http://build.fhir.org/ig/hl7au/au-fhir-base/qa.html#_scratch_ig-build-temp-HO1HKK_repo_examples_healthcareservice-example3
e.g. https://ontoserver.csiro.au/shrimp/?concept=1244901000168103&system=http://snomed.info/sct&versionId=http://snomed.info/sct/32506021000036107/version/20190331
not sure why @Grahame Grieve can you advise?
Jim Steel (Apr 02 2019 at 09:08):
Could just be outdated version? That concept was only introduced in January 2019
Grahame Grieve (Apr 02 2019 at 19:04):
then yes, I have not updated snomed on tx.fhir.org - on my todo list
Last updated: Apr 12 2022 at 19:14 UTC
