Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU International flag

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

ConceptMap: R5PersonElementMapToR4

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 Person to FHIR R4.

Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Person|5.0.0 to Personversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
Person.meta (meta)​is equivalent toPerson.metaElement `Person.meta` is mapped to FHIR R4 element `Person.meta` as `Equivalent`.
Person.implicitRules (implicitRules)​is equivalent toPerson.implicitRulesElement `Person.implicitRules` is mapped to FHIR R4 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. 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.
Person.language (language)​is equivalent toPerson.languageElement `Person.language` is mapped to FHIR R4 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)​is equivalent toPerson.textElement `Person.text` is mapped to FHIR R4 element `Person.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.
Person.contained (contained)​is equivalent toPerson.containedElement `Person.contained` is mapped to FHIR R4 element `Person.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.
Person.identifier (identifier)​is equivalent toPerson.identifierElement `Person.identifier` is mapped to FHIR R4 element `Person.identifier` as `Equivalent`.
Person.active (active)​is equivalent toPerson.activeElement `Person.active` is mapped to FHIR R4 element `Person.active` as `Equivalent`.
Person.name (name)​is equivalent toPerson.nameElement `Person.name` is mapped to FHIR R4 element `Person.name` as `Equivalent`. Person may have multiple names with different uses or applicable periods.
Person.telecom (telecom)​is equivalent toPerson.telecomElement `Person.telecom` is mapped to FHIR R4 element `Person.telecom` as `Equivalent`. 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 R4 element `Person.gender` as `Equivalent`. The gender might 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 a clear majority of systems and contexts only support M and F.
Person.birthDate (birthDate)​is equivalent toPerson.birthDateElement `Person.birthDate` is mapped to FHIR R4 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)​is equivalent toPerson.addressElement `Person.address` is mapped to FHIR R4 element `Person.address` as `Equivalent`. Person may have multiple addresses with different uses or applicable periods.
Person.photo (photo)​is equivalent toPerson.photoElement `Person.photo` is mapped to FHIR R4 element `Person.photo` as `SourceIsBroaderThanTarget`.
Person.managingOrganization (managingOrganization)​is equivalent toPerson.managingOrganizationElement `Person.managingOrganization` is mapped to FHIR R4 element `Person.managingOrganization` as `Equivalent`.
Person.link (link)​maps to wider conceptPerson.linkElement `Person.link` is mapped to FHIR R4 element `Person.link` as `Equivalent`.
Person.link.target (target)​is equivalent toPerson.link.targetElement `Person.link.target` is mapped to FHIR R4 element `Person.link.target` as `Equivalent`.
Person.link.assurance (assurance)​is equivalent toPerson.link.assuranceElement `Person.link.assurance` is mapped to FHIR R4 element `Person.link.assurance` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Person|5.0.0 to R5: Indicates if the individual is deceased or not (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.deceased[x] (deceased[x])​maps to wider conceptExtension (R5: Indicates if the individual is deceased or not (new))Element `Person.deceased[x]` has a context of Person based on following the parent source element upwards and mapping to `Person`. Element `Person.deceased[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If there's no value in the instance, it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Person|5.0.0 to R5: Marital (civil) status of a person (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.maritalStatus (maritalStatus)​maps to wider conceptExtension (R5: Marital (civil) status of a person (new))Element `Person.maritalStatus` has a context of Person based on following the parent source element upwards and mapping to `Person`. Element `Person.maritalStatus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Many countries maintain a register of births, deaths and marriages, and this would simplify that interaction

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Person|5.0.0 to R5: A language which may be used to communicate with the person about his or her health (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Person.communication (communication)​maps to wider conceptExtension (R5: A language which may be used to communicate with the person about his or her health (new))Element `Person.communication` has a context of Person based on following the parent source element upwards and mapping to `Person`. Element `Person.communication` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Person.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required. Note that this property should not be used to update any linked/logically linked practitioner resources as it serves as a language that can be used to communicate with patients - however it may be used to inform the value on practitioner, along with their role at the organization (with the practitioner's permission)
Person.communication.language (language)​maps to wider conceptExtension.extension:language (R5: The language which can be used to communicate with the person about his or her health (new))Element `Person.communication.language` is part of an existing definition because parent element `Person.communication` requires a cross-version extension. Element `Person.communication.language` has a context of Person based on following the parent source element upwards and mapping to `Person`. Element `Person.communication.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.
Person.communication.preferred (preferred)​maps to wider conceptExtension.extension:preferred (R5: Language preference indicator (new))Element `Person.communication.preferred` is part of an existing definition because parent element `Person.communication` requires a cross-version extension. Element `Person.communication.preferred` has a context of Person based on following the parent source element upwards and mapping to `Person`. Element `Person.communication.preferred` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This language is specifically identified for communicating healthcare information.