...

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 chose 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.

ClinSpark was designed with the intent of users accessing the application and performing actions in a single browser sessions session (tab or window). Although, accessing ClinSpark through multiple concurrent sessions across tabs/windows can be beneficial in limited scenarios. However for For most use cases, it is not necessary.

...

If deciding to access ClinSpark across multiple active sessions, it’s strongly recommended to do so against the same study selection. For example, in one window accessing the details of Subject S0001 in Study ABC, and in another window accessing details of Subject S0002 also in Study ABC.

Depending Relying on the use case, using session management capabilities can be beneficial to certain workflows. However, for most users, it may is 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.

...

More details about study design import/export workflows can be reviewed here: ❗Notes on Study Design Export and Import

URLs

A typical ClinSpark URL convention is as follows:

...