# What’s linked to a treatment record

Each treatment record line ties together the patient visit, catalog choices, clinicians, payments, and money fields.

### Core links

| Piece               | Role                                                                                               |
| ------------------- | -------------------------------------------------------------------------------------------------- |
| **Patient**         | Each line belongs to one patient—you open ledgers from the patient or the Treatment Records hub.   |
| **Procedure**       | The service rendered; grouping on screen uses the procedure **name** you picked from your catalog. |
| **Dentist**         | The clinician tied to that line—from your branch’s dentist list.                                   |
| **Mode of payment** | How the patient settled that line (cash, card label, etc.). Every line requires one.               |
| **Entered by**      | The staff signed in when the row was saved—helps your practice audit who captured the visit.       |

### Money fields (PHP)

* **Amount charged**
* **Amount paid**
* **Balance** — the UI also treats tiny rounding gaps as **settled** when charged and paid match

Optional **remarks** hold extra notes (materials, discounts explained in text, etc.).

### Clinical / identification fields

* **Date** — day of service (not allowed in the future).
* **Tooth No./s** — free text (`14`, `14,15`, region codes, etc.), not automatic chart painting.

### What treatment records don’t replace

* **Dental chart (odontogram)** — lives under **Dental Records**.
* **Attachments** and **patient notes** — separate patient areas included with **Growth** (scheduling-aware notes and files stay there, not on each ledger line).

### Why deletes can fail

You **cannot delete** a **procedure** or **mode of payment** still referenced by treatment lines—the app warns you until history is reconciled.

**Practice tip:** mark seldom-used catalog rows **inactive** rather than deleting, unless nothing points to them anymore.

### Link to Sales

**Sales** reads treatment-record amounts for the branch you chose, so the ledger feeds what you see there.


---

# Agent Instructions: 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:

```
GET https://associhealth.gitbook.io/associhealth-docs/treatment-records/whats-linked-to-a-record.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.