McKesson Practice Interface Center User Guide

McKesson Practice Interface Center User Guide
Title page
Business Performance Services
McKesson Practice Interface Center
Installation and User’s Guide
February 2014
Produced in Cork, Ireland
Copyright notice
Copyright notice
Copyright © 2014 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
February 2014
Produced in Cork, Ireland
Product
McKesson Practice Interface Center,
Corporate address
McKesson Corporation
5995 Windward Parkway
Alpharetta, GA 30005
404-338-6000
ii
Installation and User’s Guide
2.1
February 2014
Table of Contents
Table of Contents
Chapter 1 - McKesson Practice Interface Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shutting down Communications Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Components that are installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Currently-supported connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support for multiple connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1
2
2
2
3
3
5
6
Chapter 2 - Installing and Configuring McKesson Practice Interface Center . . . . . . . . . . 7
Upgrading McKesson Practice Interface Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installing McKesson Practice Interface Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configuration and launching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Database creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configuring Mirth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 3 - Using the MPIC Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing the MPIC Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initializing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding another connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synch logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mirth Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMR Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flow of information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Log summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create New Connection screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Folders screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RelayHealth Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MPIC Database Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter Remote Login Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
21
21
26
30
32
33
35
35
38
39
40
40
41
42
44
Chapter 4 - RelayClinical eScript Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Sign up with RelayHealth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Download and install the Relay Connector Configuration Utility . . . . . . . . . . . . . . . . .
Configure MPIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring MPIC with RelayHealth as a stand alone connection . . . . . . . . . . . .
Configuring MPIC for RelayHealth with Medisoft Clinical or Lytec MD . . . . . . . . .
Configure the Relay Connector Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . .
February 2014
Installation and User’s Guide
2.1
45
45
46
46
49
51
iii
Table of Contents
Appendix A - Transmitted Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Medisoft to Practice Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message description 
Exported segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lytec to Practice Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exported segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Medisoft or Lytec to RelayHealth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
55
55
62
62
62
69
Appendix B - Automate Provider Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Methods of provider mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Provider mapping examples for Practice Partner . . . . . . . . . . . . . . . . . . . . . . . . .
Using Automate Provider Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alternative to Automate Provider Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
71
71
73
73
Appendix C - Configuring Mirth for a Remote Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Appendix D - Installing SQL Server Express manually . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
iv
Installation and User’s Guide
February 2014
List of Figures
List of Figures
Figure 1 Communications Manager screen with transmit options highlighted . . . . . . . . . . . . . . . . . . . . . 3
Figure 2 McKesson Practice Interface Center Setup screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 3 Error message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 4 MPIC Database Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 5 McKesson Practice Interface Center Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 6 Mirth Connect Administrator Login screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 7 Welcome to Mirth Connect screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 8 Mirth Connect Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 9 Mirth Settings screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 10 Open screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 11 MPIC Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 12 Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 13 Create New Connection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 14 Initialize Data screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 15 Enter Remote Login Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 16 View Logs screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 17 Synch log with trigger highlighted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 18 MPICService.exe.config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 19 Mirth log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 20 View Logs screen with DemSch Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 21 DemSch log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 22 View Logs screen with XFire Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 23 XFire log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 24 Create New Connection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 25 Folders screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 26 RelayHealth Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 27 MPIC Database Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 28 Enter Remote Login Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 29 Interface Settings screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 30 Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 31 Relay Connector Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 32 RelayConnector Configuration Utility - Upload Messages tab . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 33 RelayConnector Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 34 Mirth Connect Service Properties (Local Computer) screen . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 35 SQL Server Installation Center screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 36 Feature Selection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 37 Instance Configuration screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 38 Server Configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 39 Database Engine Configuration screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
February 2014
Installation and User’s Guide
v
List of Figures
vi
Installation and User’s Guide
February 2014
Chapter 1 - McKesson Practice Interface Center
Overview
In this chapter you will learn the basics of McKesson Practice Interface Center, including what it is
and what it is designed to do. In addition, you will learn the prerequisites for using the application,
as well as the components that make up the application.
McKesson Practice Interface Center is an application designed to connect different McKesson
solutions and allow them to transfer data to one another and to outside organizations, such as
laboratories. It is independent of any specific McKesson solutions and will, in time, have
prefabricated configurations available to integrate your specific McKesson solutions. You will also
have the ability to customize it.
In this chapter
Topic
See page
Hardware requirements
2
Software requirements
2
Before you begin
2
Components that are installed
3
Currently-supported connections
5
February 2014
Installation and User’s Guide
2.1
1
Hardware requirements
Chapter 1 - McKesson Practice Interface Center
Hardware requirements
CPU (Processor)
Equivalent of Intel Quad Core Xeon 1.6GHz
RAM (Memory)
8GB
Storage Array Type
RAID-1
Optical Drive
DVD-ROM
Network Card (NIC)
1Gbps (cannot be a teamed network card)
Hard Drive
At least 30GB
Software requirements
• Windows Server 2008 R2 32 or 64-bit
• Windows Server 2003 32-bit
McKesson Practice Interface Center is only installed on your server. It does not need to be
installed on any of your workstations. Nor does it have to be dedicated.
• Medisoft 18 or higher or Lytec 2013 or higher installed on the same server as MPIC
• Windows PowerShell (if you are using Windows XP or Windows Server 2003 32-bit)
You may use a virtual server with McKesson Practice Interface Center.
Before you begin
Complete the following before you begin installing MPIC.
• Installed any software applications that you want to integrate, such as Medisoft Clinical, Lytec
MD, or Practice Partner.
• Administrator rights to the computer on which you are installing MPIC.
• Reviewed the hardware and software requirements to ensure that your system meets the
requirements.
• Disable Communications Manager if it was installed and running. Be sure to disable it in
Watchdog if you are using it.
2
Installation and User’s Guide
2.1
February 2014
Chapter 1 - McKesson Practice Interface Center
Shutting down Communications Manager
Shutting down Communications Manager
If you are currently using any version of Medisoft prior to Medisoft 19 or any version of Lytec prior to
Lytec 2014, open this screen in Communications Manager and clear the check boxes for
transmitting data.
Figure 1. Communications Manager screen with transmit options highlighted
In addition, click the Configuration button at the top left and clear the check box for Enable
Communications Messenger on this machine.
Components that are installed
McKesson Practice Interface Center installs several components that it uses to connect McKesson
solutions. MPIC will not reinstall any components that are already installed. The first four
components were developed and are supported by external vendors. MPIC will not uninstall or
update these components and McKesson is not responsible for their support. The final three
components are updated by McKesson and are uninstalled if you uninstall MPIC.
February 2014
Component
Description
.NET Framework 4.0
This is a software framework designed by
Microsoft that contains many libraries of
files that allow programs to communicate
with one another.
Installation and User’s Guide
2.1
3
Components that are installed
Chapter 1 - McKesson Practice Interface Center
Component
Description
SQL 2008 R2 Express SP1
This is a database engine that allows you
to create databases. In this case, the
database used by McKesson Practice
Interface Center to store settings and data
is an SQL database.
SQL Express 2008 will run side by side
with other versions of SQL.
4
Java Runtime
This program contains many files that
allow websites and other applications to
function correctly. Java must be installed
so that Mirth Connect will run correctly. For
more information on Mirth Connect, see
“Mirth Connect” on page 83.
Mirth Connect
This program contains the files that tell the
system what data to transmit.
McKesson Practice Interface Center
Control Panel
This application starts and stops the
McKesson Practice Interface Center
service.
MPIC Administration Database
This database contains all of the
information that you enter for your
configuration.
McKesson Practice Interface Center
Service
This program does all of the transfer of
data from application to application. It will
run all of the time once it is started. Also, it
will monitor any changes to data and
handle the transfer.
Installation and User’s Guide
2.1
February 2014
Chapter 1 - McKesson Practice Interface Center
Currently-supported connections
Currently-supported connections
Currently-supported connections for McKesson Practice Interface Center are as follows:
Connection
Direction of Data Flow
More Information
Medisoft to Medisoft
Clinical/Practice Partner
Bi-directional
To set up this connection, see “Configuring a
connection” on page 21.
Lytec to Lytec MD/
Practice Partner
Bi-directional
To set up this connection, see “Configuring a
connection” on page 21.
Medisoft to RelayHealth
Uni-directional: from
Medisoft to RelayHealth
only
You can see up this connection either in
conjunction with a connection to Medisoft
Clinical or as a stand alone connection. See
“RelayClinical eScript Connection” on page 45.
Lytec to RelayHealth
Uni-directional: from Lytec
to RelayHealth only
You can see up this connection either in
conjunction with a connection to Lytec MD or as
a stand alone connection. See “RelayClinical
eScript Connection” on page 45.
Medisoft to McKesson
Practice Choice
Uni-directional: from
Medisoft to Practice Choice
only
To set up this connection, see the McKesson
Practice Choice Demographic and Billing
Interface Guide for VAR at https://
mckwiki.mckesson.com/pps-var-central/
Medisoft%20Documentation
Note: Billing data is sent
from Practice Choice to
Medisoft behind the
scenes.
Lytec to McKesson
Practice Choice
Uni-directional: from Lytec
to Practice Choice only
Note: Billing data is sent
from Practice Choice to
Lytec behind the scenes.
February 2014
Installation and User’s Guide
2.1
To set up this connection, see the McKesson
Practice Choice Demographic and Billing
Interface Guide for VAR at https://
mckwiki.mckesson.com/pps-var-central/
Lytec%20Documentation
5
Support for multiple connections
Chapter 1 - McKesson Practice Interface Center
Support for multiple connections
McKesson Practice Interface Center will support multiple connections. However, you are limited to
one connection per practice. The only exception is this: if you are connecting to Practice Partner
(using Medisoft Clinical or Lytec MD), you can also connect to RelayHealth. You can find step-bystep instructions for creating this connection at “Configuring MPIC for RelayHealth with Medisoft
Clinical or Lytec MD” on page 49.
6
Installation and User’s Guide
2.1
February 2014
Chapter 2 - Installing and Configuring McKesson
Practice Interface Center
This chapter discusses how to install, configure, and start McKesson Practice Interface Center.
In this chapter
Topic
See page
Upgrading McKesson Practice Interface Center
Installing McKesson Practice Interface Center
Configuration and launching
7
7
9
Upgrading McKesson Practice Interface Center
If you are upgrading McKesson Practice Interface Center from an earlier version, launch the MPIC
Control Panel first, click the Settings button, and take note of the values in the fields. In addition,
take note of the values in the fields of the screen that appears after you click the EMR Settings
button. After you run the installer, you must re-enter this information.
Then, uninstall the existing version of MPIC by using Add/Remove programs. Click Start, point to
All Programs, and click Control Panel. Click Uninstall a program.
After this, continue with the installation (“Installing McKesson Practice Interface Center” on page 7).
Be sure to follow the steps for Configuration and Launching (“Configuration and launching” on
page 9). You will not need to create a user for Mirth but you must recreate your database and
restore the default configurations for Mirth. This will ensure that you are using the newest channels.
Installing McKesson Practice Interface Center
The installation will load the components that McKesson Practice Interface Center needs to run
(see “Components that are installed” on page 3 for more information).
If you are installing MPIC on a domain controller, you must install SQL Server manually before
installing MPIC. For instructions, see “Installing SQL Server Express manually” on page 77.
1. Use the table to select the URL for download.
February 2014
Version
URL
Medisoft 32-bit
http://www.medisoft.com/MPIC/V2/MPICv2.1_for_Medisoft‐
Setup32.zip
Installation and User’s Guide
2.1
7
Installing McKesson Practice Interface Center
Chapter 2 - Installing and Configuring McKesson Practice
Version
URL
Medisoft 64-bit
http://www.medisoft.com/MPIC/V2/MPICv2.1_for_Medisoft‐
Setup64.zip
Lytec 32-bit
http://www.lytec.com/MPIC/V2/MPICv2.1_for_Lytec‐Setup32.zip
Lytec 64-bit
http://www.lytec.com/MPIC/V2/MPICv2.1_for_Lytec‐Setup64.zip
2. Navigate to the folder where the files were unzipped and double-click the correct program file.
The McKesson Practice Interface Center Setup screen appears.
Figure 2. McKesson Practice Interface Center Setup screen
3. Select the I agree to the license terms and conditions check box.
If you want to change the default location on the hard drive for the files, click Options.
Note: if you already have applications like .NET Framework 4.0 installed, you might not see all of
the screens in this installation.
4. Click the Install button. Allow the installer to complete its operation. The Junction License
Agreement screen appears.
5. Click the Agree button. The Setup Successful screen appears.
6. Click the Close button.
This installation will install SQL 2008 R2 Express SP1 with presettings. If you need to access the
database and configuration, the default password is $Mpic2012.
8
Installation and User’s Guide
2.1
February 2014
Chapter 2 - Installing and Configuring McKesson Practice Interface Center
Configuration and launching
Configuration and launching
Database creation
1. On the desktop, double-click the McKesson Practice Interface Center icon. You will see the
following message.:
Figure 3. Error message
2. Click the OK button. The MPIC Database Settings screen appears. For more information on
this screen, see “MPIC Database Settings screen” on page 42.
Figure 4. MPIC Database Settings screen
This will display any existing SQL databases in the Server Name and Database Name fields.
3. Select the appropriate database in the Server Name field.
• If you are using Lytec, the existing Lytec database will appear in the Server Name
drop-down field.
• If you are using Medisoft, you will see the MPIC instance in the Server Name dropdown field.
4. Enter the Login and Password.
February 2014
Installation and User’s Guide
2.1
9
Configuring Mirth
Chapter 2 - Installing and Configuring McKesson Practice
• If you are using Lytec, use the login and password that you would use on the Specify
Default SQL Credentials screen.
• If you selected the MPIC instance, the default login is sa and the password is
$Mpic2012.
5. Click the Save button.
The database is selected or created and the McKesson Practice Interface Center Control Panel
appears. For more information on the Control Panel and the buttons that are available, see
“Viewing the MPIC Control Panel” on page 17.
Figure 5. McKesson Practice Interface Center Control Panel
Note: You must have administrator rights on the computer where MPIC is installed to open and use
the MPIC Control Panel.
Configuring Mirth
1. Click the Launch Mirth button on the MPIC Control panel (see Figure 5 on page 10). This will
start the Mirth Connect Server Manager application.The icon
appears in the System Tray.
10
Installation and User’s Guide
2.1
February 2014
Chapter 2 - Installing and Configuring McKesson Practice Interface Center
Configuring Mirth
2. Right-click the Mirth Connect icon in the System Tray and select Launch Administrator. A
download screen appears. When it is complete, you will see the Mirth Connect Administrator
Login screen.
Note: you may need to adjust your browser’s security setting to complete the download of any
Java updates.
3. Enter admin for both the Username and Password.
Figure 6. Mirth Connect Administrator Login screen
4. Click the Login button.
February 2014
Installation and User’s Guide
2.1
11
Configuring Mirth
Chapter 2 - Installing and Configuring McKesson Practice
5. On the Welcome to Mirth Connect screen, enter your information and set yourself up as a
user. Do NOT change the Username or Password. Continue with admin for both. Leave the two check boxes selected. Figure 7. Welcome to Mirth Connect screen
12
Installation and User’s Guide
2.1
February 2014
Chapter 2 - Installing and Configuring McKesson Practice Interface Center
Configuring Mirth
6. Click the Finish button. The Dashboard screen will appear.
Figure 8. Mirth Connect Dashboard
February 2014
Installation and User’s Guide
2.1
13
Configuring Mirth
Chapter 2 - Installing and Configuring McKesson Practice
7. Click Settings. The Settings screen appears.
Figure 9. Mirth Settings screen
8. Click Restore Config in the Server Tasks section of the screen. The Open screen appears.
Warning: if you are upgrading and have custom channels created, export these channels
before restoring the default configurations. Restoring the defaults will overwrite any existing
channels. After you restore the defaults, import your custom channels.
9. Navigate to the C:\Program Files\Mckesson\Mckesson Practice Interface Center\Mirth” folder.
14
Installation and User’s Guide
2.1
February 2014
Chapter 2 - Installing and Configuring McKesson Practice Interface Center
Configuring Mirth
10. Highlight defaultconfig.xml.
Figure 10. Open screen
11. Click the Open button.
12. Click the Yes button on the Select an Option screen.
13. Close Mirth Connect Manager.
14. Verify that HL7 triggers are enabled in Medisoft or Lytec.
If you are using...
Medisoft
follow these steps...
1. On the File menu, click Program Options. The Program
Options screen appears.
2. Click the General tab.
3. Verify that the Enable HL7 Triggers check box is
selected on the General tab.
Lytec
1. On the Admin menu, click Preferences. The
Preferences screen appears.
2. Click the General tab.
3. Verify that the HL7 Trigger Enable check box is selected
on the General tab.
15. Continue to “Configuring a connection” on page 21 to complete the configuration.
For issues with troubleshooting, see the MPIC Troubleshooting Guide at https://
mckwiki.mckesson.com/pps-var-central/mpic_troubleshooting_guide.
February 2014
Installation and User’s Guide
2.1
15
Configuring Mirth
16
Chapter 2 - Installing and Configuring McKesson Practice
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Use the MPIC Control Panel to start and stop the MPIC service, create a new connection, change existing
connections, and view any errors that occur.
In this chapter
Topic
See page
Viewing the MPIC Control Panel
17
Configuring a connection
21
Viewing logs
32
Adding another connection
30
Folders screen
40
RelayHealth Settings screen
41
Viewing the MPIC Control Panel
To view the MPIC Control Panel:
• On the Desktop, double-click the MPIC - McKesson Practice Interface Center icon. The MPIC
February 2014
Installation and User’s Guide
2.1
17
Viewing the MPIC Control Panel
Chapter 3 - Using the MPIC Control Panel
Control Panel appears.
Figure 11. MPIC Control Panel
Note: You must have administrator rights to the computer on which MPIC is installed to open
and use the MPIC Control Panel
The following table summarizes the fields and buttons that are available.
18
Field/Button/Link
Description
Last Message Sent
This reflects when the last message (data transfer) was sent
from the practice management application to the EMRs for
all connections. If messages have not been sent for some
time, there is likely an error. You can use the logs to identify
and correct the error. For more information on the logs, see
“Viewing logs” on page 32.
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Viewing the MPIC Control Panel
Field/Button/Link
Description
Last Message Received
This reflects when the last message (data transfer) was
received from the EMRs by the practice management
application for all connections. If messages have not been
received for some time, there is likely an error. You can use
the logs to identify and correct the error. For more
information on the logs, see “Viewing logs” on page 32.
Last Message Error
This reflects when the last error message occurred for all
connections. Types of errors include lost connectivity in the
network and invalid data. If there is an error, use the logs to
identify the error so you can fix it. For more information on
the logs, see “Viewing logs” on page 32.
Database Settings
Click to open the Database Settings screen. Use this screen
to create a new SQL database for MPIC to use. Lytec users
may use this screen to use the existing Lytec database for
MPIC. For more information, see “MPIC Database Settings
screen” on page 42.
Launch Mirth
Click to launch the Mirth Connect Server Manager. The icon
for this application will appear in the System Tray. For more
information on the Mirth Connect Server Manager, see
“Configuration and launching” on page 9.
Settings
Click to open the Settings screen. For more information on
this screen, see “Settings screen” on page 22.
This button will be disabled if there is no MPIC Database.
You will create this database using the MPIC Database
Settings screen. For more information, see “MPIC Database
Settings screen” on page 42.
Initialize Data
Click to open the Initialize Data screen on which you can
change the settings for the types of practice records that will
be transferred when you create the connection and perform
the initial data transfer. For more information on this screen,
see “Initialize Data screen” on page 26.
This button will be disabled until there is a connection type.
Start EMR Services
Click to launch the Demographics/Scheduling Interface,
which imports demographic and appointment scheduling
data from the practice management system to the EMR. as
well as the BillCodes application. If these applications are
already running, MPIC will stop them and then restart them.
Clicking this button will start the interface only for the
computer on which MPIC is installed. If you have
connections to remote servers, you must manually start the
EMR services from those servers.
This button will not launch either application until you have
created a connection, In addition, it will be disabled unless
your connection is for Medisoft Clinical or Lytec MD.
February 2014
Installation and User’s Guide
2.1
19
Viewing the MPIC Control Panel
Chapter 3 - Using the MPIC Control Panel
Field/Button/Link
Description
Start Service
Click to start the MPIC service for all connections. When the
service is started, data transmission between applications
will begin. Data will be transmitted behind the scenes.
Once the service is started, this button will be disabled.
Stop Service
Click to stop the service for all connections. This will stop
data transmission.
Restart Service
Click to restart the service after you manually stop it.
If you make changes to the settings while the service is
running, the service will automatically stop and restart when
you are finished making changes.
View Logs
Click to open the View Logs screen. For more information on
the logs, see “Viewing logs” on page 32.
Watchdog
Click this button to launch Watchdog, an application that
monitors processes and services running on the server for
Medisoft Clinical and Lytec MD.
If Watchdog is not installed, you will receive a message. To
learn more about Watchdog, see the Watchdog User’s Guide
at https://mckwiki.mckesson.com/pps-medisoft-central/
documentation for Medisoft or https://
Medisoft https://mckwiki.mckesson.com/pps-varmckwiki.mckesson.com/pps-lytec-central/documentation
for
central/Medisoft%20Documentation
Lytec.
Lytec
https://mckwiki.mckesson.com/pps-varValue-Added
Resellers can use the following link to access
central/Lytec%20Documentation
documentation:
View User Guide
Click to view the McKesson Practice Interface Center
Installation and User’s Guide.
You must have Adobe Reader installed to view the guide.
Close
20
Click to close the MPIC Control Panel screen.
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Configuring a connection
Configuring a connection
Initial configuration of an interface connection involves several steps: create the connection, select
applications and types of data to transfer, and start the service. You can create multiple
connections with MPIC. Use the table as an overview of the steps to take.
Action
Processes to complete
Create an interface
connection
Create the connection (see “Creating a connection” on page 21)
Update an existing
interface connection
Click Settings and update the connection (see “Creating a
connection” on page 21.
Initialize Data (see “Initializing data” on page 26).
The MPIC service will stop and restart automatically.
Add another connection
Click Settings and then the New button. Enter a new Connection
Name and then complete the fields on the Settings screen (see
“Adding another connection” on page 30).
Update Xfire, “library”
files (providers, facilities,
procedure codes,
diagnosis codes)
Initialize Data (see “Initializing data” on page 26).
Creating a connection
Use these steps to create a connection, specifying the applications for the interface, entering basic
practice information, and selecting what types of data will be transmitted behind the scenes.
1. Double-click the MPIC icon on the desktop. The MPIC Control Panel appears.
February 2014
Installation and User’s Guide
2.1
21
Creating a connection
Chapter 3 - Using the MPIC Control Panel
2. Click the Settings button. The Settings screen appears. Initially, the screen will be blank.
Figure 12. Settings screen
22
Field/Button/Link
Description
Connection Name
Use this drop-down list to select a connection. Connection
Names are added when you click the New button and add a
new connection.
New
Click this button to open the Create New Connection screen
on which you can add a new connection. For more
information, see “Create New Connection screen” on page
40.
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Creating a connection
Field/Button/Link
Description
Delete
Select this button to delete the existing connection and all
background information on the connection. You will receive a
warning prior to the deletion of the connection.
This button will be disabled if there is no existing connection.
Note: You must click the OK button on the Settings screen to
complete the deletion of the connection.
Connection Type
Select a connection type from the drop-down list. The list will
include all types currently available. What you select here
depends on what two applications you want to connect. The
connection contains hard-coded information specifically
designed to enable the two applications to transmit data to
one another.
Server Name (Path)
Enter the path of the server that MPIC is installed on.
Database Name
Use this to enter the name of the database.
User ID
Enter the ID of the administrative user.
Password
Enter the Password of the administrative user.
Practice Name
Select the appropriate practice from the drop-down list.
Transmit Interval (23600 seconds)
Use these fields to specify the amount of time in between
transmissions of data. The default, recommended value is
30. The transmitting features use this option but the syncing
features do not.
EMR Settings
Use this to open the Folders screen or the Practice Choice
Settings screen. You must set up folders before you can
perform a sync. For more information, see “Folders screen”
on page 40. If you are setting up a connection, you will need
to complete the fields on the Practice Choice Settings
screen. For more information, see McKesson Practice
Choice Demographic and Billing Interface Guide for VAR at
https://mckwiki.mckesson.com/pps-var-central/
Medisoft%20Documentation.
Transmit patient
demographics
Select this check box if you want to transmit demographic
information for new patients or changed information from the
practice management system to the EMR. This includes all
information that is common to the practice management
system and EMR.
For more information on what data is transmitted for each
connection, see “Transmitted Information” on page 55.
Selecting this check box will enable the transmission of
patient demographics behind the scenes after you click Start
Services on the MPIC Control Panel. Before you start the
service, perform the initial synchronization (load) on the
Initialize Data screen (see “Initialize Data screen” on page
26).
February 2014
Installation and User’s Guide
2.1
23
Creating a connection
Chapter 3 - Using the MPIC Control Panel
Field/Button/Link
Description
Transmit appointments
Select this check box to transmit appointment information
from the practice management system to the EMR. This
includes all pertinent information for the appointment, such
as date, time, and length.
Selecting this check box will enable the transmission of
appointments behind the scenes after you click Start
Services on the MPIC Control Panel. Before you start the
service, perform the initial synchronization (load) on the
Initialize Data screen (see “Initialize Data screen” on page
26).
Send and receive
appointment status
updates
Select this check box if you want to transmit changes to the
status of appointments that are made in your applications.
This is a bi-directional transfer.
Automate provider
mappings
Select this check box if your providers do not exist in the
EMR and you want their information transmitted to the EMR.
CLEAR this check box if either of the following situations
exist:
• You have a one-to-many relationship for your providers.
That is, you have a single record for a particular provider
in the practice management system but have more than
one record for the same provider in the EMR (for
instance, that provider works out of several locations).
If you enable this feature and use it in this situation, you
jeopardize accuracy of appointments sent from the
practice management system to the EMR, the provider
associated with a patient, and possibly the provider
assigned to charges coming in from the EMR.
For more information on provider mapping, see “Automate
Provider Mapping” on page 71.
Receive billing
messages
24
Select this check box to receive transactions/charges from
the EMR application. For Medisoft, transactions received will
appear on the Unprocessed Charges screen. For Lytec,
charges received will appear on the Pending Transactions
screen.
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Creating a connection
Field/Button/Link
Description
Transmit Demographics
to RelayHealth
Select this check box if you are going to use MPIC to send
demographic information for new patients or edited patient
records to RelayHealth.
When you select this check box, the RelayHealth Settings
button appears.
You can set up the RelayHealth connection at the same time
that you create your connection for Medisoft or Lytec or you
can return to this screen later to set it up.
For detailed instructions on setting up the connection to
RelayHealth, see “RelayClinical eScript Connection” on page
45.
RelayHealth Settings
Use this button to open the RelayHealth Settings screen. For
more information, see “RelayHealth Settings screen” on
page 41.
OK
Use this to save changes to the Settings screen and close
the screen.
Cancel
Use this to cancel any changes made to the Settings screen.
3. Click the New button. The Create New Connection screen appears.
Figure 13. Create New Connection screen
4. Enter the name for your new connection.
5. Click the OK button.
6. On the Settings screen, select a connection type option from the drop-down menu. The
interface contains various default settings used for the starting point for a connection. These
settings help establish settings for one or more connections. When you select the interface
many of the fields on this screen will be filled automatically.
7. Complete the other fields on this screen as necessary, making sure that you select the correct
Practice Name.
8. If you are setting up a connection to RelayHealth at this time, select the Transmit
Demographics to RelayHealth check box.
9. If you are setting up a connection to RelayHealth at this time, click the RelayHealth Settings
button and enter the information you received from RelayHealth on the RelayHealth Settings
screen. For more information, see “RelayHealth Settings screen” on page 41. Make sure you
enter the correct Source Provider IDs and RelayHealth Provider IDs for each of your
February 2014
Installation and User’s Guide
2.1
25
Initializing data
Chapter 3 - Using the MPIC Control Panel
providers.You can find your provider IDs in Medisoft or Lytec and RelayHealth will provide your
Relay Health Provider IDs when you sign up.
10. Click the OK button.
Initializing data
Use these steps to perform an initial synchronization of up to four different types of records, as
well as an initial “load” of patients and appointments for a new EMR.
This screen is only for an initial data transfer or occasional transfers of data if you add new
providers, facilities, procedure codes, or diagnosis codes. In addition, it is only for an initial,
one time transfer of patient and/or appointment records from the practice management system
to the EMR. Once this initial “load” is made, MPIC will automatically transfer appointments and
patients behind the scenes after you click Start Services on the MPIC Control Panel. Just
make sure you have selected the Transmit patient demographics and Transmit
appointments check boxes on the Settings screen (see “Settings screen” on page 22).
1. On the MPIC Control Panel, click the Initialize Data button. The Initialize Data screen
appears.
Figure 14. Initialize Data screen
26
Field/Button/Link
Description
Connection Name
Select the connection that you want to synch data for.
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Initializing data
Field/Button/Link
Description
Synch Providers
Select this check box if you want to send provider
information from the practice management application to the
EMR.
If Automate Provider Mapping is selected on the Settings
screen, MPIC will attempt to find a provider record in the
EMR that matches the one being sent. If it does, it will
automatically map the providers. If not, it will create a new
provider record in the EMR.
If Automate Provider Mapping is cleared on the Settings
screen, MPIC will create a new provider record in the EMR
for new providers being sent. In addition, this check box will
be disabled.
This field applies only if you are connecting to Practice
Partner.
Synch Facilities
Select this check box if you want to send facility information
from the practice management application to the EMR.
This field applies only if you are connecting to Practice
Partner.
Synch Procedure Codes
Select this check box if you want to send procedure code
information from the practice management application to the
EMR.
This field applies only if you are connecting to Practice
Partner.
Synch DX codes
Select this check box if you want to send diagnosis code
information from the practice management application to the
EMR.
This check box applies to versions prior to Medisoft v19 SP1
and Lytec 2014 SP1.
This field applies only if you are connecting to Practice
Partner.
Last Synch Times
February 2014
These date and time stamps show the last synch time for all
connections for each type of information.
Installation and User’s Guide
2.1
27
Initializing data
Chapter 3 - Using the MPIC Control Panel
Field/Button/Link
Description
Synch
Clicking this will launch XFire Demographics to send the
data from the practice management application to the EMR
based on the settings you selected. If the folders for this
connection are located on a remote server, MPIC will display
the Enter Remote Login Information screen and prompt you
for credentials for the remote server, and attempt to launch
XFire Demographics on the remote server. For more
information on the Enter Remote Login Information screen,
see “Enter Remote Login Information screen” on page 44.
Use this only if any of this information has changed in the
practice management system and you need to update the
EMR.
The EMR will check each record. If it does not exist in the
EMR, it will be added. If it does exist, it will not be duplicated.
This field applies only if you are connecting to Practice
Partner.
Patients
Select this button if you want to send the demographic data
on all patients to your EMR. This will include both active and
inactive patients, unless you chose to use the Exclude
Inactive Patients filter.
Patients and
Appointments
Select this button if you want to send all patient and
appointment data to your EMR.
Exclude Deceased
Patients
Select this check box if you want to exclude deceased
patients from your initial transfer of data. MPIC will look for a
date in the date of death field in the patient’s record. If the
field is populated, the record will not be transferred to the
EMR.
Exclude Inactive
Patients
Select this check box if you want to exclude patients who
have been marked inactive in the practice management
application.
Date Last Seen
Select this check box if you want to limit the transfer of
patient records based on the last seen date. The date is
based on either the appointment date or the last Date of
Service.
If you select this option, enter a date in the From field.
From
28
Specify a beginning appointment date for patient records to
transfer. Records of patients who had an appointment after
this date will be sent in the initial transfer of data.
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Initializing data
Field/Button/Link
Description
Load
Clicking this will send the patient and/or appointment records
to the EMR.
Use Load only to perform an initial “load” of patient and/or
appointment data into a new EMR, one that has no patient or
appointment records in it. This initial load is one time only.
When you start the service, patient and appointment records
will be updated behind the scenes.
Note: when you click Load, MPIC will clear the HL7trigger
table.
Close
Use this to close the Initialize Data screen. Your changes will
be saved.
2. Select the connection you want to initialize data for in the Connection Name field.
3. Select the check boxes for the options in the Create Master Xfire Load Files section.
4. Click the Synch button. An hourglass will appear showing the progress of the sync. When the
sync is complete, the Last Synch time fields will be updated.
This will send the types of data you selected to the EMR. Records that do not exist in the EMR
will be added. Those that exist will be updated during the synchronization.
You must sync providers before loading patients.
5. If the EMR is new and there are no patient or appointment records, select any filters you want
to use when the initial transfer of patient and/or appointment data takes place.
6. Select either Patients or Patients and Appointments.
7. Click the Load button. The Send All Records screen appears, showing you the progress in
transferring patients and/or appointments.
When the process is complete, all patients and/or appointments will be sent to the EMR.
Depending on the number of patients and appointments, as well as your filter selections, this
transmission could take some time. The Last Load Time will be updated on the Initialize Data
screen.
Clicking View Log will open the log. For more information, see “Viewing logs” on page 32.
8. Close the Initialize Data screen.
9. Double-click the MPIC icon on the desktop. The MPIC Control Panel appears.
10. Click Start Services. Now, MPIC will continually monitor changes in patient information and
appointments and transmit these changes between applications behind the scenes.
February 2014
Installation and User’s Guide
2.1
29
Adding another connection
Chapter 3 - Using the MPIC Control Panel
Adding another connection
You can have multiple connections for MPIC, but only one connection per practice. Once you have
created your first connection, follow the steps to create additional connections.
1. Follow the steps for “Configuring Mirth for a Remote Server” on page 75 to set up a user
account on the remote server. Since Mirth and MPIC are not installed on the same computer
as the server for Practice Partner, you must create this account so that Mirth can access the
server.
2. On the MPIC Control Panel, click the Settings button. The Settings screen appears.
3. Click the New button. The Create New Connection screen appears.
4. Enter a Connection Name.
5. Click the OK button.
6. Click the EMR Settings button. The Folders screen appears.
7. Be sure to enter unique paths each field. You must enter the UNC path to the server on these
fields (for example: \\abcdefg\program files\medisoft\pm).
8. Click the OK button.
9. Complete the fields on the Settings screen, making sure to select the correct Connection Type
and the correct Practice Name.
10. Click the OK button.
11. On the MPIC Control Panel, click the Initialize Data button. The Initialize Data screen
appears.
12. Select the connection and select the check boxes for the types of data you want to synch.
13. Click the Synch button. The Enter Remote Login Information screen appears.
Figure 15. Enter Remote Login Information screen
30
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Adding another connection
14. Enter the information for the remote server.
15. Click the OK button. The data is synched.
16. Select either Patients or Patients and Appointments.
17. Click the Load button. The Send All Records screen appears, showing you the progress in
transferring patients and/or appointments.
When the process is complete, all patients and/or appointments will be sent to the EMR.
Depending on the number of patients and appointments, as well as your filter selections, this
transmission could take some time. The Last Load Time will be updated on the Initialize Data
screen.
Clicking View Log will open the log. For more information, see “Viewing logs” on page 32.
18. Close the Initialize Data screen.
19. Double-click the MPIC icon on the desktop. The MPIC Control Panel appears.
20. Click Start Services. Now, MPIC will continually monitor changes in patient information and
appointments and transmit these changes between applications behind the scenes.
February 2014
Installation and User’s Guide
2.1
31
Viewing logs
Chapter 3 - Using the MPIC Control Panel
Viewing logs
MPIC creates logs as it processes transactions. These logs show you what data has transferred
and what errors, if any, have occurred.
To view logs:
1. On the MPIC Control Panel, click the View Logs button. The View Logs screen appears.
Figure 16. View Logs screen
This screen shows you the available logs and their location on the disk.
2. Select the Connection Name that you want to see logs for.
3. Click the View or List button next to each log to view the log.
32
Log
Description
Synch Logs
Use this to see the folder where this log is stored. For more
information, see “Synch logs” on page 33.
Mirth Logs
Use this to see the folder where this log is stored. For more
information, see “Mirth Log” on page 35.
DemSch Logs
Use this to see the folder where this log is stored.
XFire Logs
Use this to see the folder where this log is stored. For more
information, see “EMR Logs” on page 35.
View
Use this to open the log in Notepad.
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Synch logs
Log
Description
List
Use this to see the log in the list section of the screen below
the XFire Logs field.
Synch logs
The Synch logs show you the activity of the McKesson Practice Interface Service itself, that is, the
service that controls the real-time transfer of all data between the practice management
application and the EMR. It will show you the date and time of the transfer, the practice, and what
data was transferred. Both real-time transfers of data, such as changes to appointments and
patient demographics, and one-time transfers of data, such as sending providers or initial loads of
patient data will appear in the Synch logs.
Figure 17 shows the transmission of a change to a patient record. The log shows the date, the
number of triggers, the Event Type (A08, the change of patient information), and the patient ID. For
more information on Event Types, see “Transmitted Information” on page 55).
Figure 17. Synch log with trigger highlighted
This size of this log is limited to 10MB. When the file reaches this size, it will be renamed and a
second synch log will be created automatically. There is a limit of four synch logs. When a fifth one
is created, the oldest one will be deleted and the others will be renamed.
Modifying the Synch Log
You can control which types of information appear in the Synch log by editing the file
MPICService.exe,config. This file is located at C:\Program Files\Mckesson\Mckesson Practice
Interface Center on your hard drive.
February 2014
Installation and User’s Guide
2.1
33
Modifying the Synch Log
Chapter 3 - Using the MPIC Control Panel
When you open the file in Notepad, it looks like this:
Figure 18. MPICService.exe.config
Scroll to the section highlighted in Figure 18 and you have three options you can edit.
Option
Description
HL7TriggerBatchSize
This option controls how many triggers are in a batch for
transmission. Setting this value allows MPIC to process
batches of triggers more quickly.
HL7TriggerKeepRecordsDays
This option controls how many days that triggers will be kept
in the table. Limiting the number of days will keep the trigger
table smaller.
LoggingLevel
This option controls which items appear in the Synch log.
Choices are:
• Error: Entering Error will limit the items in the Synch log
to errors.
• Info: Entering Info will limit the items in the Synch log to
errors and informational entries (processing
messages).
• Debug: Entering Debug will include errors, informational
messages, and debugging messages.
If you make any changes to this file, be sure to save them. In addition, you must restart the service
from the MPIC Control Panel after changing this file.
34
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Mirth Log
Mirth Log
The Mirth log shows you activity in Mirth Connect, such as a successful connection to the
database and number of records transferred. Real-time transfers of appointments, changes to
patient demographics, and transfers of transactions all use Mirth Connect and appear in the Mirth
log. One-time transfers of data from the Initialize Data screen do NOT use the Mirth log. Figure 19
shows the successful start of Mirth Connect.
Figure 19. Mirth log
EMR Logs
These logs show you data that was transmitted to and from the EMR. You can see successful
transmissions as well as errors that you can use to correct information in records.
February 2014
Installation and User’s Guide
2.1
35
DemSch Logs
Chapter 3 - Using the MPIC Control Panel
DemSch Logs
Clicking the View button for DemSch Logs will display a list of logs in the View Logs screen:
Figure 20. View Logs screen with DemSch Logs
In turn, clicking one of the event logs will open the log in Notepad. This log will show you
information that is being transmitted from the practice management application to the EMR. This
includes real-time transfers of data, such as appointments and changes to patient demographics.
36
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
XFire Logs
Figure 21 shows an example of the DemSch log with a message of a real-time transfer of data. It
shows the date of the transfer, the practice, the type of transfer, and patient demographics.
Figure 21. DemSch log
XFire Logs
Clicking the View button for XFire Logs will display a list of logs in the View Logs screen:
Figure 22. View Logs screen with XFire Logs
February 2014
Installation and User’s Guide
2.1
37
Flow of information
Chapter 3 - Using the MPIC Control Panel
In turn, clicking one of the event logs will open the log in Notepad. The XFire log shows you data
that is sent to the EMR using the Initialize Data screen, such as sending Providers and Facilities, or
loading patients and/or appointments. Any errors in the transmission of this data will appear in the
XFire log.
Be sure to enter valid paths in these fields or you will receive an error.
Figure 23 shows an example of the processing of a patient record. The log shows the patient
name, ID, and insurance carriers.
Figure 23. XFire log
Flow of information
Real-time transfers
Data that is transmitted in real-time, such as changes to patient demographics, appointments, and
transactions will flow between applications in this order:
1. McKesson Practice Interface Center Service
2. Mirth Connect
3. DemSch Interface
Real-time transfers of data will flow in both directions: demographics and scheduling information
will flow from the practice management system to the EMR and billcode information will flow from
the EMR to the practice management system.
One-Time transfers
Data that is transmitted as part of a one-time transfer, such as sending providers and facilities, will
flow between applications in this order:
38
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
Log summary
1. McKesson Practice Interface Center Service
2. Crossfire (XFire)
One-time data transfer is one way only: from the practice management system to the EMR.
Log summary
Each log corresponds to the activity of one of the applications used in real-time or one-time
transfer of data:
Application
Associated Log
Time of transfer
McKesson Practice Interface Center Service
Synch
Real-time/one-time
Mirth Connect
Mirth
Real-time
DemSch Interface
DemSch
Real-time
Crossfire (XFire)
XFire
One-time
If there is a problem with data transfer, you can check the logs in the order of the flow of information
and find where the problem occurred. Each log will show you errors in transmission.
For more help troubleshooting issues with MPIC, see
https://mckwiki.mckesson.com/pps‐var‐central/mpic_troubleshooting_guide.
February 2014
Installation and User’s Guide
2.1
39
Create New Connection screen
Chapter 3 - Using the MPIC Control Panel
Create New Connection screen
Use this screen to enter a Connection Name for a new connection.
Figure 24. Create New Connection screen
Folders screen
Use the Folders screen to specify where HL7 messages will be stored when you select a Lytec MD
or Medisoft Clinical connection type. The folders will be set up automatically based on the interface
you select. Once the data in these folders has been processed, it will be deleted.
You will see this screen when you click the EMR Settings button from the Settings screen and you
are configuring a Lytec MD or Medisoft Clinical connection.
For all connections to remote servers, you must enter the UNC path to the server folder. You
cannot use a mapped network drive. If you click the Browse button and select a mapped network
drive, it will be changed automatically to the correct UNC path.
Figure 25. Folders screen
40
Folder
Description
Inbound Folder
Use this to select the folder for the inbound HL7 file. This
folder will hold the files that come from the EMR to the
practice management system.
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
RelayHealth Settings screen
Folder
Description
Outbound Folder
Use this to select the folder where the outbound HL7 file will
be deposited. This folder will hold the files that come from
the practice management system to the EMR.
Sync Folder
Use this to select the folder where the updated library files
(updates to providers, facilities, procedure codes, and
diagnosis codes) will be placed for synchronization.
EMR Folder (PPart)
Use this to select the folder where Practice Partner is
installed.
RelayHealth Settings screen
Use the RelayHealth Settings screen to enter information that you received from RelayHealth. This
information will enable MPIC to send your patient demographic information to the correct practice
at RelayHealth. Also, specify the folder where data will be stored.
You will see this screen when you click the EMR Settings button from the Settings screen and you
are configuring a Relay Health connection. You will also see it when configuring a Lytec MD or
Medisoft Clinical connection and you click the Relay Health Settings button.
Figure 26. RelayHealth Settings screen
Folder
Description
Practice Id
Use this field to enter the Practice ID you received from
RelayHealth. This is the Practice ID that RelayHealth has in
its database.
Partner Id
Use this field to enter the Partner ID you received from
RelayHealth. This value denotes the Sending Facility.
February 2014
Installation and User’s Guide
2.1
41
MPIC Database Settings screen
Chapter 3 - Using the MPIC Control Panel
Folder
Description
Relay Connector Folder
Use this field to specify the folder where demographic
information will be stored before it is sent to RelayHealth.
Data transfers will be placed as files in this folder. The
RelayConnector Configuration Utility will then send the
information in these files to RelayHealth. The files will then
be deleted.
You will need to know this path when you set up the
RelayConnector Configuration Utility. For more information,
see “Configure the Relay Connector Configuration Utility” on
page 51.
In addition, if you have more than one connection, you must
enter a UNC path in this field for all connections except the
first one you created.
Browse
Click this button to look for the folder you want demographic
information to be stored in.
Source Provider ID
Enter the ID of your provider from Medisoft or Lytec. Use
these fields for each of your providers. Enter a Source
Provider ID value and a RelayHealth value for as many
providers as you have set up in RelayHeatlh. The screen will
expand so you can enter more providers.
RelayHealth Provider
ID
Enter the corresponding ID for your provider in RelayHealth.
This field, coupled with the Source Provider IDs field,
enables MPIC to know which provider in Medisoft or Lytec to
match to which provider in RelayHealth.
RelayHealth will send you a list of your provider IDs when
you sign up.
Default
Select this button for the provider that will be your default
provider.
MPIC Database Settings screen
Use this screen to create a new SQL database for MPIC.
42
Installation and User’s Guide
2.1
February 2014
Chapter 3 - Using the MPIC Control Panel
MPIC Database Settings screen
Warning: creating a new MPIC database will cause MPIC to lose all existing settings and
configuration options and return it to its installation state.
Figure 27. MPIC Database Settings screen
Field
Description
Server Type
This field displays the type of server.
Server Name
Use this field to select the database. For Lytec users who want
to use the same database as Lytec, use the value in the Server
field on the Specify Default SQL Credentials screen. Medisoft
users will use the MPIC instance.
Database Name
This field displays the database name.
Login
Use this to enter the login name for the database.
Password
Use this to enter the password for the login.
Create Databases
Select this check box to display the login fields for the database
system administrator login information.
Select this option if you want to create a new MPIC Interop
database on the database you selected in the Server Name
field. You will need to do this if you are installing MPIC for the
first time.
Note: Creating a new database will result in the loss of all
existing configuration settings.
February 2014
Login
Enter the login for the system administrator.
Password
Enter the password for the system administrator.
Save
Click this button to save the settings.
Cancel
Click this button to cancel any changes to settings.
Installation and User’s Guide
2.1
43
Enter Remote Login Information screen
Chapter 3 - Using the MPIC Control Panel
For issues with troubleshooting, see the MPIC Troubleshooting Guide at https://
mckwiki.mckesson.com/pps-var-central/mpic_troubleshooting_guide.
Enter Remote Login Information screen
Use this screen to enter login credentials for XFire Demographics when MPIC is trying to start it on
a remote server.
Figure 28. Enter Remote Login Information screen
44
Field
Description
Domain
Enter the server name or IP address in the Domain field. The
user account you enter must have administrative rights on the
remote server.
User ID
Enter the ID of the user for the remote server.
Password
Enter the password of the user for the remote server.
Installation and User’s Guide
2.1
February 2014
Chapter 4 - RelayClinical eScript Connection
You can use MPIC to transmit patient demographic information from Medisoft or Lytec to
RelayHealth for ePrescribing purposes. This is a single direction transfer of data only and only
sends demographic information. No scheduling data is transferred. The MPIC connection uses the
RelayHealth Relay Connector to send data to RelayHealth. For more information on what
information is transferred, see “Medisoft or Lytec to RelayHealth” on page 69.
Sign up with RelayHealth
To begin the process of signing up a practice for the RelayHealth connection, visit Forms Central at
https://mckwiki.mckesson.com/pps-var-central/forms%20central%20vars. Here, you will find the
forms you need to enroll a practice. Send these forms to relayhealthagreements@mckesson.com
when your customer has completed them.
Download and install the Relay Connector
Configuration Utility
Install the Relay Connector Configuration Utility on your server computer. This must be the same
computer that MPIC is installed on.
To download and install Relay Connector, use the Installation Guide for Relay Connector. You can
find this guide at https://mckwiki.mckesson.com/pps-var-central/forms%20central%20vars. Select
the link for Relay Connector Install Guide.
You can obtain the zipped file to install Relay Connector here: https://mckwiki.mckesson.com/ppsvar-central/forms%20central%20vars. Click the link for Relay Connector Setup Guide. You will
need to unzip the program file.
McKesson highly recommends that you use a static IP address for this connection.
February 2014
Installation and User’s Guide
2.1
45
Configure MPIC
Chapter 4 - RelayClinical eScript Connection
Configure MPIC
You can set up this connection either in conjunction with a connection to Medisoft Clinical or Lytec
MD or you can set it up as a stand alone connection. Use the table below to find the steps to set up
MPIC according to your need.
Stand alone
connection?
Follow these steps:
Yes
“Configuring MPIC for RelayHealth with Medisoft Clinical or
Lytec MD” on page 49
No
“Configuring MPIC while configuring Medisoft or Lytec” on
page 49
Configuring MPIC with RelayHealth as a stand alone connection
Use these steps if you want to use MPIC only to send data from Medisoft or Lytec to RelayHealth.
Creating the connection
Use these steps to create the connection.
1. Double-click the MPIC icon on the desktop. The MPIC Control Panel appears.
46
Installation and User’s Guide
2.1
February 2014
Chapter 4 - RelayClinical eScript Connection
Creating the connection
2. Click the Settings button. The Initialize Interface Settings screen appears.
Figure 29. Interface Settings screen
February 2014
Field/Button/Link
Description
Connection Name
Use this drop-down list to select a connection. Connection
Names are added when you click the New button and add a
new connection.
New
Click this button to open the Create New Connection screen
on which you can add a new connection. For more
information, see “Create New Connection screen” on page
40.
Installation and User’s Guide
2.1
47
Creating the connection
Chapter 4 - RelayClinical eScript Connection
Field/Button/Link
Description
Delete
Select this button to delete the existing connection and all
background information on the connection. You will receive a
warning prior to the deletion of the connection.
This button will be disabled if there is no existing connection.
Note: You must click the OK button on the Settings screen to
complete the deletion of the connection.
Connection Type
Select a connection type from the drop-down list. The list will
include all types currently available. Select either Lytec to
RelayHealth or Medisoft to RelayHealth.
The connection contains hard-coded information specifically
designed to enable the two applications to transmit data to
one another.
Server Name (Path)
Enter the path of the server that MPIC is installed on.
Database Name
Use this to enter the name of the database.
User ID
Enter the ID of the administrative user.
Password
Enter the Password of the administrative user.
Practice Name
Select the appropriate practice from the drop-down list.
Transmit Interval (303600 seconds)
Use these fields to specify the amount of time in between
transmissions of data. The default, recommended value is
120. The transmitting features use this option but the syncing
features do not.
EMR Settings
Click this button to open the RelayHealth Settings screen, on
which you can enter data that RelayHealth sent you for your
connection.
Transmit patient
demographics
Select this check box if you want to transmit demographic
information for new patients or changed information from the
practice management system to RelayHealth.
Save
Use this to save changes to the Settings screen.
Delete
Select this button to delete the existing connection and all
background information on the connection. You will receive a
warning prior to the deletion of the connection.
This button will be disabled if there is no existing connection.
Cancel
Use this to cancel any changes made to the Settings screen.
3. Click the New button. The Create New Connection screen appears.
4. Enter a Connection Name.
5. Click the OK button.
6. On the Settings screen, select a connection type option from the drop-down menu. The
interface contains various default settings used for the starting point for a connection. These
48
Installation and User’s Guide
2.1
February 2014
Chapter 4 - RelayClinical eScript Connection
Configuring MPIC for RelayHealth with Medisoft Clinical or Lytec
settings help establish settings for one or more connections. When you select the interface
many of the fields on this screen will be filled automatically.
7. Complete the other fields on this screen as necessary.
8. Click the EMR Settings button. The RelayHealth Settings screen appears.
9. Complete the fields on this screen and click the Save button. For more information, see
“RelayHealth Settings screen” on page 41. Make sure you enter the correct Source Provider
IDs and RelayHealth Provider IDs for each of your providers.You can find your provider IDs in
Medisoft or Lytec, and RelayHealth will provide your Relay Health Provider IDs when you sign
up.
10. On the Settings screen, select the Transmit Patient Demographics check box.
11. Click the OK button.
12. Go to “Configure the Relay Connector Configuration Utility” on page 51.
Configuring MPIC for RelayHealth with Medisoft Clinical or Lytec
MD
Use the table below to determine which configuration steps to use.
Have you already configured MPIC for
Medisoft or Lytec?
Follow these steps:
No
“Configuring MPIC while configuring Medisoft or
Lytec” on page 49.
Yes
“Configuring MPIC after configuring Medisoft or
Lytec” on page 49.
Configuring MPIC while configuring Medisoft or Lytec
If you have all of the information at hand to set up your connection to RelayHealth at the same time
that you want to set up your connection with Medisoft or Lytec, simply follow the normal set up
procedure. See “Configuring a connection” on page 21. Be sure to perform the steps provided for
the RelayHealth connection.
Configuring MPIC after configuring Medisoft or Lytec
Configuring the Settings screen
If you have already set up your connection for Medisoft or Lytec, follow these steps to set up the
connection for RelayHealth.
1. Double-click the MPIC icon on the desktop. The MPIC Control Panel appears.
2. Click the Stop Service button.
3. Click the Settings button. The Settings screen appears.
February 2014
Installation and User’s Guide
2.1
49
Configuring MPIC after configuring Medisoft or Lytec
Chapter 4 - RelayClinical eScript Connection
4. Select the Transmit demographics to RelayHealth check box. The RelayHealth Settings button
appears.
Figure 30. Settings screen
5. Click the RelayHealth Settings button. The RelayHealth Settings screen appears. For more
information on this screen, see “RelayHealth Settings screen” on page 41.
6. Enter the Practice ID and Partner ID information you obtained from RelayHealth.
7. Select a folder for the data. Take note of the path for this folder because you will need it when
you configure the Relay Connector Configuration Utility.
8. Enter the provider ID values.
9. Click the Save button.
10. Leave all of the remaining options on the Settings screen as they are.
11. Click the Save button on the Settings screen.
50
Installation and User’s Guide
2.1
February 2014
Chapter 4 - RelayClinical eScript Connection
Configure the Relay Connector Configuration Utility
Configure the Relay Connector Configuration
Utility
Once the connection in MPIC is created, configure RelayHealth using the Relay Connector
Configuration Utility.
1. Launch the Relay Connector Configuration Utility.
Figure 31. Relay Connector Configuration Utility
2. On the File menu, click New Configuration.
February 2014
Installation and User’s Guide
2.1
51
Configure the Relay Connector Configuration Utility
Chapter 4 - RelayClinical eScript Connection
3. Click the Upload Messages tab.
Figure 32. RelayConnector Configuration Utility - Upload Messages tab
4. Right-click Message Types in the Message Routing section of the screen and click New.
5. Enter a name for the Message Type.
6. In the Route Messages From section, select File.
Figure 33. RelayConnector Configuration Utility
52
Installation and User’s Guide
2.1
February 2014
Chapter 4 - RelayClinical eScript Connection
Start the MPIC service
7. Enter or browse for the same path that you entered in the Folder field of the RelayHealth
Settings screen in MPIC.
8. Click the Save icon.
Start the MPIC service
1. On the computer desktop, double-click the MPIC - McKesson Practice Interface Center icon.
The MPIC Control Panel appears.
2. Click the Start Service button. If MPIC had been running before you added the RelayHealth
connection, click the Restart Service button.
February 2014
Installation and User’s Guide
2.1
53
Start the MPIC service
54
Chapter 4 - RelayClinical eScript Connection
Installation and User’s Guide
2.1
February 2014
Appendix A - Transmitted Information
In this appendix are lists of the data that is transferred for the different Connection Types in MPIC.
In this chapter
Topic
See page
Medisoft to Practice Partner
55
Lytec to Practice Partner
62
Medisoft or Lytec to RelayHealth
69
Medisoft to Practice Partner
Message description 
Message Type
Description
ADT A04
An ADT^A04 messages is created in response to a new patient event within
the practice management System.
ADT A08
An ADT^A08 message is created in response to an update of patient
information event within the practice management System.
ADT A40
An ADT^A40 message is not supported in Medisoft or Medisoft Clinical.
Exported segments
The detail for each segment follows this table.
Segment
Description
MSH
Message Header
EVN
Event Type
PID
Patient Identification
PV1
Patient Visit
IN1
Insurance (up to 3) (Optional)
February 2014
Installation and User’s Guide
2.1
55
MSH segment
Appendix A - Transmitted Information
MSH segment
Field
Included
Notes
1
X
“^~\&”
2
X
Sending Application – Use Practice ID
3
X
Sending Facility.
4
X
Receiving Application
5
X
Receiving Facility
6
X
Date/Time of Message
7
X
Security
8
X
Message Type
EVN segment
Field
Included
Notes
1
X
Event Code
2
X
Recorded Date Time
3
4
Date Time of Planned Event
X
Event Reason Code
5
Operator ID
6
Date Time that Event Occurred
PID segment
Field
Included
Notes
1
X
Set ID (always 1)
2
X
Patient ID
3
X
Patient Identifier List
4
X
Alternate Patient ID
5
X
Patient Name
6
7
X
Date Time of Birth
8
X
Sex
9
Patient Alias
10
Race
11
12
56
Mother’s Maiden Name
X
Patient Address
County Code
Installation and User’s Guide
2.1
February 2014
Appendix A - Transmitted Information
PID segment
13
X
Home phone number ^ Cell Phone Number^<Spacer>^Email Address
14
X
Business phone number
15
16
Primary Language
X
17
Marital Status (Concept Only)
Religion
18
X
Patient account Number (Patient ID is used. Duplicate of field 2)
19
X
Patient SSN Number
20
Patient Drivers License Number
21
Mother’s Identifier
22
Ethnic Group
23
Birth Place
24
Multiple Birth Indicator
25
Birth Order
26
Citizenship
27
Veterans Military Status
28
Nationality
29
30
February 2014
X
Patient Death Date Time (Concept Only)
Patient Death Indicator
Installation and User’s Guide
2.1
57
PV1 segment
Appendix A - Transmitted Information
PV1 segment
Field
Included
Notes
1
X
Set ID Always 1
2
X
Patient Class – Use “O”
3
Assigned Patient Location
4
Admission Type
5
Pre-admit Number
6
Prior Patient Location
7
X
Attending Doctor
8
X
Referring Doctor
9
Consulting Doctor
10
Hospital Service
11
Temporary Location
12
Pre-admit Test Indicator
13
Re-admission Indicator
14
Admit Source
15
Ambulatory Status
16
VIP Indicator
17
Admitting Doctor
18
Patient Type
19
58
X
Visit Number (Case number if available)
20
Financial Class
21
Charge Price Indicator
22
Courtesy Code
23
Credit Rating
24
Contract Code
25
Contract Effective Dat - Blank e
26
Contract Amount
27
Contract Period
28
Interest Code
29
Transfer to Bad Debt Code
30
Transfer to Bad Debt Date
31
Bad Debt Agency Code
32
Bad Debt Transfer Amount
Installation and User’s Guide
2.1
February 2014
Appendix A - Transmitted Information
IN1 segment
33
Bad Debt Recovery Amount
34
Delete Account Indicator
35
Delete Account Date
36
Discharge Disposition
37
Discharged to Location
38
Diet Type
39
Servicing Facility
40
Bed Status
41
Account Status
42
Pending Location
43
Prior Temporary Location
44
Admit Date/Time
45
Discharge Date/Time
46
Current Patient Balance
47
Total Charges
48
Total Adjustments
49
Total Payments
IN1 segment
Field
Included
Notes
1
X
Set ID - IN1 – Use “1” for Insurance carrier # 1, “2” for carrier 2 etc.
“1” represents the primary insurance carrier.
2
X
Insurance Plan ID – This is the Policy ID.
3
X
Insurance Company ID
4
X
Insurance Company Name
5
X
Insurance Company Address
6
X
Insurance Co Contact Person
7
X
Insurance Co Phone Number – Use blank string if only phone
formatting found.
8
X
Group Number
9
X
Group Name
10
X
Insured’s Group Emp ID (Policy Number)
11
Insured’s Group Emp Name
12
X
Plan Effective Date
13
X
Plan Expiration Date
February 2014
Installation and User’s Guide
2.1
59
IN1 segment
14
Authorization Information
15
Plan Type
16
X
Name Of Insured
17
X
Insured’s Relationship To Patient
18
X
Insured’s Date Of Birth
19
X
Insured’s Address
20
Assignment Of Benefits
21
Coordination Of Benefits
22
Co-ord Of Ben. Priority
23
Notice Of Admission Flag
24
Notice Of Admission Date
25
Report Of Eligibility Flag
26
Report Of Eligibility Date
27
Release Information Code
28
Pre-Admit Cert (PAC)
29
Verification Date/Time
30
Verification By
31
Type Of Agreement Code
32
Billing Status
33
Lifetime Reserve Days
34
Delay Before L.R. Day
35
Company Plan Code
36
X
Policy Number
37
Policy Deductible
38
Policy Limit - Amount
39
Policy Limit - Days
40
Room Rate - Semi-Private
41
Room Rate - Private
42
Insured’s Employment Status
43
60
Appendix A - Transmitted Information
X
Insured’s Sex
44
Insured’s Employer’s Address
45
Verification Status
46
Prior Insurance Plan ID
47
Coverage Type
Installation and User’s Guide
2.1
February 2014
Appendix A - Transmitted Information
IN1 segment
48
Handicap - Blank
49
Insured’s ID Number
February 2014
Installation and User’s Guide
2.1
61
Lytec to Practice Partner
Appendix A - Transmitted Information
Lytec to Practice Partner
Message description
Message Type
Description
ADT A04
An ADT^A04 messages is created in response to a new patient event within
the practice management System.
ADT A08
An ADT^A08 message is created in response to an update of patient
information event within the practice management System.
ADT A40
An ADT^A40 message is not supported in Lytec or Lytec MD.
Exported segments
The detail for each segment follows this table.
62
Segment
Description
MSH
Message Header
EVN
Event Type
PID
Patient Identification
PV1
Patient Visit
IN1
Insurance (up to 3) (Optional)
Installation and User’s Guide
2.1
February 2014
Appendix A - Transmitted Information
MSH segment
MSH segment
Field
Included
Notes
1
X
“^~\&”
2
X
Sending Application – Use Practice ID
3
X
Sending Facility.
4
X
Receiving Application
5
X
Receiving Facility
6
X
DateTime of Message
7
X
Security
8
X
Message Type
EVN segment
Field
Included
Notes
1
X
Event Code
2
X
Recorded Date Time
3
4
Date Time of Planned Event
X
Event Reason Code
5
Operator ID
6
Date Time that Event Occurred

