ForHosting KIT · Developer Utilities

TIMI STEMI risk score

The TIMI risk score for STEMI estimates thirty-day mortality after ST-elevation myocardial infarction from bedside findings a coronary-care team already records: age, history of diabetes hypertension or angina, systolic blood pressure, heart rate, Killip class, body weight, anterior ST elevation or left bundle-branch block, and hours to reperfusion.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

This calculator implements the published Morrow 2000 point table used in the InTIME-II trial, returning an integer score from zero to fourteen and the matching estimated thirty-day mortality percentage. Age must be a positive number; missing, non-finite, zero, or negative age fails with invalid_input and is not charged. The same pure arithmetic powers the free browser widget and the prepaid API at $0.002 per successful item. The score is educational risk stratification, not a diagnosis, not a reperfusion decision, and not a substitute for a cardiologist.

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 scoring system does this TIMI STEMI calculator use?

The TIMI risk score for STEMI published by Morrow and colleagues in 2000 from InTIME-II: integer points from age, diabetes/hypertension/angina history, systolic blood pressure, heart rate, Killip class, weight, anterior ST elevation or LBBB, and time to treatment, mapped to thirty-day mortality percentages.

What happens if age is zero, negative, or not a number?

The request fails with invalid_input. Age must be a positive number (years); missing, non-finite, zero, and negative values are rejected and are not charged.

How is estimated mortality derived from the score?

The integer total 0–14 is looked up on the InTIME-II thirty-day mortality table: 0.8, 1.6, 2.2, 4.4, 7.3, 12.4, 16.1, 23.4, 26.8 percent for scores 0 through 8, and 35.9 percent for scores above 8. The horizon field is always 30_day.

Is a TIMI STEMI score a diagnosis or a treatment recommendation?

No. It is an educational risk-stratification score with published thirty-day mortality bands. It does not diagnose infarction, choose fibrinolysis versus PCI, or replace a cardiologist.

Is the TIMI STEMI risk score free?

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

POSThttps://api.kit.forhosting.com/health/timi-stemi

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/timi-stemi \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"age":72,"history_dm_htn_angina":true,"systolic_bp":92,"heart_rate":108,"killip_class":2,"weight":64,"anterior_ste_or_lbbb":true,"time_to_treatment":5}'

const res = await fetch("https://api.kit.forhosting.com/health/timi-stemi", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "age": 72,
    "history_dm_htn_angina": true,
    "systolic_bp": 92,
    "heart_rate": 108,
    "killip_class": 2,
    "weight": 64,
    "anterior_ste_or_lbbb": true,
    "time_to_treatment": 5
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/health/timi-stemi",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "age": 72,
    "history_dm_htn_angina": true,
    "systolic_bp": 92,
    "heart_rate": 108,
    "killip_class": 2,
    "weight": 64,
    "anterior_ste_or_lbbb": true,
    "time_to_treatment": 5
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/timi-stemi", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"age":72,"history_dm_htn_angina":true,"systolic_bp":92,"heart_rate":108,"killip_class":2,"weight":64,"anterior_ste_or_lbbb":true,"time_to_treatment":5}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"age":72,"history_dm_htn_angina":true,"systolic_bp":92,"heart_rate":108,"killip_class":2,"weight":64,"anterior_ste_or_lbbb":true,"time_to_treatment":5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/timi-stemi", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "age": 72,
  "history_dm_htn_angina": true,
  "systolic_bp": 92,
  "heart_rate": 108,
  "killip_class": 2,
  "weight": 64,
  "anterior_ste_or_lbbb": true,
  "time_to_treatment": 5
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "health.timi_stemi",
  "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 →