The criteria 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.
| Approach | Description | Example Uses | Reference 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.
| 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.
|
Sequential Ordering
Displaying items for data entry in a rational way typically involves organizing the values in a selection list in an order that is logical for the end users. As illustrated in the figure below, an ordered reference set can be used to specify the order in which SNOMED CT components should be displayed.
Examples of presenting concepts (or descriptions) in an order that is rational or helpful for a particular purpose include:
- Displaying numbered body parts, such as fingers, cranial nerves or vertebrae, in numeric order
- Displaying ordinal values, such as frequencies, severities or stages, from lowest to highest
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.
1
| refsetId | referencedComponentId | order |
| 1 | ||
| 2 | ||
| 3 | ||
| 4 | ||
| 5 | ||
| 6 | ||
| 7 | ||
| 8 | ||
| 9 | ||
| 10 | ||
| 11 | ||
| 12 |
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 ordered association reference set may be used for 3.2.1.4. Order Items for Search and Data Entry, 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.
| Ref | Notes |
|---|---|
| 1 | The refsetId used in this table is fictitious |
Feedback