Medtronic PASCV Reference Guide

Connected Systems Gateway
Connectivity Guide
Federal Law (USA) restricts the device to sale by or on the order of a physician (or a properly licensed practitioner).
Trademarks in this manual The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The following are trademarks of Medtronic: Medtronic, Medtronic CareLink, SessionSync, and Paceart
Connected Systems Gateway.....................................................................................................2
Connected Systems Gateway Software Prerequisites.....................................................6
Installing the Connected Systems Gateway.........................................................................9
Paceart-CareLink Scheduling Integration............................................................................15
HL7 Integration Overview...........................................................................................................17
Paceart XML Schema....................................................................................................................61
Connectivity Guide | Contents | i
Explanation of symbols..............................................................................................................2
Indications....................................................................................................................................2
Precautions..................................................................................................................................3
Contraindications........................................................................................................................4
Paceart authorized users............................................................................................................4
Technical Support........................................................................................................................5
Installing .Net 3.5 Framework Service Pack 1..........................................................................6
Installing and Configuring MS Message Queuing for Windows XP.......................................6
Installing and Configuring MS Message Queuing for Windows Server 2003.......................7
Installing and Configuring MS Message Queuing for Windows Vista...................................7
Creating a Connected Systems Gateway user for the Paceart database..............................7
Creating a CareLink user to use with the Connected Systems Gateway..............................8
Connected Systems Gateway Configuration Manager..........................................................10
Starting the Connected Systems Gateway.............................................................................14
Scheduling integration requirements......................................................................................15
Troubleshooting scheduling connectivity problems.............................................................16
Medtronic Connected Systems Gateway HL7 Overview.......................................................17
HL7 Inbound Message Flow.....................................................................................................19
HL7 Message Acknowledgement............................................................................................19
Inbound Patient Administration Messages (ADT)..................................................................19
Inbound Message Segments....................................................................................................21
Inbound Scheduling Messages (SIU)......................................................................................23
Inbound Message Segments....................................................................................................25
Outbound Event Observation Reporting (ORU).....................................................................29
OBX:3 Coded Element...............................................................................................................34
Identifiers...................................................................................................................................39
OBX:4 Sub-ID Numbering and Data Relationship..................................................................50
Troubleshooting HL7 connectivity problems.........................................................................60
Programmer Acquisition service cannot start Event Log message..........................60
Parameter valid values..............................................................................................................61
Paceart XML export...................................................................................................................64
Lookup tables..................................................................................................................64
Patient records................................................................................................................69
2 | Connectivity Guide | Connected Systems Gateway

Connected Systems Gateway

In order to simplify the process of connecting and sharing demographic, scheduling, and device data between Medtronic applications andelectronic medical record systems (EMRs), Medtronichas developed the Connected Systems Gateway (CSG). This software application serves as the primary tool to move and share data for device patients.The CSG helps to streamline the implementation and on-going maintenance of data movement between applications.
The Connected Systems Gateway is an optional component of the Paceart System.
The CSG is used to do the following:
• Exchange scheduling data between CareLink and Paceart
• Bring in demographic and scheduling information from electronic medical record systems or practice management systems via HL7
• Export device data to electronic medical record systems via HL7

Explanation of symbols

Consult instructions for use
Conformité Européenne (European Conformity). This symbol means that the device fully complies with European Directive MDD 93/42/EEC.
For US audiences only
Authorized Representative in the European Community
Manufacturer
Lot number
Reorder number
Date of Manufacture

Indications

The Paceart System is intended for use as a 12-lead electrocardiograph, pacemaker artifact analyzer, and transtelephonic ECG receiving station. It also acts as a database for cardiac patients with or without pacemakers or implantable cardioverter defibrillators.
Connectivity Guide | Connected Systems Gateway | 3

Precautions

Storage and installation
• Avoid moisture or contact with water.
• Avoid excessive or extreme air pressure.
• Avoid vibration and mechanical shock while moving.
• Place on a level floor.
• Use AC power that corresponds in frequency, voltage, and allowable current capacity.
• Use the isolation transformer as the source of AC power during in-clinic follow-ups.
• Use a grounded 3-wire AC power plug.
• The outside of the Paceart Module can be cleaned with a clean, dry cloth.
• Use the isolation transformer as the source of AC power and plug it directly into a grounded wall outlet.
• Use a grounded 3-wire AC power cable to connect the PC to the isolation transformer.
• Ensure there is no condensed moisture on the Paceart software CD-ROMs.
• Paceart software CD-ROMs must be stored within the following conditions:
Storage Environment
-20°C to +50°CTemperature
5% to 90%Relative Humidity
System operation
Before system operation:
• Check that the system components are working properly.
• Check that the cords are connected to the system correctly.
• Ensure that the system is not being used with other instruments that may result in misdiagnosis or other problems.
• Check to be sure that there is no damage to the circuitry that connects directly to the patient.
• Ensure there is no condensed moisture on the Paceart software CD-ROMs.
• Paceart software CD-ROMs must be operating in an environment within the following conditions:
Operating Environment
-25°C to +70°CTemperature
10% to 95%Relative Humiditiy
During system operation:
• Maintain constant observation of the patient to ensure that significant events are detected immediately.
• The system can be switched off when necessary to ensure the patient's safety.
After system operation:
• The system and all the accessories should be carefully cleaned after use to prepare them for the next session.
Additional precautions
• Do not modify the original system in any way. This includes adding any software product.
4 | Connectivity Guide | Connected Systems Gateway
• The system and its components should undergo regular maintenance inspections.
• If the system is stored for a long period of time without use, make sure that the system is in perfect condition prior to operation.
• Use only ECG disposable electrodes in proper working condition.
• Use electrode gel or electrolytic pads to ensure that good electrode contact is obtained.
• Ensure that the proper lead colors are connected to the correct electrode sets.
• Do not use the equipment in an explosive atmosphere.
• Do not use liquid on top of the equipment.
• Ensure that all patient records are updated and permanently stored before turning the PC power off.
• Do not use the instrument in an environment with excessive temperature and humidity.
• Double-check the data before typing the data into the system.
• Call customer service or your biomedical department for service and repairs.
• Ensure that the report to be printed reflects the proper leads. The operator selects which leads will be shown in the printed report.
• The operator should not touch the computer and patient simultaneously when the patient is connected to the ECG electrodes.
• ECG electrodes should not contact other conductive parts, including earth.
• The Paceart ECG module is not suitable for direct cardiac applications.
Transmission and transmitter settings
• The transmitter transmission speed must match the transmit speed setting in Paceart.
• The transmitter transmit format must match the transmit format setting in Paceart.
• Discrepancies between the transmission speed or the transmission format will result in incorrect measurements that may lead to incorrect ECG interpretations.
• The Date Given field must have a date that is the same or prior to the date the transmission is recorded.
• A patient may only have one active transmitter.
• The Paceart operator is responsible for setting the speed and format settings.
ECG noise
The following may cause noise affecting artificial pacemaker spikes:
• Pacemaker programmers
• Poor electrode contact
• Electrical interference due to grounding problems
Caution: Make sure that the PC used to record pacemaker clinic ECGs is connected to AC power using an isolation transformer and a grounded three-wire power cable.

Contraindications

No known contraindications.

Paceart authorized users

Medtronic representatives provide the Paceart System orientation and training materials at the time of the installation. All users should be familiar with the Paceart documents, including the online Help, before using
Connectivity Guide | Connected Systems Gateway | 5
the Paceart System. The designated system administrator should also read the Paceart System Administrator's Guide for information on using the Paceart System software user interface for function and control.
An authorized person, preferably a physician, must verify the implantable device and electrode specifications entered into the database or modified in the database. An authorized person, preferably a physician, must verify the test results that are automatically entered into the database by the instrument. The data obtained from this device must be interpreted in conjunction with other clinical data and the results of other independent tests.

Technical Support

For technical support contact your local Medtronic office. In the US and Canada, call 1-800-PACEART.
6 | Connectivity Guide | Connected Systems Gateway Software Prerequisites

Connected Systems Gateway Software Prerequisites

Before you install and configure the Connected Systems Gateway software you must complete the following prerequisites:
• Install .Net 3.5 Framework Service Pack 1.
• Install and Configure MS Message Queue.
• Create a Connected Systems Gateway user on the Paceart Database if you are using SQL Server authentication (not needed if using Windows Authentication).
Paceart-CareLink scheduling integration prerequisites
Before you enable scheduling integration you must complete the following prerequisites:
• Create a CareLink account to use with the Connected Systems Gatewaywith the Transmission Permission selection of View changes transmission status from new to viewed.
• Configure Paceart appointments and patient records for scheduling integration.
HL7 integration prerequisites
Before you enable scheduling integration you must complete the following prerequisite.
• Review Paceart patient data to verify that each patient has the correct patient ID and there are no duplicate patient IDs in the Paceart database. If the HL7 adapter encounters multiple patients in Paceart with the same patient ID as the patient ID in the message, it will log an error message in the Paceart Data Exchange Log Viewer and the Connected Systems Gateway log.

Installing .Net 3.5 Framework Service Pack 1

You must have .Net 3.5 Framework Service Pack 1 installed before you install the Connected Systems Gateway. The .Net Framework Service Pack 1 files are located on the Connected Systems Gateway CD. You do not need to be connected to the internet to install the files.
1. Insert the Connected Systems Gateway CD into your disk drive.
2. Browse to the CD and double-click on dotnetfx35.exe.

Installing and Configuring MS Message Queuing for Windows XP

1. Open the Control Panel.
2. Double-click Add or Remove Programs.
3. Click Add/Remove Windows Components.
4. Select Message Queuing from the Windows Components Wizard dialog.
5. Click Next.
6. Click Details.
7. Select Common from the list of Subcomponents of Message Queuing.
8. Click OK on the Message Queuing dialog.
9. Click Next on the Windows Components Wizard dialog.
Connectivity Guide | Connected Systems Gateway Software Prerequisites | 7
10. When the installation completes click Finish.

Installing and Configuring MS Message Queuing for Windows Server 2003

1. Open the Control Panel.
2. Double-click Add or Remove Programs.
3. Click Add/Remove Windows Components.
4. Select Application Server from the Windows Components Wizard dialog.
5. Click Next.
6. Select Message Queuing.
7. Click Details.
8. Select Common from the list of Subcomponents of Message Queuing.
9. Click OK on the Message Queuing dialog.
10. Click Next on the Windows Components Wizard dialog.
11. When the installation completes click Finish.

Installing and Configuring MS Message Queuing for Windows Vista

1. Click Start > Control Panel.
2. Click Programs.
3. Under the Windows and Features section, 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.

Creating a Connected Systems Gateway user for the Paceart database

If you are using SQL Server authentication, you must create a Connected Systems Gateway user on your Paceart database. The user must have database reader and database writer privileges.
1. Open the Paceart System Database Manager.
2. Click Paceart_Database.
3. Click Users.
4. Click New User.
5. Click Next.
6. In login section select <new> and click Next.
7. In the Authentication window select SQL Server and click Next.
8. In the Login name field enter the user name you will use for the Connected Systems Gateway.
9. In the Password field enter and confirm your password.
10. In the Roles window accept the default and click Next.
11. Click Next through the wizard.
12. Click Finish.
8 | Connectivity Guide | Connected Systems Gateway Software Prerequisites

Creating a CareLink user to use with the Connected Systems Gateway

You must create a dedicated CareLink user for the Connected Systems Gateway to connect to. Do not use a clinical staff login.
You may use the same dedicated CareLink user allocated for downloading CareLink Transmissions into Paceart via Paceart Gateway Services.
1. Login to the Medtronic CareLink website.
2. Open the Create User Profile page.
3. From the Manage My Clinic page select Create a New CareLink User, or from the CareLink Users tab click Add User.
4. Click the Active CareLink User button.
5. Enter a first and last name.
6. Enter a user ID. The user ID must by 7-12 characters long. At least one character must be numeric (0-9).
The user ID is case-sensitive.
7. If you are using the satellite clinic feature, select the clinics for Assigned Clinics. If you have access to more than one clinic, use the Clinic Security section to specify which clinics the external system can access. An integrated system can be granted access to a single clinic, a group of clinics, or all of the clinics within the system.
Ensure that the CareLink account has access to the sub-clinics' patients that are integrated with Paceart.
8. Select the View only (not permitted to enroll clinicians or patients) option from the Administrative Privileges list.
9. Select the View changes transmission status from new to viewed option from the Transmission Privilege list.
10. Click Submit.
Connectivity Guide | Installing the Connected Systems Gateway | 9

Installing the Connected Systems Gateway

Complete the items listed in the prerequisites section before you install and configure the Connected Systems Gateway software.
1. To start the installation, insert the Connected Systems Gateway installation CD into the computer. The setup program will automatically start. If you are installing on a Windows 2003 Server, you must manually start the installation program by clicking the csginstall.msi on the installation CD.
If the setup program does not automatically start, you can manually start the installation program by clicking
csginstall.msi on the installation CD.
2. Click Next.
3. Enter a destination folder. Click Change to change from the default location of C:\Program
Files\Medtronic\Connected Systems Gateway\.
4. Click Next.
5. Click Install.
A progress bar shows the installing progress.
6. After the installation is finished click Next. The Completed Installation window is displayed.
7. Select Launch CSG Configuration Manager, and then click Finish to finish and exit the installation wizard and open the Connected Systems Gateway Configuration Manager.
8. In the CSG Feature Selecter window, select which features you want to configure and click Next.
• If you selected the Paceart/CareLink Scheduling Integration feature, the Connected Systems Gateway
Configuration Manager opens.
• If you selected the Paceart HL7 Integration feature, NeoIntegrate will be installed if it is not already
installed.
Note: NeoIntegrate installation is only launched one time. If you cancel the installation or need to re-execute the installation, you must first delete the following file to allow NeoIntegrate installation to be launched again:C:\Program Files\Medtronic\Connected Systems Gateway\HL7SubSystem\Installed. (The path will be different if the destination folder was modified it in step 3.)
a) In the NeoIntegrate - InstallShield Wizard window click Next. b) Read the license agreement. Click Next to accept it. c) Specify a destination folder. Click Change to change the default location, and then click Next. d) Select a setup type. The default is NeoIntegrate. Click Next. e) If your Paceart Systems uses SessionSync you will have a port conflict. Specify which alternate ports
you would like to use, and then click Next. f) Enter an Administrator password and click Next. g) Click Install to install NeoIntegrate. h) When the installation is complete you have the option to 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 Technical Support for licensing information.
After you click Finish the Log on dialog is displayed. The Connected Systems Gateway Configuration
Manager also opens in front of the Log on dialog. Move the Configuration Manager window out of the
way. i) Enter the username and password you specified in step f, and then click OK.
10 | Connectivity Guide | Installing the Connected Systems Gateway
j) In the LicenseManager window, click License wizard.
The License Wizard will start. k) Click Next. l) Select the I have a license string to run this product on this machine option, and then click Next. m) On the Machine/license description dialog enter a description of how this license will be used, and
then click Next.
For example "St. Elsewhere Hospital Production Server" n) On the Connection and login dialog enter your implementation information and click Next. o) Click Connect to contact NeoTool.com to obtain your license. p) After you have connected to NeoTool.com click Next. q) Click Finish. r) On the LicenseManager window click Exit.
9. In the Connected Systems Gateway Configuration Manager, enter the applicable values for the features you selected.

Connected Systems Gateway Configuration Manager

The Connected Systems Gateway consists of adapters.
Connectivity Guide | Installing the Connected Systems Gateway | 11
Paceart_GCIII_SourceAdapter tab
This adapter is for sending data out of Paceart.
ExplanationField name
PaceartDatabaseServer
PaceartDatabaseName
UseWindowsAuthentication
SQLServerUserName
SQLServerPassword
The name of the machine hosting the SQL Server database that the adapter will be using to interface with Paceart.
The database instance name of the database that the adapter will be using to interface with Paceart.
A Boolean value indicating that Windows Authentication should be used to connect to the SQL Server database. A setting of false will use the SQL User Name and SQL Password configuration values to connect. The default is "False".
The user name used to connect to the SQL Server database. Not used if "Use Windows Authentication" is True.
The password used to connect to the SQL Server database. Not used if "Use Windows Authentication" is True.
CareLink_Scheduling_DestinationAdapter tab
This adapter is used for configuring Paceart-CareLink Scheduling integration.
ExplanationField name
CareLinkSchedulingService
CareLinkSchedulingServiceSite
The name of the CareLink scheduling service that the adapter will be using. The default is "Endpoint_CSA_basicHttpsBinding".
The fully qualified path of the CareLink scheduling service that the adapter will be using. The default is "https://clscheduling.medtroniccarelink.net/SchedulingGateway/SchedulingGateway.svc".
CareLinkUserID
CareLinkUserPassword
SendPatientFirstName
SendPatientMiddleName
SendPatientGender
The name of the dedicated user that will be used to connect to the CareLink Scheduling service.
The password that will be used to authenticate the CareLink User ID with the CareLink Scheduling service.
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".
Paceart_GCIII_DestinationAdapter Tab
This adapter is used for Paceart HL7 integration.
ExplanationField name
PaceartDatabaseServer
PaceartDatabaseName
The name of the machine hosting the SQL Server database that the adapter will be using to interface with Paceart.
The database instance name of the database that the adapter will be using to interface with Paceart.
12 | Connectivity Guide | Installing the Connected Systems Gateway
ExplanationField name
UseWindowsAuthentication
SQLServerUserName
SQLServerPassword
PatientMatchingUseLastName
PatientMatchingUseMiddleName
PatientMatchingUseFirstName
PatientMatchingUseDateOfBirth
A Boolean value indicating that Windows Authentication should be used to connect to the SQL Server database. A setting of "False" will use the SQL User Name and the SQL Password configuration values to connect.
Windows Authentication is a login method that uses a Windows domain login to authenticate to the database. Some SQL Servers are configured to only allow connections via Windows logins. If you select Windows login, you must configure the HL7 services to run under the desired domain login.
The default is "False".
The user name used to connect to the SQL Server database. Not used if "Use Windows Authentication" is "True".
The password used to connect to the SQL Server database. Not used if "Use Windows Authentication" is "True".
If true, the patient last name will be used for demographic matching. The default is "True".
If true, the patient middle name will be used for demographic matching. The default is "False"
If true, the patient first name will be used for demographic matching. The default is "False".
If true, the patient date of birth will be used for demographic matching. The default is "True".
If true, the patient gender will be used for demographic matching. The default is "True".PatientMatchingUseGender
HL7_DestinationAdapter Tab
This adapter is used for Paceart HL7 integration.
ExplanationField name
OutboundSendingApplicationNamespaceID
OutboundSendingApplicationUniversalID
OutboundSendingApplicationUniversalIDType
This field uniquely identifies the sending application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. Entirely site-defined.
This information is included in the MSH segment 3, component 1.
The default is "Paceart".
This field uniquely identifies the sending application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. Entirely site-defined.
This information is included the MSH segment 3, component 2.
This field uniquely identifies the sending application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. Entirely site-defined.
This information is included the MSH segment 3, component 3.
Connectivity Guide | Installing the Connected Systems Gateway | 13
ExplanationField name
OutboundSendingFacilityNamespaceID
OutboundSendingFacilityUniversalID
OutboundSendingFacilityUniversalIDType
OutboundReceivingApplicationNamespaceID
OutboundReceivingApplicationUniversalID
This field further describes the sending application. Entirely site-defined.
This information is included the MSH segment 4, component 1.
The default value is "Medtronic".
This field further describes the sending application. Entirely site-defined.
This information is included the MSH segment 4, component 2.
This field further describes the sending application. Entirely site-defined.
This information is included the MSH segment 4, component 3.
This field uniquely identifies the receiving application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. Entirely site-defined.
This information will be in MSH, field 5, component 1.
This field uniquely identifies the receiving application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. Entirely site-defined.
OutboundReceivingApplicationUniversalIDType
OutboundReceivingFacilityNamespaceID
OutboundReceivingFacilityUniversalID
OutboundReceivingFacilityUniversalIDType
OutboundProcessingID
This information will be in MSH, field 5, component 2.
This field uniquely identifies the receiving application among all other applications within the network enterprise. The network enterprise consists of all those applications that participate in the exchange of HL7 messages within the enterprise. Entirely site-defined.
This information will be in MSH, field 5, component 3.
This field identifies the receiving application among multiple identical instances of the application running on behalf of different organizations. Entirely site-defined.
This information will be in MSH, field 6, component 1.
This field identifies the receiving application among multiple identical instances of the application running on behalf of different organizations. Entirely site-defined.
This information will be in MSH, field 6, component 2.
This field identifies the receiving application among multiple identical instances of the application running on behalf of different organizations. Entirely site-defined.
This information will be in MSH, field 6, component 3.
Defines in the MSH header whether the message is part of a production, training, or debugging system. D=Debugging, P=Production, T=Training.
This information will be in MSH, field 11, component 1.
14 | Connectivity Guide | Installing the Connected Systems Gateway
ExplanationField name
The default value is "P".
OutboundProcessingIDMode
OutboundHL7Version
OutboundIncludeEpisodeObservations
OutboundPatientVisitPatientClass
CommunicationQueue
HL7_SourceAdapter Tab
Defines in the MSH header the processing mode. A=Archive, R=Restore from archive, I=Initial load, T=Current processing transmitted at intervals.
This information will be in MSH, field 11, component 2.
Version of HL7 listed in the HL7 message header.
This information will be in MSH, field 12.
Default is "2.3.1".
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.
Default value is "False" (do not send episode data).
The default value is"U" and corresponds to a Patient Class of "Unknown". This information will be in PV1, field 2.
Used by the implementation to communicate with a third-party HL7 engine.
The default is "HL7Destination".
This adapter is used for Paceart HL7 integration.
ExplanationField name
CommunicationQueue
Used by the implementation to communicate with a third-party HL7 engine.
The default is "HL7Source". Do not change this value.

