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

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

ConceptMap: R4EventDefinitionElementMapToR4B

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

This ConceptMap represents cross-version mappings for elements from a FHIR R4 EventDefinition to FHIR R4B.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/EventDefinition|4.0.1 to EventDefinitionversion: 4.3.0)

Source CodeRelationshipTarget CodeComment
EventDefinition.meta (meta)is equivalent toEventDefinition.metaElement `EventDefinition.meta` is mapped to FHIR R4B element `EventDefinition.meta` as `Equivalent`.
EventDefinition.implicitRules (implicitRules)is equivalent toEventDefinition.implicitRulesElement `EventDefinition.implicitRules` is mapped to FHIR R4B element `EventDefinition.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.
EventDefinition.language (language)is equivalent toEventDefinition.languageElement `EventDefinition.language` is mapped to FHIR R4B element `EventDefinition.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).
EventDefinition.text (text)is equivalent toEventDefinition.textElement `EventDefinition.text` is mapped to FHIR R4B element `EventDefinition.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.
EventDefinition.contained (contained)is equivalent toEventDefinition.containedElement `EventDefinition.contained` is mapped to FHIR R4B element `EventDefinition.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.
EventDefinition.url (url)is equivalent toEventDefinition.urlElement `EventDefinition.url` is mapped to FHIR R4B element `EventDefinition.url` as `Equivalent`. 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.
EventDefinition.identifier (identifier)is equivalent toEventDefinition.identifierElement `EventDefinition.identifier` is mapped to FHIR R4B element `EventDefinition.identifier` as `Equivalent`. 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.
EventDefinition.version (version)is equivalent toEventDefinition.versionElement `EventDefinition.version` is mapped to FHIR R4B element `EventDefinition.version` as `Equivalent`. 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].
EventDefinition.name (name)is equivalent toEventDefinition.nameElement `EventDefinition.name` is mapped to FHIR R4B element `EventDefinition.name` as `Equivalent`. 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.
EventDefinition.title (title)is equivalent toEventDefinition.titleElement `EventDefinition.title` is mapped to FHIR R4B element `EventDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
EventDefinition.subtitle (subtitle)is equivalent toEventDefinition.subtitleElement `EventDefinition.subtitle` is mapped to FHIR R4B element `EventDefinition.subtitle` as `Equivalent`.
EventDefinition.status (status)is equivalent toEventDefinition.statusElement `EventDefinition.status` is mapped to FHIR R4B element `EventDefinition.status` as `Equivalent`. Allows filtering of event definitions that are appropriate for use versus not.
EventDefinition.experimental (experimental)is equivalent toEventDefinition.experimentalElement `EventDefinition.experimental` is mapped to FHIR R4B element `EventDefinition.experimental` as `Equivalent`. Allows filtering of event definitions that are appropriate for use versus not.
EventDefinition.subject[x] (subject[x])is equivalent toEventDefinition.subject[x]Element `EventDefinition.subject[x]` is mapped to FHIR R4B element `EventDefinition.subject[x]` as `Equivalent`. The target context `EventDefinition.subject[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `EventDefinition`.
EventDefinition.date (date)is equivalent toEventDefinition.dateElement `EventDefinition.date` is mapped to FHIR R4B element `EventDefinition.date` as `Equivalent`. 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.
EventDefinition.publisher (publisher)is equivalent toEventDefinition.publisherElement `EventDefinition.publisher` is mapped to FHIR R4B element `EventDefinition.publisher` as `Equivalent`. 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.
EventDefinition.contact (contact)is equivalent toEventDefinition.contactElement `EventDefinition.contact` is mapped to FHIR R4B element `EventDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
EventDefinition.description (description)is equivalent toEventDefinition.descriptionElement `EventDefinition.description` is mapped to FHIR R4B element `EventDefinition.description` as `Equivalent`. 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).
EventDefinition.useContext (useContext)is equivalent toEventDefinition.useContextElement `EventDefinition.useContext` is mapped to FHIR R4B element `EventDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
EventDefinition.jurisdiction (jurisdiction)is equivalent toEventDefinition.jurisdictionElement `EventDefinition.jurisdiction` is mapped to FHIR R4B element `EventDefinition.jurisdiction` as `Equivalent`. It may be possible for the event definition to be used in jurisdictions other than those for which it was originally designed or intended.
EventDefinition.purpose (purpose)is equivalent toEventDefinition.purposeElement `EventDefinition.purpose` is mapped to FHIR R4B element `EventDefinition.purpose` as `Equivalent`. 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.
EventDefinition.usage (usage)is equivalent toEventDefinition.usageElement `EventDefinition.usage` is mapped to FHIR R4B element `EventDefinition.usage` as `Equivalent`.
EventDefinition.copyright (copyright)is equivalent toEventDefinition.copyrightElement `EventDefinition.copyright` is mapped to FHIR R4B element `EventDefinition.copyright` as `Equivalent`.
EventDefinition.approvalDate (approvalDate)is equivalent toEventDefinition.approvalDateElement `EventDefinition.approvalDate` is mapped to FHIR R4B element `EventDefinition.approvalDate` as `Equivalent`. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.
EventDefinition.lastReviewDate (lastReviewDate)is equivalent toEventDefinition.lastReviewDateElement `EventDefinition.lastReviewDate` is mapped to FHIR R4B element `EventDefinition.lastReviewDate` as `Equivalent`. If specified, this date follows the original approval date.
EventDefinition.effectivePeriod (effectivePeriod)is equivalent toEventDefinition.effectivePeriodElement `EventDefinition.effectivePeriod` is mapped to FHIR R4B element `EventDefinition.effectivePeriod` as `Equivalent`. 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.
EventDefinition.topic (topic)is equivalent toEventDefinition.topicElement `EventDefinition.topic` is mapped to FHIR R4B element `EventDefinition.topic` as `Equivalent`.
EventDefinition.author (author)is equivalent toEventDefinition.authorElement `EventDefinition.author` is mapped to FHIR R4B element `EventDefinition.author` as `Equivalent`.
EventDefinition.editor (editor)is equivalent toEventDefinition.editorElement `EventDefinition.editor` is mapped to FHIR R4B element `EventDefinition.editor` as `Equivalent`.
EventDefinition.reviewer (reviewer)is equivalent toEventDefinition.reviewerElement `EventDefinition.reviewer` is mapped to FHIR R4B element `EventDefinition.reviewer` as `Equivalent`.
EventDefinition.endorser (endorser)is equivalent toEventDefinition.endorserElement `EventDefinition.endorser` is mapped to FHIR R4B element `EventDefinition.endorser` as `Equivalent`.
EventDefinition.relatedArtifact (relatedArtifact)is equivalent toEventDefinition.relatedArtifactElement `EventDefinition.relatedArtifact` is mapped to FHIR R4B element `EventDefinition.relatedArtifact` as `Equivalent`. Each related resource is either an attachment, or a reference to another resource, but not both.
EventDefinition.trigger (trigger)is equivalent toEventDefinition.triggerElement `EventDefinition.trigger` is mapped to FHIR R4B element `EventDefinition.trigger` as `Equivalent`.