> 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/patient/ask-for-referral.md).
# Ask for Referral
In this section, patient can able to ask for a referral
In the Ask for Referral section, patients can easily request referrals.
Ask for referral
Referral Creation Process
1. **Patient Search**
* Access the patient search feature to find patient information using their name.
2. **Select Specialty**
* After selecting the patient, choose the appropriate specialty or treatment category that best fits the patient's needs, such as mental illness or nausea
3. **Choose Referring Provider**
* A list of available referral doctors will be displayed. Select the referring provider who you believe would be best suited for the patient's needs.
4. **Provide Reason and attachment**
* Explain the reason for the referral. This helps the specialist understand the patient's situation better and provide appropriate care.
* Attach Documents: If you have any relevant documents or files that could support the referral, such as medical records or test results, you can attach them here. This additional information can help the specialist make informed decisions about the patient's care.
---
# 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/patient/ask-for-referral.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.
