R3-CapabilityStatement-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R3-CapabilityStatement-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R3-CapabilityStatement-element-map-to-R4 Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to CapabilityStatementversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 Codes from CapabilityStatement CapabilityStatement.meta meta is equivalent to CapabilityStatement.meta CapabilityStatement.meta Element `CapabilityStatement.meta` is mapped to FHIR R4 element `CapabilityStatement.meta` as `Equivalent`. CapabilityStatement.implicitRules implicitRules is equivalent to CapabilityStatement.implicitRules CapabilityStatement.implicitRules Element `CapabilityStatement.implicitRules` is mapped to FHIR R4 element `CapabilityStatement.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. CapabilityStatement.language language is equivalent to CapabilityStatement.language CapabilityStatement.language Element `CapabilityStatement.language` is mapped to FHIR R4 element `CapabilityStatement.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations gener…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4
        l: hl7.fhir.uv.xver-r3.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4
        l: hl7.fhir.uv.xver-r3.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R3-CapabilityStatement-element-map-to-R4
  l: R3-CapabilityStatement-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R3CapabilityStatementElementMapToR4
title:
  v: Cross-version mapping for FHIR STU3 CapabilityStatement to FHIR R4 CapabilityStatement
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:03:23.1770393-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR STU3 CapabilityStatement to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/3.0
  l: http://hl7.org/fhir/3.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
    l: CapabilityStatement
  source version:
    v: 3.0.2
  target:
    v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
    l: CapabilityStatement
  target version:
    v: 4.0.1
  element:
    code:
      v: CapabilityStatement.meta
    display:
      v: meta
    target:
      code:
        v: CapabilityStatement.meta
      display:
        v: CapabilityStatement.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.meta` is mapped to FHIR R4 element `CapabilityStatement.meta` as `Equivalent`.
  element:
    code:
      v: CapabilityStatement.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: CapabilityStatement.implicitRules
      display:
        v: CapabilityStatement.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.implicitRules` is mapped to FHIR R4 element `CapabilityStatement.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
  element:
    code:
      v: CapabilityStatement.language
    display:
      v: language
    target:
      code:
        v: CapabilityStatement.language
      display:
        v: CapabilityStatement.language
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.language` is mapped to FHIR R4 element `CapabilityStatement.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
  element:
    code:
      v: CapabilityStatement.text
    display:
      v: text
    target:
      code:
        v: CapabilityStatement.text
      display:
        v: CapabilityStatement.text
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.text` is mapped to FHIR R4 element `CapabilityStatement.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
  element:
    code:
      v: CapabilityStatement.contained
    display:
      v: contained
    target:
      code:
        v: CapabilityStatement.contained
      display:
        v: CapabilityStatement.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.contained` is mapped to FHIR R4 element `CapabilityStatement.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
  element:
    code:
      v: CapabilityStatement.url
    display:
      v: url
    target:
      code:
        v: CapabilityStatement.url
      display:
        v: CapabilityStatement.url
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.url` is mapped to FHIR R4 element `CapabilityStatement.url` as `Equivalent`. Can 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.
  element:
    code:
      v: CapabilityStatement.version
    display:
      v: version
    target:
      code:
        v: CapabilityStatement.version
      display:
        v: CapabilityStatement.version
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.version` is mapped to FHIR R4 element `CapabilityStatement.version` as `Equivalent`. There 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].
  element:
    code:
      v: CapabilityStatement.name
    display:
      v: name
    target:
      code:
        v: CapabilityStatement.name
      display:
        v: CapabilityStatement.name
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.name` is mapped to FHIR R4 element `CapabilityStatement.name` as `Equivalent`. The 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:
  v: CapabilityStatement.title
display:
  v: title
target:
  code:
    v: CapabilityStatement.title
  display:
    v: CapabilityStatement.title
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.title` is mapped to FHIR R4 element `CapabilityStatement.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

