# Display EHR Data

Data stored in an electronic health record (EHR) that includes SNOMED CT concepts or expressions may also include a human readable term associated with each concept identifier. In this case, EHR data can be displayed without using any terminology services. However, as shown in the table below there are several situations in which it may be necessary to lookup and display a term rather than relying upon a term stored in the rec[^1].

## Reasons for Looking Up Terms when Displaying EHR Data

The table below shows a summary of the services required to support display of EHR data including looked up terms.

<table data-full-width="true"><thead><tr><th width="374.22265625">Reason</th><th>Notes</th></tr></thead><tbody><tr><td><strong>To display the preferred term or fully specified name of a concept in the following situations:</strong></td><td><br></td></tr><tr><td><ul><li>If a record entry contains a concept identifier without an associated term</li></ul></td><td>It is good practice to store the selected term as well as the concept identifier but this is not mandatory.</td></tr><tr><td><ul><li>If a communication contains a concept identifier without an associated term</li></ul></td><td>It is good practice to communicate the selected term as well as the concept identifier but this is not mandatory. In some cases, the design of a message or interchange format may not support the inclusion of terms for all concept identifiers. This may be a particular issue when postcoordinated expressions are communicated as some interchange formats may not support the inclusion of terms for each concept identifier in an expression.</td></tr><tr><td><ul><li>If the synonym in a record entry or communication is ambiguous</li></ul></td><td><p>The term stored or communicated may be appropriate to the concept but may not be sufficiently clear.</p><ul><li>For example, the term "fundus" is a valid synonym for four different concepts. Looking up the fully specified name for the concept identifier allows the display of term that removes this ambiguity.</li></ul></td></tr><tr><td><p><strong>To display the preferred term for a concept in a familiar language:</strong></p><ul><li>If the term stored or communicated is in an unfamiliar language</li></ul></td><td>The term stored or communicated may be in a language that the user does not understand. If the concept is also included in the edition used by the viewer, it should be possible to display the term in the viewers own language.</td></tr><tr><td><p><strong>To confirm that a term linked to a concept identifier is a valid:</strong></p><ul><li>If there is a requirement for quality assurance validation</li></ul></td><td>Even when a term is stored or communicated with a concept identifier, it may be useful to confirm that the term included is associated with that concept <a data-footnote-ref href="#user-content-fn-2">identifier</a>.</td></tr></tbody></table>

## Services Required to Enable Display of EHR Data

<table data-full-width="true"><thead><tr><th width="494.34375">Practical Requirement</th><th width="215.51953125">Required Services</th><th>Dependencies</th></tr></thead><tbody><tr><td>Enable the selection of SNOMED CT edition and version to be used<br><br>REQUIRED</td><td><a href="../4-terminology-service-types/4.1-select-edition-and-version">Select Edition and Version</a></td><td>N/A</td></tr><tr><td>Display terms for the concepts in EHR record entries and communications<br><br>REQUIRED</td><td><a href="../4-terminology-service-types/4.3-get-terms-for-a-concept">Get Terms for a Concept</a></td><td>N/A</td></tr></tbody></table>

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

[^1]: Term lookup will fail if the concept is a module that is not included in the viewers edition.

[^2]: Term validation will fail if the term is in a description in a module that is not included in the viewers edition (for example the term may be part of a module including term in a language not used by the viewer.


---

# Agent Instructions: 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:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/display-ehr-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
