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 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). Invoice.text (text) is equivalent to Basic.text 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. Invoice.contained (contained) is equivalent to Basic.contained 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. Invoice.identifier (identifier) is equivalent to Basic.identifier 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). Invoice.subject (subject) is equivalent to Basic.subject 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). Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: draft | issued | balanced | cancelled | entered-in-error (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.status (status) maps to wider concept Extension (R4B: draft | issued | balanced | cancelled | entered-in-error (new)) 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). Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Reason for cancellation of this Invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.cancelledReason (cancelledReason) maps to wider concept Extension (R4B: Reason for cancellation of this Invoice (new)) 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. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Type of Invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.type (type) maps to wider concept Extension (R4B: Type of Invoice (new)) 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). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Recipient of this invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.recipient (recipient) maps to wider concept Extension (R4B: Recipient of this invoice (new)) 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). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Invoice date / posting date (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.date (date) maps to wider concept Extension (R4B: Invoice date / posting date (new)) 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. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Participant in creation of this Invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.participant (participant) maps to wider concept Extension (R4B: Participant in creation of this Invoice (new)) 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). Invoice.participant.role (role) maps to wider concept Extension.extension:role (R4B: Type of involvement in creation of this Invoice (new)) 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). Invoice.participant.actor (actor) maps to wider concept Extension.extension:actor (R4B: Individual who was involved (new)) 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). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Issuing Organization of Invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.issuer (issuer) maps to wider concept Extension (R4B: Issuing Organization of Invoice (new)) 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. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Account that is being balanced (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.account (account) maps to wider concept Extension (R4B: Account that is being balanced (new)) 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. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Line items of this Invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.lineItem (lineItem) maps to wider concept Extension (R4B: Line items of this Invoice (new)) 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). Invoice.lineItem.sequence (sequence) maps to wider concept Extension.extension:sequence (R4B: Sequence number of line item (new)) 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). Invoice.lineItem.chargeItem[x] (chargeItem[x]) maps to wider concept Extension.extension:chargeItem (R4B: Reference to ChargeItem containing details of this line item or an inline billing code (new)) 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). Invoice.lineItem.priceComponent (priceComponent) maps to wider concept Extension.extension:priceComponent (R4B: Components of total line item price (new)) 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). Invoice.lineItem.priceComponent.type (type) maps to wider concept Extension.extension:priceComponent.extension:type (R4B: base | surcharge | deduction | discount | tax | informational (new)) 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). Invoice.lineItem.priceComponent.code (code) maps to wider concept Extension.extension:priceComponent.extension:code (R4B: Code identifying the specific component (new)) 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). Invoice.lineItem.priceComponent.factor (factor) maps to wider concept Extension.extension:priceComponent.extension:factor (R4B: Factor used for calculating this component (new)) 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. Invoice.lineItem.priceComponent.amount (amount) maps to wider concept Extension.extension:priceComponent.extension:amount (R4B: Monetary amount associated with this component (new)) 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. Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Components of total line item price (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.lineItem.priceComponent (priceComponent) maps to wider concept Extension (R4B: Components of total line item price (new)) 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). Invoice.lineItem.priceComponent.type (type) maps to wider concept Extension.extension:type (R4B: base | surcharge | deduction | discount | tax | informational (new)) 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). Invoice.lineItem.priceComponent.code (code) maps to wider concept Extension.extension:code (R4B: Code identifying the specific component (new)) 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). Invoice.lineItem.priceComponent.factor (factor) maps to wider concept Extension.extension:factor (R4B: Factor used for calculating this component (new)) 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. Invoice.lineItem.priceComponent.amount (amount) maps to wider concept Extension.extension:amount (R4B: Monetary amount associated with this component (new)) 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. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Net total of this Invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.totalNet (totalNet) maps to wider concept Extension (R4B: Net total of this Invoice (new)) 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. Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Gross total of this Invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.totalGross (totalGross) maps to wider concept Extension (R4B: Gross total of this Invoice (new)) 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. Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Payment details (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.paymentTerms (paymentTerms) maps to wider concept Extension (R4B: Payment details (new)) 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. Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/Invoice|4.3.0 to R4B: Comments made about the invoice (new)version: 0.1.0) Source Code Relationship Target Code Comment Invoice.note (note) maps to wider concept Extension (R4B: Comments made about the invoice (new)) 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).
Cross-version mapping for FHIR R4B Invoice to FHIR STU3 Basic
This ConceptMap represents cross-version mappings for elements from a FHIR R4B Invoice to FHIR STU3.
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 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 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 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 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 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 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).
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).
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.
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).
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).
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.
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 `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 `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).
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.
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.
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 `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 `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 `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 `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 `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 `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 `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.
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.
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.
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.
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).