tailieu xn abbott

Abbott Laboratories 1998, 2004 Abbott LaboratoriesAbbott Park, IL 60064 ARCHITECT is a registered trademark

of Abbott LaboratoriesPatents Pending

ARCHITECTSYSTEM

Abbott Standard InterfaceRS-232 Manual

List Number 06F71-05

Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition iii91407-105March, 2004

ForewordThis manual has been designed to help you familiarize yourself with all aspects of the Abbott Standard Interface for the ARCHITECT System.

If you have any questions, do not hesitate to contact your local Abbott Laboratories Diagnostics Division Customer Support Representative to obtain prompt answers to your inquiries.

Customer Support

Proprietary StatementThe ARCHITECT System software programs and system documentation are protected by copyright. All rights are reserved.

The software and manual were developed solely for use with the ARCHITECT System and for in vitro diagnostic applications as specified in the operating instructions.

The information, documents and related graphics published herein (the Information) are the sole property of Abbott Laboratories. Permission to use the Information is granted, provided that

the copyright notice appears on all copies; use of the Information is for operation of ABBOTT prod-

ucts by Abbott trained personnel or informational use only;

the Information is not modified in any way; and no graphics are used separate from accompanying text.

Each person assumes full responsibility and all risks arising from use of the Information. The Information is presented AS IS and may include technical inaccuracies or typographical errors. Abbott Laboratories reserves the right to make additions, deletions, or modifications to the Information at any time without any prior notification.

United States: 1-800-527-1869

Canada: 1-800-387-8378 (English speaking customers)1-800-465-2675 (French speaking customers)

International: Call your local Abbott Customer Support Representative.

iv Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition91407-105March, 2004

DisclaimersAll samples (printouts, graphics, displays, screens, etc.) are for information and illustration purposes only and shall not be used for clinical or maintenance evaluations. Data shown in sample printouts and screens do not reflect actual patient names or test results.

Abbott Laboratories makes no representations or warranties about the accuracy and reliability of the information contained in or printed from the ARCHITECT System Operations Manual CD-ROM.

The Information was developed to be used by Abbott Laboratories trained personnel, by other persons knowledgeable or experienced with the operation and service of the product identified, or under the direct supervision and with cooperation from Abbott Laboratories technical sales or service representatives.

In no event shall Abbott Laboratories or its affiliates be liable for any damages or losses incurred in connection with or arising from the use of the Information by persons not fully trained by Abbott Laboratories. This limitation shall not apply to those persons knowledgeable or experienced with the operation and service of the product identified, or under the direct supervision and with cooperation from Abbott Laboratories technical sales or service representatives.

No confidential relationship shall be established in the event that any user of the Information should make any oral, written or electronic response to Abbott Laboratories (such as feedback, questions, comments, suggestions, ideas, etc.). Such response and any information submitted therewith shall be considered non-confidential, and Abbott shall be free to reproduce, publish or otherwise use such information for any purposes whatsoever including, without limitation, the research, development, manufacture, service, use, or sale of products incorporating such information. The sender of any information to Abbott is fully responsible for its content, including its truthfulness and accuracy and its non-infringement of any other persons proprietary rights.

Abbott Laboratories is not engaged in rendering medical advice or services.

Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition v91407-105March, 2004

Updates to the Information may be provided in either paper or electronic format. Always refer to the latest documents for the most current information.

Incremental manual updates may cause the master Table of contents or master Index page numbering to change.

ARCHITECT i System warrantyAbbott Laboratories (Abbott) warrants the ARCHITECT i System (system) when used for its intended purpose by the original purchaser, excluding items subject to wear and tear which require replacement during normal use. This warranty shall continue for a period of ninety (90) days commencing twenty-one (21) days from the date of system installation, or until title is transferred from the original purchaser, whichever occurs first (the Warranty Period). The warranty does not cover the software included in the system, which is subject to the warranty stated in the Software License Agreement. Other warranty options may be available through your Abbott representative. The warranty is country dependent, based on local legal requirements.

ARCHITECT c System warrantyAbbott Laboratories warrants instruments sold by Abbott Diagnostics Division to be free from defects in workmanship and materials during normal use by the original purchaser. This warranty shall continue for a period of one year, commencing twenty-one (21) days from the date of shipment to the original purchaser, or until title is transferred from the original purchaser, whichever occurs first (the Warranty Period).

If any defects occur during the Warranty period, contact your Abbott Customer Service Representative immediately, and be prepared to furnish information including the serial number, the model number, and pertinent details concerning the defect.

This Warranty does not cover defects or malfunctions which: (1) are not reported to Abbott during the Warranty Period and within one week of occurrence; (2) result from chemical decomposition or corrosion; (3) are caused primarily by failure to comply with any requirements or instruction contained in the applicable Abbott Operations Manual; or (4) result from maintenance, repair, or modification, performed without Abbotts authorization.

vi Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition91407-105March, 2004

Abbotts liability for all matters arising from the supply, installation, use, repair, and maintenance of the instrument, whether arising under this Warranty or otherwise, shall be limited solely to the repair or (at Abbotts sole discretion) replacement of the instrument or of components thereof. Replaced parts shall become the property of Abbott Laboratories. In no event shall Abbott be liable for injuries sustained by third parties, consequential damages, and/or lost profits.

The ICT module Warranty is 15,000 samples or two months post-installation, whichever occurs first.

The cuvette warranty is one year post-installation.

THE FOREGOING IS THE SOLE WARRANTY MADE BY ABBOTT LABORATORIES REGARDING THE INSTRUMENT, AND ABBOTT SPECIFICALLY DISCLAIMS ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS IMPLIED FOR A PARTICULAR PURPOSE.

Abbott warrantyABBOTT LABORATORIES MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND OR NATURE WITH RESPECT TO THE INFORMATION. ABBOTT LABORATORIES HEREBY DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, WHETHER EXPRESS OR IMPLIED, CREATED BY LAW, CONTRACT OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT. IN NO EVENT SHALL ABBOTT LABORATORIES BE LIABLE FOR ANY DAMAGES OF ANY KIND OR NATURE, INCLUDING, WITHOUT LIMITATION, DIRECT, INDIRECT, SPECIAL (INCLUDING LOSS OF PROFIT) CONSEQUENTIAL OR INCIDENTAL DAMAGES ARISING FROM OR IN CONNECTION WITH THE EXISTENCE OR USE OF THE INFORMATION, REGARDLESS OF WHETHER ABBOTT LABORATORIES HAS BEEN ADVISED AS TO THE POSSIBILITY OF SUCH DAMAGES.

ABBOTT MAKES NO WARRANTIES FOR THE INTERFACE, THE ARCHITECT HOST/INSTRUMENT DATA DISK, ASIST, OR THE ARCHITECT SCC SIMULATOR (FOR LIS VENDORS) BEYOND THOSE SET FORTH IN THE OPERATIONS MANUAL FOR THE ABBOTT SYSTEM/INSTRUMENT.

Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition vii91407-105March, 2004

Agency approvalsThe ARCHITECT System has been tested and found to comply with the following agency standards:

Underwriters Laboratories: UL 3101-1 or UL61010A-1 Electrical Equipment for Laboratory Use Part 1: General RequirementscUL: CSA c22.2 No. 1010 Safety requirements for electrical equipment for measurement, control, and laboratory use Part 1: General Requirements

21CFR Part 1040.10: Performance Standards for Light Emitting Products

IEC 60825-1: Safety of Laser Products (Class I Laser Prod-ucts)

CE Marking

