SASKATOON -- A 72-year-old last seen on security footage entering Royal University Hospital on Saturday afternoon was found dead on the hospital’s main floor.
Allan Landrie was found around 9 p.m. Tuesday. Police do not consider his death suspicious.
“We wish to extend our condolences to the family and friends of Mr. Allan Landrie. We are saddened to learn of his passing," Saskatchewan Health Authority spokesperson Amanda Purcell said in a statement to CTV News.
In the news release, Purcell said Landrie was located in a publically accessible area of the hospital.
Police, Search and Rescue, and hospital security had been searching the area and buildings around RUH after Landrie was reported missing Saturday.
In addition, staff members in the hospital were alerted to the situation so they could also be on the lookout during their regular shifts.
During the time Landrie was missing, there were no reported sightings of him outside of what was seen in surveillance footage, she said.
In a statement Thursday, vice president of infrastructure, information and support Andrew Will said the SHA is conducting a thorough review over what occurred at the hospital.
"We will be also supporting any review being done by the Coroner’s Office," he said.
"The SHA fully supported Saskatoon Police Service’s missing person investigation. Our security officers worked closely with police upon confirmation that Mr. Landrie was seen entering RUH on surveillance video, which included a search of various locations through the 1.2 million square feet of space in RUH.
"The SHA provided police with full access of video surveillance footage. For security and safety reasons the surveillance areas will not be disclosed."
Premier Scott Moe told reporters Thursday that Landrie’s death is an unfortunate circumstance and offered his condolences to Landrie’s family.
"It’s my understanding that the (Saskatchewan Health Authority) and those closely involved are working very closely with the City of Saskatoon police department to ensure they can find out what exactly has occurred here and are there protocols that need to change that this does not happen again."