ForHosting KIT · Developer Utilities

Wells PE score calculator

The Wells score for pulmonary embolism is a seven-item bedside rule that converts clinical findings into an additive point total and a published likelihood band.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

This calculator accepts six required clinical flags plus a measured heart rate in beats per minute, applies the original Wells 2000 weights—three points for signs of deep-vein thrombosis, three points when pulmonary embolism is the leading or equally likely diagnosis, one and a half points for tachycardia above one hundred beats per minute, one and a half points for immobilization or recent surgery, one and a half points for prior DVT or PE, one point for hemoptysis, and one point for active malignancy—and returns the score together with the three-tier and two-tier likelihood categories. Every criterion must be answered; a missing flag or heart rate fails with invalid_input and is not billed. The same deterministic module powers the free browser widget and the API, so teaching keys, research coding, and product prototypes never disagree on a given vignette. Treat the JSON as transparent arithmetic, not a diagnosis or a substitute for licensed clinical judgment about imaging, anticoagulation, or whether to discharge a patient.

How to use it

Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.

Check your inputs

Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.

Use it again or automate it

Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.

What you can do with it

Get an answer now

Enter one set of values and see the result without building a spreadsheet or script.

Compare scenarios

Change one value at a time and rerun the calculation to understand what affects the result.

Automate repeated work

Use the API when the same calculation needs to run inside your product or workflow.

FAQ

What is the Wells PE score?

It is Wells' seven-item bedside rule for the pretest probability of pulmonary embolism. This tool returns the weighted point total, the three-tier likelihood (low, moderate, high), and the two-tier PE-unlikely versus PE-likely band.

Which criteria does the calculator use and how many points is each worth?

Signs of DVT (3.0), PE as the leading or equally likely diagnosis (3.0), heart rate greater than 100 (1.5), immobilization or recent surgery (1.5), prior DVT or PE (1.5), hemoptysis (1.0), and active malignancy (1.0).

How is heart rate scored?

Send heart_rate in beats per minute as a finite non-negative number. The engine awards 1.5 points only when the rate is strictly greater than 100; a rate of 100 exactly scores zero. The response echoes heart_rate_gt_100 so the threshold is visible.

What happens if a criterion answer is missing?

The call fails with invalid_input naming the field. Every flag and the heart rate must be answered; missing fields and tokens such as yes are rejected and are not billed.

How should I read low, moderate, and high probability?

Low is a score below 2, moderate is 2 through 6, and high is above 6. Independently, a score of 4 or less is PE unlikely and a score above 4 is PE likely. Figures are historical cohort strata, not a personal prognosis.

Can I use this result to rule out pulmonary embolism?

No. This is an educational arithmetic aid, not medical advice. Imaging, anticoagulation, and whether to discharge need a licensed clinician and the rest of the clinical picture this calculator does not collect.

What does the Wells PE calculator cost?

The browser widget runs free and locally. The same computation via the API is billed at $0.002 per successful request from prepaid KIT balance; invalid_input failures are not charged.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/health/wells-pe

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/health/wells-pe \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"dvt_signs":true,"pe_most_likely":true,"heart_rate":110,"immobilization_or_surgery":false,"prior_dvt_pe":true,"hemoptysis":false,"malignancy":false}'

const res = await fetch("https://api.kit.forhosting.com/health/wells-pe", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "dvt_signs": true,
    "pe_most_likely": true,
    "heart_rate": 110,
    "immobilization_or_surgery": false,
    "prior_dvt_pe": true,
    "hemoptysis": false,
    "malignancy": false
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/health/wells-pe",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "dvt_signs": true,
    "pe_most_likely": true,
    "heart_rate": 110,
    "immobilization_or_surgery": false,
    "prior_dvt_pe": true,
    "hemoptysis": false,
    "malignancy": false
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/wells-pe", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"dvt_signs":true,"pe_most_likely":true,"heart_rate":110,"immobilization_or_surgery":false,"prior_dvt_pe":true,"hemoptysis":false,"malignancy":false}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"dvt_signs":true,"pe_most_likely":true,"heart_rate":110,"immobilization_or_surgery":false,"prior_dvt_pe":true,"hemoptysis":false,"malignancy":false}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/wells-pe", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "dvt_signs": true,
  "pe_most_likely": true,
  "heart_rate": 110,
  "immobilization_or_surgery": false,
  "prior_dvt_pe": true,
  "hemoptysis": false,
  "malignancy": false
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "health.wells_pe",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →