Medtronic MDTCSG2V4A Technical Manual
MAINSPRING®DATA EXPRESS
MDTCSG2 version 4.0
Mainspring®Data Express Connectivity Guide
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
Contents
Mainspring Data Express.............................................................................................................5
Mainspring Data Express Software Prerequisites.................................................................8
Installing Mainspring Data Express.........................................................................................11
Paceart Integration.......................................................................................................................14
CareLink Integration ...................................................................................................................28
Connectivity Guide | Contents | 3
Explanation of symbols.............................................................................................................5
Indications.................................................................................................................................6
Precautions...............................................................................................................................6
Contraindications......................................................................................................................6
Mainspring Data Express Authorized Users..............................................................................7
Technical Support......................................................................................................................7
Installation Prerequisites...........................................................................................................8
Installing and Configuring MS Message Queuing for Windows 7...................................8
Installing and Configuring MS Message Queuing for Windows Server 2003..................9
Installing and Configuring MS Message Queuing for Windows Server 2008..................9
Installing and Configuring MS Message Queuing for Windows Server 2008 R2............9
Installing the Java Runtime Environment........................................................................9
Installing .Net 3.5 Framework Service Pack 1...............................................................10
Stopping the Connected Systems Gateway Service....................................................10
Automatically Starting the Connected Systems Gateway After Restart...................................13
Log File Configuration.............................................................................................................13
General Paceart Settings........................................................................................................14
Configuring Paceart Settings........................................................................................14
Paceart Integration Configuration Values......................................................................15
One-Stop Scheduling..............................................................................................................15
One-Stop Scheduling Prerequisites.............................................................................16
Configuring One-Stop Scheduling................................................................................16
Troubleshooting One-Stop Scheduling.........................................................................18
Paceart Optima HL7 Integration..............................................................................................19
Configuring Paceart HL7 Integration.............................................................................20
Troubleshooting Paceart HL7 Integration......................................................................24
Local Data Interface................................................................................................................24
Local Data Interface Extended Configurations.............................................................25
Local Data Interface certificate installation...................................................................25
Enabling a data import source......................................................................................26
Remote Data Interface............................................................................................................26
Configuring Remote Data Interface..............................................................................26
Enabling remote data acquisition in Paceart.................................................................27
CareLink Report Export...........................................................................................................28
Configuring CareLink Report Export.............................................................................28
4 | Connectivity Guide | Contents
Enabling and Verifying Mainspring Report Export........................................................31
Troubleshooting Report Export.....................................................................................32
CareLink EHR Integration........................................................................................................32
Configuring EHR Integration.........................................................................................32
Installing and configuring Mirth Connect.......................................................................36
Troubleshooting EHR Integration..................................................................................37
HL7 Integration..............................................................................................................................38
Inbound Messages..................................................................................................................38
Inbound Patient Administration Messages (ADT).........................................................38
Inbound Patient Administration Message Segments....................................................39
Inbound Scheduling Messages (SIU)...........................................................................42
Inbound Scheduling Segments....................................................................................43
Inbound Observation Requests (ORU).........................................................................46
Inbound Observation Requests Segments...................................................................46
Outbound Messages in Schema 9.0.......................................................................................83
Outbound MSH Message Segments............................................................................83
Outbound PID Message Segments..............................................................................84
Outbound PV1 Message Segments.............................................................................85
Outbound PV2 Message Segments.............................................................................85
Outbound OBR Message Segments............................................................................85
Outbound NTE Message Segments.............................................................................86
Outbound OBX Messages............................................................................................86
Outbound Messages Paceart Schema 6.0............................................................................195
Outbound MSH Message Segments..........................................................................196
Outbound PID Message Segments............................................................................197
Outbound PV1 Message Segments...........................................................................197
Outbound OBR Message Segments..........................................................................197
Outbound OBX:3 Message Segments.......................................................................198
Identifiers....................................................................................................................202
XML Schema...............................................................................................................................215
Parameter valid values..........................................................................................................215
XML export............................................................................................................................218
XML Domain Mapping................................................................................................218
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 streamlinethe 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 OptimaSystem, referto the Paceart Optima SystemSoftware 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 thePaceart Database if you are using SQLServer 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 3.5 Service Pack 1.
• 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 Server 2003
1. Open the Control Panel.
2. Double-click Add or Remove Programs.
3. Click Add/Remove Windows Components.
4. Select Application Server from the Windows Components Wizard dialog.
5. Click Details.
6. Select Message Queuing.
7. Click Details.
8. Select Core Functionality from the list of Subcomponents of Message Queuing.
9. Click OK on the Message Queuing dialog.
10. Click Next on the Windows Components Wizard dialog.
11. When the installation completes click Finish.
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.
1. Click Start > Programs > Administrative Tools > Server Manager.
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 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.
10 | Connectivity Guide | Mainspring Data Express Software Prerequisites
The installation wizard starts.
3. Click Install.
A progress window is displayed.
4. Once the installation is complete, click Close.
Installing .Net 3.5 Framework Service Pack 1
You must have .Net 3.5 Framework Service Pack 1 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 dotnetfx35setup.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. You can
select multiple features under Paceart Integration section but you can only select one feature under
CareLink Integration section.
The configuration window for the feature you selected is displayed.
8. Make your configurationchanges and click OK. Refer to thefollowing 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 Systems
Gateway\Logs\.
• For 64 bit operating systems the location is C:\Program Files (x86)\Medtronic\Connected
Systems 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:
• One-Stop Scheduling: 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 IHEIDCO 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.
• Remote Data Interface: Allows you to configure the service that imports patient session data from remote
sources, such as the CareLink Network.
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 System Account
Settings on the feature-specific tab. To use different External System Accounts for each feature uncheck the
Use General Paceart External System Account Settings on the feature-specific tab.
Paceart Web Services
When installing the Paceart server a certificate is bound to either the host name or IP address of the server. If
the certificate is bound to the IP address of the server, then the IP address must be used in each of these
settings. If the certificate is bound to the Hostname of the server, than the Hostname must be used for these
settings.
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:
• One-Stop Scheduling
• HL7 Integration
• Local Data Interface
• Remote Data Interface
The Paceart Integration configuration window is displayed.
3. In the General Paceart Settings section, replace "localhost" with the hostname or the IP address of the
server and the port number in each of the Paceart Web Services paths. When you installed Paceart a server
certificate was bound either to the host name or the IP address of the sever. You must use either the IP or
hostname for these settings, depending on what the certificate is bound to in your configuration.
Connectivity Guide | Paceart Integration | 15
For example, for the PDI Authentication Service Site using a hostname bound certificate, change
http://localhost/Paceart.Services.Hosting/AuthenticationService.svc to
http://hostname:333/Paceart.Services.Hosting/AuthenticationService.svc where
hostname is the name of the server and the port number is 333. The server needs to run a port other than
443 and should be changed to 333.
4. Click OK.
Paceart Integration Configuration Values
This table explains the fields on the General Paceart Settings configuration window.
ExplanationField Name
General Paceart External System Account
Username
Password
Paceart Web Services
PDI Authentication Service Site
PDI Encounter Management Service Site
PDI Outbound XML Export Service Site
PDI Outbound Encounter Request Service Site
PDI Patient Management Service Site
PDI Appointment Management Service Site
PDI Outbound Appointment Service Site
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 URL to access the Authentication Service of the Paceart Domain
Interface.
The URL to access the Encounter Management Service of the Paceart
Domain Interface.
The URL to access the Outbound XML Export Service of the Paceart
Domain Interface.
The URL to access the Outbound Encounter Request Service of the
Paceart Domain Interface.
The URL to access the Patient Management Service of the Paceart
Domain Interface.
The URL to access the Appointment Management Service of the
Paceart Domain Interface.
The URL to access the Outbound Appointment Service of the Paceart
Domain Interface.
One-Stop Scheduling
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.
16 | Connectivity Guide | Paceart Integration
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.
One-Stop Scheduling Prerequisites
Before you configure One-Stop Scheduling 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 One-Stop Scheduling 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 havean 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 One-Stop Scheduling
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 One-Stop Scheduling and click
Configurations.
Connectivity Guide | Paceart Integration | 17
The Paceart Integration window is displayed.
3. On the One-Stop Scheduling tab enter the applicable values for your CareLink implementation. Refer to
the One-Stop Scheduling Configuration Values table for more explanation on the fields.
4. Click OK.
One-Stop Scheduling Configuration Values
This table explains the fields on the One-Stop Scheduling configuration tab.
ExplanationField name
CareLink Settings
CareLink Scheduling Service
CareLink Scheduling Service Site
External System Account Name
External System Authorization
Code
Send Patient First Name
Send Patient Gender
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 External
System 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 Gender value is sent to CareLink. If "True",
it will be used by CareLink for patient matching. The default value is "True".
Send Patient Middle Name
Paceart Settings
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".
18 | Connectivity Guide | Paceart Integration
ExplanationField name
Patient ID Type Description
Appointment Resource
The Paceart Patient ID Type Description to associate with the CareLink Remote
Patient ID. The default value is "Default".
The Paceart Appointment Resource to associate with CareLink remote appointments.
The default value is "Default Resource".
Troubleshooting One-Stop Scheduling
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.
• 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 One-Stop Scheduling tab of the Paceart
Integration dialog. The CareLink hosting system must match what was entered in the Remote Data
Interface tab. To verify this fact the Remote Data Interface feature should be selected in the Medtronic
Mainspring Data Express window.
• Verify that the Connected Systems Gateway service was started.
Connectivity Guide | Paceart Integration | 19
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".
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
20 | Connectivity Guide | Paceart Integration
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 System
Software 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 Inbound
Inbound Communication Queue
HL7 Outbound
Outbound Sending Application Namespace ID
Outbound Sending Application Universal ID
Outbound Sending Application Universal ID Type
Used by the implementation to communicate with a third-party HL7
engine.
The default value is "HL7Source". Do not change this value.
This field uniquely identifies the sending application among all other
applications within the network enterprise. The network enterprise
consists of all those applications that participate in the exchange of
HL7 messages within the enterprise. Entirely site-defined.
This information is included in the MSH segment 3, component 1.
The default value is "Paceart".
This field uniquely identifies the sending application among all other
applications within the network enterprise. The network enterprise
consists of all those applications that participate in the exchange of
HL7 messages within the enterprise. Entirely site-defined.
This information is included the MSH segment 3, component 2.
This field uniquely identifies the sending application among all other
applications within the network enterprise. The network enterprise
consists of all those applications that participate in the exchange of
HL7 messages within the enterprise. Entirely site-defined.
Outbound Sending Facility Namespace ID
This information is included the MSH segment 3, component 3.
This field further describes the sending application. Entirely
site-defined.
This information is included the MSH segment 4, component 1.
The default value is "Medtronic".
Connectivity Guide | Paceart Integration | 21
ExplanationField name
Outbound Sending Facility Universal ID
Outbound Sending Facility Universal ID Type
Outbound Receiving Application Namespace ID
Outbound Receiving Application Universal ID
Outbound ReceivingApplication Universal ID Type
This field further describes the sending application. Entirely
site-defined.
This information is included the MSH segment 4, component 2.
This field further describes the sending application. Entirely
site-defined.
This information is included the MSH segment 4, component 3.
This field uniquely identifies the receiving application among all other
applications within the network enterprise. The network enterprise
consists of all those applications that participate in the exchange of
HL7 messages within the enterprise. Entirely site-defined.
This information will be in MSH, field 5, component 1.
This field uniquely identifies the receiving application among all other
applications within the network enterprise. The network enterprise
consists of all those applications that participate in the exchange of
HL7 messages within the enterprise. Entirely site-defined.
This information will be in MSH, field 5, component 2.
This field uniquely identifies the receiving application among all other
applications within the network enterprise. The network enterprise
consists of all those applications that participate in the exchange of
HL7 messages within the enterprise. Entirely site-defined.
Outbound Receiving Facility Namespace ID
Outbound Receiving Facility Universal ID
Outbound Receiving Facility Universal ID Type
Outbound Processing ID
This information will be in MSH, field 5, component 3.
This field identifies the receiving application among multiple identical
instances of the application running on behalf of different organizations.
Entirely site-defined.
This information will be in MSH, field 6, component 1.
This field identifies the receiving application among multiple identical
instances of the application running on behalf of different organizations.
Entirely site-defined.
This information will be in MSH, field 6, component 2.
This field identifies the receiving application among multiple identical
instances of the application running on behalf of different organizations.
Entirely site-defined.
This information will be in MSH, field 6, component 3.
Defines in the MSH header whether the message is part of a
production, training, or debugging system. "D"=Debugging,
"P"=Production, "T"=Training.
This information will be in MSH, field 11, component 1.
The default value is "P".
22 | Connectivity Guide | Paceart Integration
ExplanationField name
Outbound Processing ID Mode
Outbound HL7 Version
Outbound Include Episode Observations
Outbound Patient Visit Patient Class
Outbound Communication Queue
Include Nonconforming Data
Defines in the MSH header the processing mode. "A"=Archive,
"R"=Restore from archive, "I"=Initial load, "T"=Current processing
transmitted at intervals.
This information will be in MSH, field 11, component 2.
The version of HL7 listed in the HL7 message header.
This information will be in MSH, field 12.
The default value is "2.6".
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).
The default value is "U" and corresponds to a Patient Class of
Unknown. This information will be in PV1, field 2.
Used by the implementation to communicate with a third-party HL7
engine.
The default value is "HL7Destination".
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
Include Medtronic OBX Segments
Include PV2 Segment
Paceart
Paceart XML Version
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".
Boolean valueproviding an option to include Medtronic OBX segments
in the HL7 message sent to the receiving system. Inclusion ofthis 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.
The default value is "9.0".
Connectivity Guide | Paceart Integration | 23
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 Systems
Gateway\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 you would
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 license
string 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.
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. Run
the 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.
24 | Connectivity Guide | Paceart Integration
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. 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.
• 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 messagethat says "Programmer
Acquisition service cannot start", you need to change the Corepoint Integration Engine port value.
1. Click Start > Programs > Corepoint Health > Corepoint Integration Engine > Corepoint Integration
Engine - Configuration.
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.
Local Data Interface Extended Configurations
This table explains the fields on the LDI Extended Configurations window.
ExplanationField name
Connectivity Guide | Paceart Integration | 25
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.
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.
26 | Connectivity Guide | Paceart Integration
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.
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 | 27
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
System Account Name
System Account Access Code
Data Service
Data Service Site
Manufacturer Name
Encounter Type
Clinic Request Start Date
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 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 manufacturer name of the data provided by a specific system. For
CareLink, this value is "Medtronic".
The name of the externalsystem. For CareLink, this value is "CareLink".Application ID
The type of data provided by a specific system. For CareLink, this
value is "Remote".
The value indicating the start date for requests from the external
system.
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. Double-click on the Medtronic Paceart Optima icon on your desktop.
2. Log in to Paceart.
3. Click Administration > Connectivity.
4. Click the CareLink Remote Encounter Acquisition tab.
5. Click Edit.
The CareLink Remote Encounter Acquisition dialog is displayed.
6. Select Active to enable CareLink remote data acquisition.
7. Select Nightly Active to enable nightly CareLink remote data acquisition. This option is only available if
you have selected Active.
8. Click Save.
Paceart will now be enabled for remote data acquisition.
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.
Loading...