R5-CapabilityStatement-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-CapabilityStatement-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-CapabilityStatement-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|5.0.0 to CapabilityStatementversion: 4.0.1) Source Code Relationship Target Code Comment CapabilityStatement.meta (meta) is equivalent to CapabilityStatement.meta Element `CapabilityStatement.meta` is mapped to FHIR R4 element `CapabilityStatement.meta` as `Equivalent`. CapabilityStatement.implicitRules (implicitRules) is equivalent to CapabilityStatement.implicitRules Element `CapabilityStatement.implicitRules` is mapped to FHIR R4 element `CapabilityStatement.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc. CapabilityStatement.language (language) is equivalent to CapabilityStatement.language Element `CapabilityStatement.language` is mapped to FHIR R4 element `CapabilityStatement.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations 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 sh…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-CapabilityStatement-element-map-to-R4
  l: R5-CapabilityStatement-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5CapabilityStatementElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 CapabilityStatement to FHIR R4 CapabilityStatement
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:44.2160982-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 CapabilityStatement to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
    l: CapabilityStatement
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
    l: CapabilityStatement
  target version:
    v: 4.0.1
  element:
    code:
      v: CapabilityStatement.meta
    display:
      v: meta
    target:
      code:
        v: CapabilityStatement.meta
      display:
        v: CapabilityStatement.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.meta` is mapped to FHIR R4 element `CapabilityStatement.meta` as `Equivalent`.
  element:
    code:
      v: CapabilityStatement.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: CapabilityStatement.implicitRules
      display:
        v: CapabilityStatement.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.implicitRules` is mapped to FHIR R4 element `CapabilityStatement.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
  element:
    code:
      v: CapabilityStatement.language
    display:
      v: language
    target:
      code:
        v: CapabilityStatement.language
      display:
        v: CapabilityStatement.language
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.language` is mapped to FHIR R4 element `CapabilityStatement.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
  element:
    code:
      v: CapabilityStatement.text
    display:
      v: text
    target:
      code:
        v: CapabilityStatement.text
      display:
        v: CapabilityStatement.text
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.text` is mapped to FHIR R4 element `CapabilityStatement.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
  element:
    code:
      v: CapabilityStatement.contained
    display:
      v: contained
    target:
      code:
        v: CapabilityStatement.contained
      display:
        v: CapabilityStatement.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.contained` is mapped to FHIR R4 element `CapabilityStatement.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
  element:
    code:
      v: CapabilityStatement.url
    display:
      v: url
    target:
      code:
        v: CapabilityStatement.url
      display:
        v: CapabilityStatement.url
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.url` is mapped to FHIR R4 element `CapabilityStatement.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
  element:
    code:
      v: CapabilityStatement.version
    display:
      v: version
    target:
      code:
        v: CapabilityStatement.version
      display:
        v: CapabilityStatement.version
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.version` is mapped to FHIR R4 element `CapabilityStatement.version` as `Equivalent`. There may be different capability statement instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the capability statement with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).
  element:
    code:
      v: CapabilityStatement.name
    display:
      v: name
    target:
      code:
        v: CapabilityStatement.name
      display:
        v: CapabilityStatement.name
      equivalence:
        v: equivalent
      comment:
        v: Element `CapabilityStatement.name` is mapped to FHIR R4 element `CapabilityStatement.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

code:
  v: CapabilityStatement.title
display:
  v: title
target:
  code:
    v: CapabilityStatement.title
  display:
    v: CapabilityStatement.title
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.title` is mapped to FHIR R4 element `CapabilityStatement.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

code:
  v: CapabilityStatement.status
display:
  v: status
target:
  code:
    v: CapabilityStatement.status
  display:
    v: CapabilityStatement.status
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.status` is mapped to FHIR R4 element `CapabilityStatement.status` as `Equivalent`. Allows filtering of capability statements that are appropriate for use versus not.This is not intended for use with actual capability statements, but where capability statements are used to describe possible or desired systems. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: CapabilityStatement.experimental
display:
  v: experimental
