Stream: fhir/documents
Topic: Transform FHIR-Document into a FHIR Transaction
René Spronk (Jun 18 2018 at 21:01):
After the previous DevDays in Amsterdam I provided the following comment to Rick after his FHIR documents presentation. I came across this comment today; what issues/benefits do you see in transforming a FHIR-doc into a FHIR transaction?
One thing struck me as something that I'd like to follow up on: the transformation of a FHIR document to a transaction. In our FHIR training courses we discuss the posting of FHIR docs to /Binary, to / etc., but not a mapping to a transaction.
Presumably the added value of that would be the fact that a document may be a lot older (and thus contain older versions of data) than data already known to a recieving application. Transactions support conditional updates, so that would allow a way of dealing with this. What do you see as the major advantage of such an approach? This would be a client-side (or middleware on behalf of the client) transform, so it fits with a restful way of thinking.
One could also argue that we need a server side $process-document operation which would take the data from the document, selects whatever is new and relevant, and imports it into a database.
Last updated: Apr 12 2022 at 19:14 UTC
