About myAvatar environments

myAvatar installations should have four separate environments. Each of the environments should have their own OS, Caché instance, and set of Namespace(s) for each solution.This database architecture supports a test (UAT) environment and a log-in page with a drop-down menu to ensure users access the correct environment.

Each environment must exist on its own server or virtual server. You can use a virtual server for the SANDBOX, BUILD and UAT environments since these do not require extensive server capacities. The PRODUCTION environment may also reside on a VM, but you will need to work with Netsmart to define the recommended server resources.

Select each section for more detailed information about each type of environment or system code:

► SANDBOX (SBOX System Code) 

• The SANDBOX environment is used strictly for users to ‘play’ in the myAvatar application in order to become familiar with myAvatar.
• SANDBOX is pre-populated with sample data.
• This environment is not active for interoperable transactions such as HL7 or CCD exchange.
• Modeling is not intended to be performed within SANDBOX. If your agency wishes to model within this environment, the envelopes must first be imported into the BUILD environment before being exported to import into either UAT or PRODUCTION. This is to ensure that the numbering never gets out of sync.

► BUILD (BLD System Code) 

• The BUILD environment is used to perform file build and modeling.
• The ability to create a new client (e.g. filing admissions, call intakes and pre-admissions) is disabled within this environment.
• The BUILD environment will always remain “clean” (i.e. without client data) and can be used to overwrite the UAT environment during initial conversion testing.
• It is recommended to perform all file build first in BUILD in order to overwrite UAT. After file build has been completed, User Acceptance Testing can begin. Further copies of BUILD into UAT will overwrite any testing scenarios created in UAT.
• If modeling is still being developed in BUILD, it is recommended that these envelopes be exported out of BUILD and then imported into UAT, rather than copy over UAT with BUILD.
• The BUILD environment will also be where additional modeling can be done after Go-Live. All envelopes will be exported from BUILD and imported into PRODUCTION Post Go Live.

  File Build 

  File build is done within the BUILD environment. This includes RADplus modeling, Site Specific Tab Modeling, Form Designing, Dictionary builds and creation of Report Definitions. The BUILD environment restricts the creation of new clients. Therefore, you can can choose to perform your modeling in the SANDBOX environment first. Once completed, all modeled envelopes, site specific tab modeling envelopes, report definitions and form design envelopes should be imported into the BUILD environment first before importing them into UAT or PRODUCTION. Modeling will be disabled in both the UAT and PRODUCTION environments.

  Pre-Go Live Testing Process 

  The BUILD environment will contain all of the file build and will remain a clean system. BUILD will be copied into UAT during initial conversion testing. UAT will also be used for testing purposes. If the Client prefers to separate their training environment from their testing environment, additional UAT environments can also be created. As Go-Live approaches, BUILD will be copied into the PRODUCTION environment in order for true conversion testing. This may occur several times until all testing has been completed. Since BUILD will not contain any client information, this is the appropriate environment to copy into PRODUCTION prior to Go Live.

► UAT (UAT System Code) 

• The UAT environment, although created by Netsmart’s System Administration team, contains no actual myAvatar software at the time of initial software installation.
• This environment will used for User Acceptance Testing before the Client is live with the application. Copies of the BUILD environment will overwrite this system during initial conversion testing but final conversion testing will be performed in PRODUCTION (see below for Post Go-Live Environments). It is recommended to perform all file build first in BUILD in order to overwrite UAT. After file build has been completed, User Acceptance Testing can begin. Further copies of BUILD into UAT will overwrite any testing scenarios created in UAT.
• Functionality such as modeling, site specific tab modeling and form designer will be disabled in this environment. The only modeling functionality enabled will be the ability to import envelopes created in the BUILD environment.
• This environment can be configured to test interoperable transactions such as HL7 or CCD exchange and connect with CareConnect or ProviderConnect.

► PRODUCTION (LIVE System Code) 

• The PRODUCTION environment, although created by Netsmart’s System Administration team, contains no actual Avatar software at the time of initial software installation. PRODUCTION will not be utilized until the final conversion testing.
• A copy of the BUILD environment will be copied into PRODUCTION so all of the file build will be present before conversion testing. Each conversion test will require another copy of BUILD into PRODUCTION.
• Functionality such as modeling, site specific tab modeling and form designer will be disabled in this environment. The only modeling functionality enabled will be the ability to import envelopes created in the BUILD environment. 
• Once the Client is live, no more copies into PRODUCTION will be performed. The PRODUCTION environment will house all live data upon Go Live.

Note: All updates (product updates, monthly and quarterly releases) must be loaded into each separate environment.