Revolutionising clinical trials with a Geo Matrix Decision Engine

Écran surligné

À propos de ce projet

Aurora Analytica partnered with Imaginary Cloud to build the first decision engine of the Aurora Suite - the Geo Matrix Decision Engine aimed at CRO users to run different scenarios using custom data.

Result: A new platform that provides valuable insights into customer behaviour and helps optimise workflows across key touch points such as RFIs, RFPs, and scenario planning.

notre IMPLICATION

Design

Development

technologies

Next.js

Redux

Auth0 by Okta

AWS

React

Nest.js

Prisma

PostgreSQL DB

Transforming Clinical Trials: Aurora Analytica's Innovative Big Data Platform

Aurora Analytica enables clients to leverage big data more effectively through its advanced web platform. The Aurora Suite™ (Aurora) is an advanced web application focused on key areas such as market access, performance, simulation, trial design, country/site selection, clinical operations, specialized healthcare data, generative AI/ML, and more.

By leveraging each of these key areas, Aurora Analytica has developed 11 cutting-edge components, known as Decision Engines™, that perform over 14 assessments crucial for the planning, design, and operation of clinical trials. This centralized hub for data-driven insights facilitates seamless exploration and utilization of vast amounts of information. Aurora Analytica's intuitive platform empowers users to uncover valuable patterns, correlations, and trends, driving in formed decision-making in the clinical trial domain. Their mission is to unlock break throughs and transform the future of global healthcare by empowering health pioneers to re-envision data analytics.

Aurora Analytica project frame
Exemples d'écrans
Imaginary Cloud’s role and involvement with Aurora Analytica

Imaginary Cloud played a supportive role in the project management of Aurora Analytica' platform, assisting the client in overseeing the process from the initial design phase through to development. By providing the necessary technical specialists, Imaginary Cloud enabled Aurora Analytica to make informed decisions, ensuring seamless integration of design and technical feasibility.

This collaborative approach allowed for proactive issue resolution, consistent stakeholder communication, and the timely delivery of the project. The partnership ensured that the platform not only met but exceeded expectations, establishing a strong foundation for future enhancements.

Exemples d'impact d'Imaginary CloudNOUVEAU PROJET EN TÊTE ? PARLONS-EN

pendant le projet

Imaginary Cloud used the Minimum Viable Product (MVP) process. It follows a multidisciplinary approach where product owners, developers, and UX/UI designers state all the features and their priorities to meet your project and user's requirements.

deux étapes

Migration
Développement

quatre étapes

Recherche
Idéation
Exécution
Évaluation technique

quatre étapes

Exigences
Intégration au back-end
Développement de sites Web
Filtrage et recherche avancés

quatre étapes

Recherche
Idéation
Exécution

four stages

Backlog
Bootstrap
Wave 0
Wave N

four stages

Research
Ideation
Execution
Launch & Handover

deux processus

MVP
PDP

Four stages

Scope meeting
Code review
Test review
Quality review
Assessment

pendant le projet

Imaginary Cloud used the Minimum Viable Product (MVP) process. It follows a multidisciplinary approach where product owners, developers, and UX/UI designers state all the features and their priorities to meet your project and user's requirements.

migration

Imaginary Cloud a commencé par migrer la base de données existante de Wordpress vers PostgreSQL. Une tâche ardue en raison des milliers d'articles et de la grande taille des actifs qui sont normaux sur une place de marché CG.

Une fois la migration terminée, l'équipe s'est concentrée sur la migration de son infrastructure. Le site était hébergé sur Heroku, ce qui présentait des contraintes importantes quant à sa capacité d'adaptation. Imaginary Cloud a pu le migrer vers AWS, achevant la première étape en seulement 2 mois.

Développement continu

Après la livraison réussie de la phase 1, le client a continué à travailler avec Imaginary Cloud sur une base de développement continu, ajoutant de nouvelles fonctionnalités à son produit pour stimuler sa croissance. L'équipe a travaillé sur de nombreux éléments différents, des intégrations de paiement aux outils de campagne de vente pour faciliter les campagnes promotionnelles sur le marché. Imaginary Cloud a également aidé Flipped Normals à améliorer son positionnement sur Google en mettant en œuvre un audit SEO, qui a amélioré les performances du site et la pertinence du contenu.

exigences

