Converting an old database into the new structure can be separated into two phases:

1. Creation of the patient index
2. Conversion of the patient datasets

This happens nearly instantly. In most cases, the user can continue working after a few seconds.

Technically, the following happens:

1. When starting version 9.8 with a 9.7 database, the user is asked if he wants to convert the database or would rather create a new one.
2. If the database shoud be converted coDiagnostiX first moves the old database into a subdirectory of the database path. Example: If the database is at “C:\Database\”, it is moved to “C:\Database\Legacy\”
3. coDiagnostiX then creates a new empty database and reads the list of patient datasets from the old database. All datasets remain in the old database.

When the user opens a planning, all datasets of the patient are read from the old into the new database. Depending on the amount of datasets, plans and planning objects like model scans and drill guides, this can take from about ten seconds up to several minutes.

When the planning is displayed on the screen, the conversion is done. The patient is now completely stored in the new database AND the old database. Currently, the patient is never deleted from the old database. This will change in a future update of coDiagnostiX. It is planned to delete patient data which has completely been moved to the new database.

coDiagnostiX 9.8 is able to read databases created with coDiagnostiX down to version 9.0.2. Older databases must be opened first with a coDiagnostiX version between 9.0.2 and 9.7.6.

This concerns:

• Databases
• Cases on caseXchange
• Cases on the SQL network database
• Archive files
• Exported plans