# Impression Observable

This template is employed when the LOINC term represents an impression observable, capturing a high-level clinical interpretation or summary derived from one or more observations, rather than a direct measurement or finding.

Impression observables concepts all have a primitive definition, following the template described below and documented here: [Impression observable for LOINC (observable entity) - v1.0](https://conf.spaces.snomed.org/wiki/spaces/SCTEMPLATES/pages/484769793/Impression+observable+for+LOINC+observable+entity+-+v1.0).

## Attributes <a href="#id-4.2.1qualityobservablewithcomponent-attributes" id="id-4.2.1qualityobservablewithcomponent-attributes"></a>

* **LOINC Property**: indicates that the quality being observered is some impression or interpretation.

{% hint style="info" %}
LOINC Properties currently supported: "Imp"
{% endhint %}

## Template <a href="#id-4.2.1qualityobservablewithcomponent-template" id="id-4.2.1qualityobservablewithcomponent-template"></a>

This template is utilized when the LOINC term represents an impression observable.

### Model <a href="#id-4.2.1qualityobservablewithcomponent-model" id="id-4.2.1qualityobservablewithcomponent-model"></a>

{% code overflow="wrap" %}

```
<<< 363787002 |Observable entity (observable entity)| : 
{ 370130000 |Property (attribute)| -> 118580000 |Impression AND/OR interpretation of study (property) (qualifier value)| }
```

{% endcode %}

### Terming <a href="#id-4.2.1qualityobservablewithcomponent-terming" id="id-4.2.1qualityobservablewithcomponent-terming"></a>

In the case of impression concept, the  LOINC Long Common Name is used  as both the FSN (with a semantic tag of "(observable entity)" added), and the Preferred Term.  The LOINC Short Common Name is also included unchanged as an acceptable synonym.&#x20;

In the case of the example below, this results in the following terms:

<table><thead><tr><th width="122.8359375">Concept Id</th><th width="140.3775634765625">Description Id</th><th width="97.90887451171875">Acceptability</th><th width="319.16925048828125">Term</th><th>Case</th></tr></thead><tbody><tr><td>823801010000103</td><td>4498981010000118</td><td>US: P</td><td>Genetic disease analysis overall carrier interpretation in Blood or Tissue by Molecular genetics method Narrative (observable entity)</td><td>CS</td></tr><tr><td>823801010000103</td><td>4498971010000116</td><td>US: P</td><td>Genetic disease analysis overall carrier interpretation in Blood or Tissue by Molecular genetics method Narrative</td><td>CS</td></tr><tr><td>823801010000103</td><td>4498991010000115</td><td>US: A</td><td>Genetic disease analysis overall carrier interpretation:Imp:Pt:Bld/Tiss:Nar:Molgen</td><td>CS</td></tr></tbody></table>

## Examples <a href="#id-4.2.1qualityobservablewithcomponent-examples" id="id-4.2.1qualityobservablewithcomponent-examples"></a>

#### LOINC Term [100695-6](https://loinc.org/100695-6/)

There are no LOINC parts represented in the SNOMED model for these impression concepts.   The SNOMED concepts are defined as primitive, with only the single property attribute present, always taking a value of 118580000 |Impression AND/OR interpretation of study (property).

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=LOINC+Implementation+Guide&#x26;entry.670899847=Quality%20Observable%20with%20Component" class="button primary">Provide Feedback</a>


---

# 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/implementation-guides/loinc-implementation-guide/content-development/4.2-template-based-content-creation/4.2.1-quality-observable-with-component-1.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.