Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU International flag

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

ConceptMap: R4CapabilityStatementElementMapToR5

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4-CapabilityStatement-element-map-to-R5 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R4CapabilityStatementElementMapToR5

This ConceptMap represents cross-version mappings for elements from a FHIR R4 CapabilityStatement to FHIR R5.

Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/5.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to CapabilityStatementversion: 5.0.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.meta (meta)is equivalent toCapabilityStatement.metaElement `CapabilityStatement.meta` is mapped to FHIR R5 element `CapabilityStatement.meta` as `Equivalent`.
CapabilityStatement.implicitRules (implicitRules)is equivalent toCapabilityStatement.implicitRulesElement `CapabilityStatement.implicitRules` is mapped to FHIR R5 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 it's narrative along with other profiles, value sets, etc.
CapabilityStatement.language (language)is equivalent toCapabilityStatement.languageElement `CapabilityStatement.language` is mapped to FHIR R5 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).
CapabilityStatement.text (text)is equivalent toCapabilityStatement.textElement `CapabilityStatement.text` is mapped to FHIR R5 element `CapabilityStatement.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
CapabilityStatement.contained (contained)is equivalent toCapabilityStatement.containedElement `CapabilityStatement.contained` is mapped to FHIR R5 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.
CapabilityStatement.url (url)is equivalent toCapabilityStatement.urlElement `CapabilityStatement.url` is mapped to FHIR R5 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.
CapabilityStatement.version (version)is equivalent toCapabilityStatement.versionElement `CapabilityStatement.version` is mapped to FHIR R5 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].
CapabilityStatement.name (name)is equivalent toCapabilityStatement.nameElement `CapabilityStatement.name` is mapped to FHIR R5 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.
CapabilityStatement.title (title)is equivalent toCapabilityStatement.titleElement `CapabilityStatement.title` is mapped to FHIR R5 element `CapabilityStatement.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
CapabilityStatement.status (status)is equivalent toCapabilityStatement.statusElement `CapabilityStatement.status` is mapped to FHIR R5 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.
CapabilityStatement.experimental (experimental)is equivalent toCapabilityStatement.experimentalElement `CapabilityStatement.experimental` is mapped to FHIR R5 element `CapabilityStatement.experimental` as `Equivalent`. Allows filtering of capability statements that are appropriate for use versus not.
CapabilityStatement.date (date)is equivalent toCapabilityStatement.dateElement `CapabilityStatement.date` is mapped to FHIR R5 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.
CapabilityStatement.publisher (publisher)is equivalent toCapabilityStatement.publisherElement `CapabilityStatement.publisher` is mapped to FHIR R5 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.
CapabilityStatement.contact (contact)is equivalent toCapabilityStatement.contactElement `CapabilityStatement.contact` is mapped to FHIR R5 element `CapabilityStatement.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
CapabilityStatement.description (description)is equivalent toCapabilityStatement.descriptionElement `CapabilityStatement.description` is mapped to FHIR R5 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 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.
CapabilityStatement.useContext (useContext)is equivalent toCapabilityStatement.useContextElement `CapabilityStatement.useContext` is mapped to FHIR R5 element `CapabilityStatement.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
CapabilityStatement.jurisdiction (jurisdiction)is equivalent toCapabilityStatement.jurisdictionElement `CapabilityStatement.jurisdiction` is mapped to FHIR R5 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.
CapabilityStatement.purpose (purpose)is equivalent toCapabilityStatement.purposeElement `CapabilityStatement.purpose` is mapped to FHIR R5 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.
CapabilityStatement.copyright (copyright)is equivalent toCapabilityStatement.copyrightElement `CapabilityStatement.copyright` is mapped to FHIR R5 element `CapabilityStatement.copyright` as `Equivalent`.
CapabilityStatement.kind (kind)is equivalent toCapabilityStatement.kindElement `CapabilityStatement.kind` is mapped to FHIR R5 element `CapabilityStatement.kind` as `Equivalent`.
CapabilityStatement.instantiates (instantiates)is equivalent toCapabilityStatement.instantiatesElement `CapabilityStatement.instantiates` is mapped to FHIR R5 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.
CapabilityStatement.imports (imports)is equivalent toCapabilityStatement.importsElement `CapabilityStatement.imports` is mapped to FHIR R5 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).
CapabilityStatement.software (software)is broader thanCapabilityStatement.softwareElement `CapabilityStatement.software` is mapped to FHIR R5 element `CapabilityStatement.software` as `Equivalent`.
CapabilityStatement.software.name (name)is equivalent toCapabilityStatement.software.nameElement `CapabilityStatement.software.name` is mapped to FHIR R5 element `CapabilityStatement.software.name` as `Equivalent`.
CapabilityStatement.software.version (version)is equivalent toCapabilityStatement.software.versionElement `CapabilityStatement.software.version` is mapped to FHIR R5 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.
CapabilityStatement.software.releaseDate (releaseDate)is equivalent toCapabilityStatement.software.releaseDateElement `CapabilityStatement.software.releaseDate` is mapped to FHIR R5 element `CapabilityStatement.software.releaseDate` as `Equivalent`.
CapabilityStatement.implementation (implementation)is broader thanCapabilityStatement.implementationElement `CapabilityStatement.implementation` is mapped to FHIR R5 element `CapabilityStatement.implementation` as `Equivalent`.
CapabilityStatement.implementation.description (description)is equivalent toCapabilityStatement.implementation.descriptionElement `CapabilityStatement.implementation.description` is mapped to FHIR R5 element `CapabilityStatement.implementation.description` as `Equivalent`.
CapabilityStatement.implementation.url (url)is equivalent toCapabilityStatement.implementation.urlElement `CapabilityStatement.implementation.url` is mapped to FHIR R5 element `CapabilityStatement.implementation.url` as `Equivalent`.
CapabilityStatement.implementation.custodian (custodian)is equivalent toCapabilityStatement.implementation.custodianElement `CapabilityStatement.implementation.custodian` is mapped to FHIR R5 element `CapabilityStatement.implementation.custodian` as `Equivalent`.
CapabilityStatement.fhirVersion (fhirVersion)is equivalent toCapabilityStatement.fhirVersionElement `CapabilityStatement.fhirVersion` is mapped to FHIR R5 element `CapabilityStatement.fhirVersion` as `SourceIsNarrowerThanTarget`. The mappings for `CapabilityStatement.fhirVersion` do not allow expression of the necessary codes, per the bindings on the source and target. 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.
CapabilityStatement.format (format)is equivalent toCapabilityStatement.formatElement `CapabilityStatement.format` is mapped to FHIR R5 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.
CapabilityStatement.patchFormat (patchFormat)is equivalent toCapabilityStatement.patchFormatElement `CapabilityStatement.patchFormat` is mapped to FHIR R5 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.
CapabilityStatement.implementationGuide (implementationGuide)is equivalent toCapabilityStatement.implementationGuideElement `CapabilityStatement.implementationGuide` is mapped to FHIR R5 element `CapabilityStatement.implementationGuide` as `Equivalent`.
CapabilityStatement.rest (rest)is broader thanCapabilityStatement.restElement `CapabilityStatement.rest` is mapped to FHIR R5 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).
CapabilityStatement.rest.mode (mode)is equivalent toCapabilityStatement.rest.modeElement `CapabilityStatement.rest.mode` is mapped to FHIR R5 element `CapabilityStatement.rest.mode` as `Equivalent`.
CapabilityStatement.rest.documentation (documentation)is equivalent toCapabilityStatement.rest.documentationElement `CapabilityStatement.rest.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.documentation` as `Equivalent`.
CapabilityStatement.rest.security (security)is broader thanCapabilityStatement.rest.securityElement `CapabilityStatement.rest.security` is mapped to FHIR R5 element `CapabilityStatement.rest.security` as `Equivalent`.
CapabilityStatement.rest.security.cors (cors)is equivalent toCapabilityStatement.rest.security.corsElement `CapabilityStatement.rest.security.cors` is mapped to FHIR R5 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.
CapabilityStatement.rest.security.service (service)is equivalent toCapabilityStatement.rest.security.serviceElement `CapabilityStatement.rest.security.service` is mapped to FHIR R5 element `CapabilityStatement.rest.security.service` as `Equivalent`.
CapabilityStatement.rest.security.description (description)is equivalent toCapabilityStatement.rest.security.descriptionElement `CapabilityStatement.rest.security.description` is mapped to FHIR R5 element `CapabilityStatement.rest.security.description` as `Equivalent`.
CapabilityStatement.rest.resource (resource)is broader thanCapabilityStatement.rest.resourceElement `CapabilityStatement.rest.resource` is mapped to FHIR R5 element `CapabilityStatement.rest.resource` as `Equivalent`. Max of one repetition per resource type.
CapabilityStatement.rest.resource.type (type)is broader thanCapabilityStatement.rest.resource.typeElement `CapabilityStatement.rest.resource.type` is mapped to FHIR R5 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.
CapabilityStatement.rest.resource.profile (profile)is equivalent toCapabilityStatement.rest.resource.profileElement `CapabilityStatement.rest.resource.profile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.profile` as `Equivalent`. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system.
CapabilityStatement.rest.resource.supportedProfile (supportedProfile)is equivalent toCapabilityStatement.rest.resource.supportedProfileElement `CapabilityStatement.rest.resource.supportedProfile` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.supportedProfile` as `Equivalent`. Supported profiles are different than the profile that applies 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 do? 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).
CapabilityStatement.rest.resource.documentation (documentation)is equivalent toCapabilityStatement.rest.resource.documentationElement `CapabilityStatement.rest.resource.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.documentation` as `Equivalent`.
CapabilityStatement.rest.resource.interaction (interaction)is broader thanCapabilityStatement.rest.resource.interactionElement `CapabilityStatement.rest.resource.interaction` is mapped to FHIR R5 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).
CapabilityStatement.rest.resource.interaction.code (code)is equivalent toCapabilityStatement.rest.resource.interaction.codeElement `CapabilityStatement.rest.resource.interaction.code` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction.code` as `Equivalent`.
CapabilityStatement.rest.resource.interaction.documentation (documentation)is equivalent toCapabilityStatement.rest.resource.interaction.documentationElement `CapabilityStatement.rest.resource.interaction.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`.
CapabilityStatement.rest.resource.versioning (versioning)is equivalent toCapabilityStatement.rest.resource.versioningElement `CapabilityStatement.rest.resource.versioning` is mapped to FHIR R5 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.
CapabilityStatement.rest.resource.readHistory (readHistory)is equivalent toCapabilityStatement.rest.resource.readHistoryElement `CapabilityStatement.rest.resource.readHistory` is mapped to FHIR R5 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.
CapabilityStatement.rest.resource.updateCreate (updateCreate)is equivalent toCapabilityStatement.rest.resource.updateCreateElement `CapabilityStatement.rest.resource.updateCreate` is mapped to FHIR R5 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.
CapabilityStatement.rest.resource.conditionalCreate (conditionalCreate)is equivalent toCapabilityStatement.rest.resource.conditionalCreateElement `CapabilityStatement.rest.resource.conditionalCreate` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.conditionalCreate` as `Equivalent`. Conditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2.
CapabilityStatement.rest.resource.conditionalRead (conditionalRead)is equivalent toCapabilityStatement.rest.resource.conditionalReadElement `CapabilityStatement.rest.resource.conditionalRead` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.conditionalRead` as `Equivalent`. Conditional Read is mainly appropriate for interface engine scripts converting from other formats, such as v2.
CapabilityStatement.rest.resource.conditionalUpdate (conditionalUpdate)is equivalent toCapabilityStatement.rest.resource.conditionalUpdateElement `CapabilityStatement.rest.resource.conditionalUpdate` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.conditionalUpdate` as `Equivalent`. Conditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2.
CapabilityStatement.rest.resource.conditionalDelete (conditionalDelete)is equivalent toCapabilityStatement.rest.resource.conditionalDeleteElement `CapabilityStatement.rest.resource.conditionalDelete` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.conditionalDelete` as `Equivalent`. Conditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2.
CapabilityStatement.rest.resource.referencePolicy (referencePolicy)is equivalent toCapabilityStatement.rest.resource.referencePolicyElement `CapabilityStatement.rest.resource.referencePolicy` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.referencePolicy` as `Equivalent`.
CapabilityStatement.rest.resource.searchInclude (searchInclude)is equivalent toCapabilityStatement.rest.resource.searchIncludeElement `CapabilityStatement.rest.resource.searchInclude` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`. If this list is empty, the server does not support includes.
CapabilityStatement.rest.resource.searchRevInclude (searchRevInclude)is equivalent toCapabilityStatement.rest.resource.searchRevIncludeElement `CapabilityStatement.rest.resource.searchRevInclude` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchRevInclude` as `Equivalent`. If this list is empty, the server does not support reverse includes.
CapabilityStatement.rest.resource.searchParam (searchParam)is broader thanCapabilityStatement.rest.resource.searchParamElement `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR R5 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.
CapabilityStatement.rest.resource.searchParam.name (name)is equivalent toCapabilityStatement.rest.resource.searchParam.nameElement `CapabilityStatement.rest.resource.searchParam.name` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.name` as `Equivalent`. Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined.
CapabilityStatement.rest.resource.searchParam.definition (definition)is equivalent toCapabilityStatement.rest.resource.searchParam.definitionElement `CapabilityStatement.rest.resource.searchParam.definition` is mapped to FHIR R5 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.
CapabilityStatement.rest.resource.searchParam.type (type)is equivalent toCapabilityStatement.rest.resource.searchParam.typeElement `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR R5 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.
CapabilityStatement.rest.resource.searchParam.documentation (documentation)is equivalent toCapabilityStatement.rest.resource.searchParam.documentationElement `CapabilityStatement.rest.resource.searchParam.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`.
CapabilityStatement.rest.resource.operation (operation)is broader thanCapabilityStatement.rest.resource.operationElement `CapabilityStatement.rest.resource.operation` is mapped to FHIR R5 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.
CapabilityStatement.rest.resource.operation.name (name)is equivalent toCapabilityStatement.rest.resource.operation.nameElement `CapabilityStatement.rest.resource.operation.name` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation.name` as `Equivalent`. The name here SHOULD be the same as the name in the definition, unless there is a name clash and the name cannot be used. The name does not include the "$" portion that is always included in the URL.
CapabilityStatement.rest.resource.operation.definition (definition)is equivalent toCapabilityStatement.rest.resource.operation.definitionElement `CapabilityStatement.rest.resource.operation.definition` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation.definition` as `Equivalent`. This can be used to build an HTML form to invoke the operation, for instance.
CapabilityStatement.rest.resource.operation.documentation (documentation)is equivalent toCapabilityStatement.rest.resource.operation.documentationElement `CapabilityStatement.rest.resource.operation.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.resource.operation.documentation` as `Equivalent`.
CapabilityStatement.rest.interaction (interaction)is broader thanCapabilityStatement.rest.interactionElement `CapabilityStatement.rest.interaction` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction` as `Equivalent`.
CapabilityStatement.rest.interaction.code (code)is equivalent toCapabilityStatement.rest.interaction.codeElement `CapabilityStatement.rest.interaction.code` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction.code` as `Equivalent`.
CapabilityStatement.rest.interaction.documentation (documentation)is equivalent toCapabilityStatement.rest.interaction.documentationElement `CapabilityStatement.rest.interaction.documentation` is mapped to FHIR R5 element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`.
CapabilityStatement.rest.searchParam (searchParam)is equivalent toCapabilityStatement.rest.searchParamElement `CapabilityStatement.rest.searchParam` is mapped to FHIR R5 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.
CapabilityStatement.rest.operation (operation)is equivalent toCapabilityStatement.rest.operationElement `CapabilityStatement.rest.operation` is mapped to FHIR R5 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.
CapabilityStatement.rest.compartment (compartment)is equivalent toCapabilityStatement.rest.compartmentElement `CapabilityStatement.rest.compartment` is mapped to FHIR R5 element `CapabilityStatement.rest.compartment` as `Equivalent`. At present, the only defined compartments are at [CompartmentDefinition](https://hl7.org/fhir/compartmentdefinition.html).
CapabilityStatement.messaging (messaging)is broader thanCapabilityStatement.messagingElement `CapabilityStatement.messaging` is mapped to FHIR R5 element `CapabilityStatement.messaging` as `Equivalent`. Multiple repetitions allow the documentation of multiple endpoints per solution.
CapabilityStatement.messaging.endpoint (endpoint)is broader thanCapabilityStatement.messaging.endpointElement `CapabilityStatement.messaging.endpoint` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint` as `Equivalent`.
CapabilityStatement.messaging.endpoint.protocol (protocol)is equivalent toCapabilityStatement.messaging.endpoint.protocolElement `CapabilityStatement.messaging.endpoint.protocol` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`.
CapabilityStatement.messaging.endpoint.address (address)is equivalent toCapabilityStatement.messaging.endpoint.addressElement `CapabilityStatement.messaging.endpoint.address` is mapped to FHIR R5 element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`.
CapabilityStatement.messaging.reliableCache (reliableCache)is equivalent toCapabilityStatement.messaging.reliableCacheElement `CapabilityStatement.messaging.reliableCache` is mapped to FHIR R5 element `CapabilityStatement.messaging.reliableCache` as `Equivalent`. If this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging.
CapabilityStatement.messaging.documentation (documentation)is equivalent toCapabilityStatement.messaging.documentationElement `CapabilityStatement.messaging.documentation` is mapped to FHIR R5 element `CapabilityStatement.messaging.documentation` as `Equivalent`.
CapabilityStatement.messaging.supportedMessage (supportedMessage)is broader thanCapabilityStatement.messaging.supportedMessageElement `CapabilityStatement.messaging.supportedMessage` is mapped to FHIR R5 element `CapabilityStatement.messaging.supportedMessage` as `Equivalent`. This is a proposed alternative to the messaging.event structure.
CapabilityStatement.messaging.supportedMessage.mode (mode)is equivalent toCapabilityStatement.messaging.supportedMessage.modeElement `CapabilityStatement.messaging.supportedMessage.mode` is mapped to FHIR R5 element `CapabilityStatement.messaging.supportedMessage.mode` as `Equivalent`.
CapabilityStatement.messaging.supportedMessage.definition (definition)is equivalent toCapabilityStatement.messaging.supportedMessage.definitionElement `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R5 element `CapabilityStatement.messaging.supportedMessage.definition` as `Equivalent`.
CapabilityStatement.document (document)is broader thanCapabilityStatement.documentElement `CapabilityStatement.document` is mapped to FHIR R5 element `CapabilityStatement.document` as `Equivalent`.
CapabilityStatement.document.mode (mode)is equivalent toCapabilityStatement.document.modeElement `CapabilityStatement.document.mode` is mapped to FHIR R5 element `CapabilityStatement.document.mode` as `Equivalent`.
CapabilityStatement.document.documentation (documentation)is equivalent toCapabilityStatement.document.documentationElement `CapabilityStatement.document.documentation` is mapped to FHIR R5 element `CapabilityStatement.document.documentation` as `Equivalent`.
CapabilityStatement.document.profile (profile)is equivalent toCapabilityStatement.document.profileElement `CapabilityStatement.document.profile` is mapped to FHIR R5 element `CapabilityStatement.document.profile` as `Equivalent`. The profile is actually on the Bundle.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: type additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.rest.resource.type (type)is equivalent toExtension (R4: type additional codes)Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R5 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.