Release 4B 5 Ballot

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0-ballot: R5 Ballot - STU see ballot notes ). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4

4.12 Resource TerminologyCapabilities - Content

Vocabulary icon Work Group Maturity Level : 0 1   Trial Use Security Category : Anonymous Compartments : Not linked to any defined compartments

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.

4.12.1 Scope and Usage

The TerminologyCapabilities resource provides for a terminology server to describe how the underlying terminology service works.

A client can get the TerminologyCapabilities statement for a Terminology Service by using the capabilities API : 

 GET [base]/metadata?mode=terminology

This will return the TerminologyCapabilities resource that applies to the service itself.

4.12.2 Boundaries and Relationships

  • The TerminologyCapabilities resource does not describe the API - see CapabilityStatement for this.
  • The CodeSystem resource documents the inherent structure and capabilities of code system, whereas the TerminologyCapabilities resource documents what a server hosting the code system is capable of

4.12.3 References to this Resource

No resources refer to references for this resource directly. This resource does not implement any patterns. Resource.

4.12.4 Resource Content

Structure

URI
Name Flags Card. Type Description & Constraints doco
. . TerminologyCapabilities TU DomainResource A statement of system capabilities
+ Warning: Name should be usable as an identifier for the module by machine processing applications such as code generation
+ Rule: A Terminology Capability Statement statement SHALL have at least one of description, software, or implementation element. element
+ Rule: If kind = instance, implementation must be present and software may be present
+ Rule: If kind = capability, implementation must be absent, software must be present
+ Rule: If kind = requirements, implementation and software must be absent
+ Rule: Each instance of the codeSystem element must represent a distinct code system.

Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
Interfaces Implemented: CanonicalResource
. . . url Σ C 0..1 uri Canonical identifier for this terminology capabilities, represented as a URI (globally unique)
+ Warning: URL should not contain | or # - these characters make processing canonical references problematic
. . version . identifier Σ 0..1 0..* string Identifier Business version of Additional identifier for the terminology capabilities

. . . name version Σ 0..1 string Name for this Business version of the terminology capabilities (computer friendly)
. . . title Σ 0..1 string Name for this terminology capabilities (human friendly)
... status ?! Σ 1..1 code draft | active | retired | unknown
PublicationStatus ( Required )
. . . experimental Σ 0..1 boolean For testing purposes, not real usage
. . . date Σ 1..1 dateTime Date last changed
. . . publisher Σ 0..1 string Name of the publisher publisher/steward (organization or individual)
. . . contact Σ 0..* ContactDetail Contact details for the publisher

. . . description 0..1 markdown Natural language description of the terminology capabilities
. . . useContext Σ 0..* UsageContext The context that the content is intended to support

. . . jurisdiction Σ 0..* CodeableConcept Intended jurisdiction for terminology capabilities (if applicable)
Jurisdiction ( Extensible )

. . . purpose 0..1 markdown Why this terminology capabilities is defined
. . . copyright Σ 0..1 markdown Use and/or publishing restrictions
. . . kind Σ I C 1..1 code instance | capability | requirements
CapabilityStatementKind ( Required )
. . . software Σ I C 0..1 BackboneElement Software that is covered by this terminology capability statement
. . . . name Σ 1..1 string A name the software is known by
. . . . version Σ 0..1 string Version covered by this statement
. . . implementation Σ I C 0..1 BackboneElement If this describes a specific instance
. . . . description Σ 1..1 string Describes this specific instance
. . . . url Σ 0..1 url Base URL for the implementation
. . . lockedDate Σ 0..1 boolean Whether lockedDate is supported
. . . codeSystem I C 0..* BackboneElement A code system supported by the server
+ Rule: If there is more than one version, a version code must be defined
+ Rule: Each version.code element must be distinct for a particular code system.
+ Rule: A codeSystem element instance may have at most one version.isDefault element with a value of 'true'.

. . . . uri 0..1 canonical ( CodeSystem ) Canonical identifier for the Code System code system, represented as a URI
. . . . version 0..* BackboneElement Version of Code System supported

. . . . . code Σ I C 0..1 string Version identifier for this version
. . . . . isDefault Σ 0..1 boolean If this is the default version for this code system
. . . . . compositional 0..1 boolean If compositional grammar is supported
. . . . . language 0..* code Language Displays supported
Common Languages ( Required )

. . . . . filter 0..* BackboneElement Filter Properties supported

. . . . . . code 1..1 code Code of the property supported
. . . . . . op 1..* code Operations supported for the property

. . . . . property 0..* code Properties supported for $lookup

. . . . content Σ 1..1 code not-present | example | fragment | complete | supplement
CodeSystemContentMode ( Required )
. . . . subsumption 0..1 boolean Whether subsumption is supported
. . . expansion 0..1 BackboneElement Information about the [ValueSet/$expand](valueset-operation-expand.html) operation
. . . . hierarchical 0..1 boolean Whether the server can return nested value sets
. . . . paging 0..1 boolean Whether the server supports paging on expansion
. . . . incomplete 0..1 boolean Allow request for incomplete expansions?
. . . . parameter 0..* BackboneElement Supported expansion parameter

. . . . . name 1..1 code Expansion Parameter name Name of the supported expansion parameter
. . . . . documentation 0..1 string Description of support for parameter
. . . . textFilter 0..1 markdown Documentation about text searching works
. . . codeSearch 0..1 code explicit in-compose | all in-expansion | in-compose-or-expansion
CodeSearchSupport ( Required )
. . . validateCode 0..1 BackboneElement Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation
. . . . translations 1..1 boolean Whether translations are validated
. . . translation 0..1 BackboneElement Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation
. . . . needsMap 1..1 boolean Whether the client must identify the map
. . . closure 0..1 BackboneElement Information about the [ConceptMap/$closure](conceptmap-operation-closure.html) operation
. . . . translation 0..1 boolean If cross-system closure is supported

doco Documentation for this format

See the Extensions for this resource

UML Diagram ( Legend )

TerminologyCapabilities ( DomainResource ) + CanonicalResource 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 url : uri [0..1] A formal identifier that is used to identify this terminology capabilities when it is represented in other formats, or referenced in a specification, model, design or an instance identifier : Identifier [0..*] 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 version : string [0..1] 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 name : string [0..1] « This element has or is affected by some invariants C » A short, descriptive, user-friendly title for the terminology capabilities title : string [0..1] The status of this terminology capabilities. Enables tracking the life-cycle of the content (this element modifies the meaning of other elements) status : code [1..1] « null (Strength=Required) PublicationStatus ! » 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 experimental : boolean [0..1] 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 date : dateTime [1..1] The name of the organization or individual that published responsible for the release and ongoing maintenance of the terminology capabilities publisher : string [0..1] Contact details to assist a user in finding and communicating with the publisher contact : ContactDetail [0..*] 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 description : markdown [0..1] 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 useContext : UsageContext [0..*] A legal or geographic region in which the terminology capabilities is intended to be used jurisdiction : CodeableConcept [0..*] « null (Strength=Extensible) Jurisdiction ValueSet + » Explanation of why this terminology capabilities is needed and why it has been designed as it has purpose : markdown [0..1] 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 copyright : markdown [0..1] 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) kind : code [1..1] « null (Strength=Required) CapabilityStatementKind ! » « This element has or is affected by some invariants C » Whether the server supports lockedDate lockedDate : boolean [0..1] The degree to which the server supports the code search parameter on ValueSet, if it is supported codeSearch : code [0..1] « null (Strength=Required) CodeSearchSupport ! » Software Name the software is known by name : string [1..1] The version identifier for the software covered by this statement version : string [0..1] Implementation Information about the specific installation that this terminology capability statement relates to description : string [1..1] An absolute base URL for the implementation url : url [0..1] CodeSystem URI Canonical identifier for the Code System code system, represented as a URI uri : canonical [0..1] « CodeSystem » The extent of the content of the code system (the concepts and codes it defines) are represented in this resource instance content : code [1..1] « null (Strength=Required) CodeSystemContentMode ! » True if subsumption is supported for this version of the code system subsumption : boolean [0..1] Version For version-less code systems, there should be a single version with no identifier code : string [0..1] « This element has or is affected by some invariants C » If this is the default version for this code system isDefault : boolean [0..1] If the compositional grammar defined by the code system is supported compositional : boolean [0..1] Language Displays supported language : code [0..*] « null (Strength=Required) CommonLanguages ! » Properties supported for $lookup property : code [0..*] Filter Code of the property supported code : code [1..1] Operations supported for the property op : code [1..*] Expansion Whether the server can return nested value sets hierarchical : boolean [0..1] Whether the server supports paging on expansion paging : boolean [0..1] Allow request True if requests for incomplete expansions? expansions are allowed incomplete : boolean [0..1] Documentation about text searching works textFilter : markdown [0..1] Parameter Expansion Parameter name Name of the supported expansion parameter name : code [1..1] Description of support for parameter documentation : string [0..1] ValidateCode Whether translations are validated translations : boolean [1..1] Translation Whether the client must identify the map needsMap : boolean [1..1] Closure If cross-system closure is supported translation : boolean [0..1] 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 software [0..1] 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 implementation [0..1] Filter Properties supported filter [0..*] For the code system, a list of versions that are supported by the server version [0..*] 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 codeSystem [0..*] Supported expansion parameter parameter [0..*] Information about the [ValueSet/$expand](valueset-operation-expand.html) operation expansion [0..1] Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation validateCode [0..1] Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation translation [0..1] Whether the $closure operation is supported closure [0..1]

XML Template 

<TerminologyCapabilities xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <

 <url value="[uri]"/><!-- 0..1 Canonical identifier for this terminology capabilities, represented as a URI (globally unique) -->
 <identifier><!-- 0..* Identifier Additional identifier for the terminology capabilities --></identifier>

 <version value="[string]"/><!-- 0..1 Business version of the terminology capabilities -->
 <

 <name value="[string]"/><!-- I 0..1 Name for this terminology capabilities (computer friendly) -->

 <title value="[string]"/><!-- 0..1 Name for this terminology capabilities (human friendly) -->
 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <experimental value="[boolean]"/><!-- 0..1 For testing purposes, not real usage -->
 <date value="[dateTime]"/><!-- 1..1 Date last changed -->
 <

 <publisher value="[string]"/><!-- 0..1 Name of the publisher/steward (organization or individual) -->

 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the terminology capabilities -->
 <useContext><!-- 0..* UsageContext The context that the content is intended to support --></useContext>
 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for terminology capabilities (if applicable) --></jurisdiction>
 <purpose value="[markdown]"/><!-- 0..1 Why this terminology capabilities is defined -->
 <copyright value="[markdown]"/><!-- 0..1 Use and/or publishing restrictions -->
 <
 <

 <kind value="[code]"/><!-- I 1..1 instance | capability | requirements -->
 <software>  <!-- I 0..1 Software that is covered by this terminology capability statement -->

  <name value="[string]"/><!-- 1..1 A name the software is known by -->
  <version value="[string]"/><!-- 0..1 Version covered by this statement -->
 </software>
 <

 <implementation>  <!-- I 0..1 If this describes a specific instance -->

  <description value="[string]"/><!-- 1..1 Describes this specific instance -->
  <url value="[url]"/><!-- 0..1 Base URL for the implementation -->
 </implementation>
 <lockedDate value="[boolean]"/><!-- 0..1 Whether lockedDate is supported -->
 <codeSystem>  <!-- 0..* A code system supported by the server -->
  <</uri>

  <uri><!-- 0..1 canonical(CodeSystem) Canonical identifier for the code system, represented as a URI --></uri>

  <version>  <!-- 0..* Version of Code System supported -->
   <

   <code value="[string]"/><!-- I 0..1 Version identifier for this version -->

   <isDefault value="[boolean]"/><!-- 0..1 If this is the default version for this code system -->
   <compositional value="[boolean]"/><!-- 0..1 If compositional grammar is supported -->
   <

   <language value="[code]"/><!-- 0..* Language Displays supported -->

   <filter>  <!-- 0..* Filter Properties supported -->
    <code value="[code]"/><!-- 1..1 Code of the property supported -->
    <op value="[code]"/><!-- 1..* Operations supported for the property -->
   </filter>
   <property value="[code]"/><!-- 0..* Properties supported for $lookup -->
  </version>
  <content value="[code]"/><!-- 1..1 not-present | example | fragment | complete | supplement -->

  <subsumption value="[boolean]"/><!-- 0..1 Whether subsumption is supported -->
 </codeSystem>
 <expansion>  <!-- 0..1 Information about the [ValueSet/$expand](valueset-operation-expand.html) operation -->
  <hierarchical value="[boolean]"/><!-- 0..1 Whether the server can return nested value sets -->
  <paging value="[boolean]"/><!-- 0..1 Whether the server supports paging on expansion -->
  <

  <incomplete value="[boolean]"/><!-- 0..1 Allow request for incomplete expansions? -->

  <parameter>  <!-- 0..* Supported expansion parameter -->
   <

   <name value="[code]"/><!-- 1..1 Name of the supported expansion parameter -->

   <documentation value="[string]"/><!-- 0..1 Description of support for parameter -->
  </parameter>
  <textFilter value="[markdown]"/><!-- 0..1 Documentation about text searching works -->
 </expansion>
 <

 <codeSearch value="[code]"/><!-- 0..1 in-compose | in-expansion | in-compose-or-expansion -->

 <validateCode>  <!-- 0..1 Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation -->
  <translations value="[boolean]"/><!-- 1..1 Whether translations are validated -->
 </validateCode>
 <translation>  <!-- 0..1 Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation -->
  <needsMap value="[boolean]"/><!-- 1..1 Whether the client must identify the map -->
 </translation>
 <closure>  <!-- 0..1 Information about the [ConceptMap/$closure](conceptmap-operation-closure.html) operation -->
  <translation value="[boolean]"/><!-- 0..1 If cross-system closure is supported -->
 </closure>
