Release 5 Draft Ballot Code System

Vocabulary Work Group Maturity Level: 0Informative Use Context: Any

This is a code system defined by the FHIR project.


Defining URL:
Title:Capability Features

A feature that may be declared in a capability statement. For discussion, see CapabilityStatement2 Notes

OID: (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:


Kindkind property defines whether the concept is a feature (that can be present or absent, or have a feature) or a value (the value of a defined feature), or a context (can be used to qualify the scope of a feature)code
Contextcontext property defines the contexts to which this feature appliescode
Valuesvalues specifies what the values for a feature can be code
Qualificationqualification specifies how a context entry can be qualifiedcode
Scopescope property defines the feature scope in which a feature exists (e.g. sub-context)code

This code system defines the following codes:

1features Root concept for all feature definitionsinternal
2  feature-header Whether the server supports the Required-Feature header by which a client makes a feature as mandatory for processing a requrest properlyfeaturerest#booleans
2  security-cors featurerest#booleans
2  security-service featurerest
2  versioning featurerest.resource#versioning
2  readHistory featurerest.resource#booleans
2  updateCreate featurerest.resource#booleans
2  updateCreate featurerest.resource#booleans
2  conditionalCreate featurerest.resource#booleans
2  conditionalRead featurerest.resource#conditional-read-status
2  conditionalUpdate featurerest.resource#booleans
2  conditionalDelete featurerest.resource#conditional-delete-status
2  referencePolicy featurerest.resource#reference-handling-policy
2  searchInclude featurerest.resource
2  searchRevInclude featurerest.resource
1values Root concept for all feature valuesinternal
2  booleans Values that are booleansinternal
3    true Value is truevalue
3    false Value is falsevalue
2  versioning Values for versioning featureinternal
3    no-version No VersionId SupportVersionId meta-property is not supported (server) or used (client).value
3    versioned VersionedVersionId meta-property is supported (server) or used (client).value
3    versioned-update VersionId tracked fullyVersionId must be correct for updates (server) or will be specified (If-match header) for updates (client).value
2  conditional-read-status Values for conditional-read-statusinternal
3    not-supported Not SupportedNo support for conditional reads.value
3    modified-since If-Modified-SinceConditional reads are supported, but only with the If-Modified-Since HTTP Header.value
3    not-match If-None-MatchConditional reads are supported, but only with the If-None-Match HTTP Header.value
3    full-support Full SupportConditional reads are supported, with both If-Modified-Since and If-None-Match HTTP Headers.value
2  conditional-delete-status Values for conditional-delete-statusinternal
3    not-supported Not SupportedNo support for conditional deletes.value
3    single Single Deletes SupportedConditional deletes are supported, but only single resources at a time.value
3    multiple Multiple Deletes SupportedConditional deletes are supported, and multiple resources can be deleted in a single interaction.value
2  reference-handling-policy Values for reference-handling-policyinternal
3    literal Literal ReferencesThe 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').value
3    logical Logical ReferencesThe server allows logical references (i.e. using Reference.identifier).value
3    resolves Resolves ReferencesThe 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).value
3    enforced Reference Integrity EnforcedThe 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.value
3    local Local References OnlyThe server does not support references that point to other servers.value
1contexts Root concept for all context definitionsinternal
2  rest The REST API as a wholecontextserver|client
2  resource Support for a resource on the REST APIcontextresource typerest
2  interaction Support for a interaction (not on a resource) on the REST APIcontextinteraction.coderest, resource
2  searchParam Support for a search parameter across resources on the REST APIcontextsearchparam.coderest, resource
2  operation Support for a operation not on a resource on the REST APIcontextoperation.namerest, resource
2  compartment Support for a compartment on the REST APIcontextcompartment.coderest


See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. 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