code:
  v: CapabilityStatement.status
display:
  v: status
target:
  code:
    v: CapabilityStatement.status
  display:
    v: CapabilityStatement.status
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.status` is mapped to FHIR R4 element `CapabilityStatement.status` as `Equivalent`. Allows filtering of capability statements that are appropriate for use vs. not. This 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:
  v: CapabilityStatement.experimental
display:
  v: experimental
target:
  code:
    v: CapabilityStatement.experimental
  display:
    v: CapabilityStatement.experimental
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.experimental` is mapped to FHIR R4 element `CapabilityStatement.experimental` as `Equivalent`. Allows 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:
  v: CapabilityStatement.date
display:
  v: date
target:
  code:
    v: CapabilityStatement.date
  display:
    v: CapabilityStatement.date
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.date` is mapped to FHIR R4 element `CapabilityStatement.date` as `Equivalent`. Note 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:
  v: CapabilityStatement.publisher
display:
  v: publisher
target:
  code:
    v: CapabilityStatement.publisher
  display:
    v: CapabilityStatement.publisher
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.publisher` is mapped to FHIR R4 element `CapabilityStatement.publisher` as `Equivalent`. Usually 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:
  v: CapabilityStatement.contact
display:
  v: contact
target:
  code:
    v: CapabilityStatement.contact
  display:
    v: CapabilityStatement.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.contact` is mapped to FHIR R4 element `CapabilityStatement.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.

code:
  v: CapabilityStatement.description
display:
  v: description
target:
  code:
    v: CapabilityStatement.description
  display:
    v: CapabilityStatement.description
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.description` is mapped to FHIR R4 element `CapabilityStatement.description` as `Equivalent`. This 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:
  v: CapabilityStatement.useContext
display:
  v: useContext
target:
  code:
    v: CapabilityStatement.useContext
  display:
    v: CapabilityStatement.useContext
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.useContext` is mapped to FHIR R4 element `CapabilityStatement.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.

code:
  v: CapabilityStatement.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: CapabilityStatement.jurisdiction
  display:
    v: CapabilityStatement.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.jurisdiction` is mapped to FHIR R4 element `CapabilityStatement.jurisdiction` as `Equivalent`. It may be possible for the capability statement to be used in jurisdictions other than those for which it was originally designed or intended.

code:
  v: CapabilityStatement.purpose
display:
  v: purpose
target:
  code:
    v: CapabilityStatement.purpose
  display:
    v: CapabilityStatement.purpose
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.purpose` is mapped to FHIR R4 element `CapabilityStatement.purpose` as `Equivalent`. This 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:
  v: CapabilityStatement.copyright
display:
  v: copyright
target:
  code:
    v: CapabilityStatement.copyright
  display:
    v: CapabilityStatement.copyright
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.copyright` is mapped to FHIR R4 element `CapabilityStatement.copyright` as `Equivalent`.

code:
  v: CapabilityStatement.kind
display:
  v: kind
