Sneak peeks

Please note: This is an early-access feature intended to solicit comments and usability suggestions. Performance of this feature will be poor on older computers. A modern multi-core system is recommended to achieve best performance.

Snow Owl now supports concurrently searching through multiple terminologies and resources simultaneously. In addition to SNOMED CT, ICD-10, and ATC, the framework makes it easy to add additional additional categories. The quick search window will appear after pressing CTRL-4 (Windows) or CMD-4 (OS X). Start typing to see matches; the matching results will be displayed as you type. Tip: you can quickly find longer concepts by typing the first few characters of each word in their description. For example, entering 'bl pr st sy' will quickly find Standing systolic blood pressure.

The search will initially limit the number of results displayed in each category based on the total number of search hits. Pressing CTRL-4 (Windows) or CMD-4 (OS X) will toggle between this limited set of results and displaying more matches that were found.

Selecting an item from the search results will trigger an action according to the type of item selected. Terminology concepts will be opened in a concept editor. Reference sets will be opened in a reference set editor.

The following sections describe the included search providers.

Supported quick search categories

Previous choices

The previous choices category provides access to your concept selection history. Selecting an item will open it in the appropriate editor.


The bookmarks search displays matching SNOMED CT concepts from your bookmarks. Selecting an bookmarked item will open it in the SNOMED CT concept editor.


This section provides a list of matching SNOMED CT concepts. All description types are considered for matches, including customized description types defined by the description format reference set.

Example quick search for 'reps sys'

SNOMED CT reference sets

This section displays matching reference sets; selecting one will open a reference set editor.


This section displays matching ICD-10 classes. Selecting one will open a corresponding ICD-10 editor.


This section displays ATC codes; selecting a code will open the ATC editor.


This section displays open editors that match the selection. This allows quickly switching between editor tabs on opened concepts.


This section displays all available Snow Owl views. For example, typing 'history' allows you to easily jump to the History view.


Matching perspectives are displayed here, including customized layouts.


This section contains arbitrary commands that can be executed outside of a specific context.

Menus matching the search criteria are displayed in this section.


This section displays options for creating new items, for example, to quickly create a new simple type reference set.


The preferences section displays matching configuration items from Snow Owl > Preferences.

Example quick search for 'owl'


Configurable properties matching the search criteria are displayed in this section.

Constraint model editor

Please note: The constraint model editor is intended as developer tooling, rather than as an end-user feature. Nevertheless, we have found it valuable to view the imported MRCM constraints to clarify unintended behaviors in the MRCM-based reference set editors, as the IHTSDO Phase I MRCM release contains some known problems.

The MRCM editor allows viewing and maintaining the concept model.

MRCM Editor

Node detail pages

The right part of the editor changes based on which type of node is selected in the tree. Every detail page contains a Constraint meta-data section, which contains the common properties of every constraint model node, such as UUID, author, effective date and active/inactive state.

Attribute constraint

The strength of the MRCM constraint can be specified on at the attribute constraint view. The user can also select which normal form the relationship predicates should apply for.

Attribute constraint


The tree on the left side of the editor displays all the constraints, sorted by their domain. When you expand one of the constraint nodes, you can see a quick overview of the constraint's domain and predicate. Depending on the types of nodes you can drill down even further to explore the whole structure of a constraint's predicates and concept set definitions. Click on a node to view or edit its properties using the detail page displayed on the right.

You can add and delete constraints using the buttons in the top right corner of the section; other nodes can be added and deleted using the right-click menu. Please note that the editor enforces a strict constraint model structure, which means that the commands for adding new nodes might not always be available. If this is the case, just delete the existing node you want to replace before trying to add a new one.

MRCM domains

Reference set concept set definition

The reference set concept set definition allows concepts to be restricted based on their reference set membership. Reference sets can be used as a domain or a range for a relationship predicate.

Reference set concept set definition

Hierarchy concept set definition

Hierarchy concept set definition allows specifying constraints to a concept and/or the inclusive or exclusive subtypes. Concept hierarchies can be present as a domain or a range for a relationship predicate.

Hierarchy concept set definition

Composite concept set definition

Composite concept set definition allows the combination of more concept sets and concept set definition types, for example adding a list of reference sets as a domain or range.


Predicate cardinality

This section allows the user specify the cardinality of the predicates, and to set relationship group rules for the relationship predicates.

Cardinality predicate

Relationship predicate

Relationship predicate restricts the type of relationships that can be applied to a domain. The relationship predicate should always have an attribute and a range definition.

Relationship predicate

Description predicate

Description predicate allows the user to define the necessary description types a domain should have.

Description predicate

Concrete domain predicate

Concrete domain predicates allows the user specify the datatypes associated with a domain.

Concrete domain predicate