ForHosting KIT · Developer Utilities

Revised Trauma Score calculator

The Revised Trauma Score, often abbreviated RTS, is the physiology score Champion, Sacco, Copes, Gann, and colleagues published in 1989 to summarise three bedside observations into one weighted number for trauma teaching and research coding.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

This calculator accepts the Glasgow Coma Scale, systolic blood pressure in millimetres of mercury, and respiratory rate in breaths per minute, maps each observation onto the published 0–4 coded table, and returns the weighted RTS using the Champion coefficients 0.9368 for GCS, 0.7326 for systolic pressure, and 0.2908 for respiratory rate. Every input must be a non-negative finite number; a missing field, a negative value, or a non-numeric token fails with invalid_input and is not billed. The same deterministic module powers the free browser widget and the API path, so teaching keys, coding scripts, and product prototypes never disagree on a given vignette. Treat the JSON as a transparent arithmetic aid, not a diagnosis or a substitute for licensed trauma, emergency, or critical-care judgment.

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 Revised Trauma Score (RTS)?

It is Champion's 1989 physiology score from Glasgow Coma Scale, systolic blood pressure, and respiratory rate. This tool returns the 0–4 coded values and the weighted RTS using coefficients 0.9368, 0.7326, and 0.2908.

How is the weighted RTS calculated?

Each vital is coded 0–4 with the Champion tables, then RTS = 0.9368×GCS_c + 0.7326×SBP_c + 0.2908×RR_c. The result is rounded to four decimal places and ranges from 0 to 7.8408.

What happens if an input is negative or missing?

The call fails with invalid_input naming the field. Every input must be a non-negative finite number; missing fields, NaN, Infinity, and negative values are rejected and are not billed.

Is a respiratory rate of 0 or a systolic pressure of 0 allowed?

Yes. Zero is a published Champion code-0 row (no measurable pressure or no respiratory effort). Only negative or non-numeric values are rejected.

Can I use this result to triage a real patient?

No. This is an educational arithmetic aid, not medical advice. Real triage, transfer, and treatment need a licensed clinician and the rest of the clinical picture this calculator does not collect.

What does the Revised Trauma Score calculator cost?

The browser widget runs free and locally. The same computation via the API is billed at $0.002 per successful request; 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/revised-trauma-score

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/revised-trauma-score \
  -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/revised-trauma-score", {
  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/revised-trauma-score",
    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/revised-trauma-score", 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/revised-trauma-score", 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.revised_trauma_score",
  "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 →