| Table of Contents |
|---|
Onboarding Environment Lifecycle
Onboarding is the process leading up to a customer going live in Production (PROD). During this process, a series of short lived environments (also called ‘instances’) are created to support particular phases of onboarding. This guide describes these environments and clarifies their lifecycle.
Here is an overview of onboarding from an instance standpoint:
...
High Level Overview
Demo instance is for Foundry Health to demo ClinSpark in ‘branded’ environment to a potential customer.
...
Community Dev is a shared environment Foundry Health makes available to all customers, with the purpose to explore latest ClinSpark release functionality at any time. It is available for use during and after onboarding phases, but typically, customers explore ClinSpark in their own Demo and Sandbox instances first. More details are on our Community page.
Demo Environment
A Demo environment is first used by Foundry Health to demonstrate ClinSpark to a prospective customer. After the demo, it may also be provided to a customer prior to contact signing to explore ClinSpark functionality for a short period of time.
...
Demo environments do not receive IQ documentation.
Sandbox Pair
Once a customer signs a contract, the Sandbox pair is created. Depending customer preference, Sandbox can either be a brand new ‘empty’ instance pair or a clone of Demo instance in order to preserve data and configurations already familiar from the Demo instance.
...
Administration > Roles
Administration > Sites (Note that archived sites are not passed)
Administration > General Settings (except when this is integration-specific such as with SSO)
Administration > System Settings
Administration > Medical Dictionaries
Devices
Labs, Panels, Lab Tests
Barcode Label Configurations
Migration
A dedicated Migration instance is created for customers whose source database will be migrated to ClinSpark. This instance exists solely for the purpose of presenting the output of the the migration logic for review by the customer. It is a single instance, and only the main instance is provided to support this activity.
...
All Volunteers
Archived studies, created to support historical study participation
These Volunteer > Configure elements:
...
VAL (Validation) Pair
VAL is a formal environment provided to support a customer’s validation activities. This environment will be produced with the general configuration from the source instance selected by the customer PLUS the migration output. Note that this is effectively a dry run of the same mechanism used to create PROD.
...
VAL environments receive IQ documentation.
PROD (Production) Pair
These are customer production instances. After “go-live” these instances remain as is until upgrading.
PROD environments receive IQ documentation.
PROD “go-live” steps
Customer: provide FH with final source DB dump/files and any other related files.
FH: extract configuration from the source ClinSpark instance agreed upon by the customer
FH: run the migration program to produce the new ClinSpark instance
FH: populate, configure, review the final PROD Main instance
FH: provide formal IQ documentation
Customer: perform final QC check