|
|
(12 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | ==[[#Nt4|Concept Domain]] Revision [[#Nt2|''[Not fully exposed in application]'']]==
| + | {{:VocMnt-DomainRev/Root}} |
− | | + | {{:VocMnt-DomainRev/Create}} |
− | A concept domain represents an abstract conceptual space that can be associated with RIM-derived coded attributes. A concept domain can be represented by one or more value sets, where each associated value set applies in a given context. Further, sub-sets of concept domains may, themselves, be represented as concept domains in a parent-child semantic hierarchy. The set of operations that can be made on concept domains includes: create, define (or redefine), rename, move (in the hierarchy) and delete, as indicated below:
| + | :{{to-top}} |
− | | + | {{:VocMnt-DomainRev/Redefine}} |
− | [[Image:VocMnt705.gif|thumb|center|384px|Element '''vocabularyDomainRevision''' -- Revising Concept Domains]]
| + | :{{to-top}} |
− |
| + | {{:VocMnt-DomainRev/Rename}} |
− | ===Creating Concept Domains [[#Nt3|''[Exposed under VS in application]'']]===
| + | :{{to-top}} |
− | | + | {{:VocMnt-DomainRev/Move}} |
− | The vast majority of the concept domains will be created during the RIM modeling process. The following operation can be used in cases where the domain doesn’t already exist in the RIM model.
| + | :{{to-top}} |
− | | + | {{:VocMnt-DomainRev/Delete}} |
− | [[Image:VocMnt710.gif|thumb|center|384px|Element '''createVocabularyDomain ''']]
| |
− | | |
− | The creation of a new domain needs to be voted upon, therefore '''createVocabularyDomain''' has an optional '''ballotStatus element'''. The description is technically optional, but is '''virtually required by HL7's style and balloting guides'''. It provides a description of the concept domain. '''createVocabularyDomain''' has the following attributes:
| |
− | | |
− | [[Image:VocMnt720.gif|thumb|center|512px|Attributes of '''createVocabularyDomain ''']]
| |
− | | |
− | {| class="wikitable" style="text-align:left" | |
− | !width="15%"|
| |
− | !
| |
− | |-
| |
− | !valign="top"|vocabularyDomain
| |
− | |The name of the new concept domain to be created
| |
− | |-
| |
− | !valign="top"|restrictsDomain
| |
− | |The name of the parent concept domain (optional).
| |
− | |}
| |
− | | |
− | [[Image:VocMnt731.gif|thumb|center|640px|Example XML for '''createVocabularyDomain ''']]
| |
− | | |
− | The example above creates two concept domains – OrderableBeers and OrderableAles. OrderableAles is defined as a proper subset (restriction or constraint) on OrderableBeers.
| |
− | | |
− | ===Define or Redefine Concept Domain [[#Nt1|''[Not exposed in application]'']]===
| |
− | | |
− | A new or revised definition can be assigned to a concept domain with the '''defineVocabularyDomain ''' element.
| |
− | | |
− | [[Image:VocMnt730.gif|thumb|center|384px|Element '''defineVocabularyDomain''']]
| |
− | | |
− | As with all updates, '''defineVocabularyDomain''' can have its own '''ballotStatus''' if needed to reflect special cases. It has a '''newDescription''' element that contains the revised description or can be empty if the description is to be completely removed. '''defineVocabularyDomain''' has a single attribute:
| |
− | | |
− | [[Image:VocMnt740.gif|thumb|center|512px|Attribute of '''defineVocabularyDomain ''']]
| |
− | | |
− | {| class="wikitable" style="text-align:left" | |
− | !width="15%"|
| |
− | !
| |
− | |-
| |
− | !valign="top"|vocabularyDomain
| |
− | |The name of the concept domain to be (re)defined.
| |
− | |}
| |
− |
| |
− | ===Rename Concept Domain [[#Nt1|''[Not exposed in application]'']]===
| |
− | | |
− | A new name can be assigned to a concept domain with the '''renameVocabularyDomain''' element.
| |
− | | |
− | [[Image:VocMnt750.gif|thumb|center|384px|Element '''renameVocabularyDomain ''']]
| |
− | | |
− | As with all updates, '''renameVocabularyDomain''' can have its own '''ballotStatus''' if needed to reflect special cases. '''renameVocaabularyDomain''' has two attributes:
| |
− | | |
− | [[Image:VocMnt760.gif|thumb|center|512px|Attributes of '''renameVocabularyDomain ''']]
| |
− | | |
− | {| class="wikitable" style="text-align:left" | |
− | !width="15%"|
| |
− | !
| |
− | |-
| |
− | !valign="top"|vocabularyDomain
| |
− | |The current name of the concept domain to be (re)defined.
| |
− | |-
| |
− | !valign="top"|newDomainName
| |
− | |The new name of the concept domain.
| |
− | |}
| |
− | | |
− | ===Move Concept Domain [[#Nt1|''[Not exposed in application]'']]===
| |
− | | |
− | A concept domain can be moved within the domain hierarchy – made a child of another domain, made a child of a different domain than previously, or removed from under its parent -- using the '''moveVocabularyDomain''' element.
| |
− | | |
− | [[Image:VocMnt770.gif|thumb|center|384px|Element '''moveVocabularyDomain''']]
| |
− | | |
− | As with all updates, '''moveVocabularyDomain''' can have its own '''ballotStatus''' if needed to reflect special cases. '''moveVocaabularyDomain''' has three attributes:
| |
− | | |
− | [[Image:VocMnt780.gif|thumb|center|512px|Attributes of '''moveVocabularyDomain''']]
| |
− | | |
− | {| class="wikitable" style="text-align:left"
| |
− | !width="15%"|
| |
− | !
| |
− | |-
| |
− | !valign="top"|vocabularyDomain
| |
− | |The name of the concept domain being moved.
| |
− | |-
| |
− | !valign="top"|fromDomain
| |
− | |The current direct parent of the concept domain, if any. This attribute should be omitted if the concept domain doesn’t currently occur under any other node.
| |
− | |-
| |
− | !valign="top"|toDomain
| |
− | |The new parent of the concept domain. If omitted, the concept domain no longer has a parent in the domain hierarchy.
| |
− | |}
| |
− | | |
− | ===Delete Concept Domain [[#Nt1|''[Not exposed in application]'']]===
| |
− | | |
− | A concept domain can be deleted from the set of HL7 domains using the '''moveVocabularyDomain''' element.
| |
− | | |
− | [[Image:VocMnt790.gif|thumb|center|384px|Element '''deleteVocabularyDomain ''']]
| |
− | | |
− | As with all updates, '''moveVocabularyDomain''' can have its own '''ballotStatus''' if needed to reflect special cases. '''moveVocaabularyDomain''' has one attributes:
| |
− | | |
− | [[Image:VocMnt800.gif|thumb|center|512px|Attribute of '''deleteVocabularyDomain''']]
| |
− | | |
− | {| class="wikitable" style="text-align:left" | |
− | !width="15%"|
| |
− | !
| |
− | |-
| |
− | !valign="top"|vocabularyDomain
| |
− | |The name of the concept domain to be deleted.
| |
− | |}
| |
- [Not fully exposed in application]
A concept domain represents an abstract conceptual space that can be associated with RIM-derived coded attributes. A concept domain can be represented by one or more value sets, where each associated value set applies in a given context. Further, sub-sets of concept domains may, themselves, be represented as concept domains in a parent-child semantic hierarchy. The set of operations that can be made on concept domains includes: create, define (or redefine), rename, move (in the hierarchy) and delete, as indicated below:
Element
vocabularyDomainRevision -- Revising Concept Domains
Creating Concept Domains
- [Exposed under VS in application]
The vast majority of the concept domains will be created during the RIM modeling process. The following operation can be used in cases where the domain doesn’t already exist in the RIM model.
Element
createVocabularyDomain
The creation of a new domain needs to be voted upon, therefore createVocabularyDomain has an optional ballotStatus element. The description is technically optional, but is virtually required by HL7's style and balloting guides. It provides a description of the concept domain. createVocabularyDomain has the following attributes:
Attributes of
createVocabularyDomain
|
|
vocabularyDomain
|
The name of the new concept domain to be created
|
restrictsDomain
|
The name of the parent concept domain (optional).
|
Example XML for
createVocabularyDomain
The example above creates two concept domains – OrderableBeers and OrderableAles. OrderableAles is defined as a proper subset (restriction or constraint) on OrderableBeers.
- Jump to top of page
Define or Redefine Concept Domain
- [Not exposed in application]
A new or revised definition can be assigned to a concept domain with the defineVocabularyDomain element.
Element
defineVocabularyDomain
As with all updates, defineVocabularyDomain can have its own ballotStatus if needed to reflect special cases. It has a newDescription element that contains the revised description or can be empty if the description is to be completely removed. defineVocabularyDomain has a single attribute:
Attribute of
defineVocabularyDomain
|
|
vocabularyDomain
|
The name of the concept domain to be (re)defined.
|
- Jump to top of page
Rename Concept Domain
- [Not exposed in application]
A new name can be assigned to a concept domain with the renameVocabularyDomain element.
Element
renameVocabularyDomain
As with all updates, renameVocabularyDomain can have its own ballotStatus if needed to reflect special cases. renameVocaabularyDomain has two attributes:
Attributes of
renameVocabularyDomain
|
|
vocabularyDomain
|
The current name of the concept domain to be (re)defined.
|
newDomainName
|
The new name of the concept domain.
|
- Jump to top of page
Move Concept Domain
- [Not exposed in application]
A concept domain can be moved within the domain hierarchy – made a child of another domain, made a child of a different domain than previously, or removed from under its parent -- using the moveVocabularyDomain element.
Element
moveVocabularyDomain
As with all updates, moveVocabularyDomain can have its own ballotStatus if needed to reflect special cases. moveVocaabularyDomain has three attributes:
Attributes of
moveVocabularyDomain
|
|
vocabularyDomain
|
The name of the concept domain being moved.
|
fromDomain
|
The current direct parent of the concept domain, if any. This attribute should be omitted if the concept domain doesn’t currently occur under any other node.
|
toDomain
|
The new parent of the concept domain. If omitted, the concept domain no longer has a parent in the domain hierarchy.
|
- Jump to top of page
Delete Concept Domain
- [Not exposed in application]
A concept domain can be deleted from the set of HL7 domains using the moveVocabularyDomain element.
Element
deleteVocabularyDomain
As with all updates, moveVocabularyDomain can have its own ballotStatus if needed to reflect special cases. moveVocaabularyDomain has one attributes:
Attribute of
deleteVocabularyDomain
|
|
vocabularyDomain
|
The name of the concept domain to be deleted.
|