Stefanseiler at 10:25, 9 June 2025

2025-06-09T10:25:34Z

← Older revision		Revision as of 10:25, 9 June 2025
Line 16:		Line 16:
	* Each Device Data Upload Service, has a setting file, which holds the device-type and deviceID, which was created earlier with KORDEUS admin tools		* Each Device Data Upload Service, has a setting file, which holds the device-type and deviceID, which was created earlier with KORDEUS admin tools
	* Once any of the device data is used, it can be tracked in the DMS-System (so if a device error happens, we can prove that later).		* Once any of the device data is used, it can be tracked in the DMS-System (so if a device error happens, we can prove that later).
			[[Category:Agents]]

Stefanseiler: Created page with " === ToDo === * Device Data Upload Server should take the information and write it to an envelope in a standard format defining from which device-instance the information it is coming from. This file is put into the `/input` folder * The KDI will read the envelope, will detect the device-type (e.g. IOL Master 700) of device-group-type (e.g. optical biometer). This information is managed with KORDEUS admin tools. * With this device type KDI will invoke the dev..."

2025-06-09T10:25:12Z

Created page with " === ToDo === * Device Data Upload Server should take the information and write it to an envelope in a standard format defining from which device-instance the information it is coming from. This file is put into the <code>/input</code> folder * The KDI will read the envelope, will detect the device-type (e.g. IOL Master 700) of device-group-type (e.g. optical biometer). This information is managed with KORDEUS admin tools. * With this device type KDI will invoke the dev..."

New page

=== ToDo ===

* Device Data Upload Server should take the information and write it to an envelope in a standard format defining from which device-instance the information it is coming from. This file is put into the <code>/input</code> folder
* The KDI will read the envelope, will detect the device-type (e.g. IOL Master 700) of device-group-type (e.g. optical biometer). This information is managed with KORDEUS admin tools.
* With this device type KDI will invoke the device-type specific data parser centrally and convert the information into a standard format. Once the conversion was successful:
** KDI writes the converted files to a <code>/convertedOK</code> folder, which holds all information in a standard import format, which still holds the original file information presented by the device in a binary format.
** If KDI does not succeed, it will move the failed conversion file to a <code>/conversionFailed</code> folder
* Upon request the data can be imported into the database. Before the data is used, the standard import format is saved to the DMS and receives a documentID there, which is kept with the dataset
* KDI will archive all files to the document-management system.
** from the <code>/input</code> folder before deleting them physically from the hdd
** from the <code>/convertedOK</code> folder, after it has been imported once

Goal

* Each Device Data Upload Service, has a setting file, which holds the device-type and deviceID, which was created earlier with KORDEUS admin tools
* Once any of the device data is used, it can be tracked in the DMS-System (so if a device error happens, we can prove that later).

KORDEUS Device Integration (KDI) Agent - Revision history

Stefanseiler at 10:25, 9 June 2025