...
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.
| Info |
|---|
ClinSpark was designed with the intent of users accessing the application and performing actions in a single browser |
...
session (tab or window). |
...
Accessing ClinSpark through multiple concurrent sessions across tabs/windows can be beneficial only in limited scenarios. |
...
For most use cases, it is not necessary or recommended. |
Due to this, there There may be an undesirable user experience in ClinSpark if performing actions across multiple active sessions. For example, if in one window a user is accessing a subject record in Study ABC, but in another window decide to switch to Study XYZ and complete another action. When returning to the first window accessing Study ABC, actions taken will no longer be contextual to that study, since the last action taken by that user in the application was in Study XYZ. This challenge can be extended in situations where there may be device integrations in use, where data collection workflows may not yield expected results with device data being properly collected into study forms.
If deciding to access ClinSpark across multiple active sessions, it’s strongly recommended to only 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 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. |
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:
...
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 IQVIA 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.
...