MEDILENS / MEDICINE TRACEABILITY

Smart medicine verification & traceability

MediLens connects a medicine's product, batch, and serial identity to a public verification page that anyone can open from a package QR.

Public verification does not require an account.

MediLens

Public verification flow

A package QR opens the record that matters.

The QR carries only the public verification URL. Product, batch, and serial details are resolved by MediLens.

How MediLens works

From manufacturer record to public result.

01

Manufacturer enrols

Start with an authenticated manufacturer workspace.

02

Product registered

Create the product identity used in traceability records.

03

Batch created

Connect production details, dates, quantity, and status.

04

Serial identities created

Create individual or database-generated serial identities.

05

QR placed on medicine

Prepare a QR that contains only its public verification URL.

06

Public scans

A phone opens the public MediLens verification page.

What can be verified

A focused public view of a medicine record.

A public scan can show product identity, batch number, manufacture and expiry dates, and the current verification result. Private tenant and internal database information stays out of the public response.

Verified genuine

The serial matches a valid product and batch record.

Recalled

The associated batch is currently under recall.

Expired

The associated batch is past its expiry date.

Unknown

No valid public record was found, or the serial is not eligible for verification.

Why MediLens

Built around the identity chain.

Product identity

Keep the product name, dosage form, strength, manufacturer, and GTIN together.

Batch traceability

Connect a medicine identity to its manufacture and expiry dates and current status.

Serialized identity

Create single serials or atomic batches of globally unique serial codes.

QR verification

Use a compact public route that leads directly to a serial verification result.

Manufacturer control

Manage products, batches, serials, recalls, and QR preparation from an authenticated portal.

Tenant isolation

Manufacturer records are scoped by tenant in backend authorization and database policies.

Security & trust

Public access and manufacturer operations stay separate.

Manufacturer operations require authentication and are protected by role-based backend authorization.

Manufacturer data is tenant-scoped, with authorization checks in the service layer and Supabase Row Level Security.

Public verification is an anonymous read path for the limited product, batch, serial, and status information intended for a scan.

The QR itself contains only the public verification URL, not an internal UUID, tenant ID, API URL, or authentication data.

For manufacturers

Bring product identity into a controlled workspace.

The current portal supports authenticated product, batch, serial, recall, and QR preparation operations. Manufacturer enrolment itself is available through the guided company account setup.

Create a company account

FAQ

What is MediLens?+

MediLens is a medicine verification and traceability platform for product, batch, and serialized medicine records.

Who can use MediLens?+

Anyone can use the public verification page. Manufacturers with an account use the authenticated portal for operations.

Does a consumer need an account?+

No. Public verification is designed to work anonymously from a medicine QR.

What happens when I scan a QR?+

Your browser opens the MediLens public verification route, which displays the available product, batch, serial, and status result.

Can MediLens work alongside an existing ERP?+

The product model includes an optional external ERP reference. A broader ERP integration is not implemented in this repository.