This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "VocMnt-ValueSetRev/Create"

From HL7Wiki
Jump to navigation Jump to search
Line 32: Line 32:
 
|}  
 
|}  
 
   
 
   
[[Image:VocMnt471.gif|thumb|center|640px|Example XML for '''createValueSet ''']]
+
{{{{{1|Show}}}Graphic|VocMnt471.gif|Example XML for '''createValueSet '''|The fragment in the example above creates a value set called “OrderableBeers” and assigns all of the codes from the BEERS code system to the set.  It then creates a second value set called OrderableAles that is also drawn from the BEERS code system and assigns code 1001 (ALES) as the head code for the value set.}}
 
 
In the example above creates a value set called “OrderableBeers” and assigns all of the codes from the BEERS code system to the set.  It then creates a second value set called OrderableAles that is also drawn from the BEERS code system and assigns code 1001 (ALES) as the head code for the value set.
 
  
 
The '''underValueSet''' element allows the newly created value set to be added as nested element in an already existing value set.  
 
The '''underValueSet''' element allows the newly created value set to be added as nested element in an already existing value set.  

Revision as of 16:47, 30 September 2007

Creating a New Value Set

Element createValueSet

ballotStatus is the first element defined when creating a value set. As described above, it is optional except in the case when the vocabularyRevision.documentStatus is Final, in which case all revisions have to be associated with a non- Proposed status.

The description element is technically optional but virtually required by HL7 style and ballot guides. When present, it provides a description of the use and purpose of the value set.

Attributes of createValueSet
setName The unique name of the value set
codeSystemName The mnemonic for the code system associated with the value set (if any)
allCodes If codeSystemName is supplied, this flag determines whether all of the codes in the code system are included in the value set or just selected codes.
headCode It codeSystemName is supplied, this can be the concept code of the “head code” – the code that represents the entire value set.
headCodePrintName A valid designation for the headCode. Optional, but validated if supplied.
asVocabularyDomain <<Editor unsure of meaning. Does it mean "If true means that a concept domain should also be created."?>>
Example XML for createValueSet

The fragment in the example above creates a value set called “OrderableBeers” and assigns all of the codes from the BEERS code system to the set. It then creates a second value set called OrderableAles that is also drawn from the BEERS code system and assigns code 1001 (ALES) as the head code for the value set.

The underValueSet element allows the newly created value set to be added as nested element in an already existing value set.

Attributes of underValueSet
setName The name of an existing value set to add this new value set under
addAsType One of abstract or specializable. Abstract means that the head code (if any) of the new value set is not to be considered part of setName. Specializable means that the head code (if any) is to be included in setName.