Hi, we have just upgraded one of our AlignRT systems to v7.4. Because the database is not compatible with v6.3 we have rolled it out using a local server for now while we decide what to do with our current patients on our other 7 alignRT systems. We are looking to upgrade dept-wide in January.
How have others dealt with the change from v6.3 to 7.4? Have you just deleted all the data in the 6.3 database or ensured the data has been sent to a pdf report and then stored?
Hi Colin, This is not great news. I have never had a software upgrade that could not port the previous data into it. You could keep two data bases but eventually you would have to give up version 6.3. I am interested in how others are handling this and what vision RT advice is on this is.
Hi Colin,
We’ve found the current upgrade process quite challenging due to compatibility issues. For example, when attempting to upgrade from V6.3 MR1 → V6.3 MR2, we learned that archived patient data would be lost unless restored beforehand. To avoid this, we decided not to proceed with that upgrade.
We’re now waiting for the V8 release, as we’ve been advised that backward compatibility will be addressed moving forward. However, we’re unsure if the same issue exists when upgrading from V6.3 → V7.4, as we don’t have V7.4 installed.
If your standard practice is not to archive patients, meaning all data remains in the active database, it’s possible those records would carry over to V7.4. It might be worth clarifying whether the upgrade affects only archived patient databases or all patient data.
I realize this may not be very helpful, but I wanted to share our approach: we prefer to take the burden only once, even if it means losing some existing data.
Best regards,
Deepak