# PC-PTSD-5 (Prins)

PC-PTSD-5

Status: LIVE
Price: $0.005 USDC
`GET /api/calc/pc_ptsd_5`
HTML: https://magentlab.com/docs/pc-ptsd-5
Markdown: https://magentlab.com/docs/pc-ptsd-5.md

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

## What it computes

Apply the Prins 2016 PC-PTSD-5 trauma-exposure gate and sum five caller-assigned past-month yes/no items (max 5). Return whether the score is at or above that paper's optimally sensitive cut of 3.

## When to use

When an agent has already assigned the Prins 2016 lifetime trauma-exposure flag and five past-month symptom flags and needs the published total and ≥3 sensitive screen, not a PTSD diagnosis or an interview.

## When not to use

- Not a medical device and not a PTSD diagnosis.
- magent does not interview the patient.
- The caller assigns each flag. magent does not interpret individual items.
- If trauma_exposure is false, the five past-month items are not counted (score is 0) even if they are true; they remain required query parameters.
- This is Prins 2016 PC-PTSD-5 only (lifetime trauma-exposure gate and five past-month items; optimally sensitive screen at score ≥ 3). Cuts of 4 (maximized efficiency) and 5 (maximized specificity) are published in that paper and are not the primary flag. magent does not apply later sex-specific cutoffs. Not the DSM-IV four-item PC-PTSD.

## Formula

```
If trauma_exposure is false, PC-PTSD-5 = 0 (five past-month items are required but not counted). If trauma_exposure is true, PC-PTSD-5 = nightmare_or_intrusion + avoidance + hypervigilance_or_startle + numbing_or_detachment + guilt_or_blame; each 1 if true; max 5; at_or_above_sensitive_cutoff iff score ≥ 3 (Prins 2016 optimally sensitive cut; 4 maximized efficiency; 5 maximized specificity)
```

## Citation