Le projet a débuté par une réunion d'équipe pour répertorier toutes les exigences du client. Cette enquête approfondie permet une livraison plus facile, plus rapide et plus rentable. Cette réunion a été dirigée par notre chef de projet, qui soutient l'équipe tout au long du projet, et notre développeur, qui s'assure que tous les détails techniques sont discutés.

Eurofound a fourni un dossier solide qui a rendu compte de l'infrastructure existante, de sa vision du site Web et des contraintes et exigences techniques. Il s'agissait d'une tâche difficile qui devait être réalisée en 6 semaines.

intégration au back-end

Notre développeur a commencé le processus de développement en créant l'intégration principale qui permettrait au nouveau site Web de récupérer le contenu de la base de données existante. À l'aide d'un framework Django, nous avons pu créer une application efficace et rapide qui récupérait des données, générait des listes de résultats et permettait des options plus avancées.

Imaginary Cloud et Eurofound se sont rencontrés chaque semaine pour s'assurer que tout était développé conformément aux exigences du client.

développement de sites Web

Une fois le logiciel principal terminé, l'étape suivante a consisté à développer le site Web permettant d'accéder à cet outil. Pour cela, notre développeur a suivi le guide de style d'Eurofound afin de garantir la cohérence de la présence numérique du client.

Bien qu'aucun designer n'ait été affecté à ce projet, notre développeur a suivi les meilleures pratiques en matière d'UX/UI, puisqu'il a pu entrer en contact avec plusieurs des concepteurs d'Imaginary Cloud.

filtrage et recherche avancés

Afin d'améliorer la navigation dans le contenu, Eurofound souhaitait inclure une fonctionnalité avancée de filtrage et de recherche dans sa base de données. Après avoir entièrement cartographié le contenu de la base de données dans le nouveau logiciel, notre développeur a pu créer un ensemble de filtres de catégories permettant aux utilisateurs de sélectionner le contenu d'un sujet donné, et a implémenté un élément de recherche sur la page, permettant à l'utilisateur de rechercher librement n'importe quel document.

research
1. Briefing
2. Benchmark
3. User Research

We identify the main aspects of the business model and user needs.
First, we gather evidence that will support the decisions taken henceforth, ensuring that no decision is made based on vague assumptions.

This stage consists of 3 steps: a briefing with the project's vision and goals and business requirements; user research to guarantee product usefulness and effectiveness from the user's perspective; and a design benchmark to analyze the landscape of similar and complementary products, design patterns and technologies used in the industry.


The Research stage allows us to leverage the knowledge and skills of existing players and ensure features and design differentiation in the market, and ensure costumer fit.

ideation
1. User journey
2. Decision Matrix
3. Wireframes
4. Moodboard

We formulate an approach to the product based on the user's needs and the business model.
This is the core of the creative process and it is where the concept of the product is formulated based on the user's needs and the business model (both identified in the Research phase). Here, the UX designer, the product designer, and the product owner work closely together.

This stage consists of 4 steps: mapping out the user journey, by describing each user's action, with various user scenarios; a decision matrix that helps prioritize the users' and product's goals while considering the product life cycle's current stage; drawing the wireframes, i.e., the pages’ structure and navigation flow to ensure interface usability and reduce design time; and finally, a mood board to ensure that the product's look and feel conveys the desired user experience and is aligned with the user profile and market strategy.

Execution
1.Style guide
2. Graphic user interface
3. prototype

We bring the concept to life and put it into practice.
In this stage, the product designer focuses on creating a physical representation of the concept that has been defined up to this point.

It consists of 3 steps: a style guide, where we define a graphic interface’s style, considering colour palette, fonts, image style, input fields, buttons, and so on, to ensure consistency throughout the application; a graphic user interface design (GUI) which are the end-looking screens by applying the style guide to the wireframes; and a click-through prototype to facilitate the feedback from stakeholders or potential users and investors.

TECHNICAL ASSESSMENT
1. HIGH-LEVEL ARCHITEcTURE
2. PROJECT PLAN

We guarantee that all requirements and ideas generated are realistic to implement.
In this stage, all the work previously done should be achievable considering the available time and budget previously settled.

It consists of 2 steps: a high-level architecture where we detail how the product will be built, identifying baselines for the needed technologies and skills to make it; and a project plan to define the major milestones and provides a general understanding of the project's structure, phases, intersections and interdependencies.

research
1. business case

This initial stage involves gathering crucial information to understand the project's vision, goals, and business requirements. We present the business case, outlining the project timeline, main competitors, complementary products, and high-level exploration of personas. This also involves asking and answering questions to define objectives and explore ideas, ensuring differentiation from existing players in the market.

ideation
1. sITEMAP
2. WIREFRAMES
3. cONTENT

During the ideation phase, we provide the blueprint and structure for the whole website, which defines the relative importance of content as it flows down the page.

The site map establishes the website's structure and content hierarchy for optimal navigation. Wireframing outlines screen structure and navigation flow, prioritizing your digital product’s functionality over aesthetics. Lastly, for the content ideation we help you plan the page content, providing guidelines for audience-adapted material.

Execution
1. pAGE 0
2. GUI DESIGN
3. WEBFLOW DEVELOPMENT

During execution, we deliver the first significant page, typically the home page, ensuring it aligns with your target audience and market strategy. We then apply style to wireframes through GUI design, focusing on visual aesthetics and maintaining consistency across the website. Our Webflow development process follows best practices, incorporating interactions, animations, and responsiveness across devices.

Finally, we present results on a test domain, with client involvement being crucial for a successful outcome.

LAUNCH & HANDOVER
1. TRAINING SESSION
2. PUBLISH WEBSITE

We provide your teams with comprehensive training sessions and Q&A opportunities to empower them to autonomously manage the content. We offer ongoing support, ensuring all necessary information for website updates is readily available, and we configure permissions within Webflow as needed.

Additionally, we seamlessly integrate the website with essential marketing tools such as Google Analytics, configure SEO optimizations, and seamlessly migrate and connect the desired domain. Leveraging Webflow's reliable hosting services, we ensure the website is published with optimal performance and reliability.

recherche
1. Exposé
2. Point de référence
3. recherche de données

Nos concepteurs UX cibleront les profils des utilisateurs et identifieront leurs besoins lors de l'utilisation de votre produit, en tenant compte de son utilité et de son efficacité de leur point de vue. La recherche sur les modèles de conception et les technologies les plus utilisées du secteur permet de tirer parti des connaissances et des pratiques des acteurs existants et de les comprendre. De plus, cela garantit que votre produit/design est spécifique et différent.

idéation
1. Évaluation de l'utilisateur
2. Présentation exécutive

Nous procéderons à un examen de l'expérience utilisateur afin de définir les exigences du produit en tenant compte des heuristiques d'utilisabilité établies sur le terrain afin de fournir une expérience utilisateur cohérente et fluide. Toutes les informations concernant les informations et les analyses seront résumées dans un rapport d'audit visuel et convaincant qui présente les principales conclusions de l'audit UX, les résultats rapides et les recommandations concernant les améliorations potentielles de votre produit.

Exécution
1. Guide de style
2. Interface utilisateur graphique

Ensemble, nous élaborerons le guide de style pour nous assurer que les différents éléments de l'interface visuelle de votre produit sont cohérents et cohérents. La réalisation d'un audit UX nous permet de résoudre les principaux problèmes rencontrés lors de l'exécution d'écrans finaux. De plus, toutes les recommandations issues de la reconnaissance des gains rapides seront conçues pour être mises en œuvre.

BACKLOG
1. PRODUCT BACKLOG
2. sprint backlog
3. sprint Execution

The product backlog is a list of business and project goals and contains what is forecasted to be developed by the development team, and maintained by the Product Owner. It is a living document, updated continuously, prioritized, and ordered by business value. It may also have product improvements, bugs, technical questions, and so on. Its purpose is mainly to have everything that is needed to reach the project’s Product Vision.

In this stage, we also create a sprint backlog, which is a list of tasks that need to be completed during each sprint. We prioritise the user stories for each sprint and ensure that the team knows what they need to work on.

With the sprint backlog in place, the development process finally starts. Working through the sprint backlog, and delivering small usable pieces of software frequently allows for continuous feedback and refinement, ensuring that the product is always on the right track.

BOOSTRAP
1. Ux assessment
2. high-level architecture
3. CI/CD workflow
4. Feature 0

In this stage, we put in place a briefing that includes the information gathered during the workshop with the team and stakeholders. It presents the vision and goals of the project and clarifies all necessary business requirements. This is also where a FAQ session relative to the nature of the project takes place.

The high-level architecture involves the development of the technical design, with the ideal balance between complexity and reach. This is where we identify external dependencies from third-party providers, such as Stripe, Facebook, Amazon, and so on.

We then start the CI/CD workflow which is the setup of the issue management tool, code repositories, continuous integration system, and development & staging environments. It’s followed by the setup of the code repo and automated test framework, the staging environment and production servers, as well as the continuous integration ecosystem (i.e. servers, deploy hooks)/continuous deployment.

Finally, in Feature 0 we deliver the first meaningful feature: a homepage, a login screen, part of the first dashboard. This step ensures that there is something demonstrable with the perception of value at the end of the phase.

WAVE 0
1.data model
2. Poc, mtp or mvp
3. viability assessment

With the Data Model, we provide the first baseline of the product’s evolutive data model. It identifies the main data entities and relationships and baselines the data sources and data stores (i.e. relational databases, document data stores, etc.). This step also consists of iterating the product concept and designing the first version of the data model.

Here’s when we present the Proof Of Concept (PoC), Minimal Testable Product (MTP), or Minimal Viable Product (MVP), and we deliver and deploy the first version of the product - even if that version is the implementation of a concept. This helps mitigate technical risks and test the main business premises for developing a market-ready version of the product through a viability assessment.

WAVE N
1. production increments
2. wave retrospective reviews

On the production increments step, we review technical and business risks and the impact of the PoC, MTP, or MVP on the initial premises or Wave 0. Here, we also identify reusable components from Wave 0 to Wave 1 (i.e. often PoCs are not reusable). This helps gather feedback about the first integrated model and assesses the product's viability before moving to Wave 1.

Finally, the wave retrospective reviews the product state, evaluates wave success against business goals, and identifies improvements. We then design goals for the next wave & prioritise features. Doing this allows the team to analyse the work that has been done in previous sprints and plan consciously what should be the next mountain to climb.

SCOPE REVIEW MEETING

We start with a Scope Review Meeting where we identify the main project goals, the domains to review, and which metrics we will assess, capturing info about Maintainability, Cyclomatic, Inheritance, Class, and others.

code review

We proceed to execute the Code Review by looking at Architecture to understand how the product is built, its principles, and its patterns.

TEST REVIEW

Now it's time for a Test Review, where we assess unit tests, code coverage, and test quality.

CODE QUALITY REVIEW

We follow up with a Code Quality Review, where we list all the issues and describe them to the fullest, identifying the critical ones and categorising them.

ASSESSMENT

We close the process with an Assessment stage where we list all recommended fixes and provide an estimate of the resources needed to implement them.

TECHNOLOGIES utilisées

Next.js
Next.js
Redux
Redux
Auth0 by Okta
Auth0 by Okta
AWS
AWS
React
React
Nest.js
Nest.js
Prisma
Prisma
PostgreSQL DB
PostgreSQL DB

Front-end technology used to build Aurora Analytica’s Geo Matrix Decision Engine.

Popular JavaScript library for managing application state in a predictable way, especially for complex applications with global state.

Used for CSV imports and exports from the data table.

Auth0 provides authentication and authorization services, and the Next.js SDK simplifies integrating those services into the application. This provides a platform for user authentication and management across the platform.

Used for deploying and hosting the platform on the web.

This enables the user to see a world map that reflects the results of the calculations in the Geo Matrix.

Back-end technology used to build Aurora Analytica’s Geo Matrix Decision Engine.

Acts as a layer of abstraction between the application code and the PostgreSQL database, allowing users to interact with the database of Aurora Analytica using a type-safe and intuitive API.

Used to build Aurora Analytica’s database. It’s an open-source object-relational database management system (DBMS) known for its reliability, scalability, and advanced features.

Écran du modèle de travail
modèle de travail et équipe

We implemented the Managed Project Working Model which included our Front and Back-end Developers, Designers, and Project Managers.

Front-end and Back-end Developers: Responsible for ensuring that the platform’s users can easily interact with it through the combination of design, technology, and programming the platform’s appearance, as well as taking care of debugging.

Designers: Carried out the visuals for the final MVP.

Project Managers: Defined the project requirements and outlined the scope of the project. Steering the project from concept to completion, the project manager ensured clear communication, managed resources and kept the development of the website on track.

principaux résultats

Ce projet a permis de mieux comprendre la personnalité du client et son interaction avec le service.

1

The Geo Matrix Decision Engine is able to empower CROs to strategise and predict outcomes virtually before real-world implementation.

2

CROs are able to optimize workflows across key touchpoints like requests (RFIs & RFPs) and scenario planning by analysing simulated scenarios.

Clutch logo

5,0

5/5 stars rating
Aurora Analytica project
Citant
Dropdown caret icon
Expliquez votre projet et réservez une réunion dès aujourd'hui.