How to launch a UK eye health telehealth service in 2026: dry eye, conjunctivitis, and safe remote triage

Eye complaints are one of the most common reasons UK patients look for a same-day appointment, yet eye health has stayed largely outside private telehealth, dominated instead by high-street optometry. That gap isn't really about demand — it's caution. A small number of eye presentations are genuinely low-risk to manage remotely, provided the triage protocol treats every red flag as non-negotiable rather than a judgement call.

Why eye health is an underused telehealth vertical

Red eye and eye irritation are among the most frequent presenting complaints in community pharmacy, and most cases resolve without specialist input — a self-limiting viral conjunctivitis, a flare of seasonal allergy, or dry eye brought on by screen time and air conditioning. None of that requires a slit lamp.

What has kept platforms away isn't the clinical reality, it's the perceived risk of missing something serious behind a red eye. That risk is real but manageable — the same way a migraine service manages headache red flags or an asthma service manages breathlessness red flags: with a triage protocol built around exclusion criteria, not optimism.

Which eye conditions are suitable for remote assessment

The safe remote caseload is narrower than most founders assume, but it's a real caseload. Dry eye disease is the most common chronic complaint and responds well to artificial tears, lid hygiene advice, and environmental changes, with remote follow-up entirely appropriate if symptoms persist.

• Dry eye disease (screen-related, environmental, or age-related)
• Allergic and seasonal conjunctivitis — bilateral itching, watering, no pain
• Suspected bacterial conjunctivitis without red flags — purulent discharge, no pain, no visual change
• Blepharitis and lid margin disease
• Recurrent stye or chalazion advice and self-care

Red flags that require same-day face-to-face care

The entire safety case for this vertical rests on the exclusion list being followed every time, not most times. Sudden vision loss or change, significant eye pain, photophobia, and any history of trauma or chemical exposure all take the patient out of the remote pathway immediately.

• Sudden or progressive loss of vision
• Significant eye pain, rather than irritation or grittiness
• Photophobia alongside a red eye
• Trauma, chemical splash, or foreign body sensation with visual disturbance
• Contact lens wearer with a painful red eye — stop lens wear and refer same day given the risk of microbial keratitis
• Unilateral red eye with reduced vision, or a fixed, distorted pupil

The regulatory picture: GPhC, CQC, and where GOC fits

For a pharmacist- or prescriber-led model, dispensing sits under a GPhC-regulated pharmacy and superintendent pharmacist, and the service itself is very likely a CQC-registrable activity once it involves remote diagnosis and treatment rather than pure information. The medicines themselves — chloramphenicol, antihistamine drops, artificial tears — sit under ordinary MHRA distance-selling rules.

It's worth being precise about where the General Optical Council fits, because it's easy to conflate. GOC regulates optometrists and dispensing opticians carrying out eye examinations, sight tests, and refraction. A symptomatic-treatment telehealth service that assesses and dispenses for conditions like conjunctivitis or dry eye is a GPhC matter, not a GOC one — that only changes if the service starts offering optometrist-led sight tests or clinical eye examinations.

Designing the clinical pathway

A structured questionnaire does most of the safety work before a prescriber ever sees the case: onset, laterality, pain versus irritation, vision change, contact lens use, and photo upload of the affected eye for visual triage. Gating questions should route any red-flag answer straight to a same-day referral message, not a queue.

The prescriber review then confirms the triage decision and adds safety-netting advice to every consultation regardless of outcome — what to watch for, and where to go if it worsens. This is the same discipline covered in writing clinical SOPs for UK telehealth and in the wider safeguarding process for remote consultations.

A dry eye consultation and a painful red eye in a contact lens wearer can look similar in a two-line message. The triage questionnaire's job is to tell them apart before a human ever has to.

Dispensing and operational considerations

Eye drops and ointments carry short in-use expiry once opened — commonly around four weeks — and that needs to be on the patient information clearly, not buried in a leaflet insert. Stock rotation and batch tracking matter more here than the shelf life alone suggests, in line with the discipline covered in packaging and tamper-evidence and medicines waste and returns.

There's no cold-chain complexity here, unlike a GLP-1 or biologic line, which makes eye health a comparatively simple addition to an existing same-day dispensing operation — the bottleneck is clinical triage design, not logistics.

How PExpo supports an eye health vertical

Adding eye health to an existing clinic or brand doesn't need a separate dispensing setup. PExpo's regulated pharmacy layer — superintendent pharmacist accountability, dispensing, and same-day fulfilment — sits behind the clinical front end you already run, the same way it supports clinic dispensing and white-label telehealth brands across other verticals.

The clinical protocol is the part worth getting right before anything else — the platform work is comparatively small once the triage and escalation rules are settled.

Eye health won't be a headline vertical the way GLP-1 or HRT have been, but it's a low-complexity addition for an operator that already has a CQC-registered clinical front end and a dispensing partner in place. The work is almost entirely in the triage protocol — get the exclusion list right, keep the safe caseload narrow, and the rest follows the same pattern as any other telehealth vertical. See pricing or get in touch to talk through adding it to an existing service.

Frequently asked questions