Extensions for Using Data Elements from FHIR R4B in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR STU3 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4B-EventDefinition-element-map-to-R3 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R4BEventDefinitionElementMapToR3 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R4B EventDefinition to FHIR STU3.
Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/3.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.meta (meta) | is equivalent to | Basic.meta | Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `EventDefinition.meta` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
| EventDefinition.implicitRules (implicitRules) | is equivalent to | Basic.implicitRules | Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `EventDefinition.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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. |
| EventDefinition.language (language) | is equivalent to | Basic.language | Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `EventDefinition.language` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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). |
| EventDefinition.text (text) | is equivalent to | Basic.text | Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `EventDefinition.text` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.text` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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. |
| EventDefinition.contained (contained) | is equivalent to | Basic.contained | Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `EventDefinition.contained` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.contained` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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. |
| EventDefinition.identifier (identifier) | is equivalent to | Basic.identifier | Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `EventDefinition.identifier` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this event definition outside of FHIR, where it is not possible to use the logical URI. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Canonical identifier for this event definition, represented as a URI (globally unique) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.url (url) | maps to wider concept | Extension (R4B: Canonical identifier for this event definition, represented as a URI (globally unique) (new)) | Element `EventDefinition.url` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.url` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Business version of the event definition (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.version (version) | maps to wider concept | Extension (R4B: Business version of the event definition (new)) | Element `EventDefinition.version` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). There may be different event definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the event definition with the format [url]|[version]. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Name for this event definition (computer friendly) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.name (name) | maps to wider concept | Extension (R4B: Name for this event definition (computer friendly) (new)) | Element `EventDefinition.name` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Name for this event definition (human friendly) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.title (title) | maps to wider concept | Extension (R4B: Name for this event definition (human friendly) (new)) | Element `EventDefinition.title` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Subordinate title of the event definition (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.subtitle (subtitle) | maps to wider concept | Extension (R4B: Subordinate title of the event definition (new)) | Element `EventDefinition.subtitle` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.subtitle` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: draft | active | retired | unknown (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.status (status) | maps to wider concept | Extension (R4B: draft | active | retired | unknown (new)) | Element `EventDefinition.status` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of event definitions that are appropriate for use versus not. |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: For testing purposes, not real usage (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.experimental (experimental) | maps to wider concept | Extension (R4B: For testing purposes, not real usage (new)) | Element `EventDefinition.experimental` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.experimental` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of event definitions that are appropriate for use versus not. |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Type of individual the event definition is focused on (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.subject[x] (subject[x]) | maps to wider concept | Extension (R4B: Type of individual the event definition is focused on (new)) | Element `EventDefinition.subject[x]` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.subject[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Date last changed (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.date (date) | maps to wider concept | Extension (R4B: Date last changed (new)) | Element `EventDefinition.date` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.date` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the event definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. |
Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Name of the publisher (organization or individual) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.publisher (publisher) | maps to wider concept | Extension (R4B: Name of the publisher (organization or individual) (new)) | Element `EventDefinition.publisher` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.publisher` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Usually an organization but may be an individual. The publisher (or steward) of the event definition is the organization or individual primarily responsible for the maintenance and upkeep of the event definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the event definition. This item SHOULD be populated unless the information is available from context. |
Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Contact details for the publisher (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.contact (contact) | maps to wider concept | Extension (R4B: Contact details for the publisher (new)) | Element `EventDefinition.contact` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.contact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). May be a web site, an email address, a telephone number, etc. |
Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Natural language description of the event definition (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.description (description) | maps to wider concept | Extension (R4B: Natural language description of the event definition (new)) | Element `EventDefinition.description` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This description can be used to capture details such as why the event definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the event definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the event definition is presumed to be the predominant language in the place the event definition was created). |
Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: The context that the content is intended to support (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.useContext (useContext) | maps to wider concept | Extension (R4B: The context that the content is intended to support (new)) | Element `EventDefinition.useContext` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.useContext` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. |
Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Intended jurisdiction for event definition (if applicable) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.jurisdiction (jurisdiction) | maps to wider concept | Extension (R4B: Intended jurisdiction for event definition (if applicable) (new)) | Element `EventDefinition.jurisdiction` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). It may be possible for the event definition to be used in jurisdictions other than those for which it was originally designed or intended. |
Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Why this event definition is defined (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.purpose (purpose) | maps to wider concept | Extension (R4B: Why this event definition is defined (new)) | Element `EventDefinition.purpose` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.purpose` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the event definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this event definition. |
Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Describes the clinical usage of the event definition (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.usage (usage) | maps to wider concept | Extension (R4B: Describes the clinical usage of the event definition (new)) | Element `EventDefinition.usage` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.usage` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Use and/or publishing restrictions (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.copyright (copyright) | maps to wider concept | Extension (R4B: Use and/or publishing restrictions (new)) | Element `EventDefinition.copyright` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.copyright` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: When the event definition was approved by publisher (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.approvalDate (approvalDate) | maps to wider concept | Extension (R4B: When the event definition was approved by publisher (new)) | Element `EventDefinition.approvalDate` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.approvalDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The 'date' element may be more recent than the approval date because of minor changes or editorial corrections. |
Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: When the event definition was last reviewed (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.lastReviewDate (lastReviewDate) | maps to wider concept | Extension (R4B: When the event definition was last reviewed (new)) | Element `EventDefinition.lastReviewDate` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.lastReviewDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If specified, this date follows the original approval date. |
Group 21 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: When the event definition is expected to be used (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.effectivePeriod (effectivePeriod) | maps to wider concept | Extension (R4B: When the event definition is expected to be used (new)) | Element `EventDefinition.effectivePeriod` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.effectivePeriod` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The effective period for a event definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015. |
Group 22 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: E.g. Education, Treatment, Assessment, etc. (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.topic (topic) | maps to wider concept | Extension (R4B: E.g. Education, Treatment, Assessment, etc. (new)) | Element `EventDefinition.topic` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.topic` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 23 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Who authored the content (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.author (author) | maps to wider concept | Extension (R4B: Who authored the content (new)) | Element `EventDefinition.author` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.author` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). While the source element matches Basic element path `` (``), the definitions are not compatible (source: `ContactDetail`:0..* -> basic: `Reference(http://hl7.org/fhir/StructureDefinition/Practitioner,http://hl7.org/fhir/StructureDefinition/Patient,http://hl7.org/fhir/StructureDefinition/RelatedPerson)`:0..1). |
Group 24 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Who edited the content (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.editor (editor) | maps to wider concept | Extension (R4B: Who edited the content (new)) | Element `EventDefinition.editor` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.editor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 25 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Who reviewed the content (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.reviewer (reviewer) | maps to wider concept | Extension (R4B: Who reviewed the content (new)) | Element `EventDefinition.reviewer` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.reviewer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 26 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Who endorsed the content (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.endorser (endorser) | maps to wider concept | Extension (R4B: Who endorsed the content (new)) | Element `EventDefinition.endorser` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.endorser` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 27 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: Additional documentation, citations, etc. (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.relatedArtifact (relatedArtifact) | maps to wider concept | Extension (R4B: Additional documentation, citations, etc. (new)) | Element `EventDefinition.relatedArtifact` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.relatedArtifact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Each related resource is either an attachment, or a reference to another resource, but not both. |
Group 28 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.3.0 to R4B: "when" the event occurs (multiple = 'or') (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| EventDefinition.trigger (trigger) | maps to wider concept | Extension (R4B: "when" the event occurs (multiple = 'or') (new)) | Element `EventDefinition.trigger` is not mapped to FHIR STU3, since FHIR R4B `EventDefinition` is not mapped. Element `EventDefinition.trigger` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4b.r3#0.1.0 based on FHIR 3.0.2. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change