Hematology · LIVE

RBC ABO/Rh compatibility (AABB)

Apply AABB Standards for Blood Banks and Transfusion Services Standard 5.14 ABO/Rh compatibility of RBC units from caller-assigned recipient and unit ABO and RhD, and return compatible, abo_compatible, and rhd_compatible.

LIVE $0.005 USDC GET /api/calc/rbc_abo

Markdown: /docs/rbc-abo.md · Canonical: https://magentlab.com/docs/rbc-abo

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

What it computes

Apply AABB Standards for Blood Banks and Transfusion Services Standard 5.14 ABO/Rh compatibility of RBC units from caller-assigned recipient and unit ABO and RhD, and return compatible, abo_compatible, and rhd_compatible.

When to use

When an agent already has caller-assigned recipient and unit ABO group and RhD and needs AABB Standard 5.14 RBC compatibility, and must not invent an emergency RhD-positive-to-negative exception, a plasma or platelet rule, or an antibody-screen formula.

When not to use

• Not a medical device. Not a transfusion order.
• magent does not type blood. recipient_abo, recipient_rhd, unit_abo, and unit_rhd are caller-assigned.
• AABB Standard 5.14 RBC ABO/Rh compatibility only. Does not encode emergency RhD-positive-to-negative exceptions, plasma or platelet compatibility, or antibody-screen units-to-crossmatch formulas.

Formula

compatible iff abo_compatible and rhd_compatible. RBC ABO: unit o → recipient o|a|b|ab; unit a → a|ab; unit b → b|ab; unit ab → ab. RhD: unit negative → recipient negative|positive; unit positive → recipient positive only (AABB Standards 28th ed. Standard 5.14). Not an emergency RhD-positive-to-negative exception. Not plasma or platelets. magent does not type blood

Citation

Title

Standards for Blood Banks and Transfusion Services

Authors

AABB

Source

28th ed. Bethesda, MD: AABB; 2012. Standard 5.14

DOI

none

Worked example

Also searched as

• RBC ABO compatibility
• ABO RhD compatibility
• AABB RBC compatibility
• red cell ABO Rh
• compatible RBC units
• ABO compatible red cells
• RhD compatible RBCs

Try

Opens the live endpoint. Unpaid browser requests show the paywall; agents should send Accept: application/json.

/api/calc/rbc_abo?recipient_abo=o&recipient_rhd=negative&unit_abo=o&unit_rhd=negative

Full URL: https://api.magentlab.com/api/calc/rbc_abo?recipient_abo=o&recipient_rhd=negative&unit_abo=o&unit_rhd=negative

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/rbc_abo?recipient_abo=o&recipient_rhd=negative&unit_abo=o&unit_rhd=negative"

Parameters

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.

POST /api/calc/rbc_abo Max 25 unit_amount + extra_item_amount * (n - 1) extra $0.002 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 (fixture)

{
  "items": [
    {
      "recipient_abo": "o",
      "recipient_rhd": "negative",
      "unit_abo": "o",
      "unit_rhd": "negative"
    },
    {
      "recipient_abo": "o",
      "recipient_rhd": "negative",
      "unit_abo": "o",
      "unit_rhd": "negative"
    }
  ]
}

Open bulk paywall →

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/rbc_abo",
  "items": [
    {
      "compatible": true,
      "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": "AABB",
        "id": "aabb-rbc-abo-compatibility",
        "source": "28th ed. Bethesda, MD: AABB; 2012. Standard 5.14",
        "title": "Standards for Blood Banks and Transfusion Services"
      },
      "formula": "rbc_abo",
      "formula_expression": "compatible iff abo_compatible and rhd_compatible. RBC ABO: unit o → recipient o|a|b|ab; unit a → a|ab; unit b → b|ab; unit ab → ab. RhD: unit negative → recipient negative|positive; unit positive → recipient positive only (AABB Standards 28th ed. Standard 5.14). Not an emergency RhD-positive-to-negative exception. Not plasma or platelets. magent does not type blood",
      "criteria": [
        {
          "factor": "abo_compatible",
          "met": true
        },
        {
          "factor": "rhd_compatible",
          "met": true
        }
      ],
      "abo_compatible": true,
      "recipient_abo": "o",
      "recipient_rhd": "negative",
      "rhd_compatible": true,
      "unit_abo": "o",
      "unit_rhd": "negative"
    },
    {
      "compatible": true,
      "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": "AABB",
        "id": "aabb-rbc-abo-compatibility",
        "source": "28th ed. Bethesda, MD: AABB; 2012. Standard 5.14",
        "title": "Standards for Blood Banks and Transfusion Services"
      },
      "formula": "rbc_abo",
      "formula_expression": "compatible iff abo_compatible and rhd_compatible. RBC ABO: unit o → recipient o|a|b|ab; unit a → a|ab; unit b → b|ab; unit ab → ab. RhD: unit negative → recipient negative|positive; unit positive → recipient positive only (AABB Standards 28th ed. Standard 5.14). Not an emergency RhD-positive-to-negative exception. Not plasma or platelets. magent does not type blood",
      "criteria": [
        {
          "factor": "abo_compatible",
          "met": true
        },
        {
          "factor": "rhd_compatible",
          "met": true
        }
      ],
      "abo_compatible": true,
      "recipient_abo": "o",
      "recipient_rhd": "negative",
      "rhd_compatible": true,
      "unit_abo": "o",
      "unit_rhd": "negative"
    }
  ]
}

Response

Example JSON

Machine form of the same example. Frozen fixture. Not a live lookup.

{
  "compatible": true,
  "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": "AABB",
    "id": "aabb-rbc-abo-compatibility",
    "source": "28th ed. Bethesda, MD: AABB; 2012. Standard 5.14",
    "title": "Standards for Blood Banks and Transfusion Services"
  },
  "formula": "rbc_abo",
  "formula_expression": "compatible iff abo_compatible and rhd_compatible. RBC ABO: unit o → recipient o|a|b|ab; unit a → a|ab; unit b → b|ab; unit ab → ab. RhD: unit negative → recipient negative|positive; unit positive → recipient positive only (AABB Standards 28th ed. Standard 5.14). Not an emergency RhD-positive-to-negative exception. Not plasma or platelets. magent does not type blood",
  "criteria": [
    {
      "factor": "abo_compatible",
      "met": true
    },
    {
      "factor": "rhd_compatible",
      "met": true
    }
  ],
  "abo_compatible": true,
  "recipient_abo": "o",
  "recipient_rhd": "negative",
  "rhd_compatible": true,
  "unit_abo": "o",
  "unit_rhd": "negative"
}

Client errors (HTTP 400)

Invalid params return 400 without charge. Shared HTTP 402 and 503 meanings: Payments.

Related tools

• Plasma starting dose — Compute the BSH Green 2018 starting plasma volume from body weight: 15 mL/kg in the absence of major bleeding. Adult starting dose only.
• Allowable blood loss — Compute Gross 1983 dilution-corrected allowable blood loss from a caller-supplied estimated blood volume and initial versus target hematocrit.

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. HTTP 402 never includes the tool JSON.
• 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.