---
title: "Medical Hebrew Translation API: baba HebrewCore Clinical"
slug: "medical-hebrew-translation-api"
canonical: "https://www.itsbaba.com/medical-hebrew-translation-api"
question: "Is there an API for medical Hebrew translation?"
answer: "Yes. baba HebrewCore, the Hebrew API from baba, is a medical Hebrew translation API: its Clinical API translates clinical English into Israeli medical Hebrew with drug names, doses, lab values and codes locked behind placeholders, checks every number, negation and left/right, has an independent model review each sentence, and returns the English sentence flagged when it cannot verify the Hebrew. It streams, searches records and verifies, on every plan."
description: "Translate clinical English into verified Hebrew: drug names, doses and lab values locked, streaming, record search and verification. On every HebrewCore plan."
cluster: "developers"
html_status: "live"
updated: "2026-09-27"
numbers_used: "[20000, 100000]"
competitors_named: "[]"
---

# Medical Hebrew translation API for health products

baba HebrewCore, the Hebrew API from baba and the engine the baba Hebrew translator app runs on, has a Clinical API for health products that keep records and models in English and speak to people in Hebrew: patient portals, care-team tools, clinical assistants and record viewers.

## How each sentence is handled

1. Protect: drug names, doses and concentrations, lab values, units, ICD-10 codes, clinical abbreviations, identifiers and every number are replaced with placeholders the model cannot change.
2. Translate into Israeli medical Hebrew for a clinician or a patient.
3. Check: every placeholder appears exactly once, every number survives and none is invented, negation and left/right survive.
4. Review: an independent model checks for changes in certainty, timing, dosing wording, who is described, omissions and additions.
5. Retry once with a stronger model, or fall back: the English sentence is returned with `status: "fallback"`. Unverified Hebrew is never returned.
6. Restore the values, wrapped in Unicode isolates so `5 mg` never renders as `mg 5`; ambiguous dates are rewritten unambiguously.

## Endpoints

- `POST /v1/medical/translate`: a complete English text, up to 20,000 characters.
- `POST /v1/medical/translate/stream`: the same, as Server-Sent Events.
- `GET /v1/medical/stream` (WebSocket): send English as your model writes it; each Hebrew sentence returns once verified.
- `POST /v1/medical/query`: a Hebrew question becomes an English query for your record search.
- `POST /v1/medical/verify`: checks Hebrew produced elsewhere against its English source.

## Example

```bash
curl https://hc.itsbaba.com/v1/medical/translate \
  -H "Authorization: Bearer hc_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "text": "You are taking Eliquis 5 mg twice a day. Your dose was changed on 03/04/2026.", "audience": "patient", "reader_gender": "female", "protected_terms": ["Eliquis 5 mg"] }'
```

Result text: את נוטלת Eliquis 5 mg פעמיים ביום. המינון שלך שונה ב־4 במרץ 2026.

## Access and data handling

- On every plan, including Free. Clinical calls count 3x against the monthly characters.
- Server to server only: a request with a browser `Origin` header is refused with `403 server_only`.
- Nothing is stored beyond character counts; responses carry `Cache-Control: no-store` and `X-Content-Stored: false`.
- Names in `redact_terms`, and record numbers, phone numbers, SSNs and emails found in the text, reach the model only as blank placeholders.

Translation is an aid, not a clinical record. Keep the English original available and treat any fallback sentence as untranslated.

We did not find another vendor documenting a clinical Hebrew endpoint with server-only enforcement and placeholder protection for personal data as of September 2026.

Related: https://www.itsbaba.com/hebrewcore , https://www.itsbaba.com/best-hebrew-api , https://www.itsbaba.com/hebrew-medical-phrases