Skip Navigation
Human Research Program

Integration of iRevive with the Lightweight Trauma Module

Completed Technology Project

Project Description

Integration of iRevive with the Lightweight Trauma Module
Key to this system is the collection and presentation of data. This has required: 1) rewriting the iRevive GUI and database codebase using current technology; 2) defining the communication protocol between the LTM and iRevive; and 3) building a LTM simulator to debug the iRevive-LTM communication protocol, which was hardcoded into the LTM. In the past year we have rewritten the GUI and database for iRevive to increase the speed, portability, and maintainability of the codebase, which is now in Python for improved interaction with the Internet and the world wide web. The GUI has improved graphics and more complete pull down menus, to facilitate ease of use and generate a more complete record with less user training required. Another focus has been defining a communication protocol for the LTM to exchange data with iRevive. This protocol was implemented as an LTM simulator for testing, debugging, and then in a FPGA. Our approach defined a base protocol to transmit parametric vital sign information. It was then extended to transmit wave type data, alarms, device configuration, and connection initiation. This effort produced a high-level protocol specification. We are using traditional Internet protocols, including UDP at the transport layer to exchange end-to-end packets. This information includes a sequence number, time stamp, packet type, and meta information describing the data from the LTM. The packet format defines all parametric vital sign data from each device module in the LTM, including SpO2, EtCO2, temperature, invasive and non-invasive blood pressure, ECG, and ventilator settings. These packets contain meta information, which describes attributes such as when measurements should be flagged with an alarm and the measurement units. The packet format also defines device alarms including their priority, how an alarm is indicated to the user (i.e., audible and latching), and information unique to each LTM device module. Work was also done to define the protocols and processes required for waveform data as well as an initiation protocol. Waveform data will be displayed with allowable ranges. Initiation protocols will synchronize these ranges and timing as well as provide the connection between LTM and iRevive. As the funding period is now complete, and the defined goals reached, the technical, funding, and schedule risk for this proposal are by definition low or non-existent. More »

Anticipated Benefits

Primary U.S. Work Locations and Key Partners

Technology Transitions

Light bulb

Suggest an Edit

Recommend changes and additions to this project record.

This is a historic project that was completed before the creation of TechPort on October 1, 2012. Available data has been included. This record may contain less data than currently active projects.