A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage.

Based on ATNA (RFC 3881).

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

An Extension

R5: AuditEvent.severity (new:code)

Element AuditEvent.severity has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.severity has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). ATNA will map this to the SYSLOG PRI element.

R5: AuditEvent.occurred[x] (new:dateTime, Period)

Element AuditEvent.occurred[x] has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.occurred[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The time or period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.

R5: AuditEvent.basedOn (new:Reference(CarePlan,DeviceRequest,ImmunizationRecommendation,MedicationRequest,NutritionOrder,ServiceRequest,Task))

Element AuditEvent.basedOn has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.basedOn has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: AuditEvent.patient (new:Reference(Patient))

Element AuditEvent.patient has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.patient has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: AuditEvent.encounter (new:Reference(Encounter))

Element AuditEvent.encounter has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.encounter has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

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. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

Identifier for a family of the event. For example, a menu item, program, rule, policy, function code, application name or URL. It identifies the performed function.

Type of event.

This identifies the performed function. For "Execute" Event Action Code audit records, this identifies the application function performed.

An Extension

R5: AuditEvent.category additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.category is mapped to FHIR STU3 element AuditEvent.type as SourceIsBroaderThanTarget. The mappings for AuditEvent.category do not cover the following types: CodeableConcept. The mappings for AuditEvent.category do not cover the following types based on type expansion: text.

The time when the event occurred on the source.

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

This ties an event to a specific date and time. Security audits typically require a consistent time base (e.g. UTC), to eliminate time-zone issues arising from geographical distribution.

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.

An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility.

An Extension

R5: AuditEvent.agent.type (new:CodeableConcept)

Element AuditEvent.agent.type has a context of AuditEvent.agent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.agent.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). For example: assembler, author, prescriber, signer, investigator, etc.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

Indicator that the user is or is not the requestor, or initiator, for the event being audited.

There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

This value is used to distinguish between requestor-users and recipient-users. For example, one person may initiate a report-output to be sent to another user.

The system that is reporting the event.

Since multi-tier, distributed, or composite applications make source identification ambiguous, this collection of fields may repeat for each application or process actively involved in the event. For example, multiple value-sets can identify participating web servers, application processes, and database server threads in an n-tier distributed application. Passive event participants (e.g. low-level network transports) need not be identified.

The event is reported by one source.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

Identifier of the source where the event was detected.

This field ties the event to a specific source system. It may be used to group events for analysis according to where the event was detected.

An Extension

R5: AuditEvent.source.observer additional types (Reference(http://hl7.org/fhir/StructureDefinition/Practitioner), Reference(http://hl7.org/fhir/StructureDefinition/PractitionerRole), Reference(http://hl7.org/fhir/StructureDefinition/Organization), Reference(http://hl7.org/fhir/StructureDefinition/CareTeam), Reference(http://hl7.org/fhir/StructureDefinition/Patient), Reference(http://hl7.org/fhir/StructureDefinition/Device), Reference(http://hl7.org/fhir/StructureDefinition/RelatedPerson))

Element AuditEvent.source.observer is mapped to FHIR STU3 element AuditEvent.source.identifier as SourceIsBroaderThanTarget. The mappings for AuditEvent.source.observer do not cover the following types: Reference.

The purpose of this identifier.

This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

R5: AuditEvent.severity (new:code)

Element AuditEvent.severity has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.severity has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). ATNA will map this to the SYSLOG PRI element.

R5: AuditEvent.occurred[x] (new:dateTime, Period)

Element AuditEvent.occurred[x] has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.occurred[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The time or period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.

R5: AuditEvent.basedOn (new:Reference(CarePlan,DeviceRequest,ImmunizationRecommendation,MedicationRequest,NutritionOrder,ServiceRequest,Task))

Element AuditEvent.basedOn has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.basedOn has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: AuditEvent.patient (new:Reference(Patient))

Element AuditEvent.patient has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.patient has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: AuditEvent.encounter (new:Reference(Encounter))

Element AuditEvent.encounter has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.encounter has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: AuditEvent.category additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.category is mapped to FHIR STU3 element AuditEvent.type as SourceIsBroaderThanTarget. The mappings for AuditEvent.category do not cover the following types: CodeableConcept. The mappings for AuditEvent.category do not cover the following types based on type expansion: text.

R5: AuditEvent.code additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.code is mapped to FHIR STU3 element AuditEvent.subtype as RelatedTo. The mappings for AuditEvent.code do not cover the following types: CodeableConcept. The mappings for AuditEvent.code do not cover the following types based on type expansion: text.

R5: AuditEvent.outcome.code (new:Coding)

Element AuditEvent.outcome.code has a context of AuditEvent.outcome based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.outcome.code has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: AuditEvent.outcome.detail (new:CodeableConcept)

Element AuditEvent.outcome.detail has a context of AuditEvent.outcome based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.outcome.detail has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). A human readable description of the error issue SHOULD be placed in details.text.

R5: AuditEvent.agent.type (new:CodeableConcept)

Element AuditEvent.agent.type has a context of AuditEvent.agent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.agent.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). For example: assembler, author, prescriber, signer, investigator, etc.