Starting the Connected Systems Gateway

During installation and configuration, you should manually start the Connected Systems Gateway service. After you have verified that your implementation was successful you can choose to automatically restart the service.
1. To start the Connected Systems Gateway go to Start > Administrative Tools > Services.
2. Right-click the Connected Systems Gateway service and select Start.
If you restart your computer you will have to restart this service.
3. After you verify that your implementation was successful you can set this service to automatically connect. Go to Start > Administrative Tools > Services.
4. Right-click the Connected Systems Gateway service and select Automatic.
If you restart your computer this service will automatically restart.
Connectivity Guide | Paceart-CareLink Scheduling Integration | 15

Paceart-CareLink Scheduling Integration

The Paceart-CareLink Scheduling Integration feature provides a way to automatically synchronize scheduling between the CareLink Network and the Paceart System. If you schedule an appointment in CareLink, it will be downloaded to the Paceart System; if you schedule an appointment in Paceart, it will be sent to CareLink.
Paceart regularly requests status information for appointments scheduled in CareLink. Schedules are either updated nightly or when a clinician makes a request from the Paceart System.
If an appointment is created in CareLink, CareLink retains ownership until the appointment is sent to Paceart. Once the Paceart System is updated to reflect the CareLink Network appointment, the appointment is owned by Paceart.
If a remote appointment is created or modified in Paceart, the appointment is automatically created or updated in CareLink. Ownership of the appointment remains with the Paceart System.
Paceart receives appointment status information that reflects the last known status as reported by CareLink. The remote status is displayed in patient appointment information on the Paceart System. Paceart records the completion and failure status details of this information in its log. Paceart scheduling requests that violate CareLink Network scheduling rules are displayed as errors in the Paceart System Remote Status field.

Scheduling integration requirements

You must ensure that Paceart patient records and appointments meet the following criteria before you use Paceart-CareLink scheduling integration.
• The Paceart patient record for patients followed on CareLink must have a birth date and a valid patient ID number. If either the birth date or the patient ID number is not in Paceart, appointments will not be sent to CareLink.
• Appointments created or updated in Paceart must have the patient remote follow-up service set to Medtronic CareLink Network, and the patient must have an active Medtronic ICD or pacemaker that is supported by the Medtronic CareLink Network. To find out if a device is supported, log into CareLink and click Resources > CareLink Supported Implanted Devices.
Paceart/CareLink patient matching for a single patient
The primary match is on the patient ID number 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 is not present in the CareLink system, a demographic match is performed. The configurable matching criteria include first name, middle initial, and gender in addition to the last name and birth date which are always used. If the demographic match succeeds, CareLink will record the patient number so future matches will be simpler and quicker.
This matching is performed on CareLink and is used when adding, updating and removing appointments, and when updating remote appointment status.
Paceart/CareLink patient matching for a batch download
In this scenario, the Paceart System downloads a list of all CareLink patients and appointments and then matches CareLink patients to Paceart patients. The primary matching is on the patient ID number and the birth date. If the patient ID number 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.
16 | Connectivity Guide | Paceart-CareLink Scheduling Integration

Troubleshooting scheduling connectivity problems

CareLink
• Verify that the CareLink account used to connect to the Connected Systems Gateway has a Transmission Permission selection of View changes transmission status from new to viewed.
• Verify that the CareLink account used to connect to the Connected Systems Gateway does not have an expired password.
• If the CareLink clinic has sub-clinics, verify that the CareLink account used to connect to the Connected Systems Gateway has access to the sub-clinics' patients integrated with Paceart.
• Verify that scheduling integration has not been unlinked. Go to the CareLink Network website and click
Manage My Clinic > Clinic Profile > External Systems Integration.
Paceart
• Verify that the Paceart database has a Connected Systems Gateway user.
• Verify the Paceart database password associated with the Connected Systems Gateway user.
• Verify that the patient's Scheduling tab in Paceart has the patient remote follow-up service set to Medtronic CareLink Network, and that the patient has a Medtronic ICD or pacemaker that is supported by the Medtronic CareLink Network. To view the CareLink Network supported devices list login to the CareLink website and go to Resources > CareLink Supported Implantable Devices.
• Verify that the Paceart patient record has a date of birth and a valid patient ID number.
Connected Systems Gateway
• Verify that the Connected Systems Gateway software and adapters were properly installed and configured.
• Verify that the correct CareLink hosting system was entered in the CareLink_Scheduling_DestinationAdapter tab of the Connected Systems Gateway Configuration Manager. The CareLink hosting system must match what was entered in the Remote Acquisition tab of the Paceart Gateway Services.
• Verify that the SQL Server user name and password were correctly entered in the Paceart_GCIII_SourceAdapter tab of the Connected Systems Gateway Configuration Manager if you are not using Windows authentication.
• Verify that the Paceart database name and server were correctly entered in the Paceart_GCIII_SourceAdapter tab of the Connected Systems Gateway Configuration Manager.
• Verify that the Connected Systems Gateway service was started.
Connectivity Guide | HL7 Integration Overview | 17

HL7 Integration Overview

The Paceart System supports the HL7 protocol which allows Paceart to integrate with your existing HL7-based Electronic Health Record (EHR) and Practice Management Systems. This allows you to import patient demographic and scheduling information into Paceart and to export transtelephonic, in-clinic, and remote event data from Paceart to EHR systems.
The information contained in this section assumes an understanding of the HL7 Message Specification and a working knowledge of Paceart.

Medtronic Connected Systems Gateway HL7 Overview

Paceart Patient Identifiers
The Paceart System supports a single value for a patient ID number. The Medtronic Connected Systems Gateway (CSG) requires that the sending system provide a single, unique patient ID number in every HL7 message. This patient ID number will be stored in the Paceart database as the patient ID number and will be used for patient matching.
Paceart does not support multiple patient identifiers. The patient ID number must be unique. The patient ID number in the Paceart System and the patient ID number in the EMR/PM system must match.
Patient Matching
Patient matching must be selected in the Connected Systems Gateway Configuration Manager. As part of implementing HL7 integration, the Paceart patient data must be reviewed to verify that each patient has the correct patient ID and that there are no duplicate patient IDs in the Paceart database.
Paceart has a process for matching patient data from the received HL7 message to the patients existing in the Paceart database. When an HL7 message is received, the Paceart database is searched to see if there is a Paceart patient ID that matches the patient ID from the HL7 message.
• If no match is found, then the patient does not exist in the Paceart System.
• If a match is found and the Paceart ID is HL7Confirmed, then this is considered a match and the patient exists in the Paceart System.
• If a match is found and the Paceart ID is not HL7Confirmed, then the customer-defined patient matching criteria is used to determine if this is the same person.
If the Paceart patient information matches the HL7 message patient information according to the matching criteria, then the Paceart ID is marked as HL7Confirmed. This is considered a match and the patient exists in the Paceart System.
If the verification criteria does not match between the HL7 message patient and the Paceart patient, Paceart will log an error message in the Paceart Data Exchange Log Viewer and the Connected Systems Gateway log. No data will be added or updated in Paceart.
The following diagram illustrates the process used by the HL7 adapter to determine if there is a patient in Paceart that matches the patient information in the HL7 message.
18 | Connectivity Guide | HL7 Integration Overview
Verification Criteria
Patient matching must be configured in the Connected Systems Gateway Feature Selector by the administrator during implementation. One or more of the following patient demographic fields can be configured to ensure the match:
• Last name
• First name
• Middle initial
• Date of birth
• Gender
If multiple fields are selected, then they all must match (i.e. multiple criteria are treated as a logical AND statement).
Connectivity Guide | HL7 Integration Overview | 19

HL7 Inbound Message Flow

Segments and Fields
Field definitions for message segments have been included in this document for easy reference.
A three character segment identifierSeg
Represents the position of the field within the segmentField
The descriptive name of the fieldName
Indicates whether the field may repeat, with the following designations:Repeating
• N - No repetition
• Y - The field may repeat an indefinite or site-determined number of times
• (Integer) - The field may repeat up to the number of times specified by the integer
This indicates the field designation using one of the following designators:OPT
• R - Required
• O - Optional
• C - Conditional on the trigger event or another field
• X - Not used with this trigger event
• B - Field remains for backward compatibility with previous version of HL7
HL7 Length
This is the maximum length specified in the HL7 specifications. It is the maximum number of characters that one occurrence of the data field may occupy.

HL7 Message Acknowledgement

Acknowledgement Message
The CSG HL7 adapter supports both HL7 original and enhanced acknowledgement mode for inbound messages. Refer to the Configuring reciever ACKnowledgement behavior topic in the NeoIntegrate online Help.
The acknowledgement messages that are sent to the sending systems are determined by the message status and the acknowledgement type that was requested in the MSH segment of the sending system.

Inbound Patient Administration Messages (ADT)

Purpose
The CSG HL7 adapter can receive demographic information from any system or interface engine that is using HL7 messaging. This allows for consistent patient demographic information across systems and reduces duplication of data entry.
20 | Connectivity Guide | HL7 Integration Overview
The patient administration transaction set provides for the transmission of new or updated demographic information about patients. Information that is entered in a patient administration system can be passed to Paceart as an unsolicited HL7 message.
The CSG HL7 adapter 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.
Default Configured HL7 Triggers
A04, A08, A28, A29, A47
Supported Transaction Types
DescriptionTransaction Type
Add new patient to Paceart (demographic information)
Update existing Paceart patient demographics
Mark patient for delete
If the patient does not exist in Paceart, then add the patient demographic information as a new record.
If multiple patients match in Paceart, then no Paceart data is updated and an error is logged in the Data Exchange Log Viewer of the Client application and in the Connected Systems Gateway Log.
If the patient exists in Paceart, then update the patient demographic information.
If the patient does not exist in Paceart, then no Paceart data is updated.
If multiple patients match in Paceart, then no Paceart data is updated and an error is logged in the Data Exchange Log Viewer of the client application and in the Connected Systems Gateway Log.
If the patient exists in Paceart, then change the Paceart Status field to inactive ("X").
If the patient does not exist in Paceart, then no Paceart data is updated.
If multiple patients match in Paceart, then no Paceart data is updated and an error is logged in the Data Exchange Log Viewer of the client application and in the Connected Systems Gateway Log.
Change the patient ID of a patient
If the current ID exists in Paceart and the new ID does not exist, then change the patient ID from current ID to new ID.
If the current ID does not exist in Paceart, then no Paceart data is changed.
If the current ID exists in Paceart and the new ID also exists in Paceart, then no Paceart data is updated and an error is logged in the Connected Systems Gateway Log.
If multiple patients match in Paceart, then no Paceart data is updated and an error is logged in the Data Exchange Log Viewer of the client application and in the Connected Systems Gateway Log.
Connectivity Guide | HL7 Integration Overview | 21
Paceart Patient Data
The following Paceart database fields can be updated by the Paceart HL7 processing of ADT messages:
PA LengthPA Req.PA FieldPA Table
20YPatientIDMaster
32YNameMaster
14NFirst_NameMaster
1NMiddle_IniMaster
DT8NBirth_DateMaster
1NSexMaster
50NAddressMaster
50NAddr_Line2Master
20NCityMaster
10NStateMaster
10NZipMaster
50NCountryMaster
20NPhoneNum1Master
20NPhoneNum2Master
The following Paceart labels are used to reference data only when the patient is added by the Paceart HL7 processing:
PA LengthPA Req.PA FieldPA Table
1NStatusMaster
6NAffilMaster

Inbound Message Segments

MSH - Message Header Segment (Required)
The following table shows the standard HL7 format for the message segment.
Field lengthOPTRPTNameFieldSeg
1RNField Separator1MSH
4RNEncoding Characters2MSH
180ONSending Application3MSH
180ONSending Facility4MSH
180ONReceiving Application5MSH
180ONReceiving Facility6MSH
22 | Connectivity Guide | HL7 Integration Overview
Field lengthOPTRPTNameFieldSeg
26ONDate/Time of message7MSH
40ONSecurity8MSH
7RNMessage Type9MSH
20RNMessage Control ID10MSH
3RNProcessing ID11MSH
60RNVersion ID12MSH
15ONSequence Number13MSH
180ONContinuation Pointer14MSH
2ONAccept Acknowledgement Type15MSH
2ONApplication Acknowledgement Type16MSH
2ONCountry Code17MSH
16OYCharacter Set18MSH
60ONPrincipal Language of Message19MSH
20MSH
scheme
ENV - Event Type Segment (Optional)
Event type segments are optional in the Paceart HL7 implementation.
PID - Patient Identification Segment (Required)
The following table shows the standard HL7 format for the patient identification segments (PIDs). The shaded fields show the fields being updated in the Paceart database.
Set ID1PID
Patient ID2PID
Patient Identifier List3PID
Check Digit3.2PID
Check digit scheme employed3.3PID
20ONAlternate Character Set handling
Paceart fieldsField lengthNameFieldSeg
Patient ID20ID3.1PID
Assigning authority3.4PID
Identifier type code3.5PID
Assigning facility3.6PID
Alternate Patient ID - PID4PID
Patient Name5PID
Last Name32Family Name5.1PID
First Name14Given Name5.2PID
Connectivity Guide | HL7 Integration Overview | 23
Paceart fieldsField lengthNameFieldSeg
Middle initial or name5.3PID
Suffix5.4PID
Prefix5.5PID
Degree5.6PID
Name Type Code5.7PID
Mother's Maiden Name6PID
Date of Birth26Date/Time of Birth7PID
Patient Sex1Sex8PID
Patient Alias9PID
Race10PID
Patient Address11PID
Address 150Street Address11.1PID
Address 250Other designation11.2PID
City20City11.3PID
State10State or province11.4PID
Zip Code10Zip or postal code11.5PID
Country50Country11.6PID
Address Type11.7PID
Country Code12PID
Phone Number 120Phone Number Home13PID
Phone Number 220Phone Number Business14PID
MRG - Patient Identification Segment (Required for ADT^A47)
The following table shows the standard HL7 format for the patient identification segments (MRGs). The shaded fields show the fields being updated in the Paceart database.
Paceart fieldsField lengthNameFieldSeg
Patient ID20Prior Patient Identifier List1MRG
Prior Alternate Patient ID2MRG
Prior Patient Account Number3MRG

Inbound Scheduling Messages (SIU)

Purpose
The Connected Systems Gateway HL7 adapter can accept unsolicited schedule notification messages (SIU) from a scheduling filler application. The HL7 standard defines four roles that the system can assume in scheduling
24 | Connectivity Guide | HL7 Integration Overview
integration. Paceart operates as an Auxiliary application or an "interested third-party." This allows for existing scheduling systems to serve as the Filler application and to send schedule notification messages to the Paceart System. The Filler application is said to "own" the schedule for the specified resources or, in other words, is the authoritative source for scheduling information.
Default Configured HL7 Triggers
S12, S13, S14, S15
Supported Transaction Types
The schedule notification messages can be processed to not only create and modify appointments in Paceart, but also can be used to add to or modify patient information. This allows for a patient to be added to Paceart based on their first appointment with a device clinic.
Updating, rescheduling, or canceling an appointment can only be performed as long as the appointment exists in Paceart. A Paceart appointment is said to exist if the appointment ID and associated Patient ID match the filler appointment ID and patient ID in the HL7 message. Appointments created by an HL7 message cannot be modified in the Paceart application, but they can be deleted from within the Paceart application. Paceart also removes appointments once an applicable event has been created for the patient. Appointments created by HL7 messages are processed in Paceart the same as appointments created directly in the Paceart application.
DescriptionTransaction Type
Add new patient to Paceart (demographic information)
Update existing Paceart patient demographics
Create new appointment for a patient that exists in Paceart
Reschedule an existing HL7-created Paceart appointment
If the patient does not exist in Paceart, then add the patient demographic information as a new record.
If multiple patients match in Paceart, then no Paceart data is updated and an error is logged in the Data Exchange Log Viewer of the Client application and in the Connected Systems Gateway Log.
If the patient exists in Paceart, then update the patient demographic information.
If the patient does not exist in Paceart, then no Paceart data is updated.
If multiple patients match in Paceart, then no Paceart data is updated and an error is logged in the Data Exchange Log Viewer of the Client application and in the Connected Systems Gateway Log.
Create a new appointment in Paceart if the appointment ID does not already exist in Paceart. If the appointment does exist then no appointment will be added.
Reschedule the appointment in Paceart if the appointment ID already exists in Paceart. If the appointment does not exist then no appointment will be rescheduled.
Modify an existing HL7-created Paceart appointment
Cancel an existing HL7-created Paceart appointment
Modify the appointment in Paceart if the appointment ID already exists in Paceart. If the appointment does not exist then no appointment will be modified.
Cancel/Remove the appointment in Paceart if the appointment ID already exists in Paceart. If the appointment does not exist then no appointment will be cancelled/removed.
Connectivity Guide | HL7 Integration Overview | 25
Paceart Scheduling Data
The following Paceart database fields are updated by the Paceart HL7 processing of SIU messages.
PA LengthPA Req.PA FieldPA Table
75 charactersYAppointmentIDEventData
DT8YEventDateEventData
255 charactersYEventTypeEventData
255 charactersNCommentEventData
75 charactersNVisit_IDEventData
AppointmentType Mapping
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 event type information is available in the scheduling messages, the appointment will fail to add/update the Paceart database.
The default configuration looks for this value in AIG-3.1.
Paceart Scheduled Event TypeAppointmentType
Arrhythmia TTM1
Arrhythmia Clinic2
Pacemaker TTM3
Pacemaker Clinic4
ICD Clinic6
Programming8
Miscellaneous10
Pacemaker Implant12
Pacemaker Remote13
ICD Implant14
ICD Remote15

Inbound Message Segments

The following is a list of inbound message segments. Some of the segments listed are required and others are optional.
MSH and PID-Patient Identification Segment (Required)
For information on the PID segment, see the "Inbound Patient Administration Messages (ADT)" section of this manual.
SCH-Schedule Activity Information Segment (Required)
The SCH segment contains the general information about the scheduled appointment.
26 | Connectivity Guide | HL7 Integration Overview
The following table lists schedule activity information segments. The shaded fields show the fields being updated in the Paceart database.
Placer Appointment ID1SCH
Occurrence Number3SCH
Placer Group Number4SCH
Schedule ID5SCH
Event Reason6SCH
Appointment Reason7SCH
Appointment Type8SCH
Appointment Duration9SCH
Appointment Duration Units10SCH
Appointment Timing Quantity11SCH
Paceart fieldField lengthNameFieldSeg
Appointment ID75Filler Appointment ID2SCH
Quantity11.1SCH
Interval11.2SCH
Duration11.3SCH
Appointment date/time26start date/time11.4SCH
end date/time11.5SCH
Priority11.6SCH
PV1-Patient Visit Segment (Optional)
The following table lists patient visit segments. The shaded fields show the fields being updated in the Paceart database.
Paceart fieldField lengthNameFieldSeg
Set ID1PV1
Patient Class2PV1
Assigned Patient Location3PV1
Admission Type4PV1
Preadmit Number5PV1
Prior Patient Location6PV1
Attending Doctor7PV1
Referring Doctor8PV1
Consulting Doctor9PV1
Hospital Service10PV1
Temporary Location11PV1
Preadmit Test Indicator12PV1
Readmission Indicator13PV1
Admit Source14PV1
Ambulatory Status15PV1
VIP Indicator16PV1
Admitting Doctor17PV1
Patient Type18PV1
RGS-Resource Group Segment (Optional)
Set ID - RGS1RGS
Segment Action Code2RGS
Connectivity Guide | HL7 Integration Overview | 27
Paceart fieldField lengthNameFieldSeg
Visit ID20Visit Number19PV1
Field lengthNameFieldSeg
Resource Group ID3RGS
AIS- Appointment Information - Service Segment (Optional)
Set ID - AIS1AIS
Segment Action Code2AIS
Universal Service ID3AIS
Start Date/Time4AIS
Start Date/Time Offset5AIS
Start Date/Time Offset6AIS
Duration7AIS
Duration Units8AIS
Allow Substitution Code9AIS
Filler Status Code10AIS
AIG-Appointment Information - General Resource Segment (Optional)
Field lengthNameFieldSeg
The shaded fields show the fields being updated in the Paceart database.
Set ID - AIG1AIG
Segment Action Code2AIG
Resource ID3AIG
Field lengthNameFieldSeg
255Identifier3.1AIG
28 | Connectivity Guide | HL7 Integration Overview
AIL - Appointment Information - General Resource Segment (Optional)
Set ID - AIL1AIL
Segment Action Code2AIL
Location Resource ID3AIL
Location Type-AIL4AIL
Location Group5AIL
Start Date/Time6AIL
Start Date/Time Offset7AIL
Start Date/Time Offset Units8AIL
Duration9AIL
Duration Units10AIL
Allow Substitution Code11AIL
Field lengthNameFieldSeg
Filler Status Code12AIL
AIP - Appointment Information - Personnel Resource Segment (Optional)
Set ID - AIL1AIP
Segment Action Code2AIP
Personnel Resource ID3AIP
Resource Role4AIP
Resource Group5AIP
Start Date/Time6AIP
Start Date/Time Offset7AIP
Start Date/Time Offset Units8AIP
Duration9AIP
Duration Units10AIP
Allow Substitution Code11AIP
Paceart fieldField lengthNameFieldSeg
Appointment reason code/visit type
Filler Status Code12AIP
NTE - Notes and Comments Segment (Optional)
The shaded fields show the fields being updated in the Paceart database.
Set ID - NTE1NTE
Source of Comment2NTE
Paceart fieldField lengthNameFieldSeg
Connectivity Guide | HL7 Integration Overview | 29
Paceart fieldField lengthNameFieldSeg
Appointment comment255Comment3NTE
Comment Type4NTE