Trademark statementARCHITECT, i 2000, Chemiflex, and AxSYM are registered trademarks of Abbott Laboratories.

i 2000SR, i 4000, i 6000, i 8000, ci 8200, ARCHITECT ARMTM, c 8000, and SmartWash are trademarks of Abbott Laboratories.

INTEL and PENTIUM are registered trademarks of Intel Corporation.

ASTM is a registered trademark of the American Society for Testing and Materials.

Windows and MS-DOS are registered trademarks of Microsoft Corporation.

The following references are used throughout this manual to represent trademarks of Abbott Laboratories.

In Vitro Diagnostic Directive 98/79/ECLegal Manufacturer Abbott Laboratories

Abbott Park, IL 60064 USAAuthorized Representative Abbott

Max-Planck-Ring 265205 WiesbadenGermany+49-6122-580

viii Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition91407-105March, 2004

All Abbott Laboratories product names and trademarks are owned by or licensed to Abbott Laboratories, its subsidiaries or affiliates. No use of any Abbott trademark, trade name, trade dress, or product name may be made without the prior written authorization of Abbott Laboratories, except to identify the product or services of Abbott Laboratories. All other trademarks, brands, product names, and trade names are the property of their respective companies. All rights reserved.

Except as permitted above, no license or right, express or implied, is granted to any person under any patent, trademark, or other proprietary right of Abbott Laboratories.

The following U.S. Patents are relevant to the ARCHITECT c System or its components.

The following U.S. Patents are relevant to the ARCHITECT i System or its components.

There are other such patents and patent applications in the United States and worldwide.

Reference TrademarkARM ARCHITECT ARMTM

c 8000 c 8000i 2000 i 2000i 2000SR i 2000SRci 8200 ci 8200

4,533,457 4,619,739 4,647,362 4,678,7554,797,192 5,025,389 5,413,770

5,468,646 5,536,049 5,543,524 5,545,7395,565,570 5,669,819 5,682,662 5,723,7955,795,784 Des. 397,938 Des. 401,699 Des. 401,697Des. 401,700 5,783,699 5,856,194 5,859,429Des. 404,829 Des. 406,901 5,915,583 5,938,120Des. 413,539 5,965,828 6,022,746 6,063,6346,150,113 6,153,377 6,162,645

Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition ix91407-105March, 2004

System labelingThe symbols in the following table are used on ARCHITECT System labeling.

Key to symbols used on labelingLabel Description

Authorized representatitve

Legal manufacturer

For in vitro diagnostic use

Manufacturing location

Date of manufacture

Serial number

AC input power

Class 2 laser product

Electrical shock

Sample Cups

ICT Cleaning Fluid

ICT Lyophilized Cleaning Solution

Water Bath Additive

x Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition91407-105March, 2004

Pre-Trigger Solution

Trigger Solution

Wash buffer

Reaction Vessels

Septum

Replacement Caps

List number

Temperature limitation

Use by/expiration date

Consult instructions for use

Caution, consult instructions for use

Lot number

Quantity

Unit

Biological risk

Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition Table of Contents-191407-105March, 2004

Table of Contents

Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiCustomer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiProprietary Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiDisclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivARCHITECT i System warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vARCHITECT c System warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vAbbott warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viAgency approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademark statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiSystem labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

How to Use this Manual Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Use this Manual-1Overview of the Manual . . . . . . . . . . . . . . . . . How to Use this Manual-3Alternative Reference Materials . . . . . . . . . . . How to Use this Manual-5

Section 1 Abbott Standard InterfaceIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Overview of the Abbott Standard Interface (ASI). . . . . . . . . . . . . . . . . 1-3Layered Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Electrical Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Mechanical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Signaling Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Character Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Data Link Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14Sending an [ENQ] and Receiving an [ACK] . . . . . . . . . . . . . . . . 1-14

Sending an [ENQ] and Receiving a [NAK] . . . . . . . . . . . . . . 1-15Sending an [ENQ] and Receiving an [ENQ] . . . . . . . . . . . . . 1-15

Transfer Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Time-outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22During the Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . 1-22During the Transfer Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22

Termination Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22Restricted Message Characters. . . . . . . . . . . . . . . . . . . . . . . . 1-22

Table of Contents-2 Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition91407-105March, 2004

ASTM E 1381-91 Sender/ Receiver State Diagram. . . . . . . . . . . 1-24Presentation Layer Message Content. . . . . . . . . . . . . . . . . . . . . . . . 1-27

Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31Delimiters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31

ASI Defined Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35Sender Name or ID (ASTM E 1394-91 Field 7.1.5) . . . . . . . 1-35Universal Test ID (ASTM E 1394-91 Field 6.6.1) . . . . . . . . 1-36Specimen IDs (ASTM E 1394-91 Field 9.4.3, 9.4.4) . . . . . . 1-39Patient IDs (ASTM E 1394-91 Fields 8.1.3, 8.1.4, and 8.1.5) 1-39Action Codes (ASTM E 1394-91 Field 9.4.12). . . . . . . . . . . 1-41Report Type (ASTM E 1394-91 Field 9.4.26). . . . . . . . . . . . 1-42Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42Record Sequence Number . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43Records and Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44Request Information Record . . . . . . . . . . . . . . . . . . . . . . . . . 1-56

Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65Category I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65Category II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-66Category III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-67Category IV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68

Section 2 Use or functionIntroduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1ARCHITECT System overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Primary components of an ARCHITECT System . . . . . . . . . . . 2-3ARCHITECT ci 8200 integrated system. . . . . . . . . . . . . . . . . 2-3ARCHITECT c 8000 System . . . . . . . . . . . . . . . . . . . . . . . . . 2-4i 2000 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5ARCHITECT i 2000SR System . . . . . . . . . . . . . . . . . . . . . . . . 2-6

System control center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9SCC standard components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Network hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11SCC optional components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12ARCHITECT System software. . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Software interface description . . . . . . . . . . . . . . . . . . . . . . . . 2-13Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Software navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19


