Infection / VTE · LIVE

Michigan PICC-DVT risk score

Sum the Chopra 2017 Michigan Risk Score factors for PICC-associated thrombosis and return class I–IV with Table 4 observed percents.

LIVE $0.005 USDC GET /api/calc/michigan_picc

Markdown: /docs/michigan-picc.md · Canonical: https://magentlab.com/docs/michigan-picc

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

What it computes

Sum the Chopra 2017 Michigan Risk Score factors for PICC-associated thrombosis and return class I–IV with Table 4 observed percents.

When to use

When an agent needs the published Michigan PICC-DVT point total (not Padua, not IMPROVE) and must not invent a PICC order or lumen count.

When not to use

• Not a medical device and not a diagnosis of PICC-associated thrombosis. magent does not examine the patient; flags are caller-assigned.
• Not a PICC order, insertion, or removal decision.
• magent does not count lumens. Caller assigns single, double, or triple; triple includes quad as published.
• VTE history is one 3-tier field (never / remote / within_30_days). Remote and recent are not added.
• Observed percents are Chopra 2017 Table 4 (class I 0.9%, II 1.6%, III 2.7%, IV 4.7%). Not Padua or IMPROVE.

Formula

Michigan PICC-DVT (Chopra 2017) = other_cvc (1) + (WBC >12 x10^9/L) (1) + active_cancer (2) + picc_lumens (single 0, double 2, triple 3; triple includes quad) + vte_history (never 0, remote 2, within_30_days 3); max 10; class I=0 (observed 0.9%), II=1-2 (1.6%), III=3-4 (2.7%), IV=>4 (4.7% Table 4)

Citation

Title

The Michigan Risk Score to predict peripherally inserted central catheter-associated thrombosis

Authors

Chopra V, Kaatz S, Conlon A, Paje D, Grant PJ, Rogers MAM, Bernstein SJ, Saint S, Flanders SA

Source

J Thromb Haemost. 2017;15(10):1951-1962

DOI

10.1111/jth.13794

Worked example

Also searched as

• Michigan PICC-DVT Risk Score
• Michigan Risk Score
• Chopra PICC thrombosis
• PICC-associated thrombosis
• PICC DVT score
• Chopra 2017
• Michigan PICC score
• PICC thrombosis risk

Try

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

/api/calc/michigan_picc?other_cvc=false&wbc_k_ul=8&active_cancer=false&picc_lumens=single&vte_history=never