Outbound Event Observation Reporting (ORU)

Purpose
The Connected Systems Gateway can send event and device information to other systems. This is done using the HL7 observation reporting message. Paceart can generate an unsolicited transmission of an observation message for any Paceart follow-up event or test. A user can use the export function in Paceart to send the current information to other systems in an HL7 message.
The observation reporting message will contain patient demographic information as well as observations related to device and follow-up event information.
Summary of Supported Actions
All exported events are sent as an unsolicited observation result (ORU^R01).
Outbound Message Format
Observation Results (unsolicited)ORU^R01
Message HeaderMSH
Patient IdentificationPID
Observation Report ID{ OBR
{ OBX }
}
Including a PDF report with an HL7 message
Paceart offers the option of embedding a PDF copy of the Paceart follow-up report in an HL7 message.
The embedded PDF binary object will be sent in a single OBX segment. The segment's data type (OBX-2) will be ED (encapsulated data). The value field (OBX-5) will be a multiple component field with the following layout.
Observation/Result
ValueComponent NameComponent
PaceartSource ApplicationOBX-5.1
ApplicationType of DataOBX-5.2
PostScriptData SubtypeOBX-5.3
Base64EncodingOBX-5.4
DataOBX-5.5
{Base64 encoded data stream of the PDF document}
30 | Connectivity Guide | HL7 Integration Overview
Example Segment:
OBX|5|ED|RPT-0001^Paceart PDF Embedded|1|Paceart^Application^PostScript^Base64^JVBERi0xLjI {a lot more data}
MSH - Message Header Segment
The following is the configuration for the construction of the MSH segment of the ORU^R01 message.
Note: Shaded items represent the HL7 data that is configurable in the Connected Systems Gateway Configuration Manager.
Field Separator1MSH
Encoding Characters2MSH
CSG Configuration Manager settingLengthNameFieldSeg
Tab:HL7_DestinationAdapter180Sending Application3MSH
180Namespace ID3.1
Universal ID3.2
Universal ID Type3.3
Namespace ID4.1
Universal ID Type4.3
Namespace ID5.1
Universal ID5.2
Universal ID Type5.3
Field: OutboundSendingApplicationNamespaceID
Field: OutboundSendingApplicationUniversalID
Field: OutboundSendingApplicationUniversalIDType
Tab: HL7_DestinationAdapter180Sending Facility4MSH
Field: OutboundSendingFacilityNamespaceID
Field: OutboundSendingFacilityUniversalIDUniversal ID4.2
Field: OutboundSendingFacilityUniversalIDTYpe
Tab: HL7_DestinationAdapter180Receiving Application5MSH
Field: OutboundReceivingApplicationNamespaceID
Field: OutboundReceivingApplicationUniversalID
Field: OutboundReceivingApplicationUniversalIDType
Tab: HL7_DestinationAdapter180Receiving Facility6MSH
Namespace ID6.1
Universal ID6.2
Universal ID Type6.3
12Date/Time of Message7MSH
Security8MSH
Field: OutboundReceivingFacilityNamespaceID
Field: OutboundReceivingFacilityUniversalID
Field: OutboundReceivingFacilityUniversalIDType
Date/Time message was created (YYYYMMDDHHSS)
Connectivity Guide | HL7 Integration Overview | 31
CSG Configuration Manager settingLengthNameFieldSeg
Message Type9MSH
Type ID9.1
Trigger Event ID9.2
20Message Control ID10MSH
Tab: HL7_DestinationAdapter3Processing ID11MSH
Field: OutboundProcessingIDProcessing ID11.1
Field: OutboundProcessingIDModeProcessing ID Mode11.2
Field: OutboundHL7Version60Version ID12MSH
PID - Patient Identification Segment
The following is the default configuration for the construction of the PID segment of the ORU^R01 message. The Paceart labels can be mapped to different HL7 fields in the PID segment in the Connected Systems Gateway Configuration Manager.
Note: Shaded items represent HL7 data that is mapped to Paceart and the default message locations they are mapped to.
Paceart fieldsLengthNameFieldSeg
Set ID1
Patient ID2
Patient Identifier List3
PatientID20ID3.1PID
Check Digit3.2
Check digit scheme employed3.3
Assigning authority3.4
Identifier type code3.5
Assigning facility3.6
Alternate Patient ID - PID4
Patient ID5
LastName32Family Name5.1PID
FirstName14Given Name5.2PID
MiddleInitial1Middle initial or name5.3PID
Suffix5.4
Prefix5.5
Degree5.6
Name Type Code5.7
Mother's Maiden Name6
32 | Connectivity Guide | HL7 Integration Overview
Paceart fieldsLengthNameFieldSeg
8Date/Time of Birth7PID
Patient Alias9
Race10
Patient Address11
Country11.6
Address Type11.7
Country Code12
BirthDate (YYYMMDD)
PA.Sex1Sex8PID
Address50Street Address11.1PID
AddressLine250Other designation11.2PID
City20City11.3PID
State10State or province11.4PID
ZipCode10Zip or postal Code11.5PID
PhoneNumber140Phone Number Home13PID
PhoneNumber240Phone Number Business14PID
OBR - Observation Request Segment (Report Header)
The following is the configuration for the construction of the OBR segment.
Note: Shaded items represent HL7 data that is mapped to Paceart and the default message locations they are mapped to.
NotesLengthDTNameFieldSeg
Sequence number starting at 1.4SISet ID - OBR1OBR
EIPlacer Order Number2OBR
38EIFiller Order Number3OBR
200CEUniversal Service ID4OBR
IDPriority5OBR
TSRequested Date/Time6OBR
TSObservation End Date/Time8OBR
CQCollection Volume9OBR
Unique identifier for the event observation set
See list under OBR:4 coded elements
Event date/time14TSObservation Date/Time7OBR
XCNCollector Identifier10OBR
IDSpecimen Action Code11OBR
CEDanger Code12OBR
Connectivity Guide | HL7 Integration Overview | 33
NotesLengthDTNameFieldSeg
STRelevent Clinical Info.13OBR
TSSpecimen Received Date/Time14OBR
CMSpecimen Source15OBR
Referring doctor 180XCNOrder Provider16OBR
XTNOrder Callback Phone Number17OBR
STPlacer Field 118OBR
STPlacer Field 219OBR
STFiller Field 120OBR
STFiller Field 221OBR
22OBR
Date/Time
CMCharge to Practice23OBR
IDDiagnostic Serv Sect ID24OBR
IDResult Status25OBR
CMParent Result26OBR
TQQuantity/Timing27OBR
CMParent29OBR
IDTransportation Mode30OBR
CEReason for Study31OBR
CMPrincipal Result Interpreter32OBR
CMAssistant Result Interpreter33OBR
OBX - Observation/Result Segment
The following is the configuration for the construction of the OBX segment.
Export date/time14TSResults Rpt/Status chng -
Referring doctor 280XCNResults Copies to28OBR
Event Operator50CMTechnician34OBR
Note: Shaded items represent HL7 data that is mapped to Paceart and the default message locations they are mapped to.
NotesLengthDTNameFieldSeg
Sequence number starting at 16SISet ID - OBX1OBX
Value type of OBX.53IDValue Type2OBX
Coded identifier80CEObservation Identifier3OBX
20STObservation Sub-ID4OBX
Sequence number for repeating observations
Value65536*Observation Value5OBX
34 | Connectivity Guide | HL7 Integration Overview
Device Observation
Device and evaluation data is represented in an HL7 ORU^R01 message as defined above. Each message contains one or more OBR segments with related attribute data represented in a series of OBX segments.
Coding
The identifier coding system referenced in OBR:4 and OBX:3 was developed by Medtronic specifically for the Paceart System outbound observation messaging. The name of the coding system component has been omitted from the coded element data because the Medtronic coding system is assumed throughout all ORU^R01 outbound messages.
OBR:4 Coded Elements
The items below identify the referenced Universal Service IDs (OBR:4).
OBR:4.2OBR:4.1
ICD Device ObservationDEV1
NotesLengthDTNameFieldSeg
Units60CEUnits6OBX
Pacemaker Device ObservationDEV2
Lead Device ObservationDEV3
Adapter Device ObservationDEV4
Transmitter Device ObservationDEV5
Arrhythmia (TTM) ObservationEVAL1
Arrhythmia (Clinic) ObservationEVAL2
Pacemaker (TTM) EvaluationEVAL3
Pacemaker (Clinic) EvaluationEVAL4
Pacemaker (Remote) EvaluationEVAL5
ICD (Clinic) EvaluationEVAL6
ICD (Implant) EvaluationEVAL7
ICD (Remote) EvaluationEVAL8
Programming EvaluationEVAL9
Miscellaneous EvaluationEVAL10
Pacemaker (Implant) EvaluationEVAL11

OBX:3 Coded Element

The items below identify the possible referenced Observation identifiers (OBX:3).
DEV-0003
Commentary
Connectivity Guide | HL7 Integration Overview | 35
Applies to:
Adapter
Lead
ICD
Pacemaker
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
STManufacturer
*
Transmitter
XXXXXICD, IPG, LEAD, or ADAP50CETypeDEV-0001
XXXXX50STManufacturerDEV-0002
XXXXXL
XXXXX50STModelDEV-0004
XXXXX20STSerial NumberDEV-0005
XXXX8DTImplant DateDEV-0006
XXAtrium or Ventricle60STChamber LocationDEV-0007
XXXX50STLocationDEV-0008
XX50STLead - Adaptor TypeDEV-0009
DEV-0014
DEV-0015
DEV-0021
Physician
Physician
Enabled
XXBipolar or Unipolar50STPolarityDEV-0010
XX50STAccessDEV-0011
XX20STConnectDEV-0012
XXY=Yes or N=No01361IDPacingDEV-0013
XXXX001060XCNPri. Implanting
XXXX001060XCNSec. Implanting
XXXX8DTAbandon DateDEV-0016
XXXX8DTPartial Explant DateDEV-0017
XXXX8DTExplant DateDEV-0018
STPatientCommentaryDEV-0019
STAlertDEV-0022
*
*
XXXXL
XXY=Yes or N=No01361IDBi-VentricularDEV-0020
XXY=Yes or N=No01361IDRemote Follow-up
XXXXXL
XXXX6STWarrantyDEV-0023
X100STBOL CharacteristicsDEV-0024
X100STEOL CharacteristicsDEV-0025
X12STEOL Charge TimeDEV-0026
X12STEOL VoltageDEV-0027
X12STERT Charge TimeDEV-0028
X12STERT VoltageDEV-0029
36 | Connectivity Guide | HL7 Integration Overview
Applies to:
Adapter
Lead
ICD
Pacemaker
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
Transmitter
Xj,v1STEnergy UnitsDEV-0030
X8DTDate GivenDEV-0031
X4.4.4.1.110STAcquisition SpeedDEV-0032
X25STTransmission FormatDEV-0033
X4.4.4.1.212STDefault GainDEV-0034
DEV-0035
Physician
DEV-0036
Physician
L*= Field can contain over 3000 characters.
Acquisition Speed Values
Default Gain Values
XXXX001080XCNAbandoning
XXXX001080XCNPartially Explanting
XXXX001080XCNExplanting PhysicianDEV-0037
Displayed in PaceartSent in HL7
1 X1
2 X2
3 X3
4 X4
Displayed in PaceartSent in HL7
5 mm/mV0.25
10 mm/mV0.5
20 mm/mV1
40 mm/mV2
80 mm/mV4
Example:
OBR|1||{F7FE875F-2BB5-4F1B-AB2B-5AE4E0B56811}|DEV2^Pacemaker Device
Observation |||2005091925625|||||||||6643^Claybourne^Wanda^^^^MD||||||2005 0919125625| OBX|1|CE|DEV-0001^Type|1|IPG^Pacemaker| OBX|2|ST|DEV-0002^Manufacturer|1|Medtronic| OBX|3|ST|DEV-0003^Manufacturer Commentary|1|DDD/RO or SSI/R \F\ Threshold Margin Test with magnet application is 3 (sets of) asynchronous pulses at a rate of 100 ppm (PW reduced by 25% on the
third pulse). \F\ | OBX|4|ST|DEV-0004^Model|1|7941 Thera DR | OBX|5|ST|DEV-0005^Serial Number|1|PAP003047| OBX|6|DT|DEV-0006^Implant Date|1|19971122| OBX|7|ST|DEV-0008^Location|1|Left Chest| OBX|8|XCN|DEV-00014^Pri. Implanting Physician|1|1211^Fischer^Raymond^^^^MD| OBX|9|DT|DEV-0018^Explant Date|1|10030722| OBX|10|ST|DEV-0024^BOL Characteristics|1|85 ppm (DOO/SOO)| OBX|11|ST|DEV-0025^EOL Characteristics|1|65 ppm (VOO)|
Arrhythmia Observation Identifiers
Connectivity Guide | HL7 Integration Overview | 37
Possible values or unitsTableLengthOBX2OBX:3.2OBX:3.1
14TSDate of eventARR-0001
TTM or Clinic10STEvent typeARR-0002
1=Yes or 0=No1IDCardioVoiceARR-0003
50STOperatorARR-0004
*
STEvent CommentaryARR-0005
L
L*= Field can contain over 3000 characters.
Device Evaluation Observation Identifiers
78STPatient LocationARR-0006
78STPatient activityARR-0007
200STFindings of testARR-0008
bpm4NMMinimum rateARR-0009
bpm4NMMaximum rateARR-0010
sec4NMPR interval at minimum rateARR-0011
sec4NMPR interval at maximum rateARR-0012
sec4NMQRS interval at minimum rateARR-0013
sec4NMQRS interval at maximum rateARR-0014
sec4NMQT interval at minimum rateARR-0015
sec4NMQT interval at maximum rateARR-0016
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Clinic
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
TTM
EVAL-0001
XXXXXXX14TSDate of
event
XXXXXXXTTM, Clinic, Remote, or Implant10STEvent TypeEVAL-0002
XXXXXXXY=Yes or N=No01361IDCardioVoiceEVAL-0003
38 | Connectivity Guide | HL7 Integration Overview
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Clinic
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
TTM
XXXXXXX50STOperatorEVAL-0004
EVAL-0007
EVAL-0008
EVAL-0009
EVAL-0010
EVAL-0011
EVAL-0012
EVAL-0013
EVAL-0014
EVAL-0015
XXXXXXX255STEvent
Commentary
XXXXms10NMDemand
Interval
XXXXms10NMDemand AV
Delay
XXXXms10NMMagnet
Interval
XXXXms10NMMagnet AV
Delay
XXXXms10NMMagnet
Atrial Pulse
Duration
XXXXms10NMMagnet
Vent. Pulse
Duration
XXXXXXXD=Dependant, ?=Undetermined, and -=N/A01361STAtrial
Capture
XXXXXXXD=Dependant, ?=Undetermined, and -=N/A01361STAtrial
Sensing
EVAL-0016
Capture
EVAL-0017
Sensing
EVAL-0018
Pressure
*
EVAL-0022
Commentary
STEval.
L*= Field can contain over 3000 characters.
XXXXXXXD=Dependant, ?=Undetermined, and -=N/A01361STVentricular
XXXXXXXD=Dependant, ?=Undetermined, and -=N/A01361STVentricular
XXXXXX25STBlood
XXX75STSymptomsEVAL-0019
XXXXXX75STRhythmEVAL-0020
XXXXXXXL

Identifiers

