The platform
Nexession takes the paper requisitions your lab receives every day and carries them through screening, reading, validation, and review, delivering a conformant HL7 order into the system you already run. Every step leaves a record you can audit.
How the work moves
Each order is graded by the confidence of what was read. High-confidence orders wait only for an identity confirmation, uncertain fields route to a reviewer, and anything that fails validation is held until it is corrected.
Inbound documents are treated as untrusted until proven safe: file type, size, and active content are checked before anything is read. The form is then matched to a known template and aligned precisely, checkboxes are measured with classical computer vision, and written fields are read with character recognition and scored for confidence. A form we do not recognize routes to a person instead of being force-fit.
A configurable rules engine checks required fields, code validity, and compatibility, alongside CLIA requisition-element rules cited to 42 CFR 493.1241. The result is a grade that decides the order’s path. Two gates sit above every grade: identity fields always need a human confirmation, and machine-read order content is never submitted without one.
High confidence. Waits only for identity confirmation by a reviewer.
One or more uncertain fields. Routed to the review queue.
Failed validation. Held with a reason until corrected.
The review console shows each flagged field beside the exact region of the source image it came from, so the reviewer reads the form, never a guess. Once identity and order content are confirmed, the order is serialized as a standard HL7 message and delivered over your transport with acknowledgement tracking. A failed delivery is held for replay rather than lost.
The order record
Under the pipeline sits a single structured order record. Every field carries the method that read it, the region of the page it came from, its confidence, its review status, and the original value before any correction. The same record drives the review console, the HL7 message, and the QA evidence.
How the evidence is producedIn a 30-minute session we take a requisition from fax to validated HL7 order in front of you, and you leave with the pilot outline and the five inputs we need to begin.
Occasional email updates on product milestones and pilot results, written by the team. A few times a year, and never a sales sequence.
