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 and the html lang attribute). AuditEvent.text (text) is equivalent to AuditEvent.text 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. AuditEvent.contained (contained) is equivalent to AuditEvent.contained 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. AuditEvent.type (type) is narrower than AuditEvent.category Element `AuditEvent.type` is mapped to FHIR R5 element `AuditEvent.category` as `SourceIsNarrowerThanTarget`. AuditEvent.subtype (subtype) is equivalent to AuditEvent.code Element `AuditEvent.subtype` is mapped to FHIR R5 element `AuditEvent.code` as `RelatedTo`. AuditEvent.action (action) is equivalent to AuditEvent.action Element `AuditEvent.action` is mapped to FHIR R5 element `AuditEvent.action` as `Equivalent`. AuditEvent.recorded (recorded) is equivalent to AuditEvent.recorded 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. AuditEvent.outcome (outcome) is related to AuditEvent.outcome.code 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. AuditEvent.purposeOfEvent (purposeOfEvent) is equivalent to AuditEvent.authorization 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. AuditEvent.agent (agent) is broader than AuditEvent.agent 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. AuditEvent.agent.type (type) is equivalent to AuditEvent.agent.type Element `AuditEvent.agent.type` is mapped to FHIR R5 element `AuditEvent.agent.type` as `Equivalent`. AuditEvent.agent.role (role) is equivalent to AuditEvent.agent.role 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. AuditEvent.agent.who (who) is equivalent to AuditEvent.agent.who 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. AuditEvent.agent.requestor (requestor) is equivalent to AuditEvent.agent.requestor 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. AuditEvent.agent.location (location) is equivalent to AuditEvent.agent.location Element `AuditEvent.agent.location` is mapped to FHIR R5 element `AuditEvent.agent.location` as `Equivalent`. AuditEvent.agent.policy (policy) is equivalent to AuditEvent.agent.policy 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. AuditEvent.agent.network (network) is broader than AuditEvent.agent.network[x] 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`. AuditEvent.agent.purposeOfUse (purposeOfUse) is equivalent to AuditEvent.agent.authorization 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. AuditEvent.source (source) is broader than AuditEvent.source 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. AuditEvent.source.site (site) is broader than AuditEvent.source.site 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. AuditEvent.source.observer (observer) is equivalent to AuditEvent.source.observer Element `AuditEvent.source.observer` is mapped to FHIR R5 element `AuditEvent.source.observer` as `Equivalent`. AuditEvent.source.type (type) is equivalent to AuditEvent.source.type Element `AuditEvent.source.type` is mapped to FHIR R5 element `AuditEvent.source.type` as `SourceIsNarrowerThanTarget`. AuditEvent.entity (entity) is broader than AuditEvent.entity 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. AuditEvent.entity.what (what) is equivalent to AuditEvent.entity.what Element `AuditEvent.entity.what` is mapped to FHIR R5 element `AuditEvent.entity.what` as `Equivalent`. AuditEvent.entity.role (role) is equivalent to AuditEvent.entity.role Element `AuditEvent.entity.role` is mapped to FHIR R5 element `AuditEvent.entity.role` as `SourceIsNarrowerThanTarget`. AuditEvent.entity.securityLabel (securityLabel) is equivalent to AuditEvent.entity.securityLabel Element `AuditEvent.entity.securityLabel` is mapped to FHIR R5 element `AuditEvent.entity.securityLabel` as `SourceIsNarrowerThanTarget`. Copied from entity meta security tags. AuditEvent.entity.query (query) is equivalent to AuditEvent.entity.query 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. AuditEvent.entity.detail (detail) is broader than AuditEvent.entity.detail Element `AuditEvent.entity.detail` is mapped to FHIR R5 element `AuditEvent.entity.detail` as `Equivalent`. AuditEvent.entity.detail.type (type) is broader than AuditEvent.entity.detail.type 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. AuditEvent.entity.detail.value[x] (value[x]) is equivalent to AuditEvent.entity.detail.value[x] 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. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: When the activity occurred (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.period (period) is equivalent to Extension (R4: When the activity occurred (new)) 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. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: outcome additional codesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.outcome (outcome) is broader than Extension (R4: outcome additional codes) 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. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Description of the event outcome (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.outcomeDesc (outcomeDesc) is equivalent to Extension (R4: Description of the event outcome (new)) 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). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Alternative User identity (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.agent.altId (altId) is equivalent to Extension (R4: Alternative User identity (new)) 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). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Human friendly name for the agent (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.agent.name (name) is equivalent to Extension (R4: Human friendly name for the agent (new)) 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). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Type of media (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.agent.media (media) is equivalent to Extension (R4: Type of media (new)) 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). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Identifier for the network access point of the user device (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.agent.network.address (address) is equivalent to Extension (R4: Identifier for the network access point of the user device (new)) 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. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: The type of network access point (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.agent.network.type (type) is equivalent to Extension (R4: The type of network access point (new)) 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`. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: site additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.source.site (site) is equivalent to Extension (R4: site additional types) 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. Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Type of entity involved (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.type (type) is equivalent to Extension (R4: Type of entity involved (new)) 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. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Life-cycle stage for the entity (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.lifecycle (lifecycle) is equivalent to Extension (R4: Life-cycle stage for the entity (new)) 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. Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Descriptor for entity (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.name (name) is equivalent to Extension (R4: Descriptor for entity (new)) 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. Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: Descriptive text (new)version: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.description (description) is equivalent to Extension (R4: Descriptive text (new)) 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). Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.0.1 to R4: type additional typesversion: 0.1.0) Source Code Relationship Target Code Comment AuditEvent.entity.detail.type (type) is equivalent to Extension (R4: type additional types) 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.
Cross-version mapping for FHIR R4 AuditEvent to FHIR R5 AuditEvent
This ConceptMap represents cross-version mappings for elements from a FHIR R4 AuditEvent to FHIR R5.
Element `AuditEvent.meta` is mapped to FHIR R5 element `AuditEvent.meta` as `Equivalent`.
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 `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 `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 `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 `AuditEvent.type` is mapped to FHIR R5 element `AuditEvent.category` as `SourceIsNarrowerThanTarget`.
Element `AuditEvent.subtype` is mapped to FHIR R5 element `AuditEvent.code` as `RelatedTo`.
Element `AuditEvent.action` is mapped to FHIR R5 element `AuditEvent.action` as `Equivalent`.
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.
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.
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.
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.
Element `AuditEvent.agent.type` is mapped to FHIR R5 element `AuditEvent.agent.type` as `Equivalent`.
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.
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.
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.
Element `AuditEvent.agent.location` is mapped to FHIR R5 element `AuditEvent.agent.location` as `Equivalent`.
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.
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`.
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.
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.
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.
Element `AuditEvent.source.observer` is mapped to FHIR R5 element `AuditEvent.source.observer` as `Equivalent`.
Element `AuditEvent.source.type` is mapped to FHIR R5 element `AuditEvent.source.type` as `SourceIsNarrowerThanTarget`.
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.
Element `AuditEvent.entity.what` is mapped to FHIR R5 element `AuditEvent.entity.what` as `Equivalent`.
Element `AuditEvent.entity.role` is mapped to FHIR R5 element `AuditEvent.entity.role` as `SourceIsNarrowerThanTarget`.
Element `AuditEvent.entity.securityLabel` is mapped to FHIR R5 element `AuditEvent.entity.securityLabel` as `SourceIsNarrowerThanTarget`. Copied from entity meta security tags.
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.
Element `AuditEvent.entity.detail` is mapped to FHIR R5 element `AuditEvent.entity.detail` as `Equivalent`.
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.
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.
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.
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).
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).
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).
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).
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.
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`.
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.
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.
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.
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).