> ## Documentation Index
> Fetch the complete documentation index at: https://docs.locusmedical.fr/llms.txt
> Use this file to discover all available pages before exploring further.

# drug (roadmap)

> Structured medication data (BDPM) — planned, not yet available.

<Warning>
  **Not yet available.** `drug` is designed but not implemented. There is no
  endpoint or MCP tool yet — this page describes the intended behavior so
  integrators can plan. It will appear in the API Reference and `tools/list` only
  once shipped.
</Warning>

<Note>
  **What already exists, elsewhere.** The medication sub-graph (substances,
  products, SmPC sections) is populated and **read by `/v2/retrieve`**: an answer
  carries the drugs prescribed by the rules it cites, in `drugs[]`, with their
  posology. `GET /v2/drugs/rubrics/{id}` returns a section's full text. What is
  still missing, and what this page describes, is the `drug` tool as a
  **directly queryable** surface, without going through a clinical question.
</Note>

## What it will do

`drug` will serve **structured medication data** from the French BDPM database:
indications, interactions, adverse effects, and dosage.

## One tool, sub-resources as a parameter

`drug` will be a **single** tool, not one tool per data type. The kind of data is
a parameter:

| `resource`     | Returns               |
| -------------- | --------------------- |
| `indication`   | Approved indications. |
| `interactions` | Known interactions.   |
| `adverse`      | Adverse effects.      |
| `dosage`       | Posology.             |

## Intended shape (subject to change)

```json theme={null}
// Request
{ "molecules": ["apixaban"], "resource": "interactions" }

// Response — structured data for the requested resource
{ "molecules": ["apixaban"], "resource": "interactions", "items": [ /* ... */ ] }
```

<Note>
  Sources such as BDPM are content behind this tool — not separate tools. The
  exact contract is being designed; this page will be replaced by the live
  reference when `drug` ships.
</Note>