AuditEvent Profile¶
| Canonical | ../StructureDefinition/nexus-emr-core-auditevent |
|---|---|
| Status | draft (experimental) · 1.26.0 |
| Base | AuditEvent (constraint) |
| Source | FSH · JSON |
Nexus EMR profile for AuditEvent -- the access and activity log: who acted, on which record, when, through what interaction, and with what outcome.
Access
What the endpoint offers¶
AuditEvent is modelled by this IG but is not offered as an API surface.
No capability statement in this IG names AuditEvent, so there are no interactions and no search parameters declared for it. This IG publishes Server Capability Statement; profiling a resource and offering it are two different decisions, and each statement's own description says which types it covers and which it deliberately leaves out.
SMART on FHIR scopes¶
A SMART on FHIR app cannot reach AuditEvent.
This is the default, not an omission. A resource is unreachable unless its profile declares smart-exposed, because profiling a resource and exposing it to a third-party app are two different decisions: the first is modelling, the second is authorization. No scope naming AuditEvent will be granted, and a wildcard scope (patient/*.rs) does not expand over it.