February 2014
Installation and User’s Guide
2.1
63
EVN segment PID segment
Appendix A - Transmitted Information

PID segment
Field
Included
Notes
1
X
Set ID (always 1)
2
X
Patient ID
3
X
Patient Identifier List
4
X
Alternate Patient ID
5
X
Patient Name
6
Mother’s Maiden Name
7
X
Date Time of Birth
8
X
Sex
9
Patient Alias
10
Race
11
X
12
County Code
13
X
Home phone number ^ Cell Phone Number^<Spacer>^Email Address
14
X
Business phone number
15
16
Primary Language
X
17
Marital Status (Concept Only)
Religion
18
X
Patient account Number (Patient ID is used. Duplicate of field 2)
19
X
Patient SSN Number
20
Patient Drivers License Number
21
Mother’s Identifier
22
Ethnic Group
23
Birth Place
24
Multiple Birth Indicator
25
Birth Order
26
Citizenship
27
Veterans Military Status
28
Nationality
29
30
64
Patient Address
X
Patient Death Date Time (Concept Only)
Patient Death Indicator
Installation and User’s Guide
2.1
February 2014
Appendix A - Transmitted Information
PV1 segment
PV1 segment
Field
Included
Notes
1
X
Set ID Always 1
2
X
Patient Class – Use “O”
3
Assigned Patient Location
4
Admission Type
5
Pre-admit Number
6
Prior Patient Location
7
X
Attending Doctor
8
X
Referring Doctor
9
Consulting Doctor
10
Hospital Service
11
Temporary Location
12
Pre-admit Test Indicator
13
Re-admission Indicator
14
Admit Source
15
Ambulatory Status
16
VIP Indicator
17
Admitting Doctor
18
Patient Type
19
X
Visit Number (Case number if available)
20
Financial Class
21
Charge Price Indicator
22
Courtesy Code
23
Credit Rating
24
Contract Code
25
Contract Effective Date - Blank e
26
Contract Amount
27
Contract Period
28
Interest Code
29
Transfer to Bad Debt Code
30
Transfer to Bad Debt Date
31
Bad Debt Agency Code
32
Bad Debt Transfer Amount
February 2014
Installation and User’s Guide
2.1
65
PV1 segment
Appendix A - Transmitted Information
33
Bad Debt Recovery Amount
34
Delete Account Indicator
35
Delete Account Date
36
Discharge Disposition
37
Discharged to Location
38
Diet Type
39
Servicing Facility
40
Bed Status
41
Account Status
42
Pending Location
43
Prior Temporary Location
44
Admit Date/Time
45
Discharge Date/Time
46
Current Patient Balance
47
Total Charges
48
Total Adjustments
49
Total Payments

