FHIR Provenance vs AuditEvent: GxP Traceability Matrix
FHIR Provenance vs AuditEvent: GxP Traceability Matrix | IntuitionLabs
Summary
FHIR offers two distinct resources for traceability: Provenance and AuditEvent. Provenance tracks how a resource version came into existence (activities, agents, sources), while AuditEvent records operational and security events (actors, entities, outcomes). Understanding this distinction is critical for GxP compliance and system validation.
Details
This report provides a decision aid for FHIR architects and security teams, clarifying the distinct roles of Provenance and AuditEvent. Provenance asserts the 'origin story' of a resource version (e.g., creation, update, deletion), while AuditEvent focuses on recording operational and security events—the 'who did what' to the system. This distinction is vital not only for technical architecture but also for meeting regulatory requirements like 21 CFR Part 11 and EU Annex 11, which mandate reliable electronic records and secure audit trails. System validation must measure event coverage, versioned-reference resolution, and cross-system correlation, emphasizing that relying on a single resource is insufficient for compliance.
Original content copyright by respective publishers