Generated Narrative: ConceptMap R5-AuditEvent-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to AuditEventversion: 4.0.1) Source Code Relationship Target Code Comment AuditEvent.meta (meta) is equivalent to AuditEvent.meta Element `AuditEvent.meta` is mapped to FHIR R4 element `AuditEvent.meta` as `Equivalent`. AuditEvent.implicitRules (implicitRules) is equivalent to AuditEvent.implicitRules Element `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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc. AuditEvent.language (language) is equivalent to AuditEvent.language Element `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) is equivalent to AuditEvent.text Element `AuditEvent.text` is mapped to FHIR R4 element `AuditEvent.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. AuditEvent.contained (contained) is equivalent to AuditEvent.contained Element `AuditEvent.contained` is mapped to FHIR R4 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. AuditEvent.category (category) maps to wider concept AuditEvent.type Element `AuditEvent.category` is mapped to FHIR R4 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. AuditEvent.code (code) is related to AuditEvent.subtype Element `AuditEvent.code` is mapped to FHIR R4 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. AuditEvent.action (action) is equivalent to AuditEvent.action Element `AuditEvent.action` is mapped to FHIR R4 element `AuditEvent.action` as `Equivalent`. AuditEvent.occurred[x] (occurred[x]) maps to wider concept AuditEvent.period Element `AuditEvent.occurred[x]` is mapped to FHIR R4 element `AuditEvent.period` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.occurred[x]` do not cover the following types: dateTime. The mappings for `AuditEvent.occurred[x]` do not cover the following types based on type expansion: value. The time or period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time. AuditEvent.recorded (recorded) is equivalent to AuditEvent.recorded Element `AuditEvent.recorded` 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.outcome (outcome) maps to wider concept AuditEvent.outcome Element `AuditEvent.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.authorization (authorization) is equivalent to AuditEvent.purposeOfEvent Element `AuditEvent.authorization` is mapped to FHIR R4 element `AuditEvent.purposeOfEvent` as `Equivalent`. Use AuditEvent.agent.authorization when you know that it is specific to the agent, otherwise use AuditEvent.authorization. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why. AuditEvent.agent (agent) maps to wider concept AuditEvent.agent Element `AuditEvent.agent` is mapped to FHIR R4 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. When a network are used in an event being recorded, there should be distinct agent elements for the known actors using the network. The agent with a network detail would be the responsible agent for use of that network. AuditEvent.agent.type (type) is equivalent to AuditEvent.agent.type Element `AuditEvent.agent.type` is mapped to FHIR R4 element `AuditEvent.agent.type` as `Equivalent`. For example: assembler, author, prescriber, signer, investigator, etc. AuditEvent.agent.role (role) is equivalent to AuditEvent.agent.role Element `AuditEvent.agent.role` is mapped to FHIR R4 element `AuditEvent.agent.role` as `Equivalent`. For example: Chief-of-Radiology, Nurse, Physician, Medical-Student, etc. AuditEvent.agent.who (who) maps to wider concept AuditEvent.agent.who Element `AuditEvent.agent.who` is mapped to FHIR R4 element `AuditEvent.agent.who` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `AuditEvent.agent.who` with unmapped reference targets: CareTeam. Where a User ID is available it will go into who.identifier. Where a name of the user (human readable) it will go into who.display. AuditEvent.agent.requestor (requestor) is equivalent to AuditEvent.agent.requestor Element `AuditEvent.agent.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 agent as the initiator. AuditEvent.agent.location (location) is equivalent to AuditEvent.agent.location Element `AuditEvent.agent.location` is mapped to FHIR R4 element `AuditEvent.agent.location` as `Equivalent`. AuditEvent.agent.policy (policy) is equivalent to AuditEvent.agent.policy Element `AuditEvent.agent.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.agent.network[x] (network[x]) is equivalent to AuditEvent.agent.network Element `AuditEvent.agent.network[x]` is mapped to FHIR R4 element `AuditEvent.agent.network` as `Equivalent`. When remote network endpoint is known, another agent representing the remote agent would indicate the remote network endpoint used. Convention is to indicate data flowing from Source to Destination. The convention for Search, given data flows both ways (query parameters vs results), is to have the Source as the initiator of the Search Transaction, and the Destination the responder to the Search transaction. AuditEvent.agent.authorization (authorization) is equivalent to AuditEvent.agent.purposeOfUse Element `AuditEvent.agent.authorization` is mapped to FHIR R4 element `AuditEvent.agent.purposeOfUse` as `Equivalent`. Use AuditEvent.agent.authorization when you know that is specific to the agent, otherwise use AuditEvent.authorization. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why. AuditEvent.source (source) maps to wider concept AuditEvent.source Element `AuditEvent.source` is mapped to FHIR R4 element `AuditEvent.source` as `Equivalent`. Events are reported by the actor that detected them. This may be one of the participating actors, but may also be different. The actor may be a human such as a medical-records clerk disclosing data manually, that clerk would be the source for the record of disclosure. AuditEvent.source.site (site) maps to wider concept AuditEvent.source.site Element `AuditEvent.source.site` is mapped to FHIR R4 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. AuditEvent.source.observer (observer) maps to wider concept AuditEvent.source.observer Element `AuditEvent.source.observer` is mapped to FHIR R4 element `AuditEvent.source.observer` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `AuditEvent.source.observer` with unmapped reference targets: CareTeam. AuditEvent.source.type (type) maps to wider concept AuditEvent.source.type Element `AuditEvent.source.type` is mapped to FHIR R4 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. AuditEvent.entity (entity) maps to wider concept AuditEvent.entity Element `AuditEvent.entity` is mapped to FHIR R4 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. AuditEvent.entity.what (what) is equivalent to AuditEvent.entity.what Element `AuditEvent.entity.what` is mapped to FHIR R4 element `AuditEvent.entity.what` as `Equivalent`. Use .what.display when all you have is a string (e.g. ParticipantObjectName). AuditEvent.entity.role (role) maps to wider concept AuditEvent.entity.role Element `AuditEvent.entity.role` is mapped to FHIR R4 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. AuditEvent.entity.securityLabel (securityLabel) maps to wider concept AuditEvent.entity.securityLabel Element `AuditEvent.entity.securityLabel` is mapped to FHIR R4 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. AuditEvent.entity.query (query) is equivalent to AuditEvent.entity.query Element `AuditEvent.entity.query` is mapped to FHIR R4 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, 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. The DICOM AuditMessage schema does not support both .name and .query being populated. AuditEvent.entity.detail (detail) maps to wider concept AuditEvent.entity.detail Element `AuditEvent.entity.detail` is mapped to FHIR R4 element `AuditEvent.entity.detail` as `Equivalent`. AuditEvent.entity.detail.type (type) maps to wider concept AuditEvent.entity.detail.type Element `AuditEvent.entity.detail.type` is mapped to FHIR R4 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. AuditEvent.entity.detail.value[x] (value[x]) maps to wider concept AuditEvent.entity.detail.value[x] Element `AuditEvent.entity.detail.value[x]` is mapped to FHIR R4 element `AuditEvent.entity.detail.value[x]` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.entity.detail.value[x]` do not cover the following types: boolean, CodeableConcept, dateTime, integer, Period, Quantity, Range, Ratio, time. 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|5.0.0 to R5: category additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.category (category) maps to wider concept Extension (R5: category additional types) Element `AuditEvent.category` is mapped to FHIR R4 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. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: Specific type of event additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.code (code) maps to wider concept Extension (R5: Specific type of event additional types) Element `AuditEvent.code` is mapped to FHIR R4 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. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: emergency | alert | critical | error | warning | notice | informational | debug (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.severity (severity) maps to wider concept Extension (R5: emergency | alert | critical | error | warning | notice | informational | debug (new)) 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 R4. Typically, this is because the element has been added (is a new element). ATNA will map this to the SYSLOG PRI element. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: occurred additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.occurred[x] (occurred[x]) maps to wider concept Extension (R5: occurred additional types) Element `AuditEvent.occurred[x]` is mapped to FHIR R4 element `AuditEvent.period` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.occurred[x]` do not cover the following types: dateTime. The mappings for `AuditEvent.occurred[x]` do not cover the following types based on type expansion: value. The time or period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: Whether the event succeeded or failed (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.outcome.code (code) maps to wider concept Extension (R5: Whether the event succeeded or failed (new)) 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 R4. 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. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: Additional outcome detail (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.outcome.detail (detail) maps to wider concept Extension (R5: Additional outcome detail (new)) 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 R4. 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. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: Workflow authorization within which this event occurred (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.basedOn (basedOn) maps to wider concept Extension (R5: Workflow authorization within which this event occurred (new)) 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 R4. Typically, this is because the element has been added (is a new element). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: The patient is the subject of the data used/created/updated/deleted during the activity (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.patient (patient) maps to wider concept Extension (R5: The patient is the subject of the data used/created/updated/deleted during the activity (new)) 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 R4. Typically, this is because the element has been added (is a new element). Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: Encounter within which this event occurred or which the event is tightly associated (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.encounter (encounter) maps to wider concept Extension (R5: Encounter within which this event occurred or which the event is tightly associated (new)) 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 R4. Typically, this is because the element has been added (is a new element). Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: agentversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.agent (agent) is equivalent to Extension (R5: agent) Element `AuditEvent.agent` is mapped to FHIR R4 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. When a network are used in an event being recorded, there should be distinct agent elements for the known actors using the network. The agent with a network detail would be the responsible agent for use of that network. AuditEvent.agent.type (type) is equivalent to Extension.extension:type (R5: type) Element `AuditEvent.agent.type` is mapped to FHIR R4 element `AuditEvent.agent.type` as `Equivalent`. For example: assembler, author, prescriber, signer, investigator, etc. AuditEvent.agent.role (role) is equivalent to Extension.extension:role (R5: role) Element `AuditEvent.agent.role` is mapped to FHIR R4 element `AuditEvent.agent.role` as `Equivalent`. For example: Chief-of-Radiology, Nurse, Physician, Medical-Student, etc. AuditEvent.agent.who (who) is equivalent to Extension.extension:who (R5: who) Element `AuditEvent.agent.who` is mapped to FHIR R4 element `AuditEvent.agent.who` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `AuditEvent.agent.who` with unmapped reference targets: CareTeam. Where a User ID is available it will go into who.identifier. Where a name of the user (human readable) it will go into who.display. AuditEvent.agent.requestor (requestor) is equivalent to Extension.extension:requestor (R5: requestor) Element `AuditEvent.agent.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 agent as the initiator. AuditEvent.agent.location (location) is equivalent to Extension.extension:location (R5: The agent location when the event occurred) Element `AuditEvent.agent.location` is mapped to FHIR R4 element `AuditEvent.agent.location` as `Equivalent`. AuditEvent.agent.policy (policy) is equivalent to Extension.extension:policy (R5: Policy that authorized the agent participation in the event) Element `AuditEvent.agent.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.agent.network[x] (network[x]) is equivalent to Extension.extension:network (R5: This agent network location for the activity) Element `AuditEvent.agent.network[x]` is mapped to FHIR R4 element `AuditEvent.agent.network` as `Equivalent`. When remote network endpoint is known, another agent representing the remote agent would indicate the remote network endpoint used. Convention is to indicate data flowing from Source to Destination. The convention for Search, given data flows both ways (query parameters vs results), is to have the Source as the initiator of the Search Transaction, and the Destination the responder to the Search transaction. AuditEvent.agent.authorization (authorization) is equivalent to Extension.extension:authorization (R5: Allowable authorization for this agent) Element `AuditEvent.agent.authorization` is mapped to FHIR R4 element `AuditEvent.agent.purposeOfUse` as `Equivalent`. Use AuditEvent.agent.authorization when you know that is specific to the agent, otherwise use AuditEvent.authorization. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to Alternate Referenceversion: 5.2.0) Source Code Relationship Target Code Comment AuditEvent.agent.who (who) is equivalent to Extension.extension:who Element `AuditEvent.agent.who` is mapped to FHIR R4 element `AuditEvent.agent.who` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `AuditEvent.agent.who` with unmapped reference targets: CareTeam. Where a User ID is available it will go into who.identifier. Where a name of the user (human readable) it will go into who.display. Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: site additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.source.site (site) is equivalent to Extension (R5: site additional types) Element `AuditEvent.source.site` is mapped to FHIR R4 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. Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: type additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.source.type (type) is equivalent to Extension (R5: type additional types) Element `AuditEvent.source.type` is mapped to FHIR R4 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. Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: role additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.role (role) is equivalent to Extension (R5: role additional types) Element `AuditEvent.entity.role` is mapped to FHIR R4 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. Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: securityLabel additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.securityLabel (securityLabel) is equivalent to Extension (R5: securityLabel additional types) Element `AuditEvent.entity.securityLabel` is mapped to FHIR R4 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. Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: type additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.detail.type (type) is equivalent to Extension (R5: type additional types) Element `AuditEvent.entity.detail.type` is mapped to FHIR R4 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. Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|5.0.0 to R5: value additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.detail.value[x] (value[x]) is equivalent to Extension (R5: value additional types) Element `AuditEvent.entity.detail.value[x]` is mapped to FHIR R4 element `AuditEvent.entity.detail.value[x]` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.entity.detail.value[x]` do not cover the following types: boolean, CodeableConcept, dateTime, integer, Period, Quantity, Range, Ratio, time. 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`.
Cross-version mapping for FHIR R5 AuditEvent to FHIR R4 AuditEvent
This ConceptMap represents cross-version mappings for elements from a FHIR R5 AuditEvent to FHIR R4.
Element `AuditEvent.meta` is mapped to FHIR R4 element `AuditEvent.meta` as `Equivalent`.
Element `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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
Element `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).
Element `AuditEvent.text` is mapped to FHIR R4 element `AuditEvent.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Element `AuditEvent.contained` is mapped to FHIR R4 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 `AuditEvent.category` is mapped to FHIR R4 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.
Element `AuditEvent.code` is mapped to FHIR R4 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.
Element `AuditEvent.action` is mapped to FHIR R4 element `AuditEvent.action` as `Equivalent`.
Element `AuditEvent.occurred[x]` is mapped to FHIR R4 element `AuditEvent.period` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.occurred[x]` do not cover the following types: dateTime. The mappings for `AuditEvent.occurred[x]` do not cover the following types based on type expansion: value. The time or period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.
Element `AuditEvent.recorded` 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.
Element `AuditEvent.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.
Element `AuditEvent.authorization` is mapped to FHIR R4 element `AuditEvent.purposeOfEvent` as `Equivalent`. Use AuditEvent.agent.authorization when you know that it is specific to the agent, otherwise use AuditEvent.authorization. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.
Element `AuditEvent.agent` is mapped to FHIR R4 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. When a network are used in an event being recorded, there should be distinct agent elements for the known actors using the network. The agent with a network detail would be the responsible agent for use of that network.
Element `AuditEvent.agent.type` is mapped to FHIR R4 element `AuditEvent.agent.type` as `Equivalent`. For example: assembler, author, prescriber, signer, investigator, etc.
Element `AuditEvent.agent.role` is mapped to FHIR R4 element `AuditEvent.agent.role` as `Equivalent`. For example: Chief-of-Radiology, Nurse, Physician, Medical-Student, etc.
Element `AuditEvent.agent.who` is mapped to FHIR R4 element `AuditEvent.agent.who` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `AuditEvent.agent.who` with unmapped reference targets: CareTeam. Where a User ID is available it will go into who.identifier. Where a name of the user (human readable) it will go into who.display.
Element `AuditEvent.agent.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 agent as the initiator.
Element `AuditEvent.agent.location` is mapped to FHIR R4 element `AuditEvent.agent.location` as `Equivalent`.
Element `AuditEvent.agent.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.
Element `AuditEvent.agent.network[x]` is mapped to FHIR R4 element `AuditEvent.agent.network` as `Equivalent`. When remote network endpoint is known, another agent representing the remote agent would indicate the remote network endpoint used. Convention is to indicate data flowing from Source to Destination. The convention for Search, given data flows both ways (query parameters vs results), is to have the Source as the initiator of the Search Transaction, and the Destination the responder to the Search transaction.
Element `AuditEvent.agent.authorization` is mapped to FHIR R4 element `AuditEvent.agent.purposeOfUse` as `Equivalent`. Use AuditEvent.agent.authorization when you know that is specific to the agent, otherwise use AuditEvent.authorization. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.
Element `AuditEvent.source` is mapped to FHIR R4 element `AuditEvent.source` as `Equivalent`. Events are reported by the actor that detected them. This may be one of the participating actors, but may also be different. The actor may be a human such as a medical-records clerk disclosing data manually, that clerk would be the source for the record of disclosure.
Element `AuditEvent.source.site` is mapped to FHIR R4 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.
Element `AuditEvent.source.observer` is mapped to FHIR R4 element `AuditEvent.source.observer` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `AuditEvent.source.observer` with unmapped reference targets: CareTeam.
Element `AuditEvent.source.type` is mapped to FHIR R4 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.
Element `AuditEvent.entity` is mapped to FHIR R4 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.
Element `AuditEvent.entity.what` is mapped to FHIR R4 element `AuditEvent.entity.what` as `Equivalent`. Use .what.display when all you have is a string (e.g. ParticipantObjectName).
Element `AuditEvent.entity.role` is mapped to FHIR R4 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.
Element `AuditEvent.entity.securityLabel` is mapped to FHIR R4 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.
Element `AuditEvent.entity.query` is mapped to FHIR R4 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, 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. The DICOM AuditMessage schema does not support both .name and .query being populated.
Element `AuditEvent.entity.detail` is mapped to FHIR R4 element `AuditEvent.entity.detail` as `Equivalent`.
Element `AuditEvent.entity.detail.type` is mapped to FHIR R4 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.
Element `AuditEvent.entity.detail.value[x]` is mapped to FHIR R4 element `AuditEvent.entity.detail.value[x]` as `SourceIsBroaderThanTarget`. The mappings for `AuditEvent.entity.detail.value[x]` do not cover the following types: boolean, CodeableConcept, dateTime, integer, Period, Quantity, Range, Ratio, time. 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`.
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 R4. Typically, this is because the element has been added (is a new element). ATNA will map this to the SYSLOG PRI element.
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 R4. 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.
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 R4. 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.
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 R4. Typically, this is because the element has been added (is a new element).
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 R4. Typically, this is because the element has been added (is a new element).
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 R4. Typically, this is because the element has been added (is a new element).