> For the complete documentation index, see [llms.txt](https://docs.physiqo.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.physiqo.in/04-product/prd-7.md).

# Patient Dashboard

## Patient Dashboard

***

## 1. Purpose

The Patient Dashboard serves as the primary interface for patients after authentication.

It provides complete visibility into appointments, payments, physiotherapist assignments, invoices, reviews and account information.

The dashboard shall minimize the need to contact customer support.

***

## 2. Business Objectives

The Patient Dashboard shall:

* Provide a personalized experience.
* Display appointment history.
* Improve booking transparency.
* Enable self-service actions.
* Reduce customer support dependency.
* Improve patient retention.

***

## 3. Dashboard Sections

The dashboard shall include:

* Home
* Upcoming Appointment
* Booking History
* My Profile
* Payments & Invoices
* Reviews
* Help & Support
* Referral Program (Future)

***

## 4. Home Screen

The Home Screen shall display:

* Welcome Message
* Next Appointment
* Assigned Physiotherapist
* Appointment Countdown
* Quick Book Button
* Recent Activity

***

## 5. Booking History

Patients shall be able to view:

* Booking ID
* Appointment Date
* Physiotherapist Name
* Booking Status
* Payment Status
* Invoice
* Review Status

Patients may filter bookings by:

* Upcoming
* Completed
* Cancelled
* Refunded

```mermaid
flowchart TD

A[Dashboard]

A --> B[Upcoming Appointment]

A --> C[Booking History]

A --> D[Profile]

A --> E[Payments]

A --> F[Reviews]

A --> G[Support]
```

***

## 6. Profile Management

Patients may:

* Update Name
* Update Gender
* Update Date of Birth
* Update Address
* Manage Emergency Contact (Future)

Mobile number changes shall require OTP verification.

***

## 7. Payments & Invoices

Patients shall be able to:

* View Payment History
* Download Invoice
* View Refund Status
* View Transaction Details

***

## 8. Support

Patients may:

* Contact Support
* Raise a Complaint
* Track Complaint Status
* View FAQs

***

## 9. Business Rules

* Only authenticated patients may access the dashboard.
* Dashboard data shall belong only to the logged-in patient.
* Invoice downloads shall be available only for successful payments.
* Booking history shall not be deleted by patients.

***

## 10. Backend Mapping

Controllers

* PatientDashboardController

Services

* PatientDashboardService
* BookingService
* PaymentService
* ReviewService

Repositories

* BookingRepository
* PaymentRepository
* ReviewRepository

***

## 11. Future Enhancements

* AI Recovery Progress
* Exercise Library
* Treatment Notes
* Prescription Upload
* Family Members
* Favorite Physiotherapists
* Health Reports

***

## Related Documents

* Booking PRD
* Payment PRD
* Reviews PRD
* User Journey
* Business Rules

***

Status

Draft


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.physiqo.in/04-product/prd-7.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.