> For the complete documentation index, see [llms.txt](https://docs.omnivatelehealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnivatelehealth.com/consulting-provider/specialty.md). # Specialty View specialty list ### Overview The **Specialty Section** in the side menu categorises and organizes various medical specialities, allowing patients to easily find providers based on their medical needs.

Speciality

**Viewing Specialties**: * It will contain the list of available specialities. * **Action:** To edit and delete the specialities **Searching for a Specialty**: * Use the **search bar** at the top of the speciality list to type and quickly find a specific speciality. **Adding a New Specialty**: * Click the **Add Specialty** button, typically located at the top-right corner of the speciality page. * Choose from the list of specialty * Click **Save** to add the new speciality to the system.

Add speciality

--- # 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.omnivatelehealth.com/consulting-provider/specialty.md?ask=&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.