> ## Documentation Index
> Fetch the complete documentation index at: https://docs.phbhealth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Request a feature

> How to ask PHB for a new feature or tool today, and the recommended process for everything else.

## What exists in PHB today

### Doctors: Request this tool

The only feature-request form inside PHB is in the doctor's **Clinical Tools** library.

<Steps>
  <Step title="Search the library">
    Open **Tools** in the clinical sidebar (`/clinical/tools`) and search for what you need.
  </Step>

  <Step title="Click Request this tool">
    The button appears only when your search finds nothing.
  </Step>

  <Step title="Describe it">
    Give it a title (your search is filled in), pick a type (tool, feature, integration, data or other), and write a short briefing: what you need and why.
  </Step>

  <Step title="Send">
    You see that the request was sent to the PHB team's review queue.
  </Step>
</Steps>

PHB's team reviews these. They set a status (new, reviewing, planned, in progress, shipped or declined), a priority and a note.

<Note>
  **Not built yet:** a screen where you can see the status of your own request. You are not notified when its status changes.
</Note>

### Everyone: Was this helpful?

At the bottom of each guide in **Help & guides**, tap **No** and say what you needed. PHB's team reads these. This is for guide quality, not new features.

## Everyone else: recommended process

Nurses, front desk, cashiers, pharmacists, lab scientists, hospital admins, the Care Line and patients have no feature-request form in PHB yet.

<Warning>
  The process below is **recommended**, not built into PHB. Agree it with PHB before relying on it.
</Warning>

**Recommended:** PHB's team raises a GitHub issue in the PHB repository for each request, using this template. Staff send the details to their owner or admin, who passes them to PHB.

| Field | What to write |
| - | - |
| **Role** | Your role as PHB stores it, such as `nurse` or `receptionist`. |
| **What you were trying to do** | The task, in your own words. |
| **Expected behaviour** | What you expected PHB to do. |
| **What happens now** | What PHB actually does. |
| **Screenshots** | Only synthetic examples. Never real patient data. Use Jane Doe and `PHB-0000-0000-0000`. |
| **Business justification** | Why it matters: time saved, patients helped, risk avoided. |
| **Urgency** | Low, medium or high, and why. |
| **Acceptance criteria** | How you will know it is done, as a short checklist. |

<Warning>
  Never put patient names, HPNs, phone numbers, results or diagnoses in a request or a screenshot.
</Warning>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.