Preparation

Please ensure before the conversion that

• The source data base (custo diagnostics 4) and the target data base (custo diagnostics 5) are reachable and writable.
  (During the conversion all GUIDS of the corresponding newly created elements in the version 5 DB are recorded in the old version 4 DB)
• The source CST  directory is reachable and readable. 
• The tenant functionality is disabled in target system
• The destination DB (custo diagnostics 5) is empty
• All unassigned evaluations are assigned
• All tasks in the task manager are processed (no conversion of tasks takes place)

Optional checks before the conversion

Please check the following points before the conversion which however do not prevent the conversion:

• All user passwords match the password policy rules of the version 5 traget system, as the relevant users otherwise will be deactivated.

Automated checks of the tool

The following checks are done automatically by the conversion tool. In case of an error, the following repair steps are displayed:

Check	Stops the conversion process:	Description
Are the source and destination DBs reachable and writable?		If either the source or the destination DB are unreachable the conversion process is aborted,
Is the table scheme of the source DB correct?		In case of a lack of integrity in source DB (missing columns) the conversion is aborted. Please note that the source DB must be in the starte for version 4.5.x to have all tables correct.
Is the target system configured as tenant system?		In case a tenant configuration exists in the target system
Is the custocfg.ini in an integer state?		In case of integrity issues of the custocfg.ini, the conversion is aborted because it cannot be read automatically which system should be converted.
Are the at least 100 GB of free space on the CST target path?		In case of less than 100 GB of free disk space a warning message appears, however the conversion is still possible.
Is the target data base a H2 data base?		If  the target is a H2 DB a warning appears as the warning , as the conversion for H2 DBs may easily cause errors and as there is no possibility to work with multiple threads.
Is the target system old than 90 days?		In case the target system is older than 90 days there is a risk that the conversion may cause the loss of already existing configurations. A warning message appears, but the conversion is still possible.
Are there any evaluations in the target system?		In case there are evaluations in the target system, there is the risk that the conversion may overwrite already existing evaluations. A warning message is displayed, but the conversion can be continued.

Which content will not be converted?

In general everything is converted as well as possible. The folllowing features are however not (yet) processed by the conversion:

• The user "Supervisor"
• All data of the custo Kybe
• Open tasks in the task manager
• The table "events" (a log table), respectively also all other log tables
• The table "Cfg_Update" (as well as all data base updates)
• Die table "system data" (is not applicable)
• Die table "Practice data" (now handled via "Doctor")
• Satellite sync data (there is no more satellite system)
• The import list
• Recorder patient statistics
• Evaluation groups
• The EvalOrderInfo table

Conversion of archived and moved evaluations

All archived evaluations are converted 1:1 and can be opened in custo diagnostics 5 System afterwards still as archived evaluations.

All moved evaluations from the version 4 will become also archived evaluations. In version 5 the flag "moved" does not exist any more. Moved and archived evaluations are hence treated equally in version 5. 

Trend files

For archived and moved evaluations trend files cannot be created, because in most cases it is not possible physically access those files. In CSC it is possible, that you get that error message recreation the trend files:

Options for the conversion

Configuration of the conversion

Option Beschreibung (1) Select here the custoCfg.ini of the source system from which it should be converted to custo diagnostics 5. (2) Select here to extend of the conversion (Full oder Smart-conversion), see Options for the conversion On top in can be configured whether evaluations should be deleted in source system after the successful conversion of every single CST file. Please be careful with that option: You may have only one try! (3) Select here the time range of the conversion. (4) You may select here the conversion of the trends  ( is time consuming and can be rather performed afterwards) (5) Starts the whole conversion including the settings data base. (6) Starts the conversion of the patient master data and of the evaluations - without the settings.

Full conversion

In case of the full conversion everything configured in the time range (3) gets converted.

If you configure the last 2 years, only patients and evaluations of the last 2 years will be converted. Data beyond that will not be available in target system after the conversion.

Advantage:

 After completion of the full conversion with the time range "All" the custo diagnostics 4 system can be turned off.

Disadvanatages:

 The conversion takes very long, as all CST files must be copied.
 After a full conversion with the time range limit not all patients and evaluations are in the target system (may even be desired)

Smart conversion

The smart conversion always converts always the whole DB, but copies only CST-files, which are in the scope configured in (3). All other evaluations are marked internally as "smartConverted" and are only copied, if the relevant evaluation is opened up.

In case the user tries to open a smartConverted" evaluation where the relevant files cannot be found, a message dialog appears in which the user should select the directory of the relevant CST file. On top the option "Delete version 4 CST-File after smart converted..." can be activated, which will get the original evaluation removed from the version 4 data directory, after the evaluation has been stored in the version 5 system.

Advantages:

 The conversion can be performed very quickly
