This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
FHIR Infrastructure Work Group | Maturity Level: N | Normative (from v4.0.0) | Use Context: Not Intended for Production use |
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.3.0-snapshot1 |
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 Resource | XML / JSON |
This value set is used in the following places:
http://hl7.org/fhir/capability-statement-kind
This expansion generated 20 Dec 2021
This value set contains 3 concepts
Expansion based on CapabilityStatementKind v4.3.0-snapshot1 (CodeSystem)
All codes in this table are from the system http://hl7.org/fhir/capability-statement-kind
Code | Display | Definition |
instance | Instance | The CapabilityStatement instance represents the present capabilities of a specific system instance. This is the kind returned by /metadata for a FHIR server end-point. |
capability | Capability | The CapabilityStatement instance represents the capabilities of a system or piece of software, independent of a particular installation. |
requirements | Requirements | The 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:
Lvl | A 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 |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
Display | The 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 |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |