Stream: IG creation
Topic: error using standard extensions
Jose Costa Teixeira (Mar 11 2020 at 07:51):
I'm getting this when I use a standard extension
Unable to find name for the resource StructureDefinition/iso21090-ADXP-houseNumber. Names are mandatory to allow proper population of the artifact list.
Jose Costa Teixeira (Mar 11 2020 at 07:52):
I don't declare them in the IG, they just get picked up by the publisher because they are in my input folder.
is that the reason?
Update: Yes, seems that is the reason.
Jose Costa Teixeira (Mar 11 2020 at 08:22):
Now I get another error:
the canonical URL (https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/iso21090-ADXP-houseNumber) does not match the URL (http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber)
How can i fix this? The extension's canonical URL should remain at hl7.org... right?
Giorgio Cangioli (Mar 11 2020 at 09:10):
Hi Jose,
as a general comment I fixed this kind of URL errors by using the 'special-url' parameter
e.g.
<parameter>
<code value="special-url"/>
<value value="http://terminology.hl7.it/CodeSystem/istat-statoCivile"/>
</parameter>
However, I don't think this should apply for published hl7.org extensions
So far I've used these standard extensions iso21090-ADXP- too, without adding them as special-url parameter.....
Giorgio Cangioli (Mar 11 2020 at 09:11):
Curious to learn if anything has changed :-)
Giorgio Cangioli (Mar 11 2020 at 09:47):
..just tried to recompile my IG that uses these extensions with the latest IG publisher and I've not such a kind of error...
Jose Costa Teixeira (Mar 11 2020 at 09:51):
thanks, let me see what is wrong on my side.
Jose Costa Teixeira (Mar 11 2020 at 10:03):
@Giorgio Cangioli , where is your IG for me to compare?
Grahame Grieve (Mar 11 2020 at 11:41):
How can i fix this? The extension's canonical URL should remain at hl7.org... right?
It looks like you are trying to redeclare the extension, rather than use it?
Jose Costa Teixeira (Mar 11 2020 at 12:13):
Yes, correct. I had them there because I wanted them to be available in the download. Removing them removes the error.
Jose Costa Teixeira (Mar 11 2020 at 12:13):
Thanks
Grahame Grieve (Mar 11 2020 at 12:56):
they'll be in a dependent package.
Lloyd McKenzie (Mar 11 2020 at 15:23):
Right now, we don't allow inclusion of dependent artifacts in the download for an IG. We've discussed the notion of 'importing' artifacts, but right now that's not enabled.
Jose Costa Teixeira (Mar 11 2020 at 15:54):
Yes, i recall that, but I did not change accordingly. my bad
Last updated: Apr 12 2022 at 19:14 UTC
