Stream: IG creation
Topic: Unable to resolve auto-generated link?
Sean McIlvenna (Mar 21 2018 at 22:01):
Getting this error: "The link 'StructureDefinition/hai-report-questionnaire.html|Healthcare Associated Infection Report Questionnaire#Questionnaire.id' cannot be resolved"
The link appears to be auto-generated by the ig-publisher. Wondering if anyone knows how this link is generated, and what it's based on
Sean McIlvenna (Mar 21 2018 at 22:06):
I'm also getting this error:
"The link 'http://hl7-fhir.github.io/??.html#Reference' cannot be resolved"
Sean McIlvenna (Mar 21 2018 at 22:06):
No idea why the ?? is in there
Grahame Grieve (Mar 21 2018 at 22:07):
I do. can I reproduce these?
Sean McIlvenna (Mar 21 2018 at 22:07):
Sean McIlvenna (Mar 21 2018 at 22:07):
the entire ig (which is rather small right now) is in there
Sean McIlvenna (Mar 21 2018 at 22:07):
it builds, but with a ton of these errors that I can't figure out
Sarah Gaunt (Mar 21 2018 at 22:14):
Though if you add in the questionnaire-item-note resource to the IG file, it no longer builds and you get the dupe id error.
I'll add that into the file and comment it out and commit it (because it does need to be there).
Sean McIlvenna (Mar 21 2018 at 22:15):
@Sarah Gaunt , thinking questionnaire-item-note is an extension built into the spec
Sarah Gaunt (Mar 21 2018 at 22:15):
It's our extension.
Sean McIlvenna (Mar 21 2018 at 22:15):
I thought I saw it on the main extensions
Sean McIlvenna (Mar 21 2018 at 22:15):
(and used in other igs)
Sarah Gaunt (Mar 21 2018 at 22:16):
Let me double check.
Sean McIlvenna (Mar 21 2018 at 22:16):
but, not finding it, either
Sean McIlvenna (Mar 21 2018 at 22:16):
so, maybe I'm full of it
Sarah Gaunt (Mar 21 2018 at 22:16):
Yeah, it's ours! I'm pretty sure I created it, memory hazy... :)
Sean McIlvenna (Mar 21 2018 at 22:17):
making sure no one included in dependencies either
Sean McIlvenna (Mar 21 2018 at 22:18):
yup, don't see it anywhere
Sarah Gaunt (Mar 21 2018 at 22:18):
You might be thinking of questionnaire-allowed-profile - that's not ours
Sean McIlvenna (Mar 21 2018 at 22:19):
yah, must be
Grahame Grieve (Mar 21 2018 at 22:55):
so this guide is not set up for the auto-ig-publisher. It needs to be
Sarah Gaunt (Mar 21 2018 at 22:57):
Don't we need to get it publishing locally first?
Grahame Grieve (Mar 21 2018 at 22:58):
that's up to you. but it seems like a good idea to have it set up correctly so that you can get it running on the auto-ig-publisher without too much fuss
Sarah Gaunt (Mar 21 2018 at 22:58):
Fair enough
Grahame Grieve (Mar 21 2018 at 22:59):
I've made a change that will affect your build... the IG publisher now uses validator.pack instead of definitions.json.zip - so that's for US core.
Grahame Grieve (Mar 21 2018 at 23:00):
anyway, I have it building, and I see all the errors. I will look into them later today
Lloyd McKenzie (Mar 21 2018 at 23:14):
What's the reason for the switch?
Lloyd McKenzie (Mar 21 2018 at 23:15):
I've got an externally-created definitions.json.zip that's generated by a custom process - not produced by the IGPublisher. Can I just rename the file or do they need to add new content?
Eric Haas (Mar 22 2018 at 00:39):
Can you elaborate on the issue for US Core and does this affect how to use dependencies in ig.json?
Grahame Grieve (Mar 22 2018 at 05:46):
validator.pack is in 3.2.0 version. definitions.x.zip was but that was a bug and it just got changed to be in the version of the ig. so now validator.pack is what the IG publisher wants
Grahame Grieve (Mar 22 2018 at 05:47):
if you nominate the path of the actual ig in the json file - which is what the doco says to do - then things will continue to work just fine. if you hack with the process, then you'll have to change your hack
Last updated: Apr 12 2022 at 19:14 UTC
