Notifications
Clear all
Topic starter
We use a 3rd party CCC type of template strategy and must upgrade quarterly. As long as I have been doing this stuff I have not ran into a problem and haven't backed up the part of the db via export of clinical kits before importing new ones which will change things.
The issue I had was not due to the content but due to a problem which we have attempted to solve with Athena Support. What happens is we log in and immediately get an error which says "failed to create Scheduling control. Can not display schedule". It is also impossible to open scheduling after logging in and receiving that error message. Athena support would only say that we had to reinstall the CPS client on affected workstations, and to use the cab file instead of the html page.. At the time, I wasn't real happy with that answer because I thought maybe someday that I would walk in to the office with everyone down and not being able to view their schedule. Well, that worst fear almost came true late last night. Fortunately I was able to get assistance from the template provider and reinstall some older content instead of touching many workstations. Again, I do not believe the problem lies with the templates because the scheduling component is not part of the EHR portion of CPS but it did seem to trigger the underlying issue.
So, my question is, is there a way to "dump" all of the clinical kits right before I do such an upgrade? I would just keep a copy so that I could make a quick recovery. I only see a way to manually dump each ckt, which I suppose I could do but it would be very tedious and I am thinking there should be a better way.
I could have relied on a VMWare snapshot and will do that if there is not an easy way to backup the existing ckt files. A VMWare snapshot comes with it's own challenges because I don't generally set up a maintenance window which would discourage anyone from adding new DB content during the time I do these updates. I will from now on, unless I can do a backup of all existing ckt files.
Thanks
Mike Zavolas
Tallahassee Neurological Clinic
Posted : March 5, 2021 3:09 am
I don't have an answer for a better way to export clinical kits. The problem is very interesting to me though. I don't see how clinical forms interact with the schedule module.
Have you run a trace on startup? This from my documentation. It doesn't look like my composition style though, so I probably copied it from somewhere years ago.
- If the application will not start, or hangs as it starts, use this alternate method to start the trace.
- Locate and open the file C:\Program Files\Centricity Practice Solution\mlsetupo.txt with a text editor such as Notepad.
- Find the line: // Trace: "C:\\TRACE.TXT"
- Enable the trace. Remove the double forward slashes (//) at the front of the line: Trace: "C:\\TRACE.TXT"
- Save the file and restart the application. The program will start with the trace running.
- Reproduce your problem.
- When you have reproduced your problem, close the application. The file, trace.log will record what happened with the program.
There is also a "tracemel" flag as well. Perhaps that might provide some insight.
-dp
Posted : March 5, 2021 4:38 am
Mike, I know there isn't a way to export ALL the clinical content with a couple of clicks, but you can export ALL the Forms, ALL the Templates, etc., each with just a couple of clicks. I guess you could queue them all into one giant export but I wouldn't recommend it. Particularly since order matters. For example, you have to import Forms, then Document Templates, them Encounter Types for your Encounters to be correct.
Posted : March 5, 2021 12:24 pm
Topic starter
I will likely leverage the VMWare snapshot process from now on. It will require a more structured mini upgrade process but is safer and easily recoverable.
Posted : March 8, 2021 5:54 am
Topic starter
I think we did all of that with support when it happened initially. The last time it happened, it didn't seem to have anything to do with template updates. Support's recommendation of just reinstalling the client means that they had no idea either.
We are doing a V20 upgrade on Friday which is why I was concerned about this. I don't like not having answers about things...
Posted : March 8, 2021 5:58 am
