As Lily McQueen prepares to flee Chester with Romeo she's unaware she has life-threatening sepsis, will anyone find her before it's too late?
Lily McQueen’s life is in terrible danger after medics discovered she was suffering from sepsis. Lily (Lauren McQueen) has gone on the run with Romeo Quinn (Owen Warner) unaware she’s got potentially fatal blood poisoning.
During the special episode we see flash backs to memories of Lily’s early life with her mum.
Lily is seen enjoying baking and a flashback to 2006 shows a young Lily having burnt her hand and her mum saying it breaks her heart to see her hurt.
Meanwhile back in the present, Lily’s Aunty Diane, is horrified when psychologist Farrah Maalik (Krupa Pattani), breaks the news that the blood tests have shown that Lily has sepsis which will already be spreading to her organs and if left untreated, will kill her.
Lily’s friends, Peri Lomax (Ruby O'Donnell) and Yazz Maalik (Haiesha Mistry) are distraught when they realise her life is in danger and they immediately tell Diane where they think she’s gone with Romeo.
Diane, Prince and Tony desperately scramble to track Lily down and race to the station, but are they too late? Has Lily boarded a train with Romeo or has she already fallen victim to her untreated sepsis?
Hollyoaks is shown weekdays on C4 at 6.30pm with the next episode following on E4
Tess is a senior writer for What’s On TV, TV Times, TV & Satellite and WhattoWatch.com She's been writing about TV for over 25 years and worked on some of the UK’s biggest and best-selling publications including the Daily Mirror where she was assistant editor on the weekend TV magazine, The Look, and Closer magazine where she was TV editor. She has freelanced for a whole range of websites and publications including We Love TV, The Sun’s TV Mag, Woman, Woman’s Own, Fabulous, Good Living, Prima and Woman and Home.
Get the latest updates, reviews and unmissable series to watch and more!
Thank you for signing up to Whattowatch. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.