Stream: IG creation
Topic: bad links to core r3 and r4 specification
Eric Haas (Mar 09 2019 at 19:16):
for DEQM source= bad_links_branch
link to qa.html report = http://build.fhir.org/ig/HL7/davinci-deqm/qa.html#internal
I have multiple bad links to core r3 and r4 specification in both the local build and autobuild. They all seem to good links to me.
-
What is new is that I am using site variables that I define in _config.yml :
*{{site.r4}} = http://hl7.org/fhir/R4/
*{{site.r3}} = http://hl7.org/fhir/STU/ ( instead of the{{site.data.fhir.path}}
) -
all the links are defined in a single page: source/includes/link-list.md
here is sample from the qa report:
datax.html#/html/head/body/div/div/div/div/div/div/p/a at Line 297, column 529 error The link 'http://hl7.org/fhir/R4/operations.html' for "FHIR operations" cannot be resolved datax.html#/html/head/body/div/div/div/div/div/div/ol/li/a at Line 422, column 27 error The link 'http://hl7.org/fhir/R4/measure-operation-data-requirements.html' for "$data-requirements (R4)" cannot be resolved datax.html#/html/head/body/div/div/div/div/div/div/ol/li/a at Line 572, column 31 error The link 'http://hl7.org/fhir/R4/measure-operation-submit-data.html' for "$submit-data (R4)" cannot be resolved datax.html#/html/head/body/div/div/div/div/div/div/ol/li/a at Line 698, column 225 error The link 'http://hl7.org/fhir/R4/measure-operation-collect-data.html' for "$collect-data (R4)" cannot be resolved datax.html#/html/head/body/div/div/div/div/div/div/p/a at Line 866, column 89 error The link 'http://hl7.org/fhir/STU3/subscription.html' for "Subscription" cannot be resolved
Furthermore ONLY in the autobuild several new bad links arise assigning extensions a us core path to body-site-extension instead of the fhir specification.
here is an example:
StructureDefinition-organization-deqm-definitions.html#/html/head/body/div/div/div/div/div/div/table/tr/td/br/tr/td/p/a at Line 608, column 339 error The link 'http://hl7.org/fhir/us/core/extension-rendered-value.html' for "Rendered Value extension" cannot be resolved StructureDefinition-medicationadministration-deqm-definitions.html#/html/head/body/div/div/div/div/div/div/table/tr/td/br/tr/td/p/a at Line 577, column 168 error The link 'http://hl7.org/fhir/STU3/extension-body-site-instance.html' for "body-site-instance" cannot be resolved
Eric Haas (Mar 09 2019 at 19:18):
I can work around this in the short term but would certainly like to define paths globally and easily going forward. so I need to figure out if its user error or not.
other paths I defined this way seem to be ok.
Eric Haas (Mar 10 2019 at 19:30):
digging into to spurious us core extension errors. DEQM --> QI Core --> US Core --> STU3 . The references are links in the descriptions of the extensions and are defined in STU3 StructureDefinition using standard markdown syntax. They show up in the snapshot for each profile definition and the link changes for STU3 to us core. once practitioner is profile in US Core. Note that US Core does not mention or use the constraint, but is still showing up in the snapshot in the SD. So there are to or three issues here.
- local vs autobuild behavior is different these bad links only in the autobuild and not locally
- unused Extensions appearing in snapshot
- links in descriptions using wrong path. instead of STU3 using the ig canonical path. ( since the original description is using relative path = e.g.
[name of extension](extension-path.html)
that part kind of makes sense.
Sarah Gaunt (Mar 11 2019 at 06:04):
I am getting something similar:
Patient-hai-patient-1.html#/html/head/link/body/div/div/div/p/a at Line 309, column 107 error The link 'http://hl7.org/fhir/STU3/' for "FHIR Version: 3.0.1" cannot be resolved CodeSystem-2.16.840.1.113883.6.259.json.html#/html/head/link/body/div/div/div/p/a at Line 1228, column 107 error The link 'http://hl7.org/fhir/STU3/' for "FHIR Version: 3.0.1" cannot be resolved Questionnaire-hai-questionnaire-los-event.json.html#/html/head/link/body/div/div/div/p/a at Line 648, column 107 error The link 'http://hl7.org/fhir/STU3/' for "FHIR Version: 3.0.1" cannot be resolved
Links all appear to be good.
Think they are from here in our footer.html: {{site.data.fhir.versionFull}}
Grahame Grieve (Mar 11 2019 at 10:50):
I have to rebuild US Core to fix these
Grahame Grieve (Mar 11 2019 at 10:50):
can't easily do that
Grahame Grieve (Mar 11 2019 at 10:50):
I will fix links by hand if I have to
Eric Haas (Mar 11 2019 at 14:19):
Let me know if I can help with us core
Eric Haas (Mar 11 2019 at 18:42):
my r3 r4 issue was boneheaded mistake in my config file...
Eric Haas (Mar 11 2019 at 18:43):
forgot to append STU3 in the source path
Last updated: Apr 12 2022 at 19:14 UTC