How it Works
Medtronic
Loading...
MDTCSG2034
Technical Manual
270 pgs1.68 Mb0
Table of contents
Loading...

Medtronic MDTCSG2034 Technical Manual

Mainspring Data Express™
MDTCSG2 Version 11.0 Connectivity Guide
Technical Reference Manual
Medtronic, Medtronic with rising man logo, and Medtronic logo are trademarks of Medtronic. Third-party trademarks (“TM*”) belong to their respective owners. The following list includes trademarks or registered trademarks of a Medtronic entity in the United States and/or in other countries.
CareLink™, Export™, Integrity™, Medtronic CareLink™, Paceart Optima™, Paceart™, Vitatron™

Contents

3 Installing Mainspring Data Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Automatically Starting the Connected Systems Gateway After Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3 Log File Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4 Paceart System Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 About Paceart System Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 General Paceart System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3 CareLink Scheduling Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.4 Paceart Optima System HL7 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.5 Local Data Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.6 Local Data Interface Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.7 CareLink Transmission Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.8 Mainspring Health Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5 CareLink Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.1 About CareLink Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2 CareLink Report Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3 CareLink EHR Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6 HL7 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.1 About HL7 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.2 Inbound Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.3 Outbound Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.4 HL7 Update Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
7 IDCO 1.1 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
8 Uninstalling Mainspring Data Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
3

1 About Mainspring Data Express

1.1 Mainspring Data Express

Mainspring – because 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 andpatient 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.

1.2 Explanation of symbols

Consult instructions for use
Manufacturer
Lot number
Reorder 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.
Storage temperature limit
Transit temperature limit
Humidity Limitation
Software
Model number
Manufactured in
Authorized Representative in the European Community

1.3 Indications

Mainspring Data Express is an optional component of the Medtronic CareLink Network and the Paceart Optima System. Mainspring Data Express can be used to provide data integration between disparate systems, using a defined mapping.
For more information on the Paceart Optima System, refer to the Paceart Optima System Software User Manual or the Paceart Optima System Online Help.

1.4 Precautions

Mainspring Data Express USBs must be operating in an environment within the following conditions :
Storage Environment
Temperature -20°C (-4°F) to +70°C (158°F) Relative Humidity 20% to 75%
Mainspring Data Express USBs must be operating in an environment within the following conditions :
4
Operating Environment
Temperature 0°C (32°F) to +65°C (149°F) Relative Humidity 20% to 75%
Call customer service or your biomedical department for service and repairs.

1.5 Contraindications

No known contraindications.

1.6 Mainspring Data Express Authorized Users

Medtronic representatives provide the Mainspring Data Express orientation and training materials at the timeof the installation. Users should be familiar with the Mainspring Data Express documents before using Mainspring Data Express.

1.7 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.

2 Mainspring Data Express software prerequisites

2.1 Installation prerequisites

Before you install and configure the Mainspring Data Express software you must install and Configure MS Message Queuing.
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 SystemExternal System Account User and Role. For instructions refer to the Paceart Optima System online help.
• Install and configure MS Message Queuing.
• If you will be using the EHR Integration feature, install the Java Runtime Environment version 1.8 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 softwarewill import any existing configurations. For example, if you have an existing Paceart System-CareLink scheduling integration configuration, the settings will be saved and used in the new version of the Mainspring Data Express software.

2.1.1 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.

2.1.2 Installing and Configuring MS Message Queuing for Windows 10

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.
1. Open the Control Panel.
2. Click Programs, and then under Programs and Features, click Turn Windows features on or off.
3. Under the Microsoft Message Queue (MSMQ) Server option, check the Microsoft Message Queue (MSMQ) Server option. This enables all of the MSMQ Server Core subfeatures.
4. Click OK.
5. If you are prompted to restart the computer, click Restart now to complete the installation.
5

2.1.3 Installing and Configuring MS Message Queueing for Windows Server 2012, 2012 R2, 2016, and 2019

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.
3. Click Next until the Features page opens.
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.

2.1.4 Installing Open JDK

If you will be installing the EHR Integration feature, you will need to install Open JDK version 16 or higher. You do not need to be connected to the internet to install the files.
1. Insert the Mainspring Data Express software USB drive into your USB port.
2. Browse to Resources\Mirth on the USB and right-click on openjdk-16.0.1_windows-x64_bin.zip to extract the files needed.
3. Select a location to extract the files. This location will be needed later on, take note on where these files are being extracted to. A progress window is displayed.
4. Once the files have been extracted, close any file system windows still open.

3 Installing Mainspring Data Express

