Stream: IG creation
Topic: Help: Spurious SNOMED Terminology Errors from IG Pub v1.1.94
Saul Kravitz (Jan 10 2022 at 16:57):
I'm getting two new and spurious errors on SNOMED terms in IG Publisher 1.1.93.
No changes have been made to the IG for almost one month, and it previously had a clean build (with v1.1.84)
here is the QA report -- http://build.fhir.org/ig/HL7/fhir-mCODE-ig/qa.html
The terms in question are:
entire - https://browser.ihtsdotools.org/?perspective=full&conceptId1=255503000&edition=MAIN/2021-07-31&release=&languages=en
lower - https://browser.ihtsdotools.org/?perspective=full&conceptId1=261122009&edition=MAIN/2021-07-31&release=&languages=en
These are not new terms.
The Valueset that is squawked about includes them in its expansion
The error is simply not correct. Thoughts on how to work around?
None of the codings provided are in the value set 'Radiotherapy Treatment Location Qualifier Value Set' (http://hl7.org/fhir/us/mcode/ValueSet/mcode-radiotherapy-treatment-location-qualifier-vs), and a coding from this value set is required) (codes = http://snomed.info/sct#255503000)
None of the codings provided are in the value set 'Radiotherapy Treatment Location Qualifier Value Set' (http://hl7.org/fhir/us/mcode/ValueSet/mcode-radiotherapy-treatment-location-qualifier-vs), and a coding from this value set is required) (codes = http://snomed.info/sct#261122009)
@Grahame Grieve @Rob Hausam
Saul Kravitz (Jan 12 2022 at 18:10):
Any idea how these spurious errors were introduced or can be banished? @Grahame Grieve @Rob Hausam
Saul Kravitz (Jan 12 2022 at 20:51):
When I build locally on my laptop, there are no errors.
Saul Kravitz (Jan 12 2022 at 22:52):
Same problem on 1.1.93 and 1.1.94 in the CI build.
Grahame Grieve (Jan 13 2022 at 06:03):
ok I think I solved it. Wow that was hard. And a subtle and difficult problem with potentially real consequences, so I'm glad you characterised it and I chose not to ignore it. I will work to get a fixed IG publisher out as soon as possible
Grahame Grieve (Jan 13 2022 at 06:25):
you'll also need to blow away the tx-cache once the new IG publisher is released
Saul Kravitz (Jan 13 2022 at 15:26):
Hi @Grahame Grieve , thanks for resolving...
Since the IG output appears correct, can we proceed to publication with these two errors?
Grahame Grieve (Jan 13 2022 at 19:26):
sure. there'll be a new release before we actually do the publication
Last updated: Apr 12 2022 at 19:14 UTC
