Stream: IG creation
Topic: new Bundle validation behaviour
John Moehrke (Dec 14 2021 at 13:54):
I have re-built an IG, just to keep up-to-date, but now I am getting errors on example Bundles having content that is not matching profiles. This was working before, i think it is still right, but not now.
Did something changed in the rules the IG build is enforcing regarding Bundles? Profiles?
John Moehrke (Dec 14 2021 at 16:19):
seems "ref-1" is being enforced differently now than before?
Grahame Grieve (Dec 14 2021 at 18:58):
no change
John Moehrke (Dec 14 2021 at 22:20):
I have not changed my IG source. The sushi output, with new sushi, is logically identical to before. But now the IG publisher throws "ref-1" errors. The only thing I change is to get the new publisher. I get a couple of errors with the following pattern.
Bundle.entry[0] (l17/c6) error This element does not match any known slice defined in the profile http://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.Minimal.ProvideBundle and slicing is CLOSED: Bundle.entry[0]: Does not match slice 'SubmissionSet', Bundle.entry[0]: Details for Bundle matching against Profile http://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.Minimal.SubmissionSet, Bundle.entry[0]: Does not match slice 'DocumentRefs', Bundle.entry[0]: Details for Bundle matching against Profile http://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.Minimal.DocumentReference, Bundle.entry[0]: Does not match slice 'Documents', Bundle.entry[0]: Details for Bundle matching against Profile http://hl7.org/fhir/StructureDefinition/Binary, Bundle.entry[0]: Does not match slice 'Folders', Bundle.entry[0]: Details for Bundle matching against Profile http://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.Minimal.Folder, Bundle.entry[0]: Does not match slice 'Patient', Bundle.entry[0]: Details for Bundle matching against Profile http://hl7.org/fhir/StructureDefinition/Patient
Bundle (l1/c2) error Bundle.entry:SubmissionSet: minimum required = 1, but only found 0 (from http://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.Minimal.ProvideBundle)
Bundle.entry[0].resource.extension[1].value.ofType(Reference) (l57/c14) error ref-1: 'SHALL have a contained resource if a local reference is provided' 'SHALL have a contained resource if a local reference is provided' ( (url: in-practitioner2; ids: ))
John Moehrke (Dec 14 2021 at 22:21):
I am fine with being told that XYZ is now more strict, and that I had been taking advantage of liberal previous version of the IG builder..
John Moehrke (Dec 14 2021 at 22:21):
But, when I inspect the structure definitions and the examples, they look good to me.
John Moehrke (Dec 14 2021 at 22:32):
hm, my testBundle project does not have the problem... that one assembles similar bundles, but does not have any profiling.
John Moehrke (Dec 14 2021 at 22:35):
the project that is failing is a profiled bundle using #profile slicing discriminator
John Moehrke (Dec 14 2021 at 22:47):
nope. not an issue with #profile slicing. just migrated that to testBundle without failure
John Moehrke (Dec 14 2021 at 23:16):
I can't figure out why it built perfectly a month ago, but now fails on bundles with the ref-1 error
https://github.com/IHE/ITI.MHD
John Moehrke (Dec 15 2021 at 18:07):
@Grahame Grieve (I hope the fish were large and challenging) - I too was FSHing. I have isolated the bug. I have created a testBundle IG that isolates the problem.
https://github.com/JohnMoehrke/testBundle
cI-Build
http://build.fhir.org/ig/JohnMoehrke/testBundle/branches/main/index.html
John Moehrke (Dec 15 2021 at 18:10):
The errors are thrown when... I have a Bundle that is profiled, that bundle profile is by #profile, and a resource in the bundle has a contained resource.
See fshFood.fsh. comment out like 91 and 92 (the contained Practitioner); and no error will be thrown.
John Moehrke (Dec 15 2021 at 18:14):
note, it does not help for the profile of that resource to mandate contained resource. (line 80)
John Moehrke (Dec 16 2021 at 14:53):
https://github.com/HL7/fhir-ig-publisher/issues/357
Grahame Grieve (Dec 17 2021 at 03:37):
fixed next release
John Moehrke (Dec 23 2021 at 13:08):
latest publisher does seem to work for this issue.
Last updated: Apr 12 2022 at 19:14 UTC