Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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 R3

4.4.1.56 Value Set http://hl7.org/fhir/ValueSet/capability-statement-kind

FHIR Infrastructure Work Group Maturity Level: NNormative (from v4.0.0) Use Context: Any
This page has been approved as part of an ANSI standard. See the Conformance Package for further details.

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/capability-statement-kind
Version:4.2.0
Name:CapabilityStatementKind
Title:CapabilityStatementKind
Definition:

How a capability statement is intended to be used.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.198 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

4.4.1.56.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.4.1.56.2 Expansion

This expansion generated 31 Dec 2019

This value set contains 3 concepts

Expansion based on http://hl7.org/fhir/capability-statement-kind version 4.2.0

All codes from system http://hl7.org/fhir/capability-statement-kind

CodeDisplayDefinition
instanceInstanceThe CapabilityStatement instance represents the present capabilities of a specific system instance. This is the kind returned by /metadata for a FHIR server end-point.
capabilityCapabilityThe CapabilityStatement instance represents the capabilities of a system or piece of software, independent of a particular installation.
requirementsRequirementsThe CapabilityStatement instance represents a set of requirements for other systems to meet; e.g. as part of an implementation guide or 'request for proposal'.

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code