R4-AuditEvent-element-map-to-R5
type: ConceptMap
node role: treeRoot
id:
  v: R4-AuditEvent-element-map-to-R5
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R4-AuditEvent-element-map-to-R5 Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/5.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to AuditEventversion: 5.0.0) Source Code Relationship Target Code Comment AuditEvent.meta (meta) is equivalent to AuditEvent.meta Element `AuditEvent.meta` is mapped to FHIR R5 element `AuditEvent.meta` as `Equivalent`. AuditEvent.implicitRules (implicitRules) is equivalent to AuditEvent.implicitRules Element `AuditEvent.implicitRules` is mapped to FHIR R5 element `AuditEvent.implicitRules` as `Equivalent`. 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 it's narrative along with other profiles, value sets, etc. AuditEvent.language (language) is equivalent to AuditEvent.language Element `AuditEvent.language` is mapped to FHIR R5 element `AuditEvent.language` as `Equivalent`. 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 a…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5
        l: hl7.fhir.uv.xver-r4.r5
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5
        l: hl7.fhir.uv.xver-r4.r5
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R4-AuditEvent-element-map-to-R5
  l: R4-AuditEvent-element-map-to-R5
version:
  v: 0.1.0
name:
  v: R4AuditEventElementMapToR5
title:
  v: Cross-version mapping for FHIR R4 AuditEvent to FHIR R5 AuditEvent
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:34.4488044-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R4 AuditEvent to FHIR R5.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source scope: Canonical
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
target scope: Uri
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
    l: http://hl7.org/fhir/StructureDefinition/AuditEvent
  target:
    v: http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0
    l: http://hl7.org/fhir/StructureDefinition/AuditEvent
  element:
    code:
      v: AuditEvent.meta
    display:
      v: meta
    target:
      code:
        v: AuditEvent.meta
      display:
        v: AuditEvent.meta
      relationship:
        v: equivalent
      comment:
        v: Element `AuditEvent.meta` is mapped to FHIR R5 element `AuditEvent.meta` as `Equivalent`.
  element:
    code:
      v: AuditEvent.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: AuditEvent.implicitRules
      display:
        v: AuditEvent.implicitRules
      relationship:
        v: equivalent
      comment:
        v: Element `AuditEvent.implicitRules` is mapped to FHIR R5 element `AuditEvent.implicitRules` as `Equivalent`. 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 it's narrative along with other profiles, value sets, etc.
  element:
    code:
      v: AuditEvent.language
    display:
      v: language
    target:
      code:
        v: AuditEvent.language
      display:
        v: AuditEvent.language
      relationship:
        v: equivalent
      comment:
        v: Element `AuditEvent.language` is mapped to FHIR R5 element `AuditEvent.language` as `Equivalent`. 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).
  element:
    code:
      v: AuditEvent.text
    display:
      v: text
    target:
      code:
        v: AuditEvent.text
      display:
        v: AuditEvent.text
      relationship:
        v: equivalent
      comment:
        v: Element `AuditEvent.text` is mapped to FHIR R5 element `AuditEvent.text` as `Equivalent`. 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 information is added later.
  element:
    code:
      v: AuditEvent.contained
    display:
      v: contained
    target:
      code:
        v: AuditEvent.contained
      display:
        v: AuditEvent.contained
      relationship:
        v: equivalent
      comment:
        v: Element `AuditEvent.contained` is mapped to FHIR R5 element `AuditEvent.contained` as `Equivalent`. 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.
  element:
    code:
      v: AuditEvent.type
    display:
      v: type
    target:
      code:
        v: AuditEvent.category
      display:
        v: AuditEvent.category
      relationship:
        v: source-is-narrower-than-target
      comment:
        v: Element `AuditEvent.type` is mapped to FHIR R5 element `AuditEvent.category` as `SourceIsNarrowerThanTarget`.
  element:
    code:
      v: AuditEvent.subtype
    display:
      v: subtype
    target:
      code:
        v: AuditEvent.code
      display:
        v: AuditEvent.code
      relationship:
        v: equivalent
      comment:
        v: Element `AuditEvent.subtype` is mapped to FHIR R5 element `AuditEvent.code` as `RelatedTo`.
  element:
    code:
      v: AuditEvent.action
    display:
      v: action
    target:
      code:
        v: AuditEvent.action
      display:
        v: AuditEvent.action
      relationship:
        v: equivalent
      comment:
        v: Element `AuditEvent.action` is mapped to FHIR R5 element `AuditEvent.action` as `Equivalent`.
  element:
    code:
      v: AuditEvent.recorded