target:
  code:
    v: CapabilityStatement.kind
  display:
    v: CapabilityStatement.kind
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.kind` is mapped to FHIR R4 element `CapabilityStatement.kind` as `Equivalent`.

code:
  v: CapabilityStatement.instantiates
display:
  v: instantiates
target:
  code:
    v: CapabilityStatement.instantiates
  display:
    v: CapabilityStatement.instantiates
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.instantiates` is mapped to FHIR R4 element `CapabilityStatement.instantiates` as `Equivalent`. HL7 defines the following Services: [Terminology Service](https://hl7.org/fhir/terminology-service.html). Many [Implementation Guides](http://fhir.org/guides/registry) define additional services.

code:
  v: CapabilityStatement.software
display:
  v: software
target:
  code:
    v: CapabilityStatement.software
  display:
    v: CapabilityStatement.software
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.software` is mapped to FHIR R4 element `CapabilityStatement.software` as `Equivalent`.

code:
  v: CapabilityStatement.software.name
display:
  v: name
target:
  code:
    v: CapabilityStatement.software.name
  display:
    v: CapabilityStatement.software.name
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.software.name` is mapped to FHIR R4 element `CapabilityStatement.software.name` as `Equivalent`.

code:
  v: CapabilityStatement.software.version
display:
  v: version
target:
  code:
    v: CapabilityStatement.software.version
  display:
    v: CapabilityStatement.software.version
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.software.version` is mapped to FHIR R4 element `CapabilityStatement.software.version` as `Equivalent`. If possible, a version should be specified, as statements are likely to be different for different versions of software.

code:
  v: CapabilityStatement.software.releaseDate
display:
  v: releaseDate
target:
  code:
    v: CapabilityStatement.software.releaseDate
  display:
    v: CapabilityStatement.software.releaseDate
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.software.releaseDate` is mapped to FHIR R4 element `CapabilityStatement.software.releaseDate` as `Equivalent`.

code:
  v: CapabilityStatement.implementation
display:
  v: implementation
target:
  code:
    v: CapabilityStatement.implementation
  display:
    v: CapabilityStatement.implementation
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.implementation` is mapped to FHIR R4 element `CapabilityStatement.implementation` as `Equivalent`.

code:
  v: CapabilityStatement.implementation.description
display:
  v: description
target:
  code:
    v: CapabilityStatement.implementation.description
  display:
    v: CapabilityStatement.implementation.description
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.implementation.description` is mapped to FHIR R4 element `CapabilityStatement.implementation.description` as `Equivalent`.

code:
  v: CapabilityStatement.implementation.url
display:
  v: url
target:
  code:
    v: CapabilityStatement.implementation.url
  display:
    v: CapabilityStatement.implementation.url
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.implementation.url` is mapped to FHIR R4 element `CapabilityStatement.implementation.url` as `Equivalent`.

code:
  v: CapabilityStatement.fhirVersion
display:
  v: fhirVersion
target:
  code:
    v: CapabilityStatement.fhirVersion
  display:
    v: CapabilityStatement.fhirVersion
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.fhirVersion` is mapped to FHIR R4 element `CapabilityStatement.fhirVersion` as `SourceIsNarrowerThanTarget`.

code:
  v: CapabilityStatement.format
display:
  v: format
target:
  code:
    v: CapabilityStatement.format
  display:
    v: CapabilityStatement.format
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.format` is mapped to FHIR R4 element `CapabilityStatement.format` as `Equivalent`. "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:
  v: CapabilityStatement.patchFormat
display:
  v: patchFormat
target:
  code:
    v: CapabilityStatement.patchFormat
  display:
    v: CapabilityStatement.patchFormat
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.patchFormat` is mapped to FHIR R4 element `CapabilityStatement.patchFormat` as `Equivalent`. At 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:
  v: CapabilityStatement.implementationGuide
display:
  v: implementationGuide
target:
  code:
    v: CapabilityStatement.implementationGuide
  display:
    v: CapabilityStatement.implementationGuide
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.implementationGuide` is mapped to FHIR R4 element `CapabilityStatement.implementationGuide` as `Equivalent`.

code:
  v: CapabilityStatement.profile
display:
  v: profile
target:
  code:
    v: CapabilityStatement.rest.resource.supportedProfile
  display:
    v: CapabilityStatement.rest.resource.supportedProfile
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.profile` do not cover the following types based on type expansion: display, identifier, reference. Supported 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:
  v: CapabilityStatement.rest
display:
  v: rest
target:
  code:
    v: CapabilityStatement.rest
  display:
    v: CapabilityStatement.rest
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest` is mapped to FHIR R4 element `CapabilityStatement.rest` as `Equivalent`. Multiple repetitions allow definition of both client and/or server behaviors or possibly behaviors under different configuration settings (for software or requirements statements).

code:
  v: CapabilityStatement.rest.mode
display:
  v: mode
target:
  code:
    v: CapabilityStatement.rest.mode
  display:
    v: CapabilityStatement.rest.mode
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.mode` is mapped to FHIR R4 element `CapabilityStatement.rest.mode` as `Equivalent`.

code:
  v: CapabilityStatement.rest.documentation
display:
  v: documentation
target:
  code:
    v: CapabilityStatement.rest.documentation
  display:
    v: CapabilityStatement.rest.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.documentation` as `Equivalent`.

code:
  v: CapabilityStatement.rest.security
display:
  v: security
target:
  code:
    v: CapabilityStatement.rest.security
  display:
    v: CapabilityStatement.rest.security
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.security` is mapped to FHIR R4 element `CapabilityStatement.rest.security` as `Equivalent`.

code:
  v: CapabilityStatement.rest.security.cors
display:
  v: cors
target:
  code:
    v: CapabilityStatement.rest.security.cors
  display:
    v: CapabilityStatement.rest.security.cors
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.security.cors` is mapped to FHIR R4 element `CapabilityStatement.rest.security.cors` as `Equivalent`. The easiest CORS headers to add are Access-Control-Allow-Origin: * & Access-Control-Request-Method: GET, POST, PUT, DELETE. All servers SHOULD support CORS.

code:
  v: CapabilityStatement.rest.security.service
display:
  v: service
target:
  code:
    v: CapabilityStatement.rest.security.service
  display:
    v: CapabilityStatement.rest.security.service
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.security.service` is mapped to FHIR R4 element `CapabilityStatement.rest.security.service` as `Equivalent`.

code:
  v: CapabilityStatement.rest.security.description
display:
  v: description
target:
  code:
    v: CapabilityStatement.rest.security.description
  display:
    v: CapabilityStatement.rest.security.description
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.security.description` is mapped to FHIR R4 element `CapabilityStatement.rest.security.description` as `Equivalent`.

code:
  v: CapabilityStatement.rest.resource
display:
  v: resource
target:
  code:
    v: CapabilityStatement.rest.resource
  display:
    v: CapabilityStatement.rest.resource
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.resource` is mapped to FHIR R4 element `CapabilityStatement.rest.resource` as `Equivalent`. Max of one repetition per resource type.

code:
  v: CapabilityStatement.rest.resource.type
display:
  v: type
target:
  code:
    v: CapabilityStatement.rest.resource.type
  display:
    v: CapabilityStatement.rest.resource.type
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.type` as `SourceIsNarrowerThanTarget`. The mappings for `CapabilityStatement.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target.

code:
  v: CapabilityStatement.rest.resource.profile
display:
  v: profile
target:
  code:
    v: CapabilityStatement.rest.resource.profile
  display:
    v: CapabilityStatement.rest.resource.profile
  equivalence:
    v: relatedto
  comment:
    v: Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, reference. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system.
target:
  code:
    v: CapabilityStatement.rest.resource.supportedProfile
  display:
    v: CapabilityStatement.rest.resource.supportedProfile
  equivalence:
    v: relatedto
  comment:
    v: Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, reference. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system.

code:
  v: CapabilityStatement.rest.resource.documentation
display:
  v: documentation
target:
  code:
    v: CapabilityStatement.rest.resource.documentation
  display:
    v: CapabilityStatement.rest.resource.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.documentation` as `Equivalent`.

code:
  v: CapabilityStatement.rest.resource.interaction
display:
  v: interaction
target:
  code:
    v: CapabilityStatement.rest.resource.interaction
  display:
    v: CapabilityStatement.rest.resource.interaction
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.resource.interaction` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction` as `Equivalent`.

code:
  v: CapabilityStatement.rest.resource.interaction.code
display:
  v: code
target:
  code:
    v: CapabilityStatement.rest.resource.interaction.code
  display:
    v: CapabilityStatement.rest.resource.interaction.code
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.interaction.code` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction.code` as `Equivalent`.

code:
  v: CapabilityStatement.rest.resource.interaction.documentation
display:
  v: documentation
target:
  code:
    v: CapabilityStatement.rest.resource.interaction.documentation
  display:
    v: CapabilityStatement.rest.resource.interaction.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.interaction.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`.

code:
  v: CapabilityStatement.rest.resource.versioning
display:
  v: versioning
target:
  code:
    v: CapabilityStatement.rest.resource.versioning
  display:
    v: CapabilityStatement.rest.resource.versioning
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.versioning` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.versioning` as `Equivalent`. If a server supports versionIds correctly, it SHOULD support vread too, but is not required to do so.

code:
  v: CapabilityStatement.rest.resource.readHistory
display:
  v: readHistory
target:
  code:
    v: CapabilityStatement.rest.resource.readHistory
  display:
    v: CapabilityStatement.rest.resource.readHistory
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.readHistory` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.readHistory` as `Equivalent`. It is useful to support the vRead operation for current operations, even if past versions aren't available.

code:
  v: CapabilityStatement.rest.resource.updateCreate
display:
  v: updateCreate
target:
  code:
    v: CapabilityStatement.rest.resource.updateCreate
  display:
    v: CapabilityStatement.rest.resource.updateCreate
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.updateCreate` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.updateCreate` as `Equivalent`. Allowing 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:
  v: CapabilityStatement.rest.resource.conditionalCreate
display:
  v: conditionalCreate
target:
  code:
    v: CapabilityStatement.rest.resource.conditionalCreate
  display:
    v: CapabilityStatement.rest.resource.conditionalCreate
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.conditionalCreate` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.conditionalCreate` as `Equivalent`. Conditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2.

code:
  v: CapabilityStatement.rest.resource.conditionalRead
display:
  v: conditionalRead
target:
  code:
    v: CapabilityStatement.rest.resource.conditionalRead
  display:
    v: CapabilityStatement.rest.resource.conditionalRead
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.conditionalRead` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.conditionalRead` as `Equivalent`. Conditional Read is mainly appropriate for interface engine scripts converting from other formats, such as v2.

code:
  v: CapabilityStatement.rest.resource.conditionalUpdate
display:
  v: conditionalUpdate
target:
  code:
    v: CapabilityStatement.rest.resource.conditionalUpdate
  display:
    v: CapabilityStatement.rest.resource.conditionalUpdate
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.conditionalUpdate` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.conditionalUpdate` as `Equivalent`. Conditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2.

code:
  v: CapabilityStatement.rest.resource.conditionalDelete
display:
  v: conditionalDelete
target:
  code:
    v: CapabilityStatement.rest.resource.conditionalDelete
  display:
    v: CapabilityStatement.rest.resource.conditionalDelete
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.conditionalDelete` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.conditionalDelete` as `Equivalent`. Conditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2.

code:
  v: CapabilityStatement.rest.resource.referencePolicy
display:
  v: referencePolicy
target:
  code:
    v: CapabilityStatement.rest.resource.referencePolicy
  display:
    v: CapabilityStatement.rest.resource.referencePolicy
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.referencePolicy` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.referencePolicy` as `Equivalent`.

code:
  v: CapabilityStatement.rest.resource.searchInclude
display:
  v: searchInclude
target:
  code:
    v: CapabilityStatement.rest.resource.searchInclude
  display:
    v: CapabilityStatement.rest.resource.searchInclude
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchInclude` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`. If this list is empty, the server does not support includes.

code:
  v: CapabilityStatement.rest.resource.searchRevInclude
display:
  v: searchRevInclude
target:
  code:
    v: CapabilityStatement.rest.resource.searchRevInclude
  display:
    v: CapabilityStatement.rest.resource.searchRevInclude
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchRevInclude` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchRevInclude` as `Equivalent`. If this list is empty, the server does not support reverse includes.

code:
  v: CapabilityStatement.rest.resource.searchParam
display:
  v: searchParam
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam
  display:
    v: CapabilityStatement.rest.resource.searchParam
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam` as `Equivalent`.

code:
  v: CapabilityStatement.rest.resource.searchParam.name
display:
  v: name
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam.name
  display:
    v: CapabilityStatement.rest.resource.searchParam.name
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam.name` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.name` as `Equivalent`. Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined.

code:
  v: CapabilityStatement.rest.resource.searchParam.definition
display:
  v: definition
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam.definition
  display:
    v: CapabilityStatement.rest.resource.searchParam.definition
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam.definition` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.definition` as `Equivalent`. This 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:
  v: CapabilityStatement.rest.resource.searchParam.type
display:
  v: type
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam.type
  display:
    v: CapabilityStatement.rest.resource.searchParam.type
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.type` as `SourceIsNarrowerThanTarget`. The mappings for `CapabilityStatement.rest.resource.searchParam.type` do not allow expression of the necessary codes, per the bindings on the source and target. While 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:
  v: CapabilityStatement.rest.resource.searchParam.documentation
display:
  v: documentation
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam.documentation
  display:
    v: CapabilityStatement.rest.resource.searchParam.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`.

code:
  v: CapabilityStatement.rest.interaction
display:
  v: interaction
target:
  code:
    v: CapabilityStatement.rest.interaction
  display:
    v: CapabilityStatement.rest.interaction
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.interaction` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction` as `Equivalent`.

code:
  v: CapabilityStatement.rest.interaction.code
display:
  v: code
target:
  code:
    v: CapabilityStatement.rest.interaction.code
  display:
    v: CapabilityStatement.rest.interaction.code
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.interaction.code` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction.code` as `Equivalent`.

code:
  v: CapabilityStatement.rest.interaction.documentation
display:
  v: documentation
target:
  code:
    v: CapabilityStatement.rest.interaction.documentation
  display:
    v: CapabilityStatement.rest.interaction.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.interaction.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`.

code:
  v: CapabilityStatement.rest.searchParam
display:
  v: searchParam
target:
  code:
    v: CapabilityStatement.rest.searchParam
  display:
    v: CapabilityStatement.rest.searchParam
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.searchParam` is mapped to FHIR R4 element `CapabilityStatement.rest.searchParam` as `Equivalent`. Typically, the only search parameters supported for all searchse are those that apply to all resources - tags, profiles, text search etc.

code:
  v: CapabilityStatement.rest.operation
display:
  v: operation
target:
  code:
    v: CapabilityStatement.rest.operation
  display:
    v: CapabilityStatement.rest.operation
  equivalence:
    v: relatedto
  comment:
    v: Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.operation` as `Equivalent`.
target:
  code:
    v: CapabilityStatement.rest.resource.operation
  display:
    v: CapabilityStatement.rest.resource.operation
  equivalence:
    v: relatedto
  comment:
    v: Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.operation` as `Equivalent`.

code:
  v: CapabilityStatement.rest.operation.name
display:
  v: name
target:
  code:
    v: CapabilityStatement.rest.resource.operation.name
  display:
    v: CapabilityStatement.rest.resource.operation.name
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.operation.name` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.name` as `Equivalent`. The 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:
  v: CapabilityStatement.rest.operation.definition
display:
  v: definition
target:
  code:
    v: CapabilityStatement.rest.resource.operation.definition
  display:
    v: CapabilityStatement.rest.resource.operation.definition
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types based on type expansion: display, identifier, reference. This can be used to build an HTML form to invoke the operation, for instance.

code:
  v: CapabilityStatement.rest.compartment
display:
  v: compartment
target:
  code:
    v: CapabilityStatement.rest.compartment
  display:
    v: CapabilityStatement.rest.compartment
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.compartment` is mapped to FHIR R4 element `CapabilityStatement.rest.compartment` as `Equivalent`. At present, the only defined compartments are at [CompartmentDefinition](https://hl7.org/fhir/compartmentdefinition.html).

code:
  v: CapabilityStatement.messaging
display:
  v: messaging
target:
  code:
    v: CapabilityStatement.messaging
  display:
    v: CapabilityStatement.messaging
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.messaging` is mapped to FHIR R4 element `CapabilityStatement.messaging` as `Equivalent`. Multiple repetitions allow the documentation of multiple endpoints per solution.

code:
  v: CapabilityStatement.messaging.endpoint
display:
  v: endpoint
target:
  code:
    v: CapabilityStatement.messaging.endpoint
  display:
    v: CapabilityStatement.messaging.endpoint
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.messaging.endpoint` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint` as `Equivalent`.

code:
  v: CapabilityStatement.messaging.endpoint.protocol
display:
  v: protocol
target:
  code:
    v: CapabilityStatement.messaging.endpoint.protocol
  display:
    v: CapabilityStatement.messaging.endpoint.protocol
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.messaging.endpoint.protocol` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`.

code:
  v: CapabilityStatement.messaging.endpoint.address
display:
  v: address
target:
  code:
    v: CapabilityStatement.messaging.endpoint.address
  display:
    v: CapabilityStatement.messaging.endpoint.address
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.messaging.endpoint.address` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`.

code:
  v: CapabilityStatement.messaging.reliableCache
display:
  v: reliableCache
target:
  code:
    v: CapabilityStatement.messaging.reliableCache
  display:
    v: CapabilityStatement.messaging.reliableCache
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.messaging.reliableCache` is mapped to FHIR R4 element `CapabilityStatement.messaging.reliableCache` as `Equivalent`. If this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging.

code:
  v: CapabilityStatement.messaging.documentation
display:
  v: documentation
target:
  code:
    v: CapabilityStatement.messaging.documentation
  display:
    v: CapabilityStatement.messaging.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.messaging.documentation` is mapped to FHIR R4 element `CapabilityStatement.messaging.documentation` as `Equivalent`.

code:
  v: CapabilityStatement.messaging.supportedMessage
display:
  v: supportedMessage
target:
  code:
    v: CapabilityStatement.messaging.supportedMessage
  display:
    v: CapabilityStatement.messaging.supportedMessage
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.messaging.supportedMessage` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage` as `Equivalent`. This is a proposed alternative to the messaging.event structure.

code:
  v: CapabilityStatement.messaging.supportedMessage.mode
display:
  v: mode
target:
  code:
    v: CapabilityStatement.messaging.supportedMessage.mode
  display:
    v: CapabilityStatement.messaging.supportedMessage.mode
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.messaging.supportedMessage.mode` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage.mode` as `Equivalent`.

code:
  v: CapabilityStatement.messaging.supportedMessage.definition
display:
  v: definition
target:
  code:
    v: CapabilityStatement.messaging.supportedMessage.definition
  display:
    v: CapabilityStatement.messaging.supportedMessage.definition
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: display, identifier, reference.

code:
  v: CapabilityStatement.document
display:
  v: document
target:
  code:
    v: CapabilityStatement.document
  display:
    v: CapabilityStatement.document
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.document` is mapped to FHIR R4 element `CapabilityStatement.document` as `Equivalent`.

code:
  v: CapabilityStatement.document.mode
display:
  v: mode
target:
  code:
    v: CapabilityStatement.document.mode
  display:
    v: CapabilityStatement.document.mode
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.document.mode` is mapped to FHIR R4 element `CapabilityStatement.document.mode` as `Equivalent`.

code:
  v: CapabilityStatement.document.documentation
display:
  v: documentation
target:
  code:
    v: CapabilityStatement.document.documentation
  display:
    v: CapabilityStatement.document.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.document.documentation` is mapped to FHIR R4 element `CapabilityStatement.document.documentation` as `Equivalent`.

code:
  v: CapabilityStatement.document.profile
display:
  v: profile
target:
  code:
    v: CapabilityStatement.document.profile
  display:
    v: CapabilityStatement.document.profile
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.document.profile` is mapped to FHIR R4 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.document.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: display, identifier, reference. The first resource is the document resource.

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.acceptUnknown
  l: extension-CapabilityStatement.acceptUnknown
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.acceptUnknown
  display:
    v: acceptUnknown
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.acceptUnknown` has a context of CapabilityStatement based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.acceptUnknown` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Unknown 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:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.profile
  l: extension-CapabilityStatement.profile
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.profile
  display:
    v: profile
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `CapabilityStatement.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.profile` do not cover the following types based on type expansion: display, identifier, reference. Supported 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:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.security.certificate
  l: extension-CapabilityStatement.rest.security.certificate
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.rest.security.certificate
  display:
    v: certificate
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `CapabilityStatement.rest.security.certificate` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: CapabilityStatement.rest.security.certificate.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:type
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.rest.security.certificate.type` is part of an existing definition because parent element `CapabilityStatement.rest.security.certificate` requires a cross-version extension. Element `CapabilityStatement.rest.security.certificate.type` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: CapabilityStatement.rest.security.certificate.blob
  display:
    v: blob
  target:
    code:
      v: Extension.extension:blob
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.rest.security.certificate.blob` is part of an existing definition because parent element `CapabilityStatement.rest.security.certificate` requires a cross-version extension. Element `CapabilityStatement.rest.security.certificate.blob` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate.blob` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.resource.profile
  l: extension-CapabilityStatement.rest.resource.profile
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.rest.resource.profile
  display:
    v: profile
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, reference. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system.

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.operation.definition
  l: extension-CapabilityStatement.rest.operation.definition
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.rest.operation.definition
  display:
    v: definition
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types based on type expansion: display, identifier, reference. This can be used to build an HTML form to invoke the operation, for instance.

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.messaging.supportedMessage.definition
  l: extension-CapabilityStatement.messaging.supportedMessage.definition
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.messaging.supportedMessage.definition
  display:
    v: definition
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: display, identifier, reference.

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.messaging.event
  l: extension-CapabilityStatement.messaging.event
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.messaging.event
  display:
    v: event
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `CapabilityStatement.messaging.event` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The same event may be listed up to two times - once as sender and once as receiver.
element:
  code:
    v: CapabilityStatement.messaging.event.code
  display:
    v: code
  target:
    code:
      v: Extension.extension:code
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.messaging.event.code` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.code` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: CapabilityStatement.messaging.event.category
  display:
    v: category
  target:
    code:
      v: Extension.extension:category
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.messaging.event.category` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.category` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: CapabilityStatement.messaging.event.mode
  display:
    v: mode
  target:
    code:
      v: Extension.extension:mode
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.messaging.event.mode` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.mode` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: CapabilityStatement.messaging.event.focus
  display:
    v: focus
  target:
    code:
      v: Extension.extension:focus
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.messaging.event.focus` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.focus` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This SHALL be provided if the event type supports multiple different resource types.
element:
  code:
    v: CapabilityStatement.messaging.event.request
  display:
    v: request
  target:
    code:
      v: Extension.extension:request
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.messaging.event.request` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.request` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.request` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: CapabilityStatement.messaging.event.response
  display:
    v: response
  target:
    code:
      v: Extension.extension:response
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.messaging.event.response` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.response` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.response` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: CapabilityStatement.messaging.event.documentation
  display:
    v: documentation
  target:
    code:
      v: Extension.extension:documentation
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.messaging.event.documentation` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.documentation` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.documentation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.document.profile
  l: extension-CapabilityStatement.document.profile
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.document.profile
  display:
    v: profile
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.document.profile` is mapped to FHIR R4 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.document.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: display, identifier, reference. The first resource is the document resource.