> For the complete documentation index, see [llms.txt](https://edehr.gitbook.io/edehr-compass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edehr.gitbook.io/edehr-compass/developments-and-updates/new-feature-requests.md).

# New Feature Requests

### New Feature Requests

This section is dedicated to new feature requests from current EdEHR clients & users. If you’re not yet a user and want to learn more about the platform or how to get involved, please contact xyz for more information.

For current users, the client portal is your go-to place for submitting feature requests and providing feedback. Here’s how the process works:

1. Submit a new feature request through the client portal.
2. The EdEHR team will review your submission. If approved, your request will be queued for development.
3. If a request needs additional information, subject matter expert collaboration, or broader feedback from other participating institutions, the team will reach out for further input.
4. You can monitor the status of your requests directly through the client portal.

To learn more about the client portal, visit the Client Portal page or contact xyz.

Your ideas and feedback from across the PSI community are invaluable. Every request helps EdEHR grow in ways that are most meaningful and sustainable for everyone involved.


---

# 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:

```
GET https://edehr.gitbook.io/edehr-compass/developments-and-updates/new-feature-requests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.