> 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-ehr-requirements-guide/3-user-interface.md).

# User Interface

The success of an implementation of SNOMED CT is often driven by the quality and approach that has been employed in the development of the user interface. This is where end users will interact and use SNOMED CT and a poor implementation will have a considerable impact on the quality of data entered. These points provide some guidance on what should be expected from vendors in systems using SNOMED CT.

1. Use SNOMED CT for searching, display, storage, communication, knowledge linkage, querying and analytics in the following clinical domains (or specific data elements)
   * Problems, Diagnosis and Clinical Findings
   * Reason for Admission
   * Procedures (e.g. Planned Procedures, Performed Procedures)
   * Allergies
2. Support searching for SNOMED CT concepts using any term that is preferred or acceptable in the national language reference set.
3. The vendor shall include one of the following options for each SNOMED CT coded data element (depending on user preferences and local requirements for standardization of interface terms):
   * Upon selection of a concept, use the term entered by the user to display the selected concept; OR
   * Upon selection of a concept, use the preferred term from the national language reference set) to display the selected concept; OR
   * Upon selection of a concept, use the preferred term from the regional or institution specific language reference set to display the selected concept.
4. The vendor shall allow searching and selection of only those concepts from the SNOMED CT subset that has been specifically bound to that data element.
5. The vendor shall display the most frequently selected concepts at the top of the list, for elements bound to a subset containing more than 20 concepts.
6. As the user types each character into a SNOMED CT coded data element, limit the selection of concepts to those with a preferred or acceptable term that matches the characters types (using a ‘word prefix any order’ algorithm), and use auto-complete when only one option is available for selection.
7. When displaying the list of possible matches, display the concept with the shortest matching term first.
8. For each free text data element that records clinical information (e.g. Past history, Clinical notes) use SNOMED CT-enabled techniques (e.g. Natural Language Processing) to suggest possible SNOMED CT encoding (including appropriate contextual information), for selection and confirmation by the user.
9. Support the capture of SNOMED CT post-coordinated expressions using predefined expression templates and automatically-generated interface terms – for laterality, allergies and family history.
10. Use SNOMED CT concept identifiers stored in the EHR to suggest patient-specific clinical knowledge to the clinician, and to test clinical decision support rules.
11. Use SNOMED CT codes stored in the EHR, together with SNOMED CT and other map-enabled coding systems (e.g. SNOMED to ICD-10) to suggest appropriate codes for the clinician to select (if required).
12. The system shall be sufficiently performant to return the first (X) results in a given time period (e.g. less than 1s).

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=EHR+Requirements+Guide&#x26;entry.670899847=3.%20User%20Interface" class="button primary">Provide Feedback</a>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-ehr-requirements-guide/3-user-interface.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.