[The Primary Care PTSD Screen for DSM-5 (PC-PTSD-5): Development and Evaluation Within a Veteran Primary Care Sample](https://doi.org/10.1007/s11606-016-3703-5)
Prins A, Bovin MJ, Smolenski DJ, Marx BP, Kimerling R, Jenkins-Guarnieri MA, Kaloupek DG, Schnurr PP, Pless Kaiser A, Leyva YE, Tiet QQ
J Gen Intern Med. 2016;31(10):1206-1211
DOI: [10.1007/s11606-016-3703-5](https://doi.org/10.1007/s11606-016-3703-5)

## Worked example

### No trauma exposure

Given: `avoidance=false, guilt_or_blame=false, hypervigilance_or_startle=false, nightmare_or_intrusion=false, numbing_or_detachment=false, trauma_exposure=false`

1. trauma_exposure false: five past-month items are not counted
2. score = 0
3. at_or_above_sensitive_cutoff false (threshold is ≥3)


### Trauma and three past-month items

Given: `avoidance=true, guilt_or_blame=false, hypervigilance_or_startle=true, nightmare_or_intrusion=true, numbing_or_detachment=false, trauma_exposure=true`

1. trauma_exposure true: score = nightmare_or_intrusion + avoidance + hypervigilance_or_startle
2. score = 3
3. at_or_above_sensitive_cutoff true


## Also searched as

- PC-PTSD-5
- Primary Care PTSD Screen for DSM-5
- Prins PC-PTSD-5
- PC-PTSD DSM-5
- primary care PTSD screen
- PC PTSD 5
- Prins 2016 PTSD screen

## Parameters

- `trauma_exposure` (boolean, required): Caller-assigned Prins 2016 lifetime trauma-exposure gate: whether an unusually or especially frightening, horrible, or traumatic event has ever been experienced (examples in that paper include a serious accident or fire, physical or sexual assault or abuse, earthquake or flood, war, seeing someone killed or seriously injured, or a loved one dying by homicide or suicide). true or false. If false, the five past-month items are not counted (score is 0) but remain required. magent does not interview the patient.
- `nightmare_or_intrusion` (boolean, required): In the past month, nightmares about the event(s) or unwanted thoughts of the event(s) (Prins 2016). true or false as assigned by the caller. Counted only when trauma_exposure is true. magent does not interview the patient.
- `avoidance` (boolean, required): In the past month, tried hard not to think about the event(s) or went out of the way to avoid situations that reminded of the event(s) (Prins 2016). true or false as assigned by the caller. Counted only when trauma_exposure is true. magent does not interview the patient.
- `hypervigilance_or_startle` (boolean, required): In the past month, constantly on guard, watchful, or easily startled (Prins 2016). true or false as assigned by the caller. Counted only when trauma_exposure is true. magent does not interview the patient.
- `numbing_or_detachment` (boolean, required): In the past month, felt numb or detached from people, activities, or surroundings (Prins 2016). true or false as assigned by the caller. Counted only when trauma_exposure is true. magent does not interview the patient.
- `guilt_or_blame` (boolean, required): In the past month, felt guilty or unable to stop blaming self or others for the event(s) or problems the event(s) may have caused (Prins 2016). true or false as assigned by the caller. Counted only when trauma_exposure is true. magent does not interview the patient.

## 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/pc_ptsd_5`
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": [
    {
      "avoidance": "false",
      "guilt_or_blame": "false",
      "hypervigilance_or_startle": "false",
      "nightmare_or_intrusion": "false",
      "numbing_or_detachment": "false",
      "trauma_exposure": "false"
    },
    {
      "avoidance": "false",
      "guilt_or_blame": "false",
      "hypervigilance_or_startle": "false",
      "nightmare_or_intrusion": "false",
      "numbing_or_detachment": "false",
      "trauma_exposure": "false"
    }
  ]
}
```

Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/pc-ptsd-5

Example 200:

```json
{
  "count": 2,
  "path": "/api/calc/pc_ptsd_5",
  "items": [
    {
      "components": [
        {
          "factor": "nightmare_or_intrusion",
          "points": 0,
          "present": false
        },
        {
          "factor": "avoidance",
          "points": 0,
          "present": false
        },
        {
          "factor": "hypervigilance_or_startle",
          "points": 0,
          "present": false
        },
        {
          "factor": "numbing_or_detachment",
          "points": 0,
          "present": false
        },
        {
          "factor": "guilt_or_blame",
          "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": "Prins A, Bovin MJ, Smolenski DJ, Marx BP, Kimerling R, Jenkins-Guarnieri MA, Kaloupek DG, Schnurr PP, Pless Kaiser A, Leyva YE, Tiet QQ",
        "doi": "10.1007/s11606-016-3703-5",
        "id": "prins-2016",
        "pmid": "27170304",
        "source": "J Gen Intern Med. 2016;31(10):1206-1211",
        "title": "The Primary Care PTSD Screen for DSM-5 (PC-PTSD-5): Development and Evaluation Within a Veteran Primary Care Sample"
      },
      "formula": "pc_ptsd_5",
      "formula_expression": "If trauma_exposure is false, PC-PTSD-5 = 0 (five past-month items are required but not counted). If trauma_exposure is true, PC-PTSD-5 = nightmare_or_intrusion + avoidance + hypervigilance_or_startle + numbing_or_detachment + guilt_or_blame; each 1 if true; max 5; at_or_above_sensitive_cutoff iff score ≥ 3 (Prins 2016 optimally sensitive cut; 4 maximized efficiency; 5 maximized specificity)",
      "max_score": 5,
      "score": 0,
      "at_or_above_sensitive_cutoff": false,
      "trauma_exposure": false
    },
    {
      "components": [
        {
          "factor": "nightmare_or_intrusion",
          "points": 0,
          "present": false
        },
        {
          "factor": "avoidance",
          "points": 0,
          "present": false
        },
        {
          "factor": "hypervigilance_or_startle",
          "points": 0,
          "present": false
        },
        {
          "factor": "numbing_or_detachment",
          "points": 0,
          "present": false
        },
        {
          "factor": "guilt_or_blame",
          "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": "Prins A, Bovin MJ, Smolenski DJ, Marx BP, Kimerling R, Jenkins-Guarnieri MA, Kaloupek DG, Schnurr PP, Pless Kaiser A, Leyva YE, Tiet QQ",
        "doi": "10.1007/s11606-016-3703-5",
        "id": "prins-2016",
        "pmid": "27170304",
        "source": "J Gen Intern Med. 2016;31(10):1206-1211",
        "title": "The Primary Care PTSD Screen for DSM-5 (PC-PTSD-5): Development and Evaluation Within a Veteran Primary Care Sample"
      },
      "formula": "pc_ptsd_5",
      "formula_expression": "If trauma_exposure is false, PC-PTSD-5 = 0 (five past-month items are required but not counted). If trauma_exposure is true, PC-PTSD-5 = nightmare_or_intrusion + avoidance + hypervigilance_or_startle + numbing_or_detachment + guilt_or_blame; each 1 if true; max 5; at_or_above_sensitive_cutoff iff score ≥ 3 (Prins 2016 optimally sensitive cut; 4 maximized efficiency; 5 maximized specificity)",
      "max_score": 5,
      "score": 0,
      "at_or_above_sensitive_cutoff": false,
      "trauma_exposure": false
    }
  ]
}
```

## Response fields

- `formula` (string): pc_ptsd_5
- `formula_expression` (string): Exact expression used
- `trauma_exposure` (boolean): Prins 2016 lifetime trauma-exposure gate as assigned by the caller. If false, score is 0.
- `score` (integer): PC-PTSD-5 points 0-5
- `max_score` (integer): 5
- `at_or_above_sensitive_cutoff` (boolean): true iff score ≥ 3 (Prins 2016 optimally sensitive cut). That paper also reported 4 maximized efficiency and 5 maximized specificity; those are not the primary flag. Not a PTSD diagnosis.
- `components` (array): Per-item points (weight 0 if no trauma)
- `citation` (object): Prins et al. J Gen Intern Med 2016 citation
- `disclaimer` (string): Not-a-device notice

## Example JSON

Frozen fixture. Not a live lookup.

```json
{
  "components": [
    {
      "factor": "nightmare_or_intrusion",
      "points": 0,
      "present": false
    },
    {
      "factor": "avoidance",
      "points": 0,
      "present": false
    },
    {
      "factor": "hypervigilance_or_startle",
      "points": 0,
      "present": false
    },
    {
      "factor": "numbing_or_detachment",
      "points": 0,
      "present": false
    },
    {
      "factor": "guilt_or_blame",
      "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": "Prins A, Bovin MJ, Smolenski DJ, Marx BP, Kimerling R, Jenkins-Guarnieri MA, Kaloupek DG, Schnurr PP, Pless Kaiser A, Leyva YE, Tiet QQ",
    "doi": "10.1007/s11606-016-3703-5",
    "id": "prins-2016",
    "pmid": "27170304",
    "source": "J Gen Intern Med. 2016;31(10):1206-1211",
    "title": "The Primary Care PTSD Screen for DSM-5 (PC-PTSD-5): Development and Evaluation Within a Veteran Primary Care Sample"
  },
  "formula": "pc_ptsd_5",
  "formula_expression": "If trauma_exposure is false, PC-PTSD-5 = 0 (five past-month items are required but not counted). If trauma_exposure is true, PC-PTSD-5 = nightmare_or_intrusion + avoidance + hypervigilance_or_startle + numbing_or_detachment + guilt_or_blame; each 1 if true; max 5; at_or_above_sensitive_cutoff iff score ≥ 3 (Prins 2016 optimally sensitive cut; 4 maximized efficiency; 5 maximized specificity)",
  "max_score": 5,
  "score": 0,
  "at_or_above_sensitive_cutoff": false,
  "trauma_exposure": false
}
```

## Errors

- HTTP 400 `invalid_pc_ptsd_5`: PC-PTSD-5 inputs must match Prins 2016 trauma exposure and five past-month symptom items from that paper. 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

- [HARK](https://magentlab.com/docs/hark) — Sum the four Sohal 2007 HARK items and return whether one or more answers are affirmative.
- [HITS](https://magentlab.com/docs/hits) — Sum four caller-assigned Sherin 1998 HITS integers (hurt, insult, threaten, scream; each 1-5) and return the published total (4-20) and ≥10 screen.
- [PHQ-9](https://magentlab.com/docs/phq-9) — Sum nine caller-assigned Kroenke 2001 PHQ-9 integers (0-3) and return the published total (max 27), severity cutpoints, and ≥10 screen.

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