R5: AuditEvent.source.site additional types (Reference(http://hl7.org/fhir/StructureDefinition/Location)) additional types from child elements (identifier)

Element AuditEvent.source.site is mapped to FHIR STU3 element AuditEvent.source.site as SourceIsBroaderThanTarget. The mappings for AuditEvent.source.site do not cover the following types: Reference. The mappings for AuditEvent.source.site do not cover the following types based on type expansion: identifier.

R5: AuditEvent.source.observer additional types (Reference(http://hl7.org/fhir/StructureDefinition/Practitioner), Reference(http://hl7.org/fhir/StructureDefinition/PractitionerRole), Reference(http://hl7.org/fhir/StructureDefinition/Organization), Reference(http://hl7.org/fhir/StructureDefinition/CareTeam), Reference(http://hl7.org/fhir/StructureDefinition/Patient), Reference(http://hl7.org/fhir/StructureDefinition/Device), Reference(http://hl7.org/fhir/StructureDefinition/RelatedPerson))

Element AuditEvent.source.observer is mapped to FHIR STU3 element AuditEvent.source.identifier as SourceIsBroaderThanTarget. The mappings for AuditEvent.source.observer do not cover the following types: Reference.

R5: AuditEvent.source.type additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.source.type is mapped to FHIR STU3 element AuditEvent.source.type as SourceIsBroaderThanTarget. The mappings for AuditEvent.source.type do not cover the following types: CodeableConcept. The mappings for AuditEvent.source.type do not cover the following types based on type expansion: text.

R5: AuditEvent.entity.what additional types from child elements (display, reference, type)

Element AuditEvent.entity.what is mapped to FHIR STU3 element AuditEvent.entity.identifier as SourceIsBroaderThanTarget. Element AuditEvent.entity.what is mapped to FHIR STU3 element AuditEvent.entity.reference as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.what do not cover the following types based on type expansion: display, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element AuditEvent.entity.what with unmapped reference targets: Resource. Use .what.display when all you have is a string (e.g. ParticipantObjectName).

R5: AuditEvent.entity.agent (new:AuditEvent.agent)

Element AuditEvent.entity.agent has a context of AuditEvent.entity based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.entity.agent has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). A usecase where one AuditEvent.entity.agent is used where the Entity that was used in the creation/updating of a target resource, is not in the context of the same custodianship as the target resource, and thus the meaning of AuditEvent.entity.agent is to say that the entity referenced is managed elsewhere and that this Agent provided access to it. This would be similar to where the Entity being referenced is managed outside FHIR, such as through HL7 V2, v3, or XDS. This might be where the Entity being referenced is managed in another FHIR resource server. Thus it explains the provenance of that Entity's use in the context of this AuditEvent activity.

R5: AuditEvent.entity.role additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.entity.role is mapped to FHIR STU3 element AuditEvent.entity.role as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.role do not cover the following types: CodeableConcept. The mappings for AuditEvent.entity.role do not cover the following types based on type expansion: text.

R5: AuditEvent.entity.securityLabel additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.entity.securityLabel is mapped to FHIR STU3 element AuditEvent.entity.securityLabel as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.securityLabel do not cover the following types: CodeableConcept. The mappings for AuditEvent.entity.securityLabel do not cover the following types based on type expansion: text. Copied from entity meta security tags.

R5: AuditEvent.entity.detail.value[x] additional types (Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, time, dateTime, Period)

Element AuditEvent.entity.detail.value[x] is mapped to FHIR STU3 element AuditEvent.entity.detail.value as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.detail.value[x] do not cover the following types: boolean, CodeableConcept, dateTime, integer, Period, Quantity, Range, Ratio, string, time.

R5: AuditEvent.entity.detail.type additional types (CodeableConcept) additional types from child elements (coding)

Element AuditEvent.entity.detail.type is mapped to FHIR STU3 element AuditEvent.entity.detail.type as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.detail.type do not cover the following types: CodeableConcept. The mappings for AuditEvent.entity.detail.type do not cover the following types based on type expansion: coding.

A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage.

Based on ATNA (RFC 3881).

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

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

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

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

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).

Unless not suitable, these codes SHALL be taken from Common Languages
(extensible to http://hl7.org/fhir/ValueSet/languages|3.0.2)

A human language.

A human-readable narrative that contains a summary of the resource, and may 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 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 in formation is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

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.

An Extension

R5: AuditEvent.severity (new:code)

Element AuditEvent.severity has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.severity has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). ATNA will map this to the SYSLOG PRI element.

R5: AuditEvent.occurred[x] (new:dateTime, Period)

Element AuditEvent.occurred[x] has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.occurred[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The time or period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.

R5: AuditEvent.basedOn (new:Reference(CarePlan,DeviceRequest,ImmunizationRecommendation,MedicationRequest,NutritionOrder,ServiceRequest,Task))

Element AuditEvent.basedOn has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.basedOn has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: AuditEvent.patient (new:Reference(Patient))

Element AuditEvent.patient has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.patient has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: AuditEvent.encounter (new:Reference(Encounter))

Element AuditEvent.encounter has a context of AuditEvent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.encounter has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

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. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

Identifier for a family of the event. For example, a menu item, program, rule, policy, function code, application name or URL. It identifies the performed function.

Type of event.

This identifies the performed function. For "Execute" Event Action Code audit records, this identifies the application function performed.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.category additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.category is mapped to FHIR STU3 element AuditEvent.type as SourceIsBroaderThanTarget. The mappings for AuditEvent.category do not cover the following types: CodeableConcept. The mappings for AuditEvent.category do not cover the following types based on type expansion: text.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Identifier for the category of event.

Sub-type of event.

This field enables queries of messages by implementation-defined event categories.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.code additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.code is mapped to FHIR STU3 element AuditEvent.subtype as RelatedTo. The mappings for AuditEvent.code do not cover the following types: CodeableConcept. The mappings for AuditEvent.code do not cover the following types based on type expansion: text.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

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

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

This broadly indicates what kind of action was done on the AuditEvent.entity by the AuditEvent.agent.

The time when the event occurred on the source.

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

This ties an event to a specific date and time. Security audits typically require a consistent time base (e.g. UTC), to eliminate time-zone issues arising from geographical distribution.

Indicates whether the event succeeded or failed.

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.

Indicates whether the event succeeded or failed

unique id for the element within a resource (for internal references)

An Extension

R5: AuditEvent.outcome.code (new:Coding)

Element AuditEvent.outcome.code has a context of AuditEvent.outcome based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.outcome.code has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R5: AuditEvent.outcome.detail (new:CodeableConcept)

Element AuditEvent.outcome.detail has a context of AuditEvent.outcome based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.outcome.detail has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). A human readable description of the error issue SHOULD be placed in details.text.

Primitive value for code

A free text description of the outcome of the event.

The purposeOfUse (reason) that was used during the event being recorded.

Use AuditEvent.agent.purposeOfUse when you know that it is specific to the agent, otherwise use AuditEvent.purposeOfEvent. 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.

The reason the activity took place.

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.

An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.agent.type (new:CodeableConcept)

Element AuditEvent.agent.type has a context of AuditEvent.agent based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.agent.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). For example: assembler, author, prescriber, signer, investigator, etc.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

The security role that the user was acting under, that come from local codes defined by the access control security system (e.g. RBAC, ABAC) used in the local context.

Should be roles relevant to the event. Should not be an exhaustive list of roles.

Unless not suitable, these codes SHALL be taken from SecurityRoleType
(extensible to http://hl7.org/fhir/ValueSet/security-role-type|1.8.0)

What security role enabled the agent to participate in the event

This value ties an audited event to a user's role(s). It is an optional value that might be used to group events for analysis by user functional role categories.

Direct reference to a resource that identifies the agent.

This field ties an audit event to a specific resource.

Unique identifier for the user actively participating in the event.

A unique value within the Audit Source ID. For node-based authentication -- where only the system hardware or process, but not a human user, is identified -- User ID would be the node name.

This field ties an audit event to a specific user.

Alternative agent Identifier. For a human, this should be a user identifier text string from authentication system. This identifier would be one known to a common authentication system (e.g. single sign-on), if available.

In some situations, a human user may authenticate with one identity but, to access a specific application system, may use a synonymous identify. For example, some "single sign on" implementations will do this. The alternative identifier would then be the original identify used for authentication, and the User ID is the one known to and used by the application.

Human-meaningful name for the agent.

The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.

Indicator that the user is or is not the requestor, or initiator, for the event being audited.

There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

This value is used to distinguish between requestor-users and recipient-users. For example, one person may initiate a report-output to be sent to another user.

Where the event occurred.

The policy or plan that authorized the activity being recorded. Typically, a single activity may have multiple applicable policies, such as patient consent, guarantor funding, etc. The policy would also indicate the security token used.

For example: Where an OAuth token authorizes, the unique identifier from the OAuth token is placed into the policy element Where a policy engine (e.g. XACML) holds policy logic, the unique policy identifier is placed into the policy element.

This value is used retrospectively to determine the authorization policies.

Type of media involved. Used when the event is about exporting/importing onto media.

Used when the event is about exporting/importing onto media.

Usually, this is used instead of specifying a network address. This field is not used for Media Id (i.e. the serial number of a CD).

Logical network location for application activity, if the activity has a network location.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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.

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.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

An identifier for the network access point of the user device for the audit event.

This could be a device id, IP address or some other identifier associated with a device.

This datum identifies the user's network access point, which may be distinct from the server that performed the action. It is an optional value that may be used to group events recorded on separate servers for analysis of a specific network access point's data access across all servers.

An identifier for the type of network access point that originated the audit event.

The type of network access point of this agent in the audit event

This datum identifies the type of network access point identifier of the user device for the audit event. It is an optional value that may be used to group events recorded on separate servers for analysis of access according to a network access point's type.

The reason (purpose of use), specific to this agent, that was used during the event being recorded.

Use AuditEvent.agent.purposeOfUse when you know that is specific to the agent, otherwise use AuditEvent.purposeOfEvent. 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.

The reason the activity took place.

The system that is reporting the event.

Since multi-tier, distributed, or composite applications make source identification ambiguous, this collection of fields may repeat for each application or process actively involved in the event. For example, multiple value-sets can identify participating web servers, application processes, and database server threads in an n-tier distributed application. Passive event participants (e.g. low-level network transports) need not be identified.

The event is reported by one source.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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.

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.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

Logical source location within the healthcare enterprise network. For example, a hospital or other provider location within a multi-entity provider group.

This value differentiates among the sites in a multi-site enterprise health information system.

unique id for the element within a resource (for internal references)

An Extension

R5: AuditEvent.source.site additional types (Reference(http://hl7.org/fhir/StructureDefinition/Location)) additional types from child elements (identifier)

Element AuditEvent.source.site is mapped to FHIR STU3 element AuditEvent.source.site as SourceIsBroaderThanTarget. The mappings for AuditEvent.source.site do not cover the following types: Reference. The mappings for AuditEvent.source.site do not cover the following types based on type expansion: identifier.

The actual value

Identifier of the source where the event was detected.

This field ties the event to a specific source system. It may be used to group events for analysis according to where the event was detected.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.source.observer additional types (Reference(http://hl7.org/fhir/StructureDefinition/Practitioner), Reference(http://hl7.org/fhir/StructureDefinition/PractitionerRole), Reference(http://hl7.org/fhir/StructureDefinition/Organization), Reference(http://hl7.org/fhir/StructureDefinition/CareTeam), Reference(http://hl7.org/fhir/StructureDefinition/Patient), Reference(http://hl7.org/fhir/StructureDefinition/Device), Reference(http://hl7.org/fhir/StructureDefinition/RelatedPerson))

Element AuditEvent.source.observer is mapped to FHIR STU3 element AuditEvent.source.identifier as SourceIsBroaderThanTarget. The mappings for AuditEvent.source.observer do not cover the following types: Reference.

The purpose of this identifier.

This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage.

Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

Code specifying the type of source where event originated.

Code specifying the type of system that detected and recorded the event.

This field indicates which type of source is identified by the Audit Source ID. It is an optional value that may be used to group events for analysis according to the type of source where the event occurred.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.source.type additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.source.type is mapped to FHIR STU3 element AuditEvent.source.type as SourceIsBroaderThanTarget. The mappings for AuditEvent.source.type do not cover the following types: CodeableConcept. The mappings for AuditEvent.source.type do not cover the following types based on type expansion: text.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

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.

The event may have other entities involved.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.entity.what additional types from child elements (display, reference, type)

Element AuditEvent.entity.what is mapped to FHIR STU3 element AuditEvent.entity.identifier as SourceIsBroaderThanTarget. Element AuditEvent.entity.what is mapped to FHIR STU3 element AuditEvent.entity.reference as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.what do not cover the following types based on type expansion: display, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element AuditEvent.entity.what with unmapped reference targets: Resource. Use .what.display when all you have is a string (e.g. ParticipantObjectName).

R5: AuditEvent.entity.agent (new:AuditEvent.agent)

Element AuditEvent.entity.agent has a context of AuditEvent.entity based on following the parent source element upwards and mapping to AuditEvent. Element AuditEvent.entity.agent has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). A usecase where one AuditEvent.entity.agent is used where the Entity that was used in the creation/updating of a target resource, is not in the context of the same custodianship as the target resource, and thus the meaning of AuditEvent.entity.agent is to say that the entity referenced is managed elsewhere and that this Agent provided access to it. This would be similar to where the Entity being referenced is managed outside FHIR, such as through HL7 V2, v3, or XDS. This might be where the Entity being referenced is managed in another FHIR resource server. Thus it explains the provenance of that Entity's use in the context of this AuditEvent activity.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

Identifies a specific instance of the entity. The reference should always be version specific.

Identifier detail depends on entity type.

Identifies a specific instance of the entity. The reference should be version specific.

The type of the object that was involved in this audit event.

This value is distinct from the user's role or any user relationship to the entity.

Code for the entity type involved in the audit event

To describe the object being acted upon. In addition to queries on the subject of the action in an auditable event, it is also important to be able to query on the object type for the action.

Code representing the role the entity played in the event being audited.

Code representing the role the entity played in the audit event

For some detailed audit analysis it may be necessary to indicate a more granular type of entity, based on the application role it serves.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.entity.role additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.entity.role is mapped to FHIR STU3 element AuditEvent.entity.role as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.role do not cover the following types: CodeableConcept. The mappings for AuditEvent.entity.role do not cover the following types based on type expansion: text.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Identifier for the data life-cycle stage for the entity.

This can be used to provide an audit trail for data, over time, as it passes through the system.

Identifier for the data life-cycle stage for the entity

Institutional policies for privacy and security may optionally fall under different accountability rules based on data life cycle. This provides a differentiating value for those cases.

Security labels for the identified entity.

Copied from entity meta security tags.

Unless not suitable, these codes SHALL be taken from All Security Labels
(extensible to http://hl7.org/fhir/ValueSet/security-labels|3.0.2)

Security Labels from the Healthcare Privacy and Security Classification System.

This field identifies the security labels for a specific instance of an object, such as a patient, to detect/track privacy and security issues.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.entity.securityLabel additional types (CodeableConcept) additional types from child elements (text)

Element AuditEvent.entity.securityLabel is mapped to FHIR STU3 element AuditEvent.entity.securityLabel as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.securityLabel do not cover the following types: CodeableConcept. The mappings for AuditEvent.entity.securityLabel do not cover the following types based on type expansion: text. Copied from entity meta security tags.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

A name of the entity in the audit event.

This field may be used in a query/report to identify audit events for a specific person. For example, where multiple synonymous entity identifiers (patient number, medical record number, encounter number, etc.) have been used.

Use only where entity can't be identified with an identifier.

Text that describes the entity in more detail.

Use only where entity can't be identified with an identifier.

The query parameters for a query-type entities.

For query events, it may be necessary to capture the actual query input to the query process in order to identify the specific event. Because of differences among query implementations and data encoding for them, this is a base 64 encoded data blob. It may be subsequently decoded or interpreted by downstream audit analysis processing.

Tagged value pairs for conveying additional information about the entity.

Implementation-defined data about specific details of the object accessed or used.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: AuditEvent.entity.detail.value[x] additional types (Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, time, dateTime, Period)

Element AuditEvent.entity.detail.value[x] is mapped to FHIR STU3 element AuditEvent.entity.detail.value as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.detail.value[x] do not cover the following types: boolean, CodeableConcept, dateTime, integer, Period, Quantity, Range, Ratio, string, time.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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.

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.

The type of extra detail provided in the value.

unique id for the element within a resource (for internal references)

An Extension

R5: AuditEvent.entity.detail.type additional types (CodeableConcept) additional types from child elements (coding)

Element AuditEvent.entity.detail.type is mapped to FHIR STU3 element AuditEvent.entity.detail.type as SourceIsBroaderThanTarget. The mappings for AuditEvent.entity.detail.type do not cover the following types: CodeableConcept. The mappings for AuditEvent.entity.detail.type do not cover the following types based on type expansion: coding.

The actual value

The details, base64 encoded. Used to carry bulk information.

The value is base64 encoded to enable various encodings or binary content.

Should not duplicate the entity value unless absolutely necessary.