# DASH recurrent VTE DASH Status: LIVE Price: $0.005 USDC `GET /api/calc/dash` HTML: https://magentlab.com/docs/dash Markdown: https://magentlab.com/docs/dash.md Not a medical device. Not a diagnosis, dose, or listing recommendation. ## What it computes Compute the Tosetto 2012 DASH score (abnormal D-dimer after stopping anticoagulation, age <50, male sex, hormone use at the initial VTE in women) and return the published recurrence band. ## When to use When an agent needs the published Tosetto 2012 DASH arithmetic after unprovoked VTE and must not invent a duration-of-anticoagulation decision. ## When not to use - Not a medical device. magent does not diagnose recurrent VTE or assay D-dimer. - Not a duration-of-anticoagulation order and not a stop-or-continue anticoagulation protocol. Recurrence bands are published Tosetto 2012 groups, not treatment instructions. - Age scores only when <50 years (Tosetto 2012 abstract). Age 50 does not score. - Hormone use at the initial VTE scores -2 in women only. Male with hormone_use=true is rejected. - Abnormal D-dimer is after stopping anticoagulation as published. Percents are not returned in the JSON body. ## Formula ``` DASH = 2*abnormal_d_dimer + 1*(age<50) + 1*male + (-2)*hormone_use(female only); max 4; recurrence_band <=1 / 2 / >=3 ``` ## Citation [Predicting disease recurrence in patients with previous unprovoked venous thromboembolism: a proposed prediction score (DASH)](https://doi.org/10.1111/j.1538-7836.2012.04735.x) Tosetto A, Iorio A, Marcucci M, et al. J Thromb Haemost. 2012;10(6):1019-1025 DOI: [10.1111/j.1538-7836.2012.04735.x](https://doi.org/10.1111/j.1538-7836.2012.04735.x) ## Worked example ### Age 60 female, no D-dimer, no hormone use Given: `abnormal_d_dimer=false, age=60, hormone_use=false, sex=female` 1. abnormal_d_dimer false → 0; age 60 is not <50 → 0; female → 0; hormone_use false → 0 2. Score = 0 (max 4); recurrence_band <=1 ### Age 40 male with abnormal D-dimer Given: `abnormal_d_dimer=true, age=40, hormone_use=false, sex=male` 1. abnormal_d_dimer → 2; age 40 < 50 → 1; male → 1; hormone_use false → 0 2. Score = 4 (max 4); recurrence_band >=3 ## Also searched as - DASH score - DASH VTE - Tosetto DASH - recurrent VTE DASH - DASH prediction score - unprovoked VTE recurrence ## Parameters - `age` (integer, required): Age in years (18-120). Scores 1 when age is <50 (Tosetto 2012). Age 50 does not score. - `sex` (string, required): female or male. Male scores 1. Hormone use applies only when female. - `abnormal_d_dimer` (boolean, required): Abnormal D-dimer after stopping anticoagulation (Tosetto 2012). true or false. 2 points if true. - `hormone_use` (boolean, required): Hormone use at the initial VTE. Required. Scores -2 only when sex is female and true. Must be false when sex is male. ## 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/dash` 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": [ { "abnormal_d_dimer": "false", "age": "60", "hormone_use": "false", "sex": "female" }, { "abnormal_d_dimer": "false", "age": "60", "hormone_use": "false", "sex": "female" } ] } ``` Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/dash Example 200: ```json { "count": 2, "path": "/api/calc/dash", "items": [ { "components": [ { "factor": "abnormal_d_dimer", "points": 0, "present": false }, { "value": 60, "factor": "age_lt_50", "points": 0, "present": false }, { "factor": "male", "points": 0, "present": false }, { "factor": "hormone_use", "points": 0, "present": false } ], "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": "Tosetto A, Iorio A, Marcucci M, et al.", "doi": "10.1111/j.1538-7836.2012.04735.x", "id": "tosetto-2012", "pmid": "22489957", "source": "J Thromb Haemost. 2012;10(6):1019-1025", "title": "Predicting disease recurrence in patients with previous unprovoked venous thromboembolism: a proposed prediction score (DASH)" }, "formula": "dash", "formula_expression": "DASH = 2*abnormal_d_dimer + 1*(age<50) + 1*male + (-2)*hormone_use(female only); max 4; recurrence_band <=1 / 2 / >=3", "max_score": 4, "score": 0, "age_years": 60, "sex": "female", "recurrence_band": "<=1" }, { "components": [ { "factor": "abnormal_d_dimer", "points": 0, "present": false }, { "value": 60, "factor": "age_lt_50", "points": 0, "present": false }, { "factor": "male", "points": 0, "present": false }, { "factor": "hormone_use", "points": 0, "present": false } ], "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": "Tosetto A, Iorio A, Marcucci M, et al.", "doi": "10.1111/j.1538-7836.2012.04735.x", "id": "tosetto-2012", "pmid": "22489957", "source": "J Thromb Haemost. 2012;10(6):1019-1025", "title": "Predicting disease recurrence in patients with previous unprovoked venous thromboembolism: a proposed prediction score (DASH)" }, "formula": "dash", "formula_expression": "DASH = 2*abnormal_d_dimer + 1*(age<50) + 1*male + (-2)*hormone_use(female only); max 4; recurrence_band <=1 / 2 / >=3", "max_score": 4, "score": 0, "age_years": 60, "sex": "female", "recurrence_band": "<=1" } ] } ``` ## Response fields - `formula` (string): dash - `formula_expression` (string): Exact expression used - `score` (integer): DASH points from -2 to 4 - `max_score` (integer): 4 - `recurrence_band` (string): Tosetto 2012 published annualized-recurrence group: <=1, 2, or >=3. Percents are not returned. Not a stop-or-continue anticoagulation order. - `age_years` (integer): Age used for the <50 criterion - `sex` (string): female or male - `components` (array): Per-factor points - `citation` (object): Tosetto 2012 J Thromb Haemost citation - `disclaimer` (string): Not-a-device notice ## Example JSON Frozen fixture. Not a live lookup. ```json { "components": [ { "factor": "abnormal_d_dimer", "points": 0, "present": false }, { "value": 60, "factor": "age_lt_50", "points": 0, "present": false }, { "factor": "male", "points": 0, "present": false }, { "factor": "hormone_use", "points": 0, "present": false } ], "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": "Tosetto A, Iorio A, Marcucci M, et al.", "doi": "10.1111/j.1538-7836.2012.04735.x", "id": "tosetto-2012", "pmid": "22489957", "source": "J Thromb Haemost. 2012;10(6):1019-1025", "title": "Predicting disease recurrence in patients with previous unprovoked venous thromboembolism: a proposed prediction score (DASH)" }, "formula": "dash", "formula_expression": "DASH = 2*abnormal_d_dimer + 1*(age<50) + 1*male + (-2)*hormone_use(female only); max 4; recurrence_band <=1 / 2 / >=3", "max_score": 4, "score": 0, "age_years": 60, "sex": "female", "recurrence_band": "<=1" } ``` ## Errors - HTTP 400 `invalid_age`: age must be an integer from 18 to 120 Returned before settlement; you are not charged. - HTTP 400 `invalid_sex`: sex must be female or male Returned before settlement; you are not charged. - HTTP 400 `invalid_flag`: boolean clinical flags must be true or false Returned before settlement; you are not charged. - HTTP 400 `invalid_dash_hormone`: hormone_use may be true only when sex is female (Tosetto 2012 DASH). 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 - [Wells PE](https://magentlab.com/docs/wells-pe) — Compute the Wells pulmonary-embolism probability score and return three-tier and two-tier bands. - [Wells DVT](https://magentlab.com/docs/wells-dvt) — Compute the Wells deep-vein thrombosis probability score and return three-tier and two-tier bands. - [YEARS algorithm](https://magentlab.com/docs/years) — Apply the van der Hulle 2017 YEARS algorithm: count three caller-assigned items and return whether PE is excluded at the published D-dimer threshold. ## 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.