Device Specific Integration Applications: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) No edit summary |
Stefanseiler (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
* [[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 | * [[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 | |||
== See also == | == See also == | ||
* [[Software infrastructure requirements]] | * [[Software infrastructure requirements]] | ||
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