FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r4.r5
Resource TypeConceptMap
IdConceptMap-R4-Practitioner-element-map-to-R5.json
FHIR VersionR5
Sourcehttp://hl7.org/fhir/uv/xver-r4.r5/0.1.0/ConceptMap-R4-Practitioner-element-map-to-R5.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R4-Practitioner-element-map-to-R5
Version0.1.0
Statusactive
Date2026-03-17T16:04:37.2795825-05:00
NameR4PractitionerElementMapToR5
TitleCross-version mapping for FHIR R4 Practitioner to FHIR R5 Practitioner
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R4 Practitioner to FHIR R5.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R4-Practitioner-element-map-to-R5

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


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

Source CodeRelationshipTarget CodeComment
Practitioner.meta (meta)is equivalent toPractitioner.metaElement `Practitioner.meta` is mapped to FHIR R5 element `Practitioner.meta` as `Equivalent`.
Practitioner.implicitRules (implicitRules)is equivalent toPractitioner.implicitRulesElement `Practitioner.implicitRules` is mapped to FHIR R5 element `Practitioner.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 it's narrative along with other profiles, value sets, etc.
Practitioner.language (language)is equivalent toPractitioner.languageElement `Practitioner.language` is mapped to FHIR R5 element `Practitioner.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).
Practitioner.text (text)is equivalent toPractitioner.textElement `Practitioner.text` is mapped to FHIR R5 element `Practitioner.text` as `Equivalent`. 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 information is added later.
Practitioner.contained (contained)is equivalent toPractitioner.containedElement `Practitioner.contained` is mapped to FHIR R5 element `Practitioner.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.
Practitioner.identifier (identifier)is equivalent toPractitioner.identifierElement `Practitioner.identifier` is mapped to FHIR R5 element `Practitioner.identifier` as `Equivalent`.
Practitioner.active (active)is equivalent toPractitioner.activeElement `Practitioner.active` is mapped to FHIR R5 element `Practitioner.active` as `Equivalent`. If the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role.
Practitioner.name (name)is equivalent toPractitioner.nameElement `Practitioner.name` is mapped to FHIR R5 element `Practitioner.name` as `Equivalent`. The selection of the use property should ensure that there is a single usual name specified, and others use the nickname (alias), old, or other values as appropriate. In general, select the value to be used in the ResourceReference.display based on this: 1. There is more than 1 name 2. Use = usual 3. Period is current to the date of the usage 4. Use = official 5. Other order as decided by internal business rules.
Practitioner.telecom (telecom)is equivalent toPractitioner.telecomElement `Practitioner.telecom` is mapped to FHIR R5 element `Practitioner.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 to help with identification. These typically will have home numbers, or mobile numbers that are not role specific.
Practitioner.address (address)is equivalent toPractitioner.addressElement `Practitioner.address` is mapped to FHIR R5 element `Practitioner.address` as `Equivalent`. The PractitionerRole does not have an address value on it, as it is expected that the location property be used for this purpose (which has an address).
Practitioner.gender (gender)is equivalent toPractitioner.genderElement `Practitioner.gender` is mapped to FHIR R5 element `Practitioner.gender` as `Equivalent`.
Practitioner.birthDate (birthDate)is equivalent toPractitioner.birthDateElement `Practitioner.birthDate` is mapped to FHIR R5 element `Practitioner.birthDate` as `Equivalent`.
Practitioner.photo (photo)is equivalent toPractitioner.photoElement `Practitioner.photo` is mapped to FHIR R5 element `Practitioner.photo` as `Equivalent`.
Practitioner.qualification (qualification)is broader thanPractitioner.qualificationElement `Practitioner.qualification` is mapped to FHIR R5 element `Practitioner.qualification` as `Equivalent`.
Practitioner.qualification.identifier (identifier)is equivalent toPractitioner.qualification.identifierElement `Practitioner.qualification.identifier` is mapped to FHIR R5 element `Practitioner.qualification.identifier` as `Equivalent`.
Practitioner.qualification.code (code)is equivalent toPractitioner.qualification.codeElement `Practitioner.qualification.code` is mapped to FHIR R5 element `Practitioner.qualification.code` as `Equivalent`.
Practitioner.qualification.period (period)is equivalent toPractitioner.qualification.periodElement `Practitioner.qualification.period` is mapped to FHIR R5 element `Practitioner.qualification.period` as `Equivalent`.
Practitioner.qualification.issuer (issuer)is equivalent toPractitioner.qualification.issuerElement `Practitioner.qualification.issuer` is mapped to FHIR R5 element `Practitioner.qualification.issuer` as `Equivalent`.
Practitioner.communication (communication)is equivalent toPractitioner.communication.languageElement `Practitioner.communication` is mapped to FHIR R5 element `Practitioner.communication.language` as `SourceIsBroaderThanTarget`. 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.

Source1