</TerminologyCapabilities>

JSON Template 

{doco
  "resourceType" : "TerminologyCapabilities",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "

  "url" : "<uri>", // Canonical identifier for this terminology capabilities, represented as a URI (globally unique)
  "identifier" : [{ Identifier }], // Additional identifier for the terminology capabilities

  "version" : "<string>", // Business version of the terminology capabilities
  "

  "name" : "<string>", // I Name for this terminology capabilities (computer friendly)

  "title" : "<string>", // Name for this terminology capabilities (human friendly)
  "status" : "<code>", // R!  draft | active | retired | unknown
  "experimental" : <boolean>, // For testing purposes, not real usage
  "date" : "<dateTime>", // R!  Date last changed
  "

  "publisher" : "<string>", // Name of the publisher/steward (organization or individual)

  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "description" : "<markdown>", // Natural language description of the terminology capabilities
  "useContext" : [{ UsageContext }], // The context that the content is intended to support
  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for terminology capabilities (if applicable)
  "purpose" : "<markdown>", // Why this terminology capabilities is defined
  "copyright" : "<markdown>", // Use and/or publishing restrictions
  "
  "

  "kind" : "<code>", // I R!  instance | capability | requirements
  "software" : { // I Software that is covered by this terminology capability statement

    "name" : "<string>", // R!  A name the software is known by
    "version" : "<string>" // Version covered by this statement
  },
  "

  "implementation" : { // I If this describes a specific instance

    "description" : "<string>", // R!  Describes this specific instance
    "url" : "<url>" // Base URL for the implementation
  },
  "lockedDate" : <boolean>, // Whether lockedDate is supported
  "codeSystem" : [{ // A code system supported by the server
    "

    "uri" : "<canonical(CodeSystem)>", // Canonical identifier for the code system, represented as a URI

    "version" : [{ // Version of Code System supported
      "

      "code" : "<string>", // I Version identifier for this version

      "isDefault" : <boolean>, // If this is the default version for this code system
      "compositional" : <boolean>, // If compositional grammar is supported
      "

      "language" : ["<code>"], // Language Displays supported

      "filter" : [{ // Filter Properties supported
        "code" : "<code>", // R!  Code of the property supported
        "op" : ["<code>"] // R!  Operations supported for the property
      }],
      "property" : ["<code>"] // Properties supported for $lookup
    }],
    "content" : "<code>", // R!  not-present | example | fragment | complete | supplement

    "subsumption" : <boolean> // Whether subsumption is supported
  }],
  "expansion" : { // Information about the [ValueSet/$expand](valueset-operation-expand.html) operation
    "hierarchical" : <boolean>, // Whether the server can return nested value sets
    "paging" : <boolean>, // Whether the server supports paging on expansion
    "

    "incomplete" : <boolean>, // Allow request for incomplete expansions?

    "parameter" : [{ // Supported expansion parameter
      "

      "name" : "<code>", // R!  Name of the supported expansion parameter

      "documentation" : "<string>" // Description of support for parameter
    }],
    "textFilter" : "<markdown>" // Documentation about text searching works
  },
  "

  "codeSearch" : "<code>", // in-compose | in-expansion | in-compose-or-expansion

  "validateCode" : { // Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation
    "translations" : <boolean> // R!  Whether translations are validated
  },
  "translation" : { // Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation
    "needsMap" : <boolean> // R!  Whether the client must identify the map
  },
  "closure" : { // Information about the [ConceptMap/$closure](conceptmap-operation-closure.html) operation
    "translation" : <boolean> // If cross-system closure is supported
  }
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:TerminologyCapabilities;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:

  fhir:TerminologyCapabilities.url [ uri ]; # 0..1 Canonical identifier for this terminology capabilities, represented as a URI (globally unique)
  fhir:TerminologyCapabilities.identifier [ Identifier ], ... ; # 0..* Additional identifier for the terminology capabilities

  fhir:TerminologyCapabilities.version [ string ]; # 0..1 Business version of the terminology capabilities
  fhir:

  fhir:TerminologyCapabilities.name [ string ]; # 0..1 I Name for this terminology capabilities (computer friendly)

  fhir:TerminologyCapabilities.title [ string ]; # 0..1 Name for this terminology capabilities (human friendly)
  fhir:TerminologyCapabilities.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:TerminologyCapabilities.experimental [ boolean ]; # 0..1 For testing purposes, not real usage
  fhir:TerminologyCapabilities.date [ dateTime ]; # 1..1 Date last changed
  fhir:

  fhir:TerminologyCapabilities.publisher [ string ]; # 0..1 Name of the publisher/steward (organization or individual)

  fhir:TerminologyCapabilities.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:TerminologyCapabilities.description [ markdown ]; # 0..1 Natural language description of the terminology capabilities
  fhir:TerminologyCapabilities.useContext [ UsageContext ], ... ; # 0..* The context that the content is intended to support
  fhir:TerminologyCapabilities.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for terminology capabilities (if applicable)
  fhir:TerminologyCapabilities.purpose [ markdown ]; # 0..1 Why this terminology capabilities is defined
  fhir:TerminologyCapabilities.copyright [ markdown ]; # 0..1 Use and/or publishing restrictions
  fhir:
  fhir:

  fhir:TerminologyCapabilities.kind [ code ]; # 1..1 I instance | capability | requirements
  fhir:TerminologyCapabilities.software [ # 0..1 I Software that is covered by this terminology capability statement

    fhir:TerminologyCapabilities.software.name [ string ]; # 1..1 A name the software is known by
    fhir:TerminologyCapabilities.software.version [ string ]; # 0..1 Version covered by this statement
  ];
  fhir:

  fhir:TerminologyCapabilities.implementation [ # 0..1 I If this describes a specific instance

    fhir:TerminologyCapabilities.implementation.description [ string ]; # 1..1 Describes this specific instance
    fhir:TerminologyCapabilities.implementation.url [ url ]; # 0..1 Base URL for the implementation
  ];
  fhir:TerminologyCapabilities.lockedDate [ boolean ]; # 0..1 Whether lockedDate is supported
  fhir:TerminologyCapabilities.codeSystem [ # 0..* A code system supported by the server
    fhir:

    fhir:TerminologyCapabilities.codeSystem.uri [ canonical(CodeSystem) ]; # 0..1 Canonical identifier for the code system, represented as a URI

    fhir:TerminologyCapabilities.codeSystem.version [ # 0..* Version of Code System supported
      fhir:

      fhir:TerminologyCapabilities.codeSystem.version.code [ string ]; # 0..1 I Version identifier for this version

      fhir:TerminologyCapabilities.codeSystem.version.isDefault [ boolean ]; # 0..1 If this is the default version for this code system
      fhir:TerminologyCapabilities.codeSystem.version.compositional [ boolean ]; # 0..1 If compositional grammar is supported
      fhir:TerminologyCapabilities.codeSystem.version.language [ code ], ... ; # 0..* Language Displays supported
      fhir:TerminologyCapabilities.codeSystem.version.filter [ # 0..* Filter Properties supported
        fhir:TerminologyCapabilities.codeSystem.version.filter.code [ code ]; # 1..1 Code of the property supported
        fhir:TerminologyCapabilities.codeSystem.version.filter.op [ code ], ... ; # 1..* Operations supported for the property
      ], ...;
      fhir:TerminologyCapabilities.codeSystem.version.property [ code ], ... ; # 0..* Properties supported for $lookup
    ], ...;
    fhir:TerminologyCapabilities.codeSystem.content [ code ]; # 1..1 not-present | example | fragment | complete | supplement

    fhir:TerminologyCapabilities.codeSystem.subsumption [ boolean ]; # 0..1 Whether subsumption is supported
  ], ...;
  fhir:TerminologyCapabilities.expansion [ # 0..1 Information about the [ValueSet/$expand](valueset-operation-expand.html) operation
    fhir:TerminologyCapabilities.expansion.hierarchical [ boolean ]; # 0..1 Whether the server can return nested value sets
    fhir:TerminologyCapabilities.expansion.paging [ boolean ]; # 0..1 Whether the server supports paging on expansion
    fhir:

    fhir:TerminologyCapabilities.expansion.incomplete [ boolean ]; # 0..1 Allow request for incomplete expansions?

    fhir:TerminologyCapabilities.expansion.parameter [ # 0..* Supported expansion parameter
      fhir:

      fhir:TerminologyCapabilities.expansion.parameter.name [ code ]; # 1..1 Name of the supported expansion parameter

      fhir:TerminologyCapabilities.expansion.parameter.documentation [ string ]; # 0..1 Description of support for parameter
    ], ...;
    fhir:TerminologyCapabilities.expansion.textFilter [ markdown ]; # 0..1 Documentation about text searching works
  ];
  fhir:

  fhir:TerminologyCapabilities.codeSearch [ code ]; # 0..1 in-compose | in-expansion | in-compose-or-expansion

  fhir:TerminologyCapabilities.validateCode [ # 0..1 Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation
    fhir:TerminologyCapabilities.validateCode.translations [ boolean ]; # 1..1 Whether translations are validated
  ];
  fhir:TerminologyCapabilities.translation [ # 0..1 Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation
    fhir:TerminologyCapabilities.translation.needsMap [ boolean ]; # 1..1 Whether the client must identify the map
  ];
  fhir:TerminologyCapabilities.closure [ # 0..1 Information about the [ConceptMap/$closure](conceptmap-operation-closure.html) operation
    fhir:TerminologyCapabilities.closure.translation [ boolean ]; # 0..1 If cross-system closure is supported
  ];
]

