Hematology · LIVE

Corrected count increment

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.

LIVE $0.005 USDC GET /api/calc/cci

Markdown: /docs/cci.md · Canonical: https://magentlab.com/docs/cci

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

What it computes

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.

When to use

When an agent already has pre and post platelet counts, BSA, and the transfused dose in 10^11 and needs the published CCI arithmetic, not a refractoriness cutoff, a transfusion order, a platelet assay, or Nadler BSA from height and weight.

When not to use

• Not a medical device and not a transfusion order. magent does not assay platelets or measure BSA.
• bsa_m2 is caller-supplied. magent does not compute Nadler BSA from height and weight; that is a different tool.
• Does not emit a refractoriness cutoff. Published 5000 versus 7500 thresholds disagree; Davis 1999 argues against CCI as a study outcome.
• Davis 1999 cautions that CCI and percent platelet recovery (PPR) can distort comparisons of platelet products.
• Not the Charlson comorbidity index.

Formula

cci = (post_plt_per_ul - pre_plt_per_ul) * bsa_m2 / platelets_transfused_e11

Citation

Title

Corrected count increment and percent platelet recovery as measures of posttransfusion platelet response: problems and a solution

Authors

Davis KB, Slichter SJ, Corash L

Source

Transfusion. 1999;39(6):586-592

DOI

10.1046/j.1537-2995.1999.39060586.x

Worked example

Also searched as

• corrected count increment
• CCI platelet transfusion
• platelet CCI
• posttransfusion platelet increment
• Davis CCI
• corrected platelet increment
• platelet transfusion increment
• count increment CCI

Try

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

/api/calc/cci?pre_plt_per_ul=10000&post_plt_per_ul=30000&bsa_m2=1.8&platelets_transfused_e11=3

Full URL: https://api.magentlab.com/api/calc/cci?pre_plt_per_ul=10000&post_plt_per_ul=30000&bsa_m2=1.8&platelets_transfused_e11=3

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/cci?pre_plt_per_ul=10000&post_plt_per_ul=30000&bsa_m2=1.8&platelets_transfused_e11=3"

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/cci 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": [
    {
      "bsa_m2": "1.8",
      "platelets_transfused_e11": "3",
      "post_plt_per_ul": "30000",
      "pre_plt_per_ul": "10000"
    },
    {
      "bsa_m2": "1.8",
      "platelets_transfused_e11": "3",
      "post_plt_per_ul": "30000",
      "pre_plt_per_ul": "10000"
    }
  ]
}

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/cci",
  "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": "Davis KB, Slichter SJ, Corash L",
        "doi": "10.1046/j.1537-2995.1999.39060586.x",
        "id": "davis-1999",
        "pmid": "10354261",
        "source": "Transfusion. 1999;39(6):586-592",
        "title": "Corrected count increment and percent platelet recovery as measures of posttransfusion platelet response: problems and a solution"
      },
      "formula": "cci",
      "formula_expression": "cci = (post_plt_per_ul - pre_plt_per_ul) * bsa_m2 / platelets_transfused_e11",
      "bsa_m2": 1.8,
      "cci": 1.2e4,
      "increment_per_ul": 2.0e4,
      "platelets_transfused_e11": 3.0,
      "post_plt_per_ul": 3.0e4,
      "pre_plt_per_ul": 1.0e4
    },
    {
      "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": "Davis KB, Slichter SJ, Corash L",
        "doi": "10.1046/j.1537-2995.1999.39060586.x",
        "id": "davis-1999",
        "pmid": "10354261",
        "source": "Transfusion. 1999;39(6):586-592",
        "title": "Corrected count increment and percent platelet recovery as measures of posttransfusion platelet response: problems and a solution"
      },
      "formula": "cci",
      "formula_expression": "cci = (post_plt_per_ul - pre_plt_per_ul) * bsa_m2 / platelets_transfused_e11",
      "bsa_m2": 1.8,
      "cci": 1.2e4,
      "increment_per_ul": 2.0e4,
      "platelets_transfused_e11": 3.0,
      "post_plt_per_ul": 3.0e4,
      "pre_plt_per_ul": 1.0e4
    }
  ]
}

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": "Davis KB, Slichter SJ, Corash L",
    "doi": "10.1046/j.1537-2995.1999.39060586.x",
    "id": "davis-1999",
    "pmid": "10354261",
    "source": "Transfusion. 1999;39(6):586-592",
    "title": "Corrected count increment and percent platelet recovery as measures of posttransfusion platelet response: problems and a solution"
  },
  "formula": "cci",
  "formula_expression": "cci = (post_plt_per_ul - pre_plt_per_ul) * bsa_m2 / platelets_transfused_e11",
  "bsa_m2": 1.8,
  "cci": 1.2e4,
  "increment_per_ul": 2.0e4,
  "platelets_transfused_e11": 3.0,
  "post_plt_per_ul": 3.0e4,
  "pre_plt_per_ul": 1.0e4
}

Client errors (HTTP 400)

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

Related tools

• 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.