To keep everyone informed of a recent conversation @sashrika and I had.
Lets say that you’re using FHIR to update an obs. A client sends a POST that basically reads, “Update Obs identified by UUID XYZ”. As you know, the OpenMRS API will do this by creating a brand new obs, and giving it a new UUID. And so, if the same client were to try and retrieve it using the UUID that they know of (XYZ), they won’t be able to obtain the newest info.
My recommendation is that we ensure that FHIR returns the uuid of the new object as part of the response sent to the client whenever he creates or updates any resource. The uuid can be returned as part of the MethodOutcome and thus, the client will be aware of the newly updated resource.