.png)
Lessons from the Glasgow Clinical Research Facility on usability, flexibility, and supporting sites under real-life pressure
At the end of 2025, we had the opportunity to visit the Glasgow Clinical Research Facility (GCRF) within NHS Greater Glasgow & Clyde, one of more than 55 centers across the UK dedicated to supporting experimental medicine. Based within the Queen Elizabeth University Hospital, the facility offers flexible clinical space, an on-site pharmacy, and the ability to adapt its setup to meet the needs of a wide range of studies.
What stood out most, however, was not just the physical environment, but the scale and complexity of the work taking place. At any given time, the GCRF may support almost 200 clinical trials, plus over 200 other research projects across a network of hospitals, local practices, and specialist wards. Coordinating this requires careful management of training, access, records, and systems across many roles and responsibilities.
The visit offered valuable insight into how clinical research sites actually operate day to day — insights that are highly relevant to anyone designing technology, processes, or services for this environment. Here are some of the key themes that emerged.
________________
Terminology plays a critical role in clarity and compliance.
Small differences in wording can have significant implications, particularly when different teams use the same term in different ways. Clear, role appropriate naming and precise definitions help avoid confusion, reduce unnecessary queries, and support smoother collaboration across functions such as pharmacy, clinical operations, and supply.

Research sites are busy environments, balancing patient care, complex protocols, and tight timelines. Systems that are intuitive and supportive make a meaningful difference.
Features that guide users in context, provide easy access to help, and follow logical navigation patterns can significantly reduce cognitive load. Good usability is not a “nice to have” — it directly impacts efficiency, confidence, and compliance.
One important operational reality is that certain study visits require significant preparation before the patient arrives. This is especially true for studies involving complex or temperature sensitive products, early morning appointments, or long onsite days.
As a result, sites may complete preparatory steps in advance, with appropriate approvals. Systems that acknowledge this reality — for example, by allowing flexibility in scheduling and avoiding overly rigid constraints — are better aligned with how research is actually conducted.

Sites receive a high volume of automated messages, particularly around logistics and supply. When notifications are too frequent or poorly targeted, they can create frustration rather than support.
More thoughtful alerting — triggered only when action is genuinely required and sent to the right people — helps ensure important messages are noticed and acted upon, without adding unnecessary noise.

Rather than large, generic reports, sites often need very focused information, such as the history of a single item, everything related to a particular shipment, or events tied to one participant.
The ability to quickly access targeted, relevant data is often far more useful than having access to many high-level summaries.

Fields or labels that are unclear or not yet meaningful can cause confusion. Even temporary identifiers benefit from being intuitive and self-explanatory, helping users understand what they are seeing and why it matters.

At study closeout, sites may need access to a complete history of communications and records relevant to their role — including items generated before current staff were in place.
Ensuring this information can be retrieved when needed is essential for audits, accountability, and peace of mind.

Despite increasing digitalization, paper documentation remains a reality in many research settings. Shipping records, preparation logs, confirmations, manuals, and protocols often still end up in physical binders.
Designing processes and tools with this hybrid reality in mind leads to more practical, adoptable solutions.

Where possible, systems should avoid unnecessary restrictions. Allowing updates when they are genuinely needed — while clearly capturing reasons for changes — helps prevent workarounds, delays, and mistakes.

Effective training is tailored to the user’s role, easy to revisit, and does not require repetition of the same material across multiple studies when functionality is consistent. This respects users’ time and supports better retention.

Simple status indicators for integrations or data transfers can save time and reduce uncertainty. Clear visibility helps users know whether something is pending, completed, or needs attention — without having to chase answers.

Clinical research is carried out by people under real-world pressures. Patients run late. Appointments change. Unexpected issues arise.
Systems that provide guidance rather than rigid barriers, allow corrections, and make support easy to access are far better suited to this environment. Technology should adapt to human workflows — not the other way around.

Visiting the Glasgow Clinical Research Facility was a powerful reminder of the complex, demanding, and deeply human context in which clinical research operates. The more closely we align technology and processes with how sites actually work, the better we can support the people delivering vital research every day.

What we saw in Glasgow reinforced a core belief at Endpoint: the best technology is built through close partnership with the people who use it. Research sites are not just system users — they are expert teams navigating complex scientific, operational, and human challenges every day.
By continuing to learn directly from sites and incorporating these perspectives into our thinking, we aim to support research teams with solutions that are practical, intuitive, and grounded in real-life experience.

This visit — and the insights captured in this piece — was shaped by the observations and expertise of the following Endpoint team members:
We are grateful to the team at the Glasgow Clinical Research Facility for their time, openness, and willingness to share the realities of their day-to-day work.

Find out how these real-world insights influence Endpoint’s approach to supporting clinical research.
Learn More: https://www.endpointclinical.com/request-a-demo
.png)
Lessons from the Glasgow Clinical Research Facility

Why RTSM Needs Real-Time Intelligence

How Elosity enables shared inventory across protocols, reducing waste and preventing stockouts.