Founder work

PLATFORMS / 01—03

Founder-built platforms.
Real engineering evidence.

Before RefLens Ltd was formed — and alongside it — its founder designed and built working software. These platforms are shown here because they demonstrate, concretely, the engineering the consultancy offers.

Discuss a project See the services

Founder-owned work

These platforms were built and are currently owned personally by Dr Musaab Elkheder. They are shown as evidence of the founder's technical work, not as RefLens Ltd products or client engagements.

01 · TraceCite

Checking references before anyone relies on them

For researchers, editors and reviewers who need to know which citations in a document are incomplete, inconsistent or hard to verify.

TraceCite compares the bibliographic details of a reference against available scholarly metadata and applies AI-assisted checks, flagging what looks wrong for a human to judge. It is live and in its evaluation stage: the workflow works end to end, and the current focus is measuring how well it does so.

Status and limits: results depend on the coverage of the metadata sources queried, and every flag is intended for human review rather than automatic acceptance. It is not a plagiarism, integrity or compliance tool.

What this demonstrates: retrieval and matching against external sources, LLM-assisted checking with human review designed in, and an evaluation stage treated as part of the build rather than an afterthought.

Visit tracecite.com
ENGINEERING TRACECITE / 01
  1. 01

    Metadata retrieval and reconciliation across external scholarly sources

  2. 02

    AI-assisted checks that produce reviewable flags, never silent corrections

  3. 03

    Batch processing with per-item provenance for every result

  4. 04

    English and Arabic interfaces, including right-to-left layout

02 · EnayaMed

Clinical and operational workflows in one platform

For healthcare providers coordinating clinical work, appointments and operations across more than one site or team.

EnayaMed is a multi-tenant healthcare-workflow platform covering clinical records, appointments, and the operational processes around them. It is in development.

Status and limits: a development-stage project, not a certified or regulated medical device, and not offered here as a clinical service. Any demonstration uses synthetic data only.

What this demonstrates: multi-tenant architecture with data isolation designed in from the schema upward, healthcare interoperability, and delivery of a large domain model without losing auditability.

Visit enayamed.com
ENGINEERING ENAYAMED / 02
  1. 01

    Multi-tenant Django architecture with tenant-scoped data access

  2. 02

    Extensive relational domain model with audit trails and role-based access

  3. 03

    Partial FHIR interfaces for interoperability with other systems

  4. 04

    Arabic-first delivery with full right-to-left support

03 · EnayaCode

Clinical coding suggestions a coder can review

For clinical coding teams preparing insurance claims, where an incorrect code has a direct financial and compliance cost.

EnayaCode reads clinical documentation and proposes codes with the evidence for each suggestion, in a workbench built for a coder to accept, reject or amend. It is in development.

Status and limits: a development-stage project. It produces reviewable suggestions rather than autonomous coding decisions, and makes no claim of coding accuracy, regulatory approval or billing compliance. Any demonstration uses synthetic data only.

What this demonstrates: retrieval-augmented generation over a controlled vocabulary, a review workbench that keeps a human accountable for the output, and provenance carried through to the exported result.

Visit enayacode.com
ENGINEERING ENAYACODE / 03
  1. 01

    Retrieval-augmented pipeline on PostgreSQL with pgvector

  2. 02

    Hybrid retrieval and asynchronous indexing of reference material

  3. 03

    Review workbench recording who accepted or changed each suggestion

  4. 04

    Structured export with the evidence behind each code retained

The shared approach

The same habits, across all three.

These are the practices the consultancy sells, applied where the founder had complete control of the decisions.

Multi-tenancy from the schema up
Data isolation designed in at the model layer, not bolted on at the view.
Human review in front of consequence
AI output is presented for judgement; it does not act unsupervised.
Provenance and auditability
What changed, when, by whom and on what basis — retained rather than reconstructed.
Bilingual delivery
English and Arabic, including right-to-left layout, where the users need it.
Tests, documentation and handover
Treated as delivery requirements rather than optional extras.

Status and ownership

Whose these are, plainly.

Each platform was created by Dr Musaab Elkheder and remains personally owned by him, pending any formal written IP assignment to RefLens Ltd. They are not currently presented as RefLens Ltd products.

Visiting a platform's website does not create a consultancy or product contract with RefLens Ltd, and none of these platforms is offered for sale or subscription here.

Screenshots and demonstrations of the healthcare platforms show synthetic data only. Nothing on this page describes a regulated medical device or a clinical service.

Apply it to your problem

Need a similar capability?

The same engineering, scoped to your organisation and handed over to your team.

Discuss a project