FHIR Application Feature Framework Implementation Guide, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/capstmt/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/uv/application-feature/ValueSet/capability-feature-value-vs | Version: 1.0.0-ballot | |||
Standards status: Trial-use | Maturity Level: 1 | Computable Name: CapabilityFeatureValueVS |
A vaule for a feature that may be declared in a capability statement
References
Generated Narrative: ValueSet capability-feature-value-vs
Last updated: 2021-12-19 08:15:41+1100
Profile: Shareable ValueSet
http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs
Generated Narrative: ValueSet
Last updated: 2021-12-19 08:15:41+1100
Profile: Shareable ValueSet
Expansion based on codesystem Capability Feature Value CS v1.0.0-ballot (CodeSystem)
This value set contains 23 concepts
Level | Code | System | Display | Definition |
1 | values | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Root concept for all feature values | |
2 | booleans | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Values that are booleans | |
3 | true | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Value is true | |
3 | false | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Value is false | |
2 | versioning | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Values for versioning feature | |
3 | no-version | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | No VersionId Support | VersionId meta-property is not supported (server) or used (client). |
3 | versioned | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Versioned | VersionId meta-property is supported (server) or used (client). |
3 | versioned-update | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | VersionId tracked fully | VersionId must be correct for updates (server) or will be specified (If-match header) for updates (client). |
2 | conditional-read-status | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Values for conditional-read-status | |
3 | cond-read-not-supported | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Not Supported | No support for conditional reads. |
3 | modified-since | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | If-Modified-Since | Conditional reads are supported, but only with the If-Modified-Since HTTP Header. |
3 | not-match | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | If-None-Match | Conditional reads are supported, but only with the If-None-Match HTTP Header. |
3 | full-support | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Full Support | Conditional reads are supported, with both If-Modified-Since and If-None-Match HTTP Headers. |
2 | conditional-delete-status | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Values for conditional-delete-status | |
3 | cond-delete-not-supported | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Not Supported | No support for conditional deletes. |
3 | single | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Single Deletes Supported | Conditional deletes are supported, but only single resources at a time. |
3 | multiple | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Multiple Deletes Supported | Conditional deletes are supported, and multiple resources can be deleted in a single interaction. |
2 | reference-handling-policy | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Values for reference-handling-policy | |
3 | literal | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | 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 | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Logical References | The server allows logical references (i.e. using Reference.identifier). |
3 | resolves | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | 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 | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | 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 | http://hl7.org/fhir/uv/application-feature/CodeSystem/capability-feature-value-cs | Local References Only | The server does not support references that point to other servers. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | 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) |
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 |