# necessary condition

## necessary condition

A characteristic that is always true of a concept.

#### Notes

* Some *necessary conditions* can be represented as defining relationships but other *necessary conditions* that can be represented as OWL axioms cannot be represented as *relationships*.
* The relationship file represents the inferred view of *necessary conditions* in that can be represented as *relationships*.

#### Example

* If you have a [71620000 | fracture of femur|](http://snomed.info/id/71620000) , the morphological abnormality [72704001 | fracture|](http://snomed.info/id/72704001) must be present. Therefore, [116676008 | morphology|](http://snomed.info/id/116676008) = [72704001 | fracture|](http://snomed.info/id/72704001) is a *necessary condition* of [71620000 | fracture of femur|](http://snomed.info/id/71620000) .

#### Change Notices

* Prior to July 2018, SNOMED CT represented all *necessary conditions* in the stated view as defining relationships in the stated relationship file.
* Changes introduced in the July 2018 release of the International Edition mean that in future *necessary conditions* \_\_ in the stated view will be represented as axioms in the OWL axiom reference set file.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Glossary&#x26;entry.670899847=necessary%20condition" 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/snomed-international-documents/snomed-ct-glossary/n/necessary-condition.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.