Client setting lastUpdated

[John Moehrke]

Is it possible to have the .meta.lastUpdated preserved from that set by the client update? It seems that HAPI always puts in current time when an update happens. I have a case where I need to set historic data, and want to use the .meta.lastUpdated as the historic last updated date/time.

John Moehrke 🔥 Architect: Healthcare Informatics Standards - Interoperability, Privacy, and Security
IHE Co-Chair IT Infrastructure Planning and Technical
HL7 Co-Chair Security WG, FHIR FMG, FHIR facilitator, and FHIR Foundation founding member

Employee of By Light -- Contractor to VHA MyHealtheVet
JohnM...@gmail.com  |  M +1 920-564-2067  |  John.M...@bylight.com
 https://healthcaresecprivacy.blogspot.com

[G G (Tadgh)]

Hello John, you can rewrite history by enabling history rewriting, but there is no way to modify the `_lastUpdated` field via a client, even when rewriting history. That is server-controlled, and represents the time the operation that modified the resource occurred. The spec indicates that "The server / resource manager sets this value; what a client provides is irrelevant." You are free to implement a Provider and repository which contravenes the spec, but HAPI-FHIR provides no such mechanism.

Cheers,

--Gary