Changes since R4

TerminologyCapabilities
TerminologyCapabilities.identifier
  • No Changes Added Element
TerminologyCapabilities.codeSystem.version.language
  • Add Binding http://hl7.org/fhir/ValueSet/languages|5.0.0-ballot (required)
  • Add Binding http://hl7.org/fhir/ValueSet/languages|5.0.0-ballot (required)
TerminologyCapabilities.codeSystem.content
  • Added Mandatory Element

See the Full Difference for further information

This analysis is available as XML or JSON .

Conversions between R3 and R4 See R3 <--> R4 Conversion Maps (status = Not Mapped)

Structure

URI
Name Flags Card. Type Description & Constraints doco
. . TerminologyCapabilities TU DomainResource A statement of system capabilities
+ Warning: Name should be usable as an identifier for the module by machine processing applications such as code generation
+ Rule: A Terminology Capability Statement statement SHALL have at least one of description, software, or implementation element. element
+ Rule: If kind = instance, implementation must be present and software may be present
+ Rule: If kind = capability, implementation must be absent, software must be present
+ Rule: If kind = requirements, implementation and software must be absent
+ Rule: Each instance of the codeSystem element must represent a distinct code system.

Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
Interfaces Implemented: CanonicalResource
. . . url Σ C 0..1 uri Canonical identifier for this terminology capabilities, represented as a URI (globally unique)
+ Warning: URL should not contain | or # - these characters make processing canonical references problematic
. . version . identifier Σ 0..1 0..* string Identifier Business version of Additional identifier for the terminology capabilities

. . . name version Σ 0..1 string Name for this Business version of the terminology capabilities (computer friendly)
. . . title Σ 0..1 string Name for this terminology capabilities (human friendly)
... status ?! Σ 1..1 code draft | active | retired | unknown
PublicationStatus ( Required )
. . . experimental Σ 0..1 boolean For testing purposes, not real usage
. . . date Σ 1..1 dateTime Date last changed
. . . publisher Σ 0..1 string Name of the publisher publisher/steward (organization or individual)
. . . contact Σ 0..* ContactDetail Contact details for the publisher

. . . description 0..1 markdown Natural language description of the terminology capabilities
. . . useContext Σ 0..* UsageContext The context that the content is intended to support

. . . jurisdiction Σ 0..* CodeableConcept Intended jurisdiction for terminology capabilities (if applicable)
Jurisdiction ( Extensible )

