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": "R2-Conformance-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-r2.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-r2.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R2-Conformance-element-map-to-R5",
  "version": "0.1.0",
  "name": "R2ConformanceElementMapToR5",
  "title": "Cross-version mapping for FHIR DSTU2 Conformance to FHIR R5 CapabilityStatement",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:05:26.2023001-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 DSTU2 Conformance to FHIR R5.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceScopeCanonical": "http://hl7.org/fhir/1.0",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|5.0.0",
      "element": [
        {
          "code": "Conformance.meta",
          "display": "meta",
          "target": [
            {
              "code": "CapabilityStatement.meta",
              "display": "CapabilityStatement.meta",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.meta` is mapped to FHIR R5 element `CapabilityStatement.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.meta` do not cover the following types: Meta.\nThe mappings for `Conformance.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        },
        {
          "code": "Conformance.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "CapabilityStatement.implicitRules",
              "display": "CapabilityStatement.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Conformance.implicitRules` is mapped to FHIR R5 element `CapabilityStatement.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 as much as possible."
            }
          ]
        },
        {
          "code": "Conformance.language",
          "display": "language",
          "target": [
            {
              "code": "CapabilityStatement.language",
              "display": "CapabilityStatement.language",
              "relationship": "equivalent",
              "comment": "Element `Conformance.language` is mapped to FHIR R5 element `CapabilityStatement.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": "Conformance.text",
          "display": "text",
          "target": [
            {
              "code": "CapabilityStatement.text",
              "display": "CapabilityStatement.text",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.text` is mapped to FHIR R5 element `CapabilityStatement.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.text` do not cover the following types: Narrative.\nThe mappings for `Conformance.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."
            }
          ]
        },
        {
          "code": "Conformance.contained",
          "display": "contained",
          "target": [
            {
              "code": "CapabilityStatement.contained",
              "display": "CapabilityStatement.contained",
              "relationship": "equivalent",
              "comment": "Element `Conformance.contained` is mapped to FHIR R5 element `CapabilityStatement.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": "Conformance.url",
          "display": "url",
          "target": [
            {
              "code": "CapabilityStatement.url",
              "display": "CapabilityStatement.url",
              "relationship": "equivalent",
              "comment": "Element `Conformance.url` is mapped to FHIR R5 element `CapabilityStatement.url` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.version",
          "display": "version",
          "target": [
            {
              "code": "CapabilityStatement.version",
              "display": "CapabilityStatement.version",
              "relationship": "equivalent",
              "comment": "Element `Conformance.version` is mapped to FHIR R5 element `CapabilityStatement.version` as `Equivalent`.\nThere may be multiple different instances of a conformance statement that have the same identifier but different versions."
            }
          ]
        },
        {
          "code": "Conformance.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.name",
              "display": "CapabilityStatement.name",
              "relationship": "equivalent",
              "comment": "Element `Conformance.name` is mapped to FHIR R5 element `CapabilityStatement.name` as `Equivalent`.\nThe name is not expected to be globally unique."
            }
          ]
        },
        {
          "code": "Conformance.status",
          "display": "status",
          "target": [
            {
              "code": "CapabilityStatement.status",
              "display": "CapabilityStatement.status",
              "relationship": "source-is-narrower-than-target",
              "comment": "Element `Conformance.status` is mapped to FHIR R5 element `CapabilityStatement.status` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Conformance.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nThis is not intended for use with actual conformance statements, but where conformance statements are used to describe possible or desired systems."
            }
          ]
        },
        {
          "code": "Conformance.experimental",
          "display": "experimental",
          "target": [
            {
              "code": "CapabilityStatement.experimental",
              "display": "CapabilityStatement.experimental",
              "relationship": "equivalent",
              "comment": "Element `Conformance.experimental` is mapped to FHIR R5 element `CapabilityStatement.experimental` as `Equivalent`.\nAllows filtering of conformance statements that are appropriate for use vs. not."
            }
          ]
        },
        {
          "code": "Conformance.publisher",
          "display": "publisher",
          "target": [
            {
              "code": "CapabilityStatement.publisher",
              "display": "CapabilityStatement.publisher",
              "relationship": "equivalent",
              "comment": "Element `Conformance.publisher` is mapped to FHIR R5 element `CapabilityStatement.publisher` as `Equivalent`.\nUsually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context."
            }
          ]
        },
        {
          "code": "Conformance.contact",
          "display": "contact",
          "target": [
            {
              "code": "CapabilityStatement.contact",
              "display": "CapabilityStatement.contact",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.contact` is mapped to FHIR R5 element `CapabilityStatement.contact` as `Equivalent`.\nMay be a web site, an email address, a telephone number (tel:), etc."
            }
          ]
        },
        {
          "code": "Conformance.contact.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.contact",
              "display": "CapabilityStatement.contact",
              "relationship": "related-to",
              "comment": "Element `Conformance.contact.name` is mapped to FHIR R5 element `CapabilityStatement.contact` as `RelatedTo`.\nThe mappings for `Conformance.contact.name` do not cover the following types: string.\nThe mappings for `Conformance.contact.name` do not cover the following types based on type expansion: value.\nIf there is no named individual, the telecom is for the organization as a whole."
            }
          ]
        },
        {
          "code": "Conformance.contact.telecom",
          "display": "telecom",
          "target": [
            {
              "code": "CapabilityStatement.contact",
              "display": "CapabilityStatement.contact",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.contact.telecom` is mapped to FHIR R5 element `CapabilityStatement.contact` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.contact.telecom` do not cover the following types: ContactPoint.\nThe mappings for `Conformance.contact.telecom` do not cover the following types based on type expansion: period, rank, system, use, value."
            }
          ]
        },
        {
          "code": "Conformance.date",
          "display": "date",
          "target": [
            {
              "code": "CapabilityStatement.date",
              "display": "CapabilityStatement.date",
              "relationship": "equivalent",
              "comment": "Element `Conformance.date` is mapped to FHIR R5 element `CapabilityStatement.date` as `Equivalent`.\nAdditional specific dates may be added as extensions."
            }
          ]
        },
        {
          "code": "Conformance.description",
          "display": "description",
          "target": [
            {
              "code": "CapabilityStatement.description",
              "display": "CapabilityStatement.description",
              "relationship": "equivalent",
              "comment": "Element `Conformance.description` is mapped to FHIR R5 element `CapabilityStatement.description` as `Equivalent`.\nThis field may include the purpose of this conformance statement, comments about its context etc. This does not need to be populated if the description is adequately implied by the software or implementation details."
            }
          ]
        },
        {
          "code": "Conformance.requirements",
          "display": "requirements",
          "target": [
            {
              "code": "CapabilityStatement.purpose",
              "display": "CapabilityStatement.purpose",
              "relationship": "equivalent",
              "comment": "Element `Conformance.requirements` is mapped to FHIR R5 element `CapabilityStatement.purpose` as `Equivalent`.\nThis element does not describe the usage of the conformance statement (that's done in comments), rather it's for traceability of *why* the element is either needed or why the constraints exist as they do.  This may be used to point to source materials or specifications that drove the structure of this data element."
            }
          ]
        },
        {
          "code": "Conformance.copyright",
          "display": "copyright",
          "target": [
            {
              "code": "CapabilityStatement.copyright",
              "display": "CapabilityStatement.copyright",
              "relationship": "equivalent",
              "comment": "Element `Conformance.copyright` is mapped to FHIR R5 element `CapabilityStatement.copyright` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.kind",
          "display": "kind",
          "target": [
            {
              "code": "CapabilityStatement.kind",
              "display": "CapabilityStatement.kind",
              "relationship": "equivalent",
              "comment": "Element `Conformance.kind` is mapped to FHIR R5 element `CapabilityStatement.kind` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.software",
          "display": "software",
          "target": [
            {
              "code": "CapabilityStatement.software",
              "display": "CapabilityStatement.software",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.software` is mapped to FHIR R5 element `CapabilityStatement.software` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.software.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.software.name",
              "display": "CapabilityStatement.software.name",
              "relationship": "equivalent",
              "comment": "Element `Conformance.software.name` is mapped to FHIR R5 element `CapabilityStatement.software.name` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.software.version",
          "display": "version",
          "target": [
            {
              "code": "CapabilityStatement.software.version",
              "display": "CapabilityStatement.software.version",
              "relationship": "equivalent",
              "comment": "Element `Conformance.software.version` is mapped to FHIR R5 element `CapabilityStatement.software.version` as `Equivalent`.\nIf possible, version should be specified, as statements are likely to be different for different versions of software."
            }
          ]
        },
        {
          "code": "Conformance.software.releaseDate",
          "display": "releaseDate",
          "target": [
            {
              "code": "CapabilityStatement.software.releaseDate",
              "display": "CapabilityStatement.software.releaseDate",
              "relationship": "equivalent",
              "comment": "Element `Conformance.software.releaseDate` is mapped to FHIR R5 element `CapabilityStatement.software.releaseDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.implementation",
          "display": "implementation",
          "target": [
            {
              "code": "CapabilityStatement.implementation",
              "display": "CapabilityStatement.implementation",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.implementation` is mapped to FHIR R5 element `CapabilityStatement.implementation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.implementation.description",
          "display": "description",
          "target": [
            {
              "code": "CapabilityStatement.implementation.description",
              "display": "CapabilityStatement.implementation.description",
              "relationship": "equivalent",
              "comment": "Element `Conformance.implementation.description` is mapped to FHIR R5 element `CapabilityStatement.implementation.description` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.implementation.url",
          "display": "url",
          "target": [
            {
              "code": "CapabilityStatement.implementation.url",
              "display": "CapabilityStatement.implementation.url",
              "relationship": "equivalent",
              "comment": "Element `Conformance.implementation.url` is mapped to FHIR R5 element `CapabilityStatement.implementation.url` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.fhirVersion",
          "display": "fhirVersion",
          "target": [
            {
              "code": "CapabilityStatement.fhirVersion",
              "display": "CapabilityStatement.fhirVersion",
              "relationship": "source-is-narrower-than-target",
              "comment": "Element `Conformance.fhirVersion` is mapped to FHIR R5 element `CapabilityStatement.fhirVersion` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Conformance.format",
          "display": "format",
          "target": [
            {
              "code": "CapabilityStatement.format",
              "display": "CapabilityStatement.format",
              "relationship": "equivalent",
              "comment": "Element `Conformance.format` is mapped to FHIR R5 element `CapabilityStatement.format` as `Equivalent`.\n\"xml\" or \"json\" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here."
            }
          ]
        },
        {
          "code": "Conformance.profile",
          "display": "profile",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.supportedProfile",
              "display": "CapabilityStatement.rest.resource.supportedProfile",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.profile` do not cover the following types: Reference.\nThe mappings for `Conformance.profile` do not cover the following types based on type expansion: display, reference.\nSupported profiles are different to the profiles that apply to a particular resource in rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that does? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile).  Typical supported profiles cross resource types to describe a network of related resources, so they are listed here rather than by resource. However, they do not need to describe more than one resource."
            }
          ]
        },
        {
          "code": "Conformance.rest",
          "display": "rest",
          "target": [
            {
              "code": "CapabilityStatement.rest",
              "display": "CapabilityStatement.rest",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest` is mapped to FHIR R5 element `CapabilityStatement.rest` as `Equivalent`.\nMultiple repetitions allow definition of both client and / or server behaviors or possibly behaviors under different configuration settings (for software or requirements statements)."
            }
          ]
        },
        {
          "code": "Conformance.rest.mode",
          "display": "mode",
          "target": [
            {
              "code": "CapabilityStatement.rest.mode",
              "display": "CapabilityStatement.rest.mode",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.mode` is mapped to FHIR R5 element `CapabilityStatement.rest.mode` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.documentation",
              "display": "CapabilityStatement.rest.documentation",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.security",
          "display": "security",
          "target": [
            {
              "code": "CapabilityStatement.rest.security",
              "display": "CapabilityStatement.rest.security",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.security` is mapped to FHIR R5 element `CapabilityStatement.rest.security` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.security.cors",
          "display": "cors",
          "target": [
            {
              "code": "CapabilityStatement.rest.security.cors",
              "display": "CapabilityStatement.rest.security.cors",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.security.cors` is mapped to FHIR R5 element `CapabilityStatement.rest.security.cors` as `Equivalent`.\nThe easiest CORS headers to add are Access-Control-Allow-Origin: * & Access-Control-Request-Method: GET, POST, PUT, DELETE. All servers SHOULD support CORS."
            }
          ]
        },
        {
          "code": "Conformance.rest.security.service",
          "display": "service",
          "target": [
            {
              "code": "CapabilityStatement.rest.security.service",
              "display": "CapabilityStatement.rest.security.service",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.security.service` is mapped to FHIR R5 element `CapabilityStatement.rest.security.service` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.security.description",
          "display": "description",
          "target": [
            {
              "code": "CapabilityStatement.rest.security.description",
              "display": "CapabilityStatement.rest.security.description",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.security.description` is mapped to FHIR R5 element `CapabilityStatement.rest.security.description` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource",
          "display": "resource",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource",
              "display": "CapabilityStatement.rest.resource",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.resource` is mapped to FHIR R5 element `CapabilityStatement.rest.resource` as `Equivalent`.\nMax of one repetition per resource type."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.type",
          "display": "type",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.type",
              "display": "CapabilityStatement.rest.resource.type",
              "relationship": "related-to",
              "comment": "Element `Conformance.rest.resource.type` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.type` as `RelatedTo`.\nThe mappings for `Conformance.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.profile",
          "display": "profile",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.profile",
              "display": "CapabilityStatement.rest.resource.profile",
              "relationship": "related-to",
              "comment": "Element `Conformance.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.\nElement `Conformance.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`.\nThe mappings for `Conformance.rest.resource.profile` do not cover the following types: Reference.\nThe mappings for `Conformance.rest.resource.profile` do not cover the following types based on type expansion: display, reference.\nThe profile applies to all  resources of this type - i.e. it is the superset of what is supported by the system."
            },
            {
              "code": "CapabilityStatement.rest.resource.supportedProfile",
              "display": "CapabilityStatement.rest.resource.supportedProfile",
              "relationship": "related-to",
              "comment": "Element `Conformance.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.\nElement `Conformance.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`.\nThe mappings for `Conformance.rest.resource.profile` do not cover the following types: Reference.\nThe mappings for `Conformance.rest.resource.profile` do not cover the following types based on type expansion: display, reference.\nThe profile applies to all  resources of this type - i.e. it is the superset of what is supported by the system."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.interaction",
          "display": "interaction",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.interaction",
              "display": "CapabilityStatement.rest.resource.interaction",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.resource.interaction` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.interaction.code",
          "display": "code",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.interaction.code",
              "display": "CapabilityStatement.rest.resource.interaction.code",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.resource.interaction.code` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction.code` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.interaction.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.interaction.documentation",
              "display": "CapabilityStatement.rest.resource.interaction.documentation",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.interaction.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.versioning",
          "display": "versioning",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.versioning",
              "display": "CapabilityStatement.rest.resource.versioning",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.versioning` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.versioning` as `Equivalent`.\nIf a server supports versionIds correctly, it SHOULD support vread too, but is not required to do so."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.readHistory",
          "display": "readHistory",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.readHistory",
              "display": "CapabilityStatement.rest.resource.readHistory",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.readHistory` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.readHistory` as `Equivalent`.\nIt is useful to support the vRead operation for current operations, even if past versions aren't available."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.updateCreate",
          "display": "updateCreate",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.updateCreate",
              "display": "CapabilityStatement.rest.resource.updateCreate",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.updateCreate` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.updateCreate` as `Equivalent`.\nAllowing the clients to create new identities on the server means that the system administrator needs to have confidence that the clients do not create clashing identities between them. Obviously, if there is only one client, this won't happen. While creating identities on the client means that the clients need to be managed, it's much more convenient for many scenarios if such management can be put in place."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.conditionalCreate",
          "display": "conditionalCreate",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.conditionalCreate",
              "display": "CapabilityStatement.rest.resource.conditionalCreate",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.conditionalCreate` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.conditionalCreate` as `Equivalent`.\nConditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.conditionalUpdate",
          "display": "conditionalUpdate",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.conditionalUpdate",
              "display": "CapabilityStatement.rest.resource.conditionalUpdate",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.conditionalUpdate` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.conditionalUpdate` as `Equivalent`.\nConditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.conditionalDelete",
          "display": "conditionalDelete",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.conditionalDelete",
              "display": "CapabilityStatement.rest.resource.conditionalDelete",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.conditionalDelete` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.conditionalDelete` as `Equivalent`.\nConditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.searchInclude",
          "display": "searchInclude",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchInclude",
              "display": "CapabilityStatement.rest.resource.searchInclude",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.searchInclude` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`.\nIf this list is empty, the server does not support includes."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.searchRevInclude",
          "display": "searchRevInclude",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchRevInclude",
              "display": "CapabilityStatement.rest.resource.searchRevInclude",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.searchRevInclude` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchRevInclude` as `Equivalent`.\nIf this list is empty, the server does not support includes."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.searchParam",
          "display": "searchParam",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam",
              "display": "CapabilityStatement.rest.resource.searchParam",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.resource.searchParam` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.searchParam.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam.name",
              "display": "CapabilityStatement.rest.resource.searchParam.name",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.searchParam.name` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.name` as `Equivalent`.\nParameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.searchParam.definition",
          "display": "definition",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam.definition",
              "display": "CapabilityStatement.rest.resource.searchParam.definition",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.searchParam.definition` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.definition` as `Equivalent`.\nThis SHOULD be present, and matches SearchParameter.url."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.searchParam.type",
          "display": "type",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam.type",
              "display": "CapabilityStatement.rest.resource.searchParam.type",
              "relationship": "source-is-narrower-than-target",
              "comment": "Element `Conformance.rest.resource.searchParam.type` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.type` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Conformance.rest.resource.searchParam.type` do not allow expression of the necessary codes, per the bindings on the source and target.\nWhile this can be looked up from the definition, it is included here as a convenience for systems that autogenerate a query interface based on the server conformance statement.  It SHALL be the same as the type in the search parameter definition."
            }
          ]
        },
        {
          "code": "Conformance.rest.resource.searchParam.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam.documentation",
              "display": "CapabilityStatement.rest.resource.searchParam.documentation",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.searchParam.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.interaction",
          "display": "interaction",
          "target": [
            {
              "code": "CapabilityStatement.rest.interaction",
              "display": "CapabilityStatement.rest.interaction",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.interaction` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.interaction.code",
          "display": "code",
          "target": [
            {
              "code": "CapabilityStatement.rest.interaction.code",
              "display": "CapabilityStatement.rest.interaction.code",
              "relationship": "source-is-narrower-than-target",
              "comment": "Element `Conformance.rest.interaction.code` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction.code` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Conformance.rest.interaction.code` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "Conformance.rest.interaction.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.interaction.documentation",
              "display": "CapabilityStatement.rest.interaction.documentation",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.interaction.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.searchParam",
          "display": "searchParam",
          "target": [
            {
              "code": "CapabilityStatement.rest.searchParam",
              "display": "CapabilityStatement.rest.searchParam",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.searchParam` is mapped to FHIR R5 element `CapabilityStatement.rest.searchParam` as `Equivalent`.\nTypically, the only search parameters supported for all parameters are search parameters that apply to all resources - tags, profiles, text search etc."
            }
          ]
        },
        {
          "code": "Conformance.rest.operation",
          "display": "operation",
          "target": [
            {
              "code": "CapabilityStatement.rest.operation",
              "display": "CapabilityStatement.rest.operation",
              "relationship": "related-to",
              "comment": "Element `Conformance.rest.operation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`.\nElement `Conformance.rest.operation` is mapped to FHIR R5 element `CapabilityStatement.rest.operation` as `Equivalent`."
            },
            {
              "code": "CapabilityStatement.rest.resource.operation",
              "display": "CapabilityStatement.rest.resource.operation",
              "relationship": "related-to",
              "comment": "Element `Conformance.rest.operation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`.\nElement `Conformance.rest.operation` is mapped to FHIR R5 element `CapabilityStatement.rest.operation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.rest.operation.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.operation.name",
              "display": "CapabilityStatement.rest.resource.operation.name",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.operation.name` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation.name` as `Equivalent`.\nThe name here SHOULD be the same as the name in the definition, unless there is a name clash and the name cannot be used."
            }
          ]
        },
        {
          "code": "Conformance.rest.operation.definition",
          "display": "definition",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.operation.definition",
              "display": "CapabilityStatement.rest.resource.operation.definition",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.operation.definition` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.rest.operation.definition` do not cover the following types: Reference.\nThe mappings for `Conformance.rest.operation.definition` do not cover the following types based on type expansion: display, reference.\nThis can be used to build an HTML form to invoke the operation, for instance."
            }
          ]
        },
        {
          "code": "Conformance.rest.compartment",
          "display": "compartment",
          "target": [
            {
              "code": "CapabilityStatement.rest.compartment",
              "display": "CapabilityStatement.rest.compartment",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.compartment` is mapped to FHIR R5 element `CapabilityStatement.rest.compartment` as `Equivalent`.\nAt present, the only defined compartments are at [[compartments.html]]."
            }
          ]
        },
        {
          "code": "Conformance.messaging",
          "display": "messaging",
          "target": [
            {
              "code": "CapabilityStatement.messaging",
              "display": "CapabilityStatement.messaging",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.messaging` is mapped to FHIR R5 element `CapabilityStatement.messaging` as `Equivalent`.\nMultiple repetitions allow the documentation of multiple endpoints per solution."
            }
          ]
        },
        {
          "code": "Conformance.messaging.endpoint",
          "display": "endpoint",
          "target": [
            {
              "code": "CapabilityStatement.messaging.endpoint",
              "display": "CapabilityStatement.messaging.endpoint",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.messaging.endpoint` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.messaging.endpoint.protocol",
          "display": "protocol",
          "target": [
            {
              "code": "CapabilityStatement.messaging.endpoint.protocol",
              "display": "CapabilityStatement.messaging.endpoint.protocol",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.endpoint.protocol` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.messaging.endpoint.address",
          "display": "address",
          "target": [
            {
              "code": "CapabilityStatement.messaging.endpoint.address",
              "display": "CapabilityStatement.messaging.endpoint.address",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.endpoint.address` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.messaging.reliableCache",
          "display": "reliableCache",
          "target": [
            {
              "code": "CapabilityStatement.messaging.reliableCache",
              "display": "CapabilityStatement.messaging.reliableCache",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.reliableCache` is mapped to FHIR R5 element `CapabilityStatement.messaging.reliableCache` as `Equivalent`.\nIf this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging."
            }
          ]
        },
        {
          "code": "Conformance.messaging.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.messaging.documentation",
              "display": "CapabilityStatement.messaging.documentation",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.documentation` is mapped to FHIR R5 element `CapabilityStatement.messaging.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.document",
          "display": "document",
          "target": [
            {
              "code": "CapabilityStatement.document",
              "display": "CapabilityStatement.document",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.document` is mapped to FHIR R5 element `CapabilityStatement.document` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.document.mode",
          "display": "mode",
          "target": [
            {
              "code": "CapabilityStatement.document.mode",
              "display": "CapabilityStatement.document.mode",
              "relationship": "equivalent",
              "comment": "Element `Conformance.document.mode` is mapped to FHIR R5 element `CapabilityStatement.document.mode` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.document.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.document.documentation",
              "display": "CapabilityStatement.document.documentation",
              "relationship": "equivalent",
              "comment": "Element `Conformance.document.documentation` is mapped to FHIR R5 element `CapabilityStatement.document.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Conformance.document.profile",
          "display": "profile",
          "target": [
            {
              "code": "CapabilityStatement.document.profile",
              "display": "CapabilityStatement.document.profile",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.document.profile` is mapped to FHIR R5 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.document.profile` do not cover the following types: Reference.\nThe mappings for `Conformance.document.profile` do not cover the following types based on type expansion: display, reference.\nThe first resource is the document resource."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.meta|0.1.0",
      "element": [
        {
          "code": "Conformance.meta",
          "display": "meta",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.meta` is mapped to FHIR R5 element `CapabilityStatement.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.meta` do not cover the following types: Meta.\nThe mappings for `Conformance.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.text|0.1.0",
      "element": [
        {
          "code": "Conformance.text",
          "display": "text",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.text` is mapped to FHIR R5 element `CapabilityStatement.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.text` do not cover the following types: Narrative.\nThe mappings for `Conformance.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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.contact.name|0.1.0",
      "element": [
        {
          "code": "Conformance.contact.name",
          "display": "name",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.contact.name` is mapped to FHIR R5 element `CapabilityStatement.contact` as `RelatedTo`.\nThe mappings for `Conformance.contact.name` do not cover the following types: string.\nThe mappings for `Conformance.contact.name` do not cover the following types based on type expansion: value.\nIf there is no named individual, the telecom is for the organization as a whole."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.contact.telecom|0.1.0",
      "element": [
        {
          "code": "Conformance.contact.telecom",
          "display": "telecom",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.contact.telecom` is mapped to FHIR R5 element `CapabilityStatement.contact` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.contact.telecom` do not cover the following types: ContactPoint.\nThe mappings for `Conformance.contact.telecom` do not cover the following types based on type expansion: period, rank, system, use, value."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.acceptUnknown|0.1.0",
      "element": [
        {
          "code": "Conformance.acceptUnknown",
          "display": "acceptUnknown",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Conformance.acceptUnknown` has a context of CapabilityStatement based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.acceptUnknown` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nUnknown elements in a resource can only arise as later versions of the specification are published, because this is the only place where such elements can be defined. Hence accepting unknown elements is about inter-version compatibility.  Applications are recommended to accept unknown extensions and elements ('both'), but this is not always possible."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.profile|0.1.0",
      "element": [
        {
          "code": "Conformance.profile",
          "display": "profile",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.profile` do not cover the following types: Reference.\nThe mappings for `Conformance.profile` do not cover the following types based on type expansion: display, reference.\nSupported profiles are different to the profiles that apply to a particular resource in rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that does? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile).  Typical supported profiles cross resource types to describe a network of related resources, so they are listed here rather than by resource. However, they do not need to describe more than one resource."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.security.certificate|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.security.certificate",
          "display": "certificate",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.security.certificate` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.rest.security.certificate` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Conformance.rest.security.certificate.type",
          "display": "type",
          "target": [
            {
              "code": "Extension.extension:type",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.security.certificate.type` is part of an existing definition because parent element `Conformance.rest.security.certificate` requires a cross-version extension.\nElement `Conformance.rest.security.certificate.type` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.rest.security.certificate.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Conformance.rest.security.certificate.blob",
          "display": "blob",
          "target": [
            {
              "code": "Extension.extension:blob",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.security.certificate.blob` is part of an existing definition because parent element `Conformance.rest.security.certificate` requires a cross-version extension.\nElement `Conformance.rest.security.certificate.blob` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.rest.security.certificate.blob` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.resource.type|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.resource.type",
          "display": "type",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.resource.type` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.type` as `RelatedTo`.\nThe mappings for `Conformance.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.resource.profile|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.resource.profile",
          "display": "profile",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.\nElement `Conformance.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`.\nThe mappings for `Conformance.rest.resource.profile` do not cover the following types: Reference.\nThe mappings for `Conformance.rest.resource.profile` do not cover the following types based on type expansion: display, reference.\nThe profile applies to all  resources of this type - i.e. it is the superset of what is supported by the system."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.resource.interaction.code|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.resource.interaction.code",
          "display": "code",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.resource.interaction.code` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction.code` as `SourceIsBroaderThanTarget`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.resource.searchParam.target|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.resource.searchParam.target",
          "display": "target",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.searchParam.target` has a context of CapabilityStatement.rest.resource.searchParam based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.rest.resource.searchParam.target` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThis SHALL be the same as or a proper subset of the resources listed in the search parameter definition."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.resource.searchParam.modifier|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.resource.searchParam.modifier",
          "display": "modifier",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.searchParam.modifier` has a context of CapabilityStatement.rest.resource.searchParam based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.rest.resource.searchParam.modifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.resource.searchParam.chain|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.resource.searchParam.chain",
          "display": "chain",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.resource.searchParam.chain` has a context of CapabilityStatement.rest.resource.searchParam based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.rest.resource.searchParam.chain` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nSystems are not required to list all the chain names they support, but if they don't list them, clients may not know to use them."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.transactionMode|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.transactionMode",
          "display": "transactionMode",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Conformance.rest.transactionMode` has a context of CapabilityStatement.rest based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.rest.transactionMode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.rest.operation.definition|0.1.0",
      "element": [
        {
          "code": "Conformance.rest.operation.definition",
          "display": "definition",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.rest.operation.definition` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.rest.operation.definition` do not cover the following types: Reference.\nThe mappings for `Conformance.rest.operation.definition` do not cover the following types based on type expansion: display, reference.\nThis can be used to build an HTML form to invoke the operation, for instance."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.messaging.event|0.1.0",
      "element": [
        {
          "code": "Conformance.messaging.event",
          "display": "event",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.event` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.messaging.event` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThe same event may be listed up to two times - once as sender and once as receiver."
            }
          ]
        },
        {
          "code": "Conformance.messaging.event.code",
          "display": "code",
          "target": [
            {
              "code": "Extension.extension:code",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.event.code` is part of an existing definition because parent element `Conformance.messaging.event` requires a cross-version extension.\nElement `Conformance.messaging.event.code` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.messaging.event.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Conformance.messaging.event.category",
          "display": "category",
          "target": [
            {
              "code": "Extension.extension:category",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.event.category` is part of an existing definition because parent element `Conformance.messaging.event` requires a cross-version extension.\nElement `Conformance.messaging.event.category` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.messaging.event.category` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Conformance.messaging.event.mode",
          "display": "mode",
          "target": [
            {
              "code": "Extension.extension:mode",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.event.mode` is part of an existing definition because parent element `Conformance.messaging.event` requires a cross-version extension.\nElement `Conformance.messaging.event.mode` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.messaging.event.mode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Conformance.messaging.event.focus",
          "display": "focus",
          "target": [
            {
              "code": "Extension.extension:focus",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.messaging.event.focus` is part of an existing definition because parent element `Conformance.messaging.event` requires a cross-version extension.\nElement `Conformance.messaging.event.focus` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.messaging.event.focus` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThis SHALL be provided if the event type supports multiple different resource types."
            }
          ]
        },
        {
          "code": "Conformance.messaging.event.request",
          "display": "request",
          "target": [
            {
              "code": "Extension.extension:request",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.event.request` is part of an existing definition because parent element `Conformance.messaging.event` requires a cross-version extension.\nElement `Conformance.messaging.event.request` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.messaging.event.request` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Conformance.messaging.event.response",
          "display": "response",
          "target": [
            {
              "code": "Extension.extension:response",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.event.response` is part of an existing definition because parent element `Conformance.messaging.event` requires a cross-version extension.\nElement `Conformance.messaging.event.response` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.messaging.event.response` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Conformance.messaging.event.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "Extension.extension:documentation",
              "relationship": "equivalent",
              "comment": "Element `Conformance.messaging.event.documentation` is part of an existing definition because parent element `Conformance.messaging.event` requires a cross-version extension.\nElement `Conformance.messaging.event.documentation` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `Conformance.messaging.event.documentation` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Conformance|1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-Conformance.document.profile|0.1.0",
      "element": [
        {
          "code": "Conformance.document.profile",
          "display": "profile",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Conformance.document.profile` is mapped to FHIR R5 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`.\nThe mappings for `Conformance.document.profile` do not cover the following types: Reference.\nThe mappings for `Conformance.document.profile` do not cover the following types based on type expansion: display, reference.\nThe first resource is the document resource."
            }
          ]
        }
      ]
    }
  ]
}