Stream: IG creation
Topic: US ed Snomed for US Core
Eric Haas (Dec 01 2020 at 05:37):
we have this error:
ERROR: CareTeam/example: CareTeam.participant[1].role[0].coding[0]: Unable to find code 453231000124104 in http://snomed.info/sct (version http://snomed.info/sct/900000000000207008/version/20200731); The code "453231000124104" is not valid in the system http://snomed.info/sct; The code provided (http://snomed.info/sct#453231000124104) is not valid in the value set 'All codes known to the system' (from http://tx.fhir.org/r4) for 'http://snomed.info/sct#453231000124104'
This is a US ed Snomed code and we would like to know how to make the ig-pub validator aware of this?
Grahame Grieve (Dec 01 2020 at 05:54):
I don't think US core is US Snomed. I've been meaning to ask about this
Eric Haas (Dec 01 2020 at 06:16):
We would like it reference US ed of SNOMED. smoking status codes for instance
Gay Dolin (Dec 01 2020 at 16:51):
The Smoking status issue is just the display name issue. Someone made a comment that they wanted the (funky) US names for this set. The codes are the same. The Care Team one is a great example of why US Realm IGs should be able to access the US edition
Eric Haas (Dec 01 2020 at 17:03):
smoking status codes have three us edition codes:
Code Display
449868002 Current every day smoker
428041000124106 Current some day smoker
8517006 Former smoker
266919005 Never smoker
77176002 Smoker, current status unknown
266927001 Unknown if ever smoked
428071000124103 Current Heavy tobacco smoker
428061000124105 Current Light tobacco smoker
Eric Haas (Dec 01 2020 at 17:04):
don't resolve when clicked on version 3.1.1 now we are moving that to vsac and getting a host of new issues but the point remains is based on us ed
Gay Dolin (Dec 01 2020 at 17:10):
Ahh, right, I stand corrected. ALSO different (preferred) display names for the one that are in both.
Grahame Grieve (Dec 02 2020 at 03:53):
ok @Eric Haas I just pushed the change to make US Core depend on US version of snomed. You might need to rework it so it doesn't overwritten by sushi or whatever it is you d o
Eric Haas (Dec 02 2020 at 19:29):
@Lloyd McKenzie the addition of a Parameters resource for the purpose of defining expansion behavior is something I would prefer not being exposed to the reader, because it is strictly infrastructure for publishing. Is there a way to hide them from the artifacts table?
( On a separate ediorial note, I find the utility of the table when there are more than a small ( <20 ) items suspect. IMO this table is unusable for US Core since is too long and and too much visual noise. )
Grahame Grieve (Dec 02 2020 at 19:30):
why would they appear in the artifacts table?
Eric Haas (Dec 02 2020 at 19:33):
The script sucks up all the resources in the resources folder
Grahame Grieve (Dec 02 2020 at 19:34):
which script?
Grahame Grieve (Dec 02 2020 at 19:35):
but why would it include resources that are not in the IG?
Eric Haas (Dec 02 2020 at 19:36):
I think there is a stylesheet that produces this artifact. @Lloyd McKenzie ?
Eric Haas (Dec 02 2020 at 19:37):
thanks for adding this parameter
Grahame Grieve (Dec 02 2020 at 19:44):
it doesn't have to be in the directory I put it in, if some script is reading the filesystem not the actual list of registered resources
Eric Haas (Dec 02 2020 at 19:48):
ok so it does not need to be in either :
path-resource:
- input/resources
- fsh-generated/resources
which are defined in the ig resource?
Grahame Grieve (Dec 02 2020 at 19:58):
no. it can be anywhere you want it that you can describe from the IG resource.
Eric Haas (Dec 02 2020 at 20:16):
OK I am trying to reference another 'private' directory but the relative reference does not work :-(
....
path-expansion-params: '../input/_resources/exp-params.json' # for using US ed of SNOMED
active-tables: 'false'
...
getting this error...
Publishing Content Failed: /Users/ehaas/Documents/FHIR/US-Core-R4/fsh-generated/input/_resources/exp-params.json (No such file or directory) (00:32.0434)
Grahame Grieve (Dec 02 2020 at 20:20):
well, is that the right path?
Eric Haas (Dec 02 2020 at 20:22):
oops..... nm
Last updated: Apr 12 2022 at 19:14 UTC