. . . purpose 0..1 markdown Why this terminology capabilities is defined
. . . copyright Σ 0..1 markdown Use and/or publishing restrictions
. . . kind Σ I C 1..1 code instance | capability | requirements
CapabilityStatementKind ( Required )
. . . software Σ I C 0..1 BackboneElement Software that is covered by this terminology capability statement
. . . . name Σ 1..1 string A name the software is known by
. . . . version Σ 0..1 string Version covered by this statement
. . . implementation Σ I C 0..1 BackboneElement If this describes a specific instance
. . . . description Σ 1..1 string Describes this specific instance
. . . . url Σ 0..1 url Base URL for the implementation
. . . lockedDate Σ 0..1 boolean Whether lockedDate is supported
. . . codeSystem I C 0..* BackboneElement A code system supported by the server
+ Rule: If there is more than one version, a version code must be defined
+ Rule: Each version.code element must be distinct for a particular code system.
+ Rule: A codeSystem element instance may have at most one version.isDefault element with a value of 'true'.

. . . . uri 0..1 canonical ( CodeSystem ) Canonical identifier for the Code System code system, represented as a URI
. . . . version 0..* BackboneElement Version of Code System supported

. . . . . code Σ I C 0..1 string Version identifier for this version
. . . . . isDefault Σ 0..1 boolean If this is the default version for this code system
. . . . . compositional 0..1 boolean If compositional grammar is supported
. . . . . language 0..* code Language Displays supported
Common Languages ( Required )

. . . . . filter 0..* BackboneElement Filter Properties supported

. . . . . . code 1..1 code Code of the property supported
. . . . . . op 1..* code Operations supported for the property

. . . . . property 0..* code Properties supported for $lookup

. . . . content Σ 1..1 code not-present | example | fragment | complete | supplement
CodeSystemContentMode ( Required )
. . . . subsumption 0..1 boolean Whether subsumption is supported
. . . expansion 0..1 BackboneElement Information about the [ValueSet/$expand](valueset-operation-expand.html) operation
. . . . hierarchical 0..1 boolean Whether the server can return nested value sets
. . . . paging 0..1 boolean Whether the server supports paging on expansion
. . . . incomplete 0..1 boolean Allow request for incomplete expansions?
. . . . parameter 0..* BackboneElement Supported expansion parameter

. . . . . name 1..1 code Expansion Parameter name Name of the supported expansion parameter
. . . . . documentation 0..1 string Description of support for parameter
. . . . textFilter 0..1 markdown Documentation about text searching works
. . . codeSearch 0..1 code explicit in-compose | all in-expansion | in-compose-or-expansion
CodeSearchSupport ( Required )
. . . validateCode 0..1 BackboneElement Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation
. . . . translations 1..1 boolean Whether translations are validated
. . . translation 0..1 BackboneElement Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation
. . . . needsMap 1..1 boolean Whether the client must identify the map
. . . closure 0..1 BackboneElement Information about the [ConceptMap/$closure](conceptmap-operation-closure.html) operation
. . . . translation 0..1 boolean If cross-system closure is supported

doco Documentation for this format

See the Extensions for this resource

UML Diagram ( Legend )

TerminologyCapabilities ( DomainResource ) + CanonicalResource 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 url : uri [0..1] A formal identifier that is used to identify this terminology capabilities when it is represented in other formats, or referenced in a specification, model, design or an instance identifier : Identifier [0..*] 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 version : string [0..1] 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 name : string [0..1] « This element has or is affected by some invariants C » A short, descriptive, user-friendly title for the terminology capabilities title : string [0..1] The status of this terminology capabilities. Enables tracking the life-cycle of the content (this element modifies the meaning of other elements) status : code [1..1] « null (Strength=Required) PublicationStatus ! » 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 experimental : boolean [0..1] 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 date : dateTime [1..1] The name of the organization or individual that published responsible for the release and ongoing maintenance of the terminology capabilities publisher : string [0..1] Contact details to assist a user in finding and communicating with the publisher contact : ContactDetail [0..*] 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 description : markdown [0..1] 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 useContext : UsageContext [0..*] A legal or geographic region in which the terminology capabilities is intended to be used jurisdiction : CodeableConcept [0..*] « null (Strength=Extensible) Jurisdiction ValueSet + » Explanation of why this terminology capabilities is needed and why it has been designed as it has purpose : markdown [0..1] 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 copyright : markdown [0..1] 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) kind : code [1..1] « null (Strength=Required) CapabilityStatementKind ! » « This element has or is affected by some invariants C » Whether the server supports lockedDate lockedDate : boolean [0..1] The degree to which the server supports the code search parameter on ValueSet, if it is supported codeSearch : code [0..1] « null (Strength=Required) CodeSearchSupport ! » Software Name the software is known by name : string [1..1] The version identifier for the software covered by this statement version : string [0..1] Implementation Information about the specific installation that this terminology capability statement relates to description : string [1..1] An absolute base URL for the implementation url : url [0..1] CodeSystem URI Canonical identifier for the Code System code system, represented as a URI uri : canonical [0..1] « CodeSystem » The extent of the content of the code system (the concepts and codes it defines) are represented in this resource instance content : code [1..1] « null (Strength=Required) CodeSystemContentMode ! » True if subsumption is supported for this version of the code system subsumption : boolean [0..1] Version For version-less code systems, there should be a single version with no identifier code : string [0..1] « This element has or is affected by some invariants C » If this is the default version for this code system isDefault : boolean [0..1] If the compositional grammar defined by the code system is supported compositional : boolean [0..1] Language Displays supported language : code [0..*] « null (Strength=Required) CommonLanguages ! » Properties supported for $lookup property : code [0..*] Filter Code of the property supported code : code [1..1] Operations supported for the property op : code [1..*] Expansion Whether the server can return nested value sets hierarchical : boolean [0..1] Whether the server supports paging on expansion paging : boolean [0..1] Allow request True if requests for incomplete expansions? expansions are allowed incomplete : boolean [0..1] Documentation about text searching works textFilter : markdown [0..1] Parameter Expansion Parameter name Name of the supported expansion parameter name : code [1..1] Description of support for parameter documentation : string [0..1] ValidateCode Whether translations are validated translations : boolean [1..1] Translation Whether the client must identify the map needsMap : boolean [1..1] Closure If cross-system closure is supported translation : boolean [0..1] 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 software [0..1] 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 implementation [0..1] Filter Properties supported filter [0..*] For the code system, a list of versions that are supported by the server version [0..*] 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 codeSystem [0..*] Supported expansion parameter parameter [0..*] Information about the [ValueSet/$expand](valueset-operation-expand.html) operation expansion [0..1] Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation validateCode [0..1] Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation translation [0..1] Whether the $closure operation is supported closure [0..1]

