Defining Relationships between Concept Codes
Additional relationships other than subsumption may be asserted to exist between concept codes. As an example, one may want to assert that one concept code occurs before a second in a basic ordering. Relationships can be added to concept codes during either the code system registration or code system update phases.
As with the other operations, addConceptRelationship can have its own ballotStatus or can inherit the ballotStatus from the containing entry. The addConceptRelationship attributes define the relationship to be added:
|parentCodeSystemMnemonic||The mnemonic identifying the code system that holds the parent code. Optional. If blank, is assumed to be the code system established by the parent registerCodeSystem or selectCodeSystem.|
|parentCode||The concept code that occurs on the “left hand” or parent side of the relationship|
|parentName||A valid designation for the parent code. Optional but validated if present|
|relationship||A valid relationship code (e.g. smallerThan)|
|childCodeSystemMnemonic||The mnemonic identifying the code system that holds the child (related) code. Optional. If blank, is assumed to be the code system established by the parent registerCodeSystem or selectCodeSystem.|
|childCode||The concept code that occurs on the “right hand” or child side of the relationship|
|childName||A valid designation for the child code. Optional but validated if present.|
The above example asserts that concept code “1002” is “less than” concept code “1003” in an ordinal sense.