Telemetry Observation Identifiers
Connectivity Guide | HL7 Integration Overview | 39
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
Clinic
TEL-0001
TEL-0002
TEL-0003
TEL-0005
TEL-0006
TEL-0007
TEL-0008
TEL-0009
TEL-0010
XXX10NMPercent Pacing
Atrial
XXX10NMPercent Pacing
Ventricular
XXXv7NMMin. Volt During
Charging
XXXs10NMTest Charge TimeTEL-0004
XXXj,v10NMTest Charge
Energy
XXXv20STLast High Voltage
Energy
XXXs10STLast Hi Volt Chrg
Time
XXXohm15STLead Impedance
Atrial
XXXohm15STLead Impedance
Left Vent
XXXohm15STLead Impedance
Right Vent
TEL-0011
TEL-0014
XXXohm15STLead Impedance
High Volt
XXX10STAutoGainTEL-0012
XXXXXXv7STBattery VoltageTEL-0013
XXXohm7STBattery
Impedance
Example:
OBX|10|NM|TEL-0004^Test Charge Time|1|7.9|s|
OBX|11|NM|TEL-0005^Test Charge Energy|1|35|j| OBX|12|NM|TEL-0006^Last High Voltage Energy|1|35|v| OBX|13|NM|TEL-0007^Last Hi Volt Chrg Time|1|8.45|s| OBX|14|NM|TEL-0008^Lead Impedance Atrial|1|412|ohm| OBX|15|NM|TEL-0010^Lead Impedance Right Vent|1|440|ohm| OBX|16|NM|TEL-0011^Lead Impedance High Volt|1|202|ohm| OBX|17|NM|TEL-0013^Battery Voltage|1|2.99|v|
40 | Connectivity Guide | HL7 Integration Overview
Lead Observation Identifiers
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2ClassOBX:3.1
Clinic
2STChamberLeadLEAD-0001
LeadLEAD-0002
Impedance
LeadLEAD-0003
Impedance
LeadLEAD-0004
Response
Example:
OBX|15|ST|LEAD-0001^Chamber|1|RA| OBX|16|NM|LEAD-0002^Bipolar Impedance|1|450|ohm| OBX|17|ST|LEAD-0001^Chamber|2|RV| OBX|18|NM|LEAD-0002^Bipolar Impedance|2|550|ohm|
Threshold Observation Sensing Identifiers
Ventricle (RV), or Left Ventricle (LV)
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
Clinic
Remote
XXXRight Atrium (RA), Left Atrium (LA), Right
XXXohm15STBipolar
XXXohm15STUnipolar
XXX7STEvoked
XXX7STPolarizationLeadLEAD-0005
ICDPacemaker
Implant
Clinic
Remote
Implant
TSEN-0004
2STChamberTSEN-0001
Ventricle (RV), or Left Ventricle (LV)
Graphing
Example:
OBX|19|ST|TSEN-0001^Chamber|1|RA| OBX|20|NM|TSEN-0002^Amplitude millivolts|1| 5|mv| OBX|21|ST|TSEN-0003^Polarity|1|B| OBX|22|ID|TSEN-0004^Use For Graphing|1|Y|
XXXXXXRight Atrium (RA), Left Atrium (LA), Right
XXXXXXmv10NMAmplitudeTSEN-0002
XXXXXXU=Unipolar or B=Bipolar1STPolarityTSEN-0003
XXXXXXY=Yes or N=No01361IDUse for
XXXXXXM = Manual or A = Automatic1STTypeTSEN-0005
Threshold Observation Capture Identifiers
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
Connectivity Guide | HL7 Integration Overview | 41
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Clinic
2STChamberTCAP-0001
Ventricle (RV), or Left Ventricle (LV)
1STPolarityTCAP-0004
R=Ring>Coil
TCAP-0005
Graphing
Example:
OBX|26|ST|TCAP-0001^Chamber|1|RA| OBX|27|NM|TCAP-0002^Amplitude|1|1|v| OBX|28|ST|TCAP-0003^Duration|1|0.1| OBX|29|ST|TCAP-0004^Polarity|1|B| OBX|30|ID|TCAP-0005^Use For Graphing|1|N|
Detections and Treatments Observation Identifiers
XXXXXXRight Atrium (RA), Left Atrium (LA), Right
XXXXXXv10NMAmplitudeTCAP-0002
XXXXXXms10NMDurationTCAP-0003
XXXXXXU=Unipolar, B=Bipolar, T=Tip>Ring, or
XXXXXXY=Yes or N=No01361IDUse for
XXXXXXM = Manual or A = Automatic16STTypeTCAP-0006
ICD
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXX10STVentricular FibrillationDT-0001
XXX10STFast Vent. TachycardiaDT-0002
XXX10STSlow Vent. TachycardiaDT-0003
XXX10STVery Slow Vent. Tachy.DT-0004
XXX10STAtrial FibrillationDT-0005
XXX10STAtrial FlutterDT-0006
XXX10STAtrial TachycardiaDT-0007
XXX10STExt. HiRate Sus. DetectDT-0008
XXX6STNon Sus. Vent. DetectDT-0009
XXX6STNon Sus. Atrial DetectDT-0010
XXX10STAMS EpisodesDT-0011
XXX10STShocks delivered Vent.DT-0012
42 | Connectivity Guide | HL7 Integration Overview
Example:
OBX|36|ST|DT-0018^Percent Pacing Ventricular|1|99|pct| OBX|37|ST|DT-0019^Percent Pacing Atrial|1|99|pct|
ICD
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXX10STShocks delivered AtrialDT-0013
XXX10STShocks aborted Vent.DT-0014
XXX10STShocks aborted AtrialDT-0015
XXX10STATP Episodes VentricularDT-0016
XXX10STATP Episodes AtrialDT-0017
XXXpct10STPercent Pacing VentricularDT-0018
XXXpct10STPercent Pacing AtrialDT-0019
Telemetry Totals Observation Identifiers
ICD
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXX10STShocks DeliveredTOT-0001
XXX10STShocks AbortedTOT-0002
XXX20STTest ChangesTOT-0003
XXX20STTotal ChangesTOT-0004
XXXsec.15STCumulative Charge TimeTOT-0005
XXX26TSCounters Cleared DateTOT-0006
XXX5STCharges (50-200)TOT-0007
XXX5STCharges (250-400)TOT-0008
XXX5STCharges (450-600)TOT-0009
XXX5STCharges (650-750)TOT-0010
Example:
OBX|21|ST|TOT-0001^Shocks Delivered|1| 2| OBX|22|ST|TOT-0004^Total Charges|1|3| OBX|23|TS|TOT-0006^Counters Cleared Date|1|20010404000000|
ICD Episode Observation Identifiers
Connectivity Guide | HL7 Integration Overview | 43
ICD
Implant
Remote
ICD
Clinic
Clinic
XXX26TSLast InterrogatedEPH-0001
XXX26TSLast Cleared DateEPH-0002
Remote
XXXVT/VF, SVT/NST, or Mode Switch12STEpisode TypeEP-0001
XXX6NMEpisodeIDEP-0002
Implant
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Example:
OBX|39|TS|EPH-0001^Last Interrogated|1|20051111| OBX|40|TS|EPH-0002^Last Cleared Date|1|20041111| OBX|41|ST|EP-0001^Episode Type|1.1|VT/VF| OBX|42|NM|EP-0002^EpisodeID|1.1|7893t-0998| OBX|43|ST|EPD-0001^Field Name|1.1.1|<field name>| OBX|44|ST|EPD-0002^Field Value|1.1.1|<field value>|
Brady Programming Observation Identifiers
ICD
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
Implant
Remote
XXX50STField NameEPD-0001
XXX50STField ValueEPD-0002
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXXXXX5STPacing ModeBRDY-0001
XXXXXXbpm5STLower RateBRDY-0002
XXXXXXbpm5STTracking RateBRDY-0003
XXXXXXbpm5STMax. Sensor RateBRDY-0004
44 | Connectivity Guide | HL7 Integration Overview
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXXXXXbpm10STHysteresis RateBRDY-0005
XXXXXXbpm5STSleep RateBRDY-0006
XXXXXXOn; Off; Auto; N/A20STPMT InterventionBRDY-0007
Example:
OBX|35|ST|BRDY-0001^Pacing Mode|1|DDDR| OBX|36|NM|BRDY-0002^Lower Rate|1|70|bpm| OBX|37|NM|BRDY-0003^Tracking Rate|1|140|bpm| OBX|38|NM|BRDY-0004^Max Sensor Rate|1|120|bpm|
Brady Sensing Observation Identifiers
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
2STChamberBSEN-0001
Ventricle (RV), or Left Ventricle (LV)
Remote
XXXXXXRight Atrium (RA), Left Atrium (LA), Right
XXXXXXOn; Off; N/A; PVARP on PVC; DVI
XXXXXXYes; No; Int10STDependancyBRDY-0009
XXXXXX50STNotesBRDY-0010
Implant
20STPVC InterventionBRDY-0008
on PVC
ICDPacemaker
Clinic
Implant
Remote
Clinic
1STPolarityBSEN-0003
or Tip Ring (R)
Example:
OBX|39|ST|BSEN-0001^Chamber|1|RA| OBX|40|NM|BSEN-0002^Amplitude|1|1.0|mv| OBX|41|NM|BSEN-0004^Refractory Period|1|300|ms|
XXXXXXmv5STAmplitudeBSEN-0002
XXXXXXBipolar (B), Unipolar (U), Dual (D), Tip Coil (C),
XXXXXXms5STRefractory PeriodBSEN-0004
XXXXXXms5STBlanking PeriodBSEN-0005
Brady Pacing Observation Identifiers
Connectivity Guide | HL7 Integration Overview | 45
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
2STChamberBPAC-0001
Ventricle (RV), or Left Ventricle (LV)
1STPolarityBPAC-0004
(C), or Tip Ring (R)
Example:
OBX|45|ST|BPAC-0001^Chamber|1|RA| OBX|46|NM|BPAC-0002^Amplitude|1|3.8|v| OBX|47|NM|BPAC-0003^Pulse Width|1|0.4|ms|
Brady Rate Modulation Observation Identifiers
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
Remote
ICDPacemaker
Implant
Clinic
XXXXXXRight Atrium (RA), Left Atrium (LA), Right
XXXXXXv5STAmplitudeBPAC-0002
XXXXXXms5STPulse WidthBPAC-0003
XXXXXXBipolar (B), Unipolar (U), Dual (D), Tip Coil
Remote
XXXXXX15STThresholdBMOD-0001
Implant
BMOD-0003
BMOD-0004
XXXXXX15STSlopeBMOD-0002
XXXXXX15STAcceleration
Reaction
XXXXXX15STDeceleration
Recovery
XXXXXXbpm5STADL RateBMOD-0005
Example:
OBX|57|ST|BMOD-0001^Threshold|1|Medium| OBX|58|ST|BMOD-0002^Slope|1|7| OBX|59|ST|BMOD-0003^Accleration Reaction|1|30 min| OBX|60|ST|BMOD-0004^Decleration Recovery|1|5 sec|
46 | Connectivity Guide | HL7 Integration Overview
Brady AV Delay Observation Identifiers
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXXXXXms5STSensed AV DelayBAVD-0001
XXXXXXms5STPaced AV DelayBAVD-0002
BAVD-0003
Status
BAVD-0004
Minimum
BAVD-0005
Maximum
BAVD-0006
Minimum
BAVD-0007
Minimum
Brady AMS Observation Identifiers
XXXXXXOn; Off; Slow;Med; Fast; High; Low; N/A8STAdaptive AVDelay
XXXXXXbpm8STAdaptive Rate
XXXXXXbpm8STAdaptive Rate
XXXXXXms8STAdaptive Sensed
XXXXXXms8STAdaptive Paced
XXXXXXms8STVV DelayBAVD-0008
ICDPacemaker
Implant
Remote
Clinic
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXXXXXbpm5STRateBAMS-0001
Example:
OBX|58|NM|BAMS-0001^Rate|1|170|bpm|
Tachy Observation Identifiers
TACH-0001
Ventricular
XXXXXXms10STDurationBAMS-0002
XXXXXXbpm5STFallback RateBAMS-0003
ICD
Implant
Remote
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXXDisabled; 1-Zone; 2-Zone; 3-Zone; 4-Zone50STDetection Status
XXXDisabled; 1-Zone; 2-Zone; 3-Zone50STDetection Status AtrialTACH-0002
Connectivity Guide | HL7 Integration Overview | 47
ICD
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
Remote
Implant
TACH-0003
Ventricular
STCommentaryTACH-0005
L*= Field can contain over 3000 characters.
Example:
OBX|18|ST|TACH-0001^Detection Status Ventricular|1|1-ZONE| OBX|19|ST|TACH-0003^Therapy Status Ventricular|1|5.9|
Tachy VF Zone Observation Identifiers
TVF-0002
Configuration
XXXEnabled; Disabled; Monitor25STTherapy Status
XXXEnabled; Disabled; Monitor25STTherapy Status AtrialTACH-0004
*
ICD
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
25STTherapy
6-Shocks; 7-Shocks
Clinic
XXXL
Remote
XXXFixed: VF25STZone TypeTVF-0001
XXXN/A; Disabled; Monitor; 4-Shocks; 5-Shocks;
Implant
Example:
OBX|29|NM|TVF-0002^Detection Interval|1|343|ms|
Tachy VFZ Shock Therapy Observation Identifiers
XXXms10NMDetection IntervalTVF-0003
XXX25STDetection DurationTVF-0004
XXX25STRedetection DurationTVF-0005
XXXY=Yes or N=No01361IDCommittedTVF-0006
ICD
Implant
Remote
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXX3NMTherapy NumberTVFS-0001
XXXY=Yes or N=No01361IDStatusTVFS-0002
XXXv, j10NMShocks EnergyTVFS-0003
48 | Connectivity Guide | HL7 Integration Overview
ICD
Implant
Remote
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXXBiphasic or Monophasic20STWaveformTVFS-0004
XXXms10NMPulse Width PositiveTVFS-0005
TVFS-0006
Negative
Example:
OBX|63|NM|TVFS-0001^Therapy Number|1|1| OBX|64|ID|TVFS-0002^Status|1|N| OBX|65|NM|TVFS-0003^Shock Energy|1|0.4| OBX|66|ST|TVFS-0004^Waveform|1|Biphasic| OBX|67|ST|TVFS-0007^Pathway|1|AX>B|
Tachy Zone Observation Identifiers
XXXms10NMPulse Width
Remote
XXXB>AX; Initial; Reversed; RV(+), Can(-);
XXX10NMCardioversion DelayTVFS-0008
XXX1IDCommittedTVFS-0009
Implant
20STpathwayTVFS-0007
RV(-), Can(+); RV(+), SVC/Can(-);or
RV(-), SVC/Can(+); Ax>B
ICD
Possible values or unitsLengthOBX:2OBX:3.2OBX:3.1
Clinic
8STZoneTypeTZON-0001
EHR_SRDRate_bpmTZON-0007
*
NM*= Field is labeled NM but will send string data.
XXXFastVT; SlowVT, VSlowVT, AFib, AFlutter,
ATach
XXX25STTherapy ConfigurationTZON-0002
XXXms10NMDetection IntervalTZON-0003
XXX25STDetection DurationTZON-0004
XXX25STRedetection DurationTZON-0005
XXX16STCommentaryTZON-0006
XXXbpm10NM
XXXms10STEHR_SRD DurationTZON-0008
XXXms or pct5STSudden Onset CriteriaTZON-0009
XXXms5STRate Stability CriteriaTZON-0010
XXX25STQRS Morphology CriteriaTZON-0011
Example:
OBX|213|ST|TZON-0001^Therapy Configuration|1|Disabled| OBX|214|NM|TZON-0002^Detection Interval|1|350| OBX|215|NM|TZON-0007^EHR SRD Duration|1|12 min| OBX|216|ST|TZON-0009^Rate Stability Criteria|1|30| OBX|217|ST|TZON-0011^Zone Type|1|FastVT|
Tachy Z ATP Observation Identifiers
Connectivity Guide | HL7 Integration Overview | 49
ICD
Remote
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
Clinic
XXX3NMTherapy NumberTZAT-0001
XXXY=Yes or N=No01361IDStatusTZAT-0002
XXXBurst, Burst+, Aburst+, Ramp, Ramp+10STTherapy TypeTZAT-0003
Implant
TZAT-0006
TZAT-0012
TZAT-0014
XXX10NMStimuli CountTZAT-0004
XXXms, pct10NMCoupling IntervalTZAT-0005
XXXms, pct10NMCoupling Interval
Decrement
XXXms, pct10NMBurst Cycle LengthTZAT-0007
XXXpct10NMS1S2 RampTZAT-0008
XXXpct10NMS2SN RampTZAT-0009
XXXms10NMRamp DecrementTZAT-0010
XXXms10NMInterval DecrementTZAT-0011
XXXms10NMMinimum Burst Cycle
Length
XXX10NMNumber Of SequencesTZAT-0013
XXX10NMMaximum Number Of
Pulses
XXX10STPulse IncrementTZAT-0015
XXXms10NMScan DecrementTZAT-0016
XXXDecrement, Increment, or Dec./Inc.10STSequenceTZAT-0017
Example:
OBX|103|NM|TZAT-0001^Therapy Number|1|2| OBX|104|ID|TZAT-0002^Status|1|N|
XXXY=Yes or N=No01361IDSmart ModeTZAT-0018
XXXv10NMOutput AmplitudeTZAT-0019
XXXms10NMOutput DurationTZAT-0020
50 | Connectivity Guide | HL7 Integration Overview
OBX|105|ST|TZAT-0003^Therapy Type|1|Ramp| OBX|106|NM|TZAT-0004^Stimuli Count|1|8| OBX|107|NM|TZAT-0005^Coupling Interval|1|91| OBX|108|NM|TZAT-0011^Interval Decrement|1|10|ms| OBX|109|NM|TZAT-0012^Minimum Burst Cycle Length|1|200|ms| OBX|110|NM|TZAT-0013^Number Of Sequences|1|3| OBX|111|NM|TZAT-0019^Output Amplitude|1|8|v| OBX|112|NM|TZAT-0020^Output Duration|1|1.6|ms|
Tachy Z Shock Therapy Observation Identifiers
ICD
Implant
Remote
Possible values or unitsTableLengthOBX:2OBX:3.2OBX:3.1
Clinic
TZST-0001
TZST-0003
TZST-0005
TZST-0006
TZST-0008
Number
Energy
Positive
Negative
20STPathwayTZST-0007
RV(-), Can(+); RV(+), SVC/Can(-); RV(-),
SVC/Can(+); RV(+), SVC/Can(-);or RV(-),
SVC/Can(+)
Delay
Example:
OBX|203|NM|TZST-0001^Therapy Number|1|6| OBX|204|ID|TZST-0002^Status|1|N| OBX|205|NM|TZST-0003^Shock Energy|1|0.4| OBX|206|ST|TZST-0004^Waveform|1|Biphasic| OBX|207|ST|TZST-0007^Pathway|1|AX>B*|
XXXNMTherapy
XXXY=Yes or N=No01361IDStatusTZST-0002
XXXv, j10NMShock
XXX20STWaveformTZST-0004
XXXms10STPulse Width
XXXms10STPulse Width
XXXB>AX; Initial; Reversed; RV(+), Can(-);
XXXms10NMCardioversion

OBX:4 Sub-ID Numbering and Data Relationship

