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

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 PractitionerRole 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/PractitionerRole|5.0.0 to PractitionerRoleversion: 4.0.1)

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/PractitionerRole|5.0.0Codes from PractitionerRole
PractitionerRole.metameta​is equivalent toPractitionerRole.metaPractitionerRole.metaElement `PractitionerRole.meta` is mapped to FHIR R4 element `PractitionerRole.meta` as `Equivalent`.
PractitionerRole.implicitRulesimplicitRules​is equivalent toPractitionerRole.implicitRulesPractitionerRole.implicitRulesElement `PractitionerRole.implicitRules` is mapped to FHIR R4 element `PractitionerRole.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.
PractitionerRole.languagelanguage​is equivalent toPractitionerRole.languagePractitionerRole.languageElement `PractitionerRole.language` is mapped to FHIR R4 element `PractitionerRole.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).
PractitionerRole.texttext​is equivalent toPractitionerRole.textPractitionerRole.textElement `PractitionerRole.text` is mapped to FHIR R4 element `PractitionerRole.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.
PractitionerRole.containedcontained​is equivalent toPractitionerRole.containedPractitionerRole.containedElement `PractitionerRole.contained` is mapped to FHIR R4 element `PractitionerRole.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.
PractitionerRole.identifieridentifier​is equivalent toPractitionerRole.identifierPractitionerRole.identifierElement `PractitionerRole.identifier` is mapped to FHIR R4 element `PractitionerRole.identifier` as `Equivalent`. A specific identifier value (e.g. Minnesota Registration ID) may appear on multiple PractitionerRole instances which could be for different periods, or different Roles (or other reasons). A specific identifier may be included multiple times in the same PractitionerRole instance with different identifier validity periods.
PractitionerRole.activeactive​is equivalent toPractitionerRole.activePractitionerRole.activeElement `PractitionerRole.active` is mapped to FHIR R4 element `PractitionerRole.active` as `Equivalent`. If this value is false, you may refer to the period to see when the role was in active use. If there is no period specified, no inference can be made about when it was active.
PractitionerRole.periodperiod​is equivalent toPractitionerRole.periodPractitionerRole.periodElement `PractitionerRole.period` is mapped to FHIR R4 element `PractitionerRole.period` as `Equivalent`. If a practitioner is performing a role within an organization over multiple, non-adjacent periods, there should be a distinct PractitionerRole instance for each period. For example, if a nurse is employed at a hospital, leaves the organization for a period of time due to pandemic related stress, but returns post-pandemic to the same job role, there would be two PractitionerRole instances for the different periods of employment.
PractitionerRole.practitionerpractitioner​is equivalent toPractitionerRole.practitionerPractitionerRole.practitionerElement `PractitionerRole.practitioner` is mapped to FHIR R4 element `PractitionerRole.practitioner` as `Equivalent`.
PractitionerRole.organizationorganization​is equivalent toPractitionerRole.organizationPractitionerRole.organizationElement `PractitionerRole.organization` is mapped to FHIR R4 element `PractitionerRole.organization` as `Equivalent`.
PractitionerRole.codecode​is equivalent toPractitionerRole.codePractitionerRole.codeElement `PractitionerRole.code` is mapped to FHIR R4 element `PractitionerRole.code` as `Equivalent`. A person may have more than one role.
PractitionerRole.specialtyspecialty​is equivalent toPractitionerRole.specialtyPractitionerRole.specialtyElement `PractitionerRole.specialty` is mapped to FHIR R4 element `PractitionerRole.specialty` as `Equivalent`. The specialty represents the functional role a practitioner is playing within an organization/location. This role may require the individual have certain qualifications, which would be represented in the Practitioner.qualifications property. Note that qualifications may or might not relate to or be required by the practicing specialty.
PractitionerRole.locationlocation​is equivalent toPractitionerRole.locationPractitionerRole.locationElement `PractitionerRole.location` is mapped to FHIR R4 element `PractitionerRole.location` as `Equivalent`.
PractitionerRole.healthcareServicehealthcareService​is equivalent toPractitionerRole.healthcareServicePractitionerRole.healthcareServiceElement `PractitionerRole.healthcareService` is mapped to FHIR R4 element `PractitionerRole.healthcareService` as `Equivalent`.
PractitionerRole.availabilityavailability​is related toPractitionerRole.availableTimePractitionerRole.availableTimeElement `PractitionerRole.availability` is mapped to FHIR R4 element `PractitionerRole.availableTime` as `SourceIsBroaderThanTarget`. Element `PractitionerRole.availability` is mapped to FHIR R4 element `PractitionerRole.notAvailable` as `SourceIsBroaderThanTarget`. The mappings for `PractitionerRole.availability` do not cover the following types: Availability. The mappings for `PractitionerRole.availability` do not cover the following types based on type expansion: allDay, availableEndTime, availableStartTime, availableTime, daysOfWeek, description, during, notAvailableTime. More detailed availability information may be provided in associated Schedule/Slot resources. Systems may choose to render availability differently than it is exchanged on the interface. For example, rather than "Mon, Tue, Wed, Thur, Fri from 9am-12am; Mon, Tue, Wed, Thur, Fri from 1pm-5pm" as would be implied by two availableTime repetitions, an application could render this information as "Mon-Fri 9-12am and 1-5pm". The NotAvailableTime(s) included indicate the general days/periods where the practitioner is not available (for things such as vacation time, or public holidays).
​is related toPractitionerRole.notAvailablePractitionerRole.notAvailableElement `PractitionerRole.availability` is mapped to FHIR R4 element `PractitionerRole.availableTime` as `SourceIsBroaderThanTarget`. Element `PractitionerRole.availability` is mapped to FHIR R4 element `PractitionerRole.notAvailable` as `SourceIsBroaderThanTarget`. The mappings for `PractitionerRole.availability` do not cover the following types: Availability. The mappings for `PractitionerRole.availability` do not cover the following types based on type expansion: allDay, availableEndTime, availableStartTime, availableTime, daysOfWeek, description, during, notAvailableTime. More detailed availability information may be provided in associated Schedule/Slot resources. Systems may choose to render availability differently than it is exchanged on the interface. For example, rather than "Mon, Tue, Wed, Thur, Fri from 9am-12am; Mon, Tue, Wed, Thur, Fri from 1pm-5pm" as would be implied by two availableTime repetitions, an application could render this information as "Mon-Fri 9-12am and 1-5pm". The NotAvailableTime(s) included indicate the general days/periods where the practitioner is not available (for things such as vacation time, or public holidays).
PractitionerRole.endpointendpoint​is equivalent toPractitionerRole.endpointPractitionerRole.endpointElement `PractitionerRole.endpoint` is mapped to FHIR R4 element `PractitionerRole.endpoint` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/PractitionerRole|5.0.0 to R5: Official contact details relating to this PractitionerRole (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
PractitionerRole.contact (contact)​maps to wider conceptExtension (R5: Official contact details relating to this PractitionerRole (new))Element `PractitionerRole.contact` has a context of PractitionerRole based on following the parent source element upwards and mapping to `PractitionerRole`. Element `PractitionerRole.contact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/PractitionerRole|5.0.0 to R5: Collection of characteristics (attributes) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
PractitionerRole.characteristic (characteristic)​maps to wider conceptExtension (R5: Collection of characteristics (attributes) (new))Element `PractitionerRole.characteristic` has a context of PractitionerRole based on following the parent source element upwards and mapping to `PractitionerRole`. Element `PractitionerRole.characteristic` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). These could be such things as is the service mode used by this role.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/PractitionerRole|5.0.0 to R5: A language the practitioner (in this role) can use in patient communication (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
PractitionerRole.communication (communication)​maps to wider conceptExtension (R5: A language the practitioner (in this role) can use in patient communication (new))Element `PractitionerRole.communication` has a context of PractitionerRole based on following the parent source element upwards and mapping to `PractitionerRole`. Element `PractitionerRole.communication` 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 code this but instead have it as free text. Hence CodeableConcept instead of code as the data type. Note that for non-patient oriented communication, see Practitioner.communication. Note that all 'person' type resources (Person, RelatedPerson, Patient, Practitioner) have a communication structure that includes preferences. Role or service oriented resources such as HealthcareService and PractitionerRole only include languages that are available for interacting with patients.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/PractitionerRole|5.0.0 to R5: Times the Practitioner is available at this location and/or healthcare service (including exceptions) additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PractitionerRole.availability (availability)​maps to wider conceptExtension (R5: Times the Practitioner is available at this location and/or healthcare service (including exceptions) additional types)Element `PractitionerRole.availability` is mapped to FHIR R4 element `PractitionerRole.availableTime` as `SourceIsBroaderThanTarget`. Element `PractitionerRole.availability` is mapped to FHIR R4 element `PractitionerRole.notAvailable` as `SourceIsBroaderThanTarget`. The mappings for `PractitionerRole.availability` do not cover the following types: Availability. The mappings for `PractitionerRole.availability` do not cover the following types based on type expansion: allDay, availableEndTime, availableStartTime, availableTime, daysOfWeek, description, during, notAvailableTime. More detailed availability information may be provided in associated Schedule/Slot resources. Systems may choose to render availability differently than it is exchanged on the interface. For example, rather than "Mon, Tue, Wed, Thur, Fri from 9am-12am; Mon, Tue, Wed, Thur, Fri from 1pm-5pm" as would be implied by two availableTime repetitions, an application could render this information as "Mon-Fri 9-12am and 1-5pm". The NotAvailableTime(s) included indicate the general days/periods where the practitioner is not available (for things such as vacation time, or public holidays).