Stream: IG creation
Topic: Specifying SCT US edition
David Pyke (Jan 26 2022 at 20:19):
MY QA report tells me "Snomed: The IG does not specify the US edition of SNOMED CT version in the parameters (http://snomed.info/sct/731000124108)"
We don't have any codesystems or valuesets. Where would I specify it? (I'm using fsh/sushi)
Lloyd McKenzie (Jan 26 2022 at 20:29):
Do you make use of any SNOMED codes in any examples?
David Pyke (Jan 26 2022 at 20:31):
Yep, in an Encounter. I'll update that.
David Pyke (Jan 26 2022 at 20:41):
I'm feeling dumb today. It doesn't like http://snomed.info/sct/731000124108 as a system URI... what do I use?
Lloyd McKenzie (Jan 27 2022 at 00:23):
The system URL must always be "http://snomed.info/sct". You need to include a Parameters instance in your IG that indicates the release of SNOMED to use
David Pyke (Jan 27 2022 at 13:35):
Okay, which Parameter shows that one? I've never done this before
David Pyke (Jan 27 2022 at 16:16):
Can anyone point me to an IG that specifies this so I can copy? I can't find anything in USCore that does it
Jean Duteau (Jan 27 2022 at 16:33):
https://github.com/HL7/fhir-icsr-ae-reporting
David Pyke (Jan 27 2022 at 16:33):
Where do I look?
David Pyke (Jan 27 2022 at 16:34):
Nevermind, found it!
David Pyke (Jan 27 2022 at 16:34):
The exp-params.json file in the root
John Moehrke (Jan 27 2022 at 16:37):
what is an exp-params.json file?
David Pyke (Jan 27 2022 at 16:37):
It's an instance of the Parameters resource in json format
John Moehrke (Jan 27 2022 at 16:38):
in the root?
John Moehrke (Jan 27 2022 at 16:38):
the set of input files to the build is getting out of hand
Elliot Silver (Jan 27 2022 at 16:39):
Can I put any build parameters in here?
David Pyke (Jan 27 2022 at 16:46):
You can put it in the root but need a link to it in the parameters in sushi-config
parameters:
path-expansion-params: '../../exp-params.json'
Elliot Silver (Jan 27 2022 at 16:50):
Elliot Silver said:
Can I put any build parameters in here?
Apparently not -- this is just for the terminology "expansion" parameters.
John Moehrke (Jan 27 2022 at 17:02):
John Moehrke said:
the set of input files to the build is getting out of hand
I state again
David Pyke (Jan 27 2022 at 17:05):
There's probably a way to include this directly in sushi-config or the IG resource directly.
John Moehrke (Jan 27 2022 at 17:06):
that would be a bit more controlled.. yes.
John Moehrke (Jan 27 2022 at 17:10):
and then it could be documented as an IG publisher parameter
David Pyke (Jan 27 2022 at 17:19):
Running it though a build, the fsh-generated IG resource just has the path that is in sushi-config. The final IG resource has it as an extension (using the IG-parameter extension) under the definitions section.
So, no, you can't just put it in the sushi-config but you can put it in the IG resource
{
"extension": [
{
"url": "code",
"valueString": "system-version"
},
{
"url": "value",
"valueString": "http://snomed.info/sct|http://snomed.info/sct/731000124108"
}
],
John Moehrke (Jan 27 2022 at 17:58):
you can put ig extension parameters in your sushi-config
John Moehrke (Jan 27 2022 at 17:58):
in theory.. last time I tried it didn't work.
David Pyke (Jan 27 2022 at 17:59):
No, it didn't work for me, either. So I started a thread in the shorthand stream
John Moehrke (Jan 27 2022 at 19:10):
so... @Lloyd McKenzie @Grahame Grieve ... can we get this capability as an IG publisher parameter rather than this one-off root folder json file?
John Moehrke (Jan 27 2022 at 19:11):
or better, an IG parameter
David Pyke (Jan 27 2022 at 19:11):
Wouldn't it be better if sushi or the other (lesser) tools could just create the extension necessary?
John Moehrke (Jan 27 2022 at 19:12):
sushi can manage IG publisher parameters and IG parameters.. so sushi support would happen automatically if either of those were used.
John Moehrke (Jan 27 2022 at 19:13):
this capability is needed by IGs that are vegan too
David Pyke (Jan 27 2022 at 19:13):
But it's an ig-parameters extension already, so it can be manually added. Are you asking it to be added to the core IG resource?
John Moehrke (Jan 27 2022 at 19:14):
okay, what you are saying is that the solution is in hand if we can just get sushi to work with ig-parameter extensions... which is needed to be fixed anyway. okay.
David Pyke (Jan 27 2022 at 19:14):
yep!
John Moehrke (Jan 27 2022 at 19:15):
just don't like json file solution
David Pyke (Jan 27 2022 at 19:16):
Nope, that's less than optimal but it's a good stopgap until sushi can be modded to handle that parameter (now that it's needed for all SNOMED use in the US)
Grahame Grieve (Jan 27 2022 at 19:23):
can we get this capability as an IG publisher parameter rather than this one-off root folder json file?
no. that would be a retrograde step and I don't understand why you think that would be a good idea.
Lloyd McKenzie (Jan 27 2022 at 20:22):
It's not necessarily just a single parameter. There could, in principle, be a whole lot of terminology configuration information that might be relevant to a particular IG.
David Pyke (Jan 27 2022 at 20:32):
Can these be documented somewhere so that people know how to configure it all (and save people like me from having to start threads like these)
Chris Moesel (Jan 27 2022 at 20:33):
It's not clear to me: Is the Parameters JSON file necessary or is the extension on ImplementationGuide.parameters sufficient? I think someone said the publisher just ends up sticking that data into the IG JSON anyway (as that extension) -- so I'm trying to figure out what is actually necessary.
David Pyke (Jan 27 2022 at 20:34):
The file is just a way to get the template/publisher/fairy godmother to create the extension
David Pyke (Jan 27 2022 at 20:34):
All that is necessary seems to be that if the jurisdiction is US, then the extension is created saying that SNOMED-US is to be used
David Pyke (Jan 27 2022 at 20:35):
And that's only if there's a SNOMED reference somewhere in the IG
David Pyke (Jan 27 2022 at 20:39):
I assume this parameter is needed for any jurisdiction that has a regionalized SNOMED
Chris Moesel (Jan 27 2022 at 20:41):
Well, we can make sure that if someone puts an extension in the parameters in sushi-config.yaml that it gets carried over then. As for whether you should be skipping the Parameters JSON file or not, I'll let the community sort that out. ;-)
Grahame Grieve (Jan 27 2022 at 21:06):
Can these be documented somewhere
the $expand operation documents the parameters
David Pyke (Jan 27 2022 at 21:07):
I meant for IG creation. If we're now to add parameters to the IG (via whatever mechanism), it would be useful for this to be added to the IG creation documentation
Grahame Grieve (Jan 27 2022 at 21:10):
no, I don't follow. This is all documented. What do you think is not documented?
David Pyke (Jan 27 2022 at 21:11):
This all started with my qa report having "Snomed: The IG does not specify the US edition of SNOMED CT version in the parameters (http://snomed.info/sct/731000124108)"
Where is how to resolve that QA issue documented?
David Pyke (Jan 27 2022 at 21:13):
(or the steps to prevent it, either one)
AbdulMalik Shakir (Feb 13 2022 at 06:43):
What is the resolution to this QA issue?
Lloyd McKenzie (Feb 13 2022 at 15:53):
Are you declaring your SNOMED version Parameters instance in your IG (look at US-Core to see how)
David Pyke (Feb 14 2022 at 14:06):
You get an exp-params.json file like the one here: https://github.com/HL7/fhir-icsr-ae-reporting
You can put it in the root but need a link to it in the parameters in sushi-config
parameters:
path-expansion-params: '../../exp-params.json'
Last updated: Apr 12 2022 at 19:14 UTC
