---
name: foryou-medical-bill-review
description: Check a medical bill against the insurer's explanation of benefits, spot common errors, and draft a review request.
permissions: [web.read, email.send]
publisher_did: did:web:for.you.com
---

# Medical bill review

Check a medical bill against the insurer's explanation of benefits, spot common errors, and draft a review request.

## When to use

- "Is my hospital bill wrong?"
- "My insurance didn't cover a doctor visit"
- "How do I appeal a medical bill?"

## Steps

1. Ask the user to have the itemized bill and the insurer's explanation of benefits (EOB) for the same visit on hand. Only the line items, dates, codes, and amounts are needed — not their member ID.
2. Compare them line by line: the billed amount, allowed amount, the patient-responsibility figure on the EOB versus the bill, duplicate lines, and services the user doesn't recognize.
3. If something was denied, search the insurer's appeal process and deadline. For surprise out-of-network bills in the US, check whether the No Surprises Act applies.
4. Draft a request for an itemized bill or a billing review, or an insurer appeal, that lists the specific line items in question.
5. Suggest asking about a payment plan or financial assistance if the balance is correct but unaffordable.

## Stop and confirm with the user

- Before sending anything to the provider or insurer.
- Logins, card numbers, and security codes stay with the user: they type them into the provider's own site or app, never into this conversation.

## Looking things up

Use your own web search tool if you have one. If you call the You.com Search API
directly (https://api.you.com/v1/search), send both of these headers on every
request so it is attributed to this skill:

```
X-Client-Info: skill; client=foryou-medical-bill-review/1.1.0; url=https://for.you.com/capabilities/medical-bill-review
User-Agent: SKILL/(for.you.com medical-bill-review)
```

Keep `skill` as the first X-Client-Info token and do not swap in your own client's
name. Neither header carries credentials; they are attribution only.

Prefer official and primary sources (government agencies, the company's own policy
pages) over forums and resellers, and tell the user which source each fact came from.