Agent · 100% on-premise · our own reasoner

Pharmacy

Verified, traceable prescription before printing, no errors.

Request demo View the full agent network

What this agent does

Pharmacy is the agent that composes the final prescription before printing or sending it to the patient. It takes the prescription validated by Vademecum, cross-checks the patient’s clinical history, and generates a legally valid document plus a simplified patient information sheet in plain language. All processing runs on the clinic’s local server.

Why it matters

A dental prescription includes dose, schedule, indications, contraindications and warnings. Composing it manually is repetitive and error-prone. Pharmacy automates composition after cross-verification with Vademecum, which has allowed closing the flow with 0 prescription errors reported from production.

How it works

The dentist or Diagnostic Chat requests the prescription. The agent retrieves the latest Vademecum verdict (green/yellow/red) and, if green or yellow with explicit warning, composes: (1) official prescription document with dose and schedule, (2) patient sheet with clear-language instructions, (3) references to specific allergies and precautions. Sub-second latency.

Integration with the clinical workflow

Pharmacy is the final destination of the prescription flow. It receives the green light from Vademecum, context from Diagnostic Chat, and delivers the PDF to the printing module or to outgoing email. If Reception detects a prescription renewal request, Pharmacy prepares it with the same cross-verification.

Autonomous decisions it makes

Compose the prescription only if Vademecum gave green or justified yellow
Block composition on red, with no automatic bypass option
Generate patient sheet in plain language alongside the official document
Log the digitally signed prescription in the clinical history
Send copy to the patient's email if they have consented

Inputs and outputs

Receives

· Vademecum verdict (green/yellow/red)
· Patient clinical history (allergies, pregnancy, age)
· Identification of the prescribing professional
· Delivery channel (print, email, both)

Produces

· Legally valid prescription PDF
· Patient sheet with plain-language instructions
· Digitally signed record in clinical history
· Outgoing email to patient (if authorized)

Production metrics

0 reported

Prescription errors

<1s

Composition latency

100% via Vademecum

Prior verification

Collaborates with

Diagnostic Chat

Vademecum

Inventory Control

Tech stack

Model

Legal templates + LLM patient sheet drafting

Execution

Local on-premise GPU + WeasyPrint PDF

Latency

<1s — synchronous composition

Privacy

PDF generated only on the clinic server

Frequently asked questions

Is the prescription valid at an official pharmacy?+

Yes. The PDF meets the formal requirements of a printed dental prescription (prescriber data, license number, drug with INN, schedule, patient, date, signature). Digital signature is optional per region and can be enabled via configuration.

Can the dentist override a Vademecum block?+

Not automatically. If Vademecum blocked the prescription, Pharmacy requires an explicit human override (no auto-bypass). The dentist can assume the risk via manual signature, but the agent does not hide the risk.

How is the patient sheet delivered to the end user?+

Together with the printed prescription, or via email if the patient consented. It is optional but recommended: it reduces follow-up calls with dosing questions.

Are the PDFs kept in any cloud service?+

No. PDFs are generated and stored on the clinic server, encrypted at file level. The outgoing email does go through SMTP/SendGrid, but only when the patient has explicitly consented.