# Give or withdraw the medical consent

Canonical page: https://docs.ovok.com/api/me/consent/give-or-withdraw-the-medical-consent

`POST /v1/me/consent/medical`

Gives or withdraws the medical settings notifications consent for the signed-in practitioner and returns the resulting medical consent. Other consents are not changed.

**Auth:** Bearer token for a practitioner session (the profile must be a `Practitioner`). The caller's access policy must grant `Consent:read`, `Consent:search`, `Consent:create` and `Consent:update` (a project admin who holds no access policy skips this check).
**Scope:** The caller's practitioner profile in the caller's project (from the token).

## Behaviour

- `medicalSettingsNotificationsConsent: true` records the consent on the currently published version. `false` withdraws it.
- Sending the current value again writes nothing.
- The value read by `GET /v1/slim/user/consents` changes in the same commit.
- The response has the shape of `GET /v1/me/consent/medical`: `medical` is `null` after a withdrawal.


## Example

```bash
curl -X POST 'https://api.sandbox.ovok.com/v1/me/consent/medical' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk' \
  -H 'Content-Type: application/json' \
  -d '{ "medicalSettingsNotificationsConsent": true }'
```