FHIR IG analytics| Package | hl7.fhir.uv.xver-r3.r4 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R3-ChargeItem-element-map-to-R4.json |
| FHIR Version | R4 |
| Source | http://hl7.org/fhir/uv/xver-r3.r4/0.1.0/ConceptMap-R3-ChargeItem-element-map-to-R4.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R3-ChargeItem-element-map-to-R4 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:03:23.2216689-05:00 |
| Name | R3ChargeItemElementMapToR4 |
| Title | Cross-version mapping for FHIR STU3 ChargeItem to FHIR R4 ChargeItem |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR STU3 ChargeItem to FHIR R4. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R3-ChargeItem-element-map-to-R4
Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ChargeItem|3.0.2 to ChargeItemversion: 4.0.1)
| Source Code | Relationship | Target Code | Comment |
| ChargeItem.meta (meta) | is equivalent to | ChargeItem.meta | Element `ChargeItem.meta` is mapped to FHIR R4 element `ChargeItem.meta` as `Equivalent`. |
| ChargeItem.implicitRules (implicitRules) | is equivalent to | ChargeItem.implicitRules | Element `ChargeItem.implicitRules` is mapped to FHIR R4 element `ChargeItem.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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
| ChargeItem.language (language) | is equivalent to | ChargeItem.language | Element `ChargeItem.language` is mapped to FHIR R4 element `ChargeItem.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). |
| ChargeItem.text (text) | is equivalent to | ChargeItem.text | Element `ChargeItem.text` is mapped to FHIR R4 element `ChargeItem.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 in formation is added later. |
| ChargeItem.contained (contained) | is equivalent to | ChargeItem.contained | Element `ChargeItem.contained` is mapped to FHIR R4 element `ChargeItem.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. |
| ChargeItem.identifier (identifier) | is equivalent to | ChargeItem.identifier | Element `ChargeItem.identifier` is mapped to FHIR R4 element `ChargeItem.identifier` as `SourceIsNarrowerThanTarget`. |
| ChargeItem.definition (definition) | is equivalent to | ChargeItem.definitionUri | Element `ChargeItem.definition` is mapped to FHIR R4 element `ChargeItem.definitionUri` as `Equivalent`. Target Resource is yet to be defined as a container that holds information about list prices and rules applicable to the charge item code. Once defined, change type back to Reference(Definition Type). |
| ChargeItem.status (status) | is equivalent to | ChargeItem.status | Element `ChargeItem.status` is mapped to FHIR R4 element `ChargeItem.status` as `Equivalent`. Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. This element is labeled as a modifier because the status contains the code entered-in-error that marks the charge item as not currently valid. |
| ChargeItem.partOf (partOf) | is equivalent to | ChargeItem.partOf | Element `ChargeItem.partOf` is mapped to FHIR R4 element `ChargeItem.partOf` as `Equivalent`. |
| ChargeItem.code (code) | is equivalent to | ChargeItem.code | Element `ChargeItem.code` is mapped to FHIR R4 element `ChargeItem.code` as `Equivalent`. |
| ChargeItem.subject (subject) | is equivalent to | ChargeItem.subject | Element `ChargeItem.subject` is mapped to FHIR R4 element `ChargeItem.subject` as `Equivalent`. |
| ChargeItem.context (context) | is equivalent to | ChargeItem.context | Element `ChargeItem.context` is mapped to FHIR R4 element `ChargeItem.context` as `Equivalent`. |
| ChargeItem.occurrence[x] (occurrence[x]) | is equivalent to | ChargeItem.occurrence[x] | Element `ChargeItem.occurrence[x]` is mapped to FHIR R4 element `ChargeItem.occurrence[x]` as `Equivalent`. The target context `ChargeItem.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ChargeItem`. The list of types may be constrained as appropriate for the type of charge item. |
| ChargeItem.participant (participant) | maps to wider concept | ChargeItem.performer | Element `ChargeItem.participant` is mapped to FHIR R4 element `ChargeItem.performer` as `Equivalent`. |
| ChargeItem.participant.role (role) | is equivalent to | ChargeItem.performer.function | Element `ChargeItem.participant.role` is mapped to FHIR R4 element `ChargeItem.performer.function` as `Equivalent`. |
| ChargeItem.participant.actor (actor) | is equivalent to | ChargeItem.performer.actor | Element `ChargeItem.participant.actor` is mapped to FHIR R4 element `ChargeItem.performer.actor` as `Equivalent`. |
| ChargeItem.performingOrganization (performingOrganization) | is equivalent to | ChargeItem.performingOrganization | Element `ChargeItem.performingOrganization` is mapped to FHIR R4 element `ChargeItem.performingOrganization` 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. |
| ChargeItem.requestingOrganization (requestingOrganization) | is equivalent to | ChargeItem.requestingOrganization | Element `ChargeItem.requestingOrganization` is mapped to FHIR R4 element `ChargeItem.requestingOrganization` as `Equivalent`. The rendered Service may not be associated with a Request. It has to be made clear, ob which Organization's Request, the services have been rendered. (In many cases, this may just be the Department associated with the Encounter.location). |
| ChargeItem.quantity (quantity) | is equivalent to | ChargeItem.quantity | Element `ChargeItem.quantity` is mapped to FHIR R4 element `ChargeItem.quantity` as `Equivalent`. In many cases this may just be a value, if the underlying units are implicit in the definition of the charge item code. |
| ChargeItem.bodysite (bodysite) | is equivalent to | ChargeItem.bodysite | Element `ChargeItem.bodysite` is mapped to FHIR R4 element `ChargeItem.bodysite` as `Equivalent`. Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [body-site-instance](https://hl7.org/fhir/extension-body-site-instance.html). May be a summary code, or a reference to a very precise definition of the location, or both. |
| ChargeItem.factorOverride (factorOverride) | is equivalent to | ChargeItem.factorOverride | Element `ChargeItem.factorOverride` is mapped to FHIR R4 element `ChargeItem.factorOverride` as `Equivalent`. There is no reason to carry the factor in the instance of a ChargeItem unless special circumstances require a manual override. The factors are usually defined by a set of rules 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 overriden. |
| ChargeItem.priceOverride (priceOverride) | is equivalent to | ChargeItem.priceOverride | Element `ChargeItem.priceOverride` is mapped to FHIR R4 element `ChargeItem.priceOverride` 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 overriden. |
| ChargeItem.overrideReason (overrideReason) | is equivalent to | ChargeItem.overrideReason | Element `ChargeItem.overrideReason` is mapped to FHIR R4 element `ChargeItem.overrideReason` as `Equivalent`. Derived Profiles may chose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled. |
| ChargeItem.enterer (enterer) | is equivalent to | ChargeItem.enterer | Element `ChargeItem.enterer` is mapped to FHIR R4 element `ChargeItem.enterer` as `Equivalent`. The enterer is also te person considered responsible for factor/priceOverrides if applicable. |
| ChargeItem.enteredDate (enteredDate) | is equivalent to | ChargeItem.enteredDate | Element `ChargeItem.enteredDate` is mapped to FHIR R4 element `ChargeItem.enteredDate` as `Equivalent`. The actual date when the service associated with the charge has been rendered is captured in occurrence[x]. |
| ChargeItem.reason (reason) | is equivalent to | ChargeItem.reason | Element `ChargeItem.reason` is mapped to FHIR R4 element `ChargeItem.reason` as `Equivalent`. If the application of the charge item requires a reason to be given, it can be captured here. Textual reasons can be captured using reasonCode.text. |
| ChargeItem.service (service) | is equivalent to | ChargeItem.service | Element `ChargeItem.service` is mapped to FHIR R4 element `ChargeItem.service` as `Equivalent`. |
| ChargeItem.account (account) | is equivalent to | ChargeItem.account | Element `ChargeItem.account` is mapped to FHIR R4 element `ChargeItem.account` as `Equivalent`. Systems posting the ChargeItems may 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. |
| ChargeItem.note (note) | is equivalent to | ChargeItem.note | Element `ChargeItem.note` is mapped to FHIR R4 element `ChargeItem.note` as `Equivalent`. |
| ChargeItem.supportingInformation (supportingInformation) | is equivalent to | ChargeItem.supportingInformation | Element `ChargeItem.supportingInformation` is mapped to FHIR R4 element `ChargeItem.supportingInformation` as `Equivalent`. |
{
"resourceType": "ConceptMap",
"id": "R3-ChargeItem-element-map-to-R4",
"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-r3.r4"
}
]
}
},
{
"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-r3.r4"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R3-ChargeItem-element-map-to-R4",
"version": "0.1.0",
"name": "R3ChargeItemElementMapToR4",
"title": "Cross-version mapping for FHIR STU3 ChargeItem to FHIR R4 ChargeItem",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:03:23.2216689-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 STU3 ChargeItem to FHIR R4.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceCanonical": "http://hl7.org/fhir/3.0",
"targetUri": "http://hl7.org/fhir/4.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/ChargeItem",
"sourceVersion": "3.0.2",
"target": "http://hl7.org/fhir/StructureDefinition/ChargeItem",
"targetVersion": "4.0.1",
"element": [
{
"code": "ChargeItem.meta",
"display": "meta",
"target": [
{
"code": "ChargeItem.meta",
"display": "ChargeItem.meta",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.meta` is mapped to FHIR R4 element `ChargeItem.meta` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.implicitRules",
"display": "implicitRules",
"target": [
{
"code": "ChargeItem.implicitRules",
"display": "ChargeItem.implicitRules",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.implicitRules` is mapped to FHIR R4 element `ChargeItem.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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."
}
]
},
{
"code": "ChargeItem.language",
"display": "language",
"target": [
{
"code": "ChargeItem.language",
"display": "ChargeItem.language",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.language` is mapped to FHIR R4 element `ChargeItem.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": "ChargeItem.text",
"display": "text",
"target": [
{
"code": "ChargeItem.text",
"display": "ChargeItem.text",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.text` is mapped to FHIR R4 element `ChargeItem.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 in formation is added later."
}
]
},
{
"code": "ChargeItem.contained",
"display": "contained",
"target": [
{
"code": "ChargeItem.contained",
"display": "ChargeItem.contained",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.contained` is mapped to FHIR R4 element `ChargeItem.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."
}
]
},
{
"code": "ChargeItem.identifier",
"display": "identifier",
"target": [
{
"code": "ChargeItem.identifier",
"display": "ChargeItem.identifier",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.identifier` is mapped to FHIR R4 element `ChargeItem.identifier` as `SourceIsNarrowerThanTarget`."
}
]
},
{
"code": "ChargeItem.definition",
"display": "definition",
"target": [
{
"code": "ChargeItem.definitionUri",
"display": "ChargeItem.definitionUri",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.definition` is mapped to FHIR R4 element `ChargeItem.definitionUri` as `Equivalent`.\nTarget Resource is yet to be defined as a container that holds information about list prices and rules applicable to the charge item code. Once defined, change type back to Reference(Definition Type)."
}
]
},
{
"code": "ChargeItem.status",
"display": "status",
"target": [
{
"code": "ChargeItem.status",
"display": "ChargeItem.status",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.status` is mapped to FHIR R4 element `ChargeItem.status` as `Equivalent`.\nUnknown does not represent \"other\" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.\n\nThis element is labeled as a modifier because the status contains the code entered-in-error that marks the charge item as not currently valid."
}
]
},
{
"code": "ChargeItem.partOf",
"display": "partOf",
"target": [
{
"code": "ChargeItem.partOf",
"display": "ChargeItem.partOf",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.partOf` is mapped to FHIR R4 element `ChargeItem.partOf` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.code",
"display": "code",
"target": [
{
"code": "ChargeItem.code",
"display": "ChargeItem.code",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.code` is mapped to FHIR R4 element `ChargeItem.code` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.subject",
"display": "subject",
"target": [
{
"code": "ChargeItem.subject",
"display": "ChargeItem.subject",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.subject` is mapped to FHIR R4 element `ChargeItem.subject` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.context",
"display": "context",
"target": [
{
"code": "ChargeItem.context",
"display": "ChargeItem.context",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.context` is mapped to FHIR R4 element `ChargeItem.context` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.occurrence[x]",
"display": "occurrence[x]",
"target": [
{
"code": "ChargeItem.occurrence[x]",
"display": "ChargeItem.occurrence[x]",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.occurrence[x]` is mapped to FHIR R4 element `ChargeItem.occurrence[x]` as `Equivalent`.\nThe target context `ChargeItem.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ChargeItem`.\nThe list of types may be constrained as appropriate for the type of charge item."
}
]
},
{
"code": "ChargeItem.participant",
"display": "participant",
"target": [
{
"code": "ChargeItem.performer",
"display": "ChargeItem.performer",
"equivalence": "wider",
"comment": "Element `ChargeItem.participant` is mapped to FHIR R4 element `ChargeItem.performer` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.participant.role",
"display": "role",
"target": [
{
"code": "ChargeItem.performer.function",
"display": "ChargeItem.performer.function",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.participant.role` is mapped to FHIR R4 element `ChargeItem.performer.function` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.participant.actor",
"display": "actor",
"target": [
{
"code": "ChargeItem.performer.actor",
"display": "ChargeItem.performer.actor",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.participant.actor` is mapped to FHIR R4 element `ChargeItem.performer.actor` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.performingOrganization",
"display": "performingOrganization",
"target": [
{
"code": "ChargeItem.performingOrganization",
"display": "ChargeItem.performingOrganization",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.performingOrganization` is mapped to FHIR R4 element `ChargeItem.performingOrganization` 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": "ChargeItem.requestingOrganization",
"display": "requestingOrganization",
"target": [
{
"code": "ChargeItem.requestingOrganization",
"display": "ChargeItem.requestingOrganization",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.requestingOrganization` is mapped to FHIR R4 element `ChargeItem.requestingOrganization` as `Equivalent`.\nThe rendered Service may not be associated with a Request. It has to be made clear, ob which Organization's Request, the services have been rendered. (In many cases, this may just be the Department associated with the Encounter.location)."
}
]
},
{
"code": "ChargeItem.quantity",
"display": "quantity",
"target": [
{
"code": "ChargeItem.quantity",
"display": "ChargeItem.quantity",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.quantity` is mapped to FHIR R4 element `ChargeItem.quantity` as `Equivalent`.\nIn many cases this may just be a value, if the underlying units are implicit in the definition of the charge item code."
}
]
},
{
"code": "ChargeItem.bodysite",
"display": "bodysite",
"target": [
{
"code": "ChargeItem.bodysite",
"display": "ChargeItem.bodysite",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.bodysite` is mapped to FHIR R4 element `ChargeItem.bodysite` as `Equivalent`.\nOnly used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [body-site-instance](https://hl7.org/fhir/extension-body-site-instance.html). May be a summary code, or a reference to a very precise definition of the location, or both."
}
]
},
{
"code": "ChargeItem.factorOverride",
"display": "factorOverride",
"target": [
{
"code": "ChargeItem.factorOverride",
"display": "ChargeItem.factorOverride",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.factorOverride` is mapped to FHIR R4 element `ChargeItem.factorOverride` as `Equivalent`.\nThere is no reason to carry the factor in the instance of a ChargeItem unless special circumstances require a manual override. The factors are usually defined by a set of rules 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 overriden."
}
]
},
{
"code": "ChargeItem.priceOverride",
"display": "priceOverride",
"target": [
{
"code": "ChargeItem.priceOverride",
"display": "ChargeItem.priceOverride",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.priceOverride` is mapped to FHIR R4 element `ChargeItem.priceOverride` 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 overriden."
}
]
},
{
"code": "ChargeItem.overrideReason",
"display": "overrideReason",
"target": [
{
"code": "ChargeItem.overrideReason",
"display": "ChargeItem.overrideReason",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.overrideReason` is mapped to FHIR R4 element `ChargeItem.overrideReason` as `Equivalent`.\nDerived Profiles may chose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled."
}
]
},
{
"code": "ChargeItem.enterer",
"display": "enterer",
"target": [
{
"code": "ChargeItem.enterer",
"display": "ChargeItem.enterer",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.enterer` is mapped to FHIR R4 element `ChargeItem.enterer` as `Equivalent`.\nThe enterer is also te person considered responsible for factor/priceOverrides if applicable."
}
]
},
{
"code": "ChargeItem.enteredDate",
"display": "enteredDate",
"target": [
{
"code": "ChargeItem.enteredDate",
"display": "ChargeItem.enteredDate",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.enteredDate` is mapped to FHIR R4 element `ChargeItem.enteredDate` as `Equivalent`.\nThe actual date when the service associated with the charge has been rendered is captured in occurrence[x]."
}
]
},
{
"code": "ChargeItem.reason",
"display": "reason",
"target": [
{
"code": "ChargeItem.reason",
"display": "ChargeItem.reason",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.reason` is mapped to FHIR R4 element `ChargeItem.reason` as `Equivalent`.\nIf the application of the charge item requires a reason to be given, it can be captured here. Textual reasons can be captured using reasonCode.text."
}
]
},
{
"code": "ChargeItem.service",
"display": "service",
"target": [
{
"code": "ChargeItem.service",
"display": "ChargeItem.service",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.service` is mapped to FHIR R4 element `ChargeItem.service` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.account",
"display": "account",
"target": [
{
"code": "ChargeItem.account",
"display": "ChargeItem.account",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.account` is mapped to FHIR R4 element `ChargeItem.account` as `Equivalent`.\nSystems posting the ChargeItems may 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": "ChargeItem.note",
"display": "note",
"target": [
{
"code": "ChargeItem.note",
"display": "ChargeItem.note",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.note` is mapped to FHIR R4 element `ChargeItem.note` as `Equivalent`."
}
]
},
{
"code": "ChargeItem.supportingInformation",
"display": "supportingInformation",
"target": [
{
"code": "ChargeItem.supportingInformation",
"display": "ChargeItem.supportingInformation",
"equivalence": "equivalent",
"comment": "Element `ChargeItem.supportingInformation` is mapped to FHIR R4 element `ChargeItem.supportingInformation` as `Equivalent`."
}
]
}
]
}
]
}