FHIR Chat · Jira-Spec-Artifacts defaultWorkgroup · IG creation

Stream: IG creation

Topic: Jira-Spec-Artifacts defaultWorkgroup

view this post on Zulip Abdullah Rafiqi (Nov 12 2021 at 03:38):

Trying to check in FHIR-us-qicore and getting the following validation error in regards to assigning a value to defaultWorkgroup

validate:
[schemavalidate] Desktop/GitRepo/JIRA-Spec-Artifacts/xml/FHIR-us-qicore.xml:2:289: cvc-datatype-valid.1.2.1: '' is not a valid value for 'NMTOKEN'.
[schemavalidate] Desktop/GitRepo/JIRA-Spec-Artifacts/xml/FHIR-us-qicore.xml:2:289: cvc-attribute.3: The value '' of attribute 'defaultWorkgroup' on element 'specification' is not valid with respect to its type, 'WorkGroup'.

I can see that defaultWorkgroup="" when it should be cqi, should this be manually changed within the xml file or is there a change in a specific source that would generate the correct workgroup?

view this post on Zulip Jean Duteau (Nov 12 2021 at 07:44):

Never change things manually in the XML file. It is defined in your ImplementationGuide resource as the URL of the publisher element. That should correspond to the WG for your guide.

view this post on Zulip Abdullah Rafiqi (Nov 12 2021 at 14:56):

Thanks for the clarification @Jean Duteau. Looking at the IG resource I have the following in the publisher element and still not able to generate the defaultWorkgroup in the spec?

<publisher value="Clinical Quality Information WG"/>
  <contact>
    <name value="Clinical Quality Information WG"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/cqi/index.cfm"/>
    </telecom>
  </contact>

view this post on Zulip Jean Duteau (Nov 12 2021 at 16:51):

remove the /index.cfm. the URL should be http://www.hl7.org/Special/committees/cqi

view this post on Zulip Abdullah Rafiqi (Nov 15 2021 at 00:29):

Looks to have sorted out the defaultWorkgroup issue, now generating the following:

ERROR: Version with code 2.0 in specification FHIR-us-qicore has been removed or changed.  Versions should never change.  Keys should also not be removed.  Versions can only be removed if no JIRA tracker references that version.  If this is the case and the version should really be removed, please coordinate with an administrator.

Current version that we are publishing is 4.1.0, is the error due to there being no version 2.0 but instead 2.0.0 in FHIR-us-qicore being checked in?

view this post on Zulip Jean Duteau (Nov 15 2021 at 00:41):

You previously had a version 2.0. You can’t change that once it exists. So you need to put version 2.0 back. Or reach out to @Lloyd McKenzie if you really really don’t want v2.0 to show up (and if there are no Jira tickets against it)

view this post on Zulip Jean Duteau (Nov 15 2021 at 00:49):

Just checked and you have a bunch of tickets against v2.0. So you can’t get rid of it.

view this post on Zulip Jean Duteau (Nov 15 2021 at 00:59):

@Lloyd McKenzie Looks like the initial FHIR-us-qicore was manually created as it only has version=“2.0” and all of the tickets are against that. The generated one has a whole swack of versions listed except for 2.0

view this post on Zulip Lloyd McKenzie (Nov 15 2021 at 02:19):

If there are tickets against 2.0, then it needs to be retained. You can mark it as deprecated, but you can't remove it.

view this post on Zulip Abdullah Rafiqi (Nov 15 2021 at 18:30):

@Lloyd McKenzie I can't see anything in the package-list json to set deprecated=true. In this scenario would this be done manually in the XML?

view this post on Zulip Bryn Rhodes (Nov 15 2021 at 19:02):

Yes

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -