TRUST

Invisible in the workflow. Visible in the log.

A licensed pharmacist gates every action on the fill path. Every model runs on the pharmacy's own hardware, so prescription images, cards, and claims never leave the building. Controlled substances stay out of automation entirely. And every write is read back before it counts.

COMMITMENTS

Four commitments, designed in — not bolted on.

None of these are policy paragraphs you have to take on faith. Each is a decision baked into how the system is built, so it holds whether or not anyone is watching.

01 / 04

The pharmacist gate

A licensed pharmacist is a hard gate on every action on the fill path. The agent perceives, reasons, and stages; the human signs. Nothing moves without them.

PHARMACIST SIGNED

This is the one place a person — not the machine — has the final say.

02 / 04

Edge-only PHI

Every model runs on the pharmacy's own hardware. Prescription images, cards, IDs, and claims never leave the building for a third-party AI cloud. HIPAA posture is architectural, not a policy paragraph.

03 / 04

Controlled substances excluded

Controlled substances are excluded from every automated workflow — no auto-typing, no automated perpetual count, no automated ordering. 222/CSOS stays manual. A design decision, not a limitation to relax later.

04 / 04

Verified writes, honest reads

Every write is read back and compared before it counts. Every action lands in an append-only log — the same trail that becomes the audit-defense evidence.

Read together: the machine does the work, and a licensed human owns the outcome.

Operating authority

SSVP runs under the pharmacy's own PrimeRx license and user account, performing actions the pharmacy's own staff are entitled to perform, at the pharmacy's direction. Staff are trained on it; the owner and pharmacist-in-charge control it; the append-only log makes every action attributable after the fact.
Headless — not hidden from the people accountable.

RISK REGISTER

Five ways this could go wrong. Five brakes.

Every automation carries risk. Here is the honest list of what could fail — and exactly what stops it from reaching a patient or a claim.

Mitigation

Versioned UIA maps per build, canary checks, auto-halt to manual — the pharmacy is never worse off than before install.

Mitigation

Confidence scoring, mandatory human verification on the fill path, field-level provenance.

Mitigation

Versioned + dated KB, audit_outcome flags rules that stopped winning, re-verification before production changes.

Mitigation

Pharmacist sign-off, controlled-substance exclusion, edge-only PHI, a complete action trail — built to be shown to a board of pharmacy, not hidden from one.

Mitigation

Net-against-in-transit, pack-size rounding, per-line reason codes, owner approval before transmission.

PLATFORM

Every model on your hardware.

The whole stack runs on the pharmacy's own machines. Nothing about a patient leaves the building to make the software work.

OCR: PaddleOCR · Surya
Vision-language: Qwen2.5-VL · MiniCPM-V · InternVL2
Language reasoning: Ollama · llama.cpp (quantized, local)
UI automation: FlaUI
Overlay shell: Electron · .NET Windows-native
Data spine: PostgreSQL · pgvector

Business Associate Agreement

Because every model runs on-premise, no prescription image, insurance card, or claim is ever sent to a third-party AI cloud — there is no external model provider handling your patients' data, and nothing to intercept in transit. Where SSVP HOLDING LLC would qualify as a business associate under HIPAA, a Business Associate Agreement is executed before go-live.

Built to be shown to a board of pharmacy, not hidden from one.