Introduction

This Article describes the Settings to configure the Connection between custo diagnostic and Cosmed Omnia.

Requirements

Minimum Version are:

custo diagnostic: 4.5.x
cosmed Omnia: 1.4

Functionality

The current Interface has the following Functionality:

  1. The Selection of the Patient or the Order has to be done in custo diagnostic.
  2. The System can be run in two different Operation Modes:
    1. COSMED Omnia (master), custo diagnostic does not control the Training Device
    2. COSMED Omnia (slave), custo diagnostic control the Training Device
  3. The CPET Examination can be terminated in custo diagnostic OR in Cosmed Omnia.
  4. The Recall of an Evaluation can be done only throught custo diagnostic.

Settings in custo diagnostic

For the perfect operation you have to set up the following options:

  1. Select Cosmed Omnia as CPET Software in the Interface Selection
    Please compare also with the Types of the Interface


  2. Enable necessary Dialogues to ask the Customer for required Data
    For the Operation of Cosmed Omnia the Weight and Height of the Patient is mandatory!
    You have to enable these Options:


  3. Enable PDF-Grabbing
    The PDF Grabbing import the PDF into the Evaluation which is printed from Cosmed Omnia as Report while the Test.


  4. If custo diagnostic should make a Printout after the Examination you have to enable 'PDF attachments'. This Option add the via PDF Grabbing imported PDFs (Printouts) from Cosmed Omnia to the normal Printout of custo diagnostic. If you want to export these PDFs to the HIS you have to switch the 'Printout Type' to the Option 'PDF Export' and than enable in this Printout Type the Option 'PDF attachments'.

     

  5. Configure the LoginUserName and LoginPassword from Cosmed Omnia
    The Login Credentials are mandatory because its a part of the TCP/IP Communication.


  6. Configure the Program Name of Cosmed Omnia
    This Program will be started if you launch a CPET Test in custo diagnostic.


Settings in Cosmed Omnia

  1. Install Cosmed Omnia (min. Version 1.4) on the PC

  2. Start Cosmed Omnia the first Time and make it running

  3. Activate the TCP/IP Interface in the File "\%PUBLIC%\Documents\Cosmed\CosmedLab\ACS.XML". The File exists only you had start Cosmed Omnia one times. After that you have to edit the File manually.

    <ExtendedConfiguration Version="1">
      <General>
        <TimeOutMinCheckValue Type="System.Int32" Value="15" />
        <MenuMatrix Type="Tuple" TypeID="System.Int32" ID="2" TypeValue="System.Int32" Value="3" />
      </General>
      <EntityFramework>
        <SessionTimeout Type="System.Int32" Value="60" />
        <MaxRetryCount Type="System.Int32" Value="5" />
        <MaxDelay Type="System.Int32" Value="26" />
      </EntityFramework>
      <Bridge>
        <Debugger Type="System.Boolean" Value="True" />
        <Control Type="Tuple" TypeID="System.String" ID="tcp" TypeValue="System.String" Value="xml" TypeItem2="System.String" Item2="utf-8" TypeItem3="System.String" Item3="5530" TypeItem4="System.String" Item4="OmniaXB" />
        <Legacy Type="Tuple" TypeID="System.String" ID="legacy" TypeValue="System.String" Value="raw" TypeItem2="System.String" Item2="ascii" TypeItem3="System.String" Item3="" TypeItem4="System.String" Item4="" />
      </Bridge>
      <Ergo>
        <ShowDataOnProtocolChart Type="System.Boolean" Value="True" />
      </Ergo>
    </ExtendedConfiguration>

     To activate the Communication via TCP/IP you have to insert this Line inside the Section <Bridge>:

        <Control Type="Tuple" TypeID="System.String" ID="tcp" TypeValue="System.String" Value="xml" TypeItem2="System.String" Item2="utf-8" TypeItem3="System.String" Item3="5530" TypeItem4="System.String" Item4="OmniaXB" />
    

    Please be careful that only one Line of the Type <Control> in the Section <Bridge> exists.

     

  4. Start Cosmed Omnia
    Login as an Administrator. You can use these Credential also in the Configuration in custo diagnostic.
    With the Patient "DEMO SUBJECT" every time a Test can be performed.

  5. Configure the Device K5


  6. Start a test once time and select 'PC Software ECG' as HR Source and 'Ergoline900' as the bike. This is only possible after you had selected the Device K5!



 

