How do I record why a compound was needed?

Compounding reasons record the clinical justification for a compounded preparation — why this patient needed a compound rather than a commercially available product. Attach them per prescription line at order creation using the reasons array. Blend ships a set of global reasons organized as parent categories with subcategories. You can add your own, and nest them under a global parent or one of your own.

See what’s available

curl https://api.byblend.com/api/v1/reasons \
  -H "Authorization: Bearer {access_token}"

Reasons come back as parent categories each containing subcategories — for example “Adherence or Compliance” containing “Behavioral Issues”, alongside standalone categories such as “Palatability”. Filter with type=global or type=customer to separate Blend’s list from your own.

Attach them to an order line

{
  "patient": { "external_id": "clinic-pt-4471" },
  "products": {
    "prescription": [
      {
        "product_code": "HC-RAPA31",
        "quantity": 1,
        "reasons": [
          { "id": "0227d1e5-ba9a-42b5-8fe2-38882aa65708" }
        ]
      }
    ]
  }
}

Reasons attach to the line item, not the order. An order containing three compounded products can carry a different justification for each.

Create your own

curl -X POST https://api.byblend.com/api/v1/reasons \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Physical location",
    "description": "Patient cannot access a physical pharmacy due to natural disaster or similar event.",
    "parent_id": "0227d1e5-ba9a-42b5-8fe2-38882aa65708"
  }'

Both name and description are required. parent_id is optional — supply it to nest the reason under a global category or one of your own, or omit it to create a top-level category.

Give the description real substance. It’s the text that explains the clinical rationale to anyone reviewing the record later, and a vague description makes the reason much less useful than no reason at all.

Prefer an existing global reason over creating a near-duplicate. A short, shared vocabulary reports far better across your whole order history than dozens of one-off custom reasons that mean the same thing.

Custom reasons can be updated later with PUT /api/v1/reasons/{reason_id}.

Get compounding reasons

Global and custom, with subcategories

Create a custom compounding reason

POST /reasons

Update a custom compounding reason

PUT /reasons/reason_id

Create an order

reasons on each prescription line

Guides

Getting started

Prescriptions

Patients

Orders

Prescribers

Products and catalog

Reporting and operations

How do I record why a compound was needed?

See what’s available

Attach them to an order line

Create your own

Get compounding reasons

Create a custom compounding reason

Update a custom compounding reason

Create an order

​See what’s available

​Attach them to an order line

​Create your own

Get compounding reasons

Create a custom compounding reason

Update a custom compounding reason

Create an order

See what’s available

Attach them to an order line

Create your own