Stream: implementers
Topic: FHIR metadata for updates
Brian Reinhold (Jun 07 2017 at 20:18):
This is kind of an academic question, but if I do an update transaction twice with exactly the same resource, will the versionId change? I assume the lastUpdated will change even if the content is identical.
Lloyd McKenzie (Jun 07 2017 at 20:23):
Most servers would do that, though I don't think a server has to do that. (Smart servers could theoretically accept the update and send back the etag from the prior event - though how audit, etc. would work, I'm not sure.)
Brian Reinhold (Jun 07 2017 at 20:27):
That is helpful. Its basically because I am trying to think of what is the simplest way to avoid data duplication should a filter fail.
For example, some Personal Health Devices are very bad about data management and will upload old data until it gets flushed out of the buffer by subsequent measurements. Conditional creates are one way to do that, but that is expensive and requires a well thought out set of selection criteria. Perhaps a simple update would suffice and be simplest for both server and client
John Moehrke (Jun 08 2017 at 13:06):
Audit should record all attempts, it could indicate which were ignored.
Grahame Grieve (Jun 08 2017 at 20:56):
see also https://chat.fhir.org/#narrow/stream/implementers/subject/HTTP.2C.20Idempotency.2C.20and.20FHIR
Last updated: Apr 12 2022 at 19:14 UTC
