Search



Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The criteria f or  for a successful implementation of SNOMED CT includes the customization of SNOMED CT to meet user needs. The order in which SNOMED CT components are displayed is often important  for data entry and searching. This topic is further explored in the  Search and Data Entry Guide. In general, rational ordering of selectable items depends on the nature of the application and its operating environment. The table below shows examples of ordering data entry items and search results rationally.

...

ApproachDescriptionExample UsesReference Set
Sequential ordering

Annotating each subset member with an integer, which specify the consecutive order of the members. Two subset members do not have the same number assigned to them.

Displaying descriptions sequentially according to their specified order.Ordered component reference set

Prioritization
Annotating each subset member with a an integer, which specify a priority order. Two or more subset members may have the same number assigned to them.

 

Showing concepts with a high priority before their siblings using hierarchical display results.

  • Display search results in priority order
    • Results with same rank ordered by shortest or closest match
  • Displaying a rank indicator in search result list
Ordered component reference set


Initially listing concepts and associated descriptions with a priority above a specified threshold and requiring additional steps to access those assigned a lower priority.

  • Initial search is conducted on components with highest priority
  • Allow search to be extended to lower priorities
    • If no high priority matches
    • If user requests more matches

...

The table below shows how the order of cranial nerves can be specified in an ordered component reference set. The order attribute is used to indicate the sequential order of each subset member. Note that the linkedToId is set to 0 in this case because this reference set does not specify a hierarchy of reference set members.


Footnote Macro

The refsetId used in this table is fictitious


refsetIdreferencedComponentIdorderlinkedToId

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t11522000 | Olfactory nerve structure (body structure) |

10

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t18234004 | Optic nerve structure (body structure) |

20

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t56193007 | Oculomotor nerve structure (body structure) |

30

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t39322007 | Trochlear nerve structure (body structure) |

40

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t80622005 | Abducens nerve structure (body structure) |

50

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t27612005 | Trigeminal nerve structure (body structure) |

60

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t56052001 | Facial nerve structure (body structure) |

70

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t8598002 | Vestibulocochlear nerve structure (body structure) |

80

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t21161002 | Glossopharyngeal nerve structure (body structure) |

90

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t88882009 | Vagus nerve structure (body structure) |

100

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t15119000 | Accessory nerve structure (body structure) |

110

Concept
t609999999102 | Cranial nerve simple reference set |

Concept
t37899009 | Hypoglossal nerve structure (body structure) |

120

If there is a need to specify a customized hierarchical structure to support navigation, this can be achieved by specifying an alternative hierarchical view using an  ordered association reference set.

Prioritization

Some situations may require a set of subset  members to be grouped. For example, a set of concepts may need to be grouped based on how frequently they are used within a particular specialty, department or data entry scenario. In this case, an  an ordered association reference set may be used for  prioritization, instead of a purely sequential ordering of each member.  Prioritization is similar to sequential ordering, but also supports assigning the same rank to multiple components. A common use of prioritization is to support rational ordering of concepts or descriptions for display of data entry items and search results. More advanced uses may also be required, for example where the priority order is used to trigger certain decision support features or data entry options.

PDF: Hide in PDF Export


PDF: Hide in Web View

Image Modified



Display Footnotes Macro