FHIR Chat · Summary of remaining open DEQM QA issues · IG creation

Stream: IG creation

Topic: Summary of remaining open DEQM QA issues


view this post on Zulip Eric Haas (Jul 08 2020 at 22:57):

Issues:

  1. Capabilitystatement Errors due to context rules on extensions http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation - this causes dozens of errors here and 100s on US Core. How to resolve this?

ZULIP LINK: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/new.20validation.20error.20on.20extensions

CapabilityStatement/reporter-client: CapabilityStatement.rest[0].resource[0]    error   The extension http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation is not allowed to be used at this point (allowed = e:CapabilityStatement.rest.resource.interaction, e:CapabilityStatement.rest.resource.searchParam, e:CapabilityStatement.rest.searchParam, e:CapabilityStatement.rest.operation, e:CapabilityStatement.document, e:CapabilityStatement.rest.interaction, e:CapabilityStatement.rest.resource.searchInclude, e:CapabilityStatement.rest.resource.searchRevInclude; this element is [[CapabilityStatement.rest.resource, BackboneElement.resource, BackboneElement])
  1. the "|" syntax for canonicals is causing an error. within the text narrative.

ZULIP LINK: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/validation.20errors.20when.20using.20'.7Cn.2En.2En'.20for.20canonical.20url

CapabilityStatement/reporter-client: CapabilityStatement.rest[0].resource[0]    error   The extension http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation is not allowed to be used at this point (allowed = e:CapabilityStatement.rest.resource.interaction, e:CapabilityStatement.rest.resource.searchParam, e:CapabilityStatement.rest.searchParam, e:CapabilityStatement.rest.operation, e:CapabilityStatement.document, e:CapabilityStatement.rest.interaction, e:CapabilityStatement.rest.resource.searchInclude, e:CapabilityStatement.rest.resource.searchRevInclude; this element is [[CapabilityStatement.rest.resource, BackboneElement.resource, BackboneElement])
  1. The new undocumented validation rules for MR that failed to recognise the data exchange use case.

ZULIP LINK: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/spurious.20MR.20error

MeasureReport/datax-measurereport01: MeasureReport (l1/c2)  error   The MeasureReport does not include a group for the group MRP Group
  1. The new undocumented validation rules for MR that failed to recognise the possibility for and extension on the measure score.

ZULIP LINK: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/MR.20error.20for.20MeasureScore.20despite.20extension

Path    Severity    Message
MeasureReport/date-of-last-power-outage: MeasureReport (l1/c2)  Process Info    Validate resource against profile http://hl7.org/fhir/StructureDefinition/MeasureReport
MeasureReport/date-of-last-power-outage: MeasureReport.group[0].measureScore (l62/c31)  error   A value is required when the Measure.scoring={0}
  1. StructureDefinition-medicationrequest-deqm.xml can the VTE folks provide an example using it? @Bryn Rhodes
StructureDefinition.where(url = 'http://hl7.org/fhir/us/davinci-deqm/StructureDefinition/medicationrequest-deqm')   warning The Implementation Guide contains no examples for this profile
  1. Cannot get the dependencies to QI Core v4.0.0 to work; (J#26303)

ZULIP CHAT: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/dependency.20issue.20to.20Quality.20IGs

  1. CQFM url links are bad - assuming these will go away when it is published.

view this post on Zulip Grahame Grieve (Jul 14 2020 at 00:18):

trying to run the current DEQM:

org.hl7.fhir.exceptions.FHIRException: Error loading template /Users/ehaas/Documents/FHIR/ig-template-base: Unable to load template from /Users/ehaas/Documents/FHIR/ig-template-base cannot find template. Use a github URL, a local directory, or #[folder] for a contained template

view this post on Zulip Eric Haas (Jul 14 2020 at 02:26):

oops , recommitting with davinci templates ...

view this post on Zulip Grahame Grieve (Jul 15 2020 at 02:03):

the "|" syntax for canonicals is causing an error. within the text narrative.

That's in the narrative you created...

view this post on Zulip Eric Haas (Jul 15 2020 at 02:26):

yes via a Python library.

view this post on Zulip Grahame Grieve (Jul 15 2020 at 02:40):

well, you have to URLEncode the | in the html ref.

view this post on Zulip Grahame Grieve (Jul 15 2020 at 02:41):

MR that failed to recognise the data exchange use case

fixed next release

view this post on Zulip Eric Haas (Jul 15 2020 at 18:06):

thanks

view this post on Zulip Eric Haas (Jul 17 2020 at 00:35):

Re the the "|" syntax I url encoded it and now am getting these kinds of errors:

CapabilityStatement-consumer-client.html#/html/body/div/div/div/div/div/div/ul/li/a at Line 233, column 1017    error   The link 'http://hl7.org/fhir/us/qicore/ImplementationGuide/hl7.fhir.us.qicore%7C4.0.0' for "http://hl7.org/fhir/us/qicore/ImplementationGuide/hl7.fhir.us.qicore%7C4.0.0" cannot be resolved

and yet these url resolve.

view this post on Zulip Eric Haas (Jul 17 2020 at 00:39):

here is the file:

https://build.fhir.org/ig/HL7/davinci-deqm/CapabilityStatement-consumer-client.json.html

and here is the offending bit in the narrative reproduced here:

<ul>
  <li>
    <ahref=\"http://hl7.org/fhir/us/qicore/ImplementationGuide/hl7.fhir.us.qicore%7C4.0.0\">http://hl7.org/fhir/us/qicore/ImplementationGuide/hl7.fhir.us.qicore%7C4.0.0</a>
  </li>
</ul>
<ul>
  <li>
    <ahref=\"http://hl7.org/fhir/us/cqfmeasures/ImplementationGuide/hl7.fhir.us.cqfmeasures%7C2.0.0\">http://hl7.org/fhir/us/cqfmeasures/ImplementationGuide/hl7.fhir.us.cqfmeasures%7C2.0.0</a>
  </li>
</ul>

view this post on Zulip Grahame Grieve (Jul 17 2020 at 01:25):

that will be fixed this coming release

view this post on Zulip Eric Haas (Jul 21 2020 at 16:01):

@Grahame Grieve OK thanks for the fixes here is where DEQM is at for publishing errors:

Issues:
1. as discussed on FHIR-I CapabilityStatement Errors due to context rules on extensions

http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation

ZULIP LINK: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/new.20validation.20error.20on.20extensions

2. StructureDefinition-medicationrequest-deqm.xml VTE example

MedicationRequest example based on VTE1 Measure (For Medication Not
Ordered Concept) violates QI Core MedicationRequest Profile

        Bundle/single-indv-vte-report-option7: Bundle.entry[6].resource.ofType(MedicationRequest).doNotPerform (l484/c30)   error   Value is "true" but must be "false"

created FHIR-2814 - this one won't
be fixed before publishing.
(FYI @Bryn Rhodes )

3. Cannot get the dependencies to QI Core v4.0.0 to work - the links now resolve (thanks) but now there are over 100 build link errors being reported in the IG.

4. CQFM url links are bad - assuming these will go away when CQFM is published.

view this post on Zulip Grahame Grieve (Jul 22 2020 at 01:06):

3 - fixed
4 - yes.
2 - nothing for me to do (yay!)

  1. fixed next release

view this post on Zulip Bryn Rhodes (Jul 22 2020 at 20:33):

@Eric Haas , I added a comment on the story there

view this post on Zulip Eric Haas (Jul 23 2020 at 00:25):

thanks Bryn I will update the profile!

view this post on Zulip Eric Haas (Jul 27 2020 at 20:48):

one more issue cropped up over the weekend (thanks for the fixes):

rendered link in the narrative to CQFM extension in DEQM StructureDefinitions are malformed.

~~~
The URL
file://C:\GitHub\hl7.fhir.us.cqfmeasures#2.0.0\output/StructureDefinition-device-softwaresystem-cqfm.html
is not valid (URL contains Invalid
Characters ([\]))
~~~

here and here:

view this post on Zulip Grahame Grieve (Jul 27 2020 at 20:48):

what is your dependency?

view this post on Zulip Eric Haas (Jul 27 2020 at 20:49):

  - version: 2.0.0
    id: cqfm
    packageId: hl7.fhir.us.cqfmeasures
    uri: 'http://hl7.org/fhir/us/cqfmeasures/ImplementationGuide/hl7.fhir.us.cqfmeasures'

view this post on Zulip Grahame Grieve (Jul 27 2020 at 20:56):

ok fixed next release


Last updated: Apr 12 2022 at 19:14 UTC