---
title: "Accept a CDSS alert"
method: POST
path: "/v1/cdss/alerts/{alert_id}/accept"
tags: ["CDSS"]
---

# Accept a CDSS alert

`POST /v1/cdss/alerts/{alert_id}/accept`

## Request

- Base URL: `https://scribe-api.telepatia.ai`
- URL: `https://scribe-api.telepatia.ai/v1/cdss/alerts/{alert_id}/accept`
- Auth: HTTP bearer

Record the doctor's decision to accept a clinical decision support alert. The accepted change is applied to the medical record asynchronously, so a success response means the decision was recorded, not that the record has already been updated.

## Path parameters

- `alert_id` string, required: The alert `id` returned by the medical record documents endpoint.

## Response `200`

Successful Response

- CdssDecisionResponse: The decision recorded for a CDSS alert. A 200 means the decision is recorded. An accepted alert is applied to the medical record by a background task, so the record itself may still show its previous content immediately afterwards.
  - `id` string, required: The alert identifier the decision was recorded for.
  - `elementId` string, required: Clinical element key the alert refers to.
  - `status` string, required: The recorded decision: `accepted` or `rejected`.

## Other responses

- `400`: Bad Request — invalid parameters, validation failures, or missing fields.
- `401`: Unauthorized — missing or invalid API key.
- `403`: Forbidden — the API key is not allowed to perform this operation.
- `404`: Not Found — the requested resource does not exist.
- `409`: Conflict — resource already exists or is in a conflicting state.
- `503`: Service Unavailable — an external dependency is down.

---

[API](https://skmtc.dev/telepatia/apis/scribe-public-api.md) - [All operations](https://skmtc.dev/telepatia/apis/scribe-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/telepatia/apis/scribe-public-api/revisions/be963942e472?raw)