> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/extensions/nexhealth.md).

# NexHealth

Add a real-time appointment scheduling widget to your DoctorLogic website.

One of the most popular customer requests we receive is for a real-time appointment scheduling solution that directly integrates with their DoctorLogic website.

Different from an appointment request, real-time scheduling allows a patient to view your up-to-date calendar and schedule an appointment for a specific procedure, location, and provider. Once scheduled, the appointment details are automatically synced with your EHR (electronic health records) system.

We’re very excited to have partnered with NexHealth to directly integrate with their 30+ EHR platforms across a variety of specialities. Working with the teams at DoctorLogic and NexHealth we can get you set up with an integrated real-time scheduling solution in a matter of minutes.

For additional information please contact <support@doctorlogic.com>[<br>](https://help.doctorlogic.com/docs/extensions/hubspot)


---

# 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://help.doctorlogic.com/docs/extensions/nexhealth.md?ask=<question>&goal=<user_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.
