Atrial fibrillation · LIVE
ATRIA hemorrhage score
Compute the Fang 2011 ATRIA hemorrhage score from caller-assigned anemia, severe renal disease, age, prior hemorrhage, and hypertension flags.
Markdown: /docs/atria.md · Canonical: https://magentlab.com/docs/atria
Not a medical device. Not a diagnosis, dose, or listing recommendation.
What it computes
Compute the Fang 2011 ATRIA hemorrhage score from caller-assigned anemia, severe renal disease, age, prior hemorrhage, and hypertension flags.
When to use
When an agent needs the published ATRIA AF hemorrhage-risk arithmetic (not HAS-BLED) and must not invent the point total from prose.
When not to use
- Not a diagnosis. magent does not diagnose hemorrhage or atrial fibrillation.
- Not HAS-BLED. This tool is the Fang 2011 ATRIA hemorrhage score only.
- Not a warfarin order. Not a treatment or anticoagulation recommendation.
- magent does not measure hemoglobin or compute eGFR. Anemia (paper: Hb <13 g/dL men or <12 g/dL women) and severe renal disease (paper: eGFR <30 or dialysis) are caller flags.
Formula
ATRIA = anemia (3) + severe_renal_disease (3) + age_ge_75 (2) + prior_hemorrhage (1) + hypertension (1); max 10; 0-3 low, 4 intermediate, 5-10 high
Citation
- Authors
- Fang MC, Go AS, Chang Y, et al.
- Source
- J Am Coll Cardiol. 2011;58(4):395-401
Worked example
Age 60, all flags false
Given:
age=60anemia=falsehypertension=falseprior_hemorrhage=falsesevere_renal_disease=false
- Anemia, severe renal disease, prior hemorrhage, and hypertension false → 0; age 60 is not ≥75 → 0
- Score = 0 (max 10); risk_band low
Anemia plus hypertension is intermediate
Given:
age=60anemia=truehypertension=trueprior_hemorrhage=falsesevere_renal_disease=false
- Anemia → 3; hypertension → 1
- Score = 4 (max 10); risk_band intermediate
Also searched as
- ATRIA score
- ATRIA bleeding score
- Fang ATRIA hemorrhage
- ATRIA warfarin bleed
- AF ATRIA score
- Anticoagulation and Risk Factors in Atrial Fibrillation
Try
Opens the live endpoint. Unpaid browser requests show the paywall; agents should send Accept: application/json.
Full URL: https://api.magentlab.com/api/calc/atria?anemia=false&severe_renal_disease=false&age=60&prior_hemorrhage=false&hypertension=false
Call
Expect HTTP 402 until you retry with PAYMENT-SIGNATURE. Incomplete query params
return HTTP 400 before any quote or charge.
curl -i -H "Accept: application/json" "https://api.magentlab.com/api/calc/atria?anemia=false&severe_renal_disease=false&age=60&prior_hemorrhage=false&hypertension=false"
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
anemia |
boolean | required | Anemia as assigned by the caller (paper: hemoglobin <13 g/dL in men or <12 g/dL in women). true or false. Scores 3. magent does not measure hemoglobin. |
severe_renal_disease |
boolean | required | Severe renal disease as assigned by the caller (paper: eGFR <30 or dialysis). true or false. Scores 3. magent does not compute eGFR. |
age |
integer | required | Age in years (18-120). ≥75 scores 2 (75 scores; 74 does not). |
prior_hemorrhage |
boolean | required | Any prior hemorrhage diagnosis as assigned by the caller. true or false. Scores 1. |
hypertension |
boolean | required | Diagnosed hypertension as assigned by the caller. true or false. Scores 1. |
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.
- 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 (fixture)
{
"items": [
{
"age": "60",
"anemia": "false",
"hypertension": "false",
"prior_hemorrhage": "false",
"severe_renal_disease": "false"
},
{
"age": "60",
"anemia": "false",
"hypertension": "false",
"prior_hemorrhage": "false",
"severe_renal_disease": "false"
}
]
}
Opens a two-item fixture on the API host. Unpaid browsers get the same MetaMask paywall as GET; Pay retries POST with those items.
Example 200 (fixture)
{
"count": 2,
"path": "/api/calc/atria",
"items": [
{
"components": [
{
"factor": "anemia",
"points": 0,
"present": false
},
{
"factor": "severe_renal_disease",
"points": 0,
"present": false
},
{
"value": 60,
"factor": "age_ge_75",
"points": 0,
"present": false
},
{
"factor": "prior_hemorrhage",
"points": 0,
"present": false
},
{
"factor": "hypertension",
"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.",
"age_years": 60,
"citation": {
"authors": "Fang MC, Go AS, Chang Y, et al.",
"doi": "10.1016/j.jacc.2011.03.031",
"id": "fang-2011",
"pmid": "21757117",
"source": "J Am Coll Cardiol. 2011;58(4):395-401",
"title": "A new risk scheme to predict warfarin-associated hemorrhage: the ATRIA (Anticoagulation and Risk Factors in Atrial Fibrillation) Study"
},
"formula": "atria",
"formula_expression": "ATRIA = anemia (3) + severe_renal_disease (3) + age_ge_75 (2) + prior_hemorrhage (1) + hypertension (1); max 10; 0-3 low, 4 intermediate, 5-10 high",
"max_score": 10,
"score": 0,
"risk_band": "low"
},
{
"components": [
{
"factor": "anemia",
"points": 0,
"present": false
},
{
"factor": "severe_renal_disease",
"points": 0,
"present": false
},
{
"value": 60,
"factor": "age_ge_75",
"points": 0,
"present": false
},
{
"factor": "prior_hemorrhage",
"points": 0,
"present": false
},
{
"factor": "hypertension",
"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.",
"age_years": 60,
"citation": {
"authors": "Fang MC, Go AS, Chang Y, et al.",
"doi": "10.1016/j.jacc.2011.03.031",
"id": "fang-2011",
"pmid": "21757117",
"source": "J Am Coll Cardiol. 2011;58(4):395-401",
"title": "A new risk scheme to predict warfarin-associated hemorrhage: the ATRIA (Anticoagulation and Risk Factors in Atrial Fibrillation) Study"
},
"formula": "atria",
"formula_expression": "ATRIA = anemia (3) + severe_renal_disease (3) + age_ge_75 (2) + prior_hemorrhage (1) + hypertension (1); max 10; 0-3 low, 4 intermediate, 5-10 high",
"max_score": 10,
"score": 0,
"risk_band": "low"
}
]
}
Response
| Field | Type | Description |
|---|---|---|
formula |
string | atria |
formula_expression |
string | Exact expression used |
score |
integer | Total points 0-10 |
max_score |
integer | Always 10 |
risk_band |
string | low when score is 0-3; intermediate when 4; high when 5-10. Not a diagnosis. |
age_years |
integer | Age used for the ≥75 criterion |
components |
array | Per-factor points |
citation |
object | Fang 2011 J Am Coll Cardiol citation |
disclaimer |
string | Not-a-device notice |
Example JSON
Machine form of the same example. Frozen fixture. Not a live lookup.
{
"components": [
{
"factor": "anemia",
"points": 0,
"present": false
},
{
"factor": "severe_renal_disease",
"points": 0,
"present": false
},
{
"value": 60,
"factor": "age_ge_75",
"points": 0,
"present": false
},
{
"factor": "prior_hemorrhage",
"points": 0,
"present": false
},
{
"factor": "hypertension",
"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.",
"age_years": 60,
"citation": {
"authors": "Fang MC, Go AS, Chang Y, et al.",
"doi": "10.1016/j.jacc.2011.03.031",
"id": "fang-2011",
"pmid": "21757117",
"source": "J Am Coll Cardiol. 2011;58(4):395-401",
"title": "A new risk scheme to predict warfarin-associated hemorrhage: the ATRIA (Anticoagulation and Risk Factors in Atrial Fibrillation) Study"
},
"formula": "atria",
"formula_expression": "ATRIA = anemia (3) + severe_renal_disease (3) + age_ge_75 (2) + prior_hemorrhage (1) + hypertension (1); max 10; 0-3 low, 4 intermediate, 5-10 high",
"max_score": 10,
"score": 0,
"risk_band": "low"
}
Client errors (HTTP 400)
Invalid params return 400 without charge. Shared HTTP 402 and 503 meanings: Payments.
| HTTP | Code | When |
|---|---|---|
| 400 | invalid_age |
age must be an integer from 18 to 120 Returned before settlement; you are not charged. |
| 400 | invalid_flag |
boolean clinical flags must be true or false Returned before settlement; you are not charged. |
| 400 | invalid_items |
POST body must be a JSON object with only an items array Returned before settlement; you are not charged. |
| 400 | invalid_item_count |
items must be an array of 1 to 25 objects Returned before settlement; you are not charged. |
| 400 | invalid_item |
each items entry must be a JSON object Returned before settlement; you are not charged. |
Related tools
- HAS-BLED — Compute the HAS-BLED bleeding-risk score from discrete clinical flags.
- ORBIT bleeding score — Compute the O'Brien 2015 ORBIT bleeding score from age and caller-assigned anemia, bleeding history, insufficient kidney, and antiplatelet flags.
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. Unpaid valid requests return HTTP 402 with a base64
PAYMENT-REQUIRED
header. HTTP 503 is not a new quote: retry the same PAYMENT-SIGNATURE. Full handshake
and shared payment errors: Payments.
Stdio MCP: /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.