target:
  code:
    v: CapabilityStatement.experimental
  display:
    v: CapabilityStatement.experimental
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.experimental` is mapped to FHIR R4 element `CapabilityStatement.experimental` as `Equivalent`. Allows filtering of capability statements that are appropriate for use versus not.

code:
  v: CapabilityStatement.date
display:
  v: date
target:
  code:
    v: CapabilityStatement.date
  display:
    v: CapabilityStatement.date
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.date` is mapped to FHIR R4 element `CapabilityStatement.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. 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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: CapabilityStatement.publisher
display:
  v: publisher
target:
  code:
    v: CapabilityStatement.publisher
  display:
    v: CapabilityStatement.publisher
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.publisher` is mapped to FHIR R4 element `CapabilityStatement.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the capability statement is the organization or individual primarily responsible for the maintenance and upkeep of the capability statement. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the capability statement. This item SHOULD be populated unless the information is available from context.

code:
  v: CapabilityStatement.contact
display:
  v: contact
target:
  code:
    v: CapabilityStatement.contact
  display:
    v: CapabilityStatement.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.contact` is mapped to FHIR R4 element `CapabilityStatement.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: CapabilityStatement.description
display:
  v: description
target:
  code:
    v: CapabilityStatement.description
  display:
    v: CapabilityStatement.description
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.description` is mapped to FHIR R4 element `CapabilityStatement.description` as `Equivalent`. This description can be used to capture details such as 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 capability statement is presumed to be the predominant language in the place the capability statement was created).This does not need to be populated if the description is adequately implied by the software or implementation details.

code:
  v: CapabilityStatement.useContext
display:
  v: useContext
target:
  code:
    v: CapabilityStatement.useContext
  display:
    v: CapabilityStatement.useContext
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.useContext` is mapped to FHIR R4 element `CapabilityStatement.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

code:
  v: CapabilityStatement.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: CapabilityStatement.jurisdiction
  display:
    v: CapabilityStatement.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.jurisdiction` is mapped to FHIR R4 element `CapabilityStatement.jurisdiction` as `Equivalent`. Element `CapabilityStatement.jurisdiction` has been flagged as deprecated. It may be possible for the capability statement to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)

code:
  v: CapabilityStatement.purpose
display:
  v: purpose
target:
  code:
    v: CapabilityStatement.purpose
  display:
    v: CapabilityStatement.purpose
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.purpose` is mapped to FHIR R4 element `CapabilityStatement.purpose` as `Equivalent`. This element does not describe the usage of the capability statement. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this capability statement.

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

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

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

code:
  v: CapabilityStatement.imports
display:
  v: imports
