Build Environments

Connect Care uses Epic Systems Corporation clinical information system (CIS) software, with multiple instances of the software deployed to allow testing, training and development activities to be separated from clinical use of the production CIS. Each instance is referred to as an "Environment". Known outages will be indicated next to relevant environment titles below. Production environment status is updated at status.connect-care.ca.

Below is a non-exhaustive list of the AHS instances of Epic environments most commonly used by Builders. Application configuration is generally maintained in POC, migrated to TST and PRD using Data Couriers.

POC - Proof of Concept Build Testing

• Use: Build and configuration work, conducted in absence of real patient data

• Category: Production support

• Refreshed: Persistent

• System Interfaces: None

• Users: IT, CMIO Physician Leads, Builders

• Requirements: Epic Proficiency

• Logon: personal and model users

• Patient data: demo patients only

• Privacy audits: None

TST - Test

• Use: integration & interface testing, application testing, end user acceptance testing; last point for build test with real patient data before migration to PRD.

• Category: Production support

• Refreshed: Persistent

• System Interfaces: Selected upstream and downstream (e.g., Netcare, Transfusion, etc.)

• Users: POC Users plus AHS Analytics users, Integrated Area Testing, Testing Validators

• Requirements: Epic Certification, Epic Fundamentals training

• Logon: personal and model users

• Patient data: demo patients only

• Privacy audits: None

PRD - Production

• Use: Primary working environment for clinical information system use in clinical settings

• Refreshed: Persistent

• Category: Production

• System Interfaces: All upstream and downstream systems (Netcare, Transfusion, etc.)

• Users: All authorized Connect Care users

• Requirements: Basic Training, EUPA, Personalization

• Logons: Personal only

• Patient data: real patients

• Privacy audits: Full, with automated checks for potential inappropriate access

REL - Conversion Testing

• Use: testing and validating data converted from legacy systems.

• Refreshed: Monthly from POC

• Category: Non-production

• System Interfaces: Selected upstream legacy CIS, EMR and other source systems as needed for testing

• Users: Configuration Analysts, Validating Clinicians and Lab SMEs

• Requirements: Epic Proficiency

• Logon: personal accounts

• Patient data: demo patients only

• Privacy audits: None

SBX - Sandbox

• Use: testing workflows, scenarios, information pathways in support of build and configuration activities

• Refreshed: Daily from POC

• Category: Non-production

• System Interfaces: None

• Users: IT, CMIO Physician Leads, Builders, Trainers, Power Users

• Requirements: Epic Proficiency

• Logon: personal and model users

• Patient data: demo patients only

• Privacy audits: None

MPE - Multipurpose

• Use: testing workflows, scenarios, information pathways in support of build and configuration activities

• Refreshed: Monthly from POC

• Category: Production support

• System Interfaces: None

• Users: IT, CMIO Physician Leads, Builders, Trainers, Power Users

• Requirements: Epic Proficiency

• Logon: personal and model users

• Patient data: demo patients only

• Privacy audits: None

SUP - Support

• Use: Support Team to troubleshoot problem reports that can only be investigated with "real" patient files and contexts; limited use for exploration of possible build/configuration issues prior to move to production.

• Refreshed: Nightly from PRD

• Category: Production support

• System Interfaces: None

• Users: Information Services support personnel and approved builders

• Requirements: IT or acceptable build certifications

• Logons: personal accounts

• Patient data: real patients, one day off-set

• Privacy audits: Full, with automated checks for potentially inappropriate access to patient data

ACE - Training

• Use: virtual and in-person training

• Refreshed: Nightly from PREP

• Category: Training

• System Interfaces: None

• Users: All users participating in training sessions

• Requirements: None

• Logon: model accounts

• Patient data: demo patients only

• Privacy audits: None

EXAM - Proficiency

• Use: training proficiency examination

• Refreshed: Nightly from PREP

• Category: Training

• System Interfaces: None

• Users: All users participating in training sessions

• Requirements: None

• Logon: model accounts

• Patient data: demo patients only

• Privacy audits: None

PLY - Learning

• Use: practice after basic training of users

• Refreshed: Nightly from PREP

• Category: Training

• System Interfaces: None

• Users: All users with DMO access plus all users with basic training

• Requirements: Basic Training

• Logon: model accounts

• Privacy audits: None

DMO - Demonstration

• Use: analysts, informaticians and clinician leaders to demonstrate functionality prior to release of training environments (deprecated at training, do not use)

• Refreshed: Weekly (Mondays) from POC

• Category: Training

• System Interfaces: None

• Users: IT, CMIO Physician Leads, CKCM, AHS Analytics, Human Factors, HIM, HPSP, Trainers, Power Users

• Requirements: Epic Fundamentals Training

• Logon: model users

• Patient data: demo patients only

• Privacy audits: None

MST - Master Training

• Use: training team for curriculum development and testing.

• Refreshed: Persistent

• Category: Training

• System Interfaces: None

• Users: Senior and Area Trainers

• Requirements: Epic Proficiency

• Logon: model accounts

• Patient data: demo patients only

• Privacy audits: None