> 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-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-and-disorder-modeling/specific-clinical-finding-and-disorder-modeling/multisystem-disorders.md).

# Multisystem disorders

Multisystem disorders are often rare conditions. There may be limited information about such disorders, so they should be carefully modeled.

When determining parent concepts:

* A multisystem parent concept should be included.
* Genetic or inherited disorders should be modeled in the same way as other genetic and inherited disorders.
* The manifestations of the disorder must always necessarily be true before assigning the relevant parents.
* Attributes must also always necessarily be true.
  * For example,
    * 702410002 |Iris coloboma with ptosis, hypertelorism, and mental retardation (disorder)| Since the coloboma of the iris is not always present, coloboma would not be explicitly modeled in the relationships.

Some multisystem disorders can be named by their manifestations. The FSN should be descriptive rather than just a list of names.

For example,

* 717909004 |Bilateral microtia with deafness and cleft palate syndrome (disorder)|

A multisystem disorder with an eponymous syndrome name should be included as a synonym only.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Multisystem%20disorders" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-and-disorder-modeling/specific-clinical-finding-and-disorder-modeling/multisystem-disorders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
