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

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

ConceptMap: R4CapabilityStatementElementMapToR3

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

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

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


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

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1Codes from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2
CapabilityStatement.metametais equivalent toCapabilityStatement.metaCapabilityStatement.metaElement `CapabilityStatement.meta` is mapped to FHIR STU3 element `CapabilityStatement.meta` as `Equivalent`.
CapabilityStatement.implicitRulesimplicitRulesis equivalent toCapabilityStatement.implicitRulesCapabilityStatement.implicitRulesElement `CapabilityStatement.implicitRules` is mapped to FHIR STU3 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.languagelanguageis equivalent toCapabilityStatement.languageCapabilityStatement.languageElement `CapabilityStatement.language` is mapped to FHIR STU3 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.texttextis equivalent toCapabilityStatement.textCapabilityStatement.textElement `CapabilityStatement.text` is mapped to FHIR STU3 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.containedcontainedis equivalent toCapabilityStatement.containedCapabilityStatement.containedElement `CapabilityStatement.contained` is mapped to FHIR STU3 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.urlurlis equivalent toCapabilityStatement.urlCapabilityStatement.urlElement `CapabilityStatement.url` is mapped to FHIR STU3 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.versionversionis equivalent toCapabilityStatement.versionCapabilityStatement.versionElement `CapabilityStatement.version` is mapped to FHIR STU3 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.namenameis equivalent toCapabilityStatement.nameCapabilityStatement.nameElement `CapabilityStatement.name` is mapped to FHIR STU3 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.titletitleis equivalent toCapabilityStatement.titleCapabilityStatement.titleElement `CapabilityStatement.title` is mapped to FHIR STU3 element `CapabilityStatement.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
CapabilityStatement.statusstatusis equivalent toCapabilityStatement.statusCapabilityStatement.statusElement `CapabilityStatement.status` is mapped to FHIR STU3 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.experimentalexperimentalis equivalent toCapabilityStatement.experimentalCapabilityStatement.experimentalElement `CapabilityStatement.experimental` is mapped to FHIR STU3 element `CapabilityStatement.experimental` as `Equivalent`. Allows filtering of capability statements that are appropriate for use versus not.
CapabilityStatement.datedateis equivalent toCapabilityStatement.dateCapabilityStatement.dateElement `CapabilityStatement.date` is mapped to FHIR STU3 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.publisherpublisheris equivalent toCapabilityStatement.publisherCapabilityStatement.publisherElement `CapabilityStatement.publisher` is mapped to FHIR STU3 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.contactcontactis equivalent toCapabilityStatement.contactCapabilityStatement.contactElement `CapabilityStatement.contact` is mapped to FHIR STU3 element `CapabilityStatement.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
CapabilityStatement.descriptiondescriptionis equivalent toCapabilityStatement.descriptionCapabilityStatement.descriptionElement `CapabilityStatement.description` is mapped to FHIR STU3 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.useContextuseContextis equivalent toCapabilityStatement.useContextCapabilityStatement.useContextElement `CapabilityStatement.useContext` is mapped to FHIR STU3 element `CapabilityStatement.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
CapabilityStatement.jurisdictionjurisdictionis equivalent toCapabilityStatement.jurisdictionCapabilityStatement.jurisdictionElement `CapabilityStatement.jurisdiction` is mapped to FHIR STU3 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.purposepurposeis equivalent toCapabilityStatement.purposeCapabilityStatement.purposeElement `CapabilityStatement.purpose` is mapped to FHIR STU3 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.copyrightcopyrightis equivalent toCapabilityStatement.copyrightCapabilityStatement.copyrightElement `CapabilityStatement.copyright` is mapped to FHIR STU3 element `CapabilityStatement.copyright` as `Equivalent`.
CapabilityStatement.kindkindis equivalent toCapabilityStatement.kindCapabilityStatement.kindElement `CapabilityStatement.kind` is mapped to FHIR STU3 element `CapabilityStatement.kind` as `Equivalent`.
CapabilityStatement.instantiatesinstantiatesis equivalent toCapabilityStatement.instantiatesCapabilityStatement.instantiatesElement `CapabilityStatement.instantiates` is mapped to FHIR STU3 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.softwaresoftwaremaps to wider conceptCapabilityStatement.softwareCapabilityStatement.softwareElement `CapabilityStatement.software` is mapped to FHIR STU3 element `CapabilityStatement.software` as `Equivalent`.
CapabilityStatement.software.namenameis equivalent toCapabilityStatement.software.nameCapabilityStatement.software.nameElement `CapabilityStatement.software.name` is mapped to FHIR STU3 element `CapabilityStatement.software.name` as `Equivalent`.
CapabilityStatement.software.versionversionis equivalent toCapabilityStatement.software.versionCapabilityStatement.software.versionElement `CapabilityStatement.software.version` is mapped to FHIR STU3 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.releaseDatereleaseDateis equivalent toCapabilityStatement.software.releaseDateCapabilityStatement.software.releaseDateElement `CapabilityStatement.software.releaseDate` is mapped to FHIR STU3 element `CapabilityStatement.software.releaseDate` as `Equivalent`.
CapabilityStatement.implementationimplementationmaps to wider conceptCapabilityStatement.implementationCapabilityStatement.implementationElement `CapabilityStatement.implementation` is mapped to FHIR STU3 element `CapabilityStatement.implementation` as `Equivalent`.
CapabilityStatement.implementation.descriptiondescriptionis equivalent toCapabilityStatement.implementation.descriptionCapabilityStatement.implementation.descriptionElement `CapabilityStatement.implementation.description` is mapped to FHIR STU3 element `CapabilityStatement.implementation.description` as `Equivalent`.
CapabilityStatement.implementation.urlurlis equivalent toCapabilityStatement.implementation.urlCapabilityStatement.implementation.urlElement `CapabilityStatement.implementation.url` is mapped to FHIR STU3 element `CapabilityStatement.implementation.url` as `Equivalent`.
CapabilityStatement.fhirVersionfhirVersionmaps to wider conceptCapabilityStatement.fhirVersionCapabilityStatement.fhirVersionElement `CapabilityStatement.fhirVersion` is mapped to FHIR STU3 element `CapabilityStatement.fhirVersion` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.fhirVersion` do not cover the following types: code. The mappings for `CapabilityStatement.fhirVersion` do not cover the following types based on type expansion: value. 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.formatformatis equivalent toCapabilityStatement.formatCapabilityStatement.formatElement `CapabilityStatement.format` is mapped to FHIR STU3 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.patchFormatpatchFormatis equivalent toCapabilityStatement.patchFormatCapabilityStatement.patchFormatElement `CapabilityStatement.patchFormat` is mapped to FHIR STU3 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.implementationGuideimplementationGuideis equivalent toCapabilityStatement.implementationGuideCapabilityStatement.implementationGuideElement `CapabilityStatement.implementationGuide` is mapped to FHIR STU3 element `CapabilityStatement.implementationGuide` as `Equivalent`.
CapabilityStatement.restrestmaps to wider conceptCapabilityStatement.restCapabilityStatement.restElement `CapabilityStatement.rest` is mapped to FHIR STU3 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.modemodeis equivalent toCapabilityStatement.rest.modeCapabilityStatement.rest.modeElement `CapabilityStatement.rest.mode` is mapped to FHIR STU3 element `CapabilityStatement.rest.mode` as `Equivalent`.
CapabilityStatement.rest.documentationdocumentationis equivalent toCapabilityStatement.rest.documentationCapabilityStatement.rest.documentationElement `CapabilityStatement.rest.documentation` is mapped to FHIR STU3 element `CapabilityStatement.rest.documentation` as `Equivalent`.
CapabilityStatement.rest.securitysecuritymaps to wider conceptCapabilityStatement.rest.securityCapabilityStatement.rest.securityElement `CapabilityStatement.rest.security` is mapped to FHIR STU3 element `CapabilityStatement.rest.security` as `Equivalent`.
CapabilityStatement.rest.security.corscorsis equivalent toCapabilityStatement.rest.security.corsCapabilityStatement.rest.security.corsElement `CapabilityStatement.rest.security.cors` is mapped to FHIR STU3 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.serviceserviceis equivalent toCapabilityStatement.rest.security.serviceCapabilityStatement.rest.security.serviceElement `CapabilityStatement.rest.security.service` is mapped to FHIR STU3 element `CapabilityStatement.rest.security.service` as `Equivalent`.
CapabilityStatement.rest.security.descriptiondescriptionis equivalent toCapabilityStatement.rest.security.descriptionCapabilityStatement.rest.security.descriptionElement `CapabilityStatement.rest.security.description` is mapped to FHIR STU3 element `CapabilityStatement.rest.security.description` as `Equivalent`.
CapabilityStatement.rest.resourceresourcemaps to wider conceptCapabilityStatement.rest.resourceCapabilityStatement.rest.resourceElement `CapabilityStatement.rest.resource` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource` as `Equivalent`. Max of one repetition per resource type.
CapabilityStatement.rest.resource.typetypemaps to wider conceptCapabilityStatement.rest.resource.typeCapabilityStatement.rest.resource.typeElement `CapabilityStatement.rest.resource.type` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.type` as `SourceIsBroaderThanTarget`.
CapabilityStatement.rest.resource.profileprofilemaps to wider conceptCapabilityStatement.rest.resource.profileCapabilityStatement.rest.resource.profileElement `CapabilityStatement.rest.resource.profile` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: canonical. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: value. 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.supportedProfilesupportedProfileis related toCapabilityStatement.profileCapabilityStatement.profileElement `CapabilityStatement.rest.resource.supportedProfile` is mapped to FHIR STU3 element `CapabilityStatement.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.supportedProfile` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.resource.supportedProfile` do not cover the following types: canonical. The mappings for `CapabilityStatement.rest.resource.supportedProfile` do not cover the following types based on type expansion: value. 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).
is related toCapabilityStatement.rest.resource.profileCapabilityStatement.rest.resource.profileElement `CapabilityStatement.rest.resource.supportedProfile` is mapped to FHIR STU3 element `CapabilityStatement.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.supportedProfile` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.resource.supportedProfile` do not cover the following types: canonical. The mappings for `CapabilityStatement.rest.resource.supportedProfile` do not cover the following types based on type expansion: value. 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.documentationdocumentationis equivalent toCapabilityStatement.rest.resource.documentationCapabilityStatement.rest.resource.documentationElement `CapabilityStatement.rest.resource.documentation` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.documentation` as `Equivalent`.
CapabilityStatement.rest.resource.interactioninteractionmaps to wider conceptCapabilityStatement.rest.resource.interactionCapabilityStatement.rest.resource.interactionElement `CapabilityStatement.rest.resource.interaction` is mapped to FHIR STU3 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.codecodeis equivalent toCapabilityStatement.rest.resource.interaction.codeCapabilityStatement.rest.resource.interaction.codeElement `CapabilityStatement.rest.resource.interaction.code` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.interaction.code` as `Equivalent`.
CapabilityStatement.rest.resource.interaction.documentationdocumentationis equivalent toCapabilityStatement.rest.resource.interaction.documentationCapabilityStatement.rest.resource.interaction.documentationElement `CapabilityStatement.rest.resource.interaction.documentation` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`.
CapabilityStatement.rest.resource.versioningversioningis equivalent toCapabilityStatement.rest.resource.versioningCapabilityStatement.rest.resource.versioningElement `CapabilityStatement.rest.resource.versioning` is mapped to FHIR STU3 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.readHistoryreadHistoryis equivalent toCapabilityStatement.rest.resource.readHistoryCapabilityStatement.rest.resource.readHistoryElement `CapabilityStatement.rest.resource.readHistory` is mapped to FHIR STU3 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.updateCreateupdateCreateis equivalent toCapabilityStatement.rest.resource.updateCreateCapabilityStatement.rest.resource.updateCreateElement `CapabilityStatement.rest.resource.updateCreate` is mapped to FHIR STU3 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.conditionalCreateconditionalCreateis equivalent toCapabilityStatement.rest.resource.conditionalCreateCapabilityStatement.rest.resource.conditionalCreateElement `CapabilityStatement.rest.resource.conditionalCreate` is mapped to FHIR STU3 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.conditionalReadconditionalReadis equivalent toCapabilityStatement.rest.resource.conditionalReadCapabilityStatement.rest.resource.conditionalReadElement `CapabilityStatement.rest.resource.conditionalRead` is mapped to FHIR STU3 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.conditionalUpdateconditionalUpdateis equivalent toCapabilityStatement.rest.resource.conditionalUpdateCapabilityStatement.rest.resource.conditionalUpdateElement `CapabilityStatement.rest.resource.conditionalUpdate` is mapped to FHIR STU3 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.conditionalDeleteconditionalDeleteis equivalent toCapabilityStatement.rest.resource.conditionalDeleteCapabilityStatement.rest.resource.conditionalDeleteElement `CapabilityStatement.rest.resource.conditionalDelete` is mapped to FHIR STU3 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.referencePolicyreferencePolicyis equivalent toCapabilityStatement.rest.resource.referencePolicyCapabilityStatement.rest.resource.referencePolicyElement `CapabilityStatement.rest.resource.referencePolicy` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.referencePolicy` as `Equivalent`.
CapabilityStatement.rest.resource.searchIncludesearchIncludeis equivalent toCapabilityStatement.rest.resource.searchIncludeCapabilityStatement.rest.resource.searchIncludeElement `CapabilityStatement.rest.resource.searchInclude` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`. If this list is empty, the server does not support includes.
CapabilityStatement.rest.resource.searchRevIncludesearchRevIncludeis equivalent toCapabilityStatement.rest.resource.searchRevIncludeCapabilityStatement.rest.resource.searchRevIncludeElement `CapabilityStatement.rest.resource.searchRevInclude` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.searchRevInclude` as `Equivalent`. If this list is empty, the server does not support reverse includes.
CapabilityStatement.rest.resource.searchParamsearchParammaps to wider conceptCapabilityStatement.rest.resource.searchParamCapabilityStatement.rest.resource.searchParamElement `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR STU3 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.namenameis equivalent toCapabilityStatement.rest.resource.searchParam.nameCapabilityStatement.rest.resource.searchParam.nameElement `CapabilityStatement.rest.resource.searchParam.name` is mapped to FHIR STU3 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.definitiondefinitionis equivalent toCapabilityStatement.rest.resource.searchParam.definitionCapabilityStatement.rest.resource.searchParam.definitionElement `CapabilityStatement.rest.resource.searchParam.definition` is mapped to FHIR STU3 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.typetypemaps to wider conceptCapabilityStatement.rest.resource.searchParam.typeCapabilityStatement.rest.resource.searchParam.typeElement `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.searchParam.type` as `SourceIsBroaderThanTarget`. 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.documentationdocumentationis equivalent toCapabilityStatement.rest.resource.searchParam.documentationCapabilityStatement.rest.resource.searchParam.documentationElement `CapabilityStatement.rest.resource.searchParam.documentation` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`.
CapabilityStatement.rest.resource.operationoperationis related toCapabilityStatement.rest.operationCapabilityStatement.rest.operationElement `CapabilityStatement.rest.resource.operation` is mapped to FHIR STU3 element `CapabilityStatement.rest.operation` as `SourceIsNarrowerThanTarget`. 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.namenameis equivalent toCapabilityStatement.rest.operation.nameCapabilityStatement.rest.operation.nameElement `CapabilityStatement.rest.resource.operation.name` is mapped to FHIR STU3 element `CapabilityStatement.rest.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.definitiondefinitionmaps to wider conceptCapabilityStatement.rest.operation.definitionCapabilityStatement.rest.operation.definitionElement `CapabilityStatement.rest.resource.operation.definition` is mapped to FHIR STU3 element `CapabilityStatement.rest.operation.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.resource.operation.definition` do not cover the following types: canonical. The mappings for `CapabilityStatement.rest.resource.operation.definition` do not cover the following types based on type expansion: value. This can be used to build an HTML form to invoke the operation, for instance.
CapabilityStatement.rest.interactioninteractionmaps to wider conceptCapabilityStatement.rest.interactionCapabilityStatement.rest.interactionElement `CapabilityStatement.rest.interaction` is mapped to FHIR STU3 element `CapabilityStatement.rest.interaction` as `Equivalent`.
CapabilityStatement.rest.interaction.codecodeis equivalent toCapabilityStatement.rest.interaction.codeCapabilityStatement.rest.interaction.codeElement `CapabilityStatement.rest.interaction.code` is mapped to FHIR STU3 element `CapabilityStatement.rest.interaction.code` as `Equivalent`.
CapabilityStatement.rest.interaction.documentationdocumentationis equivalent toCapabilityStatement.rest.interaction.documentationCapabilityStatement.rest.interaction.documentationElement `CapabilityStatement.rest.interaction.documentation` is mapped to FHIR STU3 element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`.
CapabilityStatement.rest.searchParamsearchParamis equivalent toCapabilityStatement.rest.searchParamCapabilityStatement.rest.searchParamElement `CapabilityStatement.rest.searchParam` is mapped to FHIR STU3 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.operationoperationis equivalent toCapabilityStatement.rest.operationCapabilityStatement.rest.operationElement `CapabilityStatement.rest.operation` is mapped to FHIR STU3 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.compartmentcompartmentis equivalent toCapabilityStatement.rest.compartmentCapabilityStatement.rest.compartmentElement `CapabilityStatement.rest.compartment` is mapped to FHIR STU3 element `CapabilityStatement.rest.compartment` as `Equivalent`. At present, the only defined compartments are at [CompartmentDefinition](https://hl7.org/fhir/compartmentdefinition.html).
CapabilityStatement.messagingmessagingmaps to wider conceptCapabilityStatement.messagingCapabilityStatement.messagingElement `CapabilityStatement.messaging` is mapped to FHIR STU3 element `CapabilityStatement.messaging` as `Equivalent`. Multiple repetitions allow the documentation of multiple endpoints per solution.
CapabilityStatement.messaging.endpointendpointmaps to wider conceptCapabilityStatement.messaging.endpointCapabilityStatement.messaging.endpointElement `CapabilityStatement.messaging.endpoint` is mapped to FHIR STU3 element `CapabilityStatement.messaging.endpoint` as `Equivalent`.
CapabilityStatement.messaging.endpoint.protocolprotocolis equivalent toCapabilityStatement.messaging.endpoint.protocolCapabilityStatement.messaging.endpoint.protocolElement `CapabilityStatement.messaging.endpoint.protocol` is mapped to FHIR STU3 element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`.
CapabilityStatement.messaging.endpoint.addressaddressis equivalent toCapabilityStatement.messaging.endpoint.addressCapabilityStatement.messaging.endpoint.addressElement `CapabilityStatement.messaging.endpoint.address` is mapped to FHIR STU3 element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`.
CapabilityStatement.messaging.reliableCachereliableCacheis equivalent toCapabilityStatement.messaging.reliableCacheCapabilityStatement.messaging.reliableCacheElement `CapabilityStatement.messaging.reliableCache` is mapped to FHIR STU3 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.documentationdocumentationis equivalent toCapabilityStatement.messaging.documentationCapabilityStatement.messaging.documentationElement `CapabilityStatement.messaging.documentation` is mapped to FHIR STU3 element `CapabilityStatement.messaging.documentation` as `Equivalent`.
CapabilityStatement.messaging.supportedMessagesupportedMessagemaps to wider conceptCapabilityStatement.messaging.supportedMessageCapabilityStatement.messaging.supportedMessageElement `CapabilityStatement.messaging.supportedMessage` is mapped to FHIR STU3 element `CapabilityStatement.messaging.supportedMessage` as `Equivalent`. This is a proposed alternative to the messaging.event structure.
CapabilityStatement.messaging.supportedMessage.modemodeis equivalent toCapabilityStatement.messaging.supportedMessage.modeCapabilityStatement.messaging.supportedMessage.modeElement `CapabilityStatement.messaging.supportedMessage.mode` is mapped to FHIR STU3 element `CapabilityStatement.messaging.supportedMessage.mode` as `Equivalent`.
CapabilityStatement.messaging.supportedMessage.definitiondefinitionmaps to wider conceptCapabilityStatement.messaging.supportedMessage.definitionCapabilityStatement.messaging.supportedMessage.definitionElement `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR STU3 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: canonical. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: value.
CapabilityStatement.documentdocumentmaps to wider conceptCapabilityStatement.documentCapabilityStatement.documentElement `CapabilityStatement.document` is mapped to FHIR STU3 element `CapabilityStatement.document` as `Equivalent`.
CapabilityStatement.document.modemodeis equivalent toCapabilityStatement.document.modeCapabilityStatement.document.modeElement `CapabilityStatement.document.mode` is mapped to FHIR STU3 element `CapabilityStatement.document.mode` as `Equivalent`.
CapabilityStatement.document.documentationdocumentationis equivalent toCapabilityStatement.document.documentationCapabilityStatement.document.documentationElement `CapabilityStatement.document.documentation` is mapped to FHIR STU3 element `CapabilityStatement.document.documentation` as `Equivalent`.
CapabilityStatement.document.profileprofilemaps to wider conceptCapabilityStatement.document.profileCapabilityStatement.document.profileElement `CapabilityStatement.document.profile` is mapped to FHIR STU3 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.document.profile` do not cover the following types: canonical. The mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: value. The profile is actually on the Bundle.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: Canonical URL of another capability statement this adds to (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.imports (imports)maps to wider conceptExtension (R4: Canonical URL of another capability statement this adds to (new))Element `CapabilityStatement.imports` has a context of CapabilityStatement based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.imports` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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).

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: Organization that manages the data (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.implementation.custodian (custodian)maps to wider conceptExtension (R4: Organization that manages the data (new))Element `CapabilityStatement.implementation.custodian` has a context of CapabilityStatement.implementation based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.implementation.custodian` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: FHIR Version the system supports additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.fhirVersion (fhirVersion)is equivalent toExtension (R4: FHIR Version the system supports additional types)Element `CapabilityStatement.fhirVersion` is mapped to FHIR STU3 element `CapabilityStatement.fhirVersion` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.fhirVersion` do not cover the following types: code. The mappings for `CapabilityStatement.fhirVersion` do not cover the following types based on type expansion: value. 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.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: typeversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.rest.resource.type (type)is equivalent toExtension (R4: type)Element `CapabilityStatement.rest.resource.type` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.type` as `SourceIsBroaderThanTarget`.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: profile additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.rest.resource.profile (profile)is equivalent toExtension (R4: profile additional types)Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: canonical. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: value. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: Profiles for use cases supported additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.rest.resource.supportedProfile (supportedProfile)maps to wider conceptExtension (R4: Profiles for use cases supported additional types)Element `CapabilityStatement.rest.resource.supportedProfile` is mapped to FHIR STU3 element `CapabilityStatement.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.supportedProfile` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.resource.supportedProfile` do not cover the following types: canonical. The mappings for `CapabilityStatement.rest.resource.supportedProfile` do not cover the following types based on type expansion: value. 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).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: number | date | string | token | reference | composite | quantity | uri | specialversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.rest.resource.searchParam.type (type)is equivalent toExtension (R4: number | date | string | token | reference | composite | quantity | uri | special)Element `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR STU3 element `CapabilityStatement.rest.resource.searchParam.type` as `SourceIsBroaderThanTarget`. 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.

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: definition additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.rest.resource.operation.definition (definition)maps to wider conceptExtension (R4: definition additional types)Element `CapabilityStatement.rest.resource.operation.definition` is mapped to FHIR STU3 element `CapabilityStatement.rest.operation.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.resource.operation.definition` do not cover the following types: canonical. The mappings for `CapabilityStatement.rest.resource.operation.definition` do not cover the following types based on type expansion: value. This can be used to build an HTML form to invoke the operation, for instance.

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: Specific details about operation behavior (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.rest.resource.operation.documentation (documentation)maps to wider conceptExtension (R4: Specific details about operation behavior (new))Element `CapabilityStatement.rest.resource.operation.documentation` has a context of CapabilityStatement.rest.operation based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.resource.operation.documentation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: definition additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.messaging.supportedMessage.definition (definition)is equivalent toExtension (R4: definition additional types)Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR STU3 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: canonical. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: value.

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|4.0.1 to R4: Constraint on the resources used in the document additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CapabilityStatement.document.profile (profile)is equivalent toExtension (R4: Constraint on the resources used in the document additional types)Element `CapabilityStatement.document.profile` is mapped to FHIR STU3 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.document.profile` do not cover the following types: canonical. The mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: value. The profile is actually on the Bundle.