Extensions for Using Data Elements from FHIR STU3 in FHIR R4B - Downloaded Version null See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: R3CapabilityStatementElementMapToR4B - XML Representation

Raw xml | Download

<ConceptMap xmlns="http://hl7.org/fhir">
  <id value="R3-CapabilityStatement-element-map-to-R4B"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R3-CapabilityStatement-element-map-to-R4B</b></p><a name="R3-CapabilityStatement-element-map-to-R4B"> </a><a name="hcR3-CapabilityStatement-element-map-to-R4B"> </a><p>Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="http://hl7.org/fhir/R4B/capabilitystatement.html">CapabilityStatementversion: 4.3.0)</a></p><table class="grid"><tr><td colspan="2"><b>Source Concept Details</b></td><td><b>Relationship</b></td><td colspan="2"><b>Target Concept Details</b></td><td><b>Comment</b></td></tr><tr><td colspan="2"><b>Codes</b> from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</td><td/><td colspan="2" title="http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.3.0"><b>Codes</b> from CapabilityStatement</td><td/></tr><tr><td style="border-right-width: 0px">CapabilityStatement.meta</td><td style="border-left-width: 0px">meta</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.meta</td><td style="border-left-width: 0px">CapabilityStatement.meta</td><td>Element `CapabilityStatement.meta` is mapped to FHIR R4B element `CapabilityStatement.meta` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.meta` do not cover the following types: Meta.
The mappings for `CapabilityStatement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.implicitRules</td><td style="border-left-width: 0px">implicitRules</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.implicitRules</td><td style="border-left-width: 0px">CapabilityStatement.implicitRules</td><td>Element `CapabilityStatement.implicitRules` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.language</td><td style="border-left-width: 0px">language</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.language</td><td style="border-left-width: 0px">CapabilityStatement.language</td><td>Element `CapabilityStatement.language` is mapped to FHIR R4B 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).</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.text</td><td style="border-left-width: 0px">text</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.text</td><td style="border-left-width: 0px">CapabilityStatement.text</td><td>Element `CapabilityStatement.text` is mapped to FHIR R4B element `CapabilityStatement.text` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.text` do not cover the following types: Narrative.
The mappings for `CapabilityStatement.text` do not cover the following types based on type expansion: div, status.
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 &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded in formation is added later.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.contained</td><td style="border-left-width: 0px">contained</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.contained</td><td style="border-left-width: 0px">CapabilityStatement.contained</td><td>Element `CapabilityStatement.contained` is mapped to FHIR R4B element `CapabilityStatement.contained` as `SourceIsBroaderThanTarget`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.url</td><td style="border-left-width: 0px">url</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.url</td><td style="border-left-width: 0px">CapabilityStatement.url</td><td>Element `CapabilityStatement.url` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.version</td><td style="border-left-width: 0px">version</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.version</td><td style="border-left-width: 0px">CapabilityStatement.version</td><td>Element `CapabilityStatement.version` is mapped to FHIR R4B 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].</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.name</td><td style="border-left-width: 0px">name</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.name</td><td style="border-left-width: 0px">CapabilityStatement.name</td><td>Element `CapabilityStatement.name` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.title</td><td style="border-left-width: 0px">title</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.title</td><td style="border-left-width: 0px">CapabilityStatement.title</td><td>Element `CapabilityStatement.title` is mapped to FHIR R4B element `CapabilityStatement.title` as `Equivalent`.
This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.status</td><td style="border-left-width: 0px">status</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.status</td><td style="border-left-width: 0px">CapabilityStatement.status</td><td>Element `CapabilityStatement.status` is mapped to FHIR R4B element `CapabilityStatement.status` as `Equivalent`.
Allows filtering of capability statements that are appropriate for use vs. not.  
This is labeled as &quot;Is Modifier&quot; 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.experimental</td><td style="border-left-width: 0px">experimental</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.experimental</td><td style="border-left-width: 0px">CapabilityStatement.experimental</td><td>Element `CapabilityStatement.experimental` is mapped to FHIR R4B element `CapabilityStatement.experimental` as `Equivalent`.
Allows filtering of capability statement that are appropriate for use vs. not. This is labeled as &quot;Is Modifier&quot; because applications should not use an experimental capability statement in production.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.date</td><td style="border-left-width: 0px">date</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.date</td><td style="border-left-width: 0px">CapabilityStatement.date</td><td>Element `CapabilityStatement.date` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.publisher</td><td style="border-left-width: 0px">publisher</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.publisher</td><td style="border-left-width: 0px">CapabilityStatement.publisher</td><td>Element `CapabilityStatement.publisher` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.contact</td><td style="border-left-width: 0px">contact</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.contact</td><td style="border-left-width: 0px">CapabilityStatement.contact</td><td>Element `CapabilityStatement.contact` is mapped to FHIR R4B element `CapabilityStatement.contact` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.contact` do not cover the following types: ContactDetail.
The mappings for `CapabilityStatement.contact` do not cover the following types based on type expansion: name, telecom.
May be a web site, an email address, a telephone number, etc.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.description</td><td style="border-left-width: 0px">description</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.description</td><td style="border-left-width: 0px">CapabilityStatement.description</td><td>Element `CapabilityStatement.description` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.useContext</td><td style="border-left-width: 0px">useContext</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.useContext</td><td style="border-left-width: 0px">CapabilityStatement.useContext</td><td>Element `CapabilityStatement.useContext` is mapped to FHIR R4B element `CapabilityStatement.useContext` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.useContext` do not cover the following types: UsageContext.
The mappings for `CapabilityStatement.useContext` do not cover the following types based on type expansion: code, value[x].
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.jurisdiction</td><td style="border-left-width: 0px">jurisdiction</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.jurisdiction</td><td style="border-left-width: 0px">CapabilityStatement.jurisdiction</td><td>Element `CapabilityStatement.jurisdiction` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.purpose</td><td style="border-left-width: 0px">purpose</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.purpose</td><td style="border-left-width: 0px">CapabilityStatement.purpose</td><td>Element `CapabilityStatement.purpose` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.copyright</td><td style="border-left-width: 0px">copyright</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.copyright</td><td style="border-left-width: 0px">CapabilityStatement.copyright</td><td>Element `CapabilityStatement.copyright` is mapped to FHIR R4B element `CapabilityStatement.copyright` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.kind</td><td style="border-left-width: 0px">kind</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.kind</td><td style="border-left-width: 0px">CapabilityStatement.kind</td><td>Element `CapabilityStatement.kind` is mapped to FHIR R4B element `CapabilityStatement.kind` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.instantiates</td><td style="border-left-width: 0px">instantiates</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.instantiates</td><td style="border-left-width: 0px">CapabilityStatement.instantiates</td><td>Element `CapabilityStatement.instantiates` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.software</td><td style="border-left-width: 0px">software</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.software</td><td style="border-left-width: 0px">CapabilityStatement.software</td><td>Element `CapabilityStatement.software` is mapped to FHIR R4B element `CapabilityStatement.software` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.software.name</td><td style="border-left-width: 0px">name</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.software.name</td><td style="border-left-width: 0px">CapabilityStatement.software.name</td><td>Element `CapabilityStatement.software.name` is mapped to FHIR R4B element `CapabilityStatement.software.name` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.software.version</td><td style="border-left-width: 0px">version</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.software.version</td><td style="border-left-width: 0px">CapabilityStatement.software.version</td><td>Element `CapabilityStatement.software.version` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.software.releaseDate</td><td style="border-left-width: 0px">releaseDate</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.software.releaseDate</td><td style="border-left-width: 0px">CapabilityStatement.software.releaseDate</td><td>Element `CapabilityStatement.software.releaseDate` is mapped to FHIR R4B element `CapabilityStatement.software.releaseDate` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.implementation</td><td style="border-left-width: 0px">implementation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.implementation</td><td style="border-left-width: 0px">CapabilityStatement.implementation</td><td>Element `CapabilityStatement.implementation` is mapped to FHIR R4B element `CapabilityStatement.implementation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.implementation.description</td><td style="border-left-width: 0px">description</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.implementation.description</td><td style="border-left-width: 0px">CapabilityStatement.implementation.description</td><td>Element `CapabilityStatement.implementation.description` is mapped to FHIR R4B element `CapabilityStatement.implementation.description` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.implementation.url</td><td style="border-left-width: 0px">url</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.implementation.url</td><td style="border-left-width: 0px">CapabilityStatement.implementation.url</td><td>Element `CapabilityStatement.implementation.url` is mapped to FHIR R4B element `CapabilityStatement.implementation.url` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.fhirVersion</td><td style="border-left-width: 0px">fhirVersion</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.fhirVersion</td><td style="border-left-width: 0px">CapabilityStatement.fhirVersion</td><td>Element `CapabilityStatement.fhirVersion` is mapped to FHIR R4B element `CapabilityStatement.fhirVersion` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.format</td><td style="border-left-width: 0px">format</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.format</td><td style="border-left-width: 0px">CapabilityStatement.format</td><td>Element `CapabilityStatement.format` is mapped to FHIR R4B element `CapabilityStatement.format` as `Equivalent`.
&quot;xml&quot;, &quot;json&quot; and &quot;ttl&quot; are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.patchFormat</td><td style="border-left-width: 0px">patchFormat</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.patchFormat</td><td style="border-left-width: 0px">CapabilityStatement.patchFormat</td><td>Element `CapabilityStatement.patchFormat` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.implementationGuide</td><td style="border-left-width: 0px">implementationGuide</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.implementationGuide</td><td style="border-left-width: 0px">CapabilityStatement.implementationGuide</td><td>Element `CapabilityStatement.implementationGuide` is mapped to FHIR R4B element `CapabilityStatement.implementationGuide` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.profile</td><td style="border-left-width: 0px">profile</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.supportedProfile</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.supportedProfile</td><td>Element `CapabilityStatement.profile` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest</td><td style="border-left-width: 0px">rest</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest</td><td style="border-left-width: 0px">CapabilityStatement.rest</td><td>Element `CapabilityStatement.rest` is mapped to FHIR R4B 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).</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.mode</td><td style="border-left-width: 0px">mode</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.mode</td><td style="border-left-width: 0px">CapabilityStatement.rest.mode</td><td>Element `CapabilityStatement.rest.mode` is mapped to FHIR R4B element `CapabilityStatement.rest.mode` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.documentation</td><td style="border-left-width: 0px">documentation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.documentation</td><td style="border-left-width: 0px">CapabilityStatement.rest.documentation</td><td>Element `CapabilityStatement.rest.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.documentation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.security</td><td style="border-left-width: 0px">security</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.security</td><td style="border-left-width: 0px">CapabilityStatement.rest.security</td><td>Element `CapabilityStatement.rest.security` is mapped to FHIR R4B element `CapabilityStatement.rest.security` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.security.cors</td><td style="border-left-width: 0px">cors</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.security.cors</td><td style="border-left-width: 0px">CapabilityStatement.rest.security.cors</td><td>Element `CapabilityStatement.rest.security.cors` is mapped to FHIR R4B element `CapabilityStatement.rest.security.cors` as `Equivalent`.
The easiest CORS headers to add are Access-Control-Allow-Origin: * &amp; Access-Control-Request-Method: GET, POST, PUT, DELETE. All servers SHOULD support CORS.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.security.service</td><td style="border-left-width: 0px">service</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.security.service</td><td style="border-left-width: 0px">CapabilityStatement.rest.security.service</td><td>Element `CapabilityStatement.rest.security.service` is mapped to FHIR R4B element `CapabilityStatement.rest.security.service` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.security.description</td><td style="border-left-width: 0px">description</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.security.description</td><td style="border-left-width: 0px">CapabilityStatement.rest.security.description</td><td>Element `CapabilityStatement.rest.security.description` is mapped to FHIR R4B element `CapabilityStatement.rest.security.description` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource</td><td style="border-left-width: 0px">resource</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource</td><td>Element `CapabilityStatement.rest.resource` is mapped to FHIR R4B element `CapabilityStatement.rest.resource` as `Equivalent`.
Max of one repetition per resource type.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.type</td><td style="border-left-width: 0px">type</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.type</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.type</td><td>Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.type` as `RelatedTo`.
The mappings for `CapabilityStatement.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target.</td></tr><tr><td style="border-right-width: 0px; border-bottom-style: none">CapabilityStatement.rest.resource.profile</td><td style="border-left-width: 0px; border-bottom-style: none">profile</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.profile</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.profile</td><td>Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px; border-top-style: none"/><td style="border-top-style: none; border-left-width: 0px"/><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.supportedProfile</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.supportedProfile</td><td>Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.documentation</td><td style="border-left-width: 0px">documentation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.documentation</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.documentation</td><td>Element `CapabilityStatement.rest.resource.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.documentation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.interaction</td><td style="border-left-width: 0px">interaction</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.interaction</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.interaction</td><td>Element `CapabilityStatement.rest.resource.interaction` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.interaction` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.interaction.code</td><td style="border-left-width: 0px">code</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.interaction.code</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.interaction.code</td><td>Element `CapabilityStatement.rest.resource.interaction.code` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.interaction.code` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.interaction.documentation</td><td style="border-left-width: 0px">documentation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.interaction.documentation</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.interaction.documentation</td><td>Element `CapabilityStatement.rest.resource.interaction.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.versioning</td><td style="border-left-width: 0px">versioning</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.versioning</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.versioning</td><td>Element `CapabilityStatement.rest.resource.versioning` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.readHistory</td><td style="border-left-width: 0px">readHistory</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.readHistory</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.readHistory</td><td>Element `CapabilityStatement.rest.resource.readHistory` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.updateCreate</td><td style="border-left-width: 0px">updateCreate</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.updateCreate</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.updateCreate</td><td>Element `CapabilityStatement.rest.resource.updateCreate` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.conditionalCreate</td><td style="border-left-width: 0px">conditionalCreate</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.conditionalCreate</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.conditionalCreate</td><td>Element `CapabilityStatement.rest.resource.conditionalCreate` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.conditionalCreate` as `Equivalent`.
Conditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.conditionalRead</td><td style="border-left-width: 0px">conditionalRead</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.conditionalRead</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.conditionalRead</td><td>Element `CapabilityStatement.rest.resource.conditionalRead` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.conditionalRead` as `Equivalent`.
Conditional Read is mainly appropriate for interface engine scripts converting from other formats, such as v2.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.conditionalUpdate</td><td style="border-left-width: 0px">conditionalUpdate</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.conditionalUpdate</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.conditionalUpdate</td><td>Element `CapabilityStatement.rest.resource.conditionalUpdate` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.conditionalUpdate` as `Equivalent`.
Conditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.conditionalDelete</td><td style="border-left-width: 0px">conditionalDelete</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.conditionalDelete</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.conditionalDelete</td><td>Element `CapabilityStatement.rest.resource.conditionalDelete` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.conditionalDelete` as `Equivalent`.
Conditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.referencePolicy</td><td style="border-left-width: 0px">referencePolicy</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.referencePolicy</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.referencePolicy</td><td>Element `CapabilityStatement.rest.resource.referencePolicy` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.referencePolicy` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchInclude</td><td style="border-left-width: 0px">searchInclude</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchInclude</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.searchInclude</td><td>Element `CapabilityStatement.rest.resource.searchInclude` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`.
If this list is empty, the server does not support includes.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchRevInclude</td><td style="border-left-width: 0px">searchRevInclude</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchRevInclude</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.searchRevInclude</td><td>Element `CapabilityStatement.rest.resource.searchRevInclude` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchRevInclude` as `Equivalent`.
If this list is empty, the server does not support reverse includes.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam</td><td style="border-left-width: 0px">searchParam</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.searchParam</td><td>Element `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchParam` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam.name</td><td style="border-left-width: 0px">name</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam.name</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.searchParam.name</td><td>Element `CapabilityStatement.rest.resource.searchParam.name` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchParam.name` as `Equivalent`.
Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam.definition</td><td style="border-left-width: 0px">definition</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam.definition</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.searchParam.definition</td><td>Element `CapabilityStatement.rest.resource.searchParam.definition` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam.type</td><td style="border-left-width: 0px">type</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam.type</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.searchParam.type</td><td>Element `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam.documentation</td><td style="border-left-width: 0px">documentation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.searchParam.documentation</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.searchParam.documentation</td><td>Element `CapabilityStatement.rest.resource.searchParam.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.interaction</td><td style="border-left-width: 0px">interaction</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.interaction</td><td style="border-left-width: 0px">CapabilityStatement.rest.interaction</td><td>Element `CapabilityStatement.rest.interaction` is mapped to FHIR R4B element `CapabilityStatement.rest.interaction` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.interaction.code</td><td style="border-left-width: 0px">code</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.interaction.code</td><td style="border-left-width: 0px">CapabilityStatement.rest.interaction.code</td><td>Element `CapabilityStatement.rest.interaction.code` is mapped to FHIR R4B element `CapabilityStatement.rest.interaction.code` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.interaction.documentation</td><td style="border-left-width: 0px">documentation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.interaction.documentation</td><td style="border-left-width: 0px">CapabilityStatement.rest.interaction.documentation</td><td>Element `CapabilityStatement.rest.interaction.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.searchParam</td><td style="border-left-width: 0px">searchParam</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.searchParam</td><td style="border-left-width: 0px">CapabilityStatement.rest.searchParam</td><td>Element `CapabilityStatement.rest.searchParam` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px; border-bottom-style: none">CapabilityStatement.rest.operation</td><td style="border-left-width: 0px; border-bottom-style: none">operation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.operation</td><td style="border-left-width: 0px">CapabilityStatement.rest.operation</td><td>Element `CapabilityStatement.rest.operation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.operation` is mapped to FHIR R4B element `CapabilityStatement.rest.operation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px; border-top-style: none"/><td style="border-top-style: none; border-left-width: 0px"/><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.operation</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.operation</td><td>Element `CapabilityStatement.rest.operation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.operation` is mapped to FHIR R4B element `CapabilityStatement.rest.operation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.operation.name</td><td style="border-left-width: 0px">name</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.operation.name</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.operation.name</td><td>Element `CapabilityStatement.rest.operation.name` is mapped to FHIR R4B 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 &quot;$&quot; portion that is always included in the URL.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.operation.definition</td><td style="border-left-width: 0px">definition</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.resource.operation.definition</td><td style="border-left-width: 0px">CapabilityStatement.rest.resource.operation.definition</td><td>Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.rest.compartment</td><td style="border-left-width: 0px">compartment</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.rest.compartment</td><td style="border-left-width: 0px">CapabilityStatement.rest.compartment</td><td>Element `CapabilityStatement.rest.compartment` is mapped to FHIR R4B element `CapabilityStatement.rest.compartment` as `Equivalent`.
At present, the only defined compartments are at [CompartmentDefinition](https://hl7.org/fhir/compartmentdefinition.html).</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging</td><td style="border-left-width: 0px">messaging</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging</td><td style="border-left-width: 0px">CapabilityStatement.messaging</td><td>Element `CapabilityStatement.messaging` is mapped to FHIR R4B element `CapabilityStatement.messaging` as `Equivalent`.
Multiple repetitions allow the documentation of multiple endpoints per solution.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging.endpoint</td><td style="border-left-width: 0px">endpoint</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging.endpoint</td><td style="border-left-width: 0px">CapabilityStatement.messaging.endpoint</td><td>Element `CapabilityStatement.messaging.endpoint` is mapped to FHIR R4B element `CapabilityStatement.messaging.endpoint` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging.endpoint.protocol</td><td style="border-left-width: 0px">protocol</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging.endpoint.protocol</td><td style="border-left-width: 0px">CapabilityStatement.messaging.endpoint.protocol</td><td>Element `CapabilityStatement.messaging.endpoint.protocol` is mapped to FHIR R4B element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging.endpoint.address</td><td style="border-left-width: 0px">address</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging.endpoint.address</td><td style="border-left-width: 0px">CapabilityStatement.messaging.endpoint.address</td><td>Element `CapabilityStatement.messaging.endpoint.address` is mapped to FHIR R4B element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging.reliableCache</td><td style="border-left-width: 0px">reliableCache</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging.reliableCache</td><td style="border-left-width: 0px">CapabilityStatement.messaging.reliableCache</td><td>Element `CapabilityStatement.messaging.reliableCache` is mapped to FHIR R4B element `CapabilityStatement.messaging.reliableCache` as `Equivalent`.
If this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging.documentation</td><td style="border-left-width: 0px">documentation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging.documentation</td><td style="border-left-width: 0px">CapabilityStatement.messaging.documentation</td><td>Element `CapabilityStatement.messaging.documentation` is mapped to FHIR R4B element `CapabilityStatement.messaging.documentation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging.supportedMessage</td><td style="border-left-width: 0px">supportedMessage</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging.supportedMessage</td><td style="border-left-width: 0px">CapabilityStatement.messaging.supportedMessage</td><td>Element `CapabilityStatement.messaging.supportedMessage` is mapped to FHIR R4B element `CapabilityStatement.messaging.supportedMessage` as `Equivalent`.
This is a proposed alternative to the messaging.event structure.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging.supportedMessage.mode</td><td style="border-left-width: 0px">mode</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging.supportedMessage.mode</td><td style="border-left-width: 0px">CapabilityStatement.messaging.supportedMessage.mode</td><td>Element `CapabilityStatement.messaging.supportedMessage.mode` is mapped to FHIR R4B element `CapabilityStatement.messaging.supportedMessage.mode` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.messaging.supportedMessage.definition</td><td style="border-left-width: 0px">definition</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.messaging.supportedMessage.definition</td><td style="border-left-width: 0px">CapabilityStatement.messaging.supportedMessage.definition</td><td>Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4B 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.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.document</td><td style="border-left-width: 0px">document</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.document</td><td style="border-left-width: 0px">CapabilityStatement.document</td><td>Element `CapabilityStatement.document` is mapped to FHIR R4B element `CapabilityStatement.document` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.document.mode</td><td style="border-left-width: 0px">mode</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.document.mode</td><td style="border-left-width: 0px">CapabilityStatement.document.mode</td><td>Element `CapabilityStatement.document.mode` is mapped to FHIR R4B element `CapabilityStatement.document.mode` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.document.documentation</td><td style="border-left-width: 0px">documentation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">CapabilityStatement.document.documentation</td><td style="border-left-width: 0px">CapabilityStatement.document.documentation</td><td>Element `CapabilityStatement.document.documentation` is mapped to FHIR R4B element `CapabilityStatement.document.documentation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">CapabilityStatement.document.profile</td><td style="border-left-width: 0px">profile</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">CapabilityStatement.document.profile</td><td style="border-left-width: 0px">CapabilityStatement.document.profile</td><td>Element `CapabilityStatement.document.profile` is mapped to FHIR R4B 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.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.meta.html">STU3: meta additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: meta additional types)</td><td>Element `CapabilityStatement.meta` is mapped to FHIR R4B element `CapabilityStatement.meta` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.meta` do not cover the following types: Meta.
The mappings for `CapabilityStatement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.text.html">STU3: text additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: text additional types)</td><td>Element `CapabilityStatement.text` is mapped to FHIR R4B element `CapabilityStatement.text` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.text` do not cover the following types: Narrative.
The mappings for `CapabilityStatement.text` do not cover the following types based on type expansion: div, status.
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 &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded in formation is added later.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.contact.html">STU3: contact additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.contact (contact)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: contact additional types)</td><td>Element `CapabilityStatement.contact` is mapped to FHIR R4B element `CapabilityStatement.contact` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.contact` do not cover the following types: ContactDetail.
The mappings for `CapabilityStatement.contact` do not cover the following types based on type expansion: name, telecom.
May be a web site, an email address, a telephone number, etc.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.useContext.html">STU3: Context the content is intended to support additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.useContext (useContext)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Context the content is intended to support additional types)</td><td>Element `CapabilityStatement.useContext` is mapped to FHIR R4B element `CapabilityStatement.useContext` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.useContext` do not cover the following types: UsageContext.
The mappings for `CapabilityStatement.useContext` do not cover the following types based on type expansion: code, value[x].
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.acceptUnknown.html">STU3: no | extensions | elements | both (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.acceptUnknown (acceptUnknown)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: no | extensions | elements | both (new))</td><td>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 R4B. 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.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.profile.html">STU3: profile additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.profile (profile)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (STU3: profile additional types)</td><td>Element `CapabilityStatement.profile` is mapped to FHIR R4B 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.</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.res.sec.certificate.html">STU3: Certificates associated with security profiles (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.rest.security.certificate (certificate)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (STU3: Certificates associated with security profiles (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>CapabilityStatement.rest.security.certificate.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:type (STU3: Mime type for certificates (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>CapabilityStatement.rest.security.certificate.blob (blob)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:blob (STU3: Actual certificate (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.res.res.type.html">STU3: type additional codesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.rest.resource.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: type additional codes)</td><td>Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.type` as `RelatedTo`.
The mappings for `CapabilityStatement.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target.</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.res.res.profile.html">STU3: Base System profile for all uses of resource additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.rest.resource.profile (profile)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (STU3: Base System profile for all uses of resource additional types)</td><td>Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B 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.</td></tr></table><hr/><p><b>Group 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.res.ope.definition.html">STU3: definition additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.rest.operation.definition (definition)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (STU3: definition additional types)</td><td>Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4B 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.</td></tr></table><hr/><p><b>Group 12 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.mes.sup.definition.html">STU3: definition additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.messaging.supportedMessage.definition (definition)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: definition additional types)</td><td>Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4B 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.</td></tr></table><hr/><p><b>Group 13 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.mes.event.html">STU3: Declare support for this event (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.messaging.event (event)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (STU3: Declare support for this event (new))</td><td>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 R4B. 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.</td></tr><tr><td>CapabilityStatement.messaging.event.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:code (STU3: Event type (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>CapabilityStatement.messaging.event.category (category)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:category (STU3: Consequence | Currency | Notification (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>CapabilityStatement.messaging.event.mode (mode)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:mode (STU3: sender | receiver (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>CapabilityStatement.messaging.event.focus (focus)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:focus (STU3: Resource that's focus of message (new))</td><td>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 R4B. 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.</td></tr><tr><td>CapabilityStatement.messaging.event.request (request)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:request (STU3: Profile that describes the request (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>CapabilityStatement.messaging.event.response (response)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:response (STU3: Profile that describes the response (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>CapabilityStatement.messaging.event.documentation (documentation)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:documentation (STU3: Endpoint-specific event documentation (new))</td><td>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 R4B. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 14 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2</code> to <a href="StructureDefinition-ext-R3-CapabilityStatement.doc.profile.html">STU3: Constraint on a resource used in the document additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>CapabilityStatement.document.profile (profile)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Constraint on a resource used in the document additional types)</td><td>Element `CapabilityStatement.document.profile` is mapped to FHIR R4B 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.</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4b"/>
      </extension>
    </valueInteger>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4b"/>
      </extension>
    </valueCode>
  </extension>
  <url
       value="http://hl7.org/fhir/uv/xver/ConceptMap/R3-CapabilityStatement-element-map-to-R4B"/>
  <version value="0.1.0"/>
  <name value="R3CapabilityStatementElementMapToR4B"/>
  <title
         value="Cross-version mapping for FHIR STU3 CapabilityStatement to FHIR R4B CapabilityStatement"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-03-17T16:04:10.4332097-05:00"/>
  <contact>
    <name value="FHIR Infrastructure"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <description
               value="This ConceptMap represents cross-version mappings for elements from a FHIR STU3 CapabilityStatement to FHIR R4B."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <sourceCanonical value="http://hl7.org/fhir/3.0"/>
  <targetUri value="http://hl7.org/fhir/4.3"/>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <targetVersion value="4.3.0"/>
    <element>
      <code value="CapabilityStatement.meta"/>
      <display value="meta"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.meta"/>
        <display value="CapabilityStatement.meta"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.meta` is mapped to FHIR R4B element `CapabilityStatement.meta` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.meta` do not cover the following types: Meta.
The mappings for `CapabilityStatement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.implicitRules"/>
      <display value="implicitRules"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.implicitRules"/>
        <display value="CapabilityStatement.implicitRules"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.implicitRules` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.language"/>
      <display value="language"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.language"/>
        <display value="CapabilityStatement.language"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.language` is mapped to FHIR R4B 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)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.text"/>
      <display value="text"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.text"/>
        <display value="CapabilityStatement.text"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.text` is mapped to FHIR R4B element `CapabilityStatement.text` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.text` do not cover the following types: Narrative.
The mappings for `CapabilityStatement.text` do not cover the following types based on type expansion: div, status.
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 &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded in formation is added later."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.contained"/>
      <display value="contained"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.contained"/>
        <display value="CapabilityStatement.contained"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.contained` is mapped to FHIR R4B element `CapabilityStatement.contained` as `SourceIsBroaderThanTarget`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.url"/>
      <display value="url"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.url"/>
        <display value="CapabilityStatement.url"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.url` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.version"/>
      <display value="version"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.version"/>
        <display value="CapabilityStatement.version"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.version` is mapped to FHIR R4B 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]."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.name"/>
      <display value="name"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.name"/>
        <display value="CapabilityStatement.name"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.name` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.title"/>
      <display value="title"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.title"/>
        <display value="CapabilityStatement.title"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.title` is mapped to FHIR R4B element `CapabilityStatement.title` as `Equivalent`.
This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.status"/>
      <display value="status"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.status"/>
        <display value="CapabilityStatement.status"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.status` is mapped to FHIR R4B element `CapabilityStatement.status` as `Equivalent`.
Allows filtering of capability statements that are appropriate for use vs. not.  
This is labeled as &quot;Is Modifier&quot; 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.experimental"/>
      <display value="experimental"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.experimental"/>
        <display value="CapabilityStatement.experimental"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.experimental` is mapped to FHIR R4B element `CapabilityStatement.experimental` as `Equivalent`.
Allows filtering of capability statement that are appropriate for use vs. not. This is labeled as &quot;Is Modifier&quot; because applications should not use an experimental capability statement in production."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.date"/>
      <display value="date"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.date"/>
        <display value="CapabilityStatement.date"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.date` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.publisher"/>
      <display value="publisher"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.publisher"/>
        <display value="CapabilityStatement.publisher"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.publisher` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.contact"/>
      <display value="contact"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.contact"/>
        <display value="CapabilityStatement.contact"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.contact` is mapped to FHIR R4B element `CapabilityStatement.contact` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.contact` do not cover the following types: ContactDetail.
The mappings for `CapabilityStatement.contact` do not cover the following types based on type expansion: name, telecom.
May be a web site, an email address, a telephone number, etc."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.description"/>
      <display value="description"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.description"/>
        <display value="CapabilityStatement.description"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.description` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.useContext"/>
      <display value="useContext"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.useContext"/>
        <display value="CapabilityStatement.useContext"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.useContext` is mapped to FHIR R4B element `CapabilityStatement.useContext` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.useContext` do not cover the following types: UsageContext.
The mappings for `CapabilityStatement.useContext` do not cover the following types based on type expansion: code, value[x].
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.jurisdiction"/>
      <display value="jurisdiction"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.jurisdiction"/>
        <display value="CapabilityStatement.jurisdiction"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.jurisdiction` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.purpose"/>
      <display value="purpose"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.purpose"/>
        <display value="CapabilityStatement.purpose"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.purpose` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.copyright"/>
      <display value="copyright"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.copyright"/>
        <display value="CapabilityStatement.copyright"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.copyright` is mapped to FHIR R4B element `CapabilityStatement.copyright` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.kind"/>
      <display value="kind"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.kind"/>
        <display value="CapabilityStatement.kind"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.kind` is mapped to FHIR R4B element `CapabilityStatement.kind` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.instantiates"/>
      <display value="instantiates"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.instantiates"/>
        <display value="CapabilityStatement.instantiates"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.instantiates` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.software"/>
      <display value="software"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.software"/>
        <display value="CapabilityStatement.software"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.software` is mapped to FHIR R4B element `CapabilityStatement.software` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.software.name"/>
      <display value="name"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.software.name"/>
        <display value="CapabilityStatement.software.name"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.software.name` is mapped to FHIR R4B element `CapabilityStatement.software.name` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.software.version"/>
      <display value="version"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.software.version"/>
        <display value="CapabilityStatement.software.version"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.software.version` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.software.releaseDate"/>
      <display value="releaseDate"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.software.releaseDate"/>
        <display value="CapabilityStatement.software.releaseDate"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.software.releaseDate` is mapped to FHIR R4B element `CapabilityStatement.software.releaseDate` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.implementation"/>
      <display value="implementation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.implementation"/>
        <display value="CapabilityStatement.implementation"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.implementation` is mapped to FHIR R4B element `CapabilityStatement.implementation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.implementation.description"/>
      <display value="description"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.implementation.description"/>
        <display value="CapabilityStatement.implementation.description"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.implementation.description` is mapped to FHIR R4B element `CapabilityStatement.implementation.description` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.implementation.url"/>
      <display value="url"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.implementation.url"/>
        <display value="CapabilityStatement.implementation.url"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.implementation.url` is mapped to FHIR R4B element `CapabilityStatement.implementation.url` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.fhirVersion"/>
      <display value="fhirVersion"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.fhirVersion"/>
        <display value="CapabilityStatement.fhirVersion"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.fhirVersion` is mapped to FHIR R4B element `CapabilityStatement.fhirVersion` as `SourceIsNarrowerThanTarget`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.format"/>
      <display value="format"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.format"/>
        <display value="CapabilityStatement.format"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.format` is mapped to FHIR R4B element `CapabilityStatement.format` as `Equivalent`.
&quot;xml&quot;, &quot;json&quot; and &quot;ttl&quot; are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.patchFormat"/>
      <display value="patchFormat"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.patchFormat"/>
        <display value="CapabilityStatement.patchFormat"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.patchFormat` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.implementationGuide"/>
      <display value="implementationGuide"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.implementationGuide"/>
        <display value="CapabilityStatement.implementationGuide"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.implementationGuide` is mapped to FHIR R4B element `CapabilityStatement.implementationGuide` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.profile"/>
      <display value="profile"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.supportedProfile"/>
        <display value="CapabilityStatement.rest.resource.supportedProfile"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.profile` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest"/>
      <display value="rest"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest"/>
        <display value="CapabilityStatement.rest"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest` is mapped to FHIR R4B 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)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.mode"/>
      <display value="mode"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.mode"/>
        <display value="CapabilityStatement.rest.mode"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.mode` is mapped to FHIR R4B element `CapabilityStatement.rest.mode` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.documentation"/>
      <display value="documentation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.documentation"/>
        <display value="CapabilityStatement.rest.documentation"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.documentation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.security"/>
      <display value="security"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.security"/>
        <display value="CapabilityStatement.rest.security"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.security` is mapped to FHIR R4B element `CapabilityStatement.rest.security` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.security.cors"/>
      <display value="cors"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.security.cors"/>
        <display value="CapabilityStatement.rest.security.cors"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.security.cors` is mapped to FHIR R4B element `CapabilityStatement.rest.security.cors` as `Equivalent`.
The easiest CORS headers to add are Access-Control-Allow-Origin: * &amp; Access-Control-Request-Method: GET, POST, PUT, DELETE. All servers SHOULD support CORS."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.security.service"/>
      <display value="service"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.security.service"/>
        <display value="CapabilityStatement.rest.security.service"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.security.service` is mapped to FHIR R4B element `CapabilityStatement.rest.security.service` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.security.description"/>
      <display value="description"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.security.description"/>
        <display value="CapabilityStatement.rest.security.description"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.security.description` is mapped to FHIR R4B element `CapabilityStatement.rest.security.description` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource"/>
      <display value="resource"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource"/>
        <display value="CapabilityStatement.rest.resource"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource` is mapped to FHIR R4B element `CapabilityStatement.rest.resource` as `Equivalent`.
Max of one repetition per resource type."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.type"/>
      <display value="type"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.type"/>
        <display value="CapabilityStatement.rest.resource.type"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.type` as `RelatedTo`.
The mappings for `CapabilityStatement.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.profile"/>
      <display value="profile"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="relatedto"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.profile"/>
        <display value="CapabilityStatement.rest.resource.profile"/>
        <equivalence value="relatedto"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B 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>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="relatedto"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.supportedProfile"/>
        <display value="CapabilityStatement.rest.resource.supportedProfile"/>
        <equivalence value="relatedto"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B 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>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.documentation"/>
      <display value="documentation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.documentation"/>
        <display value="CapabilityStatement.rest.resource.documentation"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.documentation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.interaction"/>
      <display value="interaction"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.interaction"/>
        <display value="CapabilityStatement.rest.resource.interaction"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.interaction` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.interaction` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.interaction.code"/>
      <display value="code"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.interaction.code"/>
        <display value="CapabilityStatement.rest.resource.interaction.code"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.interaction.code` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.interaction.code` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code
            value="CapabilityStatement.rest.resource.interaction.documentation"/>
      <display value="documentation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code
              value="CapabilityStatement.rest.resource.interaction.documentation"/>
        <display
                 value="CapabilityStatement.rest.resource.interaction.documentation"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.interaction.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.versioning"/>
      <display value="versioning"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.versioning"/>
        <display value="CapabilityStatement.rest.resource.versioning"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.versioning` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.readHistory"/>
      <display value="readHistory"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.readHistory"/>
        <display value="CapabilityStatement.rest.resource.readHistory"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.readHistory` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.updateCreate"/>
      <display value="updateCreate"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.updateCreate"/>
        <display value="CapabilityStatement.rest.resource.updateCreate"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.updateCreate` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.conditionalCreate"/>
      <display value="conditionalCreate"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.conditionalCreate"/>
        <display value="CapabilityStatement.rest.resource.conditionalCreate"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.conditionalCreate` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.conditionalCreate` as `Equivalent`.
Conditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.conditionalRead"/>
      <display value="conditionalRead"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.conditionalRead"/>
        <display value="CapabilityStatement.rest.resource.conditionalRead"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.conditionalRead` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.conditionalRead` as `Equivalent`.
Conditional Read is mainly appropriate for interface engine scripts converting from other formats, such as v2."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.conditionalUpdate"/>
      <display value="conditionalUpdate"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.conditionalUpdate"/>
        <display value="CapabilityStatement.rest.resource.conditionalUpdate"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.conditionalUpdate` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.conditionalUpdate` as `Equivalent`.
Conditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.conditionalDelete"/>
      <display value="conditionalDelete"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.conditionalDelete"/>
        <display value="CapabilityStatement.rest.resource.conditionalDelete"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.conditionalDelete` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.conditionalDelete` as `Equivalent`.
Conditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.referencePolicy"/>
      <display value="referencePolicy"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.referencePolicy"/>
        <display value="CapabilityStatement.rest.resource.referencePolicy"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.referencePolicy` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.referencePolicy` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.searchInclude"/>
      <display value="searchInclude"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.searchInclude"/>
        <display value="CapabilityStatement.rest.resource.searchInclude"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.searchInclude` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`.
If this list is empty, the server does not support includes."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.searchRevInclude"/>
      <display value="searchRevInclude"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.searchRevInclude"/>
        <display value="CapabilityStatement.rest.resource.searchRevInclude"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.searchRevInclude` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchRevInclude` as `Equivalent`.
If this list is empty, the server does not support reverse includes."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.searchParam"/>
      <display value="searchParam"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.searchParam"/>
        <display value="CapabilityStatement.rest.resource.searchParam"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchParam` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.searchParam.name"/>
      <display value="name"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.searchParam.name"/>
        <display value="CapabilityStatement.rest.resource.searchParam.name"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.searchParam.name` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchParam.name` as `Equivalent`.
Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.searchParam.definition"/>
      <display value="definition"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code
              value="CapabilityStatement.rest.resource.searchParam.definition"/>
        <display
                 value="CapabilityStatement.rest.resource.searchParam.definition"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.searchParam.definition` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.resource.searchParam.type"/>
      <display value="type"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.searchParam.type"/>
        <display value="CapabilityStatement.rest.resource.searchParam.type"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code
            value="CapabilityStatement.rest.resource.searchParam.documentation"/>
      <display value="documentation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code
              value="CapabilityStatement.rest.resource.searchParam.documentation"/>
        <display
                 value="CapabilityStatement.rest.resource.searchParam.documentation"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.searchParam.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.interaction"/>
      <display value="interaction"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.interaction"/>
        <display value="CapabilityStatement.rest.interaction"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.interaction` is mapped to FHIR R4B element `CapabilityStatement.rest.interaction` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.interaction.code"/>
      <display value="code"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.interaction.code"/>
        <display value="CapabilityStatement.rest.interaction.code"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.interaction.code` is mapped to FHIR R4B element `CapabilityStatement.rest.interaction.code` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.interaction.documentation"/>
      <display value="documentation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.interaction.documentation"/>
        <display value="CapabilityStatement.rest.interaction.documentation"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.interaction.documentation` is mapped to FHIR R4B element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.searchParam"/>
      <display value="searchParam"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.searchParam"/>
        <display value="CapabilityStatement.rest.searchParam"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.searchParam` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.operation"/>
      <display value="operation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="relatedto"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.operation"/>
        <display value="CapabilityStatement.rest.operation"/>
        <equivalence value="relatedto"/>
        <comment
                 value="Element `CapabilityStatement.rest.operation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.operation` is mapped to FHIR R4B element `CapabilityStatement.rest.operation` as `Equivalent`."/>
      </target>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="relatedto"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.operation"/>
        <display value="CapabilityStatement.rest.resource.operation"/>
        <equivalence value="relatedto"/>
        <comment
                 value="Element `CapabilityStatement.rest.operation` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.operation` is mapped to FHIR R4B element `CapabilityStatement.rest.operation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.operation.name"/>
      <display value="name"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.operation.name"/>
        <display value="CapabilityStatement.rest.resource.operation.name"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.operation.name` is mapped to FHIR R4B 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 &quot;$&quot; portion that is always included in the URL."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.operation.definition"/>
      <display value="definition"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.resource.operation.definition"/>
        <display
                 value="CapabilityStatement.rest.resource.operation.definition"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.compartment"/>
      <display value="compartment"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.rest.compartment"/>
        <display value="CapabilityStatement.rest.compartment"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.compartment` is mapped to FHIR R4B element `CapabilityStatement.rest.compartment` as `Equivalent`.
At present, the only defined compartments are at [CompartmentDefinition](https://hl7.org/fhir/compartmentdefinition.html)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging"/>
      <display value="messaging"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.messaging"/>
        <display value="CapabilityStatement.messaging"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.messaging` is mapped to FHIR R4B element `CapabilityStatement.messaging` as `Equivalent`.
Multiple repetitions allow the documentation of multiple endpoints per solution."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.endpoint"/>
      <display value="endpoint"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.messaging.endpoint"/>
        <display value="CapabilityStatement.messaging.endpoint"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.messaging.endpoint` is mapped to FHIR R4B element `CapabilityStatement.messaging.endpoint` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.endpoint.protocol"/>
      <display value="protocol"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.messaging.endpoint.protocol"/>
        <display value="CapabilityStatement.messaging.endpoint.protocol"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.messaging.endpoint.protocol` is mapped to FHIR R4B element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.endpoint.address"/>
      <display value="address"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.messaging.endpoint.address"/>
        <display value="CapabilityStatement.messaging.endpoint.address"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.messaging.endpoint.address` is mapped to FHIR R4B element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.reliableCache"/>
      <display value="reliableCache"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.messaging.reliableCache"/>
        <display value="CapabilityStatement.messaging.reliableCache"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.messaging.reliableCache` is mapped to FHIR R4B element `CapabilityStatement.messaging.reliableCache` as `Equivalent`.
If this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.documentation"/>
      <display value="documentation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.messaging.documentation"/>
        <display value="CapabilityStatement.messaging.documentation"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.messaging.documentation` is mapped to FHIR R4B element `CapabilityStatement.messaging.documentation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.supportedMessage"/>
      <display value="supportedMessage"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.messaging.supportedMessage"/>
        <display value="CapabilityStatement.messaging.supportedMessage"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.messaging.supportedMessage` is mapped to FHIR R4B element `CapabilityStatement.messaging.supportedMessage` as `Equivalent`.
This is a proposed alternative to the messaging.event structure."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.supportedMessage.mode"/>
      <display value="mode"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.messaging.supportedMessage.mode"/>
        <display value="CapabilityStatement.messaging.supportedMessage.mode"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.messaging.supportedMessage.mode` is mapped to FHIR R4B element `CapabilityStatement.messaging.supportedMessage.mode` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code
            value="CapabilityStatement.messaging.supportedMessage.definition"/>
      <display value="definition"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code
              value="CapabilityStatement.messaging.supportedMessage.definition"/>
        <display
                 value="CapabilityStatement.messaging.supportedMessage.definition"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4B 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.document"/>
      <display value="document"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.document"/>
        <display value="CapabilityStatement.document"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.document` is mapped to FHIR R4B element `CapabilityStatement.document` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.document.mode"/>
      <display value="mode"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.document.mode"/>
        <display value="CapabilityStatement.document.mode"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.document.mode` is mapped to FHIR R4B element `CapabilityStatement.document.mode` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.document.documentation"/>
      <display value="documentation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="CapabilityStatement.document.documentation"/>
        <display value="CapabilityStatement.document.documentation"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.document.documentation` is mapped to FHIR R4B element `CapabilityStatement.document.documentation` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.document.profile"/>
      <display value="profile"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="CapabilityStatement.document.profile"/>
        <display value="CapabilityStatement.document.profile"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.document.profile` is mapped to FHIR R4B 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."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.meta"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.meta"/>
      <display value="meta"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.meta` is mapped to FHIR R4B element `CapabilityStatement.meta` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.meta` do not cover the following types: Meta.
The mappings for `CapabilityStatement.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.text"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.text"/>
      <display value="text"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.text` is mapped to FHIR R4B element `CapabilityStatement.text` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.text` do not cover the following types: Narrative.
The mappings for `CapabilityStatement.text` do not cover the following types based on type expansion: div, status.
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 &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded in formation is added later."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.contact"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.contact"/>
      <display value="contact"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.contact` is mapped to FHIR R4B element `CapabilityStatement.contact` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.contact` do not cover the following types: ContactDetail.
The mappings for `CapabilityStatement.contact` do not cover the following types based on type expansion: name, telecom.
May be a web site, an email address, a telephone number, etc."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.useContext"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.useContext"/>
      <display value="useContext"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.useContext` is mapped to FHIR R4B element `CapabilityStatement.useContext` as `SourceIsBroaderThanTarget`.
The mappings for `CapabilityStatement.useContext` do not cover the following types: UsageContext.
The mappings for `CapabilityStatement.useContext` do not cover the following types based on type expansion: code, value[x].
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.acceptUnknown"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.acceptUnknown"/>
      <display value="acceptUnknown"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. 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."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.profile"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.profile"/>
      <display value="profile"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.profile` is mapped to FHIR R4B 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."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.security.certificate"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.rest.security.certificate"/>
      <display value="certificate"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.security.certificate.type"/>
      <display value="type"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:type"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.rest.security.certificate.blob"/>
      <display value="blob"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:blob"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.resource.type"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.rest.resource.type"/>
      <display value="type"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.type` as `RelatedTo`.
The mappings for `CapabilityStatement.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.resource.profile"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.rest.resource.profile"/>
      <display value="profile"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`.
Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4B 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>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.rest.operation.definition"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.rest.operation.definition"/>
      <display value="definition"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4B 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."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.messaging.supportedMessage.definition"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code
            value="CapabilityStatement.messaging.supportedMessage.definition"/>
      <display value="definition"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4B 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."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.messaging.event"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.messaging.event"/>
      <display value="event"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="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 R4B. 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.event.code"/>
      <display value="code"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:code"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.event.category"/>
      <display value="category"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:category"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.event.mode"/>
      <display value="mode"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:mode"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.event.focus"/>
      <display value="focus"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:focus"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. 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."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.event.request"/>
      <display value="request"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:request"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.event.response"/>
      <display value="response"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:response"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="CapabilityStatement.messaging.event.documentation"/>
      <display value="documentation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:documentation"/>
        <equivalence value="equivalent"/>
        <comment
                 value="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 R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
  </group>
  <group>
    <source
            value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-CapabilityStatement.document.profile"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="CapabilityStatement.document.profile"/>
      <display value="profile"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `CapabilityStatement.document.profile` is mapped to FHIR R4B 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."/>
      </target>
    </element>
  </group>
</ConceptMap>