> 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/pneumonia-vs-pneumonitis.md).

# Pneumonia vs. Pneumonitis

The terms *pneumonia* and *pneumonitis* are often used interchangeably. In SNOMED CT, *pneumonia* is used for infectious causes, and *pneumonitis* is used for noninfectious causes.

{% hint style="warning" %}
Some concepts may contain a synonym with the other *pneumoni*- term due to high/common usage in medical literature.
{% endhint %}

Pneumonia is a type of pneumonitis, as inflammation is present in both. The distinguishing feature between the two disorders is the presence of infection in pneumonia. Pneumonia has a Pathological process (attribute) of Infectious process (qualifier value); pneumonitis does not.

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FykMS0a9VG9DrNzbxMPjt%2Fimage.png?alt=media&amp;token=6b07631c-9273-4c93-8764-d1de681b1f17" alt=""><figcaption></figcaption></figure>

<figure><img src="https://github.com/SNOMED-Documents/snomed-editorial-guide/blob/main/authoring/clinical-finding-and-disorder/images/225051456.png" alt=""><figcaption><p>Figure: Stated view of 205237003 |Pneumonitis (disorder)|</p></figcaption></figure>

<figure><img src="https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2Fu8zRWSfUVR2zDpu7WWzO%2Fimage.png?alt=media&amp;token=f056729d-dfaa-49b9-8e4a-899c381eb4bd" alt=""><figcaption></figcaption></figure>

<figure><img src="https://github.com/SNOMED-Documents/snomed-editorial-guide/blob/main/authoring/clinical-finding-and-disorder/images/225051457.png" alt=""><figcaption><p>Figure: Stated view of 233604007 |Pneumonia (disorder)|</p></figcaption></figure>

### Morphologic abnormality

The morphologic abnormality for both 233604007 |Pneumonia (disorder)| and 205237003 |Pneumonitis (disorder)| is 409774005 |Inflammatory morphology (morphologic abnormality)|.

The clinically-warranted morphologic abnormality for many subtypes of pneumonia is 707496003 |Inflammation and consolidation (morphologic abnormality)|. Consolidation is a feature of most forms of pneumonia; however, it may not be a feature of all pneumonias, such as atypical pneumonias.

### Guidance exception

Content has been added that aligns with the 2025 International Multidisciplinary Classification of the Interstitial Pneumonias with attribution to ERS/ATS - European Respiratory Society/American Thoracic Society. For these concepts, the fully specified term and preferred term align with the classification which uses the term *pneumonia* instead of *pneumonitis,* even in the absence of an infectious cause.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Pneumonia%20vs.%20Pneumonitis" 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 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-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/pneumonia-vs-pneumonitis.md?ask=<question>&goal=<user_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.