target:
  code:
    v: CapabilityStatement.imports
  display:
    v: CapabilityStatement.imports
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.imports` is mapped to FHIR R4 element `CapabilityStatement.imports` as `Equivalent`. the contents of any directly or indirectly imported CapabilityStatements SHALL NOT overlap, i.e. they cannot refer to the same rest/resource, operations/name, searchparam/name, interaction/code, messaging/endpoint, document/mode pair. A capability statement that imports another CapabilityStatement automatically instantiates it too (though this is often not a very useful statement for the kinds of CapabilityStatements that are suitable for importing).

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

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

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

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

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

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

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

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

code:
  v: CapabilityStatement.fhirVersion
display:
  v: fhirVersion
target:
  code:
    v: CapabilityStatement.fhirVersion
  display:
    v: CapabilityStatement.fhirVersion
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.fhirVersion` is mapped to FHIR R4 element `CapabilityStatement.fhirVersion` as `SourceIsBroaderThanTarget`. Servers may implement multiple versions (see [Managing Multiple Versions](https://hl7.org/fhir/versioning.html), and the [$versions](https://hl7.org/fhir/capabilitystatement-operation-versions.html) operation). If they do, and the CapabilityStatement is requested from the server, then this fhirVersion will be either the version requested, or the server's default version.

code:
  v: CapabilityStatement.format
display:
  v: format
target:
  code:
    v: CapabilityStatement.format
  display:
    v: CapabilityStatement.format
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.format` is mapped to FHIR R4 element `CapabilityStatement.format` as `Equivalent`. "xml", "json" and "ttl" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here.

code:
  v: CapabilityStatement.patchFormat
display:
  v: patchFormat
target:
  code:
    v: CapabilityStatement.patchFormat
  display:
    v: CapabilityStatement.patchFormat
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.patchFormat` is mapped to FHIR R4 element `CapabilityStatement.patchFormat` as `Equivalent`. At present, the patch mime types application/json-patch+json and application/xml-patch+xml are legal. Generally, if a server supports PATCH, it would be expected to support the patch formats and match the formats it supports, but this is not always possible or necessary.

code:
  v: CapabilityStatement.implementationGuide
display:
  v: implementationGuide
target:
  code:
    v: CapabilityStatement.implementationGuide
  display:
    v: CapabilityStatement.implementationGuide
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.implementationGuide` is mapped to FHIR R4 element `CapabilityStatement.implementationGuide` as `Equivalent`. Note: this is primarily only relevant in terms of ImplementationGuides that don't define specific CapabilityStatements declaring the expectation of distinct roles. (E.g. generic IGs that establish privacy policies.) In situations where an ImplementationGuide does define CapabilityStatements, asserting CapabilityStatement.implementationGuide means that the implementation adheres to any Implementation.global definitions present in that IG as well as any textual requirements around security or other general interoperability behaviors. However, it does not make any assertions as to conformance with any of the CapabilityStatements defined in the IG. To assert conformance with CapabilityStatements in a referenced IG, it is necessary to use the CapabilityStatement.instantiates element.

code:
  v: CapabilityStatement.rest
display:
  v: rest
target:
  code:
    v: CapabilityStatement.rest
  display:
    v: CapabilityStatement.rest
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest` is mapped to FHIR R4 element `CapabilityStatement.rest` as `Equivalent`. Multiple repetitions allow definition of both client and/or server behaviors or possibly behaviors under different configuration settings (for software or requirements statements).

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

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

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

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

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

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

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

code:
  v: CapabilityStatement.rest.resource.type
display:
  v: type
target:
  code:
    v: CapabilityStatement.rest.resource.type
  display:
    v: CapabilityStatement.rest.resource.type
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4 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.

code:
  v: CapabilityStatement.rest.resource.profile
display:
  v: profile
target:
  code:
    v: CapabilityStatement.rest.resource.profile
  display:
    v: CapabilityStatement.rest.resource.profile
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.profile` as `Equivalent`. All other profiles for this type that are listed in `.rest.resource.supportedProfile` must conform to this profile.

code:
  v: CapabilityStatement.rest.resource.supportedProfile
display:
  v: supportedProfile
target:
  code:
    v: CapabilityStatement.rest.resource.supportedProfile
  display:
    v: CapabilityStatement.rest.resource.supportedProfile
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.supportedProfile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `Equivalent`. Supported profiles must conform to the resource profile in the `.rest.resource.profile` element if it is present. The resource profile is a system-wide profile applied across *all* instances of the resource supported by the system. A supported profile is a statement about the functionality of the data and services provided by the server (or used by the client) for a particular set of use cases and will not necessarily apply to all data consumed or exposed by the server.

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

code:
  v: CapabilityStatement.rest.resource.interaction
display:
  v: interaction
target:
  code:
    v: CapabilityStatement.rest.resource.interaction
  display:
    v: CapabilityStatement.rest.resource.interaction
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.resource.interaction` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction` as `Equivalent`. In general, a Resource will only appear in a CapabilityStatement if the server actually has some capabilities - e.g. there is at least one interaction supported. However interactions can be omitted to support summarization (_summary = true).

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

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

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

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

code:
  v: CapabilityStatement.rest.resource.updateCreate
display:
  v: updateCreate
target:
  code:
    v: CapabilityStatement.rest.resource.updateCreate
  display:
    v: CapabilityStatement.rest.resource.updateCreate
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.updateCreate` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.updateCreate` as `Equivalent`. Allowing the clients to create new identities on the server means that the system administrator needs to have confidence that the clients do not create clashing identities between them. Obviously, if there is only one client, this won't happen. While creating identities on the client means that the clients need to be managed, it's much more convenient for many scenarios if such management can be put in place.

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

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

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

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

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

code:
  v: CapabilityStatement.rest.resource.searchInclude
display:
  v: searchInclude
target:
  code:
    v: CapabilityStatement.rest.resource.searchInclude
  display:
    v: CapabilityStatement.rest.resource.searchInclude
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchInclude` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`. Documenting [`_include`](http://hl7.org/fhir/R5/search.html#revinclude) support helps set conformance expectations for the desired system. Still, it is a level of detail that might not be exposed by production servers or clients when using CapabilityStatement to describe an actual implementation. If this list is empty, the server does not support includes. Support for *iterative* (a.k.a., recursive) `_include` is communicated by listing the iterative includes values supported by the server in the `searchInclude` element of the "root" resource type. For example, to support the following search: `GET [base]/CarePlan?_include=CarePlan:activity-reference:DeviceRequest&_include:iterate=DeviceRequest:device` These values would be listed as part of capabilities for "CarePlan": "searchInclude" : ["CarePlan:activity-reference:DeviceRequest","DeviceRequest:device"],

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

code:
  v: CapabilityStatement.rest.resource.searchParam
display:
  v: searchParam
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam
  display:
    v: CapabilityStatement.rest.resource.searchParam
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam` as `Equivalent`. The search parameters should include the control search parameters such as _sort, _count, etc. that also apply to this resource (though many will be listed at [CapabilityStatement.rest.searchParam](https://hl7.org/fhir/capabilitystatement-definitions.html#.html#CapabilityStatement.rest.searchParam)). The behavior of some search parameters may be further described by other code or extension elements, or narrative within the capability statement or linked [SearchParameter](https://hl7.org/fhir/s.html#) definitions.

code:
  v: CapabilityStatement.rest.resource.searchParam.name
display:
  v: name
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam.name
  display:
    v: CapabilityStatement.rest.resource.searchParam.name
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam.name` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.name` as `Equivalent`. Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined. There is no correspondence whatsoever between CapabilityStatement's searchParam.name and SearchParameter.name - the latter is used as a class name when generating code for the search parameter.

code:
  v: CapabilityStatement.rest.resource.searchParam.definition
display:
  v: definition
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam.definition
  display:
    v: CapabilityStatement.rest.resource.searchParam.definition
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam.definition` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.definition` as `Equivalent`. This SHOULD be present, and matches refers to a SearchParameter by its canonical URL. If systems wish to document their support for modifiers, comparators, target resource types, and chained parameters, they should do using a search parameter resource. This element SHALL be populated if the search parameter refers to a SearchParameter defined by the FHIR core specification or externally defined IGs.

code:
  v: CapabilityStatement.rest.resource.searchParam.type
display:
  v: type
target:
  code:
    v: CapabilityStatement.rest.resource.searchParam.type
  display:
    v: CapabilityStatement.rest.resource.searchParam.type
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.type` as `Equivalent`. While this can be looked up from the definition, it is included here as a convenience for systems that autogenerate a query interface based on the server capability statement. It SHALL be the same as the type in the search parameter definition.

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

code:
  v: CapabilityStatement.rest.resource.operation
display:
  v: operation
target:
  code:
    v: CapabilityStatement.rest.resource.operation
  display:
    v: CapabilityStatement.rest.resource.operation
  equivalence:
    v: wider
  comment:
    v: Element `CapabilityStatement.rest.resource.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation` as `Equivalent`. Operations linked from CapabilityStatement.rest.resource.operation must have OperationDefinition.type = true or OperationDefinition.instance = true. If an operation that is listed in multiple CapabilityStatement.rest.resource.operation (e.g. for different resource types), then clients should understand that the operation is only supported on the specified resource types, and that may be a subset of those listed in OperationDefinition.resource.

code:
  v: CapabilityStatement.rest.resource.operation.name
display:
  v: name
target:
  code:
    v: CapabilityStatement.rest.resource.operation.name
  display:
    v: CapabilityStatement.rest.resource.operation.name
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.operation.name` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.name` as `Equivalent`. The name here SHOULD be the same as the OperationDefinition.code in the referenced OperationDefinition, unless there is a name clash and the OperationDefinition.code cannot be used. The name does not include the "$" portion that is always included in the URL. There is no correspondence whatsoever between CapabilityStatement's operation.name and OperationDefinition.name - the latter is used as a class name when generating code for the operation. HL7 will never define operations that have conflicting names.

code:
  v: CapabilityStatement.rest.resource.operation.definition
display:
  v: definition
target:
  code:
    v: CapabilityStatement.rest.resource.operation.definition
  display:
    v: CapabilityStatement.rest.resource.operation.definition
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.resource.operation.definition` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.definition` as `Equivalent`. This can be used to build an HTML form to invoke the operation, for instance.

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

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

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

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

code:
  v: CapabilityStatement.rest.searchParam
display:
  v: searchParam
target:
  code:
    v: CapabilityStatement.rest.searchParam
  display:
    v: CapabilityStatement.rest.searchParam
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.searchParam` is mapped to FHIR R4 element `CapabilityStatement.rest.searchParam` as `Equivalent`. Typically, the only search parameters supported for all searches are those that apply to all resources - tags, profiles, text search etc. These search parameters should include the control search parameters such as _sort, _count, etc. that also apply to this resource (though many will be listed at [CapabilityStatement.rest.searchParam](https://hl7.org/fhir/capabilitystatement-definitions.html#.html#CapabilityStatement.rest.searchParam)). The behavior of some search parameters may be further described by other code or extension elements, or narrative within the capability statement or linked [SearchParameter](https://hl7.org/fhir/s.html#) definitions.

code:
  v: CapabilityStatement.rest.operation
display:
  v: operation
target:
  code:
    v: CapabilityStatement.rest.operation
  display:
    v: CapabilityStatement.rest.operation
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.operation` as `Equivalent`. CapabilityStatement.rest.operation is for operations invoked at the system level, or for operations that are supported across multiple resource types. Operations linked from CapabilityStatement.rest.operation must have OperationDefinition.system = true, or more than one Operation.resource.

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

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

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

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

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

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

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

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

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

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

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

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

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

code:
  v: CapabilityStatement.document.profile
display:
  v: profile
target:
  code:
    v: CapabilityStatement.document.profile
  display:
    v: CapabilityStatement.document.profile
  equivalence:
    v: equivalent
  comment:
    v: Element `CapabilityStatement.document.profile` is mapped to FHIR R4 element `CapabilityStatement.document.profile` as `Equivalent`. The profile is actually on the Bundle.

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-CapabilityStatement.identifier
  l: extension-CapabilityStatement.identifier
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.identifier
  display:
    v: identifier
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `CapabilityStatement.identifier` has a context of CapabilityStatement based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-CapabilityStatement.fhirVersion
  l: extension-CapabilityStatement.fhirVersion
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.fhirVersion
  display:
    v: fhirVersion
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.fhirVersion` is mapped to FHIR R4 element `CapabilityStatement.fhirVersion` as `SourceIsBroaderThanTarget`. Servers may implement multiple versions (see [Managing Multiple Versions](https://hl7.org/fhir/versioning.html), and the [$versions](https://hl7.org/fhir/capabilitystatement-operation-versions.html) operation). If they do, and the CapabilityStatement is requested from the server, then this fhirVersion will be either the version requested, or the server's default version.

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-CapabilityStatement.acceptLanguage
  l: extension-CapabilityStatement.acceptLanguage
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.acceptLanguage
  display:
    v: acceptLanguage
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `CapabilityStatement.acceptLanguage` has a context of CapabilityStatement based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.acceptLanguage` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). In general, if a server gets a request with an Accept-Language that it doesn't support, it should still reutrn the resource, just in its default language for the resource.

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-CapabilityStatement.rest.resource.type
  l: extension-CapabilityStatement.rest.resource.type
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.rest.resource.type
  display:
    v: type
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/CapabilityStatement
  l: CapabilityStatement
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-CapabilityStatement.rest.resource.conditionalPatch
  l: extension-CapabilityStatement.rest.resource.conditionalPatch
target version:
  v: 0.1.0
element:
  code:
    v: CapabilityStatement.rest.resource.conditionalPatch
  display:
    v: conditionalPatch
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `CapabilityStatement.rest.resource.conditionalPatch` has a context of CapabilityStatement.rest.resource based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.resource.conditionalPatch` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Conditional Patch is mainly appropriate for interface engine scripts converting from other formats, such as v2.