Medtronic MDTCSG2V10A Technical Manual

MAINSPRING®DATA EXPRESS

MDTCSG2 Version 10.0

Mainspring®Data Express Connectivity Guide

Trademarks in this manual

The following list includes trademarks or registered trademarks of Medtronic in the United States and possibly in other countries. All other trademarks are the property of their respective owners. Medtronic, Paceart Optima, CareLink, Mainspring, Medtronic CareLink

Mainspring Data Express.............................................................................................................5

Mainspring Data Express Software Prerequisites.................................................................8

Installing Mainspring Data Express.........................................................................................10

Paceart System Integration........................................................................................................14

Connectivity Guide | Contents | 3

Explanation of symbols.............................................................................................................5

Indications.................................................................................................................................6

Precautions...............................................................................................................................6

Contraindications......................................................................................................................6

Mainspring Data Express Authorized Users..............................................................................6

Technical Support......................................................................................................................7

Installation Prerequisites...........................................................................................................8

Installing and Configuring MS Message Queuing for Windows 8.1................................8

Installing and Configuring MS Message Queuing for Windows 10.................................8

Installing and Configuring MS Message Queueing for Windows Server 2012, 2012

R2, 2016, and 2019...................................................................................................9

Installing the Java Runtime Environment........................................................................9

Installing .Net 4.7.2 Framework......................................................................................9

Automatically Starting the Connected Systems Gateway After Restart...................................12

Log File Configuration.............................................................................................................13

General Paceart System Settings............................................................................................14

Configuring Paceart System Settings...........................................................................14

Paceart System Integration Configuration Values.........................................................15

CareLink Scheduling Integration.............................................................................................15

CareLink Scheduling Integration Prerequisites.............................................................16

Configuring CareLink Scheduling Integration...............................................................16

Troubleshooting CareLink Scheduling Integration........................................................17

Paceart Optima System HL7 Integration.................................................................................18

Configuring Paceart HL7 Integration.............................................................................19

Troubleshooting Paceart HL7 Integration......................................................................21

Local Data Interface................................................................................................................22

Updating the Local Data Interface Port Number...........................................................22

Local Data Interface Extended Configurations.............................................................22

Local Data Interface certificate installation...................................................................22

Enabling a data import source......................................................................................23

Local Data Interface Plus.........................................................................................................23

Updating the Local Data Interface Plus Port Number...................................................23

Local Data Interface Plus certificate installation............................................................24

Enabling a data import source......................................................................................25

CareLink Transmission Integration..........................................................................................25

Remote Data Interface..................................................................................................25

4 | Connectivity Guide | Contents

Data Bridge Gateway....................................................................................................27

Mainspring Health Interface....................................................................................................29

Configuring Mainspring Health Interface......................................................................30

Mainspring Health Interface Configuration Values........................................................30

CareLink Integration ...................................................................................................................31

CareLink Report Export...........................................................................................................31

Configuring CareLink Report Export.............................................................................31

Enabling and Verifying Mainspring Report Export........................................................35

Troubleshooting Report Export.....................................................................................35

CareLink EHR Integration........................................................................................................35

Configuring EHR Integration.........................................................................................36

Installing and configuring Mirth Connect.......................................................................40

Troubleshooting EHR Integration..................................................................................41

HL7 Integration..............................................................................................................................42

Inbound Messages..................................................................................................................42

Inbound Patient Administration Messages (ADT).........................................................42

Inbound Patient Administration Message Segments....................................................43

Inbound Scheduling Messages (SIU)...........................................................................47

Inbound Scheduling Segments....................................................................................48

Inbound Observation Requests (ORU).........................................................................51

Inbound Observation Requests Segments...................................................................51

IDCO 1.1 Support.........................................................................................................97

Outbound Messages...............................................................................................................97

Outbound MSH Message Segments............................................................................97

Outbound PID Message Segments..............................................................................98

Outbound PV1 Message Segments.............................................................................98

Outbound PV2 Message Segments.............................................................................99

Outbound NTE Message Segments.............................................................................99

Outbound OBR Message Segments............................................................................99

Outbound NTE Message Segments...........................................................................101

Outbound OBX Messages..........................................................................................101

HL7 Update Notes.................................................................................................................233

Mainspring Data Express Version 9.0 to 10.0.............................................................233

Mainspring Data Express Version 8.0 to 9.0...............................................................235

Mainspring Data Express Version 7.0 to 8.0...............................................................235

Mainspring Data Express Version 6.0 to 7.0...............................................................236

Mainspring Data Express Version 5.0 to 6.0...............................................................238

Mainspring Data Express Version 4.0 to 5.0...............................................................244

Uninstalling Mainspring Data Express..................................................................................249

Connectivity Guide | Mainspring Data Express | 5

Mainspring Data Express

Mainspring – like the inner workings of a clock – it is the power source that facilitates the movement of cardiac data within your clinic, and between various departments within your organization.

Mainspring Data Express is a comprehensive solution for your cardiac patients, bringing together device and patient data from the Paceart System, the Medtronic CareLink Network, the CareLink Programmer, the Boston Scientific LATITUDE®Patient Management system, the St. Jude Medical Merlin.net®Patient Care Network, your EHR System, and local network.

In order to simplify the process of connecting and sharing demographic, scheduling, and device data between Medtronic applications and electronic health record systems (EHRs), Medtronic has developed Mainspring Data Express. This software application serves as the primary tool to move and share data for device patients. Mainspring Data Express helps to streamline the implementation andon-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

Authorized Representative in theEuropean 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.

Storage temperature limit

Transit temperature limit

Humidity Limitation

6 | Connectivity Guide | Mainspring Data Express

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 PaceartOptima System Software User Manual or the Paceart Optima System Online Help.

Precautions

Symbol definitionSymbol

Software

Mainspring Data Express USBs must be stored within the following conditions:

Storage Environment

-20°C (-4°F) to +70°C (158°F)Temperature

20% to 75%Relative Humidity

Mainspring Data Express USBs must be operating in an environment within the following conditions:

Operating Environment

0°C (32°F) to +65°C (149°F)Temperature

20% to 75%Relative Humidity

Call customer service or your biomedical department for service and repairs.

Contraindications

No known contraindications.

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.

Connectivity Guide | Mainspring Data Express | 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.

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 install and Configure MS Message Queuing.

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 System External System Account User and Role. For instructions refer to the Paceart Optima System online Help.

• Install .Net Framework version 4.7.2 (or newer).

• 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 software will import any existing configurations. For example, if you have an existing Paceart System-CareLink scheduling integration configuration, the settings will be saved and used inthe new version of the Mainspring Data Express software.

Installing and Configuring MS Message Queuing for Windows 8.1

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

1. From the Charms bar, click Settings.

2. Click Control Panel.

3. Click Programs, and then under Programs and Features, click Turn Windows features on or off.

4. Under the Microsoft Message Queue (MSMQ) Server option, check the Microsoft Message Queue (MSMQ) Server Core option. This enables all of the MSMQ Server Core subfeatures.

5. Click OK.

6. If you are prompted to restart the computer, click OK to complete the installation.

Installing and Configuring MS Message Queuing for Windows 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.

Connectivity Guide | Mainspring Data Express Software Prerequisites | 9

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 Restart now to complete the installation.

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

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.

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.8 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 double-click on jre-8u172-windows-i586.exe.

The installation wizard starts.

3. Click Install. A progress window is displayed.

4. Once the installation is complete, click Close.

Installing .Net 4.7.2 Framework

You must have .Net 4.7.2 Framework (or newer) installed before you install the Mainspring Data Express software.

You do not need to be connected to the internet to install the files.

1. Insert the Mainspring Data Express software USB drive into your USB port.

2. Browse to Resources\.Net Framework on the USB and double-click on NDP472-KB4054530-x86-x64-AllOS-ENU.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.

10 | Connectivity Guide | Installing Mainspring Data Express

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 and click CSGInstall.exe on the installation USB.

2. Click Next.

3. On the License Agreement step, click Next.

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

Connectivity Guide | Installing Mainspring Data Express | 11

5. Click Next.

6. Click Install.

A progress bar shows the installation progress.

7. Select Launch Medtronic Mainspring Data Express and then click Finish to exit the installation wizard and open the Medtronic Mainspring Data Express window.

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

12 | Connectivity Guide | Installing Mainspring Data Express

The configuration window for the feature you selected is displayed.

9. Make your configuration changes and click OK. Refer to the following sections for information on configuring each feature. The configuration window closes.

10. Click OK to close the Medtronic Mainspring Data Express window. If you selected EHR Integration for the first time, follow the installation steps in the Installing and Configuring Mirth Connect section of this document to install and configure Mirth Connect.

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.

Connectivity Guide | Installing Mainspring Data Express | 13

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.

14 | Connectivity Guide | Paceart System Integration

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

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 each feature, clear the Use General Paceart External System Account Settings check box on the feature-specific tab, then enter the Username and Password of the account.

Paceart Optima System Application Server

These settings contain information about the computer on which the Paceart Optima System Application Server is 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.

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.

Connectivity Guide | Paceart System Integration | 15

3. In the General Paceart Settings section, edit the settings as needed. a) Update the Username and Password for the external system account set up in the Paceart System.

b) Change the Hostname to the domain name or IP address of the computer on which the Paceart Optima

System Application Server is installed.

c) 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.

Paceart System Integration Configuration Values

This table explains the fields under General Paceart Settings on the Paceart Integration configuration window.

ExplanationField Name

General Paceart External System Account

Username

Password

Paceart Optima Application Server

Hostname

Port

The Paceart System External System Account username. This username is defined in the Paceart System on the External System Accounts tab.

The Paceart System External System Account password. This password is defined in the Paceart System on the External System Accounts tab.

The domain name or IP address of the computer on which the Paceart Optima System Application Server is installed.

The port number the Paceart Optima System Application Server domain interface uses. The default value is 333.

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 appointment is 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 reported by 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."

16 | Connectivity Guide | Paceart System Integration

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.

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 patientmust have an active Medtronic ICD, ICM, orpacemaker 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 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 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 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.

Configuring CareLink Scheduling Integration

1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express > Medtronic Mainspring Data Express.

2. In the Medtronic Mainspring Data Express window, select CareLink Scheduling Integration and click Configurations. The Paceart Integration window is displayed.

3. On the CareLink Scheduling Integration tab,enter the applicable valuesfor your CareLink implementation.

Refer to the CareLink Scheduling Integration Configuration Values table for more explanation on the fields.

4. Click OK.

Connectivity Guide | Paceart System Integration | 17

CareLink Scheduling Integration Configuration Values

This table explains the fields on the CareLink Scheduling Integration 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 Middle Name

Send Patient Gender

Paceart Settings

Patient ID Type Description

The name of the CareLink scheduling service that the adapter will use. The default value is "Endpoint_CSA_basicHttpsBinding".

The fully qualified path of the CareLink scheduling service that the adapter will use. The default value is "https://clscheduling.medtroniccarelink.net/SchedulingGateway/SchedulingGateway.svc".

The account name of the dedicated user that will be used to connect to the CareLink Scheduling service. This account name is created and configured on the 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 Middle Name value is sent to CareLink. If "True", it will be used by CareLink for patient matching. The default value is "True".

A Boolean value indicating if the Patient Gender value is sent to CareLink. If "True", it will be used by CareLink for patient matching. The default value is "True".

The Paceart Patient ID Type Description to associate with the CareLink Remote Patient ID. The default value is "Default".

Appointment Resource

The Paceart Appointment Resource to associatewith CareLink remote appointments. The default value is "Default Resource".

Troubleshooting CareLink Scheduling Integration

Troubleshooting scheduling connectivity problems

CareLink

• Verify that the CareLink account used to connect to Mainspring Data Express has a Transmission Permission selection of View changes transmission status from new to viewed.

• Verify that the CareLink account used to connect to Mainspring Data Express does not have an expired password.

• If the CareLink clinic has sub-clinics, verify that the CareLink account used to connect to the Medtronic Mainspring Data Express has access to the sub-clinics' patients integrated with 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.

18 | Connectivity Guide | Paceart System 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 selected in the Medtronic Mainspring Data Express window.

• Verify that the Connected Systems Gateway service was started.

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 informationchanges 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 the Paceart 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-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 the Paceart System with an "EMR" type ID and a patient ID number of "1335579".

Connectivity Guide | Paceart System Integration | 19

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.

Configuring Paceart HL7 Integration

1. To start Mainspring Data Express, click Start > Programs > Medtronic Mainspring Data Express > Medtronic Mainspring Data Express.

2. In the Medtronic Mainspring Data Express window, select HL7 Integration and click Configurations. The Paceart Integration configuration window is displayed.

3. In the HL7 Integration tab, enter the values for your configuration.

4. Click OK to close the Paceart Integration configuration window.

HL7 Integration Configuration Values

This table explains the fields on the HL7 Integration configuration tab.

ExplanationField name

HL7 Outbound

Outbound Include Episode Observations

Include Nonconforming Data

Boolean value providing an option to include episode data in the HL7 message sent to the receiving system. Inclusion of this data may add to the size of the message.

The default value is "False" (do not send episode data).

Boolean value providing an option to include nonconforming data in the HL7 message sent to the receiving system. Inclusion of this data may add to the size of the message.

Include IDCO Nonconforming Data

The default value is "True".

Boolean value providing an option to include IDCO nonconforming data in the HL7 message sent to the receiving system. Inclusion of this data may add to the size of the message.

The default value is "True".

20 | Connectivity Guide | Paceart System Integration

ExplanationField name

Include Medtronic OBX Segments

Include PV2 Segment

IDCO Message Version

Paceart

Paceart XML Version

Boolean valueproviding an option to includeMedtronic OBX segments in the HL7 message sent to the receiving system. Inclusion of this data may add to the size of the message.

The default value is "True".

Boolean value providing an option to include the PV2 segment in the HL7 message sent to the receiving system. Inclusion of this data may add to the size of the message.

The default value is "True".

The version of IDCO used to generate the HL7 message. Valid values are "1.0" or "1.1".

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.

Installing the Corepoint Integration Engine

If you selected the Paceart HL7 Integration feature, the Corepoint Integration Engine needs to be installed. If you have NeoIntegrate 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.

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.

Connectivity Guide | Paceart System Integration | 21

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 > Corepoint Health > 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 > Corepoint Health > 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 Systems

Gateway\HL7SubSystem.

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.

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.

Programmer Acquisition service cannot start Event Log message

If in the Event Log for the Programmer Acquisition service you receivean 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.

22 | Connectivity Guide | Paceart System Integration

2. Click Service > Corepoint Integration Engine Monitor Service Configuration. The Corepoint Integration Engine Monitor Service Configuration window is displayed.

3. Change the port value.

4. Click OK.

Local Data Interface

The Local Data Interface allows you to configure the service that receives patient session data transmitted from local sources, such as a programmer or LATITUDE. You can start and stop the service, configure advanced options, and enable or disable transmissions from enabled sources.

Updating the Local Data Interface Port Number

The value in the Port field on the Local Data Interface tab identifies the port Mainspring Data Express uses to receive data from local sources. This value must match the value of the port configured for the programmer or for LATITUDE.

1. If needed, change the value in the Port field to match the port configured for the local source. The default value is 443.

2. Click OK to save your changes.

Local Data Interface Extended Configurations

This table explains the fields on the LDI Extended Configurations window.

ExplanationField name

Manufacturer Name

Encounter Type

Username

Password

The manufacturer name of the data provided by a specific system. For example, "Medtronic".

The type of data provided by a specific system. The default value is "InClinic".

The username for a user-defined local data interface extended configuration.

The password for a user-defined local data interface extended configuration.

Local Data Interface certificate installation

The digital certificate allows a secure connection to be established between a data import source and 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.

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:

Connectivity Guide | Paceart System Integration | 23

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

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.

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.

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.

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.

24 | Connectivity Guide | Paceart System Integration

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.

Local Data Interface Plus certificate installation

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.

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.

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 (do not abbreviate)

• Country

3. In the Contact Information section, enter your information in the following required field:

• Email - must be in standard email format

4. From the Server Addressing section, enter 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.

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:\CertReq.txt.

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 *.ceror *.crt

file.

11. Save the certificate file to a location that is accessible from the Paceart System computer.

Connectivity Guide | Paceart System Integration | 25

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 installed Digital Certificate. 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 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.

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.

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.

26 | Connectivity Guide | Paceart System Integration

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.

4. If you receive data from more than one remote system, you must have a separate Remote Data Interface configuration for each system. Click Add to create additional configurations for additional remote systems. You can create up to 5 configurations.

5. Click OK.

Remote Data Interface Configuration Values

This table explains the fields on the Remote Data Interface configuration tab.

ExplanationField name

Carelink 1

Data Service

Data Service Site

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.

Connectivity Guide | Paceart System Integration | 27

ExplanationField name

