R3PatientElementMapToR5 - Extensions for Using Data Elements from FHIR STU3 in FHIR R5 v0.1.0

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

ConceptMap: R3PatientElementMapToR5

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

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 Patient to FHIR R5.

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

Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Patient|3.0.2 to Patientversion: 5.0.0)

Source Code

Relationship

Target Code

Comment

Patient.meta (meta)

is broader than

Patient.meta

Element `Patient.meta` is mapped to FHIR R5 element `Patient.meta` as `SourceIsBroaderThanTarget`. The mappings for `Patient.meta` do not cover the following types: Meta. The mappings for `Patient.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Patient.implicitRules (implicitRules)

is equivalent to

Patient.implicitRules

Element `Patient.implicitRules` is mapped to FHIR R5 element `Patient.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.

Patient.language (language)

is equivalent to

Patient.language

Element `Patient.language` is mapped to FHIR R5 element `Patient.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).

Patient.text (text)

is broader than

Patient.text

Element `Patient.text` is mapped to FHIR R5 element `Patient.text` as `SourceIsBroaderThanTarget`. The mappings for `Patient.text` do not cover the following types: Narrative. The mappings for `Patient.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.

Patient.contained (contained)

is equivalent to

Patient.contained

Element `Patient.contained` is mapped to FHIR R5 element `Patient.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.

Patient.identifier (identifier)

is broader than

Patient.identifier

Element `Patient.identifier` is mapped to FHIR R5 element `Patient.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Patient.identifier` do not cover the following types: Identifier. The mappings for `Patient.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.

Patient.active (active)

is equivalent to

Patient.active

Element `Patient.active` is mapped to FHIR R5 element `Patient.active` as `Equivalent`. Default is true. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient This element is labeled as a modifier because when the patient record is marked as not active it is not expected to be used/referenced without being changed back to active.

Patient.name (name)

is broader than

Patient.name

Element `Patient.name` is mapped to FHIR R5 element `Patient.name` as `SourceIsBroaderThanTarget`. The mappings for `Patient.name` do not cover the following types: HumanName. The mappings for `Patient.name` do not cover the following types based on type expansion: family, given, period, prefix, suffix, text, use. A patient may have multiple names with different uses or applicable periods. For animals, the name is a "HumanName" in the sense that is assigned and used by humans and has the same patterns.

Patient.telecom (telecom)

is broader than

Patient.telecom

Element `Patient.telecom` is mapped to FHIR R5 element `Patient.telecom` as `SourceIsBroaderThanTarget`. The mappings for `Patient.telecom` do not cover the following types: ContactPoint. The mappings for `Patient.telecom` do not cover the following types based on type expansion: period, rank, system, use, value. A Patient 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. The address may not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).

Patient.gender (gender)

is equivalent to

Patient.gender

