> 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/education/snomed-ct-education-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-and-disorder-modeling/specific-clinical-finding-and-disorder-modeling/remission.md).
# Remission
**This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.**
## Disorder in remission
*< X> disorder in remission* concepts require a stated relationship to the appropriate primitive *Disorder in remission* supertype, in addition to the appropriate supertype for the disorder.
For example,
16270831000119107 |Bulimia nervosa in partial remission (disorder)| has stated parents of 698698008 |Bulimia nervosa in remission (disorder)| and 765207007 |Disorder in partial remission (disorder)|.
Figure: Stated view of 16270831000119107 |Bulimia nervosa in partial remission (disorder)|
Where the primitive supertype for the disorder is |Disease (disorder)|, only the *Disorder in remission* supertype will be required.
For example,
91856007 |Acute lymphoid leukemia in remission (disorder)| has only one stated parent of 765205004 |Disorder in remission (disorder)|, because a potential supertype of 64572001 |Disease (disorder)| would be unnecessary.
Figure: Stated view of 91856007 |Acute lymphoid leukemia in remission (disorder)|
See also relative section:
Mental health
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/education/snomed-ct-education-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-and-disorder-modeling/specific-clinical-finding-and-disorder-modeling/remission.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.
.png?alt=media)
.png?alt=media)
