FHIR Application Feature Framework Implementation Guide
1.0.0-ballot - STU1 Ballot International flag

This page is part of the FHIR Application Feature Framework Implementation Guide (v1.0.0-ballot: STU 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions

CodeSystem: Capability Feature Value CS

Official URL: http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs Version: 1.0.0-ballot
Standards status: Trial-use Maturity Level: 1 Computable Name: CapabilityFeatureValueCS

Copyright/Legal: This CodeSystem is not copyrighted.

A feature value that may be declared in a capability statement.

This Code system is referenced in the content logical definition of the following value sets:

Generated Narrative: CodeSystem capability-feature-value-cs

This case-sensitive code system http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs defines the following codes in a Is-A hierarchy:

LvlCodeDisplayDefinition
1 values Root concept for all feature values
2   booleans Values that are booleans
3     true Value is true
3     false Value is false
2   versioning Values for versioning feature
3     no-version No VersionId Support VersionId meta-property is not supported (server) or used (client).
3     versioned Versioned VersionId meta-property is supported (server) or used (client).
3     versioned-update VersionId tracked fully VersionId must be correct for updates (server) or will be specified (If-match header) for updates (client).
2   conditional-read-status Values for conditional-read-status
3     cond-read-not-supported Not Supported No support for conditional reads.
3     modified-since If-Modified-Since Conditional reads are supported, but only with the If-Modified-Since HTTP Header.
3     not-match If-None-Match Conditional reads are supported, but only with the If-None-Match HTTP Header.
3     full-support Full Support Conditional reads are supported, with both If-Modified-Since and If-None-Match HTTP Headers.
2   conditional-delete-status Values for conditional-delete-status
3     cond-delete-not-supported Not Supported No support for conditional deletes.
3     single Single Deletes Supported Conditional deletes are supported, but only single resources at a time.
3     multiple Multiple Deletes Supported Conditional deletes are supported, and multiple resources can be deleted in a single interaction.
2   reference-handling-policy Values for reference-handling-policy
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').
3     logical Logical References The server allows logical references (i.e. using Reference.identifier).
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).
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.
3     local Local References Only The server does not support references that point to other servers.