Device Specific Integration Applications: Difference between revisions

← Older edit

VisualWikitext

Latest revision as of 11:01, 9 June 2025

This folder is used by two services, which operate in a clinic with multiple instances, e.g. one for each device:

Device Data Upload Agents - This service is retrieving information from devices and writes or copies them in a device specific format to the device integration folder. The filename has this format {GIDOfDevice}
KORDEUS Device Integration (KDI) Agent - This service will load the file and trigger the internally availbale data converter for the device identified by the GID of the device

File permissions

KORDEUS services are the owner
Owner has Read, Write permission, but not execute
Group has Read permission
Others have no permission

@@ Line 1: / Line 1: @@
 This folder is used by two services, which operate in a clinic with multiple instances, e.g. one for each device:
-* '''Device Data Upload Service''' - This service is retrieving information from devices and writes or copies them in a device specific format to the device integration folder. The filename has this format {GIDOfDevice}
+* '''Device Data Upload Agents''' - This service is retrieving information from devices and writes or copies them in a device specific format to the device integration folder. The filename has this format {GIDOfDevice}
-* '''KORDEUS Device Integration (KDI)''' '''Service''' - This service will load the file and trigger the internally availbale data converter for the device identified by the GID of the device
+* [[KORDEUS Device Integration (KDI) Agent]] - This service will load the file and trigger the internally availbale data converter for the device identified by the GID of the device
-=== ToDo ===
+==== File permissions ====
-* 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 services are the owner
+* Owner has Read, Write permission, but not execute
+* Group has Read permission
+* Others have no permission
 == See also ==
 * [[Software infrastructure requirements]]

Device Specific Integration Applications: Difference between revisions

Latest revision as of 11:01, 9 June 2025

File permissions

See also

Navigation menu

Search