Set to true of the concept has been deprecated (still can be used, but soon to be withdrawn).

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

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

Refers to another code defined within the code system that is also subsumed by this code. I.e. This concept subsumes the referenced concept. Because meaning is inferred from hierarchy as well as definition, the presence of this extension modifies the meaning of the extended concept.

Human readable names for the valueset.

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.

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

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

Workflow Status is used to represent details of the value set development process while the value set has an Activity Status of Preliminary. The development of a value set often follows a formal workflow process from initiation to completion, and this element carries the state variable for this state machine. The assumption is that when first created a value set would have a workflow state of Draft. Additional workflow states may be used.

This is the first date-time when the value set version becomes active, so this value is present on Inactive value set versions as well. The start Date_time is expected to be as of 0001 UTC of the Effective Date.

The date when the value set version is no longer expected to be used to create new content. This is the first date-time when the value set version becomes Inactive, so this value MUST present on all Inactive value set versions. The start Date_time is expected to be as of 0001 UTC of the Expiration Date.

User or Org actually involved in creating the value set content.

Each comment is a time-stamped entry of arbitrary length that is not editable except by anyone in the author group.

Indicates an authoritative source for performing value set expansions.

Information on changes made to the Value Set Definition over time, and also has a contained audit trail of all such changes.

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

A numeric value that allows the comparison (less than, greater than) or other numerical manipulation of a concept (e.g. Adding up components of a score).

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

The human-readable name for the code system.

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

If this a case sensitive code.

The OID assigned the same object as the URI points to. Examples include OIDs assigned to code systems like SNOMED CT (urn:oid:2.16.840.1.113883..6.96) or LOINC (urn:oid:2.16.840.1.113883.6.1), value sets like AdministrativeGender (urn:oid:2.16.840.1.113883.11.1), identification systems like SSN (urn:oid:2.16.840.1.113883.4.1) etc.

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.

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

Marks that the expansion is incomplete, abd other values that those listed may be valid.

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

A code that replaces this - use this code instead.

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