XML Template 

<TerminologyCapabilities xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <

 <url value="[uri]"/><!-- 0..1 Canonical identifier for this terminology capabilities, represented as a URI (globally unique) -->
 <identifier><!-- 0..* Identifier Additional identifier for the terminology capabilities --></identifier>

 <version value="[string]"/><!-- 0..1 Business version of the terminology capabilities -->
 <

 <name value="[string]"/><!-- I 0..1 Name for this terminology capabilities (computer friendly) -->

 <title value="[string]"/><!-- 0..1 Name for this terminology capabilities (human friendly) -->
 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <experimental value="[boolean]"/><!-- 0..1 For testing purposes, not real usage -->
 <date value="[dateTime]"/><!-- 1..1 Date last changed -->
 <

 <publisher value="[string]"/><!-- 0..1 Name of the publisher/steward (organization or individual) -->

 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the terminology capabilities -->
 <useContext><!-- 0..* UsageContext The context that the content is intended to support --></useContext>
 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for terminology capabilities (if applicable) --></jurisdiction>
 <purpose value="[markdown]"/><!-- 0..1 Why this terminology capabilities is defined -->
 <copyright value="[markdown]"/><!-- 0..1 Use and/or publishing restrictions -->
 <
 <

 <kind value="[code]"/><!-- I 1..1 instance | capability | requirements -->
 <software>  <!-- I 0..1 Software that is covered by this terminology capability statement -->

  <name value="[string]"/><!-- 1..1 A name the software is known by -->
  <version value="[string]"/><!-- 0..1 Version covered by this statement -->
 </software>
 <

 <implementation>  <!-- I 0..1 If this describes a specific instance -->

  <description value="[string]"/><!-- 1..1 Describes this specific instance -->
  <url value="[url]"/><!-- 0..1 Base URL for the implementation -->
 </implementation>
 <lockedDate value="[boolean]"/><!-- 0..1 Whether lockedDate is supported -->
 <codeSystem>  <!-- 0..* A code system supported by the server -->
  <</uri>

  <uri><!-- 0..1 canonical(CodeSystem) Canonical identifier for the code system, represented as a URI --></uri>

  <version>  <!-- 0..* Version of Code System supported -->
   <

   <code value="[string]"/><!-- I 0..1 Version identifier for this version -->

   <isDefault value="[boolean]"/><!-- 0..1 If this is the default version for this code system -->
   <compositional value="[boolean]"/><!-- 0..1 If compositional grammar is supported -->
   <

   <language value="[code]"/><!-- 0..* Language Displays supported -->

   <filter>  <!-- 0..* Filter Properties supported -->
    <code value="[code]"/><!-- 1..1 Code of the property supported -->
    <op value="[code]"/><!-- 1..* Operations supported for the property -->
   </filter>
   <property value="[code]"/><!-- 0..* Properties supported for $lookup -->
  </version>
  <content value="[code]"/><!-- 1..1 not-present | example | fragment | complete | supplement -->

  <subsumption value="[boolean]"/><!-- 0..1 Whether subsumption is supported -->
 </codeSystem>
 <expansion>  <!-- 0..1 Information about the [ValueSet/$expand](valueset-operation-expand.html) operation -->
  <hierarchical value="[boolean]"/><!-- 0..1 Whether the server can return nested value sets -->
  <paging value="[boolean]"/><!-- 0..1 Whether the server supports paging on expansion -->
  <

  <incomplete value="[boolean]"/><!-- 0..1 Allow request for incomplete expansions? -->

  <parameter>  <!-- 0..* Supported expansion parameter -->
   <

   <name value="[code]"/><!-- 1..1 Name of the supported expansion parameter -->

   <documentation value="[string]"/><!-- 0..1 Description of support for parameter -->
  </parameter>
  <textFilter value="[markdown]"/><!-- 0..1 Documentation about text searching works -->
 </expansion>
 <

 <codeSearch value="[code]"/><!-- 0..1 in-compose | in-expansion | in-compose-or-expansion -->

 <validateCode>  <!-- 0..1 Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation -->
  <translations value="[boolean]"/><!-- 1..1 Whether translations are validated -->
 </validateCode>
 <translation>  <!-- 0..1 Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation -->
  <needsMap value="[boolean]"/><!-- 1..1 Whether the client must identify the map -->
 </translation>
 <closure>  <!-- 0..1 Information about the [ConceptMap/$closure](conceptmap-operation-closure.html) operation -->
  <translation value="[boolean]"/><!-- 0..1 If cross-system closure is supported -->
 </closure>
</TerminologyCapabilities>

JSON Template 