Types of the Interface

In custo diagnostic → Settiungs → System → Workstation

the Type of Interface to Cosmed Omnia can be selected. This is comparable to an Operation Mode. The Selection is described as View from custo diagnostic.

SelectionOperation Mode

COSMED Omnia (slave)

Cosmed Omnia: do not control the Training Device
custo diagnostic: control the Training Device

COSMED Omnia (master)
ehemals  
COSMED Omnia

Cosmed Omnia: control the Training Device
custo diagnostic: do not control the Training Device


Special Settings in custo diagnostic

These internal Setting you can find in CSC->Daten-Export\CosmedOmnia. These Settings are available:

Setting

Default Value

Description

AutostartOmniaDebugMonitor

false

Starts a Debug Monitor Dialogue when the Communication is established. In this every Action / Reaction will be recorded during a Communication (Test) in Real Time.

AutostartOmniaProgram

false

Starts the Cosmed Omnia Main Program if custo diagnostic ist started. Otherwise the Cosmed Omnia Program ist started not until the customed has select CPET in custo diagnostic.

HostAddress

127.0.0.1

The TCP/IP Address to Cosmed Omnia (PC). Default Setting is the local Address of the PC. Often the two Programms are running on the same PC.

Port

5530

TPC Port (Cosmed Omnia) for the TCP/IP Connection

LogonPassword

<empty>

Password of the Cosmed Omnia User

LogonUserName

<empty>

Name of the Cosmed Omnia User

ProgramFullName

C:\Program Files (x86)\COSMED\Omnia\CosmedLab.exe

Path an Name of the Cosmed Omnia Programfile

PostTestCommandDelaySeconds

5

Ist die Wartezeit bei custo die nach der Ende der Messung abgewartet wird, bevor die Liste des Auswertungen (Tests) des aktuellen Patienten angefordert wird. Dies ist notwendig, denn Omni kann nicht unmittelbar nach Ende der Messung die Liste des Auswertungen (Tests) des aktuellen Patienten liefern, der befehl wird mit NACK beantwortet und steht dann auch als Fehlermeldung in der Error.log
omniacommunicator.cpp, 205   COmniaCommunicator NACK from Omnia for command 21 <SetRealTimeInfo>
Ist dies der Fall, dann muß evtl. die Wartezeit erhöht werden. Allerdings ist das nicht immer zielführend! Wenn bei Omnia nach Ende der Messung noch eine Benutzeraktion stattfindet, z.B. das Einholen der Bestätigung um Änderungen in den Einstellung zu speichern, dann wird so lange der Anwender nicht irgendeinen Taste drückt, der Befehl von uns immer mit NACK beantwortet. Dagegen ist leider noch kein Kraut gewachsen

StartTestCommandDelaySeconds

6

Ist die Wartezeit bei custo die mindestens vergeht bevor bei Omnia der Start-Dialog aufgerufen wird. Dies ist notwendig, da bei Omni der Start-Befehl erst dann verarbeitet wird, wenn die richtige Bildschirmmaske auf den Bildschirm ist und das braucht meisten 2-4- Sek. Zeit

TcpConnectionMaxRetryCount

6

gibt an wie oft maximal versucht werden soll die TCP/IP Verbindung aufzubauen.Erfahrungsgemäß gelingt nach einem Programmstart vom Omnia nicht immer auf Anhieb die Verbindung aufzubauen, daher können hier mehrer Versuche durchaus Hilfreich sein