Automated lab accessioning
Nexession reads the requisitions that arrive by fax and scanner, validates them field by field, and delivers clean HL7 orders into the LIS you already run, with a trained reviewer confirming identity and order content before anything is submitted.
Accessioning is the front door of every lab. We believe degreed scientists should spend their hours on science, not retyping faxes — and that automation on a medical order must be auditable down to the pixel.
Nexession automates the routine majority of paper orders and routes genuine uncertainty to a person. Providers change nothing. Your portal, your billing, and your LIS stay exactly as they are.
Keyed by handEvery field, every form
The problem
GI, dermatology, urology, and wound-care practices keep faxing requisitions because it fits their workflow, and the lab absorbs the cost rather than risk the referral relationship. Each of those forms is typed into the LIS by hand, and the mistakes cluster in the fields that are most expensive to fix.
From scan to submitted order
The engine handles the routine majority of orders on its own. Anything it is not certain about goes to a trained reviewer rather than being guessed at.
Nexession identifies the form, aligns it, and reads each field. Checkboxes are measured with classical computer vision so every result can be checked by hand. Written fields are read with optical character recognition and scored for confidence.
Patient identity and every machine read order detail are confirmed by a trained reviewer. The system enforces this on the server, so an order cannot be submitted until the confirmation is complete. Anything unclear is flagged, never guessed.
See the safety rules
Identity confirmedEnforced on the server
The order is sent to your laboratory information system as a standard HL7 message with acknowledgement tracking. If delivery fails, the order is held for retry rather than lost, and each message is linked back to the source image.
One structured order record decouples reading from delivery: HL7 v2.5.1 today, FHIR and other targets pluggable, working with common interface engines and tested against a test endpoint before anything touches your live interface.
Every access and every field edit is written to a permanent, append-only log with the before and after value. Each field carries its source, region, confidence, and reviewer — the answer to an auditor’s “why was this value accepted?”
Principles
A wrong test code or a mis-keyed identifier is a clinical and billing event, not a typo. Three rules are fixed in the software and cannot be turned off.
Marks are measured with classical computer vision and stored with the exact numbers behind each decision, so a reviewer or an auditor can recheck any result by hand. No language model ever reads a checkbox.
Diagnosis codes, test selections, and provider identifiers are copied from the form. They are never inferred, defaulted, or normalized into a billable code. A blank field stays blank; an unreadable one goes to a person who reads the image.
A trained reviewer confirms patient identity and order content before any order is sent, enforced on the server rather than in the interface. Every access and edit is written to a permanent, append-only log with the before and after value.
In practice
The review console runs in the browser your lab already has. Nothing to install.
Checkboxes measured by classical vision — every decision reproducible by hand.
Every access and edit on a permanent, append-only record with before and after values.
Standard HL7 into the LIS you already run, proven on a test endpoint first.
The order record
Nexession produces one structured order record for each requisition. Every field records the method that read it, the region of the page it came from, how sure the system was, and who confirmed it. When an auditor asks why a value was accepted, this record is the answer.
Who it serves
Operations feels the labor line, compliance answers to the surveyor, and IT protects the interface. Nexession was built with all three in the room.
When referral volume grows, keying hours grow with it. Nexession breaks that line.
Volume without headcountReview minutes, not keying hours
Entering a requisition into the LIS is regulated transcription. Nexession produces the proof as it works.
Surveyor-readyEvidence produced as you work
Nexession is a complement to the LIS, not a replacement — and the connection is proven before it goes live.
Your LIS, unchangedTest endpoint first
Where we stand
A young company asking for a laboratory’s trust should show its guarantees rather than borrow logos. Each statement below is enforced in the software itself, and your team is welcome to test every one of them during a pilot.
A checkbox is never read by a language model.
Deterministic computer vision; every mark stores the measurement behind the decision.
Diagnosis, test, and provider codes are transcribed only.
Never inferred, defaulted, or normalized to a billable code. Blank stays blank.
No order submits without a person.
Identity confirmation enforced on the server and re-checked by a database trigger.
Every access and edit is on the record.
Append-only audit with actor, timestamp, and before-and-after value.
Transcription QA evidence, produced as you work.
Mapped to CLIA 42 CFR 493.1241 by citation, exportable for a surveyor.
Validated on synthetic data — and we say so.
Accuracy figures come from a synthetic test set until pilots produce real ones. Your pilot sets the real baseline.
Fits the lab you already run
Orders simply arrive in your LIS already validated, over the interface you already run. The referral relationship stays intact, the portal and billing stay untouched, and the keying tax goes away.
Delivered as OML^O21 today, FHIR and other targets ready
Order record that decouples reading from delivery
Changes required from your referring providers
Where the product stands
We say this plainly because trust is the point. The engine reads, validates, reviews, and delivers on a set of degraded synthetic requisitions. Live work with protected health information happens only inside a covered environment.
See it on your forms
A 30-minute online session: watch a requisition travel from fax to validated HL7 order, ask the hard questions, and leave with the pilot outline and the five inputs we need to begin. Nothing that comes later should be a surprise.
Prefer email? contact@nexession.com
Occasional email updates on product milestones and pilot results, written by the team. A few times a year, and never a sales sequence.
