Atellica LIS Interface
Atellica LIS Interface
Atellica CI Analyzer
Configuration Instructions – System
LIS Interface
siemens-healthineers.com
Document Version
Siemens Healthcare GmbH reserves the right to change its products and services at any time.
In addition, manuals are subject to change without notice. The hard copy documents correspond to the version
at the time of system delivery and/or printout. Versions to hard copy documentation are not automatically
distributed.
Please contact your local Siemens Healthineers office to order a current version or refer to our website https://
www.siemens-healthineers.com.
Disclaimer
Siemens Healthcare GmbH provides this documentation “as is” without the assumption of any liability under
any theory of law.
The content described herein shall be used by qualified personnel who are employed by Siemens Healthcare
GmbH or one of its affiliates or who are otherwise authorized by Siemens Healthcare GmbH or its affiliates to
use such documents.
Assemblers and other persons who are not employed by or otherwise directly affiliated with or authorized by
Siemens Healthcare GmbH or one of its affiliates are not entitled to use this documentation without prior
written authority.
Copyright
"© Siemens Healthineers, 2022" refers to the copyright of a Siemens Healthineers entity such as:
1 Preparation 4
1.1 General Information 4
1.2 Safety 4
2 Third-Party LIS 5
2.1 Configure for an ASTM LIS 5
2.2 Configure for an HL7 LIS 8
1 Preparation
1.1 General Information
This document provides instructions to configure the Atellica Solution or the Atellica CI Analyzer for LIS.
1.2 Safety
For general safety information, refer to the Safety section of the CB-DOC.
WARNING
◆ Do not handle biohazardous materials without wearing personal protective equipment and observing
universal precautions.
WARNING
Carriers on the Atellica Magline Transport generate strong magnetic fields that can interfere
with cardiac medical implants.
Use extreme caution while interacting with sample carriers installed on Atellica Magline Transport.
◆ Do not position pacemakers or other implanted medical devices closer than 7.5 cm (3 inches) from
the Atellica Magline Transport.
2 Third-Party LIS
2.1 Configure for an ASTM LIS
✓ Refer to the Site Survey for customer-specific information.
2 Along the top of the LIS Configuration screen, configure the following general options. For settings not
defined here, base the configuration on the account requirements.
Field Setting
Protocol ASTM
3 Click the Application Layer subtab and set the following, then click Save. For settings not defined here,
base the configuration on the account requirements.
Field Setting
4 Click the Data Link Layer subtab and set the following, then click Save. For settings not defined here, base
the configuration on the account requirements.
Field Setting
Query Timeout 8
No Response Timeout 15
Interframe Timeout 30
Busy Timeout 10
5 Click the Physical Layer subtab and set the following, then click Save. For settings not defined here, base
the configuration on the account requirements.
Field Setting
6 Verify that the LIS is now connected. If the LIS is not connected, click the User Interface LIS Connection
Status icon and then click Connect to LIS .
If the LIS issue was not resolved following these instructions, escalate as necessary following the local
escalation process, and include the following information:
2 Along the top of the LIS Configuration screen, configure the following general options. For settings not
defined here, base the configuration on the account requirements.
Field Setting
Protocol HL7
3 Click the Application Layer subtab and set the following, then click Save. For settings not defined here,
base the configuration on the account requirements.
Field Setting
Field Setting
4 Click the Data Link Layer subtab and set the following, then click Save. For settings not defined here, base
the configuration on the account requirements.
Field Setting
MSG_TimeoutInSeconds section
Query Timeout 8
5 Click the Physical Layer subtab and set the following, then click Save. For settings not defined here, base
the configuration on the account requirements.
The port settings below are the defaults. These should not be changed unless the customer settings are
different. Refer to the Site Survey for site-specific information.
Field Setting
a. Confirm that the port start and end settings match the instrument port specified in the Physical Layer
settings as well as the site survey.
– or –
c. Confirm the port start and port end settings to match the instrument port specified in the Physical Layer
settings as well as the site survey.
Field Setting
Protocol TCP
Field Setting
Action Allow
Service LIS_IN
Log Always
Field Setting
Enable Selected
Interfaces WAN1
11 On the PCC, navigate to the Windows firewall inbound rules to verify attributes for LIS-IN:
c. In the Windows Defender Firewall with Advanced Security dialog box, click Inbound Rules.
d. Scroll down the list and click LIS-IN - {Windows Registry Key}.
e. Click Properties.
f. In the Properties dialog box, confirm the following settings on each tab and then click OK.
→ General tab
Field Setting
General section
Enabled Selected
Action
Field Setting
Protocol TCP
Field Setting
Programs section
Compartments section
Scope tab
Field Setting
Field Setting
Exceptions section
Skip this rule for connections from these users Not selected
Field Setting
Exceptions section
Skip this rule for connections from these users Not selected
Field Setting
Skip this rule for connections from these computers Not selected
Advanced tab
Field Setting
Profiles section
Domain Selected
Private Selected
Public Selected
If the LIS is not connected, click the User Interface LIS Connection Status icon and then click Connect
to LIS .
◆ Escalate as necessary following the local escalation process. Provide the following information:
These settings provide a baseline to ensure that all Atellica Solution or Atellica CI Analyzer implementations
start with the recommended settings. Baselining the configuration also prevents known issues that have been
resolved or mitigated through escalation and testing.
Provide the settings below. Replace the information between < > with site-specific settings.
Field Value
Type Instrument
Position on Automation <Inventory settings will not work if this is not completed cor‐
rectly>
This value is also used in part to configure the submodules.
Status On
Checker No
Direct Download No
Start Yes
Field Value
Ensure the settings are defined to meet customer expectations. The settings listed here are the default settings.
Reject Result by QC No
Disable test on QC No
QC prefix (empty)
Targeting Yes
Automatic Internal Download For Atellica CI Analyzer: Set this parameter to No.
For Atellica Solution: Set this parameter as requested
by the customer. For additional information, refer to
the DMS CB-DOC, DCIN-I00.812.46 Atellica Solution
Connectivity Guide).
Note: Ensure this setting is adjusted when con‐
necting the instrument to the automation.
Enable/Disable Tests on Sub-Modules Yes (When tests split by sample type exist)
RX timeout 30
TX response timeout 15
Charset ISO-8859-1
Hw flow 0
Numbers of retry 6
OID position
PID position
Sw flow 0
Field Value
Class ATELLICASHC
Type Instrument
Bit Stop
Parity
Field Value
Bit Data
Bit Rate
Position on Automation <Last three digits from the main module, prefixed by a
unique value for each submodule>
For example, if main instrument used 040, submodule 1
could use 11040 and submodule 2 could use 22040.
Status On
Checker No
Direct Download No
Start No
If this is set to yes and there is an attempt to start, you
will see port errors.
QC Lifetime (hours) 5
QC expiration date
Listener address
Site code
Submodule Options
Note that in the Instrument Options Editor, the Main Instrument must contain the main module name for the
submodule instruments.
The settings below are default settings and represent an example of a main instrument with two submodules.
Automatic Flags No
Disable test on QC No
Perform rerun No
QC prefix (empty)
Reject Results by QC No
Targeting No
Replicates Management No
• Refer to the Atellica Solution or Atellica CI Analyzer Site Survey for customer-specific information.
• Refer to the LIS Communication Guide in the Document Library for detailed information about each
parameter.
1 In the Atellica system software, navigate to Setup > System Configuration > LIS Configuration.
2 Along the top of the LIS Configuration screen, configure the following general options. For settings not
defined here, base the configuration on the account requirements.
Field Setting
Protocol ASTM
3 Click the Application Layer subtab and set the following, then click Save. For settings not defined here,
base the configuration on the account requirements.
Field Setting
Send All Patient Results and Additional Data Select if the initial result of an
instrument-ordered repeat is
to be sent to DMS
Atellica Solution automatically
sends all preliminary and final
results, except results on hold,
to the LIS. For example: This is
needed to generate the pre‐
liminary result(s) in those
cases where the Atellica ana‐
lyzer was not able to perform
the auto dilution.
Field Setting
Notify LIS for non-transmitted orders: Deleted or Moved to Histor‐ Not selected
ical
Notify LIS for non-transmitted orders: Deleted or Moved to Histor‐ Not selected
ical
Field Setting
Send Scanned Date and Time for Result Set as required by the custom‐
er’s workflow
Send Test Aspirated Date and Time Set as required by the custom‐
er’s workflow
• When the Transmit Results by Sample option is selected, the Atellica system transmits results in
one message.
• When the Transmit Results by Sample option is Not selected, the Atellica system transmits results
as each test is resulted.
Before you clear the Transmit Results by Sample option, evaluate and adjust any existing result
management configurations. For example, if Transmit Results by Sample is not selected, ISE results
may be transmitted prior to HIL results. To prevent this, the recommendation is to enable the Waiting
for HIL option.
4 Click the Data Link Layer subtab and set the following, then click Save. For settings not defined here, base
the configuration on the account requirements.
Field Setting
Query Timeout 30
No Response Timeout 15
Field Setting
Interframe Timeout 30
Busy Timeout 10
5 Click the Physical Layer subtab and set the following, then click Save. For settings not defined here, base
the configuration on the account requirements.
Field Setting
6 In DMS, enable the connection to the Atellica Solution or to the Atellica CI Analyzer.
7 On the Atellica system software, click the LIS icon and then click Online.
8 Confirm that the connection is established:
9 On the Atellica software, go to Setup > System Configuration > Patient Results Management.
10 Configure HIL ordering as required by the laboratory and then click Save.
If the customer prefers that results are held until HIL is available:
a. Set the Mode option to Review by Exception.
b. Under Hold Results by Exception, select the Waiting for HIL flag for the Hold Results option.
11 Reconnect the LIS and confirm that a stable connection is made between DMS and the Atellica Solution or
the Atellica CI Analyzer.
The purpose of this configuration is to allow samples to be sent to a specific analyzer (i.e., submodule) on an
Atellica Solution line.
Example Scenario:
A sample runs routinely on an Atellica analyzer; however, the result is off and so the sample should be run
again. If targeting is configured, the customer can set up the repeat in LIS, ADM, or DMS and target a specific
Atellica analyzer (regardless of whether it is the same analyzer or a different one). When the sample is
subsequently returned to the automation track, it is routed directly to the targeted analyzer for processing.
Targeting is implemented through the assignment of a unique Position on Automation code to each Atellica
line (main instrument) that defines that line's location on the automation system.
Each analyzer (submodule) in the Atellica line is assigned its own code, and the final three digits of the
submodule code match the Position on Automation code for the main instrument.
For example, assume a site has two Atellica lines connected to an automation system in positions 010 and
011. The table below shows example Position on Automation codes for the main instruments and for the
associated submodules.
When DMS is configured as described here, DMS receives the instrument ID from the LIS message, converts
the ID into the analyzer serial number (SN) that is defined in DMS, then sends the message to automation.
The automation system uses the SN to target the specific instrument.
✓ Prerequisite: The customer's DMS LIS must support targeting in order for this feature to function.
1 On the main instrument configuration screen, ensure that the following fields are configured as defined
here:
Field Value
Targeting Yes
Fig. 28: EXAMPLE ONLY: Serial number and position on automation settings for main instrument
Field Value
Targeting No
Position on Automation <unique code; final three digits match the position
of the Atellica line on automation>
Fig. 30: EXAMPLE ONLY: Serial number and position on automation settings for analyzer
Fig. 31: EXAMPLE ONLY: Targeting and main instrument settings for analyzer
Fig. 32: EXAMPLE ONLY: Two Atellica Solution lines with targeted analyzers
The test enable/disable option must be implemented by a trained and experienced DMS specialist.
Familiarize yourself with the entire procedure before you start a configuration, as there are multiple
configuration-dependent options.
It is critical that you discuss this feature and its ramifications with the customer before you go onsite for the
upgrade. You should ensure that they want this feature and are aware of all the necessary configuration
requirements. Some recommended areas to explore with the customer are:
• Explain the requirement to split tests based on sample type, if this configuration is not already in use.
• If test splitting is not already in place, explain that you must remove all sample data from the DMS.
• Explain that all DMS tests must convert to the new sample type format.
• Explain that the QC may need to have a stop and start point, depending on the customer configuration.
The customer should have a strategy to maintain their QC integrity if it is impacted.
• If ADM is not present, the LIS provider must provide new tests split by sample type. In this case additional
time will be needed to ensure coordination with the LIS administrator and possibly the LIS company.
Configuration Notes
• For systems that do not have a defined test for each sample type, you must edit or delete all tests.
• You must remove all sample data from the DMS database in order to ensure database continuity.
• For ease of future troubleshooting, it is recommended that all tests be assigned a suffix that is specific to
the sample type. For example, BUN_S for serum or BUN_U for urine. These changes might also be required
for the HIL tests.
• Refer to the DMS CB-DOC for additional information, especially the following documents:
1 Back up DMS. Refer to the appropriate DMS service manual in the DMS CB-DOC.
This backup should not be used after the tests are split by sample type. This backup will restore the
system to its status before the tests were split.
2 On the PuTTY console, export the DMS test configuration tables. Refer to DCIN-I00.816.06 / Test Table
Loading in the DMS CB-DOC.
c. In the loadtest.csv file, confirm that the Instr-MatCode field under Sample Type to Instrument is
correctly defined for each split test.
In the Instr-MatCode field, you must provide the code that the instrument expects in the ASTM
message. As a result, mapped sample-type codes cannot be used.
Atellica Solution and the Atellica CI Analyzer use whole words, such as serum and plasma.
d. Make sure that all other sample type columns are empty.
e. For ease of troubleshooting, make sure that the assays that will not be split are also assigned an
appropriate suffix. Refer to DCIN-I00.816.06 / Test Table Loading in the DMS CB-DOC.
WARNING
The following commands remove all sample data from the DMS database in order to prepare the
system for splitting tests by sample type.
This action can be reversed only by restoring the database from the backup. However, the
backup will overwrite any tests you renamed.
◆ Perform this step only if you intend to change or delete test names and there are orders or results
in the database with the test names.
a. On the PuTTY console, use the root user account to log into the system.
c. Confirm that all communication with the LIS and instruments has stopped.
d. Type the following commands. You must enter the commands separately in the sequence provided
here. These commands are case sensitive, and the spaces must be included as shown.
chmod 0755 /var/nemo/application/etc/sysconfig/cleanMy.sh
/var/nemo/application/etc/sysconfig/cleanMy.sh -ophd
In all cases, the cleanMy.sh command sends information to the screen. This behavior is normal.
5 Use the Truncate setting to import the updated test table. This removes old test names at the same time
as the new names are added. Refer to DCIN-I00.816.06 / Test Table Loading in the DMS CB-DOC.
Examine the Test Setup and Test on Instrument screens to ensure that all customer tests are represented
and that the material needed for each instrument class is present. See the example below.
7 Once you have confirmed that the test codes were successfully loaded in DMS, send the test map
configuration. Refer to After successfully loading and checking the test codes in DMS, send the test map
configuration to SMS. Refer to DCIN-I00.816.06 / Test Table Loading in the DMS CB-DOC.
8 If applicable, review decision rules to ensure that the rules use the correct test names.
9 If applicable, review GEM rules to ensure that the rules use the correct test names. Refer to DCIN-
I00.843.06 / Event Configuration Using the General Event Manager (GEM) in the DMS CB-DOC.
10 Review batch test entries and modify them as needed to accommodate the new test names. Refer to DCIN-
I00.843.03 / Batch Test Management in the DMS CB-DOC.
11 Define the Enable/Disable Tests on Sub-Modules option for the main module:
a. On the DMS main instrument setup screen, open the Instrument Option Editor for each Main Atellica
Solution or Atellica CI Analyzer.
Fig. 34: Configuring the Enable/Disable Tests on Sub-Modules option for the main module
The new tests with the sample type suffix are not affected by sample type management. This setup makes
it possible for DMS to check the sample type continuity with the LIS, DMS, and the instrument.
– or –
c. Confirm that the following sample type tables are completely empty. Delete any contents as needed.
the “Sample Type”, “Sample Type Instrument” and “Sample Type LIS” tables are all completely empty.
Click Save wherever necessary.
• Sample Type
e. Clear the Enable sample type management option and then click Save.
If ADM is present but sample type management is not in use on DMS, it is recommended that the sample
type coding system be purged in ADM. This ensures no sample type information is sent to DMS.
16 On the DMS Linux console, enter the command service nemoks restart.
Advanced data management functions such as QC and GEM are not supported in DMS. Escalations for
these tasks will be reviewed and sent for enhancement or confirmed complaint determination via the
standard processes. Direct headquarters support might not be provided for these functions.
• ( Page 8 Configure for an HL7 LIS): updated the steps to confirm the LFT0026111
instrument port information.
siemens-healthineers.com