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: R3PersonElementMapToR4B

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

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 Person 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/Person|3.0.2 to Personversion: 4.3.0)

Source CodeRelationshipTarget CodeComment
Person.meta (meta)maps to wider conceptPerson.metaElement `Person.meta` is mapped to FHIR R4B element `Person.meta` as `SourceIsBroaderThanTarget`. The mappings for `Person.meta` do not cover the following types: Meta. The mappings for `Person.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Person.implicitRules (implicitRules)is equivalent toPerson.implicitRulesElement `Person.implicitRules` is mapped to FHIR R4B element `Person.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.
Person.language (language)is equivalent toPerson.languageElement `Person.language` is mapped to FHIR R4B element `Person.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).
Person.text (text)maps to wider conceptPerson.textElement `Person.text` is mapped to FHIR R4B element `Person.text` as `SourceIsBroaderThanTarget`. The mappings for `Person.text` do not cover the following types: Narrative. The mappings for `Person.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.
Person.contained (contained)is equivalent toPerson.containedElement `Person.contained` is mapped to FHIR R4B element `Person.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.
Person.identifier (identifier)maps to wider conceptPerson.identifierElement `Person.identifier` is mapped to FHIR R4B element `Person.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Person.identifier` do not cover the following types: Identifier. The mappings for `Person.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Person.name (name)maps to wider conceptPerson.nameElement `Person.name` is mapped to FHIR R4B element `Person.name` as `SourceIsBroaderThanTarget`. The mappings for `Person.name` do not cover the following types: HumanName. The mappings for `Person.name` do not cover the following types based on type expansion: family, given, period, prefix, suffix, text, use. Person may have multiple names with different uses or applicable periods.
Person.telecom (telecom)maps to wider conceptPerson.telecomElement `Person.telecom` is mapped to FHIR R4B element `Person.telecom` as `SourceIsBroaderThanTarget`. The mappings for `Person.telecom` do not cover the following types: ContactPoint. The mappings for `Person.telecom` do not cover the following types based on type expansion: period, rank, system, use, value. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.
Person.gender (gender)is equivalent toPerson.genderElement `Person.gender` is mapped to FHIR R4B element `Person.gender` as `Equivalent`. The gender may not match the biological sex as determined by genetics, or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than M and F, though the vast majority of systems and contexts only support M and F.
Person.birthDate (birthDate)is equivalent toPerson.birthDateElement `Person.birthDate` is mapped to FHIR R4B element `Person.birthDate` as `Equivalent`. At least an estimated year should be provided as a guess if the real DOB is unknown.
Person.address (address)maps to wider conceptPerson.addressElement `Person.address` is mapped to FHIR R4B element `Person.address` as `SourceIsBroaderThanTarget`. The mappings for `Person.address` do not cover the following types: Address. The mappings for `Person.address` do not cover the following types based on type expansion: city, country, district, line, period, postalCode, state, text, type, use. Person may have multiple addresses with different uses or applicable periods.
Person.photo (photo)maps to wider conceptPerson.photoElement `Person.photo` is mapped to FHIR R4B element `Person.photo` as `SourceIsBroaderThanTarget`. The mappings for `Person.photo` do not cover the following types: Attachment. The mappings for `Person.photo` do not cover the following types based on type expansion: contentType, creation, data, hash, language, size, title, url.
Person.managingOrganization (managingOrganization)maps to wider conceptPerson.managingOrganizationElement `Person.managingOrganization` is mapped to FHIR R4B element `Person.managingOrganization` as `SourceIsBroaderThanTarget`. The mappings for `Person.managingOrganization` 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 `Person.managingOrganization` with unmapped reference targets: Organization.
Person.active (active)is equivalent toPerson.activeElement `Person.active` is mapped to FHIR R4B element `Person.active` as `Equivalent`.
Person.link (link)maps to wider conceptPerson.linkElement `Person.link` is mapped to FHIR R4B element `Person.link` as `Equivalent`.
Person.link.target (target)maps to wider conceptPerson.link.targetElement `Person.link.target` is mapped to FHIR R4B element `Person.link.target` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Person.link.target` with unmapped reference targets: Patient, Person, Practitioner, RelatedPerson.
Person.link.assurance (assurance)is equivalent toPerson.link.assuranceElement `Person.link.assurance` is mapped to FHIR R4B element `Person.link.assurance` as `Equivalent`.

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

Source CodeRelationshipTarget CodeComment
Person.meta (meta)is equivalent toExtension (STU3: meta additional types)Element `Person.meta` is mapped to FHIR R4B element `Person.meta` as `SourceIsBroaderThanTarget`. The mappings for `Person.meta` do not cover the following types: Meta. The mappings for `Person.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/Person|3.0.2 to STU3: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.text (text)is equivalent toExtension (STU3: text additional types)Element `Person.text` is mapped to FHIR R4B element `Person.text` as `SourceIsBroaderThanTarget`. The mappings for `Person.text` do not cover the following types: Narrative. The mappings for `Person.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/Person|3.0.2 to STU3: identifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.identifier (identifier)is equivalent toExtension (STU3: identifier additional types)Element `Person.identifier` is mapped to FHIR R4B element `Person.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Person.identifier` do not cover the following types: Identifier. The mappings for `Person.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/Person|3.0.2 to STU3: name additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.name (name)is equivalent toExtension (STU3: name additional types)Element `Person.name` is mapped to FHIR R4B element `Person.name` as `SourceIsBroaderThanTarget`. The mappings for `Person.name` do not cover the following types: HumanName. The mappings for `Person.name` do not cover the following types based on type expansion: family, given, period, prefix, suffix, text, use. Person may have multiple names with different uses or applicable periods.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Person|3.0.2 to STU3: telecom additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.telecom (telecom)is equivalent toExtension (STU3: telecom additional types)Element `Person.telecom` is mapped to FHIR R4B element `Person.telecom` as `SourceIsBroaderThanTarget`. The mappings for `Person.telecom` do not cover the following types: ContactPoint. The mappings for `Person.telecom` do not cover the following types based on type expansion: period, rank, system, use, value. Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Person|3.0.2 to STU3: address additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.address (address)is equivalent toExtension (STU3: address additional types)Element `Person.address` is mapped to FHIR R4B element `Person.address` as `SourceIsBroaderThanTarget`. The mappings for `Person.address` do not cover the following types: Address. The mappings for `Person.address` do not cover the following types based on type expansion: city, country, district, line, period, postalCode, state, text, type, use. Person may have multiple addresses with different uses or applicable periods.

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Person|3.0.2 to STU3: photo additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.photo (photo)is equivalent toExtension (STU3: photo additional types)Element `Person.photo` is mapped to FHIR R4B element `Person.photo` as `SourceIsBroaderThanTarget`. The mappings for `Person.photo` do not cover the following types: Attachment. The mappings for `Person.photo` do not cover the following types based on type expansion: contentType, creation, data, hash, language, size, title, url.