Outbound Configurations

Outbound configurations can be imported from a source RALS™ SYSTEM into the destination RALS™ SYSTEM.

Jump to a heading on this page:
Select Source
Select Data
Review Import
General Rules of Migration Import

Select Source

When importing outbound configurations, the following fields allow the destination RALS™ SYSTEM to connect to the source RALS™ SYSTEM:

When importing outbound configurations, you must select the following for new configurations:

Select Data

After the destination RALS™ SYSTEM has connected to the source RALS™ SYSTEM, the outbound configurations available for import will be displayed in a table. You can filter, sort, select, and de-select outbound configurations in this table. Selected outbound configurations will be processed for import.

Review Import

Prior to import, you can review outbound configurations import information, including:

All selected outbound configurations, including configurations that will be imported and configurations that will not be imported, will be displayed in a table for your reference.

General Rules of Migration Import

During the import, the RALS™ SYSTEM compares the outbound configuration between the source and destination systems. If any data is missing on the destination system, the RALS™ SYSTEM creates it during import. This data encompasses parameters, specimen types, test types, and panels. The name comparisons for these elements are case-insensitive. Edited outbound configurations are updated with the values from the source system, but the institution and location assignment are not changed.

When a parameter, specimen type, test type or panel is only on the destination system and not on the source system, then the RALS™ SYSTEM will remove it from the outbound configuration on the destination system.

Outbound configurations added via import are not assigned to any institution or default, regardless of assignments present on the source system.

In specific scenarios, outbound configurations will not be migrated. If there is a match on the outbound configuration name between the source system and the destination system, but there’s no match on the device type or interface type, then the configuration will not be migrated. The outbound migration of Configurable Device Drivers is not currently supported. If a user attempts to import a configuration that cannot be imported, then an error will be included in the debug log.