This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - 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
FHIR Infrastructure Work Group | Maturity Level: 0 | Trial Use | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/capability-feature-value |
Version: | 4.6.0 |
Name: | CapabilityFeatureValue |
Title: | Capability Feature Values |
Definition: | A vaule for a feature that may be declared in a capability statement |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.3.0 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
http://hl7.org/fhir/CodeSystem/capability-features
where kind = value
This expansion generated 15 Apr 2021
This value set contains 16 concepts
Expansion based on Capability Features v4.6.0 (CodeSystem)
All codes from system http://hl7.org/fhir/CodeSystem/capability-features
Code | Display | Definition |
true | Value is true | |
false | Value is false | |
no-version | No VersionId Support | VersionId meta-property is not supported (server) or used (client). |
versioned | Versioned | VersionId meta-property is supported (server) or used (client). |
versioned-update | VersionId tracked fully | VersionId must be correct for updates (server) or will be specified (If-match header) for updates (client). |
not-supported | Not Supported | No support for conditional reads. |
modified-since | If-Modified-Since | Conditional reads are supported, but only with the If-Modified-Since HTTP Header. |
not-match | If-None-Match | Conditional reads are supported, but only with the If-None-Match HTTP Header. |
full-support | Full Support | Conditional reads are supported, with both If-Modified-Since and If-None-Match HTTP Headers. |
single | Single Deletes Supported | Conditional deletes are supported, but only single resources at a time. |
multiple | Multiple Deletes Supported | Conditional deletes are supported, and multiple resources can be deleted in a single interaction. |
literal | Literal References | The server supports and populates Literal references (i.e. using Reference.reference) where they are known (this code does not guarantee that all references are literal; see 'enforced'). |
logical | Logical References | The server allows logical references (i.e. using Reference.identifier). |
resolves | Resolves References | The server will attempt to resolve logical references to literal references - i.e. converting Reference.identifier to Reference.reference (if resolution fails, the server may still accept resources; see logical). |
enforced | Reference Integrity Enforced | The server enforces that references have integrity - e.g. it ensures that references can always be resolved. This is typically the case for clinical record systems, but often not the case for middleware/proxy systems. |
local | Local References Only | The server does not support references that point to other servers. |
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 |