Neural · Medical supply
The order arrived by fax. It still has to become an order.
A medical supply business runs on documents that arrive in the wrong format from people who are busy: a faxed prescription, a referral with the diagnosis code missing, an insurance card as a phone photo. Every one has to become a clean order, a verified eligibility and a claim that pays, and the resupply that keeps the revenue recurring depends on someone remembering to reach out. An agent layer can read the intake, chase what is missing and draft the outreach, with a person on every step that touches a patient.
How to read this. Neural is the agent architecture behind the software we build and the work we run. Client engagements run under NDA, which is why no distributor is named on this page. Every capability below is labelled for exactly where it stands, so you can tell what is running from what is designed.
Contents
- 01Where it goes wrongThree places, in the order they cost you
- 02One order, one morningThe whole loop, start to finish
- 03The workforceFive workflows and exactly where each one stands
- 04StandingEvery piece, and exactly where it stands
- 05DeploymentThe questions your IT group will ask first
- 06How it startsOne workflow, sixty days, read-only
[01]Where it goes wrong
Three places it costs you.
Intake is transcription
Prescriptions, referrals and orders arrive as faxes, PDFs and photos. Someone reads each one and keys it into the system, and the ones missing a signature, a diagnosis code or a quantity sit in a pile until someone notices.
The paperwork decides whether you get paid
Eligibility, prior authorization, the physician's documentation: each item is owed by someone outside your building, and the claim waits on all of them. The chase is manual, and the denial arrives weeks later for a reason that was visible at intake.
Resupply is revenue that leaks
Patients come due for supplies on a schedule the payer sets and your team tracks in a spreadsheet. The contact that has to happen before a shipment is the contact that gets missed in a busy week, and every missed cycle is recurring revenue gone.
[02]One order, one morning
What it looks like from the fax to the shipment.
Written in the present tense for readability. This is the designed sequence, mapped to your operation.
- 08:05
A referral arrives by fax: a prescription for a mobility device, a face sheet, and a copy of the insurance card, two pages of it blurred.
- 08:06
The agent layer reads it into a draft order, matches the patient, flags the missing diagnosis code and the unreadable member ID, and drafts the fax back to the prescriber's office asking for both.
- 08:20
The intake coordinator checks the read, fixes one field, and sends the request. The order is queued against authorization with everything it's waiting on listed.
- Wed
The documentation comes back. The authorization packet assembles itself for review, and the order moves. Nothing shipped until a person cleared it.
- ·
Every read is logged, which systems may hold patient data is written down before any of it is read, and nothing about care was decided by software.
It reads and drafts. A person verifies every order, and nothing clinical is ever the agent's call.
[03]The workforce
Five workflows, and where each one actually stands.
Every one has the same shape: a trigger, agent work, a human checkpoint, an artifact. The status under each name is the honest part, and it names where a workflow has actually run rather than how finished it feels.
Order intake
Trigger
A fax, an email, a portal order or a photo arrives.
Agent actions
Reads it into a draft order, matches the patient and the item, checks the required fields and signatures, and drafts the request for whatever is missing.
Human checkpoint
The intake coordinator verifies every order before it exists in your system.
Output
A clean order or a specific ask, minutes after arrival.
Authorization and documentation chase
Trigger
An order needs eligibility, prior authorization or physician documentation.
Agent actions
Tracks what each order is waiting on and who owes it, drafts the request to the prescriber or the payer, reads what comes back and assembles the packet.
Human checkpoint
Billing reviews the packet and submits it. It never files a claim on its own.
Output
A per-order list of what is outstanding, oldest first, and the packet when it's complete.
Resupply outreach
Trigger
A patient comes due under the payer's schedule.
Agent actions
Drafts the contact in your voice, inside the window the payer allows, with the questions the payer requires asked in your words, and keeps the record the claim will need.
Human checkpoint
A person makes the contact, confirms the patient's request and what they have left, and documents it. Nothing ships automatically.
Output
Resupply that happens on schedule, with the contact documented for the claim.
Executive brief
Trigger
Every morning, before anyone is at a desk.
Agent actions
Reads across the systems that hold your operation and writes what changed, what slipped, and what needs a decision today.
Human checkpoint
You reply in the thread; the work routes from there.
Output
One brief, in the order you'd have asked for it.
Contract price check
Trigger
On every distributor invoice.
Agent actions
Compares invoiced prices against your contract and group-purchasing pricing and names the lines that don't match, with the contract term quoted.
Human checkpoint
Purchasing decides what to dispute.
Output
An exception list per invoice instead of a spot check.
[04]Standing
Where each piece stands.
Stated precisely, because in this category precision is the differentiator.
We've built reseller systems for medical supplies and services
Reseller systems for medical services and supplies, delivered before the agent platform existed.
We ship ordering and inventory at scale
A mobile and kiosk ordering suite across 100+ major venues, and a connected inventory platform across 500+ industrial sites. Different industries, the same problem: orders and stock across many locations, reconciled.
We run our own company on the agent layer
Neural plans, builds, reviews and ships at CKS every day, including the site you are reading. We will show you the live console on a call rather than a slide.
The supply workflows are designed, not deployed
Specified against the intake-to-claim path and the resupply cycle. Patient data is protected health information: a business associate agreement and a written data-handling plan come before any access, and no patient data is used to train any model.
What runs for a client stays with that client: what you see here is the architecture and where each piece stands.
[05]Deployment
The questions IT will ask.
Answered here rather than in the third meeting.
- Where it runs
- Your infrastructure or a private tenant. Not a shared multi-tenant product.
- What it reads
- The systems you already run. Read access first, always.
- Who approves
- Actions you designate as consequential stop at a named person before they happen. You set that boundary; the platform enforces it rather than relying on discipline.
- What's recorded
- Each agent action is logged with its inputs, the sources it cited, what it did, and who approved it. The things that hold up in a review.
- Who owns it
- Your data and configuration are yours, and we'll put the exit terms in the contract rather than asking you to trust a web page.
[06]How it starts
One workflow. Sixty days.
Not a platform rollout. We pick the single workflow where it is costing you most, stand it up against your real systems, and you judge it on whether it caught things your people did not have time to.
Week 1
The workflow and the success metric are agreed in the first session, not discovered over a month. Read-only access to the systems it needs; your security review runs in parallel.
Weeks 2–7
It runs alongside your people on live work. Every output reviewed by your team, nothing acted on automatically, false positives tuned weekly.
Week 8
Measured against the metric we set in week 1. Keep it, change it, or walk away. Because it stayed read-only, walking away means revoking credentials and removing an integration rather than migrating off a platform.
- What it costs
- Fixed fee, quoted after the working session, so it is priced against your actual systems rather than a guess. No per-seat licence during the pilot.
- How it's judged
- One number, agreed before we start. Usually exceptions caught that your team didn't have hours to catch, measured against a baseline period.
- What we need
- Read-only access to two or three systems, one person who reviews the output, and an executive who reads the weekly.
- What you keep
- The configuration and everything it produced, whether or not you continue. Data handling and retention are in the agreement before access is granted.
A working session is ninety minutes with your operators, not a pitch. We map where the cost actually lands and tell you which parts of it are worth pointing an agent at, including the parts that are not.
Other sectors