# Injury Severity Score (ISS) ISS Status: LIVE Price: $0.005 USDC `GET /api/calc/iss` HTML: https://magentlab.com/docs/iss Markdown: https://magentlab.com/docs/iss.md Not a medical device. Not a diagnosis, dose, or listing recommendation. ## What it computes Compute the Baker 1974 Injury Severity Score as the sum of squares of the three highest caller-assigned AIS body-region grades, or 75 if any region is AIS 6. ## When to use When an agent needs the published Baker 1974 ISS total and must not invent AIS grades or substitute NISS. ## When not to use - Not a triage order, disposition, or trauma-activation decision. - AIS grades are caller-assigned integers 0-6. magent does not assign AIS from an injury list or chart narrative. - Baker 1974 ISS only: the three most severely injured body regions. Not NISS, which squares the three worst injuries regardless of region. ## Formula ``` ISS = a^2 + b^2 + c^2 for the three highest AIS body-region grades (0-5); any AIS 6 => 75 ``` ## Citation [The injury severity score: a method for describing patients with multiple injuries and evaluating emergency care](https://doi.org/10.1097/00005373-197403000-00001) Baker SP, O'Neill B, Haddon W Jr, Long WB J Trauma. 1974;14(3):187-196 DOI: [10.1097/00005373-197403000-00001](https://doi.org/10.1097/00005373-197403000-00001) ## Worked example ### Head 3, chest 2, abdomen 1 Given: `ais_abdomen=1, ais_chest=2, ais_external=0, ais_extremity=0, ais_face=0, ais_head=3` 1. Three highest AIS: 3, 2, 1 2. ISS = 3^2 + 2^2 + 1^2 = 9 + 4 + 1 = 14 ### AIS 6 head is unsurvivable 75 Given: `ais_abdomen=0, ais_chest=0, ais_external=0, ais_extremity=0, ais_face=0, ais_head=6` 1. Any AIS 6 → ISS = 75 ## Also searched as - injury severity score - ISS trauma - Baker ISS - abbreviated injury scale ISS - polytrauma ISS - AIS ISS ## Parameters - `ais_head` (integer, required): Caller-assigned AIS grade for the head or neck (integer 0-6). magent does not assign AIS from an injury list. - `ais_face` (integer, required): Caller-assigned AIS grade for the face (integer 0-6). - `ais_chest` (integer, required): Caller-assigned AIS grade for the chest (integer 0-6). - `ais_abdomen` (integer, required): Caller-assigned AIS grade for the abdomen or pelvic contents (integer 0-6). - `ais_extremity` (integer, required): Caller-assigned AIS grade for the extremities or pelvic girdle (integer 0-6). - `ais_external` (integer, required): Caller-assigned AIS grade for external (integer 0-6). ## Bulk (POST) POST the same path with a JSON items array. The first item is the GET unit; each additional item is $0.002. Invalid items return HTTP 400 before settlement. Method: `POST /api/calc/iss` Max items: 25 Price: unit_amount + extra_item_amount * (n - 1) (unit 5000 atomic, extra 2000 atomic) Status: PREVIEW - 1 to 25 items. Each item uses the same keys as the GET query parameters. - POST of 1 item costs the same as GET. Lists longer than 25: chunk into multiple POSTs. Extra items still execute; do not pad dummy rows. - The first invalid item fails the whole request (index in the 400 JSON). You are not charged. - HTTP 200 is {count, path, items}. Each items[i] is the GET 200 body for that row. - Catalog misses (empty matches, found=false) stay paid 200s inside that slot. - x402 resource URL is this path plus n and body_sha256. Browsers that prefer text/html get the same paywall as GET; Pay retries POST with the same items. Example request: ```json { "items": [ { "ais_abdomen": "1", "ais_chest": "2", "ais_external": "0", "ais_extremity": "0", "ais_face": "0", "ais_head": "3" }, { "ais_abdomen": "1", "ais_chest": "2", "ais_external": "0", "ais_extremity": "0", "ais_face": "0", "ais_head": "3" } ] } ``` Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/iss Example 200: ```json { "count": 2, "path": "/api/calc/iss", "items": [ { "components": [ { "factor": "ais_head", "points": 9, "present": true, "ais": 3 }, { "factor": "ais_face", "points": 0, "present": false, "ais": 0 }, { "factor": "ais_chest", "points": 4, "present": true, "ais": 2 }, { "factor": "ais_abdomen", "points": 1, "present": true, "ais": 1 }, { "factor": "ais_extremity", "points": 0, "present": false, "ais": 0 }, { "factor": "ais_external", "points": 0, "present": false, "ais": 0 } ], "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.", "citation": { "authors": "Baker SP, O'Neill B, Haddon W Jr, Long WB", "doi": "10.1097/00005373-197403000-00001", "id": "baker-1974", "source": "J Trauma. 1974;14(3):187-196", "title": "The injury severity score: a method for describing patients with multiple injuries and evaluating emergency care" }, "formula": "iss", "formula_expression": "ISS = a^2 + b^2 + c^2 for the three highest AIS body-region grades (0-5); any AIS 6 => 75", "max_score": 75, "score": 14, "ais_abdomen": 1, "ais_chest": 2, "ais_external": 0, "ais_extremity": 0, "ais_face": 0, "ais_head": 3, "used_ais": [ 3, 2, 1 ] }, { "components": [ { "factor": "ais_head", "points": 9, "present": true, "ais": 3 }, { "factor": "ais_face", "points": 0, "present": false, "ais": 0 }, { "factor": "ais_chest", "points": 4, "present": true, "ais": 2 }, { "factor": "ais_abdomen", "points": 1, "present": true, "ais": 1 }, { "factor": "ais_extremity", "points": 0, "present": false, "ais": 0 }, { "factor": "ais_external", "points": 0, "present": false, "ais": 0 } ], "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.", "citation": { "authors": "Baker SP, O'Neill B, Haddon W Jr, Long WB", "doi": "10.1097/00005373-197403000-00001", "id": "baker-1974", "source": "J Trauma. 1974;14(3):187-196", "title": "The injury severity score: a method for describing patients with multiple injuries and evaluating emergency care" }, "formula": "iss", "formula_expression": "ISS = a^2 + b^2 + c^2 for the three highest AIS body-region grades (0-5); any AIS 6 => 75", "max_score": 75, "score": 14, "ais_abdomen": 1, "ais_chest": 2, "ais_external": 0, "ais_extremity": 0, "ais_face": 0, "ais_head": 3, "used_ais": [ 3, 2, 1 ] } ] } ``` ## Response fields - `formula` (string): iss - `formula_expression` (string): Exact expression used - `score` (integer): ISS 0-75 - `max_score` (integer): 75 - `ais_head` (integer): Caller-assigned AIS head/neck 0-6 - `ais_face` (integer): Caller-assigned AIS face 0-6 - `ais_chest` (integer): Caller-assigned AIS chest 0-6 - `ais_abdomen` (integer): Caller-assigned AIS abdomen/pelvic contents 0-6 - `ais_extremity` (integer): Caller-assigned AIS extremities/pelvic girdle 0-6 - `ais_external` (integer): Caller-assigned AIS external 0-6 - `used_ais` (array): The three highest AIS grades used for the sum of squares (descending) - `components` (array): Per-region AIS and AIS squared - `citation` (object): Baker et al. J Trauma 1974 citation - `disclaimer` (string): Not-a-device notice ## Example JSON Frozen fixture. Not a live lookup. ```json { "components": [ { "factor": "ais_head", "points": 9, "present": true, "ais": 3 }, { "factor": "ais_face", "points": 0, "present": false, "ais": 0 }, { "factor": "ais_chest", "points": 4, "present": true, "ais": 2 }, { "factor": "ais_abdomen", "points": 1, "present": true, "ais": 1 }, { "factor": "ais_extremity", "points": 0, "present": false, "ais": 0 }, { "factor": "ais_external", "points": 0, "present": false, "ais": 0 } ], "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.", "citation": { "authors": "Baker SP, O'Neill B, Haddon W Jr, Long WB", "doi": "10.1097/00005373-197403000-00001", "id": "baker-1974", "source": "J Trauma. 1974;14(3):187-196", "title": "The injury severity score: a method for describing patients with multiple injuries and evaluating emergency care" }, "formula": "iss", "formula_expression": "ISS = a^2 + b^2 + c^2 for the three highest AIS body-region grades (0-5); any AIS 6 => 75", "max_score": 75, "score": 14, "ais_abdomen": 1, "ais_chest": 2, "ais_external": 0, "ais_extremity": 0, "ais_face": 0, "ais_head": 3, "used_ais": [ 3, 2, 1 ] } ``` ## Errors - HTTP 400 `invalid_ais`: ais_head, ais_face, ais_chest, ais_abdomen, ais_extremity, and ais_external must each be an integer from 0 to 6. Returned before settlement; you are not charged. - HTTP 400 `invalid_items`: POST body must be a JSON object with only an items array Returned before settlement; you are not charged. - HTTP 400 `invalid_item_count`: items must be an array of 1 to 25 objects Returned before settlement; you are not charged. - HTTP 400 `invalid_item`: each items entry must be a JSON object Returned before settlement; you are not charged. Shared HTTP 402 and 503: https://magentlab.com/docs/payments ## Related tools - [Glasgow Coma Scale](https://magentlab.com/docs/gcs) — Compute the Glasgow Coma Scale as the sum of caller-assigned eye, verbal, and motor integers. The 1974 or 1976 edition is required. - [ABCD2 score](https://magentlab.com/docs/abcd2) — Compute the ABCD2 score as age, blood pressure, caller-assigned clinical features, symptom duration, and diabetes. - [RTS](https://magentlab.com/docs/rts) — Compute Champion 1989 coded GCS, SBP, and respiratory-rate values, the triage T-RTS sum, and the weighted RTS used for outcome evaluation. ## Payment Unpaid requests return HTTP 402 even if query parameters or POST items are missing or invalid, so CDP and agents can index the path. After a PAYMENT-SIGNATURE, invalid params return HTTP 400 JSON before settlement. magent does not charge. Fix the params, then request a new 402 quote for that complete URL. Catalog misses (empty matches, found=false) are valid paid 200s. - GET the tool with Accept: application/json (do not send Accept: text/html unless you want the human paywall). - HTTP 402 means you have not paid. Decode the base64 PAYMENT-REQUIRED header. HTTP 503 is not a new quote. - Sign accepts[0] (exact, EIP-3009) with validBefore = now + maxTimeoutSeconds (600 seconds), or accepts[1] (batch-settlement deposit/voucher) on product GET. Ping and POST {items} stay exact. Magent retries transient facilitator 429/5xx before answering. - Retry the same URL with PAYMENT-SIGNATURE (base64 JSON echoing accepted, payload, and extensions when present). - Success is HTTP 200 JSON plus PAYMENT-RESPONSE. exact settles before the tool. batch-settlement verifies (and deposit-settles) before the tool and commits the charge after HTTP 2xx. HTTP 503: retry the same PAYMENT-SIGNATURE. Mint a new exact nonce only after a new HTTP 402. - offered `exact` on eip155:8453: Fixed-price USDC on Base. The buyer authorizes the advertised amount (EIP-3009). magent settles before the tool runs (paymentFlow upfront). extra.assetTransferMethod=eip3009 extra.paymentFlow=upfront. - offered `batch-settlement` on eip155:8453: Payment-channel vouchers claimed later in batches. Exact stays accepts[0]. Same-path POST {items} is still exact. extra.assetTransferMethod=eip3009 extra.paymentFlow=authorization. - not offered `upto`: Not offered. Usage-based: buyer authorizes a ceiling, seller settles the actual amount after work. Reserved for a future metered tool. Not for current calculators or code search. Same-path POST {items} is still scheme exact: one EIP-3009 authorization for GET unit plus $0.002 per extra item. That is not x402 batch-settlement (payment channels / vouchers). Shared HTTP 402 and 503 table: https://magentlab.com/docs/payments Stdio MCP (one process per host): https://magentlab.com/docs/mcp ## Guarantees - HTTP 402 is unpaid, including a missing query. After PAYMENT-SIGNATURE, invalid parameters return HTTP 400 before settlement. You are not charged. - exact: settlement finishes before the tool (paymentFlow upfront). batch-settlement: verify/deposit before the tool; chargedCumulativeAmount commits after HTTP 2xx. Uncertain or failed settlement fails closed (HTTP 503). Retry the same PAYMENT-SIGNATURE. - HTTP 402 is unpaid only. Do not sign a second authorization because of a 503. - Execution is timeout-bounded and concurrency-capped. - Calculator inputs are stored encrypted for allowlisted operators (Magent Console). They are not in public logs, SSH lookups, catalog, or rollups. Request logs store path without query.