# Diastolic shock index

Diastolic shock index

Status: LIVE
Price: $0.005 USDC
`GET /api/calc/dsi`
HTML: https://magentlab.com/docs/dsi
Markdown: https://magentlab.com/docs/dsi.md

Not a medical device. Not a diagnosis, dose, or listing recommendation.

## What it computes

Compute the Ospina-Tascón diastolic shock index as heart rate in bpm divided by cuff diastolic pressure in mm Hg.

## When to use

When an agent needs the published heart-rate / diastolic-pressure ratio and must not invent a DSI cutoff or copy systolic shock-index bands.

## When not to use

- Not a medical device. Not a diagnosis of shock and not a treatment target.
- Ospina-Tascón 2020 did not include a control group of normal subjects, so recognizing a DSI cutoff to identify abnormality could be misleading.
- This is heart rate divided by diastolic pressure, not the Allgöwer–Burri shock index (HR/SBP).

## Formula

```
dsi = heart_rate_bpm / diastolic_mm_hg
```

## Citation

[Diastolic shock index and clinical outcomes in patients with septic shock.](https://doi.org/10.1186/s13613-020-00658-8)
Ospina-Tascón GA, Teboul JL, Hernandez G, et al.
Ann Intensive Care. 2020;10(1):41
DOI: [10.1186/s13613-020-00658-8](https://doi.org/10.1186/s13613-020-00658-8)

## Worked example

### HR 80, DBP 80

Given: `diastolic_mm_hg=80, heart_rate_bpm=80`

1. dsi = 80 / 80 = 1.00


### HR 120, DBP 80

Given: `diastolic_mm_hg=80, heart_rate_bpm=120`

1. dsi = 120 / 80 = 1.50


## Also searched as

- diastolic shock index
- DSI heart rate DBP
- HR over DBP
- heart rate diastolic ratio
- Ospina-Tascon DSI
- diastolic SI
- HR divided by diastolic

## Parameters

- `heart_rate_bpm` (integer, required): Heart rate in beats per minute (integer 30-220).
- `diastolic_mm_hg` (number, required): Cuff diastolic blood pressure in mm Hg (20-160).

## 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/dsi`
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": [
    {
      "diastolic_mm_hg": "80",
      "heart_rate_bpm": "80"
    },
    {
      "diastolic_mm_hg": "80",
      "heart_rate_bpm": "80"
    }
  ]
}
```

Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/dsi

Example 200:

```json
{
  "count": 2,
  "path": "/api/calc/dsi",
  "items": [
    {
      "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": "Ospina-Tascón GA, Teboul JL, Hernandez G, et al.",
        "doi": "10.1186/s13613-020-00658-8",
        "id": "ospina-tascon-2020",
        "pmid": "32296976",
        "source": "Ann Intensive Care. 2020;10(1):41",
        "title": "Diastolic shock index and clinical outcomes in patients with septic shock."
      },
      "formula": "dsi",
      "formula_expression": "dsi = heart_rate_bpm / diastolic_mm_hg",
      "diastolic_mm_hg": 80.0,
      "heart_rate_bpm": 80,
      "dsi": 1.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": "Ospina-Tascón GA, Teboul JL, Hernandez G, et al.",
        "doi": "10.1186/s13613-020-00658-8",
        "id": "ospina-tascon-2020",
        "pmid": "32296976",
        "source": "Ann Intensive Care. 2020;10(1):41",
        "title": "Diastolic shock index and clinical outcomes in patients with septic shock."
      },
      "formula": "dsi",
      "formula_expression": "dsi = heart_rate_bpm / diastolic_mm_hg",
      "diastolic_mm_hg": 80.0,
      "heart_rate_bpm": 80,
      "dsi": 1.0
    }
  ]
}
```

## Response fields

- `formula` (string): dsi
- `formula_expression` (string): Exact expression used
- `heart_rate_bpm` (integer): Heart rate used, bpm
- `diastolic_mm_hg` (number): Diastolic pressure used, mm Hg
- `dsi` (number): Heart rate divided by diastolic pressure, 2 decimals
- `citation` (object): Ospina-Tascón 2020 citation
- `disclaimer` (string): Not-a-device notice

## Example JSON

Frozen fixture. Not a live lookup.

```json
{
  "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": "Ospina-Tascón GA, Teboul JL, Hernandez G, et al.",
    "doi": "10.1186/s13613-020-00658-8",
    "id": "ospina-tascon-2020",
    "pmid": "32296976",
    "source": "Ann Intensive Care. 2020;10(1):41",
    "title": "Diastolic shock index and clinical outcomes in patients with septic shock."
  },
  "formula": "dsi",
  "formula_expression": "dsi = heart_rate_bpm / diastolic_mm_hg",
  "diastolic_mm_hg": 80.0,
  "heart_rate_bpm": 80,
  "dsi": 1.0
}
```

## Errors

- HTTP 400 `invalid_heart_rate`: heart_rate_bpm must be an integer from 30 to 220 Returned before settlement; you are not charged.
- HTTP 400 `invalid_diastolic_bp`: diastolic_mm_hg must be a number from 20 to 160. 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

- [Shock index](https://magentlab.com/docs/shock-index) — Compute the Allgöwer–Burri shock index as heart rate in bpm divided by cuff systolic pressure in mm Hg.
- [CPO](https://magentlab.com/docs/cpo) — Compute Fincke 2004 cardiac power output in watts from mean arterial pressure and cardiac output.

## 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.