{doco
  "resourceType" : "TerminologyCapabilities",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "

  "url" : "<uri>", // Canonical identifier for this terminology capabilities, represented as a URI (globally unique)
  "identifier" : [{ Identifier }], // Additional identifier for the terminology capabilities

  "version" : "<string>", // Business version of the terminology capabilities
  "

  "name" : "<string>", // I Name for this terminology capabilities (computer friendly)

  "title" : "<string>", // Name for this terminology capabilities (human friendly)
  "status" : "<code>", // R!  draft | active | retired | unknown
  "experimental" : <boolean>, // For testing purposes, not real usage
  "date" : "<dateTime>", // R!  Date last changed
  "

  "publisher" : "<string>", // Name of the publisher/steward (organization or individual)

  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "description" : "<markdown>", // Natural language description of the terminology capabilities
  "useContext" : [{ UsageContext }], // The context that the content is intended to support
  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for terminology capabilities (if applicable)
  "purpose" : "<markdown>", // Why this terminology capabilities is defined
  "copyright" : "<markdown>", // Use and/or publishing restrictions
  "
  "

  "kind" : "<code>", // I R!  instance | capability | requirements
  "software" : { // I Software that is covered by this terminology capability statement

    "name" : "<string>", // R!  A name the software is known by
    "version" : "<string>" // Version covered by this statement
  },
  "

  "implementation" : { // I If this describes a specific instance

    "description" : "<string>", // R!  Describes this specific instance
    "url" : "<url>" // Base URL for the implementation
  },
  "lockedDate" : <boolean>, // Whether lockedDate is supported
  "codeSystem" : [{ // A code system supported by the server
    "

    "uri" : "<canonical(CodeSystem)>", // Canonical identifier for the code system, represented as a URI

    "version" : [{ // Version of Code System supported
      "

      "code" : "<string>", // I Version identifier for this version

      "isDefault" : <boolean>, // If this is the default version for this code system
      "compositional" : <boolean>, // If compositional grammar is supported
      "

      "language" : ["<code>"], // Language Displays supported

      "filter" : [{ // Filter Properties supported
        "code" : "<code>", // R!  Code of the property supported
        "op" : ["<code>"] // R!  Operations supported for the property
      }],
      "property" : ["<code>"] // Properties supported for $lookup
    }],
    "content" : "<code>", // R!  not-present | example | fragment | complete | supplement

    "subsumption" : <boolean> // Whether subsumption is supported
  }],
  "expansion" : { // Information about the [ValueSet/$expand](valueset-operation-expand.html) operation
    "hierarchical" : <boolean>, // Whether the server can return nested value sets
    "paging" : <boolean>, // Whether the server supports paging on expansion
    "

    "incomplete" : <boolean>, // Allow request for incomplete expansions?

    "parameter" : [{ // Supported expansion parameter
      "

      "name" : "<code>", // R!  Name of the supported expansion parameter

      "documentation" : "<string>" // Description of support for parameter
    }],
    "textFilter" : "<markdown>" // Documentation about text searching works
  },
  "

  "codeSearch" : "<code>", // in-compose | in-expansion | in-compose-or-expansion

  "validateCode" : { // Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation
    "translations" : <boolean> // R!  Whether translations are validated
  },
  "translation" : { // Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation
    "needsMap" : <boolean> // R!  Whether the client must identify the map
  },
  "closure" : { // Information about the [ConceptMap/$closure](conceptmap-operation-closure.html) operation
    "translation" : <boolean> // If cross-system closure is supported
  }
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:TerminologyCapabilities;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:

  fhir:TerminologyCapabilities.url [ uri ]; # 0..1 Canonical identifier for this terminology capabilities, represented as a URI (globally unique)
  fhir:TerminologyCapabilities.identifier [ Identifier ], ... ; # 0..* Additional identifier for the terminology capabilities

  fhir:TerminologyCapabilities.version [ string ]; # 0..1 Business version of the terminology capabilities
  fhir:

  fhir:TerminologyCapabilities.name [ string ]; # 0..1 I Name for this terminology capabilities (computer friendly)

  fhir:TerminologyCapabilities.title [ string ]; # 0..1 Name for this terminology capabilities (human friendly)
  fhir:TerminologyCapabilities.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:TerminologyCapabilities.experimental [ boolean ]; # 0..1 For testing purposes, not real usage
  fhir:TerminologyCapabilities.date [ dateTime ]; # 1..1 Date last changed
  fhir:

  fhir:TerminologyCapabilities.publisher [ string ]; # 0..1 Name of the publisher/steward (organization or individual)

  fhir:TerminologyCapabilities.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:TerminologyCapabilities.description [ markdown ]; # 0..1 Natural language description of the terminology capabilities
  fhir:TerminologyCapabilities.useContext [ UsageContext ], ... ; # 0..* The context that the content is intended to support
  fhir:TerminologyCapabilities.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for terminology capabilities (if applicable)
  fhir:TerminologyCapabilities.purpose [ markdown ]; # 0..1 Why this terminology capabilities is defined
  fhir:TerminologyCapabilities.copyright [ markdown ]; # 0..1 Use and/or publishing restrictions
  fhir:
  fhir:

  fhir:TerminologyCapabilities.kind [ code ]; # 1..1 I instance | capability | requirements
  fhir:TerminologyCapabilities.software [ # 0..1 I Software that is covered by this terminology capability statement

    fhir:TerminologyCapabilities.software.name [ string ]; # 1..1 A name the software is known by
    fhir:TerminologyCapabilities.software.version [ string ]; # 0..1 Version covered by this statement
  ];
  fhir:

  fhir:TerminologyCapabilities.implementation [ # 0..1 I If this describes a specific instance

    fhir:TerminologyCapabilities.implementation.description [ string ]; # 1..1 Describes this specific instance
    fhir:TerminologyCapabilities.implementation.url [ url ]; # 0..1 Base URL for the implementation
  ];
  fhir:TerminologyCapabilities.lockedDate [ boolean ]; # 0..1 Whether lockedDate is supported
  fhir:TerminologyCapabilities.codeSystem [ # 0..* A code system supported by the server
    fhir:

    fhir:TerminologyCapabilities.codeSystem.uri [ canonical(CodeSystem) ]; # 0..1 Canonical identifier for the code system, represented as a URI

    fhir:TerminologyCapabilities.codeSystem.version [ # 0..* Version of Code System supported
      fhir:

      fhir:TerminologyCapabilities.codeSystem.version.code [ string ]; # 0..1 I Version identifier for this version

      fhir:TerminologyCapabilities.codeSystem.version.isDefault [ boolean ]; # 0..1 If this is the default version for this code system
      fhir:TerminologyCapabilities.codeSystem.version.compositional [ boolean ]; # 0..1 If compositional grammar is supported
      fhir:TerminologyCapabilities.codeSystem.version.language [ code ], ... ; # 0..* Language Displays supported
      fhir:TerminologyCapabilities.codeSystem.version.filter [ # 0..* Filter Properties supported
        fhir:TerminologyCapabilities.codeSystem.version.filter.code [ code ]; # 1..1 Code of the property supported
        fhir:TerminologyCapabilities.codeSystem.version.filter.op [ code ], ... ; # 1..* Operations supported for the property
      ], ...;
      fhir:TerminologyCapabilities.codeSystem.version.property [ code ], ... ; # 0..* Properties supported for $lookup
    ], ...;
    fhir:TerminologyCapabilities.codeSystem.content [ code ]; # 1..1 not-present | example | fragment | complete | supplement

    fhir:TerminologyCapabilities.codeSystem.subsumption [ boolean ]; # 0..1 Whether subsumption is supported
  ], ...;
  fhir:TerminologyCapabilities.expansion [ # 0..1 Information about the [ValueSet/$expand](valueset-operation-expand.html) operation
    fhir:TerminologyCapabilities.expansion.hierarchical [ boolean ]; # 0..1 Whether the server can return nested value sets
    fhir:TerminologyCapabilities.expansion.paging [ boolean ]; # 0..1 Whether the server supports paging on expansion
    fhir:

    fhir:TerminologyCapabilities.expansion.incomplete [ boolean ]; # 0..1 Allow request for incomplete expansions?

    fhir:TerminologyCapabilities.expansion.parameter [ # 0..* Supported expansion parameter
      fhir:

      fhir:TerminologyCapabilities.expansion.parameter.name [ code ]; # 1..1 Name of the supported expansion parameter

      fhir:TerminologyCapabilities.expansion.parameter.documentation [ string ]; # 0..1 Description of support for parameter
    ], ...;
    fhir:TerminologyCapabilities.expansion.textFilter [ markdown ]; # 0..1 Documentation about text searching works
  ];
  fhir:

  fhir:TerminologyCapabilities.codeSearch [ code ]; # 0..1 in-compose | in-expansion | in-compose-or-expansion

  fhir:TerminologyCapabilities.validateCode [ # 0..1 Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation
    fhir:TerminologyCapabilities.validateCode.translations [ boolean ]; # 1..1 Whether translations are validated
  ];
  fhir:TerminologyCapabilities.translation [ # 0..1 Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation
    fhir:TerminologyCapabilities.translation.needsMap [ boolean ]; # 1..1 Whether the client must identify the map
  ];
  fhir:TerminologyCapabilities.closure [ # 0..1 Information about the [ConceptMap/$closure](conceptmap-operation-closure.html) operation
    fhir:TerminologyCapabilities.closure.translation [ boolean ]; # 0..1 If cross-system closure is supported
  ];
]

