A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. If the element is present, it must have either a @value, an @id, or extensions An absolute URI that is used to identify this terminology capabilities when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this terminology capabilities is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the terminology capabilities is stored on different servers. 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. 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. A short, descriptive, user-friendly title for the terminology capabilities. The status of this terminology capabilities. Enables tracking the life-cycle of the content. 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. The date (and optionally time) when the terminology capabilities was published. The date must change 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. The name of the organization or individual that published the terminology capabilities. Contact details to assist a user in finding and communicating with the publisher. 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. The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate terminology capabilities instances. A legal or geographic region in which the terminology capabilities is intended to be used. Explanation of why this terminology capabilities is needed and why it has been designed as it has. 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. The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase). Software that is covered by this terminology capability statement. It is used when the statement describes the capabilities of a particular software version, independent of an installation. Identifies a specific implementation instance that is described by the terminology capability statement - i.e. a particular installation, rather than the capabilities of a software program. 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. Information about the [ValueSet/$expand](valueset-operation-expand.html) operation. The degree to which the server supports the code search parameter on ValueSet, if it is supported. Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation. Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation. Whether the $closure operation is supported. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Name the software is known by. The version identifier for the software covered by this statement. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Information about the specific installation that this terminology capability statement relates to. An absolute base URL for the implementation. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. URI for the Code System. For the code system, a list of versions that are supported by the server. True if subsumption is supported for this version of the code system. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. 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. Properties supported for $lookup. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Code of the property supported. Operations supported for the property. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Whether the server can return nested value sets. Whether the server supports paging on expansion. Allow request for incomplete expansions? Supported expansion parameter. Documentation about text searching works. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Expansion Parameter name. Description of support for parameter. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Whether translations are validated. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Whether the client must identify the map. A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. If cross-system closure is supported. Explicit Codes Implicit Codes The degree to which the server supports the code search parameter on ValueSet, if it is supported. If the element is present, it must have either a @value, an @id, or extensions