Hematology · LIVE

predicted CD34+ leukapheresis yield

Compute Rosenbaum 2012 predicted daily CD34+ yield (×10^6 per kg) from pre-apheresis peripheral blood CD34+ cells/µL, processed blood volume, and recipient or patient weight, using that paper's adjusted collection efficiency of 30%.

LIVE $0.005 USDC GET /api/calc/pbsc_collection

Markdown: /docs/pbsc-collection.md · Canonical: https://magentlab.com/docs/pbsc-collection

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

What it computes

Compute Rosenbaum 2012 predicted daily CD34+ yield (×10^6 per kg) from pre-apheresis peripheral blood CD34+ cells/µL, processed blood volume, and recipient or patient weight, using that paper's adjusted collection efficiency of 30%.

When to use

When an agent needs the published Rosenbaum 2012 prediction and must not invent a collection-efficiency term, write an apheresis order, or run a collection.

When not to use

• Not a medical device. magent does not run the collection, write an apheresis order, choose a machine protocol, or set a collection goal.
• Uses only the Rosenbaum 2012 adjusted collection efficiency of 30%. Later papers that substitute a different constant are not this tool.
• CD34, processed-volume, and weight clamps are fail-closed magent ranges (positive, clinically plausible). Rosenbaum 2012 does not print those input bands.
• Not Kaplan plasma volume, Ganzoni iron deficit, CCI, or a plasma dose.

Formula

predicted_cd34_e6_per_kg = (peripheral_cd34_per_ul * 0.30 / weight_kg) * processed_volume_l

Citation

Title

Validation of a formula for predicting daily CD34+ cell collection by leukapheresis

Authors

Rosenbaum ER, O'Connell B, Cottler-Fox M

Source

Cytotherapy. 2012;14(4):461-466

DOI

10.3109/14653249.2011.652733

Worked example

Also searched as

• predicted CD34+ leukapheresis yield
• Rosenbaum CD34 collection
• peripheral blood stem cell yield
• CD34 cells per kg
• leukapheresis yield
• PBSC collection prediction
• daily CD34 collection
• predicted CD34 yield

Try

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

/api/calc/pbsc_collection?peripheral_cd34_per_ul=40&processed_volume_l=15&weight_kg=70

Full URL: https://api.magentlab.com/api/calc/pbsc_collection?peripheral_cd34_per_ul=40&processed_volume_l=15&weight_kg=70

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/pbsc_collection?peripheral_cd34_per_ul=40&processed_volume_l=15&weight_kg=70"

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/pbsc_collection 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": [
    {
      "peripheral_cd34_per_ul": "40",
      "processed_volume_l": "15",
      "weight_kg": "70"
    },
    {
      "peripheral_cd34_per_ul": "40",
      "processed_volume_l": "15",
      "weight_kg": "70"
    }
  ]
}

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/pbsc_collection",
  "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": "Rosenbaum ER, O'Connell B, Cottler-Fox M",
        "doi": "10.3109/14653249.2011.652733",
        "id": "rosenbaum-2012",
        "pmid": "22277012",
        "source": "Cytotherapy. 2012;14(4):461-466",
        "title": "Validation of a formula for predicting daily CD34+ cell collection by leukapheresis"
      },
      "formula": "rosenbaum_2012",
      "formula_expression": "predicted_cd34_e6_per_kg = (peripheral_cd34_per_ul * 0.30 / weight_kg) * processed_volume_l",
      "weight_kg": 70.0,
      "collection_efficiency": 0.3,
      "peripheral_cd34_per_ul": 40.0,
      "predicted_cd34_e6_per_kg": 2.57,
      "processed_volume_l": 15.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": "Rosenbaum ER, O'Connell B, Cottler-Fox M",
        "doi": "10.3109/14653249.2011.652733",
        "id": "rosenbaum-2012",
        "pmid": "22277012",
        "source": "Cytotherapy. 2012;14(4):461-466",
        "title": "Validation of a formula for predicting daily CD34+ cell collection by leukapheresis"
      },
      "formula": "rosenbaum_2012",
      "formula_expression": "predicted_cd34_e6_per_kg = (peripheral_cd34_per_ul * 0.30 / weight_kg) * processed_volume_l",
      "weight_kg": 70.0,
      "collection_efficiency": 0.3,
      "peripheral_cd34_per_ul": 40.0,
      "predicted_cd34_e6_per_kg": 2.57,
      "processed_volume_l": 15.0
    }
  ]
}

Response

Example JSON

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

{
  "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": "Rosenbaum ER, O'Connell B, Cottler-Fox M",
    "doi": "10.3109/14653249.2011.652733",
    "id": "rosenbaum-2012",
    "pmid": "22277012",
    "source": "Cytotherapy. 2012;14(4):461-466",
    "title": "Validation of a formula for predicting daily CD34+ cell collection by leukapheresis"
  },
  "formula": "rosenbaum_2012",
  "formula_expression": "predicted_cd34_e6_per_kg = (peripheral_cd34_per_ul * 0.30 / weight_kg) * processed_volume_l",
  "weight_kg": 70.0,
  "collection_efficiency": 0.3,
  "peripheral_cd34_per_ul": 40.0,
  "predicted_cd34_e6_per_kg": 2.57,
  "processed_volume_l": 15.0
}

Client errors (HTTP 400)

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

Related tools

• Kaplan plasma volume — Compute Kaplan 1990 estimated plasma volume for therapeutic plasma exchange from weight and hematocrit as a percent, returning one plasma volume in liters and milliliters.
• Ganzoni iron deficit — Compute the Ganzoni 1970 iron deficit from weight, measured hemoglobin, a caller-supplied target hemoglobin, and depot iron stores.
• CCI — Compute the conventional corrected count increment after platelet transfusion from pre and post platelet counts per µL, caller-supplied BSA, and dose in units of 10^11.
• 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.

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.