# predicted CD34+ leukapheresis yield

predicted CD34+ leukapheresis yield

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

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

[Validation of a formula for predicting daily CD34+ cell collection by leukapheresis](https://doi.org/10.3109/14653249.2011.652733)
Rosenbaum ER, O'Connell B, Cottler-Fox M
Cytotherapy. 2012;14(4):461-466
DOI: [10.3109/14653249.2011.652733](https://doi.org/10.3109/14653249.2011.652733)

## Worked example

### 40 CD34/µL, 15 L, 70 kg (clamp illustration, not a paper patient)

Given: `peripheral_cd34_per_ul=40, processed_volume_l=15, weight_kg=70`

1. Rosenbaum 2012 prints the equation and a 30 L LVL cohort, not a numeric worked patient row. These inputs are clamps, not a paper patient.
2. predicted_cd34_e6_per_kg = (40 * 0.30 / 70) * 15 = (12 / 70) * 15 = 2.571... → 2.57


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

## Parameters

- `peripheral_cd34_per_ul` (number, required): Pre-apheresis peripheral blood CD34+ cells per µL (0.1-1000, magent clamp). Rosenbaum 2012 uses this count with the printed 30% efficiency. magent does not assay CD34.
- `processed_volume_l` (number, required): Processed blood volume in liters (1-40, magent clamp). Rosenbaum 2012 validated 30 L large-volume leukapheresis and smaller non-LVL collections. magent does not set a processed volume.
- `weight_kg` (number, optional): Recipient or patient weight in kilograms. Provide weight_kg or weight_lb.
- `weight_lb` (number, optional): Recipient or patient weight in pounds. Converted as kg = lb * 0.45359237.

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

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

Example 200:

```json
{
  "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 fields

- `formula` (string): rosenbaum_2012
- `formula_expression` (string): Exact Rosenbaum 2012 prediction expression
- `peripheral_cd34_per_ul` (number): Pre-apheresis peripheral blood CD34+ cells/µL used
- `processed_volume_l` (number): Processed blood volume in liters used
- `weight_kg` (number): Normalized recipient or patient weight in kg
- `collection_efficiency` (number): Rosenbaum 2012 adjusted collection efficiency (0.30)
- `predicted_cd34_e6_per_kg` (number): Predicted CD34+ yield as ×10^6 cells/kg, 2 decimals
- `citation` (object): Rosenbaum Cytotherapy 2012 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": "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
}
```

## Errors

- HTTP 400 `invalid_pbsc_collection`: Rosenbaum 2012 CD34 yield inputs must match that paper's peripheral CD34 count, processed volume, collection-efficiency term, and recipient weight. Returned before settlement; you are not charged.
- HTTP 400 `invalid_cd34_count`: peripheral_cd34_per_ul must be a positive number in the range printed for Rosenbaum 2012. Returned before settlement; you are not charged.
- HTTP 400 `invalid_processed_volume`: processed_volume_l must be a positive number in the range used by Rosenbaum 2012. Returned before settlement; you are not charged.
- HTTP 400 `invalid_weight`: weight_kg (1-500) or weight_lb (2-1100) is required 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

- [Kaplan plasma volume](https://magentlab.com/docs/tpe) — 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](https://magentlab.com/docs/ganzoni) — Compute the Ganzoni 1970 iron deficit from weight, measured hemoglobin, a caller-supplied target hemoglobin, and depot iron stores.
- [CCI](https://magentlab.com/docs/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](https://magentlab.com/docs/plasma-dosage) — 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.

- 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 of accepted and payload). Magent attaches canonical extensions.bazaar on CDP verify/settle; echoing 402 bazaar is optional.
- 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. 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.
