...
With the satellite system an existing custo diagnostic environment is extended with a further server - the satellite server - which is installed e.g. on a mobile equipment cart. The client installed on the trolley can either connect to the master server (network mode) or to the locally installed satellite server (satellite mode). If In case evaluations are generated in satellite mode, they are transmitted to the master server. Since this is a pure server-to-server communication, neither user interaction nor direct database/file system access is required, as it was in previous versions. For synchronization it is sufficient that the satellite server can establish a network connection - operation of the custo diagnostic client is not required.
...
The following synchronization options are available - you will find a decision basis for their activation below:
- ClientsTenants: All clients Tenants of the master system are downloaded and the corresponding links (users, patients, etc.) are set. Should be used if the master system runs with clients.
- Doctors: The doctors of the master system are downloaded and the corresponding links are set (users, patients, evaluations). If this feature is used on the master system, it should be synchronized as well.
- Devices: The devices are downloaded and the corresponding links to the waiting room list entries are set. If this feature is used on the master system, it should be synchronized as well.
- Patients: The patients and their attributes are synchronized.
- Orders: The orders are synchronized, therefore it is mandatory to synchronize the patients as well, In this case, the related patients are synchronized automatically, even the general patient sync is not activated.
- Users: The users are also synchronized, including their passwords.
- Configuration: The client configuration is synchronized. Also the client configuration of the server.(see below)
- Job status: If the status of a job changes, the master system is informed.
- Upload evaluations: The evaluations are uploaded and created in the master system. If the patient does not exist in the master system, he will be created (including his doctor). Nothing else is created (orders, devices, etc.)!
- Delete evaluation after uploading: The delete flag is set at the evaluation after uploading. Deleted evaluations are no longer synchronized with the master system.
- Print jobs on server
- Log files of the client system
...
Basically, the question must be answered whether patient data should/must be available on the satellite system. In many cases it is sufficient to record ECGs in the satellite mode (as so-called "instant Quick ECG"), to annotate them and to assign them to the corresponding patient after synchronization in the master system. The disadvantage is the step of "assigning" in the master system. But the workflow is otherwise very simple, since this can be started directly, e.g. via appropriate command line parameters. Furthermore, in GDT-based systems the patient may not be available in the custo diagnostic system (house call) and the result cannot be transferred back via GDT. Even in large practice groups it is often desired not to keep all patient names on a system that leaves the practice.
...
As a rule, this information should always be synchronized - even if this information is apparently not affected. The reason is that evaluations always have a number of links references to this information. If this information is not available in the satellite system, or if it deviates due to manual configuration, it can lead to inconsistencies.
...
Szenario | Options to be set | Remarks |
|---|---|---|
"Immediate Quick ECG" as a backup system (network failure) and situations where patient data is not available. |
| Work flow:
The disadvantage is the step of "assigning" in the master system. However, the workflow is otherwise very simple, as this can be started directly, for example, via appropriate command line parameters. Furthermore, in GDT-based systems the patient may not be available in the custo diagnostic system (house call) and the result cannot be transferred back via GDT. Even in large practice groups it is often desired not to keep all patient names on a system that leaves the practice. As there is no patient data on the system, no registration is necessary. |
Workflow |
| Configures a very simple system that only pulls patients from the central system and synchronizes the evaluations again when a connection is established. Useful, for example, for so-called "home visit" laptops, where a family doctor typically visits patients at home, or drives to a home to measure blood pressure and perform lung function, or reads the LZ ECG directly. If "Delete after upload" is activated, the laptop is also "cleaned" and no longer contains any important data. |
Simple mobile workflow |
| Configures a system that "only" synchronizes the waiting room list entries with the patients. All evaluations and order statuses are highly synchronized. If you activate "Delete after upload" the satellite is always clean after synchronization In this configuration the satellite must / can be configured independently from the central system Dummy ECG evaluations can also be generated and highly synchronized |
Guided mobile workflow without clients |
| Extends the "ECG recorder replacement" to users and their configurations, so the satellites can be configured centrally and the settings are rolled out to the satellites when they synchronize |
Guided mobile workflow with clients |
| Extends the workflow to clients Important: If a client system is configured in the central system, it should be configured identically on the satellites, otherwise the assignments can no longer work |
Complete mobile system (with or without clients) |
| Extends the workflow to include synchronization of all patients. The satellite then has the complete patient database after synchronization. This means that work can be carried out with or without orders, and the assignment to the central system is retained. |
Branch practice / Second practice |
| In this mode, all evaluations are uploaded from the "store system" / "secondary practice" to the main system without the user having to worry about them. The branch systems are independent of the main system and are not interested in their patients, users or configuration. If findings are updated in the "Branch System", they are also synchronized and the main system has the latest status of all its branches Replaces then the dial-up crutch and other handicraft solutions |
...
Taste Key | Name | Function |
|---|---|---|
| 1 | Register / Re-register | Use this button to register the satellite server with the master server (see below) Important: Set before which things should be synchronizedConfigure the synchronization options before you Register your satellite. |
| 2 | Resynchronize | Performs a complete resynchronization (see also Zeitraum der Synchronisation) |
| 3 | Remove Registration | Deletes the existing connection to the central system |
| 4 | Configurations for satellite system | Sets which entities should be synchronized, see also Mögliche Einsatzszenarien |
| 5 | Refresh | Updates the list of statuses, here you can see if there are any errors and what is synchronized in the last synchronization step |
...
State | Meaning | Tooltip |
|---|---|---|
| There are still 7 evaluations not synchronized and the central server is not available |
|
| There are still 7 evaluations not highly synchronized, but the central server is accessible | |
| There are no evaluations for synchronization, the central server is accessible |
|
| There are no evaluations for synchronization, the central server is not available |
...
Configuration of the central print job
In order to print from the satellite to the server printer, printing on the server (Drucken am Server) must first be set up in the master system. These settings are then automatically transferred to the satellite system.
...