Stream: IG creation
Topic: US edition SNOMED code not found error
Monique van Berkum (Jun 28 2021 at 21:52):
The SDOH CC Task profile Task.output.value element is constrained to CodeableConcept with out any further constraints. The task example in the IG uses a SNOMED CT US March 2021 procedure code:
"valueCodeableConcept" : {
"coding" : [
{
"system" : "http://snomed.info/sct",
"code" : "464031000124101",
"display" : "Referral to food pantry program"
}
The validator is generating the following error:
Unable to find code 464031000124101 in http://snomed.info/sct (version http://snomed.info/sct/900000000000207008/version/20210131); The code "464031000124101" is not valid in the system http://snomed.info/sct; The code provided (http://snomed.info/sct#464031000124101) is not valid in the value set 'All codes known to the system' (from http://tx.fhir.org/r4) for 'http://snomed.info/sct#464031000124101'
Our IG specifies the US edition of SNOMED CT.
The Ci Build QA page link is http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/branches/master/qa.html
After review with @Lloyd McKenzie, he suggested to post it here. How do we resolve this error?
Eric Haas (Jun 29 2021 at 01:35):
@Monique van Berkum which version of snomed us edition is this? @Rob Hausam which edition is in the term server?
Eric Haas (Jun 29 2021 at 01:40):
looks like a new concept to me:
Rob Hausam (Jun 29 2021 at 03:01):
@Eric Haas @Monique van Berkum The version of the SNOMED CT US Edition currently on tx.fhir.org server is 20210301, the latest one, and a $lookup on the server is successful.
Eric Haas (Jun 29 2021 at 04:13):
thanks for the update
Lloyd McKenzie (Jun 29 2021 at 04:36):
@Rob Hausam If the code is on the tx server, any thoughts on why the validator is saying it's not? @Mark Iantorno ?
Grahame Grieve (Jun 29 2021 at 10:46):
have you tried clearing the txCache?
Rob Hausam (Jun 29 2021 at 12:39):
Yes, that was also my thought. @Eric Haas @Monique van Berkum @Lloyd McKenzie
Monique van Berkum (Jun 30 2021 at 15:08):
That did it. Thank you. @Eric Haas @Grahame Grieve @Rob Hausam
AbdulMalik Shakir (Aug 09 2021 at 18:31):
I'm getting the following notification "Snomed: The IG does not specify the US edition of SNOMED CT version in the parameters (http://snomed.info/sct/731000124108)" in my CI Build. I updated the parameter list in the IG to read as follows:
"parameter": [
{
"code": {"value": "releaselabel"},
"value": {"value": "STU 2 Ballot"}
},
{
"code": {"value": "copyrightyear"},
"value": {"value": "2021+"}
},
{
"code": {"value": "system-version"},
"value": {"value": "http://snomed.info/sct|http://snomed.info/sct/731000124108"}
}
]
Is this incorrect? Should this remove the notification?
Lloyd McKenzie (Aug 09 2021 at 21:05):
That's incorrect. The IG needs a parameter that points to the location of an external Parameters resource that specifies the version (and possibly other information) that will be used as part of value set expansion. You can see an example of an IG that does this here: https://github.com/HL7/davinci-crd/tree/master/input
AbdulMalik Shakir (Aug 09 2021 at 22:03):
Thanks @Lloyd McKenzie So I see this:
<parameter>
<code value="path-expansion-params"/>
<value value="terminology-settings.json"/>
</parameter>
When you say "points to the location of an external Parameters resource" is that what terminology-settings.json is? How is the location of this "external" resource resolved? Can multiple IGs point to the same external resource? Can, for example, my IG point to the same external resource defined here, "terminology-settings.json"?
Lloyd McKenzie (Aug 09 2021 at 22:14):
@AbdulMalik Shakir If you look in my input folder, you'll see that terminology-settings.json is a file sitting in that folder. At the moment, the file needs to be in your local repository - we don't have a mechanism to look for files located elsewhere. However, you can just copy the file from CRD if you like.
AbdulMalik Shakir (Aug 09 2021 at 22:57):
@Lloyd McKenzie That worked.
Snomed: The IG specifies the US edition of SNOMED CT ✓
Thanks.
Last updated: Apr 12 2022 at 19:14 UTC