Introduction

Pre-requisites

1. Although Cardioline touchECG compatibility was added with ClinSpark Agent version 1.4, we recommend using Agent version 23.1 or above (https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/3700490299/ClinSpark+Agent?src=search).

Overview

A quick walk through video showing the basic use of touchECG after configuration…

Advanced Use Cases

Demo Mode

Cardioline has designed touchECG to run in Demo mode, and thus it allows for working with simulated ECGs rather than requiring actual hardware or applying leads / procuring a simulator. ClinSpark allows for this demo mode to be set proactively through device configuration, and when set will have the user.config XML file contain the HDPLUS_SN to be hardcoded to 'DEMO'. Here is the setting:

Prevent ECG data being stored on a local or shared drive

An engineering walkthrough showing the configuration required to prevent ECG data being stored on drives or servers - the data is ingested into ClinSpark only.

File Formats

1. Cardioline touchECG creates both PDF and ‘SCP’ (data) files that are consumed by ClinSpark.

Data Workflow

• Invoke device; agent receives digitally signed JSON timepoint payload from the clinspark server

  • Timepoint contains a unique 'item group data id'

• Agent attempts to locate the touchECG EXE; EXE path is built using 'LocalAppData' environment variable and appends Cardioline/touchECG/touchecg.exe

  •   If EXE is not found, user is given a warning message and test ends

• Agent attempts to find working results dir; path is built using 'AppData' environment variable and appends Local/touchECG/clinspark to it

• Agent ensures an archive directory is present as a subdirectory of results using date timestamp and host name information

• Agent creates an order text file that contains ID (randomization, lead-in, screening number), FIRSTNAME (mapped to study event and nominal timepoint), LASTNAME (study name), SEX (1=male, 2=female), BIRTHDATE (formatted yyyyMMdd), ACESSIONNUMBER (mapped to item group data id described above)

• Agent creates user config XML file applying logic to configure the powerline filter, SCP path, PDF path, database path (directory where text and user config files are written)

• When user order text and user config files are written, the touchECG executable is invoked in a separate thread, and it is passed as command line arguments -g -d <order file path>, -c <user config path>

• The agent then presents a message to the user that the order has been created, and it instructs the user to complete the test and press 'ok' when touchECG is closed

• When the user presses 'ok' the agent then begins the process to look for the result files; the result files must be named with the item group data id and be immediately followed with a suffix

• If the files are not found in a given poll cycle, the agent will attempt to look again; if it is determined that the EXE is no longer active and 8 seconds have elapsed, the agent will give up polling and return an error message to the user

• When the files are found, the SCP file is parsed and the intervals and interpretations are returned to the browser as JSON, and then the respective fields are set in the browser using JavaScript; the original SCP file is also saved with the ClinSpark form in the browser

Manufacturer's Reference Material

Watch on YouTube

User Manual

Service Manual

Embedded here for your convenience…

Additional Reference Material

1. SCP-ECG V3.0: An enhanced standard communication protocol for computer-assisted electrocardiography

   1. https://ieeexplore.ieee.org/document/7868741

2. Standard Communications Protocol for Computer-Assisted Electrocardiography

   1. https://www.iso.org/standard/46493.html