Pharmacist
Licensed PharmD, still practicing. Verification, counseling, immunizations — and the thousand small failures of pharmacy software witnessed firsthand, daily.
1 · Indications and usage
Indicated wherever medicine meets software.
Neima designs and builds healthcare applications end-to-end — from the first wireframe to the production deploy, as one person. A decade behind the pharmacy counter means the software starts from the workflow, not the other way around.
Also indicated for: independent pharmacies drowning in phone calls, clinicians tolerating decades-old tooling, and health-tech teams who need someone fluent in both HL7 and HTTP.
Limitations of use. Not indicated for engagement metrics, dark patterns, or software that treats clinicians as data-entry clerks.
2 · Dosage and administration
Titrate scope to workflow. Ship at steady state.
SIG · PO ONCE
Full product build
An app designed, engineered, and deployed end-to-end — from clinical logic to the pixel. Best taken when the workflow is understood and the vendor is not.
SIG · QW MAINTENANCE
Embedded pharmacist-engineer
Ongoing product work inside your team — a clinician in the repo, a maintenance dose of judgment where health-tech decisions get made.
SIG · STAT
Rescue mission
For legacy systems in acute distress. Stabilize the workflow, replace the failing component, discharge with better software.
3 · Mechanism of action
Dual-binding affinity: the clinic and the terminal.
Most builders of healthcare software have never verified a prescription at 6 pm on a Friday. Neima has — thousands of times — and then went home and built the software he wished existed. The mechanism is simple and rarely replicated: both binding sites, one molecule.
Engineer
TypeScript, Swift, Python. HIPAA-first architecture, self-hosted infrastructure, native apps over wrappers. Designs it, builds it, ships it — alone.
4 · Clinical applications
In production. In pharmacies. In use.
APP-001
RefillCalls
The pharmacy phone line, automated. Refill requests captured,
transcribed, and queued around the clock — while the pharmacist stays with the
patient in front of them.
● LIVE
APP-002
Pharmacy Ops
Internal tooling for the daily grind of an independent
pharmacy — workflow, tracking, and the paperwork nobody will miss.
● LIVE
APP-003
Client Studios
Bespoke sites and native apps for practices and small
businesses — designed, built, and hosted end-to-end.
◐ ONGOING
5 · Pharmacokinetics
Absorption was slow. Retention is complete.
Absorption
Pharmacy school
Doctor of Pharmacy. Pharmacology, therapeutics, and a durable suspicion of anything that interrupts patient care.
Distribution
The counter
A decade of verification queues, insurance rejections, and software that fights the clinician at every click.
Metabolism
The keyboard
Frustration converted into TypeScript, Swift, and Python. First tools, then apps, then pharmacies running on them.
Elimination
None observed
The pharmacist never left the building. Every product still starts at the counter, with the workflow.
6 · Clinical studies
Study RXC-01: the phone stopped ringing.
An open-label, real-world deployment of RefillCalls in an independent pharmacy. No placebo arm was ethical — the control condition was hold music. Enrollment ongoing.
| Endpoint | Result |
|---|---|
| Primary — refill requests captured without a human on the line | ● Met — the queue fills itself, around the clock |
| Secondary — pharmacist attention returned to patients | ● Met — measured in uninterrupted counseling |
| Exploratory — staff opinion of the previous phone workflow | Unprintable; collected verbatim |
7 · Adverse reactions
Commonly reported, rarely regretted.
- Very common (≥10%)
- Fewer phone calls. Refills that queue themselves. Staff asking “can it also do…?”
- Common (1–10%)
- Workflow satisfaction. Sudden intolerance of the previous vendor.
- Rare (<1%)
- Feature requests at dinner parties.
To report a suspected reaction — or request one — contact neima@nakhaee.us.
8 · Warnings and precautions
Read before co-administering.
Electron wrappers. On Apple platforms, NEIMA exhibits strong preference for native SwiftUI over web-view wrappers. Co-administration may result in a rewrite.
Surrendered data. Contraindicated. Infrastructure is self-hosted by default; patient data stays where it belongs.
Switching from legacy vendors. Patients may experience abrupt relief. Taper is not required.
9 · How supplied / contact
Take one conversation, by email, as needed.
neima@nakhaee.usSupplied as: one pharmacist-engineer, full-stack, self-hosted. Response within one business day. No prior authorization required.
Human-verified · No refills required