Stream: conformance
Topic: Include existing resource in bundle
ryan moehrke (Apr 23 2021 at 14:35):
while there is a requirement that in a non-history bundle all full urls SHALL be unique, for any includes searches on a reference that points to the same fhir resource (ex. Location.partOf) there's a legitimate reason why one resource could be included twice (in the search parameters and referenced by a resource in the search parameters) what's the best way to resolve this? exclude the mode:include version? exclude the mode:match version? have both entries and just have a non-conformant bundle?
I would think just exclude the mode:include version because the reference is already resolvable in-bundle, but I'm not sure I'm considering all of the nuance.
Lloyd McKenzie (Apr 23 2021 at 16:08):
Can you raise a tracker item on this? At minimum, we need to provide clarification around expected behavior.
ryan moehrke (Apr 26 2021 at 15:30):
Last updated: Apr 12 2022 at 19:14 UTC
