Basic Audit Log Patterns (BALP)
1.1.4-current - ci-build
Basic Audit Log Patterns (BALP), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.1.4-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.BasicAudit/ and changes regularly. See the Directory of published versions
In general, IHE Profiles should have “Security Considerations” sections in both Volume 1 and in Volume 2. In Volume 2, the Security Considerations section should have a definition of how the AuditEvent is filled out when the given transaction happens. This definition usually includes one specification of an AuditEvent to be created by each of the actors involved in the transaction.
All of the AuditEvent (AuditMessage) encodings can be found on Gazelle AuditTrail section. These specifications usually use a table format. These are in the format of DICOM AuditMessage, but the mapping to FHIR AuditEvent is defined in the FHIR AuditEvent mapping to DICOM.
Some of the IHE Profiles are being converted to using the IG Publisher. When this is done, the AuditEvent is “profiled” using the FHIR StructureDefinition and Examples are provided for each.
The MHD Implementation Guide has the following AuditEvent profiles:
MHD open issue to align AuditEvents with BasicAudit
The PDQm Implementation Guide has the following AuditEvent profiles:
PDQm open issue to align AuditEvents with BasicAudit
The PIXm Implementation Guide has the following AuditEvent profiles: