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-CapabilityStatement-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-CapabilityStatement-element-map-to-R5",
  "version": "0.1.0",
  "name": "R3CapabilityStatementElementMapToR5",
  "title": "Cross-version mapping for FHIR STU3 CapabilityStatement to FHIR R5 CapabilityStatement",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:59.3708933-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 CapabilityStatement 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/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|5.0.0",
      "element": [
        {
          "code": "CapabilityStatement.meta",
          "display": "meta",
          "target": [
            {
              "code": "CapabilityStatement.meta",
              "display": "CapabilityStatement.meta",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.meta` is mapped to FHIR R5 element `CapabilityStatement.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.meta` do not cover the following types: Meta.\nThe mappings for `CapabilityStatement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        },
        {
          "code": "CapabilityStatement.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "CapabilityStatement.implicitRules",
              "display": "CapabilityStatement.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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. \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": "CapabilityStatement.language",
          "display": "language",
          "target": [
            {
              "code": "CapabilityStatement.language",
              "display": "CapabilityStatement.language",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.text",
          "display": "text",
          "target": [
            {
              "code": "CapabilityStatement.text",
              "display": "CapabilityStatement.text",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.text` is mapped to FHIR R5 element `CapabilityStatement.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.text` do not cover the following types: Narrative.\nThe mappings for `CapabilityStatement.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": "CapabilityStatement.contained",
          "display": "contained",
          "target": [
            {
              "code": "CapabilityStatement.contained",
              "display": "CapabilityStatement.contained",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.url",
          "display": "url",
          "target": [
            {
              "code": "CapabilityStatement.url",
              "display": "CapabilityStatement.url",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.url` is mapped to FHIR R5 element `CapabilityStatement.url` as `Equivalent`.\nCan be a urn:uuid: or a urn:oid:, but real http: addresses are preferred.  Multiple instances may share the same url if they have a distinct version."
            }
          ]
        },
        {
          "code": "CapabilityStatement.version",
          "display": "version",
          "target": [
            {
              "code": "CapabilityStatement.version",
              "display": "CapabilityStatement.version",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.version` is mapped to FHIR R5 element `CapabilityStatement.version` as `Equivalent`.\nThere may be different capability statement instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a refrence to a particular business version of the capability statement with the format [url]|[version]."
            }
          ]
        },
        {
          "code": "CapabilityStatement.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.name",
              "display": "CapabilityStatement.name",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.name` is mapped to FHIR R5 element `CapabilityStatement.name` as `Equivalent`.\nThe name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly."
            }
          ]
        },
        {
          "code": "CapabilityStatement.title",
          "display": "title",
          "target": [
            {
              "code": "CapabilityStatement.title",
              "display": "CapabilityStatement.title",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.title` is mapped to FHIR R5 element `CapabilityStatement.title` as `Equivalent`.\nThis name does not need to be machine-processing friendly and may contain punctuation, white-space, etc."
            }
          ]
        },
        {
          "code": "CapabilityStatement.status",
          "display": "status",
          "target": [
            {
              "code": "CapabilityStatement.status",
              "display": "CapabilityStatement.status",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.status` is mapped to FHIR R5 element `CapabilityStatement.status` as `Equivalent`.\nAllows filtering of capability statements that are appropriate for use vs. not.  \nThis is labeled as \"Is Modifier\" because applications should not use a retired capability statement without due consideration. This is not intended for use with actual capability statements, but where capability statements are used to describe possible or desired systems."
            }
          ]
        },
        {
          "code": "CapabilityStatement.experimental",
          "display": "experimental",
          "target": [
            {
              "code": "CapabilityStatement.experimental",
              "display": "CapabilityStatement.experimental",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.experimental` is mapped to FHIR R5 element `CapabilityStatement.experimental` as `Equivalent`.\nAllows filtering of capability statement that are appropriate for use vs. not. This is labeled as \"Is Modifier\" because applications should not use an experimental capability statement in production."
            }
          ]
        },
        {
          "code": "CapabilityStatement.date",
          "display": "date",
          "target": [
            {
              "code": "CapabilityStatement.date",
              "display": "CapabilityStatement.date",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.date` is mapped to FHIR R5 element `CapabilityStatement.date` as `Equivalent`.\nNote that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the capability statement. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource."
            }
          ]
        },
        {
          "code": "CapabilityStatement.publisher",
          "display": "publisher",
          "target": [
            {
              "code": "CapabilityStatement.publisher",
              "display": "CapabilityStatement.publisher",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.publisher` is mapped to FHIR R5 element `CapabilityStatement.publisher` as `Equivalent`.\nUsually an organization, but may be an individual. The publisher (or steward) of the capability statement is the organization or individual primarily responsible for the maintenance and upkeep of the capability statement. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the capability statement. This item SHOULD be populated unless the information is available from context."
            }
          ]
        },
        {
          "code": "CapabilityStatement.contact",
          "display": "contact",
          "target": [
            {
              "code": "CapabilityStatement.contact",
              "display": "CapabilityStatement.contact",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.contact` is mapped to FHIR R5 element `CapabilityStatement.contact` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.contact` do not cover the following types: ContactDetail.\nThe mappings for `CapabilityStatement.contact` do not cover the following types based on type expansion: name, telecom.\nMay be a web site, an email address, a telephone number, etc."
            }
          ]
        },
        {
          "code": "CapabilityStatement.description",
          "display": "description",
          "target": [
            {
              "code": "CapabilityStatement.description",
              "display": "CapabilityStatement.description",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.description` is mapped to FHIR R5 element `CapabilityStatement.description` as `Equivalent`.\nThis description can be used to capture details such as why the capability statement was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the capability statement as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created). This does not need to be populated if the description is adequately implied by the software or implementation details."
            }
          ]
        },
        {
          "code": "CapabilityStatement.useContext",
          "display": "useContext",
          "target": [
            {
              "code": "CapabilityStatement.useContext",
              "display": "CapabilityStatement.useContext",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.useContext` is mapped to FHIR R5 element `CapabilityStatement.useContext` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.useContext` do not cover the following types: UsageContext.\nThe mappings for `CapabilityStatement.useContext` do not cover the following types based on type expansion: code, value[x].\nWhen multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."
            }
          ]
        },
        {
          "code": "CapabilityStatement.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "CapabilityStatement.jurisdiction",
              "display": "CapabilityStatement.jurisdiction",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.jurisdiction` is mapped to FHIR R5 element `CapabilityStatement.jurisdiction` as `Equivalent`.\nIt may be possible for the capability statement to be used in jurisdictions other than those for which it was originally designed or intended."
            }
          ]
        },
        {
          "code": "CapabilityStatement.purpose",
          "display": "purpose",
          "target": [
            {
              "code": "CapabilityStatement.purpose",
              "display": "CapabilityStatement.purpose",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.purpose` is mapped to FHIR R5 element `CapabilityStatement.purpose` as `Equivalent`.\nThis element does not describe the usage of the capability statement Instead  it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this capability statement."
            }
          ]
        },
        {
          "code": "CapabilityStatement.copyright",
          "display": "copyright",
          "target": [
            {
              "code": "CapabilityStatement.copyright",
              "display": "CapabilityStatement.copyright",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.copyright` is mapped to FHIR R5 element `CapabilityStatement.copyright` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.kind",
          "display": "kind",
          "target": [
            {
              "code": "CapabilityStatement.kind",
              "display": "CapabilityStatement.kind",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.kind` is mapped to FHIR R5 element `CapabilityStatement.kind` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.instantiates",
          "display": "instantiates",
          "target": [
            {
              "code": "CapabilityStatement.instantiates",
              "display": "CapabilityStatement.instantiates",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.instantiates` is mapped to FHIR R5 element `CapabilityStatement.instantiates` as `Equivalent`.\nHL7 defines the following Services: [Terminology Service](https://hl7.org/fhir/terminology-service.html).\n\nMany [Implementation Guides](http://fhir.org/guides/registry) define additional services."
            }
          ]
        },
        {
          "code": "CapabilityStatement.software",
          "display": "software",
          "target": [
            {
              "code": "CapabilityStatement.software",
              "display": "CapabilityStatement.software",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.software` is mapped to FHIR R5 element `CapabilityStatement.software` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.software.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.software.name",
              "display": "CapabilityStatement.software.name",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.software.name` is mapped to FHIR R5 element `CapabilityStatement.software.name` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.software.version",
          "display": "version",
          "target": [
            {
              "code": "CapabilityStatement.software.version",
              "display": "CapabilityStatement.software.version",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.software.version` is mapped to FHIR R5 element `CapabilityStatement.software.version` as `Equivalent`.\nIf possible, a version should be specified, as statements are likely to be different for different versions of software."
            }
          ]
        },
        {
          "code": "CapabilityStatement.software.releaseDate",
          "display": "releaseDate",
          "target": [
            {
              "code": "CapabilityStatement.software.releaseDate",
              "display": "CapabilityStatement.software.releaseDate",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.software.releaseDate` is mapped to FHIR R5 element `CapabilityStatement.software.releaseDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.implementation",
          "display": "implementation",
          "target": [
            {
              "code": "CapabilityStatement.implementation",
              "display": "CapabilityStatement.implementation",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.implementation` is mapped to FHIR R5 element `CapabilityStatement.implementation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.implementation.description",
          "display": "description",
          "target": [
            {
              "code": "CapabilityStatement.implementation.description",
              "display": "CapabilityStatement.implementation.description",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.implementation.description` is mapped to FHIR R5 element `CapabilityStatement.implementation.description` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.implementation.url",
          "display": "url",
          "target": [
            {
              "code": "CapabilityStatement.implementation.url",
              "display": "CapabilityStatement.implementation.url",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.implementation.url` is mapped to FHIR R5 element `CapabilityStatement.implementation.url` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.fhirVersion",
          "display": "fhirVersion",
          "target": [
            {
              "code": "CapabilityStatement.fhirVersion",
              "display": "CapabilityStatement.fhirVersion",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.fhirVersion` is mapped to FHIR R5 element `CapabilityStatement.fhirVersion` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.format",
          "display": "format",
          "target": [
            {
              "code": "CapabilityStatement.format",
              "display": "CapabilityStatement.format",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.format` is mapped to FHIR R5 element `CapabilityStatement.format` as `Equivalent`.\n\"xml\", \"json\" and \"ttl\" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here."
            }
          ]
        },
        {
          "code": "CapabilityStatement.patchFormat",
          "display": "patchFormat",
          "target": [
            {
              "code": "CapabilityStatement.patchFormat",
              "display": "CapabilityStatement.patchFormat",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.patchFormat` is mapped to FHIR R5 element `CapabilityStatement.patchFormat` as `Equivalent`.\nAt present, the patch mime types application/json-patch+json and application/xml-patch+xml are legal. Generally, if a server supports PATCH, it would be expected to support the patch formats and match the formats it supports, but this is not always possible or necessary."
            }
          ]
        },
        {
          "code": "CapabilityStatement.implementationGuide",
          "display": "implementationGuide",
          "target": [
            {
              "code": "CapabilityStatement.implementationGuide",
              "display": "CapabilityStatement.implementationGuide",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.implementationGuide` is mapped to FHIR R5 element `CapabilityStatement.implementationGuide` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.profile",
          "display": "profile",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.supportedProfile",
              "display": "CapabilityStatement.rest.resource.supportedProfile",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.profile` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.profile` do not cover the following types based on type expansion: display, identifier, reference.\nSupported profiles are different than 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).  Typically, 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": "CapabilityStatement.rest",
          "display": "rest",
          "target": [
            {
              "code": "CapabilityStatement.rest",
              "display": "CapabilityStatement.rest",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.mode",
          "display": "mode",
          "target": [
            {
              "code": "CapabilityStatement.rest.mode",
              "display": "CapabilityStatement.rest.mode",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.mode` is mapped to FHIR R5 element `CapabilityStatement.rest.mode` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.documentation",
              "display": "CapabilityStatement.rest.documentation",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.security",
          "display": "security",
          "target": [
            {
              "code": "CapabilityStatement.rest.security",
              "display": "CapabilityStatement.rest.security",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.security` is mapped to FHIR R5 element `CapabilityStatement.rest.security` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.security.cors",
          "display": "cors",
          "target": [
            {
              "code": "CapabilityStatement.rest.security.cors",
              "display": "CapabilityStatement.rest.security.cors",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.security.service",
          "display": "service",
          "target": [
            {
              "code": "CapabilityStatement.rest.security.service",
              "display": "CapabilityStatement.rest.security.service",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.security.service` is mapped to FHIR R5 element `CapabilityStatement.rest.security.service` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.security.description",
          "display": "description",
          "target": [
            {
              "code": "CapabilityStatement.rest.security.description",
              "display": "CapabilityStatement.rest.security.description",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.security.description` is mapped to FHIR R5 element `CapabilityStatement.rest.security.description` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource",
          "display": "resource",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource",
              "display": "CapabilityStatement.rest.resource",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.resource` is mapped to FHIR R5 element `CapabilityStatement.rest.resource` as `Equivalent`.\nMax of one repetition per resource type."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.type",
          "display": "type",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.type",
              "display": "CapabilityStatement.rest.resource.type",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.type` as `RelatedTo`.\nThe mappings for `CapabilityStatement.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.profile",
          "display": "profile",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.profile",
              "display": "CapabilityStatement.rest.resource.profile",
              "relationship": "related-to",
              "comment": "Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.\nElement `CapabilityStatement.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`.\nThe mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, 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 `CapabilityStatement.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.\nElement `CapabilityStatement.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`.\nThe mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, 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.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.documentation",
              "display": "CapabilityStatement.rest.resource.documentation",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.interaction",
          "display": "interaction",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.interaction",
              "display": "CapabilityStatement.rest.resource.interaction",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.resource.interaction` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.interaction.code",
          "display": "code",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.interaction.code",
              "display": "CapabilityStatement.rest.resource.interaction.code",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.interaction.code` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction.code` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.interaction.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.interaction.documentation",
              "display": "CapabilityStatement.rest.resource.interaction.documentation",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.interaction.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.versioning",
          "display": "versioning",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.versioning",
              "display": "CapabilityStatement.rest.resource.versioning",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.resource.readHistory",
          "display": "readHistory",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.readHistory",
              "display": "CapabilityStatement.rest.resource.readHistory",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.resource.updateCreate",
          "display": "updateCreate",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.updateCreate",
              "display": "CapabilityStatement.rest.resource.updateCreate",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.resource.conditionalCreate",
          "display": "conditionalCreate",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.conditionalCreate",
              "display": "CapabilityStatement.rest.resource.conditionalCreate",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.resource.conditionalRead",
          "display": "conditionalRead",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.conditionalRead",
              "display": "CapabilityStatement.rest.resource.conditionalRead",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.conditionalRead` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.conditionalRead` as `Equivalent`.\nConditional Read is mainly appropriate for interface engine scripts converting from other formats, such as v2."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.conditionalUpdate",
          "display": "conditionalUpdate",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.conditionalUpdate",
              "display": "CapabilityStatement.rest.resource.conditionalUpdate",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.resource.conditionalDelete",
          "display": "conditionalDelete",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.conditionalDelete",
              "display": "CapabilityStatement.rest.resource.conditionalDelete",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.resource.referencePolicy",
          "display": "referencePolicy",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.referencePolicy",
              "display": "CapabilityStatement.rest.resource.referencePolicy",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.referencePolicy` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.referencePolicy` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.searchInclude",
          "display": "searchInclude",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchInclude",
              "display": "CapabilityStatement.rest.resource.searchInclude",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.resource.searchRevInclude",
          "display": "searchRevInclude",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchRevInclude",
              "display": "CapabilityStatement.rest.resource.searchRevInclude",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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 reverse includes."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.searchParam",
          "display": "searchParam",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam",
              "display": "CapabilityStatement.rest.resource.searchParam",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.searchParam.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam.name",
              "display": "CapabilityStatement.rest.resource.searchParam.name",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.rest.resource.searchParam.definition",
          "display": "definition",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam.definition",
              "display": "CapabilityStatement.rest.resource.searchParam.definition",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.searchParam.definition` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.definition` as `Equivalent`.\nThis SHOULD be present, and matches refers to a SearchParameter by its canonical url. If systems wish to document their support for modifiers, comparators, target resource types, and chained parameters, they should do using a search parameter resource."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.searchParam.type",
          "display": "type",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam.type",
              "display": "CapabilityStatement.rest.resource.searchParam.type",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.type` as `SourceIsNarrowerThanTarget`.\nThe mappings for `CapabilityStatement.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 capability statement.  It SHALL be the same as the type in the search parameter definition."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.resource.searchParam.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.searchParam.documentation",
              "display": "CapabilityStatement.rest.resource.searchParam.documentation",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.searchParam.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.interaction",
          "display": "interaction",
          "target": [
            {
              "code": "CapabilityStatement.rest.interaction",
              "display": "CapabilityStatement.rest.interaction",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.interaction` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.interaction.code",
          "display": "code",
          "target": [
            {
              "code": "CapabilityStatement.rest.interaction.code",
              "display": "CapabilityStatement.rest.interaction.code",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.interaction.code` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction.code` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.interaction.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.rest.interaction.documentation",
              "display": "CapabilityStatement.rest.interaction.documentation",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.interaction.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.searchParam",
          "display": "searchParam",
          "target": [
            {
              "code": "CapabilityStatement.rest.searchParam",
              "display": "CapabilityStatement.rest.searchParam",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.searchParam` is mapped to FHIR R5 element `CapabilityStatement.rest.searchParam` as `Equivalent`.\nTypically, the only search parameters supported for all searchse are those that apply to all resources - tags, profiles, text search etc."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.operation",
          "display": "operation",
          "target": [
            {
              "code": "CapabilityStatement.rest.operation",
              "display": "CapabilityStatement.rest.operation",
              "relationship": "related-to",
              "comment": "Element `CapabilityStatement.rest.operation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`.\nElement `CapabilityStatement.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 `CapabilityStatement.rest.operation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`.\nElement `CapabilityStatement.rest.operation` is mapped to FHIR R5 element `CapabilityStatement.rest.operation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.operation.name",
          "display": "name",
          "target": [
            {
              "code": "CapabilityStatement.rest.resource.operation.name",
              "display": "CapabilityStatement.rest.resource.operation.name",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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. The name does not include the \"$\" portion that is always included in the URL."
            }
          ]
        },
        {
          "code": "CapabilityStatement.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 `CapabilityStatement.rest.operation.definition` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types based on type expansion: display, identifier, reference.\nThis can be used to build an HTML form to invoke the operation, for instance."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.compartment",
          "display": "compartment",
          "target": [
            {
              "code": "CapabilityStatement.rest.compartment",
              "display": "CapabilityStatement.rest.compartment",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.compartment` is mapped to FHIR R5 element `CapabilityStatement.rest.compartment` as `Equivalent`.\nAt present, the only defined compartments are at [CompartmentDefinition](https://hl7.org/fhir/compartmentdefinition.html)."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging",
          "display": "messaging",
          "target": [
            {
              "code": "CapabilityStatement.messaging",
              "display": "CapabilityStatement.messaging",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.messaging` is mapped to FHIR R5 element `CapabilityStatement.messaging` as `Equivalent`.\nMultiple repetitions allow the documentation of multiple endpoints per solution."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.endpoint",
          "display": "endpoint",
          "target": [
            {
              "code": "CapabilityStatement.messaging.endpoint",
              "display": "CapabilityStatement.messaging.endpoint",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.messaging.endpoint` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.endpoint.protocol",
          "display": "protocol",
          "target": [
            {
              "code": "CapabilityStatement.messaging.endpoint.protocol",
              "display": "CapabilityStatement.messaging.endpoint.protocol",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.endpoint.protocol` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.endpoint.address",
          "display": "address",
          "target": [
            {
              "code": "CapabilityStatement.messaging.endpoint.address",
              "display": "CapabilityStatement.messaging.endpoint.address",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.endpoint.address` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.reliableCache",
          "display": "reliableCache",
          "target": [
            {
              "code": "CapabilityStatement.messaging.reliableCache",
              "display": "CapabilityStatement.messaging.reliableCache",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.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": "CapabilityStatement.messaging.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.messaging.documentation",
              "display": "CapabilityStatement.messaging.documentation",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.documentation` is mapped to FHIR R5 element `CapabilityStatement.messaging.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.supportedMessage",
          "display": "supportedMessage",
          "target": [
            {
              "code": "CapabilityStatement.messaging.supportedMessage",
              "display": "CapabilityStatement.messaging.supportedMessage",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.messaging.supportedMessage` is mapped to FHIR R5 element `CapabilityStatement.messaging.supportedMessage` as `Equivalent`.\nThis is a proposed alternative to the messaging.event structure."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.supportedMessage.mode",
          "display": "mode",
          "target": [
            {
              "code": "CapabilityStatement.messaging.supportedMessage.mode",
              "display": "CapabilityStatement.messaging.supportedMessage.mode",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.supportedMessage.mode` is mapped to FHIR R5 element `CapabilityStatement.messaging.supportedMessage.mode` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.supportedMessage.definition",
          "display": "definition",
          "target": [
            {
              "code": "CapabilityStatement.messaging.supportedMessage.definition",
              "display": "CapabilityStatement.messaging.supportedMessage.definition",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R5 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: display, identifier, reference."
            }
          ]
        },
        {
          "code": "CapabilityStatement.document",
          "display": "document",
          "target": [
            {
              "code": "CapabilityStatement.document",
              "display": "CapabilityStatement.document",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.document` is mapped to FHIR R5 element `CapabilityStatement.document` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.document.mode",
          "display": "mode",
          "target": [
            {
              "code": "CapabilityStatement.document.mode",
              "display": "CapabilityStatement.document.mode",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.document.mode` is mapped to FHIR R5 element `CapabilityStatement.document.mode` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.document.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "CapabilityStatement.document.documentation",
              "display": "CapabilityStatement.document.documentation",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.document.documentation` is mapped to FHIR R5 element `CapabilityStatement.document.documentation` as `Equivalent`."
            }
          ]
        },
        {
          "code": "CapabilityStatement.document.profile",
          "display": "profile",
          "target": [
            {
              "code": "CapabilityStatement.document.profile",
              "display": "CapabilityStatement.document.profile",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.document.profile` is mapped to FHIR R5 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.document.profile` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: display, identifier, reference.\nThe first resource is the document resource."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.meta|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.meta",
          "display": "meta",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.meta` is mapped to FHIR R5 element `CapabilityStatement.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.meta` do not cover the following types: Meta.\nThe mappings for `CapabilityStatement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.text|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.text",
          "display": "text",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.text` is mapped to FHIR R5 element `CapabilityStatement.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.text` do not cover the following types: Narrative.\nThe mappings for `CapabilityStatement.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/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.contact|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.contact",
          "display": "contact",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.contact` is mapped to FHIR R5 element `CapabilityStatement.contact` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.contact` do not cover the following types: ContactDetail.\nThe mappings for `CapabilityStatement.contact` do not cover the following types based on type expansion: name, telecom.\nMay be a web site, an email address, a telephone number, etc."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.useContext|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.useContext",
          "display": "useContext",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.useContext` is mapped to FHIR R5 element `CapabilityStatement.useContext` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.useContext` do not cover the following types: UsageContext.\nThe mappings for `CapabilityStatement.useContext` do not cover the following types based on type expansion: code, value[x].\nWhen multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.acceptUnknown|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.acceptUnknown",
          "display": "acceptUnknown",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.acceptUnknown` has a context of CapabilityStatement based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.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.\n\nApplications are recommended to accept unknown extensions and elements ('both'), but this is not always possible."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.profile|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.profile",
          "display": "profile",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.profile` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.profile` do not cover the following types based on type expansion: display, identifier, reference.\nSupported profiles are different than 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).  Typically, 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/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.security.certificate|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.rest.security.certificate",
          "display": "certificate",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.security.certificate` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.rest.security.certificate` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "CapabilityStatement.rest.security.certificate.type",
          "display": "type",
          "target": [
            {
              "code": "Extension.extension:type",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.security.certificate.type` is part of an existing definition because parent element `CapabilityStatement.rest.security.certificate` requires a cross-version extension.\nElement `CapabilityStatement.rest.security.certificate.type` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.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": "CapabilityStatement.rest.security.certificate.blob",
          "display": "blob",
          "target": [
            {
              "code": "Extension.extension:blob",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.security.certificate.blob` is part of an existing definition because parent element `CapabilityStatement.rest.security.certificate` requires a cross-version extension.\nElement `CapabilityStatement.rest.security.certificate.blob` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.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/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.resource.type|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.rest.resource.type",
          "display": "type",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.type` as `RelatedTo`.\nThe mappings for `CapabilityStatement.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/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.resource.profile|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.rest.resource.profile",
          "display": "profile",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.\nElement `CapabilityStatement.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`.\nThe mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, 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/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.operation.definition|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.rest.operation.definition",
          "display": "definition",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types based on type expansion: display, identifier, reference.\nThis can be used to build an HTML form to invoke the operation, for instance."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.messaging.supportedMessage.definition|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.messaging.supportedMessage.definition",
          "display": "definition",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R5 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: display, identifier, reference."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.messaging.event|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.messaging.event",
          "display": "event",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `CapabilityStatement.messaging.event` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.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": "CapabilityStatement.messaging.event.code",
          "display": "code",
          "target": [
            {
              "code": "Extension.extension:code",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.event.code` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension.\nElement `CapabilityStatement.messaging.event.code` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.messaging.event.code` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.event.category",
          "display": "category",
          "target": [
            {
              "code": "Extension.extension:category",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.event.category` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension.\nElement `CapabilityStatement.messaging.event.category` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.messaging.event.category` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.event.mode",
          "display": "mode",
          "target": [
            {
              "code": "Extension.extension:mode",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.event.mode` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension.\nElement `CapabilityStatement.messaging.event.mode` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.messaging.event.mode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.event.focus",
          "display": "focus",
          "target": [
            {
              "code": "Extension.extension:focus",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.event.focus` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension.\nElement `CapabilityStatement.messaging.event.focus` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.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": "CapabilityStatement.messaging.event.request",
          "display": "request",
          "target": [
            {
              "code": "Extension.extension:request",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.event.request` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension.\nElement `CapabilityStatement.messaging.event.request` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.messaging.event.request` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.event.response",
          "display": "response",
          "target": [
            {
              "code": "Extension.extension:response",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.event.response` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension.\nElement `CapabilityStatement.messaging.event.response` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.messaging.event.response` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "CapabilityStatement.messaging.event.documentation",
          "display": "documentation",
          "target": [
            {
              "code": "Extension.extension:documentation",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.messaging.event.documentation` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension.\nElement `CapabilityStatement.messaging.event.documentation` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`.\nElement `CapabilityStatement.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/CapabilityStatement|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.document.profile|0.1.0",
      "element": [
        {
          "code": "CapabilityStatement.document.profile",
          "display": "profile",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `CapabilityStatement.document.profile` is mapped to FHIR R5 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`.\nThe mappings for `CapabilityStatement.document.profile` do not cover the following types: Reference.\nThe mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: display, identifier, reference.\nThe first resource is the document resource."
            }
          ]
        }
      ]
    }
  ]
}