What problem does it solve? Developers working on the Helios FHIR Server need to emit compliant audit trails for FHIR interactions, but configuring the helios-audit crate involves understanding IHE BALP profiles, multiple sink backends, and HFS_AUDIT_* environment variables. This Skill provides the operational knowledge to implement and configure audit logging correctly. ## Core Features & Use Cases - BALP AuditEvent Emission: Generate FHIR R4-family AuditEvent records following IHE BALP profiles for request/response activity, with R5/R6 builds aliasing to the R4B baseline. - Pluggable Sink Backends: Route audit events to file (NDJSON), SQL/MongoDB databases, or AWS CloudWatch Logs via the HFS_AUDIT_BACKEND setting. - Path Exclusion & Source Configuration: Skip noisy endpoints like /health and /metadata, and customize AuditEvent.source.observer references. - Use Case: You need HIPAA-style audit trails for a production FHIR server. Enable the database sink with HFS_AUDIT_DATABASE_URL, exclude health-check paths, and every FHIR interaction is recorded as a BALP-compliant AuditEvent. ## Quick Start Ask the AI to enable audit logging in helios-audit with the file sink and exclude the /health and /metadata paths.