VocApp-ValSetChanges/ValSetMenu
Contents
Changes from a Value Set Selection
The figure at right shows the various options that can be selected when a Value Set node is selected in the Value Set Navigator window, and the right mouse button is clicked. In each case, the menu selection starts a process to define changes to be applied to the selected value set. (NOTE: The first selection Create Value Set actually creates a value set as a child (sub-type) of the selected value set.) These selections are intended to cover all possible operations on a value set node. In aggregate, the functions provided include:
Further, in several cases, these operations are redundant or partially so. For example, both Create Value Set and Bind Concept Domain to Value Set allow a value set to be bound to a concept domain, but only in Create Value Set can one also define a new concept domain. |
Create Value Set
This action creates a new Value Set as a child of the Value set that was selected when the menu item was chosen. This is a multi-part operation that includes:
- Complete specification of the value set including:
- Name, description and whether "abstract or "specializable";
- Parent-child reference from the selected value set to the new one; and
- Assignment of a head code (if specializable), including the option of defining a new concept to be the head code.
- Option of binding the new value set to a concept domain, which may be created if the target does not already exist.
- Option to add existing or new coded concepts to the value set
- Option to add parent-child value set references from the new value set to existing value sets
Operations 3 and 4, above, are identical to stand-alone operations described in other sections below. They will be discussed in general terms in this section and a hyper link to the detailed discussion will be provided.
Process sequence to Create Value Set
|
|
Subprocess to specify Value Set |
|
|
|
|
|
|
|
|
|
|
|
|
|
Subprocess to Bind to domain |
|
|
|
|
|
|
|
Subprocess to Add codes |
|
|
|
Subprocess to Add child sets |
|
|
|
Subprocess to finish creation |
|
|
Delete Value Set
This selection is used to delete a Value Set from the data base.
CAUTION:
Since Value Sets may contain one or more leaf terms (coded concepts) and may reference one or more child value sets, this process leaves contained coded concepts and value sets in limbo. They remain as part of the Code System and Value Set tables, but will not be exposed because there is no longer a parent under which they will appear. In general, if you wish to remove a value set, you should also plan the disposition of its children by, for example assigning them to one or more remaining value sets. To do this, you will need to prepare a multi-step change proposal that:
|
Process sequence to Remove reference
|
|
|
Add Codes to Value Set
Value Sets may contain one or more leaf terms (coded concepts) and one or more child value sets. This process allows one to add leaf terms that are directly within the value set.
This process has multiple layers, as it also implements the function to create coded concepts in the relevant Code System, which (currently) cannot be done as a direct operation on the Code System.
CAUTION:
A coded term cannot be added to a value set if it is already in that value set or if it is in one of the descendant value sets of that value set. If you desire to move a coded concept from a descendant value set to its parent or an ancestor, you will need to prepare a two-step change proposal that:
|
Process sequence to Add codes
|
|
|
|
Subprocess to Add Existing codes |
|
|
|
|
|
|
|
|
|
Subprocess to Create new codes |
|
|
|
|
|
|
|
Subprocess to Complete addition |
|
|
Remove Codes from a Value Set
Value Sets may contain one or more leaf terms (coded concepts) and one or more child value sets. This process allows one to remove leaf terms that are directly within the value set. It will not allow removal of the "head codes" of child value sets, nor the leaf terms that are members of the child value sets.
CAUTION:
Removing a coded term from a value set leaves the coded concept in limbo. It remains part of the Code System, but will not be exposed because there is no longer a parent under which it will appear. In general, a code should only be removed from a value set in one of two circumstances:
For other purposes, the Retire Code function is probably more appropriate. |
Process sequence to Remove codes
|
|
|
Update Value Set Description
Each Value Set has a description that defines what the value set represents and/or contains. These definitions may include sections for the definition, discussion of the rationale underlying the value set. and examples of coded terms it may contain.
Process sequence to Update description
|
|
|
|
|
Bind Concept Domain to Value Set
Each Concept Domain in the terminology may be bound to one or more value sets. Where there are multiple bindings, each binding is in a particular context or binding realm. This function allows a predefined value set (the one selected to start the process) to be bound to a predefined concept domain. It uses the "default" context (no value) meaning that it will be bound in the universal (UV) realm.
Data definition for Binding Concept Domain to Value Set
CAUTIONS:
|
Process sequence to Bind Concept Domain
|
|
|
Add Value Set References
Although "reference" is a generic term, the only kind of value set reference included in the Vocabulary Maintenance Language, and in the underlying Access data base tables, is a parent-child relationship wherein the reference is from the parent to the child. This action will allow the user to select one or more value sets to be added as children to the parent Value Set selected in the Value Set Navigator.
|
|
|
|
|
|
|
Remove Value Set References
Although "reference" is a generic term, the only kind of value set reference included in the Vocabulary Maintenance Language, and in the underlying Access data base tables, is a parent-child relationship wherein the reference is from the parent to the child. This action will remove one or more parent-to-child references from the parent Value Set selected in the Value Set Navigator.
CAUTIONS:
Removing a value set reference leaves the value set and its code content in limbo. They remain part of the Code System and part of the Value Set definitions, but will not be exposed because there is no longer a parent under which they will appear. In general, a code system reference should only be removed in one of two circumstances:
For any other purpose, the Delete Value Set function is probably more appropriate. |
Process sequence to Remove reference
|
|
|
|
|