Medisoft Clinical Installation Upgrade Guide

Transcription

Title page
Medisoft Clinical
Upgrading to Version 18
September 2012
Produced in Cork, Ireland
Copyright notice
Copyright notice
Copyright © 2012 McKesson Corporation and/or one of its subsidiaries. All Rights
Reserved.
Use of this documentation and related software is governed by a license agreement. This
documentation and related software contain confidential, proprietary, and trade secret
information of McKesson Corporation and/or one of its subsidiaries, and is protected under
United States and international copyright and other intellectual property laws. Use,
disclosure, reproduction, modification, distribution, or storage in a retrieval system in any
form or by any means is prohibited without the prior express written permission of
McKesson Corporation and/or one of its subsidiaries. This documentation and related
software is subject to change without notice.
Publication date
September 2012
Produced in Cork, Ireland
Product
Medisoft, Release 18
Corporate address
McKesson Corporation
5995 Windward Parkway
Alpharetta, GA 30005
404-338-6000
ii
Release 18
September 2012
Table of contents
Table of contents
Chapter 1 - Medisoft Clinical Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Quick View: Medisoft 18 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . .
Medisoft Clinical Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Medisoft Clinical Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . .
Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrade Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sites Using Custom Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Clinical Quality Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
3
5
5
5
6
6
7
7
Chapter 2 - Upgrading Existing Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation Overview: Sites Upgrading from 9.4.x or 9.5.x . . . . . . . . . . . . . . . . . . . 9
System Preparation--Run Processes and Shut Down Services . . . . . . . . . . . . . . . . . 10
Make a Complete Backup of the Ppart folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Rename or Delete Certain List Container Names. . . . . . . . . . . . . . . . . . . . . . . . . 10
Complete Processes in Medisoft Clinical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Run the CheckAll.bat Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Download your License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Install your License file for Medisoft Clinical/Practice Partner. . . . . . . . . . . . . . . . 13
Shut down CTree Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Stop Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Install Medisoft Clinical Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Restarting the PMSI Data Server and PMSI Application Server. . . . . . . . . . . . . . 20
Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing Medisoft On the Client Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Installing Medisoft and Practice Partner Client on Each Workstation . . . . . . . . . . 21
Accessing and Registering Medisoft from the Workstation . . . . . . . . . . . . . . . . . . . . . 25
Configuring Communications Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
If you decide not to use the Automatic Provider Update Feature . . . . . . . . . . . . . 26
Automatic Provider Update Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
After Installing the Medisoft Clinical Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Appendix A - Automatic Provider Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Types of Provider Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Provider Mapping Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Using the Automatic Provider Update Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Appendix B - Upgrading PPConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Checking your Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Appendix C - Configuration of Firewalls and Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Inbound Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Outbound Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
September 2012
Release 18
iii
Table of contents
Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Appendix D - Add-Ons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Installing/Upgrading Add-Ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
iv
Release 18
September 2012
List of Figures
Figure 1 Checkall.bat utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 2 Checkall.bat utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 3 Unsupported Application warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 4 Connect DemSch In screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 5 Connect BillCode and Sch Out screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 6 End User License Agreement screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 7 Select Components to Install screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 8 Select Options Installation screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 9 FairCom Server Activation Utility screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 10 Installation Completed screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 11 Select Components to Install screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 12 Select Client Components screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 13 Select Options Installation: Server Directory screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 14 Installation Completed screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 15 PP Connect DemSch In screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 16 PP Connect BillCode and Sch Out screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 17 Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 18 Communications Manager screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 21 Connect DemSch In icon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 22 Connect Outbound BillCode icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
September 2012
Release 18
v
List of Figures
vi
Release 18
September 2012
Chapter 1 - Medisoft Clinical Upgrade Overview
In this chapter you will learn about the operating systems that Medisoft Clinical is supported on, as
well as the minimum system requirements for your server and workstations.
NOTE: You can find a brief overview of Medisoft Clinical Add-Ons (listed in the installer) at “AddOns” on page 45. Instructions for installing Medisoft Clinical Add-Ons can be found at
https://support.practicepartner.com/customer/products/proddocs.aspx.
However, you will need a login.
If you receive an error trying to open a PDF file or to install Adobe Reader, go to the Adobe web
site and download the latest version of Adobe Reader.
September 2012
Release 18
1
Quick View: Medisoft 18 Supported Operating Systems
Quick View: Medisoft 18 Supported Operating
Systems
NOTE: Medisoft 18 is a 32-Bit application, and on a supported 64-Bit platform, the
application will run in a 32-Bit mode.
SERVER
WORKSTATION
DATABASE
Version of Medisoft 18
Version of
Advantage
OPERATING SYSTEM
Network
Professiona
l
Single-User or
Advanced
Network
Professiona
l
Single-User or
Advanced
Local or
Remote
Windows Server 2003 SP2 32-Bit or
Windows Server 2003 R2 SP2 32-Bit
Y
N/A
Y
N/A
Remote
Windows Server 2008 32-Bit or
Windows Server 2012 32-Bit
Y
N/A
Y
N/A
Remote
Windows Server 2008 R2 64-Bit or
Y
N/A
Y
N/A
Remote
Windows Vista Business SP1 32-Bit
N/A
Y
Y
Y
Local
Windows Vista Business SP1 64-Bit
N/A
Y
Y
Y
Local
Windows XP Professional SP3 32-Bit
N/A
Y
Y
Y
Local
N/A
Y
Y
Y
Local
N/A
Y
Y
Y
Local
Windows 7 Ultimate 32-Bit
N/A
Y
Y
Y
Local
N/A
Y
Y
Y
Local
Windows 7 Professional 32-Bit
2
Release 18
September 2012
Medisoft Clinical Supported Operating Systems
SERVER
WORKSTATION
DATABASE
Version of ctree Server
OPERATING SYSTEM
Medisoft Clinical with Medisoft
Network Professional
Medisoft Clinical with
Medisoft Network
Professional
c-tree Server
7.12 Standard
Windows Server 2003 SP2 32-Bit or
Windows Server 2003 R2 SP2 32-Bit
Y
N/A
Y
Windows Server 2012 or 2008 32-Bit
or 64-Bit
Y*
N/A
Windows Server 2008 R2 64-Bit or
Y
N/A
(See note above)
Y
Y**
Windows Vista Business 32-Bit
N/A
Y
Y
Windows XP Professional SP3 32-Bit
N/A
Y
Y
Windows or 8 or 7 Professional 32Bit
N/A
Windows 8 or 7 Professional 64-Bit
N/A
Y***
NA
N/A
Y
NA
N/A
Y***
NA
Y
NA
* Medisoft Clinical does not support the Remote Application feature in Windows Server 2008 64Bit.
September 2012
Release 18
3
** When running Medisoft Clinical with Windows Server 2008, you must turn off the Windows UAC
feature (requirement of c-tree Server).
***EKG and Spirometry, as well as all Midmark, devices are not supported on 64-Bit computers.
Currently, only Welch Allyn EKG is supported.
Medisoft Clinical requires a domain/Active Directory infrastructure.
Each Medisoft Clinical user must have a unique Windows/domain username for security reasons.
Medisoft and Lytec will not support Windows RT on the ARM processor.
4
Release 18
September 2012
Medisoft Clinical Hardware and Software Requirements
Medisoft Clinical Hardware and Software
Requirements
Workstation
CPU (Processor)
Intel Core 2 Duo 1.6GHz
RAM (Memory)
2GB for Windows XP, 4GB for Windows Vista and Windows 7
Network Card (NIC)
100 Mbps
Video Resolution
1024x768 (1200x800 for widescreen displays)
Note: You must have an internet connection to use Medisoft Network Professional.
Application Server
CPU (Processor)
Intel Dual Core Xeon 1.6GHz
RAM (Memory)
4GB
Storage Array Type
RAID-1
Optical Drive
DVD-ROM
Network Card (NIC)
1Gbps
Now available is a tool that will determine if you have enough free space on your application
server. It is available on the Internet at http://www.medisoft.com/download/training/04TechInstall/
PracticePartner95PreUpgradeValidationUtility.pdf.
Additional documentation for Practice Partner can be found at
However, a login is required. McKesson recommends that you save these files on your workstation
and create a desktop icon for them for easy access.
In addition, several guides for using Practice Partner are available on your Medisoft Clinical
installation DVD. You can access them from the DVD or insert the DVD and start Autorun. These
guides can be viewed from Autorun.
September 2012
Release 18
5
Prerequisites
Prerequisites
This section lists general pre-installation requirements.
• You will need your Advantage Server License Number and your Medisoft Network Professional
License Number that shipped with Medisoft 18.
• Date and time synchronization between the server and client PCs.
• The Windows Time Service is a feature of Windows operating systems that maintains date
and time synchronization on all clients and servers in a network, using the Simple Network
Time Protocol (SNTP). It is standard practice for all Medisoft Clinical customers to use this
feature to maintain time and date synchronization of all the computers in your network.
Medisoft Clinical will use this synchronized date and time to the date/time of events, including
audit trail entries. To synchronize your client workstations to your server, run the following
command line prompt on your client workstations: Net Time \\servername/set/y where
[servername] is the name of your server.
• If your site is using Microsoft Windows Server 2003, you must have Microsoft Windows Server
2003 Service Pack 2 installed on your server before installing Medisoft Clinical 18.
• WTS and Citrix only: If you are using Windows Terminal Services (WTS) or Citrix, run the
installation through the WTS or Citrix server Control Panel’s Add/Remove Programs wizard.
This will allow you to select which Medisoft Clinical program files are allowed to be accessed
by multiple sessions.
Upgrade Path
Below is a table listing the upgrade path for Practice Partner 9.3, 9.4, and 9.5. Note that if you are
using Practice Partner 9.3.x, you must upgrade to Medisoft 16 before you can upgrade to Medisoft
18, which has Practice Partner 9.5.2 SP2.
Starting Version
Maximum Upgrade Version
Medisoft 15 (PP 9.3.x)
Medisoft 16 (PP 9.4.1)
Medisoft 16 (PP 9.4.x)
Medisoft 18 (PP 9.5.2 SP2)
Medisoft 17 (PP 9.4.1)
Medisoft 17 SP1 (PP 9.5)
Medisoft 17 SP2 (PP 9.5.1)
Medisoft 17 SP2 (PP 9.5.2)
Medisoft 17 SP3 (PP 9.5.2.1)
Medisoft 18 PP 9.5.2 SP2)
If you are upgrading from Practice Partner 9.5.2 or 9.5.2.1, you will NOT need a new license file.
Your existing license file will work. During installation, you will see the License file screen. On this
screen, you can select a different folder or computer on which to store the license file.
6
Release 18
September 2012
Sites Using Custom Interfaces
Sites Using Custom Interfaces
If your organization uses a custom interface(s) and you are upgrading to Medisoft Clinical/Practice
Partner 9.5.2 SP2, please contact Practice Partner Customer Support to schedule a time to
upgrade your custom interface(s).
Please allow at least 30 days advance lead time when scheduling this upgrade.
Installing Clinical Quality Measures
If you have the 64-bit version of Microsoft Office installed on your computer, you will receive a
message during installation asking you if you would like to uninstall this version to install Clinical
Quality Measures. Clinical Quality Measures is made to work with the 32-bit version of Microsoft
Office. McKesson recommends that you do not uninstall your current version of Microsoft Office
and that instead you install Practice Partner Client and Clinical Quality Measures on a different
computer.
September 2012
Release 18
7
Installing Clinical Quality Measures
8
Release 18
September 2012
Chapter 2 - Upgrading Existing Sites
In this chapter, you will learn how to install Medisoft Clinical on your server computer, as well as
your workstations. In addition, you will learn how to prepare your system for your upgrade.
WARNING: Back up your data in Medisoft and Practice Partner.
NOTE: You must have administrative privileges to complete the installation.
Installation Overview: Sites Upgrading from 9.4.x or 9.5.x
The following steps overview the process for installing Medisoft 18 and Medisoft Clinical.
Step
Process
1
Prepare your server by running certain processes and shutting down various services.
2
Install the Medisoft Clinical Server upgrade. The instructions for this step are detailed in
“Install Medisoft Clinical Server Upgrade ” on page 16.
3
Install the Medisoft on the client workstations. The instructions for these tasks are
detailed in “Installing Medisoft On the Client Workstations” on page 21.
4
Launch Medisoft Network Professional, convert your data, and register your software.
5
Edit (if necessary) your connection Between Medisoft and Medisoft Clinical in
Communications Manager if you plan on using the Automatic Provider Mapping feature.
The instructions for this task are detailed in “Configuring Communications Manager ” on
page 26.
6
Review your after-installation options, detailed in “After Installing the Medisoft Clinical
Update” on page 33.
.
September 2012
Release 18
9
System Preparation--Run Processes and Shut Down Services
System Preparation--Run Processes and Shut
Down Services
A. Make a Complete Backup of the Ppart folder
This will ensure that you have a complete copy of the folder prior to starting the upgrade.
NOTE: This may take several hours depending on the size of this folder. McKesson recommends
that you perform this step at the end of the day.
B. Rename or Delete Certain List Container Names
If certain List names in Practice Partner exist prior to installing Release 9.5 or higher, the
installation will fail and Practice Partner will become unusable. These list names are as follows:
• ENCOUNTER LIST
• REGISTRY TYPE
• ADMINISTRATION ROUTE
• ADMINISTRATION SITE
• VACCINE MANUFACTURER
• ADMINISTRATION DEVICE
• IMMUNIZATION SERVICE FUNDING ELIGIBILITY
• VACCINE DOSE UNITS
If your database uses these list names, you must rename the list or delete it prior to installing.
Modifying List Names
To access the List names and modify them:
1. In Practice Partner Client (Medisoft Clinical Client), select Maintenance.
2. Click Templates.
3. Click List Maintenance.
4. Check for the above names. If you find a list with any of these names, either use the Edit
button to change the name of the List or use the Delete button to delete the list.
C. Complete Processes in Medisoft Clinical
This section lists processes within Medisoft Clinical that you must complete before installing.
• Bill Electronic Claims: Create and send transmission files for all claims in the intermediate
claim file. Mark all claims billed.
• Make sure all users are logged out of Medisoft Clinical. Likewise, if you are running Dragon
software for speech recognition, have all users exit Dragon.
10
Release 18
September 2012
Run the CheckAll.bat Utility
• Make a full cold backup of your Medisoft Clinical database server. This backup must include
everything you need to recreate your production environment. Do not continue the
conversion until the backup is complete and verified!
• Uninstall ALL patch installers that are used specifically to install patches for Practice Partner.
These patches are called McKesson Practice Partner Client Patch Installer and McKesson
Practice Partner Server Patch Installer. It is possible that these patches exist multiple times on
a single machine. All instances will need to be removed for the Practice Partner 9.5.x installer
to work properly. They can be removed by using the Add/Remove Programs feature in Control
Panel.
• Turn off anti-virus programs. If your computer is running any antivirus software, turn it off
before installing. If it is scanning files that the installer needs to update, the installation might
fail.
• Turn off any automatic backup services. If your organization is using any automatic back up
services, turn them off. The installer needs exclusive access to files on the Ppart folder.
Note: During the upgrade installation, the sample Appointment Scheduler encounter forms (for
instance, AS_Encounter, AS_Label, OE_Custom, OE_Label, and Cancelled_Orders) will be
overwritten. If you are using these forms, you must copy your encounter forms before the
installation to ensure that the forms are saved for future use. For more information, see the
Encounter Forms section in the Patient Records User’s and Technical Guide.
D.Run the CheckAll.bat Utility
Before installing the upgrade, if you have not recently run the checkall.bat, you will need to run this
utility. You can do this up to 72 hours prior to upgrading. It will check your database for errors and
you will need to rebuild the errors so that you will not run into problems when you convert your
data.
1. Run checkall.bat from the Practice Partner directory folder on the server drive. Go to step 5.
or
Run the utility from the command prompt by clicking Run on the Start menu.
2. In the Run box, type cmd.
3. Click OK. The command prompt screen opens.
4. Type P: (or whatever letter the server drive is named) and press Enter to change the drive to
that drive. From the drive prompt, type cd\[Practice Partner directory name] and press
September 2012
Release 18
11
Run the CheckAll.bat Utility
Enter to browse to the directory (for instance, cd\ppart). Type in checkall.bat and press Enter
to start the utility.
Figure 1. Checkall.bat utility
5. The utility runs. Allow the utility to complete.
Figure 2. Checkall.bat utility
6. The command prompt will return to the directory when completed. Close the screen. Check
the checkall.log file for errors. Open this file in your database directory (typically p:\ppart) and,
with a text editor such as Notepad, perform three searches (1-Problem, 2- error, 3- missing). If
errors are detected, you need to repair the files before upgrading.
12
Release 18
September 2012
Download your License File
If you receive the following error message, click OK and continue.
Figure 3. Unsupported Application warning
E. Download your License File
If you are upgrading from Practice Partner 9.4 and above, you will need to download only one
license file, the latest one for Practice Partner 9.5.2 SP2. You will NOT need multiple license files to
upgrade.
In addition, if you are upgrading from Practice Partner 9.5.2 or 9.5.2.1 (Medisoft Clinical 17 SP2 or
SP3), you will NOT need a new license file. Your existing license file will work. During installation,
you will see the License file screen. On this screen, you can select a different folder or computer on
which to store the license file.
To download your license file:
1. Go to the Medisoft Clinical/Practice Partner Customer Support Web site at
https:\\support.practicepartner.com
2. Enter your user name and password. If you forgot your password, click the Forgot your
Password? link and follow the instructions.
3. Under Account Links on the right side of the page, click on View Product Details. Here is a
list of your registered Products. Click the product you would like to request the license for.
4. For the Medisoft Clinical license, you can click on ASWIN or PRWIN. On the next screen,
choose “Request a license file for installing…” Then, the license file will be sent to the logged
on user for the support website.
F. Install your License file for Medisoft Clinical/Practice Partner
Important: You must download your license file and place it in the proper folder before you begin
your upgrade of Medisoft Clinical/Practice Partner.
Simply save the files attached to the email into the License folder (usually P:\license) that already
exists on your server computer. One of the files will be named "pplic.txt". If this file doesn't exist
(because some Email programs strip this file), save the other file in the License folder and rename
it to "pplic.txt".
G. Shut down CTree Server
Shut down all connections to CTree Server and stop CTree Server prior to converting. Practice
Partner 9.5.2 SP2 will not work with CTree Plus. If this version of CTree is installed, you will
receive an error message during installation. Please call Medisoft Technical Support for help with
this issue.
September 2012
Release 18
13
Stop Services
Reminder: Make sure all users are logged out of all Practice Partner applications and will not log
back in until after the upgrade is complete.
Note: if you are installing over Practice Partner 9.4, make sure you disable all legacy CTree servers
as well.
H. Stop Services
1) Shut Down Watchdog
If you have Watchdog installed and running, you must stop it first or it will restart services (such as
Communications Manager and the PMSI Server) even if you stop them manually. To shut down
Watchdog:
1. Check if the green Watchdog icon displays in the System Tray. If it does not display in the
System Tray, you do not have it installed.
2. If so, right click the icon and select Stop.
2) Shut Down PP Connect
1. On the desktop, click the Exit button on the Connect-DemSch In screen if it is open.
Note: To open this screen, double click the Inbound DemSched icon on the desktop.
Figure 4. Connect DemSch In screen
2. On the desktop, click the Exit button on the Connect-BillCode and Sch Out screen if it is open.
14
Release 18
September 2012
3) Shut down the PMSI Data Server and Application Server
Note: To open this screen, double click the Outbound BillCode icon on the desktop.
Figure 5. Connect BillCode and Sch Out screen
3) Shut down the PMSI Data Server and Application Server
Stop the PMSI Data Server and PMSI Application Server. If you do not stop the service, you will
not be able to upgrade successfully.
1. Click Start and point to Control Panel.
2. Click Performance and Maintenance.
3. Click Administrative Tools and then Services.
4. Find PMSI Data Server and right-click. Click Stop.
5. Find PMSI Application Server and right-click. Click Stop.
Before using Medisoft Clinical, you will need to verify that the installation restarted the
services. Instructions are provided at “Restarting the PMSI Data Server and PMSI Application
Server” on page 20.
4) Close Communications Manager and Messenger
1. Close Communications Manager if it is open and running on the server.
2. You must also stop Communications Messenger. Right-click its icon in the system tray.
3. Click Exit.
4. Click OK on the message screen that appears.
Before using Communications Manager, you will start it again. Do this AFTER installing the
upgrade on the server. Use these steps:
1. Launch Communications Manager.
2. Click Configuration and select the Enable Communications Messenger on this Machine
check box.
September 2012
Release 18
15
Install Medisoft Clinical Server Upgrade
Important note: If you are extracting the ISO or webinstall file to the hard drive prior to installing,
extract to a folder that is immediately off the root drive and the folder name must be short. For
example, c:\Install. Do NOT use a long folder name. This is recommended for both server and
workstation installs.
1. Insert the Medisoft Clinical DVD in the server drive. The Installation screen appears.
If the Installation screen does not appear automatically, click Start and select Run. On the
Run screen in the Open field, type X:\AUTORUN (where X is your DVD-ROM drive letter) and
click OK. The Installation screen appears.
McKesson recommends that you do NOT attempt to install using any programs with the
extension *.msi, such as setup.msi. Doing so may result in failure of the installation. Always
use autorun.exe.
Note: If you are required to install any further software (such as .NET Framework 3.5.1) that
requires a reboot, make sure the PMSI services and Communications Manager did not restart.
2. On the Installation screen, click the Install Medisoft Clinical link. The Welcome screen
appears.
3. Click Next. If you see the Beta Agreement screen, click Next. The End User License
Agreement screen appears.
4. Select I accept the agreement.
Figure 6. End User License Agreement screen
16
Release 18
September 2012
5. Click Next. The Select Medisoft Clinical Components to Install screen appears.
Figure 7. Select Components to Install screen
6. Select the Advantage Database Server V10.10, Medisoft Clinical Server check box, and
the CTree Server V7 check box. If you currently have Medisoft Client, Office Pro, and
Medisoft Clinical Client installed on the server, select these check boxes as well.
Note: You must select Advantage Database Server for Medisoft 18.
If you select these options, you will see additional screens for these options during the install.
Be sure to select the CTree Server check box even if you are installing over a previous
version. Re-installing reconfigures CTree Server to run with the Medisoft Clinical upgrade.
7. Click Next. The Select Options Installation screen appears.
Figure 8. Select Options Installation screen
September 2012
Release 18
17
8. Enter the information for your Advantage license. Click Next. McKesson recommends that you
do not put any spaces in the field for Registered Owner.
9. Click Next on the Select Options Installation screen that shows you the current location of the
Medisoft Clinical Server files. This screen will also show you the version you are upgrading
from.
10. On the Select Destination Directory screen, on the CTree Server Options section of the screen
in the Password field, enter a CTree server password for the installation. For instance, you
could enter the Password as your password or Admin as a password.
11. Click Next. The Medisoft Clinical Basic Options screen appears.
12. Create a user name and password for the installation for Medisoft Clinical. The name entered
in the Admin User Name field and the password entered is for the installation only.
NOTE: For existing sites, this name and password is only used for the installation of the upgrade.
You will still use your user name and password that you created when you previously installed
Medisoft Clinical to log into Medisoft Clinical.
13. Click Next. The Ready to Install screen appears.
14. Click Install. The FairCom Server Activation Utility screen appears.
15. Enter the last six digits of your CTree serial number in the Serial Number field and enter your
Activation Key in the Activation Key field.
16. Click Activate.
Figure 9. FairCom Server Activation Utility screen
17. Click OK on the information message. A progress bar appears, tracking the installation.
Warning: if you already have the latest version of Practice Partner Server installed, or a version
newer than the one you are attempting to install, you will receive a warning message. Click OK if
you want to continue with the installation and overwrite the existing version of Practice Partner
Server or click Cancel to stop the installation of Practice Partner Server and finish installing the
other items selected on the Select Components to Install screen.
The installation of Practice Partner Server could take several hours to a full day because your
data is being upgraded during the installation. Once the installation has started, do not
cancel the installation or you will have to start it over.
If you are upgrading from Release 16 with Practice Partner 9.4 and receive the error, “Cannot
access file mrpath.fl, please check permissions,” click OK and the installation will stop at this
18
Release 18
September 2012
point. Copy the file mrpath.fl from the Ppart_Legacy folder on the P: drive into the Ppart folder.
Then, restart the installation and select only Medisoft Clinical Server and Medisoft Clinical
Client and allow the installation to finish.The Installation Completed screen appears.
18. Click Finish. The screen closes and the installation finishes.
Figure 10. Installation Completed screen
19. Install or upgrade any Medisoft Clinical Add-Ons that you want to install or upgrade. For more
information on Add-Ons, see “Add-Ons” on page 51.
20. After you complete the upgrade of Medisoft Clinical and any Add-Ons, run the Patch Updater
Utility to install patches to Practice Partner that are on your installation DVD. Patches issued
after DVD was pressed must still be downloaded using the Patch Updater Utility. Instructions
for using this utility are available on your Medisoft Clinical DVD via the autorun.exe program.
Start Autorun and select Patch Download/Installation.
To launch the Update Utility:
a. Open Windows Explorer and navigate to P:\ppart\Updater.
b. Double click PMSI.Installer.Updater.Manager.exe.
c. Follow the steps in the Updater to complete downloading and installing the
patches.
September 2012
Release 18
19
Restarting the PMSI Data Server and PMSI Application Server
Medisoft Clinical installs Practice Partner 9.5.2 SP2. If the Updater utility lists SP2 as a potential
update, please disregard it and install the other updates. Leave the options as they are and
continue.
Restarting the PMSI Data Server and PMSI Application Server
Before using Medisoft Clinical, you will need to verify if the installation restarted the PMSI Data
Server and PMSI Application Server. If these services were not restarted, you will need to restart
them. To do so,
1. Click Start and navigate to the Control Panel.
2. Click Performance and Maintenance.
3. Click Administrative Tools.
4. Click Services.
NOTE: depending on your version of the Windows operating system, the Performance and
Maintenance option does not always appear. In this case, go to the Administrative Tools option.
5. Find PMSI Data Server and right-click. Click Start.
6. Find PMSI Application Server and right-click. Click Start.
Watchdog
If you have Watchdog installed, you will need to restart it. To do so,
1. Right click the yellow Watchdog icon in the System Tray
2. Select Start or Restart. It will turn green to indicate it is restarted.
20
Release 18
September 2012
Installing Medisoft On the Client Workstations
Installing Medisoft On the Client Workstations
Installing Medisoft and Practice Partner Client on Each
Workstation
1. Insert the Medisoft Clinical DVD in the client drive. The Installation screen appears.
If the Installation screen does not appear automatically, click Start and select Run. The Run
screen appears. On the Run screen in the Open field, type X:\AUTORUN (where X is your
DVD-ROM drive letter) and click OK. The Installation screen appears. McKesson recommends
that you do NOT attempt to install using any of the programs with the extension *.msi, such as
setup.msi. Doing so may result in failure of the installation. Always use autorun.exe.
If you are installing on the Windows Vista or Windows 7 platform, the User Account Control
screen may appear. Click Allow.
2. On the Installation screen, click Install Medisoft Clinical. The Welcome screen appears.
3. On the Welcome screen, click Next. The End User License Agreement appears.
4. Click the I Accept the agreement button.
5. Click Next. The Select Medisoft Clinical Components to Install screen appears.
6. Select the Medisoft Client check box and select the Medisoft Clinical Client check box.
NOTE: You will not be able to make this selection if you have not completed the server installation.
The installer will look for the server installation before it will allow you to select the Medisoft Clinical
Client option.
Figure 11. Select Components to Install screen
7. Click Next. The Subscription Agreement screen appears.
8. Click the I accept the agreement button.
September 2012
Release 18
21
Installing Medisoft and Practice Partner Client on Each Workstation
9. Click Next. The Select Components screen appears.
10. Select available check boxes to install the options.
Figure 12. Select Client Components screen
11. Click Next. The Select Destination Directory screen appears. Accept the default or browse for
a location to install Medisoft Net Pro. If a previous version is already installed, select that
location.
If you select a destination directory that is non-standard, or different from the existing one, you will
need to manually edit the *.ini files for this new location (DemSch, BillCode, XFire, etc).
12. Click Next. If you chose to install Office Hours, use this screen to select the location for Office
Hours Net Pro.
13. Click Next. The Select Medisoft Clinical Directory screen appears.
14. Click Next to install the Medisoft client in the default directory. This choice is the one of the
previous version of Medisoft Clinical. Do NOT change these paths.
Figure 13. Select Options Installation: Server Directory screen
22
Release 18
September 2012
Installing Medisoft and Practice Partner Client on Each
Users must have at least WRITE permission to this directory, as well as the User directory
(usually c:\Documents & Settings\All Users\Application Data\Medisoft), or you may receive
errors when you start Medisoft.
15. Click Next. The Ready to Install screen appears.
Click Next. A progress bar appears until you receive the Installation Completed screen.
Warning: if you already have the latest version of Practice Partner Client installed, or a version
newer than the one you are attempting to install, you will receive a warning message. Click OK if
you want to continue with the installation and overwrite the existing version of Practice Partner
Server or click Cancel to stop the installation of Practice Partner Client and finish installing the
other items selected on the Select Components to Install screen.
16. Click Finish. The Installation Completed screen appears.
Figure 14. Installation Completed screen
17. Install or upgrade any Medisoft Clinical Add-Ons that you want to install or upgrade. For more
information on Add-Ons, see “Add-Ons” on page 51.
18. After you complete the upgrade of Medisoft Clinical and any Add-Ons, run the Patch Updater
Utility to install patches to Practice Partner that are on your installation DVD. Patches issued
after DVD was pressed must still be downloaded using the Patch Updater Utility. Instructions
for using this utility are available on your Medisoft Clinical DVD via the autorun.exe program.
Start Autorun and select Patch Download /Installation.
To launch the Update Utility:
a. Open Windows Explorer and navigate to P:\ppart\Updater.
b. Double click PMSI.Installer.Updater.Manager.exe.
c. Follow the steps in the Updater to complete downloading and installing the
patches.
September 2012
Release 18
23
Installing Medisoft and Practice Partner Client on Each Workstation
Medisoft Clinical installs Practice Partner 9.5.2 SP2. If the Updater utility lists SP2 as a potential
update, please disregard it and install the other updates. Leave the options as they are and
continue.
19. Repeat these steps for each client workstation.
24
Release 18
September 2012
Accessing and Registering Medisoft from the Workstation
Accessing and Registering Medisoft from the
Workstation
When you purchased Medisoft Network Professional, you also purchased a number of connections
for your network.
After Medisoft has been installed on each computer, launch Medisoft on any workstation. The first
time the program opens, a data conversion message appears. This is normal. Back up data before
completing data conversion.
After Medisoft launches for the first time, the Registration screen appears. Register now or within
30 days after installation. For instructions or questions on registering, click the Help button on the
Registration screen.
If you are working with multiple practices, each time you open a new practice that particular
practice also needs to be converted until all practices have been converted to the current version.
September 2012
Release 18
25
Configuring Communications Manager
Configuring Communications Manager
If Communications Manager is already configured and you do not need to change any settings,
skip to “After Installing the Medisoft Clinical Update” on page 33.
Option: Edit your Medisoft Clinical connection in Communications Manager to take advantage of
the Automatic Provider Mapping and Library Synchronization features or continue to manually
enter providers and update the DemSch and Billing cross reference files. To do so, skip to
“Automatic Provider Update Overview” on page 27.
Consider reviewing the section at “If you decide not to use the Automatic Provider Update Feature”
on page 26 before going to the next step. This section documents using the library update feature
for sending facilities, procedure codes, and diagnosis codes. If you do not turn on the automatic
provider mapping feature, you will need to continue manually editing the provider cross-reference
files for any new providers. The files are located in the [Practice Partner directory
folder]\interface\Medisoft\RCV\CrossRef\ directory and the [Practice Partner directory
folder]\interface\Medisoft\SND\CrossRef directory. See the Set up Cross-Referencing section in
the PPConnect: Dem/Sch/Billing User’s Guide for a complete explanation. The guide is located in
the Documentation folder on the Medisoft Clinical DVD.
If you decide not to use the Automatic Provider Update Feature
Even if you are not using the automatic provider mapping feature, you can still send other library
synchronization updates such as facilities, diagnosis codes, and procedure codes.
When sending Library Synchronization data (in this case facilities, diagnosis codes, and procedure
codes) you cannot also send demographic and appointment data. Each of these processes needs
to have separate cycles that complete before the process runs to guarantee that data transfers.
When you have a need to send the latest library updates (facilities, procedure codes, or diagnosis
codes) from Medisoft to Medisoft Clinical,
1. Verify that the Medisoft Clinical Inbound DemSch and Outbound Bill Code features are not
running.
2. In Communications Manager on the Medisoft Clinical connection, clear the Transmit
Appointments check box, Transmit Patient Demographics check box, Receive Medisoft
Clinical transactions check box, and Send & Receive appointment status updates check
box.
3. Select the Library Synchronization choices of Send Facilities box, Send Procedure Codes
box, or Send Diagnosis Codes check box.
4. Click Done. The library updates are sent at the next transmission interval.
5. After sending the updates, verify that the information transferred to Medisoft Clinical. Then
return to Communications Manager and on the Medisoft Clinical connection select (check) the
Transmit Appointments check box, Transmit Patient Demographics check box, Receive
Medisoft Clinical transactions check box, and Send & Receive appointment status
updates check box. The demographic and appointment updates are sent at the next
transmission interval.
6. Turn on the Medisoft Clinical Inbound DemSch and Outbound Bill Code features to import this
data (demographics and appointments) into Medisoft Clinical.
26
Release 18
September 2012
Automatic Provider Update Overview
Automatic Provider Update Overview
Before you perform the procedure below for using Communications Manager with Automatic
Provider Mapping, carefully read “Types of Provider Mappings” on page 35 so you understand how
mappings work.
The automatic provider mapping feature, when turned on, manages provider updates and replaces
the need to edit and update the DemSch and Billing cross reference files. The automatic provider
mapping feature replaces the need to enter providers in both systems (now entered in Medisoft
only) and to update the provider mappings in the cross reference files.
Configuring the Automatic Provider Update Feature
Use this procedure if you decide to start using Automatic Provider Mapping.
1. Verify that the Medisoft Clinical DemSch feature is not running. On the desktop, click the Exit
button on the Connect-DemSch In screen if it is open.
Figure 15. PP Connect DemSch In screen
2. Also verify that the Medisoft Clinical Outbound BillCode feature is not running. On the desktop,
click the Exit button on the Connect-BillCode and Sch Out screen if it is open.
Figure 16. PP Connect BillCode and Sch Out screen
3. Launch Medisoft on a client computer (not the server) and open a practice.
September 2012
Release 18
27
4. On the Tools menu, click Communications Manager.
Figure 17. Tools menu
5. Communications Manager launches showing the practice you are logged into and your user
name.
6. Click Connections and click Edit on your Medisoft Clinical connection.
Note: If you changed the path to Practice Partner from P:\ppart to anything else, make sure you
change the path in the PP Server Location field.
7. To use this feature to manage your provider updates, you will first resend your providers using
the automatic provider mapping feature. At the same time, you can also send any other library
synchronization data (facilities, diagnosis codes, and procedure codes) to Medisoft Clinical.
8. Make the following selections:
28
Check box
Selected
Automatic Provider Mapping
Yes
Bypass Synchronization Process
Yes
Transmit Appointments
No
Transmit Patient Demographics
No
Receive Medisoft Clinical transactions
No
Send & Receive appointment status updates
No
Force Resynch on next transmission interval
No
Release 18
September 2012
Figure 18. Communications Manager screen
9. Select the Send Providers check box.
Option: Also select the Send Facilities check box, Send Procedure Code check box, and
Send Diagnosis Codes check box. Sending procedure codes and diagnosis codes can take
several hours depending on the file size. Consider selecting these options at the close of your
business day.
WARNING: Click Configure and verify that the Synchronization File Destination check box has
a value. If this field is not populated, Library Synchronization will fail. In almost all cases, do not
change this default value. If you change this location, the updates will not transmit unless you also
change settings in the .ini file in the CrossFire application in Medisoft Clinical.
10. Click Done. Providers and any other library data are sent at the next transmission interval.
WARNING: The appointment and demographic data transfer is a different process than the library
synchronization process. The library synchronization cannot occur at the same time as
September 2012
Release 18
29
appointment and demographic data transfer; if these processes run at the same time, data might
not completely transfer.
11. Click Configuration. Make sure the Enable Communications Messenger on this Machine
check box is selected. The data is transferred at the next transmission interval.
12. Click the Medisoft Clinical icon and verify that any new providers transferred to Medisoft
Clinical.
13. Return to Communications Manager. On the Connections screen, click the Edit button on the
Medisoft Clinical connection entry. Make the following selections:
30
Check box
Selected
Automatic Provider Mapping
Yes
Bypass Synchronization Process
Yes
Yes
Yes
Receive Medisoft Clinical transactions
Yes
Send & Receive appointment status
updates
Yes
Force Resynch on next transmission
interval
Yes
Release 18
September 2012
Library Synchronization
14. Make sure the Library Synchronization check boxes (Send Providers, Send Facilities, Send
Procedure Codes, and Send Diagnosis Codes) are NOT selected (checked).
15. Click Done.
16. Double-click the Medisoft Clinical Inbound DemShed icon on the Medisoft Clinical client pc
desktop. The Connect-DemSch In screen launches.
Figure 21. Connect DemSch In icon
17. Double-click the Medisoft Clinical Outbound BillCode icon on the Medisoft Clinical client pc
desktop. The Connect-BillCode and Sch Out screen launches.
Figure 22. Connect Outbound BillCode icon
18. Return to Medisoft Clinical and verify that appointments and demographics transferred to
Medisoft Clinical.
When sending Library Synchronization data (in this case facilities, diagnosis codes, and procedure
codes), you cannot also send demographic and appointment data. Each of these processes needs
September 2012
Release 18
31
to have separate cycles that complete before the process runs to guarantee that data transfers.
When you have a need to send the latest library updates (facilities, procedure codes, or diagnosis
codes) from Medisoft to Medisoft Clinical,
1. Verify that the Medisoft Clinical Inbound DemSch and Outbound Bill Code features are not
running.
2. In Communications Manager on the Medisoft Clinical connection, clear the Transmit
Appointments check box, Transmit Patient Demographics check box, Receive Medisoft
Clinical transactions check box, and Send & Receive appointment status updates check
box.
3. Select the Library Synchronization choices of Send Facilities check box, Send Procedure
Codes check box, or Send Diagnosis Codes check box.
4. Click Done. The library updates are sent at the next transmission interval.
5. After sending the updates, verify that the information transferred to Medisoft Clinical. Then
return to Communications Manager and on the Medisoft Clinical connection select (check) the
Transmit Appointments check box, Transmit Patient Demographics check box, Receive
Medisoft Clinical transactions check box, and Send & Receive appointment status
updates check box. The demographic and appointment updates are sent at the next
transmission interval.
6. Turn on the Medisoft Clinical Inbound DemSch and Outbound Bill Code features to import this
data (demographics and appointments) into Medisoft Clinical.
NOTE: After the data is sent to Medisoft Clinical, the Library Synchronization boxes you selected
are cleared, and the system displays when the update occurred. There is no need to turn off the
Medisoft Clinical Inbound DemSch and Outbound BillCode until you need to synchronize these
libraries again.
32
Release 18
September 2012
After Installing the Medisoft Clinical Update
After Installing the Medisoft Clinical Update
NOTE: If the conversion of one or more of your database tables did not complete correctly, you will
receive the following message for each of tables that did not complete correctly: “Conversion of
<TABLENAME> failed. Please contact Medisoft Clinical Support Department”, where
<TABLENAME> is the name of the database table that did not complete correctly. If you receive
this message, you can continue safely with the upgrade by clicking the OK button. Please contact
Technical Support after you have completed the installation.
This section lists general and specific post-installation requirements.
After the installation
1. Confirm that the installation was properly completed and that the system is operational by
launching the application and logging in.
If any of your users are unable to login after the upgrade, your system administrator should
reset their password in Medisoft Clinical. See the “Procedure for changing a password” section
in Patient Records Help for step-by-step instructions.
2. Set access levels for the new features.
3. For Microsoft Windows XP, Windows Vista Business edition, and Windows 7, make sure users
have adequate permission authority to read, write, and change files. Once Medisoft Clinical is
installed, reapply permissions to files and subdirectories.
4. Update your form item list with items added in Medical Billing 9.5.2.1. To update your list:
a. Start Medical Billing.
b. Click Maintenance.
c. Click Utilities.
d. Click Medical Billing.
e. Click Import New Form Items.
f. Click OK on the Add New Form screen. Medical Billing will add the new items to the form
item library.
Watchdog
A program called Watchdog is available. This program will monitor applications and services used
with Medisoft Clinical and can notify you if there are failures in these applications and services. In
addition, you can use Watchdog to shut down and restart applications and services (such as
PPConnect) periodically to ensure they are running or when you are running an automatic backup.
It can also be set up to notify you via email if there are failures in any applications and services.
To download and install Watchdog, navigate to http://www,medisoft.com/Watchdog/ and follow the
instructions.
September 2012
Release 18
33
Watchdog
34
Release 18
September 2012
Appendix A - Automatic Provider Mapping
WARNING: Do not select the checkbox for Automatic Provider Mapping in Communications
Manager before reviewing this information. Your provider ID mapping between Medisoft and
Medisoft Clinical determines if you use this feature. Using this feature if your provider ID mappings
do not meet certain conditions can jeopardize accuracy of appointments sent from Medisoft to
Medisoft Clinical, the provider associated with a patient, and possibly the provider assigned to
charges coming in from Medisoft Clinical to Medisoft. Also, before using this feature, back up your
data.
Types of Provider Mappings
There are two methods for mapping providers between Medisoft and Medisoft Clinical:
• via manual provider entry in Medisoft and Medisoft Clinical and then updating the cross
reference files to map the providers between the systems, or
• via automatic provider mapping controlled by the Automatic Provider Mapping box that
manages the process.
The automatic provider mapping feature replaces the need to enter providers in both systems (now
entered in Medisoft only) and to update the provider mappings in the cross reference files.
You can take advantage of this new feature if you are upgrading your version of Medisoft Clinical--if
you have a one-to-one relationship in your current provider record mapping between Medisoft and
Medisoft Clinical in the DemSch and Billing cross reference files.
A one-to-one mapping relationship means that you only have one provider ID for each provider
record in your practice mapping to one provider ID in Medisoft Clinical. If your practice is set up
with one-to-one provider mappings between Medisoft and Medisoft Clinical, then you can use the
automatic provider mapping feature.
Provider Mapping Examples
If you are unsure of the status of your mappings, contact Medisoft Clinical support at 800-3344006. You can also check the DemSch cross reference file (DemSch_Pvid.ref) and Billing cross
reference file (BillCode_Pvid.ref) to determine your mapping status.
One-to-One Mapping Example
To check the Dem Sch cross reference file for one-to-one mappings, go to [Practice Partner
directory folder]\\Interface\BillingBridge\DemSch\CrossRef and open the DemSch_Pvid.ref in
NotePad or WordPad. When you open this file, you will see a series of entries, for instance in a
three doctor practice:
September 2012
Release 18
35
Variation of a One-to-One Mapping Example
MM471 | MM4
JM875 | JM8
WW934 | WW9
The first entry for each line is the Provider ID from Medisoft. The second entry for each line is the
Provider ID in Medisoft Clinical.
Both items when combined create a mapping from Medisoft to Medisoft Clinical and this mapping
is used by the applications to accurately transfer or map data between the systems. In this
example, the relationship is one to one. Each of the three provider IDs in Medisoft match a single
provider ID in Medisoft Clinical.
Variation of a One-to-One Mapping Example
Another variation of a one-to-one mapping is the following:
MM471 | MM4
MM571 | MM5
MM671 | MM6
In this example, the provider in the Medisoft practice has three provider IDs (multiple provider
records in Medisoft); however, each of these Medisoft provider IDs is mapped to a specific provider
ID in Medisoft Clinical (also multiple provider records in Medisoft Clinical).
Multiple Mappings Example
If the cross reference file looked like this example below, the practice is set up using a multiple-toone mapping:
MM471 | MM4
MM571 | MM4
MM671 | MM4
In this example, there are three provider IDs in Medisoft for a single provider and the IDs are
mapped to one provider ID in Medisoft Clinical.
Check Billing Mappings Also
You must also check your mappings in the Billing cross reference file (BillCode_Pvid.ref) to
determine your mapping status. Your Billing mappings must be the same as your Dem Sch but in
reverse order; that is, the Medisoft Clinical provider IDs appear first, followed by the Medisoft
provider IDs. For instance, if you have five entries in your Dem Sch mapping, then these entries
would need to be in your Billing mapping but in reverse order (Medisoft Clinical provider ID first).
To check the Billing cross reference file, go to [Practice Partner directory
folder]\\Interface\BillingBridge\BillCode\CrossRef and open the BillCode_Pvid.ref in NotePad or
WordPad. Compare these mappings to the mappings in the Dem Sch.
If you want to interface Race, Ethnicity, and Relationship to Insured (new for Medisoft 18), you will
need to create new cross reference files.
For Race, create DemSch-Race.ref with this configuration:
36
Release 18
September 2012
Check Billing Mappings Also
C | White
B | Black
I | Indian/Alask
A | Asian
E | Other
P | Pac Isle
N | Non-Hispanic
H | Hispanic
For Ethnicity, create DemSch-Ethnicity.ref with the following values:
N | Non-Hispanic
H | Hispanic
For Relationship to Insured, create DemSch_InsRel.ref with a configuration something like the
following:
Self | S
Spouse | O
Child | C
Other | O
The following table provides a summary:
Mapping relationship
between DemSch and Billing
cross reference files
1 to 1
September 2012
Candidate for
Automatic Provider
Mapping
Yes
Release 18
Description
Do not modify the DemSch or Billing
cross reference files once you have used
automatic provider mapping. During the
initial provider library synchronization
process, the original cross reference files
for DemSch and Billing are renamed as a
precaution to the following format:
_Original.TXT.
37
Using the Automatic Provider Update Feature
1 to many
no
Do not use automatic provider mapping if
multiple provider IDs exist and are
mapped to one provider ID in Medisoft
Clinical. Doing so jeopardizes the
accuracy of:
appointments sent from Medisoft to
Medisoft Clinical,
providers associated with a patient, and
the provider assigned to charges coming
from Medisoft Clinical to Medisoft.
To use this feature to manage your provider updates, you will first send (new site) or resend
(existing site) your providers. At this time you can also send any other library synchronization data
(facilities, diagnosis codes, and procedure codes) to Medisoft Clinical. Then after this information is
transferred by Communications Manager, you can send your other data such as appointments,
demographics, etc.
Always send provider updates before sending appointment or demographic data; otherwise the
appointment and demographic data would not have a provider record to associate with in Medisoft
Clinical—providers need to be in Medisoft Clinical first.
WARNING: The appointment and demographic data transfer is a different process than the library
synchronization process. The library synchronization cannot occur at the same time as
appointment and demographic data transfer; if these processes run at the same time, data might
not completely transfer.
When using this feature, when provider records are added or updated in Medisoft and these
changes are sent via Communications Manager to Medisoft Clinical, the data is added in the
Medisoft Clinical Provider Maintenance table. Also, the Inactive status will transfer. If you mark a
provider as inactive in Medisoft, this setting transfers to Medisoft Clinical.
Also the conversion process creates a record of the automatic provider mapping outside of the
database (text file) also as a precaution/reference named using the following format: _Map.TXT.
The DemSch and Billing cross reference file mappings are replaced by new logic that converts
Medisoft provider codes that are greater than three characters to a three character code in Medisoft
Clinical. This feature manages provider matching/mapping between the systems.
Verify that the Medisoft Clinical Inbound DemSch and Outbound Bill Code features are not running.
Also you will need to clear (uncheck) in Communications Manager on the Medisoft Clinical
connection the following options:
Check Box
38
Release 18
September 2012
Check Box
Receive Medisoft Clinical Transactions
Send & Receive Appointment Status Updates
Force Resynch on Next Transmission
After sending the updates, verify that the information transferred to Medisoft Clinical. Then return to
Communications Manager and reselect the appointment and demographic options to import other
data (demographics and appointments) into Medisoft Clinical. Also turn on the Medisoft Clinical
Inbound DemSch and Outbound Bill Code features.
September 2012
Release 18
39
40
Release 18
September 2012
Appendix B - Upgrading PPConnect
In this appendix, you will learn how to check your interfaces for proper functioning.
Checking your Interfaces
The installation will have automatically installed your interfaces for you using the
MasterPPConnect.ini file that is present in your Practice Partner directory. To confirm that the
interfaces are working, you can:
1. Run your interface. If the interface runs, it was updated automatically during the installation.
2. Double-click the Connect icon “process”. If the interface loads without error, it was updated
automatically. You can exit the application.
3. Sign into Crosscheck, and open an exception file. If the file opens without error, the interface
was updated automatically.
If your site has multiple interfaces, it is recommended that you complete the instructions above for
all interfaces.
If you encounter any errors during the confirmation process, follow the instructions in the PP
Connect User Guide that is contained on your Medisoft Clinical DVD. You can access this guide as
follows:
1. Insert your DVD in your DVD drive and allow it to boot up.
2. Click Practice Partner User Guides.
3. Click DemSch Billing.
September 2012
Release 18
41
Checking your Interfaces
42
Appendix B - Upgrading PPConnect
Release 18
September 2012
Appendix C - Configuration of Firewalls and
Routers
Medisoft Clinical
• requires that your router or firewall allow inbound and outbound traffic, and
• uses two services, which are installed on the application server: PMSI data server, and PMSI
application server.
Establish these behind the firewall. All of these run under the Local System account to maintain
least privilege security on Windows XP and Windows 2003 Servers.
TCP Port
UDP Port
Description
50501
NA
PMSI Data server
50502
NA
PMSI Application server
139
137
File and printer sharing (standard
Windows services)
445
138
File and printer sharing (standard
Windows services)
Inbound Interfaces
The system does not use inbound serves as services.
TCP Port
Description
9100
Demographic data
9110
Scheduling data
9120
Combined demographic and scheduling data
9130
Laboratory data
9140
Textual data
9150
ADT data, such as medical record number
September 2012
Release 18
43
Outbound Interfaces
Appendix C - Configuration of Firewalls and Routers
Outbound Interfaces
Outbound interfaces use the following ports. Apart from outbound Order Entry, all other interfaces
are usually behind the firewall. Always use secure, encrypted connections for interfaces outside
the firewall.
TCP Port
Description
9160
All outbound interfaces
9004
Demographic data
9005
Outbound orders to LabCorp clinical laboratories
Time Synchronization
To synchronize time, Simple Network Time Protocol (SNTP) runs under the Local system Account
to maintain least privilege security, and runs both within and outside the firewall.
44
UDP Port
Description
123
Time synchronization
Release 18
September 2012
Appendix D - Add-Ons
Your Medisoft Clinical DVD comes with six add-on applications that can boost the power of
Medisoft Clinical. These add-Ons are
Add-On
Description
ePrescribing
Enables you to send and receive prescription-related messages to
and from pharmacies, to view real-time pharmacy benefits and
eligibility data on your patients, to see up-to-date formulary and
coverage information for specific drugs during the prescribing
process, and to view information about prescriptions your patients
have had filled, even from other providers
Templates
Enables you to use templates to save time by eliminating the need to
type up routine tasks.
Growth Chart
Enables you to use growth plot files for charting children’s growth.
PPConnect
Enables you to add and update information from a third-party system
into Practice Partner Patient Records and Appointment Scheduler,
as well as Practice Partner to a third-party system.
Remote Client Connect
Enables you to run interfaces on client workstations.
LabCorp
Enables you to receives patient lab results and sends orders created
in Patient Records to the lab.
NOTE: You can find detailed instructions for installing these Add-Ons at
However, you will need a login.
Installing/Upgrading Add-Ons
To install an Add-On:
1. Insert the Medisoft Clinical DVD in the drive. The Autorun screen appears. If the Autorun
screen does not appear automatically, click Start and select Run. The Run screen appears.
On the Run screen in the Open field, type X:\AUTORUN (where X is your DVD-ROM drive
letter) and click OK.
2. Click the Medisoft Clinical Add-Ons link. A list of Add-Ons appears.
3. Click the link for the Add-On you want to install. The installer starts.
4. Follow the installation wizard for the Add-On.
September 2012
Release 18
45
Installing/Upgrading Add-Ons
Appendix D - Add-Ons
5. Run the Patch Updater Utility once you have installed or upgraded your Add-Ons. For more
information on using this utility, see the Patch Download/Installation book on your Medisoft
Clinical DVD.
46
Release 18
September 2012
Index
Index
installing license file 13
installing on client 21
installing on server 16
A
Add-Ons 45
installing 45
Automatic Provider Update Feature 38
automatic provider update overview 27
C
L
changes to the installer for this release 7
checkall.bat utility
running 11
client
installing 21
Clinical Quality Measures
installing 7
closing Communications Manager 15
Communications Manager
closing 15
configuring 26
completing processes in Medisoft and Medisoft
Clinical 10
configuring Communications Manager 26
configuring firewalls and routers 43, 45
CTree server, shutting down 13
D
download
license file 13
E
ePrescribing 45
F
firewalls and routers
configuring 43, 45
G
Growth Chart 45
I
inbound interfaces 43
installation overview 9
installing
Add-Ons 45
installing Clinical Quality Measures 7
September 2012
LabCorp 45
library synchronization 31
license file
downloading 13
installing 13
M
Medisoft Clinical Add-Ons 45
Medisoft Clinical Hardware and Software
requirements 5
Medisoft Clinical Supported Operating Systems 3
Medisoft Supported Operating Systems 2
O
outbound interfaces 44
P
PMSI Application Server
restarting 16
shutting down 15
PMSI Server
restarting 16
shutting down 15
PP Connect
checking your interfaces 41
PPConnect 45
prerequisites to installing 6
provider mapping examples 35
R
registering Medisoft 25
Remote Client Connect 45
renaming or deleting list container names 10
restarting PMSI Data and Application servers 16
running the checkall.bat utility 11
S
server install 16
shut down CTree server 13
sites using custom interfaces 7
Release 18
47
Index
stopping services
PMSI server and application server 14
PP Connect 14
Watchdog 14
system preparation 10
T
Templates 45
time synchronization 44
types of provider mappings 35
U
upgrade path information 6
upgrading PP Connect 41
W
Watchdog
restarting 20
shutting down 14
48
Release 18
September 2012

Medisoft Clinical Installation Upgrade Guide

Transcription

Similar documents

Demographic and Billing Interface Guide for Medisoft

MediSoft Training Manual

Medisoft Installation Guide

Medisoft Installation Guide

Physician Practice Solutions

Regions CD Check Viewer Installation Guide

Medisoft 18 User Manual and Guide

Medisoft Network Professional Medisoft Advanced Medisoft