IEEE Std 1073.3.1-1994 IEEE Standard for Medical Device Communications-Transport Profile-Connection Mode.pdf

The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright © 1995 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 1995. Printed in the United States of America. ISBN 1-55937-504-3 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. IEEE Std 1073.3.1-1994 IEEE Standard for Medical Device CommunicationsTransport Profi leConnection Mode Sponsor Medical Information Bus Committee of the Engineering in Medicine and Biology Society Approved December 13, 1994 IEEE Standards Board Abstract: A local area network (LAN) for the interconnection of computers and medical devices is defi ned by the specifi cations and guidelines set forth in this standard. The functions, features, and protocols of the intra-room communications subnet of a bedside communications network known as the Medical Information Bus (MIB) are defi ned. This communications subnet is the functional equivalent for the MIB of the Transport, Network, Data Link, and Physical layers of the Organization for International Standards (ISO) Reference Model for Open Systems Interconnection (OSI). This standard defi nes the services and protocols for the MIB Transport, Net- work, and Data Link layers. Keywords: bedside communications controller (BCC), bedside medical device, Data Link layer, device communications controller (DCC), frame, fl ow control, high-level data link control (HDLC), Medical Information Bus (MIB), Network layer, Physical layer, subnetwork, Transport layer Authorized licensed use limited to: Tsinghua University Library. Downloaded on December 25,2010 at 10:26:42 UTC from IEEE Xplore. Restrictions apply. IEEE Standards documents are developed within the Technical Committees of the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an interest in partici- pating in the development of the standard. Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, mar- ket, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and com- ments received from users of the standard. Every IEEE Standard is subjected to review at least every fi ve years for revision or reaffi rmation. When a document is more than fi ve years old and has not been reaffi rmed, it is reasonable to conclude that its contents, although still of some value, do not wholly refl ect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affi liation with IEEE. Suggestions for changes in docu- ments should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specifi c applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appro- priate responses. Since IEEE Standards represent a consensus of all concerned inter- ests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason IEEE and the members of its technical com- mittees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE Standards Board 445 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA IEEE Standards documents may involve the use of patented technology. Their approval by the Institute of Electrical and Electronics Engineers does not mean that using such technology for the purpose of conforming to such standards is authorized by the patent owner. It is the obligation of the user of such technology to obtain all necessary permissions. Authorized licensed use limited to: Tsinghua University Library. Downloaded on December 25,2010 at 10:26:42 UTC from IEEE Xplore. Restrictions apply. iii Introduction (This introduction is not a part of IEEE Std 1073.3.1-1994, IEEE Standard for Medical Device CommunicationsTransport Profi le Connection Mode.) This communications subnet is a member of the 1073 family of standards for computer communication with medical devices, known as the Medical Information Bus (MIB). Collectively, the MIB family of standards covers the entire seven layers of the communications architecture of the Open Systems Interconnect (OSI) Reference Model. This particular standard specifi es the services and protocols for the Data Link, Network, and Transport layers, also known as layers 24. This standard is intended to facilitate fast, reliable, and robust communications with a variety of medical devices at a single patient bedside in an integrated manner. The services and protocols defi ned address the special requirements of the medical users in the patient bedside environment. These include automatic detection of device connections (and disconnections) and establishment of communications without any action on the part of the user other than plugging in the communications cable; logical association of devices with a particular geographical location (a particular bed, and, by inference, a particular patient); and unique identifi cation of devices on the network without address settings, switches, or unique codes in read-only memory. The services and protocols of this standard are optimized for use in the medical bedside environment. As such, this communications subnet addresses the special requirements of the medical environment in which it is intended to operate. Consequently, this standard should be considered a “special purpose” communications facility. Nonetheless, for the services defined, this is a self-contained and stand-alone specification for the lower four layers of the OSI Reference Model. There are no restrictions on the user entity which makes use of this standard. The scope of this standard does not preclude the use of the standard for domains outside of the medical bedside environment, but it is not the intent to define the requirements for, nor to optimize this standard for, those other domains. At the time this standard was completed, the P1073.3.1 Working Group had the following membership: Robert J. Kennelly, Chair John J. Harrington, Vice Chair Mike Glass, Lower Layers Chair Charles BrillHarald GreinerDave Ostler Don EddlemanBill HawleyS. Mark Poler Yossi ElazEarl F. HoernerM. Michael Shabot John FioriglioGideon KantorBob Strehlow David F. FranklinRandy KrohnCharles Turini Kenneth FuchsRon LevinCliff Weber Reed GardnerScott MorinJan Wittenber Lee GolterKatherine NicholsDale Zeskind Authorized licensed use limited to: Tsinghua University Library. Downloaded on December 25,2010 at 10:26:42 UTC from IEEE Xplore. Restrictions apply. iv The following persons were on the balloting committee: J. A. P. M. AnsemsShaun J. GlennS. Mark Poler George W. BeelerLee GolterVince C. Price Jeffrey B. BeersHarald GreinerRobin Roehl Thomas BookerCharles GropperAnders B. Rorholt Branko Celler Gene Gryziecki Ricardo F. Ruiz Todd CooperJames HanCarlos H. Salvador Phil CurranJohn J. HarringtonPascal Schirato James R. “Bob” DavisBill HawleyM. Michael Shabot Alan FiglerEarl F. HoernerAndrew L. Spector Paul FitzmeyerJorg KampmannMike Spicer Michael FloetottoConstance KellySunder Subramanian David F. FranklinTimothy J. KellyAlessandro Taddei Kenneth FuchsRandy KrohnHelmut Thiemann Elmer GabrieliChristopher LynchCharles Turini John GagePaul OehlerJan Wittenber Reed GardnerJames R. PetersonDale Zeskind When the IEEE Standards Board approved this standard on December 13, 1994, it had the following membership: Wallace S. Read, Chair Donald C. Loughry, Vice Chair Andrew G. Salem, Secretary Gilles A. BarilDonald N. Heirman Joseph L. Koepfi nger* Bruce B. BarrowRichard J. HollemanD. N. “Jim” Logothetis José A. Berrios de la PazJim IsaakL. Bruce McClung Clyde R. CampBen C. JohnsonMarco W. Migliaro James CostantinoSonny KasturiMary Lou Padgett Stephen L. DiamondLorraine C. KevraArthur K. Reilly Donald C. FleckensteinE. G. “Al” KienerRonald H. Reimer Jay Forster*Ivor N. KnightGary S. Robinson Ramiro GarciaLeonard L. Tripp *Member Emeritus Also included are the following nonvoting IEEE Standards Board liaisons: Satish K. Aggarwal James Beall Richard B. Engelman Robert E. Hebner Valerie E. Zelenty IEEE Standards Project Editor Authorized licensed use limited to: Tsinghua University Library. Downloaded on December 25,2010 at 10:26:42 UTC from IEEE Xplore. Restrictions apply. v Contents CLAUSEPAGE 1.Overview 1 1.1 Scope 1 1.2 Purpose. 1 1.3 Standards compatibility . 2 2.References 2 3.Definitions 3 4.Abbreviations and acronyms 8 5.Communications nodes on the subnet 10 5.1 Overview 10 5.2 Bedside communications controller (BCC). 11 5.3 Device communications controller (DCC) 11 6.Inactive Transport layer. 11 6.1 Service specification 11 6.2 PDU specification 19 6.3 Mode of operation 19 7.Inactive Network layer. 22 7.1 Service specification 22 7.2 PDU specification 29 7.3 Mode of operation 30 8.Data Link layer 32 8.1 Table of capabilities. 32 8.2 Service specification 32 8.3 PDU specification 49 8.4 DL elements of procedure 53 8.5 DL procedure descriptions. 64 8.6 Interrupt requests and acknowledgments. 74 8.7 Formal description of procedures 75 9.Labelling and conformance requirements 175 9.1 Implementation requirements 175 9.2 Labelling requirements 175 9.3 Conformance requirements 175 Annex (normative) Systems and data link management 177 Authorized licensed use limited to: Tsinghua University Library. Downloaded on December 25,2010 at 10:26:42 UTC from IEEE Xplore. Restrictions apply. 1 IEEE Standard for Medical Device CommunicationsTransport Profi le Connection Mode 1. Overview 1.1 Scope The specifi cations and guidelines set forth in this standard are intended to defi ne a local area network (LAN) for the interconnection of computers and medical devices. This standard defi nes the functions, features, and protocols of the intra-room communications subnet of a bedside communications network known as the Medical Information Bus (MIB). This communications subnet is the functional equivalent for the MIB of the Transport, Network, Data Link, and Physical layers of the Organization for International Standards (ISO) Reference Model for Open Systems Interconnection (OSI). This standard defi nes the services and protocols for the MIB Transport, Network, and Data Link layers. The Physical Layer, specifi ed in IEEE Std 1073.4.1-1994 1 a)Uses EIA-485 for data transfer. b)Provides DC power distribution for device communications hardware. c)Provides a pair of special function signals for the purposes of providing device connection indications, interrupt requests, time synchronization, and frame delimiting. d) Specifi es a unique MIB connector and cable. The MIB Data Link layer offers services for data line connection, data transfer, and disconnection using high-level data link control (HDLC) procedures. The Transport and Network layers are inactive i.e., there are no functions for packet assembly and disassembly (PAD) or end-to-end acknowledgments or any other services usually associated with Transport and Network layers. See fi gure 1. 1.2 Purpose The purpose of this subnet is to provide connection-oriented communications services. It is functional as a stand-alone network for any application entity that can directly use the transport services offered. The LAN is designed to provide a logical association between a patient and those medical devices connected to, monitoring, or otherwise data-related to that patient and in close physical proximity. New device connections are automatically detected and communications are established with those new devices without the need of any user input. The network is intended to provide a highly reliable data transfer medium with a priority on providing quantitative throughput to each attached node. The network is intended to be highly 1 Information on references can be found in clause 2. Authorized licensed use limited to: Tsinghua University Library. Downloaded on December 25,2010 at 10:26:42 UTC from IEEE Xplore. Restrictions apply. IEEE Std 1073.3.1-1994IEEE STANDARD FOR MEDICAL DEVICE COMMUNICATIONS 2 robust in an environment where devices are frequently connected to and disconnected from the network. It responds to a changing device topology by establishing new connections and detecting disconnections in a manner that is transparent to the clinical user. Hence, in regard to the device nodes on the network, it is a completely automatic and self-regulating communications subnet. 1.3 Standards compatibility The polling protocol procedures defi ned in clause 8 utilize some of the concepts and principles, as well as commands and responses, of the link control procedures known as two-way alternate normal response mode (TWANRM), as defi ned in ISO/IEC 4335: 1993. TWANRM defi nes a half-duplex data link in which there is a primary station and a secondary station. The secondary station shall only transmit in response to a transmission by the primary station. For the purpose of this standard, the bedside communications controller (BCC) is the primary station, while the device communications controller (DCC) is the secondary station. The frame structure defi ned for the data link procedures (as described in clause 8) utilizes the same basic structure and format as defi ned in ISO/IEC 3309: 1993 with the same fi eld usage, except that some fi elds are unused and the poll bit usage is defi ned by this standard. Use of the exchange identifi cation (XID) frame for negotiation purposes during connection establishment conforms with usage described in ISO/IEC 8885: 1993. The Physical layer media specifi cation and data transfer coding are called out in IEEE Std 1073.4.1- 1994 and EIA-485 (1983). 2. References This standard shall be used in conjunction with the following standards. When the following standards are superseded by an approved revision, the revision shall apply. EIA-485 (1983), Standard for Electrical Characteristics of