FHIR Chat · list of documents · implementers

Stream: implementers

Topic: list of documents


view this post on Zulip frank cao (Nov 20 2018 at 18:45):

Hi all,
We have a use case to retrieve a list of discharge summary documents from a clinical repository. The documents will be pre-assembled in CDA format (likely level 1 only) before being converted to FHIR. While reading the documents page, it's not clear to me if documents must be represented using Bundle. So my question is "is it FHIR conformant to use a list of Composition resource for a list of documents"? If so, is there any implication to support submitting documents to the repository in this manner? Thank you!

view this post on Zulip Lloyd McKenzie (Nov 20 2018 at 19:00):

A FHIR document must be a Bundle whose first entry is a Composition. However, you might find it useful to have your list be a collection of DocumentReference instances that provide metadata and point to the documents rather than the documents themselves

view this post on Zulip frank cao (Nov 21 2018 at 17:15):

Thank you Lloyd. If I want to query for a list of documents of a certain type, can I use search on Composition and return a bundle of Bundles? In the bundle, each entry may be either a document bundle or a documentReference.

view this post on Zulip John Moehrke (Nov 21 2018 at 17:25):

The more general solution is to use DocumentReference. More general in that it can support ANY kind of document format, including CDA and FHIR document. Once you have everything in FHIR Document form, there is still an opportunity to use DocumentReference as the single method of getting the metadata alone, and also to get link to a seralized instance of the Composition. I think this does require that anyone creating a Composition, to determine when they are done assembling the first version, seralize it into a Bundle (to make it a formal document), and referencing that with a DocumentReference. Note the DocumentReference can also have a direct pointer to the Composition in addition to the attachment of the seralized bundle. There is not an obvious place in DocuentReference for this direct pointer to Composition, I guess this should be clarified. Else it would today be able to be in DocumentReference.context.related

view this post on Zulip John Moehrke (Nov 21 2018 at 17:25):

all good things to discover during this STU phase...

view this post on Zulip Yunwei Wang (Nov 21 2018 at 17:53):

Depends on if you use Bundle or DocumentReference:
GET [base]/bundle?composition.type=xxxx, or
GET [base]/documentReference.type=xxx


Last updated: Apr 12 2022 at 19:14 UTC