Using Jira as a requirements library for clinical trials delivery

Using Jira as a requirements library for clinical trials delivery Passed

Tuesday May 20, 2025 16:00 - 16:30 F1

Track: Data / Information

Clinical trials are becoming digital and the delivery of the trial system does not differ that much from the delivery of an IT system.

Most of the clinical trials have a number of standard requirements that are the same across different trials and there is only a small number of requirements that need to be configured in a study.

AZ has created a library in Jira, where configurable requirements can be reused and configured based on trial needs, while the requirements that remain the same across trials are only referenced in the study URS.

Moreover, using Jira for automated creation of documents such as User requirements specification or Test report, takes a big burden from the teams that needed to create these documents manually.

This approach allows the delivery team to focus only on the requirements that need configuration and additional validation, and together with automated document creation, it minimizes the time and effort for study delivery.

Language

English

Topic

Technology

Seminar type

Live + On site

Lecture type

Presentation

Objective of lecture

Tools for implementation

Level of knowledge

Intermediate

Target audience

Management/decision makers
Organizational development
Technicians/IT/Developers

Keyword

Actual examples (good/bad)
Benefits/effects
Education (verification)
Management
Innovation/research
Test/validation
Documentation
Apps
Usability
Informatics/Interoperability

Lecturers

Michalis Fardis Lecturer

Business analyst
AstraZeneca

Medical informatics professional with strong interdisciplinary background in IT and healthcare. Passionate about driving innovation and change in healthcare through IT solutions
Currently I work in AstraZeneca where I support the delivery of innovative solutions in clinical trials, ensuring that they add value to AZ's trials, while meticulously managing the actions needed from pilot to full-scale implementation.

Cookie	Category	Provider	Expiry	Legal basis	Intention
_production_session_id	Necessary	InvitePeople	Session	Legitimate interest	Stores a unique ID of the InvitePeople-user session. This will allow the user to login into InvitePeople.
order_id	Necessary	InvitePeople	6 hours	Legitimate interest	Stores a unique ID of the current order (shopping cart). This allows the user to add, view, and manage items in their order during the session.
cookie_consent_[ID]	Necessary	InvitePeople	6 months	Legitimate interest	Stores the user's cookie consent preference for a specific Optional cookie policy. The ID in the cookie name refers to the unique identifier of that policy. This ensures the user’s choice—whether accepting all cookies or only necessary ones—is remembered on future visits.
lang	Necessary	InvitePeople	1 year	Legitimate interest	Remembers the user’s selected language version.
logged_in_user	Necessary	InvitePeople	1 year	Legitimate interest	Stores a unique ID of the InvitePeople-user. This will help the user navigate.
production_auth	Necessary	InvitePeople	1 year	Legitimate interest	Stores a unique ID of the InvitePeople-user. This will help the user with future logins.