Stream: IG creation
Topic: ImplementationGuide.definition.resource
Nick George (Mar 27 2020 at 19:59):
Moving to this stream per Grahame's suggestion - do I need to manually list every resource in my IG in the ImplementationGuide.definition.resource field? Seems like since it already pulls in all the structure definitions from the input/resources dir, that should be sufficient?
Jens Villadsen (Mar 27 2020 at 19:59):
you don't have to
Jens Villadsen (Mar 27 2020 at 19:59):
So far I've succeeded only listing examples
Jens Villadsen (Mar 27 2020 at 20:01):
There's an example here https://github.com/hl7dk/dk-core/blob/master/input/dk.fhir.ig.dk-core.xml
Nick George (Mar 27 2020 at 20:03):
ahh cool, the error I'm seeing is
Unable to find name for the resource StructureDefinition/Patient. Names are mandatory to allow proper population of the artifact list.
but the name field is populated in the struct defs
Jens Villadsen (Mar 27 2020 at 20:06):
is this where its comming from? https://github.com/HL7/ig-template-base/blob/9cc9002f2ead2f258ad162ee6842d10a517dcc3a/scripts/onGenerate.qa.xslt#L17
Nick George (Mar 27 2020 at 20:07):
certainly fits the bill
Jens Villadsen (Mar 27 2020 at 20:10):
It's also present in the UTG IG, (https://build.fhir.org/ig/HL7/UTG/branches/master/qa.html) but I can see that it does not stop the build there
Jens Villadsen (Mar 27 2020 at 20:10):
Maybe @Lloyd McKenzie being the author to the xslt can say what the problem is?
Lloyd McKenzie (Mar 27 2020 at 21:19):
The issue isn't Patient.name, it's ImplementationGuide.definition.resource.name. All examples need to be enumerated in the implementation guide because that's the only place that a name and description can be defined (unlike profiles, value sets, etc. where the tooling will automatically grab the titles and descriptions from there). I'll update the error message to be even more clear.
Lloyd McKenzie (Mar 27 2020 at 21:23):
Done. Should be effective in about 60 seconds.
Nick George (Mar 27 2020 at 21:23):
but I don't have any examples in my IG
Lloyd McKenzie (Mar 27 2020 at 21:25):
Sorry, I misread the thread. The resource.name is inferred from StructureDefinition.title, not StructureDefinition.name - that might be your issue?
Nick George (Mar 27 2020 at 21:25):
ah yeah. I have name and id but not title
Lloyd McKenzie (Mar 27 2020 at 21:26):
I had proposed renaming IG.definition.resource.name to title to help reduce some of this confusion, but I think it got turned down.
Nick George (Mar 27 2020 at 21:26):
it's pretty confusing as-is, at the least maybe say that the title must be populated instead of saying name must be populated
Nick George (Mar 27 2020 at 21:27):
thanks for the help though
Lloyd McKenzie (Mar 27 2020 at 21:29):
Well, the issue is that what it's looking at is the ImplementationGuide - where it needs resource.name. The version of the ImplementationGuide it's working with is one that's gone through pre-processing where some of the names and descriptions have been filled in from elsewhere - and at that point in the processing it has no clue where stuff came from. It also doesn't know what elements the extraction would have happened from.
Last updated: Apr 12 2022 at 19:14 UTC
