Stream: implementers
Topic: Reason for change
Calum Turner (Mar 17 2021 at 15:25):
Hello, I have received a requirement to store the reason a particular Resource has been updated and by whom. I have seen the AuditEvent exists and can be used to modal rest events. Does it make sense that a downstream service that collects the data from the user, sends the updated resource and an AuditEvent detailing what has changed and who changed it? Is there an appropriate way to link the resource to the AuditEvent?
Many thanks
Lloyd McKenzie (Mar 17 2021 at 15:57):
Typically you'd share Provenance, not AuditEvent. The former captures much of the same information.
Calum Turner (Mar 17 2021 at 16:19):
Perfect thank you!
Calum Turner (Mar 17 2021 at 17:04):
In case anyone else looks into this, I found that you can set a custom header on when performing a PUT or POST operation that provides the provenance: https://www.hl7.org/fhir/provenance.html#header
Last updated: Apr 12 2022 at 19:14 UTC
