Latrikos Labs

Laboratory requests turned into structured data.

Interprets tests, abbreviations and handwriting in their clinical context, with documented criteria your team can adjust.

Reading the text is the easy part.

Every day a clinical laboratory receives requests in very different formats: printed forms, scanned documents, handwritten notes. The hard part is understanding what each item refers to and which test is being requested.

Request received

Laboratory test request

DepartmentInt. Med.

Hb, Glu, CRP

Ferrit.

TSH + FT4

urg.fasting

Signature

Latrikos layer
  1. 1Reads the format and the handwriting
  2. 2Interprets each test in its clinical context
  3. 3Normalises and documents the criterion
Structured request
  • Hb → Haemoglobin
  • Glu → Glucose
  • CRP → C-reactive protein
  • TSH → Thyroid-stimulating hormone
  • FT4 → Free thyroxine
  • urg. → Urgent priority · fasting
  • Assumptions and criteria documented, adjustable by your team
  • Every item can be checked against the original request
Illustrative example: how Labs structures a laboratory request

The Latrikos clinical engine, applied to the laboratory.

Any format

Handles the variety of formats and the handwriting in the requests the laboratory already receives.

Tests in context

Interprets tests and abbreviations from the clinical context of each request.

Structured output

Returns structured, normalised output, ready for review.

Reviewable item by item, like the rest of the platform.

Every item can be checked against the document it comes from, and human review still has the final say.

Tell us how requests reach your laboratory today.

Turn your next report into your next study.