Agent · 100% on-premise · our own reasoner

Vademecum

AEMPS-sync, interactions, contraindications and dosing in real time.

What this agent does

Vademecum is the pharmacology agent of Dental Brain. It syncs daily with the Spanish drug agency AEMPS and verifies every prescription against interactions, contraindications, allergies and maximum doses, cross-checking the patient’s clinical history. All inference is local on the clinic’s GPU.

Why it matters

A dental prescription poorly cross-checked with the patient’s chronic medication can end in a severe interaction. The manual protocol (paper vademecum, phone call to the pharmacist) introduces latency and errors. Vademecum does it automatically before printing, with the official AEMPS database and full traceability of the decision.

How it works

When the dentist prescribes a drug, the agent takes medication, dose and schedule and cross-checks: (1) official AEMPS sheet, (2) patient chronic medication, (3) declared allergies, (4) status (pregnancy, lactation), (5) age and weight. Returns green / yellow (warning) / red (block). Sub-second latency.

Integration with the clinical workflow

Vademecum receives context from Diagnostic Chat when the conversation leads to prescription. It passes verification to Pharmacy, which composes the final printable prescription. Traceability of each decision is kept in the clinical history.

Autonomous decisions it makes

  • Query the up-to-date official AEMPS sheet before each verification
  • Block prescription when an absolute contraindication is detected
  • Warn with justification when there is a minor or moderate interaction
  • Suggest an equivalent pharmacological alternative when blocking
  • Log traceability of the decision in the patient history

Inputs and outputs

Receives

  • · Proposed medication, dose and schedule
  • · Patient clinical history (chronic medication, allergies)
  • · Patient status (pregnancy, lactation, age, weight)
  • · Context from Diagnostic Chat (when routed)

Produces

  • · Green / yellow / red verdict
  • · List of detected interactions
  • · Suggested pharmacological alternatives (if blocking)
  • · Justification with AEMPS reference

Production metrics

Daily
AEMPS sync
<1s
Verification latency
0 reported
Prescription errors

Tech stack

Model
Rules engine + contextual LLM verification
Execution
Local on-premise GPU + local AEMPS database
Latency
<1s — synchronous verification
Privacy
Clinical history never leaves the server

Frequently asked questions

What happens if AEMPS updates a drug sheet?+
The daily sync incorporates the changes automatically. If a previous prescription becomes contraindicated by the update, the system flags the case for review without altering the original prescription.
Does it cover interactions with non-Spanish medication?+
The main corpus is AEMPS, but the engine also cross-checks international databases (DrugBank, RxNorm) when a patient declares imported medication. Those are marked as secondary source.
Does my clinical history travel to AEMPS for the query?+
No. The AEMPS database is cached locally. Only the drug (not the patient) enters the daily sync query, which is a bulk download without individual queries.
Can I add patient-specific contraindications?+
Yes. The dentist can register specific allergies, intolerances or restrictions in the patient record. Vademecum includes them in every verification.

10 autonomous agents. One brain. Your clinic.

Meet the agents running inside Dental Brain. Each one makes autonomous decisions, on local GPU, with no cloud.