Stream: implementers
Topic: reference to contained resource
Shamil Nizamov (Feb 01 2019 at 16:31):
What would be a proper link to reference to a contained resource across resource boundaries within the transaction Bundle. Both top level resources are presented only once (i.e., there is a single instance of that resource type in the Bundle). The sample in 2.4.0.5 is misleading.
reference=[type]/#a1
or
reference= [type]/[id]#a1
Lloyd McKenzie (Feb 01 2019 at 16:35):
You can't link to contained resources except by the linking resource. If they have an identity that allows external linkages, they shouldn't be contained.
Shamil Nizamov (Feb 01 2019 at 16:44):
If it's possible to reference to the narrative across resource boundaries in the Bundle (see the sample in 2.4.0.5), why it's not possible to reference to a contained resource in the similar way?
Grahame Grieve (Feb 01 2019 at 19:54):
reference= [type]/[id]#a1 is legal
Brian Postlethwaite (Feb 03 2019 at 22:49):
Really? I need to go recheck that for myself. That would break a few assumptions in my code.
Brian Postlethwaite (Feb 03 2019 at 22:52):
The regex on that property doesn't support that.
Brian Postlethwaite (Feb 03 2019 at 23:01):
I can't spot anywhere in http://build.fhir.org/references.html#literal that mensions the contained reference as valid after the resource id.
Lloyd McKenzie (Feb 04 2019 at 03:59):
I don't remember us agreeing to allow it - and it sort of breaks the notion of what a 'contained' resource is.
Last updated: Apr 12 2022 at 19:14 UTC
