Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4-Invoice-element-map-to-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R4InvoiceElementMapToR5 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R4 Invoice to FHIR R5.
Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/5.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1 to Invoiceversion: 5.0.0)
| Source Code | Relationship | Target Code | Comment |
| Invoice.meta (meta) | is equivalent to | Invoice.meta | Element `Invoice.meta` is mapped to FHIR R5 element `Invoice.meta` as `Equivalent`. |
| Invoice.implicitRules (implicitRules) | is equivalent to | Invoice.implicitRules | Element `Invoice.implicitRules` is mapped to FHIR R5 element `Invoice.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. |
| Invoice.language (language) | is equivalent to | Invoice.language | Element `Invoice.language` is mapped to FHIR R5 element `Invoice.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
| Invoice.text (text) | is equivalent to | Invoice.text | Element `Invoice.text` is mapped to FHIR R5 element `Invoice.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
| Invoice.contained (contained) | is equivalent to | Invoice.contained | Element `Invoice.contained` is mapped to FHIR R5 element `Invoice.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
| Invoice.identifier (identifier) | is equivalent to | Invoice.identifier | Element `Invoice.identifier` is mapped to FHIR R5 element `Invoice.identifier` as `Equivalent`. |
| Invoice.status (status) | is equivalent to | Invoice.status | Element `Invoice.status` is mapped to FHIR R5 element `Invoice.status` as `Equivalent`. |
| Invoice.cancelledReason (cancelledReason) | is equivalent to | Invoice.cancelledReason | Element `Invoice.cancelledReason` is mapped to FHIR R5 element `Invoice.cancelledReason` as `Equivalent`. Derived Profiles may choose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled. |
| Invoice.type (type) | is equivalent to | Invoice.type | Element `Invoice.type` is mapped to FHIR R5 element `Invoice.type` as `Equivalent`. |
| Invoice.subject (subject) | is equivalent to | Invoice.subject | Element `Invoice.subject` is mapped to FHIR R5 element `Invoice.subject` as `Equivalent`. |
| Invoice.recipient (recipient) | is equivalent to | Invoice.recipient | Element `Invoice.recipient` is mapped to FHIR R5 element `Invoice.recipient` as `Equivalent`. |
| Invoice.date (date) | is equivalent to | Invoice.date | Element `Invoice.date` is mapped to FHIR R5 element `Invoice.date` as `Equivalent`. The list of types may be constrained as appropriate for the type of charge item. |
| Invoice.participant (participant) | is broader than | Invoice.participant | Element `Invoice.participant` is mapped to FHIR R5 element `Invoice.participant` as `Equivalent`. |
| Invoice.participant.role (role) | is equivalent to | Invoice.participant.role | Element `Invoice.participant.role` is mapped to FHIR R5 element `Invoice.participant.role` as `Equivalent`. |
| Invoice.participant.actor (actor) | is equivalent to | Invoice.participant.actor | Element `Invoice.participant.actor` is mapped to FHIR R5 element `Invoice.participant.actor` as `Equivalent`. |
| Invoice.issuer (issuer) | is equivalent to | Invoice.issuer | Element `Invoice.issuer` is mapped to FHIR R5 element `Invoice.issuer` as `Equivalent`. 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. |
| Invoice.account (account) | is equivalent to | Invoice.account | Element `Invoice.account` is mapped to FHIR R5 element `Invoice.account` as `Equivalent`. 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. |
| Invoice.lineItem (lineItem) | is broader than | Invoice.lineItem | Element `Invoice.lineItem` is mapped to FHIR R5 element `Invoice.lineItem` as `Equivalent`. |
| Invoice.lineItem.sequence (sequence) | is equivalent to | Invoice.lineItem.sequence | Element `Invoice.lineItem.sequence` is mapped to FHIR R5 element `Invoice.lineItem.sequence` as `Equivalent`. |
| Invoice.lineItem.chargeItem[x] (chargeItem[x]) | is equivalent to | Invoice.lineItem.chargeItem[x] | Element `Invoice.lineItem.chargeItem[x]` is mapped to FHIR R5 element `Invoice.lineItem.chargeItem[x]` as `Equivalent`. The target context `Invoice.lineItem.chargeItem[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Invoice.lineItem`. |
| Invoice.lineItem.priceComponent (priceComponent) | is broader than | Invoice.lineItem.priceComponent | Element `Invoice.lineItem.priceComponent` is mapped to FHIR R5 element `Invoice.lineItem.priceComponent` as `Equivalent`. |
| Invoice.totalPriceComponent (totalPriceComponent) | is broader than | Invoice.totalPriceComponent | Element `Invoice.totalPriceComponent` is mapped to FHIR R5 element `Invoice.totalPriceComponent` as `SourceIsBroaderThanTarget`. The mappings for `Invoice.totalPriceComponent` do not cover the following types: Invoice.lineItem.priceComponent. |
| Invoice.totalNet (totalNet) | is equivalent to | Invoice.totalNet | Element `Invoice.totalNet` is mapped to FHIR R5 element `Invoice.totalNet` as `Equivalent`. 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. |
| Invoice.totalGross (totalGross) | is equivalent to | Invoice.totalGross | Element `Invoice.totalGross` is mapped to FHIR R5 element `Invoice.totalGross` as `Equivalent`. 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. |
| Invoice.paymentTerms (paymentTerms) | is equivalent to | Invoice.paymentTerms | Element `Invoice.paymentTerms` is mapped to FHIR R5 element `Invoice.paymentTerms` as `Equivalent`. Derived Profiles may chose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled. |
| Invoice.note (note) | is equivalent to | Invoice.note | Element `Invoice.note` is mapped to FHIR R5 element `Invoice.note` as `Equivalent`. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1 to R4: priceComponentversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Invoice.lineItem.priceComponent (priceComponent) | is equivalent to | Extension (R4: priceComponent) | Element `Invoice.lineItem.priceComponent` is mapped to FHIR R5 element `Invoice.lineItem.priceComponent` as `Equivalent`. |
| Invoice.lineItem.priceComponent.type (type) | is equivalent to | Extension.extension:type (R4: base | surcharge | deduction | discount | tax | informational (new)) | Element `Invoice.lineItem.priceComponent.type` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`. Element `Invoice.lineItem.priceComponent.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
| Invoice.lineItem.priceComponent.code (code) | is equivalent to | Extension.extension:code (R4: Code identifying the specific component (new)) | Element `Invoice.lineItem.priceComponent.code` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`. Element `Invoice.lineItem.priceComponent.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
| Invoice.lineItem.priceComponent.factor (factor) | is equivalent to | Extension.extension:factor (R4: Factor used for calculating this component (new)) | Element `Invoice.lineItem.priceComponent.factor` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`. Element `Invoice.lineItem.priceComponent.factor` has no mapping targets in FHIR R5. 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. |
| Invoice.lineItem.priceComponent.amount (amount) | is equivalent to | Extension.extension:amount (R4: Monetary amount associated with this component (new)) | Element `Invoice.lineItem.priceComponent.amount` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`. Element `Invoice.lineItem.priceComponent.amount` has no mapping targets in FHIR R5. 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. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1 to R4: base | surcharge | deduction | discount | tax | informational (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Invoice.lineItem.priceComponent.type (type) | is equivalent to | Extension (R4: base | surcharge | deduction | discount | tax | informational (new)) | Element `Invoice.lineItem.priceComponent.type` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`. Element `Invoice.lineItem.priceComponent.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1 to R4: Code identifying the specific component (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Invoice.lineItem.priceComponent.code (code) | is equivalent to | Extension (R4: Code identifying the specific component (new)) | Element `Invoice.lineItem.priceComponent.code` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`. Element `Invoice.lineItem.priceComponent.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1 to R4: Factor used for calculating this component (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Invoice.lineItem.priceComponent.factor (factor) | is equivalent to | Extension (R4: Factor used for calculating this component (new)) | Element `Invoice.lineItem.priceComponent.factor` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`. Element `Invoice.lineItem.priceComponent.factor` has no mapping targets in FHIR R5. 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. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1 to R4: Monetary amount associated with this component (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Invoice.lineItem.priceComponent.amount (amount) | is equivalent to | Extension (R4: Monetary amount associated with this component (new)) | Element `Invoice.lineItem.priceComponent.amount` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`. Element `Invoice.lineItem.priceComponent.amount` has no mapping targets in FHIR R5. 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. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4.r5#0.1.0 based on FHIR 5.0.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change