Snapshot 3: Connectathon 32 Base

This page is part of the FHIR Specification (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B

Vocabulary icon Work GroupMaturity Level: N/AStandards Status: Informative
Core profiles and extensions defined for the ValueSet resource
Profiles:
ShareableValueSetEnforces the minimum information set for the value set metadata required by HL7 and other organizations that share and publish value sets
PublishableValueSetDefines and enforces the minimum expectations for publication and distribution of a value set, typically as part of an artifact repository or implementation guide publication
ComputableValueSetDefines a computable value set as one that SHALL have an expression-based definition (i.e. a value set defined intensionally using expressions of the code systems involved) and MAY have an expansion included. The expression-based definition SHALL be represented in only one of three ways; using the compose element, using the expression extension, or using the rules-text extension to provide a step-by-step process for expanding the value set definition
ExecutableValueSetDefines an executable value set as one that SHALL have an expansion included, as well as a usage warning indicating the expansion is a point-in-time snapshot and must be maintained over time for production usage. The value set expansion specifies the timestamp when the expansion was produced, SHOULD contain the parameters used for the expansion, and SHALL contain the codes that are obtained by evaluating the value set definition. If this is ONLY an executable value set, a computable definition of the value set must be obtained to compute the updated expansion.
Extensions:
valueset-concept-definitionVSConceptDefinition :

A definition that describes the meaning of this code when used as part of this value set.

valueset-concept-commentsVSConceptComments :

A comment that explains how this code is used in this context (where the value set is expected to be used).

valueset-otherNameVSOtherName :

Natural language names identifying the value set. These names should be usable as an identifier for the module by machine processing applications such as code generation.

valueset-sourceReferenceVSSourceReference :

This text is intended to act as a citation to work done elsewhere that is not part of the current stewarding process where the referenced source is in some way a basis of the current value set definition.

valueset-keyWordVSKeyword :

Word or words used in an information retrieval system to indicate the content of the value set. (deprecated)

valueset-usageVS Usage :

Consumers of the value set and the implementations, projects or standards that the author has utilized the value set in.

valueset-workflowStatusDescriptionWorkflowStatusDescription :

Workflow Status is used to represent details of the value set development process while in a single Activity Status.

valueset-trusted-expansionVSTrustedExpansion :

Indicates an authoritative source for performing value set expansions.

valueset-labelVSLabel :

The label to list in front of a code when presenting a list of possible values in a questionnaire-like fashion.

valueset-conceptOrderVSConceptOrder :

Identifies the relative order in which concepts within the value set should be presented to a user.

valueset-systemRefVSSystemReference :

The formal URI for the code system. I.e. ValueSet.codeSystem.system (or its equivalent).

valueset-caseSensitiveVSCaseSensitive :

If this a case sensitive code.

valueset-referenceVSReference :

A logical reference (e.g. a reference to ValueSet.url) that identifies the value set/version that identifies the set of possible coded values this coding was chosen from or constrained by.

valueset-expansionSourceVSExpansionSource :

The logical URL of the ValueSet definition that was used to generate this expansion.

valueset-unclosedVS Unclosed :

Marks that the expansion is incomplete, and values other than those listed may be valid. This may be used because post-coordinated codes are allowed, and no practical expansion can be produced.

valueset-toocostlyVSToocostly :

Marks that the expansion is incomplete, because the full value set is too large to represent, and the client asked for an incomplete fragment.

valueset-mapVSMap :

A reference to a concept map that is relevant for the interpretation of this value set.

valueset-warningVS Warning :

An extra warning about the correct use of the value set.

valueset-systemVSSystem :

Allows a direct reference to the code system for FHIR query.

valueset-supplementVSSupplement :

This extension declares that a value set depends on a particular supplement and should not be used in its absence.

valueset-parameterSourceVSParameterSource :

Declares what the source of this parameter is.

valueset-deprecatedVSDeprecated :

if true, indicates that the concept is deprecated from the value set - that is, it should not be used, and is planned to be withdrawn.

valueset-special-statusVSSpecialStatus :

A special note for implementers about the status of the resource.

valueset-extensibleVSExtensible :

Whether this is intended to be used with an extensible binding or not.

valueset-authoritativeSourceVSAuthoritativeSource :

A reference to the authoritative accessible, persisted source of truth of the entire Value Set Definition, including textual information and available versions.

valueset-expressionVSExpression :

An expression that provides an alternative definition of the content of the value set (compose). There are two different ways to use this expression extension: If both an expression (this extension) and a compose element is present, the compose is understood to the make the same statement as the expression. If there is no compose, the expression is the only definition of the value set, and the value set can only be processed by a server that understands the expression syntax, the expression is computable.

valueset-rules-textVSRulesText :

An expression that provides an alternative definition of the content of the value set in some form that is not computable - e.g instructions that could only be followed by a human.

valueset-otherTitleVSOtherTitle :

Human readable titles for the valueset.

valueset-systemTitleVSSystemTitle :

The human-readable name for the code system.

valueset-systemNameVSSystemName :

The human-readable name for the code system.

valueset-compose-createdByVSComposeCreatedBy :

User who created the compose for the ValueSet.

valueset-compose-creationDateVSComposeCreationDate :

Date the compose was created.

valueset-compose-include-valueSetTitleVSIncludeVSTitle :

Human readable name for the included Value Set.

Search parameters defined by this package. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPathsSource
authorstringOptional Extensions ElementCodeSystem.extension('http://hl7.org/fhir/StructureDefinition/valueset-author').valueXML / JSON
effectivedateOptional Extensions ElementCodeSystem.extension('http://hl7.org/fhir/StructureDefinition/valueset-effectiveDate').valueXML / JSON
enddateOptional Extensions ElementCodeSystem.extension('http://hl7.org/fhir/StructureDefinition/valueset-expirationDate').valueXML / JSON
keywordstringOptional Extensions ElementCodeSystem.extension('http://hl7.org/fhir/StructureDefinition/valueset-keyWord').valueXML / JSON
workflowtokenOptional Extensions ElementCodeSystem.extension('http://hl7.org/fhir/StructureDefinition/valueset-workflowStatus').valueXML / JSON