Stream: IG creation
Topic: Errors with FHIR 4b guide
Giorgio Cangioli (Jun 29 2021 at 10:11):
Compiling a FHIR 4b-based guide I'm experiencing "new" errors I don't see in FHIR 4-based guides..
For example I have about 20 of errors in my ig.xml like these ones
ImplementationGuide.definition.parameter[0].code error The value provided ('copyrightyear') is not in the value set http://hl7.org/fhir/ValueSet/guide-parameter-code|4.1.0 (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#copyrightyear in http://hl7.org/fhir/guide-parameter-code)
ImplementationGuide.definition.parameter[1].code error The value provided ('releaselabel') is not in the value set http://hl7.org/fhir/ValueSet/guide-parameter-code|4.1.0 (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#releaselabel in http://hl7.org/fhir/guide-parameter-code)
that I cannot fix, being these parameters required by the Publisher
Suggestions are welcome
Grahame Grieve (Jun 29 2021 at 10:47):
no you can't fix those. That's something you'll have to put up with
Giorgio Cangioli (Jun 29 2021 at 12:35):
Grahame Grieve said:
That's something you'll have to put up with
Should I have a similar approach also for other kinds of errors like these ones ?
StructureDefinition.snapshot.element[1].type[0].extension[0] error The Extension 'http://hl7.org/fhir/StructureDefinition/structuredefinition-fhir-type' definition allows for the types [url] but found type uri
StructureDefinition.snapshot.element[4].binding.extension[0] error The extension http://hl7.org/fhir/build/StructureDefinition/definition is unknown, and not allowed here
StructureDefinition.snapshot.element[4].binding.extension[0].url error URL value 'http://hl7.org/fhir/build/StructureDefinition/definition' does not resolve
..or they are things I can try to fix ?
Grahame Grieve (Jun 29 2021 at 12:45):
no you can't fix those either
Giorgio Cangioli (Jun 29 2021 at 12:54):
Ok, thanks.
.. just to complete the report :-) I've about 51000 broken links with errors like:
The link 'http://build.fhir.org/branches/R4B//datatypes.html#Coding#Coding.system' for "system" cannot be resolved or
The link 'http://build.fhir.org/' for "FHIR 4.1.0" cannot be resolved
can be them "ignored" or this works only for warnings ?
Lloyd McKenzie (Jun 29 2021 at 13:16):
Ignored only works for warnings
Grahame Grieve (Jun 29 2021 at 18:35):
you shouldn't get the second error - where are you getting it?
Giorgio Cangioli (Sep 28 2021 at 10:49):
these errors appear in the "fhir-for-fair" IG
"The link 'http://build.fhir.org/' for "FHIR 4.1.0" cannot be resolved" seems to be associated to the link in the footer (but the link works)
the other broken links appear for each element in the structureDefinition (but also in this case the link seems to work..)
The plan is to have the ballot in January, any suggestion on how to clean the qa.html ?
Grahame Grieve (Sep 29 2021 at 07:47):
fixed next release
Giorgio Cangioli (Mar 22 2022 at 21:39):
I've a set of (new) errors in the FHIR for FAIR guide I'm not able to address.
They appear in profiles where I'm using extensions.
The extension http://hl7.org/fhir/build/StructureDefinition/binding-definition is unknown, and not allowed here
URL value 'http://hl7.org/fhir/build/StructureDefinition/binding-definition' does not resolve
Suggestions ?
Lloyd McKenzie (Mar 22 2022 at 22:06):
Are you using the latest publisher? It should make that problem go away. If not, the next release ought to. It's a tooling issue, not anything you have control over.
Giorgio Cangioli (Mar 23 2022 at 07:41):
Looking at the QA.html file it should be the latest .. I'll wait for next versions :-)
David Pyke (Mar 23 2022 at 15:29):
I'm using the latest publisher and getting these as well using R5 snapshot 1
Giorgio Cangioli (Mar 31 2022 at 13:30):
Is there any plan for these errors ? ... are there also with v114...
Lloyd McKenzie (Mar 31 2022 at 15:19):
Yes. They will go away at some point. Ignore for now.
Last updated: Apr 12 2022 at 19:14 UTC