System Account Name

System Account Access Code

Manufacturer Name

Encounter Type

Clinic Request (Days of History)

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 manufacturer name of the data provided by a specific system. For CareLink, this value is "Medtronic".

The name of the external system. For CareLink, this value is "CareLink".Application ID

The type of data provided by a specific system. For CareLink, this value is "Remote".

The value indicating how many days of history to request from the external system. The default value is 7.

Enabling remote data acquisition in the Paceart System

After you have configured Remote Data Interface for Mainspring Data Express, you need to enable remote data 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.

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.

Enabling Data Bridge Gateway Integration in CareLink

Before you can configure the Data Bridge Gateway integration, you need to set up an external system account for Mainspring Data Express in the CareLink Network.

1. On the CareLink Network website, create an External System Account for Mainspring Data Express. For that External System Account, enable and configure the EHR Integration feature. For instructions, refer to the CareLink Network online Help.

The EHR Integration feature in CareLink sets up the credentials needed for Mainspring Data Express to access the Data Bridge Gateway and retrieve patient session data.

2. On your network, install and configure the Mainspring Data Express software (install prerequisites first).

3. Enable and configure the Data Bridge Gateway feature in Mainspring Data Express.

28 | Connectivity Guide | Paceart System Integration

4. Test your configuration by putting it into Test on the CareLink Network and export data. After you have

tested your integration, move your configuration to Production on the CareLink Network. For instructions, refer to the CareLink network online Help.

Configuring Data Bridge Gateway

1. To start Mainspring Data Express, go to Start > Programs > Medtronic Mainspring Data Express > Medtronic Mainspring Data Express.

2. In the Medtronic Mainspring Data Express window, select Data Bridge Gateway and click Configurations.

The Paceart Integration configuration window is displayed.

3. On the CareLink DataBridge Gateway tab, enter the applicable values for your implementation. Refer to

the CareLink DataBridge Gateway Configuration Values table for more explanation on the fields.

4. If you receive data from more than one remote CareLink Network system, you must have a separate Data Bridge Gateway configuration for each system. Click Add to create additional configurations for additional remote systems. You can create up to 15 configurations.

5. Click OK.

Connectivity Guide | Paceart System Integration | 29

CareLink DataBridge Gateway Configuration Values

This table explains the fields on the Data Bridge Gateway configuration tab.

ExplanationField Name

Configuration 1

Description

Data Bridge Service

Data Bridge Service Site

External System Account Name

External System Account Authorization Code

An optional field for entering the name of your configuration. Limit 15 configurations.

The name of the CareLink Data Bridge service the adapter will use. The default is "Endpoint_CSA_basicHttpsBinding"

The path of the CareLink Data Bridge Service site that the adapter will use.

• To connect in the US and Canada, select https://cl-emr.medtroniccarelink.net/ DataBridgeGateway/DataBridgeGatewayService.svc

• To connect in Europe and Asia, select http://cl-emr.europe.medtroniccarelink.net/ DataBridgeGateway/DataBridgeGatewayService.svc

The account name used to connect to the CareLink system. This account name is created and configured on the External 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.

Troubleshooting Data Bridge Gateway Integration

CareLink EHR Integration

• Verify that the Mainspring Data Express software prerequisites were installed or configured correctly.

• Verify that you selected the correct Data Bridge Service Site for your geography.

• Verify that the External System Account Name and External System Account Authorization Code match what was created in CareLink on the External System Accounts tab.

• Verify that you've selected True in the Use Specified Credentials field if the report destination requires you to enter a Windows username and password. Then verify that the Windows username and password were entered correctly in the Username and Password fields.

• Verify that the Connected Systems Gateway service was started.

Paceart Integration

• Verify the Paceart External System Account password associated with the Mainspring Data Express user.

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.

30 | Connectivity Guide | Paceart System Integration

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.

Mainspring Health Interface Configuration Values

This table explains the fields on the Mainspring Health Interface configuration tab.

ExplanationField Name

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.

Connectivity Guide | CareLink Integration | 31

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 EHR Export 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.

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.

32 | Connectivity Guide | CareLink Integration

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.

Connectivity Guide | CareLink Integration | 33

5. Click OK.

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.

34 | Connectivity Guide | CareLink Integration

This table explains the fields on the CareLink Report Export configuration window.

number

ExplanationField nameCallout

Description1

Data Bridge Service2

Data Bridge Service Site

External System Account Name

External System Account Authorization Code

File Folder Location6

An optional field for entering the name of your configuration. Limit 15 configurations.

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.

• To connect in the US and Canada select " https://cl-emr.medtroniccarelink.net/ DataBridgeGateway/DataBridgeGatewayService.svc"

• To connect in Europe and Asia select "http://cl-emr.europe.medtroniccarelink.net/ DataBridgeGateway/DataBridgeGatewayService.svc "

The account name used to connect to the CareLink system. This account name is created and configured on the External System Accounts tab on the CareLink website.

The authorization code used to connect to the CareLink website. This authorization code is configured on the External System Accounts tab on the CareLink website.

The file destination path where CareLink PDF reports are exported. On the CareLink website this is called the document folder. The file destination path can be specified as a UNC path (\\ComputerName\SharedFolder\Reports) or a mapped drive (z: \\computer\reports). Using a mapped drive allows you to use a shorter file name but the computer hosting Mainspring Data Express must have the network drive mapped to it.

Use Specified Credentials

Username8

Password9

Overwrite Existing File(s)

A "True" value indicates that the Windows Username and Password field values shouldbe used as authentication credentials when accessing the destination path. A "False" value indicates that a username and password are not required to access the destination path.

The default is "False".

When Use Specified Credentials is "True", this is the Windows username that will be used when accessing the destination file system. The Windows username value should follow the UPN (User Principal Name) format username@domain. For example BSMITH@ENT.

When Use Specified Credentials is "True", this is the password associated to the Windows Username that will be used when accessing the destination file system.

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

number

Connectivity Guide | CareLink Integration | 35

ExplanationField nameCallout

Minimum Available Disk Space

The minimum amount of free space in MB on the destination file system required for the adapter to initialize.

The default is "15" MB.

Enabling and Verifying Mainspring Report Export

After you install and configure Mainspring Report Export you need to enable the Report Export feature on the CareLink website.

1. Log into the CareLink website.

2. Click Manage My Clinic > Clinic Profile > External Systems Integration.

3. In the Report Export section, select Yes to enable report export.

Note: You can configure the report filename. For more information on configuring the filename refer to

the Editing Report Filename for Report Export topic in the CareLink online Help.

4. Click Save.

5. After you have enabled the feature, export a sample report from CareLink.

6. Browse to the documentation folder location and verify that the sample report was successfully exported.

Troubleshooting Report Export

CareLink Report Export

• Verify that the Mainspring Data Express software prerequisites were installed or configured correctly.

• Verify that you selected the correct Data Bridge Service Site for your geography.

• Verify that the External System Account Name and External System Account Authorization Code match what was created in CareLink on the External System Accounts tab.

• Verify that the Connected Systems Gateway service was started.

Mainspring Report Export on CareLink

• Verify that you created an External System Account in CareLink.

• Verify that the created External System Account was configured to include Report Export external system associations.

• Verify that Report Export was enabled on the External System Integration tab of the CareLink website.

• Verify that the Report Export file naming format was configured as desired.

CareLink EHR Integration

CareLink EHR Integration allows you to export patient data from the CareLink Network and import it into your clinic's Electronic Health Records (EHR) system. This feature uses Mirth Connect to route the data exported from the CareLink Network to your EHR.

36 | Connectivity Guide | CareLink Integration

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.

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.

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 configurations for other clinics.

Connectivity Guide | CareLink Integration | 37

5. Click OK.

You will need to install and configure Mirth Connect.

CareLink EHR Integration Configuration Values

This table explains the fields on the CareLink EHR Integration configuration window.

38 | Connectivity Guide | CareLink Integration

number

Connectivity Guide | CareLink Integration | 39

ExplanationField nameCallout

Description1

Data Bridge Service2

External System Account Name

External System Account Authorization Code

Document Folder Location6

An optional field for entering the name of your configuration. Limit 15 configurations.

The name of the CareLink Data Bridge service the adapter will use.

The default is "Endpoint_CSA_basicHttpsBinding"

The path of the CareLink Data Bridge Service site that the adapter will use.Data Bridge Service Site3

• To connect in the US and Canada select https://cl-emr.medtroniccarelink.net/ DataBridgeGateway/DataBridgeGatewayService.svc

• To connect in Europe and Asia select http://cl-emr.europe.medtroniccarelink.net/ DataBridgeGateway/DataBridgeGatewayService.svc

The account name used to connect to the CareLink system. This account name is created and configured on the External System Accounts tab on the CareLink website.

The authorization code used to connect to the CareLink website. This authorization code is configured on the External System Accounts tab on the CareLink website.

The file destination path where files will be written. On the CareLink website this is called the document folder. The file destination path can be specified as a UNC path (\\ComputerName\SharedFolder\Reports) or a mapped drive (z:\\computer\reports). Using a mapped drive allows you to use a shorter file name but the computer hosting Mainspring Data Express must have the network drive mapped to it.

Use Specified Credentials7

Username8

Password9

Overwrite Existing File(s)10

Minimum Available Disk Space

A "True" value indicates that the Windows Username and Password field values should be used as authentication credentials when accessing the destination path. A "False" value indicates that a username and password are not required to access the destination path.

The default is "False".

When Use Specified Credentials is "True", this is the password associated to the Windows Username that will be usedwhen accessing the destination file system.

The default is "True".

The minimum amount of free space in MB on the destination file system required for the adapter to initialize.

The default is "15" MB.

40 | Connectivity Guide | CareLink Integration

number

ExplanationField nameCallout

Specifies a file system path where HL7messages will be available for Mirth Connect software to use.

The file system path where Mirth is configured to writefailed HL7 messages.Mirth Error Path13

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.

Mirth Inbound Path12

Minimum Available Disk Space

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-2.2.1.5861.b1248-windows.exe.

2. In the Welcome to the Mirth Connect Setup Wizard window, click Next.

3. Read the license agreement, select I accept the agreement, and then click Next.

4. Select the destination directory and click Next.

5. Make sure all of the components are selected and then click Next.

6. Select the Start menu folder settings and then click Next.

7. Configure the network port settings and then click Next.

8. Configure your password requirements and then click Next.

9. Configure your server settings and then click Next.

10. Select Install service and then click Next.

11. Click Finish.

Mirth Connect has been installed.

12. In the system tray, right-click on the Mirth Connect Server Manager icon and select Show Manager.

The Mirth Connect Server Manager is displayed.

13. In the Mirth Connect Server Manager, click Administrator.

14. If a Security Information dialog box appears, click Run. The Mirth Server Manager is installed.

15. In the Mirth Connect Login dialog box, in the Username field enter "admin" and in the Password field

enter "admin".

16. Click Login. The Welcome to Mirth Connect dialog box is displayed.

17. Create and enter a newusername and password. Enter the other required information and then click Finish.

18. In the Mirth Connect Administrator window, click Channels.

19. In the Channel Tasks pane, click Import Channel. An Open dialog box is displayed.

20. Select the File to MLLP.xml file located at the default path of C:\Program

Files\Medtronic\Connected Systems Gateway\MLLPSubsystem. The Edit Channel window is displayed.

Connectivity Guide | CareLink Integration | 41

21. Click the Destinations tab.

22. Enter the Host Address and Host Port that the HL7 message should be sent to.

23. Click Save Changes.

24. In the Mirth Connect pane, click Channels.

25. Click the File to MLLP channel in the Channels pane, and then click Enable Channel from the Channel Tasks pane.

The channel status is Enabled.

26. In the Channel Tasks pane, click Deploy Channel. The Dashboard shows that the File to MLLP status is "Started".

Troubleshooting EHR Integration

CareLink EHR Integration

• Verify that the Mainspring Data Express software prerequisites were installed or configured correctly.

• Verify that you selected the correct Data Bridge Service Site for your geography.

• Verify that the External System Account Name and External System Account Authorization Code match what was created in CareLink on the External System Accounts tab.

• Verify that the Connected Systems Gateway service was started.

Mirth Connect

• Verify that the File to MLLP status is "Started".

• Verify that the Mirth Connect windows service status is "Started".

42 | Connectivity Guide | HL7 Integration

HL7 Integration

The Medtronic CareLink Network and the Paceart System support the HL7 protocol which allows those systems to integrate with your existing HL7-based Electronic Health Record (EHR) and Practice Management Systems. This allows you to import patient demographic information, scheduling information, and interrogated device data that conforms to the IHE IDCO profile into the Paceart System. And allows you to export transtelephonic, in-clinic, and remote encounter data from the Paceart System and CareLink to your EHR system.

If you want to integrate Merlin.net into your Paceart System, you can do so with an HL7 ORU message that conforms to the IDCO profile.

The information contained in this section assumes an understanding of the HL7 Message Specification and a working knowledge of the Paceart System.

The terms "IDCO 1.0" and "IDCO 1.1" are used in the sections below. IDCO 1.0 is the IDCO profile defined in revision 3 of the Devices Technical Framework, and only includes version 1.0.0 terms of the IEEE 11073-10103 standard. IDCO 1.1 is an in-progress update that includes the proposed addition of version 1.1.0 terms in IEEE 11073-10103 standard.

Inbound Messages

The Paceart System integrates with the HL7 protocol for inbound messages from external systems to the Paceart System by mapping HL7 values to Paceart System parameters.

Inbound Patient Administration Messages (ADT)

The Medtronic Mainspring Data Express HL7 integration can receive demographic information from any system or interface engine that is using HL7 messaging. This feature allows for consistent patient demographic information across systems and reduces duplication of data entry.

The patient administration transaction set provides for the transmission of new or updated demographic information about patients. Information that is entered in a patient administration system can be passed to the Paceart System as an unsolicited HL7 message.

The Medtronic Mainspring Data Express HL7 integration supports a wide array of ADT trigger events to allow you to configure the HL7 integration to capture the desired changes to patient demographic information.

Table : Supported HL7 ADT Triggers

The Patient Add, Patient Update, or Patient Add-Update Paceart System requests can be configured for the A04, A08, and A28 messages. Patient Update is most often used.

Paceart RequestHL7 Message

Patient AddADT^A04

Patient UpdateADT^A08

Patient Add-UpdateADT^A28

Patient DeleteADT^A29

Patient Change IDADT^A47

Table : Patient Processing

Connectivity Guide | HL7 Integration | 43

DescriptionPaceart Request

Patient Add

Patient Update

Patient Add-Update

Patient Delete

Adds the patient to the Paceart System if there is no matching patient record found.

Updates the patient record if a single matching patient is found in the Paceart System.

Adds the patient to the Paceart System if there is no matching patient record found. Updates the patient record if a single matching patient is found in the Paceart System.

Deletes the patient from the Paceart System only if a single matching patient is found, and the Paceart System patient record does not have any associated device, encounter, or appointment.

Changes the specified patient ID if a single matching patient is found.Patient Change ID

Inbound Patient Administration Message Segments

PID - Patient Identification Segment

The PID segment provides important identification information about the patient and is used as the primary means of communicating the identifying and demographic information about a patient between systems.

ComponentField

component

OccurrenceSub-

Name

Paceart valuesParameter TypeParameter

1N/A1PID-3

Value

1N/A5PID-3

Description

2..21N/A1PID-3 Value

2..21N/A5PID-3 Description

111PID-5

Name

1N/A2PID-5

Name

1N/A3PID-5

Initial

N/AN/AN/APID-7

Birth

ENUMPatient GenderN/AN/AN/APID-8

1N/A1PID-11

Address Line 1

N/AString 50Patient ID

N/AString 50Patient ID Type

N/AString 50Patient ID

N/AString 50Patient ID Type

N/AString 50Patient Last

N/AString 50Patient First

N/AString 1Patient Middle

N/ADateTimePatient Date Of

F, f, M, m, O, o, U, u, A, a, N, n

N/AString 50Patient

44 | Connectivity Guide | HL7 Integration

ComponentField

component

OccurrenceSub-

Name

1N/A2PID-11

Paceart valuesParameter TypeParameter

N/AString 50Patient

Address Line 2

1N/A3PID-11

N/AString 50Patient

Address City

1N/A4PID-11

N/AString 10Patient

Address State

1N/A5PID-11

N/AString 10Patient Address Postal Code

1N/A6PID-11

N/AString 50Patient Address Country

1N/A4PID-13

N/AString 100Patient Email Address

N/AN/A1PID-13

N/AString 20Patient Phone Number

N/AN/A1PID-14

N/AString 20Patient Phone Number Other

N/AN/A1PID-15

ENUMPatient

Language

English, French,

Italian, German,

Spanish, Mandarin,

Hindi, Arabic,

Russian,

Portuguese,

Bengali, Malay