v: recorded

code:
  v: AuditEvent.recorded
display:
  v: AuditEvent.recorded
relationship:
  v: equivalent
comment:
  v: Element `AuditEvent.recorded` is mapped to FHIR R5 element `AuditEvent.recorded` as `Equivalent`. In a distributed system, some sort of common time base (e.g. an NTP [RFC1305] server) is a good implementation tactic.

code:
  v: AuditEvent.outcome
display:
  v: outcome
target:
  code:
    v: AuditEvent.outcome.code
  display:
    v: AuditEvent.outcome.code
  relationship:
    v: related-to
  comment:
    v: Element `AuditEvent.outcome` is mapped to FHIR R5 element `AuditEvent.outcome.code` as `SourceIsNarrowerThanTarget`. The mappings for `AuditEvent.outcome` do not allow expression of the necessary codes, per the bindings on the source and target. 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.

code:
  v: AuditEvent.purposeOfEvent
display:
  v: purposeOfEvent
target:
  code:
    v: AuditEvent.authorization
  display:
    v: AuditEvent.authorization
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.purposeOfEvent` is mapped to FHIR R5 element `AuditEvent.authorization` as `Equivalent`. 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.

code:
  v: AuditEvent.agent
display:
  v: agent
target:
  code:
    v: AuditEvent.agent
  display:
    v: AuditEvent.agent
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `AuditEvent.agent` is mapped to FHIR R5 element `AuditEvent.agent` as `Equivalent`. 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.

code:
  v: AuditEvent.agent.type
display:
  v: type
target:
  code:
    v: AuditEvent.agent.type
  display:
    v: AuditEvent.agent.type
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.agent.type` is mapped to FHIR R5 element `AuditEvent.agent.type` as `Equivalent`.

code:
  v: AuditEvent.agent.role
display:
  v: role
target:
  code:
    v: AuditEvent.agent.role
  display:
    v: AuditEvent.agent.role
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.agent.role` is mapped to FHIR R5 element `AuditEvent.agent.role` as `Equivalent`. Should be roles relevant to the event. Should not be an exhaustive list of roles.

code:
  v: AuditEvent.agent.who
display:
  v: who
target:
  code:
    v: AuditEvent.agent.who
  display:
    v: AuditEvent.agent.who
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.agent.who` is mapped to FHIR R5 element `AuditEvent.agent.who` as `Equivalent`. Where a User ID is available it will go into who.identifier.

code:
  v: AuditEvent.agent.requestor
display:
  v: requestor
target:
  code:
    v: AuditEvent.agent.requestor
  display:
    v: AuditEvent.agent.requestor
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.agent.requestor` is mapped to FHIR R5 element `AuditEvent.agent.requestor` as `Equivalent`. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

code:
  v: AuditEvent.agent.location
display:
  v: location
target:
  code:
    v: AuditEvent.agent.location
  display:
    v: AuditEvent.agent.location
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.agent.location` is mapped to FHIR R5 element `AuditEvent.agent.location` as `Equivalent`.

code:
  v: AuditEvent.agent.policy
display:
  v: policy
