Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4 - Downloaded Version null See the Directory of published versions

ConceptMap: R2AuditEventElementMapToR4

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R2-AuditEvent-element-map-to-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R2AuditEventElementMapToR4

This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 AuditEvent to FHIR R4.

Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|1.0.2 to AuditEventversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
AuditEvent.meta (meta)maps to wider conceptAuditEvent.metaElement `AuditEvent.meta` is mapped to FHIR R4 element `AuditEvent.meta` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.meta` do not cover the following types: Meta. The mappings for `AuditEvent.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
AuditEvent.implicitRules (implicitRules)is equivalent toAuditEvent.implicitRulesElement `AuditEvent.implicitRules` is mapped to FHIR R4 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 as much as possible.
AuditEvent.language (language)is equivalent toAuditEvent.languageElement `AuditEvent.language` is mapped to FHIR R4 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).
AuditEvent.text (text)maps to wider conceptAuditEvent.textElement `AuditEvent.text` is mapped to FHIR R4 element `AuditEvent.text` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.text` do not cover the following types: Narrative. The mappings for `AuditEvent.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.
AuditEvent.contained (contained)is equivalent toAuditEvent.containedElement `AuditEvent.contained` is mapped to FHIR R4 element `AuditEvent.contained` as `SourceIsBroaderThanTarget`. 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.
AuditEvent.event (event)is related toAuditEventElement `AuditEvent.event` is mapped to FHIR R4 element `AuditEvent` as `SourceIsNarrowerThanTarget`.
AuditEvent.event.type (type)is equivalent toAuditEvent.typeElement `AuditEvent.event.type` is mapped to FHIR R4 element `AuditEvent.type` as `Equivalent`.
AuditEvent.event.subtype (subtype)is equivalent toAuditEvent.subtypeElement `AuditEvent.event.subtype` is mapped to FHIR R4 element `AuditEvent.subtype` as `Equivalent`.
AuditEvent.event.action (action)is equivalent toAuditEvent.actionElement `AuditEvent.event.action` is mapped to FHIR R4 element `AuditEvent.action` as `Equivalent`.
AuditEvent.event.dateTime (dateTime)is equivalent toAuditEvent.recordedElement `AuditEvent.event.dateTime` is mapped to FHIR R4 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.
AuditEvent.event.outcome (outcome)is equivalent toAuditEvent.outcomeElement `AuditEvent.event.outcome` is mapped to FHIR R4 element `AuditEvent.outcome` as `Equivalent`. 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.
AuditEvent.event.outcomeDesc (outcomeDesc)is equivalent toAuditEvent.outcomeDescElement `AuditEvent.event.outcomeDesc` is mapped to FHIR R4 element `AuditEvent.outcomeDesc` as `Equivalent`.
AuditEvent.event.purposeOfEvent (purposeOfEvent)narrowerAuditEvent.purposeOfEventElement `AuditEvent.event.purposeOfEvent` is mapped to FHIR R4 element `AuditEvent.purposeOfEvent` as `SourceIsNarrowerThanTarget`. Use participant.purposeOfUse when you know that is specific to the participant, otherwise use event.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.
AuditEvent.participant (participant)maps to wider conceptAuditEvent.agentElement `AuditEvent.participant` is mapped to FHIR R4 element `AuditEvent.agent` as `Equivalent`. There may be more than one user per event, for example, in cases of actions initiated by one user for other users, or in events that involve more than one user, hardware device, or system process. However, only one user may be the initiator/requestor for the event.
AuditEvent.participant.role (role)is equivalent toAuditEvent.agent.roleElement `AuditEvent.participant.role` is mapped to FHIR R4 element `AuditEvent.agent.role` as `Equivalent`.
AuditEvent.participant.reference (reference)is related toAuditEvent.agent.whoElement `AuditEvent.participant.reference` is mapped to FHIR R4 element `AuditEvent.agent.who` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AuditEvent.participant.reference` with unmapped reference targets: Device, Organization, Patient, Practitioner, RelatedPerson.
AuditEvent.participant.altId (altId)is equivalent toAuditEvent.agent.altIdElement `AuditEvent.participant.altId` is mapped to FHIR R4 element `AuditEvent.agent.altId` as `Equivalent`.
AuditEvent.participant.name (name)is equivalent toAuditEvent.agent.nameElement `AuditEvent.participant.name` is mapped to FHIR R4 element `AuditEvent.agent.name` as `Equivalent`.
AuditEvent.participant.requestor (requestor)is equivalent toAuditEvent.agent.requestorElement `AuditEvent.participant.requestor` is mapped to FHIR R4 element `AuditEvent.agent.requestor` as `Equivalent`. There can only be one initiator. If the initiator is not clear, then do not choose any one participant as the initiator.
AuditEvent.participant.location (location)maps to wider conceptAuditEvent.agent.locationElement `AuditEvent.participant.location` is mapped to FHIR R4 element `AuditEvent.agent.location` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.participant.location` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AuditEvent.participant.location` with unmapped reference targets: Location.
AuditEvent.participant.policy (policy)is equivalent toAuditEvent.agent.policyElement `AuditEvent.participant.policy` is mapped to FHIR R4 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.
AuditEvent.participant.media (media)is equivalent toAuditEvent.agent.mediaElement `AuditEvent.participant.media` is mapped to FHIR R4 element `AuditEvent.agent.media` as `Equivalent`.
AuditEvent.participant.network (network)maps to wider conceptAuditEvent.agent.networkElement `AuditEvent.participant.network` is mapped to FHIR R4 element `AuditEvent.agent.network` as `Equivalent`.
AuditEvent.participant.network.address (address)is equivalent toAuditEvent.agent.network.addressElement `AuditEvent.participant.network.address` is mapped to FHIR R4 element `AuditEvent.agent.network.address` as `Equivalent`. This could be a device id, IP address or some other identifier associated with a device.
AuditEvent.participant.network.type (type)is equivalent toAuditEvent.agent.network.typeElement `AuditEvent.participant.network.type` is mapped to FHIR R4 element `AuditEvent.agent.network.type` as `Equivalent`.
AuditEvent.participant.purposeOfUse (purposeOfUse)narrowerAuditEvent.agent.purposeOfUseElement `AuditEvent.participant.purposeOfUse` is mapped to FHIR R4 element `AuditEvent.agent.purposeOfUse` as `SourceIsNarrowerThanTarget`. Use participant.purposeOfUse when you know that is specific to the participant, otherwise use event.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.
AuditEvent.source (source)maps to wider conceptAuditEvent.sourceElement `AuditEvent.source` is mapped to FHIR R4 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.
AuditEvent.source.site (site)is equivalent toAuditEvent.source.siteElement `AuditEvent.source.site` is mapped to FHIR R4 element `AuditEvent.source.site` as `Equivalent`.
AuditEvent.source.identifier (identifier)is related toAuditEvent.source.observerElement `AuditEvent.source.identifier` is mapped to FHIR R4 element `AuditEvent.source.observer` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.source.identifier` do not cover the following types: Identifier. The mappings for `AuditEvent.source.identifier` do not cover the following types based on type expansion: period, system, type, use, value.
AuditEvent.source.type (type)is equivalent toAuditEvent.source.typeElement `AuditEvent.source.type` is mapped to FHIR R4 element `AuditEvent.source.type` as `Equivalent`.
AuditEvent.object (object)maps to wider conceptAuditEvent.entityElement `AuditEvent.object` is mapped to FHIR R4 element `AuditEvent.entity` as `Equivalent`. Required unless the values for Event Identification, Active Participant Identification, and Audit Source Identification are sufficient to document the entire auditable event. Because events may have more than one participant object, this group can be a repeating set of values.
AuditEvent.object.identifier (identifier)is related toAuditEvent.entity.whatElement `AuditEvent.object.identifier` is mapped to FHIR R4 element `AuditEvent.entity.what` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.object.identifier` do not cover the following types: Identifier. The mappings for `AuditEvent.object.identifier` do not cover the following types based on type expansion: period, system, type, use, value. Identifier detail depends on object type.
AuditEvent.object.reference (reference)is related toAuditEvent.entity.whatElement `AuditEvent.object.reference` is mapped to FHIR R4 element `AuditEvent.entity.what` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.object.reference` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `AuditEvent.object.reference` with unmapped reference targets: Resource.
AuditEvent.object.type (type)is equivalent toAuditEvent.entity.typeElement `AuditEvent.object.type` is mapped to FHIR R4 element `AuditEvent.entity.type` as `Equivalent`. This value is distinct from the user's role or any user relationship to the participant object.
AuditEvent.object.role (role)is equivalent toAuditEvent.entity.roleElement `AuditEvent.object.role` is mapped to FHIR R4 element `AuditEvent.entity.role` as `Equivalent`. See RFC 3881 for rules concerning matches between role and type.
AuditEvent.object.lifecycle (lifecycle)is equivalent toAuditEvent.entity.lifecycleElement `AuditEvent.object.lifecycle` is mapped to FHIR R4 element `AuditEvent.entity.lifecycle` as `Equivalent`. This can be used to provide an audit trail for data, over time, as it passes through the system.
AuditEvent.object.securityLabel (securityLabel)is equivalent toAuditEvent.entity.securityLabelElement `AuditEvent.object.securityLabel` is mapped to FHIR R4 element `AuditEvent.entity.securityLabel` as `Equivalent`.
AuditEvent.object.name (name)is equivalent toAuditEvent.entity.nameElement `AuditEvent.object.name` is mapped to FHIR R4 element `AuditEvent.entity.name` as `Equivalent`. This field may be used in a query/report to identify audit events for a specific person. For example, where multiple synonymous Participant Object IDs (patient number, medical record number, encounter number, etc.) have been used.
AuditEvent.object.description (description)is equivalent toAuditEvent.entity.descriptionElement `AuditEvent.object.description` is mapped to FHIR R4 element `AuditEvent.entity.description` as `Equivalent`.
AuditEvent.object.query (query)is equivalent toAuditEvent.entity.queryElement `AuditEvent.object.query` is mapped to FHIR R4 element `AuditEvent.entity.query` as `Equivalent`.
AuditEvent.object.detail (detail)maps to wider conceptAuditEvent.entity.detailElement `AuditEvent.object.detail` is mapped to FHIR R4 element `AuditEvent.entity.detail` as `Equivalent`.
AuditEvent.object.detail.type (type)is equivalent toAuditEvent.entity.detail.typeElement `AuditEvent.object.detail.type` is mapped to FHIR R4 element `AuditEvent.entity.detail.type` as `Equivalent`.
AuditEvent.object.detail.value (value)is equivalent toAuditEvent.entity.detail.value[x]Element `AuditEvent.object.detail.value` is mapped to FHIR R4 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`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|1.0.2 to DSTU2: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
AuditEvent.meta (meta)is equivalent toExtension (DSTU2: meta additional types)Element `AuditEvent.meta` is mapped to FHIR R4 element `AuditEvent.meta` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.meta` do not cover the following types: Meta. The mappings for `AuditEvent.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|1.0.2 to DSTU2: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
AuditEvent.text (text)is equivalent toExtension (DSTU2: text additional types)Element `AuditEvent.text` is mapped to FHIR R4 element `AuditEvent.text` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.text` do not cover the following types: Narrative. The mappings for `AuditEvent.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|1.0.2 to DSTU2: Unique identifier for the user (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
AuditEvent.participant.userId (userId)is equivalent toExtension (DSTU2: Unique identifier for the user (new))Element `AuditEvent.participant.userId` has a context of AuditEvent.agent based on following the parent source element upwards and mapping to `AuditEvent`. Element `AuditEvent.participant.userId` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|1.0.2 to DSTU2: identifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
AuditEvent.source.identifier (identifier)maps to wider conceptExtension (DSTU2: identifier additional types)Element `AuditEvent.source.identifier` is mapped to FHIR R4 element `AuditEvent.source.observer` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.source.identifier` do not cover the following types: Identifier. The mappings for `AuditEvent.source.identifier` do not cover the following types based on type expansion: period, system, type, use, value.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|1.0.2 to DSTU2: Specific instance of object (e.g. versioned) additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
AuditEvent.object.identifier (identifier)maps to wider conceptExtension (DSTU2: Specific instance of object (e.g. versioned) additional types)Element `AuditEvent.object.identifier` is mapped to FHIR R4 element `AuditEvent.entity.what` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.object.identifier` do not cover the following types: Identifier. The mappings for `AuditEvent.object.identifier` do not cover the following types based on type expansion: period, system, type, use, value. Identifier detail depends on object type.