No.1802_0000005686
10
Infinity Network RS-232 Export Protocol
RS-232 Export Protocol
Introduction
1 Introduction
1.1 Scope of protocol
This document defines the requirements and schemes for the message
protocol used between Olympus compliant patient monitors (servers) and
client systems such as Clinical Information Systems, Anesthesia Record
Systems and Data Loggers for RS-232 based communications.
The document is partitioned into 2 parts:
1. The first part deals with general guidelines for implementation and
interfacing with Drager devices supporting the Export Protocol.
2. The second part specifies the messages used during Basic Data Mode.
This mode support exchange of demographics, the parameter dictionary
and parameter data.
In the future we expect to add additional ‘Parts’ to this document which define
further extensions to the Export Protocol. For example, we may add support
for waveforms, which is referred to in places as ‘Extended Data Mode’. In
anticipation of this, the document sometimes refers to reserved bytes and
fields which are reserved for this mode.
1.1.1 VF level protocol
enhancement
The new parameters available in the VF release require the use of a second
parameter block. Use of this parameter block requires applications to
recognize a 2 byte ID (i.e. FExxh). While the Export Protocol has always
specified that a second byte was possible, we were concerned that some
applications have not properly implemented this feature. As a result we have
limited the previous 057h Data Message Request to those parameters
available using a single byte ID. We have defined a new Data Message
Request 77h, which will transmit all parameters using 2 byte Ids which
eliminates the use of the existing 57h data request message.
1.2 Basic protocol goals and assumptions
The protocol defined in this document is constructed to meet a number of
goals:
– The communication scheme should minimize the need for having to
perform simultaneous client software releases each time new parameters
are added to an Olympus compliant server. A system of self defining
parameter definitions is used at startup time so that the client can identify
and label all possible parameters which might be sent from the server
(host bedside).
– No “edge triggered” logic is used in the message scheme; i.e., data is
sent repetitively, and not only when things change.
– All available parameter data is available to the client.
– It is assumed that the client does not need to track the alarm condition of
the server, however, provision is made to track the alarm state of each
parameter.
剩余55页未读，继续阅读
ert11569etg
- 粉丝: 1
- 资源: 11
我的内容管理
展开
最新资源
- IPQ4019 QSDK开源代码资源包发布
- 高频组电赛必备：掌握数字频率合成模块要点
- ThinkPHP开发的仿微博系统功能解析
- 掌握Objective-C并发编程：NSOperation与NSOperationQueue精讲
- Navicat160 Premium 安装教程与说明
- SpringBoot+Vue开发的休闲娱乐票务代理平台
- 数据库课程设计：实现与优化方法探讨
- 电赛高频模块攻略：掌握移相网络的关键技术
- PHP简易简历系统教程与源码分享
- Java聊天室程序设计：实现用户互动与服务器监控
- Bootstrap后台管理页面模板（纯前端实现）
- 校园订餐系统项目源码解析：深入Spring框架核心原理
- 探索Spring核心原理的JavaWeb校园管理系统源码
- ios苹果APP从开发到上架的完整流程指南
- 深入理解Spring核心原理与源码解析
- 掌握Python函数与模块使用技巧
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
