Stream: IG creation
Topic: Library.relatedArtifact slicing
Sarah Gaunt (Nov 17 2021 at 06:44):
We (@Adam Stevenson , @Bryn Rhodes ) are getting the following error: Library.relatedArtifact:sliceComputableLibrary: minimum required = 1, but only found 0 (from http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-supplemental-library)
This is the profile: http://build.fhir.org/ig/HL7/case-reporting/branches/master/StructureDefinition-us-ph-supplemental-library.html). (Git: https://github.com/HL7/case-reporting/blob/master/input/resources/structuredefinition/us-ph-supplemental-library.xml)
The example in question definitely contains all 3 required slices: https://github.com/HL7/case-reporting/blob/master/input/resources/library/library-us-ph-supplemental-library-example.xml:
<relatedArtifact>
<type value="composed-of"/>
<resource value="http://aphl.org/fhir/ecr/Library/RuleFilters"/>
</relatedArtifact>
<relatedArtifact>
<type value="composed-of"/>
<resource value="http://hl7.org/fhir/us/ecr/Library/library-us-ph-supplemental-valueset-library-example"/>
</relatedArtifact>
<relatedArtifact>
<type value="composed-of"/>
<resource value="http://hl7.org/fhir/us/ecr/ValueSet/valueset-us-ph-supplemental-valueset-example"/>
</relatedArtifact>
I can't see anything wrong with the slicing in the profile or with the example...
Sarah Gaunt (Nov 17 2021 at 06:51):
Might be a targetProfile vs profile issue... Testing now. Wasn't that!
Richard Townley-O'Neill (Nov 17 2021 at 07:00):
Can a Library satisfy both slices relatedArtifact:sliceComputableLibrary and relatedArtifact:sliceSupplementalValueSetLibrary ? That might cause a problem. But I'd expect it to be a different error.
Sarah Gaunt (Nov 17 2021 at 07:03):
Possibly (will check) but yeah, would expect to get my favourite "multiple matching slices" error if that were the case...
Sarah Gaunt (Nov 17 2021 at 07:06):
And no, I don't think a Library could match both.
Sarah Gaunt (Nov 17 2021 at 07:14):
Actually - I think it might be because of the error we are getting on RuleFilters.xml: "Canonical URL 'http://hl7.org/fhir/Library/FHIRHelpers|4.0.1' does not resolve" and FHIRHelpers.xml: "Canonical URL 'http://hl7.org/fhir/Library/FHIR-ModelInfo|4.0.1' does not resolve"
We have a known issue for that on the front page of the IG: https://jira.hl7.org/browse/FHIR-30477
@Lloyd McKenzie would you be able to confirm this is indeed the issue - we are coming to FMG tomorrow for publication approval and will need an exemption for this error, if the above is indeed the cause.
Lloyd McKenzie (Nov 17 2021 at 16:16):
If it can't find the profile, then it can't test if the instance is valid against the profile
Sarah Gaunt (Nov 17 2021 at 21:55):
Looks like the error I mentioned about the FHIRHelpers has been resolved, so I guess that is not the issue...
Sarah Gaunt (Nov 18 2021 at 00:16):
@Adam Stevenson fixed the issue! I'll let @Lynn Laakso and @Melva Peters know when I send them the final IG (i.e. when I've done the Jira spec file...)
Grahame Grieve (Nov 18 2021 at 00:26):
what was the fix?
Sarah Gaunt (Nov 18 2021 at 00:41):
@Adam Stevenson can probably explain...
His commit messages are:
- Removed FHIRHelpers and FHIR-ModelInfo Libraries and 'known issues' header
- Fixed triggering-valueset profile slicing; update chlamydia example valueset
- Fixed RuleFilters Library url to resolve slicing error
I haven't had a chance to look at the changes properly yet.
Adam Stevenson (Nov 18 2021 at 01:13):
The solution for the library example's relatedArtifact not satisfying the slice was to change the referenced Library's url base to match the IG's canonical base.
Last updated: Apr 12 2022 at 19:14 UTC
