Reads what a lab receives, drafts what the order needs.
A document arrives in whatever condition the sender chose. Identity and insurance are read in the same pass — no per-clinic template to set up first.
review and confidence
Scores the read. It never approves it.
The score is the model’s certainty about its own reading. It gives the technician confidence; it never gives the software authority.
Before a lab loads anything, on paper the model has never seen, roughly six fields in ten come back needing no correction. With a test list and referring-client codes in place that typically reaches the high eighties. The figure that counts is the one measured on the lab’s own documents — which is what the first batch is for.
what it accepts
However it turns up.
Requisitions, insurance cards and identity documents — whatever condition the sender chose. PDF, JPG, PNG or TIFF, one page or many.
scan to email
Email it in. AiReq logs what arrived.
batch processing
Batches in, worklists out.
One submission runs as a background job — no tab to keep open. A page that cannot be read becomes its own item instead of holding the batch behind it.
inside the LIS
A confirmed order, already in the system.
The order is created in CrelioHealth, where accessioning already happens — no export file, no second system, no re-keying. On a different LIS, the same read; where the order lands is what we settle first.
Duplicate checkAudit trailReady to accession
AiReq owns whether the order matches its documents. Whether a payer accepts it is Revenue Guard.
try it yourself
See it read your own requisitions.
Send a stack of your own forms — whatever turns up — and we'll show you what came back, field by field, including what it got wrong.