# Procedures **Procedures** are your practice’s **service catalog**: each item has a name, optional description, **default cost** in PHP, optional **duration in minutes**, and an **active** flag. When you add a treatment record, you pick one of these procedures (searchable autocomplete). ### Where to manage procedures **Procedures** in the main menu. Flow: * **New procedure** — define catalog row * **Procedure detail** — review fields * **Edit** — update fee, description, duration, active flag ### Branch scope Like dentists, procedures are stored **per branch**. Pick the correct **header branch** before creating catalog rows or posting treatment lines so fees align with the location serving the patient. ### Link to treatment records Every treatment line stores a **procedure ID**. The patient ledger groups lines **by procedure name** and rolls up charged/paid/balance per group. ### Why deletion may be blocked If you try to delete (or retire in a way that conflicts with linked rows) a procedure that is still referenced by treatment records, the app reports that it is **linked** to one or more treatment records and **cannot be deleted** until those records are reviewed or reassigned. This protects billing history. **Operational habit:** prefer marking seldom-used procedures **inactive** instead of deleting, unless you are sure no historical lines reference them. ### Fees on the ledger vs catalog Catalog **cost** is your reference/default when quoting or configuring fees; each treatment line still stores its own **amount charged** and **amount paid**, so you can capture discounts or overrides per visit without changing the master procedure row. ### Plan requirement **Procedures** is available on **Starter** and above—the same requirement as **Treatment Records**. --- # 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/procedures.md?ask= ``` 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.