Therapist, Assessment, Psychological Software Applications
Update: 8-10-2012 This article is only a technical summary of the process of setting up CPT II. This application will run in any Virtual Machine if properly configured. If you need assistance click the Live Technical Support Icon and ask.
TECH NOTE: For those that attempt to backup the data using the built in features you'll need to read the internal "Help Section" for backups. What appears to be Excel is not Microsoft Excel and it's clearly stated in the help files. It is a proprietary application that appears to be Excel but is NOT. The built in backups are only designed to backup and import into CPT not any other application. The best method I have found is to backup the data container and data log container. This allows you at least to recover to the same machine if a virus attacks the DB.
Custom applications developed for the 21st Century Therapist number in the hundreds.
Some of these applications are based on DOS while others use the newest technology running as multi-user applications on servers. But when you run into software designed for a system 10 years old what are the steps you need to take to make sure you preserve the integrity of your system.
Top Questions from CPT II users:
- I'm having problems installing CPT II (2) on Windows 7.
- CPT II was designed years ago and has only been modified in the way you install the application.
- CPT II requires full administrative rights to run and can be a problem if you are using your computer with PHI and using it as a testing station. If that's the case I advise that you install your CPT II in the Windows XP Virtual PC and set that system under a standard user account for testing. You'll be able to access the same Virtual PC from your login but to keep the person out of your admin folders it's what I would recommend.
- CPT II has Microsoft SQL 2005 by default set. This will not work well and the newer versions of SQL 2008 Express do not work either. You must download the SQL 2008 Express that was released prior to the SQL 2008 R2 Express (I think that's it I'll double check when you email.)
- You can also disable the UAC (User Account Controls) if they become an issue for you.
- Does CPT Run on Windows Virtual Machines?
- Yes Windows XP, 7, 8 2008, 2012
Just remember that the information you store with CPT is PHI and you need to follow the guidelines for PHI. If you have questions about how to handle PHI skip talking to your lawyer that doesn't know what NIST is and ask either your local auditor, someone that's been audited, HSA or an IT admin that has knowledge of working with sensitive compartmental data.
- Your system will need drive encryption to secure the PHI that is stored in the SQL database.
- The SQL database uses a fixed username and password that does not follow best practices for database security. You will need to adjust other settings to make it difficult to copy the data files.
- CPT requires full administrator rights to launch. (I have not found a work-around for this other than in a virtual system.
This section will cover the following manufacturers and applications.
Because you are going to need resource links for just about every software application you are about to install or adjust I'll start out with the Microsoft Links and give you a tip or two about MHS SQL issues.
NOTE: If you are setting up from the CD do not auto run the setup. Search the Knowledge base article of 901 (I'll give you one guess where) and you should be able to get things up and running. P00_ is your hint. If you have questions feel free to write or call if you need help remotely after you are exhausted by the CPT support people. (Which will say, ready 901)
One last note, if you feel that +mHs123+ is a good password for your sa account. I would guess you have never read SQL articles before. There are hundreds do your search.
References: (Old and Obsolete resources use at your own risk.)
Microsoft SQL 2005 Express Edition (Main installation package)
Microsoft SQL 2005 Express Edition SP3 Service Pack 3 (The main package seems to have this Service Pack but in case you need to run it as a stand-alone update)
Microsoft SQL Server Management Studio Express (This will help later when we tackle the MHS SA account login issue.)
Microsoft SQL Server 2005 Service Pack 4 RTM (Not tested with MHS and Q-Local but will setup to run a few tests later on a non production machine.)
Configuring and Managing SQL Server Express
MHS notes: Setup your SA account while you are installing your SQL 2005 Express Edition application. Because MHS will over write data folders and reinstall it's own version with a SA account username and password we can force feed the application to use what we have setup for the workstation. This way we can after more applications running with the same account setup. One less thing to troubleshoot if something goes wrong.
For improved manageability and security, SQL Server 2005 provides more control over the SQL Server surface area on your system. To minimize the surface area, the following default configurations have been applied to your instance of SQL server:
o TCP/IP connections are disabled
o Named Pipes is disabled
o SQL Browser must be started manually
o OPENROWSET and OPENDATASOURCE have been disabled
o CLR integration is disabled
o OLE automation is disabled
o xp_cmdshell is disabled
To enable or disable features and services, run the SQL Server Surface Area Configuration tool from the Start menu.
· To install SQL Server Management Studio Express Edition, download it from the SQL Server Developer Center on MSDN (http://go.microsoft.com/fwlink/?linkid=51793).
Documentation and Samples
To install SQL Server 2005 Books Online, download them from the SQL Server Developer Center on MSDN (http://go.microsoft.com/fwlink/?linkid=51793).
To install the .NET Framework SDK, see "Installing the .NET Framework SDK" in SQL Server Books Online.
To install sample databases and code samples, download the SQL Server Samples from the SQL Server Developer Center on MSDN (http://go.microsoft.com/fwlink/?linkid=51793).
SQL Blog: Interesting and easy to read.
And when I find the how to hack the sa to your server path article published at microsoft.com someplace I'll post that link. After all, it's your HIPAA rules at risk here and now that you know allowing a program to set the SA password to a very common password in the industry is a big no in my book. Learn how to change the application and SQL sa password and you're back in business. If not, any jr. can access your data.
Tech Note during page setup:
Microsoft SQL Server 2005 Express Edition seems to be the main SQL server these applications require. It is very important to assign a username that is specific to the SQL server. MHS uses sa accounts with their special password. Keep usernames and passwords for access to the SQL server to a minimum.