Stream: implementers
Topic: Bundle Type - Transaction or Document?
Inderpal Singh (Nov 08 2021 at 19:01):
Hello All,
For my use case, I'm interested in collecting an organization's patient data for 2 purposes, 1) Analytics and Reporting (short term) 2) Potentially the provision of care (long term goal).
We're planning to receive 1 bundle containing Patient, Service Request and Organization resources at a minimum, each bundle should contain data for 1 and only 1 patient. Updates will contain the same 3 resources at listed at a minimum, and optionally additional resources including Episode Of Care, Health Care Program, Encounter, Appointment, and Observation. Currently, there is no need to capture an Attester, Author, and other details contained in a document. My question is - could the above use case be supported using a Bundle Resource with Type - Transaction, with slices on Bundle.entry on the 3 required resources (making Cardinality 1..1 on Patient, ServiceRequest, Organization)? Or is a Bundle Type of Transaction not meant for the purposes outlined here. Is there a benefit to using the Composition resource for this type of scenario?
Thanks!
Vassil Peytchev (Nov 08 2021 at 20:23):
We're planning to receive 1 bundle
This needs further clarification. Does it mean:
- your application is going to execute a search , and the response bundle needs to meet your requirements
or
- your application is going to execute a custom operation, and the result of the operation needs to meet your requirements
or
- the source of the information will be configured to post the information to your server when a particular event occurs, and the bundle to be posted needs to meet your requirements
or
- you are planning to use FHIR messaging, and the bundle of type message needs to meet your requirements
Have you considered these options?
Inderpal Singh (Nov 08 2021 at 20:32):
Vassil Peytchev said:
We're planning to receive 1 bundle
This needs further clarification. Does it mean:
- the source of the information will be configured to post the information to your server when a particular event occurs, and the bundle to be posted needs to meet your requirements
Have you considered these options?
Hi Vassil,
Thanks for responding.
This options is the closest to what we're trying to achieve:
"* the source of the information will be configured to post the information to your server when a particular event occurs, and the bundle to be posted needs to meet your requirements"
The source will be configured to post a new bundle (for new patients), or update an existing bundle based on search criteria (using conditional update) ideally when a new event occurs (they will hold the data until end of day and send us nightly). The posted bundle will need to meet our conformance requirements.
Lloyd McKenzie (Nov 15 2021 at 03:21):
If you're wanting to comply with the FHIR specification, then you'd need to either use FHIR messaging or a custom operation. Note that both of these will require custom configuration of your communication partners and won't let you leverage things like SMART on FHIR or CDS Hooks or anything else that relies on having a RESTful FHIR server.
Last updated: Apr 12 2022 at 19:14 UTC