Most probably disk space can be saved in the target system
 It is possible to complete the smart conversion after the conversion to a full conversion (see Finish the Smart conversion)

Disadvantages:

 The version 4 share must not be turned off as there is otherwise no more access ability given to the old evaluations
Trends trends may not be rebuilt completely
All version 5 clients require acceess to the share of the version 4 system

Conversion of trends

With (4) the conversion of trends can be activated.

Workflow

Conversion to a system without tenants

In case of conversion from versions lower than 4.5.x

1. Upgrade the custo diagnostic to the most current version of 4.5.x or higher
2. Start custo manager.exe (version 4.5..x) once to ensure that the DB scheme is the current one.

Before the conversion

1. Install and configure custo diagnostic 5.x (Licence, default doctor)
2. Open custo service center (5.x) and open the conversion page
3. On the conversion page click on (2) drücken and select there the CustoCfg.ini of the 4.x-version.
4. Select the options of the conversion.
5. Click on Start Database Conversion. Afterwards the page for the conversion of the configuration DB will open.

Conversion of the configuration DB

1. In (1) it is displayed again that the supervisor user does not get converted and that users which have no password according the password policy will be deactivated.
2. After clicking on (2) the whole configuration DB will be converted. This may take some minutes time.

Errors during the conversion of the settings

In case of errors during the conversion of the settings, a dialog displaying the the problems appears. Those can be save later as well as Excel file and are stored in the Service Center logs in the path %PUBLIC%/Roaming/customed/...servicecenter.log

Conversion of the patient DB and the evaluations

1. Here it is possible to select the settings for every found patient master DB to be converted. To do so select the DB in (1) and click on "Edit Conversion Settings" (2). There are the following options:
   1. To not convert the DB (e.g. because the same one has been found several times)
   2. To convert the DB as it is.
   3. To convert the DB without tenant assignment.
   4. To convert the DB assigning the all patients to a particular tenant (see Conversion with tenant system)
2. Once everything is configured click on Next.
3. Now the conversion starts and you can see the progress and the speed.

1. Here you can see the number of the already converted DB records
2. Hier you can see the errors, which have occurred in the relevant DB records
3. Shows the current state (converted / total + speed by records per second)

Completion of the conversion

Finally, in case there are no gross errors, an error summary is displayed:

With (1) it is possible to save the error report as Excel file, so that you can process the errors afterwards.

Afterwards the conversion is ready and the following checks should be done:

1. Settings (those may have changed from version to version)
2. Doctors
3. Tenants

Conversion with tenant system

Preparation

• In case several patient master DBs should be distributed to several tenants the tenants must be created beforehand.
  With that it is possible to simulate the feature that users have there own patient master data (meaning one config DB, several patient DBs)

Conversion to tenants

• Configure the settings the same way as in the conversion process without tenants and start it
• In the conversion settings for each DB in each case a previously created tenant can be selected:
  
• in case "Convert and keep tenant settings" is selected, the tenant of the master DB are simply converted as well and everything is as in the former system
• Turn on "Patients / Patient visits tenant based" after the conversion: This way the tenant system works like in version 4.x.
  
   
• Now assign as well the users to the right tenant.

Finish the Smart conversion 

In case a DB has been smart converted, but you want to switch off the version 4 installation step by step the following steps need to be taken.

Searching of smart converted evaluations

Via the evaluation search in the custo diagnostics Service Center in is possible to easily search for smart converted evaluations (1). In case the migration should be done e.g. in small steps, becasue there always only a small time frame it makes sense to filter by time period or as well by project. In the following example screen shot only the the (3) long term EKGs of the (2) last 5 years were searched.

In this list it is possible to select with STRG+click, or SHIFT+click single evaluations or a scope of evaluations, or with STRG+A the whole list and by (4) change → Import smart converted evaluations to change to the import dialog:

Configuration of the import

ID Description 1 Configures with how many threads in parallel the import should be performed  This value should be selected with care: Per core not more than 5 threads should be used, as the system otherwise will be extremely slow  2 Here it is possible to define an additional data directory, in which it should be searched for CST files. This is helpful in case evaluations wee moved or manually archived. 3 If this option is active, evaluations are deleted from the version 4 data directory after the transfer to the version 5 system. 4 Starts the import of the evaluations.

Clean-up of custo diagnostic 4

After the transfer of all evaluations or if you consider the transfers made to be sufficient, the version 4 share can be moved to an archive media or deleted.

Trouble shooting

During the conversion it is possible to display the logs from the Service center beneath: %PUBLIC%/Roaming/customed/...servicecenter.log in an appropriate viewer. This way it is possible to quickly discover as soon as possible during the conversion.. At the end of the conversion the whole error report cam always be saved as Excel file on top.

Classical error records

FAQ