The Clinical Intelligence API.

Five REST endpoints, structured JSON, a confidence score on every field. The clinician stays in the loop.

Endpoints

One model, every module.

The whole cycle or one module. Same request shape, same review semantics.

POST/v1/origin/assessmentOriginDrop adaptive pre-visit screening into your own intake flow. Send answers, get scored instruments and a review flag back.

POST/v1/trace/noteTraceTurn a transcript into a structured, reviewable draft note. Send text, get sectioned output with per-field confidence.

POST/v1/bridge/scheduleBridgeAutomate between-visit check-ins. Schedule touchpoints and pull the responses back into your record.

GET/v1/lens/trajectoryLensShow longitudinal trajectory across instruments. Query a patient, get scored trends over time.

POST/v1/signal/evaluateSignalSurface patterns that may need attention. Send recent inputs, get a prioritised review item with source context.

# surface patterns over a 14-day window
# base URL is issued with your API key
curl $EMP_API_BASE/v1/signal/evaluate \
  -H "Authorization: Bearer $EMP_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "patient_id": "pat_8fa21",
    "window": "14d",
    "inputs": ["check_ins","journal"]
  }'
200 OK

{
  "review_priority": {
    "level": "high",
    "score": 0.71
  },
  "indicators": ["sleep_decline", "isolation"],
  "route": "care_team",
  "confidence": 0.93,
  "review_required": true
}

Why build on Empaithy

Clinical reasoning, production-ready.

The hard parts handled, so you ship a product, not a research project.

Composable

Call the whole care cycle or a single module. One request shape across every endpoint.

/v1/origin/v1/trace/v1/signal

Secure by default

Bearer-token auth, encrypted transport, scoped keys, and full request audit trails.

Bearer ••••SOC 2 in progressHIPAA

Nine languages

Clinical reasoning across languages, with no pre-translation step.

ENHIARESFRDEPT+2

Confidence on every field

Each structured field carries a score and provenance, so you know what to route for review.

0.94

Quickstart

From key to first call.

Authenticate, send clinical input, receive structured output you can act on.

Get a key

Receive a project key scoped to your environment, with a sandbox to build against.

Send clinical input

Post a transcript, note, assessment response, or signal window to the relevant module endpoint.

Receive structured output

Get back scored JSON with per-field confidence and a clear flag for anything that needs review.

Keep the clinician in the loop

Surface outputs in your product with review controls, never as autonomous decisions.

// npm i @empaithy/sdk
import Empaithy from "@empaithy/sdk";

const emp = new Empaithy(process.env.EMP_KEY);

const r = await emp.signal.evaluate({
  patient_id: "pat_8fa21",
  window: "14d"
});

console.log(r.review_priority.level); // "high"
# pip install empaithy
from empaithy import Empaithy

emp = Empaithy(os.environ["EMP_KEY"])

r = emp.signal.evaluate(
    patient_id="pat_8fa21",
    window="14d",
)

print(r.review_priority.level) # "high"

Webhooks

Pushed to you as it happens.

A check-in response and a pattern highlighted for review each arrive as a signed webhook, retried with backoff, with the same provenance and review state as the REST response.

{
  "event": "signal.review_item.created",
  "patient_id": "pat_8fa21",
  "review_priority": {
    "level": "high",
    "score": 0.71
  },
  "drew_on": ["check_ins", "session_notes"],
  "review_state": "open",
  // cannot close without a documented reason
  "requires_reason": true
}

Build on the reasoning layer.

Tell us what you are building and we will get you a sandbox key.

Request access Contact the team