Give your people back their morning.
In a lean lab, the requisitions land on the people you can least spare. AiReq reads the stack so your scientists don't spend the morning typing it.
Requisitions, insurance cards and IDs — read, pre-filled, and checked by a person before the order posts.
The stack is already waiting.
Faxed, scanned, handwritten, photographed — the overnight requisitions have piled up before anyone's had coffee.
Then the rush.
Samples arrive faster than anyone can register them. The pile grows. The clock doesn't care.
One scan.
The stack goes on the scanner that's already on the counter — one pass, no sorting, no separator sheets. AiReq reads the file whole, every format in it, fax to handwriting, and turns paper into structured orders before the coffee's cold.
A queue, not a pile.
Instead of a stack to type, a tidy list of pre-filled orders to review — with only the few uncertain fields flagged for a person.
Back at the bench.
Your scientist has the morning back — running assays, the work they came in to do, instead of transcribing insurance IDs.
Watch it read a requisition.
Sixty seconds, start to finish — the real screens, nothing staged.
“By mid-morning the requisitions are just… done. We never hired anyone to register them.”
— a US molecular lab that runs its whole requisition intake through AiReq. One technician confirms the orders; nobody was hired to type them.
how it works
- 1However it arrivesFax, scan, photo or handwriting — dropped in, or emailed in.
- 2Into the systemEvery page lands in one place — no sorting first.
- 3Read & analysedAiReq reads each one and drafts a structured order.
- 4Ready to reviewA queue of pre-filled orders — a technician checks and signs off.
Nothing posts on its own.
AiReq drafts the order — a person reviews and signs off before it's created. The AI does the typing; your team keeps the final say.
12:00 — the morning's yours again
Let AiReq take the paperwork.
Fourteen days, no card, thirty requisitions — enough to see it work on your own paper, not a prepared sample. Or book a demo and we'll run a full stack on the call.
AiReq is built by CrelioHealth, and billed separately from the CrelioHealth LIS.
Six weeks later, the denial lands anyway.
Nothing was mistyped. The name was right, the panel was right, the morning went perfectly. The payer just doesn't cover that test, coded that way — and nothing you read at 8:15 could have known that.
Revenue Guard takes the pushback.
Revenue Guard reads every order against that payer's own policy document before it reaches billing — so the coverage problem surfaces while the order can still be fixed.