Read a bit into the fhir-router code and not 100% sure about the atomic guarantees that it currently offers with Bundle transaction. The transactional nature may or may not be an issue for your use case but thought I'd share. cc: @node

Hi @rahul1 — just to check, is transaction support coming by end of March, judging by what I'm reading in the Github threads?

Hi @jasonwa.ng , that is our target but we still have some customers relying on the legacy behavior. We'll be somewhat rate-limited by their ability to switch over

Great — would appreciate updates if there are any! Thank you 🙏

Hi @rahul1 and @reshma , has the atomic behavior already been shipped? Also curious about whether there is a way to specify temporary ids for other resources in the transaction so resources can link to each other that are being created in the same transaction (eg, create a Patient and a QuestionnaireResponse with the new Patient as the subject of the QR)

@codeclayman checkout the doc for 'creating internal references' https://www.medplum.com/docs/fhir-datastore/fhir-batch-requests#creating-internal-references And I believe this is the WIP PR for transaction support https://github.com/medplum/medplum/pull/4358

@codeclayman - yes there is. This was recently released, though we are still working on the documentation for it. https://github.com/medplum/medplum/pull/4633 cc: @medplummatt