Emergency · LIVE

Wisconsin Criteria

Apply the Sitzman 2011 Wisconsin Criteria and return whether any of five caller-assigned maxillofacial trauma findings is present (meets_criteria) and how many (criteria_present 0–5).

LIVE $0.005 USDC GET /api/calc/wisconsin_criteria

Markdown: /docs/wisconsin-criteria.md · Canonical: https://magentlab.com/docs/wisconsin-criteria

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

What it computes

Apply the Sitzman 2011 Wisconsin Criteria and return whether any of five caller-assigned maxillofacial trauma findings is present (meets_criteria) and how many (criteria_present 0–5).

When to use

When an agent has caller-assigned findings after facial trauma and needs the published any-one-of-five Wisconsin Criteria, not NEXUS, PECARN head, or Canadian CT Head.

When not to use

• Not a medical device. Not a diagnosis. magent does not examine the face or assign GCS.
• This tool is the Sitzman 2011 any-one-of-five Wisconsin Criteria only. It is not NEXUS, not PECARN head, and not the Canadian CT Head Rule.
• Each flag is caller-assigned, including GCS < 14 as a boolean. magent does not take a GCS integer.
• Meeting criteria is the published any-one rule. This tool does not classify risk bands or print an imaging order.

Formula

meets_criteria iff bony_stepoff_or_instability or periorbital_swelling_or_contusion or gcs_lt_14 or malocclusion or tooth_absence

Citation

Title

Clinical criteria for obtaining maxillofacial computed tomography in trauma patients

Authors

Sitzman TJ, Hanson SE, Al-Sheikhi N, et al.

Source

Plast Reconstr Surg. 2011;127(3):1270-1278

DOI

10.1097/PRS.0b013e318205f2e0

Worked example

Also searched as

• Wisconsin Criteria
• Sitzman Wisconsin Criteria
• Wisconsin maxillofacial criteria
• Sitzman 2011 facial trauma
• maxillofacial CT criteria
• bony stepoff malocclusion
• Wisconsin facial fracture criteria
• Sitzman trauma criteria

Try

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

/api/calc/wisconsin_criteria?bony_stepoff_or_instability=false&periorbital_swelling_or_contusion=false&gcs_lt_14=false&malocclusion=false&tooth_absence=false

Full URL: https://api.magentlab.com/api/calc/wisconsin_criteria?bony_stepoff_or_instability=false&periorbital_swelling_or_contusion=false&gcs_lt_14=false&malocclusion=false&tooth_absence=false

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/wisconsin_criteria?bony_stepoff_or_instability=false&periorbital_swelling_or_contusion=false&gcs_lt_14=false&malocclusion=false&tooth_absence=false"

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/wisconsin_criteria 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": [
    {
      "bony_stepoff_or_instability": "false",
      "gcs_lt_14": "false",
      "malocclusion": "false",
      "periorbital_swelling_or_contusion": "false",
      "tooth_absence": "false"
    },
    {
      "bony_stepoff_or_instability": "false",
      "gcs_lt_14": "false",
      "malocclusion": "false",
      "periorbital_swelling_or_contusion": "false",
      "tooth_absence": "false"
    }
  ]
}

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/wisconsin_criteria",
  "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": "Sitzman TJ, Hanson SE, Al-Sheikhi N, et al.",
        "doi": "10.1097/PRS.0b013e318205f2e0",
        "id": "sitzman-2011",
        "source": "Plast Reconstr Surg. 2011;127(3):1270-1278",
        "title": "Clinical criteria for obtaining maxillofacial computed tomography in trauma patients"
      },
      "formula": "wisconsin_criteria",
      "formula_expression": "meets_criteria iff bony_stepoff_or_instability or periorbital_swelling_or_contusion or gcs_lt_14 or malocclusion or tooth_absence",
      "meets_criteria": false,
      "criteria_present": 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": "Sitzman TJ, Hanson SE, Al-Sheikhi N, et al.",
        "doi": "10.1097/PRS.0b013e318205f2e0",
        "id": "sitzman-2011",
        "source": "Plast Reconstr Surg. 2011;127(3):1270-1278",
        "title": "Clinical criteria for obtaining maxillofacial computed tomography in trauma patients"
      },
      "formula": "wisconsin_criteria",
      "formula_expression": "meets_criteria iff bony_stepoff_or_instability or periorbital_swelling_or_contusion or gcs_lt_14 or malocclusion or tooth_absence",
      "meets_criteria": false,
      "criteria_present": 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": "Sitzman TJ, Hanson SE, Al-Sheikhi N, et al.",
    "doi": "10.1097/PRS.0b013e318205f2e0",
    "id": "sitzman-2011",
    "source": "Plast Reconstr Surg. 2011;127(3):1270-1278",
    "title": "Clinical criteria for obtaining maxillofacial computed tomography in trauma patients"
  },
  "formula": "wisconsin_criteria",
  "formula_expression": "meets_criteria iff bony_stepoff_or_instability or periorbital_swelling_or_contusion or gcs_lt_14 or malocclusion or tooth_absence",
  "meets_criteria": false,
  "criteria_present": 0
}

Client errors (HTTP 400)

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

Related tools

• NEXUS C-spine — Apply the Hoffman 2000 NEXUS C-spine rule and return whether the five low-risk criteria all hold (imaging not indicated by this rule).
• PECARN pediatric head CT — Apply the Kuppermann 2009 PECARN prediction trees and return high, intermediate, or low risk of clinically important brain injury from caller-assigned findings after pediatric head trauma.
• Canadian CT Head Rule — Apply the Stiell 2001 Canadian CT Head Rule and return whether CT is indicated from caller-assigned high-risk and medium-risk findings after minor blunt head injury.

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.