Caution: Federal law (USA) restricts this device to sale by or on
the order of a physician (or a properly licensed practitioner)
Trademarks in this manual
The following list includes trademarks or registered trademarks of Medtronic in the United States and possibly in
other countries. All other trademarks are the property of their respective owners.
Medtronic, Paceart Optima, CareLink, Mainspring, Medtronic CareLink
Contents
Mainspring Data Express............................................................................................................5
Mainspring Data Express Software Prerequisites................................................................8
Installing Mainspring Data Express........................................................................................11
Mainspring Data Express Version 4.0 to 5.0..............................................................196
Connectivity Guide | Mainspring Data Express | 5
Mainspring Data Express
Mainspring – like the inner workings of a clock – it is the power source that facilitates the movement of cardiac
data within your clinic, and between various departments within your organization.
Mainspring Data Express is a comprehensive solution for your cardiac patients, bringing together device and
patient data from the Paceart System, the Medtronic CareLink Network, the CareLink Programmer, the Boston
Scientific LATITUDE® Patient Management system, the St. Jude Medical Merlin.net® Patient Care Network,
your EHR System, and local network.
In order to simplify the process of connecting and sharing demographic, scheduling, and device data between
Medtronic applications and electronic health record systems (EHRs), Medtronic has developed Mainspring
Data Express.This software application serves as the primary tool to move and share data for device patients.
Mainspring Data Express helps to streamline the implementation and on-going maintenance of data movement
between applications.
This manual explains the process for installing the Mainspring Data Express software and configuring the
features.
Explanation of symbols
Symbol definitionSymbol
Consult instructions for use
For US audiences only
Authorized Representative in the European
Community
Manufacturer
Lot number
Re-order number
Date of Manufacture
Do not dispose of this product in the unsorted
municipal waste stream. Dispose of this product
according to local regulations. See
http://recycling.medtronic.com for instructions on
proper disposal of this product.
Temperature Limitation
Humidity Limitation
6 | Connectivity Guide | Mainspring Data Express
Indications
Mainspring Data Express is an optional component of the Medtronic CareLink Network and Paceart Optima
System.
Mainspring Data Express can be used to perform the following tasks:
•Save CareLink reports to a network location.
•Exchange scheduling data between CareLink and Paceart.
•Bring in demographic and scheduling information from electronic medical record systems or practice
management systems via HL7.
•Export device data to electronic medical record systems via HL7.
•Import device data via SessionSync
•Import device data to Paceart via HL7 (for properly formatted IDCO messages)
•Import device data to Paceart from Merlin.Net integration
•Import device data to Paceart from Latitude integration
Symbol definitionSymbol
Software
For more information on the Medtronic CareLink Network, refer to the CareLink Network Online Help.
For more information on the Paceart Optima System, refer to the Paceart Optima System Software User
Manual or the Paceart Optima System Online Help.
Precautions
Mainspring Data Express USBs must be stored within the following conditions:
Storage Environment
-20°C (-4°F) to +45°C (113°F)Temperature
20% to 90%Relative Humidity
Mainspring Data Express USBs must be operating in an environment within the following conditions:
Operating Environment
0°C (32°F) to +35°C (95°F)Temperature
20% to 90%Relative Humidity
Call customer service or your biomedical department for service and repairs.
Contraindications
No known contraindications.
Connectivity Guide | Mainspring Data Express | 7
Mainspring Data Express Authorized Users
Medtronic representatives provide the Mainspring Data Express orientation and training materials at the time
of the installation. Users should be familiar with the Mainspring Data Express documents before using
Mainspring Data Express.
Technical Support
In the US and Canada, call 1-800-929-4043 and select option 3. For all other countries contact your local
Medtronic representative.
8 | Connectivity Guide | Mainspring Data Express Software Prerequisites
Mainspring Data Express Software Prerequisites
Before you install and configure the Mainspring Data Express software you must complete the following
prerequisites:
•Install and Configure MS Message Queuing.
•Create a Mainspring Data Express user on the Paceart Database if you are using SQL Server authentication
(not needed if using Windows Authentication).
Installation Prerequisites
First Time Installation
If you are installing the Mainspring Data Express software for the first time, and not an upgrade, you must
complete the following prerequisites before you can install the Mainspring Data Express software.
•Create an External Systems Account on the CareLink Network. For instructions on how to create an
External Systems Account, refer to the CareLink Network Online Help.
•Create a Paceart External System Account User and Role. For instructions refer to the Paceart Optima
online Help.
•Install .Net Framework version 4.5 (or newer).
•Install and configure MS Message Queuing.
•If you will be using the EHR Integration feature, install the Java Runtime Environment version 1.6 or higher.
Upgrade Installation
If you are upgrading to a new version of Mainspring Data Express software you must first stop the existing
Connected Systems Gateway service.
You do not need to uninstall your existing Mainspring Data Express software.The new version of the software
will import any existing configurations. For example, if you have an existing Paceart-CareLink scheduling
integration configuration, the settings will be saved and used in the new version of the Mainspring Data
Express software.
Installing and Configuring MS Message Queuing for Windows 7
Membership in the local Administrators group, or equivalent, is the minimum required to complete this
procedure.
1. Open the Control Panel.
2. Select the appropriate action based on your system configuration.
•Click Programs, and then under Programs and Features, click Turn Windows features on or off.
•Click Classic View, double-click Programs and Features, and then in the tasks pane, click Turn
Windows features on or off.
3. Under the Microsoft Message Queue (MSMQ) Server option, check the Microsoft Message Queue
(MSMQ) Server Core option. This enables all of the MSMQ Server Core subfeatures.
4. Click OK.
5. If you are prompted to restart the computer, click OK to complete the installation.
Connectivity Guide | Mainspring Data Express Software Prerequisites | 9
Installing and Configuring MS Message Queuing for Windows 8.1
Membership in the local Administrators group, or equivalent, is the minimum required to complete this
procedure.
1. From the Charms bar, click Settings.
2. Click Control Panel.
3. Click Programs, and then under Programs and Features, click Turn Windows features on or off.
4. Under the Microsoft Message Queue (MSMQ) Server option, check the Microsoft Message Queue
(MSMQ) Server Core option. This enables all of the MSMQ Server Core subfeatures.
5. Click OK.
6. If you are prompted to restart the computer, click OK to complete the installation.
Installing and Configuring MS Message Queuing for Windows Server 2008
Membership in the local Administrators group, or equivalent, is the minimum required to complete this
procedure.
1. Click Start > Control Panel.
2. Double-click Programs and Features.
3. Click Turn Windows features on or off.
The Server Manager window is displayed.
4. Select Add Features in the Features and Summary section.The Add Feature Wizard dialog is displayed.
5. Under the Message Queuing > Message Queuing Services option, select the Message Queuing Server
option.
6. Click Next on the Add Feature Wizard dialog box to select features.
7. Click Install on the Add Feature Wizard dialog box to confirm your installation selections.
8. When the installation is complete, click Close.
Installing and Configuring MS Message Queuing for Windows Server 2008 R2
Membership in the local Administrators group, or equivalent, is the minimum required to complete this
procedure.
2. In the Server Manager, click Add Features to start the Add Features Wizard.
3. Expand MSMQ, expand MSMQ Services, and then select the Message Queuing Server option.
4. Click Next, and then click Install.
5. If you are prompted to restart the computer, click OK to complete the installation.
Installing and Configuring MS Message Queueing for Windows Server 2012 and Windows
Server 2012 R2
Membership in the local Administrators group, or equivalent, is the minimum required to complete this
procedure.
1. Launch Server Manager.
2. In the Server Manager, click Add Roles and Features to start the Add Roles and Features Wizard.
3. Click Next until the Features page opens.
10 | Connectivity Guide | Mainspring Data Express Software Prerequisites
4. Expand Message Queuing, expand Message Queuing Services, and then select the Message Queuing
Server option.
5. Click Next, and then click Install.
6. If you are prompted to restart the computer, click OK to complete the installation.
Installing the Java Runtime Environment
If you will be installing the EHR Integration feature, you will need to install the Java Runtime Environment
version 1.6 or higher.
You do not need to be connected to the internet to install the files.
1. Insert the Mainspring Data Express software USB into your disk drive.
2. Browse to the USB and double-click on jre-7u10-windows-i586.exe.
The installation wizard starts.
3. Click Install.
A progress window is displayed.
4. Once the installation is complete, click Close.
Installing .Net 4.5 Framework
You must have .Net 4.5 Framework (or newer) installed before you install the Mainspring Data Express
software.
You do not need to be connected to the internet to install the files.
1. Insert the Mainspring Data Express software USB into your disk drive.
2. Browse to the USB and double-click on dotNetFx45_Full_setup.exe.
3. Read the Microsoft license agreement and select I have read and ACCEPT the terms of the License
Agreement.
4. Click Install.
The .Net Framework will install. A progress bar shows the installation progress.
5. Once the setup is complete click Exit.
Stopping the Connected Systems Gateway Service
Before you install a new version of the Medtronic Mainspring Data Express software you must stop the existing
Connected Systems Gateway service.
Membership in the local Administrators group, or equivalent, is the minimum required to complete this
procedure.
1. To stop the Connected Systems Gateway service go to Start > Control Panel > Administrative Tools
> Services.
2. Right-click on the Connected Systems Gateway service and select Stop.
Connectivity Guide | Installing Mainspring Data Express | 11
Installing Mainspring Data Express
Complete the items listed in the prerequisites section before you install and configure the Mainspring Data
Express software.
1. To start the installation, insert the Mainspring Data Express installation USB into the computer.The setup
program will automatically start.
If the setup program does not automatically start, you can manually start the installation program by clicking
CSGInstall.exe on the installation USB.
2. Click Next.
3. Enter a destination folder. Click Change to change from the default location.
If you have a previous version of Mainspring Data Express installed, use the same filepath as the previous
version.
4. Click Next.
5. Click Install.
A progress bar shows the installing progress.
6. Select Launch Medtronic Mainspring Data Express and then click Finish to exit the installation wizard
and open the Medtronic Mainspring Data Express window.
12 | Connectivity Guide | Installing Mainspring Data Express
7. In the Medtronic Mainspring Data Express window, select the features you want to enable, then click
Configurations.You can select multiple features under Paceart Integration, but you can only select one
feature under CareLink Integration.
The configuration window for the feature you selected is displayed.
8. Make your configuration changes and click OK. Refer to the following sections for information on configuring
each feature.
The configuration window closes.
9. Click OK to close the Mainspring Data Express window.
If you selected EHR Integration for the first time, the Mirth Connect installer will launch. Follow the
installation steps in the Installing and Configuring Mirth Connect section of this document.
If you selected HL7 Integration for the first time, the Corepoint Integration Engine installer will launch.
Follow the installation steps in the Installing the Corepoint Integration Engine section of this document.
Connectivity Guide | Installing Mainspring Data Express | 13
Automatically Starting the Connected Systems Gateway After Restart
1. After you verify that your implementation was successful you can set this service to automatically connect.Go to Start > Control Panel > Administrative Tools > Services.
2. Right-click on the Connected Systems Gateway service and select Properties.
3. Select Automatic in the Startup type field. If you restart your computer this service will automatically
restart.
4. Click OK.
Log File Configuration
The default location for log files, depending on your operating system will be one of the following locations:
•For 32 bit operating systems the location is C:\Program Files\Medtronic\Connected SystemsGateway\Logs\.
•For 64 bit operating systems the location is C:\Program Files (x86)\Medtronic\ConnectedSystems Gateway\Logs.
The default log file retention count is 10.You can save up to 99 log files.
14 | Connectivity Guide | Paceart Integration
Paceart Integration
The Paceart Integration section of Mainspring Data Express has the following features:
•CareLink Scheduling Integration: Allows you to exchange scheduling data between the CareLink Network
and Paceart.
•HL7 Integration: Allows you to import demographic information, scheduling information, and interrogated
device data using ORU^R01 messages that conform to the IHE IDCO profile, from electronic medical
record systems or practice management systems. Also allows you to export device data to electronic
medical record systems via HL7.
•Local Data Interface: Allows you to configure the service that receives patient session data transmitted
from local sources, such as a device programmer or Latitude.
•CareLink Transmission Integration: Allows you to configure the service that imports patient session data
into Paceart from CareLink.
General Paceart Settings
General Paceart External System Account
This section gives you a simple way to configure a single account to use with all your all the integration
features.To enable this account for all Paceart features, select the Use General Paceart External SystemAccount Settings check box on the feature-specific tab.To use different external system accounts for each
feature, clear the Use General Paceart External System Account Settings check box on the feature-specific
tab, then enter the Username and Password of the account.
Paceart Optima Application Server
These settings contain information about the computer on which the Paceart Optima Application Server is
installed. Mainspring Data Express communicates with the Paceart Optima Application Server using this
hostname and port to exchange data between Paceart and external sources.
Configuring Paceart Settings
General Paceart Settings can be modified by editing the paths. For each of the Paceart Web Services, the
localhost need to be replaced with the hostname and port number.
1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express >
Medtronic Mainspring Data Express.
2. In the Medtronic Mainspring Data Express window, select at least one of the following Paceart Integration
features and click Configurations:
•CareLink Scheduling Integration
•HL7 Integration
•Local Data Interface
•Remote Data Interface
•Data Bridge Gateway
The Paceart Integration configuration window is displayed.
3. In the General Paceart Settings section, edit the settings as needed.
a) Update the Username and Password for the external system account set up in Paceart.
Connectivity Guide | Paceart Integration | 15
b) Change the Hostname to the domain name or IP address of the computer on which the Paceart Optima
Application Server is installed.
c) Change the Port to the port number the Paceart Optima Application Server uses on that computer.
The default value is 333.
4. Click OK.
Paceart Integration Configuration Values
This table explains the fields under General Paceart Settings on the Paceart Integration configuration
window.
ExplanationField Name
General Paceart External System Account
Username
Password
Paceart Optima Application Server
Hostname
Port
The Paceart External System Account username. This username is
defined in Paceart on the External System Accounts tab.
The Paceart External System Account password. This password is
defined in Paceart on the External System Accounts tab.
The domain name or IP address of the computer on which the Paceart
Optima Application Server is installed.
The port number the Paceart Optima Application Server domain
interface uses.The default value is 333.
CareLink Scheduling Integration
The Paceart-CareLink Scheduling Integration feature provides a way to automatically synchronize scheduling
between the CareLink Network and the Paceart System. If you schedule an appointment in CareLink, it will
be downloaded to the Paceart System; if you schedule an appointment in Paceart, it will be sent to CareLink.
Paceart regularly requests status information for appointments scheduled in CareLink. Schedules are either
updated nightly or when a clinician makes a request from the Paceart System.
If an appointment is created in CareLink, CareLink retains ownership until the appointment is sent to Paceart.
Once the Paceart System is updated to reflect the CareLink Network appointment, the appointment is owned
by Paceart.
If a remote appointment is created or modified in Paceart, the appointment is automatically created or updated
in CareLink. Ownership of the appointment remains with the Paceart System.
Paceart receives appointment status information that reflects the last known status as reported by CareLink.
The remote status is displayed in patient appointment information on the Paceart System. Paceart records
the completion and failure status details of this information in its log. Paceart scheduling requests that violate
CareLink Network scheduling rules are displayed as errors in the Paceart System Remote Status field.
When you schedule a remote appointment in Paceart, the Remote Status will show "Processing." Once the
appointment is successfully acknowledged by CareLink, the Remote Status will show "Scheduled." If the
appointment is not successfully sent to CareLink or if CareLink reports an error, the Remote Status will show
"Error." An "Error" status can be manually changed to "Ignore." Once the transmission is received by CareLink,
the Remote Status will show "Completed." If CareLink determines that an appointment was missed, the
Remote Status will show "Missed".
Contact your Paceart technical support specialists regarding support for appointment scheduling transfers
on the Medtronic CareLink Network.
16 | Connectivity Guide | Paceart Integration
CareLink Scheduling Integration Prerequisites
Before you configure CareLink Scheduling Integration, you must complete the following prerequisite:
•On the CareLink website, create an External System Account for Mainspring Data Express and enable
the Scheduling Integration feature.
Before you use CareLink Scheduling Integration, you must ensure that Paceart patient records and
appointments meet the following criteria:
•The Paceart patient record must have a birth date, a patient ID number, and a patient ID number type.
•Appointments created or updated in Paceart must have the patient remote follow-up service set to
Medtronic CareLink Network, and the patient must have an active Medtronic ICD, ICM, or pacemaker
that is supported by the Medtronic CareLink Network.To find out if a device is supported, log into CareLink
and click Resources > CareLink Supported Implantable Devices.
Paceart/CareLink patient matching for a single patient
The primary match is on the patient ID number, patient ID number type, and the birth date. If either of these
are not present in the Paceart System, appointments will not be sent to CareLink. If the patient ID number
and patient ID number type is not present in the CareLink system, a demographic match is performed.The
configurable matching criteria include first name, middle initial, and gender in addition to the last name and
birth date which are always used. If the demographic match succeeds, CareLink will record the patient number
so future matches will be simpler and quicker.
This matching is performed on CareLink and is used when adding, updating and removing appointments,
and when updating remote appointment status.
Paceart/CareLink patient matching for a batch download
In this scenario, the Paceart System downloads a list of all CareLink patients and appointments and then
matches CareLink patients to Paceart patients.The primary matching is on the patient ID number, patient ID
number type, and the birth date. If the patient ID number and ID number type is not present in the CareLink
system a much stricter demographic match is performed. This requires a match on the first name, middle
initial, last name, gender, and birth date.
Configuring CareLink Scheduling Integration
1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express >
Medtronic Mainspring Data Express.
2. In the Medtronic Mainspring Data Express window, select CareLink Scheduling Integration and click
Configurations.
The Paceart Integration window is displayed.
3. On the CareLink Scheduling Integration tab, enter the applicable values for your CareLink implementation.
Refer to the CareLink Scheduling Integration Configuration Values table for more explanation on the fields.
This table explains the fields on the CareLink Scheduling Integration configuration tab.
ExplanationField name
CareLink Settings
Connectivity Guide | Paceart Integration | 17
ExplanationField name
CareLink Scheduling Service
CareLink Scheduling Service Site
External System Account Name
External System Authorization
Code
Send Patient First Name
Send Patient Middle Name
Send Patient Gender
Paceart Settings
Patient ID Type Description
The name of the CareLink scheduling service that the adapter will use. The default
value is "Endpoint_CSA_basicHttpsBinding".
The fully qualified path of the CareLink scheduling service that the adapter will use.
The default value is
"https://clscheduling.medtroniccarelink.net/SchedulingGateway/SchedulingGateway.svc".
The account name of the dedicated user that will be used to connect to the CareLink
Scheduling service. This account name is created and configured on the ExternalSystem Accounts tab on the CareLink website.
The account authorization code that will be used to authenticate the CareLink User
ID with the CareLink Scheduling service. This authorization code is created and
configured on the External System Accounts tab on the CareLink website.
A Boolean value indicating if the Patient First Name value is sent to CareLink. If
"True", it will be used by CareLink for patient matching.The default value is "True".
A Boolean value indicating if the Patient Middle Name value is sent to CareLink. If
"True", it will be used by CareLink for patient matching.The default value is "True".
A Boolean value indicating if the Patient Gender value is sent to CareLink. If "True",
it will be used by CareLink for patient matching.The default value is "True".
The Paceart Patient ID Type Description to associate with the CareLink Remote
Patient ID. The default value is "Default".
Appointment Resource
The Paceart Appointment Resource to associate with CareLink remote appointments.
The default value is "Default Resource".
Troubleshooting CareLink Scheduling Integration
Troubleshooting scheduling connectivity problems
CareLink
•Verify that the CareLink account used to connect to Mainspring Data Express has a Transmission
Permission selection of View changes transmission status from new to viewed.
•Verify that the CareLink account used to connect to Mainspring Data Express does not have an expired
password.
•If the CareLink clinic has sub-clinics, verify that the CareLink account used to connect to the Medtronic
Mainspring Data Express has access to the sub-clinics' patients integrated with Paceart.
•Verify that you created an External System Account in CareLink.
•Verify that the created External System Account was configured to include Scheduling Integration external
system associations.
•Verify that scheduling integration has not been unlinked and verify the "Last Connected on" date/time
displayed. Go to the CareLink Network website and click Manage My Clinic > Clinic Profile > External
Systems Integration.
Paceart
•Verify that the Paceart Database Manager is running.
•Verify that the Paceart database has a Mainspring Data Express user.
•Verify the Paceart database password associated with the Mainspring Data Express user.
18 | Connectivity Guide | Paceart Integration
•Verify that the patient's Demographics tab in Paceart has the patient remote follow-up service set to
Medtronic CareLink Network, and that the patient has a Medtronic ICD or pacemaker that is supported
by the Medtronic CareLink Network. To view the CareLink Network supported devices list, login to the
CareLink website and go to Resources > CareLink Supported Implantable Devices.
•Verify that the Paceart patient record has a date of birth and a valid patient ID number.
Mainspring Data Express
•Verify that the Mainspring Data Express software and features were properly installed and configured.
•Verify that the correct CareLink hosting system was entered in the CareLink Scheduling Integration tab
of the Paceart Integration dialog box.The CareLink hosting system must match what was entered in the
Remote Data Interface tab.To verify these details, the Remote Data Interface feature should be selected
in the Medtronic Mainspring Data Express window.
•Verify that the Connected Systems Gateway service was started.
Paceart Optima HL7 Integration
View and Resolving Errors
In Paceart Optima you can view and resolve HL7 errors in Administration > Activity Log.The Patient
Management service logs all patient information changes from the HL7 protocol. Any additions, deletions,
and updates to patient records from HL7-based systems are logged under this service in the Activity Log. In
some instances a work item is created and requires a Paceart user or workgroup resolve the issue.
For a complete list of Activity Log Results refer to the Paceart Optima System Software User Manual or the
Paceart Optima online Help.
Paceart Optima Patient ID Configuration
In Paceart Optima a patient can have multiple patient IDs. You can configure patient IDs in Administration
> Demographics > Patient ID Types tab. Matching an inbound patient ID involves matching both the ID
number and the ID type. By default Paceart matches the first occurrence of the PID-3 segment to patient ID
number and patient ID type.
For example, your Paceart Optima System has a patient ID type called "EMR".
You receive the following PID segment in an HL7 message:
PID|||1335579^^^^EMR~654321^^^^MRN|
This would match a patient in Paceart with an "EMR" type ID and a patient ID number of "1335579".
Connectivity Guide | Paceart Integration | 19
Paceart Optima Patient Matching Configuration
In Paceart Optima you must configure patient matching in Administration > Connectivity > Patient Matching
Configuration tab. Patient matching is initially based on the patient ID only.You can configure an additional
second level of patient matching in the Verify Patient Match Configuration section. If a patient match cannot
be made using the patient ID, you can also configure matching based on patient demographic information.
You can configure this matching in the Demographics Only Match Configuration section. This additional
and secondary matching can determine when a new patient is created in Paceart, when an error is logged,
and when a work item is created.
For more information on configuring Paceart Optima patient matching refer to the Paceart Optima SystemSoftware User Manual or the Paceart Optima online Help.
Configuring Paceart HL7 Integration
1. To start Mainspring Data Express, click Start > Programs > Medtronic Mainspring Data Express >
Medtronic Mainspring Data Express.
2. In the Medtronic Mainspring Data Express window, select HL7 Integration and click Configurations.The Paceart Integration configuration window is displayed.
3. In the HL7 Integration tab, enter the values for your configuration.
4. Click OK to close the Paceart Integration configuration window.
HL7 Integration Configuration Values
This table explains the fields on the HL7 Integration configuration tab.
ExplanationField name
HL7 Outbound
Outbound Include Episode Observations
Include Nonconforming Data
Boolean value providing an option to include episode data in the HL7
message sent to the receiving system. Inclusion of this data may add
to the size of the message.
The default value is "False" (do not send episode data).
Boolean value providing an option to include nonconforming data in
the HL7 message sent to the receiving system. Inclusion of this data
may add to the size of the message.
Include IDCO Nonconforming Data
The default value is "True".
Boolean value providing an option to include IDCO nonconforming
data in the HL7 message sent to the receiving system. Inclusion of
this data may add to the size of the message.
The default value is "True".
20 | Connectivity Guide | Paceart Integration
ExplanationField name
Include Medtronic OBX Segments
Include PV2 Segment
Paceart
Paceart XML Version
Boolean value providing an option to include Medtronic OBX segments
in the HL7 message sent to the receiving system. Inclusion of this
data may add to the size of the message.
The default value is "True".
Boolean value providing an option to include the PV2 segment in the
HL7 message sent to the receiving system. Inclusion of this data may
add to the size of the message.
The default value is "True".
The version of Paceart XML that will be exported from Paceart to
HL7. This value is for reference only and cannot be edited.
Installing the Corepoint Integration Engine
If you selected the Paceart HL7 Integration feature, the Corepoint Integration Engine is installed if it is not
already installed. If you have a previous version of NeoIntegrate installed, you need to remove it and install
the Corepoint Integration Engine.
The Corepoint Integration Engine installation is only launched one time. If you cancel the installation or need
to re-execute the installation, you must first delete the following file to allow the Corepoint Integration Engine
installation to be launched again:C:\Program Files (x86)\Medtronic\Connected SystemsGateway\HL7SubSystem\Installed. (The path is different if the default destination folder was modified.)
During the Corepoint Integration Engine installation, a dialog box may be displayed that states "The installation
of Microsoft Visual C++ 2008 Redistributable Package (x86) appears to have failed. Do you want to continue
the Installation?" If this dialog box is displayed, click Yes and continue the installation.
1. On the Corepoint Health Solutions - InstallShield Wizard window, click Next.
2. Read the license agreement. Click Next to accept it.
3. Specify a destination folder. Click Change to change the default location, and then click Next.
4. Select the type of installation you want and click Next.
5. Select the products you want to install.The default selection is Corepoint Integration Engine. Click Next.
6. If your Paceart System uses SessionSync, you have a port conflict. Specify which alternate ports youwould like to use, and then click Next.
7. Enter an Administrator password and click Next.
8. Click Install to install the Corepoint Integration Engine.
9. When the installation is complete, you can launch the license manager. If you already have your licensestring select this option and click Finish.
Note: If you do not have your license string deselect the Launch the License Manager option and call
Paceart Technical Support for licensing information.
After you click Finish, the Log On dialog is displayed.The Medtronic Mainspring Data Express window
also opens in front of the Log On dialog. Move the window out of the way.
10. Enter the username and password you specified in step 6, and then click OK.
11. On the LicenseManager window, click License wizard.
The License Wizard starts.
12. Click Next.
13. Select the Request a license using a product key option, and then click Next.
Connectivity Guide | Paceart Integration | 21
14. On the Machine description dialog box, enter a description of how this license is used, and then click
Next.
For example, "St. Elsewhere Hospital Production Server"
15. On the Connection and login information dialog box, enter the Web login provided by Operations and
Technical Services and connection details and click Next.
16. Click Connect to contact Corepointhealth.com to obtain your license.
17. After you have connected to Corepointhealth.com click Next.
18. Click Finish.
19. On the LicenseManager window, click Exit.
20. After exiting the license manager, you can load the Corepoint Health configuration import/export file. Runthe Corepoint Integration Engine Administration console by clicking Start > All Programs > Corepoint
Health > Corepoint Integration Engine > Corepoint Integration Engine - Administration.
21. Enter the user name and password you specified when installing the Corepoint Integration Engine and
click OK.
The Corepoint Integration Engine Administration Console window is displayed.
22. Ensure that the Integration Engine Service is started.
23. Close the Corepoint Integration Engine Administration Console window.
24. Open the Corepoint Integration Engine Configuration console by clicking Start > All Programs > Corepoint
Health > Corepoint Integration Engine > Corepoint Integration Engine - Configuration.
25. Enter the user name and password you specified when installing the Corepoint Integration Engine and
click OK.
The Corepoint Integration Engine Configuration window is displayed.
26. Click File > Import.
The Open File window is displayed.
27. Navigate to the configuration file folder at C:\Program Files\Common Files\Medtronic\CSG
Shared Files\.
28. Double-click the HL7 Source and Destination Transformation.nix file.
The Import selected components window is displayed.
29. Select all of the components and click Import.
30. Click OK after the components have been loaded.
31. Commit the update to the Corepoint Integration Engine by clicking Version > Commit All...The Commit Changes dialog box is displayed.
32. Click Commit and Activate at the bottom of the dialog box.
33. When the Confirm Engine Reconfiguration dialog box is displayed, click Commit and Activate again
to confirm your changes.
The Corepoint Integration Engine pauses and restarts to commit the update.
34. Close the Corepoint Integration Engine Configuration window.
Troubleshooting Paceart HL7 Integration
Troubleshooting Paceart HL7 integration problems
Paceart
•Verify that the Paceart database has a Mainspring Data Express user.
•Verify the Paceart database password associated with the Mainspring Data Express user.
•Verify that the Paceart patient record has a date of birth and a valid patient ID number.
Mainspring Data Express
•Verify that the Mainspring Data Express software and features were properly installed and configured.
22 | Connectivity Guide | Paceart Integration
•Verify that the Connected Systems Gateway service was started.
Programmer Acquisition service cannot start Event Log message
If in the Event Log for the Programmer Acquisition service you receive an error message that says "Programmer
Acquisition service cannot start", you need to change the Corepoint Integration Engine port value.
2. Click Service > Corepoint Integration Engine Monitor Service Configuration.
The Corepoint Integration Engine Monitor Service Configuration window is displayed.
3. Change the port value.
4. Click OK.
Local Data Interface
The Local Data Interface allows you to configure the service that receives patient session data transmitted
from local sources, such as a programmer or LATITUDE. You can start and stop the service, configure
advanced options, and enable or disable transmissions from enabled sources.
Updating the Local Data Interface Port Number
The value in the Port field on the Local Data Interface tab identifies the port Mainspring Data Express uses
to receive data from local sources.This value must match the value of the port configured for the programmer
or for LATITUDE.
1. If needed, change the value in the Port field to match the port configured for the local source.The default
value is 443.
2. Click OK to save your changes.
Local Data Interface Extended Configurations
This table explains the fields on the LDI Extended Configurations window.
ExplanationField name
Manufacturer Name
Encounter Type
Username
Password
The manufacturer name of the data provided by a specific system.
For example, "Medtronic".
The type of data provided by a specific system.The default value is
"InClinic".
The username for a user-defined local data interface extended
configuration.
The password for a user-defined local data interface extended
configuration.
Local Data Interface certificate installation
The digital certificate allows a secure connection to be established between a data import source and Paceart.
You must complete the certificate installation before you can import data from other sources.
Connectivity Guide | Paceart Integration | 23
You will generate a certificate request that you will email to Paceart Technical Support. Then Technical
Support will email you back the certificate file that you will import into your system and install.
If you have questions please call Paceart Technical Support.
Installing the Certificate
1. On the Local Data Interface tab, click Generate Request.
The Export Certificate Request window is displayed.
2. In the Customer Information section, enter your information in the following required fields:
•Organization
•State or Province
•Country
3. In the Contact Information section, enter your information in the following required field:
•Email - must be in standard email format (the certificate will be emailed to this email address)
4. From the Server Addressing section, select how you would like the data import source to address the
Local Data Interface. Select the check box next to Host Name or IP Address.
5. Click Export Certificate Request to a File.
6. Select the location where you would like to save the certificate request file. You must save to a location
that can be accessed by a workstation or computer that has email. The default file location is
C:\PaceartGatewayCertificateRequest.McertReq.
7. Once the file has been successfully exported, click OK.
8. Send an e-mail with the exported certificate request file to Paceart Technical Support at
CertSupport@Medtronic.com.
9. Technical Support will then send the certificate file to the email address you specified.
Note: Some days may elapse before you receive the certificate. The certificate is usually sent out within
one business day.
10. Save the certificate file to a location that is accessible from the Paceart computer. The default filename
is C:\PaceartGatewayCertificate.MCert.
11. Click Install Certificate.
12. Find and select the file using the standard Windows dialog and click Open.
13. If you have completed the installation successfully, the Digital Certificate section will display Digital
Certificate has been installed. If you receive an error message, call Paceart Technical Support.
Enabling a data import source
You must install the certificate before you can enable a source for data import.
1. Click on the source ID listed in the Available for Data Import table to select it.
2. Click Add.
3. The source ID will now be in the Enabled for Data Import table.
4. Click OK for the changes to take effect. This source is now able to import data to Paceart.
24 | Connectivity Guide | Paceart Integration
CareLink Transmission Integration
The CareLink Transmission Integration options control how Paceart Optima receives transmissions from the
CareLink Network through Mainspring Data Express.
•Configure the Remote Data Interface service to import patient session data from the CareLink Network
upon request by Paceart.
The Remote Data Interface service allows patient session data to be imported from Carelink when requested
from within Paceart Optima.This service also allows you to import historical transmissions from CareLink
over the period you specify.
•Configure the Data Bridge Gateway service to export patient session data from the CareLink Network and
import it into Paceart Optima.
Remote Data Interface
The Remote Data Interface allows you to configure the service that imports patient session data from remote
sources, such as the Medtronic CareLink Network.You can start and stop the service, specify the polling
interval, select the service's auto start options, and configure the login information for remote follow-up
services.
Configuring Remote Data Interface
1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express >
Medtronic Mainspring Data Express.
2. In the Medtronic Mainspring Data Express window, select Remote Data Interface and click
Configurations.
The Paceart Integration configuration window is displayed.
3. On the Remote Data Interface tab enter the applicable values for your implementation. Refer to the
Remote Data Interface Configuration Values table for more explanation on the fields.
Connectivity Guide | Paceart Integration | 25
4. If you receive data from more than one remote system, you must have a separate Remote Data Interface
configuration for each system. Click Add to create additional configurations for additional remote systems.
You can create up to 5 configurations.
5. Click OK.
Remote Data Interface Configuration Values
This table explains the fields on the Remote Data Interface configuration tab.
ExplanationField name
Carelink 1
Data Service
Data Service Site
System Account Name
System Account Access Code
Manufacturer Name
Application ID
Encounter Type
Clinic Request (Days of History)
The name of the service. The default value is
"Endpoint_CSA_basicHttpsBinding".
The URL to access the data service(s) of a specific system. For
CareLink, this is referred to as the Transmission Gateway Service.
The account name used to connect to the CareLink system. This
account name is created and configured on the External SystemAccounts tab on the CareLink website.
The authorization code used to connect to the CareLink website.This
authorization code is configured on the External System Accounts
tab on the CareLink website.
The manufacturer name of the data provided by a specific system.
For CareLink, this value is "Medtronic".
The name of the external system. For CareLink, this value is
"CareLink".
The type of data provided by a specific system. For CareLink, this
value is "Remote".
The value indicating how many days of history to request from the
external system. The default value is 7.
Enabling remote data acquisition in Paceart
After you have configured Remote Data Interface for Mainspring Data Express, you need to enable remote
data acquisition in Paceart.
1. Log in to Paceart.
2. Use the connectivity tools available in Paceart administration to set up remote encounter acquisition.You
can enable remote encounter acquisition and set up nightly imports.
For instructions, refer to the Paceart Optima online Help or the Paceart Optima Software User Manual.
Data Bridge Gateway
The CareLink Data Bridge Gateway allows you to export patient session data from the CareLink Network and
import it into your Paceart Optima system.
When a CareLink Clinic Administrator enables the EHR Integration feature, an External System Account is
created that has privileges to retrieve data for that clinic.These External System Account credentials are
used by Mainspring Data Express to access the Data Bridge Gateway.
26 | Connectivity Guide | Paceart Integration
Enabling Data Bridge Gateway Integration in CareLink
Before you can configure the Data Bridge Gateway integration, you need to set up an external system account
for Mainspring Data Express in the CareLink Network.
1. On the CareLink Network website, create an External System Account for Mainspring Data Express.
For that External System Account, enable and configure the EHR Integration feature. For instructions,
refer to the CareLink Network online Help.
The EHR Integration feature in CareLink sets up the credentials needed for Mainspring Data Express to
access the Data Bridge Gateway and retrieve patient session data.
2. On your network, install and configure the Mainspring Data Express software (install prerequisites first).
3. Enable and configure the Data Bridge Gateway feature in Mainspring Data Express.
4. Test your configuration by putting it into Test on the CareLink Network and export data. After you have
tested your integration, move your configuration to Production on the CareLink Network. For instructions,
refer to the CareLink network online Help.
Configuring Data Bridge Gateway
1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express >
Medtronic Mainspring Data Express.
2. In the Medtronic Mainspring Data Express window, select Data Bridge Gateway and click
Configurations.
The Paceart Integration configuration window is displayed.
3. On the CareLink DataBridge Gateway tab, enter the applicable values for your implementation. Refer
to the CareLink DataBridge Gateway Configuration Values table for more explanation on the fields.
4. If you receive data from more than one remote CareLink Network system, you must have a separate Data
Bridge Gateway configuration for each system. Click Add to create additional configurations for additional
remote systems.You can create up to 15 configurations.
5. Click OK.
Connectivity Guide | Paceart Integration | 27
CareLink DataBridge Gateway Configuration Values
This table explains the fields on the Data Bridge Gateway configuration tab.
ExplanationField Name
Configuration 1
Description
Data Bridge Service
Data Bridge Service Site
External System Account Name
External System Account
Authorization Code
An optional field for entering the name of your configuration. Limit 15
configurations.
The name of the CareLink Data Bridge service the adapter will use.
The default is "Endpoint_CSA_basicHttpsBinding"
The path of the CareLink Data Bridge Service site that the adapter
will use.
•To connect in the US and Canada, select
https://cl-emr.medtroniccarelink.net/
DataBridgeGateway/DataBridgeGatewayService.svc
•To connect in Europe and Asia, select
http://cl-emr.europe.medtroniccarelink.net/
DataBridgeGateway/DataBridgeGatewayService.svc
The account name used to connect to the CareLink system. This
account name is created and configured on the External SystemAccounts tab on the CareLink website.
The authorization code used to connect to the CareLink website.This
authorization code is configured on the External System Accounts
tab on the CareLink website.
Troubleshooting Data Bridge Gateway Integration
CareLink EHR Integration
•Verify that the Mainspring Data Express software prerequisites were installed or configured correctly.
•Verify that you selected the correct Data Bridge Service Site for your geography.
•Verify that the External System Account Name and External System Account Authorization Code
match what was created in CareLink on the External System Accounts tab.
•Verify that you've selected True in the Use Specified Credentials field if the report destination requires
you to enter a Windows username and password. Then verify that the Windows username and password
were entered correctly in the Username and Password fields.
•Verify that the Connected Systems Gateway service was started.
Paceart Integration
•Verify that the Paceart Database Manager is running.
•Verify that the Paceart database has a Mainspring Data Express user.
•Verify the Paceart database password associated with the Mainspring Data Express user.
28 | Connectivity Guide | CareLink Integration
CareLink Integration
The CareLink Integration section of Mainspring Data Express has the following features:
•Report Export allows you to save CareLink Network reports to a network location.
•EHR Integration allows you to export patient data from the CareLink Network and integrate into your clinic's
Electronic Health Records (EHR) system.
CareLink Report Export
Reports can be exported from CareLink to an external system, like your clinic's Electronic Health Records
(EHR) system.
When the Report Export feature is enabled, you can use a default file naming format, or customize the filename
format by adding an additional field.You must have full administrative privileges in CareLink to edit the
filename format.
To export reports, Mainspring Data Express must be installed and configured, and a CareLink Network
Connection between Mainspring Data Express and the CareLink Network must be established.
There is a process to install and configure the Report Export feature.
1. On the CareLink Network website, create an External System Account for Mainspring Data Express.
Enable and configure the Report Export feature for that External System Account. For instructions refer
to the CareLink Network Online Help.
2. On your network, install and configure Mainspring Data Express (install prerequisites first).
3. Enable the Report Export feature in Mainspring Data Express.
4. On the CareLink website, export a report from CareLink and ensure that it arrives in the correct location.
Configuring CareLink Report Export
1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express >
Medtronic Mainspring Data Express.
2. In the Medtronic Mainspring Data Express window, select Report Export and click Configurations.
Connectivity Guide | CareLink Integration | 29
The CareLink Report Export configuration window is displayed.
3. On the Configuration1 tab enter the applicable values for your CareLink implementation. Refer to the
CareLink Report Export Configuration Values table for more explanation on the fields.
4. If you have satellite clinics in CareLink you must have a separate Report Export configuration for each
clinic. Click Add to create additional configurations for other clinics.
5. Click OK.
30 | Connectivity Guide | CareLink Integration
CareLink Report Export Configuration Values
If you have satellite clinics in CareLink you must have a separate configuration for each clinic. Click Add to
create additional configurations for other clinics.You may have up to 15 configurations. Each configuration
must have a unique External System Account Name.
This table explains the fields on the CareLink Report Export configuration window.
ExplanationField nameCallout
number
An optional field for entering the name of your configuration. Limit 15 configurations.Description1
2
3
4
Data Bridge
Service
Service Site
External
System
Account Name
The name of the CareLink reporting service the adapter will use.
The default is "Endpoint_CSA_basicHttpsBinding".
The path of the CareLink Data Bridge Service site that the adapter will use.Data Bridge
•To connect in the US and Canada select " https://cl-emr.medtroniccarelink.net/
DataBridgeGateway/DataBridgeGatewayService.svc"
•To connect in Europe and Japan select
"http://cl-emr.europe.medtroniccarelink.net/
DataBridgeGateway/DataBridgeGatewayService.svc "
The account name used to connect to the CareLink system. This account name is
created and configured on the External System Accounts tab on the CareLink
website.
number
Connectivity Guide | CareLink Integration | 31
ExplanationField nameCallout
5
6
7
External
System
Account
Authorization
Code
File Folder
Location
Use Specified
Credentials
Username8
Password9
The authorization code used to connect to the CareLink website.This authorization
code is configured on the External System Accounts tab on the CareLink website.
The file destination path where CareLink PDF reports are exported. On the CareLink
website this is called the document folder.The file destination path can be specified
as a UNC path (\\ComputerName\SharedFolder\Reports) or a mapped drive (z:
\\computer\reports). Using a mapped drive allows you to use a shorter file name
but the computer hosting Mainspring Data Express must have the network drive
mapped to it.
A "True" value indicates that the Windows Username and Password field values
should be used as authentication credentials when accessing the destination path.
A "False" value indicates that a username and password are not required to access
the destination path.
The default is "False".
When Use Specified Credentials is "True", this is the Windows username that will
be used when accessing the destination file system.The Windows username value
should follow the UPN (User Principal Name) format username@domain. For
example BSMITH@ENT.
When Use Specified Credentials is "True", this is the password associated to the
Windows Username that will be used when accessing the destination file system.
10
11
Overwrite
Existing File(s)
Minimum
Available Disk
Space
A "True" value indicates that the adapter will overwrite an existing file with a new
file of the same name. A "False" value indicates that the adapter will not overwrite
an existing file with a new file of the same name.
The default is "True".
The minimum amount of free space in MB on the destination file system required
for the adapter to initialize.
The default is "15" MB.
Enabling and Verifying Mainspring Report Export
After you install and configure Mainspring Report Export you need to enable the Report Export feature on
the CareLink website.
1. Log into the CareLink website.
2. Click Manage My Clinic > Clinic Profile > External Systems Integration.
3. In the Report Export section, select Yes to enable report export.
Note: You can configure the report filename. For more information on configuring the filename refer to
the Editing Report Filename for Report Export topic in the CareLink online Help.
4. Click Save.
5. After you have enabled the feature, export a sample report from CareLink.
6. Browse to the documentation folder location and verify that the sample report was successfully exported.
32 | Connectivity Guide | CareLink Integration
Troubleshooting Report Export
CareLink Report Export
•Verify that the Mainspring Data Express software prerequisites were installed or configured correctly.
•Verify that you selected the correct Data Bridge Service Site for your geography.
•Verify that the External System Account Name and External System Account Authorization Code
match what was created in CareLink on the External System Accounts tab.
•Verify that you've selected True in the Use Specified Credentials field if the report destination requires
you to enter a Windows username and password. Then verify that the Windows username and password
were entered correctly in the Username and Password fields.
•Verify that the Connected Systems Gateway service was started.
Mainspring Report Export on CareLink
•Verify that you created an External System Account in CareLink.
•Verify that the created External System Account was configured to include Report Export external system
associations.
•Verify that Report Export was enabled on the External System Integration tab of the CareLink website.
•Verify that the Report Export file naming format was configured as desired.
CareLink EHR Integration
CareLink EHR Integration allows you to export patient data from the CareLink Network and import it into your
clinic's Electronic Health Records (EHR) system. This feature uses Mirth Connect to route the data exported
from the CareLink Network to your EHR.
There is a process to install and configure the Mainspring Report Export feature.
1. On the CareLink Network website, create an External System Account for Mainspring Data Express.
For that External System Account enable and configure the EHR Integration feature. For instructions
refer to the CareLink Network online Help.
2. On your network, install and configure the Mainspring Data Express software (install prerequisites first).
3. Enable the EHR Integration feature in Mainspring Data Express.
4. Install and configure the Mirth Connect software.
5. Test your configuration by putting it into Test on the CareLink Network and export data. After you have
tested your integration, move your configuration to Production on the CareLink Network. For instructions
refer to the CareLink Network online Help.
Configuring EHR Integration
1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express >
Medtronic Mainspring Data Express.
2. In the Medtronic Mainspring Data Express window, select EHR Integration and click Configurations.
Connectivity Guide | CareLink Integration | 33
The CareLink EHR Integration configuration window is displayed.
3. On the Configuration1 tab enter the applicable values for your CareLink implementation. Refer to the
CareLink EHR Integration Configuration Values table for more explanation on the fields.
4. If you have satellite clinics in CareLink you must have a separate Report Export configuration for each
clinic. Click Add to create additional configurations for other clinics.
5. Click OK.
You will need to install and configure Mirth Connect.
CareLink EHR Integration Configuration Values
This table explains the fields on the CareLink EHR Integration configuration window.
34 | Connectivity Guide | CareLink Integration
number
Connectivity Guide | CareLink Integration | 35
ExplanationField nameCallout
An optional field for entering the name of your configuration. Limit 15 configurations.Description1
2
3
4
5
6
7
Data Bridge
Service
Service Site
External System
Account Name
External System
Account
Authorization
Code
Document Folder
Location
Use Specified
Credentials
The name of the CareLink Data Bridge service the adapter will use.
The default is "Endpoint_CSA_basicHttpsBinding"
The path of the CareLink Data Bridge Service site that the adapter will use.Data Bridge
•To connect in the US and Canada select
https://cl-emr.medtroniccarelink.net/DataBridgeGateway/DataBridgeGatewayService.svc
•To connect in Europe and Japan select
http://cl-emr.europe.medtroniccarelink.net/DataBridgeGateway/DataBridgeGatewayService.svc
The account name used to connect to the CareLink system.This account name is created
and configured on the External System Accounts tab on the CareLink website.
The authorization code used to connect to the CareLink website.This authorization code
is configured on the External System Accounts tab on the CareLink website.
The file destination path where files will be written. On the CareLink website this is called
the document folder. The file destination path can be specified as a UNC path
(\\ComputerName\SharedFolder\Reports) or a mapped drive (z:\\computer\reports).
Using a mapped drive allows you to use a shorter file name but the computer hosting
Mainspring Data Express must have the network drive mapped to it.
A "True" value indicates that the Windows Username and Password field values should
be used as authentication credentials when accessing the destination path. A "False"
value indicates that a username and password are not required to access the destination
path.
10
11
Username8
Password9
Overwrite Existing
File(s)
Minimum Available
Disk Space
Mirth Inbound Path12
The default is "False".
When Use Specified Credentials is "True", this is the Windows username that will be
used when accessing the destination file system. The Windows username value should
follow the UPN (User Principal Name) format username@domain. For example
BSMITH@ENT.
When Use Specified Credentials is "True", this is the password associated to the Windows
Username that will be used when accessing the destination file system.
A "True" value indicates that the adapter will overwrite an existing file with a new file of
the same name. A "False" value indicates that the adapter will not overwrite an existing
file with a new file of the same name.
The default is "True".
The minimum amount of free space in MB on the destination file system required for the
adapter to initialize.
The default is "15" MB.
Specifies a file system path where HL7 messages will be available for Mirth Connect
software to use.
The file system path where Mirth is configured to write failed HL7 messages.Mirth Error Path13
36 | Connectivity Guide | CareLink Integration
ExplanationField nameCallout
number
14
Minimum Available
Disk Space
The minimum amount of free space in MB on the file system specified in the Mirth Inbound
Path field, required for the adapter to initialize.
The default is "15" MB.
Installing and configuring Mirth Connect
After you have installed the Mainspring Data Express software and selected the EHR Integration feature, you
will need to install and configure Mirth Connect.
The Mirth Connect installation only launches automatically once. If you cancel the installation or need to
re-execute the installation, you must first delete the following file to allow the Mirth Connect installation to be
launched again:C:\Program Files (x86)\Medtronic\Connected Systems
Gateway\HL7MLLPSubsystem\Installed or C:\Program Files\Medtronic\Connected Systems
Gateway\HL7MLLPSubsystem\Installed, depending on your operating system.The path is different if
the default destination folder was modified.
1. In the Welcome to the Mirth Connect Setup Wizard window, click Next.
2. Read the license agreement, select I accept the agreement, and then click Next.
3. Select the destination directory and click Next.
4. Make sure all of the components are selected and then click Next.
5. Select the Start menu folder settings and then click Next.
6. Configure the network port settings and then click Next.
7. Configure your password requirements and then click Next.
8. Configure your server settings and then click Next.
9. Select Install service and then click Next.
10. Click Finish.
Mirth Connect has been installed.
11. In the system tray, right-click on the Mirth Connect Server Manager icon and select Show Manager.
The Mirth Connect Server Manager is displayed.
12. In the Mirth Connect Server Manager, click Administrator.
13. If a Security Information dialog box appears, click Run.The Mirth Server Manager is installed.
14. In the Mirth Connect Login dialog box, in the Username field enter "admin" and in the Password field
enter "admin".
15. Click Login.
The Welcome to Mirth Connect dialog box is displayed.
16. Create and enter a new username and password. Enter the other required information and then click
Finish.
17. In the Mirth Connect Administrator window, click Channels.
18. In the Channel Tasks pane, click Import Channel.An Open dialog box is displayed.
19. Select the File to MLLP.xml file located at the default path of C:\Program Files
(x86)\Medtronic\Connected Systems Gateway\HL7MLLPSubsystem.
The Edit Channel window is displayed.
Connectivity Guide | CareLink Integration | 37
20. Click the Destinations tab.
21. Enter the Host Address and Host Port that the HL7 message should be sent to.
22. Click Save Changes.
23. In the Mirth Connect pane, click Channels.
24. Click the File to MLLP channel in the Channels pane, and then click Enable Channel from the Channel
Tasks pane.
The channel status is Enabled.
25. In the Channel Tasks pane, click Deploy Channel.The Dashboard shows that the File to MLLP status is "Started".
Troubleshooting EHR Integration
CareLink EHR Integration
•Verify that the Mainspring Data Express software prerequisites were installed or configured correctly.
•Verify that you selected the correct Data Bridge Service Site for your geography.
•Verify that the External System Account Name and External System Account Authorization Code
match what was created in CareLink on the External System Accounts tab.
•Verify that you've selected True in the Use Specified Credentials field if the report destination requires
you to enter a Windows username and password. Then verify that the Windows username and password
were entered correctly in the Username and Password fields.
•Verify that the Connected Systems Gateway service was started.
Mirth Connect
•Verify that the File to MLLP status is "Started".
•Verify that the Mirth Connect windows service status is "Started".
38 | Connectivity Guide | HL7 Integration
HL7 Integration
The Medtronic CareLink Network and the Paceart System support the HL7 protocol which allows those
systems to integrate with your existing HL7-based Electronic Health Record (EHR) and Practice Management
Systems.This allows you to import patient demographic information, scheduling information, and interrogated
device data that conforms to the IHE IDCO profile into Paceart. And allows you to export transtelephonic,
in-clinic, and remote encounter data from Paceart and CareLink to your EHR system.
If you want to integrate Merlin.net into your Paceart System, you can do so with an HL7 ORU message that
conforms to the IDCO profile.
The information contained in this section assumes an understanding of the HL7 Message Specification and
a working knowledge of Paceart.
Inbound Messages
Paceart integrates with the HL7 protocol for inbound messages from external systems to Paceart by mapping
HL7 values to Paceart parameters.
Inbound Patient Administration Messages (ADT)
The Medtronic Mainspring Data Express HL7 integration can receive demographic information from any
system or interface engine that is using HL7 messaging.This feature allows for consistent patient demographic
information across systems and reduces duplication of data entry.
The patient administration transaction set provides for the transmission of new or updated demographic
information about patients. Information that is entered in a patient administration system can be passed to
Paceart as an unsolicited HL7 message.
The Medtronic Mainspring Data Express HL7 integration supports a wide array of ADT trigger events to allow
you to configure the HL7 integration to capture the desired changes to patient demographic information.
Table : Supported HL7 ADT Triggers
The Patient Add, Patient Update, or Patient Add-Update Paceart requests can be configured for the A04,
A08, and A28 messages. Patient Update is most often used.
Adds the patient to Paceart if there is no matching patient record found.Patient Add
Updates the patient record if a single matching patient is found in Paceart.Patient Update
Connectivity Guide | HL7 Integration | 39
DescriptionPaceart Request
Patient Add-Update
Patient Delete
Adds the patient to Paceart if there is no matching patient record found.
Updates the patient record if a single matching patient is found in Paceart.
Deletes the patient from Paceart only if a single matching patient is found,
and the paceart patient record does not have any associated device,
encounter, or appointment.
Changes the specified patient ID if a single matching patient is found.Patient Change ID
Inbound Patient Administration Message Segments
PID - Patient Identification Segment
The PID segment provides important identification information about the patient and is used as the primary
means of communicating the identifying and demographic information about a patient between systems.
The MRG segment provides receiving applications with information necessary to update patient ID data.
OccurrenceSub-componentComponentField
1N/A1MRG-1
1N/A5MRG-1
Parameter
Name
Value
Type
Description
Parameter
Type
N/AString 6Patient Code
N/AString 6Patient Code
N/AString 6Patient Code
Paceart
values
N/AString 50Patient ID
N/AString 50Patient ID
Inbound Scheduling Messages (SIU)
The Medtronic Mainspring Data Express HL7 integration can accept unsolicited schedule notification messages
(SIU) from a scheduling filler application. The HL7 standard defines four roles that the system can assume
42 | Connectivity Guide | HL7 Integration
in scheduling integration. Paceart operates as an Auxiliary application or an "interested third-party." This
allows for existing scheduling systems to serve as the Filler application and to send schedule notification
messages to the Paceart System.The Filler application is said to own the schedule for the specified resources
meaning it is the authoritative source for scheduling information.
Supported Transaction Types
The schedule notification messages can be processed to not only create, delete, cancel, and modify
appointments in Paceart, but also can be used to add or modify patient information.This allows for a patient
to be added to Paceart based on their first appointment with a clinic.
Updating, rescheduling, deleting, or canceling, an appointment can only be performed as long as the
appointment exists in Paceart.
A single matching Paceart appointment for a single matching patient is said to exist if the Appointment External
ID is the same as the Request Appointment External ID (matching appointment is found by ID) or there is an
appointment with the same start date, time, and appointment type (matching appointment is found by start
date, time, and type).
Creates a new appointment in Paceart if the appointment ID does not already exist in
Paceart. If the appointment does exist then no appointment will be added.
Modifies the appointment in Paceart if the appointment ID already exists in Paceart.
Updates the appointment information in Paceart if the appointment exists in Paceart.
If the appointment does not exist in Paceart, then it creates a new appointment in Paceart.
Cancels/Removes the appointment in Paceart if the appointment ID already exists in
Paceart.
Delete
Appointment
Deletes the appointment in Paceart if the appointment ID already exists in Paceart.
Inbound Scheduling Segments
The schedule notification message should contain information on what type of appointment has been booked.
The information can be transformed in the message to map to one of the following values. If no encounter
type information is available in the scheduling messages, the appointment will fail to add/update the Paceart
database.
Connectivity Guide | HL7 Integration | 43
SCH - Schedule Activity Information
The SCH segment contains general information about a scheduled appointment.
The PID segment provides important identification information about the patient and is used as the primary
means of communicating the identifying and demographic information about a patient between systems.
The PV1 segment is used by registration applications to communicate information on a visit-specific basis.
OccurrenceSub-componentComponentField
Name
ENUMPatient Marital
Parameter TypeParameter
Paceart valuesParameter TypeParameter
POLISH,
KANNADA,
BURMESE
MARRIED, SINGLE,
WIDOWED,
DIVORCED,
SEPARATED,
UNDETERMINED,
OTHER
N/ADateTimePatient Date of
YES, NOENUMPatient Death
Paceart
values
N/AN/A1PV1-3
Location of
Care
N/AN/A1PV1-19
Visit ID
PV2 - Patient Visit Information
The PV2 segment is a continuation of visit-specific information contained in the PV1 segment.
OccurrenceSub-componentComponentField
1N/A1PV2-7
2N/A1PV2-7
3N/A1PV2-7
4N/A1PV2-7
Parameter
Name
Value 1
Value 2
Value 3
Value 4
Parameter
Type
N/AString 1Patient Status1N/A1PV1-2
N/AReference_OnlyPatient
N/AString 50Appointment
Paceart
values
N/AString 6Patient Code
N/AString 6Patient Code
N/AString 6Patient Code
N/AString 6Patient Code
AIG - General Resource Segment
The AIG segment contains information about various kinds of resources that can be scheduled.
46 | Connectivity Guide | HL7 Integration
OccurrenceSub-componentComponentField
N/AN/A1AIG-3
Parameter
Name
Resource
Parameter
Type
Inbound Observation Requests (ORU)
The ORU-R01 message transmits observations and results. Mainspring Data Express and Paceart Optima
comply with the IDCO standard for how to use an HL7 ORU message for implantable cardiac device
observations.
Table : Supported HL7 ORU Triggers
Paceart RequestHL7 Message
Transmission DataORU^R01
DescriptionPaceart Request
Sends transmission data from one system to another system.Transmission Data
Inbound Observation Requests Segments
Paceart
values
N/AReference_OnlyAppointment
MSH - Message Header
The MSH segment is present in every HL7 message type and defines the message's source, purpose,
destination, and certain syntax specifics like delimiters (separator characters) and character sets.
The PID segment provides important identification information about the patient and is used as the primary
means of communicating the identifying and demographic information about a patient between systems.
OccurrenceSub-componentComponentField
2..21N/A1PID-3
1N/A4PID-3
Parameter
Name
Value
Session
Device
Manufacturer
Type
Paceart valuesParameter
N/AString 50Patient ID
MDC_IDC_ENUM_MFG_ANGENUMEncounter
MDC_IDC_ENUM_MFG_APC
MDC_IDC_ENUM_MFG_BIO
Paceart valuesParameter
N/AString 100Sending Application
N/AString 100Sending Application
MDC_IDC_ENUM_MFG_BSC
MDC_IDC_ENUM_MFG_CCS
Connectivity Guide | HL7 Integration | 47
OccurrenceSub-componentComponentField
Parameter
Name
Type
Paceart valuesParameter
MDC_IDC_ENUM_MFG_CIM
MDC_IDC_ENUM_MFG_CPM
MDC_IDC_ENUM_MFG_CKP
MDC_IDC_ENUM_MFG_CATM
MDC_IDC_ENUM_MFG_COR
MDC_IDC_ENUM_MFG_ELA
MDC_IDC_ENUM_MFG_GDT
MDC_IDC_ENUM_MFG_IMC
MDC_IDC_ENUM_MFG_MCO
MDC_IDC_ENUM_MFG_MDT
MDC_IDC_ENUM_MFG_OSC
MDC_IDC_ENUM_MFG_PCS
MDC_IDC_ENUM_MFG_SIE
MDC_IDC_ENUM_MFG_SOR
MDC_IDC_ENUM_MFG_SJM
MDC_IDC_ENUM_MFG_TEL
MDC_IDC_ENUM_MFG_VEN
MDC_IDC_ENUM_MFG_VIT
2..21N/A5PID-3
Type
Description
111PID-5
Name
1N/A2PID-5
Name
1N/A3PID-5
Middle
Initial
N/AN/AN/APID-7
Date Of
Birth
N/AN/AN/APID-8
Gender
N/AString 50Patient ID
N/AString 50Patient Last
N/AString 50Patient First
N/AString 1Patient
N/ADateTimePatient
MALE, FEMALE, OTHERENUMPatient
1N/A1PID-11
Address
Line 1
N/AString 50Patient
48 | Connectivity Guide | HL7 Integration
OccurrenceSub-componentComponentField
1N/A2PID-11
1N/A3PID-11
1N/A4PID-11
1N/A5PID-11
1N/A6PID-11
PV1 - Patient Visit Information
The PV1 segment is used by registration applications to communicate information on a visit-specific basis.
Parameter
Name
Address
Line 2
Address
City
Address
State
Address
Postal Code
Address
Country
Type
Paceart valuesParameter
N/AString 50Patient
N/AString 50Patient
N/AString 10Patient
N/AString 10Patient
N/AString 50Patient
OccurrenceSub-componentComponentField
N/AN/A1PV1-19
OBR - Observation Request
The OBR segment transmits information about an exam, diagnostic study/observation, or assessment that
is specific to an order or result.
Measured
Tachycardia
Therapy Counters
Lifetime Right
Ventricle ATP
Delivered
MDC_IDC_STAT_TACHYTHERAPY_TOTAL_DTM_START737921
Measured
Tachycardia
Therapy Counters
Lifetime Start Date
MDC_IDC_STAT_TACHYTHERAPY_TOTAL_DTM_END737922
Measured
Tachycardia
Therapy Counters
Lifetime End Date
MDC_IDC_STAT_TACHYTHERAPY_RECENT_DTM_START737937
Measured
Tachycardia
Therapy Counters
Since Last Counter
Reset Start Date
Parameter
Type
IntegerEncounter
DateTimeEncounter
DateTimeEncounter
DateTimeEncounter
MDC_IDC_STAT_TACHYTHERAPY_RECENT_DTM_END737938
when 737984^MDC_IDC_STAT_EPISODE_VENDOR_TYPE^MDC has OBX-5 value of 773124^STJ-Epis_VT1^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
when 737984^MDC_IDC_STAT_EPISODE_VENDOR_TYPE^MDC has OBX-5 value of 773125^STJ-Epis_VT2^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
DateTimeEncounter
Measured
Tachycardia
Therapy Counters
Since Last Counter
Reset End Date
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset VT1 Monitor
Episode Count or
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset VT1 Episode
Count
Encounter
Measured
Connectivity Guide | HL7 Integration | 77
PaceartIDCO
Parameter NameSupported Values (OBX 5)OBX 3-2OBX
3-1
Tachycardia
Detection Counters
Since Last Counter
Reset VT2 Monitor
Episode Count or
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset VT2 Episode
Count
when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754881^MDC_IDC_ENUM_EPISODE_TYPE_Epis_VF^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset VF VT
Episode Count
Parameter
Type
when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754882^MDC_IDC_ENUM_EPISODE_TYPE_Epis_VT^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754883^MDC_IDC_ENUM_EPISODE_TYPE_Epis_ATAF^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754884^MDC_IDC_ENUM_EPISODE_TYPE_Epis_SVT^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset VT Episode
Count
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset AF AT
Episode Count
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset SVT Episode
Count
when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754885^MDC_IDC_ENUM_EPISODE_TYPE_Epis_Monitor^MDC
78 | Connectivity Guide | HL7 Integration
PaceartIDCO
3-1
Parameter NameSupported Values (OBX 5)OBX 3-2OBX
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset VF VT
Monitor Episode
Count
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset VT Monitor
Episode Count
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset AF AT
Monitor Episode
Count
Parameter
Type
when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754886^MDC_IDC_ENUM_EPISODE_TYPE_Epis_PeriodicEGM^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754887^MDC_IDC_ENUM_EPISODE_TYPE_Epis_PatientActivated^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754888^MDC_IDC_ENUM_EPISODE_TYPE_Epis_Other^MDC
MDC_IDC_STAT_EPISODE_RECENT_COUNT738000
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset Periodic
Episode Count
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset Patient
Activated Episode
Count
Encounter
Measured
Tachycardia
Detection Counters
Since Last Counter
Connectivity Guide | HL7 Integration | 79
PaceartIDCO
3-1
Parameter NameSupported Values (OBX 5)OBX 3-2OBX
Reset Other
Episode Count
MDC_IDC_STAT_EPISODE_RECENT_COUNT_DTM738016
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset Start Date
MDC_IDC_STAT_EPISODE_RECENT_COUNT_DTM_START738017
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset Start Date
MDC_IDC_STAT_EPISODE_RECENT_COUNT_DTM_END738018
Measured
Tachycardia
Detection Counters
Since Last Counter
Reset End Date
Parameter
Type
DateTimeEncounter
DateTimeEncounter
DateTimeEncounter
when 737984^MDC_IDC_STAT_EPISODE_VENDOR_TYPE^MDC has OBX-5 value of 773124^STJ-Epis_VT1^MDC
MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032
when 737984^MDC_IDC_STAT_EPISODE_VENDOR_TYPE^MDC has OBX-5 value of 773125^STJ-Epis_VT2^MDC
Paceart and CareLink integrate with the HL7 protocol for outgoing messages from Paceart and CareLink to
an external system by mapping a parameter and a parameter type to HL7 values. This section describes
outbound message mapping.
Outbound MSH Message Segments
The HL7 MSH (Message Header) segment is present in every HL7 message type and defines the message's
source, purpose, destination, and certain syntax specifics like delimiters (separator characters) and character
sets.
ComponentFieldSource of Data or Literal Value
N/AMSH-1|
N/AMSH-2^~\&
1MSH-3Paceart
1MSH-4Medtronic
N/AMSH-7Local date and time in the format YYYMMDDhhmmss
1MSH-9ORU
2MSH-9R01
3MSH-9ORU_R01
N/AMSH-10Message ID in the format YYYYMMDDhhmmss######
1MSH-11P
1MSH-122.6
N/AMSH-15AL
N/AMSH-16NE
1MSH-21IHE_PCD_ORU_R01
2MSH-21IHE PCD
3MSH-211.3.6.1.4.1.19376.1.6.1.9.1
4MSH-21ISO
84 | Connectivity Guide | HL7 Integration
Outbound PID Message Segments
The PID (Patient Identification) segment provides important identification information about the patient and
is used as the primary means of communicating the identifying and demographic information about a patient
between systems.
OccurrenceComponentFieldParameter TypeParameter
2..211PID-3String 50Patient ID Value
11PID-5String 50Patient Last Name
12PID-5String 50Patient First Name
13PID-5String 1Patient Middle Initial
1N/APID-7DateTimePatient Birth Date
1N/APID-8ENUMPatient Gender
11PID-11String 50Patient Address Line 1
12PID-11String 50Patient Address Line 2
13PID-11String 50Patient Address City
Outbound PV1 Message Segments
The PV1 (Patient Visit) segment is used by registration applications to communicate information on a
visit-specific basis.
ID
14PID-11String 10Patient Address State
15PID-11String 10Patient Address Postal Code
16PID-11String 50Patient Address Country
11PID-13String 20Patient Phone Number
14PID-13String 100Patient Email Address
11PID-14String 20Patient Fax Number
11PID-29DateTimePatient Date of Death
11PID-30BooleanDeath Indicator
The OBR (Observation Request) segment transmits information about an exam, diagnostic study/observation,
or assessment that is specific to an order or result.
Parameter
and Time
OccurrenceSub-ComponentComponentFieldParameter
Type
N/AN/A1OBR-3String 32Encounter Key
N/AN/A1OBR-4ENUMEncounter Type
N/AN/A4OBR-4String 20Encounter Type
N/AN/A5OBR-4String 20Encounter Type
N/AN/A6OBR-4String 20Encounter Type
N/AN/A1OBR-7DateTimeEncounter Date and Time
N/AN/A1OBR-8DateTimeEncounter Signature Date
N/AN/A1OBR-16String 6Provider Code
N/AN/A2OBR-16String 50Provider Last Name
N/AN/A3OBR-16String 50Provider First Name
N/AN/A4OBR-16String 1Provider Middle Initial
N/AN/A5OBR-16String 20Provider Credentials
1
N/AN/A1OBR-25String 1Encounter Lock
N/AN/A1OBR-26String 32Encounter Parent Key
N/AN/A1OBR-28String 6Provider Code
N/AN/A2OBR-28String 50Provider Last Name
N/AN/A3OBR-28String 50Provider First Name
N/AN/A4OBR-28String 1Provider Middle Initial
N/AN/A5OBR-28String 20Provider Credentials
N/A11OBR-32String 6Provider Code
N/A21OBR-32String 50Provider Last Name
N/A31OBR-32String 50Provider First Name
N/A41OBR-32String 1Provider Middle Initial
N/A51OBR-32String 20Provider Credentials
1
In Paceart, if Encounter Lock is false, then the value is "P" for preliminary. If Encounter Lock is true, then the
value is "F" for final. In CareLink, when an encounter is first sent to the EHR the Encounter Lock value is "F"
for final. If subsequent values are sent then the Encounter Lock value is "C" for corrected.
86 | Connectivity Guide | HL7 Integration
OBR:4 Coded Elements
The OBR:4 segment maps the following values to the IDCO Profile values. The items below identify the
referenced Universal Service Identifiers.
CareLink integrations will only export the "REMOTE" value.
Outbound NTE Message Segments
The NTE segment is an optional segment following the OBR and is used to provide notes and comments.
The OBX segment is primarily used to carry key clinical observation and result reporting information within
report messages.
Nonconforming and discriminator OBX values
Each OBX message segment has a value to specify nonconforming values. An OBX-8 value of "NC-PA"
means that the data was nonconforming in Paceart or CareLink. An OBX-8 value of "NC-IDCO" means that
the data does not conform to the IDCO profile definition for the data.
The OBX-8 value is also used to specify a discriminator value for numerical data. For example, a numerical
message segment allows the less-than (<) and greater-than (>) symbols, but not the less-than or equal to
(<=) and greater-than or equal to (>=) symbols.The following segment is for valid values of the number:
While the following segment is for nonconforming values of the number:
Connectivity Guide | HL7 Integration | 87
Parameter
OBX-8OBX-6OBX-3OBX-2Parameter
type
>=^NC-IDCO,
<=^NC-IDCO
Programmed
Bradycardia
Automatic
NMNumericEncounter
731456^MDC_IDC_
SET_BRADY_AT_
MODE_SWITCH_
{beats}/min^
heartbeats per
minute^MDC
RATE^MDC
Mode Switch
Therapy Pacing
Rate
Enumerations
For OBX message segments that have a Parameter Type of ENUM, there are multiple OBX-5 values for
each possible value of the enumeration.These values are not listed in the OBX message segment tables.