Stream: dotnet
Topic: Contained resources
Kirt Noel (Nov 01 2019 at 19:55):
Hello,
Using the API, I've successfully created message bundles that have DocumentReference focus. It makes reference to other resources residing alongside it in the message bundle (eg. the subject, author, organization).
I'm inclined to define the resources referenced by the DocumentReference as contained references rather than to adjacent resources within the Bundle. It is not evident how one goes about building a contained reference for the author or subject using the .NET API. Can anyone provide some guidance or point me in the right direction?
Also, does anyone have any thoughts on whether it is preferable to keep referenced resources at the outer/top level of the bundle rather than encapsulate them deeper within the bundle (ie. within the DocumentReference resource)?
Thanks,
Kirt
Michele Mottini (Nov 01 2019 at 20:37):
Add the contained resources to the Contained list with some arbitrary ids, and then reference them as #[id]
Michele Mottini (Nov 01 2019 at 20:38):
I won't use contained though - it is more likely not to be supported by servers
Michele Mottini (Nov 01 2019 at 20:38):
(our mostly does not support them for example)
Kevin Mayfield (Nov 02 2019 at 12:22):
If you want a lite resource then it can be contained. If it's a complete resource then it shouldn't.
I used to make use of them to record identifiers but you can now do that within the reference.
Vadim Peretokin (Nov 04 2019 at 09:10):
If you don't want it to be searchable, then it can be contained. The spec recommends it's use as a last resort if you can't identify the resource uniquely
Last updated: Apr 12 2022 at 19:14 UTC
