# PATIENT_BILLING_ENABLED

Canonical page: https://docs.ovok.com/settings-and-features/settings/patient-billing-enabled

Turns on [patient billing and insurance](/patient-billing) for the project. Its routes under `/v1/patient-billing` then store patients' insurance, app plan, billing account and invoices as FHIR `Coverage`, `Account` and `Invoice`.

| | |
| --- | --- |
| Type | Boolean setting |
| Change with | `PUT /v1/project/settings/PATIENT_BILLING_ENABLED` |
| Read with | `GET /v1/project/settings` |
| Who can change it | Project admin |
| When unset | Off |
| Scope | Each project has its own value. |
| When off | Every `/v1/patient-billing` route answers `403` [`PATIENT_BILLING_DISABLED`](/errors/patient-billing-disabled). |

```bash
curl --request PUT \
  --url 'https://api.sandbox.ovok.com/v1/project/settings/PATIENT_BILLING_ENABLED' \
  --header "Authorization: Bearer ${OVOK_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data '{"enabled": true}'
```

## What turning it on does [#what-turning-it-on-does]

The routes start to answer. The setting writes no resource and creates no policy.

Turning it off stops the routes again. It deletes nothing: the coverages, accounts and invoices stay in FHIR.

## Gotchas [#gotchas]

- **It grants nobody access.** Callers still need the `patient_billing_*` rows in their access policy, and writing plans and invoices needs a project admin or an admin ClientApplication. See [Patient billing access](/patient-billing/access).
- **Check the project.** The setting is per project, so `PATIENT_BILLING_DISABLED` can mean the token belongs to a project where it is still off.

## Related [#related]

- [Patient billing and insurance](/patient-billing)
- [Patient billing access](/patient-billing/access)
- [Settings and features](/settings-and-features)
