Stream: implementers
Topic: Patient resource
Sirisha Rao (Mar 02 2022 at 11:51):
How can i map patient created by and datetime, updated by and datetime, merged by and reason to FHIR resources?
Sirisha Rao (Mar 02 2022 at 11:53):
@Lloyd McKenzie Can you suggest something here?
Michele Mottini (Mar 02 2022 at 15:46):
Those go into Provenance
Sirisha Rao (Mar 02 2022 at 17:49):
@Michele Mottini How different is AuditEvent from Provenance?
David Pyke (Mar 02 2022 at 17:56):
AuditEvent is a record held in the Audit system and is a record of access, etc. Provenance is a record of change/history that accompanies a Resource
John Moehrke (Mar 02 2022 at 18:01):
Here is the scope text from the FHIR core for Provenance
The Provenance resource tracks information about the activity that created, revised, deleted, or signed a version of a resource, describing the entities and agents involved. This information can be used to form assessments about its quality, reliability, trustworthiness, or to provide pointers for where to go to further investigate the origins of the resource and the information in it.
Provenance resources are a record-keeping assertion that gathers information about the context in which the information in a resource was obtained. Provenance resources are prepared by the application that initiates the create/update etc. of the resource. An AuditEvent resource contains overlapping information, but is created as events occur, to track and audit the events. AuditEvent resources are often (though not exclusively) created by the application responding to the read/query/create/update/etc. event.
John Moehrke (Mar 02 2022 at 18:02):
Not going to copy the AuditEvent definition -- but to add that AuditEvent is usable for events well beyond those recorded in Provenance. including workflow steps, security activities, privacy activities, etc -- http://build.fhir.org/auditevent.html#bnc
Last updated: Apr 12 2022 at 19:14 UTC
