# POST /v1/medical/verify

Part of the HebrewCore documentation. Web: https://hc.itsbaba.com/docs#medical-verify · Whole docs: https://hc.itsbaba.com/docs.md · Index: https://hc.itsbaba.com/llms.txt

`POST /v1/medical/verify`

Check Hebrew that was produced some other way, for example by your own model answering in Hebrew, against its English source. Every protected value must appear verbatim, dates must be unambiguous, no number may be added, and negation and laterality must survive. Set `verification: "strict"` to add the independent review; names in `redact_terms` and identifiers are replaced before the reviewer sees the text.

```http
POST /v1/medical/verify
{
  "source": "Metformin 500 mg BID since 03/04/2026.",
  "translation": "Metformin 50 mg BID מאז 03/04/2026."
}

{
  "pass": false,
  "issues": [
    { "code": "term_missing", "severity": "error", "detail": "\"500 mg\" (dose) is missing or altered." },
    { "code": "date_missing", "severity": "error", "detail": "The date \"03/04/2026\" is missing or kept in an order a Hebrew reader will misread." },
    { "code": "number_added", "severity": "error", "detail": "The number 50 does not appear in the source." }
  ],
  "usage": { "characters": 72 }
}
```

> Translation is an aid, not a clinical record. Keep the English original available to the user, and treat any sentence with `status: "fallback"` as untranslated.

> Looking for the full machine-readable contract? The OpenAPI 3.1 spec is at [`/openapi.json`](https://hc.itsbaba.com/openapi.json), rendered interactively at [/reference](https://hc.itsbaba.com/reference).