Stream: IG creation
Topic: Multiple resource options in a resource slice
David Pyke (Sep 08 2020 at 14:22):
I'm creating a bundle with slicing based on the resource entry. It's ordered. The second entry of the slices needs to be one of a selection of 4 possible profiles. That's illegal to do, in slicing on type and resource. Is there a way to actually do this?
Grahame Grieve (Sep 08 2020 at 20:51):
I think, if I understand correctly, it's not that what you are trying to do is illegal, it's just that you can't describe it with a discriminator
David Pyke (Sep 08 2020 at 23:15):
So, I have to have no discriminator, I can live with that, I guess
Grahame Grieve (Sep 08 2020 at 23:16):
it's not good for implementers. A different approach that's more explicit is easier for them
David Pyke (Sep 08 2020 at 23:18):
So I have a bundle design that requires a specific profile as entry 1, a selection of one of 4 for entry 2 and then a specific one for entry three. What would be a good way to do that?
Grahame Grieve (Sep 08 2020 at 23:19):
well, how will someone reading the bundle figure out which is which? Does they have to do bundle validation to figure it out? Or is there some code they can look at to figure it out?
David Pyke (Sep 08 2020 at 23:20):
The IG defines what needs to be done, I was just hoping to make it forced, but really, I guess I don't need to force it by constraint
Lloyd McKenzie (Sep 09 2020 at 00:22):
Is there a reason the Bundle needs to be ordered? Traditionally we dictate the first resource but don't care about the order of the rest. We've agreed to add slicing by order in R5, which will help.
David Pyke (Sep 09 2020 at 00:23):
I guess not, as long as the first is there and the rest are included, it can be processed correctly
Last updated: Apr 12 2022 at 19:14 UTC
