Get a demo

Developers

The Clinical Intelligence API.

Five REST endpoints that return structured, scored JSON, with clinician review built in, not bolted on.

Request access Your first API call

Endpoints

One model, every module.

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

  • POST
    /v1/origin/assessmentOrigin

    Drop adaptive pre-visit screening into your own intake flow.

  • POST
    /v1/trace/noteTrace

    Turn a transcript into a structured, reviewable draft note.

  • POST
    /v1/bridge/scheduleBridge

    Automate between-visit check-ins.

  • GET
    /v1/lens/trajectoryLens

    Show longitudinal trajectory across instruments.

  • POST
    /v1/signal/evaluateSignal

    Surface patterns that may need attention.

# 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"]
  }'

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

Your first API call.

  1. 1

    Get a key

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

  2. 2

    Send clinical input

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

  3. 3

    Receive structured output

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

  4. 4

    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"

Webhooks

Webhook events.

Check-in responses and highlighted patterns arrive as signed webhooks, with the same provenance and review state as the REST response.

  1. Something happens in the record

    A patient answers a Bridge check-in, or Signal highlights a pattern for review.

  2. We sign the event

    Each request carries a signature header, so you can verify it came from Empaithy.

  3. POST to your endpoint

    The event arrives as JSON. Reply with a 2xx to acknowledge.

  4. Retried if you are down

    Failed deliveries are retried with backoff, so build your handler to accept a repeat.

signal.review_item.created
{
  "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
}

Request API access.

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

Request access Contact the team