3.1 Installation steps

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 and click CSGInstall.exe on the installation USB.
2. Click Next.
3. If there are any prerequisites that must be installed, they are displayed in a list. Select and then click Install for each of the prerequisites. You may need to restart your computer depending on which prerequisites are installed.
4. On the License Agreement step, click Next.
6
5. 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.
7
6. Click Next.
7. Click Install. A progress bar shows the installation progress.
8. Select Launch Medtronic Mainspring Data Express and then click Finish to exit the installation wizard and open the Medtronic Mainspring Data Express window.
8
9. 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.
9
10. Make your configuration changes and click OK. Refer to the following sections for information on configuring each feature. The configuration window closes.
11. Click OK to close the Medtronic Mainspring Data Express window.
If you selected EHR Integration for the first time, follow the installation steps in Section 5.3.2, Installing and configuring Mirth Connect, page 30 of this document to install and configure Mirth Connect.

3.2 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.
10

3.3 Log File Configuration

The default location for log files is C:\Medtronic\Connected Systems Gateway\Logs.
The default log file retention count is 10. You can save up to 99 log files.

4 Paceart System Integration

4.1 About Paceart System Integration

The Paceart System Integration section of Mainspring Data Express has the following features:
• CareLink Scheduling Integration: Allows you to exchange scheduling data between the CareLink Network and the Paceart System.
• 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.
• Local Data Interface Plus: Allows you to configure the service that receives patient session data transmitted from local sources using a newer security model.
• CareLink Transmission Integration: Allows you to configure the service that imports patient session data into the Paceart System from CareLink.

4.2 General Paceart System Settings

General Paceart System 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 System features, select the Use General Paceart External System Account Settings check box on the feature-specific tab. To use different external system accounts for eachfeature, 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 System Application Server
These settings contain information about the computer on which the Paceart Optima System Application Serveris installed. Mainspring Data Express communicates with the Paceart Optima System Application Server using this hostname and port to exchange data between the Paceart System and external sources.

4.2.1 Configuring Paceart System Settings

General Paceart System 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
• Local Data Interface Plus
• 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.
• Update the Username and Password for the external system account set up in the Paceart System.
• Change the Hostname to the domain name or IP address of the computer on which the Paceart Optima System Application Server is installed.
• Change the Port to the port number the Paceart Optima System Application Server uses on that computer.The default value is 333.
4. Click OK.
11

4.2.2 Paceart System Integration Configuration Values

This table explains the fields under General Paceart Settings on the Paceart Integration configuration window.
Field Name Explanation General Paceart External System Account
Username The Paceart System External System Account username. Thi-
susername is defined in the Paceart System on the External Sys­tem Accounts tab.
Password The Paceart System External System Account password. This-
password is defined in the Paceart System on the External Sys­tem Accounts tab.
Paceart Optima Application Server
Hostname The domain name or IP address of the computer on which the
Paceart Optima System Application Server is installed.
Port The port number the Paceart Optima System Application Server
domain interface uses. The default value is 333.

4.3 CareLink Scheduling Integration

The Paceart System-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 the Paceart System, it will be sent to CareLink.
The Paceart System 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 the Paceart System. Once the Paceart System is updated to reflect the CareLink Network appointment, the appointmentis owned by the Paceart System.
If a remote appointment is created or modified in the Paceart System, the appointment is automatically created or updated in CareLink. Ownership of the appointment remains with the Paceart System.
The Paceart System receives appointment status information that reflects the last known status as reportedby CareLink. The remote status is displayed in patient appointment information on the Paceart System. The Paceart System records the completion and failure status details of this information in its log. The Paceart System 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 the Paceart System, 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 MedtronicCareLink Network.

4.3.1 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 the Paceart System patient records and appointments meet the following criteria:
• The Paceart System patient record must have a birth date, a patient ID number, and a patient ID number type.
• Appointments created or updated in the Paceart System 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.
4.3.1.1 Paceart System/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
12
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.
4.3.1.2 Paceart System/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 System 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.

4.3.2 Configuring CareLink Scheduling Integration