The OXB:4 field is used to distinguish between multiple OBX segments with the same observation ID organized under the same OBR segment. For example, a Pacemaker Clinic report might include pacing data for three different zones.
Connectivity Guide | HL7 Integration Overview | 51
The HL7 standard requires three OBX segments, one for each sensing zone. By putting a 1 in the Sub-ID of the first of these OBX segments, a 2 in the second, and a 3 in the third, we can uniquely identify each OBX segment for editing or replacement.
The sub-identifier is also used to group related components in reports, such as the amplitude and polarity data related to each of the sensing zones. Examples of repeating segments and grouping can be seen in the Sensing Data and Pacing Data sections.
The sub-identifier can also add heirarchical relationships to combine uniquely identified duplicate observation IDs as well as to group the data with a parent-child relationship. This is done using dot notation (example 1.1). The Zone and Therapies section illustrates how this type of sub-identifier is used in an ICD report.
Sensing Data
Each line in the circled area of the screen describes a chamber of the heart. The same data can be reported for each of the chambers. The sub-ID is used to group the data and uniquely identify the observations in the OBR segment.
The following example message shows that the data associated with the Right Atrium has a sub-ID of 1. The Right Ventricle has a sub-ID value of 2 and the Left Ventricle has a sub-ID value of 3.
Example
OBX|24|ST|BSEN-0001^Chamber|1|RA| OBX|25|NM|BSEN-0002^Amplitude|1|0.3|mv| OBX|26|ST|BSEN-0003^Polarity|1|B| OBX|27|NM|BSEN-0004^Refractory Period|1|310|ms| OBX|28|NM|BSEN-0005^Blanking Period|1|200|ms|
OBX|29|ST|BSEN-0001^Chamber|2|RV| OBX|30|NM|BSEN-0002^Amplitude|2|0.3|mv| OBX|31|ST|BSEN-0003^Polarity|2|B| OBX|32|NM|BSEN-0005^Blanking Period|2|230|ms|
OBX|33|ST|BSEN-0001^Chamber|3|LV| OBX|34|NM|BSEN-0005^Blanking Period|3|230|ms|
52 | Connectivity Guide | HL7 Integration Overview
Pacing Data
Pacing data is also grouped using a unique sub-ID for each chamber.
Example
OBX|35|ST|BPAC-0001^Chamber|1|RA| OBX|36|NM|BPAC-0002^Amplitude|1|3|v| OBX|37|NM|BPAC-0003^Pulse Width|1|0.4|ms| OBX|38|ST|BPAC-0004^Polarity|1|B|
OBX|39|ST|BPAC-0001^Chamber|2|RV| OBX|40|NM|BPAC-0002^Amplitude|2|3|v| OBX|41|NM|BPAC-0003^Pulse Width|2|0.4|ms| OBX|42|ST|BPAC-0004^Polarity|2|B|
OBX|43|ST|BPAC-0001^Chamber|3|LV| OBX|44|NM|BPAC-0002^Amplitude|3|0.5|v| OBX|45|NM|BPAC-0003^Pulse Width|3|1|ms|
Zones and Therapies
The sub-ID is also used when reporting zone and therapy data. There can be observations reported for multiple zones. Each zone can also have observations reported for multiple therapies specific to that zone.
This hierarchical relationship is reported using a #.# format in the sub-ID field. The first number indicates the zone and the second number (after the ".") indicates the therapy in that zone.
Connectivity Guide | HL7 Integration Overview | 53
Example
Data reported for the Fast VT zone, has a sub-ID of "1".
OBX|95|ST|TZON-0001^Zone Type|1|FastVT| OBX|96|ST|TZON-0002^Therapy Configuration|1|ATP + 1 Shock| OBX|97|NM|TZON-0003^Detection Interval|1|350|ms| OBX|98|NM|TZON-0008^EHR SRD Duration|1|12 min|ms| OBX|99|ST|TZON-0010^Rate Stability Criteria|1|30|ms|
The first Therapy within the Fast VT Zone has a sub-ID of "1.1" Zone 1 (Fast VT, first configured therapy).
OBX|100|NM|TZAT-0001^ATP Therapy Number|1.1|1| OBX|101|ID|TZAT-0002^Status|1.1|Y| OBX|102|ST|TZAT-0003^Therapy Type|1.1|Ramp| OBX|103|NM|TZAT-0004^Stimuli Count|1.1|8| OBX|104|NM|TZAT-0005^Coupling Interval|1.1|91|pct| OBX|105|NM|TZAT-0011^Interval Decrement|1.1|10|ms| OBX|106|NM|TZAT-0012^Minimum Burst Cycle Length|1.1|200|ms| OBX|107|NM|TZAT-0013^Number Of Sequences|1.1|3| OBX|108|ID|TZAT-0018^Smart Mode|1.1|N| OBX|109|NM|TZAT-0019^Output Amplitude|1.1|8|v| OBX|110|NM|TZAT-0020^Output Duration|1.1|1.6|ms|
Each therapy is reported in order for the fast VT zone.
The last therapy reported is a Shock therapy and has a sub-ID of 1.6, because it is the sixth reported therapy within the first zone.
54 | Connectivity Guide | HL7 Integration Overview
Example
OBX|159|NM|TZST-0001^Shock Therapy Number|1.6|6| OBX|160|ID|TZST-0002^Status|1.6|Y| OBX|161|NM|TZST-0003^Shock Energy|1.6|0.4|j| OBX|162|ST|TZST-0004^Waveform|1.6|Biphasic| OBX|163|ST|TZST-0007^Pathway|1.6|AX>B*|
The next Zone reported is Slow VT, and data has a sub-ID of "2".
Format for Zone/Therapy Sub-ID Numbering
Sub-IDObservation
1TVF (VF Zone)
1.1TVFS (Shock Therapy)
1.2TVFS (Shock Therapy)
1.3TVFS (Shock Therapy)
1.NTVFS (Shock Therapy)
1TZON (Zone)
1.1TZST (Shock Therapy)
1.2TZST (Shock Therapy)
1.3TZAT (ATP Therapy)
1.4TZAT (ATP Therapy)
2TZON (Zone)
...
...
Connectivity Guide | HL7 Integration Overview | 55
Sub-IDObservation
2.1TZAT (ATP Therapy)
2.2TZST (Shock Therapy)
2.3TZAT (ATP Therapy)
2.4TZST (Shock Therapy)
2.NTZAT (ATP Therapy)
2.N+1TZST (Shock Therapy)
XTZON (Zone)
X.1TZAT (ATP Therapy)
X.2TZAT (ATP Therapy)
X.3TZST (Shock Therapy)
...
Format for Episode Data Sub-ID Numbering
...
X.4TZST (Shock Therapy)
X.NTZAT (ATP Therapy)
X.N+1TZST (Shock Therapy)
Sub-IDObservation
1EPH
1EP
1.1EPD
1.2EPD
1.NEPD
2EP
2.1EPD
2.2EPD
...
...
2.NEPD
XEP
X.1EPD
X.2EPD
...
56 | Connectivity Guide | HL7 Integration Overview
Example 1: Brady Data
This example illustrates multiple sensing observations to the parent Brady data.
OBX|70|NM|BRDY-0002^Lower Rate|1|70|bpm| OBX|71|NM|BRDY-0003^Tracking Rate|1|110|bpm| OBX|72|NM|BRDY-0004^Max Sensor Rate|1|456|bpm| OBX|73|NM|BRDY-0005^Hysteresis Rate|1|765|bpm| OBX|74|ST|BRDY-0007^PMT Intervention|1|Off| OBX|75|ST|BRDY-0008^PVC Intervention|1|On| OBX|76|ST|BRDY-0009^Dependency|1|Yes| OBX|77|ST|BRDY-0010^Notes|1|Sample Notes|
OBX|78|ST|BSEN-0001^Chamber|1|RA| OBX|79|NM|BSEN-0002^Amplitude|1|67|mv| OBX|80|ST|BSEN-0003^Polarity|1|U| OBX|81|NM|BSEN-0004^Refractory Period|1|55|ms| OBX|82|NM|BSEN-0005^Blanking Period|1|667|ms|
OBX|83|ST|BSEN-0001^Chamber|2|RV| OBX|84|NM|BSEN-0002^Amplitude|2|2.8|mv| OBX|85|ST|BSEN-0003^Polarity|2|B| OBX|86|NM|BSEN-0004^Refractory Period|2|330|ms| OBX|87|NM|BSEN-0005^Blanking Period|2|75|ms|
Sub-IDObservation
X.NEPD
OBX|88|ST|BSEN-0001^Chamber|3|LV| OBX|89|NM|BSEN-0002^Amplitude|3|54|mv| OBX|90|ST|BSEN-0003^Polarity|3|B| OBX|91|NM|BSEN-0004^Refractory Period|3|128|ms| OBX|92|NM|BSEN-0005^Blanking Period|3|23|ms|
Example 2: Tachy Data
This example illystrates the VF Zone and zone relationship to the parent Tachy data:
OBX|57|ST|TACH-0001^Detection Status Ventricular|1|Disabled| OBX|58|ST|TACH-0002^Detection Status Atrial|1|1 - Zone| OBX|59|ST|TACH-0003^Therapy Status Ventricular|1|Enabled| OBX|60|ST|TACH-0004^Therapy Status Atrial|1|Enabled| OBX|61|ST|TACH-0005^Commentary|1|config comments|
OBX|62|ST|TVF-0001^Zone Type|1|VF| OBX|63|ST|TVF-0002^Therapy Configuration|1|6 Shocks| OBX|64|NM|TVF-0003^Detection Interval|1|300|ms| OBX|65|ST|TVF-0004^Detection Duration|1|12/16| OBX|66|ST|TVF-0005^Redetection Duration|1|6/8| OBX|67|ID|TVF-0006^Committed|1|N|
OBX|68|NM|TVFS-0001^Shock Therapy Number|1.1|1| OBX|69|ID|TVFS-0002^Status|1.1|N| OBX|70|NM|TVFS-0003^Shock Energy|1.1|0.4|j| OBX|71|ST|TVFS-0004^Waveform|1.1|Biphasic| OBX|72|ST|TVFS-0007^Pathway|1.1|AX>B*|
OBX|73|NM|TVFS-0001^Shock Therapy Number|1.2|2| OBX|74|ID|TVFS-0002^Status|1.2|N| OBX|75|NM|TVFS-0003^Shock Energy|1.2|0.4|j| OBX|76|ST|TVFS-0004^Waveform|1.2|Biphasic|
Connectivity Guide | HL7 Integration Overview | 57
OBX|77|ST|TVFS-0007^Pathway|1.2|AX>B*|
OBX|78|NM|TVFS-0001^Shock Therapy Number|1.3|3| OBX|79|ID|TVFS-0002^Status|1.3|N| OBX|80|NM|TVFS-0003^Shock Energy|1.3|10|j| OBX|81|ST|TVFS-0004^Waveform|1.3|Biphasic| OBX|82|ST|TVFS-0007^Pathway|1.3|AX>B*|
OBX|83|NM|TVFS-0001^Shock Therapy Number|1.4|4| OBX|84|ID|TVFS-0002^Status|1.4|N| OBX|85|NM|TVFS-0003^Shock Energy|1.4|10|j| OBX|86|ST|TVFS-0004^Waveform|1.4|Biphasic| OBX|87|ST|TVFS-0007^Pathway|1.4|AX>B*|
OBX|88|NM|TVFS-0001^Shock Therapy Number|1.5|5| OBX|89|ID|TVFS-0002^Status|1.5|N| OBX|90|NM|TVFS-0003^Shock Energy|1.5|10|j| OBX|91|ST|TVFS-0004^Waveform|1.5|Biphasic| OBX|92|ST|TVFS-0007^Pathway|1.5|AX>B*|
OBX|93|NM|TVFS-0001^Shock Therapy Number|1.6|6| OBX|94|ID|TVFS-0002^Status|1.6|N| OBX|95|NM|TVFS-0003^Shock Energy|1.6|10|j| OBX|96|ST|TVFS-0004^Waveform|1.6|Biphasic| OBX|97|ST|TVFS-0007^Pathway|1.6|AX>B*|
OBX|98|ST|TZON-0001^Zone Type|1|FastVT| OBX|99|ST|TZON-0002^Therapy Configuration|1|2 Shocks| OBX|100|NM|TZON-0003^Detection Interval|1|350|ms| OBX|101|NM|TZON-0008^EHR SRD Duration|1|12 min|ms| OBX|102|ST|TZON-0010^Rate Stability Criteria|1|30|ms|
OBX|103|NM|TZAT-0001^ATP Therapy Number|1.1|1| OBX|104|ID|TZAT-0002^Status|1.1|N| OBX|105|ST|TZAT-0003^Therapy Type|1.1|Ramp| OBX|106|NM|TZAT-0004^Stimuli Count|1.1|8| OBX|107|NM|TZAT-0005^Coupling Interval|1.1|91|pct| OBX|108|NM|TZAT-0011^Interval Decrement|1.1|10|ms| OBX|109|NM|TZAT-0012^Minimum Burst Cycle Length|1.1|200|ms| OBX|110|NM|TZAT-0013^Number Of Sequences|1.1|3| OBX|111|ID|TZAT-0018^Smart Mode|1.1|N| OBX|112|NM|TZAT-0019^Output Amplitude|1.1|8|v| OBX|113|NM|TZAT-0020^Output Duration|1.1|1.6|ms|
OBX|114|NM|TZAT-0001^ATP Therapy Number|1.2|2| OBX|115|ID|TZAT-0002^Status|1.2|N| OBX|116|ST|TZAT-0003^Therapy Type|1.2|Ramp| OBX|117|NM|TZAT-0004^Stimuli Count|1.2|8| OBX|118|NM|TZAT-0005^Coupling Interval|1.2|91|pct| OBX|119|NM|TZAT-0011^Interval Decrement|1.2|10|ms| OBX|120|NM|TZAT-0012^Minimum Burst Cycle Length|1.2|200|ms| OBX|121|NM|TZAT-0013^Number Of Sequences|1.2|3| OBX|122|ID|TZAT-0018^Smart Mode|1.2|N| OBX|123|NM|TZAT-0019^Output Amplitude|1.2|8|v| OBX|124|NM|TZAT-0020^Output Duration|1.2|1.6|ms|
OBX|125|NM|TZAT-0001^ATP Therapy Number|1.3|3| OBX|126|ID|TZAT-0002^Status|1.3|N| OBX|127|ST|TZAT-0003^Therapy Type|1.3|Ramp+| OBX|128|NM|TZAT-0004^Stimuli Count|1.3|3| OBX|129|NM|TZAT-0005^Coupling Interval|1.3|75|pct| OBX|130|NM|TZAT-0008^S1S2 Ramp|1.3|69|pct|
58 | Connectivity Guide | HL7 Integration Overview
OBX|131|NM|TZAT-0009^S2SN Ramp|1.3|66|pct| OBX|132|NM|TZAT-0012^Minimum Burst Cycle Length|1.3|200|ms| OBX|133|NM|TZAT-0013^Number Of Sequences|1.3|5| OBX|134|ST|TZAT-0015^Pulse Increment|1.3|1| O BX|135|ID|TZAT-0018^Smart Mode|1.3|N| OBX|136|NM|TZAT-0019^Output Amplitude|1.3|8|v| OBX|137|NM|TZAT-0020^Output Duration|1.3|1.6|ms|
OBX|138|NM|TZAT-0001^ATP Therapy Number|1.4|4| OBX|139|ID|TZAT-0002^Status|1.4|N| OBX|140|ST|TZAT-0003^Therapy Type|1.4|Ramp+| OBX|141|NM|TZAT-0004^Stimuli Count|1.4|3| OBX|142|NM|TZAT-0005^Coupling Interval|1.4|75|pct| OBX|143|NM|TZAT-0008^S1S2 Ramp|1.4|69|pct| OBX|144|NM|TZAT-0009^S2SN Ramp|1.4|66|pct| OBX|145|NM|TZAT-0012^Minimum Burst Cycle Length|1.4|200|ms| OBX|146|NM|TZAT-0013^Number Of Sequences|1.4|5| OBX|147|ST|TZAT-0015^Pulse Increment|1.4|1| OBX|148|ID|TZAT-0018^Smart Mode|1.4|N| OBX|149|NM|TZAT-0019^Output Amplitude|1.4|8|v| OBX|150|NM|TZAT-0020^Output Duration|1.4|1.6|ms|
OBX|151|NM|TZAT-0001^ATP Therapy Number|1.5|5| OBX|152|ID|TZAT-0002^Status|1.5|N| OBX|153|ST|TZAT-0003^Therapy Type|1.5|Burst| OBX|154|NM|TZAT-0004^Stimuli Count|1.5|15| OBX|155|NM|TZAT-0005^Coupling Interval|1.5|88|pct| OBX|156|NM|TZAT-0011^Interval Decrement|1.5|10|ms| OBX|157|NM|TZAT-0012^Minimum Burst Cycle Length|1.5|200|ms| OBX|158|NM|TZAT-0013^Number Of Sequences|1.5|1| OBX|159|ID|TZAT-0018^Smart Mode|1.5|N| OBX|160|NM|TZAT-0019^Output Amplitude|1.5|8|v| OBX|161|NM|TZAT-0020^Output Duration|1.5|1.6|ms|
OBX|162|NM|TZST-0001^Shock Therapy Number|1.6|6| OBX|163|ID|TZST-0002^Status|1.6|N| OBX|164|NM|TZST-0003^Shock Energy|1.6|0.4|j| OBX|165|ST|TZST-0004^Waveform|1.6|Biphasic| OBX|166|ST|TZST-0007^Pathway|1.6|AX>B*|
OBX|167|ST|TZON-0001^Zone Type|2|SlowVT| OBX|168|ST|TZON-0002^Therapy Configuration|2|ATP Only| OBX|169|NM|TZON-0003^Detection Interval|2|450|ms| OBX|170|ST|TZON-0004^Detection Duration|2|12| OBX|171|ST|TZON-0005^Redetection Duration|2|4| OBX|172|NM|TZON-0008^EHR SRD Duration|2|12 min|ms| OBX|173|ST|TZON-0010^Rate Stability Criteria|2|30|ms|
OBX|174|NM|TZAT-0001^ATP Therapy Number|2.1|1| OBX|175|ID|TZAT-0002^Status|2.1|N| OBX|176|ST|TZAT-0003^Therapy Type|2.1|Ramp| OBX|177|NM|TZAT-0004^Stimuli Count|2.1|3| OBX|178|NM|TZAT-0005^Coupling Interval|2.1|91|pct| OBX|179|NM|TZAT-0011^Interval Decrement|2.1|10|ms|
OBX|180|NM|TZAT-0012^Minimum Burst Cycle Length|2.1|200|ms| OBX|181|NM|TZAT-0013^Number Of Sequences|2.1|3| OBX|182|ID|TZAT-0018^Smart Mode|2.1|N| OBX|183|NM|TZAT-0019^Output Amplitude|2.1|8|v| OBX|184|NM|TZAT-0020^Output Duration|2.1|1.6|ms|
OBX|185|NM|TZAT-0001^ATP Therapy Number|2.2|2|
Connectivity Guide | HL7 Integration Overview | 59
OBX|186|ID|TZAT-0002^Status|2.2|N| OBX|187|ST|TZAT-0003^Therapy Type|2.2|Ramp+| OBX|188|NM|TZAT-0004^Stimuli Count|2.2|15| OBX|189|NM|TZAT-0005^Coupling Interval|2.2|75|pct| OBX|190|NM|TZAT-0008^S1S2 Ramp|2.2|69|pct| OBX|191|NM|TZAT-0009^S2SN Ramp|2.2|66|pct| OBX|192|NM|TZAT-0012^Minimum Burst Cycle Length|2.2|200|ms| OBX|193|NM|TZAT-0013^Number Of Sequences|2.2|5| OBX|194|ST|TZAT-0015^Pulse Increment|2.2|1| OBX|195|ID|TZAT-0018^Smart Mode|2.2|N| OBX|196|NM|TZAT-0019^Output Amplitude|2.2|8|v| OBX|197|NM|TZAT-0020^Output Duration|2.2|1.6|ms|
OBX|198|NM|TZAT-0001^ATP Therapy Number|2.3|3| OBX|199|ID|TZAT-0002^Status|2.3|N| OBX|200|ST|TZAT-0003^Therapy Type|2.3|Ramp+| OBX|201|NM|TZAT-0004^Stimuli Count|2.3|3| OBX|202|NM|TZAT-0005^Coupling Interval|2.3|75|pct| OBX|203|NM|TZAT-0008^S1S2 Ramp|2.3|69|pct| OBX|204|NM|TZAT-0009^S2SN Ramp|2.3|66|pct| OBX|205|NM|TZAT-0012^Minimum Burst Cycle Length|2.3|200|ms| OBX|206|NM|TZAT-0013^Number Of Sequences|2.3|5| OBX|207|ST|TZAT-0015^Pulse Increment|2.3|1| OBX|208|ID|TZAT-0018^Smart Mode|2.3|N| OBX|209|NM|TZAT-0019^Output Amplitude|2.3|8|v| OBX|210|NM|TZAT-0020^Output Duration|2.3|1.6|ms|
OBX|211|NM|TZAT-0001^ATP Therapy Number|2.4|4| OBX|212|ID|TZAT-0002^Status|2.4|N| OBX|213|ST|TZAT-0003^Therapy Type|2.4|Ramp+| OBX|214|NM|TZAT-0004^Stimuli Count|2.4|3| OBX|215|NM|TZAT-0005^Coupling Interval|2.4|75|pct| OBX|216|NM|TZAT-0008^S1S2 Ramp|2.4|69|pct| OBX|217|NM|TZAT-0009^S2SN Ramp|2.4|66|pct| OBX|218|NM|TZAT-0012^Minimum Burst Cycle Length|2.4|200|ms| OBX|219|NM|TZAT-0013^Number Of Sequences|2.4|5| OBX|220|ST|TZAT-0015^Pulse Increment|2.4|1| OBX|221|ID|TZAT-0018^Smart Mode|2.4|N| OBX|222|NM|TZAT-0019^Output Amplitude|2.4|8|v| OBX|223|NM|TZAT-0020^Output Duration|2.4|1.6|ms|
OBX|224|NM|TZAT-0001^ATP Therapy Number|2.5|5| OBX|225|ID|TZAT-0002^Status|2.5|N| OBX|226|ST|TZAT-0003^Therapy Type|2.5|Ramp| OBX|227|NM|TZAT-0004^Stimuli Count|2.5|8| OBX|228|NM|TZAT-0005^Coupling Interval|2.5|91|pct| OBX|229|NM|TZAT-0011^Interval Decrement|2.5|10|ms| OBX|230|NM|TZAT-0012^Minimum Burst Cycle Length|2.5|200|ms| OBX|231|NM|TZAT-0013^Number Of Sequences|2.5|3| OBX|232|ID|TZAT-0018^Smart Mode|2.5|N| OBX|233|NM|TZAT-0019^Output Amplitude|2.5|8|v| OBX|234|NM|TZAT-0020^Output Duration|2.5|1.6|ms|
OBX|235|NM|TZST-0001^Shock Therapy Number|2.6|6| OBX|236|ID|TZST-0002^Status|2.6|N| OBX|237|NM|TZST-0003^Shock Energy|2.6|0.4|j| OBX|238|ST|TZST-0004^Waveform|2.6|Biphasic| OBX|239|ST|TZST-0007^Pathway|2.6|AX>B*|
OBX|240|ST|TZON-0001^Zone Type|3|VSlowVT| OBX|241|ST|TZON-0002^Therapy Configuration|3|Monitor| OBX|242|ST|TZON-0001^Zone Type|4|AFib|
60 | Connectivity Guide | HL7 Integration Overview
OBX|243|ST|TZON-0002^Therapy Configuration|4|4 - Shocks| OBX|244|NM|TZON-0003^Detection Interval|4|5|ms| OBX|245|ST|TZON-0001^Zone Type|5|AFlutter| OBX|246|ST|TZON-0002^Therapy Configuration|5|1 Shock| OBX|247|ST|TZON-0010^Rate Stability Criteria|5|30|ms|
OBX|248|ST|TZON-0001^Zone Type|6|ATach| OBX|249|ST|TZON-0002^Therapy Configuration|6|3 Shocks|

Troubleshooting HL7 connectivity problems

Programmer Acquisition service cannot start Event Log message

If in the Event Log for the Programmer Acquisition service you receive an error message that says "Programmer Acquisition service cannot start", you need to change the NeoIntegrate port value.
1. Click Start > Programs > NeoTool > NeoIntegrate > NeoIntegrate Configuration.
2. Click Service > NeoIntegreate Monitor Service Configuration. The NeoIntegrate Monitor Service Configuration window is displayed.
3. Change the port value.
4. Click OK.
Connectivity Guide | Paceart XML Schema | 61

Paceart XML Schema

The Paceart System will export files that conform to a Paceart proprietary schema definition. If you will be integrating the Paceart System to another system, it is essential that you write your integration into the Paceart XML schema.

Parameter valid values

UnitsParameter
msBurstCycleLengthUnits
%
msCouplingIntervalUnits
%
msCouplingIntervalDecrementUnits
%
JShockEnergyUnits
V
msSuddenOnsetCriteriaUnits
%
JTestChargeEnergyUnits
V
ValuesExport Parameter
VT/VFEpisodeType
SVT/NST
Mode Switch/AT/AF
FastVTZoneType
SlowVT
VSlowVT
AFib
AFlutter
ATach
DecrementATPSequence
Increment
Dec./Inc.
62 | Connectivity Guide | Paceart XML Schema
ValuesExport Parameter
BurstATPTherapyType
Burst+
ABurst+
Ramp
Ramp+
AX>BShockPathway
B>AX
Initial
Reversed
RV(+), Can(-)
RV(-), Can(+)
RV(+), SVC/Can(-)
RV(-), SVC/Can(+)
UnipolarPolarity
Bipolar
AfterCrossChamberSenseBlankingPeriodType
AfterSameChamberSense
AfterCrossChamberPace
AfterSameChamberPace
AfterSameChamberSenseOrPace
AfterCrossChamberSenseOrPace
BSensePolarity
U
D
C
R
BPacePolarity
U
D
T
R
RAChamber
LA
RV
Connectivity Guide | Paceart XML Schema | 63
ValuesExport Parameter
LV
YAssessment
N
D
?
-
PacemakerLeadConnect
ICD
AtriumLeadChamber
Ventricle
Medtronic CareLink NetworkRemoteFollowUpServiceName
LATITUDE Patient Management System
St. Jude Medical Monitoring System
BIOTRONIK Home Monitoring System
monitoring service
MSex
F
SingleLeadTransmissionFormat
CardGuard
Instromedix
Zymed
Paceart3Lead
Paceart6Lead
Paceart7Lead
PaceartEASI12Lead
PaceartHeartAccess3500
TZMedical
DelMarReynolds
Braemar
ProcessingAppointment Remote Status
Scheduled
Error
Complete
Missed
64 | Connectivity Guide | Paceart XML Schema

Paceart XML export

FileInformation
This block is rooted at /Paceart/FileInformation/ in the XML output.
ValuesExport Parameter
Ignored
TypeParameter XPathParameter
string[10]@SchemaVersionN/A
string[100]@InstitutionNameReport Header Line 1
dateTime@GenerationDateN/A
string[50]@UserNameN/A
string[50]@WorkstationIDN/A

Lookup tables

