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

• Narrative Content
• XML
• JSON
• TTL

: R4BInvoiceElementMapToR3 - XML Representation

Raw xml | Download

<ConceptMap xmlns="http://hl7.org/fhir">
  <id value="R4B-Invoice-element-map-to-R3"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R4B-Invoice-element-map-to-R3</b></p><a name="R4B-Invoice-element-map-to-R3"> </a><a name="hcR4B-Invoice-element-map-to-R3"> </a><p>Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/3.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <code>http://hl7.org/fhir/StructureDefinition/Basic|3.0.2</code></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.meta</td><td>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).</td></tr><tr><td>Invoice.implicitRules (implicitRules)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.implicitRules</td><td>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.</td></tr><tr><td>Invoice.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.language</td><td>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).</td></tr><tr><td>Invoice.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.text</td><td>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 &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded information is added later.</td></tr><tr><td>Invoice.contained (contained)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.contained</td><td>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.</td></tr><tr><td>Invoice.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.identifier</td><td>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).</td></tr><tr><td>Invoice.subject (subject)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.subject</td><td>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).</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.status.html">R4B: draft | issued | balanced | cancelled | entered-in-error (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.status (status)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: draft | issued | balanced | cancelled | entered-in-error (new))</td><td>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).</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.cancelledReason.html">R4B: Reason for cancellation of this Invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.cancelledReason (cancelledReason)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Reason for cancellation of this Invoice (new))</td><td>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.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.type.html">R4B: Type of Invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Type of Invoice (new))</td><td>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).</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.recipient.html">R4B: Recipient of this invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.recipient (recipient)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Recipient of this invoice (new))</td><td>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).</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.date.html">R4B: Invoice date / posting date (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.date (date)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Invoice date / posting date (new))</td><td>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.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.participant.html">R4B: Participant in creation of this Invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.participant (participant)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Participant in creation of this Invoice (new))</td><td>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).</td></tr><tr><td>Invoice.participant.role (role)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:role (R4B: Type of involvement in creation of this Invoice (new))</td><td>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).</td></tr><tr><td>Invoice.participant.actor (actor)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:actor (R4B: Individual who was involved (new))</td><td>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).</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.issuer.html">R4B: Issuing Organization of Invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.issuer (issuer)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Issuing Organization of Invoice (new))</td><td>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.</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.account.html">R4B: Account that is being balanced (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.account (account)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Account that is being balanced (new))</td><td>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.</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.lineItem.html">R4B: Line items of this Invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.lineItem (lineItem)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Line items of this Invoice (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.sequence (sequence)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:sequence (R4B: Sequence number of line item (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.chargeItem[x] (chargeItem[x])</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:chargeItem (R4B: Reference to ChargeItem containing details of this line item or an inline billing code (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.priceComponent (priceComponent)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:priceComponent (R4B: Components of total line item price (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.priceComponent.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:priceComponent.extension:type (R4B: base | surcharge | deduction | discount | tax | informational (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.priceComponent.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:priceComponent.extension:code (R4B: Code identifying the specific component (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.priceComponent.factor (factor)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:priceComponent.extension:factor (R4B: Factor used for calculating this component (new))</td><td>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.</td></tr><tr><td>Invoice.lineItem.priceComponent.amount (amount)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:priceComponent.extension:amount (R4B: Monetary amount associated with this component (new))</td><td>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.</td></tr></table><hr/><p><b>Group 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.lin.priceComponent.html">R4B: Components of total line item price (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.lineItem.priceComponent (priceComponent)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Components of total line item price (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.priceComponent.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:type (R4B: base | surcharge | deduction | discount | tax | informational (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.priceComponent.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:code (R4B: Code identifying the specific component (new))</td><td>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).</td></tr><tr><td>Invoice.lineItem.priceComponent.factor (factor)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:factor (R4B: Factor used for calculating this component (new))</td><td>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.</td></tr><tr><td>Invoice.lineItem.priceComponent.amount (amount)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:amount (R4B: Monetary amount associated with this component (new))</td><td>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.</td></tr></table><hr/><p><b>Group 12 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.totalNet.html">R4B: Net total of this Invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.totalNet (totalNet)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Net total of this Invoice (new))</td><td>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.</td></tr></table><hr/><p><b>Group 13 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.totalGross.html">R4B: Gross total of this Invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.totalGross (totalGross)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Gross total of this Invoice (new))</td><td>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.</td></tr></table><hr/><p><b>Group 14 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.paymentTerms.html">R4B: Payment details (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.paymentTerms (paymentTerms)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Payment details (new))</td><td>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.</td></tr></table><hr/><p><b>Group 15 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Invoice.note.html">R4B: Comments made about the invoice (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Invoice.note (note)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Comments made about the invoice (new))</td><td>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).</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueUri
                  value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r3"/>
      </extension>
    </valueInteger>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueUri
                  value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r3"/>
      </extension>
    </valueCode>
  </extension>
  <url
       value="http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Invoice-element-map-to-R3"/>
  <version value="0.1.0"/>
  <name value="R4BInvoiceElementMapToR3"/>
  <title
         value="Cross-version mapping for FHIR R4B Invoice to FHIR STU3 Basic"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-03-17T16:04:31.215661-05:00"/>
  <contact>
    <name value="FHIR Infrastructure"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <description
               value="This ConceptMap represents cross-version mappings for elements from a FHIR R4B Invoice to FHIR STU3."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <sourceUri value="http://hl7.org/fhir/4.3"/>
  <targetUri value="http://hl7.org/fhir/3.0"/>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target value="http://hl7.org/fhir/StructureDefinition/Basic"/>
    <targetVersion value="3.0.2"/>
    <element>
      <code value="Invoice.meta"/>
      <display value="meta"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Basic.meta"/>
        <display value="Basic.meta"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.implicitRules"/>
      <display value="implicitRules"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Basic.implicitRules"/>
        <display value="Basic.implicitRules"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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."/>
      </target>
    </element>
    <element>
      <code value="Invoice.language"/>
      <display value="language"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Basic.language"/>
        <display value="Basic.language"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.text"/>
      <display value="text"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Basic.text"/>
        <display value="Basic.text"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded information is added later."/>
      </target>
    </element>
    <element>
      <code value="Invoice.contained"/>
      <display value="contained"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Basic.contained"/>
        <display value="Basic.contained"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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."/>
      </target>
    </element>
    <element>
      <code value="Invoice.identifier"/>
      <display value="identifier"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Basic.identifier"/>
        <display value="Basic.identifier"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.subject"/>
      <display value="subject"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Basic.subject"/>
        <display value="Basic.subject"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.status"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.status"/>
      <display value="status"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.cancelledReason"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.cancelledReason"/>
      <display value="cancelledReason"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.type"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.type"/>
      <display value="type"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.recipient"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.recipient"/>
      <display value="recipient"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.date"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.date"/>
      <display value="date"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.participant"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.participant"/>
      <display value="participant"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.participant.role"/>
      <display value="role"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:role"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.participant.actor"/>
      <display value="actor"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:actor"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.issuer"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.issuer"/>
      <display value="issuer"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.account"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.account"/>
      <display value="account"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.lineItem"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.lineItem"/>
      <display value="lineItem"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.sequence"/>
      <display value="sequence"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:sequence"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.chargeItem[x]"/>
      <display value="chargeItem[x]"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:chargeItem"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent"/>
      <display value="priceComponent"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:priceComponent"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent.type"/>
      <display value="type"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:priceComponent.extension:type"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent.code"/>
      <display value="code"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:priceComponent.extension:code"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent.factor"/>
      <display value="factor"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:priceComponent.extension:factor"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent.amount"/>
      <display value="amount"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:priceComponent.extension:amount"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.lineItem.priceComponent"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.lineItem.priceComponent"/>
      <display value="priceComponent"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent.type"/>
      <display value="type"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:type"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent.code"/>
      <display value="code"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:code"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent.factor"/>
      <display value="factor"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:factor"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
    <element>
      <code value="Invoice.lineItem.priceComponent.amount"/>
      <display value="amount"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:amount"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.totalNet"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.totalNet"/>
      <display value="totalNet"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.totalGross"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.totalGross"/>
      <display value="totalGross"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.paymentTerms"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.paymentTerms"/>
      <display value="paymentTerms"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/Invoice"/>
    <sourceVersion value="4.3.0"/>
    <target
            value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Invoice.note"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="Invoice.note"/>
      <display value="note"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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)."/>
      </target>
    </element>
  </group>
</ConceptMap>