Stream: implementers
Topic: History of device settings/properties
Michael Ilewicz (Feb 12 2021 at 16:25):
Hi, we would like to track the history of our device properties and I was wondering what the best way to do it would be.
Scenario: we have a Device D with properties A,B,C. The provider now adjusts the settings A and B which is sent to the server (maybe as a Message? or as Observation?).
The Message could have a reference to a DeviceMetric describing A/B and through an Operation (Is this the right concept? still a little new...) the content of the message would be used to apply the new setting to the Device.Property. The message could then be stored for later data analysis.
However, we are likely to have many different types of messages so I was wondering whether there would be a better way of storing that information?
I would really appreciate some clarification on this. Thank you.
Lloyd McKenzie (Feb 12 2021 at 16:46):
Ideally, you wouldn't use messaging, you'd use PATCH. The server would also retain the history of the resource and have a Provenance instance of each change, so you could go back and see what had happened, who had done it and why.
Michael Ilewicz (Feb 12 2021 at 16:57):
I see that makes a lot of sense, Thank you. Could you give me a hint on how the reason for the change and the person behind it can be identified? I can't see that from https://www.hl7.org/fhir/fhirpatch.html
Lloyd McKenzie (Feb 12 2021 at 17:02):
The person would typically be handled by the authorization of the user performing the change. If you need to capture reason, you'd have to convey Provenance in the header alongside the PATCH. (See https://build.fhir.org/provenance.html#header)
Last updated: Apr 12 2022 at 19:14 UTC
