AI in Healthcare.
The Rx Intake Bot is a digital technician that reads every prescription that arrives by fax, e-Rx, portal or PDF and types it into the pharmacy management system you already run, as a pending record. Your technician confirms it. Your pharmacist verifies it.
Built by pharmacists and engineers, and tested inside our own FDA-registered compounding facility before it reaches a partner pharmacy.
Clinically reviewed by Dr. Farah Thawer, PharmD · September 2026
Nothing happens to a script until someone has entered it. Volume goes up. Typing capacity does not. Every pharmacy has the same first job: get the prescription into the system so a pharmacist can look at it — and today that job is done by hand, between phone calls, by the person you can least afford to lose.
Every extra 250 scripts a day is another hire. The queue only moves as fast as the person typing it, between phone calls, at the counter.
Source: published data-entry technician job quotas, 2026Three quarters of those entries were made by technicians — the step before any pharmacist sees the script. Fix intake, and you fix the largest single source of error in the building.
The person doing intake is the person you can least afford to lose — and the most expensive to replace. A digital technician does not resign, and the second one costs less than the first.
Source: ASHPPrescription intake, done by a bot on the system you already run. It reads the way a person reads, types through the same screens your staff use — no API, no new system — and stops the moment anything is unclear. Four ways a prescription reaches a pharmacy; the bot takes all four from the queue they land in. Genuine paper still has to be scanned by a person; we do not remove that step.
Illustrative walkthrough with sample data. No patient information appears on this page.
These are not policy settings. They are built in — a pharmacy cannot switch them off, and neither can we.
or any clinical warning your system raises — those wait for a pharmacist, always.
below its confidence threshold, it holds the prescription and asks a person.
a missing field stays missing, and stays flagged.
those go to the pharmacist, always.
it saves the record as pending and stops.
one action stops it, from any workstation.
The Rx Intake Bot is the product. Everything else is sold only after it is live — the same engine pointed at the next queue.
Reads every prescription that arrives by fax, e-Rx, portal or PDF, matches it to your patient, prescriber and drug files, and types it into your system as a pending record. Compounds matched to your own formulary. Anything uncertain is held.
Compounding pharmacies (503A and 503B), independent retail pharmacies, and Canadian pharmacies on Kroll and the other Canadian systems.
The only one that touches the prescription record.
The same engine pointed at a second queue you name: refill automation, cycle fills, med-sync, rejected claims and prior-authorization drafts, order entry, month-end reports.
Pharmacies already running the Intake Bot.
A custom task, scoped per pharmacy. Sold second, never first.
A branded ordering page on your own website for the prescribers who send you scripts: pick the patient, pick from your catalogue, submit. Each prescriber sees their own catalogue. The script arrives as data, so the bot files it without reading a fax at all.
Compounders first; any pharmacy with 20 or more regular prescribers.
For the doctors, not your staff. Included with the Intake Bot.
A voice-and-text agent for the pharmacy’s phones: fill status, pickup, hours, price as already computed, refill requests taken into the queue. The call-center workload, without the call center. Dosing, side effects, complaints, recalls and any change to a prescription go to a person, every time.
Any pharmacy where the phone interrupts the bench.
Patient-facing. Never touches the record.
In Canada there is no e-prescribing network, so the Canada Intake Bot is the Full bot’s fax-and-portal job from day one.
| Capability | Standard Intake Bot | Full Intake Bot | Workflow Bot |
|---|---|---|---|
| Reads e-scripts arriving as data | ✓ | ✓ | – |
| Reads faxes and scanned images (vision) | – | ✓ | – |
| Reads handwriting | – | ✓ | – |
| Reads portal and PDF submissions | – | ✓ | – |
| Multi-ingredient compounds, matched to your formulary | – | ✓ | – |
| Matches patient, prescriber and drug to your files | ✓ | ✓ | ✓ |
| Profile check: same drug, same dose, early refill | ✓ | ✓ | ✓ |
| Saves as PENDING; holds anything uncertain | ✓ | ✓ | ✓ |
| Refill queue, cycle fills, med-sync | – | – | ✓ |
| Rejected claims turned into a prior-auth draft | – | draft only | ✓ |
| Order entry and month-end reports | – | – | ✓ |
| Adjudicates, bills, clears DUR alerts, controlled substances | ✕ | ✕ | ✕ |
| Dedicated support | 10 h a month | 10 h a month | |
| One bot covers | 300–500 a day* | 300–500 a day* | one queue |
*For data-entry-only work with no adjudication, such as on Kroll in Canada, one bot can cover up to 700–800 scripts a day.
Compounds arrive by fax and portal, several ingredients on one line. The bot reads each ingredient, matches it to your formulary and calculates the masses. A median 503A dispenses about 350 compounded scripts a week for 150 prescribers (APC 2025–26).
A typical independent fills 67,601 scripts a year (NCPA 2025 Digest). Most arrive as e-scripts, but every one still has to be matched, filled in and checked by a person. The Standard bot works that queue; the Full bot reads the faxes and PDFs too.
Canada has no e-prescribing network, so scripts arrive by fax and a person types every one. Kroll is the most widely deployed pharmacy system in Canada, so one screen profile covers most of the market. Our first Kroll build is under way with an independent pharmacy in Alberta.
Do not see your system? Adding one is a screen profile plus a test pass on your own scripts. Days, not months, and no API needed from the vendor.
What we can show today — real deployments, no invented numbers. Shadow-mode reports on your own scripts are the proof we offer every pharmacy.
An FDA-registered 503B outsourcing facility in Albany, New York, supplying sterile medications to ORs, ICUs and hospital pharmacies. The Rx Intake Bot is built and proven on Galaxy’s live compounding intake before it reaches any partner pharmacy.
Our first Kroll build, under way with an independent Canadian pharmacy: fax and portal prescriptions read and typed into Kroll as pending records — shadow mode on their live queue first, exactly as we offer every pharmacy.
A fixed monthly cost per bot, never per script. “From” prices, confirmed in writing before any work starts. Billed in phases as the bot takes on more scope, so what you pay follows the work it has actually taken over.
| Line | What is included | From, per month | Set-up |
|---|---|---|---|
| Rx Intake Bot · Standard | e-Rx queue only: match, fill in, check; standard medications; email support | $925 | none |
| Rx Intake Bot · Full | Adds fax, PDF, handwriting, compounds, prior-auth drafts; 10 h dedicated support a month | $2,250 | $3,000 once |
| Workflow Bot | A second queue, scoped with you | $2,250 | waived if intake is live |
| Prescriber Portal | Your branded prescribing page | included · $189 alone | none |
| Voice & Text Agent | Calls and texts, any hour | ask us | – |
| Line | What is included | From, per month | Set-up |
|---|---|---|---|
| Rx Intake Bot · Canada | Fax, portal and PDF intake, handwriting, compounds; 10 h dedicated support a month | C$1,095 | C$650 once |
| Workflow Bot | A second queue, scoped with you | C$1,095 | waived if intake is live |
| Prescriber Portal | Your branded prescribing page | included · C$249 alone | none |
| Voice & Text Agent | Calls and texts, any hour | ask us | – |
One bot is one virtual worker on one machine: 300 to 500 scripts a day on most systems, or up to 700–800 a day for data-entry-only work such as Kroll in Canada. A pharmacy above that adds a second bot at 20% less.
We do not claim an accuracy number. Shadow mode measures yours.
The bot runs on your live intake for a week and enters nothing.
What it would have entered sits next to what your staff entered, script by script.
If it clears the bar you set, it goes live, supervised. If not, you have spent a week of our time, not yours.
Three to seven weeks to live
A dedicated machine, used by nothing but the bot: a desktop at the counter (one bot per machine, monitor attached), or a virtual machine on your server or in Azure/AWS — several bots per server, no extra hardware. We recommend the VM.
Windows 10 Pro / 11, Windows Server 2016 or newer, or Ubuntu LTS · 4 cores · 8 GB RAM (16 GB for older systems) · 25–50 GB free SSD · 1920×1080 display · your pharmacy system installed and working on it · outbound internet. From us: a named technician-level login for the bot, and a signed BAA.
What is in place from day one.
No data warehouse of ours. Telemetry is counters and error codes only.
Signed before anything starts. PIPEDA-aligned privacy agreement for Canadian pharmacies.
The vision model reads; it does not train on your patients. Your data never trains a public model.
Technician role, minimum permissions. Every action attributable in your own audit log.
Who, what, when, confidence, result. Screen recording of every session.
Screen profiles are tested on your scripts before shadow mode, and re-tested after every change to your system.
TEKHQS builds the software: 250 to 300 engineers in Lake Forest, California. Galaxy Pharmaceuticals, our own FDA-registered 503B in Albany, New York, is the pharmacy it is tested in. Together they are TEKHQS AI.
Owns and runs the licensed 503B this is built in.
Ran operations across 20 pharmacies on Kroll. Trained more than 10,000 pharmacists. Clinical reviewer of this page.
Regulated manufacturing and cGMP process.
Twenty-plus years in regulated healthcare businesses.
Builds the digital technicians: intake, documents, the vision layer.
No. It works through the same screens your staff use, on a dedicated machine with your pharmacy system installed and its own login. Nothing is exported and your software vendor does not need to be involved.
It holds the prescription, pings a person, and attaches the original document. It never guesses a drug, strength or sig, and it never fills a blank to make a form validate. Every held item stays on a list your team can see.
The bot runs inside your pharmacy, no patient data leaves the site, and a Business Associate Agreement is signed before anything starts. It has its own named login so every action is in your audit log under its name. For Canadian pharmacies we sign a PIPEDA-aligned privacy agreement.
Any Windows-based system we have a screen profile for: LifeFile, Pharmetika, PK Software, PioneerRx, Liberty, BestRx, PrimeRx, Rx30, QS/1, Computer-Rx, EnterpriseRx and DigitalRx in the US; Kroll, Propel Rx, PharmaClik Rx, Fillware, WinRx, Assyst Rx-A and Nexxsys in Canada. Adding a system is one screen profile plus a test pass on your own scripts.
One bot is one virtual worker on one machine. That is about 300 to 500 scripts a day on most systems, or up to 700 to 800 a day for data-entry-only work with no adjudication, such as on Kroll in Canada. A pharmacy above that adds a second bot, which runs on a virtual machine on the same server.
A fixed monthly cost per bot, never per script, starting at $925 a month for the Standard Intake Bot in the US and C$1,095 a month in Canada. Three to seven weeks to live, including a shadow-mode week on your own prescriptions before you pay anything.
We run the Rx Intake Bot in shadow mode on your live queue and hand you the report: what it would have entered, next to what your team entered, on your own scripts. No cost. Nothing installed in production. No claim you have to take on faith.
