QRS CARDS INTEGRATION PROCESS - 07.18.02

Initial integration of pcmcia cards demonstrated and found not to 
meet data collection requirements. Data collection requirements 
explained on this date allowing for better specification to programmer

Setup, startup and module initialisation process shown graphically.


----------------------
Problem 1           
    OfficeMedic does not allow concurrent communication with EKG and
     PULSEOX cards.

 Solution
    NeatTools module has been created which talks to PULSEOX card, allowing
    collection of pulse rate and %sp02 directly from card concurrently with 
    OfficeMedic performing EKG. 

Status    OXI Data collection functionality demonstrated.


----------------------
Problem 2
     Requirement for actual  waveform  from oximeter explained. Current
     implementation not reading value "SIGNAL INTENSITY"   from oxicard.  

Solution 
     NeatTools module guru developer informed of requirement
     Guru has oxi SDK for reference

Status:     Pending guru response

------------------------

Problem 3 
    Require data collection as close to sensor as possible ( ie raw ) to allow 
    specific analysis to be performed by East Coast.
    Require sampling at 1024 Hz, or to be able to directly modify sampling
    of data

Solution
    Neat Guru informed of requirements

Status:    Pending guru repsonse. Cross Reference with Problem 4
----------------------------

Problem 4
   Investigation of the QRS OfficeMedic software reveals that patient EKG data is stored
   into the MS-SQL database,  with no immediate indication from the software 
   that individual patient records can be extracted.

   Current protocol involves that complete patient database will be burned
    to patient unique CD-rom  for dispatch via physical courier. 
   Depending on actual physical size of test database (to be determined during testing 
   protocol evaluation), this database may be uploaded  to an ftp server (address to be determined)

Solution (4A)
   Database sent to east coast analysis dept for investigation of data extraction potential.
   Possibilites include: 
    -  MS_SQL direct extraction of data ? Find someone who speaks SQL to answer this question.
    -  Direct binary data extraction from MS-SQL ?  
    - Contact with QRS manufacturer for information about data format and extraction from 
       patient record

Status (4A):   PENDING (east coast evaluation)


Solution (4B)
   NeatTools guru to be provided with EKG SDK.
   Request NeatTools module for concurrent EKG  and OXI raw data collection    
   Request sample rate as above to collect raw signals from cards, display within NeatTools, 
   and store to non proprietary, accessible datafile 
   Request timestamping of data points to allow precise correlation of different waveforms.

Status (4B) : PENDING (west coast guru)

---------------------------------------

Problem 5
    Fingerprint measurement with Bioscrypt sensors : Assembly of components for 
    interface with laptop.

Solution
    Hardware integration expert to construct from supplied component parts.

Status
   Parts dispatched to construction expert. Waiting.

-----------------------------------------

Problem 6
    Galvanic Skin Resistance measurement

Solution
     NeatTools and TNG-4 hardware interface

Status
    Awaiting delivery of TNG-4 hardware due Siggraph 

-----------------------------------------
RESOURCES:
QRS OfficeMedic | PulseOxi  SDK  |  EKG SDK
VRMC registered as OEM developer with QRS, so assistance / technical query resolution
may be possible directly from manufacturer or within SDK (assuming one reads and speaks
SDK)