Changes since Release 4

TerminologyCapabilities
TerminologyCapabilities.identifier
  • No Changes Added Element
TerminologyCapabilities.codeSystem.version.language
  • Add Binding http://hl7.org/fhir/ValueSet/languages|5.0.0-ballot (required)
  • Add Binding http://hl7.org/fhir/ValueSet/languages|5.0.0-ballot (required)
TerminologyCapabilities.codeSystem.content
  • Added Mandatory Element

See the Full Difference for further information

This analysis is available as XML or JSON .

Conversions between R3 and R4 See R3 <--> R4 Conversion Maps (status = Not Mapped)

 

See the Profiles & Extensions and the alternate Additional definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see , the extensions spreadsheet version & the dependency analysis

4.12.4.1 Terminology Bindings

Path Definition Type Reference
TerminologyCapabilities.status

The lifecycle status of an artifact.

Required PublicationStatus
TerminologyCapabilities.jurisdiction

This value set defines a base set of codes for country, country subdivision and region for indicating where a resource is intended to be used.

Note: The codes for countries and country subdivisions are taken from ISO 3166 icon while the codes for "supra-national" regions are from UN Standard country or area codes for statistical use (M49) icon.

 Extensible Jurisdiction ValueSet
TerminologyCapabilities.kind

How a capability statement is intended to be used.

Required CapabilityStatementKind
TerminologyCapabilities.codeSystem.version.language

This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47)

Required CommonLanguages
TerminologyCapabilities.codeSystem.content

The extent of the content of the code system (the concepts and codes it defines) are represented in a code system resource.

Required CodeSystemContentMode
TerminologyCapabilities.codeSearch

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

Required CodeSearchSupport

4.12.4.2 Constraints

id UniqueKey Level Location Description Expression
tcp-0 img  cnl-0 Warning (base) Name should be usable as an identifier for the module by machine processing applications such as code generation name.exists() implies name.matches('[A-Z]([A-Za-z0-9_]){0,254}') name.matches('[A-Z]([A-Za-z0-9_]){1,254}')
tcp-1 img  cnl-1 Warning TerminologyCapabilities.url URL should not contain | or # - these characters make processing canonical references problematic url.matches('([^|#])*')
img  tcp-1 Rule TerminologyCapabilities.codeSystem If there is more than one version, a version code must be defined version.count() > 1 implies version.all(code.exists())
tcp-2 img  tcp-2 Rule (base) A Terminology Capability Statement statement SHALL have at least one of description, software, or implementation element. element (description.count() + software.count() + implementation.count()) > 0
tcp-3 img  tcp-3 Rule (base) If kind = instance, implementation must be present and software may be present (kind != 'instance') or implementation.exists()
tcp-4 img  tcp-4 Rule (base) If kind = capability, implementation must be absent, software must be present (kind != 'capability') or (implementation.exists().not() and software.exists())
tcp-5 img  tcp-5 Rule (base) If kind = requirements, implementation and software must be absent (kind!='requirements') or (implementation.exists().not() and software.exists().not())
img  tcp-6 Rule (base) Each instance of the codeSystem element must represent a distinct code system. codeSystem.uri.isDistinct()
img  tcp-7 Rule TerminologyCapabilities.codeSystem Each version.code element must be distinct for a particular code system. version.code.isDistinct()
img  tcp-8 Rule TerminologyCapabilities.codeSystem A codeSystem element instance may have at most one version.isDefault element with a value of 'true'. version.where(isDefault = true).count() <= 1

4.12.5 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
context token A use context assigned to the terminology capabilities (TerminologyCapabilities.useContext.value as CodeableConcept)
context-quantity quantity A quantity- or range-valued use context assigned to the terminology capabilities (TerminologyCapabilities.useContext.value as Quantity) | (TerminologyCapabilities.useContext.value as Range)
context-type token A type of use context assigned to the terminology capabilities TerminologyCapabilities.useContext.code
context-type-quantity composite A use context type and quantity- or range-based value assigned to the terminology capabilities On TerminologyCapabilities.useContext:
  context-type: code
  context-quantity: value.as(Quantity) value.ofType(Quantity) | value.as(Range) value.ofType(Range)
context-type-value composite A use context type and value assigned to the terminology capabilities On TerminologyCapabilities.useContext:
  context-type: code
  context: value.as(CodeableConcept) value.ofType(CodeableConcept)
date N date The terminology capabilities publication date TerminologyCapabilities.date
description N string The description of the terminology capabilities TerminologyCapabilities.description
identifier token External identifier for the terminology capabilities TerminologyCapabilities.identifier
jurisdiction token Intended jurisdiction for the terminology capabilities TerminologyCapabilities.jurisdiction
name N string Computationally friendly name of the terminology capabilities TerminologyCapabilities.name
publisher N string Name of the publisher of the terminology capabilities TerminologyCapabilities.publisher
status N token The current status of the terminology capabilities TerminologyCapabilities.status
title N string The human-friendly name of the terminology capabilities TerminologyCapabilities.title
url N uri The uri that identifies the terminology capabilities TerminologyCapabilities.url
version N token The business version of the terminology capabilities TerminologyCapabilities.version