Stream: Orders and Observation WG
Topic: Canceled Order Extra Data
Jorge Yero (Feb 12 2019 at 17:32):
I can set ServiceRequest status at cancelled but I want to storage extra data like date and user who canceled the Order.
Where can I storage that info?
Lloyd McKenzie (Feb 12 2019 at 17:38):
Take a look at Provenance. It lets you capture metadata about who did something, where they did it, why, when, under whose authorization, etc.
Jorge Yero (Feb 12 2019 at 18:02):
Thanks, it is exactly I was looking for.
Yassiel Oliva (Mar 07 2019 at 18:25):
@Lloyd McKenzie we are wondering now about the difference betweenProvenance and AuditEvent. We aren't clear about where to put the information related to an order cancellation.
Lloyd McKenzie (Mar 07 2019 at 18:55):
Provenance is a record intended to be seen by clinicians and other users. It describes how a particular resource version came to be - who created it, when, where, why, what sources were drawn from and what "action" occurred to create the instance (e.g. anonymization, error correction, etc.) Provenance records are only created when data is changed.
AuditEvent is used to track system actions. That includes the creation, update and delete of records (which should also have Provenance instances associated), but it also includes queries, backups, restores, logins, password changes and all sorts of other things that could be relevant when tracking the behavior of a system to allow subsequent audit of use.
The short answer to your question is that both types of records should exist, but the user-facing data will be in Provenance.
Yassiel Oliva (Mar 07 2019 at 19:25):
thanks!
Last updated: Apr 12 2022 at 19:14 UTC
