FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

Narrative

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

Source1

{
  "resourceType": "ConceptMap",
  "id": "R3-Schedule-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-r3.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-r3.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R3-Schedule-element-map-to-R5",
  "version": "0.1.0",
  "name": "R3ScheduleElementMapToR5",
  "title": "Cross-version mapping for FHIR STU3 Schedule to FHIR R5 Schedule",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:05:00.4526607-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 STU3 Schedule to FHIR R5.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceScopeCanonical": "http://hl7.org/fhir/3.0",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Schedule|3.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/Schedule|5.0.0",
      "element": [
        {
          "code": "Schedule.meta",
          "display": "meta",
          "target": [
            {
              "code": "Schedule.meta",
              "display": "Schedule.meta",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Schedule.meta` is mapped to FHIR R5 element `Schedule.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.meta` do not cover the following types: Meta.\nThe mappings for `Schedule.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        },
        {
          "code": "Schedule.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Schedule.implicitRules",
              "display": "Schedule.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Schedule.implicitRules` is mapped to FHIR R5 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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."
            }
          ]
        },
        {
          "code": "Schedule.language",
          "display": "language",
          "target": [
            {
              "code": "Schedule.language",
              "display": "Schedule.language",
              "relationship": "equivalent",
              "comment": "Element `Schedule.language` is mapped to FHIR R5 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": [
            {
              "code": "Schedule.text",
              "display": "Schedule.text",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Schedule.text` is mapped to FHIR R5 element `Schedule.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.text` do not cover the following types: Narrative.\nThe mappings for `Schedule.text` do not cover the following types based on type expansion: div, status.\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 in formation is added later."
            }
          ]
        },
        {
          "code": "Schedule.contained",
          "display": "contained",
          "target": [
            {
              "code": "Schedule.contained",
              "display": "Schedule.contained",
              "relationship": "equivalent",
              "comment": "Element `Schedule.contained` is mapped to FHIR R5 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."
            }
          ]
        },
        {
          "code": "Schedule.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Schedule.identifier",
              "display": "Schedule.identifier",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Schedule.identifier` is mapped to FHIR R5 element `Schedule.identifier` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.identifier` do not cover the following types: Identifier.\nThe mappings for `Schedule.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value."
            }
          ]
        },
        {
          "code": "Schedule.active",
          "display": "active",
          "target": [
            {
              "code": "Schedule.active",
              "display": "Schedule.active",
              "relationship": "equivalent",
              "comment": "Element `Schedule.active` is mapped to FHIR R5 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": [
            {
              "code": "Schedule.serviceCategory",
              "display": "Schedule.serviceCategory",
              "relationship": "equivalent",
              "comment": "Element `Schedule.serviceCategory` is mapped to FHIR R5 element `Schedule.serviceCategory` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Schedule.serviceType",
          "display": "serviceType",
          "target": [
            {
              "code": "Schedule.serviceType",
              "display": "Schedule.serviceType",
              "relationship": "equivalent",
              "comment": "Element `Schedule.serviceType` is mapped to FHIR R5 element `Schedule.serviceType` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Schedule.specialty",
          "display": "specialty",
          "target": [
            {
              "code": "Schedule.specialty",
              "display": "Schedule.specialty",
              "relationship": "equivalent",
              "comment": "Element `Schedule.specialty` is mapped to FHIR R5 element `Schedule.specialty` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Schedule.actor",
          "display": "actor",
          "target": [
            {
              "code": "Schedule.actor",
              "display": "Schedule.actor",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Schedule.actor` is mapped to FHIR R5 element `Schedule.actor` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Schedule.actor` with unmapped reference targets: 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 pracitioner and a room(location) are always required by a system."
            }
          ]
        },
        {
          "code": "Schedule.planningHorizon",
          "display": "planningHorizon",
          "target": [
            {
              "code": "Schedule.planningHorizon",
              "display": "Schedule.planningHorizon",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Schedule.planningHorizon` is mapped to FHIR R5 element `Schedule.planningHorizon` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.planningHorizon` do not cover the following types: Period.\nThe mappings for `Schedule.planningHorizon` do not cover the following types based on type expansion: end, start."
            }
          ]
        },
        {
          "code": "Schedule.comment",
          "display": "comment",
          "target": [
            {
              "code": "Schedule.comment",
              "display": "Schedule.comment",
              "relationship": "equivalent",
              "comment": "Element `Schedule.comment` is mapped to FHIR R5 element `Schedule.comment` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Schedule|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Schedule.meta|0.1.0",
      "element": [
        {
          "code": "Schedule.meta",
          "display": "meta",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Schedule.meta` is mapped to FHIR R5 element `Schedule.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.meta` do not cover the following types: Meta.\nThe mappings for `Schedule.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Schedule|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Schedule.text|0.1.0",
      "element": [
        {
          "code": "Schedule.text",
          "display": "text",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Schedule.text` is mapped to FHIR R5 element `Schedule.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.text` do not cover the following types: Narrative.\nThe mappings for `Schedule.text` do not cover the following types based on type expansion: div, status.\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 in formation is added later."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Schedule|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Schedule.identifier|0.1.0",
      "element": [
        {
          "code": "Schedule.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Schedule.identifier` is mapped to FHIR R5 element `Schedule.identifier` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.identifier` do not cover the following types: Identifier.\nThe mappings for `Schedule.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Schedule|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Schedule.planningHorizon|0.1.0",
      "element": [
        {
          "code": "Schedule.planningHorizon",
          "display": "planningHorizon",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Schedule.planningHorizon` is mapped to FHIR R5 element `Schedule.planningHorizon` as `SourceIsBroaderThanTarget`.\nThe mappings for `Schedule.planningHorizon` do not cover the following types: Period.\nThe mappings for `Schedule.planningHorizon` do not cover the following types based on type expansion: end, start."
            }
          ]
        }
      ]
    }
  ]
}