A Terminology Capabilities documents a set of capabilities (behaviors) of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation.

An absolute URI that is used to identify this terminology capabilities when it is referenced in a specification, model, design or an instance. This SHOULD be globally unique, and SHOULD be a literal address at which this terminology capabilities is (or will be) published.

Allows the terminology capabilities to be referenced by a single globally unique identifier.

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 URL SHOULD include the major version of the terminology capabilities. For more information see Technical and Business Versions.

The identifier that is used to identify this version of the terminology capabilities when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the terminology capabilities author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.

There may be different terminology capabilities 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 terminology capabilities with the format [url]|[version].

A natural language name identifying the terminology capabilities. This name should be usable as an identifier for the module by machine processing applications such as code generation.

Support human navigation and code generation.

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.

A short, descriptive, user-friendly title for the terminology capabilities.

This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

The status of this terminology capabilities. Enables tracking the life-cycle of the content.

Allows filtering of terminology capabilitiess that are appropriate for use vs. not.
This is labeled as "Is Modifier" because applications should not use a retired terminology capabilities 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.

A boolean value to indicate that this terminology capabilities is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.

Enables experimental content to be developed following the same lifecycle that would be used for a production-level terminology capabilities.

Allows filtering of terminology capabilities that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental terminology capabilities in production.

The date (and optionally time) when the terminology capabilities was published. The date must change if and when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the terminology capabilities changes.

Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the terminology capabilities. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

The name of the individual or organization that published the terminology capabilities.

Helps establish the "authority/credibility" of the terminology capabilities. May also allow for contact.

Usually an organization, but may be an individual. The publisher (or steward) of the terminology capabilities is the organization or individual primarily responsible for the maintenance and upkeep of the terminology capabilities. 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 terminology capabilities. This item SHOULD be populated unless the information is available from context.

Contact details to assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number, etc.

A free text natural language description of the terminology capabilities from a consumer's perspective. Typically, this is used when the capability statement describes a desired rather than an actual solution, for example as a formal expression of requirements as part of an RFP.

This description can be used to capture details such as why the terminology capabilities 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 terminology capabilities 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.

The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate terminology capabilities instances.

Assist in searching for appropriate content.

When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.

A legal or geographic region in which the terminology capabilities is intended to be used.

It may be possible for the terminology capabilities to be used in jurisdictions other than those for which it was originally designed or intended.

Explaination of why this terminology capabilities is needed and why it has been designed as it has.

This element does not describe the usage of the terminology capabilities 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 terminology capabilities.

A copyright statement relating to the terminology capabilities and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the terminology capabilities.

Consumers must be able to determine any legal restrictions on the use of the terminology capabilities and/or its content.

Whether the server supports lockedDate.

Identifies a code system that is supported by the server. If there is a no code system URL, then this declares the general assumptions a client can make about support for any CodeSystem resource.

The code system - identified by it's system URL - may also be declared explicitly as a Code System Resource at /CodeSystem, but it might not be.

URI for the Code System.

For the code system, a list of versions that are supported by the server.

Language translations might not be available for all codes.

For version-less code systems, there should be a single version with no identifier.

If this is the default version for this code system.

If the compositional grammar defined by the code system is supported.

Language Displays supported.

Filter Properties supported.

Code of the property supported.

Operations supported for the property.

Properties supported for $lookup.

Information about the $expansion operation.

Whether the server can return nested value sets.

Whether the server supports paging on expansion.

Allow request for incomplete expansions?

Supported fields on ExpansionProfile.

Supported expansion profiles.

Documentation about text searching works.

This documentation should cover things like case sensitivity, use of punctuation if not ignored, what wild cards are supported (if any), whether text is starts with or contains, and whether word order matters.

The degree to which the the server supports the code search parameter on ValueSet, if it is supported.

See notes on the ValueSet resource.

Information about the $validation operation.

Whether translations are validated.

Information about the $translation operation.

Whether the client must identify the map.

Whether the $closure operation is supported.

If cross-system closure is supported.