SNOMED Documentation Search
Page History
This section shows some example uses, diagramming existing content from SNOMED CT.
Anchor
Figure 25–Definition of
| Concept | ||
|---|---|---|
|
The concept definition shown in Figure 25 shows that the concept
| Concept | ||
|---|---|---|
|
| scg-expression |
|---|
429353004 | Injury of radius |+ 65966004 | Fracture of forearm |: |
...
{ |
...
116676008 | Associated morphology | = 72704001 | Fracture |, |
...
363698007 | Finding site | = 62413002 | Bone structure of radius | |
...
} |
Anchor
Figure 26–Definition of
| Concept | ||
|---|---|---|
|
Figure 26 shows the definition of 12676007 | Fracture of radius | again, however this time in long normal form and without identifiers. The expression on the right had side of the diagram equates to the text expression -
64572001 | Disease | :
{
116676008 | Associated morphology | = 72704001 | Fracture |,
363698007 | Finding site | = 62413002 | Bone structure of radius |
}
- Template Expressions
...
Using the "slot" element described in A.1 it is possible to define diagrams that represent a template for concept definition or expressions. It is then possible to use this template to create concepts or expressions by filling the "slots" with appropriate concepts.
Figure 27 Example template diagram using "slots"
These template diagrams are a specialisation of concept definition diagrams as described in section 3.2; however some of the attribute value concepts are replaced by "slots" making the definition general and reusable.
Note the names provided for the "slots" are enclosed in angle brackets "<" and ">". These slot names are inserted into the name of the concept in the top left of the diagram.
The names associated with slots operate as unique variable names for a diagram or set of diagrams. When populated, every slot with the same name on a diagram, or set of related diagrams, receives the same concept value associated with that slot name. Unless all slots names used are assigned concept values, the expression is not complete.
- Additional context
...
A further suggested visual clarification to either approach specified in sections B.1 and B.2 is to use
- a dotted/dashed box around the segments of the diagram providing "additional context"
- and/or change connectors in segments reflecting "additional context" to use dotted or dashed lines
Is a complementary, not a competing, proposal to those specified in sections B.1 and B.2.
...
Section 3 explores three different forms of diagram for expressing
- Expressions
- Concept definition
- Expression relation
...
| Caption label | ||||
|---|---|---|---|---|
| ||||
shows the definition of INLINE12676007 | Fracture of radius | again, however this time in long normal form and without identifiers. The expression on the right had side of the diagram equates to the text expression - INLINE64572001 | Disease | : {116676008 | Associated morphology | = 72704001 | Fracture |, 363698007 | Finding site | = 62413002 | Bone structure of radius |} |
Figure 30 depicts a concept definition diagram as used in the Workbench Utilities at the time of writing.
The most distinguishing feature of this approach is the removal of the "equivalence" symbol as an abbreviation. This enables the concept's parents to appear above the "concept in focus" while attributes appear on the right without excess clutter (as depicted in Figure 31).
Note that this diagram also includes child concepts of the "concept in focus" below, and attributes of which the "concept in focus" is a target on the left. This results in
- The arrows emanating from the "concept in focus" showing the definition of the "concept in focus"
- The arrows entering the "concept in focus" showing where the "concept in focus" is used in the definition of other concepts.
...
The diagram options in this appendix have been largely focussed on a concept definition centric interaction/navigation; however there are other focuses that may also be useful.
For example it is common to consider browsing or navigating SNOMED CT purely from its sub/supertype relationships in a full hierarchical view back to the root node. While the examples in this section do provide immediate parents, sometimes hierarchical views showing full lineage are useful. However given the real-estate requirements of full lineage and full concept definition, it is unlikely that both renderings can coexist on the same diagram concurrently. Consequently an alternate style may be required for this view, of which there are many examples in SNOMED CT browsers at present.
Another example scenario is browsing a reference set/s or SNOMED CT content in context of a reference set/s. Again this use case is likely sufficiently at odds with the examples provided in this appendix that an alternate diagram style is required.
As this Diagramming Guideline is focussed on expressions and concept definitions, these and other potential views are out of scope and as yet unexplored formally by this document. Many examples of these renderings exist in the numerous SNOMED CT browsers, and may be left unspecified for the continued innovation of browser vendors, or explored in future versions of the Diagramming Guidelines if considered worthwhile.
- Technical Implementation Guide examples
...
...
| Display Footnotes Macro |
|---|
Overview
Content Tools
Apps