FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

Narrative

Note: links and images are rebased to the (stated) source

Source1

{
  "resourceType": "ConceptMap",
  "id": "R4-Invoice-element-map-to-R5",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4-Invoice-element-map-to-R5",
  "version": "0.1.0",
  "name": "R4InvoiceElementMapToR5",
  "title": "Cross-version mapping for FHIR R4 Invoice to FHIR R5 Invoice",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:35.360986-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4 Invoice to FHIR R5.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceScopeCanonical": "http://hl7.org/fhir/4.0",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1",
      "target": "http://hl7.org/fhir/StructureDefinition/Invoice|5.0.0",
      "element": [
        {
          "code": "Invoice.meta",
          "display": "meta",
          "target": [
            {
              "code": "Invoice.meta",
              "display": "Invoice.meta",
              "relationship": "equivalent",
              "comment": "Element `Invoice.meta` is mapped to FHIR R5 element `Invoice.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Invoice.implicitRules",
              "display": "Invoice.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Invoice.implicitRules` is mapped to FHIR R5 element `Invoice.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "Invoice.language",
          "display": "language",
          "target": [
            {
              "code": "Invoice.language",
              "display": "Invoice.language",
              "relationship": "equivalent",
              "comment": "Element `Invoice.language` is mapped to FHIR R5 element `Invoice.language` as `Equivalent`.\nLanguage is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."
            }
          ]
        },
        {
          "code": "Invoice.text",
          "display": "text",
          "target": [
            {
              "code": "Invoice.text",
              "display": "Invoice.text",
              "relationship": "equivalent",
              "comment": "Element `Invoice.text` is mapped to FHIR R5 element `Invoice.text` as `Equivalent`.\nContained 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."
            }
          ]
        },
        {
          "code": "Invoice.contained",
          "display": "contained",
          "target": [
            {
              "code": "Invoice.contained",
              "display": "Invoice.contained",
              "relationship": "equivalent",
              "comment": "Element `Invoice.contained` is mapped to FHIR R5 element `Invoice.contained` as `Equivalent`.\nThis should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."
            }
          ]
        },
        {
          "code": "Invoice.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Invoice.identifier",
              "display": "Invoice.identifier",
              "relationship": "equivalent",
              "comment": "Element `Invoice.identifier` is mapped to FHIR R5 element `Invoice.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.status",
          "display": "status",
          "target": [
            {
              "code": "Invoice.status",
              "display": "Invoice.status",
              "relationship": "equivalent",
              "comment": "Element `Invoice.status` is mapped to FHIR R5 element `Invoice.status` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.cancelledReason",
          "display": "cancelledReason",
          "target": [
            {
              "code": "Invoice.cancelledReason",
              "display": "Invoice.cancelledReason",
              "relationship": "equivalent",
              "comment": "Element `Invoice.cancelledReason` is mapped to FHIR R5 element `Invoice.cancelledReason` as `Equivalent`.\nDerived Profiles may choose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled."
            }
          ]
        },
        {
          "code": "Invoice.type",
          "display": "type",
          "target": [
            {
              "code": "Invoice.type",
              "display": "Invoice.type",
              "relationship": "equivalent",
              "comment": "Element `Invoice.type` is mapped to FHIR R5 element `Invoice.type` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.subject",
          "display": "subject",
          "target": [
            {
              "code": "Invoice.subject",
              "display": "Invoice.subject",
              "relationship": "equivalent",
              "comment": "Element `Invoice.subject` is mapped to FHIR R5 element `Invoice.subject` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.recipient",
          "display": "recipient",
          "target": [
            {
              "code": "Invoice.recipient",
              "display": "Invoice.recipient",
              "relationship": "equivalent",
              "comment": "Element `Invoice.recipient` is mapped to FHIR R5 element `Invoice.recipient` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.date",
          "display": "date",
          "target": [
            {
              "code": "Invoice.date",
              "display": "Invoice.date",
              "relationship": "equivalent",
              "comment": "Element `Invoice.date` is mapped to FHIR R5 element `Invoice.date` as `Equivalent`.\nThe list of types may be constrained as appropriate for the type of charge item."
            }
          ]
        },
        {
          "code": "Invoice.participant",
          "display": "participant",
          "target": [
            {
              "code": "Invoice.participant",
              "display": "Invoice.participant",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Invoice.participant` is mapped to FHIR R5 element `Invoice.participant` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.participant.role",
          "display": "role",
          "target": [
            {
              "code": "Invoice.participant.role",
              "display": "Invoice.participant.role",
              "relationship": "equivalent",
              "comment": "Element `Invoice.participant.role` is mapped to FHIR R5 element `Invoice.participant.role` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.participant.actor",
          "display": "actor",
          "target": [
            {
              "code": "Invoice.participant.actor",
              "display": "Invoice.participant.actor",
              "relationship": "equivalent",
              "comment": "Element `Invoice.participant.actor` is mapped to FHIR R5 element `Invoice.participant.actor` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.issuer",
          "display": "issuer",
          "target": [
            {
              "code": "Invoice.issuer",
              "display": "Invoice.issuer",
              "relationship": "equivalent",
              "comment": "Element `Invoice.issuer` is mapped to FHIR R5 element `Invoice.issuer` as `Equivalent`.\nPractitioners and Devices can be associated with multiple organizations. It has to be made clear, on behalf of which Organization the services have been rendered."
            }
          ]
        },
        {
          "code": "Invoice.account",
          "display": "account",
          "target": [
            {
              "code": "Invoice.account",
              "display": "Invoice.account",
              "relationship": "equivalent",
              "comment": "Element `Invoice.account` is mapped to FHIR R5 element `Invoice.account` as `Equivalent`.\nSystems 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."
            }
          ]
        },
        {
          "code": "Invoice.lineItem",
          "display": "lineItem",
          "target": [
            {
              "code": "Invoice.lineItem",
              "display": "Invoice.lineItem",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Invoice.lineItem` is mapped to FHIR R5 element `Invoice.lineItem` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.lineItem.sequence",
          "display": "sequence",
          "target": [
            {
              "code": "Invoice.lineItem.sequence",
              "display": "Invoice.lineItem.sequence",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.sequence` is mapped to FHIR R5 element `Invoice.lineItem.sequence` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.lineItem.chargeItem[x]",
          "display": "chargeItem[x]",
          "target": [
            {
              "code": "Invoice.lineItem.chargeItem[x]",
              "display": "Invoice.lineItem.chargeItem[x]",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.chargeItem[x]` is mapped to FHIR R5 element `Invoice.lineItem.chargeItem[x]` as `Equivalent`.\nThe 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`."
            }
          ]
        },
        {
          "code": "Invoice.lineItem.priceComponent",
          "display": "priceComponent",
          "target": [
            {
              "code": "Invoice.lineItem.priceComponent",
              "display": "Invoice.lineItem.priceComponent",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Invoice.lineItem.priceComponent` is mapped to FHIR R5 element `Invoice.lineItem.priceComponent` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.totalPriceComponent",
          "display": "totalPriceComponent",
          "target": [
            {
              "code": "Invoice.totalPriceComponent",
              "display": "Invoice.totalPriceComponent",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Invoice.totalPriceComponent` is mapped to FHIR R5 element `Invoice.totalPriceComponent` as `SourceIsBroaderThanTarget`.\nThe mappings for `Invoice.totalPriceComponent` do not cover the following types: Invoice.lineItem.priceComponent."
            }
          ]
        },
        {
          "code": "Invoice.totalNet",
          "display": "totalNet",
          "target": [
            {
              "code": "Invoice.totalNet",
              "display": "Invoice.totalNet",
              "relationship": "equivalent",
              "comment": "Element `Invoice.totalNet` is mapped to FHIR R5 element `Invoice.totalNet` as `Equivalent`.\nThere 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."
            }
          ]
        },
        {
          "code": "Invoice.totalGross",
          "display": "totalGross",
          "target": [
            {
              "code": "Invoice.totalGross",
              "display": "Invoice.totalGross",
              "relationship": "equivalent",
              "comment": "Element `Invoice.totalGross` is mapped to FHIR R5 element `Invoice.totalGross` as `Equivalent`.\nThere 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."
            }
          ]
        },
        {
          "code": "Invoice.paymentTerms",
          "display": "paymentTerms",
          "target": [
            {
              "code": "Invoice.paymentTerms",
              "display": "Invoice.paymentTerms",
              "relationship": "equivalent",
              "comment": "Element `Invoice.paymentTerms` is mapped to FHIR R5 element `Invoice.paymentTerms` as `Equivalent`.\nDerived Profiles may chose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled."
            }
          ]
        },
        {
          "code": "Invoice.note",
          "display": "note",
          "target": [
            {
              "code": "Invoice.note",
              "display": "Invoice.note",
              "relationship": "equivalent",
              "comment": "Element `Invoice.note` is mapped to FHIR R5 element `Invoice.note` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Invoice.lineItem.priceComponent|0.1.0",
      "element": [
        {
          "code": "Invoice.lineItem.priceComponent",
          "display": "priceComponent",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent` is mapped to FHIR R5 element `Invoice.lineItem.priceComponent` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Invoice.lineItem.priceComponent.type",
          "display": "type",
          "target": [
            {
              "code": "Extension.extension:type",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent.type` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`.\nElement `Invoice.lineItem.priceComponent.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Invoice.lineItem.priceComponent.code",
          "display": "code",
          "target": [
            {
              "code": "Extension.extension:code",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent.code` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`.\nElement `Invoice.lineItem.priceComponent.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Invoice.lineItem.priceComponent.factor",
          "display": "factor",
          "target": [
            {
              "code": "Extension.extension:factor",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent.factor` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`.\nElement `Invoice.lineItem.priceComponent.factor` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThere 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."
            }
          ]
        },
        {
          "code": "Invoice.lineItem.priceComponent.amount",
          "display": "amount",
          "target": [
            {
              "code": "Extension.extension:amount",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent.amount` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`.\nElement `Invoice.lineItem.priceComponent.amount` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThere is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes  (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Invoice.lineItem.priceComponent.type|0.1.0",
      "element": [
        {
          "code": "Invoice.lineItem.priceComponent.type",
          "display": "type",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent.type` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`.\nElement `Invoice.lineItem.priceComponent.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Invoice.lineItem.priceComponent.code|0.1.0",
      "element": [
        {
          "code": "Invoice.lineItem.priceComponent.code",
          "display": "code",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent.code` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`.\nElement `Invoice.lineItem.priceComponent.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Invoice.lineItem.priceComponent.factor|0.1.0",
      "element": [
        {
          "code": "Invoice.lineItem.priceComponent.factor",
          "display": "factor",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent.factor` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`.\nElement `Invoice.lineItem.priceComponent.factor` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThere is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes  (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Invoice|4.0.1",
      "target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Invoice.lineItem.priceComponent.amount|0.1.0",
      "element": [
        {
          "code": "Invoice.lineItem.priceComponent.amount",
          "display": "amount",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Invoice.lineItem.priceComponent.amount` has a context of Invoice.lineItem.priceComponent based on following the parent source element upwards and mapping to `Invoice`.\nElement `Invoice.lineItem.priceComponent.amount` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThere 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."
            }
          ]
        }
      ]
    }
  ]
}