The main goal of this demo is a simple reproduction of IFC-CNR experience in integrating different ECG devices in IFC-CNR Clinical Information System. Both ELAN (Remco-Cardioline) and AR1200 (ET-Cardiette) ECG devices declare their SCP-ECG compatibility; ELAN with 1.0 revision, AR1200 with 1.3. Because of this revision difference, some minor problems still exist in reading an SCP-ECG record on a different ECG device and different parsing strategies have been implemented in IFC-CNR Clinical System.
In brief:

• ELAN and AR1200 ECG devices have been interfaced with a PC, each one using a proprietary interfacing tool: ELAN uses an UDP protocol based on an ethernet board and AR1200 uses a proprietary infrared communication protocol.
• An SCP-ECG record has been produced with AR1200 ECG device and sent via Cardiette LEMS program to a PC of the IFC-CNR Clinical Information System.
• That file has been copied into a specific Cardioline directory thus allowing download, via Cardioline SCPserver program, on the ELAN ECG device.
• Once downloaded, the same SCP-ECG record has been printed, with patient data and diagnosis on the ELAN ECG device. The audience can verify the absolute identity in the two printouts produced by the two different cardiographs.
• From the Clinical Information System point of view, two SCP-ECG records, one coming from ELAN and one from AR1200 ECG device, have been simply copied from original receiving directories to a specific directory which is monitored by a specific daemon program.
• That program, after parsing SCP-ECG record, performs some checks on patient data and eventually stores ECG signal and diagnostic statements into the IFC-CNR Clinical Information System database.
• The IFC-CNR Clinical Information System is than able to display ECG signal and data allowing clinical overreading.