FHIR IG analytics| Package | hl7.fhir.uv.xver-r5.r3 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R5-ChargeItemDefinition-element-map-to-R3.json |
| FHIR Version | R3 |
| Source | http://hl7.org/fhir/uv/xver-r5.r3/0.1.0/ConceptMap-R5-ChargeItemDefinition-element-map-to-R3.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R5-ChargeItemDefinition-element-map-to-R3 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:05:14.339781-05:00 |
| Name | R5ChargeItemDefinitionElementMapToR3 |
| Title | Cross-version mapping for FHIR R5 ChargeItemDefinition to FHIR STU3 Basic |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R5 ChargeItemDefinition to FHIR STU3. |
No resources found
| StructureDefinition | ||
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.applicability | R5: Whether or not the billing code is applicable (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.approvalDate | R5: When the charge item definition was approved by publisher (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.code | R5: Billing code or product type this definition applies to (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.contact | R5: Contact details for the publisher (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.copyright | R5: Use and/or publishing restrictions (new) |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-ChargeItemDefinition.copyrightLabel | Cross-version Extension for R5.ChargeItemDefinition.copyrightLabel for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.date | R5: Date last changed (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.derivedFromUri | R5: Underlying externally-defined charge item definition (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.description | R5: Natural language description of the charge item definition (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.experimental | R5: For testing purposes, not real usage (new) |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-ChargeItemDefinition.instance | Cross-version Extension for R5.ChargeItemDefinition.instance for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.jurisdiction | R5: Intended jurisdiction for charge item definition (if applicable) (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.lastReviewDate | R5: When the charge item definition was last reviewed by the publisher (new) |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-ChargeItemDefinition.name | Cross-version Extension for R5.ChargeItemDefinition.name for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.partOf | R5: A larger definition of which this particular definition is a component or step (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.propertyGroup | R5: Group of properties which are applicable under the same conditions (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.publisher | R5: Name of the publisher/steward (organization or individual) (new) |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-ChargeItemDefinition.purpose | Cross-version Extension for R5.ChargeItemDefinition.purpose for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.replaces | R5: Completed or terminated request(s) whose function is taken by this new request (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.status | R5: draft | active | retired | unknown (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.title | R5: Name for this charge item definition (human friendly) (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.url | R5: Canonical identifier for this charge item definition, represented as a URI (globally unique) (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.useContext | R5: The context that the content is intended to support (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-ChargeItemDefinition.version | R5: Business version of the charge item definition (new) |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-ChargeItemDefinition.versionAlgorithm | Cross-version Extension for R5.ChargeItemDefinition.versionAlgorithm[x] for use in FHIR R4 |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R5-ChargeItemDefinition-element-map-to-R3
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.meta (meta) | is equivalent to | Basic.meta | Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `ChargeItemDefinition.meta` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
| ChargeItemDefinition.implicitRules (implicitRules) | is equivalent to | Basic.implicitRules | Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `ChargeItemDefinition.implicitRules` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 its narrative along with other profiles, value sets, etc. |
| ChargeItemDefinition.language (language) | is equivalent to | Basic.language | Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `ChargeItemDefinition.language` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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). |
| ChargeItemDefinition.text (text) | is equivalent to | Basic.text | Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `ChargeItemDefinition.text` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 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 to | Basic.contained | Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `ChargeItemDefinition.contained` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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. |
| ChargeItemDefinition.identifier (identifier) | is equivalent to | Basic.identifier | Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `ChargeItemDefinition.identifier` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 charge item definition outside of FHIR, where it is not possible to use the logical URI. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Canonical identifier for this charge item definition, represented as a URI (globally unique) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.url (url) | maps to wider concept | Extension (R5: Canonical identifier for this charge item definition, represented as a URI (globally unique) (new)) | Element `ChargeItemDefinition.url` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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/ChargeItemDefinition|5.0.0 to R5: Business version of the charge item definition (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.version (version) | maps to wider concept | Extension (R5: Business version of the charge item definition (new)) | Element `ChargeItemDefinition.version` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 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). |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: How to compare versions (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.versionAlgorithm[x] (versionAlgorithm[x]) | maps to wider concept | Extension (R5: How to compare versions (new)) | Element `ChargeItemDefinition.versionAlgorithm[x]` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.versionAlgorithm[x]` has no mapping targets in FHIR STU3. 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 5 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 Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.name (name) | maps to wider concept | Extension (R5: Name for this charge item definition (computer friendly) (new)) | Element `ChargeItemDefinition.name` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 6 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Name for this charge item definition (human friendly) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.title (title) | maps to wider concept | Extension (R5: Name for this charge item definition (human friendly) (new)) | Element `ChargeItemDefinition.title` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 7 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Underlying externally-defined charge item definition (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.derivedFromUri (derivedFromUri) | maps to wider concept | Extension (R5: Underlying externally-defined charge item definition (new)) | Element `ChargeItemDefinition.derivedFromUri` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.derivedFromUri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: A larger definition of which this particular definition is a component or step (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.partOf (partOf) | maps to wider concept | Extension (R5: A larger definition of which this particular definition is a component or step (new)) | Element `ChargeItemDefinition.partOf` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.partOf` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Completed or terminated request(s) whose function is taken by this new request (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.replaces (replaces) | maps to wider concept | Extension (R5: Completed or terminated request(s) whose function is taken by this new request (new)) | Element `ChargeItemDefinition.replaces` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.replaces` 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/ChargeItemDefinition|5.0.0 to R5: draft | active | retired | unknown (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.status (status) | maps to wider concept | Extension (R5: draft | active | retired | unknown (new)) | Element `ChargeItemDefinition.status` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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). |
Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: For testing purposes, not real usage (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.experimental (experimental) | maps to wider concept | Extension (R5: For testing purposes, not real usage (new)) | Element `ChargeItemDefinition.experimental` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.experimental` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of charge item definitions that are appropriate for use versus not. |
Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Date last changed (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.date (date) | maps to wider concept | Extension (R5: Date last changed (new)) | Element `ChargeItemDefinition.date` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.date` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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). |
Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Name of the publisher/steward (organization or individual) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.publisher (publisher) | maps to wider concept | Extension (R5: Name of the publisher/steward (organization or individual) (new)) | Element `ChargeItemDefinition.publisher` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 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. |
Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Contact details for the publisher (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.contact (contact) | maps to wider concept | Extension (R5: Contact details for the publisher (new)) | Element `ChargeItemDefinition.contact` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). |
Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Natural language description of the charge item definition (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.description (description) | maps to wider concept | Extension (R5: Natural language description of the charge item definition (new)) | Element `ChargeItemDefinition.description` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 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). |
Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: The context that the content is intended to support (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.useContext (useContext) | maps to wider concept | Extension (R5: The context that the content is intended to support (new)) | Element `ChargeItemDefinition.useContext` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 17 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Intended jurisdiction for charge item definition (if applicable) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.jurisdiction (jurisdiction) | maps to wider concept | Extension (R5: Intended jurisdiction for charge item definition (if applicable) (new)) | Element `ChargeItemDefinition.jurisdiction` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.) |
Group 18 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 Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.purpose (purpose) | maps to wider concept | Extension (R5: Why this charge item definition is defined (new)) | Element `ChargeItemDefinition.purpose` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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 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 19 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Use and/or publishing restrictions (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.copyright (copyright) | maps to wider concept | Extension (R5: Use and/or publishing restrictions (new)) | Element `ChargeItemDefinition.copyright` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.copyright` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Copyright holder and year(s) (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.copyrightLabel (copyrightLabel) | maps to wider concept | Extension (R5: Copyright holder and year(s) (new)) | Element `ChargeItemDefinition.copyrightLabel` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.copyrightLabel` has no mapping targets in FHIR STU3. 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 21 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: When the charge item definition was approved by publisher (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.approvalDate (approvalDate) | maps to wider concept | Extension (R5: When the charge item definition was approved by publisher (new)) | Element `ChargeItemDefinition.approvalDate` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). |
Group 22 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: When the charge item definition was last reviewed by the publisher (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.lastReviewDate (lastReviewDate) | maps to wider concept | Extension (R5: When the charge item definition was last reviewed by the publisher (new)) | Element `ChargeItemDefinition.lastReviewDate` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). |
Group 23 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Billing code or product type this definition applies to (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.code (code) | maps to wider concept | Extension (R5: Billing code or product type this definition applies to (new)) | Element `ChargeItemDefinition.code` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 24 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Instances this definition applies to (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.instance (instance) | maps to wider concept | Extension (R5: Instances this definition applies to (new)) | Element `ChargeItemDefinition.instance` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.instance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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. |
Group 25 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Whether or not the billing code is applicable (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.applicability (applicability) | maps to wider concept | Extension (R5: Whether or not the billing code is applicable (new)) | Element `ChargeItemDefinition.applicability` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.applicability` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.applicability.condition (condition) | maps to wider concept | Extension.extension:condition (R5: Boolean-valued expression (new)) | Element `ChargeItemDefinition.applicability.condition` is part of an existing definition because parent element `ChargeItemDefinition.applicability` requires a cross-version extension. Element `ChargeItemDefinition.applicability.condition` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.applicability.condition` has no mapping targets in FHIR STU3. 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. |
| ChargeItemDefinition.applicability.effectivePeriod (effectivePeriod) | maps to wider concept | Extension.extension:effectivePeriod (R5: When the charge item definition is expected to be used (new)) | Element `ChargeItemDefinition.applicability.effectivePeriod` is part of an existing definition because parent element `ChargeItemDefinition.applicability` requires a cross-version extension. Element `ChargeItemDefinition.applicability.effectivePeriod` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.applicability.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 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. |
| ChargeItemDefinition.applicability.relatedArtifact (relatedArtifact) | maps to wider concept | Extension.extension:relatedArtifact (R5: Reference to / quotation of the external source of the group of properties (new)) | Element `ChargeItemDefinition.applicability.relatedArtifact` is part of an existing definition because parent element `ChargeItemDefinition.applicability` requires a cross-version extension. Element `ChargeItemDefinition.applicability.relatedArtifact` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.applicability.relatedArtifact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
| ChargeItemDefinition.propertyGroup.applicability (applicability) | maps to wider concept | Extension.extension:applicability | Element `ChargeItemDefinition.propertyGroup.applicability` is part of an existing definition because parent element `ChargeItemDefinition.propertyGroup` requires a cross-version extension. Element `ChargeItemDefinition.propertyGroup.applicability` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.propertyGroup.applicability` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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. |
Group 26 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition|5.0.0 to R5: Group of properties which are applicable under the same conditions (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ChargeItemDefinition.propertyGroup (propertyGroup) | maps to wider concept | Extension (R5: Group of properties which are applicable under the same conditions (new)) | Element `ChargeItemDefinition.propertyGroup` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.propertyGroup` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
| ChargeItemDefinition.propertyGroup.applicability (applicability) | maps to wider concept | Extension.extension:applicability (R5: Conditions under which the priceComponent is applicable (new)) | Element `ChargeItemDefinition.propertyGroup.applicability` is part of an existing definition because parent element `ChargeItemDefinition.propertyGroup` requires a cross-version extension. Element `ChargeItemDefinition.propertyGroup.applicability` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.propertyGroup.applicability` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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) | maps to wider concept | Extension.extension:priceComponent (R5: Components of total line item price (new)) | Element `ChargeItemDefinition.propertyGroup.priceComponent` is part of an existing definition because parent element `ChargeItemDefinition.propertyGroup` requires a cross-version extension. Element `ChargeItemDefinition.propertyGroup.priceComponent` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped. Element `ChargeItemDefinition.propertyGroup.priceComponent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
{
"resourceType": "ConceptMap",
"id": "R5-ChargeItemDefinition-element-map-to-R3",
"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",
"valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-ChargeItemDefinition-element-map-to-R3",
"version": "0.1.0",
"name": "R5ChargeItemDefinitionElementMapToR3",
"title": "Cross-version mapping for FHIR R5 ChargeItemDefinition to FHIR STU3 Basic",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:05:14.339781-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 R5 ChargeItemDefinition to FHIR STU3.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceUri": "http://hl7.org/fhir/5.0",
"targetUri": "http://hl7.org/fhir/3.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/Basic",
"targetVersion": "3.0.2",
"element": [
{
"code": "ChargeItemDefinition.meta",
"display": "meta",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Basic.meta",
"display": "Basic.meta",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.\nElement `ChargeItemDefinition.meta` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "ChargeItemDefinition.implicitRules",
"display": "implicitRules",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Basic.implicitRules",
"display": "Basic.implicitRules",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.\nElement `ChargeItemDefinition.implicitRules` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\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 its narrative along with other profiles, value sets, etc."
}
]
},
{
"code": "ChargeItemDefinition.language",
"display": "language",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Basic.language",
"display": "Basic.language",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.\nElement `ChargeItemDefinition.language` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\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": "ChargeItemDefinition.text",
"display": "text",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Basic.text",
"display": "Basic.text",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.\nElement `ChargeItemDefinition.text` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.text` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nContained 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."
}
]
},
{
"code": "ChargeItemDefinition.contained",
"display": "contained",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Basic.contained",
"display": "Basic.contained",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.\nElement `ChargeItemDefinition.contained` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.contained` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\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": "ChargeItemDefinition.identifier",
"display": "identifier",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Basic.identifier",
"display": "Basic.identifier",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead.\nElement `ChargeItemDefinition.identifier` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nTypically, 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.url",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.url",
"display": "url",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.url` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.url` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nCan 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.\n\nThe 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). \n\nIn 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.version",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.version",
"display": "version",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.version` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThere 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)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.versionAlgorithm",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.versionAlgorithm[x]",
"display": "versionAlgorithm[x]",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.versionAlgorithm[x]` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.versionAlgorithm[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nIf 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.name",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.name",
"display": "name",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.name` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.title",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.title",
"display": "title",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.title` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis name does not need to be machine-processing friendly and may contain punctuation, white-space, etc."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.derivedFromUri",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.derivedFromUri",
"display": "derivedFromUri",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.derivedFromUri` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.derivedFromUri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.partOf",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.partOf",
"display": "partOf",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.partOf` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.partOf` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.replaces",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.replaces",
"display": "replaces",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.replaces` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.replaces` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.status",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.status",
"display": "status",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.status` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nAllows filtering of charge item definitions that are appropriate for use versus not.\n\nSee guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.experimental",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.experimental",
"display": "experimental",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.experimental` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.experimental` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nAllows filtering of charge item definitions that are appropriate for use versus not."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.date",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.date",
"display": "date",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.date` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.date` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 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.\n\nSee guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.publisher",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.publisher",
"display": "publisher",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.publisher` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.publisher` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nUsually 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.contact",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.contact",
"display": "contact",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.contact` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.contact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nMay be a web site, an email address, a telephone number, etc.\n\nSee guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.description",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.description",
"display": "description",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.description` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis 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)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.useContext",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.useContext",
"display": "useContext",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.useContext` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.useContext` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nWhen multiple useContexts are specified, there is no expectation that all or any of the contexts apply."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.jurisdiction",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.jurisdiction",
"display": "jurisdiction",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.jurisdiction` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nElement `ChargeItemDefinition.jurisdiction` has been flagged as deprecated.\nIt may be possible for the charge item definition to be used in jurisdictions other than those for which it was originally designed or intended.\n\nDEPRECATION 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.)"
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.purpose",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.purpose",
"display": "purpose",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.purpose` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.purpose` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.copyright",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.copyright",
"display": "copyright",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.copyright` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.copyright` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.copyrightLabel",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.copyrightLabel",
"display": "copyrightLabel",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.copyrightLabel` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.copyrightLabel` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe (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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.approvalDate",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.approvalDate",
"display": "approvalDate",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.approvalDate` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.approvalDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 'date' element may be more recent than the approval date because of minor changes or editorial corrections.\n\nSee guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.lastReviewDate",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.lastReviewDate",
"display": "lastReviewDate",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.lastReviewDate` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.lastReviewDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nIf specified, this date follows the original approval date.\n\nSee guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.code",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.code",
"display": "code",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.code` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.instance",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.instance",
"display": "instance",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.instance` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.instance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nIn 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.applicability",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.applicability",
"display": "applicability",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.applicability` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.applicability` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 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."
}
]
},
{
"code": "ChargeItemDefinition.applicability.condition",
"display": "condition",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:condition",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.applicability.condition` is part of an existing definition because parent element `ChargeItemDefinition.applicability` requires a cross-version extension.\nElement `ChargeItemDefinition.applicability.condition` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.applicability.condition` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nPlease note that FHIRPath Expressions can only be evaluated in the scope of the current ChargeItem resource to which this definition is being applied.\nFHIRPath 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."
}
]
},
{
"code": "ChargeItemDefinition.applicability.effectivePeriod",
"display": "effectivePeriod",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:effectivePeriod",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.applicability.effectivePeriod` is part of an existing definition because parent element `ChargeItemDefinition.applicability` requires a cross-version extension.\nElement `ChargeItemDefinition.applicability.effectivePeriod` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.applicability.effectivePeriod` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 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."
}
]
},
{
"code": "ChargeItemDefinition.applicability.relatedArtifact",
"display": "relatedArtifact",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:relatedArtifact",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.applicability.relatedArtifact` is part of an existing definition because parent element `ChargeItemDefinition.applicability` requires a cross-version extension.\nElement `ChargeItemDefinition.applicability.relatedArtifact` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.applicability.relatedArtifact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "ChargeItemDefinition.propertyGroup.applicability",
"display": "applicability",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:applicability",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.propertyGroup.applicability` is part of an existing definition because parent element `ChargeItemDefinition.propertyGroup` requires a cross-version extension.\nElement `ChargeItemDefinition.propertyGroup.applicability` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.propertyGroup.applicability` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItemDefinition",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-ChargeItemDefinition.propertyGroup",
"targetVersion": "0.1.0",
"element": [
{
"code": "ChargeItemDefinition.propertyGroup",
"display": "propertyGroup",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.propertyGroup` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.propertyGroup` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "ChargeItemDefinition.propertyGroup.applicability",
"display": "applicability",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:applicability",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.propertyGroup.applicability` is part of an existing definition because parent element `ChargeItemDefinition.propertyGroup` requires a cross-version extension.\nElement `ChargeItemDefinition.propertyGroup.applicability` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.propertyGroup.applicability` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 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."
}
]
},
{
"code": "ChargeItemDefinition.propertyGroup.priceComponent",
"display": "priceComponent",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:priceComponent",
"equivalence": "wider",
"comment": "Element `ChargeItemDefinition.propertyGroup.priceComponent` is part of an existing definition because parent element `ChargeItemDefinition.propertyGroup` requires a cross-version extension.\nElement `ChargeItemDefinition.propertyGroup.priceComponent` is not mapped to FHIR STU3, since FHIR R5 `ChargeItemDefinition` is not mapped.\nElement `ChargeItemDefinition.propertyGroup.priceComponent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
}
]
}