> 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/implementation-guides/loinc-implementation-guide/content-development/4.2-template-based-content-creation/4.2.3-quality-observable-with-inheres-in-1.md).

# Quality Observable with Inheres In and Inherent Location

This template is employed when the LOINC term involves an observation that inherently exists within or is associated with something else, and relates to a specific location such as a specific sequence within a gene.

This template is documented in Confluence here: [Quality observable with Inheres in and Inherent location for LOINC (observable entity) - v1.0](https://conf.spaces.snomed.org/wiki/spaces/SCTEMPLATES/pages/904953857/Quality+observable+with+Inheres+in+and+Inherent+location+for+LOINC+observable+entity+-+v1.0)

The java implementation of this template can be found [here](https://github.com/IHTSDO/script-library/blob/develop/src/main/java/org/ihtsdo/termserver/scripting/pipeline/loinc/template/LoincTemplatedConceptWithInheresAndInherent.java).

## Attributes <a href="#id-4.2.3qualityobservablewithinheresin-attributes" id="id-4.2.3qualityobservablewithinheresin-attributes"></a>

* **LOINC Property**: Represents the property of the observation, such as mass concentration or presence.
* **LOINC Scale**: Describes the scale type, like quantitative or qualitative.
* **LOINC Time**: Indicates the time aspect of the observation, e.g., single point in time.
* **LOINC System**: Specifies the direct site of the observation.
* **LOINC Method**: Describes the technique used for the observation.
* **LOINC Component**: Specifies what the observation inherently exists within or is associated with.

{% hint style="info" %}
LOINC Properties currently supported when LOINC Component is not 'Observation' and LOINC Class is 'MOLPATH.MUT' : "Prid"
{% endhint %}

## Template

### Model <a href="#id-4.2.3qualityobservablewithinheresin-model" id="id-4.2.3qualityobservablewithinheresin-model"></a>

{% code overflow="wrap" %}

```
=== 363787002 |Observable entity (observable entity)| : 
{ 
704319004 |Inheres in (attribute)| = 873801010000104 |Gene sequence variant (morphologic abnormality)|, 
370130000 |Property (attribute)| = 118584009 |Presence or identity (property) (qualifier value)|,
370132008 |Scale type (attribute)| = 117362005 |Nominal value (qualifier value)|,
704327008 |Direct site (attribute)| = 119297000 |Blood specimen (specimen)|,
718497002 |Inherent location (attribute)| = 1397304009 |C-C motif chemokine receptor 5 gene (cell structure)|,
246501002 |Technique (attribute)| = 873811010000101 |Targeted gene mutation analysis technique (qualifier value)|,
370134009 |Time aspect (attribute)| = 123029007 |Single point in time (qualifier value)| 
}
```

{% endcode %}

### Terming <a href="#id-4.2.3qualityobservablewithinheresin-terming" id="id-4.2.3qualityobservablewithinheresin-terming"></a>

Template slots are filled by taking the preferred term of the relevant value from the model and making the initial character lower case, if allowed by the case significance setting of the preferred term.

\[PROPERTY] of \[COMPONENT] in \[SYSTEM] at \[TIME] by \[METHOD] using \[DEVICE] \[CHALLENGE]

Some slots are optional, and are then tidied up along with any linking words (eg 'using')

The LOINC Long Common Name is specified as the Preferred Term and the LOINC Short Common Name is also included unchanged as an acceptable synonym. Finally a terse form of the LOINC Parts is added, with all part names specified, separated by colons.

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

<table><thead><tr><th>Concept Id</th><th>Description Id</th><th width="98.8125">Acceptability</th><th width="309.46875">Term</th><th>CaseSignificance</th></tr></thead><tbody><tr><td>901781010000100</td><td>5402831010000118</td><td>US: P</td><td>Presence or identity of gene sequence variant in CCR5 gene in blood at point in time by targeted gene mutation analysis (observable entity)</td><td>cI</td></tr><tr><td>901781010000100</td><td>5402821010000116</td><td>US: P</td><td>CCR5 gene mutations found [Identifier] in Blood by Targeted gene mutation analysis Nominal</td><td>CS</td></tr><tr><td>901781010000100</td><td>5402811010000110</td><td>US: A</td><td>Presence or identity of gene sequence variant in CCR5 gene in blood at point in time by targeted gene mutation analysis</td><td>cI</td></tr><tr><td>901781010000100</td><td>5402841010000114</td><td>US: A</td><td>CCR5 gene Mut Bld Mut Anl</td><td>CS</td></tr><tr><td>901781010000100</td><td>5402851010000111</td><td>US: A</td><td>CCR5 gene mutations:Prid:Pt:Bld:Nom:Targeted gene mutation analysis</td><td>CS</td></tr></tbody></table>

### Examples <a href="#id-4.2.3qualityobservablewithinheresin-examples" id="id-4.2.3qualityobservablewithinheresin-examples"></a>

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

#### LOINC Parts mapped to SNOMED Attributes <a href="#id-4.2.3qualityobservablewithinheresin-loincpartsmappedtosnomedattributes" id="id-4.2.3qualityobservablewithinheresin-loincpartsmappedtosnomedattributes"></a>

<table><thead><tr><th width="141.09375">Part Type</th><th width="201.85546875">LOINC Part Name</th><th width="132.5">LOINC Part Num</th><th>Mapped to Attribute Type / Value</th></tr></thead><tbody><tr><td>Component</td><td>CCR5 gene mutations</td><td>LP451899-1</td><td>704319004 |Inheres in (attribute)| -> 873801010000104 |Gene sequence variant (morphologic abnormality)|</td></tr><tr><td>Component core</td><td>CCR5 gene</td><td>LP19680-5</td><td>718497002 |Inherent location (attribute)| -> 1397304009 |C-C motif chemokine receptor 5 gene (cell structure)|</td></tr><tr><td>Property</td><td>Prid</td><td>LP6850-4</td><td>370130000 |Property (attribute)| -> 118584009 |Presence or identity (property) (qualifier value)|</td></tr><tr><td>Time</td><td>Pt</td><td>LP6960-1</td><td>370134009 |Time aspect (attribute)| -> 123029007 |Single point in time (qualifier value)|</td></tr><tr><td>System</td><td>Bld</td><td>LP7057-5</td><td>704327008 |Direct site (attribute)| -> 119297000 |Blood specimen (specimen)|</td></tr><tr><td>Scale</td><td>Nom</td><td>LP7750-5</td><td>370132008 |Scale type (attribute)| -> 117362005 |Nominal value (qualifier value)|</td></tr><tr><td>Method</td><td>Targeted gene mutation analysis</td><td>LP95475-7</td><td>246501002 |Technique (attribute)| -> 873811010000101 |Targeted gene mutation analysis technique (qualifier value)|</td></tr></tbody></table>

<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%20Inheres%20In" 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 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/implementation-guides/loinc-implementation-guide/content-development/4.2-template-based-content-creation/4.2.3-quality-observable-with-inheres-in-1.md?ask=<question>&goal=<user_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.
