FHIR IG analytics| Package | hl7.fhir.uv.xver-r4b.r4 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R4B-AuditEvent-element-map-to-R4.json |
| FHIR Version | R4 |
| Source | http://hl7.org/fhir/uv/xver-r4b.r4/0.1.0/ConceptMap-R4B-AuditEvent-element-map-to-R4.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R4B-AuditEvent-element-map-to-R4 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:03:45.9219083-05:00 |
| Name | R4BAuditEventElementMapToR4 |
| Title | Cross-version mapping for FHIR R4B AuditEvent to FHIR R4 AuditEvent |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R4B AuditEvent to FHIR R4. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R4B-AuditEvent-element-map-to-R4
Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/AuditEvent|4.3.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 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 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 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.type (type) | is equivalent to | AuditEvent.type | Element `AuditEvent.type` is mapped to FHIR R4 element `AuditEvent.type` as `Equivalent`. |
| AuditEvent.subtype (subtype) | is equivalent to | AuditEvent.subtype | Element `AuditEvent.subtype` is mapped to FHIR R4 element `AuditEvent.subtype` as `Equivalent`. |
| AuditEvent.action (action) | is equivalent to | AuditEvent.action | Element `AuditEvent.action` is mapped to FHIR R4 element `AuditEvent.action` as `Equivalent`. |
| AuditEvent.period (period) | is equivalent to | AuditEvent.period | Element `AuditEvent.period` is mapped to FHIR R4 element `AuditEvent.period` as `Equivalent`. The 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) | is equivalent to | 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.outcomeDesc (outcomeDesc) | is equivalent to | AuditEvent.outcomeDesc | Element `AuditEvent.outcomeDesc` is mapped to FHIR R4 element `AuditEvent.outcomeDesc` as `Equivalent`. |
| AuditEvent.purposeOfEvent (purposeOfEvent) | is equivalent to | AuditEvent.purposeOfEvent | Element `AuditEvent.purposeOfEvent` is mapped to FHIR R4 element `AuditEvent.purposeOfEvent` 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) | 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. |
| 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`. |
| 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`. 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 R4 element `AuditEvent.agent.who` as `Equivalent`. Where a User ID is available it will go into who.identifier. |
| AuditEvent.agent.altId (altId) | is equivalent to | AuditEvent.agent.altId | Element `AuditEvent.agent.altId` is mapped to FHIR R4 element `AuditEvent.agent.altId` as `Equivalent`. |
| AuditEvent.agent.name (name) | is equivalent to | AuditEvent.agent.name | Element `AuditEvent.agent.name` is mapped to FHIR R4 element `AuditEvent.agent.name` as `Equivalent`. |
| 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.media (media) | is equivalent to | AuditEvent.agent.media | Element `AuditEvent.agent.media` is mapped to FHIR R4 element `AuditEvent.agent.media` as `Equivalent`. |
| AuditEvent.agent.network (network) | maps to wider concept | AuditEvent.agent.network | Element `AuditEvent.agent.network` is mapped to FHIR R4 element `AuditEvent.agent.network` as `Equivalent`. |
| AuditEvent.agent.network.address (address) | is equivalent to | AuditEvent.agent.network.address | Element `AuditEvent.agent.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.agent.network.type (type) | is equivalent to | AuditEvent.agent.network.type | Element `AuditEvent.agent.network.type` is mapped to FHIR R4 element `AuditEvent.agent.network.type` as `Equivalent`. |
| AuditEvent.agent.purposeOfUse (purposeOfUse) | is equivalent to | AuditEvent.agent.purposeOfUse | Element `AuditEvent.agent.purposeOfUse` is mapped to FHIR R4 element `AuditEvent.agent.purposeOfUse` 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) | maps to wider concept | AuditEvent.source | Element `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 to | AuditEvent.source.site | Element `AuditEvent.source.site` is mapped to FHIR R4 element `AuditEvent.source.site` as `Equivalent`. |
| AuditEvent.source.observer (observer) | is equivalent to | AuditEvent.source.observer | Element `AuditEvent.source.observer` is mapped to FHIR R4 element `AuditEvent.source.observer` as `Equivalent`. |
| AuditEvent.source.type (type) | is equivalent to | AuditEvent.source.type | Element `AuditEvent.source.type` is mapped to FHIR R4 element `AuditEvent.source.type` as `Equivalent`. |
| 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`. |
| AuditEvent.entity.type (type) | is equivalent to | AuditEvent.entity.type | Element `AuditEvent.entity.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 entity. |
| AuditEvent.entity.role (role) | is equivalent to | AuditEvent.entity.role | Element `AuditEvent.entity.role` is mapped to FHIR R4 element `AuditEvent.entity.role` as `Equivalent`. |
| AuditEvent.entity.lifecycle (lifecycle) | is equivalent to | AuditEvent.entity.lifecycle | Element `AuditEvent.entity.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.entity.securityLabel (securityLabel) | is equivalent to | AuditEvent.entity.securityLabel | Element `AuditEvent.entity.securityLabel` is mapped to FHIR R4 element `AuditEvent.entity.securityLabel` as `Equivalent`. Copied from entity meta security tags. |
| AuditEvent.entity.name (name) | is equivalent to | AuditEvent.entity.name | Element `AuditEvent.entity.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 entity identifiers (patient number, medical record number, encounter number, etc.) have been used. |
| AuditEvent.entity.description (description) | is equivalent to | AuditEvent.entity.description | Element `AuditEvent.entity.description` is mapped to FHIR R4 element `AuditEvent.entity.description` as `Equivalent`. |
| 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, 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) | 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) | is equivalent to | AuditEvent.entity.detail.type | Element `AuditEvent.entity.detail.type` is mapped to FHIR R4 element `AuditEvent.entity.detail.type` as `Equivalent`. |
| 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 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`. 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. |
FHIR
FHIRsmith{
"resourceType": "ConceptMap",
"id": "R4B-AuditEvent-element-map-to-R4",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r4"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-AuditEvent-element-map-to-R4",
"version": "0.1.0",
"name": "R4BAuditEventElementMapToR4",
"title": "Cross-version mapping for FHIR R4B AuditEvent to FHIR R4 AuditEvent",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:03:45.9219083-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4B AuditEvent to FHIR R4.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceCanonical": "http://hl7.org/fhir/4.3",
"targetUri": "http://hl7.org/fhir/4.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/AuditEvent",
"sourceVersion": "4.3.0",
"target": "http://hl7.org/fhir/StructureDefinition/AuditEvent",
"targetVersion": "4.0.1",
"element": [
{
"code": "AuditEvent.meta",
"display": "meta",
"target": [
{
"code": "AuditEvent.meta",
"display": "AuditEvent.meta",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.meta` is mapped to FHIR R4 element `AuditEvent.meta` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.implicitRules",
"display": "implicitRules",
"target": [
{
"code": "AuditEvent.implicitRules",
"display": "AuditEvent.implicitRules",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.implicitRules` is mapped to FHIR R4 element `AuditEvent.implicitRules` as `Equivalent`.\nAsserting 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."
}
]
},
{
"code": "AuditEvent.language",
"display": "language",
"target": [
{
"code": "AuditEvent.language",
"display": "AuditEvent.language",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.language` is mapped to FHIR R4 element `AuditEvent.language` as `Equivalent`.\nLanguage 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)."
}
]
},
{
"code": "AuditEvent.text",
"display": "text",
"target": [
{
"code": "AuditEvent.text",
"display": "AuditEvent.text",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.text` is mapped to FHIR R4 element `AuditEvent.text` as `Equivalent`.\nContained 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."
}
]
},
{
"code": "AuditEvent.contained",
"display": "contained",
"target": [
{
"code": "AuditEvent.contained",
"display": "AuditEvent.contained",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.contained` is mapped to FHIR R4 element `AuditEvent.contained` as `Equivalent`.\nThis 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."
}
]
},
{
"code": "AuditEvent.type",
"display": "type",
"target": [
{
"code": "AuditEvent.type",
"display": "AuditEvent.type",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.type` is mapped to FHIR R4 element `AuditEvent.type` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.subtype",
"display": "subtype",
"target": [
{
"code": "AuditEvent.subtype",
"display": "AuditEvent.subtype",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.subtype` is mapped to FHIR R4 element `AuditEvent.subtype` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.action",
"display": "action",
"target": [
{
"code": "AuditEvent.action",
"display": "AuditEvent.action",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.action` is mapped to FHIR R4 element `AuditEvent.action` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.period",
"display": "period",
"target": [
{
"code": "AuditEvent.period",
"display": "AuditEvent.period",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.period` is mapped to FHIR R4 element `AuditEvent.period` as `Equivalent`.\nThe period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time."
}
]
},
{
"code": "AuditEvent.recorded",
"display": "recorded",
"target": [
{
"code": "AuditEvent.recorded",
"display": "AuditEvent.recorded",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.recorded` is mapped to FHIR R4 element `AuditEvent.recorded` as `Equivalent`.\nIn a distributed system, some sort of common time base (e.g. an NTP [RFC1305] server) is a good implementation tactic."
}
]
},
{
"code": "AuditEvent.outcome",
"display": "outcome",
"target": [
{
"code": "AuditEvent.outcome",
"display": "AuditEvent.outcome",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.outcome` is mapped to FHIR R4 element `AuditEvent.outcome` as `Equivalent`.\nIn some cases a \"success\" may be partial, for example, an incomplete or interrupted transfer of a radiological study. For the purpose of establishing accountability, these distinctions are not relevant."
}
]
},
{
"code": "AuditEvent.outcomeDesc",
"display": "outcomeDesc",
"target": [
{
"code": "AuditEvent.outcomeDesc",
"display": "AuditEvent.outcomeDesc",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.outcomeDesc` is mapped to FHIR R4 element `AuditEvent.outcomeDesc` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.purposeOfEvent",
"display": "purposeOfEvent",
"target": [
{
"code": "AuditEvent.purposeOfEvent",
"display": "AuditEvent.purposeOfEvent",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.purposeOfEvent` is mapped to FHIR R4 element `AuditEvent.purposeOfEvent` as `Equivalent`.\nUse AuditEvent.agent.purposeOfUse when you know that it is specific to the agent, otherwise use AuditEvent.purposeOfEvent. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why."
}
]
},
{
"code": "AuditEvent.agent",
"display": "agent",
"target": [
{
"code": "AuditEvent.agent",
"display": "AuditEvent.agent",
"equivalence": "wider",
"comment": "Element `AuditEvent.agent` is mapped to FHIR R4 element `AuditEvent.agent` as `Equivalent`.\nSeveral agents may be associated (i.e. have some responsibility for an activity) with an event or activity.\n\nFor example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity."
}
]
},
{
"code": "AuditEvent.agent.type",
"display": "type",
"target": [
{
"code": "AuditEvent.agent.type",
"display": "AuditEvent.agent.type",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.type` is mapped to FHIR R4 element `AuditEvent.agent.type` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.agent.role",
"display": "role",
"target": [
{
"code": "AuditEvent.agent.role",
"display": "AuditEvent.agent.role",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.role` is mapped to FHIR R4 element `AuditEvent.agent.role` as `Equivalent`.\nShould be roles relevant to the event. Should not be an exhaustive list of roles."
}
]
},
{
"code": "AuditEvent.agent.who",
"display": "who",
"target": [
{
"code": "AuditEvent.agent.who",
"display": "AuditEvent.agent.who",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.who` is mapped to FHIR R4 element `AuditEvent.agent.who` as `Equivalent`.\nWhere a User ID is available it will go into who.identifier."
}
]
},
{
"code": "AuditEvent.agent.altId",
"display": "altId",
"target": [
{
"code": "AuditEvent.agent.altId",
"display": "AuditEvent.agent.altId",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.altId` is mapped to FHIR R4 element `AuditEvent.agent.altId` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.agent.name",
"display": "name",
"target": [
{
"code": "AuditEvent.agent.name",
"display": "AuditEvent.agent.name",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.name` is mapped to FHIR R4 element `AuditEvent.agent.name` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.agent.requestor",
"display": "requestor",
"target": [
{
"code": "AuditEvent.agent.requestor",
"display": "AuditEvent.agent.requestor",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.requestor` is mapped to FHIR R4 element `AuditEvent.agent.requestor` as `Equivalent`.\nThere can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator."
}
]
},
{
"code": "AuditEvent.agent.location",
"display": "location",
"target": [
{
"code": "AuditEvent.agent.location",
"display": "AuditEvent.agent.location",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.location` is mapped to FHIR R4 element `AuditEvent.agent.location` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.agent.policy",
"display": "policy",
"target": [
{
"code": "AuditEvent.agent.policy",
"display": "AuditEvent.agent.policy",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.policy` is mapped to FHIR R4 element `AuditEvent.agent.policy` as `Equivalent`.\nFor example: Where an OAuth token authorizes, the unique identifier from the OAuth token is placed into the policy element Where a policy engine (e.g. XACML) holds policy logic, the unique policy identifier is placed into the policy element."
}
]
},
{
"code": "AuditEvent.agent.media",
"display": "media",
"target": [
{
"code": "AuditEvent.agent.media",
"display": "AuditEvent.agent.media",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.media` is mapped to FHIR R4 element `AuditEvent.agent.media` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.agent.network",
"display": "network",
"target": [
{
"code": "AuditEvent.agent.network",
"display": "AuditEvent.agent.network",
"equivalence": "wider",
"comment": "Element `AuditEvent.agent.network` is mapped to FHIR R4 element `AuditEvent.agent.network` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.agent.network.address",
"display": "address",
"target": [
{
"code": "AuditEvent.agent.network.address",
"display": "AuditEvent.agent.network.address",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.network.address` is mapped to FHIR R4 element `AuditEvent.agent.network.address` as `Equivalent`.\nThis could be a device id, IP address or some other identifier associated with a device."
}
]
},
{
"code": "AuditEvent.agent.network.type",
"display": "type",
"target": [
{
"code": "AuditEvent.agent.network.type",
"display": "AuditEvent.agent.network.type",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.network.type` is mapped to FHIR R4 element `AuditEvent.agent.network.type` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.agent.purposeOfUse",
"display": "purposeOfUse",
"target": [
{
"code": "AuditEvent.agent.purposeOfUse",
"display": "AuditEvent.agent.purposeOfUse",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.agent.purposeOfUse` is mapped to FHIR R4 element `AuditEvent.agent.purposeOfUse` as `Equivalent`.\nUse AuditEvent.agent.purposeOfUse when you know that is specific to the agent, otherwise use AuditEvent.purposeOfEvent. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why."
}
]
},
{
"code": "AuditEvent.source",
"display": "source",
"target": [
{
"code": "AuditEvent.source",
"display": "AuditEvent.source",
"equivalence": "wider",
"comment": "Element `AuditEvent.source` is mapped to FHIR R4 element `AuditEvent.source` as `Equivalent`.\nSince multi-tier, distributed, or composite applications make source identification ambiguous, this collection of fields may repeat for each application or process actively involved in the event. For example, multiple value-sets can identify participating web servers, application processes, and database server threads in an n-tier distributed application. Passive event participants (e.g. low-level network transports) need not be identified."
}
]
},
{
"code": "AuditEvent.source.site",
"display": "site",
"target": [
{
"code": "AuditEvent.source.site",
"display": "AuditEvent.source.site",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.source.site` is mapped to FHIR R4 element `AuditEvent.source.site` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.source.observer",
"display": "observer",
"target": [
{
"code": "AuditEvent.source.observer",
"display": "AuditEvent.source.observer",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.source.observer` is mapped to FHIR R4 element `AuditEvent.source.observer` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.source.type",
"display": "type",
"target": [
{
"code": "AuditEvent.source.type",
"display": "AuditEvent.source.type",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.source.type` is mapped to FHIR R4 element `AuditEvent.source.type` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.entity",
"display": "entity",
"target": [
{
"code": "AuditEvent.entity",
"display": "AuditEvent.entity",
"equivalence": "wider",
"comment": "Element `AuditEvent.entity` is mapped to FHIR R4 element `AuditEvent.entity` as `Equivalent`.\nRequired unless the values for event identification, agent identification, and audit source identification are sufficient to document the entire auditable event. Because events may have more than one entity, this group can be a repeating set of values."
}
]
},
{
"code": "AuditEvent.entity.what",
"display": "what",
"target": [
{
"code": "AuditEvent.entity.what",
"display": "AuditEvent.entity.what",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.what` is mapped to FHIR R4 element `AuditEvent.entity.what` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.entity.type",
"display": "type",
"target": [
{
"code": "AuditEvent.entity.type",
"display": "AuditEvent.entity.type",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.type` is mapped to FHIR R4 element `AuditEvent.entity.type` as `Equivalent`.\nThis value is distinct from the user's role or any user relationship to the entity."
}
]
},
{
"code": "AuditEvent.entity.role",
"display": "role",
"target": [
{
"code": "AuditEvent.entity.role",
"display": "AuditEvent.entity.role",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.role` is mapped to FHIR R4 element `AuditEvent.entity.role` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.entity.lifecycle",
"display": "lifecycle",
"target": [
{
"code": "AuditEvent.entity.lifecycle",
"display": "AuditEvent.entity.lifecycle",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.lifecycle` is mapped to FHIR R4 element `AuditEvent.entity.lifecycle` as `Equivalent`.\nThis can be used to provide an audit trail for data, over time, as it passes through the system."
}
]
},
{
"code": "AuditEvent.entity.securityLabel",
"display": "securityLabel",
"target": [
{
"code": "AuditEvent.entity.securityLabel",
"display": "AuditEvent.entity.securityLabel",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.securityLabel` is mapped to FHIR R4 element `AuditEvent.entity.securityLabel` as `Equivalent`.\nCopied from entity meta security tags."
}
]
},
{
"code": "AuditEvent.entity.name",
"display": "name",
"target": [
{
"code": "AuditEvent.entity.name",
"display": "AuditEvent.entity.name",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.name` is mapped to FHIR R4 element `AuditEvent.entity.name` as `Equivalent`.\nThis 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."
}
]
},
{
"code": "AuditEvent.entity.description",
"display": "description",
"target": [
{
"code": "AuditEvent.entity.description",
"display": "AuditEvent.entity.description",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.description` is mapped to FHIR R4 element `AuditEvent.entity.description` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.entity.query",
"display": "query",
"target": [
{
"code": "AuditEvent.entity.query",
"display": "AuditEvent.entity.query",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.query` is mapped to FHIR R4 element `AuditEvent.entity.query` as `Equivalent`.\nThe meaning and secondary-encoding of the content of base64 encoded blob is specific to the AuditEvent.type, AuditEvent.subtype, AuditEvent.entity.type, and AuditEvent.entity.role. The base64 is a general-use and safe container for event specific data blobs regardless of the encoding used by the transaction being recorded. An AuditEvent consuming application must understand the event it is consuming and the formats used by the event. For example, if auditing an Oracle network database access, the Oracle formats must be understood as they will be simply encoded in the base64binary blob."
}
]
},
{
"code": "AuditEvent.entity.detail",
"display": "detail",
"target": [
{
"code": "AuditEvent.entity.detail",
"display": "AuditEvent.entity.detail",
"equivalence": "wider",
"comment": "Element `AuditEvent.entity.detail` is mapped to FHIR R4 element `AuditEvent.entity.detail` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.entity.detail.type",
"display": "type",
"target": [
{
"code": "AuditEvent.entity.detail.type",
"display": "AuditEvent.entity.detail.type",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.detail.type` is mapped to FHIR R4 element `AuditEvent.entity.detail.type` as `Equivalent`."
}
]
},
{
"code": "AuditEvent.entity.detail.value[x]",
"display": "value[x]",
"target": [
{
"code": "AuditEvent.entity.detail.value[x]",
"display": "AuditEvent.entity.detail.value[x]",
"equivalence": "equivalent",
"comment": "Element `AuditEvent.entity.detail.value[x]` is mapped to FHIR R4 element `AuditEvent.entity.detail.value[x]` as `Equivalent`.\nThe 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`.\nThe 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."
}
]
}
]
}
]
}