1. To start Mainspring Data Express, go to Start > Programs > MedtronicMainspring Data Express > MedtronicMainspring 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.
4. Click OK.
4.3.2.1 CareLink Scheduling Integration Configuration Values
This table explains the fields on the CareLink Scheduling Integration configuration tab.
Field name Explanation CareLink Settings
CareLink Scheduling Service The name of the CareLink scheduling service that the adapter will use. The defaultvalue
is "Endpoint_CSA_basicHttpsBinding".
CareLink Scheduling Service Site 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
External System Account Name 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.
External System Authorization Code The account authorization code that will be used to authenticate the CareLink UserID
with the CareLink Scheduling service. This authorization code is created andconfigured on the External System Accounts tab on the CareLink website.
Send Patient First Name 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".
Send Patient Middle Name 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".
Send Patient Gender 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".
Paceart Settings
Patient ID Type Description 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".

4.3.3 Troubleshooting CareLink Scheduling Integration

Troubleshooting scheduling connectivity problems.
CareLink
• Verify that the CareLink account used to connect to Connected Systems Gateway 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.
13
• If the CareLink clinic has sub-clinics, verify that the CareLink account used to connect to the MedtronicMainspring Data Express has access to the sub-clinics’ patients integrated with the Paceart System.
• 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 the Paceart External System Account password associated with the Mainspring Data Express user.
• Verify that the patient’s Demographics tab in the Paceart System 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 System 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 selectedin the Medtronic Mainspring Data Express window.
• Verify that the Connected Systems Gateway service was started.

4.4 Paceart Optima System HL7 Integration

Viewing and Resolving Errors
In the Paceart Optima System, 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 System user or workgroup to resolve the issue.
For a complete list of Activity Log Results, refer to the Paceart Optima System Software User Manual or thePaceart Optima System online Help.
Paceart Optima System Patient ID Configuration
In the Paceart Optima System, a patient can have multiple patient IDs. You can configure patient IDs on the Administration > Demographics > Patient ID Type tab. Matching an inbound patient ID involves matching both the ID number and the ID type. By
default, the Paceart System matches the first occurrence of the PID-3segment 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 the Paceart System with an "EMR" type ID and a patient ID number of "1335579".
Paceart Optima System Patient Matching Configuration
In the Paceart Optima System, you must configure patient matching on the Administration > Connectivity Management > Patient Matching Configuration tab.
Patient matching is initially based on the patient ID only. You can configure a second level of patient matching in the Verify Patient Match Configuration section. If a patient match cannot be made using the patient ID, matching can also be configured based on patient demographic information in the Demographics Only Match Configuration section. These levels of matching can determine when a new patient is created in the Paceart System, when an error is logged, and when a work item is created.
For more information on configuring Paceart Optima System patient matching, refer to the Paceart Optima System Software User Manual or the Paceart Optima System online Help.

4.4.1 Configuring Paceart HL7 Integration

1. 1. To start Mainspring Data Express, click Start > Programs > MedtronicMainspring Data Express > MedtronicMainspring Data Express
2. 2. In the MedtronicMainspring Data Express window, select HL7 Integration and click Configurations. The Paceart Integration configuration window is displayed.
14
3. 3. In the HL7 Integration tab, enter the values for your configuration.
4. 4. Click OK to close the Paceart Integration configuration window.
4.4.1.1 HL7 Integration Configuration Values
This table explains the fields on the HL7 Integration configuration tab.
Field name Explanation HL7 Outbound
Outbound Include Episode Observations Boolean value providing an option to include episode data in the HL7 mes-
sage 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).
Include Nonconforming 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. The default value is "True".
Include IDCO Nonconforming Data 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".
Include Medtronic OBX Segments 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".
Include PV2 Segment 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".
IDCO Message Version The version of IDCO used to generate the HL7 message. Valid values are
"1.0" or "1.1".
Paceart
Paceart XML Version The version of Paceart XML that will be exported from the Paceart System to
HL7. This value is for reference only and cannot be edited.

4.4.2 Installing the Corepoint Integration Engine

