Stream: implementers
Topic: AuditEvent specific procedure
Joel Francis (Jan 07 2020 at 16:39):
How is the AuditEvent intended to capture specific procedures that have been ordered?
AuditEvent.type captures a high level "Procedure Record" but how is specificity applied to the AuditEvent. Ex: Procedure was a "Chest CT". Can the SNOMED code for this be added to the AuditEvent.subtype?
Thanks,
Joel
@Alex Goel
Lloyd McKenzie (Jan 07 2020 at 16:48):
The audit event reflects what action was done (Procedure instance created). The details of the record that was created would be in the history of the Procedure instance, not in the audit record. (Because you might well care about any piece of information that was in the procedure record.)
John Moehrke (Jan 07 2020 at 17:20):
Lloyd explained the most basic of AuditEvent, as outlined http://build.fhir.org/auditevent.html#6.4.4.4
However, yes you can record more detail. Typically the AuditEvent.entity can carry more specific codes like the SNOMED code for "Chest CT". This said, I would recommend against overly duplicating clinical or personal information in the AuditEvent. The AuditEvent should leverage references and identifiers to the resource/object that was created or updated. The AuditEvent is not intended to duplicate that information.
Last updated: Apr 12 2022 at 19:14 UTC