Element `Patient.gender` is mapped to FHIR R5 element `Patient.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. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific gender aspect of interest (anatomical, chromosonal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosonal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overrideable error, not a "hard" error.

Patient.birthDate (birthDate)

is equivalent to

Patient.birthDate

Element `Patient.birthDate` is mapped to FHIR R5 element `Patient.birthDate` as `Equivalent`. At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternaty/infant care systems).

Patient.deceased[x] (deceased[x])

is equivalent to

Patient.deceased[x]

Element `Patient.deceased[x]` is mapped to FHIR R5 element `Patient.deceased[x]` as `Equivalent`. The target context `Patient.deceased[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Patient`. 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. This element is labeled as a modifier because once a patient is marked as deceased, the actions that are appropriate to perform on the patient may be significantly different.

Patient.address (address)

is broader than

Patient.address

Element `Patient.address` is mapped to FHIR R5 element `Patient.address` as `SourceIsBroaderThanTarget`. The mappings for `Patient.address` do not cover the following types: Address. The mappings for `Patient.address` do not cover the following types based on type expansion: city, country, district, line, period, postalCode, state, text, type, use. Patient may have multiple addresses with different uses or applicable periods.

Patient.maritalStatus (maritalStatus)

is equivalent to

Patient.maritalStatus

Element `Patient.maritalStatus` is mapped to FHIR R5 element `Patient.maritalStatus` as `Equivalent`.

Patient.multipleBirth[x] (multipleBirth[x])

is equivalent to

Patient.multipleBirth[x]

Element `Patient.multipleBirth[x]` is mapped to FHIR R5 element `Patient.multipleBirth[x]` as `Equivalent`. The target context `Patient.multipleBirth[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Patient`. Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in tripplets would be valueInteger=2 and the third born would have valueInteger=3 If a bool value was provided for this tripplets examle, then all 3 patient records would have valueBool=true (the ordering is not indicated).

Patient.photo (photo)

is broader than

Patient.photo

Element `Patient.photo` is mapped to FHIR R5 element `Patient.photo` as `SourceIsBroaderThanTarget`. The mappings for `Patient.photo` do not cover the following types: Attachment. The mappings for `Patient.photo` do not cover the following types based on type expansion: contentType, creation, data, hash, language, size, title, url.

Patient.contact (contact)

is broader than

Patient.contact

Element `Patient.contact` is mapped to FHIR R5 element `Patient.contact` as `Equivalent`. Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.

Patient.contact.relationship (relationship)

is equivalent to

Patient.contact.relationship

Element `Patient.contact.relationship` is mapped to FHIR R5 element `Patient.contact.relationship` as `Equivalent`.

Patient.contact.name (name)

is broader than

Patient.contact.name

Element `Patient.contact.name` is mapped to FHIR R5 element `Patient.contact.name` as `SourceIsBroaderThanTarget`. The mappings for `Patient.contact.name` do not cover the following types: HumanName. The mappings for `Patient.contact.name` do not cover the following types based on type expansion: family, given, period, prefix, suffix, text, use.

Patient.contact.telecom (telecom)

is broader than

Patient.contact.telecom

Element `Patient.contact.telecom` is mapped to FHIR R5 element `Patient.contact.telecom` as `SourceIsBroaderThanTarget`. The mappings for `Patient.contact.telecom` do not cover the following types: ContactPoint. The mappings for `Patient.contact.telecom` do not cover the following types based on type expansion: period, rank, system, use, value. Contact 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.

Patient.contact.address (address)

is broader than

Patient.contact.address

Element `Patient.contact.address` is mapped to FHIR R5 element `Patient.contact.address` as `SourceIsBroaderThanTarget`. The mappings for `Patient.contact.address` do not cover the following types: Address. The mappings for `Patient.contact.address` do not cover the following types based on type expansion: city, country, district, line, period, postalCode, state, text, type, use.

Patient.contact.gender (gender)

is equivalent to

Patient.contact.gender

Element `Patient.contact.gender` is mapped to FHIR R5 element `Patient.contact.gender` as `Equivalent`.

Patient.contact.organization (organization)

is broader than

Patient.contact.organization

Element `Patient.contact.organization` is mapped to FHIR R5 element `Patient.contact.organization` as `SourceIsBroaderThanTarget`. The mappings for `Patient.contact.organization` 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 `Patient.contact.organization` with unmapped reference targets: Organization.

Patient.contact.period (period)

is broader than

Patient.contact.period

Element `Patient.contact.period` is mapped to FHIR R5 element `Patient.contact.period` as `SourceIsBroaderThanTarget`. The mappings for `Patient.contact.period` do not cover the following types: Period. The mappings for `Patient.contact.period` do not cover the following types based on type expansion: end, start.

Patient.communication (communication)

is broader than

Patient.communication

Element `Patient.communication` is mapped to FHIR R5 element `Patient.communication` as `Equivalent`. 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 Patient.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.

Patient.communication.language (language)

is equivalent to

Patient.communication.language

Element `Patient.communication.language` is mapped to FHIR R5 element `Patient.communication.language` as `Equivalent`. 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.

Patient.communication.preferred (preferred)

is equivalent to

Patient.communication.preferred

Element `Patient.communication.preferred` is mapped to FHIR R5 element `Patient.communication.preferred` as `Equivalent`. This language is specifically identified for communicating healthcare information.

Patient.generalPractitioner (generalPractitioner)

is broader than

Patient.generalPractitioner

Element `Patient.generalPractitioner` is mapped to FHIR R5 element `Patient.generalPractitioner` as `SourceIsBroaderThanTarget`. The mappings for `Patient.generalPractitioner` 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 `Patient.generalPractitioner` with unmapped reference targets: Organization, Practitioner. This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disablity setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources.

Patient.managingOrganization (managingOrganization)

is broader than

Patient.managingOrganization

Element `Patient.managingOrganization` is mapped to FHIR R5 element `Patient.managingOrganization` as `SourceIsBroaderThanTarget`. The mappings for `Patient.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 `Patient.managingOrganization` with unmapped reference targets: Organization. There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).

Patient.link (link)

is broader than

Patient.link

Element `Patient.link` is mapped to FHIR R5 element `Patient.link` as `Equivalent`. There is no assumption that linked patient records have mutual links. This element is labelled as a modifier because it may not be the main Patient resource, and the referenced patient should be used instead of this Patient record. This is when the link.type value is 'replaced-by'.

Patient.link.other (other)

is broader than

Patient.link.other

Element `Patient.link.other` is mapped to FHIR R5 element `Patient.link.other` as `SourceIsBroaderThanTarget`. The mappings for `Patient.link.other` 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 `Patient.link.other` with unmapped reference targets: Patient, RelatedPerson. Referencing a RelatedPerson here removes the need to use a Person record to associate a Patient and RelatedPerson as the same individual.

Patient.link.type (type)

is equivalent to

Patient.link.type

Element `Patient.link.type` is mapped to FHIR R5 element `Patient.link.type` as `Equivalent`.

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

Source Code

Relationship

Target Code

Comment

Patient.meta (meta)

is equivalent to

Extension (STU3: meta additional types)

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

Source Code

Relationship

Target Code

Comment

Patient.text (text)

is equivalent to

Extension (STU3: text additional types)

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

Source Code

Relationship

Target Code

Comment

Patient.identifier (identifier)

is equivalent to

Extension (STU3: identifier additional types)

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

Source Code

Relationship

Target Code

Comment

Patient.name (name)

is equivalent to

Extension (STU3: name additional types)

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

Source Code

Relationship

Target Code

Comment

Patient.telecom (telecom)

is equivalent to

Extension (STU3: telecom additional types)

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Patient|3.0.2 to STU3: Addresses for the individual additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

Patient.address (address)

is equivalent to

Extension (STU3: Addresses for the individual additional types)

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

Source Code

Relationship

Target Code

Comment

Patient.photo (photo)

is equivalent to

Extension (STU3: photo additional types)

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Patient|3.0.2 to STU3: name additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

Patient.contact.name (name)

is equivalent to

Extension (STU3: name additional types)

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

Source Code

Relationship

Target Code

Comment

Patient.contact.telecom (telecom)

is equivalent to

Extension (STU3: telecom additional types)

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

Source Code

Relationship

Target Code

Comment

Patient.contact.address (address)

is equivalent to

Extension (STU3: address additional types)

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

Source Code

Relationship

Target Code

Comment

Patient.contact.period (period)

is equivalent to

Extension (STU3: period additional types)

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/Patient|3.0.2 to STU3: This patient is known to be an animal (non-human) (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Patient.animal (animal)

is equivalent to

Extension (STU3: This patient is known to be an animal (non-human) (new))

Element `Patient.animal` has a context of Patient based on following the parent source element upwards and mapping to `Patient`. Element `Patient.animal` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The animal element is labeled "Is Modifier" since patients may be non-human. Systems SHALL either handle patient details appropriately (e.g. inform users patient is not human) or reject declared animal records. The absense of the animal element does not imply that the patient is a human. If a system requires such a positive assertion that the patient is human, an extension will be required. (Do not use a species of homo-sapiens in animal species, as this would incorrectly infer that the patient is an animal).

Patient.animal.species (species)

is equivalent to

Extension.extension:species (STU3: E.g. Dog, Cow (new))

Element `Patient.animal.species` is part of an existing definition because parent element `Patient.animal` requires a cross-version extension. Element `Patient.animal.species` has a context of Patient based on following the parent source element upwards and mapping to `Patient`. Element `Patient.animal.species` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If the patient is non-human, at least a species SHALL be specified. Species SHALL be a widely recognised taxonomic classification. It may or may not be Linnaean taxonomy and may or may not be at the level of species. If the level is finer than species--such as a breed code--the code system used SHALL allow inference of the species. (The common example is that the word "Hereford" does not allow inference of the species Bos taurus, because there is a Hereford pig breed, but the SNOMED CT code for "Hereford Cattle Breed" does.).

Patient.animal.breed (breed)

is equivalent to

Extension.extension:breed (STU3: E.g. Poodle, Angus (new))

Element `Patient.animal.breed` is part of an existing definition because parent element `Patient.animal` requires a cross-version extension. Element `Patient.animal.breed` has a context of Patient based on following the parent source element upwards and mapping to `Patient`. Element `Patient.animal.breed` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Breed MAY be used to provide further taxonomic or non-taxonomic classification. It may involve local or proprietary designation--such as commercial strain--and/or additional information such as production type.

Patient.animal.genderStatus (genderStatus)

is equivalent to

Extension.extension:genderStatus (STU3: E.g. Neutered, Intact (new))

Element `Patient.animal.genderStatus` is part of an existing definition because parent element `Patient.animal` requires a cross-version extension. Element `Patient.animal.genderStatus` has a context of Patient based on following the parent source element upwards and mapping to `Patient`. Element `Patient.animal.genderStatus` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).