BillingCodes
This block is rooted at /Paceart/LookupTables/BillingCodes/BillingCodeDetail/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string[40]@DescriptionBilling Description
string[8]@CodeBilling Code
int@SMSCodeBilling SMS Code
CPTCodes
This block is rooted at /Paceart/LookupTables/CPTCodes/CPTCodeDetail/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string[40]@DescriptionCurrent Procedural Terminology
Description
string[8]@CodeCurrent Procedural Terminology
Code
Pacemakers
This block is rooted at /Paceart/LookupTables/Devices/Pacemakers/PacemakerDetail/ in the XML file.
Connectivity Guide | Paceart XML Schema | 65
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@ManufacturerDevice Manufacturer
string[50]@ModelDevice Model
string[100]@BOLDevice BOL
string[100]@EOLDevice EOL
boolean@BiVentricularDevice Bi-ventricular
boolean@RemoteFollowUpEnabledDevice Remote Follow-up Enabled
string[255]@AlertDevice Model Alert Comments
short@WarrantyDevice Warranty
string@CommentaryDevice Comments
ICDs
This block is rooted at /Paceart/LookupTables/Devices/ICD/ICDDetail/ in the XML file
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@ManufacturerDevice Manufacturer
string[50]@ModelDevice Model
float@EOLChargeTimeDevice EOL Charge Time
float@EOLVoltageDevice EOL Voltage
float@ERTChargeTimeDevice ERT Charge Time
float@ERTVoltageDevice ERT Voltage
string[1]@EnergyUnitsDevice Energy Units
boolean@BiventricularDevice Bi-Ventricular
boolean@RemoteFollowUpEnabledDevice Remote Follow-up Enabled
string[255]@AlertDevice Model Alert Comments
short@WarrantyDevice Warranty
string@CommentaryDevice Comments
Leads
This block is rooted at /Paceart/LookupTables/Devices/Leads/LeadDetail/ in the XML file
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@ManufacturerDevice Manufacturer
string[50]@ModelDevice Model
string[50]@TypeDevice Type
66 | Connectivity Guide | Paceart XML Schema
Adapters
This block is rooted at /Paceart/LookupTables/Devices/Adapters/AdapterDetail/ in the XML file
TypeParameter XPathParameter
string[50]@PolarityDevice Polarity
string[255]@AlertDevice Model Alert Comments
short@WarrantyDevice Warranty
string@CommentaryDevice Comments
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@ManufacturerDevice Manufacturer
string[50]@ModelDevice Model
string[50]@TypeDevice Type
string[50]@PolarityDevice Polarity
string[255]@AlertDevice Model Alert Comments
short@WarrantyDevice Warranty
string@CommentaryDevice Comments
Transmitters
This block is rooted at /Paceart/LookupTables/Devices/Transmitters/TransmitterDetail/ in the XML file
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@ManufacturerDevice Manufacturer
string[50]@ModelDevice Model
boolean@InvertPolarityDevice Invert Polarity
float@DefaultGainDevice Default Gain
byte@AcquisitionSpeedDevice Transmit Speed
N/A@TransmissionFormatDevice Transmit Format
string@CommentaryDevice Comments
Diagnosis
This block is rooted at /Paceart/LookupTables/Diagnosis/DiagnosisDetail/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@DescriptionDiagnosis Description
string[6]@CodeDiagnosis Code
Connectivity Guide | Paceart XML Schema | 67
Doctors
This block is rooted at /Paceart/LookupTables/Doctors/DoctorDetail/ in the XML file.
TypeParameter XPathParameter
string[50]PagerServiceReference/@GUIDProvider Pager Service
string[50]@GUIDN/A
string[32]@nameLastProvider Last Name
string[14]@nameFirstProvider First Name
string[1]@nameMiddleProvider Middle Initial
string[20]@nameDegreeProvider Credentials
string[5]@nameHonorificProvider Prefix
string[50]@addrLine1Provider Address Line 1
string[50]@addrLine2Provider Address Line 2
string[20]@addrCityProvider Address City
string[10]@addrStateProvider Address State
string[10]@addrZipcodeProvider Address Postal Code
string[50]@addrCountryProvider Address Country
string[20]@addrPhoneNumberProvider Phone Number
string[20]@addrFaxnumberProvider Fax Number
string[100]@addrEmailProvider Email Address
string[6]@DoctorCodeProvider Code
string[12]@ProviderIDProvider Identifier
string[11]@SocialSecurityNumberProvider SSN
string[14]@LicenseNumberProvider License Number
string[3]@BillingCodeProvider Bill Code
string[20]@CardioVoiceIDProvider CardioVoice Identifier
string[20]@webPasswordProvider Web Password
dateTime@webLastLoginDateLast Web Login Date
string[20]@PagerPINProvider Pager PIN
string@CommentaryProvider Comments
InsuranceCompanies
This block is rooted at /Paceart/LookupTables/InsuranceCompanies/InsuranceCompanyDetail/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@CompanyNameInsurance Company Name
string[8]@CodeInsurance Company Code
68 | Connectivity Guide | Paceart XML Schema
1
2
Code
Country
Medications
This block is rooted at /Paceart/LookupTables/Medications/MedicationDetail/ in the XML file.
TypeParameter XPathParameter
string[50]@addrLine1Insurance Company Address Line
string[50]@addrLine2Insurance Company Address Line
string[20]@addrCityInsurance Company Address City
string[10]@addrStateInsurance Company Address State
string[10]@addrZipcodeInsuranceCompany Address Postal
string[50]@addrCountryInsurance Company Address
string[20]@addrPhoneNumberInsurance Company Phone Number
string[20]@addrFaxNumberInsurance Company Fax Number
TypeParameter XPathParameter
string[50]@GUIDN/A
string[40]@NameMedication Name
string[100]@CommentaryMedication Comments
string[50]@SideEffect1Medication Side Effect[1]
string[50]@SideEffect2Medication Side Effect[2]
string[50]@SideEffect3Medication Side Effect[3]
string[50]@SideEffect4Medication Side Effect[4]
string[50]@SideEffect5Medication Side Effect[5]
string[50]@SideEffect6Medication Side Effect[6]
PagerServices
This block is rooted at /Paceart/LookupTables/PagerServices/PagerServiceDetail/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@ServiceNamePager Service Name
string[20]@PhoneNumberPager Service Phone
short@MessageLengthPager Maximum Message Length
byte@MessageFormatPager Message Format
string[255]@CommentaryPager Comments
Connectivity Guide | Paceart XML Schema | 69

Patient records

