Extensions for Using Data Elements from FHIR STU3 in FHIR R4B
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R4B - Downloaded Version null See the Directory of published versions

ConceptMap: R3AccountElementMapToR4B

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-Account-element-map-to-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R3AccountElementMapToR4B

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 Account to FHIR R4B.

Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Account|3.0.2 to Accountversion: 4.3.0)

Source CodeRelationshipTarget CodeComment
Account.meta (meta)maps to wider conceptAccount.metaElement `Account.meta` is mapped to FHIR R4B element `Account.meta` as `SourceIsBroaderThanTarget`. The mappings for `Account.meta` do not cover the following types: Meta. The mappings for `Account.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Account.implicitRules (implicitRules)is equivalent toAccount.implicitRulesElement `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. 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.
Account.language (language)is equivalent toAccount.languageElement `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)maps to wider conceptAccount.textElement `Account.text` is mapped to FHIR R4B element `Account.text` as `SourceIsBroaderThanTarget`. The mappings for `Account.text` do not cover the following types: Narrative. The mappings for `Account.text` do not cover the following types based on type expansion: div, status. 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.
Account.contained (contained)is equivalent toAccount.containedElement `Account.contained` is mapped to FHIR R4B element `Account.contained` as `SourceIsBroaderThanTarget`. 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.
Account.identifier (identifier)maps to wider conceptAccount.identifierElement `Account.identifier` is mapped to FHIR R4B element `Account.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Account.identifier` do not cover the following types: Identifier. The mappings for `Account.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Account.status (status)is equivalent toAccount.statusElement `Account.status` is mapped to FHIR R4B element `Account.status` as `SourceIsNarrowerThanTarget`. The mappings for `Account.status` do not allow expression of the necessary codes, per the bindings on the source and target. 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 toAccount.typeElement `Account.type` is mapped to FHIR R4B element `Account.type` as `Equivalent`.
Account.name (name)is equivalent toAccount.nameElement `Account.name` is mapped to FHIR R4B element `Account.name` as `Equivalent`.
Account.subject (subject)maps to wider conceptAccount.subjectElement `Account.subject` is mapped to FHIR R4B element `Account.subject` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Account.subject` with unmapped reference targets: Device, HealthcareService, Location, Organization, Patient, Practitioner. 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 may not be allocated.
Account.period (period)maps to wider conceptAccount.servicePeriodElement `Account.period` is mapped to FHIR R4B element `Account.servicePeriod` as `SourceIsBroaderThanTarget`. The mappings for `Account.period` do not cover the following types: Period. The mappings for `Account.period` do not cover the following types based on type expansion: end, start. It is possible for transactions relevant to a coverage period to be posted to the account before or after the coverage period, however the services that are being charged for must be within this period.
Account.coverage (coverage)maps to wider conceptAccount.coverageElement `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 jurisdicational 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/jurisdicational extension may be defined to specify the order for the type of charge.
Account.coverage.coverage (coverage)maps to wider conceptAccount.coverage.coverageElement `Account.coverage.coverage` is mapped to FHIR R4B element `Account.coverage.coverage` as `SourceIsBroaderThanTarget`. The mappings for `Account.coverage.coverage` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Account.coverage.coverage` with unmapped reference targets: Coverage.
Account.coverage.priority (priority)is equivalent toAccount.coverage.priorityElement `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)maps to wider conceptAccount.ownerElement `Account.owner` is mapped to FHIR R4B element `Account.owner` as `SourceIsBroaderThanTarget`. The mappings for `Account.owner` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Account.owner` with unmapped reference targets: Organization.
Account.description (description)is equivalent toAccount.descriptionElement `Account.description` is mapped to FHIR R4B element `Account.description` as `Equivalent`.
Account.guarantor (guarantor)maps to wider conceptAccount.guarantorElement `Account.guarantor` is mapped to FHIR R4B element `Account.guarantor` as `Equivalent`.
Account.guarantor.party (party)maps to wider conceptAccount.guarantor.partyElement `Account.guarantor.party` is mapped to FHIR R4B element `Account.guarantor.party` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Account.guarantor.party` with unmapped reference targets: Organization, Patient, RelatedPerson.
Account.guarantor.onHold (onHold)is equivalent toAccount.guarantor.onHoldElement `Account.guarantor.onHold` is mapped to FHIR R4B element `Account.guarantor.onHold` as `Equivalent`.
Account.guarantor.period (period)maps to wider conceptAccount.guarantor.periodElement `Account.guarantor.period` is mapped to FHIR R4B element `Account.guarantor.period` as `SourceIsBroaderThanTarget`. The mappings for `Account.guarantor.period` do not cover the following types: Period. The mappings for `Account.guarantor.period` do not cover the following types based on type expansion: end, start.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Account|3.0.2 to STU3: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Account.meta (meta)is equivalent toExtension (STU3: meta additional types)Element `Account.meta` is mapped to FHIR R4B element `Account.meta` as `SourceIsBroaderThanTarget`. The mappings for `Account.meta` do not cover the following types: Meta. The mappings for `Account.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Account|3.0.2 to STU3: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Account.text (text)is equivalent toExtension (STU3: text additional types)Element `Account.text` is mapped to FHIR R4B element `Account.text` as `SourceIsBroaderThanTarget`. The mappings for `Account.text` do not cover the following types: Narrative. The mappings for `Account.text` do not cover the following types based on type expansion: div, status. 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.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Account|3.0.2 to STU3: identifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Account.identifier (identifier)is equivalent toExtension (STU3: identifier additional types)Element `Account.identifier` is mapped to FHIR R4B element `Account.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Account.identifier` do not cover the following types: Identifier. The mappings for `Account.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Account|3.0.2 to STU3: period additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Account.period (period)maps to wider conceptExtension (STU3: period additional types)Element `Account.period` is mapped to FHIR R4B element `Account.servicePeriod` as `SourceIsBroaderThanTarget`. The mappings for `Account.period` do not cover the following types: Period. The mappings for `Account.period` do not cover the following types based on type expansion: end, start. It is possible for transactions relevant to a coverage period to be posted to the account before or after the coverage period, however the services that are being charged for must be within this period.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Account|3.0.2 to STU3: Time window that transactions may be posted to this account (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Account.active (active)is equivalent toExtension (STU3: Time window that transactions may be posted to this account (new))Element `Account.active` has a context of Account based on following the parent source element upwards and mapping to `Account`. Element `Account.active` 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|3.0.2 to STU3: How much is in account? (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Account.balance (balance)is equivalent toExtension (STU3: How much is in account? (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).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Account|3.0.2 to STU3: Guarrantee account during additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Account.guarantor.period (period)is equivalent toExtension (STU3: Guarrantee account during additional types)Element `Account.guarantor.period` is mapped to FHIR R4B element `Account.guarantor.period` as `SourceIsBroaderThanTarget`. The mappings for `Account.guarantor.period` do not cover the following types: Period. The mappings for `Account.guarantor.period` do not cover the following types based on type expansion: end, start.