Stream: implementers
Topic: DocumentManifest vs Bundle
Maria Hu (Jul 23 2020 at 18:29):
If DocumentManifest is used to gather a list of resources, does that mean there's no need to use resourceBundle? Pls advise, thanks
David Pyke (Jul 23 2020 at 18:35):
They have very different use cases. Bundle is the primary method of bundling resources. Typically, DocumentManifest resources are used in document indexing systems, such as IHE XDS
Lloyd McKenzie (Jul 23 2020 at 19:06):
Bundle has no 'meaning'. It's just a mechanism to send multiple things at once. The 'meaning' between a collection of resources is conveyed by relationships between resources (DocumentManifest, List, Composition, etc.) None of those resources actually 'contains' other resources - they just point to the ones they have a relationship with.
Maria Hu (Jul 23 2020 at 19:38):
David Pyke said:
They have very different use cases. Bundle is the primary method of bundling resources. Typically, DocumentManifest resources are used in document indexing systems, such as IHE XDS
thanks David !
Maria Hu (Jul 23 2020 at 19:43):
Lloyd McKenzie said:
Bundle has no 'meaning'. It's just a mechanism to send multiple things at once. The 'meaning' between a collection of resources is conveyed by relationships between resources (DocumentManifest, List, Composition, etc.) None of those resources actually 'contains' other resources - they just point to the ones they have a relationship with.
Thanks Lloyd.
Actually my objective is to capture some meta data about a bundle of resources, can't really use meta.tags because they are elements with corresponding value, not code. Am looking for a simple resource to capture these miscellaneous (yet useful) info, any suggestions? Thanks
David Pyke (Jul 23 2020 at 19:58):
List is the simplest and most flexible for information about a Bundle of resources. It might be worthwhile to see if it fits your use case
Maria Hu (Jul 23 2020 at 20:02):
David Pyke said:
List is the simplest and most flexible for information about a Bundle of resources. It might be worthwhile to see if it fits your use case
thanks David, looking at it now.
Lloyd McKenzie (Jul 23 2020 at 22:00):
You can't presume that resources will be accompanied by their Bundle or their List (or any other referencing resource). If you have metadata that's important for someone looking at a resource to know, then it needs to be specified directly on the resource - even if it means repeating identical information on hundreds of resources. If the metadata is only relevant to the 'collection' but not to the individual resources, then putting it on something like List makes sense. Metadata on Bundle would be specific to a particular delivery package. For most types of Bundles, it wouldn't necessarily be retained once the Bundle had been received and processed (message, batch, transaction).
John Moehrke (Jul 23 2020 at 22:01):
IHE will likely be moving to List and away from DocumentManifest. This recognizing that List is more likely to be supported by many use-cases and that will drive it to be Normative, where as DocumentManafest has been misunderstood and thus used by no-one. This has not been formally agreed to, but this is the model I am driving in both camps.
Thus I am proposing a new element be added to List to enable the clinical purpose of the list, and the kind of list (manifest being one kind).
John Moehrke (Jul 23 2020 at 22:07):
I see that my request has been rejected FHIR-19821. I recommend someone else explain the need for a kind of List in addition to a clinical code for that kind of list.
Jean Duteau (Jul 23 2020 at 22:10):
@John Moehrke I just looked at your two issues and it doesn't seem like they rejected them. 19821 was said to be a duplicate of 19822. IN 19822 the agreed to make List.code 0..* and they defined a core extension for category which can be used for your list type
John Moehrke (Jul 23 2020 at 22:15):
except the other one was to move .code to 0..*; which they rejected
John Moehrke (Jul 23 2020 at 22:15):
so when I have many clincial purposes for the List, but ONE type of list... what do I do? Use .code for the type of list (manifest) and use the extension for the clinical purpose?
Jean Duteau (Jul 23 2020 at 22:16):
ah, you are right. i misread the resolution. I saw the "Persuasive with mod". That to me says that the were going to make List.code 0..* as well as the additional extension.
Jean Duteau (Jul 23 2020 at 22:16):
If they intended to not make code 0..*, that should have been Not Persuasive with mod.
John Moehrke (Jul 23 2020 at 22:16):
yup
John Moehrke (Jul 23 2020 at 22:17):
and none of this has been applied, so it is hard to guess how the editor will intepret a CR that is 6 months since the resolution
Lin Zhang (Nov 18 2020 at 11:41):
A helpful post:blush:
Last updated: Apr 12 2022 at 19:14 UTC
