Sepsis screen - SIRS plus mentation criteria and flag, free
Sepsis screening from bedside numbers is a common teaching and triage task: given temperature, heart rate, respiratory rate, white cell count, and a numeric mentation score, does the pattern meet systemic inflammatory response criteria plus altered awareness?
Run — free
Runs in your browser. Free, unlimited — your data never leaves this page.
This capability applies a deterministic SIRS-plus-mentation screen used in education and software, not a bedside diagnosis. It scores each of the five inputs against published adult teaching thresholds, lists every criterion that fires, and raises a sepsis flag when at least two criteria are met. Non-numeric, missing, or non-finite values fail with invalid_input and are never billed. The free browser widget and the API share one pure arithmetic module, so homework checkers and production clients pin the same JSON. Successful API items cost $0.002.
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
How does the sepsis screen decide which criteria are met?
It applies adult SIRS teaching cuts to temperature, heart rate, respiratory rate, and white cell count, plus GCS below 15 for mentation. The response lists every cut that fired in criteria_met.
When is sepsis_flag true?
sepsis_flag is true when two or more of the five criteria fire (criteria_count >= 2). A single abnormal vital with a normal GCS does not raise the flag.
What inputs are required?
Five finite numbers: temperature in °C, heart_rate in bpm, respiratory_rate in breaths per minute, white_cell_count in ×10^9/L, and mentation as an integer GCS from 3 to 15.
What happens if an input is not numeric?
The request fails with invalid_input naming the field. Booleans, empty strings, infinities, and non-numeric text such as a word instead of a temperature are rejected and not charged.
Is this a diagnosis, and what does the sepsis screen cost?
No. It is an educational numeric screen, not a medical device. The browser tool runs free on your device. API calls use prepaid KIT balance at $0.002 per successful item; validation 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
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/sepsis \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"items":["valor-1","valor-2"]}'const res = await fetch("https://api.kit.forhosting.com/health/sepsis", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"items": [
"valor-1",
"valor-2"
]
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/sepsis",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"items": [
"valor-1",
"valor-2"
]
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/sepsis", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"items":["valor-1","valor-2"]}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"items":["valor-1","valor-2"]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/sepsis", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"items": [
"valor-1",
"valor-2"
]
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.sepsis",
"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
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. |