Generated Narrative: ConceptMap R3-CapabilityStatement-element-map-to-R4 Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to CapabilityStatementversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 Codes from CapabilityStatement CapabilityStatement.meta meta is equivalent to CapabilityStatement.meta CapabilityStatement.meta Element `CapabilityStatement.meta` is mapped to FHIR R4 element `CapabilityStatement.meta` as `Equivalent`. CapabilityStatement.implicitRules implicitRules is equivalent to CapabilityStatement.implicitRules CapabilityStatement.implicitRules Element `CapabilityStatement.implicitRules` is mapped to FHIR R4 element `CapabilityStatement.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. CapabilityStatement.language language is equivalent to CapabilityStatement.language CapabilityStatement.language Element `CapabilityStatement.language` is mapped to FHIR R4 element `CapabilityStatement.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations 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 to CapabilityStatement.text CapabilityStatement.text Element `CapabilityStatement.text` is mapped to FHIR R4 element `CapabilityStatement.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. CapabilityStatement.contained contained is equivalent to CapabilityStatement.contained CapabilityStatement.contained 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. CapabilityStatement.url url is equivalent to CapabilityStatement.url CapabilityStatement.url 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. CapabilityStatement.version version is equivalent to CapabilityStatement.version CapabilityStatement.version Element `CapabilityStatement.version` is mapped to FHIR R4 element `CapabilityStatement.version` as `Equivalent`. There may be different capability statement instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the capability statement with the format [url]|[version]. CapabilityStatement.name name is equivalent to CapabilityStatement.name CapabilityStatement.name Element `CapabilityStatement.name` is mapped to FHIR R4 element `CapabilityStatement.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly. CapabilityStatement.title title is equivalent to CapabilityStatement.title CapabilityStatement.title 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. CapabilityStatement.status status is equivalent to CapabilityStatement.status CapabilityStatement.status Element `CapabilityStatement.status` is mapped to FHIR R4 element `CapabilityStatement.status` as `Equivalent`. Allows filtering of capability statements that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired capability statement without due consideration. This is not intended for use with actual capability statements, but where capability statements are used to describe possible or desired systems. CapabilityStatement.experimental experimental is equivalent to CapabilityStatement.experimental CapabilityStatement.experimental Element `CapabilityStatement.experimental` is mapped to FHIR R4 element `CapabilityStatement.experimental` as `Equivalent`. Allows filtering of capability statement that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental capability statement in production. CapabilityStatement.date date is equivalent to CapabilityStatement.date CapabilityStatement.date Element `CapabilityStatement.date` is mapped to FHIR R4 element `CapabilityStatement.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the capability statement. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. CapabilityStatement.publisher publisher is equivalent to CapabilityStatement.publisher CapabilityStatement.publisher 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. CapabilityStatement.contact contact is equivalent to CapabilityStatement.contact CapabilityStatement.contact 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. CapabilityStatement.description description is equivalent to CapabilityStatement.description CapabilityStatement.description Element `CapabilityStatement.description` is mapped to FHIR R4 element `CapabilityStatement.description` as `Equivalent`. This description can be used to capture details such as why the capability statement was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the capability statement as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created). This does not need to be populated if the description is adequately implied by the software or implementation details. CapabilityStatement.useContext useContext is equivalent to CapabilityStatement.useContext CapabilityStatement.useContext Element `CapabilityStatement.useContext` is mapped to FHIR R4 element `CapabilityStatement.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. CapabilityStatement.jurisdiction jurisdiction is equivalent to CapabilityStatement.jurisdiction CapabilityStatement.jurisdiction Element `CapabilityStatement.jurisdiction` is mapped to FHIR R4 element `CapabilityStatement.jurisdiction` as `Equivalent`. It may be possible for the capability statement to be used in jurisdictions other than those for which it was originally designed or intended. CapabilityStatement.purpose purpose is equivalent to CapabilityStatement.purpose CapabilityStatement.purpose 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. CapabilityStatement.copyright copyright is equivalent to CapabilityStatement.copyright CapabilityStatement.copyright Element `CapabilityStatement.copyright` is mapped to FHIR R4 element `CapabilityStatement.copyright` as `Equivalent`. CapabilityStatement.kind kind is equivalent to CapabilityStatement.kind CapabilityStatement.kind Element `CapabilityStatement.kind` is mapped to FHIR R4 element `CapabilityStatement.kind` as `Equivalent`. CapabilityStatement.instantiates instantiates is equivalent to CapabilityStatement.instantiates CapabilityStatement.instantiates 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. CapabilityStatement.software software maps to wider concept CapabilityStatement.software CapabilityStatement.software Element `CapabilityStatement.software` is mapped to FHIR R4 element `CapabilityStatement.software` as `Equivalent`. CapabilityStatement.software.name name is equivalent to CapabilityStatement.software.name CapabilityStatement.software.name Element `CapabilityStatement.software.name` is mapped to FHIR R4 element `CapabilityStatement.software.name` as `Equivalent`. CapabilityStatement.software.version version is equivalent to CapabilityStatement.software.version CapabilityStatement.software.version 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. CapabilityStatement.software.releaseDate releaseDate is equivalent to CapabilityStatement.software.releaseDate CapabilityStatement.software.releaseDate Element `CapabilityStatement.software.releaseDate` is mapped to FHIR R4 element `CapabilityStatement.software.releaseDate` as `Equivalent`. CapabilityStatement.implementation implementation maps to wider concept CapabilityStatement.implementation CapabilityStatement.implementation Element `CapabilityStatement.implementation` is mapped to FHIR R4 element `CapabilityStatement.implementation` as `Equivalent`. CapabilityStatement.implementation.description description is equivalent to CapabilityStatement.implementation.description CapabilityStatement.implementation.description Element `CapabilityStatement.implementation.description` is mapped to FHIR R4 element `CapabilityStatement.implementation.description` as `Equivalent`. CapabilityStatement.implementation.url url is equivalent to CapabilityStatement.implementation.url CapabilityStatement.implementation.url Element `CapabilityStatement.implementation.url` is mapped to FHIR R4 element `CapabilityStatement.implementation.url` as `Equivalent`. CapabilityStatement.fhirVersion fhirVersion is equivalent to CapabilityStatement.fhirVersion CapabilityStatement.fhirVersion Element `CapabilityStatement.fhirVersion` is mapped to FHIR R4 element `CapabilityStatement.fhirVersion` as `SourceIsNarrowerThanTarget`. CapabilityStatement.format format is equivalent to CapabilityStatement.format CapabilityStatement.format 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. CapabilityStatement.patchFormat patchFormat is equivalent to CapabilityStatement.patchFormat CapabilityStatement.patchFormat 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. CapabilityStatement.implementationGuide implementationGuide is equivalent to CapabilityStatement.implementationGuide CapabilityStatement.implementationGuide Element `CapabilityStatement.implementationGuide` is mapped to FHIR R4 element `CapabilityStatement.implementationGuide` as `Equivalent`. CapabilityStatement.profile profile maps to wider concept CapabilityStatement.rest.resource.supportedProfile CapabilityStatement.rest.resource.supportedProfile Element `CapabilityStatement.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.profile` do not cover the following types based on type expansion: display, identifier, reference. Supported profiles are different than the profiles that apply to a particular resource in rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that does? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile). Typically, supported profiles cross resource types to describe a network of related resources, so they are listed here rather than by resource. However, they do not need to describe more than one resource. CapabilityStatement.rest rest maps to wider concept CapabilityStatement.rest CapabilityStatement.rest 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). CapabilityStatement.rest.mode mode is equivalent to CapabilityStatement.rest.mode CapabilityStatement.rest.mode Element `CapabilityStatement.rest.mode` is mapped to FHIR R4 element `CapabilityStatement.rest.mode` as `Equivalent`. CapabilityStatement.rest.documentation documentation is equivalent to CapabilityStatement.rest.documentation CapabilityStatement.rest.documentation Element `CapabilityStatement.rest.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.documentation` as `Equivalent`. CapabilityStatement.rest.security security maps to wider concept CapabilityStatement.rest.security CapabilityStatement.rest.security Element `CapabilityStatement.rest.security` is mapped to FHIR R4 element `CapabilityStatement.rest.security` as `Equivalent`. CapabilityStatement.rest.security.cors cors is equivalent to CapabilityStatement.rest.security.cors CapabilityStatement.rest.security.cors 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. CapabilityStatement.rest.security.service service is equivalent to CapabilityStatement.rest.security.service CapabilityStatement.rest.security.service Element `CapabilityStatement.rest.security.service` is mapped to FHIR R4 element `CapabilityStatement.rest.security.service` as `Equivalent`. CapabilityStatement.rest.security.description description is equivalent to CapabilityStatement.rest.security.description CapabilityStatement.rest.security.description Element `CapabilityStatement.rest.security.description` is mapped to FHIR R4 element `CapabilityStatement.rest.security.description` as `Equivalent`. CapabilityStatement.rest.resource resource maps to wider concept CapabilityStatement.rest.resource CapabilityStatement.rest.resource Element `CapabilityStatement.rest.resource` is mapped to FHIR R4 element `CapabilityStatement.rest.resource` as `Equivalent`. Max of one repetition per resource type. CapabilityStatement.rest.resource.type type is equivalent to CapabilityStatement.rest.resource.type CapabilityStatement.rest.resource.type Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.type` as `SourceIsNarrowerThanTarget`. The mappings for `CapabilityStatement.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target. CapabilityStatement.rest.resource.profile profile is related to CapabilityStatement.rest.resource.profile CapabilityStatement.rest.resource.profile Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, reference. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system. is related to CapabilityStatement.rest.resource.supportedProfile CapabilityStatement.rest.resource.supportedProfile Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, reference. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system. CapabilityStatement.rest.resource.documentation documentation is equivalent to CapabilityStatement.rest.resource.documentation CapabilityStatement.rest.resource.documentation Element `CapabilityStatement.rest.resource.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.documentation` as `Equivalent`. CapabilityStatement.rest.resource.interaction interaction maps to wider concept CapabilityStatement.rest.resource.interaction CapabilityStatement.rest.resource.interaction Element `CapabilityStatement.rest.resource.interaction` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction` as `Equivalent`. CapabilityStatement.rest.resource.interaction.code code is equivalent to CapabilityStatement.rest.resource.interaction.code CapabilityStatement.rest.resource.interaction.code Element `CapabilityStatement.rest.resource.interaction.code` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction.code` as `Equivalent`. CapabilityStatement.rest.resource.interaction.documentation documentation is equivalent to CapabilityStatement.rest.resource.interaction.documentation CapabilityStatement.rest.resource.interaction.documentation Element `CapabilityStatement.rest.resource.interaction.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`. CapabilityStatement.rest.resource.versioning versioning is equivalent to CapabilityStatement.rest.resource.versioning CapabilityStatement.rest.resource.versioning 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. CapabilityStatement.rest.resource.readHistory readHistory is equivalent to CapabilityStatement.rest.resource.readHistory CapabilityStatement.rest.resource.readHistory 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. CapabilityStatement.rest.resource.updateCreate updateCreate is equivalent to CapabilityStatement.rest.resource.updateCreate CapabilityStatement.rest.resource.updateCreate 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. CapabilityStatement.rest.resource.conditionalCreate conditionalCreate is equivalent to CapabilityStatement.rest.resource.conditionalCreate CapabilityStatement.rest.resource.conditionalCreate 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. CapabilityStatement.rest.resource.conditionalRead conditionalRead is equivalent to CapabilityStatement.rest.resource.conditionalRead CapabilityStatement.rest.resource.conditionalRead 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. CapabilityStatement.rest.resource.conditionalUpdate conditionalUpdate is equivalent to CapabilityStatement.rest.resource.conditionalUpdate CapabilityStatement.rest.resource.conditionalUpdate 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. CapabilityStatement.rest.resource.conditionalDelete conditionalDelete is equivalent to CapabilityStatement.rest.resource.conditionalDelete CapabilityStatement.rest.resource.conditionalDelete 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. CapabilityStatement.rest.resource.referencePolicy referencePolicy is equivalent to CapabilityStatement.rest.resource.referencePolicy CapabilityStatement.rest.resource.referencePolicy Element `CapabilityStatement.rest.resource.referencePolicy` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.referencePolicy` as `Equivalent`. CapabilityStatement.rest.resource.searchInclude searchInclude is equivalent to CapabilityStatement.rest.resource.searchInclude CapabilityStatement.rest.resource.searchInclude Element `CapabilityStatement.rest.resource.searchInclude` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`. If this list is empty, the server does not support includes. CapabilityStatement.rest.resource.searchRevInclude searchRevInclude is equivalent to CapabilityStatement.rest.resource.searchRevInclude CapabilityStatement.rest.resource.searchRevInclude Element `CapabilityStatement.rest.resource.searchRevInclude` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchRevInclude` as `Equivalent`. If this list is empty, the server does not support reverse includes. CapabilityStatement.rest.resource.searchParam searchParam maps to wider concept CapabilityStatement.rest.resource.searchParam CapabilityStatement.rest.resource.searchParam Element `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam` as `Equivalent`. CapabilityStatement.rest.resource.searchParam.name name is equivalent to CapabilityStatement.rest.resource.searchParam.name CapabilityStatement.rest.resource.searchParam.name 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. CapabilityStatement.rest.resource.searchParam.definition definition is equivalent to CapabilityStatement.rest.resource.searchParam.definition CapabilityStatement.rest.resource.searchParam.definition 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. CapabilityStatement.rest.resource.searchParam.type type is equivalent to CapabilityStatement.rest.resource.searchParam.type CapabilityStatement.rest.resource.searchParam.type Element `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.type` as `SourceIsNarrowerThanTarget`. The mappings for `CapabilityStatement.rest.resource.searchParam.type` do not allow expression of the necessary codes, per the bindings on the source and target. While this can be looked up from the definition, it is included here as a convenience for systems that autogenerate a query interface based on the server capability statement. It SHALL be the same as the type in the search parameter definition. CapabilityStatement.rest.resource.searchParam.documentation documentation is equivalent to CapabilityStatement.rest.resource.searchParam.documentation CapabilityStatement.rest.resource.searchParam.documentation Element `CapabilityStatement.rest.resource.searchParam.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`. CapabilityStatement.rest.interaction interaction maps to wider concept CapabilityStatement.rest.interaction CapabilityStatement.rest.interaction Element `CapabilityStatement.rest.interaction` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction` as `Equivalent`. CapabilityStatement.rest.interaction.code code is equivalent to CapabilityStatement.rest.interaction.code CapabilityStatement.rest.interaction.code Element `CapabilityStatement.rest.interaction.code` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction.code` as `Equivalent`. CapabilityStatement.rest.interaction.documentation documentation is equivalent to CapabilityStatement.rest.interaction.documentation CapabilityStatement.rest.interaction.documentation Element `CapabilityStatement.rest.interaction.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`. CapabilityStatement.rest.searchParam searchParam is equivalent to CapabilityStatement.rest.searchParam CapabilityStatement.rest.searchParam Element `CapabilityStatement.rest.searchParam` is mapped to FHIR R4 element `CapabilityStatement.rest.searchParam` as `Equivalent`. Typically, the only search parameters supported for all searchse are those that apply to all resources - tags, profiles, text search etc. CapabilityStatement.rest.operation operation is related to CapabilityStatement.rest.operation CapabilityStatement.rest.operation Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.operation` as `Equivalent`. is related to CapabilityStatement.rest.resource.operation CapabilityStatement.rest.resource.operation Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.operation` as `Equivalent`. CapabilityStatement.rest.operation.name name is equivalent to CapabilityStatement.rest.resource.operation.name CapabilityStatement.rest.resource.operation.name Element `CapabilityStatement.rest.operation.name` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.name` as `Equivalent`. The name here SHOULD be the same as the name in the definition, unless there is a name clash and the name cannot be used. The name does not include the "$" portion that is always included in the URL. CapabilityStatement.rest.operation.definition definition maps to wider concept CapabilityStatement.rest.resource.operation.definition CapabilityStatement.rest.resource.operation.definition Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types based on type expansion: display, identifier, reference. This can be used to build an HTML form to invoke the operation, for instance. CapabilityStatement.rest.compartment compartment is equivalent to CapabilityStatement.rest.compartment CapabilityStatement.rest.compartment 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). CapabilityStatement.messaging messaging maps to wider concept CapabilityStatement.messaging CapabilityStatement.messaging Element `CapabilityStatement.messaging` is mapped to FHIR R4 element `CapabilityStatement.messaging` as `Equivalent`. Multiple repetitions allow the documentation of multiple endpoints per solution. CapabilityStatement.messaging.endpoint endpoint maps to wider concept CapabilityStatement.messaging.endpoint CapabilityStatement.messaging.endpoint Element `CapabilityStatement.messaging.endpoint` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint` as `Equivalent`. CapabilityStatement.messaging.endpoint.protocol protocol is equivalent to CapabilityStatement.messaging.endpoint.protocol CapabilityStatement.messaging.endpoint.protocol Element `CapabilityStatement.messaging.endpoint.protocol` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`. CapabilityStatement.messaging.endpoint.address address is equivalent to CapabilityStatement.messaging.endpoint.address CapabilityStatement.messaging.endpoint.address Element `CapabilityStatement.messaging.endpoint.address` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`. CapabilityStatement.messaging.reliableCache reliableCache is equivalent to CapabilityStatement.messaging.reliableCache CapabilityStatement.messaging.reliableCache 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. CapabilityStatement.messaging.documentation documentation is equivalent to CapabilityStatement.messaging.documentation CapabilityStatement.messaging.documentation Element `CapabilityStatement.messaging.documentation` is mapped to FHIR R4 element `CapabilityStatement.messaging.documentation` as `Equivalent`. CapabilityStatement.messaging.supportedMessage supportedMessage maps to wider concept CapabilityStatement.messaging.supportedMessage CapabilityStatement.messaging.supportedMessage 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. CapabilityStatement.messaging.supportedMessage.mode mode is equivalent to CapabilityStatement.messaging.supportedMessage.mode CapabilityStatement.messaging.supportedMessage.mode Element `CapabilityStatement.messaging.supportedMessage.mode` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage.mode` as `Equivalent`. CapabilityStatement.messaging.supportedMessage.definition definition maps to wider concept CapabilityStatement.messaging.supportedMessage.definition CapabilityStatement.messaging.supportedMessage.definition Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: display, identifier, reference. CapabilityStatement.document document maps to wider concept CapabilityStatement.document CapabilityStatement.document Element `CapabilityStatement.document` is mapped to FHIR R4 element `CapabilityStatement.document` as `Equivalent`. CapabilityStatement.document.mode mode is equivalent to CapabilityStatement.document.mode CapabilityStatement.document.mode Element `CapabilityStatement.document.mode` is mapped to FHIR R4 element `CapabilityStatement.document.mode` as `Equivalent`. CapabilityStatement.document.documentation documentation is equivalent to CapabilityStatement.document.documentation CapabilityStatement.document.documentation Element `CapabilityStatement.document.documentation` is mapped to FHIR R4 element `CapabilityStatement.document.documentation` as `Equivalent`. CapabilityStatement.document.profile profile maps to wider concept CapabilityStatement.document.profile CapabilityStatement.document.profile Element `CapabilityStatement.document.profile` is mapped to FHIR R4 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.document.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: display, identifier, reference. The first resource is the document resource. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to STU3: no | extensions | elements | both (new)version: 0.1.0) Source Code Relationship Target Code Comment CapabilityStatement.acceptUnknown (acceptUnknown) is equivalent to Extension (STU3: no | extensions | elements | both (new)) Element `CapabilityStatement.acceptUnknown` has a context of CapabilityStatement based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.acceptUnknown` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Unknown elements in a resource can only arise as later versions of the specification are published, because this is the only place where such elements can be defined. Hence accepting unknown elements is about inter-version compatibility. Applications are recommended to accept unknown extensions and elements ('both'), but this is not always possible. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to STU3: profile additional typesversion: 0.1.0) Source Code Relationship Target Code Comment CapabilityStatement.profile (profile) maps to wider concept Extension (STU3: profile additional types) Element `CapabilityStatement.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.profile` do not cover the following types based on type expansion: display, identifier, reference. Supported profiles are different than the profiles that apply to a particular resource in rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that does? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile). Typically, supported profiles cross resource types to describe a network of related resources, so they are listed here rather than by resource. However, they do not need to describe more than one resource. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to STU3: Certificates associated with security profiles (new)version: 0.1.0) Source Code Relationship Target Code Comment CapabilityStatement.rest.security.certificate (certificate) maps to wider concept Extension (STU3: Certificates associated with security profiles (new)) Element `CapabilityStatement.rest.security.certificate` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). CapabilityStatement.rest.security.certificate.type (type) is equivalent to Extension.extension:type (STU3: Mime type for certificates (new)) Element `CapabilityStatement.rest.security.certificate.type` is part of an existing definition because parent element `CapabilityStatement.rest.security.certificate` requires a cross-version extension. Element `CapabilityStatement.rest.security.certificate.type` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). CapabilityStatement.rest.security.certificate.blob (blob) is equivalent to Extension.extension:blob (STU3: Actual certificate (new)) Element `CapabilityStatement.rest.security.certificate.blob` is part of an existing definition because parent element `CapabilityStatement.rest.security.certificate` requires a cross-version extension. Element `CapabilityStatement.rest.security.certificate.blob` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate.blob` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to STU3: Base System profile for all uses of resource additional typesversion: 0.1.0) Source Code Relationship Target Code Comment CapabilityStatement.rest.resource.profile (profile) maps to wider concept Extension (STU3: Base System profile for all uses of resource additional types) Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, reference. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to STU3: definition additional typesversion: 0.1.0) Source Code Relationship Target Code Comment CapabilityStatement.rest.operation.definition (definition) maps to wider concept Extension (STU3: definition additional types) Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types based on type expansion: display, identifier, reference. This can be used to build an HTML form to invoke the operation, for instance. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to STU3: definition additional typesversion: 0.1.0) Source Code Relationship Target Code Comment CapabilityStatement.messaging.supportedMessage.definition (definition) is equivalent to Extension (STU3: definition additional types) Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: display, identifier, reference. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to STU3: Declare support for this event (new)version: 0.1.0) Source Code Relationship Target Code Comment CapabilityStatement.messaging.event (event) maps to wider concept Extension (STU3: Declare support for this event (new)) Element `CapabilityStatement.messaging.event` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The same event may be listed up to two times - once as sender and once as receiver. CapabilityStatement.messaging.event.code (code) is equivalent to Extension.extension:code (STU3: Event type (new)) Element `CapabilityStatement.messaging.event.code` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.code` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). CapabilityStatement.messaging.event.category (category) is equivalent to Extension.extension:category (STU3: Consequence | Currency | Notification (new)) Element `CapabilityStatement.messaging.event.category` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.category` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). CapabilityStatement.messaging.event.mode (mode) is equivalent to Extension.extension:mode (STU3: sender | receiver (new)) Element `CapabilityStatement.messaging.event.mode` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.mode` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). CapabilityStatement.messaging.event.focus (focus) is equivalent to Extension.extension:focus (STU3: Resource that's focus of message (new)) Element `CapabilityStatement.messaging.event.focus` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.focus` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This SHALL be provided if the event type supports multiple different resource types. CapabilityStatement.messaging.event.request (request) is equivalent to Extension.extension:request (STU3: Profile that describes the request (new)) Element `CapabilityStatement.messaging.event.request` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.request` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.request` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). CapabilityStatement.messaging.event.response (response) is equivalent to Extension.extension:response (STU3: Profile that describes the response (new)) Element `CapabilityStatement.messaging.event.response` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.response` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.response` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). CapabilityStatement.messaging.event.documentation (documentation) is equivalent to Extension.extension:documentation (STU3: Endpoint-specific event documentation (new)) Element `CapabilityStatement.messaging.event.documentation` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.documentation` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.documentation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/CapabilityStatement|3.0.2 to STU3: Constraint on a resource used in the document additional typesversion: 0.1.0) Source Code Relationship Target Code Comment CapabilityStatement.document.profile (profile) is equivalent to Extension (STU3: Constraint on a resource used in the document additional types) Element `CapabilityStatement.document.profile` is mapped to FHIR R4 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.document.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: display, identifier, reference. The first resource is the document resource.
Cross-version mapping for FHIR STU3 CapabilityStatement to FHIR R4 CapabilityStatement
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 CapabilityStatement to FHIR R4.
Element `CapabilityStatement.meta` is mapped to FHIR R4 element `CapabilityStatement.meta` as `Equivalent`.
Element `CapabilityStatement.implicitRules` is mapped to FHIR R4 element `CapabilityStatement.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Element `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 `CapabilityStatement.text` is mapped to FHIR R4 element `CapabilityStatement.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
Element `CapabilityStatement.contained` is mapped to FHIR R4 element `CapabilityStatement.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
Element `CapabilityStatement.url` is mapped to FHIR R4 element `CapabilityStatement.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple instances may share the same url if they have a distinct version.
Element `CapabilityStatement.version` is mapped to FHIR R4 element `CapabilityStatement.version` as `Equivalent`. There may be different capability statement instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the capability statement with the format [url]|[version].
Element `CapabilityStatement.name` is mapped to FHIR R4 element `CapabilityStatement.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly.
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.
Element `CapabilityStatement.status` is mapped to FHIR R4 element `CapabilityStatement.status` as `Equivalent`. Allows filtering of capability statements that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired capability statement without due consideration. This is not intended for use with actual capability statements, but where capability statements are used to describe possible or desired systems.
Element `CapabilityStatement.experimental` is mapped to FHIR R4 element `CapabilityStatement.experimental` as `Equivalent`. Allows filtering of capability statement that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental capability statement in production.
Element `CapabilityStatement.date` is mapped to FHIR R4 element `CapabilityStatement.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the capability statement. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
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.
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.
Element `CapabilityStatement.description` is mapped to FHIR R4 element `CapabilityStatement.description` as `Equivalent`. This description can be used to capture details such as why the capability statement was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the capability statement as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created). This does not need to be populated if the description is adequately implied by the software or implementation details.
Element `CapabilityStatement.useContext` is mapped to FHIR R4 element `CapabilityStatement.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.
Element `CapabilityStatement.jurisdiction` is mapped to FHIR R4 element `CapabilityStatement.jurisdiction` as `Equivalent`. It may be possible for the capability statement to be used in jurisdictions other than those for which it was originally designed or intended.
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.
Element `CapabilityStatement.copyright` is mapped to FHIR R4 element `CapabilityStatement.copyright` as `Equivalent`.
Element `CapabilityStatement.kind` is mapped to FHIR R4 element `CapabilityStatement.kind` as `Equivalent`.
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.
Element `CapabilityStatement.software` is mapped to FHIR R4 element `CapabilityStatement.software` as `Equivalent`.
Element `CapabilityStatement.software.name` is mapped to FHIR R4 element `CapabilityStatement.software.name` as `Equivalent`.
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.
Element `CapabilityStatement.software.releaseDate` is mapped to FHIR R4 element `CapabilityStatement.software.releaseDate` as `Equivalent`.
Element `CapabilityStatement.implementation` is mapped to FHIR R4 element `CapabilityStatement.implementation` as `Equivalent`.
Element `CapabilityStatement.implementation.description` is mapped to FHIR R4 element `CapabilityStatement.implementation.description` as `Equivalent`.
Element `CapabilityStatement.implementation.url` is mapped to FHIR R4 element `CapabilityStatement.implementation.url` as `Equivalent`.
Element `CapabilityStatement.fhirVersion` is mapped to FHIR R4 element `CapabilityStatement.fhirVersion` as `SourceIsNarrowerThanTarget`.
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.
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.
Element `CapabilityStatement.implementationGuide` is mapped to FHIR R4 element `CapabilityStatement.implementationGuide` as `Equivalent`.
Element `CapabilityStatement.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.profile` do not cover the following types based on type expansion: display, identifier, reference. Supported profiles are different than the profiles that apply to a particular resource in rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that does? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile). Typically, supported profiles cross resource types to describe a network of related resources, so they are listed here rather than by resource. However, they do not need to describe more than one resource.
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).
Element `CapabilityStatement.rest.mode` is mapped to FHIR R4 element `CapabilityStatement.rest.mode` as `Equivalent`.
Element `CapabilityStatement.rest.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.documentation` as `Equivalent`.
Element `CapabilityStatement.rest.security` is mapped to FHIR R4 element `CapabilityStatement.rest.security` as `Equivalent`.
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.
Element `CapabilityStatement.rest.security.service` is mapped to FHIR R4 element `CapabilityStatement.rest.security.service` as `Equivalent`.
Element `CapabilityStatement.rest.security.description` is mapped to FHIR R4 element `CapabilityStatement.rest.security.description` as `Equivalent`.
Element `CapabilityStatement.rest.resource` is mapped to FHIR R4 element `CapabilityStatement.rest.resource` as `Equivalent`. Max of one repetition per resource type.
Element `CapabilityStatement.rest.resource.type` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.type` as `SourceIsNarrowerThanTarget`. The mappings for `CapabilityStatement.rest.resource.type` do not allow expression of the necessary codes, per the bindings on the source and target.
Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.profile` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.resource.profile` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.supportedProfile` as `RelatedTo`. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.resource.profile` do not cover the following types based on type expansion: display, identifier, reference. The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system.
Element `CapabilityStatement.rest.resource.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.documentation` as `Equivalent`.
Element `CapabilityStatement.rest.resource.interaction` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction` as `Equivalent`.
Element `CapabilityStatement.rest.resource.interaction.code` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction.code` as `Equivalent`.
Element `CapabilityStatement.rest.resource.interaction.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.interaction.documentation` as `Equivalent`.
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.
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.
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.
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.
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.
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.
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.
Element `CapabilityStatement.rest.resource.referencePolicy` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.referencePolicy` as `Equivalent`.
Element `CapabilityStatement.rest.resource.searchInclude` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchInclude` as `Equivalent`. If this list is empty, the server does not support includes.
Element `CapabilityStatement.rest.resource.searchRevInclude` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchRevInclude` as `Equivalent`. If this list is empty, the server does not support reverse includes.
Element `CapabilityStatement.rest.resource.searchParam` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam` as `Equivalent`.
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.
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.
Element `CapabilityStatement.rest.resource.searchParam.type` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.type` as `SourceIsNarrowerThanTarget`. The mappings for `CapabilityStatement.rest.resource.searchParam.type` do not allow expression of the necessary codes, per the bindings on the source and target. While this can be looked up from the definition, it is included here as a convenience for systems that autogenerate a query interface based on the server capability statement. It SHALL be the same as the type in the search parameter definition.
Element `CapabilityStatement.rest.resource.searchParam.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.searchParam.documentation` as `Equivalent`.
Element `CapabilityStatement.rest.interaction` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction` as `Equivalent`.
Element `CapabilityStatement.rest.interaction.code` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction.code` as `Equivalent`.
Element `CapabilityStatement.rest.interaction.documentation` is mapped to FHIR R4 element `CapabilityStatement.rest.interaction.documentation` as `Equivalent`.
Element `CapabilityStatement.rest.searchParam` is mapped to FHIR R4 element `CapabilityStatement.rest.searchParam` as `Equivalent`. Typically, the only search parameters supported for all searchse are those that apply to all resources - tags, profiles, text search etc.
Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation` as `SourceIsBroaderThanTarget`. Element `CapabilityStatement.rest.operation` is mapped to FHIR R4 element `CapabilityStatement.rest.operation` as `Equivalent`.
Element `CapabilityStatement.rest.operation.name` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.name` as `Equivalent`. The name here SHOULD be the same as the name in the definition, unless there is a name clash and the name cannot be used. The name does not include the "$" portion that is always included in the URL.
Element `CapabilityStatement.rest.operation.definition` is mapped to FHIR R4 element `CapabilityStatement.rest.resource.operation.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.rest.operation.definition` do not cover the following types based on type expansion: display, identifier, reference. This can be used to build an HTML form to invoke the operation, for instance.
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).
Element `CapabilityStatement.messaging` is mapped to FHIR R4 element `CapabilityStatement.messaging` as `Equivalent`. Multiple repetitions allow the documentation of multiple endpoints per solution.
Element `CapabilityStatement.messaging.endpoint` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint` as `Equivalent`.
Element `CapabilityStatement.messaging.endpoint.protocol` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint.protocol` as `Equivalent`.
Element `CapabilityStatement.messaging.endpoint.address` is mapped to FHIR R4 element `CapabilityStatement.messaging.endpoint.address` as `Equivalent`.
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.
Element `CapabilityStatement.messaging.documentation` is mapped to FHIR R4 element `CapabilityStatement.messaging.documentation` as `Equivalent`.
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.
Element `CapabilityStatement.messaging.supportedMessage.mode` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage.mode` as `Equivalent`.
Element `CapabilityStatement.messaging.supportedMessage.definition` is mapped to FHIR R4 element `CapabilityStatement.messaging.supportedMessage.definition` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types: Reference. The mappings for `CapabilityStatement.messaging.supportedMessage.definition` do not cover the following types based on type expansion: display, identifier, reference.
Element `CapabilityStatement.document` is mapped to FHIR R4 element `CapabilityStatement.document` as `Equivalent`.
Element `CapabilityStatement.document.mode` is mapped to FHIR R4 element `CapabilityStatement.document.mode` as `Equivalent`.
Element `CapabilityStatement.document.documentation` is mapped to FHIR R4 element `CapabilityStatement.document.documentation` as `Equivalent`.
Element `CapabilityStatement.document.profile` is mapped to FHIR R4 element `CapabilityStatement.document.profile` as `SourceIsBroaderThanTarget`. The mappings for `CapabilityStatement.document.profile` do not cover the following types: Reference. The mappings for `CapabilityStatement.document.profile` do not cover the following types based on type expansion: display, identifier, reference. The first resource is the document resource.
Element `CapabilityStatement.acceptUnknown` has a context of CapabilityStatement based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.acceptUnknown` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Unknown elements in a resource can only arise as later versions of the specification are published, because this is the only place where such elements can be defined. Hence accepting unknown elements is about inter-version compatibility. Applications are recommended to accept unknown extensions and elements ('both'), but this is not always possible.
Element `CapabilityStatement.rest.security.certificate` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `CapabilityStatement.rest.security.certificate.type` is part of an existing definition because parent element `CapabilityStatement.rest.security.certificate` requires a cross-version extension. Element `CapabilityStatement.rest.security.certificate.type` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `CapabilityStatement.rest.security.certificate.blob` is part of an existing definition because parent element `CapabilityStatement.rest.security.certificate` requires a cross-version extension. Element `CapabilityStatement.rest.security.certificate.blob` has a context of CapabilityStatement.rest.security based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.rest.security.certificate.blob` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `CapabilityStatement.messaging.event` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The same event may be listed up to two times - once as sender and once as receiver.
Element `CapabilityStatement.messaging.event.code` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.code` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `CapabilityStatement.messaging.event.category` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.category` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `CapabilityStatement.messaging.event.mode` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.mode` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `CapabilityStatement.messaging.event.focus` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.focus` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This SHALL be provided if the event type supports multiple different resource types.
Element `CapabilityStatement.messaging.event.request` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.request` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.request` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `CapabilityStatement.messaging.event.response` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.response` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.response` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `CapabilityStatement.messaging.event.documentation` is part of an existing definition because parent element `CapabilityStatement.messaging.event` requires a cross-version extension. Element `CapabilityStatement.messaging.event.documentation` has a context of CapabilityStatement.messaging based on following the parent source element upwards and mapping to `CapabilityStatement`. Element `CapabilityStatement.messaging.event.documentation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).