REQUIREMENTS-DRIVEN SOLUTION DESIGN / CASE STUDY
From Clinical Needs to a Working Data Solution
How clinical requirements, IT constraints and data governance shaped a practical hospital data solution.
System Performance
Controlled SQL data retrieval
Data Access & Security
Authentication and access logging
Clinical Data Harmonisation
Mapping and transformation
The Challenge
Making hospital data accessible for clinical research without disrupting existing systems.
Clinical researchers needed a practical way to retrieve, explore and use patient data already available within the hospital’s information systems, particularly to identify patient cohorts and support observational research.
However, translating this need into a working solution presented three interconnected challenges.
- System performance: enabling data retrieval without introducing repeated queries or unnecessary workload on operational hospital databases.
- Data access and confidentiality: ensuring that only authorised users could access a clearly defined subset of clinical information, with traceable access.
- Data usability: transforming heterogeneous source data into consistent, clinically meaningful information that researchers could query independently.
The central challenge was therefore not simply technical integration. It was finding a workable balance between clinical autonomy, IT requirements and responsible data access.
Clinical Needs ≠ Technical Readiness
Bridging the gap requires more than access to data.
The Approach
The project began by translating a clinical research need into a set of functional and technical requirements. Working directly with the clinical stakeholder and hospital IT representatives, I examined the available data sources, the intended research workflows and the constraints governing access to hospital information systems.
Rather than introducing a new enterprise platform or requiring changes to existing clinical systems, I designed and developed a dedicated application built around three architectural decisions.
Explore the Solution Journey
Application Architecture
Conceptual representation of the implemented solution. Select Architecture to explore the design decisions.
Start with the clinical problem
The clinical stakeholder needed to identify patient cohorts and explore hospital data independently, while respecting the hospital’s operational constraints.
The project started with the research workflow, not with a preferred technology.
Controlled SQL Data Retrieval
Results & Impact
A practical solution designed around real clinical and IT constraints.
The team developed, tested, validated, and deployed the application to support hospital-based clinical research, enabling authorised users to identify patient cohorts and explore harmonised clinical information through a dedicated interface.
The solution delivered three operational benefits:
- Controlled data access: Data retrieval was limited to agreed, read-only SQL views, avoiding repeated queries to hospital databases during user exploration.
- Research-oriented usability: An internal data dictionary transformed heterogeneous information into structures suitable for clinical searches and cohort identification.
- Sustained operational use: The application remained in use for two years. During approximately six-monthly client follow-ups, clients requested no corrective interventions or changes.
Key Takeaway
Effective clinical data solutions begin with understanding the problem, not selecting the technology.
This project illustrates how translating clinical requirements into practical technical decisions can bridge the gap between hospital information systems and research needs—without introducing unnecessary infrastructure complexity.