-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
86 additions
and
80 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,46 @@ | ||
# Dynamic Visualization for Clinical Insights (DaVinci) | ||
|
||
### What is DaVinci? | ||
### ABSTRACT | ||
DaVinci is a dynamic, modular framework designed for interactive data exploration and visualization in clinical | ||
research. It is particularly intended to support exploratory biomarker analysis and safety review during study conduct. | ||
The framework's modules function as building blocks that can be combined to create customized R/Shiny | ||
applications, tailored to specific clinical trial and research project needs. DaVinci offers a variety of functionalities, | ||
including the ability to plot, for example, heatmaps, waterfall, and eDISH plots, as well as generate tables and listings. | ||
Currently, it boasts twelve output modules, with ongoing development to expand its capabilities. In a move towards | ||
community-driven growth and refinement, DaVinci has been open-sourced recently. | ||
|
||
DaVinci provides tools to review, aggregate and visualize data to develop and deliver safe and effective treatments for patients. Instead of creating entire R/Shiny applications, DaVinci provides individual modules. Modules are functional building blocks that can be linked together into customized apps. This customization enables App Creators to build their own app according to trial-specific needs without deep R knowledge. The concept of developing loosely coupled, functional units and composing them into a larger application is subsequently referred to as modular approach. | ||
### INTRODUCTION | ||
Successful conduct of clinical trials heavily relies on regular data reviews, in order to ensure patient safety, monitor | ||
data flow and recruitment, guarantee protocol compliance, assess data quality, etc. Moreover, regular data reviews | ||
are also meant to provide an opportunity for exploratory parameter analysis allowing for the identification of trends, | ||
patterns, and relationships within the data that may not be immediately apparent. | ||
Compared to extensive static outputs like tables, listings, and figures in PDF format, such data review procedures can | ||
be greatly enhanced by utilizing interactive visualization tools. This is where R/Shiny applications have proven | ||
excellent means for reviewers to dive deep into the study data through dynamic plots, along with real-time data | ||
access. | ||
|
||
### More information can be found on the [DaVinci website](https://boehringer-ingelheim.github.io/davinci/) | ||
### THE MODULAR APPROACH | ||
In a naive approach of using R/Shiny for interactive data visualization, one can create a comprehensive stand-alone | ||
application, that satisfies the needs of as many studies as possible. It has been observed, however, that these stand alone apps quickly become unwieldy and miss user expectations. Moreover, some minor trial-specific adjustments | ||
are impossible to be implemented without disrupting functionality for other trials. Therefore, instead of creating | ||
universal stand-alone apps, DaVinci intends to provide individual modules. R/Shiny modules serve as functional | ||
building blocks that can be easily linked together into customized apps. This customization enables trial teams to | ||
quickly build trial-specific but lean apps without extensive programming knowledge. The concept of developing | ||
loosely coupled, functional units and composing them into a larger application is referred to as modular approach | ||
|
||
![](quarto/images/building_blocks.png){fig-align="center"} | ||
|
||
The figure above schematically demonstrates the modular approach by means of building blocks. In this analogy, the building | ||
blocks symbolize the different modules. Depending on the use case, one might choose and assemble the building blocks | ||
to build a helicopter, a motorcycle, or a pick-up truck. Similarly, the trial team will develop their trial-specific | ||
application by choosing and assembling the modules based on the team’s unique requirements. | ||
|
||
### CONCLUSION | ||
In conclusion, DaVinci provides a dynamic, modular framework for interactive data exploration and visualization in the | ||
field of clinical research. Its modular design allows for the creation of lean, trial-specific applications, making this | ||
framework flexible and versatile. One of DaVinci's key features is its drill-down functionality, which is especially useful | ||
for data exploration and review during study conduct. It also integrates with modules from other modular open-source | ||
frameworks like Teal, further diversifying its range of functionalities. By making DaVinci open-source on GitHub, it | ||
opens the door for improvements and growth from the community. | ||
|
||
#### More information can be found on the [DaVinci website](https://boehringer-ingelheim.github.io/davinci/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,49 +1,14 @@ | ||
/***************************************/ | ||
/***** flipcard settings *****/ | ||
/***************************************/ | ||
.flip-card { | ||
background-color: transparent; | ||
width: 150px; | ||
height: 150px; | ||
perspective: 1000px; /* required for 3D effect */ | ||
} | ||
|
||
/* This container is needed to position the front and back side */ | ||
.flip-card-inner { | ||
position: relative; | ||
width: 100%; | ||
height: 100%; | ||
text-align: center; | ||
transition: transform 0.8s; | ||
transform-style: preserve-3d; | ||
} | ||
|
||
/* Do an horizontal flip when you move the mouse over the flip box container */ | ||
.flip-card:hover .flip-card-inner { | ||
transform: rotateY(180deg); | ||
} | ||
|
||
/* Position the front and back side */ | ||
.flip-card-front, .flip-card-back { | ||
position: absolute; | ||
width: 100%; | ||
height: 100%; | ||
display: flex; | ||
justify-content: center; | ||
align-items: center; | ||
-webkit-backface-visibility: hidden; /* Safari */ | ||
backface-visibility: hidden; | ||
} | ||
|
||
/* Style the front side (fallback if image is missing) */ | ||
.flip-card-front { | ||
background-color: #E5E3DE;//white; | ||
color: black; | ||
} | ||
|
||
/* Style the back side */ | ||
.flip-card-back { | ||
background-color: #E5E3DE;//white; | ||
color: black; | ||
transform: rotateY(180deg); | ||
} | ||
.button { | ||
width: 15%; | ||
font: bold 14px Arial; | ||
text-decoration: none; | ||
background-color: #08312a; | ||
color: #00E47C; | ||
margin: 5px; | ||
padding: 10px 14px 10px 14px; | ||
border-top: 1px solid #002b36; | ||
border-right: 2px solid #002b36; | ||
border-bottom: 2px solid #002b36; | ||
border-left: 1px solid #002b36; | ||
border-radius: 4px; | ||
} |