Download Mar 3 rd

Using PDAs to Automate Vital
signs Acquisition and Storage
(UPAVAS)
March 4, 2005
Midterm Spring Presentation
Sponsor:
Dr. Paul Harris, GCRC Informatics Director
Members:
Chris Heath, BME/EE
Adam Nagel, CompE
Chris Nash, EE
Brendan Soar, CompE
This Presentation
• Project overview
– GCRC background
– Solution requirements
• Selected design approach
• Demonstration
• Future work
What is the GCRC?
• General Clinical Research
Center
• GCRC monitors patients taking
experimental medicines and
suffering from rare medical
conditions
• Patients’ vital signs are
recorded frequently
• Sponsor D. Paul Harris is
Informatics Director, operating
and maintaining all servers
and data collection systems
Measuring equipment and interfaces
• Vital signs monitors
– DINAMAP Pro 1000 and MPS
Select
– RS-232 (serial)
– Opto-Isolated Adapter
• GCRC network
– 802.11b wireless LAN w/ SSID
• Data server
– MySQL server
– Web-based front end for
researchers
PDA Solution
Graffiti,
Touch screen
User
Commands
Device
Status
Data
PDA
Serial
commands
Dinamap
Monitor
Data
Desktop
Link
MySQL
Commands
SQL Server
PDA Solution, cont.
To User
Interface
PDA OS
802.11b
Bluetooth
Bluetooth
to Serial
Local
Storage
PDA
device
To GCRC
network
Dinamap
NI LABVIEW is the
selected design approach
• Labview obtained from
VUSE for free
– $300-$500 for GCRC
development license
• Pocket PC support
• Support for Bluetooth,
802.11b, RS232
Serial Communication Triumphs
• To verify the connection,
we had the machine print
binary garbage to RS232
• Once the settings were
correct, we were able to
trigger readings and
receive messages
• Successfully triggered
measurement and read
heart rate
Basic Functional Algorithm
Start
Start NIBP
determination
Request HR,
Parse response
Status
response
Store Data to file
Poll for
monitor model
Not Started OK
Monitor model
Started OK
NIBPD
Error
Upload data to
server
Other
Pro 1000
Yes
Alternative
Handlers
Study
Start
0–“busy”
Request NIBP
status
Upload
successful?
No
Check
status bit
Yes
1-“done”
Parse string for
DP, SP, MAP
No
(Timer) or
(User Trigger)
DB upload
error handler
DEMONSTRATION
Getting the data to
the MySQL server
• No compatible MySQL
library for PocketPC
platform
• Two workarounds
– Use a desktop as a “bridge”
• Desktop will run a “server”
VI that relays acquired data
to MySQL server using
ODBC
• This can be done over
Bluetooth or 802.11x
– Use PHP script on GCRC
webserver
• Device can use HTTP
protocol to connect, send,
and retrieve data
• Can be accessed by
device directly, or by
desktop “bridge” above
First Option
Use a desktop as a link
•
PDA
Desktop Computer
Configuration
Storage
Acquisition VI
Database Server
AirCable on
Serial Port
MYSQL Server
Data
Return
Code
Server
Info
Communication VI
Server VI
MYSQL
Query
String
ODBC
Bluetooth
COM Port
•
Advantages
– Involves mostly proven
components
– Simple server VI
application due to “data
dump” method
Disadvantages
– Requires modification of
solution requirements
– PDA must be returned
to central location
– More complex
procedure for users
Second Option
Use HTTP to access PHP pages
PDA
Acquisition VI
Webserver
Configuration
Storage
HTTP/Ethernet
• Advantages
– In line with original
Database Server
solution
requirements
– No “data dump” or
extra steps required
for nurses
– Real-time monitoring
of study progress
• Disadvantages
– HTTP access library
for eMbedded VC++
not yet identified
MYSQL Server
Data
Return
Code
Server
Info
Communication VI
ID, Vital
Signs data
HTTP/802.11x
PHP page
• Desktop link a
“fallback” if this cannot
be found
Role of MySQL Connection
• Acquired data
uploaded to server
– Return code to ensure
successful submission;
Results flagged if not
successfully submitted
– PHP-based web
interface allows realtime monitoring of
studies
Gantt Chart
To do list
• Acquisition component
– Add new features
– Beta test with nurses
• Data upload component
– Research identified alternatives
– Develop library for uploading
– Beta test library
• Field test of solution
• Develop documentation, presentation materials