2016.3 or earlier installed, you need to remove it and install the Corepoint Integration Engine.
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 type of authentication you want and click Next.
6. Specify the administrator password or Windows user depending on what authentication type was selected.
7. Click Install to install the Corepoint Integration Engine.
8. 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.
9. Enter the username and password you specified in step 6, and then click OK.
10. On the LicenseManager window, click License wizard. The License Wizard starts.
11. Click Next.
12. Select the Request a license using a product key option, and then click Next.
15
13. 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"
14. On the Connection and login information dialog box, enter the Web login provided by Operations and Technical Services and connection details and click Next.
15. Click Connect to contact Corepointhealth.com to obtain your license.
16. After you have connected to Corepointhealth.com click Next.
17. Click Finish.
18. On the LicenseManager window, click Exit.
19. 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 > CorepointHealth > Corepoint Integration Engine > Corepoint Integration Engine - Administration.
20. 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.
21. Ensure that the Integration Engine Service is started.
22. Close the Corepoint Integration Engine Administration Console window.
23. Open the Corepoint Integration Engine Configuration console by clicking Start > All Programs > CorepointHealth > Corepoint Integration Engine > Corepoint Integration Engine - Configuration.
24. 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.
25. Click File > Import. The Open File window is displayed.
26. Navigate to the configuration file folder at C:\Program Files\Medtronic\Connected SystemsGateway\HL7SubSystem. The Import selected components window is displayed.
27. Double-click the HL7 Source and Destination Transformation.nix file. The Import selected components window is displayed.
28. Select all of the components and click Import.
29. Click OK after the components have been loaded.
30. Commit the update to the Corepoint Integration Engine by clicking Version > Commit All... The Commit Changes dialog box is displayed.
31. Click Commit and Activate at the bottom of the dialog box.
32. 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.
33. Close the Corepoint Integration Engine Configuration window.

4.4.3 Troubleshooting Paceart HL7 Integration

Troubleshooting Paceart HL7 integration problems.
Paceart
• Verify the Paceart External System Account password associated with the Mainspring Data Express user.
• Verify that the Paceart System 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.
4.4.3.1 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.
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.
16
3. Change the port value.
4. Click OK.

4.5 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.

4.5.1 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.

4.5.2 Local Data Interface Extended Configurations

This table explains the fields on the LDI Extended Configurations window.
Field name Explanation
Manufacturer Name The manufacturer name of the data provided by a specific sys-
tem. For example, "Medtronic".
Encounter Type The type of data provided by a specific system. The default value
is "InClinic".
Username The username for a user-defined local data interface extended
configuration.
Password The password for a user-defined local data interface extended
configuration.

4.5.3 Local Data Interface certificate installation

The digital certificate allows a secure connection to be established between a data import source and the Paceart System. 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.
4.5.3.1 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. In the Public Key Information section, select the desired key length.
5. 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.
6. Click Export Certificate Request to a File.
7. 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.
8. Once the file has been successfully exported, click OK.
9. Send an e-mail with the exported certificate request file to Paceart Technical Support at CertSupport@Medtronic.com.
10. 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.
11. Save the certificate file to a location that is accessible from the Paceart System computer. The default filename is C: \PaceartGatewayCertificate.MCert.
17
12. Click Install Certificate.
13. Find and select the file using the standard Windows dialog and click Open.
14. 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.

4.5.4 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 the Paceart System.

4.6 Local Data Interface Plus

The Local Data Interface Plus allows you to configure the service that receives patient session data transmitted from local sources using a newer security model and technologies. You can start and stop the service, configure advanced options, and enable or disable transmissions from enabled clients.

4.6.1 Updating the Local Data Interface Plus Port Number

The value in the Port field on the Local Data Interface Plus 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 clients connecting to the Local Data Interface Plus. This value cannot be the same value that is configured for the Local Data Interface if that feature is also enabled.
1. If needed, change the value in the Port field to match the port configured for the local source. The default value is 334.
2. Click OK to save your changes.

4.6.2 Local Data Interface Plus certificate installation

The digital certificate allows a secure connection to be established between a data import source and thePaceart System. You must complete the certificate installation before you can import data from other sources.
You may select an existing certificate in the personal store on the local computer or generate a certificate request that you will send to a third-party certificate authority. If you generate a certificate request, the third-party certificate authority will return to you the certificate file that you need to import into your system and install.
If you have questions please call Paceart Technical Support.
4.6.2.1 Selecting an existing certificate
1. On the Local Data Interface Plus tab, click Select Existing Cert. A Digital Certificate selection dialog will displayed for the personal store of the local machine.
2. Select the desired Digital Certificate and click OK.
3. If you have completed the installation successfully, the Digital Certificate section will display details about the installed digital certificate. If you receive an error message, call Paceart Technical Support.
4.6.2.2 Installing a new certificate
1. On the Local Data Interface Plus tab, click Create Cert Request. The Export Certificate Request window is displayed.
2. In the Customer Information section, enter your information in the following required fields:
• Organization
• Organizational Unit
• City/Locality
• 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 Plus. The default, and most commonly used, is the fully qualified domain name of the machine.
5. In the Public Key Information section, select the desired key length. Note: Larger public key sizes increase security, but can affect performance.
18
6. Click Export Certificate Request to a File.
7. Select the location where you would like to save the certificate request file. The default file location is C: \PaceartGatewayCertificateRequest.McertReq.
8. Once the file has been successfully exported, click OK.
9. Send the certificate request to the third-party certificate authority to be processed.
10. The third-party certificate authority will then return a certificate file to you. This is typically a *.cer or *.crtfile.
11. Save the certificate file to a location that is accessible from the Paceart System computer.
12. Click Complete Cert Request.
13. Find and select the file using the standard Windows dialog and click Open.
14. If you have completed the installation successfully, the Digital Certificate section will display details about the installedDigital
Certificate. If you receive an error message, call Paceart Technical Support.

