R4B-Invoice-element-map-to-R3
type: ConceptMap
node role: treeRoot
id:
  v: R4B-Invoice-element-map-to-R3
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R4B-Invoice-element-map-to-R3 Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/3.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2 Source Code Relationship Target Code Comment Invoice.meta (meta) is equivalent to Basic.meta Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `Invoice.meta` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Invoice.implicitRules (implicitRules) is equivalent to Basic.implicitRules Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `Invoice.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. Invoice.language (language) is equivalent to Basic.language Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `Invoice.language` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.language` has no mapping targets in FHIR S…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Uri
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r3
        l: hl7.fhir.uv.xver-r4b.r3
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Uri
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r3
        l: hl7.fhir.uv.xver-r4b.r3
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Invoice-element-map-to-R3
  l: R4B-Invoice-element-map-to-R3
version:
  v: 0.1.0
name:
  v: R4BInvoiceElementMapToR3
title:
  v: Cross-version mapping for FHIR R4B Invoice to FHIR STU3 Basic
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:31.215661-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R4B Invoice to FHIR STU3.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Uri
  v: http://hl7.org/fhir/4.3
  l: http://hl7.org/fhir/4.3
target: Uri
  v: http://hl7.org/fhir/3.0
  l: http://hl7.org/fhir/3.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Invoice
    l: Invoice
  source version:
    v: 4.3.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/Basic
    l: Basic
  target version:
    v: 3.0.2
  element:
    code:
      v: Invoice.meta
    display:
      v: meta
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.meta
      display:
        v: Basic.meta
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `Invoice.meta` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
  element:
    code:
      v: Invoice.implicitRules
    display:
      v: implicitRules
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.implicitRules
      display:
        v: Basic.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `Invoice.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
  element:
    code:
      v: Invoice.language
    display:
      v: language
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.language
      display:
        v: Basic.language
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `Invoice.language` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.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).
  element:
    code:
      v: Invoice.text
    display:
      v: text
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.text
      display:
        v: Basic.text
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `Invoice.text` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.text` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
  element:
    code:
      v: Invoice.contained
    display:
      v: contained
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.contained
      display:
        v: Basic.contained
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `Invoice.contained` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.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.
  element:
    code:
      v: Invoice.identifier
    display:
      v: identifier
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.identifier
      display:
        v: Basic.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `Invoice.identifier` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
  element:
    code:
      v: Invoice.subject
    display:
      v: subject
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.subject
      display:
        v: Basic.subject
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.subject` (`Basic.subject`), use that element instead. Element `Invoice.subject` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.subject` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.status
  l: extension-Invoice.status
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.status
  display:
    v: status
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.status` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.cancelledReason
  l: extension-Invoice.cancelledReason
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.cancelledReason
  display:
    v: cancelledReason
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.cancelledReason` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.cancelledReason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Derived Profiles may choose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.type
  l: extension-Invoice.type
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.type
  display:
    v: type
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.type` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.recipient
  l: extension-Invoice.recipient
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.recipient
  display:
    v: recipient
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.recipient` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.recipient` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.date
  l: extension-Invoice.date
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.date
  display:
    v: date
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.date` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.date` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The list of types may be constrained as appropriate for the type of charge item.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.participant
  l: extension-Invoice.participant
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.participant
  display:
    v: participant
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.participant` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.participant` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.participant.role
  display:
    v: role
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:role
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.participant.role` is part of an existing definition because parent element `Invoice.participant` requires a cross-version extension. Element `Invoice.participant.role` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.participant.role` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.participant.actor
  display:
    v: actor
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:actor
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.participant.actor` is part of an existing definition because parent element `Invoice.participant` requires a cross-version extension. Element `Invoice.participant.actor` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.participant.actor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.issuer
  l: extension-Invoice.issuer
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.issuer
  display:
    v: issuer
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.issuer` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.issuer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Practitioners and Devices can be associated with multiple organizations. It has to be made clear, on behalf of which Organization the services have been rendered.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.account
  l: extension-Invoice.account
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.account
  display:
    v: account
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.account` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.account` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Systems posting the ChargeItems might not always be able to determine, which accounts the Items need to be places into. It is up to the potprocessing Financial System to apply internal rules to decide based on the Encounter/EpisodeOfCare/Patient/Coverage context and the type of ChargeItem, which Account is appropriate.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.lineItem
  l: extension-Invoice.lineItem
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.lineItem
  display:
    v: lineItem
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.sequence
  display:
    v: sequence
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:sequence
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.sequence` is part of an existing definition because parent element `Invoice.lineItem` requires a cross-version extension. Element `Invoice.lineItem.sequence` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.sequence` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.chargeItem[x]
  display:
    v: chargeItem[x]
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:chargeItem
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.chargeItem[x]` is part of an existing definition because parent element `Invoice.lineItem` requires a cross-version extension. Element `Invoice.lineItem.chargeItem[x]` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.chargeItem[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.priceComponent
  display:
    v: priceComponent
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:priceComponent
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent` is part of an existing definition because parent element `Invoice.lineItem` requires a cross-version extension. Element `Invoice.lineItem.priceComponent` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.priceComponent.type
  display:
    v: type
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:priceComponent.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent.type` is part of an existing definition because parent element `Invoice.lineItem.priceComponent` requires a cross-version extension. Element `Invoice.lineItem.priceComponent.type` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.priceComponent.code
  display:
    v: code
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:priceComponent.extension:code
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent.code` is part of an existing definition because parent element `Invoice.lineItem.priceComponent` requires a cross-version extension. Element `Invoice.lineItem.priceComponent.code` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.priceComponent.factor
  display:
    v: factor
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:priceComponent.extension:factor
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent.factor` is part of an existing definition because parent element `Invoice.lineItem.priceComponent` requires a cross-version extension. Element `Invoice.lineItem.priceComponent.factor` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent.factor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.
element:
  code:
    v: Invoice.lineItem.priceComponent.amount
  display:
    v: amount
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:priceComponent.extension:amount
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent.amount` is part of an existing definition because parent element `Invoice.lineItem.priceComponent` requires a cross-version extension. Element `Invoice.lineItem.priceComponent.amount` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent.amount` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.lineItem.priceComponent
  l: extension-Invoice.lineItem.priceComponent
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.lineItem.priceComponent
  display:
    v: priceComponent
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent` is part of an existing definition because parent element `Invoice.lineItem` requires a cross-version extension. Element `Invoice.lineItem.priceComponent` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.priceComponent.type
  display:
    v: type
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent.type` is part of an existing definition because parent element `Invoice.lineItem.priceComponent` requires a cross-version extension. Element `Invoice.lineItem.priceComponent.type` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.priceComponent.code
  display:
    v: code
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:code
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent.code` is part of an existing definition because parent element `Invoice.lineItem.priceComponent` requires a cross-version extension. Element `Invoice.lineItem.priceComponent.code` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Invoice.lineItem.priceComponent.factor
  display:
    v: factor
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:factor
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent.factor` is part of an existing definition because parent element `Invoice.lineItem.priceComponent` requires a cross-version extension. Element `Invoice.lineItem.priceComponent.factor` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent.factor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.
element:
  code:
    v: Invoice.lineItem.priceComponent.amount
  display:
    v: amount
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:amount
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.lineItem.priceComponent.amount` is part of an existing definition because parent element `Invoice.lineItem.priceComponent` requires a cross-version extension. Element `Invoice.lineItem.priceComponent.amount` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.lineItem.priceComponent.amount` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.totalNet
  l: extension-Invoice.totalNet
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.totalNet
  display:
    v: totalNet
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.totalNet` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.totalNet` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.totalGross
  l: extension-Invoice.totalGross
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.totalGross
  display:
    v: totalGross
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.totalGross` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.totalGross` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.paymentTerms
  l: extension-Invoice.paymentTerms
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.paymentTerms
  display:
    v: paymentTerms
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.paymentTerms` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.paymentTerms` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Derived Profiles may chose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled.

source:
  v: http://hl7.org/fhir/StructureDefinition/Invoice
  l: Invoice
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.note
  l: extension-Invoice.note
target version:
  v: 0.1.0
element:
  code:
    v: Invoice.note
  display:
    v: note
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Invoice.note` is not mapped to FHIR STU3, since FHIR R4B `Invoice` is not mapped. Element `Invoice.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).