Generated Narrative: ConceptMap R5-Account-element-map-to-R4B Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.3 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 to Accountversion: 4.3.0) Source Code Relationship Target Code Comment Account.meta (meta) is equivalent to Account.meta Element `Account.meta` is mapped to FHIR R4B element `Account.meta` as `Equivalent`. Account.implicitRules (implicitRules) is equivalent to Account.implicitRules Element `Account.implicitRules` is mapped to FHIR R4B element `Account.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 its narrative along with other profiles, value sets, etc. Account.language (language) is equivalent to Account.language Element `Account.language` is mapped to FHIR R4B element `Account.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). Account.text (text) is equivalent to Account.text Element `Account.text` is mapped to FHIR R4B element `Account.text` as `Equivalent`. Contained resources do not have a 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. Account.contained (contained) is equivalent to Account.contained Element `Account.contained` is mapped to FHIR R4B element `Account.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. Account.identifier (identifier) is equivalent to Account.identifier Element `Account.identifier` is mapped to FHIR R4B element `Account.identifier` as `Equivalent`. Account.status (status) is equivalent to Account.status Element `Account.status` is mapped to FHIR R4B element `Account.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the Account as not currently valid. Account.type (type) is equivalent to Account.type Element `Account.type` is mapped to FHIR R4B element `Account.type` as `Equivalent`. Account.name (name) is equivalent to Account.name Element `Account.name` is mapped to FHIR R4B element `Account.name` as `Equivalent`. Account.subject (subject) is equivalent to Account.subject Element `Account.subject` is mapped to FHIR R4B element `Account.subject` as `Equivalent`. Accounts can be applied to non-patients for tracking other non-patient related activities, such as group services (patients not tracked, and costs charged to another body), or might not be allocated. Account.servicePeriod (servicePeriod) is equivalent to Account.servicePeriod Element `Account.servicePeriod` is mapped to FHIR R4B element `Account.servicePeriod` as `Equivalent`. It is possible for transactions to be posted outside the service period, as long as the service was provided within the defined service period. Account.coverage (coverage) maps to wider concept Account.coverage Element `Account.coverage` is mapped to FHIR R4B element `Account.coverage` as `Equivalent`. Typically. this may be some form of insurance, internal charges, or self-pay. Local or jurisdictional business rules may determine which coverage covers which types of billable items charged to the account, and in which order. Where the order is important, a local/jurisdictional extension may be defined to specify the order for the type of charge. Account.coverage.coverage (coverage) is equivalent to Account.coverage.coverage Element `Account.coverage.coverage` is mapped to FHIR R4B element `Account.coverage.coverage` as `Equivalent`. Account.coverage.priority (priority) is equivalent to Account.coverage.priority Element `Account.coverage.priority` is mapped to FHIR R4B element `Account.coverage.priority` as `Equivalent`. It is common in some jurisdictions for there to be multiple coverages allocated to an account, and a sequence is required to order the settling of the account (often with insurance claiming). Account.owner (owner) is equivalent to Account.owner Element `Account.owner` is mapped to FHIR R4B element `Account.owner` as `Equivalent`. Account.description (description) is equivalent to Account.description Element `Account.description` is mapped to FHIR R4B element `Account.description` as `Equivalent`. Account.guarantor (guarantor) maps to wider concept Account.guarantor Element `Account.guarantor` is mapped to FHIR R4B element `Account.guarantor` as `Equivalent`. Account.guarantor.party (party) is equivalent to Account.guarantor.party Element `Account.guarantor.party` is mapped to FHIR R4B element `Account.guarantor.party` as `Equivalent`. Account.guarantor.onHold (onHold) is equivalent to Account.guarantor.onHold Element `Account.guarantor.onHold` is mapped to FHIR R4B element `Account.guarantor.onHold` as `Equivalent`. Account.guarantor.period (period) is equivalent to Account.guarantor.period Element `Account.guarantor.period` is mapped to FHIR R4B element `Account.guarantor.period` as `Equivalent`. Account.relatedAccount.account (account) is equivalent to Account.partOf Element `Account.relatedAccount.account` is part of an existing definition because parent element `Account.relatedAccount` requires a cross-version extension. Element `Account.relatedAccount.account` is mapped to FHIR R4B element `Account.partOf` as `SourceIsBroaderThanTarget`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 to R5: Tracks the lifecycle of the account through the billing process (new)version: 0.1.0) Source Code Relationship Target Code Comment Account.billingStatus (billingStatus) maps to wider concept Extension (R5: Tracks the lifecycle of the account through the billing process (new)) Element `Account.billingStatus` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.billingStatus` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 to R5: The list of diagnoses relevant to this account (new)version: 0.1.0) Source Code Relationship Target Code Comment Account.diagnosis (diagnosis) maps to wider concept Extension (R5: The list of diagnoses relevant to this account (new)) Element `Account.diagnosis` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.diagnosis.sequence (sequence) maps to wider concept Extension.extension:sequence (R5: Ranking of the diagnosis (for each type) (new)) Element `Account.diagnosis.sequence` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.sequence` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.sequence` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.diagnosis.condition (condition) maps to wider concept Extension.extension:condition (R5: The diagnosis relevant to the account (new)) Element `Account.diagnosis.condition` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.condition` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.condition` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.diagnosis.dateOfDiagnosis (dateOfDiagnosis) maps to wider concept Extension.extension:dateOfDiagnosis (R5: Date of the diagnosis (when coded diagnosis) (new)) Element `Account.diagnosis.dateOfDiagnosis` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.dateOfDiagnosis` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.dateOfDiagnosis` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.diagnosis.type (type) maps to wider concept Extension.extension:type (R5: Type that this diagnosis has relevant to the account (e.g. admission, billing, discharge …) (new)) Element `Account.diagnosis.type` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.type` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.diagnosis.onAdmission (onAdmission) maps to wider concept Extension.extension:onAdmission (R5: Diagnosis present on Admission (new)) Element `Account.diagnosis.onAdmission` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.onAdmission` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.onAdmission` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.diagnosis.packageCode (packageCode) maps to wider concept Extension.extension:packageCode (R5: Package Code specific for billing (new)) Element `Account.diagnosis.packageCode` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.packageCode` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.packageCode` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 to R5: The list of procedures relevant to this account (new)version: 0.1.0) Source Code Relationship Target Code Comment Account.procedure (procedure) maps to wider concept Extension (R5: The list of procedures relevant to this account (new)) Element `Account.procedure` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.procedure.sequence (sequence) maps to wider concept Extension.extension:sequence (R5: Ranking of the procedure (for each type) (new)) Element `Account.procedure.sequence` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.sequence` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.sequence` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.procedure.code (code) maps to wider concept Extension.extension:code (R5: The procedure relevant to the account (new)) Element `Account.procedure.code` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.code` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.code` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.procedure.dateOfService (dateOfService) maps to wider concept Extension.extension:dateOfService (R5: Date of the procedure (when coded procedure) (new)) Element `Account.procedure.dateOfService` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.dateOfService` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.dateOfService` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.procedure.type (type) maps to wider concept Extension.extension:type (R5: How this procedure value should be used in charging the account (new)) Element `Account.procedure.type` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.type` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.procedure.packageCode (packageCode) maps to wider concept Extension.extension:packageCode (R5: Package Code specific for billing (new)) Element `Account.procedure.packageCode` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.packageCode` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.packageCode` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.procedure.device (device) maps to wider concept Extension.extension:device (R5: Any devices that were associated with the procedure (new)) Element `Account.procedure.device` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.device` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.device` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 to R5: Other associated accounts related to this account (new)version: 0.1.0) Source Code Relationship Target Code Comment Account.relatedAccount (relatedAccount) maps to wider concept Extension (R5: Other associated accounts related to this account (new)) Element `Account.relatedAccount` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.relatedAccount` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.relatedAccount.relationship (relationship) maps to wider concept Extension.extension:relationship (R5: Relationship of the associated Account (new)) Element `Account.relatedAccount.relationship` is part of an existing definition because parent element `Account.relatedAccount` requires a cross-version extension. Element `Account.relatedAccount.relationship` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.relatedAccount.relationship` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.relatedAccount.account (account) maps to wider concept Extension.extension:account (R5: Reference to an associated Account) Element `Account.relatedAccount.account` is part of an existing definition because parent element `Account.relatedAccount` requires a cross-version extension. Element `Account.relatedAccount.account` is mapped to FHIR R4B element `Account.partOf` as `SourceIsBroaderThanTarget`. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 to R5: The base or default currency (new)version: 0.1.0) Source Code Relationship Target Code Comment Account.currency (currency) maps to wider concept Extension (R5: The base or default currency (new)) Element `Account.currency` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.currency` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 to R5: Calculated account balance(s) (new)version: 0.1.0) Source Code Relationship Target Code Comment Account.balance (balance) maps to wider concept Extension (R5: Calculated account balance(s) (new)) Element `Account.balance` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.balance.aggregate (aggregate) maps to wider concept Extension.extension:aggregate (R5: Who is expected to pay this part of the balance (new)) Element `Account.balance.aggregate` is part of an existing definition because parent element `Account.balance` requires a cross-version extension. Element `Account.balance.aggregate` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance.aggregate` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.balance.term (term) maps to wider concept Extension.extension:term (R5: current | 30 | 60 | 90 | 120 (new)) Element `Account.balance.term` is part of an existing definition because parent element `Account.balance` requires a cross-version extension. Element `Account.balance.term` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance.term` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.balance.estimate (estimate) maps to wider concept Extension.extension:estimate (R5: Estimated balance (new)) Element `Account.balance.estimate` is part of an existing definition because parent element `Account.balance` requires a cross-version extension. Element `Account.balance.estimate` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance.estimate` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Account.balance.amount (amount) maps to wider concept Extension.extension:amount (R5: Calculated amount (new)) Element `Account.balance.amount` is part of an existing definition because parent element `Account.balance` requires a cross-version extension. Element `Account.balance.amount` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance.amount` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Account|5.0.0 to R5: Time the balance amount was calculated (new)version: 0.1.0) Source Code Relationship Target Code Comment Account.calculatedAt (calculatedAt) maps to wider concept Extension (R5: Time the balance amount was calculated (new)) Element `Account.calculatedAt` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.calculatedAt` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). The total(s) are not typically updated using the restful API but more often by back-end processes included in a typical finance system.
Cross-version mapping for FHIR R5 Account to FHIR R4B Account
This ConceptMap represents cross-version mappings for elements from a FHIR R5 Account to FHIR R4B.
Element `Account.meta` is mapped to FHIR R4B element `Account.meta` as `Equivalent`.
Element `Account.implicitRules` is mapped to FHIR R4B element `Account.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 its narrative along with other profiles, value sets, etc.
Element `Account.language` is mapped to FHIR R4B element `Account.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).
Element `Account.text` is mapped to FHIR R4B element `Account.text` as `Equivalent`. Contained resources do not have a 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 `Account.contained` is mapped to FHIR R4B element `Account.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.
Element `Account.identifier` is mapped to FHIR R4B element `Account.identifier` as `Equivalent`.
Element `Account.status` is mapped to FHIR R4B element `Account.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the Account as not currently valid.
Element `Account.type` is mapped to FHIR R4B element `Account.type` as `Equivalent`.
Element `Account.name` is mapped to FHIR R4B element `Account.name` as `Equivalent`.
Element `Account.subject` is mapped to FHIR R4B element `Account.subject` as `Equivalent`. Accounts can be applied to non-patients for tracking other non-patient related activities, such as group services (patients not tracked, and costs charged to another body), or might not be allocated.
Element `Account.servicePeriod` is mapped to FHIR R4B element `Account.servicePeriod` as `Equivalent`. It is possible for transactions to be posted outside the service period, as long as the service was provided within the defined service period.
Element `Account.coverage` is mapped to FHIR R4B element `Account.coverage` as `Equivalent`. Typically. this may be some form of insurance, internal charges, or self-pay. Local or jurisdictional business rules may determine which coverage covers which types of billable items charged to the account, and in which order. Where the order is important, a local/jurisdictional extension may be defined to specify the order for the type of charge.
Element `Account.coverage.coverage` is mapped to FHIR R4B element `Account.coverage.coverage` as `Equivalent`.
Element `Account.coverage.priority` is mapped to FHIR R4B element `Account.coverage.priority` as `Equivalent`. It is common in some jurisdictions for there to be multiple coverages allocated to an account, and a sequence is required to order the settling of the account (often with insurance claiming).
Element `Account.owner` is mapped to FHIR R4B element `Account.owner` as `Equivalent`.
Element `Account.description` is mapped to FHIR R4B element `Account.description` as `Equivalent`.
Element `Account.guarantor` is mapped to FHIR R4B element `Account.guarantor` as `Equivalent`.
Element `Account.guarantor.party` is mapped to FHIR R4B element `Account.guarantor.party` as `Equivalent`.
Element `Account.guarantor.onHold` is mapped to FHIR R4B element `Account.guarantor.onHold` as `Equivalent`.
Element `Account.guarantor.period` is mapped to FHIR R4B element `Account.guarantor.period` as `Equivalent`.
Element `Account.relatedAccount.account` is part of an existing definition because parent element `Account.relatedAccount` requires a cross-version extension. Element `Account.relatedAccount.account` is mapped to FHIR R4B element `Account.partOf` as `SourceIsBroaderThanTarget`.
Element `Account.billingStatus` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.billingStatus` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.diagnosis` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.diagnosis.sequence` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.sequence` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.sequence` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.diagnosis.condition` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.condition` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.condition` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.diagnosis.dateOfDiagnosis` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.dateOfDiagnosis` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.dateOfDiagnosis` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.diagnosis.type` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.type` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.diagnosis.onAdmission` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.onAdmission` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.onAdmission` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.diagnosis.packageCode` is part of an existing definition because parent element `Account.diagnosis` requires a cross-version extension. Element `Account.diagnosis.packageCode` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.diagnosis.packageCode` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.procedure` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.procedure.sequence` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.sequence` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.sequence` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.procedure.code` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.code` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.code` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.procedure.dateOfService` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.dateOfService` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.dateOfService` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.procedure.type` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.type` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.procedure.packageCode` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.packageCode` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.packageCode` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.procedure.device` is part of an existing definition because parent element `Account.procedure` requires a cross-version extension. Element `Account.procedure.device` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.procedure.device` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.relatedAccount` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.relatedAccount` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.relatedAccount.relationship` is part of an existing definition because parent element `Account.relatedAccount` requires a cross-version extension. Element `Account.relatedAccount.relationship` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.relatedAccount.relationship` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.currency` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.currency` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.balance` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.balance.aggregate` is part of an existing definition because parent element `Account.balance` requires a cross-version extension. Element `Account.balance.aggregate` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance.aggregate` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.balance.term` is part of an existing definition because parent element `Account.balance` requires a cross-version extension. Element `Account.balance.term` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance.term` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.balance.estimate` is part of an existing definition because parent element `Account.balance` requires a cross-version extension. Element `Account.balance.estimate` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance.estimate` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.balance.amount` is part of an existing definition because parent element `Account.balance` requires a cross-version extension. Element `Account.balance.amount` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.balance.amount` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `Account.calculatedAt` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.calculatedAt` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). The total(s) are not typically updated using the restful API but more often by back-end processes included in a typical finance system.