Stream: IG creation
Topic: slicing across resource boundaries with resolve()
Rob Hausam (Jul 29 2019 at 03:29):
I think I (and others) have asked this question before, but it's been a while. Has anyone done this successfully? And, if so, is there somewhere to point to or share to show the way (best or only) that it can be done? I've tried on a number of occasions before but haven't gotten quite far enough to be successful. I keep coming back occasionally thinking that new versions of the validator and IG Publisher may help, but I'm not discovering it so far. Ideally, I would like to be able to slice Composition.section.entry across the resource boundary, either discriminating on profile or alternatively a fixed value of meta.profile on the entry resource, but any actually working and verifiable example of slicing using resolve() would be great to have a look at.
Michel Rutten (Jul 29 2019 at 08:48):
Hi @Rob Hausam, the validator in the .NET FHIR library does not yet support slicing by profile. However our team is about to start working on this right now.
Rob Hausam (Jul 29 2019 at 14:11):
Thanks, @Michel Rutten. That will be great to have when it's ready. I assume that it's correct that the use of resolve() shouldn't only be limited to slicing on profile? I've also tried to make it work with slicing by value on meta.profile of the referenced resource, but so far I haven't been able to get that to work, either.
Grahame Grieve (Jul 30 2019 at 06:32):
this should work next release
Grahame Grieve (Jul 30 2019 at 06:51):
and if you want to see an example, look in the validation tests at
- validation-examples\profile-slicing-profile-open.xml
- validation-examples\profile-slicing-bad-1.xml
- validation-examples\profile-slicing-ok-1.xml
Michel Rutten (Jul 30 2019 at 08:26):
Hi @Rob Hausam, resolve() should be supported in all contexts, but in practice I guess it depends on the actual FHIRPath engine implementation. Slicing on the value of meta.profile should be broadly supported by most implementations. However this requires all instances to be tagged correctly, so validation results are only reliable if you can guarantee this.
Rob Hausam (Jul 30 2019 at 13:27):
That's what I thought, @Michel Rutten. But I haven't been able to get it to work for properly tagged resources that are referenced in Composition.section.entry.
Michel Rutten (Jul 30 2019 at 13:47):
Hmm, the alternative approach should be supported... probably implementation bugs/limitations?
Rob Hausam (Jul 30 2019 at 13:58):
Yes, I'm assuming so (if it's not all user error!). But I'm not finding it too easy to get a clear idea of what actually is implemented and working.
Michel Rutten (Jul 30 2019 at 14:13):
The .NET library/tools should support slicing on the value of meta.profile. Not sure about the Java stack.
Rob Hausam (Jul 30 2019 at 14:23):
Yeah, I'm wondering if the Java stack is behind here. But that's what we have with IG Publisher.
Last updated: Apr 12 2022 at 19:14 UTC
