Stream: IG creation
Topic: ignorewarnings
Jose Costa Teixeira (Nov 15 2019 at 13:37):
I have a warning and want to ignore it but can't get ignoreWarnings.txt syntax right.
The value provided ('de-BE') is not in the value set http://hl7.org/fhir/ValueSet/languages (http://hl7.org/fhir/ValueSet/languages, and a code is recommended to come from this value set) (error message = The code provided (urn:ietf:bcp:47#de-BE) is not valid in the value set CommonLanguages)
Which part of this should go in the ignoreWarnings.txt?
Just the error message?
Lloyd McKenzie (Nov 15 2019 at 13:43):
The whole thing
Lloyd McKenzie (Nov 15 2019 at 13:44):
Look at what's spit out in qa.txt
Jose Costa Teixeira (Nov 15 2019 at 14:30):
I did copy the qa.txt line to ignoreWarnings.txt
Jose Costa Teixeira (Nov 15 2019 at 14:30):
so now my qa.html shows this at the end:
Suppressed Error Messages
ERROR: ImplementationGuide/hl7.be.core: ImplementationGuide.definition.parameter[10].code: The value provided ('path-qa') is not in the value set http://hl7.org/fhir/ValueSet/guide-parameter-code|4.0.1 (http://hl7.org/fhir/ValueSet/guide-parameter-code, and a code is required from this value set) (error message = Unknown Code http://hl7.org/fhir/guide-parameter-code#path-qa in http://hl7.org/fhir/guide-parameter-code)
Jose Costa Teixeira (Nov 15 2019 at 14:31):
however, it also shows this :
pasted image
Jose Costa Teixeira (Nov 15 2019 at 14:31):
shouldn't this one be suppressed?
Lloyd McKenzie (Nov 15 2019 at 14:38):
You can't suppress errors unless they're hyperlink problems.
Lloyd McKenzie (Nov 15 2019 at 14:38):
You can only suppress warning and info messages
Jose Costa Teixeira (Nov 15 2019 at 14:47):
ok i got rid of the yellows.
Jose Costa Teixeira (Nov 15 2019 at 14:51):
but this means that the pink errors like I show cannot be ignored , ever, right?
Jose Costa Teixeira (Nov 15 2019 at 14:51):
that one is a tooling issue, I think ,so I have to live with it. correct?
Lloyd McKenzie (Nov 15 2019 at 14:57):
Correct - it provides incentive to fix the tools :)
Grahame Grieve (Nov 15 2019 at 19:11):
why is that one a tooling issue?
Jose Costa Teixeira (Nov 15 2019 at 19:33):
Seems that the template is injecting these parameters. @Lloyd McKenzie is that the case?
Grahame Grieve (Nov 15 2019 at 20:38):
oh. I looked again at the code system. That is unsorted business for us. I need to figure out what to do about those codes
Kevin Mayfield (Dec 10 2019 at 16:46):
We're getting similar errors regarding SNOMED ecl. I take it we can't disable these errors
CareConnect-AllergyCertainty-1 error Error from server: The filter "constraint = (385434005 |Improbable diagnosis| OR 2931005 |Probable diagnosis| OR 255545003 |Definite| OR 410605003 |Confirmed present|)" was not understood in the context of http://snomed.info/sct
Grahame Grieve (Dec 10 2019 at 19:56):
you can add the error message to suppressederrors.txt
Kevin Mayfield (Dec 10 2019 at 21:17):
I'm getting what Lloyd mentions above. I can suppress warnings and info but not errors. I could with removing the ECL ones.
Kevin Mayfield (Dec 10 2019 at 21:19):
So FATAL and ERROR can't be suppressed - filterMessages in ValidationPresenter
(message.getLevel().equals(ValidationMessage.IssueSeverity.FATAL) || message.getLevel().equals(ValidationMessage.IssueSeverity.ERROR)))
Grahame Grieve (Dec 10 2019 at 21:33):
I guess you can't then
Kevin Mayfield (Dec 10 2019 at 21:49):
Ah well, like looking through code - helps me learn.
Lloyd McKenzie (Dec 10 2019 at 22:48):
Fatal and error issues are supposed to only be raised for "guaranteed errors", so suppressing them doesn't make sense.
Kevin Mayfield (Dec 11 2019 at 22:42):
Most of our errors were around SNOMED ECL, adding an expansion to the ValueSet stopped the errors from occurring
Rob Hausam (Dec 11 2019 at 23:59):
@Kevin Mayfield Do you mean pre-expanding the value set and including that expansion element and contents in the ValueSet resource instance in your IG?
Grahame Grieve (Dec 12 2019 at 00:06):
yes. it's a bad workaround but it works. I'll get to ECL soon
Sarah Gaunt (Jan 16 2020 at 06:12):
So using the new template I'm getting the errors that @Jose Costa Teixeira mentioned above:
The value provided ('path-output') is not in the value set http://hl7.org/fhir/ValueSet/guide-parameter-code|4.0.1 (http://hl7.org/fhir/ValueSet/guide-parameter-code, and a code is required from this value set) (error message = Unknown Code http://hl7.org/fhir/guide-parameter-code#path-output in http://hl7.org/fhir/guide-parameter-code)
I presume there is nothing I can do about these errors? Are they going to be sorted? Will these errors be waived by FMG if they are still there when we go to get approval (i.e. next week)?
Grahame Grieve (Jan 16 2020 at 06:14):
I don't know when they'll be sorted but they'll definitely be waived
Sarah Gaunt (Jan 16 2020 at 06:17):
Sweet - thanks!
Rick Geimer (Jan 20 2020 at 21:54):
Just a reminder that these errors are still showing up. Assuming they will still be waived until fixed.
Lloyd McKenzie (Jan 20 2020 at 22:08):
I've got a local-fix that addresses this. I've got one question outstanding w/ Grahame after which I'll commit and create a pull request
Last updated: Apr 12 2022 at 19:14 UTC