{
  "resourceType": "ConceptMap",
  "id": "R4-Practitioner-element-map-to-R5",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4-Practitioner-element-map-to-R5",
  "version": "0.1.0",
  "name": "R4PractitionerElementMapToR5",
  "title": "Cross-version mapping for FHIR R4 Practitioner to FHIR R5 Practitioner",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:37.2795825-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4 Practitioner to FHIR R5.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceScopeCanonical": "http://hl7.org/fhir/4.0",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Practitioner|4.0.1",
      "target": "http://hl7.org/fhir/StructureDefinition/Practitioner|5.0.0",
      "element": [
        {
          "code": "Practitioner.meta",
          "display": "meta",
          "target": [
            {
              "code": "Practitioner.meta",
              "display": "Practitioner.meta",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.meta` is mapped to FHIR R5 element `Practitioner.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Practitioner.implicitRules",
              "display": "Practitioner.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.implicitRules` is mapped to FHIR R5 element `Practitioner.implicitRules` as `Equivalent`.\nAsserting 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 it's narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "Practitioner.language",
          "display": "language",
          "target": [
            {
              "code": "Practitioner.language",
              "display": "Practitioner.language",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.language` is mapped to FHIR R5 element `Practitioner.language` as `Equivalent`.\nLanguage 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)."
            }
          ]
        },
        {
          "code": "Practitioner.text",
          "display": "text",
          "target": [
            {
              "code": "Practitioner.text",
              "display": "Practitioner.text",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.text` is mapped to FHIR R5 element `Practitioner.text` as `Equivalent`.\nContained 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 information is added later."
            }
          ]
        },
        {
          "code": "Practitioner.contained",
          "display": "contained",
          "target": [
            {
              "code": "Practitioner.contained",
              "display": "Practitioner.contained",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.contained` is mapped to FHIR R5 element `Practitioner.contained` as `Equivalent`.\nThis 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."
            }
          ]
        },
        {
          "code": "Practitioner.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Practitioner.identifier",
              "display": "Practitioner.identifier",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.identifier` is mapped to FHIR R5 element `Practitioner.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.active",
          "display": "active",
          "target": [
            {
              "code": "Practitioner.active",
              "display": "Practitioner.active",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.active` is mapped to FHIR R5 element `Practitioner.active` as `Equivalent`.\nIf the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role."
            }
          ]
        },
        {
          "code": "Practitioner.name",
          "display": "name",
          "target": [
            {
              "code": "Practitioner.name",
              "display": "Practitioner.name",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.name` is mapped to FHIR R5 element `Practitioner.name` as `Equivalent`.\nThe selection of the use property should ensure that there is a single usual name specified, and others use the nickname (alias), old, or other values as appropriate.  \r\rIn general, select the value to be used in the ResourceReference.display based on this:\r\r1. There is more than 1 name\r2. Use = usual\r3. Period is current to the date of the usage\r4. Use = official\r5. Other order as decided by internal business rules."
            }
          ]
        },
        {
          "code": "Practitioner.telecom",
          "display": "telecom",
          "target": [
            {
              "code": "Practitioner.telecom",
              "display": "Practitioner.telecom",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.telecom` is mapped to FHIR R5 element `Practitioner.telecom` as `Equivalent`.\nPerson may have multiple ways to be contacted with different uses or applicable periods.  May need to have options for contacting the person urgently and to help with identification.  These typically will have home numbers, or mobile numbers that are not role specific."
            }
          ]
        },
        {
          "code": "Practitioner.address",
          "display": "address",
          "target": [
            {
              "code": "Practitioner.address",
              "display": "Practitioner.address",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.address` is mapped to FHIR R5 element `Practitioner.address` as `Equivalent`.\nThe PractitionerRole does not have an address value on it, as it is expected that the location property be used for this purpose (which has an address)."
            }
          ]
        },
        {
          "code": "Practitioner.gender",
          "display": "gender",
          "target": [
            {
              "code": "Practitioner.gender",
              "display": "Practitioner.gender",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.gender` is mapped to FHIR R5 element `Practitioner.gender` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.birthDate",
          "display": "birthDate",
          "target": [
            {
              "code": "Practitioner.birthDate",
              "display": "Practitioner.birthDate",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.birthDate` is mapped to FHIR R5 element `Practitioner.birthDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.photo",
          "display": "photo",
          "target": [
            {
              "code": "Practitioner.photo",
              "display": "Practitioner.photo",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.photo` is mapped to FHIR R5 element `Practitioner.photo` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.qualification",
          "display": "qualification",
          "target": [
            {
              "code": "Practitioner.qualification",
              "display": "Practitioner.qualification",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Practitioner.qualification` is mapped to FHIR R5 element `Practitioner.qualification` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.qualification.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Practitioner.qualification.identifier",
              "display": "Practitioner.qualification.identifier",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.qualification.identifier` is mapped to FHIR R5 element `Practitioner.qualification.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.qualification.code",
          "display": "code",
          "target": [
            {
              "code": "Practitioner.qualification.code",
              "display": "Practitioner.qualification.code",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.qualification.code` is mapped to FHIR R5 element `Practitioner.qualification.code` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.qualification.period",
          "display": "period",
          "target": [
            {
              "code": "Practitioner.qualification.period",
              "display": "Practitioner.qualification.period",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.qualification.period` is mapped to FHIR R5 element `Practitioner.qualification.period` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.qualification.issuer",
          "display": "issuer",
          "target": [
            {
              "code": "Practitioner.qualification.issuer",
              "display": "Practitioner.qualification.issuer",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.qualification.issuer` is mapped to FHIR R5 element `Practitioner.qualification.issuer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Practitioner.communication",
          "display": "communication",
          "target": [
            {
              "code": "Practitioner.communication.language",
              "display": "Practitioner.communication.language",
              "relationship": "equivalent",
              "comment": "Element `Practitioner.communication` is mapped to FHIR R5 element `Practitioner.communication.language` as `SourceIsBroaderThanTarget`.\nThe 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."
            }
          ]
        }
      ]
    }
  ]
}