Indonesian,

Japanese, Farsi

Persian1, Urdu,

Punjabi,

Vietnamese, Tamil,

Wu, Javanese,

Turkish, Telugu,

Korean, Marathi,

Thai , Cantonese,

Gujarati, Polish,

Kannada, Burmese,

Other

N/AN/A1PID-16

ENUMPatient Marital

Status

A, a, D, d, M, m, S,

s, W, w, C, c, G, g,

P, p, R, r, E, e, N, n,

I, i

N/AN/A1PID-29

Death

The HL7 value 'Persian' is mapped to the Paceart value 'Farsi Persian'.

N/ADateTimePatient Date of

Connectivity Guide | HL7 Integration | 45

ComponentField

component

PDA - Patient Death and Autopsy

The PDA segment is used to communicate information about a patient's death or autopsy.

ComponentField

component

PV1 - Patient Visit Information

The PV1 segment is used by registration applications to communicate information on a visit-specific basis.

OccurrenceSub-

Name

N/AN/A1PID-30

Indicator

OccurrenceSub-

Name

1N/A2PDA-1

Cause

OccurrenceSub-componentComponentField

N/AN/A1PV1-3

Parameter Name

Location of Care

Parameter Type

Paceart valuesParameter TypeParameter

N, YENUMPatient Death

Paceart valuesParameter TypeParameter

N/AString 250Patient Death

Paceart values

N/AString 1Patient StatusN/AN/A1PV1-2

N/AReference_OnlyPatient

PV2 - Patient Visit Information

The PV2 segment is a continuation of visit-specific information contained in the PV1 segment.

OccurrenceSub-componentComponentField

1N/A1PV2-7

2N/A1PV2-7

3N/A1PV2-7

4N/A1PV2-7

MRG - Merge Patient Identification Segment

The MRG segment provides receiving applications with information necessary to update patient ID data.

OccurrenceSub-componentComponentField

1N/A1MRG-1

Parameter Name

Value 1

Value 2

Value 3

Value 4

Parameter Name

Value

Parameter Type

Paceart values

N/AString 6Patient Code

Paceart values

N/AString 50Patient ID

46 | Connectivity Guide | HL7 Integration

OccurrenceSub-componentComponentField

1N/A5MRG-1

IN1 - Insurance Segment

The IN1 segment is used to communicate information about a patient's insurance.

ComponentField

component

OccurrenceSub-

N/AN/AN/AIN1-3

N/AN/AN/AIN1-4

N/AN/AN/AIN1-8

Parameter Name

Type Description

Parameter Name

Company Code

Company Name

Insurance Policy Number

Parameter Type

Paceart values

N/AString 50Patient ID

Paceart values

N/AString 60Insurance

N/AString 50Insurance

N/AString 20Patient

N/AN/AN/AIN1-11

Insurance Policy Holder Employer

N/AN/AN/AIN1-12

Insurance Effective Date

N/AN/AN/AIN1-15

Insurance Type

N/AN/AN/AIN1-16

Insurance Policy Holder Name

N/AN/AN/AIN1-36

Insurance Policy Holder Certificate Number

N/AN/AN/AIN1-49

Insurance Policy Holder Social Security Number

ENUMPatient

N/AString 50Patient

N/ADatePatient

PRIMARY, SECONDARY, OTHER

N/AString 50Patient

N/AString 20Patient

N/AString 11Patient

N/AN/AN/AN/A

Insurance Status

ENUMPatient

ACTIVE, INACTIVE

Connectivity Guide | HL7 Integration | 47

Inbound Scheduling Messages (SIU)

The Medtronic MainspringData Express HL7 integration can accept unsolicited schedule notificationmessages (SIU) from a scheduling filler application. The HL7 standard defines four roles that the system can assume in scheduling integration. The Paceart System operates as an Auxiliary application or an "interested third-party." This allows for existing scheduling systems to serve as the Filler application and to send schedule notification messages to the Paceart System. The Filler application is said to own the schedule for the specified resources meaning it is the authoritative source for scheduling information.

Supported Transaction Types

The schedule notification messages can be processed to not only create, delete, cancel, and modify appointments in the Paceart System, but also can be used to add or modify patient information. This allows for a patient to be added to the Paceart System based on their first appointment with a clinic.

Updating, rescheduling, deleting, or canceling, an appointment can only be performed as long asthe appointment exists in Paceart.

A single matching Paceart System appointment for a single matching patient is said to exist if the Appointment External ID is the same as the Request Appointment External ID (matching appointment is found by ID) or there is an appointment with the same start date, time, and appointment type (matching appointment is found by start date, time, and type).

Table : Supported SIU Triggers

Paceart RequestHL7 Message

Add AppointmentSIU^S12

Update AppointmentSIU^S13

Add Update AppointmentSIU^S14

Cancel AppointmentSIU^S15

Delete AppointmentSIU^S17

Table : Appointment Processing

DescriptionPaceart Request

Add Appointment

Update Appointment

Add Update Appointment

Creates a new appointment in the Paceart System if the appointment ID does not already exist in the Paceart System. If the appointment does exist then no appointment will be added.

Modifies the appointment in the Paceart System if the appointment ID already exists in the Paceart System.

Updates the appointment information in the Paceart System if the appointment exists in the Paceart System.

Cancel Appointment

If the appointment does not exist in the Paceart System, then it creates a new appointment in the Paceart System.

Cancels/Removes the appointment in the Paceart System if the appointment ID already exists in the Paceart System.

48 | Connectivity Guide | HL7 Integration

DescriptionPaceart Request

Delete Appointment

Deletes the appointment in the Paceart System if the appointment ID already exists in the Paceart System.

Inbound Scheduling Segments

The schedule notification message should contain information on what type of appointment has been booked. The information can be transformed in the message to map to one of the following values. If no encounter type information is available in the scheduling messages, the appointment will fail to add/update the Paceart System database.

In the following tables, required fields are marked with an * (asterisk).

SCH - Schedule Activity Information

The SCH segment contains general information about a scheduled appointment.

Paceart valuesParameter TypeParameter NameOccurrenceSub-componentComponentField

N/AString 75Appointment IDN/AN/A1SCH-1

N/AN/A1SCH-2*

Appointment External ID

contain characters [, _, and %

N/AString 75, cannot

ENUMAppointment TypeN/AN/A1SCH-8

N/AN/AN/ASCH-9

N/AN/A4SCH-11*

NTE - Notes and Comments

The NTE segment is an optional segment used to provide notes and comments.

1N/A1NTE-3

PID - Patient Identification Segment

Appointment Duration

Date Time

Parameter NameOccurrenceSub-componentComponentField

Comment

1.00:00)

Type

INCLINIC, TTM, REMOTE, MISCELLANEOUS, IMPLANT, PHONENOTE

