Stream: implementers
Topic: Bundle endpoint
Jeremy Chapman (Sep 30 2019 at 17:58):
If I am using a bundle for a transaction does the endpoint need to be /Bundle or can it be anything? It would be easier for us to manage multiple endpoints for different types of transactions.
Michele Mottini (Sep 30 2019 at 18:05):
For a transaction the end point is the root, not /Bundle
Alexander Kiel (Sep 30 2019 at 18:36):
Right, it's always the base URL of the FHIR RESTful API as documented here.
Lloyd McKenzie (Sep 30 2019 at 23:24):
Generic FHIR systems won't have any notion of 'types' of transactions - a transaction is a transaction is a transaction. If you need distinct behavior, then you might need custom operations.
Jeremy Chapman (Oct 01 2019 at 21:40):
with transactions that do have behaviors, how do you account for a microservices architecture where you would have multiple services (endpoints) in a given system?
James Agnew (Oct 01 2019 at 23:52):
are you referring specifically to FHIR transactions: http://hl7.org/fhir/http.html#transaction
In that case, they have a fully specified set of behaviors and they have to happen at the root of the server whether they are in a MSA or any other setup.
If you just mean an operation you defined that happens to have transactional (in the DB sense, not the FHIR sense), you have more options in terms of what the URL will be, but it does have to follow the FHIR rules for naming operations. I.e. [baseUrl]/Bundle/$process-my-transaction would be acceptable.
Last updated: Apr 12 2022 at 19:14 UTC
