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

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

ConceptMap: R5ChargeItemDefinitionElementMapToR4

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 ChargeItemDefinition to FHIR R4.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to ChargeItemDefinitionversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
ChargeItemDefinition.meta (meta)​is equivalent toChargeItemDefinition.metaElement `ChargeItemDefinition.meta` is mapped to FHIR R4 element `ChargeItemDefinition.meta` as `Equivalent`.
ChargeItemDefinition.implicitRules (implicitRules)​is equivalent toChargeItemDefinition.implicitRulesElement `ChargeItemDefinition.implicitRules` is mapped to FHIR R4 element `ChargeItemDefinition.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
ChargeItemDefinition.language (language)​is equivalent toChargeItemDefinition.languageElement `ChargeItemDefinition.language` is mapped to FHIR R4 element `ChargeItemDefinition.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).
ChargeItemDefinition.text (text)​is equivalent toChargeItemDefinition.textElement `ChargeItemDefinition.text` is mapped to FHIR R4 element `ChargeItemDefinition.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
ChargeItemDefinition.contained (contained)​is equivalent toChargeItemDefinition.containedElement `ChargeItemDefinition.contained` is mapped to FHIR R4 element `ChargeItemDefinition.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.
ChargeItemDefinition.url (url)​is equivalent toChargeItemDefinition.urlElement `ChargeItemDefinition.url` is mapped to FHIR R4 element `ChargeItemDefinition.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.
ChargeItemDefinition.identifier (identifier)​is equivalent toChargeItemDefinition.identifierElement `ChargeItemDefinition.identifier` is mapped to FHIR R4 element `ChargeItemDefinition.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 charge item definition outside of FHIR, where it is not possible to use the logical URI.
ChargeItemDefinition.version (version)​is equivalent toChargeItemDefinition.versionElement `ChargeItemDefinition.version` is mapped to FHIR R4 element `ChargeItemDefinition.version` as `Equivalent`. There may be different charge item 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 charge item definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).
ChargeItemDefinition.title (title)​is equivalent toChargeItemDefinition.titleElement `ChargeItemDefinition.title` is mapped to FHIR R4 element `ChargeItemDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
ChargeItemDefinition.derivedFromUri (derivedFromUri)​is equivalent toChargeItemDefinition.derivedFromUriElement `ChargeItemDefinition.derivedFromUri` is mapped to FHIR R4 element `ChargeItemDefinition.derivedFromUri` as `Equivalent`.
ChargeItemDefinition.partOf (partOf)​is equivalent toChargeItemDefinition.partOfElement `ChargeItemDefinition.partOf` is mapped to FHIR R4 element `ChargeItemDefinition.partOf` as `Equivalent`.
ChargeItemDefinition.replaces (replaces)​is equivalent toChargeItemDefinition.replacesElement `ChargeItemDefinition.replaces` is mapped to FHIR R4 element `ChargeItemDefinition.replaces` as `Equivalent`.
ChargeItemDefinition.status (status)​is equivalent toChargeItemDefinition.statusElement `ChargeItemDefinition.status` is mapped to FHIR R4 element `ChargeItemDefinition.status` as `Equivalent`. Allows filtering of charge item definitions that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
ChargeItemDefinition.experimental (experimental)​is equivalent toChargeItemDefinition.experimentalElement `ChargeItemDefinition.experimental` is mapped to FHIR R4 element `ChargeItemDefinition.experimental` as `Equivalent`. Allows filtering of charge item definitions that are appropriate for use versus not.
ChargeItemDefinition.date (date)​is equivalent toChargeItemDefinition.dateElement `ChargeItemDefinition.date` is mapped to FHIR R4 element `ChargeItemDefinition.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the charge item definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
ChargeItemDefinition.publisher (publisher)​is equivalent toChargeItemDefinition.publisherElement `ChargeItemDefinition.publisher` is mapped to FHIR R4 element `ChargeItemDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the charge item definition is the organization or individual primarily responsible for the maintenance and upkeep of the charge item 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 charge item definition. This item SHOULD be populated unless the information is available from context.
ChargeItemDefinition.contact (contact)​is equivalent toChargeItemDefinition.contactElement `ChargeItemDefinition.contact` is mapped to FHIR R4 element `ChargeItemDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
ChargeItemDefinition.description (description)​is equivalent toChargeItemDefinition.descriptionElement `ChargeItemDefinition.description` is mapped to FHIR R4 element `ChargeItemDefinition.description` as `Equivalent`. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the charge item 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 charge item definition is presumed to be the predominant language in the place the charge item definition was created).
ChargeItemDefinition.useContext (useContext)​is equivalent toChargeItemDefinition.useContextElement `ChargeItemDefinition.useContext` is mapped to FHIR R4 element `ChargeItemDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
ChargeItemDefinition.jurisdiction (jurisdiction)​is equivalent toChargeItemDefinition.jurisdictionElement `ChargeItemDefinition.jurisdiction` is mapped to FHIR R4 element `ChargeItemDefinition.jurisdiction` as `Equivalent`. Element `ChargeItemDefinition.jurisdiction` has been flagged as deprecated. It may be possible for the charge item definition to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)
ChargeItemDefinition.copyright (copyright)​is equivalent toChargeItemDefinition.copyrightElement `ChargeItemDefinition.copyright` is mapped to FHIR R4 element `ChargeItemDefinition.copyright` as `Equivalent`.
ChargeItemDefinition.approvalDate (approvalDate)​is equivalent toChargeItemDefinition.approvalDateElement `ChargeItemDefinition.approvalDate` is mapped to FHIR R4 element `ChargeItemDefinition.approvalDate` as `Equivalent`. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
ChargeItemDefinition.lastReviewDate (lastReviewDate)​is equivalent toChargeItemDefinition.lastReviewDateElement `ChargeItemDefinition.lastReviewDate` is mapped to FHIR R4 element `ChargeItemDefinition.lastReviewDate` as `Equivalent`. If specified, this date follows the original approval date. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
ChargeItemDefinition.code (code)​is equivalent toChargeItemDefinition.codeElement `ChargeItemDefinition.code` is mapped to FHIR R4 element `ChargeItemDefinition.code` as `Equivalent`.
ChargeItemDefinition.instance (instance)​maps to wider conceptChargeItemDefinition.instanceElement `ChargeItemDefinition.instance` is mapped to FHIR R4 element `ChargeItemDefinition.instance` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `ChargeItemDefinition.instance` with unmapped reference targets: ActivityDefinition, DeviceDefinition, HealthcareService, PlanDefinition. In case of highly customized, individually produced or fitted devices/substances, the pricing information may be different for each instance of the product. This reference links pricing details to specific product instances.
ChargeItemDefinition.applicability (applicability)​maps to wider conceptChargeItemDefinition.applicabilityElement `ChargeItemDefinition.applicability` is mapped to FHIR R4 element `ChargeItemDefinition.applicability` as `Equivalent`. The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.
ChargeItemDefinition.propertyGroup (propertyGroup)​maps to wider conceptChargeItemDefinition.propertyGroupElement `ChargeItemDefinition.propertyGroup` is mapped to FHIR R4 element `ChargeItemDefinition.propertyGroup` as `Equivalent`.
ChargeItemDefinition.propertyGroup.applicability (applicability)​is equivalent toChargeItemDefinition.propertyGroup.applicabilityElement `ChargeItemDefinition.propertyGroup.applicability` is mapped to FHIR R4 element `ChargeItemDefinition.propertyGroup.applicability` as `Equivalent`. The applicability conditions can be used to ascertain whether a billing item is allowed in a specific context. E.g. some billing codes may only be applicable in out-patient settings, only to male/female patients or only to children.
ChargeItemDefinition.propertyGroup.priceComponent (priceComponent)​is equivalent toChargeItemDefinition.propertyGroup.priceComponentElement `ChargeItemDefinition.propertyGroup.priceComponent` is mapped to FHIR R4 element `ChargeItemDefinition.propertyGroup.priceComponent` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: How to compare versions (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ChargeItemDefinition.versionAlgorithm[x] (versionAlgorithm[x])​maps to wider conceptExtension (R5: How to compare versions (new))Element `ChargeItemDefinition.versionAlgorithm[x]` has a context of ChargeItemDefinition based on following the parent source element upwards and mapping to `ChargeItemDefinition`. Element `ChargeItemDefinition.versionAlgorithm[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Name for this charge item definition (computer friendly) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ChargeItemDefinition.name (name)​maps to wider conceptExtension (R5: Name for this charge item definition (computer friendly) (new))Element `ChargeItemDefinition.name` has a context of ChargeItemDefinition based on following the parent source element upwards and mapping to `ChargeItemDefinition`. Element `ChargeItemDefinition.name` has no mapping targets in FHIR R4. 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 4 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Why this charge item definition is defined (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ChargeItemDefinition.purpose (purpose)​maps to wider conceptExtension (R5: Why this charge item definition is defined (new))Element `ChargeItemDefinition.purpose` has a context of ChargeItemDefinition based on following the parent source element upwards and mapping to `ChargeItemDefinition`. Element `ChargeItemDefinition.purpose` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the charge item 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 charge item definition.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Copyright holder and year(s) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ChargeItemDefinition.copyrightLabel (copyrightLabel)​maps to wider conceptExtension (R5: Copyright holder and year(s) (new))Element `ChargeItemDefinition.copyrightLabel` has a context of ChargeItemDefinition based on following the parent source element upwards and mapping to `ChargeItemDefinition`. Element `ChargeItemDefinition.copyrightLabel` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Boolean-valued expression (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ChargeItemDefinition.applicability.condition (condition)​maps to wider conceptExtension (R5: Boolean-valued expression (new))Element `ChargeItemDefinition.applicability.condition` has a context of ChargeItemDefinition.applicability based on following the parent source element upwards and mapping to `ChargeItemDefinition`. Element `ChargeItemDefinition.applicability.condition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Please note that FHIRPath Expressions can only be evaluated in the scope of the current ChargeItem resource to which this definition is being applied. FHIRPath expressions can traverse into other resources linked from the ChargeItem resource, however, testing rules such as that a billing code may be billed only once per encounter need a wider scope. In such scenarios, CQL may be the appropriate choice.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: When the charge item definition is expected to be used (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ChargeItemDefinition.applicability.effectivePeriod (effectivePeriod)​maps to wider conceptExtension (R5: When the charge item definition is expected to be used (new))Element `ChargeItemDefinition.applicability.effectivePeriod` has a context of ChargeItemDefinition.applicability based on following the parent source element upwards and mapping to `ChargeItemDefinition`. Element `ChargeItemDefinition.applicability.effectivePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The effective period for a charge item 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 8 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Reference to / quotation of the external source of the group of properties (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ChargeItemDefinition.applicability.relatedArtifact (relatedArtifact)​maps to wider conceptExtension (R5: Reference to / quotation of the external source of the group of properties (new))Element `ChargeItemDefinition.applicability.relatedArtifact` has a context of ChargeItemDefinition.applicability based on following the parent source element upwards and mapping to `ChargeItemDefinition`. Element `ChargeItemDefinition.applicability.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).