Stream: australia
Topic: IG Publisher Issue Hit List
Brett Esler (Jun 23 2018 at 00:09):
I will attempt to keep this stream up to date whilst the issues remain for reference:
1. Reference to package in ig.json is resolved but seems to always use the canonical URL for links on output rather than the package location e.g. uses http://hl7.org.au/fhir rather than http://build.fhir.org/ig/hl7au/au-fhir-base as in the package-list.json entry for 'current' version (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/IG.20other.20package.20references) (For: AU-PD, Agency, Child Health, AU- Arogonaut)
2. Derived profiles that add a discriminator to an existing sliced element fail to build (see:https://chat.fhir.org/#narrow/stream/9-committers/topic/Discrimnator.20differential) (For: AU-argonaut, AU-PD, Agency)
3. Query on behaviour of output of external ValueSet references - should I expect more of the ValueSet publisher? (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/subject/ValueSet.20resolution) (For: AU-Base, Agency)
4. OpenAPI outputs failing for CapabilityStatement on build (see: https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/OpenAPI) (for: AU-PD, Child Health)
Brett Esler (Jun 26 2018 at 01:57):
1. Reference to package in ig.json is resolved but seems to always use the canonical URL for links on output rather than the package location e.g. uses http://hl7.org.au/fhir rather than http://build.fhir.org/ig/hl7au/au-fhir-base as in the package-list.json entry for 'current' version (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/IG.20other.20package.20references) (For: AU-PD, Agency, Child Health, AU- Arogonaut)
2. Derived profiles that add a discriminator to an existing sliced element fail to build (see:https://chat.fhir.org/#narrow/stream/9-committers/topic/Discrimnator.20differential) (For: AU-argonaut, AU-PD, Agency)
3. Query on behaviour of output of external ValueSet references - should I expect more of the ValueSet publisher? (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/subject/ValueSet.20resolution) (For: AU-Base, Agency)
4. OpenAPI outputs failing for CapabilityStatement on build (see: https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/OpenAPI) (for: AU-PD, Child Health)
5. Top level invariants (profile entry elements) appear in detailed description (e.g. http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation-definitions.html#Organization) but not in snapshot view (http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation.html#tabs-snap - see dom-x and org-1 missing from display)
David McKillop (Jun 26 2018 at 04:24):
@Brett Esler , @Grahame Grieve Just adding to the list :thumbs_up:
6. “IG Publisher - Adding Must Support to Patient.deceased.deceasedDateTime.date-accuracy-indicator “ refer to :
https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/Seeking.20advice.20on.20troubleshooting.20error.20with.20IG.20Publisher
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17165
7. " IG Publisher -"(unbound)" link replacing terminology binding when binding is not "example" - refer to:
https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/Additional.20.22(unbound).22.20link.20when.20not.20.22Example.22
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17117
Thanks.
Brett Esler (Jun 28 2018 at 01:26):
1. Reference to package in ig.json is resolved but seems to always use the canonical URL for links on output rather than the package location e.g. uses http://hl7.org.au/fhir rather than http://build.fhir.org/ig/hl7au/au-fhir-base as in the package-list.json entry for 'current' version (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/IG.20other.20package.20references) (For: AU-PD, Agency, Child Health, AU- Arogonaut)
2. Derived profiles that add a discriminator to an existing sliced element fail to build (see:https://chat.fhir.org/#narrow/stream/9-committers/topic/Discrimnator.20differential) (For: AU-argonaut, AU-PD, Agency)
3. Query on behaviour of output of external ValueSet references - should I expect more of the ValueSet publisher? (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/subject/ValueSet.20resolution) (For: AU-Base, Agency)
4. Top level invariants (profile entry elements) appear in detailed description (e.g. http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation-definitions.html#Organization) but not in snapshot view (http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation.html#tabs-snap - see dom-x and org-1 missing from display)
5. “IG Publisher - Adding Must Support to Patient.deceased.deceasedDateTime.date-accuracy-indicator “ refer to :
https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/Seeking.20advice.20on.20troubleshooting.20error.20with.20IG.20Publisher
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17165
6. " IG Publisher -"(unbound)" link replacing terminology binding when binding is not "example" - refer to:
https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/Additional.20.22(unbound).22.20link.20when.20not.20.22Example.22
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17117
OpenAPI output is operating with errors/warnings - taken out of this list..
Brett Esler (Jul 02 2018 at 11:26):
@Grahame Grieve these are the six issues with IG builder noted for AU work - 1,2 6 have the most impact on dependent project - let me know if more information is needed; AU-PD IG demonstrates all of these...
Grahame Grieve (Jul 02 2018 at 15:24):
ok
Brett Esler (Jul 17 2018 at 06:49):
1. Reference to package in ig.json is resolved but seems to always use the canonical URL for links on output rather than the package location e.g. uses http://hl7.org.au/fhir rather than http://build.fhir.org/ig/hl7au/au-fhir-base as in the package-list.json entry for 'current' version (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/IG.20other.20package.20references) (For: AU-PD, Agency, Child Health, AU- Arogonaut)
2. Derived profiles that add a discriminator to an existing sliced element fail to build (see:https://chat.fhir.org/#narrow/stream/9-committers/topic/Discrimnator.20differential) (For: AU-argonaut, AU-PD, Agency)
3. Query on behaviour of output of external ValueSet references - should I expect more of the ValueSet publisher? (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/subject/ValueSet.20resolution) (For: AU-Base, Agency)
4. Top level invariants (profile entry elements) appear in detailed description (e.g. http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation-definitions.html#Organization) but not in snapshot view (http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation.html#tabs-snap - see dom-x and org-1 missing from display)
5. “IG Publisher - Adding Must Support to Patient.deceased.deceasedDateTime.date-accuracy-indicator “ refer to :
https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/Seeking.20advice.20on.20troubleshooting.20error.20with.20IG.20Publisher
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17165
Number 6 looks fixed to me
David McKillop (Jul 17 2018 at 23:11):
Hi @Brett Esler FYI - I just updated to the latest IG Publisher (v3.4.0-13958, gen-code v3.4.0-13883), updated the "au-fhir-pd" repository and then ran the IG Publisher and found there were many examples of "(unbound)" present - refer to the attached:
unbound-link-20180718.JPG
Is there something else that I should be doing?
Brett Esler (Jul 17 2018 at 23:19):
perhaps try clearing your cache and building again....
David McKillop (Jul 17 2018 at 23:52):
Thanks - I deleted the contents of the "temp", "output", "qa" and "txCache" directories and I'm still getting the "(unbound)" problem. Are you not getting the presence of "(unbound)" with your "au-fhir-pd" IG Publisher build?
Brett Esler (Jul 18 2018 at 00:00):
try going to your windows user folder and removing the .fhir folder and rebuild; it will take a while...
Brett Esler (Jul 18 2018 at 00:00):
not getting that problem any more...
David McKillop (Jul 18 2018 at 00:31):
Yay - it worked. I'm not getting the "(unbound)" issue on "au-fhir-pd" I didn't know about deleting the .fhir folder - thanks for that.
I just deleted the .fhir again along with clearing the other directories in our "profile-library", ran the IG publisher and then looked at the 6 base profiles we have and "(unbound)" still exists on device.type:
unbound-device-link-20180718.JPG
which is really odd as it's the only instance remaining.
David McKillop (Jul 18 2018 at 01:06):
Hi @Brett Esler FYI - I found some instances of "(unbound)" in au-fhir-pd" ie there are 2 instances in the healthcareservice profile, but no other instances in any other au-fhir-pd profiles.
unbound-pd-link-20180718.JPG
Are you getting these in your build?
Brett Esler (Aug 10 2018 at 13:49):
@David McKillop those unbound elements are okay I think (they are unbound in the profiles)
Brett Esler (Aug 10 2018 at 13:49):
Current issues list
Brett Esler (Aug 10 2018 at 13:50):
1. Reference to package in ig.json is resolved but seems to always use the canonical URL for links on output rather than the package location e.g. uses http://hl7.org.au/fhir rather than http://build.fhir.org/ig/hl7au/au-fhir-base as in the package-list.json entry for 'current' version (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/IG.20other.20package.20references) (For: AU-PD, Agency, Child Health, AU- Arogonaut)
2. Derived profiles that add a discriminator to an existing sliced element fail to build (see:https://chat.fhir.org/#narrow/stream/9-committers/topic/Discrimnator.20differential) (For: AU-argonaut, AU-PD, Agency)
3. Query on behaviour of output of external ValueSet references - should I expect more of the ValueSet publisher? (See: https://chat.fhir.org/#narrow/stream/99-IG-creation/subject/ValueSet.20resolution) (For: AU-Base, Agency)
4. Top level invariants (profile entry elements) appear in detailed description (e.g. http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation-definitions.html#Organization) but not in snapshot view (http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation.html#tabs-snap - see dom-x and org-1 missing from display)
5. “IG Publisher - Adding Must Support to Patient.deceased.deceasedDateTime.date-accuracy-indicator “ refer to :
https://chat.fhir.org/#narrow/stream/99-IG-creation/topic/Seeking.20advice.20on.20troubleshooting.20error.20with.20IG.20Publisher
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17165
David McKillop (Aug 12 2018 at 22:57):
Hi @Brett Esler - I downloaded the latest publisher (v3.4.0-14790, gen-code v3.4.0-13883) and ran it this morning on:
1) au-fhir-pd (Provider Directory) and looking the Healthcare Service Profile there were 2 instances of "(unbound)":
Refer to Unbound-pd-HelathCareService-20180813.JPG
2) au-fhir-base and looking at the Healthcare Service profile there were 2 instances of "(unbound)":
Refer to Unbound-au-fhir-base-HCS-20180813.JPG
3) profile-library (Agency profiles) there were 1 instance of "(unbound)":
Refer to Unbound-device-20180813.JPG
Let me know if you need any further information.
David McKillop (Aug 15 2018 at 23:30):
Hi @Brett Esler - looking at the examples 1) to 3) above, I note that HealthcareService.eligibility and HealthcareService.characteristic are both unbound in STU3 and hence anything derived from these will also be unbound - hence don't worry about 1) & 2) above.
However, Device.type is bound to valueset-device-kind (example) in STU3, so I'm not sure why this one is giving "(unbound)" in in our derived profile. Your thoughts?
Last updated: Apr 12 2022 at 19:14 UTC
