• Using Codes
• Code Systems
• Value Sets
• Concept Maps
• Identifier Systems

4.3.16.29 Code System http://hl7.org/fhir/CodeSystem/capability-features

Vocabulary Work Group

Maturity Level: 0

Informative

Use Context: Any

This is a code system defined by the FHIR project.

Summary

This Code system is used in the following value sets:

• ValueSet: Capability Features (A feature that may be declared in a capability statement)
• ValueSet: Capability Feature Values (A vaule for a feature that may be declared in a capability statement)

4.3.16.29.1 Content

Properties

Name	Code	URL	Description	Type
Kind	kind	http://hl7.org/fhir/CodeSystem/capability-features#properties-kind	This 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
Context	context	http://hl7.org/fhir/CodeSystem/capability-features#properties-context	This property defines the contexts to which this feature applies	code
Values	values	http://hl7.org/fhir/CodeSystem/capability-features#properties-values	This specifies what the values for a feature can be	code
Qualification	qualification	http://hl7.org/fhir/CodeSystem/capability-features#properties-qualification	This specifies how a context entry can be qualified	code
Scope	scope	http://hl7.org/fhir/CodeSystem/capability-features#properties-scope	This property defines the feature scope in which a feature exists (e.g. sub-context)	code

This code system http://hl7.org/fhir/CodeSystem/capability-features defines the following codes:

Lvl	Code	Display	Definition	Kind	Context	Values	Qualification	Scope
1	features	Root concept for all feature definitions		internal
2	feature-header	Whether the server supports the Required-Feature header by which a client makes a feature as mandatory for processing a requrest properly		feature	rest	#booleans
2	security-cors			feature	rest	#booleans
2	security-service			feature	rest	http://hl7.org/fhir/ValueSet/restful-security-service
2	versioning			feature	rest.resource	#versioning
2	readHistory			feature	rest.resource	#booleans
2	updateCreate			feature	rest.resource	#booleans
2	updateCreate			feature	rest.resource	#booleans
2	conditionalCreate			feature	rest.resource	#booleans
2	conditionalRead			feature	rest.resource	#conditional-read-status
2	conditionalUpdate			feature	rest.resource	#booleans
2	conditionalDelete			feature	rest.resource	#conditional-delete-status
2	referencePolicy			feature	rest.resource	#reference-handling-policy
2	searchInclude			feature	rest.resource	http://hl7.org/fhir/ValueSet/search-parameters
2	searchRevInclude			feature	rest.resource	http://hl7.org/fhir/ValueSet/search-parameters
1	values	Root concept for all feature values		internal
2	booleans	Values that are booleans		internal
3	true	Value is true		value
3	false	Value is false		value
2	versioning	Values for versioning feature		internal
3	no-version	No VersionId Support	VersionId meta-property is not supported (server) or used (client).	value
3	versioned	Versioned	VersionId meta-property is supported (server) or used (client).	value
3	versioned-update	VersionId tracked fully	VersionId 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-status		internal
3	not-supported	Not Supported	No support for conditional reads.	value
3	modified-since	If-Modified-Since	Conditional reads are supported, but only with the If-Modified-Since HTTP Header.	value
3	not-match	If-None-Match	Conditional reads are supported, but only with the If-None-Match HTTP Header.	value
3	full-support	Full Support	Conditional reads are supported, with both If-Modified-Since and If-None-Match HTTP Headers.	value
2	conditional-delete-status	Values for conditional-delete-status		internal
3	not-supported	Not Supported	No support for conditional deletes.	value
3	single	Single Deletes Supported	Conditional deletes are supported, but only single resources at a time.	value
3	multiple	Multiple Deletes Supported	Conditional deletes are supported, and multiple resources can be deleted in a single interaction.	value
2	reference-handling-policy	Values for reference-handling-policy		internal
3	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').	value
3	logical	Logical References	The server allows logical references (i.e. using Reference.identifier).	value
3	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).	value
3	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.	value
3	local	Local References Only	The server does not support references that point to other servers.	value
1	contexts	Root concept for all context definitions		internal
2	rest	The REST API as a whole		context			server|client
2	resource	Support for a resource on the REST API		context			resource type	rest
2	interaction	Support for a interaction (not on a resource) on the REST API		context			interaction.code	rest, resource
2	searchParam	Support for a search parameter across resources on the REST API		context			searchparam.code	rest, resource
2	operation	Support for a operation not on a resource on the REST API		context			operation.name	rest, resource
2	compartment	Support for a compartment on the REST API		context			compartment.code	rest

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

Explanation of the columns that may appear on this page: