FHIR AuditEvent resource creation

Hi @Rajat Singhal ,

Thanks for reaching out to Microsoft Q&A.

Azure’s managed FHIR service does not automatically create FHIR “AuditEvent” resources inside your FHIR store the way some on-prem servers do.

Instead it provides two audit-style mechanisms:

1. Azure resource AuditLogs:
   • Captures every call to the FHIR API (caller IP, URL, operation, status, etc.)
   • Exposed as Azure Monitor resource logs (category AuditLogs) that you can stream to Log Analytics, Event Hub, Storage, etc., via Diagnostic Settings https://learn.microsoft.com/azure/healthcare-apis/logging
2. Azure Health Data Services Events (Event Grid)
   • Optional feature that emits FhirResourceCreated / FhirResourceUpdated / FhirResourceDeleted (and Dicom events) to an Event Grid system topic
   • Good for change-data-capture scenarios; not the same as FHIR AuditEvent but lets you subscribe to CRUD events
   • Get started: https://docs.microsoft.com/azure/healthcare-apis/events/events-overview
   • Deployment guide: https://docs.microsoft.com/azure/healthcare-apis/events/events-deploy-portal

If you specifically need FHIR AuditEvent resources persisted in your FHIR store, you’d need to build a small pipeline for example, an Azure Function or Logic App that:

• Reads AuditLogs or Event Grid messages
• Transforms them into FHIR AuditEvent resources
• Writes them back into your FHIR service

Hope this helps!

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

I think azure fhir just can’t produce auditEvent; the engine has no hook for that path, so nothing shows up no matter the op u call. if it still won’t work, turn on portal→diagnostic settings→audit/resource logs and build only from whatever trace actually lands there.