> 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-international-documents/snomed-ct-glossary/s/sufficiently-defined-concept.md).
# sufficiently defined concept
## sufficiently defined concept
A concept with one or more sufficient definitions.
#### Notes
* A SNOMED CT concept is expressed in a human-readable form by its fully specified name (FSN).
* A *sufficiently defined concept* has at least one sufficient definition that distinguishes it from any concepts or expressions that are neither equivalent to, nor subtypes of, the defined concept.
**Examples**
* The concept [74400008 | appendicitis (disorder)|](http://snomed.info/id/74400008) is *sufficiently defined* by the following definition because any concept for which these defining relationships are true, is either the disorder *appendicitis* or a subtype of *appendicitis*.
[74400008 |appendicitis (disorder)|](http://snomed.info/id/74400008)\
\=== [18526009 |disorder of appendix|](http://snomed.info/id/18526009) :\
[116676008 |associated morphology|](http://snomed.info/id/116676008) = [23583003 |inflammation|](http://snomed.info/id/23583003) ,\
[363698007 |finding site|](http://snomed.info/id/363698007) = [66754008 |appendix structure|](http://snomed.info/id/66754008)
#### Change Notices
* Prior to July 2018, SNOMED CT could only support one *sufficient definition* for each concept could not represent the [8801005 | Secondary diabetes mellitus (disorder)|](http://snomed.info/id/8801005) example above. A further limitation, that also prevented formal representation of that example was the stated relationship file was only able to represent necessary conditions.
* Changes introduced in the July 2018 release of the International Edition allow assertions to be represented as axioms in the OWL axiom reference set file. This will allow concepts to be defined by multiple sufficient definitions, some of which may contain assertions that are not necessarily true.
* Following these changes a concept will only be marked as sufficiently defined if it is sufficiently defined by relationships. However, the OWL axioms may provide a sufficient definition that cannot be fully represented as *relationships*.
## Alternatives
* **Fully defined concept**
##
Provide Feedback
---
# 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/snomed-international-documents/snomed-ct-glossary/s/sufficiently-defined-concept.md?ask=&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.