N/ATimeSpan(00:01,

N/AENUMAppointment Start

Paceart valuesParameter

N/AString 255Appointment

Connectivity Guide | HL7 Integration | 49

ComponentField

component

OccurrenceSub-

Name

1N/A1PID-3*

Value

1N/A5PID-3*

Description

2..21N/A1PID-3 Value

2..21N/A5PID-3 Description

111PID-5*

Name

1N/A2PID-5

Name

1N/A3PID-5

Initial

N/AN/AN/APID-7

Birth

ENUMPatient GenderN/AN/AN/APID-8

Paceart valuesParameter TypeParameter

N/AString 50Patient ID

N/AString 50Patient ID Type

N/AString 50Patient ID

N/AString 50Patient ID Type

N/AString 50Patient Last

N/AString 50Patient First

N/AString 1Patient Middle

N/ADateTimePatient Date Of

F, f, M, m, O, o, U, u, A, a, N, n

1N/A1PID-11

Address Line 1

1N/A2PID-11

Address Line 2

1N/A3PID-11

Address City

1N/A4PID-11

Address State

1N/A5PID-11

Address Postal Code

1N/A6PID-11

Address Country

1N/A4PID-13

Address

N/AN/A1PID-13

Number

N/AN/A1PID-14

Number Other

N/AString 50Patient

N/AString 10Patient

N/AString 50Patient

N/AString 100Patient Email

N/AString 20Patient Phone

N/AN/A1PID-15

Language

ENUMPatient

English, French, Italian, German, Spanish, Mandarin, Hindi, Arabic,

50 | Connectivity Guide | HL7 Integration

ComponentField

component

OccurrenceSub-

Name

Paceart valuesParameter TypeParameter

Russian, Portuguese, Bengali, Malay Indonesian, Japanese, Farsi Persian2, Urdu, Punjabi, Vietnamese, Tamil, Wu, Javanese, Turkish, Telugu, Korean, Marathi, Thai , Cantonese, Gujarati, Polish, Kannada, Burmese, Other

N/AN/A1PID-16

ENUMPatient Marital

Status

A, a, D, d, M, m, S, s, W, w, C, c, G, g, P, p, R, r, E, e, N, n, I, i

N/AN/A1PID-29

N/ADateTimePatient Date of

Death

N/AN/A1PID-30

N, YENUMPatient Death

Indicator

PV1 - Patient Visit Information

The PV1 segment is used by registration applications to communicate information on a visit-specific basis.

OccurrenceSub-componentComponentField

Parameter TypeParameter

Name

Paceart values

N/AString 1Patient StatusN/AN/A1PV1-2

N/AN/A1PV1-3

N/AReference_OnlyPatient Location of Care

N/AN/A1PV1-19

N/AString 50Appointment Visit ID

PV2 - Patient Visit Information

The PV2 segment is a continuation of visit-specific information contained in the PV1 segment.

OccurrenceSub-componentComponentField

Parameter Name

Parameter Type

1N/A1PV2-7

Paceart values

N/AString 6Patient Code

Value 1

The HL7 value 'Persian' is mapped to the Paceart value 'Farsi Persian'.

Connectivity Guide | HL7 Integration | 51

OccurrenceSub-componentComponentField

2N/A1PV2-7

3N/A1PV2-7

4N/A1PV2-7

AIG - General Resource Segment

The AIG segment contains information about various kinds of resources that can be scheduled.

OccurrenceSub-componentComponentField

N/AN/A1AIG-3

Parameter Name

Value 2

Value 3

Value 4

Parameter Name

Resource

Parameter Type

Paceart values

N/AString 6Patient Code

Inbound Observation Requests (ORU)

The ORU-R01 message transmits observations and results. Mainspring Data Express and the Paceart Optima System comply with the IDCO standard for how to use an HL7 ORU message for implantable cardiac device observations.

Paceart values

N/AReference_OnlyAppointment

Table : Supported HL7 ORU Triggers

Paceart RequestHL7 Message

Transmission DataORU^R01

DescriptionPaceart Request

Sends transmission data from one system to another system.Transmission Data

Inbound Observation Requests Segments

MSH - Message Header

The MSH segment is present in every HL7 message type and defines the message's source, purpose, destination, and certain syntax specifics like delimiters (separator characters) and character sets.

Parameter NameOccurrenceSub-componentComponentField

Type

N/AN/A1MSH-3

N/AN/A1MSH-4

Sub ID

Paceart valuesParameter

N/AString 100Sending Application

52 | Connectivity Guide | HL7 Integration

PID - Patient Identification Segment

OccurrenceSub-componentComponentField

1N/A1PID-3

2..21N/A1PID-3

1N/A4PID-3

Parameter Name

Device Model and Serial Number

Value

Session Device Manufacturer

Type

Paceart valuesParameter

N/AString 100Patient

N/AString 50Patient ID

MDC_IDC_ENUM_MFG_ANGENUMEncounter

MDC_IDC_ENUM_MFG_APC

MDC_IDC_ENUM_MFG_BIO

MDC_IDC_ENUM_MFG_BSC

MDC_IDC_ENUM_MFG_CCS

MDC_IDC_ENUM_MFG_CIM

MDC_IDC_ENUM_MFG_CPM

MDC_IDC_ENUM_MFG_CKP

MDC_IDC_ENUM_MFG_CATM

MDC_IDC_ENUM_MFG_COR

MDC_IDC_ENUM_MFG_ELA

MDC_IDC_ENUM_MFG_GDT

MDC_IDC_ENUM_MFG_IMC

MDC_IDC_ENUM_MFG_MCO

MDC_IDC_ENUM_MFG_MDT

MDC_IDC_ENUM_MFG_OSC

MDC_IDC_ENUM_MFG_PCS

MDC_IDC_ENUM_MFG_SIE

MDC_IDC_ENUM_MFG_SOR

MDC_IDC_ENUM_MFG_SJM

MDC_IDC_ENUM_MFG_TEL

MDC_IDC_ENUM_MFG_VEN

MDC_IDC_ENUM_MFG_VIT

MDC_IDC_ENUM_MFG_ABT

MDC_IDC_ENUM_MFG_MPT

Connectivity Guide | HL7 Integration | 53

OccurrenceSub-componentComponentField

2..21N/A5PID-3

1N/A1PID-5

1N/A2PID-5

1N/A3PID-5

1N/AN/APID-7

N/AN/AN/APID-8

1N/A1PID-11

1N/A2PID-11

Parameter Name

Type Description

Name

Middle Initial

Of Birth

Gender

Address Line 1

Address Line 2

Type

Paceart valuesParameter

N/AString 50Patient ID

N/AString 50Patient Last

N/AString 50Patient First

N/AString 1Patient

N/ADateTimePatient Date

F, f, M, m, O, o, U, u, A, a, N, nENUMPatient

N/AString 50Patient

1N/A3PID-11

Address City

1N/A4PID-11

Address State

1N/A5PID-11

Address Postal Code

1N/A6PID-11

Address Country

PV1 - Patient Visit Information

The PV1 segment is used by registration applications to communicate information on a visit-specific basis.

OccurrenceSub-componentComponentField

N/AN/A1PV1-19

Parameter Name

Visit ID

N/AString 50Patient

N/AString 10Patient

N/AString 50Patient

Parameter Type

Paceart values

N/AString 1Patient StatusN/AN/A1PV1-2

N/AString 50Appointment

54 | Connectivity Guide | HL7 Integration

OBR - Observation Request

The OBR segment transmits information about an exam, diagnostic study/observation, or assessment that is specific to an order or result.

Parameter NameOccurrenceSub-componentComponentField

Paceart valuesParameter

Type

N/AN/A1OBR-3

Sending Application Event ID

100

ENUMEncounter TypeN/AN/A1OBR-4

N/AString

IMPLANT, INCLINIC, REMOTE, TTM, PHONENOTE, MISC, PROGRAMMING

N/AN/A1OBR-7

N/ADateTimeEncounter Date and

Time

OBX - Observation Mapping

The OBX segment is primarily used to carry key clinical observation and result reporting information within report messages.

Table : MDC_IDC_DEV

PaceartIDCO

Parameter TypeParameter

3-1

IDCO Supported Values OBX-5OBX 3-2OBX

Name

753666^MDC_IDC_ENUM_PG_TYPE_ICD^MDC

753667^MDC_IDC_ENUM_PG_TYPE_CRT_D^MDC

753668^MDC_IDC_ENUM_PG_TYPE_CRT_P^MDC

753669^MDC_IDC_ENUM_PG_TYPE_Monitor^MDC

N/AMDC_IDC_DEV_SERIAL720899

753729^MDC_IDC_ENUM_MFG_ANGN^MDCMDC_IDC_DEV_MFG720900

753730^MDC_IDC_ENUM_MFG_APC^MDC

753731^MDC_IDC_ENUM_MFG_BIO^MDC

753732^MDC_IDC_ENUM_MFG_BSX^MDC

753733^MDC_IDC_ENUM_MFG_CCS^MDC

753734^MDC_IDC_ENUM_MFG_CIM^MDC

753735^MDC_IDC_ENUM_MFG_CPM^MDC

753736^MDC_IDC_ENUM_MFG_CKP^MDC

753737^MDC_IDC_ENUM_MFG_CATM^MDC

ENUMDevice Type753665^MDC_IDC_ENUM_PG_TYPE_IPG^MDCMDC_IDC_DEV_TYPE720897

String 50Device ModelN/AMDC_IDC_DEV_MODEL720898

String 20Device Serial

Number

ENUMDevice

Manufacturer

Connectivity Guide | HL7 Integration | 55

PaceartIDCO

3-1

IDCO Supported Values OBX-5OBX 3-2OBX

753738^MDC_IDC_ENUM_MFG_COR^MDC

753739^MDC_IDC_ENUM_MFG_ELA^MDC

753740^MDC_IDC_ENUM_MFG_GDT^MDC

753741^MDC_IDC_ENUM_MFG_IMC^MDC

753742^MDC_IDC_ENUM_MFG_IMT^MDC

753743^MDC_IDC_ENUM_MFG_MCO^MDC

753744^MDC_IDC_ENUM_MFG_MDT^MDC

753745^MDC_IDC_ENUM_MFG_OSC^MDC

753746^MDC_IDC_ENUM_MFG_OSY^MDC

753747^MDC_IDC_ENUM_MFG_PCS^MDC

753748^MDC_IDC_ENUM_MFG_SIE^MDC

753749^MDC_IDC_ENUM_MFG_SOM^MDC

753750^MDC_IDC_ENUM_MFG_SOR^MDC

753751^MDC_IDC_ENUM_MFG_STJ^MDC

753752^MDC_IDC_ENUM_MFG_STO^MDC

Parameter TypeParameter

Name

Table : MDC_IDC_SESS

3-1

MDC_IDC_SESS_DTM721025

721027

REPROGRAMMED

753753^MDC_IDC_ENUM_MFG_TEL^MDC

753754^MDC_IDC_ENUM_MFG_VEN^MDC

753755^MDC_IDC_ENUM_MFG_VIT^MDC

753757^MDC_IDC_ENUM_MFG_ABT^MDC

753758^MDC_IDC_ENUM_MFG_MPT^MDC

Supported Values (OBX 5)OBX 3-2OBX

755201^MDC_IDC_ENUM_SESS_REPROGRAMMED_YES^MDCMDC_IDC_SESS_

755202^MDC_IDC_ENUM_SESS_REPROGRAMMED_NO^MDC

755203^MDC_IDC_ENUM_SESS_REPROGRAMMED_Unknown^MDC

PaceartIDCO

Parameter TypeParameter

Name

DateTimeEncounter

Session

Timestamp

ENUMEncounter

Session

Reprogrammed

56 | Connectivity Guide | HL7 Integration

Table : MDC_IDC_MSMT

PaceartIDCO

3-1

721472

MDC_IDC_MSMT_BATTERY_DTM721216

MDC_IDC_MSMT_BATTERY_VOLTAGE721344

MDC_IDC_MSMT_BATTERY_IMPEDANCE721408

MDC_IDC_MSMT_BATTERY_REMAINING_

LONGEVITY

754113^MDC_IDC_ENUM_BATTERY_STATUS_BOS^MDCMDC_IDC_MSMT_BATTERY_STATUS721280

754114^MDC_IDC_ENUM_BATTERY_STATUS_EOS^MDC

754115^MDC_IDC_ENUM_BATTERY_STATUS_RRT^MDC

754116^MDC_IDC_ENUM_BATTERY_STATUS_MOS^MDC

754117^MDC_IDC_ENUM_BATTERY_STATUS_

Unknown^MDC

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Measured Device

Battery Timestamp

Measured Device

Battery Status

Measured Device

Battery Voltage

Measured Device

Battery Impedance

Measured Device

Battery Remaining

Longevity

Parameter

Type

DateTimeEncounter

ENUMEncounter

NumericEncounter

IntegerEncounter

721536

when 721856^MDC_IDC_MSMT_CAP_CHARGE_TYPE^MDC has OBX-5 value of 754177^MDC_IDC_ENUM_CHARGE_TYPE_Shock^MDC

MDC_IDC_MSMT_BATTERY_REMAINING_

PERCENTAGE

MDC_IDC_MSMT_BATTERY_RRT_TRIGGER721600

MDC_IDC_MSMT_CAP_CHARGE_DTM721664

MDC_IDC_MSMT_CAP_CHARGE_TIME721728

Measured Device

Battery Remaining

Percentage

Measured Device

Battery Status RRT

Trigger

Measured Device

Capacitor Last Full

Energy Charge

Timestamp or

Encounter

Measured Device

Capacitor Last

Therapy Charge

Timestamp

Measured Device

Capacitor Last Full

Energy Charge

NumericEncounter

String 50Encounter

DateTimeEncounter

NumericEncounter

Connectivity Guide | HL7 Integration | 57

PaceartIDCO

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

3-1

Interval or

Encounter

Measured Device

Capacitor Last

Therapy Charge

Interval

MDC_IDC_MSMT_CAP_CHARGE_ENERGY721792

Measured Device

Capacitor Last Full

Energy Charge or

Encounter

Measured Device

Capacitor Last

Therapy Charge

Energy

when 721856^MDC_IDC_MSMT_CAP_CHARGE_TYPE^MDC has OBX-5 value of 54177^MDC_IDC_ENUM_CHARGE_TYPE_Reformation^MDC

MDC_IDC_MSMT_CAP_CHARGE_DTM721664

Measured Device

Capacitor Last

Reformation

Timestamp

Parameter

Type

NumericEncounter

DateTimeEncounter

721921

MDC_IDC_MSMT_CAP_CHARGE_TIME721728

MDC_IDC_MSMT_CAP_CHARGE_ENERGY721792

MDC_IDC_MSMT_LEADCHNL_RA_DTM_

START

MDC_IDC_MSMT_LEADCHNL_RA_DTM_END721922

754177^MDC_IDC_ENUM_CHARGE_TYPE_Shock^MDCMDC_IDC_MSMT_CAP_CHARGE_TYPE721856

754178^MDC_IDC_ENUM_CHARGE_TYPE_

Reformation^MDC

754179^MDC_IDC_ENUM_CHARGE_TYPE_Unknown^MDC

NumericEncounter

Measured Device

Capacitor Last

Reformation

Interval

NumericEncounter

Measured Device

Capacitor Last

Reformation

Energy

ENUMDetermines which

parameter is used

when mapping the

above three rows.

DateTimeEncounter

Measured Right

Atrium Lead Low

Power Channel

Sensing Integrity

Counter Start Date

DateTimeEncounter

Measured Right

Atrium Lead Low

Power Channel

58 | Connectivity Guide | HL7 Integration

PaceartIDCO

3-1

721925

721929

721933

MDC_IDC_MSMT_LEADCHNL_RV_DTM_

START

MDC_IDC_MSMT_LEADCHNL_RV_DTM_END721926

START

MDC_IDC_MSMT_LEADCHNL_LV_DTM_

START

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Sensing Integrity

Counter End Date

Measured Right

VentricleLead Low

Power Channel

Sensing Integrity

Counter Start Date

Measured Right

VentricleLead Low

Power Channel

Sensing Integrity

Counter End Date

Measured Left

VentricleLead Low

Power Channel

Sensing Integrity

Counter Start Date

Parameter

Type

DateTimeEncounter

DateTimeMDC_IDC_MSMT_LEADCHNL_LA_DTM_

DateTimeMDC_IDC_MSMT_LEADCHNL_LA_DTM_END721930

DateTimeEncounter

721984

721985

721986

721987

MDC_IDC_MSMT_LEADCHNL_LV_DTM_END721934

MDC_IDC_MSMT_LEADCHNL_RA_LEAD_

CHANNEL_STATUS

MDC_IDC_MSMT_LEADCHNL_RV_LEAD_

CHANNEL_STATUS

MDC_IDC_MSMT_LEADCHNL_LA_LEAD_

CHANNEL_STATUS

MDC_IDC_MSMT_LEADCHNL_LV_LEAD_

CHANNEL_STATUS

754241^MDC_IDC_ENUM_CHANNEL_STATUS_

CheckLead^MDC

754242^MDC_IDC_ENUM_CHANNEL_STATUS_Null^MDC

754241^MDC_IDC_ENUM_CHANNEL_STATUS_

CheckLead^MDC

754242^MDC_IDC_ENUM_CHANNEL_STATUS_Null^MDC

CheckLead^MDC

754242^MDC_IDC_ENUM_CHANNEL_STATUS_Null^MDC

754241^MDC_IDC_ENUM_CHANNEL_STATUS_

CheckLead^MDC

754242^MDC_IDC_ENUM_CHANNEL_STATUS_Null^MDC

DateTimeEncounter

Measured Left

VentricleLead Low

Power Channel

Sensing Integrity

Counter End Date

ENUMEncounter

Measured Right

Atrium Lead Low

Power Channel

Status

ENUMEncounter

Measured Right

VentricleLead Low

Power Channel

Status

ENUM754241^MDC_IDC_ENUM_CHANNEL_STATUS_

ENUMEncounter

Measured Left

VentricleLead Low

Connectivity Guide | HL7 Integration | 59

PaceartIDCO

3-1

722048

722049

722050

722051

722052

722053

722054

722055

MDC_IDC_MSMT_LEADCHNL_RA_SENSING_

INTR_AMPL

MDC_IDC_MSMT_LEADCHNL_RA_SENSING_

INTR_AMPL_MAX

MDC_IDC_MSMT_LEADCHNL_RA_SENSING_

INTR_AMPL_MIN

MDC_IDC_MSMT_LEADCHNL_RA_SENSING_

INTR_AMPL_MEAN

MDC_IDC_MSMT_LEADCHNL_RV_SENSING_

INTR_AMPL

MDC_IDC_MSMT_LEADCHNL_RV_SENSING_

INTR_AMPL_MAX

MDC_IDC_MSMT_LEADCHNL_RV_SENSING_

INTR_AMPL_MIN

MDC_IDC_MSMT_LEADCHNL_RV_SENSING_

INTR_AMPL_MEAN

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Power Channel

Status

Programmed

Bradycardia Right

Atrium Sensing

Amplitude

Programmed

Bradycardia Right

Ventricle Sensing

Amplitude

Parameter

Type

NumericEncounter

722056

722057

722058

722059

722060

722061

722062

722063

722112

INTR_AMPL

MDC_IDC_MSMT_LEADCHNL_LA_SENSING_

INTR_AMPL_MAX

MDC_IDC_MSMT_LEADCHNL_LA_SENSING_

INTR_AMPL_MIN

MDC_IDC_MSMT_LEADCHNL_LA_SENSING_

INTR_AMPL_MEAN

MDC_IDC_MSMT_LEADCHNL_LV_SENSING_

INTR_AMPL

MDC_IDC_MSMT_LEADCHNL_LV_SENSING_

INTR_AMPL_MAX

MDC_IDC_MSMT_LEADCHNL_LV_SENSING_

INTR_AMPL_MIN

MDC_IDC_MSMT_LEADCHNL_LV_SENSING_

INTR_AMPL_MEAN

POLARITY

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_RA_SENSING_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

NumericMDC_IDC_MSMT_LEADCHNL_LA_SENSING_

NumericEncounter

Programmed

Bradycardia Left

Ventricle Sensing

Amplitude

ENUMEncounter

Measured Right

Atrium Lead

Sensing Threshold

Polarity

722113

POLARITY

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_RV_SENSING_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

ENUMEncounter

Measured Right

60 | Connectivity Guide | HL7 Integration

PaceartIDCO

3-1

722114

722115

722176

722177

POLARITY

MDC_IDC_MSMT_LEADCHNL_RA_PACING_

THRESHOLD_AMPLITUDE

MDC_IDC_MSMT_LEADCHNL_RV_PACING_

THRESHOLD_AMPLITUDE

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC Ventricle Lead

Sensing Threshold

Polarity

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_LV_SENSING_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

Measured Left

Ventricle Lead

Sensing Threshold

Polarity

Measured Right

Atrium Lead

Capture Threshold

Amplitude

Measured Right

Ventricle Lead

Capture Threshold

Amplitude

Parameter

Type

ENUM754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_LA_SENSING_

ENUMEncounter

NumericEncounter

722178

722179

722240

722241

722242

722243

THRESHOLD_AMPLITUDE

MDC_IDC_MSMT_LEADCHNL_LV_PACING_

THRESHOLD_AMPLITUDE

MDC_IDC_MSMT_LEADCHNL_RA_PACING_

THRESHOLD_PULSEWIDTH

MDC_IDC_MSMT_LEADCHNL_RV_PACING_

THRESHOLD_PULSEWIDTH

MDC_IDC_MSMT_LEADCHNL_LV_PACING_

THRESHOLD_PULSEWIDTH

NumericMDC_IDC_MSMT_LEADCHNL_LA_PACING_

NumericEncounter

Measured Left

Ventricle Lead

Capture Threshold

Amplitude

NumericEncounter

Measured Right

Atrium Lead

Capture Threshold

Duration

NumericEncounter

Measured Right

Ventricle Lead

Capture Threshold

Duration

NumericMDC_IDC_MSMT_LEADCHNL_LA_PACING_

NumericEncounter

Measured Left

Ventricle Lead

Capture Threshold

Duration

Connectivity Guide | HL7 Integration | 61

PaceartIDCO

3-1

722304

722305

722306

MDC_IDC_MSMT_LEADCHNL_RA_PACING_

THRESHOLD_MEASUREMENT_METHOD

MDC_IDC_MSMT_LEADCHNL_RV_PACING_

THRESHOLD_MEASUREMENT_METHOD

MDC_IDC_MSMT_LEADCHNL_LA_PACING_

THRESHOLD_MEASUREMENT_METHOD

754369^MDC_IDC_ENUM_MEASUREMENT_METHOD_

ProgrammerManual^MDC

754370^MDC_IDC_ENUM_MEASUREMENT_METHOD_

ProgrammerAutomatic^MDC

754371^MDC_IDC_ENUM_MEASUREMENT_METHOD_

DeviceAutomatic^MDC

754369^MDC_IDC_ENUM_MEASUREMENT_METHOD_

ProgrammerManual^MDC

754370^MDC_IDC_ENUM_MEASUREMENT_METHOD_

ProgrammerAutomatic^MDC

754371^MDC_IDC_ENUM_MEASUREMENT_METHOD_

DeviceAutomatic^MDC

ProgrammerManual^MDC

754370^MDC_IDC_ENUM_MEASUREMENT_METHOD_

ProgrammerAutomatic^MDC

754371^MDC_IDC_ENUM_MEASUREMENT_METHOD_

DeviceAutomatic^MDC

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Measured Right

Atrium Lead

Capture Threshold

Measurement

Method

Measured Right

Ventricle Lead

Capture Threshold

Measurement

Method

Parameter

Type

ENUMEncounter

ENUM754369^MDC_IDC_ENUM_MEASUREMENT_METHOD_

722307

722368

722369

722370

722371

MDC_IDC_MSMT_LEADCHNL_LV_PACING_

THRESHOLD_MEASUREMENT_METHOD

THRESHOLD_POLARITY

754369^MDC_IDC_ENUM_MEASUREMENT_METHOD_

ProgrammerManual^MDC

754370^MDC_IDC_ENUM_MEASUREMENT_METHOD_

ProgrammerAutomatic^MDC

754371^MDC_IDC_ENUM_MEASUREMENT_METHOD_

DeviceAutomatic^MDC

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_RA_PACING_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_RV_PACING_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_LV_PACING_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

ENUMEncounter

Measured Left

Ventricle Lead

Capture Threshold

Measurement

Method

ENUMEncounter

Measured Right

Atrium Lead

Capture Threshold

Polarity

ENUMEncounter

Measured Right

Ventricle Lead

Capture Threshold

Polarity

ENUM754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_LA_PACING_

ENUMEncounter

Measured Left

Ventricle Lead

Capture Threshold

Polarity

62 | Connectivity Guide | HL7 Integration

PaceartIDCO

3-1

722432

722433

722434

722435

MDC_IDC_MSMT_LEADCHNL_RA_

IMPEDANCE_VALUE

MDC_IDC_MSMT_LEADCHNL_RV_

IMPEDANCE_VALUE

MDC_IDC_MSMT_LEADCHNL_LV_

IMPEDANCE_VALUE

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Measured Right

Atrium Lead Low

Power Channel

Impedance

Measurement

Value

Measured Right

VentricleLead Low

Power Channel

Impedance

Measurement

Value

Measured Left

VentricleLead Low

Power Channel

Impedance

Measurement

Value

Parameter

Type

NumericEncounter

NumericMDC_IDC_MSMT_LEADCHNL_LA_

NumericEncounter

722496

722497

722498

722499

IMPEDANCE_POLARITY

MDC_IDC_MSMT_LEADHVCHNL_DTM722560

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_RA_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_RV_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_LV_

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754307^MDC_IDC_ENUM_POLARITY_Unknown^MDC

ENUMEncounter

Measured Right

Atrium Lead Low

Power Channel

Impedance Polarity

ENUMEncounter

Measured Right

VentricleLead Low

Power Channel

Impedance Polarity

ENUM?754305^MDC_IDC_ENUM_POLARITY_UNI^MDCMDC_IDC_MSMT_LEADCHNL_LA_

ENUMEncounter

Measured Left

VentricleLead Low

Power Channel

Impedance Polarity

DateTimeEncounter

Measured Right

Ventricle Lead

High Power

Channel

Connectivity Guide | HL7 Integration | 63

PaceartIDCO

3-1

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Impedance Start

Date

MDC_IDC_MSMT_LEADHVCHNL_DTM_START722561

Measured Right

Ventricle Lead

High Power

Channel

Impedance Start

Date

MDC_IDC_MSMT_LEADHVCHNL_DTM_END722562

Measured Right

Ventricle Lead

High Power

Channel

Impedance End

Date

MDC_IDC_MSMT_LEADHVCHNL_IMPEDANCE722624

Measured Right

Ventricle Lead

High Power

Channel

Impedance

Measurement

Value

Parameter

Type

DateTimeEncounter

NumericEncounter

Table : MDC_IDC_SET

729344

729408

729536

MDC_IDC_SET_CRT_LVRV_

DELAY

MDC_IDC_SET_CRT_PACED_

CHAMBERS

MDC_IDC_SET_LEADCHNL_RA_

SENSING_SENSITIVITY

Supported Values (OBX 5)OBX 3-2OBX 3-1

755265^MDC_IDC_ENUM_CRT_PACED_CHAMBERS_RV_Only^MDC

755266^MDC_IDC_ENUM_CRT_PACED_CHAMBERS_LV_ Only^MDC

755267^MDC_IDC_ENUM_CRT_PACED_CHAMBERS_ BiV^MDC

PaceartIDCO

Parameter

Name

Programmed

VV Delay

Programmed

Heart Failure

Ventricular

Pacing

Configuration

Programmed

Bradycardia

Right Atrium

Sensing

Amplitude

Parameter

Type

NumericEncounter

ENUMEncounter

NumericEncounter

64 | Connectivity Guide | HL7 Integration

PaceartIDCO

729600

729920

729664

729665

729666

729667

MDC_IDC_SET_LEADCHNL_RA_

SENSING_POLARITY

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ADAPTATION_MODE

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ANODE_LOCATION

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ANODE_LOCATION_1

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ANODE_LOCATION_2

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ANODE_LOCATION_3

Supported Values (OBX 5)OBX 3-2OBX 3-1

754305^MDC_IDC_ENUM_POLARITY_UNI^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754625^MDC_IDC_ENUM_SENSING_ADAPTATION_MODE_

AdaptiveSensing^MDC

754626^MDC_IDC_ENUM_SENSING_ADAPTATION_MODE_

FixedPacing^MDC

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

Parameter

Name

Programmed

Bradycardia

Right Atrium

Sensing

Polarity

Programmed

Bradycardia

Right Atrium

Sensing

Amplitude

Adaptation

Mode

Programmed

Bradycardia

Right Atrium

Sensing

Pathway

Location

Parameter

Type

ENUMEncounter

729792

729793

729794

729795

729728

729729

729730

729731

MDC_IDC_SET_LEADCHNL_RA_

SENSING_CATHODE_LOCATION

MDC_IDC_SET_LEADCHNL_RA_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RA_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RA_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ANODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_RA_

SENSING_ANODE_ELECTRODE_

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

ENUMEncounter

Programmed

Bradycardia

Right Atrium

Sensing

Pathway

Electrode

Connectivity Guide | HL7 Integration | 65

PaceartIDCO

729856

729857

729858

729859

729537

729601

SENSING_CATHODE_

ELECTRODE

MDC_IDC_SET_LEADCHNL_RA_

SENSING_CATHODE_

ELECTRODE_1

MDC_IDC_SET_LEADCHNL_RA_

SENSING_CATHODE_

ELECTRODE_2

MDC_IDC_SET_LEADCHNL_RA_

SENSING_CATHODE_

ELECTRODE_3

MDC_IDC_SET_LEADCHNL_RV_

SENSING_SENSITIVITY

MDC_IDC_SET_LEADCHNL_RV_

SENSING_POLARITY

Supported Values (OBX 5)OBX 3-2OBX 3-1

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDCMDC_IDC_SET_LEADCHNL_RA_

754305^MDC_IDC_ENUM_POLARITY_UNI^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

Parameter

Name

Programmed

Bradycardia

Right Ventricle

Sensing

Amplitude

Programmed

Bradycardia

Right Ventricle

Sensing

Polarity

Parameter

Type

NumericEncounter

ENUMEncounter

729921

729668

729669

729670

729671

729796

729797

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ADAPTATION_MODE

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ANODE_LOCATION

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ANODE_LOCATION_1

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ANODE_LOCATION_2

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ANODE_LOCATION_3

MDC_IDC_SET_LEADCHNL_RV_

SENSING_CATHODE_LOCATION

MDC_IDC_SET_LEADCHNL_RV_

SENSING_CATHODE_LOCATION_

754625^MDC_IDC_ENUM_SENSING_ADAPTATION_MODE_

AdaptiveSensing^MDC

754626^MDC_IDC_ENUM_SENSING_ADAPTATION_MODE_

FixedPacing^MDC

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

ENUMEncounter

Programmed

Bradycardia

Right Ventricle

Sensing

Amplitude

Adaptation

Mode

ENUMEncounter

Programmed

Bradycardia

Right Ventricle

Sensing

Pathway

Location

66 | Connectivity Guide | HL7 Integration

PaceartIDCO

729798

729799

729732

729733

729734

729735

729860

MDC_IDC_SET_LEADCHNL_RV_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RV_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ANODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_RV_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_RV_

SENSING_CATHODE_

ELECTRODE

Supported Values (OBX 5)OBX 3-2OBX 3-1

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDC

Parameter

Name

Programmed

Bradycardia

Right Ventricle

Sensing

Pathway

Electrode

Parameter

Type

ENUMEncounter

729861

729862

729863

729538

729602

729922

MDC_IDC_SET_LEADCHNL_RV_

SENSING_CATHODE_

ELECTRODE_1

MDC_IDC_SET_LEADCHNL_RV_

SENSING_CATHODE_

ELECTRODE_2

MDC_IDC_SET_LEADCHNL_RV_

SENSING_CATHODE_

ELECTRODE_3

MDC_IDC_SET_LEADCHNL_LA_

SENSING_SENSITIVITY

MDC_IDC_SET_LEADCHNL_LA_

SENSING_POLARITY

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ADAPTATION_MODE

754305^MDC_IDC_ENUM_POLARITY_UNI^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754625^MDC_IDC_ENUM_SENSING_ADAPTATION_MODE_

AdaptiveSensing^MDC

NumericEncounter

Programmed

Bradycardia

Left Atrium

Sensing

Amplitude

ENUMEncounter

Programmed

Bradycardia

Left Atrium

Sensing

Polarity

ENUMEncounter

Programmed

Bradycardia

Connectivity Guide | HL7 Integration | 67

PaceartIDCO

729672

729673

729674

729675

729800

729801

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ANODE_LOCATION

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ANODE_LOCATION_1

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ANODE_LOCATION_2

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ANODE_LOCATION_3

MDC_IDC_SET_LEADCHNL_LA_

SENSING_CATHODE_LOCATION

MDC_IDC_SET_LEADCHNL_LA_

SENSING_CATHODE_LOCATION_

Supported Values (OBX 5)OBX 3-2OBX 3-1

754626^MDC_IDC_ENUM_SENSING_ADAPTATION_MODE_

FixedPacing^MDC

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

Parameter

Name

Left Atrium

Sensing

Amplitude

Adaptation

Mode

Programmed

Bradycardia

Left Atrium

Sensing

Pathway

Location

Parameter

Type

ENUMEncounter

729802

729803

729736

729737

729738

729739

729864

729865

MDC_IDC_SET_LEADCHNL_LA_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LA_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ANODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_LA_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_LA_

SENSING_CATHODE_

ELECTRODE

MDC_IDC_SET_LEADCHNL_LA_

SENSING_CATHODE_

ELECTRODE_1

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDC

ENUMEncounter

Programmed

Bradycardia

Left Atrium

Sensing

Pathway

Electrode

68 | Connectivity Guide | HL7 Integration

PaceartIDCO

729866

729867

729539

729603

729923

MDC_IDC_SET_LEADCHNL_LA_

SENSING_CATHODE_

ELECTRODE_2

MDC_IDC_SET_LEADCHNL_LA_

SENSING_CATHODE_

ELECTRODE_3

MDC_IDC_SET_LEADCHNL_LV_

SENSING_SENSITIVITY

MDC_IDC_SET_LEADCHNL_LV_

SENSING_POLARITY

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ADAPTATION_MODE

Supported Values (OBX 5)OBX 3-2OBX 3-1

754305^MDC_IDC_ENUM_POLARITY_UNI^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754625^MDC_IDC_ENUM_SENSING_ADAPTATION_MODE_

AdaptiveSensing^MDC

754626^MDC_IDC_ENUM_SENSING_ADAPTATION_MODE_

FixedPacing^MDC

Parameter

Name

Programmed

Bradycardia

Left Ventricle

Sensing

Amplitude

Programmed

Bradycardia

Right Ventricle

Sensing

Polarity

Programmed

Bradycardia

Left Ventricle

Sensing

Amplitude

Adaptation

Mode

Parameter

Type

NumericEncounter

ENUMEncounter

729676

729677

729678

729679

729804

729805

729806

729807

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ANODE_LOCATION

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ANODE_LOCATION_1

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ANODE_LOCATION_2

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ANODE_LOCATION_3

MDC_IDC_SET_LEADCHNL_LV_

SENSING_CATHODE_LOCATION

MDC_IDC_SET_LEADCHNL_LV_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LV_

SENSING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LV_

SENSING_CATHODE_LOCATION_

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

ENUMEncounter

Programmed

Bradycardia

Left Ventricle

Sensing

Pathway

Location

Connectivity Guide | HL7 Integration | 69

PaceartIDCO

729740

729741

729742

729743

729868

729869

729870

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ANODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_LV_

SENSING_ANODE_ELECTRODE_

MDC_IDC_SET_LEADCHNL_LV_

SENSING_CATHODE_

ELECTRODE

MDC_IDC_SET_LEADCHNL_LV_

SENSING_CATHODE_

ELECTRODE_1

MDC_IDC_SET_LEADCHNL_LV_

SENSING_CATHODE_

ELECTRODE_2

Supported Values (OBX 5)OBX 3-2OBX 3-1

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDC

Parameter

Name

Programmed

Bradycardia

Left Ventricle

Sensing

Pathway

Electrode

Parameter

Type

ENUMEncounter

729871

729984

730048

730112

730432

MDC_IDC_SET_LEADCHNL_LV_

SENSING_CATHODE_

ELECTRODE_3

MDC_IDC_SET_LEADCHNL_RA_

PACING_AMPLITUDE

MDC_IDC_SET_LEADCHNL_RA_

PACING_PULSEWIDTH

MDC_IDC_SET_LEADCHNL_RA_

PACING_POLARITY

MDC_IDC_SET_LEADCHNL_RA_

PACING_CAPTURE_MODE

754305^MDC_IDC_ENUM_POLARITY_UNI^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754689^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

AdaptiveCapture^MDC

754690^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

FixedPacing^MDC

NumericEncounter

Programmed

Bradycardia

Right Atrium

Pacing

Amplitude

NumericEncounter

Programmed

Bradycardia

Right Atrium

Pacing Pulse

Width

ENUMEncounter

Programmed

Bradycardia

Right Atrium

Pacing Polarity

ENUMEncounter

Programmed

Bradycardia

Right Atrium

Pacing

70 | Connectivity Guide | HL7 Integration

PaceartIDCO

730176

730177

730178

730179

730304

730305

730306

MDC_IDC_SET_LEADCHNL_RA_

PACING_ANODE_LOCATION

MDC_IDC_SET_LEADCHNL_RA_

PACING_ANODE_LOCATION_1

MDC_IDC_SET_LEADCHNL_RA_

PACING_ANODE_LOCATION_2

MDC_IDC_SET_LEADCHNL_RA_

PACING_ANODE_LOCATION_3

MDC_IDC_SET_LEADCHNL_RA_

PACING_CATHODE_LOCATION

MDC_IDC_SET_LEADCHNL_RA_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RA_

PACING_CATHODE_LOCATION_

Supported Values (OBX 5)OBX 3-2OBX 3-1

754691^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

MonitorCapture^MDC

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

Parameter

Name

Adaptation

Mode

Programmed

Bradycardia

Right Atrium

Pacing

Pathway

Location

Parameter

Type

ENUMEncounter

730307

730240

730241

730242

730243

730368

730369

730370

730371

MDC_IDC_SET_LEADCHNL_RA_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RA_

PACING_ANODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_RA_

PACING_ANODE_ELECTRODE_1

MDC_IDC_SET_LEADCHNL_RA_

PACING_ANODE_ELECTRODE_2

MDC_IDC_SET_LEADCHNL_RA_

PACING_ANODE_ELECTRODE_3

MDC_IDC_SET_LEADCHNL_RA_

PACING_CATHODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_RA_

PACING_CATHODE_

ELECTRODE_1

MDC_IDC_SET_LEADCHNL_RA_

PACING_CATHODE_

ELECTRODE_2

MDC_IDC_SET_LEADCHNL_RA_

PACING_CATHODE_

ELECTRODE_3

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDC

ENUMEncounter

Programmed

Bradycardia

Right Atrium

Pacing

Pathway

Electrode

729985

MDC_IDC_SET_LEADCHNL_RV_

PACING_AMPLITUDE

NumericEncounter

Programmed

Connectivity Guide | HL7 Integration | 71

PaceartIDCO

730049

730113

730433

MDC_IDC_SET_LEADCHNL_RV_

PACING_PULSEWIDTH

MDC_IDC_SET_LEADCHNL_RV_

PACING_POLARITY

MDC_IDC_SET_LEADCHNL_RV_

PACING_CAPTURE_MODE

Supported Values (OBX 5)OBX 3-2OBX 3-1

754305^MDC_IDC_ENUM_POLARITY_UNI^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754689^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

AdaptiveCapture^MDC

754690^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

FixedPacing^MDC

754691^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

MonitorCapture^MDC

Parameter

Name

Bradycardia

Right Ventricle

Pacing

Amplitude

Programmed

Bradycardia

Right Ventricle

Pacing Pulse

Width

Programmed

Bradycardia

Right Ventricle

Pacing Polarity

Programmed

Bradycardia

Right Ventricle

Pacing

Adaptation

Mode

Parameter

Type

NumericEncounter

ENUMEncounter

730180

730181

730182

730183

730308

730309

730310

730311

730244

MDC_IDC_SET_LEADCHNL_RV_

PACING_ANODE_LOCATION

MDC_IDC_SET_LEADCHNL_RV_

PACING_ANODE_LOCATION_1

MDC_IDC_SET_LEADCHNL_RV_

PACING_ANODE_LOCATION_2

MDC_IDC_SET_LEADCHNL_RV_

PACING_ANODE_LOCATION_3

MDC_IDC_SET_LEADCHNL_RV_

PACING_CATHODE_LOCATION

MDC_IDC_SET_LEADCHNL_RV_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RV_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RV_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_RV_

PACING_ANODE_ELECTRODE

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

ENUMEncounter

Programmed

Bradycardia

Right Ventricle

Pacing

Pathway

Location

ENUMEncounter

Programmed

Bradycardia

72 | Connectivity Guide | HL7 Integration

PaceartIDCO

Supported Values (OBX 5)OBX 3-2OBX 3-1

730245 Right Ventricle

730246

730183

730372

730373

730374

730375

729986

MDC_IDC_SET_LEADCHNL_RV_

PACING_ANODE_ELECTRODE_1

MDC_IDC_SET_LEADCHNL_RV_

PACING_ANODE_ELECTRODE_2

MDC_IDC_SET_LEADCHNL_RV_

PACING_ANODE_ELECTRODE_3

MDC_IDC_SET_LEADCHNL_RV_

PACING_CATHODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_RV_

PACING_CATHODE_

ELECTRODE_1

MDC_IDC_SET_LEADCHNL_RV_

PACING_CATHODE_

ELECTRODE_2

MDC_IDC_SET_LEADCHNL_RV_

PACING_CATHODE_

ELECTRODE_3

MDC_IDC_SET_LEADCHNL_LA_

PACING_AMPLITUDE

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDC

Parameter

Name

Pacing

Pathway

Electrode

Programmed

Bradycardia

Left Atrium

Pacing

Amplitude

Parameter

Type

NumericEncounter

730050

730114

730434

730184

MDC_IDC_SET_LEADCHNL_LA_

PACING_PULSEWIDTH

MDC_IDC_SET_LEADCHNL_LA_

PACING_POLARITY

MDC_IDC_SET_LEADCHNL_LA_

PACING_CAPTURE_MODE

MDC_IDC_SET_LEADCHNL_LA_

PACING_ANODE_LOCATION

754305^MDC_IDC_ENUM_POLARITY_UNI^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754689^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

AdaptiveCapture^MDC

754690^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

FixedPacing^MDC

754691^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

MonitorCapture^MDC

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

NumericEncounter

Programmed

Bradycardia

Left Atrium

Pacing Pulse

Width

ENUMEncounter

Programmed

Bradycardia

Left Atrium

Pacing Polarity

ENUMEncounter

Programmed

Bradycardia

Left Atrium

Pacing

Adaptation

Mode

ENUMEncounter

Programmed

Bradycardia

Connectivity Guide | HL7 Integration | 73

PaceartIDCO

Supported Values (OBX 5)OBX 3-2OBX 3-1

730185 Left Atrium

730186

730187

730312

730313

730314

730315

730248

730249

730250

730251

730376

730377

MDC_IDC_SET_LEADCHNL_LA_

PACING_ANODE_LOCATION_1

MDC_IDC_SET_LEADCHNL_LA_

PACING_ANODE_LOCATION_2

MDC_IDC_SET_LEADCHNL_LA_

PACING_ANODE_LOCATION_3

MDC_IDC_SET_LEADCHNL_LA_

PACING_CATHODE_LOCATION

MDC_IDC_SET_LEADCHNL_LA_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LA_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LA_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LA_

PACING_ANODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_LA_

PACING_ANODE_ELECTRODE_1

MDC_IDC_SET_LEADCHNL_LA_

PACING_ANODE_ELECTRODE_2

MDC_IDC_SET_LEADCHNL_LA_

PACING_ANODE_ELECTRODE_3

MDC_IDC_SET_LEADCHNL_LA_

PACING_CATHODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_LA_

PACING_CATHODE_

ELECTRODE_1

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDC

Parameter

Name

Pacing

Pathway

Location

Programmed

Bradycardia

Left Atrium

Pacing

Pathway

Electrode

Parameter

Type

ENUMEncounter

730378

730379

729987

MDC_IDC_SET_LEADCHNL_LA_

PACING_CATHODE_

ELECTRODE_2

MDC_IDC_SET_LEADCHNL_LA_

PACING_CATHODE_

ELECTRODE_3

MDC_IDC_SET_LEADCHNL_LV_

PACING_AMPLITUDE

NumericEncounter

Programmed

Bradycardia

Left Ventricle

Pacing

Amplitude

74 | Connectivity Guide | HL7 Integration

PaceartIDCO

730051

730115

730435

730188

730189

730190

730191

MDC_IDC_SET_LEADCHNL_LV_

PACING_PULSEWIDTH

MDC_IDC_SET_LEADCHNL_LV_

PACING_POLARITY

MDC_IDC_SET_LEADCHNL_LV_

PACING_CAPTURE_MODE

MDC_IDC_SET_LEADCHNL_LV_

PACING_ANODE_LOCATION

MDC_IDC_SET_LEADCHNL_LV_

PACING_ANODE_LOCATION_1

MDC_IDC_SET_LEADCHNL_LV_

PACING_ANODE_LOCATION_2

MDC_IDC_SET_LEADCHNL_LV_

PACING_ANODE_LOCATION_3

Supported Values (OBX 5)OBX 3-2OBX 3-1

754305^MDC_IDC_ENUM_POLARITY_UNI^MDC

754306^MDC_IDC_ENUM_POLARITY_BI^MDC

754689^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

AdaptiveCapture^MDC

754690^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

FixedPacing^MDC

754691^MDC_IDC_ENUM_PACING_CAPTURE_MODE_

MonitorCapture^MDC

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

Parameter

Name

Programmed

Bradycardia

Left Ventricle

Pacing Pulse

Width

Programmed

Bradycardia

Left Ventricle

Pacing Polarity

Programmed

Bradycardia

Left Ventricle

Pacing

Adaptation

Mode

Programmed

Bradycardia

Left Ventricle

Pacing

Pathway

Location

Parameter

Type

NumericEncounter

ENUMEncounter

730316

730317

730318

730319

730252

730253

730254

MDC_IDC_SET_LEADCHNL_LV_

PACING_CATHODE_ LOCATION

MDC_IDC_SET_LEADCHNL_LV_

PACING_CATHODE_ LOCATION_1

MDC_IDC_SET_LEADCHNL_LV_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LV_

PACING_CATHODE_LOCATION_

MDC_IDC_SET_LEADCHNL_LV_

PACING_ANODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_LV_

PACING_ANODE_ELECTRODE_1

MDC_IDC_SET_LEADCHNL_LV_

PACING_ANODE_ELECTRODE_2

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

ENUMEncounter

Programmed

Bradycardia

Left Ventricle

Pacing

Pathway

Electrode

Connectivity Guide | HL7 Integration | 75

PaceartIDCO

Supported Values (OBX 5)OBX 3-2OBX 3-1

730255 754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

730380

730381

730382

730383

MDC_IDC_SET_LEADCHNL_LV_

PACING_ANODE_ELECTRODE_3

MDC_IDC_SET_LEADCHNL_LV_

PACING_CATHODE_ELECTRODE

MDC_IDC_SET_LEADCHNL_LV_

PACING_CATHODE_

ELECTRODE_1

MDC_IDC_SET_LEADCHNL_LV_

PACING_CATHODE_

ELECTRODE_2

MDC_IDC_SET_LEADCHNL_LV_

PACING_CATHODE_

ELECTRODE_3

MDC_IDC_SET_BRADY_MODE730752

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDC

754753^MDC_IDC_ENUM_BRADY_MODE_AAI^MDC

754754^MDC_IDC_ENUM_BRADY_MODE_AAIR^MDC

754755^MDC_IDC_ENUM_BRADY_MODE_AAT^MDC

754756^MDC_IDC_ENUM_BRADY_MODE_AATR^MDC

754757^MDC_IDC_ENUM_BRADY_MODE_AOO^MDC

754758^MDC_IDC_ENUM_BRADY_MODE_AOOR^MDC

754759^MDC_IDC_ENUM_BRADY_MODE_DAD^MDC

754760^MDC_IDC_ENUM_BRADY_MODE_DDD^MDC

754761^MDC_IDC_ENUM_BRADY_MODE_DDDR^MDC

754762^MDC_IDC_ENUM_BRADY_MODE_DDI^MDC

754763^MDC_IDC_ENUM_BRADY_MODE_DDIR^MDC

754764^MDC_IDC_ENUM_BRADY_MODE_DOO^MDC

754765^MDC_IDC_ENUM_BRADY_MODE_DOOR^MDC

754766^MDC_IDC_ENUM_BRADY_MODE_DVI^MDC

754767^MDC_IDC_ENUM_BRADY_MODE_DVIR^MDC

754768^MDC_IDC_ENUM_BRADY_MODE_VAT^MDC

754769^MDC_IDC_ENUM_BRADY_MODE_VDD^MDC

754770^MDC_IDC_ENUM_BRADY_MODE_VDDR^MDC

754771^MDC_IDC_ENUM_BRADY_MODE_VOO^MDC

754772^MDC_IDC_ENUM_BRADY_MODE_VOOR^MDC

754773^MDC_IDC_ENUM_BRADY_MODE_VVI^MDC

754774^MDC_IDC_ENUM_BRADY_MODE_VVIR^MDC

754775^MDC_IDC_ENUM_BRADY_MODE_VVT^MDC

754776^MDC_IDC_ENUM_BRADY_MODE_OOO^MDC

754777^MDC_IDC_ENUM_BRADY_MODE_OOOR^MDC

754778^MDC_IDC_ENUM_BRADY_MODE_VDI^MDC

Parameter

Name

Programmed

Bradycardia

Pacing Mode

Parameter

Type

ENUMEncounter

76 | Connectivity Guide | HL7 Integration

PaceartIDCO

730880

730944

MDC_IDC_SET_BRADY_

LOWRATE

MDC_IDC_SET_BRADY_

HYSTRATE

Supported Values (OBX 5)OBX 3-2OBX 3-1

754779^MDC_IDC_ENUM_BRADY_MODE_VDIR^MDC

754780^MDC_IDC_ENUM_BRADY_MODE_ODO^MDC

754781^MDC_IDC_ENUM_BRADY_MODE_VVTR^MDC

754782^MDC_IDC_ENUM_BRADY_MODE_DDTR^MDC

754783^MDC_IDC_ENUM_BRADY_MODE_OVO^MDC

754784^MDC_IDC_ENUM_BRADY_MODE_DVTR^MDC

754785^MDC_IDC_ENUM_BRADY_MODE_DDT^MDC

754786^MDC_IDC_ENUM_BRADY_MODE_VDTR^MDC

754787^MDC_IDC_ENUM_BRADY_MODE_VDT^MDC

754788^MDC_IDC_ENUM_BRADY_MODE_ADIR^MDC

754789^MDC_IDC_ENUM_BRADY_MODE_ADI^MDC

754790^MDC_IDC_ENUM_BRADY_MODE_Unknown

Parameter

Name

Programmed

Bradycardia

Lower Rate

Programmed

Bradycardia

Hysteresis Rate

Parameter

Type

NumericEncounter

731008

731136

731200

731264

731265

MDC_IDC_SET_BRADY_NIGHT_

RATE

MDC_IDC_SET_BRADY_MAX_

TRACKING_RATE

MDC_IDC_SET_BRADY_MAX_

SENSOR_RATE

MDC_IDC_SET_BRADY_SAV_

DELAY

MDC_IDC_SET_BRADY_SAV_

DELAY_HIGH

NumericEncounter

Programmed

Bradycardia

Sleep Rate

NumericEncounter

Programmed

Bradycardia

Maximum

Tracking Rate

NumericEncounter

Programmed

Bradycardia

Maximum

Sensor Rate

NumericEncounter

Programmed

Bradycardia AV

Delay Adaptive

Sensed

Minimum

NumericEncounter

Programmed

Bradycardia AV

Connectivity Guide | HL7 Integration | 77

PaceartIDCO

731266

731328

731329

731330

MDC_IDC_SET_BRADY_SAV_

DELAY_LOW

MDC_IDC_SET_BRADY_PAV_

DELAY

MDC_IDC_SET_BRADY_PAV_

DELAY_HIGH

MDC_IDC_SET_BRADY_PAV_

DELAY_LOW

Supported Values (OBX 5)OBX 3-2OBX 3-1

Parameter

Name

Delay Adaptive

Sensed

Minimum

Programmed

Bradycardia AV

Delay Sensed

Programmed

Bradycardia AV

Delay Adaptive

Paced

Minimum

Programmed

Bradycardia AV

Delay Adaptive

Paced

Minimum

Programmed

Bradycardia AV

Delay Paced

Parameter

Type

NumericEncounter

731392

MDC_IDC_SET_BRADY_AT_

MODE_SWITCH_MODE

754753^MDC_IDC_ENUM_BRADY_MODE_AAI^MDC

754754^MDC_IDC_ENUM_BRADY_MODE_AAIR^MDC

754755^MDC_IDC_ENUM_BRADY_MODE_AAT^MDC

754756^MDC_IDC_ENUM_BRADY_MODE_AATR^MDC

754757^MDC_IDC_ENUM_BRADY_MODE_AOO^MDC

754758^MDC_IDC_ENUM_BRADY_MODE_AOOR^MDC

754759^MDC_IDC_ENUM_BRADY_MODE_DAD^MDC

754760^MDC_IDC_ENUM_BRADY_MODE_DDD^MDC

754761^MDC_IDC_ENUM_BRADY_MODE_DDDR^MDC

754762^MDC_IDC_ENUM_BRADY_MODE_DDI^MDC

754763^MDC_IDC_ENUM_BRADY_MODE_DDIR^MDC

754764^MDC_IDC_ENUM_BRADY_MODE_DOO^MDC

754765^MDC_IDC_ENUM_BRADY_MODE_DOOR^MDC

754766^MDC_IDC_ENUM_BRADY_MODE_DVI^MDC

754767^MDC_IDC_ENUM_BRADY_MODE_DVIR^MDC

754768^MDC_IDC_ENUM_BRADY_MODE_VAT^MDC

754769^MDC_IDC_ENUM_BRADY_MODE_VDD^MDC

754770^MDC_IDC_ENUM_BRADY_MODE_VDDR^MDC

754771^MDC_IDC_ENUM_BRADY_MODE_VOO^MDC

ENUMEncounter

Programmed

Bradycardia

Automatic

Mode Switch

Therapy Pacing

Mode

78 | Connectivity Guide | HL7 Integration

PaceartIDCO

Supported Values (OBX 5)OBX 3-2OBX 3-1

754772^MDC_IDC_ENUM_BRADY_MODE_VOOR^MDC

754773^MDC_IDC_ENUM_BRADY_MODE_VVI^MDC

754774^MDC_IDC_ENUM_BRADY_MODE_VVIR^MDC

754775^MDC_IDC_ENUM_BRADY_MODE_VVT^MDC

754776^MDC_IDC_ENUM_BRADY_MODE_OOO^MDC

754777^MDC_IDC_ENUM_BRADY_MODE_OOOR^MDC

754778^MDC_IDC_ENUM_BRADY_MODE_VDI^MDC

754779^MDC_IDC_ENUM_BRADY_MODE_VDIR^MDC

754780^MDC_IDC_ENUM_BRADY_MODE_ODO^MDC

754781^MDC_IDC_ENUM_BRADY_MODE_VVTR^MDC

754782^MDC_IDC_ENUM_BRADY_MODE_DDTR^MDC

754783^MDC_IDC_ENUM_BRADY_MODE_OVO^MDC

754784^MDC_IDC_ENUM_BRADY_MODE_DVTR^MDC

754785^MDC_IDC_ENUM_BRADY_MODE_DDT^MDC

754786^MDC_IDC_ENUM_BRADY_MODE_VDTR^MDC

754787^MDC_IDC_ENUM_BRADY_MODE_VDT^MDC

754788^MDC_IDC_ENUM_BRADY_MODE_ADIR^MDC

754789^MDC_IDC_ENUM_BRADY_MODE_ADI^MDC

754790^MDC_IDC_ENUM_BRADY_MODE_Unknown

Parameter

Name

Parameter

Type

731456

731712

MDC_IDC_SET_BRADY_AT_

MODE_SWITCH_RATE

MDC_IDC_SET_ZONE_TYPE731648

MDC_IDC_SET_ZONE_VENDOR_

TYPE

754945^MDC_IDC_ENUM_ZONE_TYPE_Zone_VF^MDC

754946^MDC_IDC_ENUM_ZONE_TYPE_Zone_VT^MDC

754947^MDC_IDC_ENUM_ZONE_TYPE_Zone_ATAF^MDC

770113^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_

BIO-Zone_VF^MDC

770118^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_

BIO-Zone_ATAF^MDC

770121^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_

BIO-Zone_AT^MDC

771137^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_ BSX_

Zone_VT^MDC

771138^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_ BSX_

Zone_VT-1^MDC

771139^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_ BSX-Zone_VF

NumericEncounter

Programmed

Bradycardia

Automatic

Mode Switch

Detection

Criteria Rate

ENUMEncounter

Programmed

Tachycardia

Zone Type

ENUMEncounter

Programmed

Tachycardia

Zone Type

Connectivity Guide | HL7 Integration | 79

PaceartIDCO

731840

731904

MDC_IDC_SET_ZONE_STATUS731776

MDC_IDC_SET_ZONE_

DETECTION_INTERVAL

MDC_IDC_SET_ZONE_

DETECTION_BEATS_

NUMERATOR

Supported Values (OBX 5)OBX 3-2OBX 3-1

771142^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_ BSX-Zone_AF

771143^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_ BSX-Zone_AT

773188^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_ STJ-Zone_

VT1^MDC

773189^MDC_IDC_ENUM_ZONE_VENDOR_TYPE_ STJ-Zone_

VT2^MDC

755009^MDC_IDC_ENUM_ZONE_STATUS_Active ^MDC

755010^MDC_IDC_ENUM_ZONE_STATUS_Inactive ^MDC

755011^MDC_IDC_ENUM_ZONE_STATUS_Monitor ^MDC

Parameter

Name

Programmed

Tachycardia

Zone Detection

Status

Programmed

Tachycardia

Zone Detection

Interval

Programmed

Tachycardia

Zone Shared

Detection

Duration Beat

Ratio

Numerator

Parameter

Type

ENUMEncounter

NumericEncounter

731968

732225

732226

732227

732228

732229

732230

MDC_IDC_SET_ZONE_

DETECTION_BEATS_

DENOMINATOR

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_1

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_2

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_3

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_4

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_5

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_6

NumericEncounter

Programmed

Tachycardia

Zone Shared

Detection

Duration Beat

Ratio

Denominator

NumericEncounter

Programmed

Tachycardia

Shock Therapy

Energy

80 | Connectivity Guide | HL7 Integration

PaceartIDCO

732231

732232

732233

732234

732097

732098

732099

732100

732101

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_7

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_8

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_9

MDC_IDC_SET_ZONE_SHOCK_

ENERGY_10

MDC_IDC_SET_ZONE_TYPE_

ATP_1

MDC_IDC_SET_ZONE_TYPE_

ATP_2

MDC_IDC_SET_ZONE_TYPE_

ATP_3

MDC_IDC_SET_ZONE_TYPE_

ATP_4

MDC_IDC_SET_ZONE_TYPE_

ATP_5

Supported Values (OBX 5)OBX 3-2OBX 3-1

755073^MDC_IDC_ENUM_ATP_TYPE_Burst^MDC

755074^MDC_IDC_ENUM_ATP_TYPE_Ramp^MDC

755075^MDC_IDC_ENUM_ATP_TYPE_BurstScan^MDC

755076^MDC_IDC_ENUM_ATP_TYPE_RampScan^MDC

755078^MDC_IDC_ENUM_ATP_TYPE_Unknown^MDC

Parameter

Name

Programmed

Tachycardia

ATP Therapy

Type

Parameter

Type

ENUMEncounter

732102

732103

732104

732105

732106

732161

732162

732163

732164

732165

MDC_IDC_SET_ZONE_TYPE_

ATP_6

MDC_IDC_SET_ZONE_TYPE_

ATP_7

MDC_IDC_SET_ZONE_TYPE_

ATP_8

MDC_IDC_SET_ZONE_TYPE_

ATP_9

MDC_IDC_SET_ZONE_TYPE_

ATP_10

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_1

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_2

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_3

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_4

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_5

NumericEncounter

Programmed

Tachycardia

ATP Therapy

Sequence ID

732166

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_6

Connectivity Guide | HL7 Integration | 81

PaceartIDCO

732167

732168

732169

732170

730497

730498

730499

730625

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_7

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_8

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_9

MDC_IDC_SET_ZONE_NUM_ATP_

SEQS_10

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_ANODE_

LOCATION_1

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_ANODE_

LOCATION_2

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_ANODE_

LOCATION_3

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_CATHODE_

LOCATION_1

Supported Values (OBX 5)OBX 3-2OBX 3-1

754497^MDC_IDC_ENUM_ELECTRODE_LOCATION_RA^MDC

754498^MDC_IDC_ENUM_ELECTRODE_LOCATION_RV^MDC

754499^MDC_IDC_ENUM_ELECTRODE_LOCATION_LA^MDC

754500^MDC_IDC_ENUM_ELECTRODE_LOCATION_LV^MDC

754501^MDC_IDC_ENUM_ELECTRODE_LOCATION_SVC^MDC

754503^MDC_IDC_ENUM_ELECTRODE_LOCATION_Unknown^MDC

Parameter

Name

Programmed

Tachycardia

Shock Therapy

Pathway

Location

Parameter

Type

ENUMEncounter

730626

730627

730561

730562

730563

730689

730690

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_CATHODE_

LOCATION_2

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_CATHODE_

LOCATION_3

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_ANODE_

ELECTRODE_1

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_ANODE_

ELECTRODE_2

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_ANODE_

ELECTRODE_3

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_CATHODE_

ELECTRODE_1

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_CATHODE_

ELECTRODE_2

754561^MDC_IDC_ENUM_ELECTRODE_NAME_Tip^MDC

754562^MDC_IDC_ENUM_ELECTRODE_NAME_Ring^MDC

754563^MDC_IDC_ENUM_ELECTRODE_NAME_Ring1^MDC

754564^MDC_IDC_ENUM_ELECTRODE_NAME_Ring2^MDC

754565^MDC_IDC_ENUM_ELECTRODE_NAME_Ring3^MDC

754566^MDC_IDC_ENUM_ELECTRODE_NAME_Ring4^MDC

754567^MDC_IDC_ENUM_ELECTRODE_NAME_Coil^MDC

754568^MDC_IDC_ENUM_ELECTRODE_NAME_SubQPatch^MDC

754569^MDC_IDC_ENUM_ELECTRODE_NAME_Can^MDC

754580^MDC_IDC_ENUM_ELECTRODE_NAME_Unknown^MDC

ENUMEncounter

Programmed

Tachycardia

Shock Therapy

Pathway

Electrode

82 | Connectivity Guide | HL7 Integration

PaceartIDCO

730691

MDC_IDC_SET_LEADHVCHNL_

SHOCK_VECTOR_CATHODE_

ELECTRODE_3

Table : MDC_IDC_STAT

3-1

MDC_IDC_STAT_HEART_RATE_DTM_START737617

MDC_IDC_STAT_HEART_RATE_DTM_END737618

Supported Values (OBX 5)OBX 3-2OBX 3-1

Parameter

Name

PaceartIDCO

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Measured

Physiological

Measurements

Since Last Session

Start Date

Measured

Physiological

Measurements

Since Last Session

End Date

Parameter

Type

Parameter

Type

DateTimeEncounter

MDC_IDC_STAT_HEART_RATE_ATRIAL737632

Measured

Physiological

Measurements

Since Last Session

Right Atrium

Measured Heart

Rate

MDC_IDC_STAT_HEART_RATE_ATRIAL_MAX737633

Measured

Physiological

Measurements

Since Last Session

Right Atrium

Maximum Heart

Rate

MDC_IDC_STAT_HEART_RATE_ATRIAL_MIN737634

Measured

Physiological

Measurements

Since Last Session

Right Atrium

Minimum Heart Rate

IntegerEncounter

MDC_IDC_STAT_HEART_RATE_ATRIAL_MEAN737635

Measured

Physiological

IntegerEncounter

Connectivity Guide | HL7 Integration | 83

PaceartIDCO

3-1

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Measurements

Since Last Session

Right Atrium Mean

Heart Rate

MDC_IDC_STAT_HEART_RATE_VENTRICULAR737648

Measured

Physiological

Measurements

Since Last Session

Right Ventricle

Measured Heart

Rate

MDC_IDC_STAT_HEART_RATE_VENTRICULAR_MAX737649

Measured

Physiological

Measurements

Since Last Session

Right Ventricle

Maximum Heart

Rate

Parameter

Type

IntegerEncounter

MDC_IDC_STAT_HEART_RATE_VENTRICULAR_MIN737650

Measured

Physiological

Measurements

Since Last Session

Right Ventricle

Minimum Heart Rate

MDC_IDC_STAT_HEART_RATE_VENTRICULAR_MEAN737651

Measured

Physiological

Measurements

Since Last Session

Right Ventricle

Mean Heart Rate

MDC_IDC_STAT_BRADY_DTM_START737505

Measured

Bradycardia

Measurements

Since Last Session

Start Date

MDC_IDC_STAT_BRADY_DTM_END737506

Measured

Bradycardia

Measurements

Since Last Session

End Date

IntegerEncounter

DateTimeEncounter

84 | Connectivity Guide | HL7 Integration

PaceartIDCO

3-1

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

MDC_IDC_STAT_BRADY_RA_PERCENT_PACED737520

Measured

Bradycardia

Measurements

Since Last Session

Right Atrium Percent

Paced

MDC_IDC_STAT_BRADY_RV_PERCENT_PACED737536

Measured

Bradycardia

Measurements

Since Last Session

Right Ventricle

Percent Paced

MDC_IDC_STAT_BRADY_AP_VP_PERCENT737552

Measured

Bradycardia

Measurements

Since Last Session

AP VP Percent

Parameter

Type

NumericEncounter

MDC_IDC_STAT_BRADY_AS_VP_PERCENT737568

Measured

Bradycardia

Measurements

Since Last Session

AS VP Percent

MDC_IDC_STAT_BRADY_AP_VS_PERCENT737584

Measured

Bradycardia

Measurements

Since Last Session

AP VS Percent

MDC_IDC_STAT_BRADY_AS_VS_PERCENT737600

Measured

Bradycardia

Measurements

Since Last Session

AS VS Percent

MDC_IDC_STAT_AT_DTM_START737665

Measured Atrial

Tachycardia

Counters Since Last

Session Start Date

NumericEncounter

DateTimeEncounter

MDC_IDC_STAT_AT_DTM_END737666

Measured Atrial

Tachycardia

DateTimeEncounter

Connectivity Guide | HL7 Integration | 85

PaceartIDCO

3-1

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Counters Since Last

Session End Date

MDC_IDC_STAT_AT_MODE_SW_MAX_DURATION737680

Measured Atrial

Tachycardia

Counters Since Last

Session Mode

Switch Maximum

Duration

MDC_IDC_STAT_AT_BURDEN_PERCENT737696

Measured Atrial

Tachycardia

Counters Since Last

Session AT AF

Burden

MDC_IDC_STAT_AT_MODE_SW_PERCENT_TIME737712

Measured Atrial

Tachycardia

Counters Since Last

Session Mode

Switch Burden

Parameter

Type

NumericEncounter

IntegerEncounter

MDC_IDC_STAT_AT_MODE_SW_PERCENT_TIME_PER_DAY737728

Measured Atrial

Tachycardia

Counters Since Last

Session Mode

Switch Average

Daily Burden

MDC_IDC_STAT_AT_MODE_SW_COUNT737744

Measured Atrial

Tachycardia

Counters Since Last

Session Mode

Switch Count

MDC_IDC_STAT_AT_MODE_SW_COUNT_PER_DAY737760

Measured Atrial

Tachycardia

Counters Since Last

Session Mode

Switch Average

Daily Count

MDC_IDC_STAT_CRT_DTM_START737777

Measured Heart

Failure Counters

Since Last Session

Start Date

IntegerEncounter

DateTimeEncounter

86 | Connectivity Guide | HL7 Integration

PaceartIDCO

3-1

MDC_IDC_STAT_CRT_DTM_END737778

MDC_IDC_STAT_CRT_LV_PERCENT_PACED737792

MDC_IDC_STAT_CRT_PERCENT_PACED737808

MDC_IDC_STAT_TACHYTHERAPY_SHOCKS_DELIVERED_

737824

RECENT

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Measured Heart

Failure Counters

Since Last Session

End Date

Measured

Bradycardia

Measurements

Since Last Session

Left Ventricle

Percent Paced

Measured Heart

Failure Counters

Since Last Session

CRT Percent Paced

Measured

Tachycardia

Therapy Counters

Since Last Counter

Reset Right

Ventricle Shocks

Delivered

Parameter

Type

DateTimeEncounter

NumericEncounter

IntegerEncounter

MDC_IDC_STAT_TACHYTHERAPY_SHOCKS_DELIVERED_

737840

TOTAL

MDC_IDC_STAT_TACHYTHERAPY_SHOCKS_ABORTED_

737856

RECENT

MDC_IDC_STAT_TACHYTHERAPY_SHOCKS_ABORTED_TOTAL737872

IntegerEncounter

Measured

Tachycardia

Therapy Counters

Lifetime Right

Ventricle Shocks

Delivered

IntegerEncounter

Measured

Tachycardia

Therapy Counters

Since Last Counter

Reset Right

Ventricle Shocks

Aborted

IntegerEncounter

Measured

Tachycardia

Therapy Counters

Lifetime Right

Ventricle Shocks

Aborted

Connectivity Guide | HL7 Integration | 87

PaceartIDCO

3-1

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

MDC_IDC_STAT_TACHYTHERAPY_ATP_DELIVERED_RECENT737888

Measured

Tachycardia

Therapy Counters

Since Last Counter

Reset Right

Ventricle ATP

Delivered

MDC_IDC_STAT_TACHYTHERAPY_ATP_DELIVERED_TOTAL737904

Measured

Tachycardia

Therapy Counters

Lifetime Right

Ventricle ATP

Delivered

MDC_IDC_STAT_TACHYTHERAPY_TOTAL_DTM_START737921

Measured

Tachycardia

Therapy Counters

Lifetime Start Date

Parameter

Type

IntegerEncounter

DateTimeEncounter

MDC_IDC_STAT_TACHYTHERAPY_TOTAL_DTM_END737922

MDC_IDC_STAT_TACHYTHERAPY_RECENT_DTM_START737937

MDC_IDC_STAT_TACHYTHERAPY_RECENT_DTM_END737938

when 737984^MDC_IDC_STAT_EPISODE_VENDOR_TYPE^MDC has OBX-5 value of 773124^STJ-Epis_VT1^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

DateTimeEncounter

Measured

Tachycardia

Therapy Counters

Lifetime End Date

DateTimeEncounter

Measured

Tachycardia

Therapy Counters

Since Last Counter

Reset Start Date

DateTimeEncounter

Measured

Tachycardia

Therapy Counters

Since Last Counter

Reset End Date

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset VT1 Monitor

Episode Count or

Encounter

Measured

88 | Connectivity Guide | HL7 Integration

PaceartIDCO

3-1

when 737984^MDC_IDC_STAT_EPISODE_VENDOR_TYPE^MDC has OBX-5 value of 773125^STJ-Epis_VT2^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Tachycardia

Detection Counters

Since Last Counter

Reset VT1 Episode

Count

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset VT2 Monitor

Episode Count or

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset VT2 Episode

Count

Parameter

Type

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754881^MDC_IDC_ENUM_EPISODE_TYPE_Epis_VF^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754882^MDC_IDC_ENUM_EPISODE_TYPE_Epis_VT^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754883^MDC_IDC_ENUM_EPISODE_TYPE_Epis_ATAF^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset VF VT

Episode Count

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset VT Episode

Count

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset AF AT

Episode Count

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754884^MDC_IDC_ENUM_EPISODE_TYPE_Epis_SVT^MDC

Connectivity Guide | HL7 Integration | 89

PaceartIDCO

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

3-1

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754885^MDC_IDC_ENUM_EPISODE_TYPE_Epis_Monitor^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset SVT Episode

Count

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset VF VT

Monitor Episode

Count

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset VT Monitor

Episode Count

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset AF AT

Monitor Episode

Count

Parameter

Type

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754886^MDC_IDC_ENUM_EPISODE_TYPE_Epis_PeriodicEGM^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754887^MDC_IDC_ENUM_EPISODE_TYPE_Epis_PatientActivated^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset Periodic

Episode Count

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset Patient

90 | Connectivity Guide | HL7 Integration

PaceartIDCO

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

3-1

Activated Episode

Count

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754888^MDC_IDC_ENUM_EPISODE_TYPE_Epis_Other^MDC

MDC_IDC_STAT_EPISODE_RECENT_COUNT738000

MDC_IDC_STAT_EPISODE_RECENT_COUNT_DTM738016

MDC_IDC_STAT_EPISODE_RECENT_COUNT_DTM_START738017

Encounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset Other

Episode Count

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset Start Date

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset Start Date

Parameter

Type

DateTimeEncounter

MDC_IDC_STAT_EPISODE_RECENT_COUNT_DTM_END738018

when 737984^MDC_IDC_STAT_EPISODE_VENDOR_TYPE^MDC has OBX-5 value of 773124^STJ-Epis_VT1^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

when 737984^MDC_IDC_STAT_EPISODE_VENDOR_TYPE^MDC has OBX-5 value of 773125^STJ-Epis_VT2^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

DateTimeEncounter

Measured

Tachycardia

Detection Counters

Since Last Counter

Reset End Date

Encounter

Measured

Tachycardia

Detection Counters

Lifetime VT1

Episode Count or

Encounter

Measured

Tachycardia

Detection Counters

Lifetime VT1

Monitor Episode

Count

Encounter

Measured

Tachycardia

Connectivity Guide | HL7 Integration | 91

PaceartIDCO

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

3-1

Detection Counters

Lifetime VT2

Episode Count or

Encounter

Measured

Tachycardia

Detection Counters

Lifetime VT2

Monitor Episode

Count

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754881^MDC_IDC_ENUM_EPISODE_TYPE_Epis_VF^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754882^MDC_IDC_ENUM_EPISODE_TYPE_Epis_VT^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

Encounter

Measured

Tachycardia

Detection Counters

Lifetime VF VT

Episode Count

Encounter

Measured

Tachycardia

Detection Counters

Lifetime VT Episode

Count

Parameter

Type

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754883^MDC_IDC_ENUM_EPISODE_TYPE_Epis_ATAF^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754884^MDC_IDC_ENUM_EPISODE_TYPE_Epis_SVT^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754885^MDC_IDC_ENUM_EPISODE_TYPE_Epis_Monitor^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

Encounter

Measured

Tachycardia

Detection Counters

Lifetime AF AT

Episode Count

Encounter

Measured

Tachycardia

Detection Counters

Lifetime SVT

Episode Count

Encounter

Measured

Tachycardia

Detection Counters

Lifetime VF VT

Monitor Episode

Count, Encounter

92 | Connectivity Guide | HL7 Integration

PaceartIDCO

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

3-1

Measured

Tachycardia

Detection Counters

Lifetime VT Monitor

Episode Count,

Encounter

Measured

Tachycardia

Detection Counters

Lifetime AF AT

Monitor Episode

Count

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754886^MDC_IDC_ENUM_EPISODE_TYPE_Epis_PeriodicEGM^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754887^MDC_IDC_ENUM_EPISODE_TYPE_Epis_PatientActivated^MDC

Encounter

Measured

Tachycardia

Detection Counters

Lifetime Periodic

Episode Count

Parameter

Type

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

when 737952^MDC_IDC_STAT_EPISODE_TYPE^MDC has OBX-5 value of 754888^MDC_IDC_ENUM_EPISODE_TYPE_Epis_Other^MDC

MDC_IDC_STAT_EPISODE_TOTAL_COUNT738032

MDC_IDC_STAT_EPISODE_TOTAL_COUNT_DTM738048

MDC_IDC_STAT_EPISODE_TOTAL_COUNT_DTM_START738049

Encounter

Measured

Tachycardia

Detection Counters

Lifetime Patient

Activated Episode

Count

Encounter

Measured

Tachycardia

Detection Counters

Lifetime Other

Episode Count

Measured

Tachycardia

Detection Counters

Lifetime Start Date

Measured

Tachycardia

Detection Counters

Lifetime Start Date

DateTimeEncounter

MDC_IDC_STAT_EPISODE_TOTAL_COUNT_DTM_END738050

Measured

DateTimeEncounter

Connectivity Guide | HL7 Integration | 93

PaceartIDCO

3-1

Table : MDC_IDC_EPISODE

3-1

MDC_IDC_EPISODE_ID739536

MDC_IDC_EPISODE_DTM739552

754881^MDC_IDC_ENUM_EPISODE_TYPE_Epis _VF^MDCMDC_IDC_EPISODE_TYPE739568

754882^MDC_IDC_ENUM_EPISODE_TYPE_Epis _VT^MDC

754883^MDC_IDC_ENUM_EPISODE_TYPE_Epis _ATAF^MDC

754884^MDC_IDC_ENUM_EPISODE_TYPE_Epis _SVT^MDC

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Tachycardia

Detection Counters

Lifetime End Date

PaceartIDCO

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Episode Id

Episode Start

Episode Type

Parameter

Type

Parameter

Type

IntegerEncounter Episodes

DateTimeEncounter Episodes

ENUMEncounter Episodes

739600

MDC_IDC_EPISODE_VENDOR_

TYPE

754886^MDC_IDC_ENUM_EPISODE_TYPE_Epis _PeriodicEGM

^MDC

754887^MDC_IDC_ENUM_EPISODE_TYPE_Epis

_PatientActivated^MDC

754888^MDC_IDC_ENUM_EPISODE_TYPE_Epis _Other^MDC

770049^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_VF^MDC

770053^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_NSVT^MDC

770054^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_SVT^MDC

770055^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_ATAF^MDC

770057^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_AFib^MDC

770058^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_AT^MDC

770059^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_ModeSw^MDC

ENUMEncounter Episodes

Episode Type

770060^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_AMon^MDC

770066^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_PIEGM^MDC

94 | Connectivity Guide | HL7 Integration

PaceartIDCO

3-1

770067^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE

_BIO-Epis_PAT^MDC

771074^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE _

BSX-Epis_VT^MDC

771075^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE _BSX-Epis

_VT-1^MDC

771077^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE _

BSX-Epis_NSVT^MDC

773123^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE _

STJ-Epis_SVT^MDC

773124^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE _

STJ-Epis_VT1^MDC

773125^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE _

STJ-Epis_VT2^MDC

773127^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE _

STJ-Epis_AMS^MDC

773146^MDC_IDC_ENUM_EPISODE_VENDOR_TYPE _

STJ-Epis_Non-sustained^MDC

Parameter NameSupported Values (OBX 5)OBX 3-2OBX

Parameter

Type

739696

MDC_IDC_EPISODE_THERAPY_

RESULT

MDC_IDC_EPISODE_DURATION739712

755137^MDC_IDC_ENUM_EPISODE_THERAPY_RESULT

_Successful^MDC

755138^MDC_IDC_ENUM_EPISODE_THERAPY_RESULT

_Unsuccessful^MDC

755139^MDC_IDC_ENUM_EPISODE_THERAPY_RESULT

_Unknown^MDC

Episode Result

Episode Duration

ENUMEncounter Episodes

NumericEncounter Episodes

MDC_IDC_NOTIFICATION

This table is only applicable to IDCO 1.1. For additional inbound segments and values for IDCO 1.1 that are supported, see the "IDCO 1.1 Support" section.

PaceartIDCO

Parameter Type

String 100Encounter

Date TimeEncounter

740033

740035

MDC_IDC_NOTIFICATION _ID

MDC_IDC_NOTIFICATION _DTM_START

Supported Values (OBX 5)OBX 3-2OBX 3-1

Parameter Name

Notification ID

Notification Start Date

740036

MDC_IDC_ NOTIFICATION_DTM_END

Date TimeEncounter Notification End Date

Connectivity Guide | HL7 Integration | 95

PaceartIDCO

740039

MDC_IDC_NOTIFICATION _TYPE_1

Supported Values (OBX 5)OBX 3-2OBX 3-1

755457^MDC_IDC_ENUM_ NOTIFICATION_TYPE_DEVICE ^MDC

755458^MDC_IDC_ENUM_ NOTIFICATION_TYPE_Device _ Settings^MDC

755459^MDC_IDC_ENUM_ NOTIFICATION_TYPE_ Lead^MDC

755460^MDC_IDC_ENUM_ NOTIFICATION_TYPE_Atrial_ Arrhythmia^MDC

755461^MDC_IDC_ENUM_ NOTIFICATION_TYPE_ Ventricular_ Arrhythmia^MDC

755463^MDC_IDC_ENUM_ NOTIFICATION_TYPE_Heart_ Failure^MDC

Parameter Name

Notification Type 1

Parameter

Type

ENUMEncounter

755464^MDC_IDC_ENUM_ NOTIFICATION_TYPE_Shock _Therapy_ Delivered^MDC

755465^MDC_IDC_ENUM_ NOTIFICATION_TYPE_ATP_ Therapy_ Delivered^MDC

755466^MDC_IDC_ENUM_ NOTIFICATION_TYPE_Pacing_ Therapy ^MDC

755467^MDC_IDC_ENUM_ NOTIFICATION_TYPE_Other_ Clinical^MDC

755468^MDC_IDC_ENUM_ NOTIFICATION_TYPE_Follow_ Up^MDC

755469^MDC_IDC_ENUM_ NOTIFICATION_TYPE_Patient_ Request ^MDC

755470^MDC_IDC_ENUM_ NOTIFICATION_TYPE_ Connectivity_Administrative ^MDC

96 | Connectivity Guide | HL7 Integration

PaceartIDCO

740040

740041

740042

MDC_IDC_NOTIFICATION _TYPE_2

MDC_IDC_NOTIFICATION _TYPE_3

MDC_IDC_NOTIFICATION _PRIORITY

Supported Values (OBX 5)OBX 3-2OBX 3-1

Same as MDC_IDC_NOTIFICATION_ TYPE_1

755521^MDC_IDC_ENUM_ NOTIFICATION_PRIORITY_ High^MDC

755522^MDC_IDC_ENUM_ NOTIFICATION_PRIORITY_ Medium^MDC

755523^MDC_IDC_ENUM_ NOTIFICATION_PRIORITY_ Low^MDC

755524^MDC_IDC_ENUM_ NOTIFICATION_PRIORITY_ Informative^MDC

755525^MDC_IDC_ENUM_ NOTIFICATION_PRIORITY_Not_ Indicated^MDC

Parameter Name

Notification Type 2

Notification Type 3

Notification Priority

Parameter

Type

ENUMEncounter

740043

Embedded PDF

Referenced PDF

MDC_IDC_NOTIFICATION _DESCRIPTION

String 250Encounter Notification Description

PaceartHL7

OBX 3-5OBX 3-4OBX 3-3OBX 3-1OBX 2

LN18750-0ED

Attachment File Name

OBX 3-3OBX 3-1OBX 2

LN18750-0RP

Attachment Description

Supported Values OBX 5

Supported Values (OBX 5-5)

Base-64 Encoded

PaceartHL7

Parameter Name

Name

Parameter Name

Attachment File

Parameter Type

Binary 50 MB

Parameter Type

String 260Attachment File

Connectivity Guide | HL7 Integration | 97

IDCO 1.1 Support

The Paceart System will import supported IDCO 1.1 segments and values, when available in the message, regardless of the outbound version configuration.

The Paceart System supports the following manufacturer values for MDC_IDC_ENUM_MFG.

OBX-5-3OBX-5-2OBX-5-1

MDCMDC_IDC_ENUM_MFG_ABT753757

MDCMDC_IDC_ENUM_MFG_MPT753758

For additional inbound IDCO 1.1 segments and values that are supported, see the "MDC_IDC_Notification" table.

Outbound Messages

The Paceart System and CareLink integrate with the HL7 protocol for outgoing messages from the Paceart System and CareLink to an external system by mapping a parameter and a parameter type to HL7 values. This section describes outbound message mapping.

Outbound MSH Message Segments

The HL7 MSH (Message Header) segment is present in every HL7 message type and defines the message's source, purpose, destination, and certain syntax specifics like delimiters (separator characters) and character sets.

ComponentFieldSource of Data or Literal Value

N/AMSH-1|

N/AMSH-2^~\&

1MSH-3Paceart

1MSH-4Medtronic

N/AMSH-7Local date and time in the format YYYMMDDhhmmss

1MSH-9ORU

2MSH-9R01

3MSH-9ORU_R01

N/AMSH-10Message ID in the format YYYYMMDDhhmmss######

1MSH-11P

1MSH-122.6

N/AMSH-15AL

N/AMSH-16NE

1MSH-21IHE_PCD_ORU_R01

2MSH-21IHE PCD

3MSH-211.3.6.1.4.1.19376.1.6.1.9.1

4MSH-21ISO

98 | Connectivity Guide | HL7 Integration

Outbound PID Message Segments

The PID (Patient Identification) segment provides important identification information about the patient and is used as the primary means of communicating the identifying and demographic information about a patient between systems.

OccurrenceComponentFieldParameter TypeParameter

2..211PID-3String 50Patient ID Value

11PID-5String 50Patient Last Name

12PID-5String 50Patient First Name

13PID-5String 1Patient Middle Initial

1N/APID-7DateTimePatient Birth Date

1N/APID-8ENUMPatient Gender

11PID-11String 50Patient Address Line 1

12PID-11String 50Patient Address Line 2

13PID-11String 50Patient Address City

14PID-11String 10Patient Address State

15PID-11String 10Patient Address Postal Code

16PID-11String 50Patient Address Country

11PID-13String 20Patient Phone Number

14PID-13String 100Patient Email Address

11PID-14String 20Patient Phone Number 2

11PID-16ENUMPatient Marital Status

11PID-29DateTimePatient Date of Death

11PID-30BooleanDeath Indicator

Outbound PV1 Message Segments

The PV1 (Patient Visit) segment is used by registrationapplications to communicate information on a visit-specific basis.

OccurrenceSub-ComponentComponentFieldParameter TypeParameter

N/AN/A1PV1-2String 1Patient Status

N/AN/A1PV1-3StringPatient Location

of Care

N/AN/A1PV1-19String 50Encounter Visit

Connectivity Guide | HL7 Integration | 99

Outbound PV2 Message Segments

The PV2 (Patient Visit) segment is a continuation of visit-specific information contained in the PV1 segment.

OccurrenceSub-ComponentComponentFieldParameter TypeParameter

mN/A1PV2-7String 6Patient Code

Value (Paceart)

Custom Patient Field(s) (CareLink)

Outbound NTE Message Segments

The NTE segment is an optional segment that appears after the PID and is used to provide notes and comments.

Note: There is another NTE Message Segments table after the Outbound OBR Message Segments table.

Parameter

Type

Comment

NTE-3Parameter

/PaceartXML/PatientRecord/CommentString 65000Patient Record

Outbound OBR Message Segments

The OBR (Observation Request) segment transmits information about an exam, diagnostic study/observation, or assessment that is specific to an order or result.

Parameter

Type

and Time

OccurrenceSub-ComponentComponentFieldParameter

N/AN/A1OBR-3String 32Encounter Key

N/AN/A1OBR-4ENUMEncounter Type

N/AN/A4OBR-4String 20Encounter Type

N/AN/A5OBR-4String 20Encounter Type

N/AN/A6OBR-4String 20Encounter Type

N/AN/A1OBR-7DateTimeEncounter Date and Time

N/AN/A1OBR-8DateTimeEncounter Signature Date

Code

Last Name

First Name

Middle Initial

Credentials

N/AN/A1OBR-16String 6REFERRING1 Provider

N/AN/A2OBR-16String 50REFERRING1 Provider

N/AN/A3OBR-16String 50REFERRING1 Provider

N/AN/A4OBR-16String 1REFERRING1 Provider

N/AN/A5OBR-16String 20REFERRING1 Provider

100 | Connectivity Guide | HL7 Integration

Parameter

Code

Last Name

First Name

Middle Initial

Credentials

Code

Last Name

First Name

OccurrenceSub-ComponentComponentFieldParameter

Type

N/AN/A1OBR-25String 1Encounter Lock

N/AN/A1OBR-26String 32Encounter Parent Key

1N/A1OBR-28String 6REFERRING2 Provider

1N/A2OBR-28String 50REFERRING2 Provider

1N/A3OBR-28String 50REFERRING2 Provider

1N/A4OBR-28String 1REFERRING2 Provider

1N/A5OBR-28String 20REFERRING2 Provider

2N/A1OBR-28String 6REFERRING3 Provider

2N/A2OBR-28String 50REFERRING3 Provider

2N/A3OBR-28String 50REFERRING3 Provider

Middle Initial

Credentials

Code

Last Name

First Name

Middle Initial

Credentials

Name

2N/A4OBR-28String 1REFERRING3 Provider

2N/A5OBR-28String 20REFERRING3 Provider

3N/A1OBR-28String 6FOLLOWING Provider

3N/A2OBR-28String 50FOLLOWING Provider

3N/A3OBR-28String 50FOLLOWING Provider

3N/A4OBR-28String 1FOLLOWING Provider

3N/A5OBR-28String 20FOLLOWING Provider

N/A11OBR-32String 6Provider Code/Signer ID

N/A21OBR-32String 50ProviderLast Name/Signer

N/A31OBR-32String 50Provider First Name

N/A41OBR-32String 1Provider Middle Initial

In the Paceart System, if Encounter Lock is false, then the value is "P" for preliminary. If Encounter Lock is true, then the value is "F" for final. In CareLink, when an encounter is first sent to the EHR the Encounter Lock value is "F" for final. If subsequent values are sent then the Encounter Lock value is "A" for amended.

Medtronic MDTCSG2V10A Technical Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Mainspring Data Express

Explanation of symbols

Indications

Precautions

Contraindications

Mainspring Data Express Authorized Users

Technical Support

Mainspring Data Express Software Prerequisites

Installation Prerequisites

Installing and Configuring MS Message Queuing for Windows 8.1

Installing and Configuring MS Message Queuing for Windows 10

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

Installing the Java Runtime Environment

Installing .Net 4.7.2 Framework

Installing Mainspring Data Express

Automatically Starting the Connected Systems Gateway After Restart

Log File Configuration

Paceart System Integration

General Paceart System Settings

Configuring Paceart System Settings

Paceart System Integration Configuration Values

CareLink Scheduling Integration

CareLink Scheduling Integration Prerequisites

Configuring CareLink Scheduling Integration

CareLink Scheduling Integration Configuration Values

Troubleshooting CareLink Scheduling Integration

Paceart Optima System HL7 Integration

Configuring Paceart HL7 Integration

HL7 Integration Configuration Values

Installing the Corepoint Integration Engine

Troubleshooting Paceart HL7 Integration

Programmer Acquisition service cannot start Event Log message

Local Data Interface

Updating the Local Data Interface Port Number

Local Data Interface Extended Configurations

Local Data Interface certificate installation

Installing the Certificate

Enabling a data import source

Local Data Interface Plus

Updating the Local Data Interface Plus Port Number

Local Data Interface Plus certificate installation

Selecting an Existing Certificate

Installing a New Certificate

Enabling a data import source

CareLink Transmission Integration

Remote Data Interface

Configuring Remote Data Interface

Remote Data Interface Configuration Values

Enabling remote data acquisition in the Paceart System

Data Bridge Gateway

Enabling Data Bridge Gateway Integration in CareLink

Configuring Data Bridge Gateway

CareLink DataBridge Gateway Configuration Values

Troubleshooting Data Bridge Gateway Integration

Mainspring Health Interface

Configuring Mainspring Health Interface

Mainspring Health Interface Configuration Values

CareLink Integration

CareLink Report Export

Configuring CareLink Report Export

CareLink Report Export Configuration Values

Enabling and Verifying Mainspring Report Export

Troubleshooting Report Export

CareLink EHR Integration

Configuring EHR Integration

CareLink EHR Integration Configuration Values

Installing and configuring Mirth Connect

Troubleshooting EHR Integration

HL7 Integration

Inbound Messages

Inbound Patient Administration Messages (ADT)

Inbound Patient Administration Message Segments

Inbound Scheduling Messages (SIU)

Inbound Scheduling Segments

Inbound Observation Requests (ORU)