When querying patient records containing SNOMED CT-enabled data, a variety of interfaces may be adopted to support the user in authoring queries. In this section we first consider user interfaces for querying SNOMED CT, and then look at user interfaces for querying SNOMED CT enabled patient records.
When querying clinical data, it may be necessary to first define a subset of SNOMED CT concepts (e.g. disorders or procedures) that may then be compared against values in a patient record. A number of different options exist for creating these SNOMED CT subsets, including:
This approach uses a SNOMED CT browser to allow individual SNOMED CT concepts to be searched, selected and added to a subset. For large subsets this can be quite time consuming, however it is quite suitable for smaller subsets. A number of commercial tools are available which help to perform this task, including Apelon's Distributed Terminology System and B2i's Snow Owl terminology server. figure 10.1-0 below illustrates Snow Owl's authoring interface for Simple reference sets.
Other user interfaces allow a subset to be defined using a text-based query written using a predefined query language (e.g. SNOMED CT Expression Constraint Language, or SNOMED CT Query Language). These interfaces tend to be for the more technical user. However, some clinical users may be taught to use these interfaces if required.
Two examples of this style of interface are illustrated in figure 10.1-0 and figure 10.1-0. figure 10.1-0 shows the NHS Data Migration Workbench query interface, while figure 10.1-0 shows B2i's Snow Owl query interface.
A third style of user interfaces for authoring SNOMED CT subsets uses a structured
form. A form-driven query tool may allow the user to select an operator (e.g. 'memberOf',
'descendantOf'), the concept or subset to which this operator is applied (e.g. 'Example
problem list', 'Disorder'), and then one or more attribute values to limit the set
of concepts returned. (Note: The attribute name may either be selected from a list,
or hard coded on the form). Once the form is completed, a text-based query is automatically
constructed from the selected values, and executed against SNOMED CT. This style of
interface can be designed to allow users to exploit the rich semantics of SNOMED CT,
while shielding them from the underlying technical details.
figure 10.1-0 illustrates how a generic form-driven interface for authoring SNOMED CT queries works.
Vendor products which implement form-driven interfaces for authoring SNOMED CT queries
include B2i's Meaningful Query web interface (as shown in
Figure 10.1-5: B2i Snow Owl's Meaningful Query web interfacePatient Record Query Interfaces
When SNOMED CT queries are integrated (or embedded) into patient records queries, additional constraints are often added across demographic data (e.g. age, address) and episode of care data (e.g. healthcare provider, dates). These data items are often referred to as 'concrete values' and are typically not included in a terminology. A number of styles of interfaces are used to author patient record queries that include SNOMED CT content, including:
figure 10.1-0 shows an example of a search for 'diabetes' using Cerner's Semantic Search tool. This tool enables clinicians at the point of care to search in real time through a patient's multiple charts, pathology reports and other documents for topics such as 'heart disease' and 'diabetes', using SNOMED CT's hierarchical and non-hierarchical relationships.
Figure 10.1-6: User interface of Cerner's Chart Search/Semantic tool