PatientRecord detail
This block is rooted at /Paceart/PatientRecords/PatientRecord/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
Demographics
This block is rooted at /Paceart/PatientRecords/PatientRecord/Demographics/ in the XML file.
TypeParameter XPathParameter
string[50]ReferringDoctors/ReferringDoctor1/DoctorReference/@GUIDPatient Provider[1]
string[50]ReferringDoctors/ReferringDoctor2/DoctorReference/@GUIDPatient Provider[2]
string[50]ReferringDoctors/ReferringDoctor3/DoctorReference/@GUIDPatient Provider[3]
string[50]Diagnoses/Diagnosis1/DiagnosisReference/@GUIDPatient Diagnosis[1]
Holder Name[1]
Holder Employer[1]
Holder Social Security Number[1]
Holder Certificate Number[1]
Number[1]
Holder Name[2]
Holder Employer[2]
Holder Social Security Number[2]
string[50]Diagnoses/Diagnosis2/DiagnosisReference/@GUIDPatient Diagnosis[2]
string[50]Diagnoses/Diagnosis3/DiagnosisReference/@GUIDPatient Diagnosis[3]
string[25]InsuranceInformation/PrivateInsurance1/@NamePatient Insurance Policy
string[25]InsuranceInformation/PrivateInsurance1/@EmployerPatient Insurance Policy
string[11]InsuranceInformation/PrivateInsurance1/@SocialSecurityNumberPatient Insurance Policy
string[20]InsuranceInformation/PrivateInsurance1/@CertificateNumberPatient Insurance Policy
string[20]InsuranceInformation/PrivateInsurance1/@PolicyNumberPatient Insurance Policy
string[50]InsuranceInformation/PrivateInsurance1/InsuranceCompanyReference/@GUIDPatient Insurance Company[1]
string[25]InsuranceInformation/PrivateInsurance2/@NamePatient Insurance Policy
string[25]InsuranceInformation/PrivateInsurance2/@EmployerPatient Insurance Policy
string[11]InsuranceInformation/PrivateInsurance2/@SocialSecurityNumberPatient Insurance Policy
Holder Certificate Number[2]
Number[2]
string[20]InsuranceInformation/PrivateInsurance2/@CertificateNumberPatient Insurance Policy
string[20]InsuranceInformation/PrivateInsurance2/@PolicyNumberPatient Insurance Policy
string[50]InsuranceInformation/PrivateInsurance2/@GUIDPatient Insurance Company[2]
70 | Connectivity Guide | Paceart XML Schema
Date
Date
TypeParameter XPathParameter
string[12]InsuranceInformation/@MedicareNumberPatient Medicare Number
dateInsuranceInformation/@MedicareEnrollmentDatePatient Medicare Enrollment
string[14]InsuranceInformation/@MedicaidNumberPatient Medicaid Number
dateInsuranceInformation/@MedicaidEnrollmentDatePatient Medicaid Enrollment
string[5]InsuranceInformation/@BillingTypePatient Insurance Billing Type
string[32]@nameLastPatient Last Name
string[14]@nameFirstPatient First Name
string[1]@nameMiddlePatient Middle Initial
string[20]@nameDegreePatient Credential[pdc1]
string[5]@nameHonorificPatient Prefix
string[20]@PatientIDPatient Identifier
Service
string[50]@addrLine1Patient Address Line1
string[50]@addrLine2Patient Address Line2
string[20]@addrCityPatient Address City
string[10]@addrStatePatient Address State
string[10]@addrZipcodePatient Address Postal Code
string[50]@addrCountryPatient Address Country
string[20]@addrPhoneNumberPatient Phone Number 1
string[20]@addrFaxNumberPatient Phone Number 2
string[100]@addrEmailPatient Email Address
date@BirthDatePatient Birth Date
N/A@SexPatient Gender
string[6]@AffiliationPatient Affiliation Code
string[1]@StatusPatient Status
string[20]@CardioVoiceIDProvider CardioVoice Identifier
string@CommentaryPatient Comments
N/A@RemoteFollowUPServiceNamePatient Remote Follow-up
Prescriptions
This block is rooted at /Paceart/PatientRecords/PatientRecord/Prescriptions/.
TypeParameter XPathParameter
string[255]@AllergiesPatient Allergies
string[50]PharmacyDetail/@NamePatient Pharmacy Name
Number
Provider[0+]
Dispensed[0+]
Dispensed[0+]
For Use[0+]
Connectivity Guide | Paceart XML Schema | 71
TypeParameter XPathParameter
string[13]PharmacyDetail/@PhoneNumberPatient Pharmacy Phone
string[13]PharmacyDetail/@FaxNumberPatient Pharmacy Fax Number
string[50]Prescription[0+]/Medication/MedicationReference/@GUIDPatient Medication[0+]
string[50]Prescription[0+]/PrescribingDoctor/DoctorReference/@GUIDPatient Medication
string[50]Prescription[0+]/@GUIDN/A
datePrescription[0+]/@DateDispensedPatient Medication Date
shortPrescription[0+]/@NumberDispensedPatient Medication Teblets
shortPrescription[0+]/@NumberOfRefillsPatient Medication Refills[0+]
string[200]Prescription[0+]/@DirectionPatient Medication Directions
As Written[0+]
Discontinued Date[0+]
Discontinued Reason[0+][1]
Discontinued Reason[0+][2]
Discontinued Reason[0+][2]
Scheduling
This block is rooted at /Paceart/PatientRecords/PatientRecord/Scheduling/.
TypeParameter XPathParameter
shortTTMPreferences/@FrequencyAppointment TTM/Remote
Scheduling Preference Interval
byteTTMPreferences/@DayAppointment TTM/Remote
Scheduling Preference Day
booleanPrescription[0+]/@DAWPatient Medication Dispense
booleanPrescription[0+]/@StatusPatient Medication Status[0+]
booleanPrescription[0+]/@PrintPatient Medication Print[0+]
datePrescription[0+]/@DiscontinuedDatePatient Medication
string[50]Prescription[0+]/@DiscontinuedReason1Patient Medication
string[50]Prescription[0+]/@DiscontinuedReason2Patient Medication
string[50]Prescription[0+]/@DiscontinuedReason3Patient Medication
Scheduling Preference Week
Scheduling Preference Time
Preference Interval
byteTTMPreferences/@WeekAppointment TTM/Remote
timeTTMPreferences/@TimeAppointment TTM/Remote
shortClinicPreferences/@FrequencyAppointment Clinic Scheduling
72 | Connectivity Guide | Paceart XML Schema
Preference Day
Preference Week
Preference Time
Appointments
This block is rooted at
/Paceart/PatientRecords/PatientRecord/Scheduling/Appointments/<Appointment Type>/
in the XML file.
TypeParameter XPathParameter
byteClinicPreferences/@DayAppointment Clinic Scheduling
byteClinicPreferences/@WeekAppointment Clinic Scheduling
timeClinicPreferences/@TimeAppointment Clinic Scheduling
string[50]FollowUpDoctor/DoctorReference/@GUIDPatient Scheduling Provider
TypeParameter XPathParameter
string[50]@GUIDN/A
dateTime@DateAppointment Date and Time
boolean@CardioVoiceAppointment Created by
CardioVoice
string[50]@OperatorAppointment System Operator
string[75]@VisitIDAppointment Visit ID
string[255]@CommentaryAppointment Comments
N/A@RemoteFollowUpServiceNameAppointment Remote Follow-up
Service
N/A@AppointmentRemoteStatusAppointment Remote Status
string[200]@AppointmentRemoteStatusTextAppointment Remote Status Text
Note: Appointment Remote parameters apply to remote appointment types only.
Pacemaker
This block is rooted at /Paceart/PatientRecords/PatientRecord/Devices/Pacemaker/ in the XML file.
TypeParameter XPathParameter
string[50]PacemakerLookup/PacemakerReference/@GUIDPatient Device
string[50]ImplantInformation/Doctor1/DoctorReference/@GUIDPatient Device First Implanting
Provider
Implanting Provider
Diagnosis
string[50]ImplantInformation/Doctor2/DoctorReference/@GUIDPatient Device Second
string[50]ImplantInformation/Diagnosis/DiagnosisReference/@GUIDPatient Device Implant
DateImplantInformation/@DatePatient Device Implant Date
Location
Provider
Date
Connectivity Guide | Paceart XML Schema | 73
TypeParameter XPathParameter
string[50]ImplantInformation/@LocationPatient Device Implant
string[50]DeviceHistory/Abandon/Doctor/DoctorReference/@GUIDPatient Device Abandoned
DateDeviceHistory/Abandon/@DatePatient Device Abandoned
Patient Device Partially Explanted Provider
Explanted Date
Provider
ICD
This block is rooted at /Paceart/PatientRecords/PatientRecord/Devices/ICD/ in the XML file.
Patient Device First Implanting Provider
Patient Device Second Implanting Provider
@GUID
@GUID
@GUID
string[50]DeviceHistory/PartialExplant/Doctor/DoctorReference/
DateDeviceHistory/PartialExplant/@DatePatient Device Partially
string[50]DeviceHistory/Explant/Doctor/DoctorReference/@GUIDPatient Device Explanted
DateDeviceHistory/Explant/@DatePatient Device Explanted Date
string[50]@GUIDN/A
string[20]@SerialNumberPatient Device Serial Number
String@CommentaryPatient Device Comments
TypeParameter XPathParameter
string[50]ICDLookup/ ICDReference/ @GUIDPatient Device
string[50]ImplantInformation/ Doctor1/ DoctorReference/
string[50]ImplantInformation/ Doctor2/ DoctorReference/
Patient Device Implant Diagnosis
Patient Device Abandoned Provider
Patient Device Partially Explanted Provider
Date
Patient Device Explanted Provider
string[50]ImplantInformation/ Diagnosis/ DiagnosisReference/
@GUID
dateImplantInformation/ @DatePatient Device Implant Date
string[50]ImplantInformation/ @LocationPatient Device Implant Location
string[50]DeviceHistory/ Abandon/ Doctor/ DoctorReference/
@GUID
dateDeviceHistory/ Abandon/ @DatePatient Device Abandoned Date
string[50]DeviceHistory/ PartialExplant/ Doctor/
DoctorReference/ @GUID
dateDeviceHistory/ PartialExplant/ @DatePatient Device Partially Explanted
string[50]DeviceHistory/ Explant/ Doctor/ DoctorReference/
@GUID
dateDeviceHistory/ Explant/ @DatePatient Device Explanted Date
string[50]@GUIDN/A
74 | Connectivity Guide | Paceart XML Schema
Lead
This block is rooted at /Paceart/PatientRecords/PatientRecord/Devices/Lead/ in the XML file.
TypeParameter XPathParameter
string[20]@SerialNumberPatient Device Serial Number
string@CommentaryPatient Device Comments
N/A[Custom Fields]N/A
TypeParameter XPathParameter
string[50]LeadLookup/ LeadReference/ @GUIDPatient Device
Patient Device First Implanting Provider
Patient Device Second Implanting Provider
Patient Device Implant Diagnosis
Device Type
Patient Device Abandoned Provider
Patient Device Partially Explanted Provider
string[50]ImplantInformation/ Doctor1/ DoctorReference/
@GUID
string[50]ImplantInformation/ Doctor2/ DoctorReference/
@GUID
string[50]ImplantInformation/ Diagnosis/ DiagnosisReference/
@GUID
dateImplantInformation/ @DatePatient Device Implant Date
string[50]ImplantInformation/ @LocationPatient Device Implant Location
N/AImplantInformation/ @ChamberPatient Device Implant Chamber
string[50]ImplantInformation/ @AccessPatient Device Implant Access
N/AImplantInformation/ @ConnectPatient Device Implant Connected
booleanImplantInformation/ @PacingPatient Device Pacing
string[50]DeviceHistory/ Abandon/ Doctor/ DoctorReference/
@GUID
dateDeviceHistory/ Abandon/ @DatePatient Device Abandoned Date
string[50]DeviceHistory/ PartialExplant/ Doctor/
DoctorReference/ @GUID
DateDeviceHistory/ PartialExplant/ @DatePatient Device Partially Explanted
Date
Patient Device Explanted Provider
@GUID
Adapter
This block is rooted at /Paceart/PatientRecords/PatientRecord/Devices/Adapter/ in the XML file.
string[50]DeviceHistory/ Explant/ Doctor/ DoctorReference/
DateDeviceHistory/ Explant/ @DatePatient Device Explanted Date
string[50]@GUIDN/A
string[20]@SerialNumberPatient Device Serial Number
String@CommentaryPatient Device Comments
Connectivity Guide | Paceart XML Schema | 75
TypeParameter XPathParameter
string[50]AdapterLookup/ AdapterReference/ @GUIDPatient Device
Patient Device First Implanting Provider
Patient Device Second Implanting Provider
Patient Device Implant Diagnosis
Device Type
Patient Device Abandoned Provider
Patient Device Partially Explanted Provider
string[50]ImplantInformation/ Doctor1/ DoctorReference/
@GUID
string[50]ImplantInformation/ Doctor2/ DoctorReference/
@GUID
string[50]ImplantInformation/ Diagnosis/ DiagnosisReference/
@GUID
dateImplantInformation/ @DatePatient Device Implant Date
string[50]ImplantInformation/ @LocationPatient Device Implant Location
N/AImplantInformation/ @ChamberPatient Device Implant Chamber
string[50]ImplantInformation/ @AccessPatient Device Implant Access
N/AImplantInformation/ @ConnectPatient Device Implant Connected
booleanImplantInformation/ @PacingPatient Device Implant Pacing
string[50]DeviceHistory/ Abandon/ Doctor/ DoctorReference/
@GUID
dateDeviceHistory/ Abandon/ @DatePatient Device Abandoned Date
string[50]DeviceHistory/ PartialExplant/ Doctor/
DoctorReference/ @GUID
dateDeviceHistory/ PartialExplant/ @DatePatient Device Partially Explanted
Date
Patient Device Explanted Provider
@GUID
Transmitter
This block is rooted at /Paceart/PatientRecords/PatientRecord/Devices/Transmitter/ in the XML file.
Date
string[50]DeviceHistory/ Explant/ Doctor/ DoctorReference/
dateDeviceHistory/ Explant/ @DatePatient Device Explanted Date
string[50]@GUIDN/A
string[20]@SerialNumberPatient Device Serial Number
String@CommentaryPatient Device Comments
TypeParameter XPathParameter
string[50]TransmitterLookup/ TransmitterReference/ @GUIDPatient Device
string[50]@GUIDN/A
string[20]@SerialNumberPatient Device Serial Number
date@DateGivenPatient Device Transmitter Given
Due Date
date@DateDuePatient Device Transmitter Return
76 | Connectivity Guide | Paceart XML Schema
Returned Date
Tests
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/ in the XML file.
Service
TypeParameter XPathParameter
date@DateReturnedPatient Device Transmitter
TypeParameter XPathParameter
string[50]@GUIDN/A
dateTime@DateEncounter Date and Time
boolean@CardioVoiceEncounter Created By CardioVoice
string[50]@OperatorEncounter System Operator
string[75]@VisitIDEncounter Visit ID
string[255]@CommentaryEncounter Comments
N/A@RemoteFollowUpServiceNameEncounter Remote Follow-up
string[50]@RemoteFollowUpGUIDN/A
N/A@TransmissionTypeN/A
Note: Encounter Remote Follow-up Service and the last two N/A parameters apply to remote encounter types only.
Evaluation arrhythmia encounter types
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation in the XML file.
TypeParameter XPathParameter
string[50]Evaluation/ @GUIDN/A
string[78]Evaluation/ @LocationPatient Device Implant Location
string[78]Evaluation/ @ActivityEncounter Evaluated Activity
string[78]Evaluation/ @SymptomsEncounter Evaluated Symptoms
string[255]Evaluation/ @FindingsEncounter Evaluated Findings
floatEvaluation/ @measureRRIntervalMinEncounter Evaluated RR Interval
Minimum
floatEvaluation/ @measureRRIntervalMaxEncounter Evaluated RR Interval
Maximum
Minimum
Maximum
Minimum
floatEvaluation/ @measurePRIntervalMinEncounter Evaluated PR Interval
floatEvaluation/ @measurePRIntervalMaxEncounter Evaluated PR Interval
floatEvaluation/ @measureQRSIntervalMinEncounter Evaluated QRS Interval
Connectivity Guide | Paceart XML Schema | 77
TypeParameter XPathParameter
floatEvaluation/ @measureQRSIntervalMaxEncounter Evaluated QRS Interval
Maximum
floatEvaluation/ @measureQTIntervalMinEncounter Evaluated QT Interval
Minimum
floatEvaluation/ @measureQTIntervalMaxEncounter Evaluated QT Interval
Maximum
stringEvaluation/ @CommentaryEncounter Evaluated Miscellaneous
Comments
Evaluation non-arrhythmia encounter types
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation in the XML file.
TypeParameter XPathParameter
floatEvaluation/ @DemandIntervalEncounter Evaluated Demand
Interval
AV Delay Interval
Interval
AV Delay Interval
Duration
Ventricular Duration
Capture
Sensing
Ventricular Capture
Ventricular Sensing
floatEvaluation/ @DemandAVDelayExternal Measured Demand Mode
floatEvaluation/ @MagnetIntervalEncounter Evaluated Magnet
floatEvaluation/ @MagnetAVDelayExternal Measured Magnet Mode
floatEvaluation/ @MagnetADurationEncounter Evaluated Magnet Atrial
floatEvaluation/ @MagnetVDurationEncounter Evaluated Magnet
stringEvaluation/ @AtrialCaptureExternal Evaluated Right Atrial
stringEvaluation/ @AtrialSensingExternal Evaluated Right Atrial
stringEvaluation/ @VentricularCaptureExternal Evaluated Right
stringEvaluation/ @VentricularSensingExternal Evaluated Right
string[7]Evaluation/ @BloodPressureExternal Measured Blood Pressure
Comments
Note: Not all values are populated for all encounter types.
string[75]Evaluation/ @RhythmBradycardia Evaluated Rhythm
string[75]Evaluation/ @SymptomsEncounter Evaluated Symptoms
string[50]Evaluation/ @DescriptionEncounter Description
stringEvaluation/ @CommentaryEncounter Evaluated Miscellaneous
78 | Connectivity Guide | Paceart XML Schema
BradyProgramming
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/BradyProgramming in the XML file.
TypeParameter XPathParameter
Device Programmed Left Ventricular Sensing Amplitude
Device Programmed Right Atrial Sensing Amplitude
Device Programmed Right Ventricular Sensing Amplitude
Device Programmed Left Ventricular Sensing Polarity
Device Programmed Right Atrial Sensing Polarity
Device Programmed Right Ventricular Sensing Polarity
Bradycardia Programmed Left Ventricular Refractory Period
Bradycardia Programmed Right Atrial Refractory Period
Bradycardia Programmed Right Ventricular Refractory Period
Bradycardia Programmed Left Ventricular Blanking Period
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="LV"]/ @Amplitude_millivolts
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="RA"]/ @Amplitude_millivolts
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="RV"]/ @Amplitude_millivolts
N/AEvaluation/ BradyProgramming/
Sensing[@Chamber="LV"]/ @Polarity
N/AEvaluation/ BradyProgramming/
Sensing[@Chamber="RA"]/ @Polarity
N/AEvaluation/ BradyProgramming/
Sensing[@Chamber="RV"]/ @Polarity
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="LV"]/ @RefractoryPeriod_ms
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="RA"]/ @RefractoryPeriod_ms
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="RV"]/ @RefractoryPeriod_ms
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="LV"]/ @BlankingPeriod_ms
Bradycardia Programmed Right Atrial Blanking Period
Bradycardia Programmed Right Ventricular Blanking Period
N/A
N/A
N/A
Bradycardia Programmed Left Ventricular Pacing Amplitude
Bradycardia Programmed Right Atrial Pacing Amplitude
Bradycardia Programmed Right Ventricular Pacing Amplitude
Bradycardia Programmed Left Ventricular Pacing Pulse Width
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="RA"]/ @BlankingPeriod_ms
string[5]Evaluation/ BradyProgramming/
Sensing[@Chamber="RV"]/ @BlankingPeriod_ms
N/AEvaluation/ BradyProgramming/
Sensing[@Chamber="LV"]/ @BlankingPeriodType
N/AEvaluation/ BradyProgramming/
Sensing[@Chamber="RA"]/ @BlankingPeriodType
N/AEvaluation/ BradyProgramming/
Sensing[@Chamber="RV"]/ @BlankingPeriodType
string[5]Evaluation/ BradyProgramming/
Pacing[@Chamber="LV"]/ @Amplitude_volts
string[5]Evaluation/ BradyProgramming/
Pacing[@Chamber="RA"]/ @Amplitude_volts
string[5]Evaluation/ BradyProgramming/
Pacing[@Chamber="RV"]/ @Amplitude_volts
string[5]Evaluation/ BradyProgramming/
Pacing[@Chamber="LV"]/ @PulseWidth_ms
Connectivity Guide | Paceart XML Schema | 79
TypeParameter XPathParameter
Bradycardia Programmed Right Atrial Pacing Pulse Width
Bradycardia Programmed Right Ventricular Pacing Pulse Width
Device Programmed Left Ventricular Pacing Polarity
Device Programmed Right Atrial Pacing Polarity
Device Programmed Right Ventricular Pacing Polarity
Bradycardia Programmed Sensor Threshold
Bradycardia Programmed Sensor Slope
Bradycardia Programmed Sensor Acceleration Reaction
Bradycardia Programmed Sensor Deceleration Recovery
Bradycardia Programmed Activities Of Daily Living Rate
string[5]Evaluation/ BradyProgramming/
Pacing[@Chamber="RA"]/ @PulseWidth_ms
string[5]Evaluation/ BradyProgramming/
Pacing[@Chamber="RV"]/ @PulseWidth_ms
N/AEvaluation/ BradyProgramming/
Pacing[@Chamber="LV"]/ @Polarity
N/AEvaluation/ BradyProgramming/
Pacing[@Chamber="RA"]/ @Polarity
N/AEvaluation/ BradyProgramming/
Pacing[@Chamber="RV"]/ @Polarity
string[15]Evaluation/ BradyProgramming/ RateModulation/
@Threshold
string[15]Evaluation/ BradyProgramming/ RateModulation/
@Slope
string[15]Evaluation/ BradyProgramming/ RateModulation/
@Acceleration_Reaction
string[15]Evaluation/ BradyProgramming/ RateModulation/
@Deceleration_Recovery
string[5]Evaluation/ BradyProgramming/ RateModulation/
@ADLRate_bpm
Sensed
Paced
Bradycardia Programmed AV Delay Rate Adaptive Status
Bradycardia Programmed AV Delay Lower Rate
Bradycardia Programmed AV Delay Upper Rate
Bradycardia Programmed AV Delay Rate Adaptive Sensed Minimum Interval
Bradycardia Programmed AV Delay Rate Adapative Paced Minimum Interval
Heart Failure Programmed VV Delay Paced
Automatic Mode Switch Detection Criteria Rate
string[5]Evaluation/BradyProgramming/ AVDelay/ @Sensed_msBradycardia Programmed AVDelay
string[5]Evaluation/ BradyProgramming/ AVDelay/ @Paced_msBradycardia Programmed AV Delay
string[8]Evaluation/ BradyProgramming/ AVDelay/
@AdaptiveAVDelayStatus
string[8]Evaluation/ BradyProgramming/ AVDelay/
@AdaptiveRateMinimum_bpm
string[8]Evaluation/ BradyProgramming/ AVDelay/
@AdaptiveRateMaximum_bpm
string[8]Evaluation/ BradyProgramming/ AVDelay/
@AdaptiveSensedMinimum_ms
string[8]Evaluation/ BradyProgramming/ AVDelay/
@AdaptivePacedMinimum_ms
string[8]Evaluation/ BradyProgramming/ AVDelay/
@VVDelay_ms
string[5]Evaluation/ BradyProgramming/ AMS/ @Rate_bpmBradycardia Programmed
80 | Connectivity Guide | Paceart XML Schema
Automatic Mode Switch Detection Criteria Duration
TypeParameter XPathParameter
string[10]Evaluation/ BradyProgramming/ AMS/ @Duration_msBradycardia Programmed
Bradycardia Programmed Automatic Mode Switch Therapy Fallback Rate
Mode
Rate
Maximum Tracking Rate
Maximum Sensor Rate
Hysteresis Rate
Rate
Pacemaker Mediated Tachycardia Termination Algorithm
string[5]Evaluation/ BradyProgramming/ AMS/
@FallbackRate_bpm
string[50]Evaluation/ BradyProgramming/ @GUIDN/A
string[5]Evaluation/ BradyProgramming/ @PacingModeBradycardia Programmed Pacing
string[5]Evaluation/ BradyProgramming/ @LowerRate_bpmBradycardia Programmed Lower
string[5]Evaluation/ BradyProgramming/ @TrackingRate_bpmBradycardia Programmed
string[5]Evaluation/BradyProgramming/ @MaxSensorRate_bpmBradycardia Programmed
string[10]Evaluation/BradyProgramming/ @HysteresisRate_bpmBradycardia Programmed
string[5]Evaluation/ BradyProgramming/ @SleepRate_bpmBradycardia Programmed Sleep
string[20]Evaluation/ BradyProgramming/ @PMTInterventionBradycardia Programmed
string[20]Evaluation/ BradyProgramming/ @PVCInterventionBradycardia Programmed Post-Ventricular Contraction Response
string[10]Evaluation/ BradyProgramming/ @DependencyBradycardia Evaluated Pacemaker Dependency
string[50]Evaluation/ BradyProgramming/ @NotesBradycardia Programmed Configuration Comments
PacemakerTelemetry
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/PacemakerTelemetry in the XML file.
TypeParameter XPathParameter
Device Measured Left Ventricular Lead Impedance Bipolar
Device Measured Right Atrial Lead Impedance Bipolar
Device Measured Right Ventricular Lead Impedance Bipolar
Device Measured Left Ventricular Lead Impedance Unipolar
Lead[@Chamber="LV"]/ @BipolarImpedance_ohms
Lead[@Chamber="RA"]/ @BipolarImpedance_ohms
Lead[@Chamber="RV"]/ @BipolarImpedance_ohms
Lead[@Chamber="LV"]/ @UnipolarImpedance_ohms
string[15]Evaluation/ PacemakerTelemetry/
string[15]Evaluation/ PacemakerTelemetry/
string[15]Evaluation/ PacemakerTelemetry/
string[15]Evaluation/ PacemakerTelemetry/
Connectivity Guide | Paceart XML Schema | 81
TypeParameter XPathParameter
Device Measured Right Atrial Lead Impedance Unipolar
Device Measured Right Ventricular Lead Impedance Unipolar
Device Measured Left Ventricular Lead Evoked Response
Device Measured Right Atrial Lead Evoked Response
Device Measured Right Ventricular Lead Evoked Response
Device Measured Left Ventricular Lead Polarization
Device Measured Right Atrial Lead Polarization
Device Measured Right Ventricular Lead Polarization
Percent Pacing
Bradycardia Measured Right Ventricular Percent Pacing
string[15]Evaluation/ PacemakerTelemetry/
Lead[@Chamber="RA"]/ @UnipolarImpedance_ohms
string[15]Evaluation/ PacemakerTelemetry/
Lead[@Chamber="RV"]/ @UnipolarImpedance_ohms
string[7]Evaluation/ PacemakerTelemetry/
Lead[@Chamber="LV"]/ @EvokedResponse
string[7]Evaluation/ PacemakerTelemetry/
Lead[@Chamber="RA"]/ @EvokedResponse
string[7]Evaluation/ PacemakerTelemetry/
Lead[@Chamber="RV"]/ @EvokedResponse
string[7]Evaluation/ PacemakerTelemetry/
Lead[@Chamber="LV"]/ @Polarization
string[7]Evaluation/ PacemakerTelemetry/
Lead[@Chamber="RA"]/ @Polarization
string[7]Evaluation/ PacemakerTelemetry/
Lead[@Chamber="RV"]/ @Polarization
string[10]Evaluation/ PacemakerTelemetry/ @PercentPacingAtrialBradycardia Measured Right Atrial
string[10]Evaluation/ PacemakerTelemetry/
@PercentPacingVentricular
string[7]Evaluation/PacemakerTelemetry/ @BatteryVoltage_voltsDevice Measured Battery Voltage
Device Measured Battery Impedance
Thresholds
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/Thresholds in the XML file.
Bradycardia Test Programmed Left Ventricular Sensing Threshold Amplitude Bipolar [0+]
Bradycardia Test Programmed Left Ventricular Sensing Threshold Amplitude Unipolar [0+]
Bradycardia Test Programmed Right Atrial Sensing Threshold Amplitude Bipolar [0+]
Bradycardia Test Programmed Right Atrial Sensing Threshold Amplitude Unipolar [0+]
@BatteryImpedance_ohms
Sensing[@Chamber="LV"][@Polarity="Bipolar"]/ @Amplitude_millivolts [0+]
Sensing[@Chamber="LV"][@Polarity="Unipolar"]/ @Amplitude_millivolts [0+]
Sensing[@Chamber="RA"][@Polarity="Bipolar"]/ @Amplitude_millivolts [0+]
Sensing[@Chamber="RA"][@Polarity="Unipolar"]/ @Amplitude_millivolts [0+]
string[7]Evaluation/ PacemakerTelemetry/
TypeParameter XPathParameter
string[5]Evaluation/ Thresholds/
string[5]Evaluation/ Thresholds/
string[5]Evaluation/ Thresholds/
string[5]Evaluation/ Thresholds/
Bradycardia Test Programmed Right Ventricular Sensing Threshold Amplitude Bipolar [0+]
string[5]Evaluation/ Thresholds/ Sensing[@Chamber="RV"][@Polarity="Bipolar"]/ @Amplitude_millivolts [0+]
82 | Connectivity Guide | Paceart XML Schema
TypeParameter XPathParameter
Bradycardia Test Programmed Right Ventricular Sensing Threshold Amplitude Unipolar [0+]
Bradycardia Test Programmed Left Ventricular Sensing Threshold Measurement Type Bipolar[0+]
Bradycardia Test Programmed Left Ventricular Sensing Threshold Measurement Type Unipolar[0+]
Bradycardia Test Programmed Right Atrial Sensing Threshold Measurement Type Bipolar[0+]
Bradycardia Test Programmed Right Atrial Sensing Threshold Measurement Type Unipolar[0+]
Bradycardia Test Programmed Right Ventricular Sensing Threshold Measurement Type Bipolar[0+]
Bradycardia Test Programmed Right Ventricular Sensing Threshold Measurement Type Unipolar[0+]
string[5]Evaluation/ Thresholds/ Sensing[@Chamber="RV"][@Polarity="Unipolar"]/ @Amplitude_millivolts [0+]
N/AEvaluation/Thresholds/ Sensing[@Chamber="LV"][@Polarity="Bipolar"]/@Type [0+]
N/AEvaluation/Thresholds/ Sensing[@Chamber="LV"][@Polarity="Unipolar"]/@Type [0+]
N/AEvaluation/Thresholds/ Sensing[@Chamber="RA"][@Polarity="Bipolar"]/@Type [0+]
N/AEvaluation/Thresholds/ Sensing[@Chamber="RA"][@Polarity="Unipolar"]/@Type [0+]
N/AEvaluation/Thresholds/ Sensing[@Chamber="RV"][@Polarity="Bipolar"]/@Type [0+]
N/AEvaluation/Thresholds/ Sensing[@Chamber="RV"][@Polarity="Unipolar"]/@Type [0+]
External Evaluated Left Ventricular Sensing Threshold Graph Bipolar [0+]
External Evaluated Left Ventricular Sensing Threshold Graph Unipolar [0+]
External Evaluated Right Atrial Sensing Threshold Graph Bipolar [0+]
External Evaluated Right Atrial Sensing Threshold Graph Unipolar [0+]
External Evaluated Right Ventricular Sensing Threshold Graph Bipolar [0+]
External Evaluated Right Ventricular Sensing Threshold Graph Unipolar [0+]
Bradycardia Test Programmed Left Ventricular Capture Threshold Amplitude[0+]
booleanEvaluation/ Thresholds/ Sensing[@Chamber="LV"][@Polarity="Bipolar"]/ @UseForGraphing [0+]
booleanEvaluation/ Thresholds/ Sensing[@Chamber="LV"][@Polarity="Unipolar"]/ @UseForGraphing [0+]
booleanEvaluation/ Thresholds/ Sensing[@Chamber="RA"][@Polarity="Bipolar"]/ @UseForGraphing [0+]
booleanEvaluation/ Thresholds/ Sensing[@Chamber="RA"][@Polarity="Unipolar"]/ @UseForGraphing [0+]
booleanEvaluation/ Thresholds/ Sensing[@Chamber="RV"][@Polarity="Bipolar"]/ @UseForGraphing [0+]
booleanEvaluation/ Thresholds/ Sensing[@Chamber="RV"][@Polarity="Unipolar"]/ @UseForGraphing [0+]
string[50]Evaluation/ Thresholds/ Capture/ @GUIDN/A
string[5]Evaluation/ Thresholds/ Capture[@Chamber="LV"]/ @Amplitude_volts[0+]
Connectivity Guide | Paceart XML Schema | 83
TypeParameter XPathParameter
Bradycardia Test Programmed Right Atrial Capture Threshold Amplitude[0+]
Bradycardia Test Programmed Right Ventricular Capture Threshold Amplitude[0+]
Bradycardia Test Programmed Left Ventricular Capture Threshold Duration[0+]
Bradycardia Test Programmed Right Atrial Capture Threshold Duration[0+]
Bradycardia Test Programmed Right Ventricular Capture Threshold Duration[0+]
Bradycardia Test Programmed Left Ventricular Capture Threshold Measurement Type [0+]
Bradycardia Test Programmed Right Atrial Capture Threshold Measurement Type [0+]
string[5]Evaluation/ Thresholds/ Capture[@Chamber="RA"]/ @Amplitude_volts[0+]
string[5]Evaluation/ Thresholds/ Capture[@Chamber="RV"]/ @Amplitude_volts[0+]
floatEvaluation/ Thresholds/ Capture[@Chamber="LV"]/ @Duration_ms[0+]
floatEvaluation/ Thresholds/ Capture[@Chamber="RA"]/ @Duration_ms[0+]
floatEvaluation/ Thresholds/ Capture[@Chamber="RV"]/ @Duration_ms[0+]
N/AEvaluation/Thresholds/Capture[@Chamber="LV"]/ @Type[0+]
N/AEvaluation/Thresholds/Capture[@Chamber="RA"]/ @Type[0+]
Bradycardia Test Programmed Right Ventricular Capture Threshold Measurement Type [0+]
Bradycardia Test Programmed Left Ventricular Capture Threshold Polarity[0+]
Bradycardia Test Programmed Right Ventricular Capture Threshold Polarity[0+]
Bradycardia Test Programmed Right Atrial Capture Threshold Polarity[0+]
External Evaluated Left Ventricular Capture Threshold Graph[0+]
External Evaluated Right Ventricular Capture Threshold Graph[0+]
External Evaluated Left Ventricular Capture Threshold Graph[0+]
TachyProgramming
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/ in the XML file.
@Type[0+]
@Polarity[0+]
@Polarity[0+]
@Polarity[0+]
@UseForGraphing[0+]
@UseForGraphing[0+]
@UseForGraphing[0+]
N/AEvaluation/Thresholds/Capture[@Chamber="RV"]/
N/AEvaluation/ Thresholds/ Capture[@Chamber="LV"]/
N/AEvaluation/ Thresholds/ Capture[@Chamber="RV"]/
N/AEvaluation/ Thresholds/ Capture[@Chamber="RA"]/
booleanEvaluation/ Thresholds/ Capture[@Chamber="LV"]/
booleanEvaluation/ Thresholds/ Capture[@Chamber="RV"]/
booleanEvaluation/ Thresholds/ Capture[@Chamber="RA"]/
84 | Connectivity Guide | Paceart XML Schema
Ventricular Detection Configuration Summary
Detection Configuration Summary
Ventricular Therapy Configuration Summary
Therapy Configuration Summary
Comments
Ventricular Fibrillation Zone - zone detection
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/VFZone/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string[50]@DetectionStatusVentricularTachycardia Programmed Zone
string[50]@DetectionStatusAtrialTachycardia Programmed Zone Atrial
string[25]@TherapyStatusVentricularTachycardia Programmed Zone
string[25]@TherapyStatusAtrialTachycardia Programmed Zone Atrial
string@CommentaryTachycardia Programmed Configuration
Ventricular Fibrillation Configuration Comments
Ventricular Fibrillation Detection Committed
Ventricular Fibrillation Detection Criteria Duration
Ventricular Fibrillation Detection Criteria Rate
Ventricular Fibrillation Redetection Criteria Duration
Ventricular Fibrillation Therapy Configuration Summary
TypeParameter XPathParameter
string[50]@GUIDN/A
string@CommentaryTachycardia Programmed Zone
boolean@CommittedTachycardia Programmed Zone
string[25]@DetectionDurationTachycardia Programmed Zone
string[10]@DetectionInterval_msTachycardia Programmed Zone
string[25]@RedetectionDurationTachycardia Programmed Zone
string[25]@TherapyConfigurationTachycardia Programmed Zone
Ventricular Fibrillation Zone - shock therapies
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/VFZone/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
Ventricular Fibrillation Therapy Order Number [1-15]
Connectivity Guide | Paceart XML Schema | 85
TypeParameter XPathParameter
byteShockTherapy/ @TherapyNumberTachycardia Programmed Zone
Tachycardia Programmed Zone Ventricular Fibrillation Therapy Shock Cardioversion Delay [1-15]
Ventricular Fibrillation Therapy Shock Pathway [1-15]
Tachycardia Programmed Zone Ventricular Fibrillation Therapy Shock Pulse Width Negative [1-15]
Tachycardia Programmed Zone Ventricular Fibrillation Therapy Shock Pulse Width Positive [1-15]
N/A
Tachycardia Programmed Zone Ventricular Fibrillation Therapy Shock Energy [1-15] ShockTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Ventricular Fibrillation Therapy Shock Energy Volts [1-15] ShockTherapy[@TherapyNumber="[1-15]"]/
@CardioversionDelay_ms
@PulseWidthNegative_ms
@PulseWidthPositive_ms
@ShockActivationType
@ShockEnergy
@ShockEnergyUnits
@ShockEnergy
@ShockEnergyUnits
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
booleanShockTherapy[@TherapyNumber="[1-15]"]/ @CommittedN/A
N/AShockTherapy[@TherapyNumber="[1-15]"]/ @PathwayTachycardia Programmed Zone
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
booleanShockTherapy[@TherapyNumber="[1-15]"]/ @StatusTachycardia Programmed Zone Ventricular Fibrillation Therapy Status [1-15]
string[20]ShockTherapy[@TherapyNumber="[1-15]"]/ @WaveformTachycardia Programmed Zone Ventricular Fibrillation Therapy Shock Waveform [1-15]
Atrial Fibrillation Zone - zone detection
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="AFib"]/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string@CommentaryTachycardia Programmed Zone Atrial
Fibrillation Configuration Comments
string[25]@DetectionDurationTachycardia Programmed Zone Atrial
Fibrillation Detection Criteria Duration
string[10]@DetectionInterval_msTachycardia Programmed Zone Atrial
Fibrillation Detection Criteria Rate
86 | Connectivity Guide | Paceart XML Schema
Fibrillation Sustained High Rate Detection Criteria Duration
Fibrillation Sustained High Rate Detection Criteria Rate
Fibrillation Morphology Detection Criteria
Fibrillation Cardiac Cycle Stability Detection Criteria
Fibrillation Redetection Criteria Duration
TypeParameter XPathParameter
string[10]@EHR_SRDDuration_msTachycardia Programmed Zone Atrial
string[10]@EHR_SRDRate_bpmTachycardia Programmed Zone Atrial
string[25]@QRSMorphologyCriteriaTachycardia Programmed Zone Atrial
string[5]@RateStabilityCriteriaTachycardia Programmed Zone Atrial
string[25]@RedetectionDurationTachycardiaProgrammed Zone Atrial
Tachycardia Programmed Zone Atrial Fibrillation Sudden Onset Detection Criteria Interval
Tachycardia Programmed Zone Atrial Fibrillation Sudden Onset Detection Criteria Interval Percentage
Fibrillation Therapy Configuration Summary
Atrial Fibrillation Zone - ATP therapies
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="AFib"]/ in the XML file.
Atrial Fibrillation Therapy Order Number [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Initial Burst Cycle Length [1-15]
@SuddenOnsetCriteriaUnits
@SuddenOnsetCriteriaUnits
@BurstCycleLength ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLengthUnits
string[5]@SuddenOnsetCriteria
string[5]@SuddenOnsetCriteria
string[25]@TherapyConfigurationTachycardia Programmed Zone Atrial
N/A@ZoneTypeTachycardia Programmed Zone Type
TypeParameter XPathParameter
string[50]@GUIDN/A
byteATPTherapy/ @TherapyNumberTachycardia Programmed Zone
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Initial Burst Cycle Length Percentage [1-15]
N/A
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLength ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLengthUnits
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @Committed
Connectivity Guide | Paceart XML Schema | 87
TypeParameter XPathParameter
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Coupling Interval [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Coupling Interval Percentage [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Coupling Interval Decrement [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Coupling Interval Decrement Percentage [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Burst Interval Decrement [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Maximum Stimulus Count [1-15]
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingInterval ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingInterval ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrement ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrementUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrement ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrementUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @IntervalDecrement_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @MaximumNumberOfPulses
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Minimum Burst Cycle Length [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Burst Count [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Stimulus Amplitude [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Stimulus Duration [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Stimulus Count Increment [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @MinimumBurstCycleLength_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @NumberOfSequences
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @OutputAmplitude_volts
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @OutputDuration_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @PulseIncrement
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @RampDecrement_ms
88 | Connectivity Guide | Paceart XML Schema
Anti-Tachycardia Pacing Ramp Decrement [1-15]
TypeParameter XPathParameter
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing S1S2 Ramp [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing S2SN Ramp [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Scan Decrement [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Scan Sequence [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Smart Mode [1-15]
Atrial Fibrillation Therapy Status [1-15]
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @S1S2Ramp_percent
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @S2SNRamp_percent
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @ScanDecrement_ms
N/AATPTherapy[@TherapyNumber="[1-15]"]/ @Sequence
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @SmartMode
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @StatusTachycardia Programmed Zone
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Maximum Stimulus Count [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Anti-Tachycardia Pacing Type [1-15]
Atrial Fibrillation Zone - shock therapies
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="AFib"]/ in the XML file.
Atrial Fibrillation Therapy Order Number [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Shock Cardioversion Delay [1-15]
@StimuliCount
@TherapyType
@CardioversionDelay_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/
N/AATPTherapy[@TherapyNumber="[1-15]"]/
TypeParameter XPathParameter
string[50]@GUIDN/A
byteShockTherapy/ @TherapyNumberTachycardia Programmed Zone
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
Connectivity Guide | Paceart XML Schema | 89
TypeParameter XPathParameter
N/A
@Committed
Tachycardia Programmed Zone Atrial Fibrillation Therapy Shock Pathway [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Shock Pulse Width Negative [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Shock Pulse Width Positive [1-15]
N/A
Tachycardia Programmed Zone Atrial Fibrillation Therapy Shock Energy [1-15] ShockTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Atrial Fibrillation Therapy Shock Energy Volts [1-15] ShockTherapy[@TherapyNumber="[1-15]"]/
@Pathway
@PulseWidthNegative_ms
@PulseWidthPositive_ms
@ShockActivationType
@ShockEnergy
@ShockEnergyUnits
@ShockEnergy
@ShockEnergyUnits
booleanShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Atrial Fibrillation Therapy Status [1-15]
Tachycardia Programmed Zone Atrial Fibrillation Therapy Shock Waveform [1-15]
Atrial Flutter Zone - zone detection
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="AFlutter"]/ in the XML file.
Flutter Configuration Comments
Flutter Detection Criteria Duration
Flutter Detection Criteria Rate
Flutter Sustained High Rate Detection Criteria Duration
@Status
@Waveform
booleanShockTherapy[@TherapyNumber="[1-15]"]/
string[20]ShockTherapy[@TherapyNumber="[1-15]"]/
TypeParameter XPathParameter
string[50]@GUIDN/A
string@CommentaryTachycardia Programmed Zone Atrial
string[25]@DetectionDurationTachycardia Programmed Zone Atrial
string[10]@DetectionInterval_msTachycardia Programmed Zone Atrial
string[10]@EHR_SRDDuration_msTachycardia Programmed Zone Atrial
90 | Connectivity Guide | Paceart XML Schema
Flutter Sustained High Rate Detection Criteria Rate
Flutter Morphology Detection Criteria
Flutter Cardiac Cycle Stability Detection Criteria
Flutter Redetection Criteria Duration
TypeParameter XPathParameter
string[10]@EHR_SRDRate_bpmTachycardia Programmed Zone Atrial
string[25]@QRSMorphologyCriteriaTachycardia Programmed Zone Atrial
string[5]@RateStabilityCriteriaTachycardia Programmed Zone Atrial
string[25]@RedetectionDurationTachycardia Programmed Zone Atrial
Tachycardia Programmed Zone Atrial Flutter Sudden Onset Detection Criteria Interval
Tachycardia Programmed Zone Atrial Flutter Sudden Onset Detection Criteria Interval Percentage
Flutter Therapy Configuration Summary
Atrial Flutter Zone - ATP therapies
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="AFlutter"]/ in the XML file.
Atrial Flutter Therapy Order Number [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Initial Burst Cycle Length [1-15]
@BurstCycleLength ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLengthUnits
@SuddenOnsetCriteriaUnits
@SuddenOnsetCriteriaUnits
string[5]@SuddenOnsetCriteria
string[5]@SuddenOnsetCriteria
string[25]@TherapyConfigurationTachycardia Programmed Zone Atrial
N/A@ZoneTypeTachycardia Programmed Zone Type
TypeParameter XPathParameter
string[50]@GUIDN/A
byteATPTherapy/ @TherapyNumberTachycardia Programmed Zone
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Initial Burst Cycle Length Percentage [1-15]
N/A
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Coupling Interval [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLength ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLengthUnits
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @Committed
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingInterval ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingInterval
Connectivity Guide | Paceart XML Schema | 91
TypeParameter XPathParameter
Anti-Tachycardia Pacing Coupling Interval Percentage [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Coupling Interval Decrement [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Coupling Interval Decrement Percentage [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Burst Interval Decrement [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Maximum Stimulus Count [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Minimum Burst Cycle Length [1-15]
ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrement ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrementUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrement ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrementUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @IntervalDecrement_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @MaximumNumberOfPulses
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @MinimumBurstCycleLength_ms
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Burst Count [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Stimulus Amplitude [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Stimulus Duration [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Stimulus Count Increment [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Ramp Decrement [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing S1S2 Ramp [1-15]
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @NumberOfSequences
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @OutputAmplitude_volts
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @OutputDuration_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @PulseIncrement
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @RampDecrement_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @S1S2Ramp_percent
92 | Connectivity Guide | Paceart XML Schema
TypeParameter XPathParameter
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing S2SN Ramp [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Scan Decrement [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Scan Sequence [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Smart Mode [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Status [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Maximum Stimulus Count [1-15]
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @S2SNRamp_percent
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @ScanDecrement_ms
N /AATPTherapy[@TherapyNumber="[1-15]"]/ @Sequence
booleanATPTherapy[@TherapyN umber="[1-15]"]/ @SmartMode
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @Status
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @StimuliCount
Tachycardia Programmed Zone Atrial Flutter Therapy Anti-Tachycardia Pacing Type [1-15]
Atrial Flutter Zone - shock therapies
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="AFlutter"]/ in the XML file.
Atrial Flutter Therapy Order Number [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Shock Cardioversion Delay [1-15]
N/A
Tachycardia Programmed Zone Atrial Flutter Therapy Shock Pathway [1-15]
@TherapyType
@CardioversionDelay_ms
@Committed
@Pathway
N/AATPTherapy[@TherapyNumber="[1-15]"]/
TypeParameter XPathParameter
string[50]@GUIDN/A
byteShockTherapy/ @TherapyNumberTachycardia Programmed Zone
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
booleanShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
Connectivity Guide | Paceart XML Schema | 93
TypeParameter XPathParameter
Tachycardia Programmed Zone Atrial Flutter Therapy Shock Pulse Width Negative [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Shock Pulse Width Positive [1-15]
N/A
Tachycardia Programmed Zone Atrial Flutter Therapy Shock Energy [1-15] ShockTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Atrial Flutter Therapy Shock Energy Volts [1-15] ShockTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Atrial Flutter Therapy Status [1-15]
Tachycardia Programmed Zone Atrial Flutter Therapy Shock Waveform [1-15]
@PulseWidthNegative_ms
@PulseWidthPositive_ms
@ShockActivationType
@ShockEnergy
@ShockEnergyUnits
@ShockEnergy
@ShockEnergyUnits
@Status
@Waveform
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
booleanShockTherapy[@TherapyNumber="[1-15]"]/
string[20]ShockTherapy[@TherapyNumber="[1-15]"]/
Atrial Tachycardia Zone - zone detection
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="ATach"]/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string@CommentaryTachycardia Programmed Zone Atrial Tachycardia Configuration Comments
string[25]@DetectionDurationTachycardia Programmed Zone Atrial Tachycardia Detection Criteria Duration
string[10]@DetectionInterval_msTachycardia Programmed Zone Atrial Tachycardia Detection Criteria Rate
string[10]@EHR_SRDDuration_msTachycardia Programmed Zone Atrial Tachycardia Sustained High Rate Detection Criteria Duration
string[10]@EHR_SRDRate_bpmTachycardia Programmed Zone Atrial Tachycardia Sustained High Rate Detection Criteria Rate
Atrial Tachycardia Morphology Detection Criteria
string[25]@QRSMorphologyCriteriaTachycardia Programmed Zone
94 | Connectivity Guide | Paceart XML Schema
Atrial Tachycardia Cardiac Cycle Stability Detection Criteria
Atrial Tachycardia Redetection Criteria Duration
TypeParameter XPathParameter
string[5]@RateStabilityCriteriaTachycardia Programmed Zone
string[25]@RedetectionDurationTachycardia Programmed Zone
Tachycardia Programmed Zone Atrial Tachycardia Sudden Onset Detection Criteria Interval
Tachycardia Programmed Zone Atrial Tachycardia Sudden Onset Detection Criteria Interval Percentage
Atrial Tachycardia Therapy Configuration Summary
Type
Atrial Tachycardia Zone - ATP therapies
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="ATach"]/ in the XML file.
Atrial Tachycardia Therapy Order Number [1-15]
@SuddenOnsetCriteriaUnits
@SuddenOnsetCriteriaUnits
string[5]@SuddenOnsetCriteria
string[5]@SuddenOnsetCriteria
string[25]@TherapyConfigurationTachycardia Programmed Zone
N/A@ZoneTypeTachycardia Programmed Zone
TypeParameter XPathParameter
string[50]@GUIDN/A
byteATPTherapy/ @TherapyNumberTachycardia Programmed Zone
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Initial Burst Cycle Length [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Initial Burst Cycle Length Percentage [1-15]
N/A
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Coupling Interval [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLength ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLengthUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLength ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLengthUnits
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @Committed
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingInterval ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingInterval
Connectivity Guide | Paceart XML Schema | 95
TypeParameter XPathParameter
Anti-Tachycardia Pacing Coupling Interval Percentage [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Coupling Interval Decrement [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Coupling Interval Decrement Percentage [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Burst Interval Decrement [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Maximum Stimulus Count [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Minimum Burst Cycle Length [1-15]
ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrement ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrementUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrement ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingIntervalDecrementUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @IntervalDecrement_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @MaximumNumberOfPulses
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @MinimumBurstCycleLength_ms
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Burst Count [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Stimulus Amplitude [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Stimulus Duration [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Stimulus Count Increment [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Ramp Decrement [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing S1S2 Ramp [1-15]
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @NumberOfSequences
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @OutputAmplitude_volts
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @OutputDuration_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @PulseIncrement
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @RampDecrement_ms
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @S1S2Ramp_percent
96 | Connectivity Guide | Paceart XML Schema
TypeParameter XPathParameter
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing S2SN Ramp [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Scan Decrement [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Scan Sequence [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Smart Mode [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Status [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Maximum Stimulus Count [1-15]
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @S2SNRamp_percent
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @ScanDecrement_ms
N/AATPTherapy[@TherapyNumber="[1-15]"]/ @Sequence
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @SmartMode
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @Status
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @StimuliCount
Tachycardia Programmed Zone Atrial Tachycardia Therapy Anti-Tachycardia Pacing Type [1-15]
Atrial Tachycardia Zone - shock therapies
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="ATach"]/ in the XML file.
Atrial Tachycardia Therapy Order Number [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Shock Cardioversion Delay [1-15]
N/A
Tachycardia Programmed Zone Atrial Tachycardia Therapy Shock Pathway [1-15]
@TherapyType
@CardioversionDelay_ms
@Committed
@Pathway
N/AATPTherapy[@TherapyNumber="[1-15]"]/
TypeParameter XPathParameter
string[50]@GUIDN/A
byteShockTherapy/ @TherapyNumberTachycardia Programmed Zone
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
booleanShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
Connectivity Guide | Paceart XML Schema | 97
TypeParameter XPathParameter
Tachycardia Programmed Zone Atrial Tachycardia Therapy Shock Pulse Width Negative [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Shock Pulse Width Positive [1-15]
N/A
Tachycardia Programmed Zone Atrial Tachycardia Therapy Shock Energy [1-15] ShockTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Atrial Tachycardia Therapy Shock Energy Volts [1-15] ShockTherapy[@TherapyNumber="[1-15]"]/
Tachycardia Programmed Zone Atrial Tachycardia Therapy Status [1-15]
Tachycardia Programmed Zone Atrial Tachycardia Therapy Shock Waveform [1-15]
@PulseWidthNegative_ms
@PulseWidthPositive_ms
@ShockActivationType
@ShockEnergy
@ShockEnergyUnits
@ShockEnergy
@ShockEnergyUnits
@Status
@Waveform
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
string[10]ShockTherapy[@TherapyNumber="[1-15]"]/
N/AShockTherapy[@TherapyNumber="[1-15]"]/
booleanShockTherapy[@TherapyNumber="[1-15]"]/
string[20]ShockTherapy[@TherapyNumber="[1-15]"]/
Fast Ventricular Tachycardia Zone - zone detection
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="FastVT"]/ in the XML file.
TypeParameter XPathParameter
string[50]@GUIDN/A
string@CommentaryTachycardia Programmed Zone
Fast Ventricular Tachycardia Configuration Comments
string[25]@DetectionDurationTachycardia Programmed Zone
Fast Ventricular Tachycardia Detection Criteria Duration
string[10]@DetectionInterval_msTachycardia Programmed Zone
Fast Ventricular Tachycardia Detection Criteria Rate
string[10]@EHR_SRDDuration_msTachycardia Programmed Zone
Fast Ventricular Tachycardia Sustained High Rate Detection Criteria Duration
string[10]@EHR_SRDRate_bpmTachycardia Programmed Zone
Fast Ventricular Tachycardia Sustained High Rate Detection Criteria Rate
98 | Connectivity Guide | Paceart XML Schema
Fast Ventricular Tachycardia Morphology Detection Criteria
Fast Ventricular Tachycardia Cardiac Cycle Stability Detection Criteria
Fast Ventricular Tachycardia Redetection Criteria Duration
TypeParameter XPathParameter
string[25]@QRSMorphologyCriteriaTachycardia Programmed Zone
string[5]@RateStabilityCriteriaTachycardia Programmed Zone
string[25]@RedetectionDurationTachycardia Programmed Zone
Tachycardia Programmed Zone Fast Ventricular Tachycardia Sudden Onset Detection Criteria Interval
Tachycardia Programmed Zone Fast Ventricular Tachycardia Sudden Onset Detection Criteria Interval Percentage
Fast Ventricular Tachycardia Therapy Configuration Summary
Type
Fast Ventricular Tachycardia Zone - ATP therapies
This block is rooted at /Paceart/PatientRecords/PatientRecord/Tests/<Encounter Type>/Evaluation/TachyProgramming/Zone[@ZoneType="FastVT"]/ in the XML file.
Fast Ventricular Tachycardia Therapy Order Number [1-15]
@SuddenOnsetCriteriaUnits
@SuddenOnsetCriteriaUnits
string[5]@SuddenOnsetCriteria
string[5]@SuddenOnsetCriteria
string[25]@TherapyConfigurationTachycardia Programmed Zone
N/A@ZoneTypeTachycardia Programmed Zone
TypeParameter XPathParameter
string[50]@GUIDN/A
byteATPTherapy/ @TherapyNumberTachycardia Programmed Zone
Tachycardia Programmed Zone Fast Ventricular Tachycardia Therapy Anti-Tachycardia Pacing Initial Burst Cycle Length [1-15]
Tachycardia Programmed Zone Fast Ventricular Tachycardia Therapy Anti-Tachycardia Pacing Initial Burst Cycle Length Percentage [1-15]
N/A
Tachycardia Programmed Zone Fast Ventricular Tachycardia
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLength ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLengthUnits
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLength ATPTherapy[@TherapyNumber="[1-15]"]/ @BurstCycleLengthUnits
booleanATPTherapy[@TherapyNumber="[1-15]"]/ @Committed
string[10]ATPTherapy[@TherapyNumber="[1-15]"]/ @CouplingInterval
Loading...