HealthRecordCommunity
FHIR🌏 TaiwanEnriched

FHIR AuditEvent/Provenance Resource Preview Added: Towards Standardized Audit Trails

Day25 - Request-Scoped FHIR AuditEvent / Provenance Resource Preview - iT 邦幫忙

August 26, 2026

Summary

The article details the integration of FHIR R4 compliant AuditEvent and Provenance resource JSON previews into the Quality Test Report. This allows systems to demonstrate readiness for future persistent audit logging or external FHIR repository integration.

Details

Previously, evidence in the Quality Test Report was provided only as text. Now, a more structured data format is introduced: a Request-Scoped FHIR R4 AuditEvent and Provenance resource JSON preview. The goal is to move beyond merely claiming 'auditability' to demonstrating that the system can provide audit trails using a minimal 'resource shape.' The report now records validation actions, input SHA-256 hashes, gate outcomes, and the status of various readiness layers. Crucially, this feature does not imply writing persistent audit logs or submitting data to an external FHIR server; it focuses on providing a highly portable 'preview.' This establishes a foundation for developers to build future full audit workflows (e.g., operator ID, OAuth scope management). Technically, the system uses the HAPI FHIR R4 model to generate AuditEvent and Provenance objects, which are then displayed as JSON previews. For privacy, raw patient data or Bundle JSON is avoided; only the SHA-256 hash of the input data is referenced. This enhances interoperability by providing a standardized, machine-readable representation of system activity evidence.

πŸ“°
Read Original Article
ithelp.ithome.com.tw
β†’

Original content copyright by respective publishers