> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-search-and-data-entry-guide/5-optimize-display-of-search-results/5.5-display-navigation-results-effectively/5.5.3-using-the-navigation-hierarchy.md).
# Using the Navigation Hierarchy
*SNOMED CT subtype Relationships* provide a logical semantic *hierarchy*. Often it is possible to view parts of the terminology and select particular *Concepts* by navigating through this *subtype hierarchy*. However, there are many situations in which the pure *subtype hierarchy* does not provide an ideal route for navigating the *hierarchy* (see [Using the Subtype Hierarchy](/snomed-ct-practical-guides/snomed-ct-search-and-data-entry-guide/5-optimize-display-of-search-results/5.5-display-navigation-results-effectively/5.5.1-using-the-subtype-hierarchy.md)).
Navigation hierarchies can be used to drive some types of structured data entry. Navigation hierarchies can order data in sensible ways by priority, or by some readily understood convention (e.g. "cranial nerve order" or "pharmacy products in the order of strength"). Navigation hierarchies can be used for diverse purposes (e.g. "topics related to diabetes").
*Navigation links* are used to provide an alternative route through parts of the terminology. A *navigation link* can link any two *Concepts* together to identify a useful route for *navigation*. Each of the *navigation links* is directional, linking a navigational parent *Concept* to a more refined navigational *child Concept*. However, unlike the *subtype relationship* the presence or absence of a *navigation link* neither adds to nor subtracts from the definition of either of the *Concepts* that it links.
Some *Concepts* may exist only to provide nodes in a *navigation hierarchy*. These *Concepts* are *subtypes* of | Navigational *Concept* *|* and play no part in the semantic definitions of any other *Concept*.
Navigational hierarchies are represented as Reference Sets, which are available in the International Release of SNOMED CT or they can be created from scratch to meet specific user needs. Navigational hierarchies created from scratch do not have to represent subtypes or logical relationships unless it is required.
An example of a handcrafted navigation hierarchy showing a list of common viral diseases
Provide Feedback
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-search-and-data-entry-guide/5-optimize-display-of-search-results/5.5-display-navigation-results-effectively/5.5.3-using-the-navigation-hierarchy.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
