Stream: implementers
Topic: Composition $document operation
Jorn Duwel (Mar 16 2022 at 12:14):
When looking at https://hl7.org/fhir/composition-operation-document.html
You could read the OperationDefinition as allowing a client to GET [base]/Composition/$document (without [id] and without ?id=), an thus retrieving all available Compositions and referenced resources in 1 document Bundle. Would this be allowed?
Lloyd McKenzie (Mar 16 2022 at 13:59):
@Rick Geimer
Jorn Duwel (Mar 28 2022 at 14:31):
@Alexander Henket asked my to tag @Sean McIlvenna to perhaps look at this. Otherwise my resort would be to file a ticket at the Structured Documents Working Group.
Perhaps some background information: we have a use case where data is converted to FHIR, where a call of "give me all 'indicatiebesluiten'" to the database is executed, which would be all Compositions and their referenced resources - which are separate requests in FHIR as I understand it (searching GET [base]/Composition and then $document on each of the search result resources). These separate request would require the FHIR facade to store all results until the $document request has been made.
The $document operation isn't clear on if it is allowed to do GET [base]/Composition/$document (without any [id]) and what the result would look like. The text of the operation does say "Note that since this is a search operation, the document bundle is wrapped inside the search bundle" - which would indicatie that a searchset Bundle containing document Bundles is an option, but as the phrasing is singular it is not clear in which situation this quote applies.
The alternative for us would be defining a custom operation which bundles the FHIR requests into one call.
Last updated: Apr 12 2022 at 19:14 UTC
