The profile's synthesized-accessor contract: fields TypedFhir surfaces as first-class typed properties, each computed from the instance by a restricted FHIRPath expression. See Salient Fields for what they are, how they shape LLM contexts, and how to declare them.
Indicator for type of action performed during the event that generated the audit.
Comments
The interaction performed, as R4's audit-event-action codes. See the element note: the platform records a transmission action that these five codes do not express.
Present only when the outcome is known. An entry recording an outcome the platform could not determine carries no code at all -- treat absence as unknown, never as success.
When the entry was recorded, falling back from the activity period where one is given. Not necessarily the instant of the interaction -- see the recorded note.
The opaque account identifier the identity provider issues for the acting user (for example
auth0|abc123). This is the identity the platform actually holds on every entry, and it is the
element to match on when correlating an audit entry with the meta-updated-by extension on a
resource version -- the two carry the same kind of value for the same reason.
NOT a FHIR id and NOT a Practitioner reference. Resolving it to a person needs the identity
directory, which this guide does not describe.
Comments
The identity-provider subject of the acting user, as the platform holds it. An opaque account identifier, not a FHIR id and not a Practitioner reference. Resolving it to a person needs the identity directory, which this guide does not describe.