4.6.3 Enabling a data import source

You must install the certificate before you can enable a source for data import.
1. Click on the Client ID listed in the Unauthorized Clients table to select it.
2. Verify it is the same Client ID and Username listed on the Clients User Interface.
3. Click Add. The Client ID is added to the Authorized Clients table.
4. Click OK for the changes to take effect. This client is now able to import data to the Paceart System.

4.7 CareLink Transmission Integration

The CareLink Transmission Integration options control how the Paceart Optima System 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 the Paceart System.
The Remote Data Interface service allows patient session data to be imported from Carelink when requested from within the Paceart Optima System. 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 the Paceart Optima System.

4.7.1 Remote Data Interface

The Remote Data Interface allows you to configure the service that imports patient session data from remotesources, 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.
4.7.1.1 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.
19
The Paceart Integration configuration window is displayed.
3. On the Remote Data Interface tab enter the applicable values for your implementation. Refer to the Section 4.7.1.2, Remote Data Interface Configuration Values, page 20 table for more explanation on the fields.
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.
4.7.1.2 Remote Data Interface Configuration Values
This table explains the fields on the Remote Data Interface configuration tab.
Field name Explanation CareLink 1
Data Service The name of the service. The default value is "End-
point_CSA_basicHttpsBinding".
20
Field name Explanation
Data Service Site The URL to access the data service(s) of a specific system. For
CareLink, this is referred to as the Transmission Gateway Serv­ice.
System Account Name The account name used to connect to the CareLink system. This
account name is created and configured on the External Sys- tem Accounts tab on the CareLink website.
System Account Access Code 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.
Manufacturer Name The manufacturer name of the data provided by a specific sys-
tem. For CareLink, this value is "Medtronic".
Application ID The name of the external system. For CareLink, this value is
"CareLink".
Encounter Type The type of data provided by a specific system. For CareLink, this
value is "Remote".
Clinic Request (Days of History) The value indicating how many days of history to request from the
external system. The default value is 7.
4.7.1.3 Enabling remote data acquisition in the Paceart System
After you have configured Remote Data Interface for Mainspring Data Express, you need to enable remotedata acquisition in the Paceart System.
1. Log in to the Paceart System.
2. Use the connectivity tools available in the Paceart System 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 System online help or the Paceart Optima System Software User Manual.

4.7.2 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.
4.7.2.1 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.
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.
4.7.2.2 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 Section 4.7.2.3, CareLink DataBridge Gateway Configuration Values, page 22 table for more explanation on the fields.
21
4. If you receive data from more than one remote CareLink Network system, you must have a separate DataBridge 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.
4.7.2.3 CareLink DataBridge Gateway Configuration Values
This table explains the fields on the Data Bridge Gateway configuration tab.
Field Name Explanation Configuration 1
Description An optional field for entering the name of your configuration. Limit 15 configurations. Data Bridge Service The name of the CareLink Data Bridge service the adapter will use. The default is "End-
point_CSA_basicHttpsBinding"
Data Bridge Service Site 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
External System Account Name
External System Account Authorization Code

4.7.3 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.
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 con­figured on the External System Accounts tab on the CareLink website.
Paceart Integration
• Verify the Paceart External System Account password associated with the Mainspring Data Express user.

4.8 Mainspring Health Interface

The Mainspring Health Interface allows you to configure the service that sends Mainspring health information to the Paceart Optima System. This information includes which Mainspring features are enabled, which of those enabled features are running and which of them are down, and Digital Certificate management messages.

4.8.1 Configuring Mainspring Health Interface

1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express > Medtronic Mainspring Data Express.
In the Medtronic Mainspring Data Express window, if any of the Paceart Integration features are enabled, the Mainspring Health Interface is also enabled.
2. Click Configurations. The Paceart Integration configuration window is displayed.
3. In the Mainspring Health Interface tab, enter the values for your configuration.
4. Click OK to close the Paceart Integration configuration window.

4.8.2 Mainspring Health Interface Configuration Values

