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

# Client Cases

Clients are treated according to cases, with each case representing a specific body part or condition being addressed. A client may have one or more cases within a specialty (e.g., PT, OT) when appropriate.

Each case maintains its own:

* Unique name
* Care plan
* Chart notes
* Referring provider
* Authorizations

This ensures that documentation and utilization tracking remain aligned with the correct condition. Over time, we will continue to enhance this structure by more tightly linking cases to workflows such as benefits verification, and documentation to further streamline your experience.

Our intake team will create cases during client onboarding based on the referral or diagnosis information available. When the body part or condition is known, we will name the case accordingly (e.g., Right Knee, Left Shoulder). If the condition is not specified, we will create a generic name such as PT Case 1 or OT Case 1, which you can update at any time. To rename a case, click on the case name in the client profile to open the side panel and edit the case details.

## Creating cases <a href="#creating-cases" id="creating-cases"></a>

You are free to create your own case or can ask us to do it as part of the intake process.

* For name we recommend choosing a descriptive name based on the treatment (e.g. dry needling) or condition/body part (e.g. right knee)
* Assign any providers who will be documenting under this case
* Feel free to use Case Notes for any clinical information that you’d like to easily reference during documentation
* Add a referring provider if you’d like them to receive updates on evaluations and progress notes.

### Web <a href="#web" id="web"></a>

Select “Create new” from the Overview tab of the client’s profile:

![Web screenshot](https://3656044907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6YvmN64xqPwHOm4KMzh%2Fuploads%2Fgit-blob-eb7c8764735cd134051a8e162ef8bed726a7c87b%2Fclient-cases-01.png?alt=media)

This will open a drawer on the right that lets you fill in the case details:

![Web screenshot](https://3656044907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6YvmN64xqPwHOm4KMzh%2Fuploads%2Fgit-blob-67f52b54cce087f22c5149176991b4b8270c7196%2Fclient-cases-02.png?alt=media)

### Mobile <a href="#mobile" id="mobile"></a>

Go to the client’s profile and click on the “Cases” entry:

![Mobile screenshot](https://3656044907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6YvmN64xqPwHOm4KMzh%2Fuploads%2Fgit-blob-563d6c054fe591eebfde680bbccb67b0bad44d33%2Fclient-cases-03.png?alt=media)

![Mobile screenshot](https://3656044907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6YvmN64xqPwHOm4KMzh%2Fuploads%2Fgit-blob-867cef98c55ab272d46771554876fb0690ba44ec%2Fclient-cases-04.png?alt=media)

Then you can create a Case by clicking the plus icon in the top right corner:

![Mobile screenshot](https://3656044907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6YvmN64xqPwHOm4KMzh%2Fuploads%2Fgit-blob-afc78f4d53b1b8aa36d4a4a0222258790222ed64%2Fclient-cases-05.png?alt=media)


---

# 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.pravatherapy.com/client-cases.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.