66
Installation and User’s Guide
2.1
February 2014
Appendix A - Transmitted Information
IN1 segment
IN1 segment
Field
Included
Notes
1
X
Set ID - IN1 – Use “1” for Insurance carrier # 1, “2” for carrier 2 etc. “1”
represents the primary insurance carrier.
2
X
Insurance Plan ID – This is the Policy ID.
3
X
Insurance Company ID
4
X
Insurance Company Name
5
X
Insurance Company Address
6
X
Insurance Co Contact Person
7
X
Insurance Co Phone Number – Use blank string if only phone formatting
found.
8
X
Group Number
9
X
Group Name
10
X
Insured’s Group Emp ID (Policy Number)
11
Insured’s Group Emp Name
12
X
Plan Effective Date
13
X
Plan Expiration Date
14
Authorization Information
15
Plan Type
16
X
Name Of Insured
17
X
Insured’s Relationship To Patient
18
X
Insured’s Date Of Birth
19
X
Insured’s Address
20
Assignment Of Benefits
21
Coordination Of Benefits
22
Coord Of Ben. Priority
23
Notice Of Admission Flag
24
Notice Of Admission Date
25
Report Of Eligibility Flag
26
Report Of Eligibility Date
27
Release Information Code
28
Pre-Admit Cert (PAC)
29
Verification Date/Time
30
Verification By
31
Type Of Agreement Code
February 2014
Installation and User’s Guide
2.1
67
IN1 segment
68
Appendix A - Transmitted Information
32
Billing Status
33
Lifetime Reserve Days
Installation and User’s Guide
2.1
February 2014
Appendix A - Transmitted Information
Medisoft or Lytec to RelayHealth
Medisoft or Lytec to RelayHealth
PID segment
Field
Included
Notes
1
X
Set ID (always 1)
2
X
Patient ID
3
X
Patient Identifier List
4
X
Alternate Patient ID
5
X
Patient Name
6
Mother’s Maiden Name
7
X
Date Time of Birth
8
X
Sex
9
Patient Alias
10
Race
11
X
12
Patient Address
County Code
13
X
Home phone number ^ Cell Phone Number^<Spacer>^Email Address
14
X
Business phone number
15
16
Primary Language
X
17
Marital Status (Concept Only)
Religion
18
X
Patient account Number (Patient ID is used. Duplicate of field 2)
19
X
Patient SSN Number
20
Patient Drivers License Number
21
Mother’s Identifier
22
Ethnic Group
23
Birth Place
24
Multiple Birth Indicator
25
Birth Order
26
Citizenship
27
Veterans Military Status
28
Nationality
29
30
February 2014
X
Patient Death Date Time (Concept Only)
Patient Death Indicator
Installation and User’s Guide
2.1
69
PID segment
70
Appendix A - Transmitted Information
Installation and User’s Guide
2.1
February 2014
Appendix B - Automate Provider Mapping
Overview
Review this appendix to help determine if using automate provider mapping is appropriate for your
facility.
The automate provider mapping feature, when enabled, manages provider updates and replaces
the need to manually edit and update cross reference files, as well as enter providers in both the
practice management application and the EMR.
Methods of provider mappings
There are two methods for mapping providers between the practice management application and
the EMR:
• via manual provider entry in both systems and then updating the cross reference files to map
the providers between the systems, or
• via automate provider mapping controlled by the Automate Provider Mapping check box on the
Settings screen that manages the process.
You can take advantage of automatic provider mapping if you have a one-to-one relationship in
your current provider record mapping between the practice management application and your
EMR.
A one-to-one mapping relationship means that you have one provider ID for each provider record
in your practice management application mapping to one provider ID in your EMR. If your practice
is set up with one-to-one provider mapping, you can use the automatic provider mapping feature.
Provider mapping examples for Practice Partner
One-to-one mapping example
To check the Dem Sch cross reference file, 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:
MM471 | MM4
JM875 | JM8
WW934 | WW9
The first entry for each line is the Provider ID in the practice management system. The second
entry for each line is the Provider ID in Practice Partner.
February 2014
Installation and User’s Guide
2.1
71
Variation of a one-to-one mapping example
Appendix B - Automate Provider Mapping
Both items, when combined, create a mapping 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 practice management application match a single provider ID
in Practice Partner.
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 practice has three provider IDs (multiple provider records);
however, each of these provider IDs is mapped to a specific provider ID in Practice Partner (also
multiple provider records in Practice Partner).
Multiple mappings example
If the cross reference file looks 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 the practice management application for a single
provider and the IDs are mapped to one provider ID in Practice Partner.
Billing mappings
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 Practice Partner provider IDs appear first, followed by the practice management
provider IDs.
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:
C | White
B | Black
I | Indian/Alaska
A | Asian
E | Other
P | Pac Isle
72
Installation and User’s Guide
2.1
February 2014
Appendix B - Automate Provider Mapping
Using Automate Provider Mapping
D | Declined
For Ethnicity, create DemSch-Ethnicity.ref with the following values:
N | Non-Hispanic
H | Hispanic
D | Declined
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 Candidate for
between DemSch
automate provider
and Billing cross
mapping
reference files
Description
1 to 1
Yes
Do not modify the DemSch or Billing
cross reference files once you have
used automate provider mapping.
During the initial provider data
initialization process, the original cross
reference files for DemSch and Billing
are renamed as a precaution to the
following format: _Original.TXT.
1 to many
no
Do not use automate provider mapping
if multiple provider IDs exist and are
mapped to one provider ID in the EMR.
Using Automate Provider Mapping
To use this feature to manage your provider updates, follow the steps for configuring your
connection (see “Configuring a connection” on page 21), making sure to select the Automate
Provider Mapping check box on the Settings screen. When you perform the steps for initializing
data (see “Initializing data” on page 26) and send your providers, MPIC will map provider records in
the practice management system to those in the EMR.
Alternative to Automate Provider Mapping

