FHIR Chat · Warnings suppression file format issue · IG creation

Stream: IG creation

Topic: Warnings suppression file format issue


view this post on Zulip David deRoode (Jul 28 2020 at 17:58):

The message suppression file for Dental Referral IG (https://build.fhir.org/ig/HL7/dental-data-exchange) is not being recognized. It follows the this format: https://confluence.hl7.org/display/FHIR/Implementation+Guide+Parameters

view this post on Zulip Eric Haas (Jul 28 2020 at 18:29):

yes that is a silly annoying error:

you need a file input/ignoreWarnings.txt

and the file need to contain the header

== Suppressed Messages ==

view this post on Zulip John Moehrke (Jul 28 2020 at 18:47):

which did confuse me. I figured it wanted wiki markdown... but nope.

view this post on Zulip David deRoode (Jul 28 2020 at 21:42):

@Eric Haas The Dental repo seems to meet both of those requirements: https://github.com/HL7/dental-data-exchange/tree/master

view this post on Zulip Grahame Grieve (Jul 28 2020 at 21:57):

have you got a UTF BOM in the file?

view this post on Zulip David deRoode (Jul 28 2020 at 22:03):

It doesn't appear so, here are the first few lines in the file...

== Suppressed Messages ==

# {{the dental data exchange IG is using codes that are not in the UTG fragment}}
{{Unknown Code http://www.ada.org/snodent#148393D in http://www.ada.org/snodent - note that the code system is labelled as a fragment, so the code may be valid in some other fragment for "http://www.ada.org/snodent#148393D"}}
{{Unknown Code http://www.ada.org/snodent#148393D in http://www.ada.org/snodent - note that the code system is labelled as a fragment, so the code may be valid in some other fragment}}

view this post on Zulip Grahame Grieve (Jul 28 2020 at 22:04):

you have to open the file with a hex editor to see the BOM

view this post on Zulip David deRoode (Jul 28 2020 at 22:34):

I see, I needed to remove the {{}} around Reasons and Messages in the file. All set on this front

view this post on Zulip Eric Haas (Jul 31 2020 at 18:02):

I am making the documentation clearer since I thought the {{}} was liquid syntax and kept in too. though does not work for me either.

view this post on Zulip Eric Haas (Aug 07 2020 at 02:30):

I ma not successful suppressing warnings :

I have a pair of warnings:"The Measure "http://example.org/fhir/Measure/measure-medicare-stratification-example" could not be resolved, so no validation can be performed against the Measure"

so I have

== Suppressed Messages ==

# successful PR to https://github.com/hl7/jIRA-Spec-Artifacts on Jul 27, 2020 https://github.com/HL7/JIRA-Spec-Artifacts/commits/master/xml/FHIR-us-davinci-deqm.xml
The jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG.  A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts.
# COPIED FROM Data Exchange For Quality Measures STU2 IG This device profile is intended to model software systems as devices, not implantable devices like what the US Core profile is describing. Approved by US Realm on 6/30/2020.
WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/device-softwaresystem-cqfm').baseDefinition: US FHIR Usage rules require that all profiles on Device derive from the core US profile
# COPIED FROM Data Exchange For Quality Measures STU2 IG These warnings are all caused by the use of the new text/cql.identifier media type. This has been addressed in the current R5 build and are expected to resolve once the core package updates.
ValueSet http://www.rfc-editor.org/bcp/bcp13.txt not found by validator
# the validator is trying to resolve an "example.org" artifact which by convention does not exist.
The Measure "http://example.org/fhir/Measure/measure-medicare-stratification-example" could not be resolved, so no validation can be performed against the Measure

Which only resolves one of the 2 warnings

view this post on Zulip Eric Haas (Aug 07 2020 at 02:31):

I have given up..

view this post on Zulip Lloyd McKenzie (Aug 07 2020 at 03:16):

Are you grabbing the warning text from qa.txt? (Don't try to grab from qa.html)

view this post on Zulip Eric Haas (Aug 07 2020 at 14:56):

yes

view this post on Zulip Lloyd McKenzie (Aug 07 2020 at 15:20):

Is this online somewhere?

view this post on Zulip David deRoode (Aug 07 2020 at 19:14):

The below suppressed messages are still appearing in my QA as well:
US FHIR Usage rules require that all profiles on Observation derive from one of the base US profiles. Comparison with US Core Pediatric BMI for Age Observation Profile. Comparison with US Core Pediatric Weight for Height Observation Profile. Comparison with US Core Laboratory Result Observation Profile. Comparison with US Core Pulse Oximetry Profile. Comparison with US Core Smoking Status Observation Profile
ValueSet https://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.31 not found by validator
ValueSet https://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.1.11.20.2.3 not found by validator
Code System URI "http://www.ama-assn.org/go/cpt" is unknown so the code cannot be validated

view this post on Zulip Lloyd McKenzie (Aug 07 2020 at 19:33):

You copied the messages to suppress from the qa.txt and copied the full line into your suppress file?

view this post on Zulip David deRoode (Aug 07 2020 at 20:51):

Yes, "INFORMATION: ServiceRequest/Resin-restore-example: ServiceRequest.code.coding[0]: Code System URI "https://ada.org/en/publications/cdt" is unknown so the code cannot be validated"

view this post on Zulip Lloyd McKenzie (Aug 07 2020 at 22:28):

Link to the content in Git and the CI build?

view this post on Zulip David deRoode (Aug 10 2020 at 14:16):

https://build.fhir.org/ig/HL7/dental-data-exchange/
https://github.com/HL7/dental-data-exchange/tree/master

view this post on Zulip Lloyd McKenzie (Aug 23 2020 at 21:36):

Looking at the current CI build, it appears the message is being appropriately suppressed?


Last updated: Apr 12 2022 at 19:14 UTC