About
Built for the part of a laboratory nobody photographs
The analyser is the easy part. What decides whether a laboratory is trusted is everything around it — whether a result can be traced to the person who approved it, whether a report can be proven genuine, and whether the money owed is the money collected.
Diagnostic laboratories in this region carry a load that their software rarely acknowledges. A single patient may be an HMO enrollee whose claim needs tracking, a corporate account with its own price list, and a walk-in paying cash — sometimes in the same week. Results move between a scientist, a pathologist and a dispatch desk, and the paper that leaves the building is often the only durable record that any of it happened.
Most systems handle the middle of that well enough and lose the edges. Results get approved but the release goes unrecorded. Reports carry a letterhead anyone could photocopy. Claims are tracked in a spreadsheet running alongside the system that raised the invoice. None of these are dramatic failures. They are the quiet kind that surface months later, when someone asks a question the records cannot answer.
Clinexas was built to close those edges. It runs the whole workflow — registration, samples, results, approval, release, billing, and imaging alongside the laboratory — on the principle that the record should be strong enough to defend.
What we believe
Four decisions that shape everything else
Opinions held firmly enough that they show up in the architecture rather than the brochure.
Isolation is not a setting
Every laboratory gets its own database, not a row with a tenant column. Multi-tenancy done by filtering is one forgotten WHERE clause away from a breach, and a laboratory should not have to take that on trust. It is the first decision we made and the one everything else is built around.
A release should be provable
A report leaving a laboratory is a clinical and legal act. The system should be able to say what was released, by whom, to whom, and when — and the document itself should be checkable by whoever receives it, without a phone call to your front desk.
Built for how laboratories here actually bill
HMO schemes, corporate accounts, walk-in patients and referral commissions are not edge cases to be bolted on — they are the ordinary business of a diagnostic laboratory in this market, and they are modelled as such.
Software should not practise medicine
We keep records, enforce the controls you configure, and get out of the way. We do not interpret results or claim clinical judgement. The scientist and the pathologist own the result; our job is to make sure the record of it is beyond argument.
Who we build for
Laboratories that intend to be audited
Not because inspection is coming, but because a laboratory that could withstand it is simply a better-run laboratory.
- Independent diagnostic laboratories running a real departmental workflow — haematology, chemistry, microbiology, serology — rather than a single bench.
- Laboratories that also run imaging, and are tired of a second system that shares nothing with the first.
- Practices with meaningful HMO and corporate exposure, where knowing what has been billed and what has actually been collected is the difference between a good month and a bad one.
- Groups with more than one branch, where a result approved at one site may be collected at another.
Company details
- Registered name
- AYSON Technologies
- Registered address
- Lagos, Nigeria
- General enquiries
- [email protected]
Come and pull it apart
The fastest way to judge a laboratory system is to push your own awkward cases through it. Bring them.