Asserted Value Sets are not a formal model element in LexEVS. There is no asserted value set object to instantiate, instead these value set representations are expressed directly in the terminology and represented in ways similar to LexEVS models of Value Set Definitions and Coding Schemes.
Value Sets have been asserted directly in the NCI Thesaurus by creating a set of properties and relationships within the original OWL file to describe a "top node," and a set of related values associated with that node.
The "top node" is a representation of an OWL class that defines a set of properties, which provide human readable metadata about what this classification of values means.
This node, the OWL defined relationships that point to it, and a set of properties key to defining aspects of a value set, allow LexEVS to adequately define this, both in terms of a Value Set Definition, and also as a Coding Scheme object. The API's that work in conjunction with the externally defined value set definitions and resolved value set coding schemes can receive these objects transparently because they are the same type as previously defined for the legacy API. Since these Objects have been adequately defined elsewhere in this documentation set, we won't redefine them here.
Contributing Source: Describes an agency or group that defines the value set
Example:
property name: "Contributing_Source"
property value: "CDISC"
Publish Flag:
Example:
property name: "Publish_Value_Set"
property value: "Yes"
Asserted Value Set Relation: Defines an association between the members of the value set and its "top node" which is usually the target of this relationship
Example: "Concept_In_Subset"
Asserted Value Set Hierarchy: Defines an association between the value set top nodes without defining membership in a value set with nodes above and below any given node in the hieararchy.
Example: "subClassOf"
Concept Domain: An abstraction defining what type conceptual membership is defined semantically for the value set
Example: "Semantic_Type"