Full URL: https://api.magentlab.com/api/calc/michigan_picc?other_cvc=false&wbc_k_ul=8&active_cancer=false&picc_lumens=single&vte_history=never

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/michigan_picc?other_cvc=false&wbc_k_ul=8&active_cancer=false&picc_lumens=single&vte_history=never"

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/michigan_picc 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": [
    {
      "active_cancer": "false",
      "other_cvc": "false",
      "picc_lumens": "single",
      "vte_history": "never",
      "wbc_k_ul": "8"
    },
    {
      "active_cancer": "false",
      "other_cvc": "false",
      "picc_lumens": "single",
      "vte_history": "never",
      "wbc_k_ul": "8"
    }
  ]
}

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/michigan_picc",
  "items": [
    {
      "components": [
        {
          "factor": "other_cvc",
          "points": 0,
          "present": false
        },
        {
          "value": 8.0e3,
          "factor": "wbc_gt_12",
          "points": 0,
          "present": false
        },
        {
          "factor": "active_cancer",
          "points": 0,
          "present": false
        },
        {
          "value": "single",
          "factor": "picc_lumens",
          "points": 0,
          "present": false
        },
        {
          "value": "never",
          "factor": "vte_history",
          "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.",
      "citation": {
        "authors": "Chopra V, Kaatz S, Conlon A, Paje D, Grant PJ, Rogers MAM, Bernstein SJ, Saint S, Flanders SA",
        "doi": "10.1111/jth.13794",
        "id": "chopra-2017",
        "pmid": "28796444",
        "source": "J Thromb Haemost. 2017;15(10):1951-1962",
        "title": "The Michigan Risk Score to predict peripherally inserted central catheter-associated thrombosis"
      },
      "formula": "michigan_picc",
      "formula_expression": "Michigan PICC-DVT (Chopra 2017) = other_cvc (1) + (WBC >12 x10^9/L) (1) + active_cancer (2) + picc_lumens (single 0, double 2, triple 3; triple includes quad) + vte_history (never 0, remote 2, within_30_days 3); max 10; class I=0 (observed 0.9%), II=1-2 (1.6%), III=3-4 (2.7%), IV=>4 (4.7% Table 4)",
      "max_score": 10,
      "score": 0,
      "wbc_ul": 8.0e3,
      "observed_vte_percent": 0.9,
      "picc_lumens": "single",
      "risk_class": "I",
      "vte_history": "never"
    },
    {
      "components": [
        {
          "factor": "other_cvc",
          "points": 0,
          "present": false
        },
        {
          "value": 8.0e3,
          "factor": "wbc_gt_12",
          "points": 0,
          "present": false
        },
        {
          "factor": "active_cancer",
          "points": 0,
          "present": false
        },
        {
          "value": "single",
          "factor": "picc_lumens",
          "points": 0,
          "present": false
        },
        {
          "value": "never",
          "factor": "vte_history",
          "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.",
      "citation": {
        "authors": "Chopra V, Kaatz S, Conlon A, Paje D, Grant PJ, Rogers MAM, Bernstein SJ, Saint S, Flanders SA",
        "doi": "10.1111/jth.13794",
        "id": "chopra-2017",
        "pmid": "28796444",
        "source": "J Thromb Haemost. 2017;15(10):1951-1962",
        "title": "The Michigan Risk Score to predict peripherally inserted central catheter-associated thrombosis"
      },
      "formula": "michigan_picc",
      "formula_expression": "Michigan PICC-DVT (Chopra 2017) = other_cvc (1) + (WBC >12 x10^9/L) (1) + active_cancer (2) + picc_lumens (single 0, double 2, triple 3; triple includes quad) + vte_history (never 0, remote 2, within_30_days 3); max 10; class I=0 (observed 0.9%), II=1-2 (1.6%), III=3-4 (2.7%), IV=>4 (4.7% Table 4)",
      "max_score": 10,
      "score": 0,
      "wbc_ul": 8.0e3,
      "observed_vte_percent": 0.9,
      "picc_lumens": "single",
      "risk_class": "I",
      "vte_history": "never"
    }
  ]
}

Response

Example JSON

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

{
  "components": [
    {
      "factor": "other_cvc",
      "points": 0,
      "present": false
    },
    {
      "value": 8.0e3,
      "factor": "wbc_gt_12",
      "points": 0,
      "present": false
    },
    {
      "factor": "active_cancer",
      "points": 0,
      "present": false
    },
    {
      "value": "single",
      "factor": "picc_lumens",
      "points": 0,
      "present": false
    },
    {
      "value": "never",
      "factor": "vte_history",
      "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.",
  "citation": {
    "authors": "Chopra V, Kaatz S, Conlon A, Paje D, Grant PJ, Rogers MAM, Bernstein SJ, Saint S, Flanders SA",
    "doi": "10.1111/jth.13794",
    "id": "chopra-2017",
    "pmid": "28796444",
    "source": "J Thromb Haemost. 2017;15(10):1951-1962",
    "title": "The Michigan Risk Score to predict peripherally inserted central catheter-associated thrombosis"
  },
  "formula": "michigan_picc",
  "formula_expression": "Michigan PICC-DVT (Chopra 2017) = other_cvc (1) + (WBC >12 x10^9/L) (1) + active_cancer (2) + picc_lumens (single 0, double 2, triple 3; triple includes quad) + vte_history (never 0, remote 2, within_30_days 3); max 10; class I=0 (observed 0.9%), II=1-2 (1.6%), III=3-4 (2.7%), IV=>4 (4.7% Table 4)",
  "max_score": 10,
  "score": 0,
  "wbc_ul": 8.0e3,
  "observed_vte_percent": 0.9,
  "picc_lumens": "single",
  "risk_class": "I",
  "vte_history": "never"
}

Client errors (HTTP 400)

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

Related tools

• Padua score — Compute the Barbar 2010 Padua Prediction Score for VTE risk in hospitalized medical patients from age and ten caller-assigned findings.
• IMPROVE VTE — Compute the Spyropoulos 2011 7-factor associative IMPROVE VTE score during hospitalization from age and six caller-assigned 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. 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.