Home › Clinical Evidence
Trust

CLINICAL EVIDENCE & VALIDATION

Published by MCD Technology Investments Inc. · Last updated: 29 August 2026

A decision support tool is only worth the evidence behind it. This page collects, in one place, where RLES AI rules come from, who checked them, what has been measured so far in the field, and — just as importantly — what has not yet been validated.

THE EVIDENCE BASE IN NUMBERS

Every clinical page on this site carries its own reference list with full citations, DOIs and PubMed identifiers. Across the platform:

PUBLICATIONS
38Distinct peer-reviewed papers cited, each with a verified PubMed identifier
CITATIONS
43Claim-level citations placed next to the sentence they support, not in a bibliography at the end
MODULES
14Clinical modules carrying a published reference list
REVIEWERS
6Practising ophthalmic surgeons on the Medical Advisory Board, each named on the pages they reviewed

Where an exact identifier could not be verified, the page links to a literature search rather than inventing a citation. This is a stated policy, not an accident — see the Editorial Policy.

HOW A RULE ENTERS THE PLATFORM

No threshold reaches a surgeon's report without passing through the same sequence. The point of writing it down is that it can be audited.

1 · EVIDENCE IDENTIFIEDThe clinical question is traced to published guidance, peer-reviewed studies or the manufacturer's own documentation for the device in question
2 · EVIDENCE GRADEDThe source is assigned a level from A to E — guideline, peer-reviewed study, manufacturer document, RLES AI safety rule, or surgeon-specific nomogram
3 · MANUFACTURER CONSTRAINTS CROSS-CHECKEDDevice capability and published indication ranges are checked against the rule. A parameter absent from the maker's table is never estimated — the module reports “profile not loaded”
4 · RULE FORMALISEDThe threshold is written as an explicit, testable condition with its trigger, its evidence level and the source it came from attached
5 · SURGEON REVIEWA member of the Medical Advisory Board who operates in that field reviews the rule and its wording. Named review, on the record
6 · CASE TESTINGThe rule is run against real submitted cases in the pilot before it becomes binding, to see what it flags and what it misses
7 · DEPLOYMENT AND MONITORINGFlag rates are tracked in the field. A rule that fires on everything, or on nothing, is sent back to step 2

WHAT THE FIELD DATA SHOWS SO FAR

RLES AI has been in clinical testing since January 2026. The figures on the home page are read directly from the running service and are updated automatically — surgeon count, cases analysed, and the proportion of reports raising a yellow or a red flag. They are counts of system behaviour, and that is all they claim to be.

WHAT THESE NUMBERS ARE NOT

A flag rate is not an outcome measure. It records how often the safety engine raised a concern — not how often that concern was correct, and not how often the surgeon agreed. RLES AI does not yet publish sensitivity, specificity or concordance figures, because the prospective data needed to calculate them honestly does not exist yet. When it does, it will be published here with its methodology.

WHO REVIEWED WHAT

Clinical review is attributed, not implied. Each clinical page names the surgeons who reviewed it in the “Medically reviewed by” line beneath the headline, and the same reviewers appear in the page's structured data so that the human-readable and machine-readable claims match. The full board, with institutions, specialties and links to their publications, is on the About page.

DEVICE DOCUMENTATION

Laser and microkeratome parameters are treated as manufacturer facts, not clinical opinion. Published nomograms and instructions for use are loaded per platform; a device or a mode that is not in the catalogue is simply not offered. The supported platforms and the reasoning behind this are set out on the Supported Devices page.

PLATFORM VERSION HISTORY

RLES AI has been in development since February 2025; the first working version was released four months later. Versions are listed newest first, and each entry names what the release added, not how it performed.

V5.0 · AUG 2026
Cataract & RLE planning and the remaining modules added, completing the seventeen capabilities. Messaging and voice input introduced.
V6.0 · SEP 2026
The RLES AI Mobile Interface introduced: investigations are uploaded and reports opened on the surgeon's phone, with regional hosting — Türkiye for Turkish patients, the European Union for everyone else.
V4.0 · JUN 2026
CXL treatment planning, wavefront- and topography-guided planning, and presbyopia planning added.
V3.0 · JAN 2026
Structured clinical testing began. Contact-lens warpage detection and dry-eye analysis added.
V2.0 · OCT 2025
First trials with practising surgeons.
V1.1 · AUG 2025
PDF report generation.
V1.0 · JUN 2025
First working version: laser surgery planning with keratoconus and ectasia analysis.

CURRENT LIMITATIONS

  • RLES AI is in clinical testing. It is not a certified medical device and carries no regulatory clearance for autonomous clinical use
  • No prospective validation study has been completed. Agreement with expert review has not been quantified
  • Field figures come from a pilot population of collaborating surgeons and are not a random or representative sample
  • The platform does not calculate IOL power, does not recommend a lens brand or model, and does not overrule a surgeon
  • Modules that depend on image analysis are disabled in the US Edition pending regulatory submission
  • Every report is a decision support document. The clinical decision, and the responsibility for it, remain with the treating surgeon

WHAT COMES NEXT

The validation work now in preparation is a retrospective review of flagged versus unflagged cases against surgeon judgement, and a prospective comparison on ectasia screening. Results — including negative results — will be published on this page with their methods, sample sizes and dates, whether or not they favour the platform.

SEE IT ON YOUR OWN CASES.
RLES AI runs as a mobile interface on your phone — nothing to install from a store, reports in minutes. The final clinical decision always rests with the surgeon.

Request Information