Snapshot screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20User logon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Processing modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Processing module (c 8000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Processing module keypad (c System) . . . . . . . . . . . . . . . . . . 2-29Processing center (c System) . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Supply and pump center (c System) . . . . . . . . . . . . . . . . . . . . 2-44Optional components (c 8000 processing module) . . . . . . 2-47

Processing modules (ARCHITECT i System). . . . . . . . . . . . . . 2-48i 2000 processing module . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48i 2000SR processing module . . . . . . . . . . . . . . . . . . . . . . . . 2-53Processing module keypad (i System) . . . . . . . . . . . . . . . . . . 2-55Processing center (i System). . . . . . . . . . . . . . . . . . . . . . . . . . 2-56Supply and waste center (i System) . . . . . . . . . . . . . . . . . . . . 2-75Optional components (i System) . . . . . . . . . . . . . . . . . . . . . . 2-85

Sample handlers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92RSH retest sample handler (c 8000 or i 2000SR) . . . . . . . . . . . . 2-92

Priority bay (RSH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-93Routine bay (RSH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-95RSH keypad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97

SSH standard sample handler (i 2000). . . . . . . . . . . . . . . . . . . . 2-97SSH keypad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100

LAS carousel sample handler (i 2000) . . . . . . . . . . . . . . . . . . . . 2-101LAS carousel sample handler keypad. . . . . . . . . . . . . . . . . . 2-102

System statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-103Sample handler status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-103

RSH status types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-104SSH status types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-105LAS carousel sample handler status types . . . . . . . . . . . . . . 2-106

Processing module status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-107Processing module status types (c 8000) . . . . . . . . . . . . . . . 2-108Processing module status types (i 2000 and i 2000SR). . . . . 2-109

Section 3 Communication SetupIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1System startup, pause, and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

SCC power off and power on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Power on the SCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Power off the SCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Cycle power to the SCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Processing module and sample handler cycle power, startup, and pause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6


Power on the processing module and/or sample handler. . . . . 3-7Power off the processing module and/or sample handler . . . . 3-7Cycle power to the processing module and/or sample handler 3-8Start up the processing module and/or sample handler . . . . . . 3-9Pause the processing module . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Pause the RSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Pause the sample carousel (c System) . . . . . . . . . . . . . . . . . . 3-12Pause the sample load queue (SSH) . . . . . . . . . . . . . . . . . . . 3-12Pause the LAS carousel sample handler . . . . . . . . . . . . . . . . 3-13

Setting Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Host Release Mode Configuration Windows . . . . . . . . . . . . . . 3-17Configuration screen System settings view. . . . . . . . . . . . . . . . 3-20

Access the Configuration screen System settings view . . . 3-21System Control Center Configuration Windows . . . . . . . . . . . . . 3-24Serial Ports Configuration Windows . . . . . . . . . . . . . . . . . . . . . . 3-28

Section 4 ARCHITECT System-specific Outgoing MessagesIntroduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Communication: ARCHITECT System to Host. . . . . . . . . . . . . . . . . . 4-3

QC Results Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Patient Results Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Order Query Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Priority of outgoing Transmissions . . . . . . . . . . . . . . . . . . . . . . . . 4-7Logical Transmission Error Recover Requirements . . . . . . . . . . . 4-7Format Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Message Header Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Patient Information Record . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Test Order Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Result Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Comment Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Request Information Record . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Message Terminator Record . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Unicode Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Control Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21UNICODE ASTM Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Checksum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Section 5 ARCHITECT System-specific Incoming MessagesIntroduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Communication: Host to the ARCHITECT System. . . . . . . . . . . . . . . 5-3

Logical Transmission Error Recovery Requirements . . . . . . . 5-4Format Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5


Message Header Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Patient Information Record . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Test Order Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Comment Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Negative Query Response Record . . . . . . . . . . . . . . . . . . . . . 5-12Message Terminator Record. . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Section 6 ARCHITECT System Support of ASI OptionsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1ARCHITECT System Support of ASI Options . . . . . . . . . . . . . . . . . . . 6-3

Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3ASI Code Page for the ARCHITECT System . . . . . . . . . . . . . . . . 6-4

Section 7 TroubleshootingIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Error codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Error Messages Specific to the RS-232 Interface . . . . . . . . . . . . . . 7-3Observed Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31

Section 8 Abbott Host/Instrument Interface ToolsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1ASIST Tool Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Abbott ARCHITECT Host/Instrument Interface Data Disk . . . . . . . . . 8-5ARCHITECT SCC Simulator (for LIS Vendors) . . . . . . . . . . . . . . . . . 8-7

Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7SCC Simulator components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Using the simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

Selecting simulator database . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Configuring communication ports . . . . . . . . . . . . . . . . . . . . . 8-10Connecting to the communication port . . . . . . . . . . . . . . . . . 8-11Store received orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14Collate results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16Selecting views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18Refresh views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21Installing assays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Installing dilution names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24Deleting assays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25Deleting dilution names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26Creating results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27Creating queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29Order filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Deleting items from the database . . . . . . . . . . . . . . . . . . . . . . 8-36


Viewing item details from the database. . . . . . . . . . . . . . . . . 8-38Disconnecting from the communication port . . . . . . . . . . . . 8-43Sending results or queries to a host . . . . . . . . . . . . . . . . . . . . 8-45

Section 9 ARCHITECT System and AxSYM ComparisonIntroduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Functional Comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Physical Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Host Interface Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Data Link Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Establishment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Message Content Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4Canceling of Test Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4Transmission Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4Transmission of Multiple Flags . . . . . . . . . . . . . . . . . . . . . . . . 9-6Comment Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Query Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Logical Transmission Error Recovery Requirements . . . . . . . 9-7Other specific field format and content differences. . . . . . . . . 9-9

Document Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11System-Specific Outgoing Messages . . . . . . . . . . . . . . . . . . . . . . 9-11

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11Communication: (ARCHITECT vs. AxSYM) to Host . . . . . 9-11ASTM Record Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12Message Header Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13Patient Information Record . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14Test Order Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16Result Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18Comment Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22Request Information Record . . . . . . . . . . . . . . . . . . . . . . . . . 9-23Message Terminator Record . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

System-Specific Incoming Messages. . . . . . . . . . . . . . . . . . . . . . 9-24Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24Communication: Host to the System (ARCHITECT vs. AxSYM)9-24Format Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26Message Header Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26Patient Information Record . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27Test Order Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30


ARCHITECT ONLY:Comment Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34Negative Query Response Record, ARCHITECT . . . . . . . . . 9-35Request Information Record, AxSYM . . . . . . . . . . . . . . . . . . 9-35Message Terminator Record. . . . . . . . . . . . . . . . . . . . . . . . . . 9-37

GlossaryIndexRevision history

Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition How to Use this Manual-191407-105March, 2004

Section 0Introduction

The Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition provides the necessary information for interfacing the ARCHITECT System to hospital or laboratory information systems across the serial RS-232 communications port.

Topics in this section include:

Overview of the Manual Alternative Reference Materials

Introduction

How to Use this Manual-2 Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition91407-105March, 2004

NOTES


Section 0Overview of the Manual

All Abbott Standard Interface RS-232 Manuals are designed to provide clear and concise information on the communications capabilities of Abbott Diagnostic Instruments and Systems that support the Abbott Standard Interface (ASI). This interface is based on the following industry supported standards:

ASTM E 1381-91 Specification for Low-Level Protocol to Transfer Messages Between Clinical Laboratory Instruments and Computer Systems

ASTM E 1394-91 Standard Specification for Transferring Information Between Clinical Instruments and Computer Systems

The manuals provide specific information on the communications capabilities of Abbott ASI instruments and systems as well as general information on the Abbott implementation of the ASTM E 1381-91 and E 1394-91 communication protocols. Different editions exist for different instruments and systems, however they are all organized as follows:

How to Use This Manual: Discusses the purpose of the manual and provides a good overview of the information contained within.

Section 1: Discusses the Abbott implementation of the ASTM E 1381-91 and E 1394-91 standards. This section is common to all Abbott Standard Interface Manuals.

Section 2 Section 7: Discusses specific information about the instrument or system covered by that particular edition. They cover topics such as instrument overview, communications setup, content of communications messages and instrument communication diagnostics. These sections are unique for each instrument. Sections 2 7 of this edition describe the ARCHITECT System and its specific interface implementation.

Section 8: Refers to the use of ASIST (Abbott Standard Interface Simulator Tool), the ARCHITECT Host/Instrument Interface Data Disk, and the ARCHITECT SCC Simulator (for LIS Vendors).

Section 9: Discusses the differences between the ARCHITECT System and the AxSYM interface.

Overview of the Manual


This manual assumes the reader is familiar with programming techniques and is capable of programming using a high level language. This manual also assumes the reader has a good working knowledge of serial communications as they relate to the computer system that interfaces with the Abbott instrument or system.

For readers not familiar with the ASTM E 1381-91 and E 1394-91 communications standards, we highly recommend ordering these standards by calling or writing ASTM using the information provided in "Alternative Reference Materials" on page 5: All readers should carefully study the Overview of the Abbott Standard Interface section and all subsequent sections to understand how Abbott instruments implement the ASTM standards. The reader should then be able to develop and program the logic required to effectively communicate with the ARCHITECT System as well as setup and diagnose communications.

Included with this manual is a data diskette containing the Instrument Specification File (ISF) for the ARCHITECT System. When this file is loaded as the current instrument in the ASIST environment, the user can perform comprehensive testing and validation of communication protocols.

Instrument developers can use ASIST to emulate a Host computer. ASIST sends requests in user-generated test protocols to ensure that the equipment accepts and interprets these communications correctly.

Host computer software developers can use ASIST to emulate Abbott instruments to test communications without having to invest in the instruments themselves. Test transmissions of report data, using established record layouts and communications protocols, ensure that host software properly interfaces with actual instruments after installation.

The data diskette is provided with the understanding that modifying originals or copies of the data files invalidates the data files. Do not use invalid data files to represent instrument output.

Abbott provides this software as a tool to assist the development of interface software to Abbott instruments and systems. Developers should not rely solely on the use of this product for verification and validation of their interface software.

ASIST software is provided with the understanding that Abbott does not guarantee its support or future availability.


Section 0Alternative Reference Materials

Bibliography of standards and references.

ASTM Standards referenced within this document are available through:

American Society of Testing and Materials (ASTM)

100 BARR HARBOR DR

WEST CONSHOHOCKEN, PA. 19428-2959

Phone Orders: (610) 832-9585

Web: www.astm.org

Alternative Reference Materials


NOTES

Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition Section 1-191407-105March, 2004

Section 1 Abbott Standard Interface

Section 1Introduction

This section explains the Abbott implementation of the ASTM E 1381-91 and E 1394-91 communications standards.

Topics include:

Overview of the Abbott Standard Interface (ASI) Layered Protocols Physical Layer Electrical, Mechanical, and Signaling

Characteristics Data Link Layer Establishment, Transfer, and Termination Presentation Layer Message Content Application Layer

Abbott Standard InterfaceIntroduction Section 1

Section 1-2 Abbott Standard Interface RS-232 Manual/ARCHITECT System Edition91407-105March, 2004

NOTES



Section 1Overview of the Abbott StandardInterface (ASI)

Abbott instruments and data management systems provide communications to external host computers via a serial connection conforming to the specifications and requirements set forth in the ASTM E 1381-91 and ASTM E 1394-91 standards. At the most basic level these standards allow host systems to download (i.e., send) worklist messages to the Abbott instruments/systems. The Abbott instruments can then process the worklist, act on the tests that have been requested, and return the results associated with the worklist. The host computer can then process the results, generate reports, and store the information.

Although these standards form the basis of the type of information exchanged between clinical instruments and the manner that the information is transferred, they allow the instrument and system manufacturers considerable latitude in selecting field use and field substructure.

In order to ensure compatibility between Abbott instruments, systems, and external hosts, Abbott has taken the initiative to define the Abbott Standard Interface (ASI). ASI consists of a series of interpretations and definitions of the ASTM standards that provide a strict but consistent compliance to the standards, while providing the needed flexibility to handle the unique data requirements of Abbotts multiple instruments and systems.

By ensuring compatibility and by defining the fields that are instrument specific, developers benefit by structuring their software to be configurable to the highest possible extent, thus minimizing development time and costs.

Abbott Standard InterfaceOverview of the Abbott Standard Interface (ASI) Section 1


Table 1.1: Terms and Definitions

Term DefinitionASI Abbott Standard Interface: Abbotts implementation of the American Society for Testing and

Materials (ASTM) Standard.E 1394-91, A Standard Specification for Transferring Information Between Clinical Instruments and Computer Systems.E 1381-91, Specification for Low-Level Protocol to Transfer Messages Between Clinical Laboratory Instruments and Computer Systems.

Allowed Data Formats All data is represented in ASCII format within the range 0 255. Values 0 127 are defined by ANSI X3.4-1986 Standard.Values 128 255 are defined as needed by specific instruments. Values 0 31 cannot be used, with the exception of 13 (). The value 13 is reserved as a record terminator. Values 32 255 can be used, with the exception of 127 and 255. Within a data text field, only the ASCII characters 32 126 and 128 254 are permitted as usable characters. Characters used as delimiters in the transmission are excluded from the above permitted range. The sender is responsible for checking that a data text field does not contain any delimiters. The record identifier fields (H,P, O, R, L, C, M, and Q) are always uppercase when output from the Abbott instrument. On input, both upper- and lowercase record identifiers are accepted.Fields and records are variable in length with no restriction placed on the maximum length of a field or record. The high-level protocol depends on the receivers buffering capability and the low-level communication ability to divide the information into workable lengths for transmission and processing purposes. All Abbott Standard Interface RS-232 manuals provide the maximum allowable length of each field transmitted and received.

E 1394-91Message

A block of data that is transmitted in a format consistent with the ASTM E 1394-91 Standard. Data is transmitted in a series of records starting with a Header Record (H) and ending with a Terminator Record (L).When a transmission is lost, the Abbott instrument retransmits or accepts only complete messages.

E 1394-91 Record An E 1394 Record is a string of characters starting with a capital ASCII alphabet character and ending with a carriage return (ASCII 13), as defined by the ASTM E 1394-91 Standard.

Reserved Characters The following characters have special uses and should not be used for data:Vertical Bar (|)Backslash (\)Ampersand (&)Carriage Return ()Caret (^)

E 1381-91 Message A block of data that is transmitted in a format consistent with the ASTM E 1381-91 Standard. Abbott ASI instruments use an E 1394-91 Record as the E 1381-91 Message. Thus, an E 1381-91 Message may be transmitted using multiple (one or more) frames, based on the length of the message.

E 1381-91 Frame A frame is a subdivision of a message and allows transmission of up to 247 characters (240 data characters and 7 control characters). The Abbott instrument transmits one record per frame.Messages more than 247 characters long can be divided into multiple frames, as long as each frame contains only information from one record at a time.



Section 1Layered Protocols

The Abbott Standard Interface (ASI) is based on a four-layer protocol implementation, consistent with the terminology and definitions of the Organization for International Standards (ISO) reference model for Open Systems Interconnection (OSI). The OSI model is concerned with the interconnections between different systems and not with the internal functions that are performed by a given system. The OSI model provides a generalized view of a layered architecture. Using this approach, functions and services required to allow two systems to communicate are grouped in various functional layers. A given layer is responsible for performing a specific set of functions and for providing a specific set of services.

A communications architecture can then be defined in terms of the services provided by each layer and the interface between layers. Protocols define the services offered across a layer interface and the rules that are followed in the processing performed as part of a service. Data formats for the data exchanged across an interface are also defined as part of the architecture.

Two types of interfaces exist in a communications architecture. One set of interfaces exists between the layers in a given system. The second set of interfaces exists between comparable layers of different systems. ASI provides information on the second set of interfaces that allow similar layers of different systems to communicate.Layered Protocol Architecture

Figure 1.1: Layered Protocol Architecture

The OSI layer designators are used as reference and do not imply compliance with actual ISO/OSI Standards.

Based on this architecture, ASI defines the following layers for implementation of communications software:

Abbott ASI Instruments Host SystemLayer 4 (OSI Layer 7) Layer 4 (OSI Layer 7)Layer 3 (OSI Layer 6) Layer 3 (OSI Layer 6)Layer 2 (OSI Layer 2) Layer 2 (OSI Layer 2)

Layer 1 (OSI Layer 1)

Abbott Standard InterfaceLayered Protocols Section 1


Physical Layer (Layer 1) Directs transmission of serial binary data bits between the Abbott instruments and systems and external host computers across a mechanical and electrical connection, as defined by this document and ASTM E 1381-91 section 5.

Data Link Layer (Layer 2) Provides services for establishing a link connection, transferring data, and releasing the connection. Also provides services for delimiting, synchronism, sequence control, error detecting and recovering of the link, as defined by this document and ASTM E 1381-91 section 6.

Presentation Layer (Layer 3) Provides services for building message content into a standard and interpretable form, as defined by this document and ASTM E 1394-91.

Application Layer (Layer 4) Provides services for processing test requests, running assays, reporting results, etc., as defined by this document and the instrument specific operations manual.

The following figure depicts the general implementation of these layers on new Abbott instruments and systems that support the ASTM Standards.ASI Implementations

Figure 1.2: ASI Implementations

Abbott ASI Instruments Host SystemApplication LayerSoftware to process test requests, run assays, report results

Application LayerSoftware to request tests, process, store, report, and manage patient data

Message Content LayerSoftware to convert above data into a standard and interpretable form

Message Content LayerSoftware to convert above data into a standard and interpretable form

Data Link LayerSoftware for link connection and release, delimiting and synchronism, sequence control, error detection and recovery

Data Link LayerSoftware for link connection and release, delimiting and synchronism, sequence control, error detection and recovery

Physical LayerMechanical and electrical connection for serial binary data bit transmission between the instrument and the host



Section 1Physical Layer

Physical Layer

Figure 1.3: Physical Layer

Abbott instruments and systems supporting the Abbott Standard Interface (ASI) implement the physical layer of the interface as specified by the ASTM E 1381-91 standard. This interface is based on the EIA RS-232D -1986 standards, for the mechanical and electrical characteristics and the ANSI X3.15-1976 and ANSI X3.16-1976 for the signaling characteristics, such as the structure of the characters being transmitted.

Electrical CharacteristicsAbbott instruments use a voltage more negative than minus three volts (with respect to signal ground) to indicate a marking condition (binary one). A voltage more positive than plus three volts (with respect to signal ground) indicates a spacing condition (binary zero). The relevant voltage and impedance levels of the signal generator and the signal receiver circuits of ASI instruments meet the requirements set forth in the RS-232D-1986 standard.

Mechanical CharacteristicsASI instruments use a 25-pin connector to facilitate connection to an external computer system. The connection provided conforms to the requirements of the EIA RS-232D Standard. The Communication Setup section of each Abbott Standard Interface RS-232 manual covers the specifics for that instrument.

The cabling and pin-out requirements of Abbott instruments and systems conform to the specifications defined in the ASTM E 1381-91 standard. Only pins 1, 2, 3, and 7 of the connector are used. Refer to the following table and figure for pin assignment information. The ASTM E 1381-91 standard requires that the external Host computer is configured as a DCE device.

Abbott ASI Instruments Host SystemApplication Layer Application Layer

Presentation Layer Presentation Layer

Data Link Layer Data Link Layer

Physical Layer

Abbott Standard InterfacePhysical Layer Section 1


Pin-to-Pin Connections (Wiring Diagram)

Figure 1.4: Pin-to-Pin Connections (Wiring Diagram)

Table 1.2: Pin Assignments for the 25-Pin Connector

Pin No. EIACircuit

Description DirectionAbbott

InstrumentComputer

1 Shield No Connection2 BA Transmitted Data Output Input3 BB Received Data Input Output7 AB Signal Ground

NOTE: If a computer is configured as a DTE Device (i.e., pin 2 is the output and pin 3 is the input), then the cable connecting the ASI instrument to the computer must have lines 2 and 3 crossed.

1 Shield2 Output3 Input

7 Signal Ground

Transmitted DataReceived Data

Instrument (DTE) (DCE) Computer123

7

No ConnectionInput

Output

Abbott


Abbott Standard InterfaceSection 1 Physical Layer

For Host computer systems that do not conform to the ASTM standard for the physical connection, other cabling schemes may be required as shown below. Many personal computers may have a 9-pin connector instead of the 25-pin required by the ASTM specifications.Host computer (PC with 9-pin connector) with Non-ASTM compliant connector

Figure 1.5: Host computer (PC with 9-pin connector) with Non-ASTM compliant connector

Host Computer with 9-Pin PC-AT style connector

Figure 1.6: Host Computer with 9-Pin PC-AT style connector

NOTE: Pin 1 is the shield connection and connects to the instruments (DTE) frame. Leave the shield connection open at the computer (DCE) to avoid ground loops.

Shield

Output

Input

Instrument (DTE) Host ComputerAbbott

1

2

3

7

1

2

3

5Ground

(DCE)

9-PinConnector


1

2

3

7

1

2

3

5

(DTE)

9-PinConnector

Shield

Output

Input

Ground



If the same computer used a 25-pin connector configured as a DTE, the cabling requirements are as follows:Host computer (PC with 25-pin connector) with Non-ASTM compliant connector

Figure 1.7: Host computer (PC with 25-pin connector) with Non-ASTM compliant connector.

ASI instruments and systems may optionally provide fixed length cables for connecting to external systems. When cable lengths greater than 50 feet are required, then Low Capacitance shielded cables are recommended. Local Building Fire Code standards may require the use of Plenum rated cables for connecting systems. Please check with your building personnel for specific requirements that apply to wiring and cabling in your specific environment.

Signaling CharacteristicsCharacter Structure

Character bit patterns and bit rates determine how Abbott instruments communicate with computer systems.

The character bit sequencing, structure, and parity sense definitions conform to ANSI standards X3.15-1976 and X3.16-1976. The default structure for Abbott instruments character bit sequencing is:

1. A start bit with a value of zero.

2. The start bit is followed by eight bits that represent character data.

Shield

Output

Input


1

2

3

7

1

2

3

7Ground

(DTE)

25 PinConnector


Abbott Standard InterfaceSection 1 Physical Layer

3. A stop bit with a value of one ends the character structure.Default Abbott Instruments Character Structure. The start and stop bits separate ASCII characters which are eight bits long.

Figure 1.8: Default Abbott Instruments Character Structure. The start and stop bits separate ASCII characters which are eight bits long.

All ASI instruments support the ASTM required combinations of:

Start bits Data bits Parity bits Stop bits

SpeedAbbott instruments that implement ASI provide multiple baud rates for transmitting data to external systems. As a minimum, all ASI instruments support the ASTM preferred communications speed of 9600 baud, and may also support one or more of the following [1200, 2400, 4800, 14400, 19200, 28800, 38400, 57600, 115200]. The default setting of all ASI instruments for host communications is 9600 baud. For information on the exact baud rates supported by each instrument, refer to Communication Setup.

Abbott data management systems that are used as hosts support all four of the ASTM E 1381-91 required baud rates [1200, 2400, 4800, 9600]. Optionally, they may also support other baud rates [e.g., 19200, etc.] as required.

0 18 Data Bits

Start Bit Stop Bit



NOTES



Section 1Data Link Layer

Data Link Layer

Figure 1.9: Data Link Layer

The data link layer covers methods for the following:

Establishing communication connections with an external system

Providing error detection and error recovery of communications Delimiting and synchronism Controlling sequence Sending and receiving messages Terminating the communications connections

In addition, the data link layer performs the following inter-layer functions:

Interacts with higher layers in transferring data Handles requests for establishing and terminating

connections Reports the data link layer status

The data link layer uses a character-oriented protocol to send messages between two systems that are directly connected. One system transmits while the other system monitors the communications link. Thus, information flows in only one direction at a time. Replies occur after information is sent, never at the same time.

Abbott instruments implement the data link layer as specified in the ASTM E 1381-91 standard. This standard defines conditions that apply to a device if the device is an instrument, and other conditions if the device is a host computer system. Because Abbott Data Management systems are sometimes used as hosts for other Abbott instruments and other times as a link communicating to Laboratory Information Systems, these systems implement both the ASTM host and the instrument logic of the data link protocol. The configuration of these systems allows them to communicate appropriately based on the role that they are serving.



Data Link Layer Data Link Layer

Physical Layer

Abbott Standard InterfaceData Link Layer Section 1


The data link layer consists of the three following communications phases:

Establishment phase Transfer phase Termination phase

Each phase is discussed in detail.

Establishment PhaseThe establishment phase determines the direction of information flow and prepares the receiver to accept information. The system with data available for transmission initiates the establishment phase.

When Abbott ASI instruments and systems have data to send, they go into the establishment phase by transmitting the [ENQ] character. If a valid reply ([ACK], [NAK], or [ENQ]) is not received within the 15 second time period specified by ASTM E 1381-91, the Abbott instruments and systems enter the termination phase. The instrument returns to the establishment phase after waiting a certain amount of time (e.g., 30 seconds, 60 seconds, etc.) specific to that instrument.

If after a certain number of attempts the instrument is unable to establish communications with the external system, the operator is informed via a dialog box (or error message) and an error message is posted to the error log file.

Sending an [ENQ] and Receiving an [ACK]After determining that the data link is in a neutral state, the sender transmits an Enquiry [ENQ] transmission control character to the receiver, notifying the receiver that it has information to send. The receiver must send a Message Acknowledged [ACK] transmission character back to the sender before the information is sent. If the receiver is not ready to receive, it sends a Message Not Acknowledged [NAK] transmission character. All other characters are ignored by the sender and receiver. The only valid characters during the Establishment Phase are [ENQ], [ACK], and [NAK].Sender Initiating Establishment Phase. The receiver returns a signal to the sender acknowledging that it is ready to receive.

Figure 1.10: Sender Initiating Establishment Phase. The receiver returns a signal to the sender acknowledging that it is ready to receive.

Sender Receiver

1

2

[ENQ][ACK]


Abbott Standard InterfaceSection 1 Data Link Layer

Sending an [ENQ] and Receiving a [NAK]If the receiver is not ready to receive information, it sends a [NAK] in response to an [ENQ]. The sender must wait ten seconds before sending another [ENQ].Sender Receives a [NAK] Signal. If the sender receives a [NAK], the sender waits ten seconds before reinitiating the establishment phase.

Figure 1.11: Sender Receives a [NAK] Signal. If the sender receives a [NAK], the sender waits ten seconds before re-initiating the establishment phase.

Sending an [ENQ] and Receiving an [ENQ]When both systems simultaneously send an [ENQ], they are in contention. In that case, the Abbott instrument has first priority to transmit information. For example, the following figure shows a computer and an Abbott instrument simultaneously sending an [ENQ]. The computer must immediately stop trying to transmit and prepare to receive. When the next [ENQ] is received by the computer, the computer replies with an [ACK], or a [NAK], depending on its readiness to receive.Sender Receives an [ENQ] after Sending an [ENQ]. The sender prepares to receive.

Figure 1.12: Sender Receives an [ENQ] after Sending an [ENQ]. The sender prepares to receive.

Sender Receiver

1

2

[ENQ]

[NAK]

310 Seconds

4[ENQ]

Abbott InstrumentComputer System

1

[ENQ][ENQ]

2Prepare to

3[ENQ]

4[ACK]

Receive



In the example shown in the following figure, the instrument sends an [ENQ] and receives an [ENQ]. The instrument waits at least one second before re-sending another [ENQ]. The computer system must wait at least twenty seconds before trying to initiate the communications by sending another [ENQ].Instrument Receives an [ENQ] after Sending an [ENQ]. The instrument waits one second before re-sending another [ENQ].

Figure 1.13: Instrument Receives an [ENQ] after Sending an [ENQ]. The instrument waits one second before re-sending another [ENQ].

Transfer PhaseDuring the transfer phase, the sender transmits messages to the receiver until all messages are sent. Messages are sent in frames which contain a maximum of 247 characters.

Special control characters identify the frame type, the beginning and end of a frame, and provide for error detection. The following table lists the special control characters..

Computer System Abbott Instrument

1

2

[ENQ]

[ENQ]

3 1 Second

4[ENQ]

Table 1.3: Special Control Characters

Symbol Character Description[STX] Start of Text transmission control

characterFirst character transmitted at the beginning of a frame.

F# Frame Number The frame number is an ASCII digit from 0 to 7. Its purpose is to permit the receiver to distinguish between new and re-transmitted frames. This single digit is sent immediately after the STX character. The frame number begins with 1 when the transfer phase is initialized and increments by 1 each time a new frame is transmitted and acknowledged. After 7, the frame number returns to 0 and repeats the above sequence.

[ETB] End of Transmission Block transmission control character

Character used to indicate end of an intermediate frame.

[ETX] End of Text transmission control character

Character used to indicate the end of an end frame.



Frames Abbott instruments and systems supporting ASI handle an ASTM E 1394-91 record as an ASTM E 1381-91 message. If the E 1394-91 record is longer than 240 characters, the message is transmitted in multiple frames consisting of end frames and intermediate frames. If the message (i.e., E 1394-91 record) is less than or equal to 240 characters, the single frame transmitted is an end frame.

CS1 Most significant character of checksum 0 9 and A F

The checksum determines if a frame is defective. The checksum is encoded as two characters and is sent after the ETB or ETX character. The checksum is computed by adding the binary values of the characters (modulo 256), keeping the least significant 8 bits of the result. The 8 bits can be considered as two groups of 4 bits which are converted to ASCII and represented in hexadecimal format. The two ASCII characters are transmitted as the checksum with the most significant character first. The STX character initializes the checksum to zero. The first character used in computing the checksum is the frame number. The last character used is the ETB or ETX. The STX, CR, or LF are not included. Using the following Frame as an example, the checksum for this frame is calculated.

Then 673 (decimal) = 2A1 (HEX)The most significant byte (2) is discarded and the remainder is then transmitted as two characters, A (ASCII 65) and 1 (ASCII 49) to form the checksum.

CS2 Least significant character of checksum 0 9 and A F

[CR] ASCII character for carriage return

Character used to end an E 1394-91 record (i.e., E1381-91 message) and the second to last character transmitted in a frame.

[LF] ASCII character for line feed The LF character is used as the last character of a frame. The LF character may not display in the message text.

Table 1.3: Special Control Characters (continued)

Symbol Character Description

1 ABCDEFGHI A1 002 Not included in calculation

1 049 1st character for calculationA 065 2ndB 066 etc.C 067 etc.D 068 etc.E 069 etc.F 070 etc.G 071 etc.H 072 etc.I 073 etc.

003 Last character for calculationTotal= 673 Total sum value



Each new message begins in a new frame. A frame never contains more than one message or parts of more than one message. Two types of frames are used:

End frames. A message with 240 characters or less is sent in a single end frame.

Intermediate frames. Messages that are longer than 240 characters are broken into pieces that are 240 characters or less in length and sent in multiple or intermediate frames with the last part of the message sent in an end frame

.

The following figure shows how a message with more than 240 characters is sent.

Figure 1.14: Intermediate and End Frames. Multiple frame messages start with intermediate frames and end with end frames containing only the end of one message.

After a frame is sent, the sender stops transmitting and waits for an acknowledgment [ACK] from the receiver. The receiver responds to every frame and when it is ready to receive another frame, it sends one of the following replies:

Message Acknowledged [ACK] Message Not Acknowledged [NAK] End of Transmission [EOT]

Message [ETX] [CS1] [CS2] [CR] [LF][STX] [F#]

Message [ETB] [CS1] [CS2] [CR] [LF][STX] [F#]

Message 1

Message 1 continued

Message 2Message 2 is not added to the frame containing the second part of Message 1, but begins in a new frame.

Message 1 is longer than 240 characters so it is divided into sections.

Frame numbers reset after count reaches 7.

[ETB] [CS1] [CS2] [CR] [LF]

[STX][1]

[STX][2]

[STX] [0]

Message 1 continued [ETX] [CS1] [CS2] [CR] [LF][STX] [7]

Message 2 continued [ETX] [CS1] [CS2] [CR] [LF][STX] [1]


[ETX] indicates an end frame.

[ETB] indicates an intermediate frame.

[STX][3], etc.




Each of the replies is discussed below.

A reply of [ACK] acknowledges that the last frame was received successfully and that the receiver is ready for another frame. The sender must increment the frame number and transmit another frame or terminate the message transfer.Sender Transmitting After Receiving [ACK]. The sender sends another frame after successfully transferring a frame.

Figure 1.15: Sender Transmitting After Receiving [ACK]. The sender sends another frame after successfully transferring a frame.

A reply of [NAK] means that the last frame was not received successfully and that the receiver is ready to receive the frame again. The sender may re-transmit the frame or proceed to the termination phase.Sender Retransmitting a Frame After Transmission Failure. The receiver indicates transmission failure with [NAK].

Figure 1.16: Sender Retransmitting a Frame After Transmission Failure. The receiver indicates transmission failure with [NAK].

Abbott ASI instruments and systems [NAK] a frame for the following reasons:

Improperly framed transmission received after [STX]. Certain situations cause a time-out condition to occur if insufficient information is received to properly process the frame. Under these conditions, ASI instruments return to idle state without transmitting a [NAK] or any other characters.

Invalid frame number or frame number out of sequence. Restricted character received in message text. Invalid checksum received.

Sender Receiver

1

2[ACK]

3Increment

Frame 1

Frame Count

4 Frame 2

Sender Receiver

1

2[NAK]

3

Frame 1

Frame 1



Characters received before [STX] are ignored. Once [STX] is received, the ASI instrument expects a complete frame.

A reply of [EOT] acknowledges that the last frame was received successfully and that the receiver is ready for another frame, but the receiver is requesting that the sender stop transmitting. The sender must send a reply within the time-out period. End of Transmission. The receiver indicates successful receipt of the complete message with an [EOT], but requires an interrupt.

Figure 1.17: End of Transmission. The receiver indicates successful receipt of the complete message with an [EOT], but requires an interrupt.

The sender can ignore the request and continue transmitting. In this case, the receiver must re-request the interrupt for the request to remain valid. Abbott ASI instruments and systems (acting as senders) do not honor the interrupt requests originating from the receiver. Receiving the [EOT] character in place of an [ACK] character is treated equivalent to receiving the [ACK] character. Abbott ASI instruments transmit all available data before entering the termination phase and relinquishing control of the data link (return to neutral state).

Error HandlingWhen errors in the data transmission occur, both the receiver and sender must have orderly recovery procedures.

The receiver checks every frame for defects. The receiver sends a [NAK] reply if it receives a defective frame. When the sender receives a [NAK], it re-transmits the last frame using the same frame number.Re-sending a Frame after a Transmission Failure. The receiver indicates a transmission failure with a [NAK].

Figure 1.18: Re-sending a Frame After a Transmission Failure. The receiver indicates a transmission failure with a [NAK].

Sender Receiver1

2[EOT]

Frame

Sender Receiver

1

2[NAK]

3

Frame 1

Frame 1



ASI instrument communication software depends on properly framed transmissions being received. If an [STX] is received, it is an indication that a frame is being transmitted. If all of the components of a frame are not received in proper relationship to one another, the frame is rejected.

A frame is rejected by the receiver for several reasons, including:

Character structure errors are detected in parity, baud rate, etc., or transmission is improperly framed.

The frame checksum from the sender does not match the checksum on the receiving end.

The frame number is incorrect. The number must be the same as the last one rejected or one number higher than the last one accepted by the receiver.

When the sender receives anything other than an [ACK] or an [EOT], it updates a re-transmit counter by one and re-sends the frame. A frame can be re-transmitted a maximum of six times. After that, the sender must abort the message and proceed to the termination phase.

If an [EOT] is encountered by the ASI instruments during the processing of a frame, the instruments return to idle state assuming that the sender terminated transmission prematurely. The sender must re-establish the connection in order to continue.

Incrementing the Frame Counter. The sender keeps track of retransmissions with a frame counter.

Figure 1.19: Incrementing the Frame Counter. The sender keeps track of retransmissions with a frame counter.

NOTE: If the [ACK] is corrupted during transmission, the sender of data retransmits the last frame, since any character received other than an [EOT] or [ACK] is treated as a [NAK]. However, since the [ACK] was already transmitted for that frame, the receiver [NAK] duplicates frames to avoid any possibility of infinite loops. This leads to Termination Phase after six attempts.

Sender Receiver

1

2[NAK]

4

Frame 1

Frame 1

3IncrementRetransmit

Counter



Time-outsThe sender and receiver have timers to control the coordination between them and to allow a recovery method in the event a communication line fails to respond.

During the Establishment PhaseThe sender sets a timer when sending an [ENQ]. If a reply is not received within 15 seconds, a time-out occurs and the sender proceeds to the termination phase. If the host computer, acting as the receiver, detects contention, it sets a timer. If an [ENQ] is not received from the instrument within 20 seconds, a time-out occurs and the receiver regards the link as being in a neutral state.

During the Transfer PhaseThe sender sets a timer when transmitting the last character of a frame. If a reply is not received within 15 seconds, a time-out occurs and the sender proceeds to the termination phase. The receiver sets a timer when first entering the transfer phase or when replying to a frame. If no reply is received within 30 seconds, a time-out occurs and the receiver regards the link as being in a neutral state. A time out also occurs if an incomplete frame is received and the timer expires. For example, if ASI instruments do not receive the [CR] [LF] characters at the end of a frame, a time-out may occur while the instrument is waiting for the last characters, before processing the frame.

Termination PhaseDuring the termination phase, the sender transmits the [EOT] transmission control character, notifying the receiver that all of the information has been sent. The sender regards the link to be in a neutral state. After receiving the [EOT], the receiver regards the link to be in a neutral state.

Restricted Message CharactersCertain characters cannot be used in messages. The following table lists characters not allowed in message text.

Table 1.4: Restricted Message Characters

Character Symbol

Definition

[SOH] Start of Header[STX] Start of Text Transmission[ETX] End of Text Transmission



[EOT] End of Transmission[ENQ] Enquiry[ACK] Acknowledge[DLE] Data Link Escape[NAK] No Acknowledge[SYN] Synchronous Idle[ETB] End of Transmission Block[LF] Line Feed[DC1] Device Control Character 1[DC2] Device Control Character 2[DC3] Device Control Character 3[DC4] Device Control Character 4

Table 1.4: Restricted Message Characters

Character Symbol

Definition



ASTM E 1381-91 Sender/ Receiver State DiagramCopyright ASTM.Reprinted with permission.

Figure 1.20: Sender/Receiver State Diagram

A1 STATE DIAGRAMReceiving Device Sending Device

ASTM E 1381

Idle

Datato Send

Waiting

Next FrameSet Up

Waiting

Contentionor Busy Timer

Running

InterruptRequested

Awake

Waiting

FrameReceived

Have Datato Send

Old FrameSet Up

Frame Ready

NOTE 1 %8 represents modulo 8.NOTE 2 = represents assignment of a value. Timer: = 15 resets the timer to 15 s as used here.NOTE 3 Arrow associated normal text denotes a condition; arrow associated italicized text denotes action taken.

Receive or Contention

Timer (Inst) = 1 or(Comp) = 20

or Busy Timer = 10

Done

Time Out

Accept

Receive

TimeOut

Send

Retries < 6

Repeat Frame

Bad Frame

Busy Receive

Receive orTime Out

Get Frame

GoodRepeatFrame

Good NewFrame Frame

OK

Receiving any characterexcept or

Send

Zero Retry CountIncrement %8 Count

Ignore

Increment%8 Count

Send FrameTimer = 15

Increment RetriesReceive

Retries = 6Send

New FrameIncrement%8 Count

Increment%8 Count

Send Timer = 30

Send Timer = 30

Send Timer = 30

Send Set %8 Count to 1

Timer = 30

Send

Set %8 Count to 1Send

Timer = 15

Zero Retry CountReceive



Table 1.5: ASTM E 1381-91 Communication States (for Instrument)

Initial State Condition Action Final Stateidle Have data to send (periodic

check)ContentTimer



NOTES



Section 1Presentation Layer Message Content

Presentation Layer

Figure 1.21: Presentation Layer

The Abbott Standard Interface (ASI) uses the protocol defined by ASTM E 1394-91 standard as the basis for the message content layer of instrument communications software. This layer specifies the conventions used in structuring information (messages) for transmission to external host systems and for receiving information from these host systems.

MessagesThe Presentation Layer requires that transmission and reception of all data must be performed using messages. A message consists of complete study files on one or more patients. Each message is a string of records which in turn are made up of fields. The following figure shows the basic structure of a message.Message Logical Structure. Messages are subdivided into records which are made up of fields.

Figure 1.22: Message Logical Structure. Messages are subdivided into records which are made up of fields.

The high-level protocol follows two general conventions:

A hierarchical convention is implemented where records higher in the hierarchy contain information that is common to all records lower in the hierarchy.

A positional convention is used to define the structure of the records.



Data Link Layer Data Link LayerPhysical Layer

Message

RecordField

Abbott Standard InterfacePresentation Layer Message Content Section 1


These conventions allow the fields, and thus the records, to vary in length. The ASTM E 1394-91 standard allows manufacturers the flexibility to:

Create new record types through the use of the Manufacturer Record.

Define the structure of certain existing fields. Define the structure of new manufacturer records.

This manual describes how Abbott instruments use this flexibility.

RecordsRecords are collections of related information within a message. For example, one record may contain information about the system sending the message and the system receiving the message while another record may contain personal information about a patient who is to undergo tests. Records begin with an ASCII alphabetical character, called a record identifier, and end with a carriage return. In the following example, the record identifier is H, which is used to identify the Header Record.

ASI instruments use uppercase letters for all record identifiers transmitted. ASI instruments can receive upper or lowercase letters for record identifiers. The following table describes the records that Abbott instruments use and their associated record identifier fields.

H [CR]

Table 1.6: Record Types

Record Type Record ID Field

Level Description For Field ContentsRefer to

ASTM E 1394-91, Section

Header H 0 Identifies the message.Contains information about the sender and receiver of the message, such as location and type of equipment used to send and receive the message.

7

Patient Information P 1 Contains information about a patient. 8Request Information (Query)

Q 1 Used to request information on a range of test results or test orders from another system.

12

Test Order O 2 Contains information defining tests performed or requested.

9

Result R 3 Contains information about test results. 10Comment C 1 4 Contains comment text on the preceding record. 11


Abbott Standard InterfaceSection 1 Presentation Layer Message Content

The records within a message are arranged in a hierarchy of levels. The records higher in the hierarchy contain information that is common to all records that are lower in the hierarchy. The lowest number is the highest in the hierarchy. For example a Level 2 record is higher than a Level 3 record.

Manufacturers Records and Comment Records may be used within any level except Level 0.

Each level, other than Level 0, must be preceded by a higher level. The Manufacturer and Comment Records can be inserted at any level in the hierarchy and are considered to be one level below the preceding record.

For example, a Comment Record below a Patient Record at Level 1 is considered a Level 2 record and contains comments about the patient in the Patient Record. A Comment Record below a Test Order Record (O) is considered a Level 3 record and contains comments about tests described in the Test Order Record.

Manufacturer Information

M 1 4 Provided for custom use by the instrument or computer system manufacturer.

15

Scientific S N/A Not used. 14Message Terminator

L 0 Terminates the message. 13

Table 1.6: Record Types (continued)

Record Type Record ID Field

Level Description For Field ContentsRefer to

ASTM E 1394-91, Section

Abbott Standard InterfacePresentation Layer Message Content Section 1


The following figure shows how the Comment and Manufacturer Records fit into a message hierarchy.

Figure 1.23: Comment and Manufacturer Records. These records can be placed anywhere in a message between the Header and Message Terminator Records.

ASI instruments may optionally support the use of the Request Information Record (Q). Refer to the instrument specific section of each Abbott Standard Interface RS-232 manual for details on that instruments support of the Request Information Record.

ASI instruments do not accept the Request Information Record as part of a message containing Patient (P) and Order (O) Records. Also, ASI instruments do not transmit the Request Information Record as part of a message containing Patient (P), Order (O), and Result (R) Records. When used, the message only includes the following:

Manufacturer and Comment records may be used in conjunction with the Request Information Records, as needed by specific instruments.

Message 1Level 0 Header Record (H) Level 1

Comment Record (C) - Comments about the message sender and/or receiverManufacturer Record (M) - Custom information about the message senderand/or receiverPatient Record (P)

Level 2 Comment Record (C) - Comments about the patient Manufacturer Record (M) - Custom information about the patientTest Order Records (O)

Level 3Comment Record (C) - Comments about the tests orderedManufacturer Record (M) - Custom information about the tests orderedResult Records (R)

Level 4 Comment Record (C) - Comments about the test resultsManufacturer Record (M) - Custom information about the test results

Level 0Message Terminator Record (L)Message 2Level 0Header Record (H) Level 1

Request Information Record (Q) Level 2

Comment Record (C)Level 0Message Terminator Record (L)

Comment and Manufacturer Records always refer to the preceding record and are one level below the record they are referring to.

No records are allowed below a Message Terminator Record except a Header Record.

Header Record (H)

Terminator Record (L)Request Information Record (Q)


Abbott Standard InterfaceSection 1 Presentation Layer Message Content

ASI instruments and systems may be batch as well as real time. Batch instruments and systems communicate the results of a run all at one time, usually at the end of that run. The results message consists of information on multiple samples. Real time systems, however, communicate the information as it becomes available. These systems normally communicate a shorter results message consisting of information on the results of only one sample test (the one that was just completed).

FieldsFields are groups of characters that define a specific piece of information within a record, such as a patients name, telephone number, or street address. For example, the Patients Name field in the Patient Record is shown below:

Fields are position dependent. That is, fields are identified by their relative position i

tailieu xn abbott

Documents

abbott trained personnel

operation of abbott

abbott standard interface

abbott laboratoriesabbott

system documentation

informational use

persons knowledgeable

service representatives