...
Introduction
Pre-requisites
Although Cardioline touchECG compatibility was added with ClinSpark Agent version 1.4. However, we recommend using Agent version 23.1 or above (https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/3700490299/ClinSpark+Agent?src=search).
Cardioline touchECG software must be installed in the PC ‘LocalAppData’ directory (example:
<User>\AppData\Local\Cardioline\touchECG
Overview
A quick walk-through video showing the basic configuration and use of touchECG after configuration….
...
| Info |
|---|
At about 5’10” into the video, it switches to a demo of advanced ECG review using a third-party proprietary add-in application called CalECG (see AMPS CalECG). |
Advanced Use Cases
...
Cardioline has designed touchECG with the ability 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. Information about this can be reviewed in their service manual.
...
ClinSpark allows for this demo mode Demo Mode to be set proactively through global device configuration , and when set (via Devices > Configure). When set, the interface will have the user.config XML file contain the HDPLUS_SN in each invocation to be hardcoded to 'DEMO'.
Here is the setting:
...
Prevent ECG data being stored on a local or shared drive
...
Data Workflow
Invoke device; agent Agent receives digitally signed JSON timepoint payload from the clinspark 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 Agent then presents a message modal to the user in ClinSpark that the order has been created, and it instructs the user to complete the test and press 'ok' when touchECG is closed.
The test is completed in touchECG software; users will end the workflow and return back to ClinSpark.
When the user presses 'ok' the agent on the modal in Clinspark, 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 Agent will attempt to look again; if it is determined that the EXE is no longer active and 8 seconds have elapsed, the agent 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
...
Service Manual
Embedded here for your convenience…
...