target:
  code:
    v: AuditEvent.agent.policy
  display:
    v: AuditEvent.agent.policy
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.agent.policy` is mapped to FHIR R5 element `AuditEvent.agent.policy` as `Equivalent`. 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.

code:
  v: AuditEvent.agent.network
display:
  v: network
target:
  code:
    v: AuditEvent.agent.network[x]
  display:
    v: AuditEvent.agent.network[x]
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `AuditEvent.agent.network` is mapped to FHIR R5 element `AuditEvent.agent.network[x]` as `Equivalent`. The target context `AuditEvent.agent.network[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `AuditEvent.agent`.

code:
  v: AuditEvent.agent.purposeOfUse
display:
  v: purposeOfUse
target:
  code:
    v: AuditEvent.agent.authorization
  display:
    v: AuditEvent.agent.authorization
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.agent.purposeOfUse` is mapped to FHIR R5 element `AuditEvent.agent.authorization` as `Equivalent`. 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.

code:
  v: AuditEvent.source
display:
  v: source
target:
  code:
    v: AuditEvent.source
  display:
    v: AuditEvent.source
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `AuditEvent.source` is mapped to FHIR R5 element `AuditEvent.source` as `Equivalent`. 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.

code:
  v: AuditEvent.source.site
display:
  v: site
target:
  code:
    v: AuditEvent.source.site
  display:
    v: AuditEvent.source.site
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `AuditEvent.source.site` is mapped to FHIR R5 element `AuditEvent.source.site` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.source.site` do not cover the following types: string. The mappings for `AuditEvent.source.site` do not cover the following types based on type expansion: value.

code:
  v: AuditEvent.source.observer
display:
  v: observer
target:
  code:
    v: AuditEvent.source.observer
  display:
    v: AuditEvent.source.observer
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.source.observer` is mapped to FHIR R5 element `AuditEvent.source.observer` as `Equivalent`.

code:
  v: AuditEvent.source.type
display:
  v: type
target:
  code:
    v: AuditEvent.source.type
  display:
    v: AuditEvent.source.type
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.source.type` is mapped to FHIR R5 element `AuditEvent.source.type` as `SourceIsNarrowerThanTarget`.

code:
  v: AuditEvent.entity
display:
  v: entity
target:
  code:
    v: AuditEvent.entity
  display:
    v: AuditEvent.entity
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `AuditEvent.entity` is mapped to FHIR R5 element `AuditEvent.entity` as `Equivalent`. 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.

code:
  v: AuditEvent.entity.what
display:
  v: what
target:
  code:
    v: AuditEvent.entity.what
  display:
    v: AuditEvent.entity.what
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.entity.what` is mapped to FHIR R5 element `AuditEvent.entity.what` as `Equivalent`.

code:
  v: AuditEvent.entity.role
display:
  v: role
target:
  code:
    v: AuditEvent.entity.role
  display:
    v: AuditEvent.entity.role
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.entity.role` is mapped to FHIR R5 element `AuditEvent.entity.role` as `SourceIsNarrowerThanTarget`.

code:
  v: AuditEvent.entity.securityLabel
display:
  v: securityLabel
target:
  code:
    v: AuditEvent.entity.securityLabel
  display:
    v: AuditEvent.entity.securityLabel
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.entity.securityLabel` is mapped to FHIR R5 element `AuditEvent.entity.securityLabel` as `SourceIsNarrowerThanTarget`. Copied from entity meta security tags.

code:
  v: AuditEvent.entity.query
display:
  v: query
target:
  code:
    v: AuditEvent.entity.query
  display:
    v: AuditEvent.entity.query
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.entity.query` is mapped to FHIR R5 element `AuditEvent.entity.query` as `Equivalent`. The meaning and secondary-encoding of the content of base64 encoded blob is specific to the AuditEvent.type, AuditEvent.subtype, AuditEvent.entity.type, and AuditEvent.entity.role. The base64 is a general-use and safe container for event specific data blobs regardless of the encoding used by the transaction being recorded. An AuditEvent consuming application must understand the event it is consuming and the formats used by the event. For example, if auditing an Oracle network database access, the Oracle formats must be understood as they will be simply encoded in the base64binary blob.

code:
  v: AuditEvent.entity.detail
display:
  v: detail
target:
  code:
    v: AuditEvent.entity.detail
  display:
    v: AuditEvent.entity.detail
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `AuditEvent.entity.detail` is mapped to FHIR R5 element `AuditEvent.entity.detail` as `Equivalent`.

code:
  v: AuditEvent.entity.detail.type
display:
  v: type
target:
  code:
    v: AuditEvent.entity.detail.type
  display:
    v: AuditEvent.entity.detail.type
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `AuditEvent.entity.detail.type` is mapped to FHIR R5 element `AuditEvent.entity.detail.type` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.entity.detail.type` do not cover the following types: string. The mappings for `AuditEvent.entity.detail.type` do not cover the following types based on type expansion: value.

code:
  v: AuditEvent.entity.detail.value[x]
display:
  v: value[x]
target:
  code:
    v: AuditEvent.entity.detail.value[x]
  display:
    v: AuditEvent.entity.detail.value[x]
  relationship:
    v: equivalent
  comment:
    v: Element `AuditEvent.entity.detail.value[x]` is mapped to FHIR R5 element `AuditEvent.entity.detail.value[x]` as `Equivalent`. The target context `AuditEvent.entity.detail.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `AuditEvent.entity.detail`. The value can be string when known to be a string, else base64 encoding should be used to protect binary or undefined content. The meaning and secondary-encoding of the content of base64 encoded blob is specific to the AuditEvent.type, AuditEvent.subtype, AuditEvent.entity.type, and AuditEvent.entity.role. The base64 is a general-use and safe container for event specific data blobs regardless of the encoding used by the transaction being recorded. An AuditEvent consuming application must understand the event it is consuming and the formats used by the event. For example if auditing an Oracle network database access, the Oracle formats must be understood as they will be simply encoded in the base64binary blob.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.period|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.period
element:
  code:
    v: AuditEvent.period
  display:
    v: period
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.period` has a context of AuditEvent based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.outcome|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.outcome
element:
  code:
    v: AuditEvent.outcome
  display:
    v: outcome
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: Element `AuditEvent.outcome` is mapped to FHIR R5 element `AuditEvent.outcome.code` as `SourceIsNarrowerThanTarget`. The mappings for `AuditEvent.outcome` do not allow expression of the necessary codes, per the bindings on the source and target. 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.outcomeDesc|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.outcomeDesc
element:
  code:
    v: AuditEvent.outcomeDesc
  display:
    v: outcomeDesc
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.outcomeDesc` has a context of AuditEvent based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.outcomeDesc` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.altId|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.altId
element:
  code:
    v: AuditEvent.agent.altId
  display:
    v: altId
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.agent.altId` has a context of AuditEvent.agent based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.agent.altId` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.name|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.name
element:
  code:
    v: AuditEvent.agent.name
  display:
    v: name
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.agent.name` has a context of AuditEvent.agent based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.agent.name` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.media|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.media
element:
  code:
    v: AuditEvent.agent.media
  display:
    v: media
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.agent.media` has a context of AuditEvent.agent based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.agent.media` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.network.address|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.network.address
element:
  code:
    v: AuditEvent.agent.network.address
  display:
    v: address
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.agent.network.address` has a context of AuditEvent.agent.network[x] based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.agent.network.address` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The target context `AuditEvent.agent.network[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `AuditEvent.agent`. This could be a device id, IP address or some other identifier associated with a device.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.network.type|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.agent.network.type
element:
  code:
    v: AuditEvent.agent.network.type
  display:
    v: type
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.agent.network.type` has a context of AuditEvent.agent.network[x] based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.agent.network.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The target context `AuditEvent.agent.network[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `AuditEvent.agent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.source.site|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.source.site
element:
  code:
    v: AuditEvent.source.site
  display:
    v: site
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.source.site` is mapped to FHIR R5 element `AuditEvent.source.site` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.source.site` do not cover the following types: string. The mappings for `AuditEvent.source.site` do not cover the following types based on type expansion: value.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.type|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.type
element:
  code:
    v: AuditEvent.entity.type
  display:
    v: type
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.entity.type` has a context of AuditEvent.entity based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.entity.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This value is distinct from the user's role or any user relationship to the entity.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.lifecycle|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.lifecycle
element:
  code:
    v: AuditEvent.entity.lifecycle
  display:
    v: lifecycle
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.entity.lifecycle` has a context of AuditEvent.entity based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.entity.lifecycle` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This can be used to provide an audit trail for data, over time, as it passes through the system.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.name|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.name
element:
  code:
    v: AuditEvent.entity.name
  display:
    v: name
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.entity.name` has a context of AuditEvent.entity based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.entity.name` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.description|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.description
element:
  code:
    v: AuditEvent.entity.description
  display:
    v: description
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.entity.description` has a context of AuditEvent.entity based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.entity.description` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/AuditEvent
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.detail.type|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-AuditEvent.entity.detail.type
element:
  code:
    v: AuditEvent.entity.detail.type
  display:
    v: type
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `AuditEvent.entity.detail.type` is mapped to FHIR R5 element `AuditEvent.entity.detail.type` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.entity.detail.type` do not cover the following types: string. The mappings for `AuditEvent.entity.detail.type` do not cover the following types based on type expansion: value.