If you are not using the automate provider mapping feature, you can still send updates to providers,
facilities, diagnosis codes, and procedure codes. To do so, follow the steps for initializing data (see
“Initializing data” on page 26). In this case, when you send providers, MPIC will not attempt to map
the new providers in the practice management application to providers that already exist in the
February 2014
Installation and User’s Guide
2.1
73
Alternative to Automate Provider Mapping
Appendix B - Automate Provider Mapping
EMR. It will create new records in the EMR for the new records in the practice management
application.
74
Installation and User’s Guide
2.1
February 2014
Appendix C - Configuring Mirth for a Remote
Server
For those who are using Medisoft Clinical or Lytec MD and are configuring a connection to a
remote server so that Mirth needs to access the EMR/RelayHealth folders over the network
(Medisoft Clinical/Lytec MD running on a different server than Mirth/MPIC), you must configure the
Mirth service to run under a user account that has access to the folders on the remote server.
To set this up:
1. From the computer where Mirth is running (normally the computer where MPIC is installed)
click Start, point to All Programs, point to Administrative Tools, and select Services.
2. Double-click Mirth Connect Service. The Mirth Connect Service Properties screen appears.
3. Click the Log On tab. The Log On tab appears.
4. Select the This account option.
5. Enter a user account and password that has access to the folders on the remote server. The
account can be a domain account or a local account on the remote server. To use a local
account, you must create an identical user ID and password on both the Mirth server and the
remote Medisoft Clinical/Lytec MD server where the folders reside.
Figure 34. Mirth Connect Service Properties (Local Computer) screen
February 2014
Installation and User’s Guide
2.1
75
Appendix C - Configuring Mirth for a Remote Server
6. Click the OK button.
7. Restart the Mirth Connect service.
76
Installation and User’s Guide
2.1
February 2014
Appendix D - Installing SQL Server Express
manually
If you are installing MPIC on a domain controller, you must install SQL Server Express manually
prior to installing MPIC. To install SQL manually, follow these steps.
1. To extract SQL Server Express from the MPIC download, download and install 7-Zip from http:/
/www.7-zip.org.
2. Launch 7-Zip File Manager.
3. Extract MPIC-Setup32.exe or MPIC-Setup64.exe, depending on whether you are installing on
a 32-bit or 64-bit computer.
4. Double-click SQLEXPR_x64_ENU.exe or SQLEXPR_x86_ENU.exe to start the installation of
SQL Server Express.
5. Select New installation or add features to an existing installation.
Figure 35. SQL Server Installation Center screen
6. Click the Next button. The License Terms screen appears.
November 2013
Installation and User’s Guide
2.0
77
Appendix D - Installing SQL Server Express manually
7. Select the I accept the license terms check box
8. Click the Next button. The Feature Selection screen appears.
9. Select all options except SQL Server Replication.
Figure 36. Feature Selection screen
10. Click the Next button. The Instance Configuration screen appears.
11. Select Named instance.
78
Installation and User’s Guide
2.0
November 2013
Appendix D - Installing SQL Server Express manually
12. Enter MPIC in the Named Instance and Instance ID fields.
Figure 37. Instance Configuration screen
13. If MPIC is listed in the Installed instances, you do not need to continue with this installation.
Click the Cancel button.
14. Click the Next button. The Server Configuration Screen appears.
November 2013
Installation and User’s Guide
2.0
79
Appendix D - Installing SQL Server Express manually
15. In the Account Name field, select the local or NT Authority System user.
Figure 38. Server Configuration screen
16. Change Local to Automatic.
17. Click the Next button. The Database Engine Configuration screen appears.
18. Select Mixed Mode (SQL Server authentication and Windows Authentication).
19. Enter a password in the Enter password field.
20. Enter the same password in the Confirm password field.
80
Installation and User’s Guide
2.0
November 2013
Appendix D - Installing SQL Server Express manually
21. Click the Add Current User button.
Figure 39. Database Engine Configuration screen
22. Data Directories Tab – Change Data root directory to what you desire.
23. Click the Next button. The Error Reporting screen appears.
24. Click the Next button. Allow the installation to complete the installation. This will take some
minutes. The Complete screen appears.
25. Click the Close button.
26. Close any other open SQL Server screens. The setup process continues.
27. When the installation is complete, the Setup Successful screen appears.
28. Click the Close button.
29. Once SQL Server is installed, MPIC can be installed successfully. Go to “Installing McKesson
Practice Interface Center” on page 7.
November 2013
Installation and User’s Guide
2.0
81
Appendix D - Installing SQL Server Express manually
82
Installation and User’s Guide
2.0
November 2013
Glossary
This section defines terms used in the Installation and User’s Guide.
Automate Provider Mapping
This feature allows for automatic mapping of providers in the practice management application to
those in the EMR, so there is no need to manually update cross reference files.
EMR
Electronic Medical Record. This is the application that a physician’s office uses to record the results
of treating patients. It may include encounter notes, allergies listed, medications prescribed, and so
on.
HL7
Health Level 7 is the standard format for transmitting medical data electronically.
Interface
An interface is the connection that is created on the Settings page. It is the collection of settings
that controls what data is transmitted between the two applications (practice management system
and EMR) that were specified when it was selected.
Launch
In McKesson Practice Interface Center this means to start an application.
Mirth Connect
This is an application that is installed with McKesson Practice Interface Center that controls and
manages the data that is transmitted between applications.
MPIC Service
The MPIC service is the application that runs in the background on your server and transmits data
between the two applications (practice management system and EMR) that were specified when
the interface was selected.
February 2014
Installation and User’s Guide
2.1
83
Glossary
84
Installation and User’s Guide
2.1
February 2014
Index
Index
.NET Framework 3
Medisoft 59
Initialize Data screen 26
installing 45
McKesson Practice Interface Center 7
pre-requisites 2
Relay Connector Configuration Utility 45
interface
defined 23, 48
Interface Settings screen 22, 47
A
administrator rights 2
Automate Provider Mapping
using 73
automatic provider mapping overview 71
B
before you begin installing 2
J
C
Java Runtime 6.0
defined 4
configuring
Interface Settings screen for RelayHealth 49
Relay Connector Configuration Utility 51
connections
multiple 6, 30
Control Panel 17
D
DemSch logs 36
E
EMR Logs 35
enabling
HL7 triggers 15
EVN segment
Lytec 63
Medisoft 56
exported segments
Lytec 62
Medisoft 55
F
Folders screen 40
H
hardware requirements 2
HL7 triggers
enabling 15
I
IN1 segment
Lytec 67
February 2014
L
logs
DemSch 36
EMR 35
Mirth 35
summary 39
Synch 33
Lytec to Practice Partner
transmitted information 62
M
McKesson Practice Interface Center
installing 7
overview 1
McKesson Practice Interface Center Service
defined 4
Medisoft to Practice Partner
transmitted information 55
message descriptions
Lytec 62
Medisoft 55
methods of provider mappings 71
Mirth
configuring for remote server 75
Mirth Connect
defined 4
Mirth Log 35
MPIC
configuring for RelayHealth 46
MPIC Administration Database
defined 4
Installation and User’s Guide
2.1
85
Index
MPIC Control Panel 17
MSH segment
Lytec 63
Medisoft 56
transmitted information
Lytec to Practice Partner 62
troubleshooting 39
O
overview
McKesson Practice Interface Center 1
P
PID segment
Lytec 64
Medisoft 56
provider mapping
examples 71
provider mappings
methods 71
PV1 segment
Lytec 65
Medisoft 58
R
Relay Connector Configuration Utility 45
configuring 51
RelayHealth
configuring MPIC for 46
signing up 45
remote server
configuring Mirth 75
requirements
hardware 2
software 2
S
screens
Folders 40
Initialize Data 26
Interface Settings 22, 47
setting
transmit interval 23, 48
signing up
RelayHealth 45
software requirements 2
SQL Express 2008
defined 4, 8
summary of logs 39
Synch logs 33
T
transmit interval
setting 23, 48
86
Installation and User’s Guide
2.1
February 2014
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising