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

FHIR IG analytics

Packagehl7.fhir.uv.xver-r5.r3
Resource TypeConceptMap
IdConceptMap-R5-Schedule-element-map-to-R3.json
FHIR VersionR3
Sourcehttp://hl7.org/fhir/uv/xver-r5.r3/0.1.0/ConceptMap-R5-Schedule-element-map-to-R3.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R5-Schedule-element-map-to-R3
Version0.1.0
Statusactive
Date2026-03-17T16:05:20.6542106-05:00
NameR5ScheduleElementMapToR3
TitleCross-version mapping for FHIR R5 Schedule to FHIR STU3 Schedule
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R5 Schedule to FHIR STU3.

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
kvdigital.terminsynchronisation-tvs#1.7.1-Expansionsextension-Schedule.nameKBV_EX_116117_TERMINSERVICE_TVS_TERMINSYNCHRONISATION_Schedule_Slot_Profile_Name
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Schedule.serviceTypeCross-version Extension for R5.Schedule.serviceType for use in FHIR R4

Narrative

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

Generated Narrative: ConceptMap R5-Schedule-element-map-to-R3

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


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

Source CodeRelationshipTarget CodeComment
Schedule.meta (meta)is equivalent toSchedule.metaElement `Schedule.meta` is mapped to FHIR STU3 element `Schedule.meta` as `Equivalent`.
Schedule.implicitRules (implicitRules)is equivalent toSchedule.implicitRulesElement `Schedule.implicitRules` is mapped to FHIR STU3 element `Schedule.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.
Schedule.language (language)is equivalent toSchedule.languageElement `Schedule.language` is mapped to FHIR STU3 element `Schedule.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).
Schedule.text (text)is equivalent toSchedule.textElement `Schedule.text` is mapped to FHIR STU3 element `Schedule.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.
Schedule.contained (contained)is equivalent toSchedule.containedElement `Schedule.contained` is mapped to FHIR STU3 element `Schedule.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
Schedule.identifier (identifier)is equivalent toSchedule.identifierElement `Schedule.identifier` is mapped to FHIR STU3 element `Schedule.identifier` as `Equivalent`.
Schedule.active (active)is equivalent toSchedule.activeElement `Schedule.active` is mapped to FHIR STU3 element `Schedule.active` as `Equivalent`. This element is labeled as a modifier because it may be used to mark that the resource was created in error.
Schedule.serviceCategory (serviceCategory)is equivalent toSchedule.serviceCategoryElement `Schedule.serviceCategory` is mapped to FHIR STU3 element `Schedule.serviceCategory` as `SourceIsBroaderThanTarget`.
Schedule.serviceType (serviceType)maps to wider conceptSchedule.serviceTypeElement `Schedule.serviceType` is mapped to FHIR STU3 element `Schedule.serviceType` as `SourceIsBroaderThanTarget`. The mappings for `Schedule.serviceType` do not cover the following types: CodeableReference. The mappings for `Schedule.serviceType` do not cover the following types based on type expansion: reference.
Schedule.specialty (specialty)is equivalent toSchedule.specialtyElement `Schedule.specialty` is mapped to FHIR STU3 element `Schedule.specialty` as `Equivalent`.
Schedule.actor (actor)maps to wider conceptSchedule.actorElement `Schedule.actor` is mapped to FHIR STU3 element `Schedule.actor` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Schedule.actor` with unmapped reference targets: CareTeam, Device, HealthcareService, Location, Patient, Practitioner, PractitionerRole, RelatedPerson. The capacity to support multiple referenced resource types should be used in cases where the specific resources themselves cannot be scheduled without the other, and thus only make sense to the system exposing them as a group. Common examples of this are where the combination of a practitioner and a room (Location) are always required by a system.
Schedule.planningHorizon (planningHorizon)is equivalent toSchedule.planningHorizonElement `Schedule.planningHorizon` is mapped to FHIR STU3 element `Schedule.planningHorizon` as `Equivalent`.
Schedule.comment (comment)is equivalent toSchedule.commentElement `Schedule.comment` is mapped to FHIR STU3 element `Schedule.comment` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Schedule|5.0.0 to R5: Specific service additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Schedule.serviceType (serviceType)is equivalent toExtension (R5: Specific service additional types)Element `Schedule.serviceType` is mapped to FHIR STU3 element `Schedule.serviceType` as `SourceIsBroaderThanTarget`. The mappings for `Schedule.serviceType` do not cover the following types: CodeableReference. The mappings for `Schedule.serviceType` do not cover the following types based on type expansion: reference.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Schedule|5.0.0 to R5: Human-readable label (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Schedule.name (name)maps to wider conceptExtension (R5: Human-readable label (new))Element `Schedule.name` has a context of Schedule based on following the parent source element upwards and mapping to `Schedule`. Element `Schedule.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This MAY be used to describe what the schedule is for where it is clearer than just the name of the single actor.

Source1

{
  "resourceType": "ConceptMap",
  "id": "R5-Schedule-element-map-to-R3",
  "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",
            "valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-Schedule-element-map-to-R3",
  "version": "0.1.0",
  "name": "R5ScheduleElementMapToR3",
  "title": "Cross-version mapping for FHIR R5 Schedule to FHIR STU3 Schedule",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:05:20.6542106-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 R5 Schedule to FHIR STU3.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceUri": "http://hl7.org/fhir/5.0",
  "targetUri": "http://hl7.org/fhir/3.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Schedule",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Schedule",
      "targetVersion": "3.0.2",
      "element": [
        {
          "code": "Schedule.meta",
          "display": "meta",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.meta",
              "display": "Schedule.meta",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.meta` is mapped to FHIR STU3 element `Schedule.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Schedule.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.implicitRules",
              "display": "Schedule.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.implicitRules` is mapped to FHIR STU3 element `Schedule.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 its narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "Schedule.language",
          "display": "language",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.language",
              "display": "Schedule.language",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.language` is mapped to FHIR STU3 element `Schedule.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": "Schedule.text",
          "display": "text",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.text",
              "display": "Schedule.text",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.text` is mapped to FHIR STU3 element `Schedule.text` as `Equivalent`.\nContained 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."
            }
          ]
        },
        {
          "code": "Schedule.contained",
          "display": "contained",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.contained",
              "display": "Schedule.contained",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.contained` is mapped to FHIR STU3 element `Schedule.contained` as `SourceIsBroaderThanTarget`.\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": "Schedule.identifier",
          "display": "identifier",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.identifier",
              "display": "Schedule.identifier",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.identifier` is mapped to FHIR STU3 element `Schedule.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Schedule.active",
          "display": "active",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.active",
              "display": "Schedule.active",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.active` is mapped to FHIR STU3 element `Schedule.active` as `Equivalent`.\nThis element is labeled as a modifier because it may be used to mark that the resource was created in error."
            }
          ]
        },
        {
          "code": "Schedule.serviceCategory",
          "display": "serviceCategory",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.serviceCategory",
              "display": "Schedule.serviceCategory",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.serviceCategory` is mapped to FHIR STU3 element `Schedule.serviceCategory` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "Schedule.serviceType",
          "display": "serviceType",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Schedule.serviceType",
              "display": "Schedule.serviceType",
              "equivalence": "wider",
              "comment": "Element `Schedule.serviceType` is mapped to FHIR STU3 element `Schedule.serviceType` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.serviceType` do not cover the following types: CodeableReference.\nThe mappings for `Schedule.serviceType` do not cover the following types based on type expansion: reference."
            }
          ]
        },
        {
          "code": "Schedule.specialty",
          "display": "specialty",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.specialty",
              "display": "Schedule.specialty",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.specialty` is mapped to FHIR STU3 element `Schedule.specialty` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Schedule.actor",
          "display": "actor",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Schedule.actor",
              "display": "Schedule.actor",
              "equivalence": "wider",
              "comment": "Element `Schedule.actor` is mapped to FHIR STU3 element `Schedule.actor` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Schedule.actor` with unmapped reference targets: CareTeam, Device, HealthcareService, Location, Patient, Practitioner, PractitionerRole, RelatedPerson.\nThe capacity to support multiple referenced resource types should be used in cases where the specific resources themselves cannot be scheduled without the other, and thus only make sense to the system exposing them as a group. Common examples of this are where the combination of a practitioner and a room (Location) are always required by a system."
            }
          ]
        },
        {
          "code": "Schedule.planningHorizon",
          "display": "planningHorizon",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.planningHorizon",
              "display": "Schedule.planningHorizon",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.planningHorizon` is mapped to FHIR STU3 element `Schedule.planningHorizon` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Schedule.comment",
          "display": "comment",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Schedule.comment",
              "display": "Schedule.comment",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.comment` is mapped to FHIR STU3 element `Schedule.comment` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Schedule",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Schedule.serviceType",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Schedule.serviceType",
          "display": "serviceType",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Schedule.serviceType` is mapped to FHIR STU3 element `Schedule.serviceType` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.serviceType` do not cover the following types: CodeableReference.\nThe mappings for `Schedule.serviceType` do not cover the following types based on type expansion: reference."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Schedule",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Schedule.name",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Schedule.name",
          "display": "name",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Schedule.name` has a context of Schedule based on following the parent source element upwards and mapping to `Schedule`.\nElement `Schedule.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis MAY be used to describe what the schedule is for where it is clearer than just the name of the single actor."
            }
          ]
        }
      ]
    }
  ]
}