This table explains the fields on the Mainspring Health Interface configuration tab.
22
Field Name Explanation
Mainspring Server Name This value is the name of the Windows machine that Mainspring is running on. The
default value is the machine’s short name.

5 CareLink Integration

5.1 About 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.

5.2 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 EHR Export feature with the Export Report feature with the Report Export option 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.

5.2.1 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.
23
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.
24
5. Click OK.
25
5.2.1.1 CareLink Network 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.
Callout num­ber Field name Explanation
1 Description An optional field for entering the name of your configuration. Limit 15 configurations. 2 Data Bridge Service The name of the CareLink reporting service the adapter will use.
The default is "Endpoint_CSA_basicHttpsBinding".
3 Data Bridge Service Site 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"
4 External System Account
Name
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 web- site.
5 External System Account
Authorization Code
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.
6 File Folder Location 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: \\com­puter\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.
7 Use Specified Credentials 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"
26
Callout num­ber Field name Explanation
value indicates that a username and password are not required to access the desti­nation path. The default is "False".
8 Username 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.
9 Password When Use Specified Credentials is "True", this is the password associated to the Win-
dows Username that will be used when accessing the destination file system.
10 Overwrite Existing File(s) 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".
11 Minimum Available Disk
Space

5.2.2 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.
The minimum amount of free space in MB on the destination file system required for the adapter to initialize. The default is "15" MB.

5.2.3 Troubleshooting Report Export

CareLink Report Export
• Verify that the Mainspring Data Express software prerequisites were installed or configured correctly.
• Verify that you have 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.

5.3 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.
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.
27
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.

5.3.1 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. 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 configuration for other clinics.
5. Click OK. You will need to install and configure Mirth Connect.
5.3.1.1 CareLink EHR Integration Configuration Values
This table explains the fields on the CareLink EHR Integration configuration window.
28
Callout num­ber Field name Explanation
1 Description An optional field for entering the name of your configuration. Limit 15 configura-
tions.
2 Data Bridge Service The name of the CareLink Data Bridge service the adapter will use.
The default is "Endpoint_CSA_basicHttpsBinding"
3 Data Bridge Service Site 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.medtronicCare­Link.net/DataBridgeGateway/
DataBridgeGatewayService.svc
4 External System Account
Name
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.
5 External System Account
Authorization Code
The authorization code used to connect to the CareLink website. This authori­zation code is configured on the External System Accounts tab on the CareLink website.
6 Document Folder Location 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.
7 Use Specified Credentials 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".
29
Callout num­ber Field name Explanation
8 Username 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.
9 Password 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 Overwrite Existing File(s) 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".
11 Minimum Available Disk
Space
12 Mirth Inbound Path Specifies a file system path where HL7 messages will be available for Mirth Con-
13 Mirth Error Path The file system path where Mirth is configured to write failed HL7 messages. 14 Minimum Available Disk
Space

5.3.2 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.
1. Browse to Resources\Mirth on the USB and double-click on mirthconnect-3.11.0.b2609-windows-x64.exe.
2. In the Welcome to the Mirth Connect Setup Wizard window, click Next.
3. If you are promted to select a location for Java, use the location that was noted when unzipping OpenJDK.
4. Read the license agreement, select I accept the agreement, and then click Next.
5. Select the destination directory and click Next.
6. Make sure all of the components are selected and then click Next.
7. Select the Start menu folder settings and then click Next.
8. Configure the network port settings and then click Next.
9. Configure your password requirements and then click Next.
10. Configure your server settings and then click Next.
11. Select Install service and then click Next.
12. Click Finish. Mirth Connect has been installed.
13. Open a text editor with administrator privileges.
a. Navigate to C:\Program Files\Mirth Connect and open the following files.
mcserver.vmoptions mcservice.vmoptions
b. Append the contents of C:\Program Files\Mirth Connect\docs\mcservice-java9+.vmoptions to the end of both files. c. In both files, modify the -Xmx option to 512m. d. Save and close both files.
14. In the system tray, right-click on the Mirth Connect Server Manager icon and select Show Manager.
The minimum amount of free space in MB on the destination file system required for the adapter to initialize. The default is "15" MB.
nect software to use.
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.
The Mirth Connect Server Manager is displayed.
15. In the Mirth Connect Server Manager, click Administrator.
16. If a Security Information dialog box appears, click Run.
17. In the Mirth Connect Login dialog box, in the Username field enter “admin” and in the Password field enter “admin”.
30
Loading...
+ 240 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use