| Table of Contents |
|---|
Introduction
ClinSpark is a best in class, standards based, CDISC ODM certified eSource system and is offered exclusively via Software as a Service (SaaS) hosted on AWS and uses their MySQL compatible Relational Database System (RDS) - Aurora. It empowers nearly all clinical data management activities for early phase clinical research sites. ClinSpark leverages device and systems connectivity while employing a mobile-first design approach. ClinSpark is intended for all persons involved with the success of a clinical trial including bedside data collectors, study monitors, clinical research coordinators, and lab technicians.
Accessing ClinSpark
ClinSpark is designed and tested for use against the latest stable version of Google Chrome. However, we have seen ClinSpark successfully used on other Chromium based web browsers such as the latest version of Microsoft Edge.
...
More details about accessing ClinSpark in various contexts can be reviewed in this article: Computing Devices
Browser Extensions
Modern web browsers offer a capability for users to install programs called ‘Extensions’. These can be manually installed by users, or automatically by IT/IS organizations at customer sites in order to change the browsers default functionality. Most of the time, these extensions are useful and modify the browser as a convenience for the user. Here are some examples:
...
Some extensions may be able to be safely disabled when using ClinSpark, or, rely on configurations to ‘whitelist' the ClinSpark application from being impacted by their features. Customers that have questions about this topic are encouraged to reach out to our support team for further information.
Mobile Devices
Mobile web browsers are optimized to display content most effectively on smaller screens and portable devices. Mobile interfaces also vary across device, for example, making use of gestures and touch-screen controls. While mobile browsers are becoming increasingly more sophisticated, they still do not fully match the user experience as their desktop counterparts.
ClinSpark is developed to be mobile friendly, using the latest web technologies and principles such as responsive design. The mobile ClinSpark experience may vary depending on the intended use of the application.
Session Management
Modern web applications such as ClinSpark rely on session management capabilities to manage the exchange of requests and responses between users and apps. Whenever a user visits ClinSpark via web browser (such as Google Chrome), a session is established which contributes to the overall user experience. Additionally, modern browsers allow support the use of multiple tabs or windows. What this means is if a user choses to access ClinSpark across more than one active browser session in multiple tabs/windows, the user experience may vary depending on the actions that are taken between each active session.
...
Depending on the use case, using session management can be beneficial to certain workflows. However for most users, it may not be necessary.
Environments
ClinSpark is provided to customers in an environment that contains an instance pair often referred to as “Production” (PROD) and “Test” (TEST). PROD and TEST instances are referred this way from the perspective of study design, not from the perspective of systems lifecycle.
...
| Info |
|---|
Once in production, the TEST instance is also intended to be used for system orientation or study-specific user training. Other environments (e.g. Sandbox, Validation) will be retired. Instances solely for training are not provided. |
URLs
A typical ClinSpark URL convention is as follows:
...
Other URL conventions may be followed for lower environments, such as Validation or Sandbox environments, which are used during onboarding and upgrade periods.
Other environments
Foundry Health may provide customers with temporary environments to support onboarding, user acceptance testing, and/or validation testing. These temporary environments would typically follow the same previously described structure of “production” and “test” instances for CRF design and study activity testing.