Struct AuditEventInner 

pub struct AuditEventInner {

    pub id: Option<String>,
    pub meta: Option<Meta>,
    pub implicit_rules: Option<String>,
    pub language: Option<String>,
    pub text: Option<Narrative>,
    pub contained: Vec<Resource>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub category: Vec<Option<CodeableConcept>>,
    pub category_ext: Vec<Option<FieldExtension>>,
    pub code: CodeableConcept,
    pub code_ext: Option<FieldExtension>,
    pub action: Option<AuditEventAction>,
    pub action_ext: Option<FieldExtension>,
    pub severity: Option<AuditEventSeverity>,
    pub severity_ext: Option<FieldExtension>,
    pub occurred: Option<AuditEventOccurred>,
    pub occurred_ext: Option<AuditEventOccurredExtension>,
    pub recorded: Instant,
    pub recorded_ext: Option<FieldExtension>,
    pub outcome: Option<AuditEventOutcome>,
    pub outcome_ext: Option<FieldExtension>,
    pub authorization: Vec<Option<CodeableConcept>>,
    pub authorization_ext: Vec<Option<FieldExtension>>,
    pub based_on: Vec<Option<Reference>>,
    pub based_on_ext: Vec<Option<FieldExtension>>,
    pub patient: Option<Reference>,
    pub patient_ext: Option<FieldExtension>,
    pub encounter: Option<Reference>,
    pub encounter_ext: Option<FieldExtension>,
    pub agent: Vec<Option<AuditEventAgent>>,
    pub agent_ext: Vec<Option<FieldExtension>>,
    pub source: AuditEventSource,
    pub source_ext: Option<FieldExtension>,
    pub entity: Vec<Option<AuditEventEntity>>,
    pub entity_ext: Vec<Option<FieldExtension>>,
    /* private fields */
}

A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis.

AuditEvent v5.0.0

Record of an event

A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis.

Based on IHE-ATNA.

Fields

id: Option<String>

Logical id of this artifact

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

meta: Option<Meta>

Metadata about the resource

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

implicit_rules: Option<String>

A set of rules under which this content was created

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

language: Option<String>

Language; Language of the resource content

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

text: Option<Narrative>

Text summary of the resource, for human interpretation

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it “clinically safe” for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a “text blob” or where text is additionally entered raw or narrated and encoded information is added later.

contained: Vec<Resource>

Contained, inline Resources

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.

extension: Vec<Extension>

Additional content defined by implementations

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

modifier_extension: Vec<Extension>

Extensions that cannot be ignored

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

category: Vec<Option<CodeableConcept>>

AuditEventType; Type/identifier of event

Classification of the type of event.

category_ext: Vec<Option<FieldExtension>>

Extension field.

code: CodeableConcept

AuditEventSubType; Specific type of event

Describes what happened. The most specific code for the event.

code_ext: Option<FieldExtension>

Extension field.

action: Option<AuditEventAction>

AuditEventAction; Type of action performed during the event

Indicator for type of action performed during the event that generated the audit.

action_ext: Option<FieldExtension>

Extension field.

severity: Option<AuditEventSeverity>

AuditEventSeverity; emergency | alert | critical | error | warning | notice | informational | debug

Indicates and enables segmentation of various severity including debugging from critical.

ATNA will map this to the SYSLOG PRI element.

severity_ext: Option<FieldExtension>

Extension field.

occurred: Option<AuditEventOccurred>

When the activity occurred

The time or period during which the activity occurred.

The time or period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.

occurred_ext: Option<AuditEventOccurredExtension>

Extension field.

recorded: Instant

Time when the event was recorded

The time when the event was recorded.

In a distributed system, some sort of common time base (e.g. an NTP [RFC1305] server) is a good implementation tactic.

recorded_ext: Option<FieldExtension>

Extension field.

outcome: Option<AuditEventOutcome>

Whether the event succeeded or failed

Indicates whether the event succeeded or failed. A free text descripiton can be given in outcome.text.

In some cases a “success” may be partial, for example, an incomplete or interrupted transfer of a radiological study. For the purpose of establishing accountability, these distinctions are not relevant.

outcome_ext: Option<FieldExtension>

Extension field.

authorization: Vec<Option<CodeableConcept>>

AuditPurposeOfUse; Authorization related to the event

The authorization (e.g., PurposeOfUse) that was used during the event being recorded.

Use AuditEvent.agent.authorization when you know that it is specific to the agent, otherwise use AuditEvent.authorization. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.

authorization_ext: Vec<Option<FieldExtension>>

Extension field.

based_on: Vec<Option<Reference>>

Workflow authorization within which this event occurred

Allows tracing of authorizatino for the events and tracking whether proposals/recommendations were acted upon.

based_on_ext: Vec<Option<FieldExtension>>

Extension field.

patient: Option<Reference>

The patient is the subject of the data used/created/updated/deleted during the activity

The patient element is available to enable deterministic tracking of activities that involve the patient as the subject of the data used in an activity.

patient_ext: Option<FieldExtension>

Extension field.

encounter: Option<Reference>

Encounter within which this event occurred or which the event is tightly associated

This will typically be the encounter the event occurred, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission lab tests).

encounter_ext: Option<FieldExtension>

Extension field.

agent: Vec<Option<AuditEventAgent>>

Actor involved in the event

An actor taking an active role in the event or activity that is logged.

Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.

For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity.

When a network are used in an event being recorded, there should be distinct agent elements for the known actors using the network. The agent with a network detail would be the responsible agent for use of that network.

agent_ext: Vec<Option<FieldExtension>>

Extension field.

source: AuditEventSource

Audit Event Reporter

The actor that is reporting the event.

Events are reported by the actor that detected them. This may be one of the participating actors, but may also be different. The actor may be a human such as a medical-records clerk disclosing data manually, that clerk would be the source for the record of disclosure.

source_ext: Option<FieldExtension>

Extension field.

entity: Vec<Option<AuditEventEntity>>

Data or objects used

Specific instances of data or objects that have been accessed.

Required unless the values for event identification, agent identification, and audit source identification are sufficient to document the entire auditable event. Because events may have more than one entity, this group can be a repeating set of values.

entity_ext: Vec<Option<FieldExtension>>

Extension field.

Trait Implementations

impl Clone for AuditEventInner

fn clone(&self) -> AuditEventInner

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for AuditEventInner

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for AuditEventInner

fn deserialize<__D>( __deserializer: __D, ) -> Result<AuditEventInner, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl From<AuditEventInner> for AuditEvent

fn from(inner: AuditEventInner) -> AuditEvent

Converts to this type from the input type.

impl PartialEq for AuditEventInner

fn eq(&self, other: &AuditEventInner) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for AuditEventInner

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for AuditEventInner