> For the complete documentation index, see [llms.txt](https://dentaltap.gitbook.io/dentaltap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dentaltap.gitbook.io/dentaltap/treatments/periodontal-chart.md).
# Periodontal Chart
The Periodontal Chart is used to record detailed periodontal findings that cannot be represented on the standard dental chart.
It includes a complete set of periodontal metrics, such as:
* Pocket depths
* Gingival recession
* Clinical attachment levels
* Bleeding on probing
* Plaque and calculus indicators
* Furcation involvement
* Tooth mobility
Periodontal data can be recorded per tooth, providing a precise and structured overview of the patient’s periodontal status.
To start with Periodontal Chart, simply select an appointment date and proceed with entering data:
### Compare Periodontal Charts
You can compare multiple periodontal charts by selecting different appointment dates. This allows you to view periodontal metrics across multiple visits and track changes and progress over time.
The Periodontal Chart module provides a structured way to record, track, and compare periodontal metrics over time, helping clinicians monitor changes and assess treatment progress across visits.
---
# 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://dentaltap.gitbook.io/dentaltap/treatments/periodontal-chart.md?ask=&goal=
```
`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.