> 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/p/precoordinated.md).
# precoordinated
## precoordinated
**This is an abbreviation for precoordinated expression.**
## precoordinated expression
A SNOMED CT expression that containing a single concept identifier that represents an idea.
#### Notes
* *Precoordinated expressions* combine all aspects of a potentially multifaceted concept into a single discrete form.
* The syntax used to represent *SNOMED CT expressions* is called the SNOMED CT compositional grammar and is formally defined in the Compositional Grammar - Specification and Guide.
#### Example
* The procedure, laparoscopic emergency appendectomy\*\*\*\* can be represented with the *precoordinated expression* [174041007 |laparoscopic emergency appendectomy|](http://snomed.info/id/174041007) to record an instance of this procedure. This procedure has at least three distinct facets: *removal of appendix* ,*using a laparoscope* , and *as an emergency procedure*. SNOMED CT *precoordinates* these facets in one concept.
## Alternatives
* **Precoordinated**
* **Precoordination**
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/p/precoordinated.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.