Global Siemens Healthcare Headquarters
Siemens AG
Healthcare Sector
Henkestrasse 127
91052 Erlangen
Germany
Phone: +49 9131 84-0
www.siemens.com/healthcare
Order No.: AXA5-200.640.07.01.02 | © 07.2011, Siemens AG
Legal Manufacturer
Siemens AG
Wittelsbacherplatz 2
DE-80333 Muenchen
Germany
System Administration
Global Siemens Headquarters
Siemens AG
Wittelsbacherplatz 2
80333 Muenchen
Germany
AXIOM Sensis XP
Global Business Unit
Siemens AG
Medical Solutions
Angiography & Interventional X-ray Systems
Siemensstr. 1
DE-91301 Forchheim
Germany
Phone: +49 9191 18-0
www.siemens.com/healthcare
AXIOM Sensis XP
System Administration
www.siemens.com/healthcare
Global Siemens Healthcare Headquarters
Siemens AG
Healthcare Sector
Henkestrasse 127
91052 Erlangen
Germany
Phone: +49 9131 84-0
www.siemens.com/healthcare
Order No.: AXA5-200.640.07.01.02 | © 07.2011, Siemens AG
Legal Manufacturer
Siemens AG
Wittelsbacherplatz 2
DE-80333 Muenchen
Germany
System Administration
Global Siemens Headquarters
Siemens AG
Wittelsbacherplatz 2
80333 Muenchen
Germany
AXIOM Sensis XP
Global Business Unit
Siemens AG
Medical Solutions
Angiography & Interventional X-ray Systems
Siemensstr. 1
DE-91301 Forchheim
Germany
Phone: +49 9191 18-0
www.siemens.com/healthcare
AXIOM Sensis XP
System Administration
www.siemens.com/healthcare
Global Siemens Healthcare Headquarters
Siemens AG
Healthcare Sector
Henkestrasse 127
91052 Erlangen
Germany
Phone: +49 9131 84-0
www.siemens.com/healthcare
Order No.: AXA5-200.640.07.01.02 | © 07.2011, Siemens AG
Legal Manufacturer
Siemens AG
Wittelsbacherplatz 2
DE-80333 Muenchen
Germany
System Administration
Global Siemens Headquarters
Siemens AG
Wittelsbacherplatz 2
80333 Muenchen
Germany
AXIOM Sensis XP
Global Business Unit
Siemens AG
Medical Solutions
Angiography & Interventional X-ray Systems
Siemensstr. 1
DE-91301 Forchheim
Germany
Phone: +49 9191 18-0
www.siemens.com/healthcare
AXIOM Sensis XP
System Administration
www.siemens.com/healthcare
Global Siemens Headquarters
Siemens AG
Wittelsbacherplatz 2
80333 Muenchen
Germany
Global Siemens Healthcare Headquarters
Siemens AG
Healthcare Sector
Henkestrasse 127
91052 Erlangen
Germany
Phone: +49 9131 84-0
www.siemens.com/healthcare
Order No.: AXA5-200.640.07.01.02 | © 07.2011, Siemens AG
System Administration
Legal Manufacturer
Siemens AG
Wittelsbacherplatz 2
DE-80333 Muenchen
Germany
AXIOM Sensis XP
AXIOM Sensis XP
Global Business Unit
Siemens AG
Medical Solutions
Angiography & Interventional X-ray Systems
Siemensstr. 1
DE-91301 Forchheim
Germany
Phone: +49 9191 18-0
www.siemens.com/healthcare
System Administration
www.siemens.com/healthcare
AXIOM Sensis XP
System Administration
www.siemens.com/healthcare
System Administration
Legend
 Prerequisites
 Instructions
 List items
 Cross reference
Caution/
Warning
Cause
Possible consequences
 Precautions or remedies
Usability
BEFORE USING THIS SYSTEM
This system should be used only by employees adequately trained in the use of
this equipment.
Before using this system, the operator should be thoroughly acquainted with the
instructions for use and safety recommendations provided in this manual.
Failure to follow the instructions for use and safety recommendations provided in
this manual can cause serious injury to the patient, to the operator or to other persons.
CE marking
This product is provided with a CE marking in accordance with the regulations
stated in Appendix II of the Directive 93/42/EEC of June 14th, 1993 concerning
medical devices. In accordance with Appendix IX of the Directive 93/42/EEC, this
device is assigned to class II b.
The CE marking applies only to medical devices which have been put on the market according to the above-mentioned EC Directive.
Unauthorized changes to this product invalidate this declaration.
Whenever the hardware necessary to run the software is supplied, the CE Mark is
provided in accordance with, if applicable, Electro Magnetic Compatibility Directive 2004/108/EC and / or Low-Voltage Directive 2006/95/EC.
Note: Until July 19th 2009 the reference for Electro Magnetic Compatibility Directive might also be the old version 89/336/EEC.
Original language
Version
2 / 456
This manual was originally written in English.
This manual applies to system/software version VC11 and higher.
AXA5-200.640.07.01.02
System Administration
Table of Contents
Part: System Administration
11
Chapter: General Administrator Information
11
Safety section in the Operator Manual
Additional information for system administrators
System administration overview
System and user documentation
Structure of the System Administration manual
Information about the software
Communication and connectivity
11
11
11
12
13
14
15
Chapter: Information System Concepts
17
AXIOM Sensis XP: acquisition system and information system overview
AXIOM Sensis XP Acquisition System
AXIOM Sensis XP Information System
Database overview
Acquisition and information system: preregistered and
registered patients
Statistics Manager and Inventory Manager
System databases and system administration tools
The AXIOM Sensis XP Information System central database
Static and customizable database tables (groups)
Organization of groups
Dictionaries (pick lists)
Clusters
The study type concept
The reporting concept
Reporting overview
Basic principle
Reports created by the Report Generator
Supplementary graphical reports
Report Composer and template definition
Contents definition: meta tags
Template formatting: Word functions
Configuration Manager and study type association
The communication and interface concept
Communication with Dräger Infinity patient monitors
Network communication overview
Data flow during an examination
Configuring the communication with Dräger Infinity
patient monitors
Communication with HIS/RIS or CIS systems
Data import
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
18
18
20
24
24
28
28
30
31
32
33
35
38
40
40
40
40
41
42
43
44
45
46
46
46
47
48
49
50
3 / 456
System Administration
Data and report file export
syngo Dynamics integration
syngo Dynamics-Sensis system cooperation
Configuration of syngo Dynamics-Sensis communication
Communication with material management systems
Data flow between AXIOM Sensis XP Information System and
material management system
HL7 messages used in the data exchange between the systems
Configuration of material management in the
AXIOM Sensis XP Information System
The security system
Security system overview
User management: key terms and concepts
User accounts
Directories
Permissions
User groups
Roles
Use cases
Overview of the workflow in user management definition
Auditing
Backup and restore
AXIOM Sensis XP Acquisition System: archiving studies
AXIOM Sensis XP Information System: database backup
Planning a backup strategy for the information system
Chapter: Database Manager
AXA5-200.640.07.01.02
57
59
60
61
62
62
63
63
64
64
65
65
66
67
67
67
68
70
73
DB Manager overview
Overview of functions
Key terms and concepts
User interface and basic procedures
Starting DB Manager
Customizing the database
Editing dictionaries
Editing a dictionary definition file
Restoring the last version of a dictionary definition file
Creating a new dictionary
Further options for dictionary processing: Print, Cath, Delete,
Mark_all
Overview of dictionary definition files
Syntax for dictionary definition files (*.udi files)
Editing or adding customizable groups
Adding groups or fields and redefining field parameters
4 / 456
53
56
56
56
57
73
73
74
74
76
78
78
79
82
83
85
86
90
97
99
System Administration
Table of Contents
Renaming field names in group definitions
Restoring the last saved version of rep.grp
Printing group definition files
Syntax for the group definition file (rep.grp)
Editing clusters
Defining or redefining clusters
Restoring the last saved version of cathcor.clu
Printing the cluster definition file
Syntax for the cluster definition file (cathcor.clu)
Recompiling the database
Consistency check
Database maintenance
Using utilities
Service functions
Upgrading the database
Indexes
Procedures
Database reset
Chapter: Security Manager
Security Manager overview
Overview of functions
Key terms and concepts
Basic procedures
Starting Security Manager
User management
Granting access to patient data
Checking existing directories
Creating, editing, or deleting directories
Granting permission to access patient data in directories
Setting up user groups
Granting access to program functions
Defining, editing, or deleting roles
List of available use cases
Managing user accounts
Auditing
Defining what to audit
Querying the audit log
Exporting and archiving audit log data
Checking logged-on users
Changing the administrator password
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
100
101
101
102
106
108
110
111
111
120
121
123
123
125
125
126
126
126
129
129
129
130
130
131
131
132
132
133
135
136
139
139
142
145
148
148
149
150
152
153
5 / 456
System Administration
Chapter: Report Composer
155
Report Composer overview
Overview of functions
Key terms and concepts
User interface and basic procedures
Starting Report Composer
Opening a template from the database
Changing formal template aspects
Adding, moving, or removing tags
Adding tags to a template
Cluster tags
Groups (database tables)
Field tags
Patient and study data
Predefined blocks
Derived data
Tag syntax overview
Adding section breaks, unlocking, and locking sections
Previewing a report
Saving a report template and handling versions
Chapter: Communication Manager
191
Communication Manager overview
Overview of functions
Key terms and concepts
Basic procedures
Starting the Communication Manager
Defining data transfer jobs
Data transfer settings and parameters
Description of predefined transfer jobs
Configuration of automatic or semi-automatic report
distribution
Configuration of data export jobs to HIS/CIS system
Data import from a HIS/RIS or CIS system
Sending study reports as fax or email
Data export to a departmental material management system
Viewing the export queue of pending jobs
Viewing the export log
Communication appendix
HL7 data import: HL7 Listener application
Modifying the HL7 Listener error logging behavior
Checking on received messages and connection settings
Changing the communication port
6 / 456
AXA5-200.640.07.01.02
155
155
155
156
159
160
162
164
164
164
167
169
170
171
179
181
186
187
188
191
191
191
191
192
193
195
214
214
222
233
235
240
242
244
245
245
246
246
248
System Administration
Table of Contents
Activating VistA support
ADTA08 message handling
Response to unsupported ADT messages
Logging HL7 messages
Sending a test message
HL7 message specifications
Message definitions for incoming messages from HIS/RIS or CIS
Inbound messages from a material management system
Inbound HL7 messages: maximum length of elements
Message definitions for outgoing messages to a HIS/RIS or CIS
Message definitions for outgoing messages to a material
management system
ASCII flat file communication
Rules and requirements for inbound messages
Rules for outbound messages
Overview of system groups available for data export
Chapter: Configuration Manager
Configuration Manager Overview
Starting the Configuration Manager
Adjusting system parameters
Defining study types
Creating a new study type
Changing the input cluster and report template assignment
Changing the sequence of clusters and templates in the list
Saving or resetting changes
HL7 Mapping
HL7 Export mapping
HL7 Import mapping
Changing HL7 Import and HL7 Export mappings
Mapping elements PV1.2, PID.8, and FT1.6
Maintaining a service logbook
Overview of installed information system components
Editing dictionaries
Editing dictionaries and grouping items
Assigning dictionary entries to bar codes
Enabling dictionaries
Scanning bar codes
Exporting or importing bar codes for a dictionary
Terminating syngo Dynamics
Managing anatomical sites
Defining a new site
Adding new regions and subregions
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
248
248
249
249
249
250
250
257
258
259
267
268
268
271
273
305
305
305
306
310
311
312
313
313
314
315
316
317
318
319
320
321
321
323
324
325
326
327
328
329
330
7 / 456
System Administration
Editing or rearranging sites
Checking the sites configuration
List of factory-predefined anatomical sites
Defining data transfer from a Dräger Infinity patient monitor
Selecting data for transfer
Defining matching criteria
Changing gateway data
Troubleshooting
Synchronization of inventory lists
Chapter: Computer Configuration
330
331
331
343
344
345
345
345
346
349
Computer Configuration overview
Changing and testing the server connection
Installing a bar code reader
349
349
350
Chapter: Backup Manager
353
Backup Manager overview
Overview of functions
Key terms and concepts
Backup options and backup strategy
Backup to a backup server
Backup to tape
Starting the Backup Manager
Creating an immediate backup of the information system
Scheduling information system backups
Restoring the information system databases from a backup
Restoring the SIS database and server system environment
Restore SQL Server Master database
Backup protocol
353
353
353
353
354
355
357
358
359
363
363
365
368
Chapter: Configuration of Statistics Manager and Inventory
Manager
371
Statistics Manager configuration
Starting the Statistics Manager configuration
Checking the server connection
Setting database query defaults
Modifying the graphic display of aggregation results
Changing printout settings
Inventory Manager configuration
Starting the Inventory Manager configuration
Networking Inventory Manager applications
Adjusting user interface settings
8 / 456
AXA5-200.640.07.01.02
372
372
372
373
374
375
376
376
377
378
System Administration
Table of Contents
Establishing the connection with the information system
database
Redefining column headers
Chapter: Setting up Cost and Charge Control
380
382
383
Defining data acquisition
Creating the group REFPRICE
Creating the group PRICESUM
Modifying groups and dictionaries
Unit-related cost/charge calculation
Time-related cost/charge calculation
Creating the cluster PRICALC
Defining data output
Preview of accumulated cost/charge during an ongoing study
Defining a cost preview template
Previewing cost during the examination
Output of charge information in a study report together with
clinical findings
Creating an output report cluster
Re-inserting groups and fields
Saving the template under a new name
Export of cost/charge information to a HIS/RIS or CIS as an HL7
message
Export of cost/charge information to a HIS/RIS or CIS as an
ASCII flat file
385
385
387
388
388
390
392
393
393
393
394
Chapter: Installation and Update of Report Workstations
399
Hardware and software requirements
License options
Prerequisites for Report Workstation installation or update
Software installation
Installing Report Workstation software with dongle
Installing Report Workstation software with floating license
Configuring connection to the SIS server
Software update
Automatic Report Workstation update
Manual Report Workstation update
394
395
395
396
396
397
399
399
401
402
402
404
408
409
409
410
Chapter: Remote Access to the Information System Server 411
Installation of the Symantec pcAnywhere caller
Remote access to the information system server via pcAnywhere
Starting pcAnywhere
Ending a pcAnywhere session
Restarting pcAnywhere on an information system server
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
411
412
412
414
414
9 / 456
System Administration
Chapter: Calculation Methods in the Acquisition System
What is calculated and how in hemodynamics mode
Demographic data
Pressures detected on pressure waveforms
Time reference
Beat selection for pressure analysis
Ventricular pressures
Arterial pressures
Atrial and venous pressures (including PCW)
dP/dt and dP/dtmax
Exclusion area
Gradients
Pressure differences
Fractional flow reserve (FFR)
Oxygen saturation
Cardiac output
Derived parameters
SpO2 measurement with finger-tip sensor
10 / 456
AXA5-200.640.07.01.02
415
415
415
415
416
417
418
419
420
421
422
423
425
425
426
430
432
435
System Administration
Part: System Administration
General Administrator Information
Safety section in the Operator Manual
Note
Make sure that you always read the Part Safety in the AXIOM Sensis XP Operator Manual carefully before you perform any system administration tasks.
Additional information for system administrators
In addition to the user and overall safety information provided by the AXIOM Sensis XP Operator Manual the following pages provide important background information that applies to system administration in particular.
System administration overview
Scope of applicability
This System Administration manual applies to the AXIOM Sensis XP Information System, which is intended to be used in conjunction with AXIOM Sensis XP
recording systems for electrophysiological and hemodynamic studies within a
cath-lab environment.
The AXIOM Sensis XP Operator Manual contains a system overview section that
presents the key features and functions of AXIOM Sensis XP in a concise way.
See AXIOM Sensis XP Operator Manual, Part AXIOM Sensis XP System Overview, Chapter Overview of the AXIOM Sensis XP System and Product Options.
Scope of functions
AXIOM Sensis XP (VC11)
This System Administration manual describes the scope of a complete system
with all options and components that are available and have been released. The
scope of the system you have chosen may be different depending on what you ordered and how it was installed. Possible options have not been marked specially.
Please use only the text of your order as a reference for the functional scope of
your system.
AXA5-200.640.07.01.02
11 / 456
System Administration
System and user documentation
System and user documentation are the documents that you received together
with your AXIOM Sensis XP system.
System Owner
Manual
In the System Owner Manual, you will find the following documents or you
should file them there:
 Modification status of the components
 Technical data
 Certificates, labeling, drawings
 Software licenses and warranty
 Information about upgrades
Operator Manual
The Operator Manual describes the AXIOM Sensis XP system from a clinical user’s point of view.
Here you will find information about:
 Safety
Note
Be sure to read this section before you start working with the system.
 AXIOM Sensis XP system hardware
 AXIOM Sensis XP Acquisition System acquisition system software
 AXIOM Sensis XP Information System information system software
 Integration with Siemens X-Ray systems
 Troubleshooting
System Administration
Manual
The System Administration manual describes administration and configuration
of the AXIOM Sensis XP Information System, which includes:
 Configuration of the information system database
 User administration tasks for the information system
 Configuration of data exchange between the information system and other
systems
 Configuration of data backups and other information system settings
These tasks require data management and profound computer knowledge rather
than clinical knowledge.
The system administration tools and dialog boxes are not accessible to the typical
clinical user. They are password-protected and therefore only available to trained
administrators with advanced privileges.
12 / 456
AXA5-200.640.07.01.02
System Administration
General Administrator Information
Addenda
Note
Addenda are issued for software patches and minor updates.
Be sure to read the addenda to the Operator Manual and System Administration manual necessitated by technical developments.
Online help
The current AXIOM Sensis XP software version does not include context-sensitive
online help. Therefore even though Help menus and Help buttons are already
available in some application windows and dialog boxes, no help texts can be
called up yet.
Structure of the System Administration manual
Structure
The AXIOM Sensis XP system administration manual is structured in a way that
helps you find information quickly.
Chapters
This System Administration manual comprises different chapters. The chapter title is stated in the page header.
Table of contents, index,
and glossary
At the beginning of the manual you will find the table of contents, the index, and
a glossary explaining product-related terms and frequently used abbreviations.
Text layout
A set of conventions has been observed in this System Administration manual
that is intended to help you perceive the importance of a piece of text at a glance.
The following conventions have been used:
Instructional text
Instructional text guides you in the proper use of your system.
 A checkmark indicates a prerequisite that must be fulfilled before you can start
a function.
 Instructional text is preceded by a diamond.
List items
 Text of this type is preceded by a square.
Explanatory text
Explanatory text subdivides an instructional text or list text into further subitems.
– Text of this type is preceded by a dash.
Cross-reference
A cross-reference refers you to further explanations elsewhere in your System Administration or in other documents. Text of this type is preceded by an arrow, for
example, Structure of the System Administration manual 13
Note
A note emphasizes important information without there being direct danger and
helps you to operate the system properly and to avoid errors.
Notes also provide additional useful explanations about a subject.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
13 / 456
System Administration
Note
This text has a gray background.
Information about the software
User interface and language
The user interface of the administration tools is available in English only.
Copyright
The system and user software of this product are protected by copyright.
syngo®
The images of the user interface that are shown in this manual are examples only.
Differences in detail may occur in your system due to constant development and
improvement of the software.
The AXIOM Sensis XP software uses the Siemens common medical software syngo®. For more information, refer to the syngo® documentation.
DICOM compliance
The AXIOM Sensis XP software is DICOM-compliant. A DICOM conformance
statement is available from Siemens.
Third-party software
Only software authorized by Siemens for use with this product may be used.
Note
Unauthorized software or manipulations and alterations to the software can
cause the product to function incorrectly. This system behavior can cause injury
to the patient and damage to the product.
Note
If database tools are tampered with, the integrity of the database may be adversely affected. Only personnel authorized by the hospital are allowed to perform administration tasks on the AXIOM Sensis XP database.
Note
An inoperable system may result if system tools are used incorrectly.
Do not use any Windows operating system disk utilities (such as the disk defragmenter) while AXIOM Sensis XP is running.
Note
Improper connection to the DICOM interface or use of improper protocols may
cause corruption or loss of data.
Note
Improper connection to HICOR and Artis interfaces may cause corruption data or
loss of data.
Always consult Siemens technical support before connecting the HICOR and
Artis interfaces.
14 / 456
AXA5-200.640.07.01.02
System Administration
General Administrator Information
Data protection
Personal data is subject to the applicable data protection regulations.
 Please observe the relevant legal provisions.
System messages
Messages are issued by the AXIOM Sensis XP user interface on various occasions.
 Please read these messages carefully and act only when you are sure that you
have understood them.
Reference to the system
administrator
A number of system messages on the AXIOM Sensis XP clinical user interface refer to configuration issues and the system administrator.
System administration and configuration tasks are covered by this System Administration manual.
Reference to Siemens
Service
Other messages both on the clinical user interface as well as on configuration and
administration platforms refer to the Siemens Service.
As a rule, these messages refer to technical system configuration and installation
issues.
Note
If you receive messages asking you to contact service or system administration
please turn to your Siemens first line support.
Names and designations used
All names and data of patients and institutions that are used in this System Administration manual are entirely fictional.
Any resemblance to names of existing people or organizations past or present is
entirely coincidental.
Communication and connectivity
This product can communicate with other systems. However, improper connection of this system with any other products or use of improper interface protocols
may cause corrupt data or loss of data.
Refer to the released AXIOM Sensis XP DICOM conformance statement, HL7 Interface Specification, or other conformance statements and contact your authorized local Siemens sales representative.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
15 / 456
System Administration
16 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Information System Concepts
The AXIOM Sensis XP Information System is an optional component and add-on
to AXIOM Sensis XP. The AXIOM Sensis XP Information System provides data
management and reporting features that meet the particular requirements of a
cath lab. It links one or several AXIOM Sensis XP recording systems as well as one
or several AXIOM Sensis XP Post-Processing Workstation to form a comprehensive cardiac cath-lab solution.
With software version VC10 and higher, AXIOM Sensis XP acquisition and information system versions are independent of each other. This means that you can
update your information system but continue working with VC03x acquisition systems. For these acquisition systems, updating only the information system client
software will be sufficient to integrate them in a VC10 and higher network. The
acquisition system software components do not need to be updated.
This section provides an overview of the AXIOM Sensis XP Information System
and its system administration:
 AXIOM Sensis XP: acquisition system and information system overview
– Explains the key features of the AXIOM Sensis XP Acquisition System and
the AXIOM Sensis XP Information System, and explains how the two database systems interact.
 Database overview
– Provides an overview of the AXIOM Sensis XP system databases, explains
the “division of labor” between these databases and how they exchange
data.
 The AXIOM Sensis XP Information System central database
– Explains the structure and concepts of the information system central database.
 The study type concept
– Explains how data input and reporting features are linked to clinical applications.
 The reporting concept
– Describes the template concept on which report creation with the AXIOM
Sensis XP Information System is based.
 The communication and interface concept
– Explains how the AXIOM Sensis XP Information System communicates
with systems outside the cath lab.
 The security system
– Explains how the information system handles user management and auditing.
 Backup and restore
– Describes the information system backup concept.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
17 / 456
System Administration
AXIOM Sensis XP: acquisition system and
information system overview
To understand the AXIOM Sensis XP Information System concept completly, it
needs to be seen in conjunction with the AXIOM Sensis XP Acquisition System.
AXIOM Sensis XP Acquisition System
The AXIOM Sensis XP Acquisition System is a cardiac cath-lab recording system
for electrophysiological or hemodynamic studies.
Its prime focus is the performance of one study at a time for which it provides
state-of-the-art signal acquisition facilities as well as recording and evaluation
tools.
During an examination the acquisition system acquires electrophysiological or hemodynamic data from cardiac catheters, presents this data as waveforms on
screen, and provides a toolbox of evaluation procedures and calculations based on
the acquired data. During the ongoing study it allows the user to record the acquired signals, and it stores recordings and calculation and evaluation results in a
chronological way.
Each AXIOM Sensis XP Acquisition System can be operated as a stand-alone solution, therefore it has its own set of databases where patient and study data are
kept.
The key focus of the AXIOM Sensis XP Acquisition System is to record while a
study is being performed. When a study is completed the data can be kept on the
acquisition system database for a little while longer. But once the case is closed
the study should be archived on CD or DVD or in a network archive and then removed from the acquisition system database to make room for new study data.
The Patient Browser provides a view of the AXIOM Sensis XP Acquisition System databases and a toolbox for data maintenance tasks.
The AXIOM Sensis XP Configuration Panel offers configuration windows in
which signal acquisition schemes can be optimized for specific clinical applications. Most of the tools that are available on the AXIOM Sensis XP Configuration
Panel have a strong clinical focus.
The AXIOM Sensis XP Acquisition System main database cannot be customized
by a user or system administrator. Only how the data is presented in the Patient
Browser window can be configured to some degree.
Any AXIOM Sensis XP Acquisition System configuration tasks that go beyond
the clinical level and are more technical in nature are the responsibility of Siemens
Service. All settings that fall in this range have far-reaching consequences within
18 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
the system. Without a deeper knowledge of the technical details and the detailed
interaction of the various system components, you would risk malfunctions if you
changed such settings.
The overwhelming majority of the settings within the area of responsibility of Siemens Service are made immediately during installation. We recommend that you
call Siemens Service if you need to change them later on. The Service platform is
therefore password-protected and not available to clinical users or cath-lab system
administrators.
Refer to the AXIOM Sensis XP Operator Manual for a detailed description of the
AXIOM Sensis XP Acquisition System from a clinical user’s point of view.
Data flow in the AXIOM Sensis XP Acquisition System
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
19 / 456
System Administration
AXIOM Sensis XP Information System
The AXIOM Sensis XP Information System is a software package for networking,
reporting, and data management in the cath lab. The information system is not in
itself a stand-alone solution and can only be operated in conjunction with one or
several AXIOM Sensis XP recording systems.
Networking
The AXIOM Sensis XP Information System features a central database system
for all the connected AXIOM Sensis XP recording systems and AXIOM Sensis XP
Post-Processing Workstations. The information system also functions as a time
server that synchronizes time settings throughout the cath lab.
Example of an AXIOM Sensis XP Information System network
Patient Explorer and
Documentation Tool
The AXIOM Sensis XP Information System central database automatically collects all data that is relevant for reporting from a connected acquisition system
during an ongoing examination. In addition to this automatically transferred data,
a user may enter information manually. Information entered manually might be,
for example, information on medication, which is relevant for interpreting signal
readings, but which cannot be collected automatically by the system.
The Patient Explorer and the Documentation Tool are the information system
platforms for the clinical user to view and edit patient information in the system
database. The Patient Explorer presents a view of the database on a patient and
study organization level. The Documentation Tool provides access to the database tables for an individual study or a patient. It presents any manually entered
study data in the database.
The database tables that are available through the Documentation Tool can be
configured on the system administration platform DB Manager.
See Database Manager 73
20 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Reporting
The comprehensive study information pool of the AXIOM Sensis XP Information
System central database is available for reporting.
The Report Generator is based on Microsoft® Word and features automatic or
semi-automatic creation of study reports. If automatic report creation has been
enabled, a study report is created immediately after a study is closed. For semi-automatic report creation, a user clicks “Create Report” in Patient Explorer and the
system produces a report file from a template using the study data available in the
information system central database. The user can then edit this report, for example, by adding comment text which interprets the presented study results.
In the Report Generator, report creation is based on so-called report templates.
Report templates determine what information is to be read from the central database into the report and how this information is to be presented. These report
templates can be freely configured in the Report Composer. The Report Composer is available to users with administrator privileges.
See Report Composer 155
In addition to these more text-based reports, the information system features two
graphical reporting tools: Heart Picture Illustrator and Coronary Tree Illustrator, which allow you to indicate your findings in a schematic heart picture or coronary tree picture. These pictures can be integrated in the study reports created
by Report Generator. The graphical reporting tools are optimized for their respective applications and cannot be customized by a user or system administrator.
Communication
The AXIOM Sensis XP Information System can exchange data with other systems. For example, it can export data to other systems, such as a hospital (HIS),
radiology (RIS), or cardiology information system (CIS).
See The communication and interface concept 46 and Communication Manager 191
Statistical analysis and
inventory management
The information system central database forms a comprehensive data pool which
is also available for applications that reach beyond immediate case handling.
 Statistical analysis
– With the help of the Statistics Manager, the information system central
database can be queried for any information relevant for research or administrative purposes.
 Inventory management
– The optional tool Inventory Manager uses the information on the application of drugs and the use of materials stored in the information system central database. The Inventory Manager will inform you when you are
running out of stock and when you need to reorder, for example.
Both the Statistics Manager and the Inventory Manager can be configured to a
certain degree.
See Configuration of Statistics Manager and Inventory Manager 371
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
21 / 456
System Administration
Long-term storage
Whereas the main database of the AXIOM Sensis XP Acquisition System is only
designed to store study data for a limited time period, the central database of the
AXIOM Sensis XP Information System is intended as a long-term archive for patient and study data as well as reports.
The data from the information system central database does not have to be archived on external media, as is necessary for the main database of the acquisition
system. In the information system central database, study data of previous examinations will accumulate over the years to form a comprehensive cath-lab knowledge database.
The information system central database should, however, be backed up at regular intervals for data security reasons.
See Backup Manager 353
Note
Why does study data need to be archived and removed from the acquisitions system database but may remain on the information system database for long-term
storage?
The acquisition system main database stores waveform recordings (signal recording raw data). Very long recordings occupy a large amount of disk space. In
contrast, the information system database only stores findings based on or calculated from waveform readings. This type of information requires far less disk
space.
If a so-called waveform image has been stored for a study in the information system database this is not actually a waveform recording. A waveform image is a
hardcopy of the waveforms displayed on the screen at a certain point in time
during the examination. Waveform images occupy less disk space than actual
waveform recordings.
22 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Data flow in the AXIOM Sensis XP Information System
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
23 / 456
System Administration
Database overview
Earlier in this chapter the acquisition system database and the information system
database were frequently mentioned. This was, however, an oversimplification
made for the purpose of introducing the overall concept before going into detail.
In fact, a few more databases are involved.
Database overview
Acquisition and information system: preregistered and
registered patients
Both the acquisition system and the information system distinguish between studies that have already been performed or are currently being performed and studies that are scheduled to be performed soon.
However, whereas the acquisition system stores preregistration data in a separate
database, the information system has only one central database for both preregistered and examined patients and their study data. In the information system database, preregistered and examined patients are distinguished by a workstatus
flag.
24 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
The two database systems exchange data on these occasions:
 A patient is preregistered on an acquisition system.
– The patient and study are stored both in the scheduler database of the
acquisition system and in the information system central database.
– In the information system database, the study has the workstatus flag PreCath. Users can add information via the Documentation Tool here.
 A patient who was preregistered on an acquisition system is registered for an
examination on this acquisition system.
– The patient and study are moved from the scheduler to the acquisition system main database. In the information system the study’s workstatus
changes to DuringCath.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
25 / 456
System Administration
 A patient who was preregistered in the information system is registered for an
examination on one of the cath lab’s acquisition systems.
– From any acquisition system in the cath lab, users can query the information system database for preregistered patients
 A new patient is registered for an examination on an acquisition system.
– A new study is created both in the main database of the acquisition system
and in the information system central database.
26 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
 Study data transfer during an ongoing examination
– During the study, the acquisition system sends calculation results and information about events to the information system.
– Users can enter additional data via the Documentation Tool.
 Manual data transfer from the acquisition to the information system.
– If the data connection between the two database systems was lost during a
study, users can send study data to the information system manually.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
27 / 456
System Administration
Statistics Manager and Inventory Manager
The information system software tools Statistics Manager and Inventory Manager query the information system central database. However, both applications
also maintain a database of their own.
In the case of the Statistics Manager this database stores all queries of the central
information system database.
In the case of the Inventory Manager the local database stores the results of central database queries as well as inventory and vendor data.
If the Statistics Manager and Inventory Manager have been installed on several
PCs or workstations in your cath-lab network, each of these installations will set
up their own local databases.
System databases and system administration tools
Configuration of the
central database
Most of the AXIOM Sensis XP Information System system administration tools
access the information system central database:
 DB Manager
– Allows you to customize those database tables that are available for entry of
study data via the Documentation Tool. Database tables that receive data
directly from the acquisition system cannot be customized (for example,
database tables for pressure calculation results).
 Security Manager
– Allows you to define user access rights to the information system central
database and to the various information system tools and platforms.
 Backup Manager
– Helps you create backup copies of the central database on tape or to a
backup server in the network (and helps you reload backups if this becomes
necessary).
 Communication Manager
– Allows you to configure communication between the information system
and systems outside your cath-lab network.
 Configuration Manager
– For the configuration of study types, HL7 mappings, dictionaries, system
parameters, Infinity vital signs, and the anatomical sites list.
 Computer Configuration
– For setting up the server connection and installation of a bar code reader.
28 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Other information system databases
The following AXIOM Sensis XP Information System system administration tools
access other information system databases:
 Statistics Manager Configuration
– Allows you to configure the Statistics Manager application.
 Inventory Manager Configuration
– Allows you to configure the Inventory Manager application.
AXIOM Sensis XP Information System administration tools
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
29 / 456
System Administration
The AXIOM Sensis XP Information System
central database
The AXIOM Sensis XP Information System central database is a relational database, which uses the SQL query language.
Basically the structure of the information system central database is typical for a
relational database system. There are, however, a few additional concepts and
features, which make sure the information system meets the particular requirements of a cath lab. Also the terminology used in the database concept (and on
the database configuration platforms) is to some extent cath-lab and Sensis specific.
Key terms
These are information-system specific key terms in the context of the database
structure.
 Group = database table
– see Static and customizable database tables (groups) 31 and Organization of groups 32
 Scope = attribute defining the information level of a database table
– see Organization of groups 32
 Group type = attribute defining formal data characteristics of database tables
– see Organization of groups 32
 Dictionary = pick-list of predefined field (table cell) entries
– see Dictionaries (pick lists) 33
 Cluster = a collection of data groups (i.e. database tables)
– see Clusters 35
 Index = predefined secondary indexes that help to speed up search procedures
(these factory-set indexes should not be changed by a user or system administrator).
 Procedure = predefined sql procedures, which serve as extensions to the data-
base functionality (the list of factory-set procedures should not be changed).
Customizing database
features step by step
30 / 456
See Database Manager 73 for detailed instructions on how to customize these
database features. This section also includes a detailed description of the syntax
of definition files.
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Static and customizable database tables (groups)
The information system central database consists of two sorts of database tables:
 Static database tables (also called system tables or system groups)
– These tables receive data that is automatically transferred from the acquisition system (for example, measured data, calculation results).
– As a rule, static database tables cannot be edited by the clinical user and
they cannot be customized by a system administrator either.
 Freely customizable groups
– These groups include all database tables which the clinical user can fill in
and edit in the Documentation Tool.
– A system administrator can customize these database tables in the DB Manager.
AXIOM Sensis XP Information System database tables (groups)
Note
AXIOM Sensis XP (VC11)
In the information system database, tables are called groups.
AXA5-200.640.07.01.02
31 / 456
System Administration
Organization of groups
A group is a standard database table consisting of columns (fields in the information system database), rows (data records), and table cells (values).
This structure corresponds to the way these tables are presented to the clinical
user in the Documentation Tool.
Structure of customizable database table (group)
Group classification:
scope
Different database tables contain information from different information levels:
 Patient level
– This level contains, for example, patient demographic data.
 Study level
– This scope contains information that applies to one study at a time only.
 Report and template level
– This level contains information on the reports that belong to a study and the
template a report is based on.
 System level
– This scope is reserved for internal system information management.
This level definition is implemented by assigning each database table to a predefined scope (i.e. information level).
Data is inherited into the hierarchy of data levels. For example, for a new study,
information from patient tables, which was entered in during a previous study, is
also available.
Groups (database tables) are assigned to scopes during database definition in the
DB Manager. The scope “study” is the default value.
Group attribute:
group type
32 / 456
Apart from the information contents level, the groups (database tables) in the
central information system database are also categorized according to formal data
entry criteria.
AXA5-200.640.07.01.02
System Administration
Information System Concepts
The group attribute group type indicates whether database tables store only one
record per study or multiple records. The group attribute also indicates whether
the database fields allow free text entry or only entry selection from pick lists.
These group types are available for database table definition in the DB Manager:
 Only one record per study is permitted (non-repetitive group)
 Multiple records per study are permitted
– repetitive group, at least one key field
– repetitive group, repetition on a sequence number
 Free text entry permitted (free text group)
 Free text entry permitted but comment templates may be available
Dictionaries (pick lists)
AXIOM Sensis XP Information System
Customizable groups for data entry in the Documentation Tool consist of one or
more fields. These fields can either be free text fields or related to a selection list,
from which the user can pick entries.
These selection lists are called “dictionaries” in the AXIOM Sensis XP Information
System. A dictionary is a pick list of possible entries linked to a field.
Once a user picks an item from a dictionary for a table cell entry, the system stores
the code value of this item in the database (it does not store the entry as a text
string).
Dictionaries can be customized to a certain extent by clinical users in Documentation Tool. System administrators can access dictionary definition files in the DB
Manager.
Dictionary in a database table (group) not classified for free text entry
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
33 / 456
System Administration
AXIOM Sensis XP Acquisition System
There is a second set of dictionaries available for customization by a system administrator only: dictionaries for static database tables.
Above we stated that static database tables cannot be edited by users or system
administrators. However, in this case it is only the pick list (dictionary) and not the
database table that it is linked to, which can be edited.
After editing, these dictionaries can be re-imported into connected recording systems with Import Dictionary on the Configuration Panel of these acquisition systems.
In AXIOM Sensis XP Acquisition Systems these dictionaries serve as pick lists, for
example, in the Condition dialog box. Any item that the clinical user selects from
an acquisition-system dictionary edited by the system administrator during a
study will then automatically be transferred to a predefined static information system database table.
On the DB Manager platform, a system administrator can configure these acquisition-system dictionaries in the same way as dictionaries for customizable
groups.
In the AXIOM Sensis XP Acquisition System, dictionaries are required at various
times:
 During patient registration, for example, for selecting rather than entering the
performing physician’s name.
 During the examination proper, for example, in the Condition dialog box.
Note
The AXIOM Sensis XP Acquisition System also offers a configuration platform
for editing some of these dictionaries: The Registration Configuration window
can be accessed via the Configuration Panel of the acquisition system.
You should not use this window for dictionary editing if your cath lab uses an
AXIOM Sensis XP Information System. It is intended only for use on a standalone AXIOM Sensis XP Acquisition System without an information system.
As the acquisition system always reads all dictionaries from the information system during system startup, any changes you make via the Registration Configuration platform will be lost on the next system startup.
34 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Customizable dictionaries for the AXIOM Sensis XP Acquisition System
Clusters
A cluster is a collection of groups (database tables). Through clusters, the associated groups can be accessed together. This results in a much more efficient mode
of working (for example, when data export rules are defined) than if each database table were accessed individually.
The information system central database distinguishes between three basic types
of clusters:
 Input clusters
 Output clusters
 Output report clusters
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
35 / 456
System Administration
Input clusters
The tree view structure of data input tables in the Documentation Tool is produced by “clustering” groups (i.e. database tables). This clusters helps clinical users to obtain a better overview of the available database tables. For system
administrators, cluster organization presents an efficient way of defining which
tables to present to the clinical user for a specific study type.
Frequently defined input clusters are, for example:
 Flowsheet
– Comprising all the relevant groups for data entry during an examination
 Diagnostic Summary
– Group database tables for the entry of diagnostic information and conclusions
Input clusters present database tables in the Documentation Tool in a tree-view fashion
Output clusters
Clusters are also used for grouping database tables for the purpose of data export.
Accessing clusters instead of individual database tables makes the definition of export rules easier.
Output clusters can be defined to include both static and customizable groups (database tables).
If only selected fields of a group (database table) are to be included in an output
cluster for data export, for example, this can be indicated in the cluster definition.
See Editing clusters 106
Output report clusters
Output report clusters are defined specifically for the purpose of study-report creation. Output report clusters help to output study information to a report file rather than to an external system.
Output report clusters are intended to group customizable database tables and
make them available for reporting. Only customizable groups that are members of
an output report cluster are available for selection and insertion in a report template.
36 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Study data from static database tables (system tables) are made available for report definition in so-called predefined blocks. These are non-customizable factory
predefined collections of system tables.
The cluster concept
(overview)
Clusters group database tables for data input and data output purposes
Note
The cluster concept is of central importance to an understanding of the task of
information system administration.
Clusters group database tables (which are called groups in this database concept) for the purpose of data input (in the Documentation Tool) and data output (to other systems or to a study report).
Clusters are defined or customized in the DB Manager. A cluster definition syntax has to be observed here.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
37 / 456
System Administration
The study type concept
Clinical users access the information system database with the Documentation
Tool to enter data, or they retrieve information from the database for the purpose
of reporting with the help of the Report Generator.
In both cases (data input and reporting) the filter that gives users access to just the
data and database tables currently needed is the study type.
The study type is another concept that is of crucial importance to an understanding of the AXIOM Sensis XP Information System, as it controls clinical users’ access to the information system database.
What is a study type?
A study type is a typical examination that is frequently performed in your cath lab
to clarify a specific diagnostic problem. Such an examination demands that a typical set of measurements and calculations be performed. A study type also involves the collection and manual entry of a typical set of additional information by
the clinical personnel to help interpret the automatically acquired signal readings.
A specific diagnostic problem also requires a specific type of report, which presents the relevant study findings.
A study type is a typical examination that is performed to clarify a typical diagnostic problem. The study type controls the data input and reporting options presented to the clinical user.
Study type and data input
From a database point of view, the study type selects certain clusters of database
tables from all customizable groups in the database and presents them for manual
data input in the Documentation Tool.
Clinical users are prompted to specify what type of study they are about to perform (“study type” is a mandatory field during patient registration). The Documentation Tool then presents only those clusters and their groups for the clinical
user to fill out that have been predefined as input clusters for this study type.
Study type and reporting
The study type also controls what report options (report templates) are presented
to the clinical user during report generation or which report template is used if automatic report creation has been enabled.
Report templates are customized for specific study types. This means that a report
template is configured to present only the data that is relevant and has been entered specifically for this study type. And the report template will also present that
data in a way best-suited to the clinical problem at hand. Various alternative report
templates may exist for a study type, allowing the user to choose between various
report options in semi-automatic report creation.
See also The reporting concept 40
38 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Defining/customizing
study types
The AXIOM Sensis XP Information System comes with a set of predefined study
types. These study types can, however, be customized in the Configuration Manager. A system administrator may alter the definition of existing study types in the
information system or create new study types and associate (data input) clusters
and report templates with them.
See Configuration Manager 305
Study types control access to database tables (groups) for data input and data output to study reports
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
39 / 456
System Administration
The reporting concept
The AXIOM Sensis XP Information System features a powerful reporting system
comprising support for text and graphical report creation.
Reporting overview
Providing database support for an advanced and efficient reporting functionality
in an integrated cath-lab environment is one of the key features of the AXIOM
Sensis XP Information System.
Basic principle
The basic idea behind the AXIOM Sensis XP Information System reporting concept is that a central database collects a wealth of information in the preparation
phase of an examination (PreCath), during the actual examination (DuringCath),
and during post-processing of a study (PostCath).
This information is made available for report creation making sure that no data
needs to be typed into the system twice and no data can be overlooked when the
report is written.
Reports created by the Report Generator
Requirements
The information system solution
Efficient creation of reports is the prime focus of the AXIOM Sensis XP reporting
concept. “Efficient” in this case meaning that both speed and ease of creation are
important as well as adaptability of reports to the situation at hand.
The solution that the AXIOM Sensis XP Information System comes up with to
meet these requirements is a reporting process that is:
 Automatic or semi-automatic for the clinical user, and
 Highly customizable by the system administrator.
This division of labor between clinical user (quick and easy report creation and editing) and system administrator (highly flexible report customization) is a recurrent theme throughout the AXIOM Sensis XP Information System reporting
concept.
Report Generator and
Report Composer
Two applications have therefore been implemented for report creation and customization in the AXIOM Sensis XP Information System: the Report Generator
and the Report Composer, both of which are based on Microsoft® Word.
Report Generator
The Report Generator is the tool that clinical users will use when creating and editing reports, even though they might not even be aware of it. Clinical users simply
click “Create Report” and select a template, for example, in the Patient Explorer
40 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
window. They will find a report file displayed for review and editing in a “Wordlike” section of the screen. If this has been defined, reports may even be created
completely automatically when a study is closed.
Report Composer
The Report Composer is an add-in program for Microsoft® Word. It allows system
administrators to define “what a report will look like” as well as “what information
a report will contain”. The information system add-in functionality Tag Picker
helps them with this task.
Study reports and
study types
When clinical users start to create a report the study type concept acts as a filter
presenting them with only those report templates that are assigned to the current
study type.
In fact, it is only through assignment to a study type that a report template is made
available to a clinical user for selection at all. A system administrator who defines
a study report template for a specific type of examination must subsequently assign it to the study type it is intended for. The Configuration Manager is used for
assigning report templates to study types.
See also The study type concept 38
Supplementary graphical reports
In addition to reporting with the Report Generator, the AXIOM Sensis XP Information System provides tools for graphic illustration of findings for hemodynamic studies.
 The Heart Picture Illustrator is a tool for graphical presentation of congenital
anomalies in the heart.
 The Coronary Tree Illustrator is an application for the graphical presentation
of stenoses, collaterals, and grafts in coronary arteries.
In both tools, information from the AXIOM Sensis XP Information System database can be used for graphical display in a simplified heart picture.
Heart Picture Illustrator and Coronary Tree Illustrator create report definition
files that are saved back to the information system database. Schematic heart or
coronary tree pictures can be printed out or included in a report file created by the
Report Generator.
Neither of the two graphical reporting tools require customization by the system
administrator. Inclusion of schematic heart or coronary tree pictures in report templates can be configured with Report Composer.
g
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
41 / 456
System Administration
Report Composer and template definition
As a system administrator you will be using the Report Composer to customize
and create study report templates. Report templates are Microsoft® Word template files (*.dot files) that define what information from the database the final
report will present and how the final report will look.
Note
Key terms
For compatibility reasons the AXIOM Sensis XP Report Generator and Report
Composer work with Word document templates that use the Word 97-2003 format *.dot. Report Generator and Report Composer do not support the Word
2007 template format *.dotx.
There are a number of key terms and concepts you need to be familiar with when
working with the Report Composer.
Some of the terms listed here are, however, not Report Composer specific. They
are used in advanced Word document formatting. These terms are listed here as
a reminder of what level of Microsoft® Word experience you should have when
you start working with the Report Composer.
Information system
terminology
 Tags
– Tags are placeholders for information to be read from the database.
 Tag picker
– A Report Composer window for tag selection with drag and drop.
 Output report cluster
– A definable collection of customizable groups for the purpose of data output to a report. See Output report clusters 36.
 Group
– A database table in the information system database; a distinction is made
between customizable groups and static database tables. See Static and
customizable database tables (groups) 31.
 Field
– A value from the database; the term is also used for an attribute in a database table (resulting in the output of more than one value). See Organization of groups 32.
 Predefined block
– A factory-defined, non-customizable set of information from system tables.
– X-ray images, waveform images or ablation graphs (i.e. screenshots of the
Review or Ablation card showing waveforms, which are image files in
*.emf format) mapping system images and heart picture and coronary tree
images are also considered predefined blocks by the information system.
42 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
 Derived data
– Mostly hemodynamic data that was measured or calculated during an
examination by the acquisition system.
Word concepts
 *.dot file
– A Microsoft® Word document template.
 Section break
– Word concept for subdividing documents. Different sections can have different display properties.
 Layout view
– Word concept for viewing documents for content and formal outputoriented editing.
 Formatting marks
– Also known as non-printing characters or text symbols; Word concept for
showing spaces, tabs, line breaks, paragraphs, page and section breaks, and
so on.
 Header / footer
– Word concept for printing information outside the actual text frame as
defined by margins.
 Character and paragraph formatting
– Application of formal attributes to different text units.
 Tables
– Word functionality for display of data in structured form.
Contents definition: meta tags
What information from the central database is to be included in a study report is
defined by tags. The AXIOM Sensis XP Information System uses a specific syntax
that defines what data is to be inserted at a tag position.
Tag handling during report generation
Technically speaking, this is what happens when a report is being generated:
A Word document (*.doc file) is created based on the selected template (*.dot
file). The Report Generator parses the document for tags and the corresponding
data is collected from the database. The data is inserted in place of the tags and
the tags themselves are removed from the document.
Tag-picker window
The Report Composer offers a function for easy tag selection and insertion into a
report template: the tag-picker window.
When using the tag-picker window you simply drag and drop database objects
into a report template and the system automatically translates these objects into
tags. You do not have to bother with the tag syntax. Nevertheless it is useful to
familiarize yourself with at least some tag syntax basics so that you understand
what information has already been included in the template.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
43 / 456
System Administration
For details on how to work with the tag-picker window and on the tag syntax used
by the information system see Report Composer 155.
Defining a study report
template
Defining a study report template therefore means assembling tags in a template
file (*.dot file). These tags represent the data that is to be read from the database
during report generation.
Template formatting: Word functions
When it comes to formal aspects of template layout and design almost all Word
functions for text formatting are available in the Report Composer. (Exception:
the definition and use of macros). To what extent you use these formatting options entirely depends on your knowledge of Microsoft® Word. The more familiar
you are with advanced text processing in Word the more complex and individually
customized report templates you can create.
From a Word experience point of view, two levels exist for the customization of
study report templates.
Adaptation of factorydefined templates
System administrators with average experience with Word should use factorydefined report templates and adapt these to the requirements of their cath lab:
 Adapt template headers and footers (replace the Siemens name and logo).
 Add tags for additional database information to be included.
 Accept the predefined table formats for cluster tags and select table styles for
group tags.
 Possibly change font settings.
 Add section breaks and unlock sections to allow clinical users to add free text
comments or findings to a final report.
You should know the Word functions if you want to adapt factory defined report
templates:
 Showing/hiding formatting marks (also known as text symbols or non-printing
characters).
 Toggling between normal and print layout.
 Formatting characters and paragraphs.
 Changing page size and margin settings.
 Formatting the page header/footer.
 Including pictures (only if you need to include a logo).
 Formatting pictures (if you include images or a logo, for example).
 Section breaks (significance of section breaks, how to recognize them)
44 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Creating templates
from scratch
Note
Only as an advanced and very experienced Word user should you set out to create
completely new study report templates from scratch. When you define new templates, you might use Word templates for letters or other official documents that
are in use at your hospital as a basis.
Remember never to use macros when creating study report templates from
scratch. Always make sure all macros and add-ins are disabled when you base
your study report templates on existing Word *.dot files.
If you want to create report templates from scratch you should have expert (and
not only average) knowledge of all the above listed Word functions and should
also have experience with the following concepts:
 *.dot files
– How and where to save them, what information they inherit to a *.doc file.
 Macros and add-ins
– In particular: how to make sure no non-Report-Composer macros or add-ins
are active while you are working with the Report Composer.
 Styles
– How to define them, how to apply them, how to organize them, in particular with respect to the organization of styles and *.dot files.
 Page breaks
– Controlling page breaks though insertion of formatting marks or through
paragraph formatting.
 Tables
– How to format entire tables or individual table rows and columns, how to
enable or suppress automatic column width adjustment, how to remove or
add borders and shading, how to control page breaks in tables.
Configuration Manager and study type association
A new template that has been created with Word and the Report Composer and
then saved back to the database is not yet available for clinical users to select. Every template needs to be associated with a study type first.
Report templates are associated with study types in the Configuration Manager.
See also The study type concept 38 and Configuration Manager 305
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
45 / 456
System Administration
The communication and interface concept
The AXIOM Sensis XP Information System can communicate with other systems
and system components.
The information system provides interfaces and communication options that link
the information system network to other systems and system components inside
and outside the cath lab.
 Dräger Infinity patient monitors
 syngo Dynamics as an alternative reporting system
 A cardiology information system (CIS) or hospital or radiology information sys-
tem (HIS/RIS)
 A departmental material management system
Communication with Dräger Infinity patient monitors
The AXIOM Sensis XP Information System can be connected to a network of
Dräger Infinity patient monitors. This way the AXIOM Sensis XP Information System can receive vital sign trend data from the PreCath, DuringCath, and PostCath
phase and include this information in AXIOM Sensis XP reports.
Note
In order to be able to connect to a Dräger Infinity network:
 The AXIOM Sensis XP Information System must run on a Sensis XP high-
end SIS Server.
 The optional Infinity license must be installed.
We also recommend that when you connect a Dräger Infinity network you do
not register patients locally in Sensis or on Dräger patient monitors. Instead, register patients in a central hospital, radiology, or cardiology information system
(HIS/RIS or CIS) and have both the AXIOM Sensis XP Information System and
the Dräger Infinity patient monitors receive registration data from the HIS/RIS or
CIS as HL7 messages (registration via ADT feed). This strategy helps to avoid patient matching issues.
Network communication overview
Dräger Infinity patient monitors in the cath lab (DuringCath) and in the preparation (PreCath) and recovery (PostCath) area are connected to one another in a network, the Infinity network. The Infinity network communicates with the hospital
network through a gateway. The AXIOM Sensis XP Information System can also
connect to this gateway for data exchange with the Infinity network.
46 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Dräger Infinity Network and connection to the AXIOM Sensis XP Information System
Data flow during an examination
The following describes the typical workflow for an AXIOM Sensis XP study if connection to an Infinity network and vital sign data retrieval has been configured.
 Patient registration on AXIOM Sensis XP
– When a patient is registered on Sensis, the AXIOM Sensis XP Information
System queries the Infinity network when searching this patient.
– Next, the information system retrieves the patient’s vital sign trend data
from the Infinity network and stores this data in its database.
 During an examination (DuringCath)
– During the examination, AXIOM Sensis XP acquires vital sign data from its
own system, displays this data on the real-time monitor, and stores this
information in its database.
– In addition to this, the AXIOM Sensis XP Information System can continue
to collect data from the Infinity patient monitor. This data is also stored in
the information system database. You can view and edit this DuringCath
Infinity vital sign information in Documentation Tool and include it in your
report later on. However, you cannot show Infinity vital sign data on the
AXIOM Sensis XP real-time monitor.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
47 / 456
System Administration
 Closing the study on AXIOM Sensis XP
– When the study is closed on Sensis and if this has been configured, then the
information system continues to collect vital sign trends data from the
patient monitor (PostCath stage).
– Collection of Infinity vital sign data continues until the study is approved in
the AXIOM Sensis XP Information System or until the patient is discharged from the Infinity patient monitor.
 Vital sign trends data in the study report
– If appropriate report templates exist in the AXIOM Sensis XP Information
System, reports created by Report Generator will show a complete vital
sign trends report for your patient (PreCath, DuringCath, PostCath stage).
Data exchanged during the phases of a study
Configuring the communication with Dräger Infinity patient
monitors
Prerequisites
To be able to connect to a Dräger Infinity network, your system must fulfill the following prerequisites:
 The optional Infinity interface license is installed on your system.
 Your information system is installed on a Sensis XP high-end server.
– You cannot install the Infinity interface on an AXIOM Sensis XP Acquisition
System that functions as the SIS Master.
 The Dräger Infinity gateway has already been installed, configured and tested
by the Dräger Service representative.
– A test certificate should be available.
– The Infinity Gateway software version is VF5.
 The Infinity gateway can be accessed over the hospital network, and you know
the user name and password to log on to this gateway.
48 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Interface configuration
(Configuration
Manager)
If your system installation fulfills all these preconditions, you can use the Infinity
Vital Signs tab card of the Configuration Manager to configure data exchange
with the Infinity network.
On this tab card, you perform the following configuration tasks:
 You set up connection to the Infinity gateway.
 You define matching criteria for patient identification.
 You specify during which phases vital sign trend data are to be retrieved as well
as the retrieval interval.
See Defining data transfer from a Dräger Infinity patient monitor 343 .
Clusters (DB Manager)
When these configuration settings have been made, the AXIOM Sensis XP Information System receives Infinity vital signs data and stores this information in the
INFVS system table. To make this information available throughout your AXIOM
Sensis XP Information System, you need to include this database table in your
input and output clusters.
 Input clusters
– Add INFVS to your input clusters so that your users can view and edit the
information in this database table in Documentation Tool.
– See Input clusters 114.
 Output cluster
– Add INFVS to your output cluster definitions (in the cluster definition file
cathcor.clu) to send this information to the HIS/CIS system together with
other study data.
– See Output clusters 115.
Note
There is no need to include INFVS in output report clusters. As a system group
this database table and its data are included in study reports automatically as
soon as you select the Include system groups option in Report Composer.
See Inserting a cluster in a report template 165.
Communication with HIS/RIS or CIS systems
Data exchange with a HIS/RIS (hospital or radiology information system) or a CIS
(cardiology information system) is bidirectional:
 Data import during the PreCath phase
– The AXIOM Sensis XP Information System can receive preregistration data
from a HIS/RIS or CIS.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
49 / 456
System Administration
 Information about patient and study information changes
– The AXIOM Sensis XP Information System receives information about
patient and study information changes from a HIS/RIS or CIS and makes
these changes in its own database.
 Data export after completion of a study
– After all post-processing steps have been completed you can export study
data from the AXIOM Sensis XP Information System to a HIS/RIS or CIS.
– Data export is highly configurable and may range in complexity from sending a study report off automatically by email, to transferring clinical data to
a HIS/CIS for statistical evaluation, or to exporting cost information to the
hospital or cardiology information system.
Data import
Data import from a HIS/RIS or CIS is relevant at various stages of a study:
 PreCath stage
– Depending on your hospital organization, preregistration of a patient for an
examination may have been performed on a HIS/RIS or CIS system rather
than within the AXIOM Sensis XP Information System itself.
– At this stage, the information system can receive information via the data
network in one of these formats: Health Level Seven (HL7), or ASCII flat file.
Note
If the HIS/RIS or CIS communicates with your cath lab via DICOM standard, preregistration data is sent to the AXIOM Sensis XP Information System by way
of one of the AXIOM Sensis XP Acquisition Systems that were configured for
this during system installation. From the AXIOM Sensis XP Information System, you cannot configure DICOM communication and the acquisitions system
platform for DICOM settings is protected by a Siemens Service password.
 Any other stage
– If patient or study information on the HIS/RIS or CIS has changed (for example, the spelling of a patient’s name was corrected).
– The information system receives this type of information as HL7 messages
and will subsequently update the information system database.
HL 7
Note
50 / 456
Health Level Seven (HL7) is a standard for electronic data exchange in healthcare
environments. HL7 uses standardized messages to exchange certain types of information. The AXIOM Sensis XP Information System provides an HL7 interface
that is used to send and receive messages in HL7 2.4 format.
Please contact your authorized local Siemens sales representative for directions
to the HL7 Interface Specification, which is available online.
AXA5-200.640.07.01.02
System Administration
Information System Concepts
The AXIOM Sensis XP Information System HL7 interface accepts incoming messages with patient and study information for scheduled examinations as well as
messages which inform the system about patient or study information changes.
The AXIOM Sensis XP Information System application HL7 Listener is set up to
receive HL7 ADT and ORM messages over a defined TCP/IP communication port.
The AXIOM Sensis XP Information System is “listening” for the following messages:
Transfer data of scheduled patients
 ADTA01 and ADTA04
– Sends preregistered data and checks whether a patient exists in the information system database.
– If not, a new patient and preregistered study is created.
– If so, the data is updated and a new preregistered study is created.
 ADTA05
– Sends pre-admission information about a patient in preparation for the
patient's visit or stay in the healthcare facility .
– If the patient is not already pre-registered in the AXIOM Sensis XP Information System, a new patient and study are created.
– If the patient is already scheduled for examination in the AXIOM Sensis XP
Information System, patient and study data are updated.
Update data that has already been sent
 ADTA08
Delete patient and study
information
 ADTA03, ADTA11, and ADTA23
Changes to patient and
study information
– Sends preregistered data and checks whether a patient exists in the information system database: if so, the patient and study data are updated with
new data (studies with workstatus PostCath are not updated).
– Sends patient information and checks whether the patient exists in the
information system database as a preregistered patient.
– If so, the patient and all associated preregistered studies are deleted.
 ADTA39, ADTA40
– Sends information about merging of patients (for example, if a patient was
listed twice in the sender system, once with their name spelled correctly
and once with incorrect spelling, and the error has been corrected by merging the patient’s records under the patient ID of the correctly spelled name).
– Checks whether these two patient entries exist in the information system
database and merges their records under the correct patient name and ID.
 ADTA46, ADTA47
– Sends information about changes to a patient’s ID, checks whether this
patient exists in the information system database and changes this patient’s
ID accordingly.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
51 / 456
System Administration
 ADTA44, ADTA49
– Sends information about changes to the admission ID (patient account
number in HL7) of a study, checks whether a study with this admission ID
exists in the information system database and corrects it.
Order placement
 ORMO01
– The general order message ORMO01 is used to initiate the transmission of
information about an order. This information includes placing new orders,
cancelation of existing orders, holding, etc. If a preregistered patient has an
existing study without an order number, then this study is updated by this
message, otherwise a new study is created for the patient.
You can change the TCP/IP port through which the HL7 Listener is expecting to
receive HL7 messages and test the connection.
See Communication appendix 245
ASCII flat file
Format and syntax requirements
In addition to HL7 data import the AXIOM Sensis XP Information System is also
capable of receiving preregistration data via ASCII flat files. These ASCII flat files,
which are created by the external sender system, have to fulfill a number of requirements concerning information format and syntax and data transfer so that
the AXIOM Sensis XP Information System can interpret them.
The following patient data attributes can be imported from an ASCII flat file:
patient ID, last name, first name, date of birth, height, weight, sex.
Furthermore, database table information, i.e. data that are to be fed into an existing group in the information system database, can be imported. However, you will
have to observe a certain syntax when you set up data export to an ASCII flat file
on the external hospital or cardiology information system.
See Communication appendix 245
Data transfer
ASCII flat files can either be copied directly into predefined directories on the AXIOM Sensis XP Information System server or the AXIOM Sensis XP Information
System FTP server can be used for the transfer.
See Communication appendix 245
Predefined transfer job
A predefined transfer job called Import preregistered patients via ASCII flat file is
available in the AXIOM Sensis XP Information System for import of preregistration data from a HIS/CIS system via ASCII flat file. This transfer job is processed by
the Export Engine; its settings can be edited in the Communication Manager.
See Data import from a HIS/RIS or CIS system 233
52 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Data and report file export
Whereas data import to the AXIOM Sensis XP Information System requires little
configuration on the AXIOM Sensis XP side, data export is highly configurable.
The primary tool for the configuration of data export jobs is the Communication
Manager. Preparatory tasks will, however, also have to be performed on other
system administration tools.
Where the complexity of export job configuration is concerned, a distinction is
made between export of patient and study data (clinical or cost data, for example)
and the transfer of report files, usually after approval of a study. The transfer of
study report files requires fewer configuration steps than the export of clinical or
cost data from the information system database.
Output clusters (DB
Manager)
The first step in defining a data export job is to determine which data is to be exported. Output clusters are defined in DB Manager for specific export jobs.
An output cluster is a collection of database tables (i.e. groups). The rules for output cluster definition vary slightly depending on which transfer process will use a
cluster.
See Editing clusters 106
Note
Export jobs (Communication Manager)
No cluster definition is required if you plan to export only study report files.
Next, you use the Communication Manager to configure export jobs. An export
job defines:
 Where to export the data in this output cluster (destination or transfer param-
eters)
 The format for exporting the data in this output cluster (job type and job pa-
rameters)
 How and when to export the data grouped in this output cluster (trigger and
distribution method)
See Defining data transfer jobs 193
The following job types are available for the export of data from the information
system database:
 “Create HIS output file”
– ASCII flat file generation, which can be read by an external hospital or cardiology information system.
– When the external system is set up to read HIS data exported from the
AXIOM Sensis XP Information System, syntax rules have to be observed.
See Communication appendix 245
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
53 / 456
System Administration
 “Create HL7 messages”
– The AXIOM Sensis XP Information System HL7 interface supports export
of two HL7 messages: ORUR01 messages for sending clinical information
and DFTP03 messages for sending cost information.
 “Create XML reports”
– Structured ASCII file according to the XML specification to be read by any
system supporting XML data exchange.
These job types are available for sending out study report files:
 “Transfer reports (DOC, RTF, PDF)”
– A study report file can be sent as a Word file (*.doc file), as an *.rtf file, or as
a *.pdf file.
 “Create DICOM reports”
– Exporting a report file to a DICOM workstation is possible via DICOM export
of reports.
– This job type converts the pages of the report document into the frames of a
DICOM XA multiframe image and adds patient and study data as a DICOM
header.
Combined data and report export:
 “Transfer HIS output file, reports, images and waveforms”
– This job makes it possible to export a HIS output file, reports, and images (Xray images, mapping system images, waveform images, and ablation
graphs) for a study as a package of files with a common prefix string added
to each file name.
For starting scripts:
 “Run user-defined BAT file (output file)” and “Run user-defined BAT file (no out-
put file)”
– The Export Engine can also be used to process scripts for data import as
well as data export purposes. You might use this option for advanced communication requirements.
Note
The AXIOM Sensis XP Information System is an open system with an extremely high degree of adaptability to even very advanced requirements. The ability
to incorporate batch files to be processed by the system supports this openness.
You will, however, really need to know what you are doing if you want to use
the Export Engine to run your own script files.
We therefore strongly recommend that you contact the Siemens development
team (via your local sales representative or Siemens Service) if you want to use
the “Run user-defined BAT file (output file)” and “Run user-defined BAT file (no
output file)” options in transfer job definitions.
54 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Export job handling
All export jobs are stored in the central information system database. When the
specified trigger event occurs in the clinical workflow, an export job is processed.
So, depending on the set distribution method, the export job is either placed in the
Export Queue automatically, or the user is prompted to confirm the job in the AXIOM Sensis XP Transfer Agent dialog box first. As soon as the user confirms it the
job is placed in the Export Queue.
The Export Engine
The AXIOM Sensis XP Export Engine is a background application that runs automatically once every minute. The Export Engine checks the Export Queue for
pending export jobs. If it finds any such jobs there, it processes them. This means
that it fetches the data specified in the output cluster from the database, converts
the information to the required format, and transfers it to the specified destination. Or it accesses a report file, converts it as specified, and sends it to a destination.
If no export jobs are currently listed in the Export Queue when the Export Engine
starts running, no data will be exported this time.
Data export to other systems
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
55 / 456
System Administration
syngo Dynamics integration
The AXIOM Sensis XP Information System can be connected to syngo Dynamics.
syngo Dynamics-Sensis system cooperation
In the communication between the two systems, syngo Dynamics can fulfill one
or several of the following functions:
 Network archive
– Sensis recordings systems can use the syngo Dynamics as a PACS.
– Archiving of study data is configured or manually initiated on AXIOM Sensis XP Acquisition System recording systems but not in the AXIOM Sensis
XP Information System.
 Image review workstations
– During post-processing of a study, syngo Dynamics clients can serve image
display and review functions (for example, for X-ray images received from
an Artis system and stored with the Sensis study).
– syngo Dynamics cannot display DICOM waveform objects, however. Use an
AXIOM Sensis XP Post-Processing Workstation to review these study
data.
 Reporting workstations
– Reporting in syngo Dynamics can replace or supplement study report creation options in the AXIOM Sensis XP Information System.
– When you use syngo Dynamics to create a report for a Sensis study, syngo
Dynamics accesses the AXIOM Sensis XP Information System database on
the information system server. syngo Dynamics cannot only read data from
the information system server into its report but can also correct and add to
data stored in the information system database.
Note
To use syngo Dynamics as an image review and reporting workstation for the
AXIOM Sensis XP Information System, the AXIOM Sensis XP Information
System should be installed on a high-end SIS Server.
Configuration of syngo Dynamics-Sensis communication
Communication between syngo Dynamics and the AXIOM Sensis XP cath-lab solution is set up during system installation by Siemens Service. AXIOM Sensis XP
Information System administrators do not have to adapt or configure communication settings. However, if your AXIOM Sensis XP Information System is connected to syngo Dynamics remember the following prerequisites before you start
database tailoring:
56 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
 All syngo Dynamics clients need to be logged off from the AXIOM Sensis XP
Information System before you can call up DB Manager.
 When you have finished SIS database tailoring, contact the syngo Dynamics
system administrators so that they can adapt their system to your changes in
the AXIOM Sensis XP Information System database.
Communication with material management systems
The AXIOM Sensis XP Information System supports two alternatives for material
management.
 The AXIOM Sensis XP Information System component Inventory Manager.
– See AXIOM Sensis XP Operator Manual and Inventory Manager configuration 376 in this system administration manual.
 Connection to a departmental material management system.
Note
In order to be able to connect to a departmental material management system:
 AXIOM Sensis XP Information System must run on a high-end SIS server.
 The optional material management interface license must be installed.
 We recommend that patient registration is performed centrally in a hospital/
radiology or cardiology system (HIS/RIS or CIS) and both the AXIOM Sensis
XP Information System and the material management system are configured to receive registration data from the HIS/RIS or CIS as HL7 messages
(registration via ADT feed).
 If patient registration is performed on Sensis, we recommend that the pa-
tient ID is used for matching patients from Sensis and the material management system.
In software version VC11, the AXIOM Sensis XP Information System supports
connection to the material management systems QSight and Optiflex CL (by
Omnicell).
Data flow between AXIOM Sensis XP Information System and
material management system
In the communication between the AXIOM Sensis XP Information System and a
departmental material management system, two types of data exchange occur.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
57 / 456
System Administration
 Synchronization of inventory lists (transfer of the master file)
– The material management system sends information about available material to the Sensis information system at regular intervals. The send interval
can be scheduled on the material management system. Data transfer usually occurs when no Sensis studies are performed, for example, at night.
– The AXIOM Sensis XP Information System stores this information in the
system group _PRODUCT. Synchronization of this system group with the
most recent master file can be configured on the MMS tab card in Configuration Manager (see: Synchronization of inventory lists 346).
– Users can access the information from the inventory master file to document new material in Documentation Tool. (The material usage table
_VMMUSG contains a reference to the _PRODUCT table.)
– You can view the definition of this system table in the cath.grp file (see
Printing group definition files 101).
Synchronization of inventory list
 Data exchange regarding material usage
– Every time material is checked out for a patient who is scheduled to be
examined or who is currently being examined on a Sensis recording system,
the material management system sends an HL7 message to the AXIOM
Sensis XP Information System. The Sensis information system stores this
information in its database under the patient’s name.
– At any time during a study (or also during the preregistration, postprocessing, or reporting phase), users can access the materials list of a patient in
Documentation Tool and mark material as used or not used, log the time
when the material was used, and add a comment. (If you are working with a
QSight material management system, users can also mark material as
waste).
– If there is temporarily no connection between Sensis and the material management system, users can document the use of material in Documentation Tool manually.
58 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
– Data exchange between the AXIOM Sensis XP Information System and
QSight material management systems is bidirectional. Therefore, information regarding material usage is sent back to the material management system when the study is over. This will tell the material management system
whether the material was actually used (and the patient can be charged for
it), if the material was not used and can be returned to storage, or if material had to be disposed of.
– Data exchange between the AXIOM Sensis XP Information System and
Optiflex CL material management systems is unidirectional. Sensis sends no
material usage data back to the material management system.
Data exchange regarding material usage
HL7 messages used in the data exchange between the systems
The AXIOM Sensis XP Information System and the material management system use HL7 messages to exchange information about available material and material usage.
Inbound HL7 messages
 MFN: synchronization of inventory list (master file)
– This message contains the material management system’s inventory list.
– Content and send interval of this message is configured on the material
management system.
– The AXIOM Sensis XP Information System stores the information sent by
this message in a database table (system group _PRODUCT). The items in
this database table are available as a pick list in the Material Usage table of
the Documentation Tool.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
59 / 456
System Administration
 DFTP03: item usage message from the material management system
– The material management system sends an HL7 message of type DFTP03 to
the AXIOM Sensis XP Information System when a user checks out items
for a patient.
– Inbound DFTP03 messages are configured at the material management system, no configuration is required on the Sensis side.
Outbound message
(QSight only)
 DFTP03: item usage message to the material management system
– The AXIOM Sensis XP Information System also uses DFTP03 messages to
send material usage information back to the material management system.
– This outbound DFTP03 message can be configured in Communication
Manager.
Configuration of material management in the AXIOM Sensis XP
Information System
To set up communication with a material management, the following configuration settings need to be made on AXIOM Sensis XP administration platforms.
All material management systems
Check and adapt the following configuration settings:
 Cath group _VMMUSG
– Since version VC10, the material usage group (_VMMUSG) is available in the
information system. This database table cannot be customized. However,
you can view its definition in the cath.grp file.
– See Printing group definition files 101.
 Input clusters
– Add _VMMUSG to your input clusters so that users can view and complete
the information in this database table in Documentation Tool (see Input
clusters 114).
– You can exclude fields from this group so that the corresponding columns
will not be displayed in Documentation Tool (see Excluding fields from
input clusters 115).
 Master file synchronization
– On the MMS tab card of Configuration Manager, define the time of day
when the master file (inventory list) from the material management system
and the corresponding Sensis system table are to be synchronized.
– See Synchronization of inventory lists 346.
60 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
 Output report cluster
– Either: Add information to your report template as a system group. That is,
select Include system groups for one of the clusters that you drag into your
report template in Report Composer (see Inserting a cluster in a report
template 165). This adds the material usage table to the end of your
report.
– Or: Define a material usage cluster or add _VMMUSG to one of your other
output report clusters (see Editing clusters 106). With this option, you
can control where material usage information will be printed in the report.
However, if you choose this option, do not forget to add _VMMUSG to the
EXSYSGRP cluster as well, or else material usage information is likely to
appear twice in the final study report. See Study reports: exclusion of system groups 113.
QSight material management systems only
If your departmental material management system is a QSight system, also check
and adapt the following settings:
 Output cluster
– If your cluster definition file (cathcor.clu) does not already contain an
HL7MMS output cluster, create this cluster.
– This cluster contains only one database table, the material usage group
_VMMUSG (see Output cluster HL7 MMS message 118).
 Export job (Communication Manager)
– Enable the predefined transfer job Transfer material usage to material
management system. This job transfers information about the use of material back to the QSight material management system. The predefined transfer job is initially disabled. See Transfer material usage to material
management system 241.
The security system
Decisions that affect the health of patients are based on diagnostic data and medical reports. This sensitive data must be protected from unauthorized access and
any access or manipulation of this data must be recorded.
The AXIOM Sensis XP Information System therefore features an advanced security system providing efficient user management and access control as well as
tracing of data access and manipulation. This ensures coverage of regulatory requirements as they exist in various countries.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
61 / 456
System Administration
Security system overview
The AXIOM Sensis XP Information System security system can be freely configured to meet the requirements that apply to your institution and country and to
reflect the organization in your hospital.
Note
The system of user management and auditing described here only applies to the
AXIOM Sensis XP Information System. Access control to the AXIOM Sensis XP
Acquisition System is controlled by a Windows user management that was set
up during system installation.
The AXIOM Sensis XP Information System security system comprises the following components:
User management and
access control
An efficient user management allows you to control access of users to program
functions on the one hand and to patient data on the other hand.
Whenever users wish to access information system tools they are is prompted to
identify themselves by entering their user ID and password (user authentication).
Only with the appropriate user rights will a user be permitted to proceed (user authorization). Each user is therefore identifiable at all times.
Auditing and tracing
data access and manipulation
The AXIOM Sensis XP Information System security system allows the hospital to
define which actions and data manipulations are to be logged in a so-called audit
trail. The resulting log can be archived so that any access as well as manipulations
of patient and study data via the AXIOM Sensis XP Information System applications can be traced at any time.
Screen saver
If a computer with the AXIOM Sensis XP Information System remains unused for
a certain time, it is automatically locked by a screen saver. In order to be able to
resume work on this computer, you need to enter your user ID and password
again. The standard Windows screen saver functionality is used for this. This feature is therefore not described in any more detail here.
User management: key terms and concepts
The AXIOM Sensis XP Information System security system uses a number of key
terms and concepts that you may be familiar with from other user management
systems. Some terms are, however, cath-lab specific.
Key terms
The following list explains the key terms and concepts in the AXIOM Sensis XP Information System security system:
 User account - for user authentication
– See User accounts 63
62 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
 Directory - virtual folder containing patients of a certain group or category
– See Directories 63
 Permission - fine-grained access rights to data in a directory
– See Permissions 64
 User group - grouping users facilitates user management
– See User groups 64
 Role - access rights to certain subsets of program functions
– See Roles 65
 Use case - program functions required to perform a typical task;
predefined unit in role definition
– See Use cases 65
Setting up a user management system
When setting up a user management system from scratch we recommend that
you proceed in a certain order. First read the section Overview of the workflow in
user management definition 66, then refer to the Security Manager 129
for details of the steps involved.
User accounts
Access to AXIOM Sensis XP Information System applications is controlled by
user accounts. This means that unless you are a registered user, you cannot access
the AXIOM Sensis XP Information System.
In the Security Manager, a system administrator can create new users and assign
passwords.
Directories
Data protection requires that patient data be treated confidentially. This means
that only those information system users that are involved in a case should have
the right to access case data. To facilitate the control of access rights to patient
data the AXIOM Sensis XP Information System allows patients to be grouped. A
so-called directory is a virtual container for a subset of patients. The term virtual
container or folder is used here, because in the database a directory is not a physical storage area but an attribute to the patient data.
The directory structure is freely configurable in the AXIOM Sensis XP Information System security system. Directories group patients by performing physician,
for example. This way you can ensure that only performing physicians and their
teams may access the study data of a particular patient. Patients are assigned to
directories in the Patient Explorer on a patient by patient basis.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
63 / 456
System Administration
Permissions
The right to access patient data in a directory does not have to be granted wholesale. The AXIOM Sensis XP Information System security concept permits you to
distinguish what users are permitted to do with the patient data of a directory:
 Select and view data only.
 Insert and create new patient records.
 Update and edit patient and study data.
 Delete patient and study data.
User groups
In large cath labs with several registered users, it would be tedious to assign access rights to patient data on a user-to-user basis. Therefore users can be grouped.
For example, the team of one physician may form the user group: Team_DrX.
The user group structure of your user management system might, for example,
closely reflect the team structure in your hospital.
Access rights to patient data
64 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Roles
Not only the right to access patient data can be controlled by the AXIOM Sensis
XP Information System security system but also access to certain program functions. Access rights to program functions are defined as roles.
The role definition in your hospital might, for example, include the following
roles:
 Reception-desk secretary
– Who will only be allowed to preregister patients (i.e. enter their name,
address and other personal data)
 Nurse
– Who will be allowed to enter and edit any patient data, as well as study and
diagnostic information during an examination, and who will also be permitted to create preliminary study reports.
 Physician
– Who might hold all the access rights to program functions of the nurse but
who will also be allowed to approve study reports.
 System administrator
– Who will not be permitted to manipulate clinical study data but who will
have access to all configuration and system administration functions.
Roles are “packages” of access rights to program functions. The role structure in
your security system should reflect the division of labor in your hospital and cathlab organization rather than the personnel structure and hierarchy.
Use cases
In order to define roles, you assemble so-called use cases. A use case represents a
typical data manipulation task, which requires access to certain program functions.
The use cases in the AXIOM Sensis XP Information System security system are
predefined, you cannot add to or edit use cases. As a system administrator you can
only assemble and reassemble them within your role structure.
Use cases are the units which define roles.
For a list of all predefined use cases, see List of available use cases 142
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
65 / 456
System Administration
Access rights to program functions
Overview of the workflow in user management definition
When setting up a user management system in your hospital from scratch, we recommend the following workflow:
 Directories
– Set up a directory structure, i.e. define categories for patient data.
 User groups
– Establish user groups which reflect the team structure in your cath lab and
assign to them the access rights to directories.
 Roles
– Define the roles which should reflect the division of labor in your cath lab on
a functional level.
 Users
– Register all those cath-lab members as users who will be working with the
AXIOM Sensis XP Information System and assign them to roles and user
groups.
66 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Auditing
The audit trails allows you to record which users access what data and whether
they also edit that data.
These steps are involved in defining and maintaining the audit trail:
Defining what to audit
Note
As some actions are more crucial to data security and confidentiality than others,
it is up to the hospital to decide which actions to record.
When defining which actions to audit, make sure that you observe all legal requirements that apply to your organization and country.
When you define what to audit you list all use cases you wish to be able to trace.
For a list of all predefined use cases, see List of available use cases 142.
Query the audit log
In order to retrieve information from the audit log, you can query it. This way you
can trace actions performed on patient data, for example, by execution time or by
user. Refer to Security Manager 129 for details of the procedures involved in
setting up and managing the audit trail.
Storing the audit log
When you store the audit log the data is exported to a separate database, which
you can access from the file system in order to archive it on CD, for example.
Note
Be sure to observe any legal requirements concerning the archiving and required storage times that apply to your organization and country
Backup and restore
The AXIOM Sensis XP Information System and the AXIOM Sensis XP Acquisition System follow different strategies for backing up, restoring, and archiving
study data.
AXIOM Sensis XP Acquisition System: archiving studies
Necessity to archive
study data
AXIOM Sensis XP (VC11)
An AXIOM Sensis XP Acquisition System is intended to keep study data for a limited time only. Once a case is closed, the acquisition system database expects you
to archive this study and remove the data from its main database. This is, among
other reasons, necessary to clear hard disk space for new examinations.
AXA5-200.640.07.01.02
67 / 456
System Administration
Local or network archive
Acquisition data is usually archived on CD or DVD and moved to a shelf archive for
long-term storage. Archiving to a network archive, such as a syngo Dynamics archive, is also possible. If you need to retrieve archived data, you will have to reimport it into the database of your acquisition system or a post-processing workstation.
Database backup by Siemens Service
Archiving on an acquisition system only stores study data (waveform, event, and
presentation series, as well as X-ray images and DICOM reports, if these are available for a study). Archiving does not store database or system settings. In order to
secure these settings, the acquisition system can be backed up. Database or system settings are stored by Siemens Service, for example, after system installation.
Note
The acquisition system database requires archiving of study data to CD, DVD, or
to a network archive and subsequent removal of these data from its main database. Archiving of study data is performed in the Patient Browser.
A backup of system and database settings of the acquisition system can only be
made by Siemens Service on the syngo Service platform.
AXIOM Sensis XP Information System: database backup
No archiving of study
data required
The AXIOM Sensis XP Information System is itself a long-term archive for study
data, findings, and reports. As study data accumulate over time, the information
system database becomes a knowledge database for your cath-lab, which allows
you to review current as well as historical case data.
No archiving of study data to external archive media is required or intended and
no application program for writing study data to CDs, or DVDs, or to a network archive is therefore available for the AXIOM Sensis XP Information System.
Database backup
Note
The AXIOM Sensis XP Information System database should, however, be backed
up for data security reasons at regular intervals. In the rare case of data loss due
to a system crash or other hardware or software problems, you can then restore
both study data and database settings from such a backup.
The information system database is itself a long-term archive for study data,
findings and reports.
Study data and database settings need to be backed up for data security reasons
only. The Backup Manager provides a platform for backing up the information
system database. Backups should be performed at regular intervals.
68 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
What is backed up?
The backup routine of the information system Backup Manager stores the following data:
 The central information system database
– mismain with the studies of all examined patients
 The master database
– This database stores system-level information for the SQL Server system.
– It records information on all the system databases, user management information, configuration settings, initialization information for the SQL Server,
and so on.
 Report templates
 Database definition files
– Such as dictionary definition files (*.udi files) the group definition files
(rep.grp) and the cluster definition file (cathcor.clu).
 Sensis ACQ-settings and the Sensis SW 2-Settings
 Additionally, reports, X-ray and mapping system images, and waveform imag-
es and ablation graphs can also be selected for backup.
 Statistics Manager local database and settings.
 Inventory Manager local database and settings.
Note
Images require considerable space on your hard disk and in your backups.
We therefore recommend that you use the parameter WF_PIC_EXPIRED (which
you will find on the System Parameters tab card in Configuration Manager) to
delete images for approved studies regularly. This setting will help you to save
hard disk space and keep your backup file sizes small, as images (incl. waveform
images) are only required for inclusion in a report. Images are redundant once
the final report has been created and approved.
Type of backup
The Backup Manager always creates a full (normal) backup of the entire system.
This means that all files and databases are backed up, and not merely those that
have been changed since the last backup.
If you are backing up on tape, backup is done in overwrite mode. This means that
if you create a backup on a tape that already contains data, this data is overwritten
by the new backup.
Backup Manager and
Microsoft Windows
backup utility
AXIOM Sensis XP (VC11)
The Backup Manager is the information system front-end tool that helps you with
selecting what to back up and scheduling backups. For the actual backup process,
Backup Manager uses the Microsoft Windows Backup utility. You will see the
Microsoft Windows Backup screen when you restore a backup and you also use
the Microsoft Windows Backup utility when you format a tape.
AXA5-200.640.07.01.02
69 / 456
System Administration
Planning a backup strategy for the information system
We strongly recommend that you back up the AXIOM Sensis XP Information System database on a regular basis. We also recommend that you define a backup
strategy that ensures that more than one backup copy of your information system
databases is available in case the last backup is lost or corrupted.
Planning a backup strategy involves a number of technical and organizational aspects. Also bear in mind that legal requirements and regulations might apply to
your organization and country.
Backup server
You will always back up to a backup server if your AXIOM Sensis XP Information
System runs on a high-end SIS server. If the information system is installed on a
Sensis XP Master Server or an ACQ Master, backup to a backup server is an option
if your hospital has one or a system of backup servers to which the various departments can send backup files.
When a backup server is available your backup strategy will be very simple: you
schedule a daily backup of your information system databases in Backup Manager and send the backup file to a destination folder on the backup server.
The system administrator of the backup server will ensure that these backup files
are moved to backup media, that several versions are kept, and that these media
are stored in a safe place.
 Talk to the system administrators of the backup server and have them assign
you a backup server and destination folder.
– Make sure that your system has access to this server and folder.
Backup on tape
If your AXIOM Sensis XP Information System runs on a Sensis XP Master Server
on an ACQ Master, you can use the tape drive of the server PC to back up the information system database.
If you are backing up to tape you should also schedule daily backups of your information system databases in the Backup Manager and select tape as a backup destination. Because tapes, like all replaceable media, might be lost or corrupted, it is
essential that you keep several versions of your backups. And as this implies that
tapes need to be exchanged between backups, you will have to make a number of
additional arrangements:
 Appoint a person who is responsible for tape handling and storage.
– Also arrange for a replacement in case this person is on vacation or sick.
 Acquire a set of tapes and decide on a rotation scheme.
 Document your backups.
70 / 456
AXA5-200.640.07.01.02
System Administration
Information System Concepts
Alternative backup
strategies
Backup strategies can have different levels of complexity:
 Simple rotation
– In a simple rotation scheme you have five tapes for the five days of the
week, for example.
– Every Monday you overwrite last Monday’s backup, on Tuesday you overwrite last Tuesday’s backup, and so on.
 Parent - child scheme
– You have five tapes and use one for every day of the week.
– You will, however, store Friday’s tape off-site in a safe place (for example in
a fire-proof safe in the system administrator’s office).
 Grandparent - parent - child scheme
– In this scheme, you have six tapes. One tape for every day of the week.
– Friday’s tape is stored off-site.
– A different tape is used for the last Friday of the month. This tape is also
stored off-site.
Recommendation:
5-day rotation scheme
We recommend that you adopt a medium level of complexity for your backup
strategy. Our suggestion is that, unless a backup server is available, you obtain
five tapes.
You schedule daily backups to tape and use a different tape for every day of the
week. So there will be a Monday’s tape, a Tuesday’s tape, a Wednesday’s tape, a
Thursday’s tape, and a Friday’s tape. We also recommend that you store the Friday’s tape off-site.
This strategy involves exchanging tapes every day and we recommend that you
keep a protocol. In Backup protocol 368 we provide you with a form, which
you may use to document your backups in this 5-day rotation scheme.
Note
The Backup Manager allows you to configure email notification, which will help
you to monitor your backup procedures
See Email notification after backup 361.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
71 / 456
System Administration
72 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Database Manager
DB Manager overview
The Database Manager is a toolbox for database maintenance and database configuration for both AXIOM Sensis XP Information System administrators and Siemens Service.
Overview of functions
This is an overview of the features and tasks that are available in the DB Manager:
Customizing the database
This set of system administration tasks involves:
 Editing dictionaries
 Editing or adding customizable groups
 Editing clusters
 Recompiling the database
Whenever you change definition files do not forget to recompile the information
system database, otherwise your changes will not take effect.
Note
Whenever you change your database definition, for example, when you add
groups or fields to the rep.grp file or edit the cluster definition file cathcor.clu,
make sure you check all your report templates. Your report templates will not be
updated automatically.
See Report Composer 155
Database maintenance
This set of system administration tasks involves:
 Using utilities
 Upgrading the database
Service functions
These database features are not intended for system administrators:
 Indexes
 Procedures
 Database reset
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
73 / 456
System Administration
Key terms and concepts
For information on the key terms and concepts that will help you understand the
basic structure of the information system database refer to The AXIOM Sensis XP
Information System central database 30
Note
A few terms used on the DB Manager user interface differ slightly from the information system terminology used elsewhere. These terms are:
Tailor = DB Manager
tailoring = customizing the information system database
tailor = system administrator, who customizes the system database
report data group = customizable database table (whose entries will eventually
be included in a report)
report data dictionary = dictionaries for both customizable tables (pick lists in
the Documentation Tool) and the AXIOM Sensis XP Acquisition System
cath groups (dictionaries) = static (i.e. non-customizable) database tables or
dictionaries for cath groups
field / field name = used in the context of database table configuration for defining or redefining attributes in tables for data entry.
User interface and basic procedures
The DB Manager user interface consists of these elements:
 Menu bar
 Status line for the display of tool tips
 Info box
74 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Info box
The info box contains information on:
 FILENAMES
– Dictionary definition files have the extension *.udi.
– Customizable database tables are available in the group definition file
rep.grp.
– The cluster definition file of the system is called cathcor.clu.
– Secondary indexes (definition file cathcor.idx) and SQL procedures (definition files with the extension *.sp) should not be modified by system administrators.
 CHANGES
– An asterisk ( * ) in the Changes box indicates that definition files of this category have been modified and the database requires recompilation.
– Running indicates that the database is currently being recompiled.
– OK means that recompilation has been completed and was successful.
– Error indicates that one or more errors occurred during recompilation.
Menu bar
The DB Manager menu has a main menu and several submenus. The menu items
of the main menu as well as those of the submenus appear as buttons. The box to
the very left of this line of menu buttons indicates which menu or submenu you
are currently working in. (This box looks rather like a button itself, but it cannot be
clicked and its label is capitalized.)
If no further submenu exists for a function, a button executes a function directly
or opens a dialog box, for example, for the selection of the definition file you wish
to view, print, or edit.
Use the Quit button in a submenu to move one step up in the menu structure. The
main menu does not contain a Quit button but has the eXit button for closing the
DB Manager toolbox.
Tool tips
Definition file editing
with Notepad
Place the cursor on a tab or menu bar button and let it rest there for a second to
have a tool tip displayed in the status line.
The DB Manager uses the Windows Accessories tool Notepad for editing definition files.
You cannot execute other DB Manager functions while Notepad is open.
All database definition files are ASCII files, but a specific definition syntax has to
be observed for the various available definition file types.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
75 / 456
System Administration
Starting DB Manager
Before you can to start this toolbox, you need to stop all clients logged onto the
AXIOM Sensis XP Information System:
 Exit all other information system configuration tools in your cath lab.
 Ask all users who are currently working at any of the client PCs to log off.
 For syngo Dynamics version 9.5 and higher, use the Terminate Syngo Dynam-
ics button on the Dictionaries tab card in Configuration Manager to log off
syngo Dynamics users.
– See Terminating syngo Dynamics 327.
– Start DB Manager within 5 minutes after clicking Terminate Syngo
Dynamics. After 10 minutes syngo Dynamics clients can reconnect to Sensis.
 Make sure no examinations are currently being performed on any of the con-
nected AXIOM Sensis XP Acquisition Systems.
Note
While the DB Manager window is open, the system will ignore any incoming
HL7 messages (a negative acknowledgment will be sent to the HL7 server).
Logging onto the server PC
You cannot start the DB Manager from any PC other than the information system
server (i.e. the PC with SQL database).
 Log onto the Windows operating system of the server using the administrator’s
account (account with Windows administrator rights to that PC).
Starting DB Manager
 You can only start one instance of this tool.
 From the Windows Start menu, select AXIOM Sensis XP Information System
> Server > DB Manager.
– The AXIOM _Sensis_Database_Manager login screen is displayed:
76 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
 Enter the password for the MIS_ADMIN user account (the information system
“super user” or “super administrator”) and press Return.
– No distinction is made between upper and lower-case letters.
– A message appears that describes the last database modifications and date.
 Press Return to confirm.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
77 / 456
System Administration
Customizing the database
The AXIOM Sensis XP Information System comes with a preconfigured database. Even though this database will most likely meet most of your requirements
right from the start, a number of settings always have to be customized.
In order to determine what changes you want to make in the database configuration we recommend that you look at the current data entry forms (Documentation Tool) and at the predefined reports (Report Composer) and work backward
from this.
Editing dictionaries
 Click Dic in the main menu to display the Dictionaries submenu.
What is a dictionary?
Storage of dictionary
entries in the database
A dictionary is a pick list from which a clinical user can select a predefined database entry in the Documentation Tool or in the AXIOM Sensis XP Acquisition
System.
When a clinical user selects a dictionary entry, what is saved back to the database
table is not the text string he or she picked but the code value of this dictionary
entry.
Therefore you should never delete dictionary entries, except when you are adapting the factory settings immediately after system installation (when no studies
have been performed yet). Moreover you should not overwrite existing directory
entries with new labels (except when correcting typing errors) as this will also affect older records stored in the database.
Note
Do not delete dictionary entries! Do not overwrite dictionary entries!
... except when customizing the information system database right after system
installation, when no studies have been performed yet.
78 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Example
Dr. Brown used to work in your cath lab but now no longer works here.
 Do not delete this name from the physician’s list in pnname.udi.
– If you do, he will no longer be listed as performing physician in all the studies he performed while he was working in your cath lab. In fact, no performing physician will be listed for these studies any longer.
 Do not reuse this entry for the name of a new doctor who has just started work-
ing here.
– Dr. Brown’s old studies would be listed in the database under the name of
the new doctor if you did.
For a better overview and to indicate to users which names should no longer be
selected you can create a “no longer in use” category.
In this example you would create a new category, add it at the end of the personnel dictionary definition file, and move Dr. Brown to that category:
#1, Former personnel
11, Brown, Allen
Database recompilation
Do not forget to recompile the database after you have edited dictionaries or created new dictionary definition files. It is only then that your changes will become
effective.
See Recompiling the database 120.
Syntax check
Whenever you change a dictionary definition file and save and exit it, a syntax
check is performed. If errors are detected during this check you are alerted to the
fact. Always repair these errors immediately and before you run a database recompilation.
Editing a dictionary definition file
Opening a dictionary definition file for editing
 Click Edit.
 Click F1 to be presented with a list of all dictionary definition files that are avail-
able for customization.
– See also Overview of dictionary definition files 86
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
79 / 456
System Administration
 Double-click on a dictionary name to display the file in Notepad.
Header
Dictionary definition
Dictionary contents
80 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Adding a new dictionary entry
 Add a new line to the list of names under a heading.
 Enter a unique code in the form of a number or a string.
– The only prerequisite is that it is not used as a code anywhere else in this
dictionary.
 Add the new name in the way in which you want it to appear in the Documen-
tation Tool pick list.
Note
In the Documentation Tool you can select an item from a dictionary either by
selecting it from the pick list (for example, in the Select From Dictionary or
Search In Dictionary dialog boxes) or by entering its code number.
The latter option is a particulary fast way of selecting dictionary entries:
 Press the Ctrl. key while you enter the code number of a dictionary item.
– The system will fill in the dictionary item text automatically.
Other changes in a dictionary definition
Deleting or overwriting dictionary entries is not permitted, except immediately after system installation, when no studies have yet been performed.
See Storage of dictionary entries in the database 78
For other changes to a dictionary definition file see Syntax for dictionary definition files (*.udi files) 90
Saving changes to a dictionary definition file and running a syntax check
 Select File > Save in the Notepad menu to save your changes.
 Select File > Exit to close Notepad and check the syntax of your changes.
– If the system detects an error, a message is displayed.
 Print out this error message (File > Print), it will help you to repair the error.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
81 / 456
System Administration
Repairing inconsistencies
 Click Edit and select the same dictionary definition file again.
– Notepad opens, displaying the dictionary definition file again.
– This is the last saved version of this file, i.e. the one which contains the syntax error.
 Repair the syntax error.
– See Syntax for dictionary definition files (*.udi files) 90 for that.
Or
 Restore the previous version of this dictionary.
– See Restoring the last version of a dictionary definition file 82
Note
Always repair inconsistencies immediately. Do not try to recompile while syntax
errors still exist.
Restoring the last version of a dictionary definition file
Whenever you change a dictionary definition file (i.e. when you select File > Save
in Notepad) the DB Manager keeps the last version of this file as a backup file.
You can restore this version (and discard recent changes).
Note
DB Manager only keeps one version of a dictionary definition file in the backup
buffer.
 Click Restore to open this submenu.
 Click Print if you want to print out the last saved version of a dictionary defini-
tion file for a manual comparison of the two versions.
 Select the dictionary whose last saved version you want to print.
Or
 Click Compare in this submenu and select the dictionary you have just edited
from the list (F1).
 Press Return in the next dialog box.
– Notepad opens with a list of all differences between the last two versions of
this dictionary definition file.
– The path name ... \BACKUP\... indicates that this is the previous dictionary
version.
82 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
 On the basis of this comparison, decide whether to restore that file version.
 Click Restore in the Restore submenu.
 Display the list of dictionary definition files for which a backup exists (F1).
 Double-click a dictionary definition file to start restoration of the backup ver-
sion of this file.
 Click Quit to close Restore and return to the Dictionary submenu.
Creating a new dictionary
When you change a group definition or add a new group to the database you may
also need to create a new dictionary file.
 Click Edit.
 Type the new dictionary name in the Filename box and press Return.
– Remember that a dictionary name may be max. 6 characters long.
– Notepad opens with a dictionary definition file that is still empty.
Note
Do not open an existing dictionary and expect to be able to “Save as...”.
No “Save as...” procedure exists for the creation of new dictionaries. If you wish
to reuse most of a dictionary definition that already exists, read the tips on copy
and paste below (do not use Save as in the Notepad File menu!)
 Make sure you repeat the dictionary name correctly.
– The dictionary name follows directly after the header and may be maximum
six characters long:
;-----------------------------------------------# NWDICT, ...
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
83 / 456
System Administration
Note
This name is the unique identifier for this dictionary in the system.
It serves as the link between the group (database table) that uses this pick list
and the dictionary file.
 Also enter the rest of your dictionary definition according to the dictionary def-
inition syntax.
– See Syntax for dictionary definition files (*.udi files) 90
 Save your new definition and have it checked for consistency (File > Save; File
> Exit).
Note
It is not before the next database recompilation run that the new dictionary will
actually be created.
Note
Tips on efficient dictionary creation: copy and paste
You can copy sections from an existing dictionary into a new dictionary definition file via the Windows clipboard. Remember that you will have to open the
existing dictionary and copy the relevant section first before you create a new
dictionary file (as you cannot open another instance of Notepad from the DB
Manager while one is already open). Insert the copied section into the mostly
empty definition file as soon as you have created it.
If you wish to create a new dictionary as a copy of an existing one you should
proceed basically as described above. You will however have copied the entire
existing dictionary definition into the clipboard. As soon as you have inserted it
into the new dictionary (overwriting the template suggestions) make sure you
change the dictionary name immediately:
;-----------------------------------------------# NWDICT, ...
The dictionary that will be created in the next recompilation will have this name.
Only this name is relevant for the naming of the new dictionary.
Make other dictionary definition changes as necessary.
Always use copy and paste to copy from an existing dictionary, as no “Save as ...”
procedure exists in the DB Manager for the creation of new dictionary definition
files. Never simply use Save as in the Notepad File menu as this alone will not
create a new dictionary definition file.
84 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Further options for dictionary processing: Print, Cath, Delete,
Mark_all
The Dictionary submenu provides a number of additional functions to help you
with dictionary maintenance.
Print
Printouts of selected or all dictionaries in your system help you collect information
on required entries from your clinical users. Printouts of predefined dictionaries
also assist you with configuration of the information system right after system installation.
 Click Print.
– After clicking Print a dialog box is displayed, prompting you to enter the
number of copies.
 Do not enter a number here, just press Return.
– Notepad opens with the selected dictionary definition file.
 Use the Notepad print function to print the definition file (File > Print).
Cath
The Cath button provides view-only (and print-only) access to system dictionaries
that cannot be customized.
Delete
Only ever delete dictionaries when you are absolutely sure this dictionary is not
referred to in any group (database table). Deleting a dictionary that is used in a
group will result in a serious error in the next database recompilation run.
Note
No warning is issued if you attempt to delete a dictionary that is referred to in a
group (database table).
Therefore the only time this function should be used is during database customization immediately after system installation, if it turns out you will not be using
a dictionary you have created in your group definitions after all.
Mark all
During a normal database recompilation run, only those dictionaries are recompiled whose definition files have been changed since the last database recompilation.
By clicking Mark_all you select all dictionaries for recompilation during the next
database compilation run. You will use this function, for example, when you upgrade the database.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
85 / 456
System Administration
Note
Clicking Mark_all will immediately select all dictionaries. No further dialog box
or system message will be displayed.
If you click Mark_all, database recompilation will take considerably longer than
if you only recompile a few dictionaries.
Overview of dictionary definition files
Two categories exist in the information system database:
 Dictionaries for customizable groups
– These dictionaries serve as pick lists in Documentation Tool tables.
 Dictionaries for the acquisition system
– On startup the AXIOM Sensis XP Acquisition System reads these dictionaries from the information system (or these dictionaries can be imported
without restart with the Import Dictionaries icon on the AXIOM Sensis XP
Configuration Panel).
– These dictionaries serve as pick lists on various occasions during patient registration or in an ongoing study.
Note
Dictionaries for the Patient Registration window might also be configured in
the Patient Configuration window of the Configuration Panel.
Do not, however, use this Patient Configuration window for pick list configuration if you also have an AXIOM Sensis XP Information System installed.
On system restart, your changes would be overwritten by the dictionary files
read from the information system central database.
Dictionaries for the
acquisition system
Note
These are the predefined (factory-set) definition files for dictionaries that are read
by the AXIOM Sensis XP Acquisition System.
Dictionaries for the acquisition system have names starting with nc_..
Never try to delete any of these dictionaries.
86 / 456
Dictionary name
Description
nc_100.udi
Hemodynamic conditions
nc_101.udi
Attributes of Hemodynamic conditions
nc_102.udi
Conditions in electrophysiology
nc_103.udi
Interval event labels
nc_104.udi
ECG signal labels
AXA5-200.640.07.01.02
System Administration
Database Manager
AXIOM Sensis XP (VC11)
Dictionary name
Description
nc_105.udi
Electrophysiology signal labels
nc_106.udi
Beat trigger labels
nc_107.udi
ECG electrode names
nc_108.udi
Stimulation labels
nc_109.udi
Catheter sites in electrophysiology
nc_110.udi
Event labels for 12-lead ECG morphology
nc_111.udi
Event labels for extrastimulus events
nc_112.udi
Event labels for continuous stimulation events
nc_113.udi
Event labels for tachycardia events
nc_114.udi
Event labels for dynamic stimulation events
nc_115.udi
Event labels for bradychardia events
nc_116.udi
Event labels for 12-lead ECG events
nc_117.udi
Event labels for intervals
nc_118.udi
Event labels for snapshots
nc_119.udi
Event labels for waveform events
nc_120.udi
Event labels for ablation events
nc_121.udi
Event labels for text notes
nc_122.udi
Event labels for templates
nc_123.udi
Event labels for printout events
nc_124.udi
Event labels for recordings
nc_125.udi
Event labels for SpO2 events
nc_126.udi
Event labels for NBP events
nc_127.udi
Event labels for HB events
nc_128.udi
Event labels for oxygen consumption events
nc_129.udi
Event labels for oxygen events
nc_130.udi
Event labels for average oxygen events
nc_131.udi
Event labels for cardiac output events
nc_132.udi
Event labels for CO Fick events
nc_133.udi
Event labels for CO thermo events
nc_134.udi
Event labels for CO dye events
nc_135.udi
Event labels for CO angio events
nc_136.udi
Event labels for CO thermo average events
AXA5-200.640.07.01.02
87 / 456
System Administration
Dictionaries for use in
the Documentation
Tool
Note
Dictionary name
Description
nc_137.udi
Event labels for CO dye average events
nc_138.udi
Event labels for CO Angio average events
nc_139.udi
Event labels for respiration events
nc_140.udi
Event labels for pressure events
nc_141.udi
Event labels for hemodynamic sample events
nc_142.udi
Event labels for vital signs
nc_ad.udi
Admitting diagnosis
nc_ist.udi
Institution names
nc_ref.udi
Referring physicians
nc_req.udi
Requesting physicians
nc_wrd.udi
Requesting ward
This is a list of typical predefined (factory-set) dictionary definition files for customizable database tables.
This might or might not be exactly the list of dictionaries you will find in your information system configuration. You might actually find other dictionary definition files as well, or files from this list might be missing.
This is because Siemens Service will most likely have customized your system to
meet your specific requirements during system installation.
88 / 456
Dictionary name
Description
admin.udi
Drug administration method
aetiol.udi
Etiology
a_asit.udi
AHA site
a_site.udi
Coronary site
a_view.udi
View (X-ray)
backlib.udi
Catheterization background
cathet.udi
Catheters
catlib.udi
Catheterization findings
clusts.udi
Study cluster types
comlib.udi
Comments during cath
compli.udi
Complications
AXA5-200.640.07.01.02
System Administration
Database Manager
AXIOM Sensis XP (VC11)
Dictionary name
Description
congen.udi
Congenitals
contr.udi
Contrast medium
corlib.udi
Coronary findings
ctrsit.udi
Coronary sites in CTR
c_acc.udi
Accessibility
c_ahas.udi
AHA stenosis class
c_cflo.udi
Degree of collateral flow
c_curv.udi
Curvature
c_dom.udi
Dominance type
c_ecc.udi
Eccentricity
c_ext.udi
Extent
c_fill.udi
Vessel filling method
c_gra.udi
Graft type
c_graf.udi
Graft heritage
c_int.udi
Treatments
c_shap.udi
Length of Sten.
c_sit.udi
Coronary sites
c_tex1.udi
Text in Heart picture Illustrator
c_tex2.udi
Text in Coronary Tree Illustrator and Heart Picture Illustrator
c_vflo.udi
Vessel flow degree
diagno.udi
Diagnosis
ecclib.udi
Eccocardiography
emeth.udi
Incision methods
epcom.udi
Comments during EP Study
eplib.udi
EP Findings
epproc.udi
EP Procedures
esite.udi
Entry sites
fcolib.udi
Final comments
hetext.udi
Text in Heart Picture Illustrator
iesite.udi
EPCOR sites
interv.udi
Interventions (Conditions attributes)
AXA5-200.640.07.01.02
89 / 456
System Administration
Dictionary name
Description
medica.udi
Medications
nc_map.udi
Mapping dictionaries
nc_sty.udi
Studies
nc_typ.udi
Study type categories
pnname.udi
Personnel
prclib.udi
Operative Procedure
proced.udi
Procedures
reclib.udi
Recommendations
report.udi
Hospital name
reslib.udi
Intervention results
sever.udi
Severity
staff.udi
Function
suppl.udi
Other supplies
valsta.udi
Valve Status
Syntax for dictionary definition files (*.udi files)
Basic rules
See also Syntax examples
 # (hash) - precedes a command line
 ; (semicolon) - precedes a comment line
 , (comma) - separator between parameters
– If a comma is to be used within a dictionary description text where it could
be misinterpreted as a separator the dictionary description has to be placed
in quotation marks (for example “Catheters, EP”)
– If a comma is to be used in a dictionary entry text then a distinction has to
be made between standard dictionaries and dictionaries containing automatic values. In the first case no quotation marks are required (as the system does not expect any further parameters to follow in this line). In the
latter case quotation marks are required.
 Code values for dictionary entries - must be unique within a dictionary.
 Dictionary name - serves as a unique identifier for this dictionary in the sys-
tem. The dictionary name serves as the link between the dictionary and the
field in a group (database table) that refers to this dictionary.
 End each definition line with Return.
– If you forget the Return after the last definition line in the file, the system
will report an error during database recompilation.
90 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Dictionary types
See also Syntax examples
 Standard dictionaries
– Simple pick lists.
 Hierarchical dictionaries
– Large dictionaries are usually organized in a hierarchical way (tree-view)
– Up to three heading levels can be defined.
– These dictionaries are defined by a hierarchical dictionary flag (Yes/No)
– Under the heading levels, dictionary entries are defined in the same manner
as in standard dictionaries (the same syntax applies).
– You can change a non-hierarchical dictionary into a hierarchical one and
vice versa without affecting the stored data.
 Dictionaries containing automatic values
– This type of dictionary selection of an entry in one table field automatically
also enters values in subsequent fields. For example, selecting a catheter in
the Catheter field of the Catheters table automatically also enters the
French size into the table.
– A dictionary is defined as an automatic values dictionary by the parameters
C:n and L:m in the dictionary definition (command) line
(n = the number of automatic values fields; m = max. total length set aside
for the automatic value strings taken together (plus separators))
 Dictionaries containing comment text
– Dictionaries may contain frequently used comment texts.
– These comment texts can contain placeholders or tags for case-specific
information to be completed either manually by clinical users in the Documentation Tool or automatically with data from the information system
database.
– The character ~ in a comment text is a placeholder for manual entry of casespecific information. Clinical users may be expected to fill in a name, for
example, and they can use the Step to ~ command in the Documentation
Tool to jump from placeholder to placeholder.
– For automatic entry of case-specific information in comment texts you can
define so-called embedded query tags.
 Mapping dictionary nc_map.udi
– A special dictionary that maps pick lists in the acquisition system to userdefinable dictionaries which are also used by Documentation Tool.
– nc_map.udi links the pick lists for Performing Physician and Operator in
the Patient Browser of the acquisition system to the dictionary
pnname.udi.
– nc_map.udi also links the selection list for conditions in the Hemodynamics and Electrophysiology application to corresponding lists in the dictionary interv.udi.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
91 / 456
System Administration
Syntax examples
 Standard dictionary example:
1
2
3
4
5
6
# DIAGNO, Dictionary, SI, 4, 32, 16
1, Atrial Situs Solitus
2, Atrial Situs Inversus
3, Atrial Situs Ambiguous
7
8
(1) Dictionary name
– Unique dictionary identifier within the system.
– Must be between 1 and 6 characters long.
– The name that is referred to in the group definition file.
(2) Dictionary description
– Must be between 1 and 24 characters long.
– This is the descriptive text by which a user can identify a dictionary.
– Must be set in quotation marks if it contains a comma (“xy, z”).
(3) Code type
– Describes the type of value, enter one of these options:
SI = small integer (2 bytes used, value ranging from -32767 to + 32767)
C = character string
(4) Code length
– Maximum number of digits or characters in the code.
– If the code type is “C”, then the max. permitted length is 8.
(5) Length of entry text
– Max. number of characters permitted for the dictionary entry text.
– Max. length for normal dictionary entries is 74 characters (the permitted
length for predefined text comments is 4000).
(6) Truncation length (parameter only relevant with Cathcor systems)
Note
For parameters (1) to (6) (dictionary definition parameters), observe the correct
parameter sequence.
(7) Code
– Digits or characters, depending on the code type defined in command line
(see Code type).
– Must be unique within a dictionary description file.
92 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
(8) Dictionary entry text
– Descriptive text of a dictionary entry.
 Hierarchical dictionary example:
1
2
3
# DIAGNO, Diagnosis, SI, 4, 32, 16, Y
#1, General Indications
885, Unstable Angina
540, Coronary Artery Disease
364, Aortic Stenosis
#1, Congenital
#2, Shunts
1004, Ventricular Sepal Defect
...
(1) Heading level
– Level in the tree-view fashion in which the dictionary will be presented to
the clinical user in Documentation Tool.
– # 1 = heading level 1, # 2 = heading level 2, # 3 = heading level 3.
(2) Heading text
– Maximum length = 80 characters.
(3) Hierarchical dictionary flag
– Y (= yes)
 Example for a dictionary containing automatic values:
1
2
# CATHET, Catheters, SI, 4, 32, 18, N, C:2, L:9
1, Judkins, 123, 99451
2, “Pigtail, special”, 128, 99342
3
3, Loop, 167, 99342
4, Judkins, , 99451
5, ...
4
5
6
(1) Number of automatic values
– A dictionary entry definition can contain the dictionary entry plus exactly
the number of automatic values or less. For example, if C:2 then one, two or
no automatic values may follow the catheter description.
(2) Length
– Maximum total length of the automatic value strings taken together (plus
separators).
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
93 / 456
System Administration
(3) Hierarchical dictionary flag
– N (= no)
(4) Dictionary entry text
– If the descriptive text of the dictionary entry is to contain a comma, the text
must be set in quotation marks (“xy,z”) or else the comma will be misinterpreted as a separator between the entry text and the first automatic value
that is to follow.
(5) Automatic value field
– The fields are separated with commas (,).
– Quotation marks must be used if a comma is required in the automatic
value (for example, “128,5”).
(6) If a first or middle automatic value is to be omitted, the syntax for that would
be a blank between two commas.
– If a row contains less than the specified number of automatic values and no
omissions have been defined by “ , , “, then the last value(s) will automatically be omitted.
 Example for a hierarchical dictionary containing comment text:
1
2
3
# COMLIB, Comments during cath, SI, 4, 500, 16, Y
#1, "Dysf., Regurg, Calcif."
1, There is ~ segmental dysfunction.\r\n
There was ~ calcification of the pericardium or valvular saturations noted.
#1, Return after Angioplasty
2, Patient had an angioplasty and had a good angiographic result.\r\n\r\n
He returned this time with recurrence of angina with prolonged pain \
and some new ST-T changes.
4
5
(1) Heading level
(2) Code
(3) Hierarchical dictionary flag
– Y = yes
(4) Line break and related characters
– \ indicates that the text continues in the next line.
– \r\n inserts a line break (carriage return)
– \r\n\r\n inserts an empty line
(5) Predefined comment
– Max. 4000 characters long.
94 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
 Example for a comment text dictionary with case-specific information
# CATLIB, Catheterization findings, SI, 6, 500, 74, Y
1
#1, LV and AO Grams
#2, Left Ventricle
1, LEFT VENTRICULOGRAPHY FINDINGS: The left ventricular \
systolic function in the <%AN_INFO.METHOD%> projection \
was <%AN_INFO.CLVST%>. There was <%AN_INFO.MR%> mitral \
regurgitation. The calculated left ventricular ejection \
fraction was <%AN_INFO.EF%>%.
4
2
3
#2, Hypokinesis LV Gram/0 MR
2, LEFT VENTRICULAR FINDINGS: ~ LV hypokinesis \
was noted in the RAO projection. \
There was no mitral regurgitation. The calculated left \
ventricular ejection fraction was ~%.
(1) Heading level
(2) Code
(3) Embedded query tag
– This tag specifies the group (database table) and field from where to
retrieve the information to be filled in here.
(4) Manual text entry tag
– A “~“ is a placeholder for text to be entered manually by clinical users in the
Documentation Tool.
 Tag syntax for embedded query tags
<%GROUP.text&FIELD1;text&FIELD2|FIELDSEPATRATOR&ROWSEPARATOR|ROWNO,ROWNO%>
1
2
3 45
6 7
8
9
1
1
12
13 14
15
(1) Start tag (<% ... )
(2) Group specification
(3) End the group definition with a full stop (“.”) .
(4) You can include free text in front of a field in your embedded query definition
(for example, <%CA.At &AUTOTIME; the catheter of model &CATHET; was inserted into &SITE; ...).
(5) Separate the text and the field specification with a “&” character.
(6) Field specification
(7) Separate the fields in this list with a semicolon (“;”).
(8) End the field(s) list with a “|” character.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
95 / 456
System Administration
(9) Specify a character that will separate fields (for example, a comma, if no field
separator is specified fields will be separated by a TAB)
(10) End the field separator specification with a “&” character.
(11) Specify a character that will separate rows, if you do not specify a row separator the default is a carriage return or line feed (CrLf).
(12) End the row separator specification with an “|” character.
(13) Specify from which rows values will be read. For example, “2” for second row,
“F” for first row, or “L” for last row.
(14) If you specify several rows separate them with a comma (“,”).
(15) End tag ( ... %>)
 Example of nc_map.udi and corresponding pnname.udi and interv.udi:
– nc_map.udi
# NC_MAP, Mapping PNNAME , SI, 4, 24, 24, Y
# 1 , Performing physician
1, Physicians
2
2, Fellows
1
# 1, Operators
3, Nurses
# 1, Hemo condition attribute
4, Hemo Cond. Attributes
3
# 1, EP condition attribute
5, EP Cond. Attributes
(1) Links to acquisition system
Note
The labels Performing physician, Operators, Hemo condition attribute, and
EP condition attribute must never be changed.
(2) Links to heading in dictionary pnname.udi
– Only the names under the headings “Physicians” and “Fellows” will show up
in the Patient Browser.
Note
These labels must be spelled identically in the dictionaries nc_map.udi and pnname.udi. If you need to change these labels (for example, translate them)
make sure you change them in both dictionaries so that label and spelling are
identical again in nc_map.udi and pnname.udi.
(3) Links to heading in dictionary interv.udi
96 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Note
These labels must be spelled identically in the dictionaries nc_map.udi and interv.udi.
– pnname.udi
# PNNAME, Personnel, SI, 4, 30, 16, Y
# 1, Physicians
1, Robert Smith
2, James Burns
3, Allen Brown
1
# 1, Fellows
11, Ellen Green
12, Fred Newton
# 1, Nurses
21, Sharon Smith
22, James Johnson
(1) Label and spelling must be identical in nc_map.udi and pnname.udi.
– interv.udi
# INTERV, Interventions, SI, 2, 32, 16, Y
#1, Hemo Cond Attributes
1, Root
2, Rest
3, Exercise
4, Post Angio
1
#1, EP Cond Attributes
11, Isoprenaline
12, Atropine
13, Adenosine
4, Heparin
(1) Label and spelling must be identical in nc_map.udi and interv.udi.
Editing or adding customizable groups
 Click Group in the main menu to display the Group submenu.
Groups definition
All customizable database tables are defined in a file called rep.grp. This group
definition file is available for customization in the Group submenu, for one of the
following purposes:
 Adding new groups (new database tables)
 Adding new fields to existing groups
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
97 / 456
System Administration
 Renaming fields
Note
You should, however, always use the “smart rename” function Rename in the
Group submenu for changing field names. Never rename fields with the Edit
command. This would delete all previously entered data in this field.
 Deleting groups and fields
Note
In theory, you can delete groups and fields when editing the group definition
file. You should, however, never delete groups or fields except during the initial customization of your information system, immediately after system installation. Deleting groups or fields will irrevocably delete any data entered here
during a previous study.
If you want to deactivate a group for future use you do not have to delete it, removing it from one or all input clusters is enough. Data of previous examinations is not deleted that way.
See Editing clusters 106
Groups, clusters, report
templates, and study
types
Remember that when you have created a new group, this does not yet make this
database table available for data entry, nor will data of this group be output to a
report. You will first have to assign the new group to clusters:
 Input cluster
– Assign the new group to an existing input cluster.
– Check the study type association of this input cluster.
– See Defining study types 310.
 Output report cluster
– Assign the new group to an existing output report cluster.
– Check all report templates for the associated study type and make sure they
include the new group (add the new group to the cluster tag or delete the
tag and insert it again).
– See Report Composer 155.
 Output cluster
– Also add the new group to an output cluster if you want to have it included
in one of the data export routines defined in your system.
– See Editing clusters 106
Database recompilation
Do not forget to recompile the database after you have edited the group definition
file. It is only then that your changes will become effective.
See Recompiling the database 120
Syntax check
98 / 456
Whenever you change the group definition file and save and exit it, a syntax check
is performed. If errors are detected during this check you are alerted to the fact.
AXA5-200.640.07.01.02
System Administration
Database Manager
Always repair these errors immediately and before you run a database recompilation. This applies to all errors except for those relating to missing dictionaries or
changed dictionary definitions. These “errors” may not actually be errors but simply indicate that your recent dictionary changes have not yet been implemented
in the database, which will be done as soon as you run database recompilation.
Adding groups or fields and redefining field parameters
Opening the group definition file (rep.grp) for editing
 Click Edit.
 Confirm that you want to edit rep.grp in the next dialog box.
– rep.grp is now displayed in Notepad.
Header
Group definition
Field definition
d
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
99 / 456
System Administration
Adding a new group or field or modifying parameters
Observe the Syntax for the group definition file (rep.grp) when adding new
groups or fields to existing groups or when modifying group or field definition parameters.
Note
Never rename field names when you have opened rep.grp for editing with the
Edit command.
Saving changes to rep.grp and performing a syntax check
 Select File > Save in the Notepad menu to save your changes.
 Select File > Exit to close Notepad and to run a syntax check.
– If the system detects an error, a message is displayed.
Note
This check will not inform you if data are irrevocably lost due to your database
definition changes.
Repairing syntax errors
If the syntax check produced an error message, repair these errors immediately:
 Open rep.grp for editing once again and change parameters manually,
– Observe the Syntax for the group definition file (rep.grp) while doing so.
Or
 Restore the last saved version of rep.grp.
– See Restoring the last saved version of rep.grp
Renaming field names in group definitions
 Click Rename to open that submenu.
 Click Edit in the Rename submenu.
 Confirm that you wish to edit field names in the group definition file.
– rep.grp is displayed in Notepad now.
Note
100 / 456
When you now work in Notepad you seem to be able to make all sorts of parameter changes. When you later run a syntax check, however, only field name
changes will be accepted. All other changes will be rejected.
AXA5-200.640.07.01.02
System Administration
Database Manager
 Change the relevant field names.
– Observe the restrictions for field names under Syntax for the group definition file (rep.grp).
– In the next recompilation run, these field names as well as all references to
these fields will be changed in the database (“smart rename”).
 Save your changes and perform a syntax check (File > Save; File > Exit).
Restoring the last saved version of rep.grp
If errors were detected during a rep.grp syntax check you may want to return to
the last saved version of this definition file or at least produce a detailed list of
what you have changed since.
Note
DB Manager only keeps one version of the group definition file in the backup
buffer (version before last File > Save in Notepad).
 Click Restore to open this submenu.
 Click Print in the Restore submenu if you want to print out the last saved ver-
sion of rep.grp for a manual comparison of the two versions.
Or
 Click Compare in this submenu to have the two file versions compared auto-
matically.
 Press Return in the next dialog box to display the comparison file in Notepad.
– Print the file out from here, if you wish (File > Print).
 Decide on the basis of this comparison whether to restore that file version.
 Click Restore to return to the last saved rep.grp version.
 Click Quit to close the Restore and return to the Group submenu.
Printing group definition files
In the Group submenu you can view or print out the definition files for both customizable (rep.grp) and non-customizable (cath.grp) definition files.
Cath
 Use the Cath button to view or print out a definition file of all non-customiz-
able database tables in your information system central database (cath.grp).
– These database tables are filled with data that is automatically transferred
from a recording system to the information system central database during
a study.
– You cannot edit the cath.grp definition file.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
101 / 456
System Administration
Print
Use the Print button if you only want to view or print out the rep.grp file for customizable database tables but do not want to edit it.
 Click Print.
 Select the file you want to print out (F1).
 Press Return in the next dialog box to display the definition file in Notepad.
 Always use the File > Print function in Notepad for the actual printout.
Syntax for the group definition file (rep.grp)
Basic rules
See also Syntax example
 # (hash) - precedes a command line
 ; (semicolon) - precedes a comment line
 , (comma) - separator between parameters
– If a comma is to be used within a group or field description text where it
could be misinterpreted as a separator the description has to be placed in
quotation marks (for example “Angio, site”)
 basic group syntax:
# grpnam, grptxt, grptyp
fldkey, fldnam, fldtyp, fldlen[.flddec], fldtxt, [,flddic]
 The AXIOM Sensis XP Information System can handle a maximum of 400 da-
tabase tables (approx. 190 static system tables and approx. 210 customizable
groups).
– Each group can have a maximum of 38 fields.
– Groups of the group type 4 or 5 must have exactly 1 field (or 2 fields, when
time-stamped).
– A group of the group type 5 must have a dictionary reference.
 Description text in pointed brackets will not be printed in a report (for example,
<DIC>).
 End each definition line with Return.
Note
102 / 456
If you forget the Return after the last definition line in the file, the system will
report an error during database recompilation.
AXA5-200.640.07.01.02
System Administration
Database Manager
Syntax example
1
2
3
# AN, Angio, 3
N, TIM, T, 5, Time <HH:MM>
N, ANGISITE, SI,3, Angio site <DIC>, SITE
N, ANGIDOSE,SF,9.5, Dose (ml)
N, ANGITXT, C, 24, X-ray data
N, CONTRAST, SI,2, Contrast medium <DIC>, CONTR
4
5
6
7
8
9
(1) Group name
– Must be between 1 - 8 characters long
– Must be unique in rep.grp file.
– Must not be a reserved word (see Viewing or printing the reserved words
list 125).
– Must not be modified otherwise all data stored for the group with the old
name will be lost.
(2) Group description text
– Description text the clinical user will see in Documentation Tool.
– Must be 1 - 24 characters long.
(3) Group type
– Group attribute describing formal data entry criteria.
– Group type value may be:
1 = not a repetitive group
2 = repetitive group (at least one key field)
3 = repetitive group (repetition on a sequence number)
4 = free text group
5 = free text group with possibility of retrieving predefined texts
– Modifications can only be as follows: 2 to 3, 4 to 5, or vice versa.
(4) Field key
– Y (yes) or N (no).
– Set to Y to use the field as part of the record access key, which means that
this field is required to make the record unique.
– Do not change this parameter, as this may result in a record not being
unique any longer. Duplicate records will be lost.
(5) Field name
– Must be 1 - 8 characters long.
– Must be unique within group.
– Must not be a reserved word (see Viewing or printing the reserved words
list 125).
– Do not modify this name when you have accessed the rep.grp file with Edit,
or a modification would result in a loss of data. Change only if you have
opened the definition file with Rename.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
103 / 456
System Administration
Special field: automatic
time entry
– The field name AUTOTIME enters the current time automatically when a
new record is created.
Example:
# ME, Medication, 3
N, AUTOTIME, T , 5, Time<HH:MM>
N, MEDICA , SI, 3, Medication <DIC>
(6) Field type
– describes the type of value, enter one of these options:
C = character string
D = date (output format will depend on regional settings)
T = time (output format will depend on regional settings)
I = integer (4 bytes used, value ranging from -2 billion to +2 billion)
SI = small integer (2 bytes used, value ranging from -32767 to +32767)
F = floating point value/decimal value (8 bytes used, value ranging from
-10307 to +10307); see also parameter Field length
SF = small floating point value/decimal value (4 bytes used, value ranging
from -1038 to +1038); see also parameter Field length
See Presentation of float values in reports 105
(7) Field length
– A number from 1 - 74.
– The following table specifies the maximum field lengths:
Group type
1
2
3
Dictionary referenced
8
8
8
Dictionary not referenced
4000
4000
4000
4
5
74
74
74
– If a dictionary is referenced, then the length must be equal to the dictionary
code length (max. 8 characters). A decimal value must be entered here for
field types F and SF, where the value is in the range 1 - (field length - 2).
– A reduction in the field length can result in the loss of characters, as only
the number of characters in the specified field length are stored.
(8) Field description text
– Must be 1 - 24 characters long.
– This is the text clinical users will see in Documentation Tool as a column
header when they fill out the table.
(9) Dictionary name
– If the field relates to a dictionary, then the dictionary name must also be
entered (1 - 6 characters).
– If a dictionary is specified, then the dictionary must exist.
104 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Additional parameter:
range control
A min./max. value range control on integers and floating point fields can be implemented by adding the range at the end of the field definition row.
Example:
# AN, Angio, 3
N, TIM, T, 5, Time<HH:MM>
N, ANGIODOSE, SF, 8.4, Dose (ml),,0.0,9.9
Note that two commas must be inserted before the min./max. values if no dictionary name is given in the field definition.
In the example above, an error message will be displayed on the Documentation
Tool screen if the input value for the field ANGIODOSE is less than 0.0 or more
than 9.9.
Additional parameter:
scope
The information system database handles information from different information
levels:
 Patient level
– This level contains information that applies to all studies of one patient.
 Study level
– This level contains information that applies to one study at a time only.
– Study is the default for all groups that are not explicitly assigned to the
patient scope.
Example for a group of scope patient:
# AD, Address/Phone, 1, patient
N, ADDRESS1, C, 128, Home address
N, HPHONE, C, 24, Home phone no.
N, BPHONE, C, 24, Business phone no.
N, CPHONE, C, 24, Cell phone no.
Note
If you have defined groups of the scope “patient”, do not forget to include them
in your cluster definition.
See Separate input cluster for patient-level groups 114
Presentation of float values in reports
Different rules exist for the output of decimal (float) values of the type F and SF in
study reports:
 SF:
– Values are shown with the number of decimals specified in the field definition. They are also automatically rounded, if necessary.
 F:
– Values are shown with the same number of decimals entered in Documentation Tool. All trailing decimal zeros are truncated
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
105 / 456
System Administration
Example:
 Database definition
...
N, ANGIODOSE, SF, 8.2, Dose (ml)
...
(2)
(3)
(1)
...
N, ANGIODOSE, F, 8.2, Dose (ml)
...
– where (1) = field type; (2) = range control; (3) = field length
 Input in Documentation Tool
99,4509
2,80000
3
 Output in the study report
99,459
2,8
3
99,45
2,80
3,00
Editing clusters
 Click Cluster in the main menu to display the Cluster submenu.
What is a cluster?
Cluster types
Clustering is a means of grouping database tables (groups) for data input and output purposes.
The information system distinguishes between three types of clusters:
 Input clusters
– These clusters present groups for data input in the Documentation Tool.
 Output clusters
– These clusters define which groups are to be output to another system (data
export).
 Output report clusters
– These clusters define which customizable groups are to be made available
for report generation.
 System clusters
– These clusters define mandatory and requested groups for data input in the
Documentation Tool.
106 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Configuration workflow
Clustering groups is an intermediate step in the definition of data input and output paths. Defining a cluster of one type or another is never an end in itself. Other
configuration steps are always required, these involve other tools of DB Manager
as well as other applications in the AXIOM Sensis XP Information System administration package.
Data input
Adding a new data input table for one of the study types available in your AXIOM
Sensis XP application involves:
 Defining a new group
– Editing or adding customizable groups 97
 Adding the new group to an input cluster.
Or
 Creating a new input cluster for this and other new groups you just created.
 Adding the new input cluster to the relevant study type.
– Only this enables clinical users to input data in this new group at all.
– See Defining study types 310
Data export
Creating a new group whose data will eventually be exported to another system
(for example, a HIS/RIS) basically involves these steps:
 Creating the new group, adding it to an input cluster, and making sure this in-
put cluster is assigned to a study type so that data can be input at all.
 Adding the new group to an output cluster.
Or
 Defining a new output cluster for a specific data export routine.
– Refer to the group definition file rep.grp for an overview of customizable
database tables available for data export.
– Refer to the list of Cath groups for an overview of system groups (non-customizable groups) which may also be included in output clusters.
See Printing group definition files 101
And
 Defining a data output configuration that will export this output cluster to a
target destination when a specified trigger event occurs.
– See Defining data transfer jobs 193
Output of data to a study
report
To make sure the data for which you have just created a group also appears in the
study report, you must perform the following steps:
 Create the new group, adding it to an input cluster and making sure this input
cluster is assigned to a study type so that data can be input at all.
 Add the new group to an existing output report cluster.
Or
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
107 / 456
System Administration
 Create a new output report cluster for this and other groups you just created.
And
 Check all report templates are assigned to the relevant study type and:
– include the new output report cluster, or
– check the tag for the existing output report cluster in all report templates for
this study type, or
– add the new group name to the group list in the tag, or delete the output
report cluster tag from the report template and insert it again (this time the
new group will be included in the tag definition automatically.)
Cluster adaptation after system upgrades
System upgrades as a rule introduce new database tables (system groups) to the
information system database. For example, XRAYBSUM, the database table that
stores accumulated bi-plane X-ray data, was was added with the VC03A update.
These new groups need to be added to your output clusters and output report
clusters so that the infomation stored in these database tables can be exported to
other systems or included in your reports.
Database recompilation
Do not forget to recompile the database after you have edited the cluster definition file. Only then will your changes become effective.
See Recompiling the database 120
Defining or redefining clusters
To open the cluster definition file (cathcor.clu) for editing:
 Click Edit and confirm that you want to edit cathcor.clu in the next dialog box.
– cathcor.clu is now displayed in Notepad.
108 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Header
Cluster definition
Included group
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
109 / 456
System Administration
Adding a new cluster or modifying cluster definition
Observe the Syntax for the cluster definition file (cathcor.clu) when adding new
clusters or regrouping clusters.
Note
If you want to change the order in which input clusters are presented in the Documentation Tool, do this by rearranging the cluster list on the Study types tab
card of the Configuration Manager.
See Defining study types 310
Note
If you delete an input cluster that is still assigned to a study type this cluster and
the groups it used to contain are no longer presented to the clinical user for data
entry in Documentation Tool.
You should not delete output clusters unless you also remove the data export
routine (Communication Manager) they were created for.
Saving changes to cathcor.clu
 Select File > Save in the Notepad menu to save your changes.
 Select File > Exit to close Notepad.
Note
No syntax check is performed for the cluster definition file when you exit Notepad.
Restoring the last saved version of cathcor.clu
DB Manager keeps the last saved version of all definition files in a buffer memory.
You can restore this file in order to discard recent changes.
Note
DB Manager only keeps one version of the cluster definition file in the backup
buffer (version before last File > Save in Notepad).
 Click Restore to open this submenu.
 Click Print in the Restore submenu if you want to print out the last saved ver-
sion of cathcor.clu for a manual comparison of the two versions.
Or
 Click Compare in this submenu to have the two file versions compared auto-
matically.
110 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
 Press Return in the next dialog box.
– The comparison file is displayed in Notepad.
 Use the Notepad print functionality (File > Print) to print out the comparison
file, if you wish.
 On the basis of this comparison decide whether to restore that file version.
 Click Restore to return to the last saved cathcor.clu version.
 Click Quit to close the Restore and return to the Cluster submenu.
Printing the cluster definition file
 Use the Print button in the Cluster submenu to view or print out the current
cluster definition file.
Note
Having a printed version of the cluster definition file at hand is very useful when
configuring report templates in the Report Composer.
Syntax for the cluster definition file (cathcor.clu)
Basic rules
See also Syntax example
 # (hash) - precedes a command line
 ; (semicolon) - precedes a comment line
 , (comma) - separator between parameters
– If a comma is to be used within a cluster description text where it could be
misinterpreted as a separator, the description must placed in quotation
marks (for example “Conclusions, general”)
 A maximum of 100 clusters can be defined.
See also Additional rules and recommendations 112
 End each definition line with Return.
Note
AXIOM Sensis XP (VC11)
If you forget the Return after the last definition line in the file, the system will
report an error during database recompilation.
AXA5-200.640.07.01.02
111 / 456
System Administration
Syntax example
1
2
3
# I, CONCLUS, Conclusions
; Hemodynamic Results
HT
; Angiographic Results
AR
; Diagnosis
DI
; Comments
CC
# OR, PRECATH, Pre-Cath Data
Groups
; Personnel
PN
; Premedication
PM
; Indications
CD
4
(1) Cluster type
– I = input cluster
– O = output cluster
– OR = output report cluster
– S = system cluster
(2) Cluster name
– Must be 1 - 8 characters long.
– The cluster name must be unique within the cluster definition file.
(3) Cluster description text
– Must be 1 - 24 characters long.
(4) Included group
– Name of an included group.
Additional rules and
recommendations
Aside from these basic cluster definition rules a number of specific rules and requirements exist for individual clusters and cluster types.
System clusters
Data input: mandatory
and requested fields
In the Documentation Tool a number of tables contain mandatory information
while others contain information that users are only recommended to complete.
Mandatory and recommended fields are highlighted by red (mandatory) and yellow (requested) exclamation marks. If users fail to fill out all mandatory tables and
table cells they are alerted to this fact when they try to exit the Documentation
Tool.
The Documentation Tool helps a user fill in this information quickly by offering a
means of jumping from one mandatory or requested table to the next, skipping
any voluntary tables in between.
112 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Mandatory and requested fields are implemented in the cluster definition as system clusters with predefined names (MANDACLU and REQCLU). These clusters include a complete list of all mandatory and all requested tables and fields
throughout the entire database.
The MANDACLU and REQCLU clusters are used by the Documentation Tool to
map the corresponding fields in the tables of the various input clusters associated
with a study type as mandatory or requested fields.
Syntax for MANDACLU and REQCLU:
#S, MANDACLU, Mandatory fields
Groupname 1, Fieldname1, Fieldname2 ...
Groupname 2, Fieldname1, Fieldname2 ...
#S, REQCLU, Requested fields
Groupname 3, Fieldname1, Fieldname2 ...
Groupname 4, Fieldname1, Fieldname2 ...
Note
Study reports: exclusion
of system groups
These clusters must be system clusters and that their names are predefined
(i.e. the names cannot be changed).
When you create a report template in the Report Composer you can choose to include or exclude system groups by checking the Include system groups box
when you insert one OR (output report) cluster in your report, or by unchecking
this box for all your OR clusters.
See also Inserting a cluster in a report template 165; Tag syntax overview
181
If you choose to include system groups this will show all the data collected or calculated during the examination. If you do not want to show all this data in your
report but data from selected system groups only, you will add the system groups
you do not want to show in your reports to the Excluded System Groups cluster
in your cluster definition file.
The system cluster EXSYSGRP is part of the factory default cluster definition file. It
lists all system groups. However, these system groups are commented out. This
means that by default no system groups are excluded. If you actually want to exclude one or several of the groups listed here, remove the semicolon in front of
these groups.
1. Example: factory-default definition, no exclusion
#S, EXSYSGRP, Excluded System Groups
; Angioplasty timer
;;T_APLAST
; Valvuloplasty timer
;;T_VPLAST
; Count up timer
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
113 / 456
System Administration
;;T_CNTUP
; Count down timer
;;T_CNTDWN
...
If you include system groups in a report template now, data from all system
groups mentioned here (T_APLAST, T_VPLAST, T_CNTUP, T_CNTDWN) will be
shown in the report.
2. Example: modified definition, certain groups are excluded
#S, EXSYSGRP, Excluded System Groups
; Angioplasty timer
;;T_APLAST
; Valvuloplasty timer
;;T_VPLAST
; Count up timer
T_CNTUP
; Count down timer
T_CNTDWN
...
If you include system groups in a report template now, angioplasty timer events
and valvuloplasty timer event data (T_APLAST, T_VPLAST) will be shown in your report, but normal count up or count down timer event data (T_CNTUP, T_CNTDWN)
will not be shown.
Note
Excluding a system group by the method described here will remove this group
from all reports that are created in your cath lab in the future. You cannot exclude individual system groups from specific report templates only.
Input clusters
Separate input cluster
for patient-level groups
If you have defined groups of the scope “patient”, do not forget to create a separate input cluster for them. This ensures that patient-level groups are set apart
from study-related information in the Documentation Tool. It also facilitates reuse of these database tables in all of your study types.
Syntax example:
#I, PATDATA, Patient-related data
;Address/Phone
AD
See also Additional parameter: scope 105
114 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Note
Do not forget to add this input cluster to your study types.
See Defining study types 310
Excluding fields from input clusters
Note
When defining input clusters you can specify which fields you want to exclude
from data input. A field that has been excluded from data input is not shown in
the Documentation Tool, and users cannot enter data.
Excluding a field from one input cluster automatically excludes it from all other
input clusters as well.
Syntax example:
#I, FLOWSH, Flowsheet
;Personnel
PN, STAFF
In this example, the database table Personnel is available for data input in study
types that contain the input cluster Flowsheet but the field (column) Staff is hidden. In fact, with the above cluster definition, Staff is never shown in the Documentation Tool, irrespective of the study type that has been selected.
Output clusters
Output clusters: including and excluding fields
When defining an output cluster you may specify which fields of a group you want
to output in this cluster.
For example:
#O, CLUNAME
CA, AUTOTIME, CATHETER
This will include only the fields AUTOTIME and CATHETER from the CA (catheters)
group in the data output later on. This definition also means that no other information that might be stored in the catheters group will be output (for example,
catheter length, French size, removal time, vendor, and so on).
Note
Specifying fields from a database table to be included in a cluster and excluding
non-specified fields from a cluster (inclusion method) only works for most output and the system clusters.
For specific clusters (HIS transfer) and for output report clusters a different
rule applies (exclusion method).
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
115 / 456
System Administration
System groups in output
clusters
Output clusters may include both customizable groups (and their fields) and system (non-customizable) database tables.
For example, the default output cluster for HL7 ORU messages includes:
# O, HL7ORU, HL7 ORU message
...
; Pressure Values
PV
; Saturations
SA
; Ventricular Data
VD
; Valve Gradients
VG
...
; Personnel
PN
; Indications
CD
...
The first set of groups are taken from the non-customizable database tables,
which are created and filled automatically by the system during a study.
The second set of groups are customizable database tables, which are defined in
the rep.grp definition file. These groups receive their data through data input in
the Documentation Tool, before, during, or after a study.
Refer to Overview of system groups available for data export 273 for a complete list of all system groups and fields available for data output.
Output cluster HIS transfer
Note
The factory default database settings include an output cluster that has been specifically defined for data transfer from the information system to a HIS/RIS or CIS
via ASCII flat file. This cluster is called HIS transfer.
Use the HIS transfer output cluster exclusively for transfer jobs of the job type
HIS transfer in the Communication Manager, because different syntax rules
apply for this cluster.
 If the cluster is left empty, all data will be exported for the study.
 If tables are listed, only these tables will be included.
 If single field names are listed after the group name, these will be excluded.
 The tables PI, ID, PD will always be included.
 Default HIS transfer cluster definition in cathcor.clu:
116 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
;-----------------------------------------------------;Output cluster containing all groups to be exported to HIS
;NOTE: An empty cluster implies all groups are transferred
++++++++++++++++++++++++++++++++++++++
# O, TRANSFER, HIS transfer
Note
This syntax where an empty cluster implies that all groups are transferred only
applies to this particular HIS transfer data export.
 Changing the definition of HIS transfer: adding groups
If you alter the HIS transfer definition and list groups, then only these listed groups
will be sent in the HIS transfer job.
# O, TRANSFER, HIS transfer
CA
Here only information from a number of standard database tables (data that identifies the patient and study) and the CA (catheters) group is included in the cluster.
All other groups, which would be included if no group were listed, will be excluded
now.
 Changing the definition of HIS transfer: adding groups and fields
If you alter the HIS transfer definition and list groups and fields, this will have the
following effect: Only the listed groups will be sent. All fields from the listed
groups are sent, except the listed fields.
#O, TRANSFER, HIS transfer
CA, COST, CHARGE
Here only information from standard database tables (data that identifies the patient and study) and the database table CA (catheters) will be sent. From the CA
table the fields COST and CHARGE will, however, be excluded.
Output cluster HL7
DFTP03 message
Another default output cluster in the cluster definition file is the HL7 DFTP03 message cluster for transfer of cost information to a HIS/RIS or CIS system.
# O, DFTP03, HL7 DFTP03 message
PM, PREMED
CA, CATHETER
ME, MEDICA
PR, PROCEDUR
DI, DIAGNOS
For this cluster some special rules and requirements exist:
 For each table in the cluster one field must be specified.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
117 / 456
System Administration
 The text entry from this field will be sent in the HL7 message.
– For example, the name of the catheter in the catheter table will be sent in
this HL7 message.
Note
Output cluster HL7 MMS
message
These requirements apply only to output clusters that are to be sent in an HL7
DFTP03 message.
If your cath lab uses QSight for material management, this cluster needs to be defined so that information about material usage can be sent back to the material
management system.
# O, HL7MMS, HL7 MMS message
_VMMUSG
This cluster contains only one group, the material usage group. The cluster definition neither requires nor allows specification of any fields in this group.
Output clusters for Statistics Manager
If you do not want to make your entire information system database available for
statistical evaluation with Statistics Manager there are two strategies you can
choose from: an inclusion strategy and an exclusion strategy. Both strategies require that you define an output cluster and list either the groups you want to enable for database queries, or you list the groups you want to exclude from
database queries.
 Output cluster QWS
– Listing only those groups that you want to allow users to analyze with Statistics Manager makes sense if you want to enable only relatively few
groups for statistical analysis.
– A cluster named QWS exists in the factory-defined cluster definition file. By
default, this cluster is empty.
;+++++++++++++++++++++++++++++++++++++++++++++++++++++++
;
;
;
;
QWS cluster - Groups added in the QWS Cluster will be the only ones
displayed on the Statistics Manager screen.
An empty or commented out cluster implies all Sensis
database groups will be displayed.
;+++++++++++++++++++++++++++++++++++++++++++++++++++++++
# O, QWS, QWS output cluster
 Add the groups you want to enable for querying to this cluster.
118 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
 Output cluster: QWS's disabled groups
– If you want to allow statistical queries in the majority of your database
tables and want to exclude only a few groups it is easier to list only the
groups you want to exclude.
– You use the predefined cluster QWSEXCL to exclude groups.
;+++++++++++++++++++++++++++++++++++++++++++++++++++++++
;The QWSEXCL cluster defines the list of groups that shall not be available when
defining new search criteria with the AXIOM Sensis XP Statistics Manager.
;+++++++++++++++++++++++++++++++++++++++++++++++++++++++
# O, QWSEXCL, QWS's disabled groups
; Patient file creation id
A_PF
; ANCOR Patient data
A_PD
; Procedure data
A_PR
...
In the above example the groups A_PR, A_PD, and A_PR are not available in Statistics Manager.
Output report clusters
Exclusion of fields for
output report clusters
In an output report cluster you can define that certain fields from a group are not
to be output in the study report.
# OR, DURCATH, During-Cath Data Groups
;
During-Cath Data Groups
; Procedure
PR, COST
If a user inserts the cluster DuringCath Groups in a study report template, all information from the Procedure group except the COST field will be shown and printed
in the study report based on this template.
Note
You may also use this option to exclude fields of lesser importance in very large
groups from output in a study report. This helps to control the table width in very
large groups.
See also Formatting clusters 166
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
119 / 456
System Administration
Recompiling the database
After editing definition files, do not forget to recompile the database. Only then
will your changes become effective.
Asterisks ( * ) in the Changes box reminds you that recent changes exist for these
definition file types and that the database has not yet been recompiled.
Note
Only start recompilation when the syntax checks of the dictionary and group
definition files have not reported any errors.
Running a database recompilation
 Click Run to open this submenu.
 Click Continue to start database recompilation.
– Depending on how many dictionaries you are recompiling this may take a
few minutes.
– During recompilation a message is displayed. The message disappears as
soon as recompilation is complete.
– If problems occur during recompilation, “Error” will be displayed under the
Changes box of the main screen info box.
Note
If an error is reported during database recompilation make sure you repair it immediately.
Do not exit the DB Manager and do not try to run any AXIOM Sensis XP Information System application programs while errors still exist in the database.
Repairing errors
If an error occurred during database recompilation, eliminate the cause of this error immediately. Use the information the DB Manager provides concerning
where to search for the error.
 Report data dictionaries
– Open the dictionaries you have changed since the last database recompilation for editing one after another.
– Save the dictionary definition file and exit Notepad.
– A syntax check will be run and syntax errors will be reported.
 Repair these errors.
See Syntax for dictionary definition files (*.udi files) 90
120 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
 Report data groups
– Open the rep.grp file for editing.
– Save the rep.grp file and exit Notepad.
– A syntax check is run on rep.grp and a message listing all syntax errors
appears.
 Repair these errors.
See Syntax for the group definition file (rep.grp) 102
 Clusters
– Open the cathcor.clu file for editing.
– No syntax check is available for cathcor.clu.
 Compare the file with the cluster definition syntax rules.
See Syntax for the cluster definition file (cathcor.clu) 111
 Secondary indices and SQL procedures
– You are not supposed to make any changes in this definition and these
script files.
 Contact Siemens Service if errors occur in these files during database recompi-
lation.
Consistency check
Whenever you exit DB Manager, a consistency check of the information system
database is run. If the database consistency check detects any inconsistencies in
the database always make sure you correct them immediately.
Do not attempt to run any AXIOM Sensis XP Information System application
programs while database inconsistencies still exist. This might result in program
failure and loss of data.
Running the database consistency check
 Select eXit in the DB Manager main menu.
– If you have changed dictionary, group, or cluster definition files since the
last database recompilation, a message informs you that modified definition
files exist.
– However, this message is just a reminder that your latest changes have not
yet become effective in the database. It is not related to the database consistency check that starts now.
 Press Return to start the database consistency check.
– If inconsistencies are detected, the Notepad will open with a list of them.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
121 / 456
System Administration
 Print out the error log (File > Print).
– This will help you with repairing inconsistencies later on.
 Close Notepad (File > Exit).
– An info box warns you that the consistency check has failed.
 Press Esc to return to the DB Manager and start repairing the inconsistencies
listed in your printout.
– Do not press Return in the info box, as this will close DB Manager.
Repairing inconsistencies
Depending on how many changes you have made since you last ran a consistency
check successfully, you can use one of these methods to correct these inconsistencies:
 Restore the dictionary definition file or group or cluster definition file to what
it was before your last editing session.
See Restoring the last version of a dictionary definition file 82, Restoring the
last saved version of rep.grp 101, and Restoring the last saved version of cathcor.clu 110
Note
Only one version, i.e. the last saved version of these definition files, is still available.
Or
 Open the relevant definition file (*.udi, rep.grp, or cathcor.clu file) for editing.
See Editing a dictionary definition file 79, Adding groups or fields and redefining field parameters 99, and Defining or redefining clusters 108
 Correct those lines in the definition files that cause the inconsistencies.
– Use the printout of the inconsistencies message to identify these lines.
 Run a database recompilation.
 Run the consistency check again.
Note
If you are unable to correct database inconsistencies, call Siemens Service.
Do not attempt to run AXIOM Sensis XP Information System application programs or start an examination while database inconsistencies still exist.
122 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Database maintenance
Using utilities
 Click Util to open the Utilities submenu.
Viewing, printing or clearing log files
 Click Log in the Utilities menu to open the Log submenu.
 Select Session for displaying or printing a log file of all your activities since you
started up DB Manager.
 Select History to display or print a log file of all activities since system installa-
tion, database reset, or since you last cleared this history file.
 Select Clear to reset the History file (i.e. clear all previous entries and start a
new list of DB Manager activities from now on).
Viewing or printing a list of all factory-defined database definition files
 Click the Dir button in the Utilities submenu.
– A list of all factory-defined database definition files is displayed in Notepad
(or printed out).
– This list does not consider your own database definition files or your
changes to database definition files, it simply lists factory settings.
Exchanging database definition files via floppy disk
 Make sure you insert an empty floppy disk into your disk drive.
 Also make sure the floppy is not damaged.
 Click Floppy to open the Floppy submenu.
 Click Store to copy all dictionary definition files to a floppy disk.
 Open the Windows Explorer and C: \ MIS \ dbconfig \ user directory.
 Select all *.grp (group definition files) amd *.clu (cluster definition files).
 Copy these files to the floppy disk as well.
 On the target system, copy all files from the floppy disk to the C: \ MIS \ dbcon-
fig \ user directory.
Note
AXIOM Sensis XP (VC11)
Remember to recompile the database after you have loaded database definition
files from floppy disk.
AXA5-200.640.07.01.02
123 / 456
System Administration
Note
What the Store on floppy and Load from floppy functions actually do is copy
all dictionary definition files from a predefined directory on your hard disk onto
a floppy disk or vice versa.
You use Util > Floppy > Store or Load if you want to exchange all dictionary definition files between two systems.
If your system is not equipped with floppy drive, or if you only want to copy one
file or selected definition files via floppy disk you can do so using the Windows
file system.
 Open the Windows Explorer.
 Open the directory C: \ MIS \ dbconfig \ user.
– Here you find all database definition files.
– You can copy one or several files either via floppy or via the Windows network from C: \ MIS \ dbconfig \ user of the source system to the same
directory on the target system.
 Open DB Manager on the target system, click Dic to open the Dictionaries
submenu and click Mark_all to force recompilation of all dictionary definition files.
 Recompile the database to make your changes become effective in this data-
base.
“Not enough space on floppy” message
If a very large number of dictionaries has been defined on your system you might
not be able to copy them onto a floppy disk. In this case a message box opens stating that there is “Not enough space on floppy”.
This indicates that either there is not enough disk space on your floppy disk, or
that you are attempting to copy too many files (max. 233 files).
 Use a USB stick instead of a floppy disk to exchange database definition files in
this case.
Exchanging database definition files via USB stick
 Open the Windows Explorer and C: \ MIS \ dbconfig \ user directory.
 Select all dictionary files.
 Use the Windows copy-and-paste function to copy these files to USB stick.
 Copy the files to the C: \ MIS \ dbconfig \ user directory of your target system.
 Open DB Manager on the target system.
124 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
 Click Dic to open the Dictionaries submenu and click Mark_all to force recom-
pilation of all dictionary definition files.
 Recompile the database to make your changes become effective in this data-
base.
Viewing or printing the reserved words list
In the group definition syntax certain words must not be used as group or file
names. These words are reserved for special use by the Microsoft SQL Server.
 Click the Reserved button in the Utilities submenu to display or print out a list
of these reserved words (use the Notepad print function to print the list).
Service functions
The DB Manager user interface allows access to a number of functions that are
not intended for use by system administrators.
Note
These functions are intended for Siemens Service only.
Upgrading the database
Whenever the AXIOM Sensis XP system is updated to a new software version the
information system database needs to be upgraded as well. Upgrading will add or
update system definition files and recompile the database.
When upgrading the database you will not lose:
 Patient or study data stored in the database.
 Changes you made to the definition of dictionaries, database tables, or clus-
ters.
 User management and security settings.
Nevertheless, always back up the database before you start upgrading.
 Click Upgrade in the main menu.
– Detailed upgrade instructions will now be displayed in Notepad.
 Print these instructions (File > Print) before you exit Notepad (File > Exit).
Note
AXIOM Sensis XP (VC11)
These instructions might vary slightly for each software upgrade, therefore
make sure you read them carefully every time you need to upgrade.
AXA5-200.640.07.01.02
125 / 456
System Administration
 Follow these instructions step by step.
Note
When upgrading always use the same language and country settings that the
database was originally installed with.
You might not change the setup now.
Indexes
As the database becomes larger over time, selective retrieval becomes slower.
Secondary indexes for selected fields help reduce search times.
The AXIOM Sensis XP Information System database comes with a number of
predefined secondary indexes. You should not change the definition file, but you
can view or print it.
 Click Ix to open the Index submenu.
 Use Print to view or print out the index definition file.
Procedures
Stored SQL procedures are precompiled collections of SQL statements stored under a name and processed together.
The AXIOM Sensis XP Information System supplies stored procedures for managing the SQL Server and displaying information about databases and users.
You cannot edit these procedure definitions but you can view or print them for
your information.
 Click Procedure to open this submenu.
 Use Print sql and Print cmd to display or print out this information.
Note
Do not use the Mark sql or Mark cmd buttons. These buttons are intended for
use by Siemens Service only.
Database reset
Resetting the database is an option that will only ever be necessary in the course
of the system installation process and will only ever be performed by Siemens Service.
126 / 456
AXA5-200.640.07.01.02
System Administration
Database Manager
Do not reset the database at any other time as resetting the database means that:
 You will irrevocably lose all patient and study data.
 You will irrevocably lose any changes you made to the definition of dictionar-
ies, groups, or clusters.
 You will lose any settings in the Security Manager.
– These settings will, however, be documented in a file
(C: \ MIS \ dbconfig \ users_setup.txt).
Database reset is started with the rEset button in the main menu.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
127 / 456
System Administration
128 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Security Manager
Security Manager overview
The AXIOM Sensis XP Information System provides an advanced security system
that guarantees that only authorized personnel will be able to access and evaluate
patient data. Auditing allows you to trace all user activities in the system.
Overview of functions
The Security Manager allows you to perform the following configuration tasks:
User management
 Granting access to patient data
– Table tab card: Checking existing directories
– Directory tab card: Creating, editing, or deleting directories and Granting
permission to access patient data in directories
– Group tab card: Setting up user groups
 Granting access to program functions
– Role tab card: Defining, editing, or deleting roles, List of available use cases
 Managing user accounts
– User tab card: Creating a new user, Granting or denying permission on the
user level, and Editing or deleting users
Auditing
 Defining what to audit
– Audit tab card
 Querying the audit log
– Audit log tab card
 Exporting and archiving audit log data
– Save Audit Log tab card
Note
This system of user management and auditing which is configurable in the Security Manager only applies to the AXIOM Sensis XP Information System.
Access control to the AXIOM Sensis XP Acquisition System is controlled by a
Windows user management that was set up during system installation.
Checking logged-on users
The Logged in tab card provides an overview of who is logged on the AXIOM Sensis XP Information System at the moment.
Changing the administrator password
In addition to the users listed on the User tab card of the Security Manager (some
of whom may hold administrator rights) a “super user” or rather “super administrator” exists for the AXIOM Sensis XP Information System. This user has the
highest-level access to all user and administrator functions and features as well as
to all patient data. You can change this user’s password in the Security Manager.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
129 / 456
System Administration
Key terms and concepts
For information on the concepts and key terms involved in the AXIOM Sensis XP
Information System security system please refer to The security system 61
Basic procedures
Use these icon buttons or menu items for editing on the various tab cards of the
Security Manager window.
 Save (Application > Save)
– Saves changes to settings or newly created directories, groups, roles, or user
accounts back to the database.
– Saves audit trail settings.
Note
Do not forget to save changes back to the database explicitly this way.
The system will not warn you if you forget to save changes.
 Delete (Application > Delete)
– Deletes the currently displayed directory, group, role, or user account (confirmation requested).
 Clear (Application > Clear)
– Clears all entries from the input boxes on the current tab card.
– Allows you to start your definition all over again.
Note
Clearing does not, however, reset your changes back to the last saved version in
the database, it simply erases entries.
 Refresh (Application > Refresh)
– Updates the Security Manager from the database.
 Add selected value / Remove selected value
– Select one or more items in an Available ... box and click the Add selected
value icon to create a group membership, or select a use case.
– Select one or more items in a Selected ... box and click the Remove
selected value icon to remove an item from the selection list.
130 / 456
AXA5-200.640.07.01.02
System Administration
Security Manager
Starting Security Manager
 Select AXIOM Sensis Information System > Server > Security Manager from
the Windows Start menu.
– The Login dialog box for your administrator credentials is displayed:
 Enter your user name and password and click OK.
– User name and password are not case-sensitive.
Note
You need administrator rights in order to log onto the Security Manager (dbo
rights = database operating permission).
Note
Only one instance of the Security Manager can be opened at a time. If the Security Manager is currently in use on any other PC of your cath-lab information
system you will be denied access until that other instance has been closed.
After logon, the Security Manager window is displayed.
The title bar shows the computer name of the information system server and the
name of the central information system database.
User management
A user management system implies that only registered users can access the information system. It also implies that these registered users can only access the
case data they are involved in and that users can only work with those program
functions they actually need.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
131 / 456
System Administration
Granting access to patient data
Controlling access to patient data is implemented in the AXIOM Sensis XP Information System security system via directories (virtual folders), permissions (specific data manipulation rights), and user groups.
Checking existing directories
 Display the Table tab card on top.
Errors in directory assignment
Errors in the assignment of patients to directories can occur when:
 Directories are deleted (patient records become “orphans” as a result).
 A system crash occurs
A directory named ***ERROR*** is displayed if the Security Manager detects patients in the database that are not assigned to one of the available directories or
detects patients with conflicting directory assignments.
Note
132 / 456
Patients that are not assigned to a directory cannot be viewed or accessed in the
Patient Explorer.
AXA5-200.640.07.01.02
System Administration
Security Manager
Loading data from the database
 Click Load Tree to display all directories available in the central database.
 Click a directory in the tree view to display patients stored in this directory.
Correcting errors
 Click ***ERROR*** in the tree view to display these patients.
 Then right-click on the directory (target directory) to which you want to move
the patients from ***ERROR***.
 Confirm moving these patients.
 Click Load tree again to make sure that no more errors exist.
Creating, editing, or deleting directories
 Display the Directory tab card on top.
Predefined directories
AXIOM Sensis XP (VC11)
A directory is a means of categorizing patient data. By default all patients are assigned to the directory AXIOM_Sensis.
AXA5-200.640.07.01.02
133 / 456
System Administration
User-defined directories
Other directories can also be created according to your hospital’s data management policy. You will have to assign patients to these directories on a patient by
patient basis in Patient Explorer.
Creating a new directory
 Enter a new directory name in the Directory box.
Note
The directory name must be unique. If you enter the name of an existing directory (and then change permission settings) you will, in fact, change that existing
directory.
Names may contain any alphanumeric or special characters but no spaces.
 Grant permissions for the available user groups and, if necessary, for individual
users as well.
– See Granting permission to access patient data in directories 135.
 Save the new directory.
Editing an existing directory
 Select the directory whose settings you wish to change.
 Change its permission settings.
– See Granting permission to access patient data in directories 135.
Note
You cannot change the directory name. Overwriting an existing directory name
will in fact create a new directory and will copy all permission settings from the
directory you first selected.
 Save the new settings back to the database.
Deleting a directory
 Select the directory you wish to delete.
Note
You cannot delete the predefined directories Cathcor or AXIOM_Sensis.
 Click Delete.
– If this directory contains patients a message is displayed.
134 / 456
AXA5-200.640.07.01.02
System Administration
Security Manager
– In the Statistics box at the bottom of the Directory tab card you will find
information on how many patients this directory contains.
Note
If you delete a directory with patients in it make sure you move onto the Table
tab immediately. Move these patients to another directory or these patients will
no longer be available in the Patient Explorer.
See Correcting errors 133.
 Save your changes.
Granting permission to access patient data in directories
 Use either the Directory or the Group or User tab card to grant permission.
– These tab cards show the same settings but from a different perspective.
Permission to user
groups or users
Creating or editing directories implies that you define what sort of access rights to
patient data you grant to the members of a user group.
As a rule, individual users inherit the permission settings made for the user group
they belong to. You can, however, grant individual users extra rights that nobody
else in the group has, or deny a user a right that everybody else in the user group
holds.
Note
Permission settings for individual users have a higher priority than permission settings for user groups.
This means that when the permission settings for a user group and the permission settings for one of its users are contradicting, then the settings for the individual user apply to that user.
For example: User X belongs to group Y. Group Y has explicitly been denied the
right to access patient data in directory Z but user X has been granted this right
so that X can access Z but nobody else in Y can.
Granting or denying permission to a user group
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
135 / 456
System Administration
 Select one or several of these permissions:
– Select and view patient and data only.
– Insert and create new patient records.
– Update and edit patient and study data.
– Delete patient and study data.
– Owner is currently not used in the information system, so do not select it.
 Grant or deny a permission on the user group level:
(1)
(2)
(3)
– Permission granted (1)
– Permission denied (2)
– No selection on user group level means permission not granted; same
effect as denied (3).
 Save your changes.
Granting or denying permission on the user level
 Select one or several of these permissions:
– Select and view patient and data only.
– Insert and create new patient records.
– Update and edit patient and study data.
– Delete patient and study data.
– Owner is currently not used in the information system, so do not select it.
 Grant or deny a permission on the individual user level:
(1)
(2)
(3)
– Permission granted (1)
– Permission denied (2)
– Permission inherited from group (3)
 Save your changes.
Setting up user groups
 Display the Group tab card on top.
136 / 456
AXA5-200.640.07.01.02
System Administration
Security Manager
Permission settings
As a rule you grant permission to view or manipulate patient data in a directory by
user group (specific permission settings for individual users are an exception).
Granting user groups permission to the data stored in directories can either be
done on the Groups tab card or on the Directory tab card. However, on the Group
tab card you have the advantage of viewing a list of group members while you
grant or redefine permission settings.
Predefined user groups
Two user groups are predefined in the system:
 Administrative_team and
 Exam_room_team.
You can use these user groups, for example, until you have discussed a more adequate user group structure with your cath-lab team.
Creating a new user group
 Enter a new user group name in the Group box.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
137 / 456
System Administration
Note
The group name has to be unique. If you enter the name of an existing user
group (and then change permission settings) you will, in fact, change that existing user group.
Names may contain any alphanumeric or special characters but no spaces.
 Grant permission to the patient data in directories.
– See Granting or denying permission to a user group 135
 Save the new user group.
Note
You cannot assign members to user groups on the Group tab card.
 Move on to the User tab card after user group creation to assign user ac-
counts to the new group.
Editing an existing user group
 Select the user group whose settings you wish to change in the list.
 Change its permission settings.
– See Granting or denying permission to a user group 135
Note
You cannot change the group name. Overwriting an existing user group name
will in fact create a new user group and will copy all the permission settings from
the user group you first selected.
 Save the new settings back to the database.
Deleting a user group
 Select the user group you wish to delete.
Note
You cannot delete the predefined user groups Administrative_team or
Exam_room_team.
 Click Delete.
138 / 456
AXA5-200.640.07.01.02
System Administration
Security Manager
Note
Before you delete a user group, make a note of all the members of that group.
After deletion these users might no longer hold any rights (permissions) to access patient data in directories.
 Move on to the User tab card to assign the “orphaned” users to other user
groups.
 Save your changes.
Granting access to program functions
In the Security Manager, access to program functions is granted by defining roles
that reflect the division of labor in your cath lab.
Defining, editing, or deleting roles
 Display the Role tab card on top.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
139 / 456
System Administration
Roles and the cath-lab
workflow
A role allows its members to access a number of so-called use cases. A use case is
a stored procedure in the central information system database, which stores information on:
 which program functions a user, whose role includes this use case, may exe-
cute
 when in the clinical workflow he or she may execute this function or these
functions.
Refer to the AXIOM Sensis Operator Manual, Part AXIOM Sensis Information
System, Chapter Information System Overview, section The information system
workflow concept for detailed information on the cath-lab workflow and the study
states the workflow concept involves.
Predefined roles
A number of roles are predefined in the system. These include:
 Administrator
 AXIOM_Sensis_EP_Hemo
 Cath_lab_manager
 Inventory_manager
 Nurse
 Operator
 Statistics_manager
 Transcriber
Note
The predefined role Administrator comprises more rights than the sum of selected use cases.
 Never delete the predefined Administrator role, only add use cases, if nec-
essary.
Creating a new role
 Enter a new role label in the Role box.
Note
The role name must be unique. If you enter the name of an existing role (and
then change the use case settings), you will, in fact, change that existing role.
Names can contain any alphanumeric or special characters but no spaces.
 Select the use cases this role is to include.
– See List of available use cases 142
140 / 456
AXA5-200.640.07.01.02
System Administration
Security Manager
 Save the new role.
Note
You cannot assign members to roles on the Role tab card.
 Move on to the User tab card after role creation to assign user accounts to
this role.
Editing an existing role
 Select the role whose settings you wish to change.
 Change its selection of use cases.
– See List of available use cases 142
Note
You cannot change the role name. Overwriting an existing role name will in fact
create a new role and will copy the entire use case selection from the role you
first selected.
 Save the new settings back to the database.
Deleting a role
 Select the role you wish to delete.
– You cannot delete any of the predefined roles.
 Click Delete.
Note
Before you delete a role, make a note of all the members of this role. You will
have to make them members of other roles afterwards, otherwise they might no
longer hold access rights to any program functions.
 Move on to the User tab card to assign the “orphaned” users to other roles.
 Save your changes.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
141 / 456
System Administration
List of available use cases
Legend:
X : this use case can only be executed if the study is in this study state.
- : use case cannot be executed in this study state
(blank) : use case is independent of study state or irrelevant in certain study states.
ADM_RunAdmin
Backup Manager
Run Backup Manager
ADM_RunBackup
Patient Explorer
Change study state
BR_ChangeStudyState
Patient Explorer
Configure GUI (fields shown, column
width, etc.)
BR_Configuration
Patient Explorer
Delete patient / Delete study / Delete
report
BR_DeletePatStudRep
Patient Explorer
Delete preregistrations
BR_DeletePreregPatStud
Patient Explorer
Edit patient data
Patient Explorer
-
X
X
X
X
-
X
X
X
X
BR_EditPatient
-
X
X
X
X
Edit study data
BR_EditStudy
-
X
-
-
-
Patient Explorer
Rearrange studies
BR_Merge
-
X
X
X
X
Patient Explorer
Add preregistrations / Edit preregistrations
BR_PreregInsertUpdate
Patient Explorer
Change study state to Post Cath when
study is Approved
BR_UnlockStudy
-
-
-
-
X
Patient Explorer
Search for patients
BR_SearchPatients
X
X
X
X
X
Patient Explorer
Run the Patient Explorer
BR_StartBrowser
Patient Explorer
Change study state to Post Cath when
study is Frozen
BR_ResetExpiration
-
-
X
-
-
Patient Explorer
View patient data in main window
BR_ViewPatient
X
X
X
X
X
Patient Explorer
View preregistration data in main window
BR_ViewPrereg
Patient Explorer
Preview report in main window
BR_ViewReport
X
X
X
X
X
Patient Explorer
View study data in main window
BR_ViewStudy
X
X
X
X
X
Acquisition interface
Close exam in ACQ
CN_CloseExamination
-
X
-
-
-
-
Acquisition interface
Sending data from ACQ to SIS DB during examination
CN_SendClinicalData
-
X
-
-
-
-
Acquisition interface
Start exam in ACQ / Go to post-processing in ACQ
CN_StartExamination
X
-
X
-
-
-
PreCath
Approved
Run Configuration Manager
Pending approval
Configuration Manager*
Frozen
Use case
PostCath
Description
DuringCath
AXIOM Sensis XP Client
†
142 / 456
AXA5-200.640.07.01.02
X
X
X
X
System Administration
Security Manager
Documentation Tool
Edit dictionaries
DE_EditDictionaries
Documentation Tool
Run Documentation Tool
Documentation Tool
Approved
CN_VitalSignsAlarms
Pending approval
Modify system defaults for vital signs
alarms
Frozen
Acquisition interface
PostCath
Use case
DuringCath
Description
PreCath
AXIOM Sensis XP Client
X
-
X
X
X
X
DE_StartDataEntry
X
X
X
X
X
X
Edit data
DE_UpdateData
X
X
X
-
-
-
Report
Create a new report
RE_CreateReport
X
X
-
-
-
Report
Run Report Composer
RE_CreateTemplate
Report
Save a report
RE_EditReport
X
X
-
-
-
Report
Initiate e-mail report
RE_EmailReport
-
-
-
-
X
Report
Initiate transfer report
RE_ExportReport
-
-
-
-
X
Report
Initiate fax report
RE_FaxReport
-
-
-
-
X
Report
Print a report
RE_PrintReport
X
X
X
X
X
Report
Open an existing study report
RE_ViewReport
X
X
X
X
X
Communication Manager
Run Communication Manager
SICT_RunSICT
Heart Picture Illustrator
Run Heart Picture Illustrator
SOP_CHPStandard
-
X
X
-
-
-
Coronary Tree Illustrator
Run Coronary Tree Illustrator
SOP_CTRStandard
-
X
X
-
-
-
Coronary Tree Illustrator
CTI Administrator
SOP_CTIAdmin
-
X
X
-
-
-
Inventory Manager
Run Inventory Manager
SOP_IWSConfiguration
Inventory Manager
Create public views of the inventory
stock
SOP_IWSCreatePublicViews
Inventory Manager
Maintenance: Modify columns with
normal privilege level on all four tabs
SOP_IWSMaintenance
Inventory Manager
Maintenance: Modify columns with
normal privilege level in Consumption
SOP_IWSMaintenance
Consumption
Inventory Manager
Maintenance: Modify columns with
normal privilege level in Items
SOP_IWSMaintenanceItems
Inventory Manager
Maintenance: Modify columns with
normal privilege level in Orders
SOP_IWSMaintenanceOrders
Inventory Manager
Maintenance: Modify columns with
normal privilege level in Vendors
SOP_IWSMaintenanceVendors
Inventory Manager
Standard: Modify columns with normal privilege level on all four tabs
SOP_IWSStandard
Inventory Manager
Standard: Modify columns with normal privilege level in Consumption
SOP_IWSStandardConsumption
Inventory Manager
Standard: Modify columns with normal privilege level in Items
SOP_IWSStandardItems
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
143 / 456
SOP_IWSStandardOrders
Inventory Manager
Standard: Modify columns with normal privilege level in Vendors
SOP_IWSStandardVendors
Inventory Manager
View: Modify columns with normal
privilege level on all four tabs
SOP_IWSViewOnly
Inventory Manager
View: Modify columns with the lowest
privilege level in Consumption
SOP_IWSViewOnly
Consumption
Inventory Manager
View: Modify columns with normal
privilege level in Items
SOP_IWSViewOnlyItems
Inventory Manager
View: Modify columns with normal
privilege level in Orders
SOP_IWSViewOnlyOrders
Inventory Manager
View: Modify columns with normal
privilege level in Vendors
SOP_IWSViewOnlyVendors
Statistics Manager
Modify list of predefined searches
SOP_QWSSaveQuery
Statistics Manager
Search among all patients
SOP_QWSSearchAllStudies
Statistics Manager
Search in own directories
SOP_QWSSearchOwnStudies
Approved
Standard: Modify columns with normal privilege level in Orders
Pending approval
Inventory Manager
Frozen
Use case
PostCath
Description
PreCath
AXIOM Sensis XP Client
DuringCath
System Administration
*
Selecting the use case Run Configuration Manager (ADM_RunAdmin) alone is not sufficient to allow users to edit the sites list in the Configuration Manager. Only users with the predefined Administrator role are permitted to add or edit sites.
†
Selecting the use case Run Backup Manager (ADM_RunBackup) alone is not sufficient to allow users to open Backup Manager and view
and edit system backup jobs. Only users with the predefined Administrator role are permitted to open Backup Manager.
144 / 456
AXA5-200.640.07.01.02
System Administration
Security Manager
Managing user accounts
 Display the User tab card on top.
User credentials
Users need a user ID and a password to log on to an AXIOM Sensis XP Information System application or for unlocking the screen saver.
Only system administrators can assign passwords to users. Clinical users cannot
change their own passwords.
Note
AXIOM Sensis XP (VC11)
In rare cases a mismatch might occur between the user credentials stored in the
information system database and on the SQL Server. This might happen as a result of an upgrade to a new SQL server version or when you restore the information system database from a backup. In that case “:Enter Password” is added to
an affected user name in the user list of the Security Manager. Assign a new
password to all users that are marked with the “:Enter Password” extension. Tell
the users their new passwords.
AXA5-200.640.07.01.02
145 / 456
System Administration
Default directory
When you create an account the Security Manager requests selection of a default
directory.
Membership lists
On the User tab card you assign users to user groups and roles. In order to check
which permissions the available user groups hold or which use cases the available
roles imply, you need to move on to the Group or Role tab cards.
Creating a new user
 Enter the new user name in the User box.
– The user name must be unique. If you enter the name of an existing user
(and then change settings) you will, in fact, change the privileges and permissions of the existing user account.
– Names may contain any alphanumeric or special characters but no spaces.
 Enter a password for the new user.
– Every new user account should have a password.
– Make sure you remember the correct spelling of the password so that you
can pass it on to the new user. You will not see the password as you type it
and there is no way of checking passwords later on. You will have to assign
a new password if you or the user forgets the old password.
Note
Do not use any of the characters “ = ”, “ ; ” or “ ’ ” in passwords. Passwords containing these characters are not supported by the SQL server.
Accounts with passwords containing one of these characters cannot be used to
log on to an AXIOM Sensis XP Information System client or to connect to the
information system database.
 Select a default directory for the new user.
– See Default directory 146
 Select user group and role memberships for the new user.
– Remember that unless you assign role memberships to new users they cannot execute program functions or even start the various AXIOM Sensis XP
Information System application programs at all.
– Remember that unless you assign group memberships or directory permissions the new user will not be able to access any patient data.
 Grant or deny the new user directory permissions, which will only apply to this
individual user.
– See Granting or denying permission on the user level 136
 Save the new user account.
146 / 456
AXA5-200.640.07.01.02
System Administration
Security Manager
Editing or deleting users
 Select the user whose settings you wish to change or who you want to delete.
 Change the password, default directory, role and group memberships, or direc-
tory permissions.
– You cannot change the user name.
– Overwriting an existing user name creates a new user and copies all settings
from the user you first selected.
 Save your changes back to the database.
Or
 Delete the user account.
– This user will now no longer be allowed to access any AXIOM Sensis XP
Information System applications.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
147 / 456
System Administration
Auditing
Auditing allows you to trace which users have accessed what patient data and
whether they manipulated this data as well.
Defining what to audit
 Display the Audit tab card on top.
 Select the use cases you wish to audit from now on.
– See List of available use cases 142
Or
 Check the Audit everything box.
– The more you audit the more disk space the audit log will require. If you
decide to audit everything remember to save and archive the audit log regularly.
 Save your audit trail settings.
148 / 456
AXA5-200.640.07.01.02
System Administration
Security Manager
Querying the audit log
 Display the Audit log tab card on top.
 Specify what you want to trace:
– Date from ... Date to - searches an interval.
– UserID - tracks data access or manipulations by user.
– Computer - searches by the client PC in your cath-lab network from which
the data were accessed.
– Client - searches by the AXIOM Sensis XP Information System application program with which the data were accessed.
– Usecase - searches by use case.
See List of available use cases 142
– Result - searches by whether a use case was performed successfully or
whether an error occurred.
 Click Get data to start searching the audit log of the information system data-
base.
Note
AXIOM Sensis XP (VC11)
Audit log data that were exported with Save Audit Log are not queried now.
AXA5-200.640.07.01.02
149 / 456
System Administration
 Click Print to print out the query results on the default printer of the PC you are
working on.
Exporting and archiving audit log data
 Display the Save Audit Log tab card on top.
What saving the audit
log means
Saving audit log information means that you export all audit log information that
is older than a specified date to an external Microsoft Access database. The exported audit log data are then deleted from the central information system database.
The Access database is stored in a predefined location on your hard disk.
See Configuration Manager 305
You can archive this database on CD from there.
Estimating the size of
the export database
150 / 456
In order to make sure the exported Access database will fit on a CD the system estimates its size for you.
AXA5-200.640.07.01.02
System Administration
Security Manager
If the estimate shows that the exported database will be too big, you can either
perform two export runs (enter an earlier date for the first run). Or you can have
the export file split up automatically into several files of manageable size.
Reorganizing the system database
Even though exported audit log information has been deleted from the information system database you must reorganize that database in order to free the space
and make it available for new data.
Exporting audit log data
 Enter a date in the Save Audit log older than or equal to box to export and
remove from the information system database all audit log entries that are older than this date.
– The system will automatically estimate the size of the export file for you.
 Check the Estimated size.
 If necessary, split up the export file by checking the Split into files with max-
imum size box.
 Also enter a maximum size (for example, 600 MB so as to make sure it will fit
on a CD).
 Click Save Audit Log to start exporting.
 Archive the Access database that was created on the hard disk onto CD. Access
the exported database via the Windows file system in order to do so.
Database maintenance
 Choose a reorganization option:
– Release unused space to release unused disk space only from the end of
the database file (this is the faster reorganization option)
– Complete database reorganization to release unused disk space throughout the entire database file (this is the slower but more efficient database
reorganization option).
 Start database reorganization.
– Depending on the reorganization option you selected, the reorganization
process might take a while.
 Under Percent free select how much disk space should never be used for audit
trail data.
– This disk space buffer will make sure that there is always enough space for
new study data.
– We recommend that you select a higher percentage if a large number of
patients are examined at your cath lab every week.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
151 / 456
System Administration
Checking logged-on users
 Display the Logged in tab card on top.
Check here who is logged onto the information system before you perform certain
user management tasks such as deleting directories, groups, roles, or users.
The Logged in tab card will also show you whether users are no longer working
with the information system and have forgotten to log themselves off.
 Click the Logged in button to display a table with all currently logged in users.
– USERID - name of a logged in user
– PROGRAM - AXIOM Sensis XP Information System application program
onto which the user is currently logged.
– MACHINE - name of the PC the user is working with.
– LOGIN_TIME - the date and time the user logged in.
– LAST_ACCESS - the date and time of the last activity.
Note
152 / 456
If LOGIN_TIME and LAST_ACCESS was a long time ago, the user may have forgotten to log off. Check with them and tell them to log off now.
AXA5-200.640.07.01.02
System Administration
Security Manager
Changing the administrator password
In addition to the users listed on the User tab card of the Security Manager (some
of whom may hold administrator rights) a “super user” or rather “super administrator” exists for the AXIOM Sensis XP Information System. The name of this
user account is MIS_Admin. This user has the highest-level access to all user and
administrator functions and features as well as to all patient data.
Only members of the “Administrative_team” or the “super administrator” can access the DB Manager and the Security Manager.
Note
The User ID of the “super administrator” was configured during system installation. You cannot change it.
The “super administrator” password was also first set during system installation.
You can change this password in Security Manager. However, you will not use
the User tab card as you do when changing the user credentials of any other users. You use the Change MIS_ADMIN password dialog box instead.
 Select Application > Change MIS_ADMIN password.
– The Change MIS_ADMIN password dialog box is displayed.
 Enter the old password to identify yourself as “super administrator”.
 Enter a new password and confirm by entering it a second time with identical
spelling.
Note
Do not use any of the characters “ = ”, “ ; ” or “ ’ ” in passwords.
Passwords containing these characters are not supported by the SQL server.
Accounts with passwords containing one of these characters cannot be used to
log on to an AXIOM Sensis XP Information System client or to connect to the
information system database.
Note
Just like user passwords the “super administrator” password is not case sensitive.
 Confirm with OK and close the dialog box.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
153 / 456
System Administration
154 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Report Composer
Report Composer overview
The Report Composer is a component model add-in program (COM Add-in) for
Microsoft® Word. It allows you to define study report templates with respect both
to their information content and formal aspects.
Overview of functions
When customizing study report templates you will most frequently use a factorydefined template to start out from and adapt it to your own requirements.
This section assumes that this is your workflow:
 Opening a template from the database.
 Changing formal template aspects.
 Adding, moving, or removing tags.
 Adding section breaks, unlocking, and locking sections.
 Previewing a report.
 Saving a report template and handling versions.
Note
Whenever you change your database definition, for example, when you add
groups or fields, be sure to check all your report templates.
Depending on how a report template was set up, you might have to update it to
make sure it includes the new groups and fields.
Key terms and concepts
For a detailed description of the key terms and concepts used in the Report Composer refer to Information System Concepts 17.
As making full use of all report customization options provided by the AXIOM Sensis XP Information System requires an understanding of all aspects related to the
information system database, make sure you read at least these sections: Database overview 24, The AXIOM Sensis XP Information System central database 30, The study type concept 38, The reporting concept 40.
Note
Working with the Report Composer requires at least a good level of experience
with Microsoft® Word.
If you do not have such experience yet, make sure you acquire it first and only
then return to the Report Composer to customize report templates.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
155 / 456
System Administration
User interface and basic procedures
The Report Composer user interface consists of two windows: the standard Word
window and the Report Composer (tag picker) window. These are usually displayed side-by-side with the Report Composer window in the upper right-hand
corner of the screen.
Menu and tool bars
You will use the menu bar and tool bar of the Report Composer mostly for file
handling, such as opening and saving templates from and back to the database. If
saving a template file in Word is required, the system will tell you so. You will also
use this menu for Report-Composer-specific operations such as tag insertion.
For anything else, in particular for any text formatting, you use the Word menu
bar and tool bars.
Function keys
156 / 456
Function keys can be used as shortcuts for various Report Composer operations.
AXA5-200.640.07.01.02
System Administration
Report Composer
Note
The focus needs to be in the Report Composer (tag picker) window if the function key is to execute a Report Composer function. If the focus is in the Word
window the same function key will execute a Word function.
For example, press F5 with the focus in the Report Composer window and the
Open Template dialog box opens. Press F5 with the focus in the Word window
and the Find and Replace dialog box opens.
You place the focus on a window by clicking in it.
Basic procedures
 Open Template (Application > Open Template, F5)
– Displays the Open Template dialog box where you can select a study report
template from the information system database for editing.
 Preview (Application > Preview, F6)
– Prompts you to select a test case and shows what the final report will look
like.
– Preview requires you to save the template on your hard disk first.
 Save As Template (Application > Save As Template, F7)
– Saves an edited template back to the information system database.
– Prompts you to select whether you want to save it under a new name (Save
as function) or whether you want to create a new version of a template that
already exists in the database.
– Save as template requires you to save the template on your hard disk first.
 Application > Set Active Template Version (F8)
– Every time you edit and save a template back to the database a new version
of this template is created.
– This function allows you to select which of the stored template versions is to
be the active one.
– The active template version is the one a clinical user will be offered for
report generation.
 Edit > Insert Tag (F9)
– Inserts the tag you selected in the tag picker window into the template at
the current cursor position.
– If you have accidentally selected an entry in the tag picker window that
merely represents a structure element in the tree view but no selectable tag
then Edit > Insert Tag is dimmed.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
157 / 456
System Administration
 Edit > Insert Section Break (F11)
– The Report Composer uses the Word section concept for enabling predefined sections of the future report file for direct editing (that is text comment entry by clinical users).
– This menu item adds a section break in your Word template at the current
cursor position.
Note
Remember that you need two section breaks if you want to enable a limited section for editing in the middle of a report file.
Remember to always switch to View > Print Layout and also to turn on the display of formatting marks when you are working with section breaks.
 Lock/Unlock Section (Edit > Section Locked, F12)
– You unlock a section to make it available to clinical users for text entry in the
final report.
Note
Tag insertion by drag
and drop
Make sure you position the cursor somewhere in the middle of the section you
want to lock or unlock, but not directly on a section break.
 Click an entry in the tag picker window.
– The entry is highlighted.
 Hold the left mouse button pressed and drag the tag into the Word window.
– The tag is dropped exactly where the cursor stood when you last worked in
Word.
– If the cursor looks like this you selected a tag that you can drag and drop.
– If the cursor looks like this you accidentally selected a structure element in
the tag picker tree view.
Tag placement
Due to limitations of Word a number of rules exist for tag placement:
 Tags which represent images in the report (for example, Image, Waveform,
CTI, HPI) cannot be placed in text boxes.
 Cluster and predefined block tags should not be placed in footnotes.
 Cluster and predefined block tags should not be placed in a paragraph imme-
diately following a paragraph that contains a table, or a tag which will be implemented as a table in the final report.
– The tables produced by these tags would automatically be merged in the
final report.
– Always insert a blank paragraph between any such two tags.
– Report Composer will enforce this rule when validating the tag syntax,
which is when you save the template.
158 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
Starting Report Composer
 Be sure to close the Patient Explorer, if it is currently open, before you start
Report Composer.
 Start Microsoft® Word (Start > Programs > Microsoft Office > MS Office
Word 2007).
Note
On an AXIOM Sensis XP Acquisition System which serves as an AXIOM Sensis
XP Information System master PC you can also start Microsoft® Word for Windows from the Applications menu (main menu of the Hemodynamics or Electrophysiology application or syngo Patient Browser menu bar).
 Select Add-Ins > AXIOM Sensis Report Composer in the Word menu.
– The Login dialog box is displayed.
 Enter your user name and password.
– User name and password are not case-sensitive.
– The Report Composer window opens in the upper right-hand corner of the
screen.
 Arrange the Word and Report Composer windows so that they are side by side
and do not overlap.
Note
You will be prompted to save any unsaved documents and templates if you accidentally close Report Composer.
 Make sure you click Yes to save changes in open documents.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
159 / 456
System Administration
Opening a template from the database
 Click Open Template.
– The Open Template dialog box is displayed. It shows a list of all report templates that are currently available in the information system database.
– This list contains factory default templates as well as any study report templates that were created or adapted since the system was installed, either by
system administrators or by Siemens application experts immediately after
system installation.
The following list presents a selection of report templates that are most likely to
be available in most information system installations.
Note
Which report templates are available in your information system installation and
how they are labeled depends on the installed setup (English, French, German,
Spanish, or US) and on the individual configuration settings made in your particular cath lab.
 Flowsheet templates
– A flowsheet report is intended to present all data that has been acquired or
entered in the database for a study in a structured way.
– The factory predefined flowsheet reports present data from the system
tables (measured and calculated data) as well as any manually entered data
into predefined database tables that are grouped in predefined output
report clusters.
– Flowsheet templates come in two versions:
organized by data category - for example, Flowsheet (C), Diagnostic (C)
organized chronologically - for example, Flowsheet (T), Diagnostic (T)
Note
If you are editing a flowsheet report you can only insert groups (database tables)
of the scope study into this report type.
Check your group definition file in the DB Manager to make sure you are not accidentally inserting groups of the scope patient into your flowsheet report.
Make sure you check the cluster definition file as well, as an error will occur in
the Report Generator if you insert a cluster tag into a flowsheet report that contains a group of the scope patient.
 Hemodynamics (1) / Hemodynamics (2) / Hemodynamics (3)
– Three factory predefined examples of study reports for hemodynamic studies.
160 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
 Summary
– An example of a report that focuses on conclusions and text information
entered in the information system database with the Documentation Tool,
rather than on measured or calculated data.
 Waveform
– An example of how images can be inserted into a report template.
 AblationReport
– A study report template for electrophysiology studies with ablation.
 Select a report template from the list.
 Also select a template Version.
– Every time you edit a report template and save it back to the database a new
report template version is created.
– Only one version can be active at a time. This is the template version that
will be presented to clinical users during report creation. The active version
of a template is usually the most up-to-date version.
 Select where to save a local copy of your template.
– When you are editing a study template we recommend that you save your
changes frequently.
– As you will not want to create a new template version in the database every
time you save a template, intermediate template versions are stored locally
on your hard disk:
 Desktop
– *.dot-file versions are placed as objects on your desktop.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
161 / 456
System Administration
 My Documents
– *.dot-file versions are stored in your personal folder.
 Favorites
– *.dot-file versions are stored in the favorites folder of your Windows user
profile.
 Click Open.
– It is only after you have selected a template and version that the Open button becomes active.
Changing formal template aspects
When you open a Siemens-predefined report template that you plan to adapt to
your hospital’s requirements for the first time, there are a number of formal aspects you will most likely want to adapt.
 Header/footer
 Page layout and margins
 Font information
Changing header /
footer
The header/footer section of a word document appears shaded while you are editing body text.
 Double-click in the shaded header area to open it for editing.
– The page header in a predefined Siemens template consists of two sections.
(1)
(2)
(1) Institution name, address, logo
– Replace the text and logo in the table or remove the Word table altogether.
(2) Patient information section
162 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
 Move onto the page footer using the Switch Between Header and Footer icon
in the Header and Footer toolbar.
 Replace the Siemens footer with your own footer text, or remove it altogether.
 Use the commands from the Header & Footer Tools menu to change the page
numbering format, if necessary.
Note
Do not use any of the other commands from the Header & Footer Tools menu.
These commands insert Word system variables into your document, but not database tags.
 Quit the header and footer editing mode by clicking the Close Header and
Footer button on the Header & Footer Tools menu.
Replacing the logo
When replacing the dummy logo in the header of the factory-defined report templates with the logo of your own institution choose one of these two methods:
Either
 Use Insert > Picture and choose one of the supported file formats listed in the
selection dialog box.
Or
 Copy and paste or drag and drop a logo from another Word document.
Note
Paper size
Do not copy and paste or drag and drop a logo from another application program as you might attempt to insert a file format not supported by Word this
way.
In order to check whether the predefined paper size corresponds to the settings of
your printer.
 Select Page Layout > Page Setup and click the Paper tab on top.
Font settings in entire
document
If you want to change the font family and size in your entire report template remember that you will have to do that separately for the body text, the page header, and footer.
 Click Ctrl. + A to select the entire body text.
 Select Home > Font and select the required font settings here.
 Open the header section again for editing, click Ctrl.+A and Home > Font.
 Move down to the footer section and repeat Ctrl.+A and Home > Font.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
163 / 456
System Administration
Adding, moving, or removing tags
When adding tags to a template you usually use the tag picker window. Selecting
a database object from there and dragging it into a report template in the Word
window automatically converts it to a tag. You will not need to understand the tag
syntax when you do this.
However, in order to understand what information the template already contains
or if you want to move tags within a template or remove tags, some understanding of the tag syntax will be necessary.
Adding tags to a template
These are the tags you can add to a template by selecting them from the tag picker
window.
Cluster tags
A report output cluster represents a predefined collection of customizable groups
from the database. Report output clusters are defined in the DB Manager.
See Editing clusters 106
Customizable groups
and system groups
Creating a study report template by adding cluster tags is a quick and efficient way
of making sure all the relevant study information is going to be presented in the
report.
Remember, however, that output report clusters are intended only for grouping
customizable database tables. Output report clusters do not include information
from static database tables (also called system tables) unless you explicitly specify
that. Customizable groups only include information that has been entered manually with the Documentation Tool. Only system groups contain measured and
calculated data that were collected during the examination, such as pressure calculation values or vital signs data.
Predefined output report clusters
164 / 456
Some output report clusters have been predefined by Siemens. Which groups they
contain and how the clusters are labeled depends on the installed setup (English,
French, German, Spanish, or US) and on the individual configuration settings in
your particular cath lab.
AXA5-200.640.07.01.02
System Administration
Report Composer
Inserting a cluster in a report template
 Click a cluster in the tag picker window and drag it into the Word window.
– The Insert Cluster dialog box opens.
 Uncheck any of the groups that are listed here, if you want to exclude them
from the selection.
 Check the Include system groups box if you want to show these data as well.
Note
Include system groups always includes all system groups. If you want to exclude individual groups from being shown in your reports, add these groups to
the Excluded System Groups system cluster in your cluster definition file (cathcor.clu).
See Study reports: exclusion of system groups 113
Note
If you insert more than one output report cluster in your report and click Include
system groups for each of these clusters, the same system group information
will be included in the final report several times (redundant information).
Therefore, only check Include system groups once. We recommend that you
check this option for the During Cath cluster.
 Select the criterion by which the data is to be sorted in the report.
– By category (C)
– By time stamp, which means chronologically (T).
 Click OK, to include the cluster with these settings.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
165 / 456
System Administration
Formatting clusters
Clusters are collections of data groups (database tables). In the final report the
data from these database tables, which are included in the cluster, is presented in
table format.
When inserting a cluster tag in a report template you cannot control the format of
these tables. You should therefore make it a habit to check the presentation of
these tables in your template whenever you insert new clusters. Create a report
preview to do so and populate the report with test data.
See Previewing a report 187
In some cases this test might reveal that tables are too wide for your page size.
This can happen if database tables include a large number of fields and these fields
contain information with long phrases or words. (Long phrases or words in table
headings are, however, automatically rotated.)
This is what you can do if tables created for clusters turn out to be too wide in your
report preview:
Exclude fields from the
cluster
 Open the DB Manager and print the group definition files rep.grp and
cath.grp
Printing group definition files 101
 Check the group (database table) that causes the problem.
 Make a note of all those fields that do not need to be shown in the report.
– These could be cost fields, for example, or fields with less important information.
 Open the cluster definition file cathcor.clu in the DB Manager and search for
the output report cluster.
 Specify which fields in the very large group causing the problem you want to
exclude from the report.
See Exclusion of fields for output report clusters 119
 Preview the report again.
See Previewing a report 187S
Formatting options
If exclusion of fields from the cluster is not an option, Word offers these formatting options that might help display the entire table:
 Shrink the font size
 Select the cluster tag in question.
 Select Home > Font and reduce the font size.
– The table inherits font information from the cluster tag.
Or
166 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
 Increase the width of the text frame in your report template by shrinking the
margins
 Select Page Layout > Page Setup and click the Margins tab on top.
 Reduce the right or left margin here.
Or
 Increase the page width by switching to landscape format.
 Select Page Layout > Page Setup and click the Paper tab on top.
 Select Orientation: Landscape here.
– You can either change the orientation for the entire report or for the correct
section only.
– Insert section breaks before and after the cluster tag if you want to apply
landscape format only to the cluster with the large tables.
Groups (database tables)
Instead of inserting entire clusters you can select individual groups only.
Note
Inserting individual groups instead of entire clusters gives you a chance to
change table formats.
However, if you insert a group tag in a report template, this group will be shown
in each report that users create based on this template, even if the group does
not contain any data for a study. (An empty table is shown in this case.)
If you insert groups as part of a cluster, these groups will appear in the final report only if they actually contain data. (This applies both to groups listed in this
cluster and to system groups which were selected with the Include system
group checkbox).
In the tag picker window individual groups are available for selection and insertion
in a report under the output report cluster they are assigned to.
Groups that have not been assigned to an output report cluster are not available
for selection in the tag picker window.
This is true for all customizable groups (which are filled with manual data entry
from the Documentation Tool). For system groups (which contain calculated
and automatically acquired data) insertion as part of a predefined block is also
possible.
See also Predefined blocks 171
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
167 / 456
System Administration
Inserting a group in a report template
 Click a group in the tag picker window and drag it into the Word window.
– The Insert Group dialog box opens.
 Uncheck any fields that you want to exclude.
– You will immediately see the effect of exclusions on the table in the preview
section in the lower third of the dialog box.
 Apply a table style if you wish.
– These table styles are standard Word styles. They are also called Table Style
elsewhere in Word.
– If you select (none) here, you can either format the table manually or apply
a Table Style (Table Tools > Design) later.
Or
 Choose to insert the group as a Comma-separated list by checking the corre-
sponding box.
– A preview of how this list will look is displayed in the dialog box.
Refer to Syntax rules for comma-separated lists 184 for a description of how
to format comma-separated lists.
168 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
 Click OK, to include the group with these settings.
Field tags
Instead of inserting a group and omitting all but one field, you may select and insert just one field from a customizable group in the tag picker window.
Single-line fields and
multi-line fields
When inserting a field tag, the system makes a distinction between single-line
fields and multi-line fields.
Note
Remember that the term “field” stands for “attribute in a database table” in the
information system database terminology.
A single-line field represents one value (for example, only one value is available
for “total fluoroscopy time” per study). A multi-line field contains more than one
value (for example, information on medication: the patient might have been given more than one drug). Single-line field tags are inserted in a report template as
just tags. In order to control the report layout you can insert a single-line field tag
into a Word table, for example, just like in the page header of the predefined Siemens report templates).
Note
Multi-line field tags are automatically inserted into a report template as a table
(a single-column table), unless you chose to insert the group data as a commaseparated list.
See Tag syntax overview 181 for information on how to distinguish between
single and multi-line fields.
Restrictions for multiline field tags
Multi-line field tags from different groups must not be placed in the same row of
a Word table.
Inserting a field tag
 Click a field in the tag picker window and drag it into the Word window.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
169 / 456
System Administration
Patient and study data
With the help of Patient and study data tags you can insert patient demographic
data and organizational study information that was entered during patient registration in a report template.
Note
Make it a habit to use these tags from the tag picker window when you want to
insert this type of data into your report. Do not attempt to type or alter these
tags manually, as errors might easily happen here.
Inserting patient and study data
 Click a patient or study data tag and drag it into the Word window.
Or
 Insert the entire Patient data or Study data subcategory in order to show all
patient or study information that was entered during patient registration in the
report.
170 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
Note
The tags you insert here are marked as patient-level data (%_p...) or study-level
data (%_r). See also Tag syntax overview 181 (referential marker).
As a rule do not change referential markers as this might result in the wrong
data being shown in the report.
For example, a value such as the patient’s weight, which might change from one
study to the next, is inserted as study-level information (%_r...) by default. This
means that the report will be populated with the patient weight that was entered for the current study. Changing the tag to %_p... would instead result in
the report showing the weight that was entered for the first study that was performed on this patient in your cath lab five years ago.
Predefined blocks
Predefined set of system tables
Predefined blocks comprise factory predefined and non-customizable collections
of system groups. You can either insert an entire predefined block (for example,
Hemodynamics (1) block) or you can insert one or several of its sub-blocks (for example, Gradients from the Hemodynamics (2) block).
Instead of inserting hemodynamic data from system tables into a report in blocks
you might insert measured or calculated values individually from the Derived
Data section of the tag picker window.
Vital signs
With the AXIOM Sensis XP recording system you can acquire vital sign parameters during an examination and also import vital sign measurements from a connected Infinity patient monitor. The Infinity network connection allows you to
cover not only the period during the examination but also the pre-examination
and postexamination phase and include this information in your study report.
In the Report Composer you can choose to insert Sensis or Infinity vital sign data
in a report either as a table or as a graph (or both). You will find both the tags for
table and graph representation as predefined blocks in the tag picker window.
Note
Note, however, that Sensis vital sign data are stored in system groups. This
means that if you choose to include system groups in your report template in the
context of one of the output report clusters, this will ensure that Sensis vital sign
data tables will be shown in your report.
If you also included a VitalSigns predefined block this would show the vital sign
parameters acquired by your recording system twice in this report.
Therefore only insert a VitalSigns predefined block in a report template if you
have not already included system groups together with any of your output report clusters.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
171 / 456
System Administration
Images
Under the predefined blocks heading you will also find tags for the insertion of images in a report.
 Image (X-ray image)
– X-ray images will only be available in your AXIOM Sensis XP Information
System if you are using your AXIOM Sensis XP in conjunction with an Artis
or BICOR/Coroskop system.
 Waveform
– Waveform images are not actually waveform (signal) recordings. Waveform
images are image files in *.emf format (enhanced metafiles) displaying the
waveforms that were visible on the screen at the moment when the waveform image event was created.
 HPI (Heart Picture Illustrator) and CTI (Coronary Tree Illustrator)
– These will insert graphical report files, which you created with the AXIOM
Sensis XP Information System software options Heart Picture Illustrator
and Coronary Tree Illustrator in your study report.
Note
As an alternative to graphical display you can also show data from HPI or CTI reports in your Word reports as comma-separated lists.
Refer to Overview of system groups available for data export 273 for information on which systems groups contain HPI and CTI data.
Also refer to Tag syntax overview 181 for instructions on how to control
how this data will be output in the report.
 DICOM Image
– The AXIOM Sensis XP Information System can receive DICOM images over
the network from an imaging workstation or another modality.
– The DICOM images (for example, an IC3D image from a Leonardo workstation) can be shown in the AXIOM Sensis XP study report.
– Supported modalities are: XA (X-ray), US (ultrasound), MR (magnet resonance), CT (computed tomography), SC (secondary capture, not a modality
as such). For XA only single images but no scenes should be sent for optimum results.
 Ablation Graph Image
– In the AXIOM Sensis XP electrophysiology application an ablation procedure can be displayed graphically on a separate waveform card. Ablation
curve images can also be shown in the study report.
 Mapping System Image
– If your AXIOM Sensis XP electrophysiology application is connected to a
CARTO® mapping system, Sensis can import mapping system images into its
information system database and make these available for display in
reports.
172 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
When you insert an image in a report template this creates a placeholder for the
actual image, which will be inserted during report generation. You can resize this
placeholder to make sure the image is displayed large enough so that details are
clearly visible.
When a report is created on the basis of a report template that expects an image,
a dialog box opens and clinical users are prompted to select which of the images
of a category that is stored in the database for this study they want to show in the
report. If a user picks more than one image of a category (for example, more than
one X-ray image), these will all be shown in the study report.
Inserting a predefined block tag
 Click a Predefined Block or a sub-block and drag it into the Word window.
– A predefined block tag is added to the report: for example, <%#Misc.VitalSigns%>
Inserting images
 Click an image under Predefined Blocks and drag it into the Word window.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
173 / 456
System Administration
– A dummy image is inserted.
Note
Always insert images as predefined blocks by dragging and dropping them from
the tag-picker window. Never copy and paste a placeholder (dummy image) into
a report template.
Report templates into which you have copied and pasted image placeholders are
invalid. You cannot create study reports based on such templates.
Note
The AXIOM Sensis XP Information System expects imported DICOM images in
the import directory: \\"Host name of the SIS Server"\DICOM_Import$.
The user name and password for connecting to this folder on the AXIOM Sensis
XP Information System server will be provided on request by Siemens Service.
Make sure all systems that send DICOM images to the AXIOM Sensis XP Information System direct them to this folder on the AXIOM Sensis XP Information
System server.
174 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
Resizing images
 Click on the lower left-hand or right-hand corner of the dummy image.
 Keep the left mouse button pressed and drag diagonally out and down.
– If you just drag the width out, the system will ignore this as it would distort
the proportions of the image.
Inserting a vital signs graph
 Select the Vital Signs Graph or Infinity Vital Signs Graph item under Pre-
defined Blocks and drag it into the Word window.
– As soon as you release the mouse button the Insert Vital Signs Graph dialog box opens.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
175 / 456
System Administration
 Select the vital sign parameters that you want to show in your graph here.
 Also select where to plot a parameter: on the primary or secondary Y axis.
 Edit the parameter labels and graph heading, if required, and confirm with OK.
– The vital signs graph is inserted in your Word template as an MS Graph
object.
Changing the scale of vital sign graph axes
When you insert a vital sign graph, Word automatically defines the scale for the
graph axes in a way that is not particularly well-suited for the display of vital sign
data. You should therefore change these settings every time you insert a new vital
sign graph into a report template.
176 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
 Double-click the graph object in your Word template.
– The graph is now surrounded by a border, and an Excel datasheet with vital
signs data is shown.
 Right-click on the axis whose scale you want to change and select Format Axis
in the shortcut menu.
 In the Format Axis dialog box, move the Scale tab card to the foreground.
 Clear the Auto box for the Minimum, Maximum and Value (X) axis Crosses
at options.
 Enter a better range for the axis.
– For example: Minimum = 0, Maximum = 100,
Value (X) axis crosses at = 0
 Click OK to close the dialog.
 Click outside the graph object or press Esc to close the graph object.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
177 / 456
System Administration
Resizing a vital signs graph
 Double-click the graph object in your Word template.
– The graph is now surrounded by a border.
 Click on the lower left-hand or right-hand corner of the graph.
 Hold the left mouse button down and drag diagonally out and down.
– Do not just drag the width out as this would distort the proportions of the
graph.
Note
Be sure to always double-click before resizing a graph (the border must be
shown while you resize). If you resize the graph object immediately after inserting it (only grab handles are shown), as you would with an image tag, only the
graph representation in the report template but not in the final study report is
resized.
Note
If you wish to show many or all acquired vital sign parameters in a graph you will
have to resize it considerably to show all curves clearly.
You may consider reserving a full page for the graph and format this page as
landscape:
 Insert two section breaks in this case, one above and one below your graph
(Edit > Insert Section Break from the tag picker window menu).
 Place the cursor between the two section breaks and select File > Page Setup
from the Word menu bar.
 Move on to the Paper Size tab card and select Orientation: Landscape and
Apply to: This Section.
178 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
Reformatting other display settings
 Double-click the graph object in your Word template.
– The graph is now surrounded by a border.
 Right-click anywhere in this box or specifically on the legend or graph section
to open a menu with formatting options.
Derived data
Derived data are mostly hemodynamic data that were measured or calculated during an examination on the acquisition system.
The predefined blocks Hemodynamics (1) to (4) present these data in grouped
form, the Derived Data section of the tag picker window allows you to select and
insert these data into a report template individually.
The Derived Data section presents the tags you can pick from here in a structured
way. This is, however, a display mode only, it does not allow you to pick and insert
groups of data here. To select and insert one set of data at a time you will have to
use one of the predefined blocks or sub-blocks. For example, if you want to include all gradient measurements in your report template you will have to select
the sub-block Gradients under Predefined Block Hemodynamics (2). You cannot drag and drop the category Gradients under Derived Data.
Selecting a derived data tag
 Select a derived data item in the tag picker window.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
179 / 456
System Administration
– For Pressures and Gradients you can choose whether to pick and insert the
set of measured or calculated data for an entire site or just one of its component values.
– When you drop a derived data item in the Word window the Insert Derived
Data dialog box opens.
 Specify the condition the derived data value should be picked from.
These options are available:
 Specify when generating report
– An alternative to specifying a fixed condition number, which allows you to
pick derived data from different conditions during report generation. When
clinical users generate a report they will be prompted to select the condition
from which they want to pick this derived data value.
 Two conditions for comparison (Condition A or Condition B)
– If you are about to set up a comparison between derived data values from
two conditions (for example in a Word table side by side), you will select
Condition A for the first derived data item and Condition B for the derived
data item you want to compare the first one with.
– During report generation clinical users will be prompted to specify which
condition of this study should be represented by Condition A and which by
Condition B.
– By default, and unless changed during report generation, the system will
select the first available condition in a study as Condition A and the last
available condition as Condition B.
180 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
 Fixed condition number
– Select the condition number (Condition 1 = the first condition in the study,
Condition 2 = the second condition in the study, etc.)
Tag syntax overview
The intention of this section is to help you understand and interpret the tags you
will find in a report template. This section is not intended to encourage you to
build your own tag definitions.
Basic rules
 Each tag begins with a start marker and ends with a stop marker.
– <% .......... %>
 Seven tag types exist:
– <%$ ........ %> : Cluster tag (see Cluster tags)
– <%_ .......... %> : Single-line field (see Field tags)
– <%*........... %> : Multi-line field
– <%# ........ %> : Predefined block or sub-block (see Predefined blocks)
– <%& ..........%> : Derived data (see Derived data)
– <%&¤ ....... %> : Special derived data (for example, only 1 pressure value of
a site)
 Referential markers
– Field tags contain referential markers, which indicate the scope of the table
this value is to be taken from.
– <%..p .......... %> (patno) : from a patient table
– <%..r .......... %> (refno) : from a study table
Note
Syntax examples
Always check that all field tags that refer to study-related data (that is information that might differ from study to study) have the correct referential marker
before you save your new template. This is particularly important for field tags
that you typed manually into your report. Make it a habit to use the tag picker
window for dragging and dropping tags, particularly when you want to insert information from the patient and study categories.
 Cluster tag
1
2
3
4
5
6
<%$CInclSysTables.OS,XRAYSUM,FT,ID%>
(1) Start marker
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
181 / 456
System Administration
(2) Tag type indicator
– $ for “cluster”
(3) Sort criterion
– T - by time stamp (i.e chronologically)
– C - by category
(4) System tables
– InclSysTables - include system tables in report
– ExclSysTables - exclude system tables from report
Note
Inclusion of system tables should only be set for one output report cluster, preferably the During Cath cluster.
(5) Groups
– List of all customizable groups which are included in this output report cluster as defined in the DB Manager.
– Refer to the group definition file (rep.grp), which you can view in the DB
Manager, to understand these group names.
Note
With a printout of the rep.grp file at hand, you can remove or add groups here
by modifying the tag text.
(6) Stop marker
 Group representation
1
Time
Procedure
<%*rPR.TIM%>
<%*rPR.PROCEDUR%>
2
Groups are inserted in a study report template as tables (which can be reformatted
in Word) containing:
(1) Column headers
(2) Field tags
182 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
 Field tags
1
2
3
4
5 6
1
<%*rME.MEDIC%>
2 3
4
5
6
<%_ppatient.firname%>
(1) Start marker
(2) Tag type indicator
– * = multi-line field
– _ = single-line field
(3) Referential marker
– r = from study table (refno)
– p= from patient table (patno)
(4) Table name (see printout of rep.grp definition file)
(5) Field name
(6) Stop marker
 Derived data tags
1
2
3
4
5
1
<%&nc_204,1.13|1%>
2
3
4
5
<%&¤472,pv.press1/site=13|1%>
(1) Start marker
(2) Tag type indicator
– & = derived data
– &¤ = special derived data
(3) Site code
(4) Condition indicator
– |1 = explicitly set condition number for this tag
– |D = condition will be specified during report generation.
– |F = condition A (for a comparison of data, with the exact conditions to be
selected by the clinical user during report generation)
– |L = condition B
(5) Stop marker
 Predefined blocks
1
2
3
4
<%#Hemo1.*%>
1
2
3
4
<%#Hemo1.Heartrate%>
(1) Start marker
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
183 / 456
System Administration
(2) Tag type indicator
– # = predefined block
(3) Table name.Field name
– * = an asterisk indicates that all sub-blocks of this predefined block are to be
included.
(4) Stop marker
Syntax rules for comma-separated lists
When you insert group tags into a report template you can choose between two
output formats: output as tables or output as comma-separated lists.
See Inserting a group in a report template 168
By default comma-separated lists are unformatted. If you want to control the output format of a comma-separated list you can do so by manipulating its group tag
once you have inserted it in your report template.
The following format rules apply:
 Comments between items are enclosed in curly brackets: { ... }
– A comment can stand at the end of a field but not in front of it.
 ASCII codes are supported
 Curly brackets after the group name define what will be printed if the group
contains no data.
Syntax examples
 Comma-separated lists (without formatting)
1
2 3
4
5
6
<%*rCA.CATHETHER,CATHLEN%>
report text output
Judkins110,Rashkind80,...
This tag creates a list with data from the fields “catheter” and “cathlen” from the
group “CA”.
(1) Start marker
(2) Tag type indicator (* = multi-line field)
(3) Referential marker (r = from study table (refno))
(4) Group
(5) Fields
(6) Stop marker
184 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
 Comma-separated list (formatted)
1 2 3 4
5 6
7
8
9
<%*rC_LE.AHACODE{#09},INTERV1{#2C},SHAP{ Stenosis },STENOS{ %},FLOW{ flow#2C},ECCENTR{#2C},CURVAT{#0D}%>
report text output
Distal Right Coronary ArteryMedium Stenosis 81% Just visible flow, Eccentric, Moderately angulated
Proximal Right Coronary ArteryStent, Medium Stenosis 77 % Normal flow, Concentric, Non-angulated
(1) Start marker
(2) Tag type indicator (* = multi-line field)
(3) Referential marker (r = from study table (refno))
(4) Table name (see printout of cath.grp definition file)
(5) Field name
(6) ASCII code for:
– #0D = carriage return
– #09 = TAB
– #2E = .
– #2C = ,
– #7B = {
– #7D = }
– #25#3E = %>
– #3C#25 = <%
(7) Comments are only printed if the fields they belong to contain data. If a field
contains no data, the comment is suppressed.
(8) Spaces between items must be entered as comments: { }
(plain text spaces would cause an error during report generation).
(9) Comma-separated lists usually end with a comma unless you end the list with
a carriage return {#0D}
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
185 / 456
System Administration
Adding section breaks, unlocking, and
locking sections
You can allow users to add free text comments and conclusions to the final report
file. In order to do so, you define special sections for these text comments and unlock them to enable them for editing.
Default: no editing
By default the entire generated report file is locked (no text editing permitted).
This is to protect the data read from the information system database from intentional or accidental changes.
Word: section concept
Parts of a study report template are locked or unlocked based on Word sections.
Word allows you to subdivide a document into so-called sections and permits different sections to have different properties, for example, with respect to page settings or with respect to whether they are editable or not.
Technically speaking, a Word section is a range of text between two section
breaks. Removing a section break merges two sections and affects section properties.
Enabling a section for text comment entry
 Position the cursor in an empty paragraph in your Word template after which
you want the text comment section to start.
 Enter a section break (Edit > Insert Section Break).
 Enter two or three empty paragraphs in the Word template.
 Enter a second section break immediately.
 Position the cursor somewhere in the middle of the section you want to enable
for editing.
Note
Make sure you do not position the cursor on one of the section breaks.
 Click Lock/Unlock Section.
– This section is now enabled for editing, all other sections of the document
remain locked.
locked
unlocked
locked
186 / 456
AXA5-200.640.07.01.02
System Administration
Report Composer
Note
If you switched over to the normal contents editing view while inserting and
locking/unlocking sections, switch back to print layout with View > Print Layout
in the Word menu.
Previewing a report
For a better overview you can preview a report while you are editing a template.
Previewing means that the system creates a view-only dummy report file based on
the template you are currently working on and test data which you copied to test
mode in the Patient Explorer earlier. The system allows you to choose one of your
test studies for the report preview. The report preview is displayed in a new Word
window.
Previewing a study report
 Save the template in its current editing stage in Word.
– The template is saved as a *.dot file on your local hard disk, either on the
Desktop, in your MyDocuments, or in your MyFavorites folder, depending
on what you indicated when you opened the report template for editing.
– When you have finished editing and saved the new template back to the
database, you can remove this intermediate template version from your
hard disk again.
Note
Remember that Report Generator and Report Composer support Word 972003 *.dot files but not Word 2007 *.dotx files.
Do not save a template as a *.dotx file when you are working with Word 2007.
 Click Preview in the Report Composer toolbar.
– A dialog box opens requesting you to select a test study.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
187 / 456
System Administration
 Select a study and click OK.
– A new Word window opens which shows how a report based on this template would look if it were populated with real study data.
– You can leave this window open in the background while you continue editing your current template. Use Alt + Tab to switch back and forth between
the two Word windows.
 Close the preview window if you no longer need it.
Saving a report template and handling
versions
When you have finished editing your study report template you save it back to the
information system database. A new version of this template will be created in the
database.
Template versions in
the database
In the information system database old study report template versions are never
overwritten and replaced with new versions but versions will accumulate over
time (version 1 to n).
Active version
Only one template version can be active at any one time. When clinical users select
a template for a report they intend to generate, only the active version of that
template will be available to them.
Note
188 / 456
When you update a template, which means that you create a new version of it
on the server, this new version will not automatically be made the active one.
You always have to select an active version explicitly.
AXA5-200.640.07.01.02
System Administration
Report Composer
Saving an updated study report template back to the database
 Save the template in Word first.
– The *.dot file is saved on your local hard disk (on the Desktop, or under
MyDocuments or MyFavorites).
– You can remove it from there later on.
Note
If Word requests you to save Normal.dot, always confirm.
Note
Remember that Report Generator and Report Composer support Word 972003 *.dot files but not Word 2007 *.dotx files.
Do not save a template as a *.dotx file when you are working with Word 2007.
 Next save the template back to the database using the Report Composer icon
Save as template.
– The Save Template dialog box opens.
 Save the template under a new name or create a new version of an existing
template.
– When you save a template back to the server, all tags are checked for correct syntax and placement. If inconsistencies are detected, a message is displayed, informing you which tags need to be corrected.
– Correct these tags and save the template again.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
189 / 456
System Administration
Setting the active version
Note
Remember always to check the active version settings of a new or updated template. The active version will not be updated automatically.
If you have just created a new template and saved it back to the database under
a new name, even though only one version of this template exists in the database, this version is not activated automatically.
 Select Application > Set Active Template in the Report Composer menu.
– The Set Active Template version dialog box opens.
 Select the template whose active version you want to check or update.
– A list of all versions that are stored in the information system database for
this template is displayed in the Versions box.
– Usually one version is marked as the active one.
– If you select a completely new template that you just created, no version
will have been set to “active” yet.
 Click on the version you want to define as the active one.
 Click Set.
– This will now be the template version that clinical users will be offered
whenever they generate a report with this template.
190 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Communication Manager
Communication Manager overview
The Communication Manager allows you to define data transfer and study report
transfer jobs from the AXIOM Sensis XP Information System. These export jobs
are sent to a queue whenever a specified trigger event occurs. All jobs in the job
queue are executed by the background application Export Engine.
Overview of functions
Communication tasks
You use the Communication Manager for the following tasks:
 Defining data transfer jobs
– Config. tab card
 Viewing the export queue of pending jobs
– Queue tab card
 Viewing the export log
– Log tab card
Background information
In order to configure data exchange between the AXIOM Sensis XP Information
System and other systems efficiently, you need to know some background information about communication settings and format definitions.
You will find this information in the section Communication appendix 245.
Read this information to learn about how to change the communication port of
incoming HL7 messages and to make sure external sender or receiver systems
have been configured correctly.
Key terms and concepts
For information on the basic concepts the AXIOM Sensis XP Information System
uses to communicate with external systems refer to The communication and interface concept 46
Basic procedures
Use these icon buttons or menu items for editing on the various tab cards of the
Communication Manager window.
 Save (Application > Save)
– Saves changes to transfer jobs or newly created transfer jobs.
– Do not forget to save changes back to the database explicitly this way.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
191 / 456
System Administration
 Delete (Application > Delete)
– Deletes a transfer job.
– Remember that if you delete factory-defined transfer jobs there will be no
way of retrieving them.
 Clear (Application > Clear)
– Clears all entries from the input boxes on the current tab card.
Allows you to start your transfer job definition all over again.
– Clearing does not, however, reset your changes back to the last saved version in the database, it simply erases entries.
 Refresh (Application > Refresh)
– Updates the Communication Manager from the database.
Starting the Communication Manager
 Select AXIOM Sensis Information System > Server > Communication Man-
ager from the Windows Start menu.
– The Login dialog box for your administrator credentials is displayed.
 Enter your user name and password and click OK.
– User name and password are not case-sensitive.
Note
Only one instance of the Communication Manager can be open at a time. If the
Communication Manager is currently in use on any other PC of your cath-lab
information system you are denied access until that other instance has been
closed.
After logon, Communication Manager window is displayed.
192 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Defining data transfer jobs
 Display the Config tab card on top.
How to define a data
transfer job
To facilitate the task of defining data transfer a number of predefined transfer jobs
are provided with the system. In most cases, all you need to do to set up communication with other systems or define the output of study reports is to enable a
predefined transfer job and adjust a few parameters such as the destination.
For more specific communication requirements you can copy a predefined transfer job and adapt more parameters. You should, however, comment on your modifications in the job description box, if you choose this mode of working.
Expert users can, of course, also define communication jobs from scratch. This,
however, requires more than average knowledge of the information system architecture and database configuration.
Predefined transfer
jobs
Report distribution
The following transfer jobs are factory defined but disabled when the system is installed. Do not delete any of these predefined transfer jobs unless you are sure you
will no longer need them. It is not possible to retrieve factory-defined transfer jobs
once you have deleted them.
 Transfer DICOM reports back to recording application
– Study reports can be sent back to the AXIOM Sensis XP Acquisition System where the study was performed automatically or semi-automatically.
– From there, the DICOM report can be archived together with other study
data.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
193 / 456
System Administration
 Transfer DICOM reports over DICOM network to fix remote node
– Alternatively you may choose to send DICOM reports to a network address,
for example, a network archive.
 Print reports when closing study
– If automatic printing of reports has been enabled in the Configuration
Manager you define the printer and the printer settings here.
Exporting data to HIS/CIS
 Transfer HIS output file
– Output of study data to a hospital or cardiology information system as an
ASCII flat file.
 Transfer HIS output file, reports, images, and waveforms
– Transfer of the study report, X-ray images and waveform images together
with study data from the information system database to a hospital, radiology, or cardiology information system.
 Create HL7 ORU message
– Transfer of study data to a hospital or cardiology information system using
the HL7 standard.
– The HL7 message type ORU transfers study findings and clinical data.
 Create HL7 DFT message
– Transfer of cost information for a study from the information system database to a HIS/CIS as an HL7 message.
Export to a material
management system
Importing data from HIS/
CIS
Note
 Transfer material usage to material management system
– If your cath lab works with the material management system QSight, this
transfer job sends information about materials used during a Sensis study
back to the material management system.
 Import preregistered patients via ASCII flat file
– For import of preregistration data from a HIS/RIS or CIS system.
If your hospital, radiology, or cardiology information system communicates via
the DICOM standard, this cannot be configured in the AXIOM Sensis XP Information System.
DICOM communication is nevertheless possible but it uses a different path,
which is via one of the AXIOM Sensis XP Acquisition Systems in your cath lab.
DICOM communication is set up during system installation by Siemens Service.
As a system administrator you do not have access to this configuration platform
as it is protected by a service password.
194 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Data transfer settings and parameters
In order to adjust a predefined data transfer job you may have to change one of
the following parameters:
Job name and description
 Select a predefined job.
– The transfer parameters of this job are now displayed.
 Enter a new Job name to copy this job if you plan major adjustments.
– This will help you return to the factory default or check the factory default
parameters if problems arise with your own settings.
 Comment on your changes to the predefined job by adding text to the Job de-
scription.
Or
 As an expert user enter a Job name while the fields for all parameters are still
empty to start a transfer configuration from scratch.
 Also enter a Job description.
Job type and
job parameters
If you define a transfer job from scratch you first select what type of job you intend
to create.
If you are simply adapting a factory default transfer job you will not usually change
the job type but select a different factory default transfer job to start out from.
Depending on the Job type you select, different Job parameters are required.
 Select a Job type.
– A format parameter template appears in the Job parameters box.
Note
Job parameter templates indicate which parameters must or can be specified for
a job type. They appear in the PARAMNAME=<placeholder for value> form.
When replacing this placeholder with a value in your parameter definition be
sure to remove the angle brackets (< ... >).
Straight lines ( | ) indicate definition alternatives (PARAMNAME=<abc|xyz>).
When you encounter these in a job parameter template choose one of these alternatives and remove the other (for example, PARAMNAME=abc).
Run user-defined BAT
file (output file)
This job type is intended for use with the Export Engine to run a user-defined
script (batch file) which creates an output file.
This job type suggests the following Job parameters template:
FILENAME=<BAT file path>&P_1=<Param1>&P_2=<Param2>&P_3=<Outfile>&COLUMN_1=<content>
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
195 / 456
System Administration
Explanation of required and optional parameters:
 FILENAME=<BAT file path>
– Whenever you use the Export Engine to run a batch file (command file) you
must indicate where in the file system of the information system server the
Export Engine will find this batch file.
 P_1=<Param1>, P_2=<Param2>, P_3=<Outfile> (optional)
– P_n parameters specify parameters for the execution of the batch file that
change for each transfer job to be performed.
– The user will be prompted by the Transfer Agent to specify these parameters for each job.
Note
If you specify P_1 to P_n for a batch file execution you must also select Distribution method Manual.
If you select Automatic, Transfer Agent will not open, users will not be prompted to enter these parameters for the job at hand, and the batch file will probably
not be executed properly.
– <Param1> is a placeholder for the parameter name in Transfer Agent. For
example, P_1=Name will be displayed as shown in this screenshot.
– You may also suggest a default value for a P_x parameter which users can
accept or overwrite in Transfer Agent when they are prompted to confirm
execution of the transfer job and its parameters. For example:
P_1=Dept.%Cardiology will suggest Cardiology as the default for the entry
of the department where the study was performed.
196 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
– P_3=<Outfile> suggests that you might want to prompt the user to enter a
name for the output file to be created by the batch file. If your batch file
takes care of the naming of the output file you may remove this parameter
or use P_3 for some other purpose. If you intend to prompt for entry of an
output file name, then replace <Outfile> with Output file, for example, or at
least remove the angle brackets: Outfile
– P_4 ... P_n: If your batch file requires entry of more variables you can add
these to the job parameter definition.
 COLUMN_1=<content> (optional)
– A batch file might be written in such a way that the content, which is the
name of the output cluster to be processed, is important information. Which
cluster to process will control the way the batch file is executed in this
example. In this case the user must specify this in the job parameters as:
…&COLUMN_1=content.
– Other transfer job definition parameters can also be made available for the
batch file execution, for example:
…&COLUMN_1=trigname&COLUMN_2=format
– These are the parameters from the system group TRANSFER CONFIGURATIONS that can be used in a Run batch file job type definition:
cfgname - job name
cfgdesc - job description
format - job type
ftmparam - job parameters
content - name of output cluster selected
distrib - distribution method
trigname - name of the event that triggers job execution
sndtype - transfer method
sndparam - transfer parameters
retryint - retry interval
maxretry - maximum number of retries
 FIXVALUE_1=<value 1> ... FIXVALUE_n=<value n> (optional)
– Allows you to specify fixed values for the batch file execution.
– These are parameters that you enter here during transfer job definition and
which are valid for all transfer jobs of this type.
 PATTERN=<study(patno,refno).ext> (optional)
– This controls automatic naming of the output file. It will give the output file
a name that is composed of the patient number + study number, thereby
ensuring the output file name is unique. You can specify an extension for
the output file here, if this is not created automatically by the batch file.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
197 / 456
System Administration
Note
“patno” and “refno” are internal information system identification numbers for a
patient and study. They do not correspond, for example, to the Patient ID you
enter during patient registration.
You cannot deduce the patient name and study description and date from the
patno_refno_xxx.ext naming convention. Nevertheless, do not replace this filename pattern with any other definition that seems easier to identify because
only the patno_refno_... convention guarantees unique export file names. If export file names are not unique the files from different export jobs may overwrite
each other in the destination directory.
Run user-defined BAT
file (no output file)
This job type is intended for use with the Export Engine to run a user-defined
script (batch file) which does not create an output file.
This job type suggests the following Job parameters template:
FILENAME=<BAT file path>&P_1=<Param1>&P_2=<Param2>&COLUMN_1=<content>
Explanation of required and optional parameters:
 FILENAME=<BAT file path>
– Whenever you use the Export Engine to run a batch file (command file) you
must indicate where in the file system of the information system server the
Export Engine will find this batch file.
For an explanation of other optional parameters see Run user-defined BAT file
(output file)
Note
Create HIS output file
Concerning both job types: Run user-defined BAT file (output file) and Run
user-defined BAT file (no output file): We strongly recommend that you contact the Siemens development team (through your Siemens sales representative
or Siemens Service) for advice if you intend to work with batch files.
Creates an ASCII flat file to be sent to a specified destination.
This job type suggests the following Job parameters template:
FILENAME=<C:\MIS\CCNSW\HIS.BAT>&FIXVALUE_1=179&FIXVALUE_2=3&FIXVAL
UE_3=196 &PATTERN=<study(patno,refno).his>&DATEFORMAT=<MDY4/|DMY4|...>
Explanation of required and optional parameters:
 FILENAME=C:\MIS\CCNSW\HIS.BAT
– This indicates the location of the batch file which will convert the selected
data to the HIS exchange format.
198 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Note
Do not change this part of the Format parameter specification.
 FIXVALUE_1=179
– Defines the ASCII-code for the separator between fields. In the factory
default “179” is used.
– You only need to change this if this character occurs as a value in your database.
 FIXVALUE_2=2
– Defines what will be exported from fields that were filled from dictionaries.
– FIXVALUE_2 = 1 will export the code number of the selected dictionary
entry for fields.
– FIXVALUE_2 = 2 will export the description text of the selected dictionary
entries.
– FIXVALUE_2 = 3 will export both code number and description text.
 FIXVALUE_3=196
– Defines the ASCII-code for the separator character between dictionary code
and description text if FIXVALUE_2 = 3.
– “196” used to be adequate when Cathcor style was required (parameter
CODEPAGE437).
– “178” is adequate if you are using the Sensis character coding system
(Latin-1).
 PATTERN=<study(patno,refno).his>
– Defines the pattern for the creation of the output file name.
– With this definition the output file name is a unique number composed of
patient number + study number and the file extension *.his.
– You can add the study date to this file name definition:
PATTERN=study(patno,refno,studate).his
This creates an output file with the following file name:
798_811_2009-03-03_000000.his, where 798 is the patient number, 811 is
the study number, 2009-03-03 is the study date, and *.his is the extension.
 DATEFORMAT=<MDY4/|DMY4-|...>
– Defines the format in which dates are exported in the HIS output file.
– For example, “MDY4/” exports dates in the format MM/DD/YYYY
(12/24/2004“, DMY4.” exports dates as DD.MM.YYYY (24.12.2004), or
“Y4MD-” in the format YYYY-MM-DD (2004-12-24).
– A straight line ( | ) in the definition templates indicates that these examples
are alternatives, dots ( ... ) indicate that other combinations are also possible.
Note
AXIOM Sensis XP (VC11)
Choose one alternative, remove the other and also remove the angle brackets
(for example, DATEFORMAT=MDY4/).
AXA5-200.640.07.01.02
199 / 456
System Administration
 CODEPAGE437 (optional)
– This parameter was used to support the old Cathcor character coding.
 CATHCORMODE (optional)
– This parameter should be used if the PATIENT and STUDY tables are not to
be exported.
 SHOWDATETIME (optional)
– The full date and time are exported (only for database fields defined as T5
(hh:mm) or T8 (hh:mm:ss)).
 EXCLUDE_WASTE (optional)
– If an export job to the HIS/RIS or CIS system includes material management
information this parameter excludes material that has been classified as
Waste in Documentation Tool. The export job will only send information
about material classified as Used.
Note
Create HL7 messages
If comment texts that had been entered on the acquisition system contain line
feeds (carriage returns), these line feeds are removed from the text in a HIS output data transfer job. The line feeds are automatically replaced by blanks.
This job type creates a message according to the HL7 standard.
This job type suggests the following Job parameters template:
MESSAGE=<ORUR01|DFTP03>
Explanation of required and optional parameters:
 MESSAGE=<ORUR01|DFTP03>
– Two HL7 messages can be created by the AXIOM Sensis XP Information
System for transfer to a hospital, radiology or cardiology information system: ORU01, for study findings and clinical data, and DFTP03, for transfer of
cost information.
– If your AXIOM Sensis XP Information System is connected to a departmental material management system, the two systems also use HL7 messages of type DFTP03 to communicate information about material usage
(inbound and outbound).
 SHOWDATETIME (optional)
– The full date and time are exported.
– Only for database fields defined as T5 (hh:mm) or T8 (hh:mm:ss).
200 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
 USE_RECEIVED_MSH_DATA (optional)
– When the AXIOM Sensis XP Information System receives HL7 messages
containing registration data these messages contain message header (MSH)
information that will be stored in the information system database. This
MSH information can be sent together with an ORU or DFT message.
 MSH_3_1=XX&MSH_3_2=YY ... (optional)
– Allows you to define values for export fields for the message header segment. These parameters require that a value is specified, for example,
MSH_3_1=SENSIS.
– These message header text fields can be sent:
MSH_3_1 (SendingApplication.NamespaceID), setting this value overwrites
any value saved from the registering message.
MSH_3_2 (SendingApplication.UniversalID).
MSH_4_1 (SendingFacility.NamespaceID), setting this value overwrites any
value saved from the registering message.
MSH_4_2 (SendingFacility.UniversalID).
MSH_12 (VersionID.VersionID).
 HL7_VERSION (optional)
– HL7 messages include information about the HL7 version supported by the
sender system. By default this is 2.4 for messages sent from the AXIOM
Sensis XP Information System.
– With this parameter you can change the version information sent with outgoing HL7 messages. Set this parameter to 2.3, for example, to make messages sent by Sensis compatible with HIS/RIS or CIS systems that support
this previous HL7 version.
– The AXIOM Sensis XP Information System does not support HL7 3.0,
therefore do not enter this version information here.
 SENDING_APP_UNI_ID (optional)
– Sets the value of the SendingApplication.UniversalID field in the MSH segment, for example, SENDING_APP_UNI_ID=Sensis1234.
 SENDING_FAC_UNI_ID (optional)
– Sets the value of the SendingFacility.UniversalID field in the MSH segment,
for example, SENDING_FAC_UNI_ID=CathLab1.
 SAVE_REPORT_PATH (optional)
– Specifies the path where the report file is stored. Sending this information is
required if the path name is meaningful to the receiving system. For example, to enable the receiving system to access a shared folder on the information system server to pick up the report.
 TEMPLATE (optional)
– Allows filtering of reports by template type. The specified reports are
exported in the reports export job, for example, TEMPLATE=Hemo1.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
201 / 456
System Administration
Explanation of optional parameters for ORU messages:
 FREE_TEXT_AS_OBX (optional)
– With this parameter set data from free text groups are included as OBX segments and not as NTE segments. The OBX.ValueType field is set to FT (formatted text) for these segments.
 FLAT_DATA (optional)
– Sends all clinical data in one OBR segment (as opposed to having one OBR
segment for each condition).
 VA_VISTA (optional)
– This parameter must be set when sending HL7 messages to a Veterans
Affairs (VistA) system.
 OBR segment configurable fields (optional)
– Allows you to define the contents of the following fields in the message
header for ORU messages:
OBR_20 (OBR.FillerField1)
OBR_25 (OBR.Result Status)
OBR_35 (OBR.Transcriptionist)
OBR_32 (Primary Results Interpreter)
OBR_40 (Transport Arrangement Responsibility).
– When configuring these fields in an export job specify:
OBR_35 = (tableName, columnName), to assign a value from database, or
OBR_35 = value, to assign a value directly.
Explanation of optional parameters for DFT messages only:
 CODE1 to CODEn (optional)
– The AXIOM Sensis XP Information System supports the mapping of database contents (values) to codes that comply with coding schemes for health
care providers (for example, ICD 9/ICD10/CPT/ACP/DRG).
– Implementation of these coding schemes is slightly different for ORU and
DFT messages. DFT messages require specification of the coding scheme
using the job parameter CODE.
For details of how to implement a coding scheme for DFT messages see Create
HL7 DFT message 226
 PROC_AS_FT1 (optional)
– Sends procedure information as FT1 segments instead of PR1 segments.
 DIAG_AS_FT1 (optional)
– Sends diagnosis information as FT1 segments instead of DG1 segments.
 FT1_TRANS_CODE_ONLY (optional)
– Only sets the TransactionCode.Identifier field but leaves the TransactionCode.NameOfCodingSystem and TransactionCode.Text fields empty for all
FT1 segments.
202 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
 FT1 segment configurable fields (optional)
– Allows you to define the contents of the FT1_13 (DepartmentCode.Identifier) and FT1_16 (AssignedPatientLocation.PointOfCare) fields in the message header for DFT messages.
 EXCLUDE_WASTE (optional)
– For export jobs to a HIS/RIS or CIS system that include material management
information and for exports jobs directly back to the departmental material
management system.
– This parameter excludes material that has been classified as Waste in Documentation Tool. The export job will only send information about material
classified as Used.
Create XML reports
Note
This job type exports data from the information system database to an XML file.
Do not let the word “report” in this job type confuse you. It refers to data from
database tables that are to be exported here, not study reports.
This job type suggests the following Job parameters template:
PATTERN=<study(patno,refno)>
This controls automatic naming of the output file and creates a unique number
composed of patient number + study number.
You can add the study date to this file name definition:
PATTERN=study(patno,refno,studate)
This creates an output file with the following file name pattern:
798_811_2009-03-03_000000.xml, where
798 is the patient number, 811 is the study number, 2009-03-03 is the study date,
and *.xml is the extension.
Transfer reports [DOC,
RTF, PDF]
This job type outputs study reports created by Report Generator in the format
specified under Job parameters:
WORDFORMAT=<FORMAT_RTF|FORMAT_DOC|FORMAT_PDF>&PATTERN=<study(patno,refno)>&TEMPLATE=<first template name|second template
name|...>&SAVE_REPORT_PATH=<path reports are copied to>
Explanation of required and optional parameters:
 WORDFORMAT=<FORMAT_RTF|FORMAT_DOC|FORMAT_PDF>
– Here you specify if you want to export a study report as an *.rtf (rich text
format), *.doc (Word for Windows file), or *.pdf (Adobe Acrobat portable
document format) file.
– Choose one of these options (for example, WORDFORMAT=FORMAT_PDF
creates a *.pdf file of a study report)
– For creation of a *.pdf file, default Acrobat Distiller settings will be used.
You cannot change these settings.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
203 / 456
System Administration
 PATTERN=<study(patno,refno)> (optional)
– This parameter controls the file name prefix.
– With this definition the output file name is a unique number composed of
patient number + study number.
– You can add the study date to this file name definition:
PATTERN=study(patno,refno,studate)
This creates an output file with the following file name pattern:
798_811_2009-03-03_000000_Flowsheet_(C).doc, where:
798 is the patient number, 811 is the study number, 2009-03-03 is the
study date, Flowsheet_(C) indicates what template the report is based on,
and *.doc indicates that it is a Word file.
 TEMPLATE=<first template name|second template name|...> (optional)
– This parameter allows you to specify which study reports to consider in a
transfer job in terms of the report templates that were used to create the
report.
– TEMPLATE=Summary|Flowsheet (T), for example, would only create and
send the *.doc, *.rtf, or *.pdf version of study reports based on the Summary or Flowsheet (T) templates, but would ignore study reports based on a
Flowsheet (C) template.
 SAVE_REPORT_PATH=<path reports are copied to> (optional)
– Saves the network path defined in the transfer parameters (DESTDIR) for the
transfer method FileCopy. When specified, each report that is exported has
its filename and the path saved in the EXPPATH group. If this group is
included in an output cluster then it is possible to export this information.
– The path plus file name information can be sent to the HIS/RIS or CIS
together with the study results and findings in an HL7 message of the
ORUR01 type. This informs the HIS/CIS system where (network address) to
look for the report on the AXIOM Sensis XP Information System server.
See FileCopy 209
The file that will be output as specified here can either be sent to another computer, emailed, printed, or faxed. You specify these details under Transfer method
and Transfer parameters.
See Configuration of data export jobs to HIS/CIS system 222.
Create DICOM reports
This job type creates a DICOM report, which is basically a study report printout
transferred to an image file and enhanced with DICOM header information. DICOM reports can be viewed on DICOM workstations that are equipped with an image viewer. DICOM reports can also be archived together with other study data
such as event, presentation, and waveform series, which are also DICOM objects.
The DICOM header information sorts the DICOM report in with the correct patient
and study on the receiving system (DICOM workstation or archive).
The job type Create DICOM reports offers the following Job parameters template:
PCLPRINTER=\\<server>\<pcl printer>
204 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Explanation of required and optional parameters:
 PCLPRINTER=\\<server>\<pcl printer>
– This specifies a PC in your network where a PCL printer driver is installed.
Note
We suggest you simply enter PCLPRINTER=HP LaserJet 4100 PCL 6 here.
This PCL printer driver is automatically installed on the information system server PC. As the Export Engine software (which executes all transfer jobs) also runs
on the information system server, the printer can be treated as a local printer
and no network path needs to be entered.
Transfer HIS output file,
reports, images, and
waveforms
This is a combined job type which:
 creates an ASCII flat file just as Create HIS output file does,
 outputs study reports as Word, RTF or PDF files,
 outputs X-ray images as bitmap files, and
 also sends waveform images as Windows *.emf files (enhanced metafiles).
This job type suggests the following Job parameters template:
FILENAME=C:\MIS\CCNSW\HIS.BAT&FIXVALUE_1=179&FIXVALUE_2=3&
FIXVALUE_3=196& PATTERN=<study(patno,refno).his>&DATEFORMAT=<MDY4/
|DMY4-|...>& WORDFORMAT=<FORMAT_RTF|FORMAT_DOC|FORMAT_PDF>&
XRAY=<YES|NO>&WAVEFORM=<YES|NO>
Explanation of required and optional parameters:
 FILENAME=C:\MIS\... &DATEFORMAT=<MDY4/|DMY4-|...>
Refer to the job parameters description under Create HIS output file
 WORDFORMAT=<FORMAT_RTF|FORMAT_DOC|FORMAT_PDF>
Refer to the job parameters description under Transfer reports [DOC, RTF, PDF]
Note
The PATTERN parameter will also apply to the reports files and create unique file
names composed of patient number + study number + template name + format
extension.
See job parameters description under Transfer reports [DOC, RTF, PDF]
203.
 XRAY=<YES|NO> (optional)
– This parameter lets you decide whether to export X-ray images as bitmaps
together with the other study data.
– If XRAY=YES, then the naming conventions set under PATTERN will apply
here too (for example, 798_811_xray_1.bmp)
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
205 / 456
System Administration
 WAVEFORM=<YES|NO> (optional)
– This parameter lets you decide whether to export waveform images as
*.emf files together with the other study data.
– If WAVEFORM=YES, then the naming conventions set under PATTERN will
apply here, too (for example, 798_811_waveform_1.emf)
Content
 Select ***Not Applicable*** for study report export.
Or
 Select the output cluster that contains the data that you want to export.
– Before you can select an output cluster here, you need to define it in the DB
Manager.
– The AXIOM Sensis XP Information System can export information from
both customizable and system groups. The groups definition file rep.grp
provides an overview of all customizable groups (database tables). System
groups (also called Cath data groups) are not available to system administrators to edit. You can, however view and print a list of these groups.
– In the content drop-down list you will find a complete list of all output clusters (“O” clusters) defined in your system (file cathcor.clu, which can be
edited in DB Manager).
Note
Always verify in DB Manager that the output cluster you select here actually
contains all the groups that you want to transfer.
Refer to Editing clusters 106 and Printing group definition files 101
Also refer to Overview of system groups available for data export 273 for
a description of system groups in the information system database whose data
can be exported to other systems.
Note
Use the HIS transfer output cluster only in transfer jobs of the Create HIS output file job type.
Different cluster definition syntax rules apply to this job type. HIS transfer has
been customized in a way that specifically meets these requirements. If you use
Content: HIS transfer in other transfer job types this will probably not send the
data you actually want to send.
For details refer to Editing clusters 106 and Syntax for the cluster definition
file (cathcor.clu) 111
206 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Note
Regarding the precision of float values in HIS output files and HL7 outbound
messages Sensis VC03C and higher formats FLOAT values in output files as defined in the information system database (rep.grp: user-configurable database
tables, cath.grp: read-only system tables).
For example, an element defined as "SF, 5.2" in rep.grp will be exported as a
float value with 2 digits after the decimal point.
Distribution
These options are available:
 Automatic
– When the specified trigger event occurs, the transfer job is automatically
moved on to the Export Queue and executed the next time the Export
Engine runs (next minute). The user will not be prompted to confirm.
– If the trigger is activated by the user (for example, “Export Study”, “Transfer
Reports”, “Email Reports”, or “Fax Reports”) a message box opens informing
users that jobs have been added to the Export Queue.
 Manual
– When the specified trigger event occurs, the Transfer Agent window
opens, prompting clinical users to confirm execution of this transfer job.
– Only when the user confirms the transfer job will it be moved on to the
Export Queue and then executed the next time the Export Engine runs
(next minute).
 Disabled
– Transfer jobs that are disabled are not executed by the system.
– Use this parameter if you want to deactivate a transfer job temporarily
rather than delete it permanently.
All factory-default transfer jobs are disabled directly after system installation.
 Select Automatic or Manual for a predefined transfer job that you want to ac-
tivate.
Trigger
Here you specify when in the clinical workflow this transfer job is queued for execution. These options are available:
 ***Not Applicable***
– This option is reserved for system-internal transfer jobs, which are sent to
the Export Queue independently of the clinical workflow.
 Approve Study
– The transfer job is sent to the Export Queue when the study is set to
“approved” by a clinical user in Patient Explorer.
 CATHCOR Study
– This option is reserved for data exchange with Cathcor recording systems
and therefore only relevant in legacy system configurations.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
207 / 456
System Administration
 Close Study
– The transfer job is sent to the Export Queue when the study is closed on
the AXIOM Sensis XP Acquisition System (Patient > Close Study).
 Export Study
– The transfer job is sent to the Export Queue when a clinical user selects the
study and clicks the Export Study icon in Patient Explorer.
 Transfer Reports
– The transfer job is sent to the Export Queue when a clinical user selects
Report > Transfer in the Patient Explorer menu.
 Fax Reports
– The transfer job is sent to the Export Queue when a clinical user clicks the
Fax Report icon (or selects Report > Fax) in Patient Explorer or Report
Generator.
 Mail Reports
– The transfer job is sent to the Export Queue when a clinical user clicks the
Email Report icon (or selects Report > Email) in Patient Explorer or Report
Generator.
 Sender Internal
– Not triggered by users. The job is executed every time Export Engine runs.
Transfer method and
Transfer parameters
BAT
 Select a Transfer method.
– A format parameter template appears in the Transfer parameters box.
– This indicates that parameters must or can be specified for this send
method.
In this Transfer method a batch file is started. How and where data are actually
sent is defined in the batch file.
This transfer method offers the following Transfer parameters template:
FILENAME=<BAT file path>&P_1=<Param1>&P_2=<Param2>&P_3=<Outfile>&COLUMN_1=<content>
Explanation of required and optional parameters:
 FILENAME=<BAT file path>
– Whenever you use the Export Engine to run a batch file (command file) you
must indicate where in the file system of the information system server the
Export Engine will find this batch file.
For a description of all optional parameters refer to Run user-defined BAT file (output file) 195
FAX
Allows you to fax reports to a predefined fax number.
Faxing study reports is only possible if the information system server is installed
on a dedicated server PC, and a fax modem has been installed on this server PC.
208 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Note
You can only specify one receiving fax number per transfer job. This means that
this transfer job will always fax to the same fax number.
For details on how to define transfer jobs that send out study reports as faxes
refer to Fax study report to predefined fax number 235
This transfer method offers the following Transfer parameters template:
PHONENUMBER=<receiving fax number>&FAXSERVER=\\<server>
Explanation of required and optional parameters:
 PHONENUMBER=<receiving fax number>
– Enter the phone number of the receiving fax machine here.
 FAXSERVER=\\<server>
– This is the name of the PC the fax is connected to (for example, the local PC
name if the fax is connected locally, or the name of the PC a network fax is
connected to).
FileCopy
Copies the output file created by the transfer job to the directory you specify here.
This transfer method offers the following Transfer parameters template:
DESTDIR=<destination path>&DESTFILE=<file name>
Explanation of required and optional parameters:
 DESTDIR=<destination path>
– The full path of the directory to which the generated file is copied (complete
network path or local path).
– If no destination directory is entered here, files are copied to the USER root
directory.
– For export jobs that copy files to a network share make sure the network
share name does not contain any of these characters: ? + [ ] < > * ^
 DESTFILE=<file name> (not recommended)
– The name of the output file.
– Never specify DESTFILE. It might result in output files overwriting each other
in the destination directory.
FTP
Allows you to send files via FTP (file transfer protocol).
This transfer method offers the following Transfer parameters template:
HOST=<hostname|ip address>&DESTDIR=<directory path>&USER=<user name>&
PASSWORD=<password>&UNIXHOST=<YES| NO>&PASSIVEMODE=<YES|NO>&BINARYMODE = <Yes|No>
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
209 / 456
System Administration
Explanation of required and optional parameters:
 HOST=<hostname|ip address>
– The computer name or IP address the file will be transferred to, i.e. the computer that has the ftp server running on it.
– Alternatively you may enter the IP address of the ftp server in your hospital
network.
 DESTDIR=<directory path>
– The directory that the file will be transferred to.
– The directory path name must not contain any of these characters:
?+[]<>*^
 USER=<user name>
– The name of a user who has permission to transmit data to the ftp server.
 PASSWORD=<password>
– The password of the above specified user.
 UNIXHOST=<YES|NO> (optional)
– This parameter defines that Unix conventions are to be used for directory
path notation (back slashes are replaced by slashes for Unix systems).
– Enter UNIXHOST=YES if the receiving system is a Unix system.
 PASSIVEMODE=<YES|NO> (optional)
– This controls whether the job sent uses active or passive FTP mode.
 BINARYMODE = <Yes|No> (optional)
– This parameter controls whether files are transferred in binary mode.
– Always use binary mode if the receiving system is a Unix system and the file
that is sent is not a *.txt file.
– If binary mode is not used to transfer *.doc and *.pdf files to a Linux/Unix
target, the files will be corrupted.
HL7
Sends data to a network address, for example an HL7 server.
This transfer method offers the following Transfer parameters template:
HOST=<hostname|ip address>&PORT=<port number>
Explanation of required and optional parameters:
 HOST=<hostname|ip address>
– The computer name or IP address the file will be transferred to. This has a
TCP/IP connection that has been set up to listen for HL7 messages from your
AXIOM Sensis XP Information System.
 PORT=<port number>
– The port number on the HOST computer.
210 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
 HOLD_CONNECTION (optional)
– As a rule, the TCP/IP connection is disconnected after an export job has been
sent. Adding this transfer parameter will keep the connection alive, which
some receiving systems require.
– HOLD_CONNECTION is required in DFTP03 messages that are sent to the
material management system QSight.
– Refer to the specification of the receiving system to find out if this parameter is required in HL7 messages sent from the AXIOM Sensis XP Information System or not.
PRINTER
Note
Selecting PRINTER allows you to specify a printer on which the reports are to be
printed out. Both black and white and color printers are supported.
Selecting PRINTER as the transfer method only makes sense for transfer jobs that
send study reports.
This transfer method offers the following Transfer parameters template:
PRINTER=\\<server>\<printer>
Explanation of required and optional parameters:
 PRINTER=\\<server>\<printer>
– Address of a printer in your network.
– If this printer is connected locally to a PC in your network, then replace
<server> with the PC name or IP address, and <printer> with the shared
printer name.
– If the printer is installed as a network printer or locally at the information
system server PC then indicating the printer name is sufficient.
If you want to print out reports from different AXIOM Sensis XP recording systems on different printers, this can also be specified in the PRINTER parameter.
This way you can direct the report output to a printer in the examination room or
close by.
 PRINTER=\\SensisServer\HP LaserJet 4100 PS
– All study reports will be printed on an HP LaserJet 4100 PS printer connected
to the AXIOM Sensis XP Information System server.
 PRINTER_Sensis1=\\Sensis1\HP LaserJet 2200 S&
PRINTER=\\SensisServer\HP LaserJet 4100 PS
– Reports for studies created in the lab with the dialog computer named
"Sensis1" will be printed on the printer specified by parameter
PRINTER_Sensis1. All other study reports will be printed out on the printer
specified by parameter PRINTER.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
211 / 456
System Administration
 PRINTER_Sensis1=\\Sensis1\HP LaserJet 2200 S&
PRINTER_Sensis2=\\Sensis1\HP LaserJet 2200 S&
PRINTER_Sensis3=\\Sensis3\HP LaserJet 2200&
PRINTER=\\SensisServer\HP LaserJet 4100 PS
– As PRINTER_Sensis1 and PRINTER_Sensis2 refer to the same printer, reports
for studies created in the labs "Sensis1" and "Sensis2" will be printed out on
the same printer. Reports for studies created in the lab with the dialog computer named "Sensis3" will be printed out on the printer specified by parameter PRINTER_Sensis3. All other study reports will be printed out on the
printer specified by parameter PRINTER.
SMTP
Note
Transfer method SMTP allows you to send reports to one or several predefined
email address as an attachment.
If you create an e-mail job with several e-mail recipients, and one of the e-mail
addresses is incorrect, none of the e-mails will be sent.
 Check the Export Log in Communication Manager at regular intervals.
 Correct the e-mail addresses for failed jobs.
For details on how to define transfer jobs that send out study reports by email refer to Email study report to predefined mail address 238.
This transfer method offers the following Transfer parameters template:
MAILSERVER=<Mail server name>&TO=<email address>&CC=<email address>&BCC=<email address>&FROM=<email address>&SUBJECT=<Email subject
text>&BODY=<Email body text>
Explanation of required and optional parameters:
 MAILSERVER=<mail server name>
– The name or IP address of the SMTP server.
 TO=<email address>
– The destination email address
– Use a semicolon ( ; ) if you want to send reports to more than one email
address with one transfer job.
For example, “TO= alan.smith@siemens.com;john.doe@siemens.com”
 CC=<email address> (optional)
– The email address for a carbon copy.
– Use a semicolon ( ; ) if you want to send a copy to more than one email
address.
For example, “TO= alan.smith@siemens.com;john.doe@siemens.com”.
 BCC=<email address> (optional)
– The email address for a blind carbon copy.
212 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
– Use a semicolon ( ; ) if you want to send a blind carbon copy to more than
one email address.
For example, “TO= alan.smith@siemens.com;john.doe@siemens.com”.
 FROM=<email address> (optional)
– This parameter should be specified because the AXIOM Sensis XP Information System does not have an email account of its own.
 SUBJECT=<EMAIL subject text> (optional)
– Text that is in the subject of the email
 BODY=<Email body text> (optional)
– A body text to be sent with the email
Note
The tag ***PATIENT*** can be used in the subject line.
In the email, ***PATIENT*** will be replaced with the name of the patient
whose data is sent.
For example, SUBJECT=Reports for patient: ***PATIENT*** will appear in the
email as “Reports for patient: John Doe”, for example.
NOSEND
Retry interval
This transfer method is reserved for system-internal transfer jobs and batch files
that do not send data (for example, for transfer jobs that fetch data).
 Enter the Retry interval in minutes.
– The Export Engine will execute the job again after the specified time if the
first attempt fails.
– Note that Export Engine will only retry if the problem occurs when it
attempts to send the data. If the problem occurs during export file generation then no retry will be attempted.
Max. retry
 Enter the maximum number of retries in the Max. retry box.
– Use this field to prevent the system from being busy endlessly retrying to
send transfer jobs that cannot be sent for a particular reason.
– If the transfer job cannot be sent after the number of retries specified here,
the action will be aborted. An error message will be created and entered in
the Export Log. The Export Log can be viewed on the Log tab card of the
Communication Manager.
On success/On failure
 Select a transfer job that Export Engine will process immediately after per-
forming the current job sucessfully or that it will perform if the current job fails.
– Use these boxes to define sequences of transfer jobs, which will be executed one after the other, or alternative jobs in case transfer jobs fail.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
213 / 456
System Administration
Description of predefined transfer jobs
A number of predefined transfer jobs are provided with the system.
These transfer job templates help you to define communication between your AXIOM Sensis XP Information System and other systems, such as a HIS/RIS or CIS
(hospital, radiology or cardiology system) in your hospital, for example. These factory default transfer jobs also contain configuration examples for automatic report distribution. In most cases you will not have to change many parameters in
these predefined transfer jobs.
You will simply activate a job and define user-specific transfer parameters, such as
to where in your hospital network you want to send the data.
Configuration of automatic or semi-automatic report distribution
This section explains those predefined transfer jobs that help you configure report
distribution and printout.
Transfer DICOM reports back to recording application
This transfer job creates DICOM reports from all reports created for a study with
the Report Generator.
The transfer job is intended to be configured to send these reports back to the AXIOM Sensis XP acquisition system the study was performed on. Here, these DICOM reports are listed in the Patient Browser as data objects (series level) that
belong to a study. From the Patient Browser of the acquisition system you can
then archive the DICOM reports together with the waveform, events, and presentation series, and all X-ray images stored for this study.
Note
214 / 456
You cannot view DICOM reports on an AXIOM Sensis XP Acquisition System.
A DICOM image viewer is required for viewing DICOM reports. The current version of AXIOM Sensis XP is not equipped with an image viewer (but an Artis Xray system is).
AXA5-200.640.07.01.02
System Administration
Communication Manager
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
(1) DICOM report conversion is a three-step process:
– Creation of a PCL file (print to file function on a PCL printer).
– Conversion of the PCL file to an image file.
– Creation of header information (patient and study data) and saving header
and image data as a DICOM file.
 Enter Microsoft Office Document Image Writer or HP LaserJet 4014 PCL6 as
the printer driver under Job parameters.
– These printer drivers are available on the information system server where
Export Engine runs.
Note
Do not enter AXIOM Sensis XP DICOM Printer as printer driver for DICOM reports because this can result in poor image quality of Sensis waveform snapshots in the DICOM reports.
Transfer method and
transfer parameters
(2) Here you tell the system to copy the DICOM report file(s) to the dialog computer of the acquisition system the study was performed on.
Scenario 1: send reports
to acquisition system
If you want to send DICOM reports back to the same acquisition system the study
was performed on:
 Leave the Transfer parameters as suggested by the job template:
– DESTDIR=\\***COMPUTER***\DICOM_Reports
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
215 / 456
System Administration
Note
When study data is sent from an AXIOM Sensis XP Acquisition System to the
information system, the name or network identification of the Sensis acquisition
system is added to the study data.
The parameter ***COMPUTER*** is a placeholder for this acquisition system
identification. When a DICOM report has been created the acquisition system
identification will be read from the study data and entered as the send destination automatically.
See Adjusting system parameters 306
Note
The directory DICOM_Reports must exist on the destination computer and that
it must be a shared directory.
Note
Never specify a destination file name (DESTFILE) for your DICOM reports.
Specific DICOM file name conventions must be met to guarantee that Patient
Browser can read the data and list the reports correctly. The DICOM conversion
process automatically creates correct file names.
Scenario 2: send reports
to post-processing workstation
If you want to send all DICOM reports to one central post-processing workstation
where study results are reviewed before archiving and from where study data are
eventually archived:
 Replace the parameter ***COMPUTER*** with the PC name or IP address of
the post-processing system you want to send all DICOM reports to.
Note
Content
Note
216 / 456
The directory DICOM_Reports must exist on the target PC and that it must be a
shared directory.
(3) Do not select a cluster.
Content ***Not Applicable*** must be selected for all transfer jobs that send
or print study reports only.
AXA5-200.640.07.01.02
System Administration
Communication Manager
Distribution
(4) Enable the transfer job here.
 Select distribution Manual.
– This alerts clinical users to the fact that a transfer job is about to be sent to
the Export Queue. They will be requested to confirm this in Transfer
Agent.
Or
 Select Automatic.
– This will transfer reports and send them automatically in the background.
– Note, however, that if you select automatic transfer your clinical users may
not be aware of when DICOM reports are created.
Trigger
(5) This parameter indicates that the DICOM conversion job will be sent to the Export Queue when a clinical user approves a study in Patient Explorer.
– Other trigger events are also possible, make sure you select a trigger that
makes sense in the clinical workflow at your hospital.
 Select a different trigger, if you wish.
– A possible alternative trigger event might be Transfer Reports.
– This would send the conversion and transfer job to the Export Queue when
a clinical user selects Report > Transfer in the Patient Explorer menu.
– You might want to combine this trigger with the distribution method Automatic to reduce the number of clicks clinical users have to perform when
sending a DICOM report.
Max. number of retries
and retry interval
(6) No retries are planned here if the transfer job fails at the first attempt.
– An error will be reported in the Export Log of the Communication Manager in this case.
 Enter a number of retries and the retry interval if network problems occur in
your hospital occasionally .
On success/On failure
AXIOM Sensis XP (VC11)
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
AXA5-200.640.07.01.02
217 / 456
System Administration
Transfer DICOM reports over DICOM network to fix remote node
With this transfer configuration you can send DICOM reports to any DICOM workstation or to a network archive that can handle DICOM waveform objects and DICOM non-image objects (for example, syngo Dynamics).
Note
In order to be able to view a DICOM report on a DICOM workstation, DICOM
viewer software must be available.
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
(1) Here the transfer job type Create DICOM report is preselected and the system
expects you to specify the nearest PCL printer driver in your network.
 Enter Microsoft Office Document Image Writer or HP LaserJet 4014 PCL6 as
the printer driver under Job parameters.
– These printer drivers are available on the information system server where
Export Engine runs.
Note
Transfer method and
transfer parameters
Do not enter AXIOM Sensis XP DICOM Printer as printer driver for DICOM reports because this can result in poor image quality of Sensis waveform snapshots in the DICOM reports.
(2) Here you tell the system to run a batch file which will copy the DICOM report
jobs created by the above specified process to a destination whose parameters
you will enter under Transfer parameters.
 Replace the placeholders <remote_hostname>, <remote AET>, <remote port>
with the DICOM address of the send destination.
218 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
 Replace <own AET> with the host name of the information system server.
– This is usually “Sensis” plus the serial number of your system
(for example, SENSIS0020).
– Also inform the system administrator of the receiving DICOM system about
the DICOM address of the information system server (<own AET>). The
receiving system must be configured to receive data from this DICOM
address.
Note
Do not change the string FILENAME=C:\mis\ccnsw\dicom_send.bat as otherwise
the data transfer will not be performed.
Content
Note
(3) Do not select a cluster.
Content ***Not Applicable*** must be selected for all transfer jobs that send
or print study reports only.
Distribution
(4) Here you enable the transfer job.
 Select distribution Manual or Automatic.
See Distribution 207
Trigger
(5) This parameter indicates that the DICOM conversion job will be sent to the Export Queue when a clinical user approves a study in the Patient Explorer.
 Select a different trigger, if you wish.
See Trigger 207
Max. number of retries
and retry interval
(6) No retries are planned here if the transfer job fails at the first attempt.
 Enter a number of retries and the retry interval if network problems occur in
your hospital occasionally.
On success/On failure
AXIOM Sensis XP (VC11)
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
AXA5-200.640.07.01.02
219 / 456
System Administration
Print reports when closing study
On the System Parameters tab card of the Configuration Manager you can define if you want the system to create study reports automatically when a study is
closed (Patient > Close Study).
Note
One report will be created for each report template that has been assigned to a
study type and enabled for automatic report creation.
If automatic report creation has been enabled in Configuration Manager you can
define in the Communication Manager if and on which printer the reports are to
be printed out when the study is closed.
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
(1) These settings indicate that reports are to be sent to the printer as Word files.
Transfer method and
transfer parameters
(2) This defines that the reports are to be printed out on the printer specified here.
 Do not change these settings.
 Simply enter the name of the printer if the printer is connected locally to your
information system server PC or has been installed as a network printer.
– For example: PRINTER=HP Laserjet 4100 PS
Or
 Enter the name or IP address of the PC in your network to which the printer is
connected and the shared printer name.
– For example: PRINTER=\\SensisServer\\HP Laserjet 4100 PS
Or
220 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
 Distribute print jobs to the printers in the various labs.
– For example: PRINTER_Sensis1=\\Sensis1\\HP Laserjet 2200&
PRINTER_Sensis2=\\Sensis2\\HP Laserjet 4100 PS
See PRINTER 211
Content
Note
(3) Do not select a cluster.
Content ***Not Applicable*** must be selected for all transfer jobs that send
or print study reports only.
Distribution
(4) Here you enable the transfer job.
 Select distribution Manual or Automatic.
See Distribution 207
Trigger
(5) This parameter indicates that the reports will be printed as soon as you close
the study.
– This is the correct setting if “automatic report creation when study is closed”
has been set in Configuration Manager (REPORT_AUTOCREATE = 1).
 Alternately select Approve Study if the system parameter setting in the Con-
figuration Manager is to prompt for approval of the study when the study is
closed and reports are only created after that (REPORT_AUTOCREATE = 2)
See REPORT_AUTOCREATE 307
Max. number of retries
and retry interval
(6) No retries are planned here if the transfer job fails at the first attempt.
 Enter a number of retries and the retry interval if you are sending the print job
over the network and network problems occur in your hospital occasionally.
On success/On failure
AXIOM Sensis XP (VC11)
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
AXA5-200.640.07.01.02
221 / 456
System Administration
Configuration of data export jobs to HIS/CIS system
The Communication Manager offers two formats for data export from the AXIOM Sensis XP Information System to hospital (HIS), or radiology (RIS), or cardiology information systems (CIS).
Supported formats for
data export
 Messages that conform to the Health Level 7 standard (HL7)
– Two outgoing messages are supported: ORUR01 (for study findings and clinical data) and DFTP03 (for cost information)
 ASCII flat file (HIS)
– A factory predefined HIS output job is available in your system.
– Note that the receiving system must have been configured so as to understand the ASCII flat file the AXIOM Sensis XP Information System sends.
– Refer to the Communication appendix 245 for details on the syntax of
outgoing messages.
Importance of output
cluster definition in DB
Manager
During data export configuration in the Communication Manager you define
what data is to be exported by selecting output clusters in the Content box.
These output clusters are freely definable collections of database tables and fields.
Predefined output clusters for HL7 messages (clusters HL7 ORU message and HL7
DFTP03 message) and ASCII flat file output (HIS transfer) come with the system.
We recommend that you use these clusters and adapt them to the requirements
in your cath lab and hospital rather than to define output clusters for these kinds
of data export jobs from scratch.
See Editing clusters 106
Please note that slightly different syntax rules apply for the HIS transfer and HL7
DFTP cluster than for the definition of any other clusters in the information system
database.
See Output cluster HIS transfer 116 and Output cluster HL7 DFTP03 message
117.
HL7: support of coding
schemes
The AXIOM Sensis XP Information System supports the mapping of database
contents (values) to codes that comply with coding schemes for health care provider, (for example, ICD 9/ICD10/CPT/ACP/DRG).
Even though implementation of these coding schemes is slightly different for ORU
and DFT messages, the basic principle is the same:
DFT messages (cost-relevant data) typically send information on premedication,
equipment, medication, procedure, and diagnosis. All of this information is stored
in customizable database tables, and has been entered in Documentation Tool
from predefined pick lists (dictionaries).
222 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
ORU messages (study results and findings) also send information that has been
entered in the Documentation Tool from predefined pick lists (dictionaries). Additionally, this message type also transfers measured (and not user-entered) data
from system groups (such as pressure values, for example).
Dictionary plain text entries can be assigned codes that comply with a coding
scheme. The examples for HL7 DFT and HL7 ORU messages will explain how.
See Create HL7 ORU message 229 and Create HL7 DFT message 226
HL7: mapping fields
For ORU messages another type of information mapping may also be relevant: the
mapping of Group and Field designations to the database structure of the receiving system.
In Configuration Manager you can assign an Identifier and Text to any field you
intend to send in an HL7 ORU message. This helps the receiving system to sort in
the transferred data correctly.
See HL7 Mapping 314
Transfer HIS output file
The transfer configuration Transfer HIS output file creates an ASCII flat file for
data transfer to a hospital, radiology, or cardiology system.
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
AXIOM Sensis XP (VC11)
(1) Defines the transfer job type and job parameters.
For a detailed explanation of these parameters see Create HIS output file 198
AXA5-200.640.07.01.02
223 / 456
System Administration
Transfer method and
transfer parameters
(2) Indicates that the output file created by the job type process will be copied to
this directory on the information system server PC.
Scenario 1: HIS/RIS or CIS
fetches data
In this default scenario the HIS/RIS or CIS is expected to pick up the *.his file generated by this transfer job from the directory C:\MIS\CCNSW\DEMOGR via FTP.
(C:\MIS\CCNSW\DEMOGR has been enabled as the root directory in the information system FTP server.)
Scenario 2: Sensis information system sends
data
Alternately, communication between the AXIOM Sensis XP Information System
and the HIS/RIS or CIS can be set up in such a way that the HIS/RIS or CIS expects
the information system to actively send the ASCII flat file to the HIS/RIS or CIS server.
 In that case select Transfer method FTP and define the send destination under
Transfer parameters.
For details of transfer parameters see Transfer method and Transfer parameters
208
Content
Note
(3) Defines HIS transfer as the output cluster whose data are to be exported.
Always select HIS transfer as the output cluster for this job type. Do not select
any other output cluster.
Adapt HIS transfer to your requirements, if necessary.
See Output cluster HIS transfer 116
Distribution
(4) Here you enable the transfer job.
 Select distribution Manual or Automatic.
See Distribution 207
Trigger
(5) Defines the trigger event that sends this transfer job to the Export Queue.
 Select a different trigger, if you wish.
See Trigger 207
Max. number of retries
and retry interval
(6) No retries are planned here if the transfer job fails at the first attempt.
 Enter a number of retries and the retry interval if network problems occur in
your hospital occasionally .
On success/On failure
224 / 456
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
AXA5-200.640.07.01.02
System Administration
Communication Manager
Transfer HIS output file, reports, images, and waveforms
This transfer job combines the following steps:
 Creation of an ASCII flat file with study data from the information system data-
base.
 Conversion of all study reports that have been created for a study into the re-
quested format.
 Transfer of all X-ray images stored for a study in the information system data-
base (in bitmap format).
 Transfer of all waveform images available for a study in the information system
database (as enhanced metafiles (*.emf).
All of these files are stored in a predefined directory on the information server PC.
This transfer job does not export:
 Ablation graphs
 CARTO® mapping images
 CTI/HPI reports as images
 DICOM images
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
AXIOM Sensis XP (VC11)
(1) Defines creation of an ASCII flat file and creation of report and image files.
For a detailed explanation of these parameters see Transfer HIS output file, reports, images, and waveforms 205
AXA5-200.640.07.01.02
225 / 456
System Administration
Transfer method and
transfer parameters
(2) Sends the data to a directory on the local server PC from where it will be picked
up by the hospital, radiology, or cardiology system.
– If the HIS/RIS or CIS are not configured to pick up the data on the information system server, you can select FTP to send the data.
See also: Scenario 2: Sensis information system sends data 224
Content
Distribution
Trigger
Max. number of retries
and retry interval
On success/On failure
(3) Selection of the output cluster HIS transfer should not be changed here.
(4) Select Manual or Automatic to enable this transfer job.
(5) Export Study is an adequate trigger for this type of send job in most cases.
(6) No retries are planned here if the transfer job fails at the first attempt.
See Transfer HIS output file 223 for a description of these parameters.
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
Create HL7 DFT message
This transfer job exports cost information as an HL7 message of message type
DFTP03.
For a description of this message type refer to Message definitions for outgoing
messages to a HIS/RIS or CIS 259
HL7 DFTP03 message
output cluster
To help you with the definition of DFTP03 messages, a predefined output cluster
for this export job is now available in the database setup.
 Check if this output cluster contains all the information you want to send be-
fore you activate the Create HL7 DFT message job.
– Please note that special requirements exist for the definition of this output
cluster.
See Output cluster HL7 DFTP03 message 117
Assigning a coding
scheme
National regulations might require that you send codes rather than plain text information as values in an HL7 DFT message. To do this, you create coding dictionaries and map the codes to your own plain text information system dictionaries.
You will find a description of how to do this below.
226 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
Implementing a coding
scheme for dictionary
plain text entries
(1) Defines that an HL7 message of the message type DFTP03 is to be created.
 Define that code numbers are sent instead of text, if necessary.
 Start DB Manager to edit dictionary definition files and the rep.grp file.
See Editing dictionaries 78, and Editing or adding customizable groups
97
Example: implementing a coding scheme for the diagnosis dictionary
1. Create a coding dictionary, which lists the codes:
# ICD9, ICD-9, SI, 4, 16, 16
885, CODExxx
540, CODEyyy
364, CODEzzz
...
Here CODExxx, for example, is the ICD-9 code for Unstable Angina.
2. Modify the diagnosis dictionary so that it retrieves auto-values from the codes
dictionary:
DIAGNO, Diagnosis , SI, 4, 32, 16, Y, C:1, L:10
#1, General Indications
885 ,Unstable Angina, 885
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
227 / 456
System Administration
540 ,Coronary Artery Disease, 540
364 ,Aortic Stenosis, 364
...
Here the diagnosis Unstable Angina is associated with CODExxx, from the codes
dictionary.
3. Modify the diagnosis group definition and add a field for the code value:
#DI ,Diagnosis ,3
N, DIAGNOS , SI, 4 , Diagnosis <DIC>
, DIAGNO
N, CODSCHEM, SI, 4 , Diagnosis coding schema
, ICD9
N, AETIOLOG, SI, 2 , Aetiology <DIC>
, AETIOL
N, SEVERITY, SI, 2 , Severity <DIC>
, SEVER
 Return to the Communication Manager now to specify the dictionary name
from which the codes are to be read out.
4. Modify the Job parameters:
MESSAGE=DFTP03&CODE1=ICD9
The associated code is now sent in the HL7 message as well as the plain text diagnosis.
Note
Transfer method and
transfer parameters
Note
Content
Note
You can assign codes to other information exported in the HL7 DFTP03 message
as well (MESSAGE=DFTP03&CODE1=ICD9&CODE2=...)
(2) Enter the name of the HIS/RIS server and the port number to where you want
to send the message.
The system administrator of the hospital, radiology, or cardiology information
system you want to communicate with can provide you with this information.
(3) The default output cluster for typical DFTP03 messages.
Do not select another output cluster here. Check and possibly adapt the definition of HL7 DFT cluster, if necessary.
See Editing clusters 106
Distribution
(4) Here you enable the transfer job.
 Select distribution Manual or Automatic.
See Distribution 207
228 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Trigger
(5) Defines the trigger event that sends this transfer job to the Export Queue.
 Select a different trigger, if you wish.
See Trigger 207
Max. number of retries
and retry interval
(6) No retries are planned here if the transfer job fails at the first attempt.
 Enter a number of retries and the retry interval if network problems occur in
your hospital occasionally .
On success/On failure
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
Create HL7 ORU message
This transfer job exports study findings as an HL7 message of the message type
ORUR01.
For a description of this message type refer to Message definitions for outgoing
messages to a HIS/RIS or CIS 259
HL7 ORU message output cluster
To help you with the definition of HL7 ORU messages, a predefined output cluster
for this export job is available in the database setup.
 Check whether this output cluster contains all the information you want to
send before you activate a Create HL7 ORU message job.
See Syntax for the cluster definition file (cathcor.clu) 111
Mapping fields
The receiving system of your ORU message might be unable to read the group and
field names from your information system database. If this is the case, you can
map these to an Identifier and Text that the receiving system can identify.
You will do this as a preparatory step in the information system administration
tool Configuration Manager before you enable the Create HL7 ORU message
transfer job in Communication Manager.
See HL7 Mapping 314
Assigning a coding
scheme
National regulations might require that you send codes rather than plain text information as values in a HL7 ORU message.
This can be achieved in two ways:
1. The dictionary which is used can be a representation of the code standard.
– This method is simpler but only allows either the plain text or code to be
exported.
2. You can create coding dictionaries and map the codes to your own plain text
information system dictionaries.
– This method, while more complicated, allows both the plain text and the
code to be exported.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
229 / 456
System Administration
You will find a description of both methods below.
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
Note
(1) Defines that an HL7 message of the message type ORUR01 is to be created.
No CODE parameter (as in DFT messages) is required here.
Nevertheless the information sent in an ORU message can be mapped to codes.
Implementing coding
schemes
 For ORU messages only data stored in the Procedures (PR) or Diagnosis (DI)
groups can be mapped to codes.
– For data from other groups, implementation of a coding scheme is not possible.
 Sending of codes rather than plain text requires that either the job parameter
FLAT_DATA or VA_VISTA has been set.
– i.e. MESSAGE=ORUR01&FLAT_DATA, or
MESSAGE=ORUR01&VA_VISTA
 Start the DB Manager in order to edit dictionary definition files, the rep.grp
file, and the cathcor.clu file.
See Editing dictionaries 78, Editing or adding customizable groups 97,
Editing clusters 106
230 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Example: implementing a coding scheme for the diagnosis dictionary
Option 1
Assign codes and export the code rather than the dictionary plain text.
1. Create a dictionary which represents the codes and values as specified in the
standard.
# ICD9, ICD-9, SI, 4, 16, 16
420, Unstable Angina
421, Aortic Stenosis
...
Here 420, 421, and so on represent the codes in the standard ICD-9, and Unstable
Angina, Aortic Stenosis are description texts used in the information system.
2. Modify the group definition so that the dictionary created in step 1 will be used
instead of the predefined dictionary.
# DI ,Diagnosis ,3
N, DIAGNOS , SI, 4 , Diagnosis <DIC> , ICD9
N, AETIOLOG, SI, 2 , Aetiology <DIC> , AETIOL
N, SEVERITY, SI, 2 , Severity <DIC> , SEVER
3. In the Configuration Manager specify that the code rather than the meaning
from the dictionary will be exported.
See HL7 Mapping 314
Option 2
Assign codes and export both the code and the dictionary plain text.
1. Create a coding dictionary, which lists the codes:
# ICD9, ICD-9, SI, 4, 16, 16
885, xxx (xxx is the ICD-9 code for Unstable Angina)
540, yyy (yyy is the ICD-9 code for Coronary Artery Disease)
364, zzz (zzz is the ICD-9 code for Aortic Stenosis)
...
2. Modify the diagnosis dictionary so that it retrieves auto-values from the code
dictionary:
DIAGNO, Diagnosis , SI, 4, 32, 16, Y, C:1, L:10
#1, General Indications
885 ,Unstable Angina, 885
540 ,Coronary Artery Disease, 540
364 ,Aortic Stenosis, 364
...
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
231 / 456
System Administration
Here the diagnosis Unstable Angina is associated with xxx from the codes dictionary.
3. Modify the diagnosis group definition and add a field for the code value:
#DI ,Diagnosis ,3
N, DIAGNOS , SI, 4 , Diagnosis <DIC>
, DIAGNO
N, CODSCHEM, SI, 4 , Diagnosis coding schema
, ICD9
N, AETIOLOG, SI, 2 , Aetiology <DIC>
, AETIOL
N, SEVERITY, SI, 2 , Severity <DIC>
, SEVER
4. Modify the cluster definition for the output cluster HL7 ORU message
# O, HL7ORU, HL7 ORU message
; Diagnosis
DI, CODSCHEM, AETIOLOG, SEVERITY
This will not send the text from the dictionary but the associated code from the
coding scheme in the HL7 message.
Or
# O, HL7ORU, HL7 ORU message
; Diagnosis
DI
This will send all the information in the diagnosis table, which includes the diagnosis plain text and the mapped code.
Transfer method and
transfer parameters
(2) Sends the file created by this job type to the network address specified here.
 Enter the name of the HIS/RIS or CIS server and the port number to where you
want to send the message.
Note
Content
Note
The system administrator of the hospital, radiology, or cardiology information
system you want to communicate with can provide you with this information.
(3) The default output cluster for typical ORUR01 messages.
Do not select another output cluster here. Check and possibly adapt the definition of HL7 ORU cluster, if necessary.
See Editing clusters 106
Distribution
(4) Here you enable the transfer job.
 Select distribution Manual or Automatic.
See Distribution 207
232 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Trigger
(5) Defines the trigger event that sends this transfer job to the Export Queue.
 Select a different trigger, if you wish.
See Trigger 207
Max. number of retries
and retry interval
(6) No retries are planned here if the transfer job fails at the first attempt.
 Enter a number of retries and the retry interval if network problems occur in
your hospital occasionally .
On success/On failure
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
Data import from a HIS/RIS or CIS system
The AXIOM Sensis XP Information System can import preregistration data and
information about patient and study information changes from a HIS/RIS or CIS
system.
HL7 data import
Import of HL7 data into the information system database is handled by the information system application HL7 Listener.
For details about the HL7 data import see HL7 data import: HL7 Listener application 245 and HL7 message specifications 250.
ASCII flat file data import
Import of preregistration data as ASCII flat files is handled by the information system background application Export Engine. A factory predefined transfer job exists for this task.
Import preregistered patients via ASCII flat file
This transfer job is a factory defined default whose parameters you should not
change. Simply enable the job if you want to use it.
Note
AXIOM Sensis XP (VC11)
If you accidentally lose this transfer job or change any parameter settings, use
this description to return to the original default definition.
AXA5-200.640.07.01.02
233 / 456
System Administration
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
(1) Selects the batch file that handles the data import and defines parameters.
Transfer method and
transfer parameters
(2) Defines the transfer method.
– As no data are sent from the information system in this transfer configuration, the method NOSEND is selected here and no transfer parameters are
required.
Content
Distribution
Trigger
Max. number of retries
and retry interval
On success/On failure
234 / 456
(3) As no data is exported, Content is set to ***Not Applicable*** here.
(4) Select Automatic as the distribution method to enable data import via ASCII
flat file.
(5) Sender Internal, indicates that the batch file specified in the job parameters is
executed every time the Export Engine runs. However, if no ASCII flat file has
been sent from the HIS/RIS or CIS, no data will be processed.
(6) No retry attempts and retry interval need to be specified here.
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
AXA5-200.640.07.01.02
System Administration
Communication Manager
Sending study reports as fax or email
This section presents examples for less frequently used transfer configurations.
These examples are therefore not predefined in the system. If you want to use
these transfer jobs in your information system communication you will have to implement them as shown here.
Fax study report to predefined fax number
In your cath lab it might be useful if clinical users can fax study reports directly
from the Patient Explorer or the Report Generator.
Prerequisites for fax report function
The Fax Report function is available if:
 A fax modem has been installed on the AXIOM Sensis XP Information System
server PC.
 Fax report transfer jobs have been configured with the Communication Man-
ager.
Fax report concept
The basic assumption for fax communication from the AXIOM Sensis XP Information System is that only a few phone numbers are potential recipients of study
report faxes for each cath lab.
Therefore you must set up one transfer job for each fax number that you might
want to send a study report to.
You will select manual distribution to open Transfer Agent every time a user
clicks Fax Reports. In Transfer Agent, clinical users can select to which of the preconfigured fax numbers they want to send the current study report by checking
these jobs and unchecking all other fax jobs.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
235 / 456
System Administration
Example of a fax report
transfer job
(1)
(2)
(4)
(5)
(6)
(7)
(3)
Job name and job description
Job type and job parameters
Transfer method and
transfer parameters
Content
Distribution
Trigger
Note
Max. number of retries
and retry interval
236 / 456
(1) Include the fax number or the name of the recipient in the transfer job name
and job description.
– This is the information presented to clinical users in Transfer Agent when
they are prompted to select one of the available fax numbers for the report
they intend to send.
(2) Sends the original Word report in the Word document format (*.doc file)
(3) Send by fax to this predefined fax number.
– Enter the phone number of the receiving fax machine.
(4) Do not select a cluster.
(5) Be sure to select Manual as the distribution method.
(6) Select Fax Reports as the trigger event.
Be sure to select Fax Reports and not any other trigger. This ensures that reports
are only faxed when a user clicks the Fax Reports icon.
(7) Specifying retry is advisable here as the fax line might be busy at the first attempt to send the fax.
AXA5-200.640.07.01.02
System Administration
Communication Manager
On success/On failure
(8) If you wish, define a second fax job here.
– The report will then be sent to both fax numbers, the number defined in this
fax transfer job and immediately afterward also to the fax number you
defined in the transfer you selected in the On success box.
Or
– Define an alternative fax transfer job under On failure. This will send the
report to this alternative fax number if the system cannot reach the first
number.
Note
Save this transfer job and continue to define more fax jobs, one for each fax
number that might receive study reports as faxes from your cath lab.
Note
In order to organize creation of several fax jobs in a row more efficiently:
 Select the first fax job again in the Job name box.
 Overwrite the job name, job description, and transfer parameters with the
values for the second fax job.
 Save again (this saves the transfer job under the new name and with the
changed parameters).
Faxing a study report
When a clinical user clicks the Fax Report icon (or selects this menu item) in Patient Explorer or Report Generator, the Transfer Agent dialog box opens.
The user is prompted to select or check the fax number to which he or she wants
to send the current report and confirm with OK.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
237 / 456
System Administration
Email study report to predefined mail address
In your cath lab it may be useful if clinical users can email study reports directly
from the Patient Explorer or the Report Generator.
Prerequisites for mail
report function
The Mail Report function is available if:
 Email communication has been configured for the AXIOM Sensis XP Informa-
tion System server PC.
 Email report transfer jobs have been configured with the Communication
Manager.
Mail report concept
The same principle as for fax communication applies to email communication
from the AXIOM Sensis XP Information System:
 The basic assumption is that a limited number of email addresses are potential
recipients of study reports by email.
 One email transfer job is set up for each receiving email address.
 Distribution: Manual allows clinical users to select the email address for the
current report before sending out the report.
See Fax study report to predefined fax number 235
Example of a mail report transfer job
(1)
(2)
(4)
(5)
(6)
(7)
(3)
238 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Job name and job description
(1) Include the email address or the name of the recipient in the transfer job name
and job description.
– This is the information presented to clinical users in Transfer Agent when
they are prompted to select one of the available email addresses for the
report they intend to send.
Job type and job parameters
(2) Send the original Word report in the Word document format (*.doc file) or select to send an *.rtf or *.pdf file.
Transfer method and
transfer parameters
(3) Send by email to this address.
– Specify the SMTP server.
– Specify email addresses (TO).
– Also specify a recipient for a carbon copy (CC),and a blind carbon copy
(BCC).
– Specify a FROM address (this is required because the information system
does not have an email account of its own).
– Specify the SUBJECT and a BODY text, if you wish.
– The actual report will be sent as an attachment.
For a detailed description of these transfer parameters see SMTP 212
Content
Distribution
Trigger
Note
Max. number of retries
and retry interval
On success/On failure
(4) Do not select a cluster.
(5) Be sure to select Manual as the distribution method.
(6) Select Mail Reports as the trigger event.
Be sure to select Mail Reports and not any other trigger. This ensures that reports are only emailed when a user clicks the Mail Reports icon.
(7) No retries is usually required here.
(8) If you wish, define a second or alternative email job here.
Note
Save this transfer job and proceed to define more email jobs, one for each email
address that might receive study reports as emails from your cath lab.
Note
In order to organize creation of several email jobs in a row more efficiently:
 Select the first email job again in the Job name box.
 Overwrite the job name, job description, and transfer parameters with the
values for the second email job.
 Save again (this saves the transfer job under the new name and with the
changed parameters).
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
239 / 456
System Administration
Mailing a study report
When a clinical user clicks the Mail Report icon (or selects this menu item) in Patient Explorer or Report Generator, the Transfer Agent dialog box opens:
The user is prompted to select (check) the mail address to which he or she wants
to send the current report and confirm with OK.
Data export to a departmental material management system
The AXIOM Sensis XP Information System can communicate with the QSight departmental material management system. If the material management license
has been installed and communication with a material management system has
been set up, the AXIOM Sensis XP Information System will receive information
about material checked out for a patient from the material management system.
In the AXIOM Sensis XP Information System this information is available in the
Documentation Tool table Material Usage where users can identify a material as
used, unused, or waste, add comments on material usage, and document additional material usage.
The AXIOM Sensis XP Information System will use the predefined transfer job
Transfer material usage to material management system to send this updated
material management information back to the departmental management system upon a configurable trigger event.
240 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Transfer material usage to material management system
(1)
(3)
(4)
(5)
(6)
(2)
Job type and job parameters
Transfer method and
transfer parameters
Note
(1) Defines that an HL7 message of the message type DFTP03 is to be created.
(2) Enter the name of the server of the departmental material management system and the port number to which you want to send these messages.
– The system administrator of the material management system can provide
you with this information.
If the predefined transfer job does not already define the transfer parameter
HOLD_CONNECTION, be sure to add it.
This parameter ensures that the TCP connection is held long enough for the material management system to receive the complete message from the AXIOM
Sensis XP Information System.
Content
Distribution
(3) The default output cluster for typical DFTP03 messages to the material management system.
– The cluster HL7 MMS message should contain only one group, the material
usage group _VMMUSG.
– See Output cluster HL7 MMS message 118
(4) Here you enable the transfer job.
 Select distribution Manual or Automatic.
See Distribution 207
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
241 / 456
System Administration
Trigger
(5) Defines the trigger event that sends this transfer job to the Export Queue.
 Select a different trigger, if you wish.
See Trigger 207
Max. number of retries
and retry interval
(6) (If transfer of data fails the first time, the system will retry sending the message three times and wait 15 minutes between each attempt.
 Change these settings, if you wish.
On success/On failure
(7) By default no subsequent or alternative transfer job is selected for this job
(***Not Applicable***).
Viewing the export queue of pending jobs
 Display the Queue tab card on top.
– On the Queue tab card you will find a list of all transfer jobs in the Export
Queue that are waiting to be processed the next time the Export Engine
runs (next minute).
Note
242 / 456
These are export jobs whose trigger event has occurred and which have been
moved to the Export Queue either automatically or manually (after confirmation of the job by a clinical user in the Transfer Agent).
AXA5-200.640.07.01.02
System Administration
Communication Manager
Viewing transfer jobs in the export queue
 Click Refresh to make sure the information that is displayed here is current.
This is the information you will find in the Export Queue table:
 QUEUEID
– Transfer job number in the queue.
 CFGNAME
– The name of the communication configuration that created this job.
 REFNO
– The study number from the information system database.
 PATNO
– The patient number from the information system database.
 PARAM
– Data required by the Export Engine. For example, a list of report numbers,
which tells the Export Engine which reports it will process.
 QUEUE_AT
– Date and time when the job was first placed in the queue.
 SEND_AT
– Date and time of the first attempt of the Export Engine to process and send
this job.
 RETRY_AT
– Date and time of the last attempt of the Export Engine to process and send
this job.
Deleting a transfer job from the export queue
You will delete transfer jobs from the Export Queue, for example, if a job cannot
be processed and sent after several unsuccessful retries.
 Select a transfer job by clicking it.
 Hold down the Ctrl. or Shift key and click additional rows if you want to delete
more than one transfer job at once.
 Click Delete and confirm.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
243 / 456
System Administration
Viewing the export log
 Display the Log tab card on top.
– In the Export Log you will find information on all transfer jobs the Export
Engine has processed or tried to process.
– If a transfer job failed (all specified retries were unsuccessful) an error message indicates the problem.
Viewing transfer jobs in the export log
 Click Refresh to make sure the information that is displayed here is up to date.
This is the information you will find in the Export Log table:
 QUEUEID
– Transfer job number in the queue.
 DONE_AT
– Date and time when the transfer job was executed (last successful retry)
 CFGNAME
– The name of the communication configuration that created this job.
 REFNO
– The study number from the information system database.
 PATNO
– The patient number from the information system database.
244 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
 SEND_AT
– Date and time of the first attempt of the Export Engine to process and send
this job.
 ERR
– If the transfer job could not be processed, an error number is displayed
here.
 ERRDEC
– Error description text.
Deleting a transfer job from the export log
For a better overview you can delete old transfer jobs that were sent successfully.
 Select a transfer job by clicking it.
 Hold down the Ctrl. or Shift key and click additional rows if you want to delete
more than one transfer job at once.
 Click Delete and confirm.
Communication appendix
This section provides background information on communication settings and parameters.
HL7 data import: HL7 Listener application
The AXIOM Sensis XP Information System application HL7 Listener is normally
started automatically when your system is powered up.
If the AXIOM Sensis XP Information System is installed on a separate server PC
(high-end SIS server or Sensis XP Master server), this icon in the Windows task bar
(lower right-hand corner of the screen) indicates that the HL7 Listener is running.
On an AXIOM Sensis XP Master PC, i.e., an AXIOM Sensis XP Acquisition System with AXIOM Sensis XP Information System server software, the Windows
task bar is not visible.
If for some reason the HL7 Listener does not start up automatically, or if you have
closed it, call up this application again from the Windows Start menu (Programs
> Startup > HL7 Listener).
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
245 / 456
System Administration
Note
While the DB Manager window is open the system ignores any incoming HL7
message (a negative acknowledgment will be sent to the HL7 server).
Modifying the HL7 Listener error logging behavior
By default the HL7 Listener logs errors on incoming messages only every 250th
time an error is detected. Error logging applies both to messages that are rejected
by the AXIOM Sensis XP Information System and to messages that are accepted
but have errors (for example, syntax errors that affect one or several fields). This
error logging behavior can be modified.
 Open Windows Explorer and the folder
C:\Documents and Settings \ All Users \ Start Menu \ Programs \ Startup
 Right-click the file HL7Listener.exe and call up the Properties dialog box.
 Add one or both of the following command line arguments:
-v for verbose mode: this will log an error every time it occurs and not just every
250th time (HL7Listener.exe -v).
-s for strict mode: this will enforce stricter syntax checking and reject messages
with syntax errors that affect any fields used in the AXIOM Sensis XP Information System (the patient’s data will not be entered in the information system
database) (HL7Listener.exe -s).
Note
You can combine both arguments: HL7Listener.exe -v -s. This means that all
messages with errors will be rejected and every error will be logged.
Checking on received messages and connection settings
The HL7 Listener is usually active in the background. The application continuously
monitors the predefined network connection for incoming HL7 messages. User interaction is not usually necessary here.
You can, however, open the HL7 Listener application to check received messages
and connection settings or if you need to change the communication port and settings when your network configuration changes.
 Select AXIOM Sensis XP Information System > Server > HL7 Listener from
the Windows Start menu.
246 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
TCP/IP connections
The HL7 Listener interface has two main sections. The section on the left shows
any TCP/IP connections that are currently active. This includes computer name and
IP address.
Received messages
The section on the right displays information on received messages.
When an HL7 message is received the message type is listed together with infomation whether it contains all the required message fields. If required fields are
missing these fields are listed here. If the message is valid, further information
about the patient and study is displayed.
Status bar
The status bar displays the currently active communication port and whether HL7
Listener is Listening or Offline. If HL7 Listener is Offline, you can activate it
again with the Start button.
 Close the HL7 Listener with the Close Window icon in the upper right-hand
corner of the dialog box.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
247 / 456
System Administration
Changing the communication port
If your network configuration has changed you may need to change the communication port for the HL7 Listener.
 Click this button in the HL7 Listener to open the Settings dialog box.
 Change the port number.
 Confirm and subsequently close the HL7 Listener.
Activating VistA support
AXIOM Sensis XP can exchange data with VistA information systems. Data exchange is bidirectional. However, to be able to receive messages from a VistA system you must select this option explicitly.
 Click this button in the HL7 Listener to open the Settings dialog box.
 Select the Support VistA box here.
– This modifies the way messages are processed and acknowledged by the
AXIOM Sensis XP Information System.
 Confirm and subsequently close the HL7 Listener.
ADTA08 message handling
AXIOM Sensis XP Information System can process ADTA08 messages with update information on registered patients. In HL7 Listener, you can define how the
information system will treat ADTA08 messages with update information for patients who are not yet registered in the AXIOM Sensis XP Information System.
 Click this button in the HL7 Listener to open the Settings dialog box.
 Check the ADTA08: Pre-register new patient box.
– This creates a new preregistered patient when the system receives update
information on a patient that does not yet exist in the system.
248 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
 Clear this check box if you want the system to ignore ADTA08 messages with
update information on patients that do not exist in the system.
Response to unsupported ADT messages
AXIOM Sensis XP Information System supports the following ADT messages:
ADTA01, ADTA03, ADTA04, ADTA05, ADTA08, ADTA11, ADTA23, ADTA39,
ADTA40, ADTA44, ADTA46, ADTA47, ADTA49. Any other ADT messages cannot be
processed by the AXIOM Sensis XP Information System. In HL7 Listener you can
define how Sensis will respond when it receives an ADT message that it cannot
process.
 Click this button in the HL7 Listener to open the Settings dialog box.
 Select one of the following options in the Response to unsupported ADT
Events list.
– Reject (RA) (recommended)
– Error (AE)
– Accept (AA) (not recommended)
Logging HL7 messages
The AXIOM Sensis XP Information System allows you to log all incoming and acknowledgment messages and errors in a file. You will find this log file in the folder
C:\mis\log.
 Click this button in the HL7 Listener to open the Settings dialog box.
 Check the Log messages box here.
 Confirm and subsequently close the HL7 Listener.
Sending a test message
If you have made configuration changes that affect the HL7 Listener application
you can send a test message to check whether messages are received and processed correctly.
 Click the Test Message button in the HL7 Listener window.
 Select the message file in the File Open dialog box and confirm.
– The test message file is sent to the HL7 Listener over the configured TCP/IP
port and should now be visible in the Received Messages section of the
HL7 Listener window.
– If the test file contains more than one HL7 message, messages are separated by an empty line.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
249 / 456
System Administration
HL7 message specifications
This section provides technical details about the information the AXIOM Sensis
XP Information System will receive and process (inbound messages) and send
(outbound messages). Use this information to compare it with the settings of
these message types in your hospital, radiology, or cardiology information system
or material management system if problems occur during data transfer.
Message definitions for incoming messages from HIS/RIS or CIS
The AXIOM Sensis XP Information System HL7 Listener application automatically listens for incoming HL7 messages on preregistrations and patient or study
information changes over the predefined communication port.
ADTA01
Admit/Visit notification: The patient administration A01 message is sent as a result of the patient undergoing the admission process, which assigns the patient to
a bed.
ADTA04
Register a patient: The patient administration A04 message signals that the patient has arrived or checked in as a one-time or recurring outpatient and is not assigned a bed.
Segments used (ADTA01
and ADTA04)
250 / 456
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
PD1
Additional Demographics Contains additional patient demographic information that is likely to change
PV1
Patient Visit
Used to communicate information on a visit
specific basis
AL1
Allergy Information
Contains patient allergy information about a
single allergy
OBX
Observation/Result
One OBX segment maps to data that is
stored in one field of a table in the database.
The mapping is done using the ObservationIdentifier.Identifier and ObservationIdentifier.Text fields. See HL7 Import mapping
316. Note that the value of an OBX
segment must not be 0 (zero) or else the
segment will be ignored.
AXA5-200.640.07.01.02
System Administration
Communication Manager
Message example
(ADTA01)
MSH|^~\&|||||19951010214222||ADT^A01^n|10215605xgfd|D^R|D^12^10|234
513246549893||||13|ASCII~ASCII|4|ISO 2022-1994
PID|||835632^2^ISO^^VN||GUEST^MANSA
^^I^Ms^Ba^S||19691010211050|F|||19th St^^Beijing ^North China^90210^11~10th St^^Vlaardingen^Borneo^90210^4~8th St^^Picton^Sumatra^35218^14|||||||54^3^ISO^^LR
OBX|||dc^tim|1|12:34||||||X
OBX|||dc^comtxt|1|This is a comment during cath that should be more than 72
characters long. I hope it is by now! ||||||
OBX|||pm^premed|2|6||||||
OBX|||pm^amount|3|10 grams||||||
OBX|||pm^premed|3|5||||||
OBX|||pm^amount|2|2 tablets||||||
OBX|||patient^patcom|9|This is a comment about the patient which is not a good
example||||||
OBX|||cd^clindiag|4|Sinus rhythm||||||
OBX|||study^stucom|5|This is a study comment. The patient has a heart problem!||||||
OBX|||os^tim|6|15:34||||||
OBX|||os^item|6|interflow||||||
OBX|||pd^height|7|66|^INCH|||||
OBX|||pd^weight|7|102|^POUND|||||
OBX|||pm^premed|8|6||||||
OBX|||pm^amount|8|about a bucket||||||
OBX|||patient^occupat||Test this change||||||
OBX|||patient^conflict|10|||||||
OBX|||dcpat^tim|11|14:44||||||
OBX|||dcpat^comtxt|11|this is a second row for the patient scope||||||
Note
AXIOM Sensis XP (VC11)
In the OBX segments the ObservationIdentifier.Identifier and ObservationIdentifier.Text fields have values that correspond to the names of the fields they are
mapped to in the information system database. This is to make the example
more readable, it is not a requirement of the HL7 Listener.
AXA5-200.640.07.01.02
251 / 456
System Administration
ADTA05
Pre-admit a patient: An A05 event is sent when a patient undergoes the pre-admission process. During this process, episode-related data is collected in preparation for a patient's visit or stay in a healthcare facility.
If the patient is not already pre-registered in the AXIOM Sensis XP Information
System, a new patient and study are created using information from the segments specified below. The value in the PV1:PatientClass field is used to determine if this patient should be classified as an in-patient or an out-patient. If the
patient is already pre-registered in the AXIOM Sensis XP Information System,
the patient and study are updated. Only pre-registered patients and studies are
updated.
Segments used
(ADTA05)
ADTA03
Segments used
(ADTA03)
ADTA08
252 / 456
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
PD1
Additional Demographics Contains additional patient demographic information that is likely to change.
PV1
Patient Visit
Used to communicate information on a visit
specific basis.
AL1
Allergy Information
Contains patient allergy information about a
single allergy.
OBX
Observation/Result
One OBX segment maps to data that is
stored in one field of a table in the database.
The mapping is done using the ObservationIdentifier.Identifier and ObservationIdentifier.Text fields. See HL7 Import mapping
316. Note that the value of an OBX
segment must not be 0 (zero) or else the
segment will be ignored.
Discharge/End visit notification: The patient administration A03 message signals the end of a patient’s stay in a health care facility. It shows that the patient’s
status has changed to Discharged. Preregistrations are deleted from the information system database.
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
Update patient information: The patient administration A08 message is used if
any patient information has changed. The patient ID must be unique as this is used
to identify the patient in the database. The update is performed in the information
system database if the patient has been previously registered by either an
ADTA01, ADTA04, or ORMO01 message.
AXA5-200.640.07.01.02
System Administration
Communication Manager
Segments used
(ADTA08)
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
PD1
Additional Demographics Contains additional patient demographic information that is likely to change
OBX
Observation/Result
One OBX segment maps to data that is
stored in one field of a table in the database.
The mapping is done using the ObservationIdentifier.Identifier and ObservationIdentifier.Text fields. See HL7 Import mapping
316. Note that the value of an OBX
segment must not be 0 (zero) or else the
segment will be ignored.
ADTA11
Cancel admit/visit notification: The patient administration A11 message is sent
when an A01 event is canceled. This can be due to an erroneous entry of the A01
event or a decision not to admit the patient after all. Preregistrations are deleted
from the information system database.
ADTA23
Delete a patient record: The patient administration A23 message is used to delete visit or episode-specific information from the patient record. Preregistrations
are deleted from the information system database.
Segments used (ADTA11
and ADTA23)
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
ADTA39
Merge patients (patient ID): This message signals the merging of records for a
person who was incorrectly filed under two different PID-2-patient IDs (external
identifier level). Merges the patient’s records under the correct patient name and
ID in the information system database.
ADTA40
Merge patients (patient identifier list): This message signals the merging of
records for a person who was incorrectly filed under two different PID-3-patient
identifier lists (internal identifier level). Merges the patient’s records under the
correct patient name and ID in the information system database.
ADTA44
Move account information: This message signals the movement of records identified by the MRG-3-prior patient account number (accession number). The account is moved to the correct patient and study in the information system
database.
ADTA46
Change patient ID: This message signals a change to an incorrectly assigned PID2-patient ID value (external identifier level). The patient ID is corrected in the information system database.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
253 / 456
System Administration
ADTA47
Change patient identifier list: This message signals a change to an incorrectly assigned PID-3-patient identifier list value (internal identifier level).
ADTA49
Change patient account number: This message signals a change to an incorrectly assigned account number and corrects the account number in the information
system database.
Segments used
(ADTA39, ADTA40,
ADTA44, ADTA46,
ADTA47, ADTA49)
ORMO01
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
MRG
Merge Information
Provides the receiving application with the
information necessary to initiate the merging of patient data
General order message: The general order message ORMO01 is used to initiate
the transmission of information about an order. This includes placing new orders,
cancelation of existing orders, holding, etc.
If the patient specified in the ORMO01 message does not already exist in the information system database, a new patient is created using the information contained in the various segments. If the patient already exists, only data from the
following fields are inserted/updated.
 ORC.PlacerOrderNumber.EntityIdentifier or OBR.PlacerOrderNumber.Entity
Identifier if the first is empty.
 OBR.UniversalServiceID.Text
 OBR.OrderingProvider(0) (FamilyName and GivenName)
 Any data held in the OBX segments
 N.B. no information from PID, PV1 or AL1 segments is updated.
 The PlacerOrderNumber from the ORM message is used in the ORUR01 export
message to link the order to the results.
Segments used
(ORMO01)
254 / 456
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
PV1
Patient Visit
Used to communicate information on a visitspecific basis
AL1
Allergy Information
Contains patient allergy information about a
single allergy
AXA5-200.640.07.01.02
System Administration
Communication Manager
ORC
Common Order
Holds information specific to the order
Sensis cannot process order cancellation
messages (ORC|CA), the AXIOM Sensis XP Information System ignores these messages.
Preregistered patients for whom a cancellation message was sent remain in the information system database for as long as
specified by the parameter
PREREG_EXPIRED.
See Communication Manager, Adjusting
system parameters 306
Message example
(ORMO01)
OBR
Observation Report
OBR holds information about the order
OBX
Observation/Result
One OBX segment maps to data that is
stored in one field of a table in the database.
The mapping is done using the ObservationIdentifier.Identifier and ObservationIdentifier.Text fields. See HL7 Import mapping
316. Note that the value of an OBX
segment must not be 0 (zero) or else the
segment will be ignored.
MSH|^~\&|EPIC|EpicCare|Sensis|Hemo Cath
Lab|20110119075110||ORM^O01|465373A|P|2.4
PID|1|656927|E630433||DOE^JOHN^H||19471226|M|||9999 TYLER RD^^OREGON^WI^53575|||||||656927-8183532|395506102
PV1|1|O|10T^1001^1001-1|||||2635^GIMELLI^GIORGIO|||||||||||35732243
ORC|NW|35732243
OBR||35732243||CARD102^CARDIAC CATH (CV LAB) PROCEDURE||||||||||||63359^HANSON^HOLLY
OBX|1|TX||1|Cardiology Group->UWMF
OBX|2|TX||2|Reason for Cardiac Cath Procedure?->Structural defect
OBX|3|TX||3|Additional Reason for Cardiac Cath Procedure?->Other - explain in
comments
OBX|4|TX||4|*** recent chf and change in RV/LV function
OBX|5|TX||5|Procedure?->LHC
OBX|6|TX||6|Percutaneous Intervention?->Possible
OBX|7|TX||7|Complexity->Intermediate
OBX|8|TX||8|History of CABG?->Yes
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
255 / 456
System Administration
Note
In the OBX segments the ObservationIdentifier.Identifier and ObservationIdentifier.Text fields have values that correspond to the names of the fields they are
mapped to in the information system database. This is to make the example
more readable, it is not a requirement of the HL7 Listener.
ACK
Message Acknowledgment: The ACK message is sent in reply to an ADT or ORM
message received.
When a message has been received and processed an acknowledgment message,
(ACK), is sent back to the sending system. The ACK message has an acknowledgment code which shows if there was a problem with the received message.
The codes can be:
 AA - message received and processed correctly
 AR - message rejected
 AE - an error occurred.
The table below describes the different reasons for receiving a certain error code.
Segments used (ACK)
MSH
Message Header
Standard HL7 message header
MSA
Message Acknowledgment
Contains information sent while acknowledging another message
Acknowledgment codes
Event
Acknowledgment code
Message processed correctly
AA
DB Manager is running
AE
Database is down or does not exist
AE
Internal HL7Listener error
AE
Message has syntax error or missing required data AR
OBX segments with same ObservationSubID map- AR
ping to different tables
A value from an OBX segment is the wrong type for AR
a DB field
Unknown message type
256 / 456
AXA5-200.640.07.01.02
AR
System Administration
Communication Manager
Inbound messages from a material management system
MFNM12
Segments used
(MFNM12)
MFKM01
Segments used
(MFKM01)
DFTP03
Segments used
(DFTP03)
AXIOM Sensis XP (VC11)
Material master file update from a QSight material management system:
This message is used to synchronize the inventory list of the QSight material management system with the materials selection list in the Material Usage table in
Documentation Tool.
MSH
Message Header
Standard HL7 message header
MFI
Master File Identification
Contains information about origin and version of the master file.
MFE
Master File Entry
Contains information about how Sensis is to
treat the master file entry or record.
ZII
Item information
This segment contains information on an
item or product.
Acknowledgment for material master file update: This message is sent every
time Sensis receives an inventory master file update.
MSH
Message Header
Standard HL7 message header
MSA
Message Acknowledgment
Contains information sent while acknowledging another message
Item usage message from a QSight material management system:
This message is used between QSight and Sensis in both directions. QSight uses
this message to notify Sensis of item usage transactions.
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
PV1
Patient Visit
Used to communication information on a
visit-specific basis.
FT
Item transaction informa- Information about material items checked
tion
out for a patient.
ZII
Item information
This segment contains information on an
item or product.
AXA5-200.640.07.01.02
257 / 456
System Administration
ACKP03
Segments used
(ACKP03)
Acknowledgment for material master file update: This message is sent every
time Sensis receives a DFTP03 message from the material management system.
MSH
Message Header
Standard HL7 message header
MSA
Message Acknowledgment
Contains information sent while acknowledging another message
Inbound HL7 messages: maximum length of elements
For all inbound HL7 messages the length (character count) of elements must be
considered. The general rule is that the character count of elements sent to the
AXIOM Sensis XP Information System must not exceed the length of the corresponding fields in the system groups PATIENT and STUDY. If elements sent to the
information system exceed the permissible length either the entire message is rejected or the element is truncated.
 Message rejected
The entire message will be rejected if the elements listed in the following table exceed the specified maximum length.
ADT
element
Element name
MSH:10
Message control ID
PID:2/1
Patient ID
PATIENT:PATID
64 characters
yes
PID:3/1
Patient Identifier List
PATIENT:PATID
64 characters
-
PID:18/1
Patient Account Number
STUDY:ADMISSID
64 characters
-
PID:19
Social Security Number
PATIENT:SSNUMBER
32 characters
-
PV1:19/1
Visit Number
STUDY:ACCESSNO
16 characters
-
ORC:2/1
OBR:2/1
Placer Order Number
STUDY:ORDNUM
32 characters
-
*
System group and field Max. length
name
mandatory
20 characters*
The AXIOM Sensis XP Information System conforms to the HL7 2.4 specification in that it supports only messages with control IDs of up
to 20 characters. Messages with longer control IDs are rejected.
 Element truncated
If other ADT elements exceed the length of the corresponding information system
field the element will be tuncated, for example, only the first 64 characters sent
are imported and the rest of the element information is lost.
258 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
ADT
element
Element name
System group and field Max. length
name
mandatory
PID:5/1
PID:5/2
PID:5/3
PID:5/4
PID:5/5
Patient Name
PATIENT:LASTNAME
PATIENT:MIDNAME
PATIENT:FIRNAME
PATIENT:SUFFIX
PATIENT:TITLE
64 characters
64 characters
64 characters
64 characters
64 characters
-
PID:11/1
PID:11/3
PID:11/4
Patient Address
PATIENT:ADDRESS
64 characters
-
PID:22/2
Ethnic Group
PATIENT:ETHNIC
16 characters
-
PV1:3/2
Assigned Patient Location
Room
STUDY:INSTRES
64 characters
-
PV1:3/9
Assigned Patient Location
Location Description
STUDY:PATLOC
64 characters
-
PV1:8/2/2
Referring Physician
STUDY:REFPHYS
64 characters
-
OBR:4/2
Universal Service ID Text
STUDY:STUDESC
64 characters
-
OBR:16/2/1
Ordering Provider
STUDY:REQPHYS
64 characters
-
PD1:20
Military Rank Grade
PATIENT:MILRANK
64 characters
-
AL1:3/2
Allergy Code Mnemonic Description Text
STUDY:ALLERGY
64 characters
-
Message definitions for outgoing messages to a HIS/RIS or CIS
ORUR01
Segments used
(ORUR01)
AXIOM Sensis XP (VC11)
Unsolicited transmission of an observation
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
PV1
Patient visit
Used to communicate information on a visitspecific basis
AXA5-200.640.07.01.02
259 / 456
System Administration
OBR
Observation Report
One OBR segment is added for each condition in the study, and the data from the
specified tables is sorted by condition and
added under its OBR segment.
If the database tables that have no condition
information are specified they are placed in
a separate OBR segment.
How the OBR segment is created can be configured with the FLAT_DATA parameter.
See also Create HL7 messages 200
NTE
Notes
One NTE segment is added for each row in a
Free Text table. Each line is placed in a repeat of the NTE Comment field. If the note
has a time associated with it, this is placed in
the first NTE Comment.
The NTE segments can be replaced by OBX
segments by specifying the
FREE_TEXT_AS_OBX parameter.
See also Create HL7 messages 200
OBX
Message example
(ORUR01)
Observation/Result
One OBX segment is added for each exported database field. It contains information
about the field and its value.
MSH|^~\&|CATH^Sensis||^Server||20030916133738||ORU^R01|9|P|2.4
PID||8888|8888||BIX^YMIR^^II^Mr||19961010|M|||6th St, Vlaardingen, NorthShore, 35242
PV1||U|||||||||||||||||24
OBR||||0
NTE|1||11:10~The patient was premedicated with Diphenhydramine 50 and Valium cap 10. The groin was prepared with Betadine and draped in the usual sterile
fashion.|DC^Comments during cath
NTE|2||13:28~After local infiltration with 2% Xylocaine, the Left Femoral Artery
and the Left Femoral Vein were entered using the Percutaneous technique.~This
dictionary definition serves as an example only. You can add any pre-programmed
free text comments you like, and you can build up the hierarchy in the dictionaries
as you like with up to four levels in the hierarchy. Refer to the System administration manual delivered with the system.~~more|DC^Comments during cath
260 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
NTE|3||15:37~We would recommend a trial of medical therapy with calcium channel blockade and nitrates. If a stress is then positive or should the patient have a
recurrence of symptoms, at that point, consider aortocoronary bypass surgery.|DC^Comments during cath
NTE|4||15:38~This patient had an angioplasty in his head and had good angiographic result. He returned this time with recurrence of angina with prolonged
pain and some new ST-T changes.|DC^Comments during cath
NTE|5||this comment holds some hemodynamic results|HT^Hemodynamic Results
NTE|6||Angio result |AR^Angiographic Results
NTE|7||Comment 10|CC^Final comments
NTE|8||The aortic valve was found to be stenotic.|ECF^Eccocard. Findings
NTE|9||The patient arrived with the pre-cath diagnosis stable angina. Selective
coronary angiography of both right and left coronaries with subsequent PTCA was
therefore made in our cath lab today.|BA^Cath. background
NTE|10||Venous hemoglobin oxygen saturations were drawn in the upper IVC/low
right atrium/mid right atrium/SVC/RV/main PA/right pulmonary artery/left pulmonary artery.|OP^Operative Procedure
NTE|11||LEFT VENTRICULOGRAPHY FINDINGS: The left ventricular silhouette in diastole was unremarkable. During systole there was normal motion in all walls in
the RAO projection. There was no mitral regurgitation. The calculated left ventricular ejection fraction on a sinus beat was normal at 89%.|FI^Catheterization findings
NTE|12||RIGHT CORONARY FINDINGS: The right coronary artery was large in caliber. It was a nondominant vessel giving rise to posterior descending artery/and
post-operatively branches. There was no disease seen in the system.|CR^Coronary
findings
NTE|13||This patient is not at high risk, but is a suitable candidate for PTCA and
should therefore be scheduled for a PTCA with normal priority.|RE^Recommendation
OBX|1|ST|^^^TS^Sample Number|1|1||||||F
OBX|2|ST|^^^TS^Acquis. time <HH:MM:SS>|1|10:34:46||||||F
OBX|3|ST|^^^TS^Sample Number|2|2||||||F
OBX|4|ST|^^^TS^Acquis. time <HH:MM:SS>|2|10:35:43||||||F
OBX|5|ST|^^^SPO2^Time <HH:MM>|1|10:36||||||F
OBX|6|ST|^^^SPO2^Pulse rate|1|67||||||F
OBX|7|ST|^^^SPO2^SpO2|1|97||||||F
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
261 / 456
System Administration
OBX|8|ST|^^^SPO2^Time <HH:MM>|2|13:42||||||F
OBX|9|ST|^^^SPO2^Pulse rate|2|75||||||F
OBX|10|ST|^^^SPO2^SpO2|2|98||||||F
OBX|11|ST|^^^NIBP^Time <HH:MM>|1|13:40||||||F
OBX|12|ST|^^^NIBP^Pulse rate|1|70||||||F
OBX|13|ST|^^^NIBP^NIBPs|1|120||||||F
OBX|14|ST|^^^NIBP^NIBPd|1|80||||||F
OBX|15|ST|^^^NIBP^NIBPm|1|100||||||F
OBX|16|ST|^^^NIBP^Time <HH:MM>|2|13:41||||||F
OBX|17|ST|^^^NIBP^Pulse rate|2|80||||||F
OBX|18|ST|^^^NIBP^NIBPs|2|110||||||F
OBX|19|ST|^^^NIBP^NIBPd|2|90||||||F
OBX|20|ST|^^^NIBP^NIBPm|2|100||||||F
OBX|21|ST|^^^RESP^Time <HH:MM>|1|16:38||||||F
OBX|22|ST|^^^RESP^Resp rate|1|12||||||F
OBX|23|ST|^^^RESP^Time <HH:MM>|2|13:42||||||F
OBX|24|ST|^^^RESP^Resp rate|2|15||||||F
OBX|25|ST|^^^RESP^Time <HH:MM>|3|13:45||||||F
OBX|26|ST|^^^RESP^Resp rate|3|10||||||F
OBX|27|ST|^^^PN^Name <DIC>|1|Duffey, Janet||||||F
OBX|28|ST|^^^PN^Staff <DIC>|1|Nurse||||||F
OBX|29|ST|^^^PN^Name <DIC>|2|Johnsson, Karen||||||F
OBX|30|ST|^^^PN^Staff <DIC>|2|Technician||||||F
OBX|31|ST|^^^PN^Name <DIC>|3|Smith, Beatrice||||||F
OBX|32|ST|^^^PN^Staff <DIC>|3|Physician||||||F
OBR||||1^Rest|||20030909103305
OBX|1|ST|^^^PV^Site <DIC>|1|RV||||||F
OBX|2|ST|myPressure1^pressure value 1^^PV^Syst/A|1|87||||||F
OBX|3|ST|^^^PV^#1|1|1||||||F
OBX|4|ST|^^^PV^Diast/V|1|5||||||F
OBX|5|ST|^^^PV^#2|1|1||||||F
262 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
OBX|6|ST|^^^PV^ED/Mean|1|13||||||F
OBX|7|ST|^^^PV^#3|1|1||||||F
OBX|8|ST|^^^PV^Site <DIC>|2|PCW||||||F
OBX|9|ST|myPressure1^pressure value 1^^PV^Syst/A|2|||||||F
OBX|10|ST|^^^PV^#1|2|1||||||F
OBX|11|ST|^^^PV^Diast/V|2|13||||||F
OBX|12|ST|^^^PV^#2|2|1||||||F
OBX|13|ST|^^^PV^ED/Mean|2|57||||||F
OBX|14|ST|^^^PV^#3|2|1||||||F
OBX|15|ST|^^^PV^Site <DIC>|3|LV||||||F
OBX|16|ST|myPressure1^pressure value 1^^PV^Syst/A|3|31||||||F
OBX|17|ST|^^^PV^#1|3|1||||||F
OBX|18|ST|^^^PV^Diast/V|3|7||||||F
OBX|19|ST|^^^PV^#2|3|1||||||F
OBX|20|ST|^^^PV^ED/Mean|3|11||||||F
OBX|21|ST|^^^PV^#3|3|1||||||F
OBX|22|ST|^^^PV^Site <DIC>|4|AO||||||F
OBX|23|ST|myPressure1^pressure value 1^^PV^Syst/A|4|128||||||F
OBX|24|ST|^^^PV^#1|4|1||||||F
OBX|25|ST|^^^PV^Diast/V|4|70||||||F
OBX|26|ST|^^^PV^#2|4|1||||||F
OBX|27|ST|^^^PV^ED/Mean|4|95||||||F
OBX|28|ST|^^^PV^#3|4|1||||||F
OBX|29|ST|^^^VD^Site <DIC>|1|RV||||||F
OBX|30|ST|^^^VD^Max dp/dt (mm hg/s)|1|667||||||F
OBX|31|ST|^^^VD^Max dp/dt/p (/s)|1|20||||||F
OBX|32|ST|^^^VD^Mean Sys press (mm hg)|1|||||||F
OBX|33|ST|^^^VD^Mean Dias press (mm hg)|1|||||||F
OBX|34|ST|^^^VD^Stroke Work|1|||||||F
OBX|35|ST|^^^VD^Stroke Work Index|1|||||||F
OBX|36|ST|^^^VD^Stroke Power|1|||||||F
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
263 / 456
System Administration
OBX|37|ST|^^^VD^Stroke Power Index|1|||||||F
OBX|38|ST|^^^VD^Sample Number|1|1||||||F
OBX|39|ST|^^^VD^Site <DIC>|2|LV||||||F
OBX|40|ST|^^^VD^Max dp/dt (mm hg/s)|2|222||||||F
OBX|41|ST|^^^VD^Max dp/dt/p (/s)|2|8||||||F
OBX|42|ST|^^^VD^Mean Sys press (mm hg)|2|||||||F
OBX|43|ST|^^^VD^Mean Dias press (mm hg)|2|14||||||F
OBX|44|ST|^^^VD^Stroke Work|2|||||||F
OBX|45|ST|^^^VD^Stroke Work Index|2|||||||F
OBX|46|ST|^^^VD^Stroke Power|2|||||||F
OBX|47|ST|^^^VD^Stroke Power Index|2|||||||F
OBX|48|ST|^^^VD^Sample Number|2|1||||||F
OBR||||2^Isometric Exercise|||20030909103530
OBX|1|ST|^^^PV^Site <DIC>|1|RV||||||F
OBX|2|ST|myPressure1^pressure value 1^^PV^Syst/A|1|87||||||F
OBX|3|ST|^^^PV^#1|1|2||||||F
OBX|4|ST|^^^PV^Diast/V|1|5||||||F
OBX|5|ST|^^^PV^#2|1|2||||||F
OBX|6|ST|^^^PV^ED/Mean|1|13||||||F
OBX|7|ST|^^^PV^#3|1|2||||||F
OBX|8|ST|^^^PV^Site <DIC>|2|PCW||||||F
OBX|9|ST|myPressure1^pressure value 1^^PV^Syst/A|2|||||||F
OBX|10|ST|^^^PV^#1|2|2||||||F
OBX|11|ST|^^^PV^Diast/V|2|13||||||F
OBX|12|ST|^^^PV^#2|2|2||||||F
OBX|13|ST|^^^PV^ED/Mean|2|56||||||F
OBX|14|ST|^^^PV^#3|2|2||||||F
OBX|15|ST|^^^PV^Site <DIC>|3|LV||||||F
OBX|16|ST|myPressure1^pressure value 1^^PV^Syst/A|3|31||||||F
OBX|17|ST|^^^PV^#1|3|2||||||F
OBX|18|ST|^^^PV^Diast/V|3|6||||||F
264 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
OBX|19|ST|^^^PV^#2|3|2||||||F
OBX|20|ST|^^^PV^ED/Mean|3|11||||||F
OBX|21|ST|^^^PV^#3|3|2||||||F
OBX|22|ST|^^^PV^Site <DIC>|4|AO||||||F
OBX|23|ST|myPressure1^pressure value 1^^PV^Syst/A|4|128||||||F
OBX|24|ST|^^^PV^#1|4|2||||||F
OBX|25|ST|^^^PV^Diast/V|4|70||||||F
OBX|26|ST|^^^PV^#2|4|2||||||F
OBX|27|ST|^^^PV^ED/Mean|4|95||||||F
OBX|28|ST|^^^PV^#3|4|2||||||F
OBX|29|ST|^^^VD^Site <DIC>|1|RV||||||F
OBX|30|ST|^^^VD^Max dp/dt (mm hg/s)|1|642||||||F
OBX|31|ST|^^^VD^Max dp/dt/p (/s)|1|19||||||F
OBX|32|ST|^^^VD^Mean Sys press (mm hg)|1|||||||F
OBX|33|ST|^^^VD^Mean Dias press (mm hg)|1|||||||F
OBX|34|ST|^^^VD^Stroke Work|1|||||||F
OBX|35|ST|^^^VD^Stroke Work Index|1|||||||F
OBX|36|ST|^^^VD^Stroke Power|1|||||||F
OBX|37|ST|^^^VD^Stroke Power Index|1|||||||F
OBX|38|ST|^^^VD^Sample Number|1|2||||||F
OBX|39|ST|^^^VD^Site <DIC>|2|LV||||||F
OBX|40|ST|^^^VD^Max dp/dt (mm hg/s)|2|225||||||F
OBX|41|ST|^^^VD^Max dp/dt/p (/s)|2|8||||||F
OBX|42|ST|^^^VD^Mean Sys press (mm hg)|2|||||||F
OBX|43|ST|^^^VD^Mean Dias press (mm hg)|2|14||||||F
OBX|44|ST|^^^VD^Stroke Work|2|||||||F
OBX|45|ST|^^^VD^Stroke Work Index|2|||||||F
OBX|46|ST|^^^VD^Stroke Power|2|||||||F
OBX|47|ST|^^^VD^Stroke Power Index|2|||||||F
OBX|48|ST|^^^VD^Sample Number|2|2||||||F
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
265 / 456
System Administration
DFTP03
Segments used
(DFTP03)
Message example
(DFTP03)
Post detail financial transactions: The Detailed Financial Transaction message is
used to describe a financial transaction transmitted between systems.
MSH
Message Header
Standard HL7 message header
EVN
Event Type
Necessary trigger event information
PID
Patient Identification
Minimal patient identification information
FT1
Financial Transaction
Contains the detailed data necessary to post
charges, payments, etc. to patient accounting records.
PR1
Procedures
Contains information about the procedures
performed.
DG1
Diagnosis
Contains information about any diagnoses
made.
MSH|^~\&|CATH^Sensis||^Server||20030304085017||DFT^P03|77|P|2.4
EVN||20030304085017
PID||20020904 1755|20020904 1755||Cathcor case^O'Leary||19431024|F
FT1|0|||20030304085017||CG|Femoral vein left^Judkins JR 3.5^ESITE|Judkins JR
3.5
FT1|1|||20030304085017||CG|Umbilical artery^Judkins JL 6^ESITE|Judkins JL 6
FT1|2|||20030304085017||CG|Saphenous vein right^Swan Ganz Monitoring^ESITE|Swan Ganz Monitoring
FT1|3|||20030304085018||CG|Newton, Fred^^PNNAME^Physician^^STAFF
FT1|4|||20030304085018||CG|Taylor, George^^PNNAME^Nurse^^STAFF
FT1|5|||20030304085018||CG|Jensen, Henry^^PNNAME^Circulator^^STAFF
FT1|6|||20030304085018||CG|Atropine^^MEDICA|||10
FT1|7|||20030304085018||CG|Cimetidine^^MEDICA|||22
FT1|8|||20030304085018||CG|Solu-Cortef^^MEDICA|||50
FT1|9|||20030304085019||CG|Digoxin^^MEDICA|||20
FT1|10|||20030304085019||CG|Cimetidine^^MEDICA|||10
PR1|0|PROCED|Selective Aortography^Selective Aortography^PROCED|Selective
Aortography|000000001002|I
PR1|1|PROCED|Endomyocardial Biopsy^Endomyocardial Biopsy^PROCED|Endomyocardial Biopsy|000000001003|I
PR1|2|PROCED|Temporary Transcutaneous Pacing^Temporary Transcutaneous
Pacing^PROCED|Temporary Transcutaneous Pacing|000000001003|I
266 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
DG1|0|DIAGNO|Acute Myocardial Infarction^Acute Myocardial Infarction^DIAGNO|Acute Myocardial Infarction||W||||||||||^Brown, Allan~^Smith, Beatrice
DG1|1|DIAGNO|Mitral Stenosis^Mitral Stenosis^DIAGNO|Mitral Stenosis||W||||||||||^Brown, Allan~^Smith, Beatrice
DG1|2|DIAGNO|Atypical Chest pain^Atypical Chest pain^DIAGNO|Atypical Chest
pain||W||||||||||^Brown, Allan~^Smith, Beatrice
DG1|3|DIAGNO|Positive Stress Test^Positive Stress Test^DIAGNO|Positive Stress
Test||W||||||||||^Brown, Allan~^Smith, Beatrice
DG1|4|DIAGNO|Mitral Regurgitation^Mitral Regurgitation^DIAGNO|Mitral Regurgitation||W||||||||||^Brown, Allan~^Smith, Beatrice
DG1|5|DIAGNO|Aortic Regurgitation^Aortic Regurgitation^DIAGNO|Aortic Regurgitation||W||||||||||^Brown, Allan~^Smith, Beatrice
DG1|6|DIAGNO|IHSS^IHSS^DIAGNO|IHSS||W||||||||||^Brown, Allan~^Smith, Beatrice
DG1|7|DIAGNO|Aortic Stenosis^Aortic Stenosis^DIAGNO|Aortic Stenosis||W||||||||||^Brown, Allan~^Smith, Beatrice
Message definitions for outgoing messages to a material management system
DFTP03
Segments used
(DFTP03)
ACKP03
AXIOM Sensis XP (VC11)
Item usage message back to the material management system: This message
is used between QSight and Sensis in both directions. Sensis uses the message to
notify QSight of item usage information entered in Documentation Tool.
MSH
Message Header
Standard HL7 message header
PID
Patient Identification
Minimal patient identification information
PV1
Patient Visit
Used to communicate information on a visitspecific basis.
FT
Item transaction informa- Information about material items checked
tion
out for a patient.
ZII
Item information
This segment contains information of an
item or product.
Acknowledgment for material master file update: This message is sent every
time QSight receives a DFTP03 message from the Sensis.
AXA5-200.640.07.01.02
267 / 456
System Administration
Segments used
(ACKP03)
MSH
Message Header
Standard HL7 message header
MSA
Message Acknowledgment
Contains information sent while acknowledging another message
ASCII flat file communication
The AXIOM Sensis XP Information System can exchange data with other systems via ASCII flat file. A number of syntax and format rules as well as general data
transfer requirements have to be observed.
Rules and requirements for inbound messages
These are the rules you need to observe when configuring an ASCII flat file in the
other system. The AXIOM Sensis XP Information System can only read and interpret ASCII flat files that send data and present them as described here.
Transferred data
Data import via ASCII flat file applies only to preregistration data. The following patient data attributes can be imported: ID, Last name, First name, DOB (data of
birth), Height, Weight, Sex. Furthermore, any database table can be included in
the import (section between extend_begin ... extend_end).
Transfer process
The information system expects the external sender system to transfer the ASCII
flat file to the directory C: \ MIS \ ccnsw \ demogr \ data on the AXIOM Sensis XP
Information System server. Furthermore, a flag file with the same name as the
data file indicating completed file transfer must be stored in the directory C: \ MIS
\ ccnsw \ demogr \ flag. The send order of the files is important. The data file must
be sent and stored before the flag file.The files can either be copied directly to the
directories, or transferred via ftp.
Syntax rules for the import file
Patient data
 ID
– Patient ID, max. 64 characters.
 Last name
– Max. 64 characters
 First name
– The first name field can also contain middle name and prefix and suffix in
DICOM notation.
– Max. 64 characters for each of the parts.
– Max. 120 characters for total length
Example for first name fields:
– First name only (firstname = firstname)
268 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
– First name, middle name (firstname = firstname^middlename)
– First name, prefix (firstname = firstname^^prefix)
– First name, prefix, postfix (firstname = firstname^^prefix^suffix)
– All parts (firstname = firstname^middlename^prefix^suffix)
 DOB (date of birth)
– Format: mm/dd/yyyy
– mm = month, dd = day, yyyy = year. Years must be 4 digits.
 Height
– Format: xxx <unit>
– xxx is the height value (without decimals). <unit> is the height unit string, it
can be “cm” or “inch”.
 Weight
– Format: xxx.x <unit>
– xxx.x is the weight value (with or without decimals, decimal separator must
be a decimal point “.”).
<unit> is the weight unit string, it can be “kg” or “pound”.
 Sex
– Can be “female” or “male”.
Syntax example:
status:1
id:Prereg 1
lastname:Prereg 1 Last name
firstname:Prereg 1 First name^Midddle name^^postfix
dob:02/15/2002
height:52 cm
weight:3.7 kg
sex:male
extend_begin:
extend_end:
….
id:Prereg n
lastname:Prereg n Last name
firstname:Prereg n First name
dob:01/15/2002
height:74 cm
weight:7.3 kg
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
269 / 456
System Administration
sex:male
extend_begin:
extend_end:
Note
Section: extend_begin...
extend_end
The file can contain preregistration information for one or several patients. The
first line of the file must contain “status:x”, where x must be > 0.
 The data has to be entered as a number of lines in ASCII format.
– All characters must be in 8-bit ASCII IBM code page 437.
– The pipe character (|) (decimal value 179) is used as a separator between
field names and data.
 Only customer-defined groups (database tables) are accepted.
 Field and data lines can be a maximum of 80 characters long.
– If lines would turn out longer they must be split up (each new line may
again be a maximum of 80 characters long).
– The line break must be between two field items.
– A hyphen (-) indicates the line is to be continued.
Syntax example:
extend_begin:
group:GROUP1group name
fields:|FIELD1|FILED2|.|FIELDN| field names
|data1|data2|.|datan| data for the fields, record 1
|data1|data2|.|datan| record 2
..
|data1|data2|.|datan| record n
group:GROUP2 group name
fields:|FIELD1|FILED2|.|FIELDN|- field names, first part, ended by a hyphen (-)
|FIELDN+1|.|FIELDX| field names continued
|data1|data2|.|datax| data for the fields, record 1
|data1|data2|.|datax| record 2
..
|data1|data2|.|datax| record n
extend_end:
 Only the field names of the fields to which data are to be written need to be
included.
270 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
 The order of the data fields in the data record must be the same as the order of
the field names in the fields line.
 If no data exist for a field, the enclosing pipe characters must still be present to
maintain the correct order.
 All fields defined as key fields in a group must be present in the fields line. Data
must also be present in the corresponding data fields in each data record.
 The number of permitted data records for a group depends on the group type.
– Group type = 1 - only one data record is allowed.
– Group type = 2 - any number of data records are allowed, but the key fields
data values for each record must form a unique key.
– Group type = 3,4,5 - any number of data records are allowed.
 The contents of a field is checked against the type of the field, to which it will
be loaded. If, for example, a non-digit character is sent to an integer field, the
complete data record will be ignored.
 There is no check whether the data (the code) entered in a field with an asso-
ciated dictionary is actually present in the corresponding dictionary.
– It is the responsibility of the external sender system to have access to the
current definition of the corresponding dictionary.
Rules for outbound messages
Whenever you define ASCII flat file export of data from the AXIOM Sensis XP Information System database (data format HIS on the Config tab card of the Communication Manager), this is the syntax that will be used.
In order to make sure the other system reads this information correctly you will
have to configure data import there according to these rules.
Transferred data
The data of any database table configured in the DB Manager can be exported using this export method. An output cluster must be created for each data export
job.
The following rules apply for cluster definition:
 If left empty, all data will be exported for the study.
 If tables are listed, only these tables will be included.
 If single field names are listed after the group name, these will be excluded.
 The tables PI, ID, PD will always be included.
See Editing clusters 106
Transfer process
AXIOM Sensis XP (VC11)
The export file can either be copied directly to a network node (send method File
Copy or FTP) or copied to a local directory where an external system picks it up
(send method File Copy).
AXA5-200.640.07.01.02
271 / 456
System Administration
If the other system uses ftp to pick up the file, the file should be copied to the directory C: \ MIS \ ccnsw \ demogr \ his_output.
Syntax of the export
file
Example
Group:PI
Fields:|REFNO|IDNR|LASTNAME|FIRNAME|UNIQID|EXAMFILE|
|1|47111|Lastname|Testfirstname|XXXX|YYYY|
Group:PD
Fields:|REFNO|SEX|DOB|AGE|AGEUNIT|AGEDAYS|HEIGHT|WEIGHT|BSA|PREHB|
|1|1-Female|12/31/99|66|1-Years||177|88.00|1.23|13.40|
Group:ID
Fields:|REFNO|EXAMDATE|STATIME|PROCTIME|ENDTIME|
|1|02/02/93|12:00|60|13:00|
Group:CN
Fields:|REFNO|CONDNR|CONDDATE|CONDTIME|HR|HRNR|HRSITE|
|1|1|12/31/99|12:01|66|4|20-LV|
|1|2|12/31/99|12:20|88|14|20-LV|
Group:IV
Fields:|REFNO|CONDNR|INTERV|AMOUNT|
|1|1|0-Rest||
|1|2|1-Exercise|12W|
|1|2|16-Atrophine|10mg|
Group:PV
Fields:|REFNO|CONDNR|SITE|PRESS1|SAMP1|PRESS2|SAMP2|PRESS3|SAMP3|
|1|1|2-IVC|7|1|6|1|7|1|
|1|1|3-RA|4|2|4|2|4|2|
|1|1|27-ART R.Br|165|9|98|9|120|9|
|1|1|70-PA Prox|19|10|11|10|15|10|
|1|2|5-IVC Low|5|11|6|11|15|11|
|1|2|13-VEN|4|12|3|12|1|12|
|1|2|22-AO|143|15|100|15|121|15|
|1|2|101-ART R.Ca|143|16|99|16|132|16|
272 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Overview of system groups available for data export
This is an overview of the system tables you may include in output clusters in order
to export their data to other systems.
.
Group Name
Group Text
Field Name
Format
Field Text
PATIENT
Patient
LASTNAME
64 chrs
Last name
FIRNAME
64 chrs
First name
MIDNAME
64 chrs
Middle name
TITLE
64 chrs
Title
SUFFIX
64 chrs
Suffix
PATID
64 chrs
PATCHGS
Patient record
changes
AXIOM Sensis XP (VC11)
Dictionary
Patient ID
*
PATBIRTH
Date 10
PATSEX
Integer
Patient's Sex
NAME1
64 chrs
Other Patient Names
PATID1
64 chrs
Other Patient ID
OCCUPAT
16 chrs
Occupation
HL7LOCK
1 chr
Data change lock.
PATHIST
Text file
Add. patient history
PATCOM
Text file
Additional info
ADDRESS
64 chrs
Patient's Address
ETHNIC
16 chrs
Ethnic Group
MILRANK
64 chrs
Military Rank
PID
Integer
PID
CONFLICT
Date 10
Patient ID conflict
ORIGIN
Integer
Registration origin
SSNUMBER
32 chrs
Social Security No.
SITEID
180 chrs
Site Id
TIMESTMP
Date 10
Changed time
LASTNAME
64 chrs
Last name
FIRNAME
64 chrs
First name
MIDNAME
64 chrs
Middle name
TITLE
64 chrs
Title
SUFFIX
64 chrs
Suffix
AXA5-200.640.07.01.02
Patient's Birth Date
273 / 456
System Administration
Group Name
STUDY
274 / 456
Group Text
Study
Field Name
Format
Field Text
PATID
64 chrs
Patient ID
PATBIRTH
Date 10
Patient's Birth Date
PATSEX
Integer
Patient's Sex
NAME1
64 chrs
Other Patient Names
PATID1
64 chrs
Other Patient ID
OCCUPAT
16 chrs
Occupation
ADDRESS
64 chrs
Patient's Address
ETHNIC
16 chrs
Ethnic Group
MILRANK
64 chrs
Military Rank
HOSTNAME
64 chrs
Computer name
USERID
64 chrs
User login id
USERACT
10 chrs
User action
REFNO
Integer
Entry in table PI
OPENED
1 chrs
Study open Y/N
ACQU
1 chrs
Acquisition Y/N
TIMEOUT
1 chrs
Study timeout Y/N
SIGNED
1 chrs
Study signed Y/N
STUDATE
Date 10
Study date
NCSTUID
64 chrs
Newcor StudyInstance UID
UNIQID
24 chrs
CATHCOR case uniqid
REFPHYS
64 chrs
Referring Phys.'s Name
REQPHYS
64 chrs
Requesting Phys.'s Name
DIAGNOSE
64 chrs
Admitting Diagnosis Dscp
PATLOC
64 chrs
Current Patient Location
ADMISSID
64 chrs
Admission ID
INSTRES
64 chrs
Patient's Inst Residence
STUDYID
16 chrs
Study id
ACCESSNO
16 chrs
Accession Number
REQPRID
16 chrs
Requested Procedure ID
REQPRDES
64 chrs
Req. Procedure Descript
STUDESC
64 chrs
Study Description
STUCOM
Text file
Study Comments
AXA5-200.640.07.01.02
Dictionary
System Administration
Communication Manager
Group Name
PI
PD
Group Text
Case identification
Demographic data
AXIOM Sensis XP (VC11)
Field Name
Format
Field Text
PATPOS
16 chrs
Patient Position
INSTNAME
64 chrs
Institution Name
PERPHYS1
64 chrs
Performing Phys 1’s Name
PERPHYS2
64 chrs
Performing Phys 2’s Name
OPNAME1
64 chrs
Operator 1's Name
OPNAME2
64 chrs
Operator 2's Name
PREMED
64 chrs
Pre-Medication
CONTRAST
64 chrs
Requested Contrast Agent
MEDALERT
64 chrs
Medical Alert
ALLERGY
64 chrs
Contrast Allergies
SPECNEED
64 chrs
Special Needs
PATSTATE
64 chrs
Patient State
SMOKING
16 chrs
Smoking status
PREGSTAT
Integer
Pregnancy Status
MENSDATE
Date 10
Last Menstruation Date
STATEID
Integer
State id. See stustate
PCATHTIM
Date 10
Postcath start time
ORDNUM
32 chrs
Placer Order Number
IDNR
20 chrs
ID
LASTNAME
30 chrs
Last name
FIRNAME
30 chrs
First name
UNIQID
24 chrs
Network-unique Case ID
EXAMFILE
12 chrs
Examination file
SEX
Integer
Sex <DIC>
DOB
Date 10
Date of birth
AGE
Integer
Age
AGEUNIT
Integer
Age unit <DIC>
AGEDAYS
Integer
Age in Days
HEIGHT
Integer
Height (cm)
WEIGHT
Float
Weight (kg)
BSA
Float
Body surface area (sqm)
PREHB
Float
"Field is not used"
AXA5-200.640.07.01.02
Dictionary
SEX
AGEUNI
275 / 456
System Administration
Group Name
Group Text
Field Name
Format
Field Text
PE
Preregister date
EDATE
Date 10
Registration date
PH
Extended HIS date
EXTDATE
90 chrs
Extended HIS date
UN
Units
HB
Integer
HB unit <DIC>
UNWORK
Integer
WORK & POWER unit <DIC> WPUNIT
RESIST
Integer
RESISTANCE unit <DIC>
REUNIT
INFHR
Integer
HR unit <DIC>
HRUNIT
INFSPO2
Integer
SpO2 unit <DIC>
SPUNIT
INFRESP
Integer
RESP unit <DIC>
RPUNIT
INFNBP
Integer
NBP unit <DIC>
NBUNIT
INFETCO2
Integer
etCO2 unit <DIC>
ETUNIT
ETCO2
Integer
etCO2 unit <DIC>
_ETCO2
EXAMDATE
Date 10
Examination Date
ID
Investigation data
†
Dictionary
HBUNIT
STATIME
Time 8
Start Time
PROCTIME
Integer
Procedure Time (min)
ENDTIME
Time 8
End time
ACQNAME
ACQ Unit Computer COMPUTER
name
64 chrs
ACQ Unit Computer name
CN
Conditions
CONDNR
Integer
Condition number
CONDDATE
Date 10
Cond. date (user format)
CONDTIME
Time 8
Condition time
HR
Integer
Heart rate (/min)
HRNR
Integer
HR Sample Number
HRSITE
Integer
HR site <DIC>
CONDNAME
64 chrs
Condition name
CONDNR
Integer
Condition number
INTERV
Integer
Intervention <DIC>
AMOUNT
20 chrs
Amount
CONDNR
Integer
Cond. no
SITE
Integer
Site <DIC>
PRESS1
Integer
Syst/A
SAMP1
Integer
#1
PRESS2
Integer
Diast/V
IV
PV
276 / 456
Interventions
Pressure Values
AXA5-200.640.07.01.02
SITE
INTERV
SITE
System Administration
Communication Manager
Group Name
_FFR
_M_FFR
SA
VD
Group Text
FFR
Manual FFR
Saturations
Ventricular data
AXIOM Sensis XP (VC11)
Field Name
Format
Field Text
SAMP2
Integer
#2
PRESS3
Integer
ED/Mean
SAMP3
Integer
#3
CONDNR
Integer
Condition no.
DATETIME
Time
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
FFRVALUE
Float
FFR Value
SITE1
100 chrs
Anatomic site
SITE2
100 chrs
Anatomic site
PRO_MEAN
Float
Proximal mean pressure
DIS_MEAN
Float
Distal mean pressure
EVNT_DUR
Integer
Event duration (s)
PRES_DIF
Integer
Pressure difference
CONDNR
Integer
Condition no.
DATETIME
Time
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
FFRVALUE
Float
FFR Value
SITE1
100 chrs
1st anatomic site
SITE2
100 chrs
2nd anatomic site
CONDNR
Integer
Condition number
SITE
Integer
Site <DIC>
O2SAT
Float
O2-Sat.
O2CONT
Float
O2-Cont.
OXYTIME
Time 5
Sample time
PO2
Float
PO2
CONDNR
Integer
Condition number
SITE
Integer
Site <DIC>
DPDT
Integer
Max dp/dt (mm hg/s)
DPDTP
Integer
Max dp/dt/p (/s)
MSPRE
Integer
Mean Sys press (mm hg)
AXA5-200.640.07.01.02
Dictionary
SITE
Float
SITE
277 / 456
System Administration
Group Name
VG
SG
278 / 456
Group Text
Valve gradients
Special gradients
Field Name
Format
Field Text
MDPRE
Integer
Mean Dias press (mm hg)
SW
Float
Stroke Work
SWI
Float
Stroke Work Index
SP
Float
Stroke Power
SPI
Float
Stroke Power Index
LVNR
Integer
Sample Number
CONDNR
Integer
Condition number
VALVE
Integer
Valve <DIC>
GRAD
Integer
Mean gradient (mm hg)
VALVAREA
Float
Valve area (sqcm)
PERIOD
Float
Period (s/min)
PREDIFF
Integer
Press diff (mm hg)
SIMPUB
Integer
Simult. or PUB <DIC>
VGNR
Integer
Sample Number
DURATION
Integer
SED or DFD (ms)
VAIX
Float
Valve Area Index
COTYPE
Integer
CO-method
VALVA226
Float
Valve area (sqcm)
VALVA227
Float
Valve area (sqcm)
VALVA145
Float
Valve area (sqcm)
VALVA225
Float
Valve area (sqcm)
SITE1
Integer
Site 1
SITE2
Integer
Site 2
VAIX226
Float
Valve area index
VAIX227
Float
Valve area index
VAIX145
Float
Valve area index
VAIX225
Float
Valve area index
CONDNR
Integer
Condition number
SITE1
Integer
Site 1 <DIC>
SITE
SITE2
Integer
Site 2 <DIC>
SITE
GRAD
Integer
Mean gradient (mm hg)
VALVAREA
Float
Valve area (sqcm)
AXA5-200.640.07.01.02
Dictionary
VALVE
SIMPUB
System Administration
Communication Manager
Group Name
CO
CF
CP
Group Text
Cardiac output
Field Name
Format
Field Text
PERIOD
Float
Period (s/min)
PREDIFF
Integer
Press diff (mm hg)
SIMPUB
Integer
Simult. or PUB <DIC>
SGNR
Integer
Sample Number
CONDNR
Integer
Condition number
COTYPE
Integer
CO-method <DIC>
COTYPE
INJSITE
Integer
Injection site <DIC>
SITE
SAMPSITE
Integer
Sample site <DIC>
SITE
CO
Float
Cardiac output (1/min)
COHR
Integer
Heart rate (/min)
COTIME
Time 5
CO sample time
CI
Float
Cardiac Index(l/min/sqm)
INHERIT
Integer
Inherited flag (1=yes)
SCONDNR
Integer
Source condition number
Integer
Condition number
O2CONS
Float
O2-consumption (ml/min)
O2CONSP
Float
Pred. O2-cons. (ml/min)
AVO2DIFF
Float
A-V O2-diff. (ml/l)
O2CAP
Float
O2-capacity
CONHB
Float
HB
Integer
Condition number
PREDCO
Float
Pred. CO (l/min)
COTYPE
Integer
CO-method <DIC>
CI
Float
Cardiac Index (l/min/sqm)
SV
Float
Stroke Volume (ml/beat)
SVI
Float
S.V. Index (ml/beat/sqm)
PAR
Float
Pulm. Art. Res.
SVR
Float
Syst. Vasc. Res.
TPR
Float
Total Pulm. Res.
PARIX
Float
PAR index
SVRIX
Float
SVR index
TPRIX
Float
TPR index
Cardiac output - Fick CONDNR
Derived parameters CONDNR
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
Dictionary
SIMPUB
COTYPE
279 / 456
System Administration
Group Name
280 / 456
Group Text
Field Name
Format
Field Text
TPRTSR
Float
TPR/TSR
REGSV
Float
Regurg.SV (ml/beat)
REGSVI
Float
Regurg.SVI (ml/beat/sqm)
REGF
Float
Regurg. Fraction
PARSVR
Float
PAR/SVR
PARPRD
Float
Predicted PAR
SVRPRD
Float
Predicted SVR
TSR
Float
Total Syst. Res.
TSRIX
Float
TSR Index
TPAR
Float
Thermo PAR
DPAR
Float
Dye PAR
APAR
Float
Angio PAR
FPAR
Float
Fick PAR
TTPR
Float
Thermo TPR
DTPR
Float
Dye TPR
ATPR
Float
Angio TPR
FTPR
Float
Fick TPR
TPARIX
Float
Thermo PAR Index
DPARIX
Float
Dye PAR Index
APARIX
Float
Angio PAR Index
FPARIX
Float
Fick PAR Index
TTPRIX
Float
Thermo TPR Index
DTPRIX
Float
Dye TPR Index
ATPRIX
Float
Angio TPR Index
FTPRIX
Float
Fick TPR Index
TSVR
Float
Thermo SVR
DSVR
Float
Dye SVR
ASVR
Float
Angio SVR
FSVR
Float
Fick SVR
TTSR
Float
Thermo TSR
DTSR
Float
Dye TSR
ATSR
Float
Angio TSR
AXA5-200.640.07.01.02
Dictionary
System Administration
Communication Manager
Group Name
SH
Group Text
Shunts
AXIOM Sensis XP (VC11)
Field Name
Format
Field Text
FTSR
Float
Fick TSR
TSVRIX
Float
Thermo SVR Index
DSVRIX
Float
Dye SVR Index
ASVRIX
Float
Angio SVR Index
FSVRIX
Float
Fick SVR Index
TTSRIX
Float
Thermo TSR Index
DTSRIX
Float
Dye TSR Index
ATSRIX
Float
Angio TSR Index
FTSRIX
Float
Fick TSR Index
TTTR
Float
Thermo TPR TSR Ratio
DTTR
Float
Dye TPR TSR Ratio
ATTR
Float
Angio TPR TSR Ratio
FTTR
Float
Fick TPR TSR Ratio
TPSR
Float
Thermo PAR SVR Ratio
DPSR
Float
Dye PAR SVR Ratio
APSR
Float
Angio PAR SVR Ratio
FPSR
Float
Fick PAR SVR Ratio
CONDNR
Integer
Condition number
PAVO2D
Float
Pulm. AVO2-diff. (ml/l)
SAVO2D
Float
Syst. AVO2-diff. (ml/l)
PF
Float
Pulm. Flow (1/min)
SF
Float
Syst. Flow (1/min)
PFI
Float
P.F.Index (1/min/sqm)
SFI
Float
S.F.Index (1/min/sqm)
PSV
Float
P.S.V. (ml/beat)
SSV
Float
S.S.V. (ml/beat)
PSVI
Float
P.S.V.I. (ml/beat/sqm)
SSVI
Float
S.S.V.I. (ml/beat/sqm)
SITEMV
Integer
Site-Mixed Venous <DIC>
SATMV
Float
O2-Sat. Mixed Venous
SITEPA
Integer
Site - Pulm. Art.<DIC>
SATPA
Float
O2 Sat. Pulm. Art.
AXA5-200.640.07.01.02
Dictionary
SITE
SITE
281 / 456
System Administration
Group Name
GM
SM
282 / 456
Group Text
Study measurem.Grads
Study measurem.single S.
Field Name
Format
Field Text
Dictionary
SITEPV
Integer
Site - Pulm. Ven <DIC>
SITE
SATPV
Float
O2 Sat. Pulm. Ven
SITESA
Integer
Site - Syst. Art.<DIC>
SATSA
Float
O2 Sat. Syst. Art.
LRRATIO
Float
L-R shunt ratio
RLRATIO
Float
R-L shunt ratio
LRFLOW
Float
L-R shunt (1/min)
RLFLOW
Float
R-L shunt (1/min)
PSRATIO
Float
Pulm/Syst flow ratio
PO2MV
Float
PO2 - Mixed Venous
PO2PA
Float
PO2 - Pulm. Art.
PO2PV
Float
PO2 - Pulm. Ven.
PO2SA
Float
PO2 - Syst. Art.
CONDNR
Integer
Condition number
SERIENR
Integer
Study series no.
MEASNR
Integer
Measurement no.
GMTIME
Time 5
Time of measurement
DURATION
Integer
Inflation time (sec)
INFL
6 chrs
Infl press/amount
GRAD
Integer
Gradient
CONDNR
Integer
Condition number
SERIENR
Integer
Study series no.
Integer
MEASNR
Integer
Measurement no.
Integer
SMTIME
Time 5
Time of measurement
DURATION
Integer
Inflation time (sec)
INFL
6 chrs
Infl press/amount
PRE1
Integer
Pressure S/A
PRE2
Integer
Pressure D/V
PRE3
Integer
Pressure E/M
AXA5-200.640.07.01.02
SITE
System Administration
Communication Manager
Group Name
Group Text
Field Name
Format
Field Text
AM
Study measurem.Area
CONDNR
Integer
Condition number
SERIENR
Integer
Study series no.
MEASNR
Integer
Measurement no.
AMTIME
Time 5
Time of measurement
DURATION
Integer
Inflation time (sec)
INFL
6 chrs
Infl press/amount
GRAD
Integer
Gradient
PROXPRE
Integer
Proximal pressure
DISTPRE
Integer
Distal pressure
PREDIFF
Integer
Pressure difference
MONPRE
Integer
Monitoring pressure
CO
Float
CO
AREA
Float
Area
CONDNR
Integer
Condition number
STUDYTYP
Integer
Study type <DIC>
SERIENR
Integer
Study series no.
SCALE
Integer
Histogram scale
PROXSITE
Integer
Proximal site <DIC>
SITE
DISTSITE
Integer
Distal site <DIC>
SITE
NOMEA
Integer
Total no.of measurements
NRINT
Integer
Total no. of infl or inj
DURATION
Integer
Total inflation time
MAXAMO
6 chrs
Max infl.pr. or amount
FIRSTGRA
Integer
First gradient
LASTGRA
Integer
Last gradient
CONDNR
Integer
Condition number
STUDYTYP
Integer
Study type <DIC>
SERIENR
Integer
Study series no.
SCALE
Integer
Histogram scale
GS
SS
Study SummaryGradient
Study Sum.- Single
Sites
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
Dictionary
STUDY
STUDY
283 / 456
System Administration
Group Name
VS
TS
LCI
284 / 456
Group Text
Study Summary Areas
Sample Acquisition
times
Log Condition
Field Name
Format
Field Text
Dictionary
SITE
Integer
Site code <DIC>
SITE
NOMEA
Integer
Total no.of measurements
NRINT
Integer
Total no. of infl or inj
DURATION
Integer
Total inflation time
MAXAMO
6 chrs
Max infl.pr. or amount
DISPTYPE
Integer
Type of display
FIPRE1
Integer
First pressure S/A
FIPRE2
Integer
First pressure D/V
FIPRE3
Integer
First pressure E/M
LAPRE1
Integer
Last pressure S/A
LAPRE2
Integer
Last pressure D/V
LAPRE3
Integer
Last pressure E/M
CONDNR
Integer
Condition number
STUDYTYP
Integer
Study type <DIC>
SERIENR
Integer
Study series no.
PROXSITE
Integer
Proximal site <DIC>
SITE
DISTSITE
Integer
Distal site <DIC>
SITE
NOMEA
Integer
Total no.of measurements
NRINT
Integer
Total no. of infl or inj
DURATION
Integer
Total inflation time
MAXAMO
6 chrs
Max infl.pr. or amount
FIRSTGRA
Integer
First gradient
LASTGRA
Integer
Last gradient
PROXTYPE
Integer
Proximal pressure type
DISTTYPE
Integer
Distal pressure type
MONSITE
Integer
Site for monitoring <DIC>
MONTYPE
Integer
Monitoring pressure type
SAMPNR
Integer
Sample number
SAMPTIME
Time 8
Acquisition time
ATIME
Time 8
Acquisition time
AXA5-200.640.07.01.02
STUDY
SITE
System Administration
Communication Manager
Group Name
LCF
LCO
Group Text
Log CO-Fick
Log CO
AXIOM Sensis XP (VC11)
Field Name
Format
Field Text
CONDNR
Integer
Condition number
INTERV1
Integer
Intervention 1 <DIC>
AMOUNT1
6 chrs
Amount 1
INTERV2
Integer
Intervention 2 <DIC>
AMOUNT2
6 chrs
Amount 2
INTERV3
Integer
Intervention 3 <DIC>
AMOUNT3
6 chrs
Amount 3
INTERV4
Integer
Intervention 4 <DIC>
AMOUNT4
6 chrs
Amount 4
CONDNAME
64 chrs
Condition name
ATIME
Time 8
Acquisition time
CONDNR
Integer
Condition number
CO
Float
Cardiac output
ARTSIT
Integer
Arterial site <DIC>
SITE
VENSIT
Integer
Venous site <DIC>
SITE
SAT1
Float
O2-Sat 1
SAT2
Float
O2-Sat 2
O2CONS
Float
O2 Consumption
FICKHB
Float
Hemoglobin (Fick)
COHR
Integer
Entered Heart Rate
COVTIM
Time 5
Entered time
ATIME
Time 8
Acquisition time
CONDNR
Integer
Condition number
COTYPE
Integer
CO method <DIC>
COMEAN
Float
Mean CO
SITE1
Integer
Injection site <DIC>
SITE
SITE2
Integer
Sample site <DIC>
SITE
CO1
Float
CO 1
CO2
Float
CO 2
CO3
Float
CO 3
CO4
Float
CO 4
CO5
Float
CO 5
AXA5-200.640.07.01.02
Dictionary
INTERV
INTERV
INTERV
INTERV
COTYPE
285 / 456
System Administration
Group Name
LSA
LPV
LP1
Group Text
Field Name
Format
Field Text
COHR
Integer
Entered heart rate
COVTIM
Time 5
Entered time
ATIME
Time 5
Acquisition time
PARTNR
Integer
Part number
CONDNR
Integer
Condition number
TIME1
Time 5
Sample time 1
SITE1
Integer
Site 1 <DIC>
SAT1
Float
O2 sat 1
TIME2
Time 5
Sample time 2
SITE2
Integer
Site 2 <DIC>
SAT2
Float
O2 sat 2
TIME3
Time 5
Sample time 3
SITE3
Integer
Site 3 <DIC>
SAT3
Float
O2 sat 3
PSRATIO
Float
Pulm/Syst flow ratio
LRRATIO
Float
L-R shunt ratio
RLRATIO
Float
R-L shunt ratio
SITEMV
Integer
Site -mixed venous <DIC>
SITE
SITEPA
Integer
Site - pulm. art <DIC>
SITE
SITEPV
Integer
Site - pulm. ven. <DIC>
SITE
SITESA
Integer
Site - syst. art <DIC>
SITE
PO21
Float
PO2 1
PO22
Float
PO2 2
PO23
Float
PO2 3
ATIME
Time 8
Acquisition time
CONDNR
Integer
Condition number
SEQNR
Integer
Sequence number
RSEQNR
Integer
Retr. sequence number
HR
Integer
Heart rate (/min)
HRSITE
Integer
HR Site <DIC>
Log Single Pressures SEQNR
Integer
Sequence number
Integer
Pressure Channel
Log Saturations
Log Pressure Seq.
CHANNEL
286 / 456
AXA5-200.640.07.01.02
Dictionary
SITE
SITE
SITE
SITE
System Administration
Communication Manager
Group Name
LP2
LP3
LP4
Group Text
Field Name
Format
Field Text
Dictionary
SITE
Integer
Site <DIC>
SITE
PRESS1
Integer
Pressure 1
PRESS2
Integer
Pressure 2
PRESS3
Integer
Pressure 3
SCONDNR
Integer
Source Condition number
RPRESS
1 chr
Representative Pressure
SEQNR
Integer
Sequence number
CHANNEL
Integer
Pressure channel
SITE1
Integer
Site 1 <DIC>
FPRESS1
Integer
Site 1 pressure 1
FPRESS2
Integer
Site 1 pressure 2
FPRESS3
Integer
Site 1 pressure 3
SITE2
Integer
Site 2 <DIC>
SPRESS1
Integer
Site 2 pressure 1
SPRESS2
Integer
Site 2 pressure 2
SPRESS3
Integer
Site 2 pressure 3
RPRESS
1 chr
Representative Pressure
RPRESS1
1 chr
Representative Pressure 1
Log Valve Gradients SEQNR
Integer
Sequence number
VALVE
Integer
Valve <DIC>
GRAD
Integer
Mean gradient (mm hg)
PREDIFF
Integer
Press diff (mm hg)
VALVAREA
Float
Valve area (sqcm)
PERIOD
Float
Period (s/min)
DURATION
Integer
SED or DFD (ms)
SEQNR
Integer
Sequence number
SITE1
Integer
Site 1 <DIC>
SITE
SITE2
Integer
Site 2 <DIC>
SITE
GRAD
Integer
Mean gradient (mm hg)
PREDIFF
Integer
Press diff (mm hg)
Log Pullback Pressures
Log Special Gradients
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
SITE
SITE
VALVE
287 / 456
System Administration
Group Name
LP5
LP6
LPI
LPA
288 / 456
Group Text
Field Name
Format
Field Text
VALVAREA
Float
Valve area (sqcm)
PERIOD
Float
Period (s/min)
Integer
Sequence number
SITE
Integer
Site <DIC>
DPDT
Integer
Max dp/dt (mm hg/s)
DPDTP
Integer
Max dp/dt/p (/s)
MSPRE
Integer
Mean sys press (mm hg)
MDPRE
Integer
Mean dias press (mm hg)
Log SpO2, NIBP and SEQNR
RESP
Integer
Sequence number
PRS
Integer
Heart rate SpO2
SPO2
Integer
SpO2
PRN
Integer
Heart rate NIBP
NIBPS
Integer
NIBPs
NIBPD
Integer
NIBPd
NIBPM
Integer
NIBPm
RESP
Integer
Resp rate
Time 8
Acquisition time
CONDNR
Integer
Condition number
STUDY
Integer
Type =1 infl. =2 interv
DURATION
Integer
Inflation time
AMOUNT
6 chrs
Intervention amount
ATIME
Time 8
Acquisition time
CONDNR
Integer
Condition number
STUDY
Integer
Type = 3
COMEAN
Integer
"Field is not used"
CO1
Float
CO 1
CO2
Float
CO 2
CO3
Float
CO 3
CO4
Float
CO 4
CO5
Float
CO 5
Log Ventricular Data SEQNR
Log Study-Interven- ATIME
tion
Log Study-Area
AXA5-200.640.07.01.02
Dictionary
SITE
System Administration
Communication Manager
Group Name
LSY
LPM
T_APLAST
T_VPLAST
T_CNTUP
T_CNTDWN
XRAY
Group Text
Field Name
Format
Field Text
VALVAREA
Float
Valve area (sqcm)
Time 8
Acquisition time
CONDNR
Integer
Condition number
STUDY
Integer
Study type <DIC>
STUDY
PROXSITE
Integer
Proximal site <DIC>
SITE
DISTSITE
Integer
Distal site <DIC>
SITE
Time 5
Time
MEALBL
12 chrs
Measurement (ms)
TOTINT
Integer
Total
INT1
Integer
Interval 1
INT2
Integer
Interval 2
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
INFLPRE
Integer
Infl. pressure
INFLDUR
Integer
Infl. duration
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
INFLPRE
Integer
Infl. pressure
INFLDUR
Integer
Infl. duration
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
ELAPSED
Time 8
Elapsed time
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
ELAPSED
Time 8
Elapsed time
ATIME
Time 8
Acquis. time
PLANE
1 chr
Plane
Log Study-Meas. Se- ATIME
rie
Time measurements ATIME
Angioplasty timer
Valvuloplasty timer
Count up timer
Count down timer
X-ray scene
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
Dictionary
289 / 456
System Administration
Group Name
XRAYA
XRAYSUM
XRAYASUM
290 / 456
Group Text
X-ray scene
Accum. X-ray data
Field Name
Format
Field Text
RLANG
Float
RAO/LAO angle <+/->
CCANG
Float
Cran./Caud. angle <+/->
SID
Float
SID <cm>
MAG
Integer
Magnification <%>
MO
1 chr
Mode <DIC>
KV
Float
Tube voltage <kV>
MA
Float
Tube current <mA>
FPS
Float
Frame rate <1/s>
PW
Float
Pulse width <ms>
TI
Float
Time of scene <s>
FO
1 chr
Focus <DIC>
LA
Integer
Detector size <cm>
ATIME
Time 8
Acquis. time
PLANE
1 chr
Plane
AD
Integer
Area dose <cGycm2>
SD
Integer
Skin dose <mGy>
CF
Float
Cu filter <mm>
NF
Integer
Number of frames
SC
Integer
Series counter
ASD
Integer
Ang. step Dyna <deg/pls>
IV
Integer
Injection volume <ml>
IFL
Integer
Injection flow <ml/s>
PLANE
1 chr
Plane
DOSE
Integer
Total area dose <cGycm2>
FLTIME
Float
Tot. fluoro time <min>
ALOAD
Integer
Load <for future use>
AFV
Float
Avg fluoro voltage kV
AFC
Float
Avg fluoro current mA
1 chr
Plane
SKNDS
Integer
Total skin dose <mGy>
LA
Integer
Amplifier format <cm>
ADPFL
Integer
Fluoro area dose<cGycm2>
Accum. X-ray data 2 PLANE
AXA5-200.640.07.01.02
Dictionary
XRMODE
FOCMOD
System Administration
Communication Manager
Group Name
XRAYBSUM
Group Text
Acc bi-plane x-ray
data
Field Name
Format
Field Text
SKDFL
Integer
Fluoro skin dose <mGy>
DOSE
Integer
Total area dose <cGycm2>
FLTIME
Float
Tot. fluoro time <min>
SKNDS
Integer
Total skin dose <mGy>
V_SIGNS‡
(do not send)
-
-
-
SPO2
Spo2
ATIME
Time 5
Time
PR
Integer
Heart rate
O2
Integer
SpO2
ATIME
Time 5
Time
PR
Integer
Heart rate
SYST
Integer
NIBPs
DIAST
Integer
NIBPd
MEAN
Integer
NIBPm
ATIME
Time 5
Time
RESP
Integer
Resp rate
EtCO2
Float
etCO2
ATIME
Time 5
Time
CHANNEL
Integer
IBPchannel
SITE
Integer
IBPsite
SYST
Integer
IBPs
DIAST
Integer
IBPd
NIBP
RESP
_IBP
NIBP
RESP
IBP
MEAN
ALDRSCRE
INFVS
Aldrete Score
Infinity Vital Signs
AXIOM Sensis XP (VC11)
Dictionary
IBPm
ATIME
Time 5
Time
CNSNS
Integer
Consciousness
RESPRN
Integer
Respiration
SKINCLR
Integer
Skin Color
MSCFN
Integer
Muscle Function
CIRCLN
Integer
Circulation
TAS
Integer
Total Aldrete Score
ATIME
Time 5
Time
HR
Integer
Heart rate
AXA5-200.640.07.01.02
291 / 456
System Administration
Group Name
REC
E_RECON
E_RECOFF
E_SNPSHT
E_WAVEF
E_ECG12
E_INTERV
292 / 456
Group Text
Case recording
Recording on
Recording off
Snapshot
Waveform
Ecg12Lead
Interval
Field Name
Format
Field Text
SYST
Integer
NIBPs
DIAST
Integer
NIBPd
MEAN
Integer
NIBPm
SPO2
Integer
SpO2
RESP
Integer
Resp rate
ETCO2
Float
etCO2
INFVSCMT
4000 chrs
Comment
VOLUME
12 chrs
Case recording volume
RECID
24 chrs
Case recording ID
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CONDNR
Integer
Condition no
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
MORPH
64 chrs
ECG Morphology
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
AXA5-200.640.07.01.02
Dictionary
System Administration
Communication Manager
Group Name
E_STIMEX
Group Text
Stim Extra
AXIOM Sensis XP (VC11)
Field Name
Format
Field Text
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
INTERV1
Integer
1st Interval (ms)
INTERV2
Integer
2nd Interval (ms)
INTERV3
Integer
3rd Interval (ms)
INTERV4
Integer
4th Interval (ms)
INTERV5
Integer
5th Interval (ms)
INTERV6
Integer
6th Interval (ms)
INTERV7
Integer
7th Interval (ms)
INTERV8
Integer
8 th Interval (ms)
INTLAB1
1000 chrs
1st Interval label
INTLAB2
1000 chrs
2nd Interval label
INTLAB3
1000 chrs
3rd Interval label
INTLAB4
1000 chrs
4th Interval label
INTLAB5
1000 chrs
5th Interval label
INTLAB6
1000 chrs
6th Interval label
INTLAB7
1000 chrs
7th Interval label
INTLAB8
1000 chrs
8th Interval label
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
LABEL
64 chrs
Stim setting label
PECHA
16 chrs
Positive electrode ch A
NECHA
16 chrs
Negative electrode ch A
PECHB
16 chrs
Positive electrode ch B
NECHB
16 chrs
Negative electrode ch B
S1S1
Integer
S1S1 time (ms)
S1S2
Integer
S1S2 time (ms)
S2S3
Integer
S2S3 time (ms)
S3S4
Integer
S3S4 time (ms)
S4S5
Integer
S4S5 time (ms)
AXA5-200.640.07.01.02
Dictionary
293 / 456
System Administration
Group Name
Group Text
Field Name
Format
Field Text
E_STIMC1
Stim Cont On
CONDNR
Integer
Condition no
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
LABEL
64 chrs
Stim setting label
PECHA
16 chrs
Positive electrode ch A
NECHA
16 chrs
Negative electrode ch A
PECHB
16 chrs
Positive electrode ch B
NECHB
16 chrs
Negative electrode ch B
PCL
Integer
Paced Cycle Length (ms)
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
LABEL
64 chrs
Stim setting label
PECHA
16 chrs
Positive electrode ch A
NECHA
16 chrs
Negative electrode ch A
PECHB
16 chrs
Positive electrode ch B
NECHB
16 chrs
Negative electrode ch B
PCLSTART
Integer
PCL start pulstrain (ms)
CONDNR
Integer
Condition no
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
LABEL
64 chrs
Stim setting label
PECHA
16 chrs
Positive electrode ch A
NECHA
16 chrs
Negative electrode ch A
PECHB
16 chrs
Positive electrode ch B
E_STIMC2
E_STIMD1
E_STIMDY
294 / 456
Stim Cont Off
Stim dynamic on
Stim dynamic off
AXA5-200.640.07.01.02
Dictionary
System Administration
Communication Manager
Group Name
_ESTEX2
_ESTC12
_ESTC22
_ESTD12
Group Text
Stim Extra
Stim Cont
Stim Cont Off
Stim dynamic on
AXIOM Sensis XP (VC11)
Field Name
Format
Field Text
NECHB
16 chrs
Negative electrode ch B
PCLSTART
Integer
PCL start pulstrain (ms)
PCLSTOP
Integer
PCL stop pulstrain (ms)
NOPULSES
Integer
No of pulses in train
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
INPCHA
Integer
Stim Input Channel
OUTSITE
64 chrs
Stim output site
S1S1
Integer
S1S1 time (ms)
S1S2
Integer
S1S2 time (ms)
S2S3
Integer
S2S3 time (ms)
S3S4
Integer
S3S4 time (ms)
S4S5
Integer
S4S5 time (ms)
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
INPCHA
Integer
Stim Input Channel
OUTSITE
64 chrs
Stim output site
PCL
Integer
Paced Cycle Length (ms)
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
INPCHA
Integer
Stim Input Channel
OUTSITE
64 chrs
Stim output site
AXA5-200.640.07.01.02
Dictionary
295 / 456
System Administration
Group Name
_ESTDY2
E_ABLAT1
E_ABLAT2
E_ABLAT3
296 / 456
Group Text
Stim dynamic off
Ablation On
Ablation Off
Ablation Summary
Field Name
Format
Field Text
PCLSTART
Integer
PCL start pulstrain (ms)
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
INPCHA
Integer
Stim Input Channel
OUTSITE
64 chrs
Stim output site
PCLSTART
Integer
PCL start pulstrain (ms)
PCLSTOP
Integer
PCL stop pulstrain (ms)
NOPULSES
Integer
No. of pulses in train
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
EVSEQNO
Integer
Event sequence no
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
EVSEQNO
Integer
Event sequence no
DURATION
Integer
Event duration (sec)
AVTEMP
Integer
Average temp (degree C)
AVPOWER
Integer
Average power (W)
AVIMPD
Integer
Average impedance (Ohm)
ENERGY
Integer
Ablation energy (J)
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
NOABLS
Integer
No of ablations
DURATION
Integer
Total time (sec)
AVTEMP
Integer
Average temp (degree C)
MAXTEMP
Integer
Max temp (degree C)
AVIMPD
Integer
Average imp (Ohm)
AXA5-200.640.07.01.02
Dictionary
System Administration
Communication Manager
Group Name
ABLGRIMG
E_TACHY1
E_TACHY2
E_BRADY1
E_BRADY2
MPSYSIMG
Group Text
Ablation Graph Images
Tachycardia on
Tachycardia off
Bradycardia on
Bradycardia off
Field Name
Format
Field Text
MAXIMPD
Integer
Max imp (Ohm)
AVPOWER
Integer
Average power (W)
MAXPOWER
Integer
Max power (W)
ENERGY
Integer
Ablation energy (J)
ATIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
FILENAME
128 chrs
Image Filename
CONDNR
Integer
Condition no
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CL
Integer
Arrythm cycle length ms
ONSET
Time 8
Onset time
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
CL
Integer
Arrythm cycle length ms
ONSET
Time 8
Onset time
CONDNR
Integer
Condition no
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
Time 8
Event Date/Time
4000 chrs
Event Comment
Mapping System Im- ATIME
ages
EVENTCMT
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
Dictionary
297 / 456
System Administration
Group Name
C_HEX
298 / 456
Group Text
Coronary variables
Field Name
Format
Field Text
IMGNAME
256 chrs
Image Name
IMGCMT
256 chrs
Image Comment
FILENAME
128 chrs
Image Filename
VERS
Integer
Version
SEQN
Integer
Sequence number
VAR1
Integer
Value1
VAR2
Integer
Value2
VAR3
Integer
Value3
VAR4
Integer
Value4
VAR5
Integer
Value5
VAR6
Integer
Value6
VAR7
Integer
Value7
VAR8
Integer
Value8
VAR9
Integer
Value9
VAR10
Integer
Value10
TEXT1
49 chrs
Text1
TEXT2
49 chrs
Text2
TEXT3
49 chrs
Text3
TEXT4
49 chrs
Text4
TEXT5
49 chrs
Text5
TEXT6
49 chrs
Text6
MULT
Integer
Multiple Sten.
IRRE
Integer
Irregular Sten.
INTER1
Integer
Angioplasty
INTER2
Integer
Stent
INTER3
Integer
TCA
INTER4
Integer
IC Lytics
INTER5
Integer
Artherect.
INTER6
Integer
Rotoblator
INTER7
Integer
TEC
INTER8
Integer
Laser
INTER9
Integer
Other Interv.
AXA5-200.640.07.01.02
Dictionary
System Administration
Communication Manager
Group Name
Group Text
Field Name
Format
Field Text
GRAF1
Integer
Graft Shape
GRAF2
Integer
Graft type
VFLOW
Integer
Flow in stenos
TORTU
Integer
Tortuosity
ANGUL
Integer
Angulation
SPASM
Integer
Spasm
SITCOD
Integer
Site Code
Dictionary
C_HET
Coronary Comments
COMTXT
74 chrs
Comment
C_DE
Dominance Entry
DOMINAN
1 chr
Dominance type <L/M/R>
C_LE
Lesion Entry
VERS
Integer
Version
SEQN
Integer
Sequence number
SITE
4 chrs
Site Index (internal)
STENOS
Integer
Stenosis degree <0-100>
AHACLASS
Integer
AHA class <DIC>
C_AHAC
SHAP
Integer
Short-Long-Etc. <DIC>
C_SHAP
LENMM
Integer
Length in mm.
LEXTENT
Integer
Length <DIC>
C_EXT
FLOW
Integer
Flow degree <DIC>
C_VFLO
FILLING
Integer
Distal filling <DIC>
C_FILL
INTERV1
Integer
Intervention 1
C_INT
INTERV2
Integer
Intervention 2
C_INT
INTERV3
Integer
Intervention 3
C_INT
INTERV4
Integer
Intervention 4
C_INT
INTERV5
Integer
Intervention 5
C_INT
INTERV6
Integer
Intervention 6
C_INT
INTERV7
Integer
Intervention 7
C_INT
INTERV8
Integer
Intervention 8
C_INT
INTERV9
Integer
Intervention 9
C_INT
ECCENTR
Integer
Eccentricity <DIC>
C_ECC
LACCESS
Integer
Tortuosity <DIC>
C_ACC
CURVAT
Integer
Angulation <DIC>
C_CURV
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
299 / 456
System Administration
Group Name
C_CE
C_GE
STUDYPIC
STUDYWF
Group Text
Collateral Entry
Graft Entry
Study pictures
Study waveforms
Field Name
Format
Field Text
Dictionary
BIFURC
1 chr
Bifurcation <Y/N>
A_YN
OSTIAL
1 chr
Ostial <Y/N>
A_YN
CALCIF
1 chr
Calcification <Y/N>
A_YN
THROMBUS
1 chr
Thrombus <Y/N>
A_YN
SPASM
1 chr
Spasm <Y/N>
A_YN
ECTASIA
1 chr
Ectasia <Y/N>
A_YN
ANEURYSM
1 chr
Aneurysm <Y/N>
A_YN
AHACODE
4 chrs
AHA site code <DIC>
C_SIT
GRAFT
Integer
Graft <DIC>
C_GRAF
VERS
Integer
Version
SEQN
Integer
Sequence number
GSITE
4 chrs
Giving site <DIC>
C_SIT
RSITE
4 chrs
Receiving site <DIC>
C_SIT
DEGREE
Integer
Degree collateral flow
<DIC>
C_CFLO
VERS
Integer
Version
SEQN
Integer
Sequence number
GSITE
4 chrs
Giving site <DIC>
C_SIT
RSITE1
4 chrs
1st receiving site <DIC>
C_SIT
RSITE2
4 chrs
2nd receiving site <DIC>
C_SIT
RSITE3
4 chrs
3rd receiving site <DIC>
C_SIT
GSHAPE
Integer
Graft shape <DIC>
C_GRA
GTYPE
Integer
Graft type 1 <DIC>
C_GRAF
FILENAME
250 chrs
Picture filename
DESCRPT
1000 chrs
Picture description
FILENAME
250 chrs
Waveform filename
DESCRPT
1000 chrs
Waveform description
EXPPATH
Export paths
EXPPATH
250 chrs
Export path
HL7DATA
Extra HL7 Data
RECAPP
250 chrs
Rec appl
RECFAC
250 chrs
Rec facility
SENDAPP
250 chrs
Send appl
SENDFAC
250 chrs
Send facility
300 / 456
AXA5-200.640.07.01.02
System Administration
Communication Manager
Group Name
Group Text
Field Name
Format
Field Text
Dictionary
CHPD
CHP Diagnoses
CHPCOD
Integer
CHP Diagnoses
CONGEN
_E_MARKE
Mark Event
CONDNR
Integer
Condition no.
DATETIME
Time 8
Event Date/Time
EVENTLBL
100 chrs
Event Label
EVENTCMT
4000 chrs
Event Comment
EVSEQNO
Integer
Event sequence no.
64 chrs
Case Id
SENDNAME
255 chrs
Sender Name
SENDAPP
255 chrs
Sender Application
TRANSID
32 chrs
TransactionId
AUTOTIME
Time 8
Transaction Time
STATUS
Integer
Status
ITEMID
32 chrs
Item Id
ETYPE
Integer
Entry Type
COMMENT
255 chrs
Comment
SERIALNO
64 chrs
Serial Number
LOTNO
64 chrs
Lot Number
AUTOTIME
Time 8
Time
STATUS
Integer
Status
CODE
Integer
Description
COMMENT
255 chrs
Comment
CTGRNAME
64 chrs
Category
MANNAME
255 chrs
Manufacturer
BRAND
255 chrs
Brand
ITEMID
32 chrs
Item Id
SERIALNO
64 chrs
Serial Number
LOTNO
64 chrs
Lot Number
COST
Float
Cost
CHARGE
Float
Chatge
CHRGCODE
32 chrs
Charge Code
CTLOGNUM
64 chrs
Catalog Number
ACCSEQ
Integer
ACCDevice Sequence
_EN2STU
_ITEMUSG
_VMMUSG
Encounter To Study CASEID
Item Usage
Material Usage
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
_MSTAT
301 / 456
System Administration
Group Name
_CORONRY
_GRAFDES
_GFTARGT
_INTRVEN
_LESION
302 / 456
Group Text
Coronaries
Graft Description
Graft Target
Intervention
Lesion
Field Name
Format
Field Text
ACCCODE
Integer
ACC Code
ETYPE
Integer
Source
TRANSID
32 chrs
TransactionId
DOMINAN
Integer
Dominance
COMMENT
255 chrs
Comment
MODIFYDT
Date 10
Last Modified Date
ASSESSED
Integer
Assessed
GFCOMPLX
Integer
Graft Complexity
GRAFTID
Integer
Graft ID
GRAFTYPE
Integer
Graft Type
COMMENT
255 chrs
Comment
GRAFTSEG
Integer
Graft Segment
IonsofID
255 chrs
Ionosoft ID
TORTOUSE
Integer
Tortuosity
VESLCODE
Integer
Vessel Code
VESLSEG
Integer
Vessel Segment
ASSOCITO
255 chrs
Associated To
INTRVID
255 chrs
Intervention ID
INTRVTYP
Integer
Intervention Type
INTRVDAT
Date 10
Intervention Date
PREVINTR
Integer
Previous Intervention
COMMENT
255 chrs
Comment
INGRAFT
Integer
Ingraft
IONSOFID
255 chrs
Ionosoft ID
LENGTH
Integer
Length
PRETIMI
Integer
Pre TIMI
POSTTIMI
Integer
Post TIMI
RESIDUAL
Integer
Residual Severity
SEVERITY
Integer
Stenosis Severity
ULCERTED
Integer
Ulcerated
VESLCODE
255 chrs
Vessel Code
VESLSEG
Integer
Vessel Segment
AXA5-200.640.07.01.02
Dictionary
_ETYPE
System Administration
Communication Manager
Group Name
_ABNORM
_VESLINF
Group Text
Vessel Abnormalities
Vessel Findings
Field Name
Format
Field Text
LESNTYPE
Integer
Lesion Type
ABRNTYPE
Integer
Aberration Type
COMMENT
255 chrs
Comment
IONSOFID
255 chrs
Ionosoft ID
PRETIMI
Integer
Pre TIMI
POSTTIMI
Integer
Post TIMI
SEVERITY
Integer
Stenosis Severity
VESLCODE
255 chrs
Vessel Code
VESLSEG
Integer
Vessel Segment
CALIBER
Integer
Caliber
COMMENT
255 chrs
Comment
DISTLFLW
Integer
Distal Flow
IONSOFID
255 chrs
Ionosoft ID
ASSESSED
Integer
Assessed
TORTOUSE
Integer
Tortuosity
VESLCODE
Integer
Vessel Code
Dictionary
*
“Date 10” stores information about day (DD), month (MM), and year in four digits (YYYY), the output format will depend on the regional
settings
†
“Time 8” = HH:MM:SS; “Time 5” = HH:MM
‡
Do not send data from the V_SIGNS group, send data from the SP02, NIBP, or RESP group instead.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
303 / 456
System Administration
304 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Configuration Manager
Configuration Manager Overview
The Configuration Manager is a platform for configuration of general system parameters and study types, for mapping HL7 codes for data export, for assigning
bar codes to dictionary entries, and other purposes.
Overview of functions
You use the Configuration Manager for the following tasks:
 Adjusting system parameters
– System parameters tab card
 Defining study types
– Study Types tab card
 HL7 Mapping
– HL7 Mapping tab card
 Maintaining a service logbook
– Service Logbook tab card
 Overview of installed information system components
– Installed Applications tab card
 Editing dictionaries
– Dictionaries tab card
 Terminating syngo Dynamics
– Dictionaries tab card
 Managing anatomical sites
– Sites tab card
 Defining data transfer from a Dräger Infinity patient monitor
– Infinity Vital Signs tab card
 Synchronization of inventory lists
– MMS tab card
Key terms and concepts
For information on the basic concepts of the AXIOM Sensis XP Information System refer to Information System Concepts 17
Starting the Configuration Manager
 Select AXIOM Sensis Information System > Server > Configuration Manag-
er from the Windows Start menu.
– The Login dialog box is displayed.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
305 / 456
System Administration
 Enter your user name and password and click OK.
– User name and password are not case-sensitive.
– Only one instance of the Configuration Manager can be open at a time.
Note
When you start Configuration Manager and all tab cards are dimmed except for
the Dictionaries and the Sites tab cards, this indicates that Documentation Tool
is currently open on a recording or reporting workstation in your cath lab.
Adjusting system parameters
 Display the System Parameters tab card on top.
306 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
System parameters
 ACQ_CATHETERS
– Specifies the group selected by default in the Documentation Tool when
the Documentation Tool is called up from the acquisition system with the
Catheters icon on the Notes subtask card.
– Factory default setting is CA.
 ACQ_DRUGS
– Specifies the group selected by default in the Documentation Tool when
the Documentation Tool is called up from the acquisition system with the
Drugs icon on the Notes subtask card.
– Factory default setting is ME.
 ACQ_TEXTNOTES
– Specifies the group selected by default in the Documentation Tool when
the Documentation Tool is called up from the acquisition system with the
Text Notes icon on the Notes subtask card.
– Factory default setting is DC.
 PATH_AUDIT
– Specifies the path on the information system server PC where the audit log
is stored.
– Factory default setting is C: \ MIS \ bin.
– See Exporting and archiving audit log data 150
 PREREG_EXPIRED
– Specifies the number of days a preregistered patient is held in the information system database.
– If the patient is not examined within the time specified here, the patient will
be deleted from the database.
– Factory default setting is 28 (days)
 PREREG_EXPIRED_OUTPAT
– Specifies the number of days preregistered outpatients are held in the information system database.
– If the patient is not examined within the time specified here, the patient will
be deleted from the database.
– Factory default setting is 7 (days)
 REPORT_AUTOCREATE
– A study report can be created automatically when the study is closed on the
acquisition system (Patient > Close).
– The system will use the template selected for automatic report creation for
this study type (see Defining study types 310).
– Factory default setting is 0 (no auto-creation of study reports).
– Alternative settings are 1 (automatic creation of reports when the study is
closed, approval of a study is not necessary here) and 2 (clinical users are
prompted to confirm approval of a study and auto-creation of study reports
when they close a study on the acquisition system).
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
307 / 456
System Administration
Note
If a report template contains image tags or derived data tags, all available images or derived data of the specified type will be included in the report. The user is
not prompted to confirm. Images or derived data are inserted at the first tag of
the relevant type.
 REPORT_DICOM_HOST
– This parameter is relevant for Cathcor studies.
 REPORT_DICOM_MATCHCRT
– Specifies the criterion or criteria which the AXIOM Sensis XP Information
System will use to assign DICOM images to patients.
– Factory default setting is a patient’s last name and patient ID.
 REPORT_WATERMARK
– Study reports created with Report Generator are marked as draft reports
until the study is approved. After approval the draft watermark is automatically removed from a report.
– Here you can define the watermark text. The factory setting is “Draft” but
you can replace it with another term, for example, “Preliminary”, if you wish.
Note
If you want text printed without watermark in non-approved reports then remove “Draft” from the value box here and leave this box empty.
 STUDY_ID_AUTOMATIC
– With this parameter set you can have the system assign a unique study ID to
each study.
– Factory default is 0 (no automatic assignment of unique study IDs).
– Alternative settings are 1 (the system will create a unique study ID when a
patient is registered in the AXIOM Sensis XP Information System) or 2
(the system will use the placer order number from the HIS/RIS or CIS as
unique study ID (refno) in the AXIOM Sensis XP Information System)
 STUDY_TIMEOUT
– The number of hours a study is held in study state PostCath until the study
state is set to Frozen.
– Factory default setting is 120 (this means that the system expects you to
approve a study within five days).
 STUDY_TYPE_DEFAULT
– This parameter used to be relevant for Cathcor studies.
308 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
 WF_PIC_EXPIRED
– On a Sensis recording system users can import and save images (X-ray
images, mapping system images, waveform images, ablation graphs).
These image files are available for inclusion in a study report created by
Report Generator.
– Physically, these image files are stored in predefined directories in the file
system of your information system server PC.
– Images require a lot of hard disk space. In the system parameter
WF_PIC_EXPIRED you can specify after how many days after a study these
files are deleted to free hard disk space.
– Images are deleted after this time irrespectively of whether the study has
been approved or not.
– The factory setting for this parameter is 90 days.
Note
Be sure to inform your users about this system parameter and the number
of days set here.
Users cannot reset the study state and regenerate reports after this time. Waveform and X-ray images will be missing from the new reports.
Be sure your users understand that this expiry date refers to the number of days
after a study was performed and not to after the study was approved.
Changing system parameters
 Select the system parameter you wish to change from the drop-down list.
 Type a new value or setting in the Value box and click Apply to save these
changes back to the database.
Restoring factory settings
You can either restore the factory settings for a single parameter or for all system
parameters at once.
 Select a system parameter.
– In the Factory setting box you can see the factory default for this parameter.
 Click Restore to reset the selected system parameter to the factory settings.
Or
 Click Restore All Factory Settings to reset all system parameters.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
309 / 456
System Administration
Defining study types
 Display the Study Types tab card on top.
What is a study type?
A study type represents a typical examination that is frequently performed in your
cath lab to clarify a specific diagnostic problem. This involves a typical set of data
and eventual creation of a specific type of report. Therefore a specific selection of
input clusters (groups of database tables) and a specific set of report templates are
associated with a particular study type.
Study type management
On the Study Types tab card of the Configuration Manager you can change the
assignment of input clusters and report templates to existing study types. You can
also create new study types.
Note
You cannot rename or delete study types but you can deactivate them.
 Select a study type and clear the Active box to do so.
Synchronization of
study types
310 / 456
If AXIOM Sensis XP receives information about scheduled studies from a HIS/RIS
or CIS (hospital, radiology, or cardiology information system) preregistration data
usually include information about the type of study to be performed. This requires
that study type definitions are synchronized on the HIS/RIS or CIS and in the AXIOM Sensis XP Information System.
AXA5-200.640.07.01.02
System Administration
Configuration Manager
DICOM Modality Worklist
If AXIOM Sensis XP receives information about scheduled studies from a DICOM
Modality Worklist, study type preselection is defined in the DICOM Worklist field
"RequestedProcedureDescription" (0032,1060).
In the DICOM Worklist field "RequestedProcedureDescription" (0032,1060), study
types must be spelled exactly as on the Study Types tab card of the Configuration
Manager. If a study type has been misspelled users are prompted to select a study
type in the Patient Registration window of the AXIOM Sensis XP recording system the first time they try to register a patient with this misspelled study type in
the patient’s preregistration data. The next time the same problem occurs Sensis
automatically uses the study type that was selected manually the first time.
Once a user has mapped a RequestedProcedureDescription to a study type as described above, you cannot unmap it again.
HL7 ORMO01
If AXIOM Sensis XP receives information about scheduled studies from the central information system as an HL7 ORMO01 message, AXIOM Sensis XP prompts
users to select a study type manually every time the problem occurs. In this case,
a message appears in the status bar of the Patient Registration window of the
AXIOM Sensis XP recording system in this case: “Study information missing. Inconsistencies with RIS possible.”
Correct study type definitions and names immediately on the Study Type tab card
of the Configuration Manager when users report that they encountered this
message during registration of preregistered patients. Or talk to the system administrator of the HIS/RIS or CIS, if the problem needs to be corrected on that end.
Creating a new study type
 Click the New Study Type button to open the New Study Type dialog box.
 Select the Category for which you want to create a new study type:
– Coronary
– Peripheral
– Pediatric
– Valcular
– Electrophysiology
– Pacemaker/ACIDs
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
311 / 456
System Administration
Note
The categories are defined in the dictionary nc_typ. You can add categories
there but you should not change or delete categories.
For details on editing dictionaries refer to Editing dictionaries 78.
 Enter the name of the new study type and click Add.
Changing the input cluster and report template assignment
If you have just created a new study type, no input clusters and report templates
are assigned yet.
In order to change the input cluster and report template assignment of an existing
study type select it in the dropdown list first.
 Click an input cluster in the Available Clusters list and move it to the Associ-
ated Clusters list with the arrow button.
Or
 Use the Shift or Ctrl. key to select and assign several clusters at once.
– Remember that at least one input cluster has to be selected for each study
type.
Note
If you cannot find the input cluster to which you want to assign to your study
type, it may not have been defined yet.
See Editing clusters 106
 Assign Report Templates in the same way.
Note
If you cannot find the report template you wish to assign to your study type, it
may not have been saved back to the database yet.
See Report Composer 155
If you have enabled automatic creation of a report when a study is closed on the
System Parameters tab card then also select a template here.
See Adjusting system parameters 306: parameter REPORT_AUTOCREATE = 1
(or 2).
312 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
 Check the template which all automatically created reports of this study type
will be based on.
– Clinical users will not be prompted to confirm or alter this selection when a
study is closed and a report is created.
Note
Be aware that if you check more than one template here, more than one report
will be auto-created every time a study of this type is closed on an AXIOM Sensis
XP Acquisition System in your cath lab.
Changing the sequence of clusters and templates in
the list
In Documentation Tool, input clusters are presented in exactly the same sequence in which these clusters are listed here. The same is true for Report Templates and the order in which they are presented in the Select Report Template
dialog box of the Report Generator.
You can change the order in which clusters and templates are listed in the Associated Clusters and Associated Report Templates boxes for each study type.
 Select a cluster or template.
 Right-click and drag the cluster or template up or down.
 Release the mouse button to drop the selection onto its new location.
Saving or resetting changes
Whenever you change a study type definition, remember to save it back to the database to make the new or changed study type available for clinical users to select
during patient registration.
 Click Save on the Study Types tab card.
Or
 Use Reset to return to the last saved version of this study type in the database
if you have not yet saved your changes.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
313 / 456
System Administration
HL7 Mapping
 Display the HL7 Mapping tab card on top.
Mapping groups and
fields for HL7 data
transfer
On this card you map information system groups and fields for the purpose of HL7
data transfer.
The tab card is subdivided into two sections:
The upper screen half allows you to map information system group and field designations in outgoing HL7 ORU messages to labels that are easier to interpret for
the receiving system.
Note
Mapping of group and field labels in outgoing HL7 messages is only possible for
message type HL7 ORU (study results and clinical findings) but not for HL7 DFT
messages.
In the lower screen half you can map incoming HL7 data to information system
groups and fields.
314 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
Note
Editing options
The AXIOM Sensis XP Information System can receive HL7 messages of the
types: ADTA01, ADTA03, ADTA04, ADTA05, ADTA08, ADTA11, ADTA23,
ADTA39, ADTA40, ADTA44, ADTA46, ADTA47, ADTA49 and ORMO01
On the HL7 Mapping tab card you can view the list of mapped codes. You can add
new mappings and edit the code designation and meaning of previously mapped
codes.
You can delete a mapping with the Delete key on your keyboard. You cannot
change the group and field selection of a code once you have created it.
HL7 Export mapping
 Click Add Export Mapping to open the Add Export Mapping dialog box.
 Select a Group (database table) and a Field from this table.
 Enter an Identifier and a Text.
– This information will be sent in the outgoing HL7 ORU message together
with the groups and field designation.
 If the selected field is filled with information from a dictionary you can also se-
lect whether you want to send the Dictionary Meaning or the Dictionary
Code.
– In most cases you will select Dictionary Meaning here.
– Dictionary Code would send the information system internal code number
for the dictionary entry.
 Click Add to accept your entries and close the dialog box.
– The new HL7 Export mapping is now listed on the HL7 Mapping tab card.
 Click Apply to accept this mapping or Reset to return to the previous HL7 Map-
ping list.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
315 / 456
System Administration
HL7 mapping example:
identifier and text
This HL7 export mapping sends the following lines in the outgoing HL7 ORU message:
OBX|10|ST|Pressure^Sample Site^^PV^SITE|1|RV||||||F
OBX|11|ST|Pressure^Systolic^^PV^PRESS1|1|81||||||F
HL7 mapping example:
dictionary code
# DIAGNO, Diagnosis, SI, 4, 32, 16, Y
#1, General Indications
885, Unstable Angina
540, Coronary Artery Disease
...
For a dictionary entry which is defined like this, selecting the radio button Dictionary Code would send “885” instead of “Unstable Angina” in the outgoing message.
HL7 Import mapping
 Click Add Import Mapping to open the Add Import Mapping dialog box.
 Select a Group (database table) and a Field from this table.
 Enter an Identifier and a Text.
– This tells the information system that when data with this identifier and text
are sent in an incoming HL7 message the data will be sorted into the group
and field selected above.
316 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
 If the selected field is associated with a dictionary you can also select whether
the information system should interpret the information received as the Dictionary Meaning or the Dictionary Code.
– In either case the system checks whether the dictionary meaning text or dictionary code number that is sent exists in the dictionary assigned to the
receiving field. If not, the message is rejected.
– Dictionary Code means that the information system retrieves the actual
value for this field from its own dictionary, which is associated to this field.
 Click Add to accept your entries and close the dialog box.
– The new HL7 Import mapping is now listed on the HL7 Mapping tab card.
 Click Apply to accept this mapping or Reset to return to the previous HL7 Map-
ping list.
HL7 mapping example:
dictionary code
#PN, Personnel, 3
N, PNNAME , SI, 4, Name <DIC>
...
, PNNAME
For a group and field which are defined like this an associated dictionary exists in
the information system database:
# PNNAME, Personnel, SI, 4, 30, 16, Y
#1, Physicians
1, Brown, Allan
2, Smith, Beatrice
3, Anderson, Charlie
4, Peterson, Dave
...
If the corresponding HL7 import mapping specifies that Dictionary Code is sent in
the incoming HL7 message rather than Dictionary Meaning, then the information system expects “1”, “2”, “3”, or “4” as values for PN, PNNAME in the inbound
HL7 message. The information system will retrieve the corresponding names
(“Brown, Allan”, “Smith, Beatrice”, “Anderson, Charlie”, or “Peterson, Dave”) from
its own dictionary.
Changing HL7 Import and HL7 Export mappings
 Double-click on an HL7 Export or HL7 Import definition line to activate editing
mode.
 Make your changes.
 Click elsewhere to close editing mode and accept your changes.
 Click Apply to confirm.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
317 / 456
System Administration
Mapping elements PV1.2, PID.8, and FT1.6
You use the HL7 Mapping tab card of Configuration Manager to map any HL7
elements except elements PV1.2, PID.8, and FT1.6.
To import and export mapping of these HL7 elements you use a different configuration method, which is direct editing of an xml file on the AXIOM Sensis XP Information System server.
 Open the Windows Explorer on the AXIOM Sensis XP Information System serv-
er.
 Select the folder C:\mis\config.
 Open HL7.config with Notepad.
 Scroll down to the end of the file.
– Here you will find the mapping tables for the SensisCodes (dictionary codes)
and HL7 values.
 Edit these mappings, if necessary.
– For example, replace the labels for patient sex with the labels the system
you communicate with sends. This would would most likely be “W” instead
of “F” in a German system installation.
 Save the file and close Notepad.
318 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
Maintaining a service logbook
 Display the Service Logbook tab card on top.
This tab card is intended for Service personnel only.
Service technicians will note major changes to the system configuration here by
clicking New Note and entering their names and the changes they just made.
Note
AXIOM Sensis XP (VC11)
Once entered these notes can neither be changed nor deleted.
AXA5-200.640.07.01.02
319 / 456
System Administration
Overview of installed information system
components
 Display the Installed Applications tab card on top.
The Installed Applications gives you an overview of all AXIOM Sensis XP Information System components currently in use. Here you will find information on
the installed version of each component as well as the date and time this component was last used.
 Click Refresh List to make sure the list is up to date.
320 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
Editing dictionaries
 Display the Dictionaries tab card on top.
Dictionary editing options in Configuration
Manager
You use the Dictionaries tab card of Configuration Manager to edit dictionaries,
that is to add or modify items, to rearrange or group items in a dictionary, and to
assign bar codes to items. For any other dictionary configuration tasks refer to Editing dictionaries 78 in DB Manager.
Editing dictionaries and grouping items
 Select a dictionary from the list.
 If you do not find the dictionary that you want to edit in the Dictionary drop-
down list, click Add.
 Select a dictionary from the Available dictionaries list.
 Also select a group that refers to this dictionary.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
321 / 456
System Administration
Adding a new dictionary item
 Click the New item button in order to add a dictionary entry.
 Enter an item designation (Meaning).
 Also change the item code number suggested by the system, if you wish.
– Code numbers can be used for quick and easy data entry in the Documentation Tool.
– See Editing dictionaries 78 for a description of dictionary types and
dictionary definitions.
 Scan the bar code.
 Click Apply.
Editing existing dictionary entries
 Select the entry.
 Change its information on the right-hand side of the tab card.
 Click Apply.
 Click Reset if you have made changes but want to undo them.
Rearranging dictionary items
 Click a dictionary item to select it.
 Now click the dictionary item again, however, with the right mouse button.
 Hold the mouse button down and drag the dictionary item up or down.
 Release the mouse button to drop the item at the new location.
Grouping dictionary items
 Select the first item in a dictionary that is to go to the new group.
 Click New Hierarchy.
322 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
 Type the name of the new hierarchy level in the Meaning box.
– A dictionary can have up to three hierarchy levels.
Note
If you select a hierarchy level rather than a dictionary item before clicking New
Hierarchy, a new structure element of the same level as the selected one is added. The system also requires you to create a new dictionary item for this hierarchy element.
Removing dictionary items
You cannot delete dictionary items, even if you just created them. We recommend that you move dictionary items that you no longer need to the end of the
list. You might also sort them under a hierarchy that you label No longer in use.
Saving changes
 Always remember to save your changes (Save Dictionary).
Assigning dictionary entries to bar codes
Your system supports bar code readers for data entry in the Documentation Tool.
This means that instead of selecting a dictionary item for a table and field in the
software, clinical users can scan the bar code of, for example, a consumable item
such as a catheter.
Two different bar code reader models are supported:
 Intermec ScanPlus 1800 (wired bar code reader)
 Datalogic Powerscan (wireless bar code reader)
Bar code reader configuration
Installation and configuration of a bar code reader involves these procedures:
 Connecting the bar code reader to an AXIOM Sensis XP Information System
client PC or to a recording system which acts as an information system master
or client via serial connector.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
323 / 456
System Administration
 Configuring the bar code reader on the Bar Code Reader tab card of the Com-
puter Configuration platform of this PC.
– See Installing a bar code reader 350
 Scanning bar codes and assigning them to dictionary entries for various data-
base tables. This is done on the Dictionaries tab card of the Configuration
Manager.
Assigning bar codes:
procedure overview
Assignment of bar codes to dictionary entries involves a two-step procedure:
 Enabling dictionaries
– You can only assign bar codes to entries of dictionaries that have been
enabled for bar code scanning.
– If a dictionary is used in several groups (database tables), you need to select
for which database table you want to enable bar code scanning.
Note
Bar codes do not apply to all groups a dictionary is used in but only to one group.
This is the group for which bar code scanning was enabled for this dictionary.
Use the Change Group button if you want to enable the selected dictionary,
however, in a different group.
– The Add and Remove buttons next to the drop-down list allow you to
enable more dictionaries or to remove dictionaries from this list.
Note
Remember that if you remove dictionaries from the list of dictionaries enabled
for bar code usage you will lose all scanned bar codes. If you re-enable the dictionary again later on, you will have to scan all its bar codes again.
 Scanning bar codes
– Once a dictionary has been enabled for bar codes, you can select it in the list
and scan the bar codes of its items one after another.
Enabling dictionaries
 Click Add to open the Add Dictionary dialog box.
 Select a dictionary from the Available dictionaries list.
 Also select the database table in which bar code scanning is to be enabled for
this dictionary.
324 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
 Click Add.
– The dictionary is now available in the list of enabled dictionaries.
Scanning bar codes
 Select the dictionary for which you want to scan bar codes in the Dictionary
drop-down list.
 Select the dictionary entry for which you want to scan and assign a bar code.
 Scan the bar code.
 Click Apply to accept the scan and assign it to the selected item.
 Continue in the same way with other items in the dictionary.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
325 / 456
System Administration
 Click Save Dictionary to save the changes back to the database.
Note
Remember always to save your changes explicitly with Save Dictionary. If you
only scan and click Apply, your changes are not transferred to the database.
Also remember to click Save dictionary after you have deleted a bar code assignment (that is, selected an item and clicked the Delete Bar Code button).
Exporting or importing bar codes for a dictionary
For service purposes dictionaries can be exported or imported from a file created
on another AXIOM Sensis XP Information System installation.
Exporting bar codes for a dictionary
 Select a dictionary that contains bar code assignments from the Dictionary list.
 Click the Export Bar Codes button to open the Save As dialog box.
 Select a destination in your file system or on an external medium (for example,
a USB stick).
 Accept the suggested name, or change it.
– Do not change the file format.
 Click OK to confirm.
Importing bar codes for a dictionary
 Click this button and select the definition file in the Open dialog box.
– The system will import bar codes for all items for which it finds exact
matches in the imported file and the currently selected dictionary.
– The system will not, however, overwrite bar code definitions that already
exist in the currently selected dictionary.
326 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
Terminating syngo Dynamics
 Display the Dictionaries tab card on top.
syngo Dynamics 9.5
and higher
If your AXIOM Sensis XP Information System communicates with a syngo Dynamics system, all syngo Dynamics clients need to be logged off from SIS before
you can call up DB Manager and start tailoring the database.
For syngo Dynamics systems version 9.5 and higher, Sensis offers a button that
helps you with logging off syngo Dynamics clients.
 Click Terminate Syngo Dynamics in the lower right-hand corner of the Dictio-
naries tab card of Configuration Manager.
– A message is sent to all syngo Dynamics users informing them to save and
close their sessions. After 5 minutes syngo Dynamics sessions will be terminated automatically.
– Note that the Terminate Syngo Dynamics button will not appear
depressed while syngo Dynamics users are logged off. Nor will you as Sensis
administrator be informed in any other way that termination of syngo
Dynamics sessions is in progress.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
327 / 456
System Administration
 Start DB Manager within the next 5 minutes.
– See also Starting DB Manager 76.
– If you fail to open DB Manager within the next five minutes, syngo Dynamics clients will attempt to log on again.
syngo Dynamics versions earlier than 9.5
The Terminate Syngo Dynamics button only affects syngo Dynamics 9.5 and
higher. For earlier syngo Dynamics versions, simply tell users to log off and wait
until they all have done so.
Managing anatomical sites
 Display the Sites tab card on top.
Note
In order to be able to edit the sites list you need to be a member of the Administrator role.
See Granting access to program functions 139
Anatomical site labels
for pressure signals
328 / 456
In the AXIOM Sensis XP Acquisition System pressure waveforms are labeled
with an abbreviation of the anatomical site where the catheter currently rests. The
site label of a pressure waveform also defines which algorithms the system uses
for various calculations in the AXIOM Sensis XP hemodynamics application.
AXA5-200.640.07.01.02
System Administration
Configuration Manager
During an examination, clinical users assign site labels to pressure waveforms
from a preconfigured anatomical sites list. On the Sites tab card of the Configuration Manager the system administrator can edit this list and add new sites, or
groups of sites. The location of a new site with respect to the anatomical area, region and subregion of this factory-preconfigured list defines which calculation algorithms will be active at the new site.
Defining a new site
 Select the ALL SITES view on the Sites tab card whenever you want to edit the
anatomical sites list.
 Open the anatomical area, region, and subregion to which you want to add a
new anatomical site.
Note
Remember that the correct location of the new site with respect to the factorypredefined anatomical areas, regions, and subregions is crucial. It will define the
algorithms for pressure calculations at this new site and for how pressure readings from this site will be used in the calculation of derived data.
The location of the new site within the list and therefore the association of the
new site to an anatomical area or region also defines display characteristics for
the pressure waveform. Four different waveform characteristics (default display
settings) have been defined in the system for arterial, venous, atrial, and ventricular sites. These display settings can, of course, be changed in real time
(Waveform Properties dialog box) or in a setup.
 Click Add Site.
– A new anatomical site will be added to this area, region, or subregion.
 Type a Site label and Description text in the Site Properties box to the right of
the sites list.
– The site label will show up as a waveform label in the hemodynamics or
electrophysiology application.
– The description text will be shown in the site selection dialog box of the
hemodynamics or electrophysiology application as a short description of
this site.
 Select the Category under which the new site will be listed in the site selection
dialog.
– An anatomical site can be listed in more than one category.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
329 / 456
System Administration
 Click Save to save your new site in the information system database.
– The new sites list is available in all studies that you start or continue from
now on.
– Site list changes do not affect studies that are in progress.
Adding new regions and subregions
You can not only add individual sites but also create groups of sites by creating
new regions or subregions. New regions and subregions and their site lists inherits
their pressure calculation algorithms from the anatomical area (or factory-predefined region) in which they are listed.
Note
No new regions can be created in the anatomical area Great Vessels and Heart
Cavities, only subregions and site labels can be added here.
 Select the ALL SITES view.
 Select the anatomical area in which you want to create a new region.
 Click Add Site and enter a label and description
 Save your changes to create a new region site.
 Next select the newly created region site.
 Click Add Site again and enter a label and description.
 Save your changes to create a new subregion site.
 Add more (subregion) sites, if you wish.
Editing or rearranging sites
 Select the ALL SITES view.
 Select the site you wish to edit in the tree view.
 Change the site label, description text and category association, if necessary.
– Renaming a site changes only its label. It will not change the pressure calculation algorithms assigned to this site.
330 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
Note
If you uncheck all categories this will hide an anatomical site from the site selection dialog box in the hemodynamics or electrophysiology application.
You cannot delete sites from the list this way, only hide them.
 Right-click a site label, keep the mouse button pressed, and drag the site label
up or down to move it within the same anatomical area or region.
Note
Sites must be arranged along the blood flow, and rearranging sites in a different
order can result in serious system problems (examinations can no longer be
started on the recording systems in your cath lab).
You will therefore only rearrange sites directly after defining a new site in order
to place it in its correct position. Note also that you cannot move a site from one
area, region, or subregion to another.
 Do not forget to Save your changes.
Checking the sites configuration
After adding new sites or editing or rearranging sites you can check how these
sites will be arranged in the site selection dialog box for your clinical users.
 Select the categories from the View box one after another and check the ar-
rangement of sites under these categories.
– Remember that you cannot edit these lists in this view.
– In order to edit the arrangement of sites, return to the --ALL SITES-- view.
Region
1XXX
Y
13
Peripheral
Description
Coronary
Name
Normal
Code
Congenital
List of factory-predefined anatomical sites
PERIPHERAL VEINS
VEN
Vein
Waveform characteristic
Comments
Venous
Y
Y
Y
BRACHIO-CEPHALIC
Y
Y
VEN Inno
Vein Innominate
Y
Y
Y
52
VEN R.Inno
Vein Right Innominate
Y
Y
Y
VEN R.In*
53
VEN L.Inno
Vein Left Innominate
Y
Y
Y
VEN L.In*
VEN Jugu
Vein Jugular
Y
Y
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
331 / 456
System Administration
Vein Right Internal Jugular
Y
Y
VEN R.Ju*
55
VEN L.InJu
Vein Left Internal Jugular
Y
Y
VEN L.Ju*
VEN R.ExJu
Vein Right External Jugular
VEN L.ExJu
Vein Left External Jugular
VEN R.AnJu
Vein Right Anterior Jugular
VEN L.AnJu
Vein Left Anterior Jugular
VEN Subc
Vein Subclavian
Y
Y
56
VEN R.Su
Vein Right Subclavian
Y
Y
57
VEN L.Su
Vein Left Subclavian
Y
Y
VEN Axil
Vein Axillary
VEN R.Axil
Vein Right Axillary
VEN L.Axil
Vein Left Axillary
VEN Brac
Vein Brachial
VEN R.Brac
Vein Right Brachial
VEN L.Brac
Vein Left Brachial
Region
Y
Y
Peripheral
VEN R.InJu
Coronary
54
Congenital
Description
Normal
Name
Y
Waveform characteristic
Comments
Code
ABDOMINAL
Y
59
Y
Y
Y
58
VEN Hep
Vein Hephatic
Y
Y
VEN InHe
Vein Intermediate Hephatic
Y
Y
VEN MiHe
Vein Middle Hephatic
Y
Y
VEN Rena
Vein Renal
VEN R.Rena
Vein Right Renal
VEN L.Rena
Vein Left Renal
VEN Azyg
Vein Azygos
VEN H.Az
Vein Hemiazygos
VEN H.AA
Vein Hemiazygos Accessoria
VEN Umb
Vein Umbilical
Y
Y
PELVIS AND LEG
Y
332 / 456
VEN Ilia
Vein Iliac
VEN R.CIli
Vein Right Common Iliac
VEN L.CIli
Vein Left Common Iliac
VEN R.ExIl
Vein Right External Iliac
VEN L.ExIl
Vein Left External Iliac
VEN R.InIl
Vein Right Internal Iliac
VEN L.InIl
Vein Left Internal Iliac
AXA5-200.640.07.01.02
System Administration
Congenital
Y
VEN Femo
Vein Femoral
Y
Y
VEN R.Femo
Vein Right Femoral
Y
Y
VEN L.Femo
Vein Left Femoral
Y
Y
VEN R.DeFe
Vein Right Deep Femoral
VEN L.DeFe
Vein Left Deep Femoral
VEN FePo
Vein Femoropopliteal
2XXX
Y
44
Y
CARDIAC VEINS
VEN Cor
Vein Coronary Sinus
CVE
Cardiac Vein
CVE An
Cardiac Vein Anterior
CVE Gr
Cardiac Vein Great
CVE Mi
Cardiac Vein Middle
CVE Sm
Cardiac Vein Small
CVE Ss
Cardiac Vein Smallest
3XXX
Y
Y
Y
Peripheral
Description
Coronary
Name
Region
Code
Normal
Configuration Manager
Waveform characteristic
Comments
Venous
Y
Y
Y
GREAT VESSELS AND HEART CAVITIES
1
SVC
Superior Vena Cava
Y
Y
12
SVC High
Superior Vena Cava High
Y
Y
104
SVC Low
Superior Vena Cava Low
Y
Y
15
SVC L.Hi
Superior Vena Cava Left High
Y
60
SVC L.Lo
Superior Vena Cava Left Low
Y
61
SVC Anom
Superior Vena Cava Anomalous
Y
2
IVC
Inferior Vena Cava
Y
Y
5
IVC Low
Inferior Vena Cava Low
Y
Y
62
IVC High
Inferior Vena Cava High
Y
Y
25
IVC Left
Inferior Vena Cava Left
Y
63
IVC Anom
Inferior Vena Cava Anomalous
Y
14
IVC Azyg
Inferior Vena Cava Azygos
Y
64
IVC H.Az
Inferior Vena Cava Hemi Azygos
Y
3
RA
Right Atrium
Y
Y
51
RA Infl
Right Atrium Inflow (=Mixed
Venous)
Y
Y
4
RA High
Right Atrium High
Y
Y
6
RA Low
Right Atrium Low
Y
Y
AXIOM Sensis XP (VC11)
Venous
Venous
Atrial
AXA5-200.640.07.01.02
RA Inflow (=Mixed Venous)*
333 / 456
System Administration
Right Atrium Pulmonary Return
Y
65
RA Comm
Common (Single) Atrium of RAtype
Y
7
RV
Right Ventricle
Y
Y
66
RV Infl
Right Ventricle Inflow
Y
Y
8
RV Oufl
Right Ventricle Outflow
Y
Y
67
RV Rudi
Right Ventricle Rudimentary
Y
68
RV Comm
Common (Single) Ventricle of RVtype
Y
RV - Common (Single) Ventricle of RVtype*
69
RV Sys
Systemic Ventricle of RV-type
Y
RV - Systemic Ventricle of RV-type*
Y
9
PA
Pulmonary Artery Main
70
PA Prox
Pulmonary Artery Main Proximal
Y
Main Pulmonary Artery Main Proximal*
71
PA Dist
Pulmonary Artery Main Distal
Y
Main Pulmonary Artery Main Distal*
10
PA R.Pr
Pulmonary Artery Right Proximal
Y
Y
Main Pulmonary Artery Right Proximal*
11
PA L.Pr
Pulmonary Artery Left Proximal
Y
Y
Main Pulmonary Artery Left Proximal*
72
PA R.Di
Pulmonary Artery Right Distal
Y
Main Pulmonary Artery Right Distal*
73
PA L.Di
Pulmonary Artery Left Distal
Y
Main Pulmonary Artery Left Distal*
Y
16
PCW
Pulmonary Capillary Wedge
Y
Y
18
PCW Left
Pulmonary Capillary Wedge Left
Y
Y
17
PCW Rght
Pulmonary Capillary Wedge Right
Y
Y
Y
38
PVW
Pulmonary Venous Wedge
Y
74
PVW L.Up
Pulmonary Venous Wedge Left
Upper
Y
75
PVW R.Up
Pulmonary Venous Wedge Right
Upper
Y
40
PVW L.Lo
Pulmonary Venous Wedge Left
Lower
Y
39
PVW R.Lo
Pulmonary Venous Wedge Right
Lower
Y
Y
41
PV
Pulmonary Vein
Y
Y
35
PV L.Up
Pulmonary Vein Left Upper
Y
Y
36
PV R.Up
Pulmonary Vein Right Upper
Y
Y
43
PV L.Lo
Pulmonary Vein Left Lower
Y
42
PV R.Lo
Pulmonary Vein Right Lower
Y
46
PV Anom
Pulmonary Vein Anomalous
Y
334 / 456
Y
Y
Peripheral
RA Pulm
Coronary
33
Congenital
Description
Normal
Name
Region
Y
Waveform characteristic
Comments
Code
RA - Common (Single) Atrium of RAtype*
Ventricular
Arterial
Pulmonary Main Artery*
Atrial
Arterial
Venous
AXA5-200.640.07.01.02
System Administration
Configuration Manager
Pulmonary Vein Common(Third
Atrium)
19
LA
Left Atrium
Y
Y
76
LA High
Left Atrium High
Y
Y
77
LA Low
Left Atrium Low
Y
Y
34
LA Sys
Left Atrium Systemic Return
Y
45
LA Comm
Common (Single) Atrium of LAtype
Y
Y
20
LV
Left Ventricle
Y
Y
78
LV Infl
Left Ventricle Inflow
Y
Y
21
LV Oufl
Left Ventricle Outflow
Y
Y
79
LV Rudi
Left Ventricle Rudimentary
Y
47
LV Comm
Common (Single) Ventricle of LVtype
Y
LV - Common (Single) Ventricle of LVtype*
80
LV Pulm
Pulmonary Ventricle of LV-type
Y
LV - Pulmonary Ventricle of LV-type*
Y
22
AO
Aorta
Y
Y
Y
Y
24
AO Asc
Aorta Ascending
Y
Y
Y
Y
81
AO Arch
Aorta Arch
Y
Y
Y
Y
23
AO Desc
Aorta Descending
Y
Y
Y
Y
82
AO R.Ar
Aorta Right Arch
Y
83
AO R.Ds
Aorta Right Descending
Y
Y
49
TRU
PA-AO Trunc
Y
84
TRU Comm
PA-AO Trunc Communis
Y
85
TRU Coll
PA-AO Trunc Aorto-Pulmonary
Collateral
Y
86
TRU APW
PA-AO Trunc Aorto-Pulmonary
Window
Y
Y
48
DUC
Ductus
Y
87
DUC Left
Ductus Left
Y
88
DUC Rght
Ductus Right
Y
89
DUC Othr
Ductus Other
Y
Y
50
CON
Conduit
Y
90
CON L.Pr
Conduit Left Proximal
Y
91
CON R.Pr
Conduit Right Proximal
Y
92
CON L.Di
Conduit Left Distal
Y
AXIOM Sensis XP (VC11)
Peripheral
PV Comm
Coronary
32
Congenital
Description
Normal
Name
Region
Y
Waveform characteristic
Comments
Code
Y
Atrial
LA - Common (Single) Atrium of LAtype*
Ventricular
Arterial
Arterial
Arterial
DUCTUS ARTERIOSUS
Arterial
CONDUITS OF ARTERIAL TYPE
AXA5-200.640.07.01.02
335 / 456
93
CON R.Di
Conduit Right Distal
Y
94
CON Othr
Conduit Other
Y
Region
4XXX
Y
CORONARY ARTERIES
IM
Internal Mammary Artery
Y
105
LIM
Left Internal Mammary Artery
Y
106
RIM
Right Internal Mammary Artery
Y
152
RCA
Right Coronary Artery
Y
107
RCA P
Proximal Right Coronary Artery
Y
108
RCA M
Mid Right Coronary Artery
Y
109
RCA D
DistalRight Coronary Artery
Y
Y
110
CA
Conus Artery
Y
Y
111
SN
Sinus Node Artery
Y
153
RSN
Right Sinus Node Artery
Y
154
LSN
Left Sinus Node Artery
Y
155
AM
Acute Marginal Branch
Y
112
AM 1
First Acute Marginal Branch
Y
113
AM 2
Second Acute Marginal Branch
Y
114
AM 3
Third Acute Marginal Branch
Y
115
PDA
Posterior Descending Artery
Y
156
RPDA
Right Posterior Descending Artery
Y
157
LPDA
Left Posterior Descending Artery
Y
158
ANA
Atrio-Ventricular Node Artery
Y
159
RANA
Right Atrio-Ventricular Node Artery
Y
160
LANA
Left Atrio-Ventricular Node Artery
Y
161
PL
Postero-Lateral Branch
Y
118
RPL 1
Right First Postero-Lateral Branch
Y
119
RPL 2
Right Second Postero-Lateral
Branch
Y
120
RPL 3
Right Third Postero-Lateral Branch
Y
162
LPL 1
Left First Postero-Lateral Branch
Y
163
LPL 2
Left Second Postero-Lateral
Branch
Y
164
LPL 3
Left Third Postero-Lateral Branch
Y
121
LMN
Left Main Artery
Y
Y
Y
Y
Y
Y
336 / 456
Waveform characteristic
Comments
Arterial
151
Y
Peripheral
Description
Congenital
Name
Normal
Code
Coronary
System Administration
AXA5-200.640.07.01.02
System Administration
165
LAD
Left Anterior Descending Artery
Y
122
LAD P
Proximal Left Anterior Descending
Artery
Y
123
LAD M
Mid Left Anterior Descending Artery
Y
124
LAD D
Distal Left Anterior Descending
Artery
Y
166
DIA
Diagonal Branch
Y
125
DIA 1
First Diagonal Branch
Y
167
DIA L1
Lateral First Diagonal Branch
Y
126
DIA 2
Second Diagonal Branch
Y
168
DIA L2
Lateral Second Diagonal Branch
Y
169
DIA 3
Third Diagonal Branch
Y
170
DIA L3
Lateral Third Diagonal Branch
Y
171
SEPT
Septal Branch
Y
127
SEPT 1
First Septal Branch
Y
172
SEPT 2
Second Septal Branch
Y
173
SEPT 3
Third Septal Branch
Y
CX
Circumflex
Y
174
LCX
Left Circumflex Artery
Y
128
LCX P
Proximal Left Circumflex Artery
Y
175
LCX M
Mid Left Circumflex Artery
Y
129
LCX D
Distal Left Circumflex Artery
Y
176
OM
Obtuse Marginal Branch
Y
131
OM 1
First Obtuse Marginal
Y
177
OM L1
Lateral First Obtuse Marginal
Y
132
OM 2
Second Obtuse Marginal
Y
178
OM L2
Lateral Second Obtuse Marginal
Y
133
OM 3
Third Obtuse Marginal
Y
179
OM L3
Lateral Third Obtuse Marginal
Y
Y
116
PDSP
Posterior Descending Septal Perforators Segment
Y
Y
134
RAMI
Ramus Intermedius
Y
180
RAMI L
Lateral Ramus Intermedius
Y
Region
Y
Y
Y
Y
Y
Y
AXIOM Sensis XP (VC11)
Coronary
Description
Congenital
Name
Normal
Code
Peripheral
Configuration Manager
Waveform characteristic
AXA5-200.640.07.01.02
Comments
337 / 456
Region
135150
Old user defined coronary sites
5XXX
CORONARY GRAFTS
Saphenous Vein Graft
Y
Y
LMN SVG
Left Main Artery Graft
Y
Y
LAD SVG
Left Anterior Descending Artery
Graft
Y
LAD P SVG
Proximal Left Anterior Descending
Artery Graft
Y
LAD M SVG
Mid Left Anterior Descending Artery Graft
Y
LAD D SVG
Distal Left Anterior Descending
Artery Graft
Y
DIA SVG
Diagonal Branch Graft
Y
DIA 1 SVG
First Diagonal Branch Graft
Y
DIA 2 SVG
Second Diagonal Branch Graft
Y
DIA 3 SVG
Third Diagonal Branch Graft
Y
Y
CX SVG
Circumflex Artery Graft
Y
Y
LCX SVG
Left Circumflex Artery Graft
Y
LCX P SVG
Proximal Left Circumflex Artery
Graft
Y
LCX M SVG
Mid Left Circumflex Artery Graft
Y
LCX D SVG
Distal Left Circumflex Artery Graft
Y
Y
ACX SVG
Atrial Circumflex Artery Graft
Y
Y
OM SVG
Obtuse Marginal Graft
Y
OM 1 SVG
First Obtuse Marginal Graft
Y
OM 2 SVG
Second Obtuse Marginal 2 Graft
Y
RCA SVG
Right Coronary Artery Graft
Y
RCA P SVG
Proximal Right Coronary Artery
Graft
Y
RCA M SVG
Mid Right Coronary Artery Graft
Y
RCA D SVG
Distal Right Coronary Artery Graft
Y
PDA SVG
Posterior Descending Artery Graft
Y
RPDA SVG
Right Posterior Descending Artery
Graft
Y
LPDA SVG
Left Posterior Descending Artery
Graft
Y
Y
338 / 456
Comments
Arterial
SVG
Y
Waveform characteristic
From previous software versions
Y
Y
Peripheral
Description
Coronary
Name
Normal
Code
Congenital
System Administration
AXA5-200.640.07.01.02
System Administration
Y
RAMI SVG
Ramus Intermedius Artery Graft
Y
Y
IM SVG
Internal Mammary Artery Graft
Y
RIMA SVG
Right Internal Mammary Artery
Graft
Y
LIMA SVG
Left Internal Mammary Artery
Graft
Y
Region
6XXX
Y
26
Coronary
Description
Congenital
Name
Normal
Code
Peripheral
Configuration Manager
PERIPHERAL ARTERIES
ART
Waveform characteristic
Comments
Arterial
Artery
Y
Y
Y
BRACHIO-CEPHALIC
Y
ART Inno
Artery Innominate
Y
Y
97
ART R.Inno
Artery Right Innominate
Y
Y
ART R.In*
98
ART L.Inno
Artery Left Innominate
Y
Y
ART L.In*
ART Caro
Artery Common Carotid
Y
Y
Artery Carotid*
101
ART R.Ca
Artery Right Carotid
Y
Y
102
ART L.Ca
Artery Left Carotid
Y
Y
ART R.InCa
Artery Right Internal Carotid
Y
ART L.InCa
Artery Left Internal Carotid
Y
ART R.ExCa
Artery Right External Carotid
Y
ART L.ExCa
Artery Left External Carotid
Y
ART Cere
Artery Cerebral
ART R.IMCe
Artery Right Internal Middle Cerebral + branches
ART L.IMCe
Artery Left Internal Middle Cerebral + branches
ART R.IACe
Artery Right Internal Anterior Cerebral + branches
ART L.IACe
Artery Left Internal Anterior Cerebral + branches
ART Occi
Artery Occipital
ART R.ExOc
Artery Right External Occipital
ART L.ExOc
Artery Left External Occipital
ART Maxi
Artery Maxillary
ART R.ExMa
Artery Right External Maxillary +
branches
ART L.ExMa
Artery Left External Maxillary +
branches
Y
Y
Y
Y
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
339 / 456
System Administration
ART L.InMa
Artery Left Internal Maxillary +
branches
ART Phar
Artery Pharyngeal
ART R.EAPh
Artery Right External Ascending
Pharyngeal
ART L.IAPh
Artery Left Internal Ascending
Pharyngeal
ART Faci
Artery Facial
ART R.ExFa
Artery Right External Facial
ART L.ExFa
Artery Left External Facial
ART Subc
Artery Subclavian
Y
Y
99
ART R.Sc
Artery Right Subclavian
Y
Y
Now placed under a region
100
ART L.Sc
Artery Left Subclavian
Y
Y
Now placed under a region
ART Axil
Artery Axillary
Y
ART R.Axil
Artery Right Axillary
Y
ART L.Axil
Artery Left Axillary
Y
ART Brac
Artery Brachial
Y
Y
Y
27
ART R.Br
Artery Right Brachial
Y
Y
Y
95
ART L.Br
Artery Left Brachial
Y
Y
Y
ART Ulna
Artery Ulnar
Y
ART R.Ulna
Artery Right Ulnar
Y
ART L.Ulna
Artery Left Ulnar
Y
ART Radi
Artery Radial
Y
ART R. Radi
Artery Right Radial
Y
ART L.Radi
Artery Left Radial
Y
ART Vert
Artery Vertebral
ART R.Vert
Artery Right Vertebral
ART L.Vert
Artery Left Vertebral
ART TCeT
Artery Thyreo-cervical Trunk
ART R.TCeT
Artery Right Thyreo-cervical Trunk
ART L.TCeT
Artery Left Thyreo-cervical Trunk
ART Cerv
Artery Cervical
ART R.ACer
Artery Right Ascending Cervical
Region
Y
Y
Y
Y
Y
Y
Y
Y
Y
340 / 456
Peripheral
Artery Right Internal Maxillary +
branches
Coronary
ART R.InMa
Congenital
Description
Y
Waveform characteristic
Comments
Name
Normal
Code
AXA5-200.640.07.01.02
System Administration
ART L.ACer
Artery Left Ascending Cervical
Region
Peripheral
Description
Coronary
Name
Normal
Code
Congenital
Configuration Manager
Waveform characteristic
Comments
ABDOMINAL
Y
ART Celi
Artery Celiac
ART CeTr
Artery Celiac Trunk
ART CeAx
Artery Celiac Axis
Y
ART Sple
Artery Splenic
Y
ART Hepa
Artery Hepatic
Y
ART GaDu
Artery Gastro-duodenal
Y
ART GaEp
Artery Gastro-epiploic
Y
ART Mese
Artery Mesenteric
ART MSup
Artery Superior Mesenteric
Branches
ART MInf
Artery Inferior Mesenteric Branches
ART Rena
Artery Renal
Y
ART R.Rena
Artery Right Renal
Y
ART L.Rena
Artery Left Renal
Y
ART R.ReSc
Artery Right Renal Secondary
Branch
Y
ART L.ReSc
Artery Left Renal Secondary
Branch
Y
ART ICos
Artery Intercostal
ART R.ICos
Artery Right Intercostal
ART L.Icos
Artery Left Intercostal
ART Lumb
Artery Lumbar
ART R.Lumb
Artery Right Lumbar
ART L.Lumb
Artery Left Lumbar
ART Umb
Artery Umbilical
Y
Y
Y
Y
103
Y
PELVIS AND LEG
Y
ART Ilia
Artery Iliac
Y
ART R.Ili
Artery Right Common Iliac
Y
ART L.Ili
Artery Left Common Iliac
Y
ART CL.CIl
Artery Contralateral Common Iliac
Y
ART R.ExIl
Artery Right External Iliac
Y
ART L.ExIl
Artery Left External Iliac
Y
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
341 / 456
System Administration
Artery Contralateral External Iliac
Y
ART R.InIl
Artery Right Internal Iliac
Y
ART L.InIl
Artery Left Internal Iliac
Y
ART CL.InI
Artery Contralateral Internal Iliac
Y
ART Femo
Artery Femoral
Y
Y
Y
28
ART R.Fe
Artery Right Femoral
Y
Y
Y
96
ART L.Fe
Artery Left Femoral
Y
Y
Y
ART R.CFem
Artery Right Common Femoral
Y
ART L.CFem
Artery Left Common Femoral
Y
ART CL.CFe
Artery Contralateral Common
Femoral
Y
ART Popl
Artery Popliteal
ART R.Popl
Artery Right Popliteal
ART L.Popl
Artery Left Popliteal
ART CL.Pop
Artery Contralateral Popliteal
ART TPTr
Artery Tibio-peroneal Trunk
ART R.TPTr
Artery Right Tibio-peroneal Trunk
ART L.TPTr
Artery Left Tibio-peroneal Trunk
ART CL.TPT
Artery Contralateral Tibio-peroneal Trunk
Region
Y
Y
Y
Peripheral
ART CL.ExI
Coronary
Description
Congenital
Name
Normal
Code
Waveform characteristic
Comments
SPECIAL SITES (HIDDEN)
Y
*
0
ECG
ECG
Site related to electrocardiographic
leads
29
X
Arterial
Arterial
MICOR compatibility sites
30
XB
Ventricular
Ventricular
MICOR compatibility sites
31
XA
Atrial
Atrial
MICOR compatibility sites
37
NONE
Reserved
Atrial
MICOR compatibility sites
117
AVN
Artery Atrio-Ventricular Node
Arterial
'117' site is not used by Sensis ('158' is
used instead). Site '117' is listed here for
Cathcor-Sensis compatibility reasons
Name in previous software versions
342 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
Defining data transfer from a Dräger Infinity patient monitor
 Display the Infinity Vital Signs tab card on top.
Infinity patient monitors
The AXIOM Sensis XP Information System can be connected to a Dräger Infinity
network with Infinity patient monitors and receive vital sign data from there. This
allows inclusion of vital sign data which cover not only the actual study period but
also the period before and after the study in AXIOM Sensis XP study reports. The
system will query for and retrieve vital sign data from patient monitors for as long
as the patient is connected to an Infinity patient monitor or until a study is approved or user manually stop vital sign collection.
On the Infinity Vital Signs tab card you can configure the commnunication with
the Infinity network.
For information about the Dräger Infinity interface concept see also Communication with Dräger Infinity patient monitors 46.
Identifying Infinity
monitors in the network
AXIOM Sensis XP (VC11)
When you enable data transfer here, the information system can import vital sign
data collected on an Infinity patient monitor into its database and make it available for reporting. The criteria used by the system to associate Infinity data to an
AXIOM Sensis XP study automatically are as configured above.
AXA5-200.640.07.01.02
343 / 456
System Administration
Active Infinity patient monitors that cannot be associated with a Sensis study automatically can be assigned to Sensis studies manually in Documentation Tool
(Application > Select Infinity Monitor for Vital Signs Import). However, the Select Infinity Monitor for Vital Signs Import dialog box lists only unassigned Infinity monitors. Once a user assigns a monitor to a Sensis study this monitor is no
longer listed in this dialog box.
Criteria for identifying Infinity monitors in the Select Infinity Monitor for Vital
Signs Import dialog box are a combination of patient name, ID, care unit, and bed
label. Therefore be sure your cath lab uses unique care unit and bed labels in the
Infinity network. Otherwise users might not be able to find the patient monitor
they are looking for and might not be able to associate the Infinity data to their
Sensis study.
Database tables
This is a list of the information system database tables involved in the Infinity integration (this information is intended as reference information).
 INFMONS
– This table contains the list of bedsides reporting to the Infinity gateway.
The table is updated every 10 seconds when the gateway is polled.
– The table contains the information that is shown in the Select Infinity Monitor for Vital Signs Import dialog box (patient name, ID, care unit, and bed
label for unassigned Infinity patient monitors, see above).
 INFCONN
– This table contains the bed label, associated patient, starting time of the
Sensis study and next query time for Infinity data.
– When the patient is discharged from the bedside, when the study is
approved, or when the PostCath period expires, the patient and bedside
record is dropped from the database table. This indicates that the patient is
no longer connected to the monitor and data import to Sensis ends.
 INFVS
– This table holds the actual Infinity vital signs data retrieved from the bedside
patient monitor.
Selecting data for transfer
 Check the Import Vital Signs check box for the period whose vital sign data
you want to import.
– Selecting a period enables the selection boxes in this group.
 Select which data items to import for a phase by checking the corresponding
boxes: Heart Rate, SpO2, NBP, Respiration, etCO2.
344 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
 Also select the Sample Rate.
– If you select 10 minutes, for example, the system will query the Infinity network for vital sign data after 1, 11, 21, 31, 41, 51 minutes and so on.
– NBP values are saved every time an NBP measurement is performed. The
Sample Rate has no effect on these values.
 Click Apply to save your changes.
Defining matching criteria
By default, the patient name and the patient ID are selected as the criterion for
matching incoming Infinity data to an AXIOM Sensis XP patient.
 Select Patient Name or Patient ID, if required.
 Do not forget to click Apply to save your changes.
Changing gateway data
In the Infinity Gateway section of the Infinity Vital Signs tab card you can add or
edit a connection to the Infinity network.
 Click Add to establish a connection to the Infinity network.
-Or Select the predefined gateway and click Edit.
– The Add/Edit Infinity Gateway dialog box opens.
 Enter the Infinity Gateway (IP address), and its User Name and Password.
Troubleshooting
If you have trouble connecting to the Infinity network, check the following settings:
 Do all settings on the Infinity Vital Signs tab card of the Configuration Man-
ager conform to the physical installation environment?
– Infinity Gateway IP address or host name.
– Gateway OS user (local administrator user on the gateway).
 Are the patient matching criteria set correctly?
– Recommended: Patient Name and Patient ID
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
345 / 456
System Administration
 Are the Infinity Gateway and bedside monitors online and can the gateway be
pinged with the host name or IP address?
– If errors are found, confirm the IP and network status.
 Has the SIS Infinity Service been started and is it set to Automatic?
– The path to this service is: Computer Management > Services > SIS Infinity > Properties.
 Is the Infinity Interface License installed on the AXIOM Sensis XP Information
System server?
– See c:\MIS\config\licensing\license.dat
 Did the SIS Infinity log report errors related to Infinity gateway communica-
tion?
– See c:\MIS\Log \Infinity\<gateway IP>\_conn.log.
– If logon errors (user and password) are listed, contact the Dräger service
and double-check the gateway user and password used by Sensis.
Synchronization of inventory lists
 Display the MMS tab card on top.
346 / 456
AXA5-200.640.07.01.02
System Administration
Configuration Manager
The tab card MMS is relevant only if the optional material management interface
license is installed on your AXIOM Sensis XP. If your AXIOM Sensis XP Information System is connected to a departmental material management system, it receives an inventory list (master file) from that system at regular intervals. Sensis
uses the information in this file to update its own inventory list (system group
_PRODUCT).
For background information on the material management interface, refer to Communication with material management systems 57.
On the MMS tab card of Configuration Manager, you configure when synchronization of _PRODUCT with the latest version of the master file from the material
management system will take place.
 In the Material Management System interface to list, select which material
management system you are using.
– QSight, or Optiflex CL (by Omnicell)
 Under Master file synchronization parameters, enter a time of day when it is
unlikely that examinations are being performed.
– Use the 24 hour time format.
– Enter 00:00 and 23:59, if you do now want to configure a synchronization
period. The system will attempt to update the inventory list as soon as a
new master file has arrived from the material management system.
 Also define when and how often the system will retry updating its inventory
list if the first attempt fails, for example, because an examination is currently
being performed.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
347 / 456
System Administration
348 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Computer Configuration
Computer Configuration overview
With the help of the Computer Configuration tool you can apply information system settings to the registry of your local client PC.
You use the Computer Configuration window for the following tasks:
 Changing and testing the server connection
 Installing a bar code reader
Starting the Computer Configuration
 Select AXIOM Sensis Information System > Server > Computer Configura-
tion from the Windows Start menu.
Changing and testing the server connection
 Display the Server tab card on top.
Exchanging the information system server
PC
During system installation or if you reconfigure your AXIOM Sensis XP Information System you might have to exchange the information server computer. Subsequently you will need to change the server name in the registry of all client
computers. You use this tab card to do so.
Changing the server names, applying changes and testing the connection
 Enter the new server IP address or host name under SQL Server Name and
Server Computer Name.
 Click Apply and Test to apply and test your changes.
– You will be requested to log onto the server.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
349 / 456
System Administration
 Enter the user name and password for the MIS_ADMIN user account (the infor-
mation system “super user” or “super administrator”) and click OK.
Note
User name and password are not case-sensitive.
– If the test was successful a message informs you of this.
– The new server connection is written to the registry of your client computer.
 Repeat this step on all other client PCs in your information system network.
Installing a bar code reader
 Display the Bar Code Reader tab card on top.
Bar code reader functionality
Your system allows you to use a bar code reader for data entry in the Documentation Tool.
Instead of selecting a dictionary entry for a table and field in the software, a clinical user may simply select a field and scan the bar code of, for example, a consumable item such as a catheter, if a bar code reader has been connected.
You can connect one bar code reader to each client PC in your information system
network.
350 / 456
AXA5-200.640.07.01.02
System Administration
Computer Configuration
Bar code reader configuration
Installation and configuration of a bar code reader involves these procedures:
 Installing the bar code reader at an AXIOM Sensis XP Information System cli-
ent PC (via serial connector) and configuring it here.
Different installation procedures apply for different bar code reader models.
Please contact Siemens Service if you want to install a bar code reader at you local
Sensis information system PC. They will either be able to help you or provide you
with installation instructions.
 Scanning bar codes and assigning them to dictionary entries for various data-
base tables. This is done on the Dictionaries tab card of the Configuration
Manager.
See Editing dictionaries 321
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
351 / 456
System Administration
352 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Backup Manager
Backup Manager overview
We strongly recommend that you back up your information system databases at
regular intervals.
The Backup Manager is the information system administration platform for performing and scheduling database backups and for restoring data from tape or network if this becomes necessary.
Overview of functions
You will use the Backup Manager for the following tasks:
 Creating an immediate backup of the information system
 Scheduling information system backups
 Restoring the information system databases from a backup
Key terms and concepts
For information on the backup, restore, and data archiving concept of the AXIOM
Sensis XP Information System refer to Backup and restore 67
Backup options and backup strategy
These backup options exist for the AXIOM Sensis XP Information System:
 Backup to a backup server
– If your AXIOM Sensis XP Information System runs on a high-end SIS
server, a backup server address is required for database backup because no
tape drives are installed in high-end servers.
– If your AXIOM Sensis XP Information System runs on a Sensis XP Master
Server or ACQ Master, tape drives are available in these server PCs. However, you might nevertheless prefer to back up to a backup server if your
hospital provides one.
– It is the task of the backup server to guarantee that these backups are stored
safely and that several versions are kept.
 Backup to tape
– If no backup server is available in your hospital and the AXIOM Sensis XP
Information System runs on a Sensis XP Master Server or ACQ Master, you
will use the tape drive in your information system server PC to back up data.
– In this case it is your responsibility to define a backup strategy that involves
tape handling tasks.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
353 / 456
System Administration
Backup to a backup server
If a backup server is available in your hospital the task of ensuring data security for
your information system database is fairly easy for you: You schedule regular
backups to this server (we recommend that you schedule daily backups). However, a number of settings must be made so that backups over network run smoothly.
General prerequisites
for network backups
 A backup server must be available in your hospital network and a shared back-
up folder must exist on this server.
– In this example let us assume the backup server name is backup_node and
the shared folder name is backup_share.
 A backup user must have been created on the backup server and this user must
have read and write permissions on the shared backup folder.
– Let us assume here that this user account is backup_user and its password is
backup_password.
 Backup_user (with backup_password) must also have been defined on the in-
formation system server (in the Windows user administration of the information system server PC).
– Backup_user must have administrator privileges here.
Prerequisites for scheduled network backups
To ensure that scheduled backups to a backup server in the hospital network can
be executed, the network share, backup account, and password must have been
configured on the AXIOM Sensis XP Information System Site Configuration
platform. The settings you are expected to make here differ for access to the backup server for local login or for login with a domain address.
 Start the Site Configuration Wizard with the Windows Start menu:
Start > AXIOM Sensis Information System > Configuration > Site Configuration on the information system server PC.
 Advance to the Configure Network backup page.
354 / 456
AXA5-200.640.07.01.02
System Administration
Backup Manager
 For login with a local account:
 Enter the following settings:
– Network Share: K: \\backup_node\backup_share
– Backup Account: backup_user
– Password: backup_password
 For login with a domain account:
 Enter the following settings:
– Network Share:
K: \\hospitaldomain\host /user:"hospitaldomain\backupuser"
– Backup Account: backup_user
– Password: backup_password
Backup_node, backup_share, backup_user, and backup_password are, of course,
placeholders for the actual names in this example. The drive letter K: is not to be
used elsewhere on your system.
Prerequisites for an immediate backup to a
backup server and for
restoring backups
In order to be able start a network backup immediately or to restore a backup from
a backup server:
 Log off from your correct Windows session (Windows Start menu Log off).
 Log on with backup_user and backup_password.
 Start the Windows Explorer.
 Select Tools > Map Network Drive in the Windows Explorer menu bar.
 Map K: to \\backup_node\backup_share
– We also recommend that you select the Reconnect at logon checkbox. This
way K: will be permanently mapped to the backup server and folder for this
user.
 Start the Backup Manager with your normal information system administrator
user name and password.
Backup to tape
If you are using tapes to back up your information system databases and settings
it is your responsibility to define a backup strategy that involves the following provisions:
 Appointing a person who is responsible for backup, tape handling, and check-
ing the backup log regularly.
 Obtaining enough tapes so that more than one backup version is available in
case a tape is lost or corrupted or one backup failed for some reason.
 Defining a rotation scheme for the tapes.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
355 / 456
System Administration
 Documenting tape handling and replacement.
When working with tape backups also remember that the Backup Manager expects you to use tapes exclusively for backing up the AXIOM Sensis XP Information System, but not for storage of any other data.
Strategy for tape backups
Various alternatives exist for tape backup strategies. They differ in how many
tapes are required and the complexity of the rotation scheme.
See Backup and restore 67
We recommend that you adopt a rotation scheme that involves:
 Five tapes
– One for every day of the week.
– The tapes should be labeled accordingly.
 Scheduled daily backups
– Tapes must be exchanged between backups.
 Off-site storage of Friday’s tape
– For example in a fire-proof safe, if this is possible.
 Documentation of tape exchange and checking of the backup log.
– For example, copy and use the form provided at the end of this chapter.
See Backup protocol 368.
Note
What tapes to use
We also recommend that you replace tapes regularly. As a rule of thumb you
should acquire a new set of tapes once a year.
As regards PC hardware, AXIOM Sensis XP and your AXIOM Sensis XP Information System server may be installed on:
 Siemens Celsius 440 or 450 PC with a Seagate Travan 40 GB tape drive.
 Siemens M460 PC with Quantum DAT drive (72 GB).
356 / 456
AXA5-200.640.07.01.02
System Administration
Backup Manager
Formatting tapes
Before you use a new tape for the first time you may have to format it.
Tapes are available either “preformatted” or unformatted. If you have bought
tapes that are not already “preformatted” use the Windows Backup Utility to format new tapes.
 Access the Windows Backup Utility from the Windows Start menu.
– Start > Programs > Accessories > System Tools > Backup.
Refer to the Windows Backup online help for instructions on how to format tapes.
To find the relevant topic use the index and type the keyword “formatting tapes”.
Starting the Backup Manager
 The Backup Manager is only available on the information system server (the
PC with the SQL database).
– This may be an information system Master PC or a server PC.
 In order to be able to run backups or restore backups you must have adminis-
trator rights in the Windows operating system.
 In order to be able to call up the Backup Manager you need to be a member
of the Administrator role in the AXIOM Sensis XP Information System user
management.
See Granting access to program functions 139
 From the Windows Start menu, select AXIOM Sensis XP Information System
> Server > Backup Manager.
– The Login dialog box is displayed.
 Enter your user name and password and click OK.
– User name and password are not case-sensitive.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
357 / 456
System Administration
Creating an immediate backup of the information system
 Before you start a backup, exit all other AXIOM Sensis XP Information System
tools and ask all other users to log out, too.
 Display the Backup tab card on top.
 Enter a Backup Name.
– The Backup Manager utility will automatically add the creation date and
time to that name. This will help you identify a backup later on.
– Date and time are not, however, part of the backup name, even though in
the Restore utility it may seem so. Subsequent backups to the same destination (for example, same tape) will therefore overwrite each other.
 Also enter a Backup Description, if you like.
Note
Problems may occur when dates are included in a backup name or description
in a date format that uses reserved characters.
 Do not use “/” in the backup name and description fields in the Backup Man-
ager.
For example, do not type "04/Apr/2008", because "/A" is a reserved command
line argument for the MS NT Backup utility. Type "04-Apr-2008" instead.
Backup to tape
 Insert a tape and select Tape as the backup medium.
– Before you do this make sure the tape is not write-protected.
Or
Backup to backup server
 Select Filename and enter the backup drive and file name (K:filename.bkf).
– Be sure you are logged on as backup_user and that the shared folder on the
backup server has been mapped to a drive.
See General prerequisites for network backups 354 and Prerequisites for an
immediate backup to a backup server and for restoring backups 355
 Select what data you want to back up:
– Database - all information system databases are automatically selected for
backup.
– Include in backup - check if you want to include Reports, Pictures (X-ray
and mapping system images), and Waveforms (waveform images and ablation graphs) in your backup.
358 / 456
AXA5-200.640.07.01.02
System Administration
Backup Manager
 Click OK to start the backup.
– A message box opens prompting you to confirm immediate backup.
– After clicking Yes, you are asked whether the system should check the
integrity of the databases.
 We recommend that you click Yes.
– When the integrity check is completed a message informs you of this.
– You can check the results of the database integrity check in the Windows
Event Viewer (Programs > Administrative Tools > Event Viewer), which
you can open even while the Backup Manager message is still being displayed.
 Click Yes to continue and start the actual backup process.
– During this procedure the Backup Manager copies the specified databases
and files temporarily to a backup directory (C: \ MIS \ backup).
– Once the backup is complete these files and folders are deleted from the
hard disk again.
 Check the backup and restore log file after the backup is complete to verify that
it was performed successfully and that no errors occurred.
Scheduling information system backups
You can schedule the database backup to be performed at a time when nobody is
working with the system (for example, at night).
The system allows you to schedule one of the following options:
 One backup run
– This option makes sense if you cannot perform a backup immediately due to
an ongoing examination.
 Regular backups (daily or weekly)
– We recommend that you back up your information system daily.
– Weekly backups are only recommended if only few examinations are performed in your cath lab every week and your acquisition system is not used
and therefore switched off for entire days.
Basic procedure for scheduled backups
 Display the Backup tab card on top.
Backup to tape
If you are using tape backup proceed as follows:
 Insert a fresh tape ahead of time and make sure it is not write-protected.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
359 / 456
System Administration
 Select Tape as the backup medium.
Note
Remember that the Backup Manager expects tapes to be used exclusively for
information system backups. Other data will be deleted from the tape.
Or
Backup to backup server
If a backup server is available proceed as follows:
 Select Filename and enter the backup drive and file name (K:filename.bkf).
– Be sure the correct SQL Server Agent settings have been made in the Site
Configuration Wizard.
See General prerequisites for network backups 354 and Prerequisites for
scheduled network backups 354
 Specify a Backup Name, Backup Description, and what to Include in backup.
Note
The Backup Manager can back up reports, X-ray images, and waveform images
only if they are stored in the directories C: \ MIS \ reports, C: \ MIS \ studypic,
and C: \ MIS \ studywf.
 Define the backup schedule.
 Close the Backup Manager when you have finished(Application > Exit).
– Do not click on the OK button as this would start data backup immediately
and not simply close the Backup Manager window.
Scheduling a one-time backup run
 The Backup tab card of the Backup Manager is displayed.
 A backup name, destination, and which data to back up have been defined.
 Check Schedule.
 Click One time.
 Select a backup date and time.
360 / 456
AXA5-200.640.07.01.02
System Administration
Backup Manager
Scheduling a daily backup routine
 Check Schedule.
 Click Daily.
– We recommend that you back up your databases daily.
– Weekly backups are recommended only if only a few studies are performed
in your cath lab each week.
 Select the date and time for the first backup.
 Select an End Date as well, if you want.
Note
If you are backing up to tape, remember to exchange tapes between backups or
you will overwrite the backups.
Email notification after backup
When you are working with scheduled backups, email notification helps you with
an overview of successful database backups and alerts you if problems arise.
 Display the Notification tab card on top.
 Enter the name or IP address of your SMTP mail server.
 Specify one or several email addresses (use a semicolon as the separator).
Note
If you create an e-mail job with several e-mail recipients, and one of the e-mail
addresses is incorrect, none of the e-mails will be sent.
 Check the Export Log in the Communication Manager at regular intervals.
 Correct the e-mail addresses for failed jobs.
 Enter a sender address under Return Address.
– This is required because the AXIOM Sensis XP Information System does
not have an email account of its own.
– Any auto-reply messages will be sent to this return address if one of the
email recipients has configured auto reply.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
361 / 456
System Administration
 Select when email notification will be sent:
– Always send backup result notification sends an email both after successful and unsuccessful backups.
– Only send notification if backup failed only alerts you if problems occur.
– Never send backup result notification disables email notification.
 Click this button to send a test email.
 Do not forget to save your settings.
Checking the backup and restore log file
Checking the backup and restore log file at intervals is particularly important if you
are working with scheduled backups. Scheduled backups run entirely in the background, no message is displayed if errors occur.
 Click View Log to display the backup and restore log file of your system.
– This log file lists all backup and restore runs on your system chronologically.
 Scroll to the end of the file.
 Check if your recent backup runs have been performed successfully.
If errors occurred during backups there may be various reasons for this.
Errors during network
backup
The backup server was down when the information system attempted to access it.
The information system server was denied access to the destination server and
folder.
 In both cases contact the system administrator of the backup server.
Errors during tape backup
362 / 456
The tape was write-protected.
 Open the lock in the upper left-hand corner of the tape.
AXA5-200.640.07.01.02
System Administration
Backup Manager
 Move the red slider to the unlocked position.
 Repeat the backup
The tape was not inserted correctly.
 Pull the tape out and reinsert it in the drive.
The tape is damaged.
 Use a new tape.
The tape drive could not be accessed.
 Reboot the system with a tape in the drive.
Restoring the information system databases from a backup
If you detect or suspect loss of data, for example, after a system crash, you can restore the latest backup of your databases from tape or from the network.
Three data restoration options are available in the Backup Manager:
 Restoring the SIS database and server system environment
– This option is preselected, it is the option you will use in most cases.
 Restore SQL Server Master database
– Restoring the master database is, as a rule, only necessary if a serious (hardware) crash has occurred.
 Restore SIS database
– This option is used by Siemens Service only.
Note
During data restoration the Dräger Infinity interface and the HL7 Listener are automatically stopped.
Restoring the SIS database and server system environment
 Stop all AXIOM Sensis XP Information System application programs.
 If your AXIOM Sensis XP Information System runs on a high-end SIS server,
stop the service SIS MMService before you restore data.
– Press the Windows Start key, select Run, and enter services.msc.
– Stop SIS MMService and return to Backup Manager.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
363 / 456
System Administration
 Display the Restore tab card on top.
 Select Restore SIS database and Server system environment.
Note
Whether report files, X-ray pictures, and waveform images will also be restored
depends on whether you included them in the backup earlier.
Restore from tape
If you want to restore the data from a tape:
 Insert the tape with the backup in the tape drive.
 Click Restore to open the Windows Backup utility.
 Start the Restore Wizard.
 Select the backup you want to restore in the Restore Wizard dialog box.
 Click Next to continue.
 Finally click Finish in the Restore Wizard dialog box.
– The wizard will rewind the tape and then start the restore process.
Restore from backup server
If you want to restore data from a backup server:
 Make sure you are logged in as backup_user.
See Prerequisites for an immediate backup to a backup server and for restoring
backups 355
 Click Import File and enter the network path and file name in the Backup File
Name dialog box.
– Use the format: K:\\filename.bkf.
364 / 456
AXA5-200.640.07.01.02
System Administration
Backup Manager
 Click OK to accept this path and file name and close the dialog box.
 Expand the File catalog in What to restore.
 Expand the backup file and select C:
 Click Next to continue.
 Finally, click Finish in the Restore Wizard dialog box.
– You will be prompted to confirm the backup file name.
When restoration of the selected backup is complete the Restore Process dialog
box tells you so.
 Close the Restore Process dialog box (Close) and also the Windows Backup
utility (Job > Exit).
– A message box is displayed asking you whether you want to continue database restoration.
 Click Yes if no errors occurred while the backup file was read from tape.
– The databases are now restored from the backup file and a progress indicator is shown.
 Close the Backup Manager when database restoration is complete.
Restore SQL Server Master database

Stop all AXIOM Sensis XP Information System application programs.
 If your AXIOM Sensis XP Information System runs on a high-end SIS server,
stop the service SIS MMService before you restore data.
– Press the Windows Start key, select Run, and enter services.msc.
– Stop SIS MMService.
 Stop the SQL Server.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
365 / 456
System Administration
 Start the SQL Server again in single user mode from a command window with
the command sqlservr -c -m
– You must be in the correct directory for the required instance of the SQL
Server, for example: c:\Program FIles \ Microsoft SQL Server \ MSSQL \ Bin
 Start the Backup Manager.
 Display the Restore tab card on top.
 Select Restore SQL Server Master database.
Restore from tape
If you want to restore the data from a tape:
 Insert the tape with the backup in the tape drive.
 Click Restore to open the Windows Backup utility.
 Start the Restore Wizard.
 Select the backup you want to restore in the Restore Wizard dialog box.
 Click Next to continue.
 Finally click Finish in the Restore Wizard dialog box.
– The wizard will rewind the tape and then start the restore process.
Restore from backup server
If you want to restore data from a backup server:
 Make sure you are logged in as backup_user.
See Prerequisites for an immediate backup to a backup server and for restoring
backups 355
366 / 456
AXA5-200.640.07.01.02
System Administration
Backup Manager
 Click Import File and enter the network path and file name in the Backup File
Name dialog box.
– Use the format: K:\\filename.bkf.
 Click OK to accept this path and file name and close the dialog box.
 Expand the File catalog in What to restore.
 Expand the backup file and select C:
 Click Next to continue.
 Finally, click Finish in the Restore Wizard dialog box.
When restoration of the selected backup is complete the Restore Process dialog
box tells you so.
 Close the Restore Process dialog box (Close) and also the Windows Backup
utility (Job > Exit).
– A message box is displayed asking you whether you want to continue database restoration.
 Click Yes if no errors occurred while the backup file was read from tape.
– The master database is now restored from the backup file and a progress
indicator is shown.
– When restoration is complete the server shuts itself down automatically.
Note
AXIOM Sensis XP (VC11)
After database restoration, the SQL Server is automatically restarted in multi
user mode.
AXA5-200.640.07.01.02
367 / 456
System Administration
Backup protocol
Year
_____________________
Week
Mon
Tue
Wed
Thur
Friday
Check Log
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
368 / 456
AXA5-200.640.07.01.02
System Administration
Backup Manager
Year
_____________________
Week
Mon
Tue
Wed
Thur
Friday
Check Log
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
369 / 456
System Administration
370 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Configuration of Statistics Manager and Inventory
Manager
The AXIOM Sensis XP Information System provides two tools that make use of
the information system central database for applications beyond immediate case
handling. The user interfaces of both software tools can be configured to some degree.
Overview
 The Statistics Manager
– For statistical analysis based on the information system database.
– Refer to Statistics Manager configuration 372 on how to customize
this tool.
 The Inventory Manager
– For inventory management, handling of vendors’ lists and order placement.
– Refer to Inventory Manager configuration 376 on how to customize
this tool.
Database information
and operator manual
Refer to Information System Concepts 17 for details of how the Statistics
Manager and Inventory Manager tools fit into the bigger picture of AXIOM Sensis XP Information System applications. Here you will also find information on
how the databases of these applications interact with the central database.
Refer to the AXIOM Sensis XP Operator Manual, Part AXIOM Sensis XP Information System, Chapters Statistics Manager and Inventory Manager for details
of how to operate these tools from a clinical user’s perspective.
User rights for the Statistics and Inventory
Manager applications
Various use cases exist that can be combined in the definition of access rights for
individual users and user groups to inventory and statistic manager functions.
Please inform your users to which statistics and inventory manager functions they
have access and which functions are not available for them even though these
functions are described in the operator manual.
Refer to Defining, editing, or deleting roles 139 and List of available use cases 142 for instructions on how to grant access rights to program functions
and information on use cases.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
371 / 456
System Administration
Statistics Manager configuration
You use the configuration platform of the Statistics Manager for the following
tasks:
 Checking the server connection
 Setting database query defaults
 Modifying the graphic display of aggregation results
 Changing printout settings
Note
For exclusion of groups (database tables) from statistical queries refer to Output
clusters: including and excluding fields 115
Starting the Statistics Manager configuration
 Close the Statistics Manager application if it is currently open.
 Select AXIOM Sensis Information System > Client > Statistics Manager Con-
figuration from the Windows Start menu.
Checking the server connection
 Display the Database Server tab card on top.
Server connection
372 / 456
On the Database Server tab card you will find information on the server connection. The Host name listed here is the computer in your cath-lab network on
which the information system central database is located.
AXA5-200.640.07.01.02
System Administration
Configuration of Statistics Manager and Inventory Manager
Setting database query defaults
 Display the Query tab card on top.
Default fields
Whenever you run a query on the information system database with Statistics
Manager, these fields are automatically displayed together with the search results.
 Make sure none of the searches stored in the Statistics Manager explicitly
search for this information.
 If your users want to include any of these fields explicitly in their search defini-
tions, the corresponding field must be disabled in the Default Fields list.
SQL Log
You can have the SQL search statements of the queries run by the Statistics Manager saved in a log file for use elsewhere.
 Click this option to have the file QWSSQL.LOG created and updated with each
query.
– The log file is saved to directory C: \ MIS \ log \ qws on your local hard disk.
Saving changes
 Make sure you click the Save button at the bottom of the Query tab card if you
have changed any settings.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
373 / 456
System Administration
Modifying the graphic display of aggregation results
 Display the Chart tab card on top.
Display options
 Number of items per page in a bar/line chart
– The system will fit up to the number of items specified here on a page in a
printout. If the aggregation procedure results in more than the number of
items specified here, a second page will be printed out.
 Max. number of items in a pie chart
– If more than the number of items specified here will result from the aggregation procedure, a bar chart is displayed instead of a pie chart.
 Max. text label length
– If text labels in any of the three chart types are longer than specified here (in
millimeters), they are truncated both on screen and in the printout.
 Modify bar/line color
– Allows you to select the color in which bar and line charts are displayed. The
color is the same for screen display and printout.
– To select a different color click the button.
Note
If you are using a black and white laser printer the color you select here will appear as a shade of gray.
Therefore always select a color with a good visibility both on screen and on a
black and white printout.
Saving changes
 Make sure you click the Save button at the bottom of the Chart tab card if you
have changed any settings.
374 / 456
AXA5-200.640.07.01.02
System Administration
Configuration of Statistics Manager and Inventory Manager
Changing printout settings
 Display the Report tab card on top.
Header text
Margins
Include search definition
Saving changes
 Enter the header text for printouts of statistical queries here.
 Select the page margins for printouts here.
 Select whether the search definition is to be printed out together with query
results.
– We recommend that you select this option. It will help with trouble-shooting and with interpretation of the printout.
 Make sure you click the Save button at the bottom of the Report tab card if you
have changed any settings.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
375 / 456
System Administration
Inventory Manager configuration
You use the Inventory Manager configuration platform for the following tasks:
 Networking Inventory Manager applications
– As explained in the information system and administration overview, the
Inventory Manager is an optional application program. Inventory Manager queries the information system central database for consumption
information but stores internal information, such as vendor lists, stock,
orders, etc., in a local database of its own, the inventory database.
See also Information System Concepts 17.
– If you are working with several Inventory Manager installations in your
cath-lab network you will want all of these installations to access the same
inventory database. You can network several Inventory Manager installations in your cath-lab by mapping the Inventory database path of all of
these installations to the same network drive.
 Adjusting user interface settings
 Redefining column headers
 Establishing the connection with the information system database
Starting the Inventory Manager configuration
 Close the Inventory Manager application, if it is currently open.
 Select AXIOM Sensis Information System > Client > Inventory Manager
Configuration from the Windows Start menu.
– The Login dialog box is displayed.
 Enter your user name and password and click OK.
Note
376 / 456
No distinction is made between upper and lower case letters.
AXA5-200.640.07.01.02
System Administration
Configuration of Statistics Manager and Inventory Manager
Networking Inventory Manager applications
 Display the Setup tab card on top.
The Inventory database path on the Setup tab card specifies the location of the
local Inventory Manager database. By default this path is c: \ mis \ iws on the local PC where Inventory Manager is installed. If you are working with several Inventory Manager installations the default path settings result in each of these
installations working with its own inventory management database.
In order to network all Inventory Manager installations in your cath lab proceed
as follows:
 Create a directory on the hard disk of your information system server PC.
– For example, c: \ mis \ iws.
 Share this directory.
 Map this directory to a network drive using the Windows Explorer on the client
PC (Tools > Map Network Drive, make sure you check Reconnect at logon).
 Enter the name of this network drive in the Inventory database path box.
 Make sure you repeat this step on the Inventory Manager Configuration plat-
forms of all Inventory Manager installations of your cath-lab network.
– All these local Inventory Manager programs will now access the same
database iws_db.mdb on the information system server PC.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
377 / 456
System Administration
Note
Once you have networked your Inventory Manager installations, all the Inventory Manager Configuration settings (except for resolution and inventory database path) you make on one client PC will also apply to the configuration of all
other Inventory Manager installations in the network.
All configuration settings you make on an Inventory Manager Configuration
platform are stored in the Inventory Manager database (iws_db.mdb), with the
exception of the resolution and inventory database path. These two settings are
stored locally on each PC in a file called iwsaxsis.ini in the Windows root directory (this is usually C: / WINNT ).
Adjusting user interface settings
 Display the Setup tab card on top.
Changing the resolution
You can change the size of the Inventory Manager application window.
 Click the Change button in the Resolution section of the Setup tab card.
– These options are available: 640*480 (default), 800*600, and 1024*768
(recommended).
Changing printout settings
Under Report margins you can change the page settings for printouts.
 Overwrite the default 1 cm in the various boxes, if you wish.
378 / 456
AXA5-200.640.07.01.02
System Administration
Configuration of Statistics Manager and Inventory Manager
Note
The margin settings are always indicated in centimeters, no matter what your
Windows Regional Settings are set to.
Period management
In the Inventory Manager a "period information" system keeps track of cost and
unit information. Cost and unit information is available for the current and previous period. When a new period is started, information of earlier periods is lost.
On the Setup tab card you set the start date of a new period, for example, at the
beginning of a fiscal year.
 Click Start New Period to start a new period with the current date.
– What used to be the current period before you clicked the button is now the
previous period.
Note
You will always have to start a new period manually here. New periods will not
start automatically after a certain time (for example, a year) has elapsed.
Setting Order IDs
All orders are numbered on the Orders tab card of the Inventory Manager.
You can set the order number prefix (Key) and the Counter in the Order-ID section of the Setup tab card.
Accumulated cost calculation
In this section of the Setup tab card you can set how to calculate costs.
 After stored order
– This option adds up costs when a new order has been placed, the goods
have been received, and the order status has been set to “goods stored”.
– This means costs are added up when a bill is paid.
 After consumption
– This option adds up costs when consumption is read from the information
system database.
– This means costs are added up when actual consumption occurs.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
379 / 456
System Administration
Establishing the connection with the information system database
 Display the Connection tab card on top.
You use the Connection tab card to load the list of consumables from the information system database into the Inventory Manager database during system installation.
Defining the mapping table
 These definitions must have been made in the DB Manager:
– The group names you want to enter in the mapping table on the Connection tab card are defined in the information system database.
– A Vendor field is configured for the groups you map here.
– A Vendor dictionary exists.
– Each item entered in a consumables table in the database has information
on a vendor (this is achieved by setting up the vendor information as an
automatic entry), cost information is optional.
– The group definition and dictionary definition files appear as shown below.
380 / 456
AXA5-200.640.07.01.02
System Administration
Configuration of Statistics Manager and Inventory Manager
# CA, Catheter, 3
N, ENTTIM, T, 5, Time <HH:MM>
N, REMTIM, T,5, Removal <HH:MM>
N, CATHETER,SI,5, Catheter <DIC>, CATHET
N, VENDOR, SI, 5, Vendor <DIC>, VENDOR
N, COST, SF,8.2, Cost
N, ENTRSITE,C,4Entry site <DIC>, ESITE
...
# CATHET, Catheters, SI, 5, 32, 14, Y, C:2, L:20
#1, Right Heart
1, Swan Ganz Monitoring, 3,123.25
2, Swan Ganz Thermal Dilution, 1,123.45
Catheter group definition
Catheter dictionary definition
#1, Left Heart
.3, ..
# VENDOR, Vendors, SI, 5, 60, 14
1, Vendor name 1
2, Vendor name 2
3, Vendor name 3
Vendor dictionary definition
 Double-click in the Group name box of the empty row in the mapping table
(the row marked with an *).
 Enter the name of the information system database table containing the infor-
mation you wish to load.
– Use upper case letters only.
 Press Return to accept.
 Enter the Item field name.
 Enter the Vendor field name.
If a quantity field has been defined for the items in this group:
 Enter the Quantity field name here as well.
– Quantity is used if one registration is not equal to consumption of one unit.
 Click Retrieve to retrieve this information from the central information system
database.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
381 / 456
System Administration
Removing test data from the consumption spreadsheet
 Use the clear consumption spreadsheet and the clear buffer functions to re-
move test data of new consumption from the consumption spreadsheet of the
Inventory Manager during system installation and configuration.
 Click Clear in the Consumption spreadsheet section.
 Also click Clear buffer in the Consumption memory section.
Cost calculation
 Decide whether you want cost data to be read from the central information sys-
tem database into the Inventory Manager.
– True: yes, cost data will be queried
– False: no cost data will be read from the information system database.
Redefining column headers
 Display the Column Headers tab card on top.
On the Column Header tab card you can change all the header labels of the Inventory Manager.
 Double-click on a label in the Customized column
 Overwrite the existing text.
 Press Return to confirm.
382 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Setting up Cost and Charge Control
The AXIOM Sensis XP Information System allows you to monitor and record cost
aspects of examinations performed in your cath lab.
The system allows you to calculate costs and charge for each study:
 Cost control
– Calculates what consumables used and personnel time spent in an examination actually cost the hospital (internal costs).
 Charge calculation
– Calculates what the patient will be charged for an examination.
Note
Cost and charge calculation work basically in the same way but use a different
set of prices.
Cost and charge control are not preconfigured in your system (no factory defaults exist). For most country setups you will have to configure this feature entirely from scratch.
In the U.S. setup of the System Administration, cost and charge calculation is
partially preconfigured. Nevertheless check these settings to make sure they
meet the requirements of your cath lab.
When configuring cost control you can either implement both cost and charge
calculation or only one of these options.
Note
Cost and charge calculation works on a study-by-study basis. This means the system will calculate cost and/or charge for one study at a time.
If you want to obtain statistical information about accumulated costs of all examinations in your database or of a defined subset, use the Statistics Manager.
But note that you can only analyze cost aspects in the Statistics Manager if cost
control has been configured in the information system as explained below.
Procedure overview
These are the steps that you must perform to set up cost and charge calculation:
Defining data acquisition
In order to enable cost and charge data to be acquired during an examination you
will have to make a number of adjustments to the database definition files.
 Start DB Manager and edit the group definition file (rep.grp), the cluster defi-
nition file (cathcor.clu), and dictionary definition files (*.udi files).
Refer to Database Manager 73 for details of how to edit these files.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
383 / 456
System Administration
Steps to perform in the DB Manager:
 Creating the group REFPRICE
 Creating the group PRICESUM
 Modifying groups and dictionaries
 Creating the cluster PRICALC
Note
Recompile the database after you have adapted these database definition files
so that your changes will take effect.
See Recompiling the database 120
Defining data output
You can output cost and charge data either to a study report or export that information to another system such as a HIS/RIS or CIS for further processing.
Refer to Report Composer 155 for details on study report template creation.
Refer to Communication Manager 191 for details on setting up data transfer
jobs to other systems.
Note
If you want to check the accumulated costs (or charge) during an ongoing examination, we recommend that you create a report template for this purpose
and preview this report repeatedly during the examination.
These options exist for viewing and outputting cost and/or charge control data:
 Preview of accumulated cost/charge during an ongoing study
 Output of charge information in a study report together with clinical findings
 Export of cost/charge information to a HIS/RIS or CIS as an HL7 message
 Export of cost/charge information to a HIS/RIS or CIS as an ASCII flat file
Step-by-step
The following step-by-step instructions guide you through setting up cost and
charge control in your AXIOM Sensis XP Information System.
Unless specified otherwise, these definitions are not examples but have to be entered in the relevant definition files exactly as shown here.
All cost and charge values shown in this section are, of course, only placeholders
for your own prices.
384 / 456
AXA5-200.640.07.01.02
System Administration
Setting up Cost and Charge Control
Defining data acquisition
Creating the group REFPRICE
Reference cost and reference charge define setpoints for the typical cost and
charge levels for cath-lab examinations.
If you use a study report for monitoring accumulated costs and charges during the
examination you can display the reference cost next to the actual accumulated
cost (and reference charge next to accumulated charge) for a better overview of
the current situation.
See also Preview of accumulated cost/charge during an ongoing study 393
Note
REFPRICE is a mandatory group that must be defined if you want to set up cost/
charge control in your system.
 Open rep.grp for editing.
See Editing or adding customizable groups 97
 Add the group REFPRICE.
Basic definition
# REFPRICE, Reference Price, 3
N, COST, SF,8.2,Cost
N, CHARGESF,8.2,Charge
Note
Cost and/or charge calculation
REFPRICE is a predefined name, do not change it.
In the REFPRICE group definition you set whether you want to introduce cost control and the calculation of charges into your system or whether you want to implement one of these two options only.
 Skip the N, COST, ... line if you want to calculate only what the patient will be
charged for the examination but no internal costs.
Or
 Skip the N, CHARGE, ... line if you want to calculate internal costs only.
Note
Reference cost/charge
entry options
AXIOM Sensis XP (VC11)
If you define both a reference cost and a reference charge field here, you must
also enter both cost and charge in all cost-relevant groups.
Once you have defined REFPRICE you decide how to handle data entry for cost and
charge reference.
AXA5-200.640.07.01.02
385 / 456
System Administration
These are the alternatives:
No cost/charge reference handling
Note
Manual entry for each
study
If you are not interested in calculating cost/charge reference values no additional
definition is required here.
However, you must define the REFPRICE group .
If you want to be able to enter a different reference cost/charge setpoint for each
study you make these fields available for manual data entry in the Documentation Tool:
 Use this REFPRICE definition in the rep.grp definition file:
# REFPRICE, Reference Price, 3
N, COST, SF,8.2,Cost
N, CHARGESF,8.2,Charge
 Define an input cluster in the cathcor.clu definition file to make these fields
available for data input in the Documentation Tool:
# I, REFP, Ref Cost and Charge
REFPRICE
For cluster creation and editing see Editing clusters 106.
 Add this cluster to all study types for which reference cost and/or reference
charge are relevant.
See Defining study types 310.
Dictionary-controlled
entry by procedure
Reference Cost and Reference Charge can be predefined in the system for different types of procedures. Once a clinical user has selected the procedure in Documentation Tool, Reference Cost and Reference Charge are entered from a
dictionary as automatic values.
 Use this REFPRICE definition in the rep.grp definition file:
# REFPRICE, Reference Price, 3
N, PROCED,SI,2,Type of Procedure <DIC>, REFCST
N, COST,SF,8.2,Cost
N, CHARGE,SF,8.2,Charge
 Create the dictionary referred to in this group definition (refcst.udi)
– Define two automatic fields in this dictionary.
– Enter the list of procedures from which the user can pick in the Documentation Tool.
– Enter a reference cost and reference charge value for each procedure.
# REFCST, Reference Cost, SI, 2, 32, 16, N, C:2, L:50
1, Diagnostic, 5000, 6000
2, Interventional, 5500, 6500
386 / 456
AXA5-200.640.07.01.02
System Administration
Setting up Cost and Charge Control
For dictionary creation and editing see Editing dictionaries 78.
 Define an input cluster in the cathcor.clu definition file to make these fields
available for data input in the Documentation Tool:
# I, PROCED, Procedures and Costs
REFPRICE
For cluster creation and editing see Editing clusters 106.
 Add this cluster to all study types for which reference cost and/or reference
charge is relevant.
See Defining study types 310.
Creating the group PRICESUM
The group PRICESUM automatically sums up all COST, CHARGE, REFCOST, and REFCHARG fields in your groups.
Note
PRICESUM is a mandatory group that must be defined if you want to set up cost/
charge control in your system.
Note
Do not put the group PRICESUM in an input cluster as it calculates cost and
charge totals automatically and should not be made available to clinical users.
 Open rep.grp for editing.
See Editing or adding customizable groups 97.
 Add the group PRICESUM.
Basic definition
# PRICESUM, Cost and Charge Totals, 1
N, COST, SF,8.2,Cost Total
N, CHARGESF,8.2,Charge Total
N, REFCOST,SF,8.2,Reference Cost Total
N, REFCHARG,SF,8.2,Reference Charge Total
Note
Cost and/or charge
calculation
REFCOST (and REFCHARG) must be specified in PRICESUM, even if you do not
plan to enter reference prices in your cost calculation system.
If you only want to set up cost control and no charge calculation, skip the
N, CHARGE ... and the N, REFCHARG ... lines.
If you only want to set up charge calculation, skip the N, COST ... and the
N, REFCOST ... lines.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
387 / 456
System Administration
Note
Your choice of cost and/or charge calculation must correspond to the settings
made in the REFPRICE group definition and in all other cost-relevant groups.
All these groups must either specify both cost and charge or only cost or only
charge. Cost control will not work properly if you are not consistent here.
Modifying groups and dictionaries
In the next step you modify all groups that are to contain cost and/or charge information. Different schemes exist for how cost and charge may be calculated.
The basic distinction here is between:
 Unit-related cost/charge calculation, and
 Time-related cost/charge calculation.
The examples below show suggestions for how to calculate cost/charge for typical
cost-relevant factors in an examination.
As prices for consumables and services are usually defined by the hospital and are
valid for a certain period of time, we recommend that you enter cost and charge
values in dictionaries and define these fields as automatic fields. Your clinical personnel will then not have to bother about prices during a study. They will select a
consumable, procedure, or person participating in a study, and cost and/or charge
will be counted automatically .
Unit-related cost/charge calculation
Unit-related cost/charge calculation counts a cost and/or charge when, for example, the use of a certain catheter is selected in the Documentation Tool or when
performance of a procedure is entered there.
Example 1: Catheters
 Edit the catheters group (CA) in the rep.grp definition file as follows:
# CA, Catheter, 3
N, ENTTIM,T,5,Entry <HH:MM>
N, REMTIM,T,5,Removal <HH:MM>
N, CATHETER,SI, 3,Catheter <DIC>, CATHET
N, CATHSIZE,C ,6,French
N, CATHLEN,C ,6,Length
N, COST,SF,8.2,Cost
N, CHARGE,SF,8.2,Charge
N, ENTRSITE,C , 4,Entry site <DIC>, ESITE
N, ENTRMETH,SI,1,Entry method <DIC>, EMETH
 Edit the catheters dictionary (cathet.udi) as follows:
388 / 456
AXA5-200.640.07.01.02
System Administration
Setting up Cost and Charge Control
# CATHET, Catheters, SI, 3, 32, 14, Y, C:4, L:30
#1, Right Heart
0 , “Swan Ganz Monitoring”, 7, 120, 30, 120
1 , “Swan Ganz Thermal Dilution”, 7.5, 120, 40, 145
Every time one of these catheters is picked from this dictionary in the Catheters
table of the Documentation Tool during an examination, its French size, length,
as well as cost and charge are automatically entered here as well.
Cost and charge will contribute to the total accumulated cost/charge for this study
as calculated by PRICESUM.
Example 2: Medication
Medication costs are calculated based on the amount of a drug administered to a
patient. As the information system database cannot usually handle cost calculation on a “cost times amount” basis, we suggest you create a dictionary containing
typical amounts administered and the corresponding cost/charge values as automatic values.
 Edit the medication group (ME) in the rep.grp definition file as follows:
# ME, Medication, 3
N, TIM,T, 5, Time <HH:MM>
N, MEDIC,SI,3, Medication <DIC> , MEDICA
N, COST,SF,8.2,Cost
N, CHARGE,SF,8.2,Charge
N, ADMIN,SI,2, Route <DIC> , ADMIN
 Edit the medication dictionary (medica.udi) so that it is structured in a hierar-
chical way and contains automatic values for amount, cost and charge:
# MEDICA, Medication, SI, 3, 32, 16, Y, C:2, L:24
# 1 , Ativan
1 , “Ativan 10 ml”, 8, 11
2 , “Ativan 12 ml”, 10, 13
3 , “Ativan 15 ml”, 12, 15
# 1 , Atropine
4 , “Atropine 10 ml”, 20, 24
5 , “Atropine 20 ml”, 40, 44
Note
Frequently, dictionaries are used by more than one group. For example, the
medication dictionary is usually also accesses by the Premedication group. In
this case, make sure you either change the Premedication group definition as
well or use different dictionaries for each group. Otherwise the system will report an error during database recompilation.
A clinical user entering information on drugs given in the Documentation Tool
will now open the Medication dictionary, search for a drug in the dictionary hierarchy, and select the amount that was administered.
Amount, cost, and charge are then automatically entered in the adjacent fields of
this input table. These cost and charge values will be considered in the calculation
of the total cost and charge for this study.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
389 / 456
System Administration
Example 3: Procedures
as unit costs
Procedures may be charged for either as a unit cost or by duration time. This example shows the required modifications to the Procedures group and dictionary
if a fixed price is to be calculated for every procedure performed during a study.
 Edit the procedure group (PR) in the rep.grp definition file as follows:
# PR, Procedure, 3
N, AUTOTIME, T, 5,Time <HH:MM>
N, PROCEDUR,SI, 4,Procedure <DIC>, PROCED
N, COST,SF,8.2,Cost
N, CHARGE, SF,8.2,Charge
 Edit the procedures dictionary (proced.udi) as follows:
# PROCED, Procedure, SI, 4, 36, 14, Y, C:2, L:20
#1, Diagnostic
1, “Left Heart Cath” , 3000, 4000
2, “Right Heart Cath” , 3300, 4400
When a clinical user selects a procedure from this dictionary in the Procedures table of the Documentation Tool, the predefined cost/charge is automatically entered in the table and considered in PRICESUM.
Time-related cost/charge calculation
Some costs are strictly time-related. In this case, you will record the time that a
nurse participates in an examination, for example, and a cost factor (time cost) per
minute. The system will automatically calculate the total cost/charge for personnel participating in an examination from the total time they were present and
their personnel costs per minute (time cost).
Start time options
You can choose between two methods of starting the recording time:
AUTOTIME: Time recording starts the moment a dictionary entry is selected in
Documentation Tool.
STATIME: You will have to enter the start time for a time recording manually with
Documentation Tool.
Note
If you frequently enter the personnel participating in a study during preregistration we strongly recommend that you choose STATIME.
AUTOTIME would enter the preregistration time and not the moment the examination actually starts or the moment personnel starts to participate in a study.
You would have to correct this time entry manually in Documentation Tool. If
you forgot to do so, the calculated costs and charge would be wrong.
Stop time options
390 / 456
Time recordings stop at a recording end time entered manually by the user if a
STOPTIME field has been defined and a stop time entered in Documentation Tool.
AXA5-200.640.07.01.02
System Administration
Setting up Cost and Charge Control
If a STOPTIME field has been defined but no stop time has been entered by the
clinical user, then the examination end is used as the recording stop time by the
system.
If no STOPTIME field has been defined the start time of the next record serves as a
stop time for the first record (see Example 5: Procedures charged for by duration).
Example 4: Personnel
 Edit the personnel group (PN) in the rep.grp definition file as follows:
# PN, Personnel, 3
N, PNNAME, SI, 4,Name <DIC>, PNNAME
N, STAFF,SI, 2,Function <DIC>, STAFF
N, TIMCOST,SF,8.2,Cost per Minute
N, TIMCHARG,SF,8.2,Charge per Minute
N, STATIME,T,5,Start Time <HH:MM>
N, STOPTIME,T,5,Stop Time <HH:MM>
N, COST,SF,8.2,Cost <AUTOMATIC>
N, CHARGE, SF,8.2,Charge <AUTOMATIC>
Note
TIMCOST and TIMCHARG are always calculated per minute, you cannot change
that to any other time unit.
Note
<AUTOMATIC> behind cost and charge is an optional indicator that these fields
will be calculated and filled out by the system automatically once all required
data are available (start time, stop time and time cost).
Remind clinical users not to fill in these fields in the Documentation Tool manually.
 Edit the staff dictionary (staff.udi) as follows:
# STAFF, Function, SI, 2, 30, 16, N, C:2, L:20
1, Physician, 10, 30
2, Technician, 8, 20
3, Nurse, 9, 26
The system calculates the time period between start time and stop time in minutes. The resulting minutes will then be multiplied by personnel cost and charge
per minute and automatically entered in the cost and charge fields of the personnel table.
The resulting personnel cost/charge will also be considered in PRICESUM.
Example 5: Procedures
charged for by duration
AXIOM Sensis XP (VC11)
 Edit the procedure group (PR) in the rep.grp definition file as follows:
AXA5-200.640.07.01.02
391 / 456
System Administration
# PR, Procedure, 3
N, AUTOTIME, T, 5,Time <HH:MM>
N, PROCEDUR,SI, 4,Procedure <DIC>, PROCED
N, TIMCOST, SF, 8.2, Cost per Minute
N, TIMCHARG, SF, 8.2, Charge per Minute
N, COST,SF,8.2,Cost <AUTOMATIC>
N, CHARGE, SF,8.2,Charge <AUTOMATIC>
 Edit the procedures dictionary (proced.udi) as follows:
# PROCED, Procedure, SI, 4, 36, 14, Y, C:2, L:20
#1, Diagnostic
1, Left Heart Cath , 15, 28
2, Right Heart Cath , 20, 40
The system will automatically start recording time as soon as the clinical user selects a procedure in the Documentation Tool.
As no stop time is available in this example recording ends when the next procedure is selected.
The recording time (in minutes) is then multiplied by the procedure costs per
minute. The resulting cost and/or charge for this procedure appears in the Procedures table in the Documentation Tool and is considered in PRICESUM.
Creating the cluster PRICALC
The PRICALC cluster is required by the system as a list of groups participating in the
cost/charge calculation. It is defined as an output cluster but it also serves systeminternal purposes.
Note
PRICALC is a mandatory cluster that must be defined if you want to set up cost/
charge control in your system.
 Open cathcor.clu for editing.
See Editing clusters 106
 Add the cluster PRICALC.
# O, PRICALC, Cost Control
REFPRICE
CA
PM
ME
PN
PR
392 / 456
AXA5-200.640.07.01.02
System Administration
Setting up Cost and Charge Control
Note
REFPRICE must be the first group in this cluster.
Do not include PRICESUM in this cluster.
If your cath lab works with a QSight material management system, also add the
material usage group to the PRICALC cluster.
# O, PRICALC, Cost Control
REFPRICE
CA
PM
ME
PN
PR
_VMMSUG
Defining data output
Preview of accumulated cost/charge during an ongoing study
In order to be able to preview accumulated costs during an examination you create a study report template specifically for that purpose.
For details about template creation and editing see Report Composer 155.
Defining a cost preview template
 Start Microsoft® Word (Start > Programs > Microsoft Word).
 Select Tools > Report Composer in the Word menu bar.
 Open a template that is easy to clear.
 Remove all tags from the template body.
– Also modify the template header/footer, if you wish.
 Add these labels and field tags:
Reference costs:<%_rPRICESUM.REFCOST%>
Accumulated costs for this study:<%_rPRICESUM.COST%>
Reference charge:<%_rPRICESUM.REFCHARG%>
Accumulated charge for this study:<%_rPRICESUM.CHARGE%>
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
393 / 456
System Administration
 Save the template under a new template name (for example, Cost Control Pre-
view).
 Assign this new report template to all study types for which you want to enable
real-time cost control.
See Defining study types 310.
Previewing cost during the examination
During an examination, clinical users can preview this report in order to check accumulated costs and charges and compare these figures with the reference costs
and charge.
To do so they will proceed as follows:
 Click the Report Generator icon on the Notes subtask card of the Electrophys-
iology or Hemodynamics task card.
 Select the Cost Control Preview report template from the Select Template dia-
log box.
– This cost control report shows all costs (and charges) accumulated during
the current study up to the moment the user clicked Report Generator.
Output of charge information in a study report together with clinical findings
You will usually not want to show internal costs in a study report that may be
handed out to the patient or to a referring physician. Therefore you may want to
include charge information but should not, as a rule, include cost information in
study report templates.
Note
If you define a cost control system after your System Administration has been
in operation for a while, and depending on how the templates were set up, your
study report templates may not include charge information.
These rules apply to study report templates and database updates:
 If a report template contains a cluster and the groups that are referenced in this
cluster contain cost and charge information then this data will be displayed in
the report automatically (you do not have to change the template).
 If you want to hide cost information in the report you must exclude these fields
from output.
See Exclusion of fields for output report clusters 119.
394 / 456
AXA5-200.640.07.01.02
System Administration
Setting up Cost and Charge Control
 If a report template comprises individual groups or fields you will have to up-
date this template to make sure charge information also appears in the final report.
In order to add charge information to existing or new report templates we recommend that you proceed in this way:
 Create an output report cluster
– This cluster should include all cost-relevant groups for a better overview
 Re-insert groups and fields
– Remove existing group tags and insert them again, or edit tags.
 Save the template under a new name
– This will make sure a “clinical findings only” version remains available.
Creating an output report cluster
 Open cathcor.clu for editing.
See Editing clusters 106
 Add a new output report cluster.
# OR, COSTCAL, Cost and Charge
CA
ME
...
PRICESUM
Note
A quick and easy way of doing this is to copy the group list from the PRICALC
cluster definition and remove the REFPRICE and then add the PRICESUM group.
As a result of this cluster definition, cost-relevant groups are now listed separately
in the tag-picker window of the Report Composer.
Re-inserting groups and fields
For details about template creation and editing see Report Composer 155.
 Start Microsoft® Word (Start > Programs > Microsoft Word).
 Select Tools > Report Composer in the Word menu bar.
 Open the template you wish to modify.
– The groups that were inserted before you started cost-control configuration
do not contain cost and charge fields.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
395 / 456
System Administration
 Remove a group from a template and insert it again.
– As you drag the group from the tag-picker window into the report template
area the Insert Group dialog box opens.
 Select Charge as one of the fields you want to show in the report.
Note
Expert users of the Report Composer may find it easier to modify existing group
tables and tags in a template. In order to do so you need to be familiar with the
tag syntax used in the Report Composer and the group and field names used in
your database definition.
See Tag syntax overview 181
Saving the template under a new name
After adding charge information to a report template you might want to save it
under a new template name. This way a report template version with clinical findings only is still available for your clinical users to select.
Saving a report template and handling versions 188
Export of cost/charge information to a HIS/RIS or CIS as
an HL7 message
If the receiving HIS/RIS or CIS expects data to be sent as HL7 messages, you must
configure separate export jobs for these data:
 Clinical study findings (ORUR01 message type)
 Cost data (DFTP03 message type)
In order to define cost data export via HL7, proceed as follows:
 Create an output cluster containing all groups to be exported.
– You can use the same output report cluster for the ORUR01 message and
the DFTP03 message. Only clinical information will be exported from the
included groups in the first message and only cost data will be transferred in
the second message.
For a description of how to create output clusters see Editing clusters 106.
 Define the DFTP03 message
See Create HL7 DFT message 226 for details of parameter settings.
396 / 456
AXA5-200.640.07.01.02
System Administration
Setting up Cost and Charge Control
Export of cost/charge information to a HIS/RIS or CIS as
an ASCII flat file
If the receiving HIS/RIS or CIS expects data to be sent in ASCII flat file format, proceed as follows:
 Create a new output cluster for a transfer job, for example:
# O, BILL, Charge Report
PR, COST
CA, COST
ME
...
PRICESUM
For a description of how to create output clusters see Editing clusters 106
 Define an ASCII flat file transfer job using the predefined “Create HIS Output
file” as a template.
See Transfer HIS output file 223 for details of parameter settings.
Note
AXIOM Sensis XP (VC11)
Please read the details on ASCII flat file outbound messages from the AXIOM
Sensis XP Information System in section Rules for outbound messages
271 before you start transfer job definition.
AXA5-200.640.07.01.02
397 / 456
System Administration
398 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Installation and Update of Report Workstations
The AXIOM Sensis XP cath-lab solution includes an optional software package
which allows installation of AXIOM Sensis XP Information System software on
standard desktop PCs in physicians’ or nurses’ offices. This software package is
called AXIOM Sensis XP Report Workstation (RWS).
Hardware and software requirements
PCs on which the AXIOM Sensis XP Report Workstation is to be installed must
fulfill the following hardware and software requirements.
 Hardware requirements
– Pentium III 700 MHz or higher
– Minimum of 512 MB RAM
– 30 GB hard disk or more, and min. 1 GB of free disk space
– Network connection (Ethernet or WLAN)
– USB port (for dongle option)
– DVD/CD-ROM, 48x speed or higher
 Software requirements
– Windows XP Professional SP3
– Microsoft Office XP Standard Edition 2003 or 2007
– Adobe Acrobat Reader (If the Acrobat Reader is not installed on a PC, you
can download it from www.adobe.com.)
License options
AXIOM Sensis XP Report Workstation (RWS) is available with two alternative license types and various license options.
License options
All AXIOM Sensis XP Report Workstation software options are protected by a liccense. The following licenses are available:
 RWS client package
– Patient Explorer (MIS_BROWSER_CLIENT)
– Report Generator (MIS_REPORTING_CLIENT)
– Documentation Tool (MIS_DATA_ENTRY_CLIENT)
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
399 / 456
System Administration
 Additional license options
– Barcode reader (MIS_BARCODE_READER), as an add-on to the RWS client
package.
– Old Coronary Tree Illustrator (license: MIS_CTR), as an add-on to the RWS client package.
– New Coronary Tree Illustrator (license: MIS_CTI_NEW), as an add-on to the
RWS client package.
– Heart Picture Illustrator (MIS_CHP), as an add-on to the RWS client package.
– Statistics Manager (MIS_QWS), as an add-on to the RWS client package or
for installation on a PC without RWS client package.
– Inventory Manager (MIS_IWS), as an add-on to the RWS client package or for
installation on a PC without RWS client package.
License models
Two alternative types of license are available for software version VC10 and higher:
 Hardware dongle (node locked license)
– For AXIOM Sensis XP Information System installations that run on an ACQ
SIS Master (one AXIOM Sensis XP Acquisition System with AXIOM Sensis
XP Information System server software installed on it) or on a dedicated
server with the Sensis XP Server Package, you will need a dongle for each
desktop PC on which RWS software is to be installed.
– Dongles exist for the parallel port (up to software version VC01E) or USB
port (software version VC03A and higher).
– A license file is supplied with the dongle. The license file enables the purchased software options.
 Floating licenses
– In AXIOM Sensis XP Information System installations with high-end SIS
server, a floating license option is also available.
– With floating licenses, RWS software can be installed on as many desktop
PCs as required. However, only as many clients as software licenses were
purchased can log on to the AXIOM Sensis XP Information System server
concurrently.
Note
If your AXIOM Sensis XP Information System runs on a high-end SIS server you
can also combine these two license models.
For example, you may choose to purchase node locked licenses for the basic
RWS client package but use floating licenses for less frequently used applications
such as Statistics Manager.
Call Siemens Service for support with RWS installations that combine the two license models.
400 / 456
AXA5-200.640.07.01.02
System Administration
Installation and Update of Report Workstations
Prerequisites for Report Workstation installation or update
Do not try to install or update the AXIOM Sensis XP Report Workstation software
package before you have checked the following prerequisities:
Microsoft Word version
 Microsoft Word 2003 or 2007 is already installed on the PC.
– If Word 2007 is installed, make sure MS Office Tools are also installed. If not,
install MS Office Tools first.
Microsoft Windows components
 The Windows Installer Service is enabled.
 The Windows Management Instrumentation (WMI) is installed and enabled.
– Reference WMI: http://msdn.microsoft.com/en-us/library/aa394582.aspx
http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx
http://microsoft.com
 Windows Scripting Host (WSH) is installed and enabled.
– Reference WSH:
http://msdn.microsoft.com/en-us/library/9bbdkx3k(VS.85).aspx
Antivirus software
Note
 The antivirus scan engine is disabled for the duration of the update.
Antivirus software must be stopped as it may script blocking enabled which might
halt the RWS installation or update.
 Contact the vendor of the antivirus software for information on how to disable
and re-enable the virus scan engine.
User privileges
The user who performs the RWS installation or update holds the following rights:
 Full access permission to Windows registry and file system is required during
the installation or update.
– Read/Write permissions to key/subkeys under
HKEY_LOCAL_MACHINE\SOFTWARE\Siemens
 Admin rights to the following folders:
– C:\MIS
– C:\Temp
 Admin rights to the following files:
– C:\Temp\SIS_msi.log
– C:\Temp\SIS_Uninstall.log
– %WINDIR%\ODBC.ini
– %WINDIR%\win.ini
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
401 / 456
System Administration
Environment variable
 The path environment variable includes %SystemRoot%\System32\Wbem.
– This is automatically set if WMI has been installed and enabled correctly.
Auto Log On
 Auto Log On is switched off.
– Information on how to disable Auto Log On on a specific PC must be provided by the local administrator.
– A user name and password are required for manual logon to Windows.
Network ports
 The Report Workstation was working with the Standard SQL ports prior to the
installation or update.
Software installation
Installing Report Workstation software with dongle
License information
In order to be able to install AXIOM Sensis XP Report Workstation software you
must know which options are included in the purchased license package.
 Insert the floppy disk or CD with the license file in your floppy disk drive or CD-
ROM drive.
 Open the file license.dat with WordPad.
 Check and make a note of which of the following license options are available:
– Statistics Manager (MIS_QWS)
– Old Coronary Tree Illustrator (MIS_CTR)
– New Coronary Tree Illustrator (MIS_CTI_NEW)
– Heart Picture Illustrator (MIS_CHP)
– Inventory Manager (MIS_IWS)
 Close WordPad again.
Installing the dongle
 Shut down the computer.
If you have initially purchased the RWS software package with software version
VC01E or earlier:
 Plug the parallel port dongle into the parallel port of the computer.
If you have purchased the RWS software package with software version VC03A or
later:
 Plug the USB port dongle into any free USB port.
402 / 456
AXA5-200.640.07.01.02
System Administration
Installation and Update of Report Workstations
Copying the license file
If you received the RWS license file that came with the dongle on a CD:
 Copy the license file onto the hard disk of the PC and remember the path.
Starting the setup
 Insert the Report Workstation software CD into the DVD/CD-ROM drive.
 Double-click Setup.exe on the CD if setup does not start automatically.
– The RWS Installation Wizard opens.
 Click Next to continue.
 Check the software options that you want to install.
– If you select more options than you have licenses for, these options will not
be installed.
 Click Next to continue.
 Select Node locked license and use Browse to select the license file in the next
installation window.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
403 / 456
System Administration
 Click Next to continue.
– The software is now being installed.
– After a few minutes a message box opens prompting you to reboot the PC
and also reminding you not to remove the installation CD.
 Click Yes to restart the PC.
– After system restart the RWS Installation Wizard informs you that the software has been installed.
 Click Finish to close the installation wizard window.
Installing Report Workstation software with floating license
Preparing the license file on the high-end SIS server
If floating licenses for RWS clients is a new feature in your AXIOM Sensis XP Information System, then the license file on the high-end SIS server needs to be replaced with a new version of this file (one which includes the floating licenses).
If the floating license option is already installed on your high-end SIS server and
you only want to install new RWS clients that use this license option you can skip
this step.
 On the high-end server, open the Windows Explorer.
 Open the folder C:\MIS\Config\Licensing
 Replace the existing license file with the license.dat file you received from Sie-
mens.
404 / 456
AXA5-200.640.07.01.02
System Administration
Installation and Update of Report Workstations
 Open the new license file with WordPad.
– The file includes node locked licenses for the high-end SIS server itself and
the floating licenses for the Report Workstations.
– The floating licenses can be identified by the string _FLT after the license
name, for example:
FEATURE MIS_BROWSER_CL_FLT SAG_med 1.0 permanent 20\
 Search for the first occurence of the following two lines:
– SERVER dummy FLEXID=x-xxxxxxxx TCP:27000
VENDOR SAG_med
 Replace the word dummy with the hostname of the high-end SIS server.
– For example: SERVER SENSIS13999 FLEXID=x-xxxxxxxx TCP:27000
 After Vendor SAG_med add the string PORT=27100.
– VENDOR SAG_med PORT=27100
 Add a # sign at the beginning of all lines in the license file that start with
Server dummy FLEXID=.............. and VENDOR SAG_med
– For example:
#SERVER dummy FLEXID=. . . . . . . .
#VENDOR SAG_med
 Save and close the file.
Checking license information on the high-end SIS server
In order to be able to install AXIOM Sensis XP Report Workstation software you
must know which options are included in the purchased license package.
 On the high-end server, open the Windows Explorer.
 Open the folder C:\MIS\Config\Licensing
 Open the new file license.dat with WordPad.
 Check and make a note of which of the following license options are available:
– Statistics Manager (MIS_QWS)
– Old Coronary Tree Illustrator (MIS_CTR)
– New Coronary Tree Illustrator (MIS_CTI_NEW)
– Heart Picture Illustrator (MIS_CHP)
– Inventory Manager (MIS_IWS)
 Close WordPad again.
Adapting firewall settings
In an RWS installation with floating licenses the information system server and the
Report Workstation PC communicate license information over two fixed network
ports: port 27000 and port 27100. Therefore you need to open these two ports in
the Windows firewall prior to installation.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
405 / 456
System Administration
 Open the Microsoft Windows Security Center.
 Select Windows Firewall under Manage security settings for.
 Select the Exceptions tab card.
 Click Add Port.
 Select TCP.
 Enter FlexLM for the port name and 27000 for the port number and click OK.
 Click Add Port again and also open port 27100 this way.
Starting the setup on the client PC
 Insert the AXIOM Sensis XP Report Workstation software CD into the DVD/
CD-ROM drive.
 Double-click Setup.exe on the CD if setup does not start automatically.
– The RWS Installation Wizard opens.
 Click Next to continue.
 Check the software options you want to install.
– If you select more options than you have licenses for, these options will not
be installed.
406 / 456
AXA5-200.640.07.01.02
System Administration
Installation and Update of Report Workstations
 Click Next to continue.
 Select Floating license in the next installation window.
 Click Next to continue.
– The software is now being installed.
– After a few minutes a message box opens prompting you to reboot the PC
and also reminding you not to remove the installation CD.
 Click Yes to restart the PC.
– After system restart the RWS Installation Wizard informs you that the software has been installed.
 Click Finish to close the installation wizard window.
Configuring connection to the SIS server
Connecting to the SIS server
 Log on to the Report Workstation PC with a user account with administrator
rights.
 Select AXIOM Sensis Information System > Server > Computer Configura-
tion from the Windows Start menu.
 Enter the host name or IP address of the information system server in both the
SQL Server Name and Server Computer Name boxes.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
407 / 456
System Administration
 Click Apply and Test.
 Log on with the MIS_Admin user name and password.
– A message appears that tells you that the connection test was sucessful.
Troubleshooting
If connection to the SIS server failed perform the following checks:
 Make sure network cables are connected.
 Make sure you are logged in as a user with administrator rights.
 Verify that the names you entered as SQL Server Name and Server Computer
Name are the same as the host name of the SIS server, and that the name is
spelled correctly.
 Ping the SIS server:
– Open the command shell (Start > Run).
– Type ping <host name> and press Return.
– Type ping <IP address of the server> and press Return.
– If ping to <host name> is not successful but ping to <IP address> is, then the
SIS server needs to be added to the hosts file.
 To add the SIS server to the hosts file:
– Open the file C:\WINNT\system32\drivers\etc\hosts or C:\WINDOWS\system32\drivers\etc\hosts with NotePad.
– Add the IP address and the host name of your SIS server.
– Perform ping <Host name> again.
408 / 456
AXA5-200.640.07.01.02
System Administration
Installation and Update of Report Workstations
Software update
When an AXIOM Sensis XP Information System server is updated to a new software version, any AXIOM Sensis XP Report Workstation installations in physicians’ or nurses’ offices need to be updated as well. RWS updates are usually
started automatically when a Report Workstation user tries to log on to Patient Explorer for the first time after the server update.
Note
Automatic AXIOM Sensis XP Report Workstation updates require that automatic logon to Windows is turned off on a PC and that the user who logs on to
the PC has administrator rights to this PC.
This section describes the standard (automatic) update process as well as a manual update option, if automatic update fails.
Automatic Report Workstation update
 AutoLogOn has been switched off on your computer.
 You have logged on manually to the Windows operating system.
 The account you have logged on with has administrator rights on this PC.
 Close all programs properly and deactivate the virus scanner.
 Select AXIOM Sensis XP Information System > Client > Patient Explorer
from the Windows Start menu.
– A message box opens that informs you that a new software version of the
AXIOM Sensis XP Information System is available.
– You must install this software in order to be able to continue working with
the information system.
 Click Yes to continue.
– The installation will take several minutes.
– After a while a second message appears that asks you to restart the computer now.
 Restart your computer.
– The installation will not reboot the computer on its own. You as a user will
have to do this.
– After the computer has been restarted and before it prompts you to log on
to Windows again the system completes the update installation.
– When the update is complete you are prompted to log on to Windows
again.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
409 / 456
System Administration
 Open Patient Explorer (Start > AXIOM Sensis XP Information System > Cli-
ent > Patient Explorer).
 Select Help > About and check whether the dialog box shows the new soft-
ware version number.
Manual Report Workstation update
 AutoLogOn has been switched off on your computer.
 You have logged on manually to the Windows operating system.
 The account you have logged on with has administrator rights on this PC.
 Insert the AXIOM Sensis XP Report Workstation software CD in the DVD/CD-
ROM drive.
 Open the Windows Explorer.
 Open the folder RWSUpgradeFromCD on the CD.
 Double-click the file RWSUpgradeFromCD.bat.
– The command shell opens and the system starts executing the update
script.
 Press a key on your keyboard whenever the command shell prompts you to.
– To finalize the software upgrade the upgrade script will reboot the system.
 Open Patient Explorer (Start > AXIOM Sensis XP Information System > Cli-
ent > Patient Explorer).
 Select Help > About and check whether the dialog box shows the new soft-
ware version number.
Note
410 / 456
If both automatic and manual RWS update fails, call Siemens Service.
AXA5-200.640.07.01.02
System Administration
System Administration
Remote Access to the Information System Server
The AXIOM Sensis XP Information System supports Symantec pcAnywhere for remote access to information system server tools for database tailoring and other
administration tasks.
The Symantec pcAnywhere software comprises these system components:
 pcAnywhere host software
– The pcAnywhere host software version 10 and higher is part of the information system server software package.
– It has been automatically installed together with the information system
database and server tools.
 pcAnywhere remote software
– The so-called caller is the client software of the pcAnywhere package.
– It is not part of the scope of delivery of the AXIOM Sensis XP Information
System client package.
– A pcAnywhere caller license (Vs. 10 and higher) must be purchased separately for each PC in your hospital from where you want to access the
AXIOM Sensis XP Information System server.
Installation of the Symantec pcAnywhere
caller
 Make sure you have the correct caller software version (compatible with pcAn-
ywhere version 10 and higher).
 Insert the CD with the correct caller software into the PC from which you wish
to access the information system server.
 Double-click on the installation package icon (pcAnywhere SRS Caller.MSI).
 Follow the instructions of the Symantec pcAnywhere Setup.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
411 / 456
System Administration
Remote access to the information system
server via pcAnywhere
 The Symantec pcAnywhere caller software (Vs. 10.5 compatible) must have
been installed on your PC.
Starting pcAnywhere
 Make sure no study or post-processing session is currently active on any of your
AXIOM Sensis XP acquisition systems or post-processing workstations.
 Select Symantec pcAnywhere in the Windows Start menu of your PC.
– The pcAnywhere Manager dialog box opens.
412 / 456
AXA5-200.640.07.01.02
System Administration
Remote Access to the Information System Server
 Double-click the SIS icon.
 Select your information system server in the next dialog box.
 Enter your Username and Password in the pcAnywhere Host Login dialog
box now.
– If you misspell user name or password you may repeat it three times.
– After you have logged in from your PC the system waits for confirmation of
remote access on the information system server.
 Contact the cath-lab manager and ask him or her to confirm this dialog box for
you.
– The screen of the AXIOM Sensis XP Dialog PC where the information system server is installed or the screen of the AXIOM Sensis XP Information
System server PC is now displayed on your monitor.
– The pcAnywhere title bar and toolbar indicates that you are working on a
different PC via pcAnywhere remote access.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
413 / 456
System Administration
 Call up the DB Manager here using the Windows Start menu, for example.
– Depending on the transmission rate in your network this may take a while,
longer than if you were working directly on the information system server
PC.
Ending a pcAnywhere session
 Close the information system administration tool you were working with prop-
erly via remote access on the server PC.
– For example, exit DB Manager, if this was the server tool you have been
working with.
– If errors or database inconsistencies are reported, it is important that you
solve these problems before you close this application program.
 Click on the pcAnywhere icon in the title bar and select pcAnywhere > End
Session.
 Confirm that you want to end your pcAnywhere session.
– New examinations or post-processing sessions can now be started on the
AXIOM Sensis XP acquisition systems or post-processing workstations in
your cath lab.
Restarting pcAnywhere on an information
system server
On an AXIOM Sensis XP Information System server the pcAnywhere host software
is started automatically when the server starts up or is rebooted.
If the software was stopped for any reason, it can be restarted manually. You
should therefore create a shortcut for this program on the Windows desktop of
your information system server PC.
 Be sure you have logged on to the server as administrator.
 Open the Windows Explorer.
 Open the folder C:\Documents and Settings\All Users\Application Data\pcAny-
where.
 Right-click Siemens Remote Services for SIS and select Create Shortcut.
 Cut the shortcut file and paste it on the Windows desktop.
 Use this shortcut to start PcAnywhere whenever necessary.
414 / 456
AXA5-200.640.07.01.02
System Administration
System Administration
Calculation Methods in the Acquisition System
In this section you will find information about calculation methods and algorithms
used in the AXIOM Sensis XP acquisition system for hemodynamic and vital sign
measurements.
What is calculated and how in hemodynamics mode
Demographic data
If body weight and height are entered, the body surface area (BSA) is calculated in
square metres.
By default the following formula (Dubois and Dubois) is used:
BSA = 0.007184 x W0.425 x H0.725
Note
The formula can be configured in the Parameters Configuration dialog box of
the Configuration Panel of your AXIOM Sensis XP recording systems.
Pressures detected on pressure waveforms
Ventricles
RV, LV
 Systolic pressure (SP)
 Begin diastolic pressure (BDP)
 End diastolic pressure (EDP)
 dP/dtmax
 dP/dtmax
P
Arteries
Regions PA, AO, TRU, DUC, CON, ART, coronary arteries, and user-defined sites for
these regions
 Systolic pressure (SP)
 Diastolic pressure (DP)
 Mean pressure (M)
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
415 / 456
System Administration
Atria and veins
Regions VEN, SVC, IVC, RA, PCW, PVW, PV, LA, and user-defined sites for these regions.
 ”a” wave (if atrial fibrillation occurs, the analysis can be disabled)
 ”v” wave
 Mean pressure (M)
Pulmonic and aortic
valve
and manually combined ventricular and arterial pressures
 Mean systolic gradient
 Systolic pressure difference
 LV (RV) mean systolic pressure
 Systolic ejection duration (SED) (ms/beat)
 Systolic ejection period (SEP)
SEP =
Mitral and tricuspid
valves
SED x HR (s/min)
1000
and manually combined ventricular and atrial pressures
 Mean diastolic gradient
 Diastolic pressure difference
 LV (RV) mean diastolic pressure
 Diastolic filling duration (DFD) (ms/beat)
 Diastolic filling period (DFP)
DFP =
Other manually combined pressures
DFD x HR (s/min)
1000
Pressure difference
Time reference
A time reference must be established to calculate heart rate and select the beats
to be analyzed.
Possible sources for the time reference are listed here in order of priority. The first
one to become available is used:
 LV, end diastolic point
 RV, end diastolic point.
 ART, diastolic point shifted back 20% of the time interval.
 AO, diastolic point shifted back 10% of the time interval.
416 / 456
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
 PA, diastolic point shifted back 10% of the time interval.
 ECG
– In the Pressure Calculation Settings dialog of the Hemodynamics task card
you can decide whether ECG will be the first or the last item in this list of
possible sources for time references.
Note
A pressure channel with a pullback is never used as a time reference.
The time reference points are detected from the first available signal. Time intervals are then calculated between the detected points and the median value of all
intervals is also calculated.
The time intervals within a range of ±25% of the median value are approved for
further investigations.
The time reference sequence is accepted if the approved time intervals cover 75%
of the analysis window or 75% of each of the two parts of a split window. If the
approved time intervals do not meet this 75% criteria, the reference points from
the next available signal in the priority sequence are detected and the procedure
repeated. If no signal fulfills the 75% criteria, the one with the highest coverage
will be used.
The beginning and end points of all approved time intervals are shown as light
blips on the ECG waveform.
The median time interval is converted to heart rate and presented on the screen.
A heart rate of less than 30 or more than 300 is considered physiologically unreasonable and is not used. The words ”BAD TIME REFERENCE” are displayed.
Note
The heart rate in the ”Retrieve - derived data” procedure and in a report is derived
from the last accepted pressure sequence in the appropriate condition.
Beat selection for pressure analysis
For non-pullback pressures, the first eight of the approved time intervals are selected. For pullback pressures, the first eight of all beats on both sides of the transition area are used. The transition area is assumed to be located within the
”opening” between the two windows or, if there is only one window, in the middle.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
417 / 456
System Administration
Ventricular pressures
Systolic pressure, SP
Maximum pressure in the time reference interval. If the pressure is clipped, the
systolic pressure is still measured, but no blip is displayed.
Begin diastolic pressure, BDP
Searching starts at the point where the pressure has decreased to 15% of the systolic pressure. If such a point is not found (diastolic pressure too high), searching
starts where the pressure level is equal to
MIN + 0.15 x (SP - MIN)
where MIN is the minimum pressure in the time reference interval. BDP is defined
as the first point with a dP/dt that is greater than (i.e. less negative than)
-50 mmHg/s.
End diastolic pressure,
EDP
The max. and min. pressure points are detected and measured. An ”intersection
point” is set 25% below the max. point (on the pressure upslope). Another ”intersection point” is set 25% above the min. point (on the pressure downslope). A reference line is ”drawn” between the two intersection points.
EDP is defined as the point on the pressure curve which is farthest from the reference line (measured perpendicular to the reference line). The point is accepted
only if the pressure is above zero and if the slope (dP/dt) is the same as for the reference line.
Quality assessment of
ventricular pressures
If no begin diastolic pressure is found (in the entire sequence) or the difference
between the median systolic and median begin diastolic pressure is 5 mmHg or
less, the entire sequence is not considered a ventricular pressure waveform and
no values are reported.
A systolic pressure for an individual beat greater than 500 mmHg or less than 10
mmHg (2 mmHg for RV) is considered physiologically unreasonable and is not accepted.
A diastolic pressure for an individual beat 150 (100 for RV) mmHg or less than -10
mmHg (-5 mmHg for RV) is considered physiologically unreasonable and is not accepted.
Limits for BDP and EDP:
 BDP LV min/max: -10/150
 EDP LV min/max: 0/150
 BDP RV min/max: -5/100
 BDP RV min/max: 0/100
(See also Parameters Configuration dialog box of the Configuration Panel of your
AXIOM Sensis XP recording systems.)
418 / 456
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
BDP is subtracted from SP for all beats, and the median value of the differences is
computed. All beats that deviate by more than ±15% of the median value are disregarded. This eliminates the influence of PVCs, for example.
Accepted SP, BDP, and EDP points appear as light blips on the Review waveform
card and their median values are presented in the Pressure Calculation Event
Properties dialog box.
Arterial pressures
Systolic pressure, SP
Diastolic pressure, DP
Maximum pressure in the time reference interval. If the pressure is clipped, the
systolic pressure is still measured, but no blip is displayed.
Searching starts 100 ms to the left of the time reference point. A preliminary DP is
defined as the first point where dP/dt is greater than 70 (20 for PA and PVW)
mmHg/s.
An average dP/dt is continuously computed from the preliminary DP to a point
moving forward along the time axis. lf this average dP/dt is greater than 70 (20 for
PA and PVW) mmHg/s until the pressure is midway between the preliminary DP
and systolic pressure, the preliminary DP is accepted. If not, the procedure is repeated with a preliminary DP defined as the second point with a dP/dt greater than
70 (20 for PA and PVW) mmHg/s.
Mean pressure
Quality assessment of
arterial pressures
The median value of the mean pressures for the beats that have been accepted by
the time reference assessment. If no acceptable time reference has been found,
the mean pressure for the entire sequence is calculated, ignoring the analysis window. If pullback is in operation, 20% in the middle of the window is excluded.
If the median systolic pressure and the median mean pressure are less than
10 mmHg (0 for PA and PVW), the entire sequence is not considered an arterial
pressure waveform and no values are reported.
A systolic pressure for an individual beat greater than 500 mmHg or less than 0
mmHg is considered physiologically unreasonable. A diastolic pressure for an individual beat greater than 150 mmHg (100 mmHg for PA and PVW) or less than 0
mmHg is considered physiologically unreasonable. A mean pressure for an individual beat greater than 300 mmHg (200 mmHg for PA and PVW) or less than 10
mmHg (0 mmHg for PA and PVW) is considered physiologically unreasonable and
is not accepted.
DP is subtracted from SP for all beats and the median value of the differences is
computed. All beats that deviate by more than ±15% of the median value are disregarded. This eliminates the influence of PVCs, for example.
Accepted SP and DP points appear as light blips on the Review waveform card and
their median values are presented in the Pressure Calculation Event Properties
dialog. If no usable time references are found, only mean pressure is reported.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
419 / 456
System Administration
Atrial and venous pressures (including PCW)
”a” and ”v” waves
The time interval for each beat is divided in two equal parts and shifted back a distance equal to 30% of the time interval (PCW pressure is first shifted back160 ms).
The ”a” wave is defined as the highest peak found in the first part. The ”v” wave is
defined as the highest peak found between 25 and 75% of the time interval ”t”
(counted from the ”a” wave). If no ”a” wave is calculated, the ”v” wave is the highest peak in the second part of the time interval, shifted back 30%.
Time
reference
a-wave
search
interval
(v-wave
search
interval)
v-wave
search
interval
25%
Note
Mean pressure
75%
Very small peaks are disregarded. If the ”a” (”v”) wave is overranged, neither the
”a” (”v”) wave pressure nor the mean pressure are measured on that beat.
The median value of the mean pressures (during the time-shifted interval) for the
beats that have been accepted by the time reference assessment.
If no acceptable time reference has been found, the mean pressure for the entire
sequence is calculated, ignoring the analysis window. If pullback is in operation,
20% in the center of the window is excluded.
Quality assessment of
atrial and venous pressures
If the ”a” wave, ”v” wave, and mean pressures are equal, the entire sequence is not
considered an atrial waveform and no values are reported.
An ”a” or ”v” wave pressure greater than 100 mmHg or less than 0 mmHg is considered physiologically unreasonable and is not accepted.
A mean pressure for an individual beat over 100 (50 for SVC, IVC and RA) mmHg
or under 0 mmHg is considered physiologically unreasonable and is not accepted.
420 / 456
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
The detected "a" and "v" waves appear as light blips on the Review waveform card
and their median values are presented in the Pressure Calculation Event Properties dialog box.
If no usable time references are found, only mean pressure is reported.
dP/dt and dP/dtmax
For each invasive pressure channel AXIOM Sensis XP automatically calculates the
dP/dt curve, that is the rate of pressure change.
dP/dt curve
dP/dtmax
If the dP/dt curve has not been configured to be shown in a view, use Manage
View to display it. This is possible in either the Hemodynamics application or the
Electrophysiology application.
In pressure calculation events (Hemodynamics application), Sensis calculates
dP/dtmax for ventricular pressures.
dP/dtmax and dP/dtmax (Vpm)
P
Searching extends between the end diastolic pressure point and the systolic pressure point. The maximum values of dP/dt and Vpm are detected.
RV recording
SP
SP
25% down
Reference line
25% up
EDP
BDP
The dP/dtmax value shown in the pressure calculation event properties is the median dP/dtmax of all heart cycles in the analysis window.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
421 / 456
System Administration
Exclusion area
In a pressure calculation a user may choose to exclude sections of the recorded
waveforms from calculation.
Analysis window adaptation
This feature is called “Changing the analysis window” and allows the user to define
exclusion areas (which are displayed gray-shaded) at either end or in the middle
of the pressure calculation snapshot. The system checks whether the remaining
analysis window fulfills the requirements for different pressure curves. The system
will adapt the analysis window slightly if this is not the case, and will not include
the gray-shaded exclusion areas in pressure calculations.
These system adaptations to the analysis window vary depending on the waveform type, whether it is arterial, atrial, or ventricular. This is because the algorithms for analyze the different curve types use different parts of the waveform.
Pullback exclusion area
The exclusion area concept is also used by AXIOM Sensis XP in pullback calculations. Here a waveform area is excluded from calculation to exclude the transition
area in which the waveforms are distorted due to catheter movement.
For pullbacks, an area in the middle of the review screen is therefore automatically
excluded by the system (factory default is 20% of screen width but this can be configured in the Pressure Calculation Settings dialog box).
As it is difficult for the system to determine the actual waveform transition area
precisely, the pullback exclusion area set by the system is merely an estimation.
The user must always check and possibly adjust the pullback exclusion area to the
actual situation in the pressure calculation snapshot at hand.
When the user makes adjustments to the pullback exclusion area, the system may
again adjust these changes slightly according to the principles listed below.
Exclusion area adjustments by the system
 For ventricular curves, up to a whole heart beat after the last visible time refer-
ence in that waveform area are used in analysis
 For arterial curves, 100 ms before the first visible time reference in that wave-
form area is used in analysis
 For atrial curves, 30% of a heart beat before the first visible time reference in
that waveform area is used in analysis.
 If there are several waveforms of different types, then the exclusion areas of
the different curve types are combined to generate the smallest possible exclusion areas.
 If there is one pullback curve and one or more non-pullback curves, then the
pullback exclusion window is shown for all curves. However, it only applies to
the pullback curve. This means that pressure markers will be visible on the nonpullback curves in the exclusion area.
422 / 456
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
Gradients
Valve gradients
If pressure readings from both sides of a valve are available, either simultaneously
from two pressure channels or from a pullback procedure with one catheter, a
valve gradient is automatically calculated.
Other gradients
In addition to this automatic gradient calculation function users may also choose
to have pressure differences calculated between any two points in the heart from
where pressure readings are available during a pressure calculation run. These
readings may again be collected either simultaneously from two pressure channels or in a pullback procedure between sites that are not on both sides of a valve.
Gradients are labeled with the name of the valve, while gradients between other
measurement points are labeled with the two involved catheter sites.
Virtual pullback
The virtual pullback function can be used to calculate gradients between any two
pressure measurements from previously accepted pressure calculation events. In
virtual pullback calculations the same algorithms are used as in real-time pullback
procedures.
Systolic mean gradients across pulmonic and aortic valves and between ventricular and arterial pressures
The starting point of systolic ejection duration (SED) is defined as the point where
ventricular pressure is equal to the arterial diastolic pressure. The length of systolic
ejection duration is defined as 90% of the time between the starting point and the
point where the ventricular pressure downslope reaches the same pressure as the
starting pressure. The systolic gradient is defined as the mean ventricular pressure
during the systolic ejection duration minus the mean arterial pressure during the
same time period beginning at the DP point. This method makes it unnecessary to
time-shift waveforms and is unaffected by false intersections caused by catheter
”flings”. A negative gradient is considered physiologically unreasonable and is reported as 0 (zero).
SED
SED
AO - LV recording
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
423 / 456
System Administration
(1) Diastolic pressure point in aorta (or PA)
(2) Same pressure on LV (or RV) upslope
(3) Same pressure on LV (or RV) downslope
(4) 90% of time interval 2 to 3 is defined as SED
(5) Same time interval applied to aorta (PA) pressure
Diastolic mean gradients across tricuspid and mitral valves and between ventricular and atrial pressures
The diastolic filling duration (DFD) is defined as the longest of the two values computed using the following criteria.
 Starting point of DFD is defined as the point where the ventricular pressure
downslope intersects the atrial pressure (or PCW shifted backwards 160 ms).
End point of DFD is defined as the point where the ventricular pressure upstroke intersects the atrial pressure. If a pullback sequence is in progress, intersections with the mean atrial pressure are used.
 Starting point of DFD is defined as the BDP point. End point of DFD is defined
as the EDP point.
b)
a)
DFD
Intersections Catheter
"fling"
Intersections
BDP
EDP
EDP
BDP
DFD
LA - LV recording
The diastolic gradient is the mean atrial pressure minus the mean ventricular pressure during the diastolic filling duration. A negative gradient is considered physiologically unreasonable and is reported as 0 (zero).
424 / 456
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
Pressure differences
Pressure difference is defined by the type of waveforms for the two pressures.
Type of waveform for one site
Type of waveform for the other site
Atrial
Ventricular
Arterial
Atrial
Atrial mean pressure minus atrial
mean pressure
Atrial mean pressure minus ventricular end
diastolic pressure
Atrial mean pressure minus arterial
mean pressure
Systolic pressure
minus systolic
pressure
Ventricular systolic
pressure minus arterial systolic pressure
Ventricular
Arterial
Systolic pressure
minus systolic
pressure or arterial
mean pressure minus arterial mean
pressure, depending on customization
A negative pressure difference that is found in the automatically initiated valve
gradient measurement is considered physiologically unreasonable and is reported
as 0 (zero).
Pressure differences between manually combined pressures are reported as absolute values, and the catheter site with the highest pressure is always reported first,
independent of the order of entry.
Fractional flow reserve (FFR)
Fractional flow reserve, or FFR, is a technique that helps to determine the physiological significance of coronary lesions. FFR measures the pressure difference
across a coronary artery stenosis during maximum vasodilation. To calculate FFR,
pressure readings from the distal and proximal sites are collected during drug-induced maximum hyperemia. Pressure readings from the distal site are acquired
with a pressure guidewire system.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
425 / 456
System Administration
A pressure guidewire is a thin wire with an electronic pressure sensor at its tip. The
guidewire is so thin that pressures can be measured in the coronary arteries without interfering with the flow, even in the presence of a stenosis. A pressure
guidewire can also be used like a normal guidewire.
The fractional flow reserve (FFR) parameter is a good indication of whether a
stenosis is significant in restricting the blood flow and whether a lesion should be
treated with drugs or interventionally (with a device). FFR is also used to determine which of several stenoses are significant and restrict the blood flow most.
The FFR value is obtained by dividing the coronary mean pressure (CORdistal,
where COR stands a coronary site such as RCA or LCX) distal to the stenosis to be
evaluated, by the mean pressure from the proximal site (CORprox, where COR is a
proximal coronary site or aorta) at maximum hyperemia. The hyperemia condition
is induced by giving a vasodilator drug intravenously or intracardially. The purpose
of vasodilation is to reduce the pressure resistance in the myocardial capillary beds
to isolate the pressure gradient caused by the lesion. The FFR value is the minimum value for the CORdistal/CORprox signal during the analyzed time. An FFR value above 95% means that no treatment is necessary while an FFR value below
75% indicates that treatment is highly recommended. For the 75% to 95% range
there is no clear recommendation and it is up to the physician to decide whether
treatment is necessary or not.
Oxygen saturation
In the oxygen saturation procedure, oxygen saturation values are entered and a
shunt calculation is performed automatically, although manual override (adjustment of parameters) is possible.
Oxygen content
If hemoglobin (Hb) has been previously entered, the oxygen content will be calculated.
The formulas below assume that Hb is entered in g/l. However, the system can be
changed to accept g/100 ml or mmol/l.
O2 Content (ml/l) = O2 Sat
100
O2 Capacity = Hb x 1.36
x O2 Capacity + O2 Dissolved
(ml/l)
If PO2 is entered, O2Dissolved is calculated as:
O2 Dissolved = 0.03 x PO2
426 / 456
(ml/l)
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
If PO2 is not entered, O2Dissolved is derived from oxygen saturation according to
Kelman & Nunn "Nomograms for corrections of blood pO2, pCO2,pH and base excess for time and temperature", J. Appl. Physiol. 1966, 21. 1484 - 1490.
Note
AV O2 Diff
O2 Sat.
%
O2Diss.
ml/l
O2 Sat.
%
O2Diss.
ml/l
O2 Sat.
%
O2Diss.
ml/l
98.0
3.3
92
1.9
70
1.1
97.5
3.0
91
1.8
65
1.0
97.0
2.7
89
1.7
58
0.91
96
2.5
87
1.6
49
0.79
95
2.3
84
1.5
40
0.68
94
2.1
80
1.4
30
0.57
93
2.0
75
1.3
20
0.47
O2Dissolved can be excluded in the Parameters Configuration dialog box of
the Configuration Panel of your AXIOM Sensis XP recording systems and the
O2Capacity formula can be configured there.
AV O2 diff. = SART O2 content - PA O2 content
or, in the presence of a shunt:
Pulm. AV O2 diff. = PV O2 content - PA O2 content
Syst. AV O2 diff = SART O2 content - MV O2 content
The following sites and saturations are used.
 If no shunt is considered present.
– If available: saturations for the sites entered in CO-Fick procedure are used.
– Otherwise: saturations in the following sites will be used.
– As SART: the first (entered) site searching backward from peripheral arteries
to the region PV.
– As PA: the first (entered) site searching backward from peripheral veins to
the region PA.
– The flow directions are defined as in the shunt calculation.
 If a shunt is detected and accepted: sites and saturations are accepted in the
OXY procedure.
Automatic shunt
detection and
calculations
To make a shunt calculation possible, oxygen saturation values from four different
areas are needed:
 Before the right heart
– Mixed venous (MV)
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
427 / 456
System Administration
 After the right heart
– Pulmonary artery (PA)
 Before the left heart
– Pulmonary vein (PV)
 After the left heart
– Systemic artery (SART)
If a genuine value is not available (not entered) for one of the above sites, the system assumes that a value from another site can be used. To reduce the influence
of insufficiently mixed blood as well as inaccuracy in the saturation measurements, some assessment criteria must be fulfilled before a shunt is considered
present. The assumptions and assessment criteria are described below.
The assessment constants (marked with *) are customer-specific and may be different in your system.
Left-to-right shunt
When searching for a left-to-right shunt, the following flow direction is assumed:
From the regions in the greater vessels and heart cavities starting with SVC over
IVC to PA (IVC -> SVC -> RA -> RV -> PA).
Step-up
SVC
RA
Step-down
RV
PA
Lungs
PV
LA
LV
SART
IVC
Right-to-left
Left-to-right
> 9%
> 2%
> 5%
> 3%
Criteria for shunt detection
An L-R shunt is searched for using the following sequence.
1. PA O2Sat. is defined as the saturation in the first site that is found (i.e. the first
site that is entered) searching backward from the region PA to the peripheral
veins.
428 / 456
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
– If saturations from both PA L.Pr and PA R.Pr are entered and the difference is
less than or equal to 5%.
PA O2 Sat =
PA R.Pr O2Sat. + PA L.Pr O2Sat.
2
– If the difference is greater than 5%, no shunt will be calculated. (This will
avoid meaningless shunt detection for patients with Patent Ductus Arteriosus or Left or Right Block Shunt.)
2. Preliminary MV O2Sat. is defined as MV O2Sat.** If unavailable, it is defined as
the lowest saturation in the IVC and SVC regions.
** MV O2Sat. = 3/4 SVCH (or SVC or SVC Low) O2Sat. + 1/4 IVCL (or IVC or IVC High) O2Sat.
Note that the constants (3/4 and 1/4) can be adjusted in the Parameters Configuration dialog box of the Configuration Panel of your AXIOM Sensis XP recordings systems.
3. Prel. MV O2Sat. is subtracted from PA O2Sat. If the difference is > 9%*, a shunt
is considered present. Prel. MV O2Sat. is defined as MV O2Sat. and the search
is interrupted. If the difference is less than the above percentage, searching
proceeds.
4. Preliminary MV O2 Sat. is defined as the lowest saturation in the RA region.
5. Prel. MV O2Sat. is subtracted from PA O2Sat. If the difference is >5%*, a shunt
is considered present. Prel. MV O2Sat. is defined as MV O2Sat. and the search
is interrupted. If the difference is less than the above percentage, searching
proceeds.
6. Prel. MV O2Sat. is defined as the lowest saturation in the RV region.
7. Prel. MV O2Sat. is subtracted from PA O2Sat. If the difference is >3%*, a shunt
is considered present. Prel. MV O2Sat. is defined as MV O2Sat.
If no L-R shunt is considered present, the lowest of the above preliminary MV O2
saturations is defined as MV O2Sat. If no prel. MV O2Sat. is available, MV O2Sat. is
defined as the lowest saturation in the PA region.
Right-to-left shunt
When searching for a right-to-left shunt, the following flow direction is assumed:
PV -> LA -> LV -> AO -> ART.
PV O2Sat. is defined as the first of the following criteria that is fulfilled.
 The highest O2Sat. value in the PV region.
 The saturation in the first site that is found searching forward from LA region
to peripheral arteries provided that the saturation is >96%.
 96%*.
SART O2Sat. is defined as the O2Sat. value at the first site found searching backward from arteries to LA region.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
429 / 456
System Administration
If SART O2Sat. subtracted from PV O2Sat. is >2%*, an R-L shunt is considered
present.
If a shunt is considered present, it will be calculated as follows:
Left to right ratio =
PA O2Cont. - MV O2Cont.
PV O2Cont. - MV O2Cont.
= the fraction of pulmonic flow that flows through the shunt.
An L-R shunt is reported only if the ratio is >0.2*.
Right to left ratio =
PV O2Cont. - SART O2Cont.
PV O2Cont. - MV O2Cont.
= the fraction of systemic flow that flows through the shunt.
An R-L shunt is reported only if the ratio is >0.2*.
If sites for shunt detection are entered manually instead of sbeing elected automatically, shunt calculations are always performed. However, a shunt is reported
only if the above ratio(s) is (are) >0.2*.
Pulm/syst flow ratio =
SART O2Cont. - MV O2Cont.
PV O2Cont. - PA O2Cont.
If Hb is not entered, oxygen saturations are used instead of oxygen contents.
If the blood flow(s) is (are) known (as calculated according to FICK), the shunt
flow(s) is (are) calculated as follows:
Left-to-right shunt flow (l/min) = L-R ratio x Pulm. flow
Right-to-left shunt flow (l/min) = R-L ratio x Syst. flow
Cardiac output
Cardiac output values can either be entered manually or calculated automatically
by the AXIOM Sensis XP software.
Thermo, Dye, Angio
(manual data input)
Cardiac output values can be calculated with a separate thermo or dye dilution
unit or they can be acquired based on angiographic imaging.
If more than one value is entered, an average is computed and reported.
Thermo (automatic calculation)
430 / 456
In principle a thermal dilution procedure is carried out as follows: A thermal indicator (for example, cooled saline) is injected into either the venae cavae or right
atrium. The resultant change in blood temperature is continuously recorded by a
thermistor, mounted on the tip of a catheter at a point downstream, usually the
pulmonary artery. Alternative injection and sampling sites are possible.
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
The cardiac output is then calculated by the following formula:
CO =
VipiCi (Tb -Ti) x 0.82 x 60
pbCb x
∞
 0 ΔDb(t)dt x K
where:
– Vi = Volume of injectant (ml)
– pi = Specific gravity of injectant
– pb = Specific gravity of blood
– Ci = Specific heat of injectant
– Cb = Specific heat of blood
– Tb = Initial temperature of blood (°C)
– Ti = Initial temperature of injectant (°C)
– 0.82 = Empirical correction factor for indicator loss between end and tip of
the catheter
– 60 = 60 seconds/minute
– K = Calibration factor for the curve (°C/mm deflection)
For details see Yang, Bentivoglio, Maranhao, Goldberg, From Cardiac Catheterization Data to Hemodynamic Parameters, 1978, (ISBN 0-8036-9706-6)
Fick
The description assumes that Hb is entered in g/100 ml. However, the system can
be changed to accept Hb in g/l or mmol/l.
Cardiac output is computed using the following formula:
CO (Fick) =
O2consumption
AV O2diff. x 10
(l/min)
or, if a shunt is detected (and accepted) in the OXY procedure
Pulm. blood flow (PBF) =
O2consumption
Pulm.AV O2diff. x 10
(l/min)
Syst. blood flow (SBF) =
O2consumption
Syst.AV O2diff. x 10
(l/min)
where
O2cons. = oxygen consumption in ml/min.
If available, a measured and entered value is used, otherwise a predicted oxygen
consumption is used (see below).
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
431 / 456
System Administration
Note
In case of transposition and some other congenital anomalies (or surgical repairs), the PA O2Sat. is higher than the AO O2Sat. In such a situation, a shunt
most probably exists, but cannot be calculated. Only Systemic AV O2diff. and
Systemic Blood Flow are calculated.
Predicted oxygen consumption:
 Age up to 20 years:
O2 cons. = 1.39 x Height (cm) + 0.84 x Weight (kg) - 35.7
L.G. Krovets and S. Goldbloom, Hopkins Medical Journal, vol. 130, March 1972.
 Age above 20 years:
– Females:
O2 cons. = BSA x (138.1 - 17.04 x elog(age) + 0.378 x HR)
– Males:
O2 cons. = BSA x (138.1 - 11.49 x elog(age) + 0.378 x HR)
LaFarge, C.G. & Miettinen, O.S., 1970, "The estimation of oxygen consumption".
Cardiovascular Research, 4, 23 - 30.
Derived parameters
The following derived parameters are computed in the procedure (measurements, OXY or CO) where the required values become available for the first time
in a condition. If a value is changed, the parameters in question are automatically
recalculated.
Note
Derived parameters are calculated for all available CO methods and presented in
the Hemodynamic Worksheet.
Valve area
Valve area (cm2) =
Cardiac output x 1000
SEP x Const. x 44.5 x
Mean grad.
DFP can be used instead of SEP. Const. = 0.85 for mitral valve and for special gradients with the following site combinations: PCW and LV, PV and LV, LA and LV.
Const. = 1.0 for other valves.
Work and power
Stroke work (J/beat) =
432 / 456
(Mean ventr. syst.pres. - ED pres.) x 133.3 x CO
HR x 1000
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
Stroke work
Body surface area
Stroke work index ((J/beat/m2) =
Stroke power (J/s) =
Stroke work x 1000
SED
Stroke power index (J/s/m2) =
Stroke power
Body surface area
In some systems J (Joule) is converted to gram metres by multiplying by:
1000
9.81
Note
Cardiac index, flow and
stroke volume
Mean ventricular systolic pressure, stroke work, and stroke power are calculated
only in conjunction with valve gradient measurements.
Cardiac index (CI) =
CO
BSA
(l/min/m2)
PBF index =
PBF
BSA
(l/min/m2)
SBF index =
SBF
BSA
(l/min/m2)
Stroke volume =
CO x 1000
HR
(ml/beat)
Pulm. stroke volume =
PBF x 1000
HR
(ml/beat)
Syst. stroke volume =
SBF x 1000
HR
(ml/beat)
If available, the HR entered in a CO procedure is used. Otherwise, the HR from the
last accepted pressure sequence is used.
Stroke volume index =
Resistances
(ml/beat/m2)
Stroke volume
BSA
Pulm. stroke vol. index (ml/beat/m2) =
Pulm. stroke vol
BSA
Syst. stroke vol. index (ml/beat/m2) =
Syst. stroke vol
BSA
Pulmonary arteriolar resistance (PAR):
PAR (dynes x s x cm-5) =
80 x (PA mean pres. - LA mean pres.)
Pulm. flow
Total pulm. resistance (TPR):
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
433 / 456
System Administration
TPR (dynes x s x cm-5) =
80 x PA mean pres.
Pulm. flow
Systemic vascular resistance (SVR):
SVR (dynes x s x cm-5) =
80 x (SART mean pres. - RA mean pres. *)
Systemic. flow
* If no RA pressure is available, 3 mmHg is used.
Total systemic resistance (TSR):
TSR (dynes x s x cm-5) =
80 x SART mean pres.
Systemic. flow
If both PA R.Pr mean pressure and PA L.Pr mean pressure are measured and the
lower of the two is more than 60% of the higher, PA mean pressure is defined as:
PA mean pres. =
PA R. Pr mean pres + PA L. Pr mean pres
2
Otherwise, PA mean pres. is defined as the first available in the regions PA and
PCW (such as PA, PA R.Pr, PA L.Pr, PVW, PVW L.Up, PVW R.Up, PVW L.Lo, PVW R.Lo).
LA mean pressure is defined as the first available in the regions LA and PCW (such
as LA, LA High, LA Low, PCW, PCW Right, PCW Left).
SART mean pressure is defined as the first available from peripheral arteries to region AO (such as ART, ART R.Br, ART L.Br, ART R.Fe, ART L.Fe, AO, AO Asc, AO Arch,
AO Desc).
RA mean pressure is defined as the first available in the RA region.
Note
dynes x s x cm-5 is also called an ”absolute resistance unit” (ARU) which is 80
times the ”hybrid resistance unit” (HRU) in mmHg/(l/min).
PAR Index = PAR x BSA
TPR Index = TPR x BSA
SVR Index = SVR x BSA
Resistance ratios
Total resist. ratio (TPR/TSR):
TPR/TSR =
PA mean pres.
SART mean pres.
x
Pulm./systemic resist.rato (PAR/SVR) =
1
Pulm./Sys. flow ratio
PA mean pres. - LA mean pres.
SART mean pres. - RA mean pres.
x
1
Pulm./Sys.fl.r
If Pulm./Sys. flow ratio (Sys.fl.r) is not known, it is assumed to be 1.
Regurgitation
If cardiac output values from both angio and some other CO method are entered,
the regurgitation values will be calculated. The ”other CO” is for the last accepted
method or, if this is angio CO, the first available of Thermo, Fick and Dye.
Regurgitation fraction =
434 / 456
Angio CO - Other CO
Angio CO
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
Regurg. stroke vol (ml/beat) = Angio stroke vo. - Other stroke vol.
Regurg. stroke vol. index =
Reg. stroke vol
BSA
SpO2 measurement with finger-tip sensor
This section provides background information on SpO2 measurements with finger-tip sensors supported by AXIOM Sensis XP.
SpO2 measurements performed at regular intervals can be monitored and logged
automatically by the AXIOM Sensis XP acquisition system.
Note
Only SpO2 finger-tip sensors produced by Nonin may be used in conjunction
with the AXIOM Sensis XP system.
The following theory of operation applies for these SpO2 measurement devices.
Overview
 The pulse oximeter registers functional saturation of the blood oxygenation.
 The measurement wavelengths are 660 nm (red) and 910 nm (infrared).
 The output power is 3mW nominal each for the red and infrared.
 Pulse oximetry readings are updated with a frequency of 3 Hz.
 The calibration of the pulse oximeter module is interpolated.
 No calibration of the pulse oximetry module and/or sensor is needed.
Oximetry
The pulse oximeter shines red and infrared light through the tissue and detects
the fluctuating signals caused by arterial blood pulses. The ratio of the fluctuation
of the red and infrared light signals received determines the oxygen saturation
content. Conditions such as steady venous blood flow, skin thickness, finger nail
thickness, etc., do not affect the saturation reading because they are constant and
do not cause fluctuations.
The function f depends on the physical properties of the LEDs producing the light.
These physical properties are fixed by the manufacturing material and processes.
SpO2 =

min
ln  ------------- Ree
 max Red
------------------------------------min
ln  ------------- IR
 max
Note that the oximeter's readings do not depend on the absolute light intensity
but on the fluctuations in light intensity. Characteristics such as thick skin or skin
pigmentation will affect the min and max proportionally, so the ratio min/max
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
435 / 456
System Administration
does not change. However, if too little light passes through, the oximeter will not
display values. Pulse oximeters use two different wavelengths of light (red and infrared), providing the ability to determine one component of blood. The oximeter
is calibrated to closely approximate functional oxygen saturation values. These
values will closely approximate laboratory instrument functional saturation values
if the dysfunctional hemoglobin saturation levels are negligible.
In other words, no re-calibration is needed because the oximeter performs all
computations in the internal software and there are no critical parts to drift.
If the dysfunctional hemoglobin is carboxyhemoglobin or methemoglobin, the
difference between the oxygen saturation value displayed by the oximeter and
the oxygen saturation values determined by the laboratory instrument will be
greater, as the dysfunctional hemoglobin levels rise approximately in accordance
with the following formulas:
SpO2 = O2Hb + COHb + MetHb
O2 Hb

SaO2 = 100  ------------------------------------------------------------- 100 – COHb – MetHb
where:
SpO2 = ONYX determined and numerically displayed oxygen saturation in percent.
O2Hb = Fractional oxyhemoglobin saturation in percent
COHb = Carboxyhemoglobin saturation in percent
MetHb = Methemoglobin saturation in percent
SaO2 = Functional oxygen saturation in percent
Averaging
Example 1
Example 2
O2Hb = 96
O2Hb = 88
COHb = 0.5
COHb = 8
MetHb = 0.6
MetHb = 2
SpO2 = 97
SpO2 = 98
SaO2 = 97.07
SaO2 = 97.78
For pulse rates below 112 BPM the averaging calculation is based on a four-beat
exponential average for SpO2 (see below) and an eight-beat sliding average for
pulse rate. For pulse rates above 112 BPM the averaging is doubled and then redoubled above 225 BPM. The oximeter will not include questionable pulses in the
average. Marginal pulses may count less in the average than good pulses.
All averages are updated on a beat-by-beat basis.
436 / 456
AXA5-200.640.07.01.02
System Administration
Calculation Methods in the Acquisition System
With the four-beat exponential average, the effect of each measurement gradually decreases beat by beat. Each measurement initially counts for one fourth of the
average. This weight is decreased by multiplying three fourths on each succeeding
beat:
Beat
Effect (weighting in average)
1
1/4 = 0.250
2
x 3/4 =0.1875
3
x 3/4 = 0.1406
4
x 3/4 = 0.1055
5
x 3/4 = 0.0791
The SpO2 four-beat exponential average is fast enough to follow physiological
changes.
For the pulse rate sliding eight-beat average, each beat counts one eighth for
eight beats and thereafter has no effect on the average.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
437 / 456
System Administration
438 / 456
AXA5-200.640.07.01.02
System Administration
Glossary
In alphabetical order
ACOM
Archiving and Communication
Siemens product family for archiving, image handling and editing, and networking in the cardiology department.
ASCII flat file
Auditing
The AXIOM Sensis XP Information System supports data export as structured ASCII
data.
Concept of the AXIOM Sensis XP Information System security system for tracing
access to patient data and program functions.
Artis
The name Artis represents two product families of Siemens angiography systems.
AXIOM Artis and Artis zee/zeego.
AXIOM Sensis XP
Comprehensive Siemens cath-lab solution comprising the AXIOM Sensis XP Acquisition System and the AXIOM Sensis XP Information System.
AXIOM Sensis XP Acquisition System
Siemens recording system for cardiac cath labs; for hemodynamic and electrophysiological examinations.
AXIOM Sensis XP Information System
Information system for cath lab systems including inventory management and reporting.
AXIOM Sensis XP PostProcessing Workstation
Workstation for post-processing and review of waveform recordings from AXIOM
Sensis XP hemodynamic or electrohysiology examinations.
AXIOM Sensis XP Report Workstation
An optional software package comprising information system tools for data management and reporting. The AXIOM Sensis XP Report Workstation (RWS) software
can be installed on a standard desktop PC in doctors’ or nurses’ offices.
Backup Manager
AXIOM Sensis XP Information System component for starting information system
database backups, scheduling regular database backups, and restoring backed-up
data in case of system failure.
Bar Code Reader
The AXIOM Sensis XP Information System supports bar code scanning to facilitate
data input.
Cathcor
AXIOM Sensis XP (VC11)
Siemens cath lab system for hemodynamic studies
(predecessor system to AXIOM Sensis XP).
AXA5-200.640.07.01.02
439 / 456
System Administration
Central information
system database
CIS
Cluster
Database of the AXIOM Sensis XP Information System for patient and study data.
Cardiology Information System
Collection of database tables (groups).
Clusters are defined for data input and output purposes. Three cluster types exist:
input clusters, output clusters, and output report clusters.
Communication Manager
Configuration platform of the AXIOM Sensis XP Information System for defining
automatic or semi-automatic data transfer to other systems.
Computer Configuration
Configuration platform of the AXIOM Sensis XP Information System for local client
PC configuration.
Condition
AXIOM Sensis XP protocol function that allows subdivision of an examination into
phases or stages.
Configuration Manager
AXIOM Sensis XP Information System configuration platform for the definition of
study types, adjustment of system parameters, and other purposes.
Coronary Tree Illustrator
Software component of the AXIOM Sensis XP Information System; graphical reporting tool for the creation of coronary tree reports.
DB Manager
Database configuration platform of the AXIOM Sensis XP Information System.
Derived data
Derived data are mostly hemodynamic data that were measured or calculated during an examination on the acquisition system.
Dialog Monitor
Monitor on which the user interface of the AXIOM Sensis XP software is displayed.
DICOM
Digital Imaging and Communication in Medicine
An international standard of communication for imaging networks in the hospital;
permits the exchange of medical data between systems.
DICOM report
The AXIOM Sensis XP Information System supports conversion of reports created
by the Report Generator to DICOM report format.
A DICOM report contains the report text as image data and a DICOM header containing information that identifies the patient and study.
440 / 456
AXA5-200.640.07.01.02
System Administration
Glossary
Dictionary
Pick list with predefined entries for selection lists.
Dictionaries used in the Documentation Tool can be edited by the clinical user.
Dictionaries used in any other software components of the AXIOM Sensis XP system can only be edited by a system administrator.
Directory
Concept of the AXIOM Sensis XP Information System user management for grouping patient data and granting access to the data of these patients.
Documentation Tool
Software component of the AXIOM Sensis XP Information System for data entry
and data management of detailed study-specific information.
Electrophysiology application
AXIOM Sensis XP software application for performing electrophysiological studies.
AXIOM Sensis XP is started either with the electrophysiology or the hemodynamics application.
EP
Event
Abbreviation for “electrophysiology”.
Events are bookmarks, pointers referencing a specific time stamp within signal recordings for the purpose of quick retrieval of data and for documenting the examination.
Other user interactions such as, for example, performing pressure calculations,
taking notes, printing out waveforms, or entering data measured on an external
device are also treated as events by AXIOM Sensis XP.
Export Engine
Group
AXIOM Sensis XP Information System background application for executing predefined data export and other jobs.
Database table in the central information system database.
The AXIOM Sensis XP Information System makes a distinction between static
groups (also called system, cath, or non-customizable groups) and customizable
groups.
Group type
Attribute of information system database tables (groups).
The group type attribute differentiates between groups with only one record per
study, multiple records per study, groups for free text entry, and so on.
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
441 / 456
System Administration
Health Level 7 (HL7)
Health Level Seven (HL7) is a standard for electronic data exchange in health-care
environments. HL7 uses standardized messages to exchange certain types of information.
The AXIOM Sensis XP Information System provides an HL7 interface that is used
to send and receive messages in the HL7 2.4 format.
Heart Picture Illustrator
Hemo
Hemodynamics application
HIS
HL7 Listener
Infinity patient monitors
Software component of the AXIOM Sensis XP Information System; graphical reporting tool for the creation of reports on congenital heart defects.
Abbreviation for “hemodynamics”.
AXIOM Sensis XP software application for performing hemodynamic studies. AXIOM Sensis XP is started either with the hemodynamics or the electrophysiology
application.
Hospital Information System
Software component of the AXIOM Sensis XP Information System for data exchange with HIS/RIS or HIS/CIS systems.
A network of patient monitors by Dräger, which can be connected to the AXIOM
Sensis XP Information System and which can provide vital signs data not only from
during the examination but also from the PreCath and PostCath phase.
Inventory Manager
Software component of the AXIOM Sensis XP Information System or inventory
management.
Inventory Manager
database
Local or network database containing inventory management data.
Main database
Database of the AXIOM Sensis XP Acquisition System for patient and study data.
MIS_ADMIN login
AXIOM Sensis XP Information System “super user”. User account with the highest
access rights level to patient data and program functions.
The DB Manager and the Security Manager, for example, can only be accessed by
the MIS_ADMIN “super user”.
Optiflex CL
442 / 456
Departmental material management system by Omnicell that can be connected to
the AXIOM Sensis XP Information System for the purpose of inventory management. An alternative to the AXIOM Sensis XP component Inventory Manager.
AXA5-200.640.07.01.02
System Administration
Glossary
PACS
Picture Archiving and Communication System
Patient Browser
Software platform of the AXIOM Sensis XP acquisition system for handling patient
and study data.
Patient Explorer
Software platform of the AXIOM Sensis XP information system for handling patient and study data.
Patient registration
Entry of patient demographic data and study-relevant information prior to an examination.
Permissions
Concept of the AXIOM Sensis XP Information System user management for granting access rights to patient data.
Preregistration
Entry of patient demographic data and study information prior to the examination.
Privilege
Concept of the AXIOM Sensis XP Information System user management for granting access rights to program functions.
QSight
Departmental material management system that can be connected to the AXIOM
Sensis XP Information System for the purpose of inventory management. An alternative to the AXIOM Sensis XP component Inventory Manager.
Querying
Searching in a database.
Real Time Monitor
Monitor for real-time signal display during an examination.
Remote Monitor(s)
One or two AXIOM Sensis XP monitors in the examination room.
Report Composer
Microsoft Word based solution for study report template configuration.
Report Generator
The semi-automatic reporting tool of the AXIOM Sensis XP Information System.
Report templates
Predefined study report templates that are filled with study data during semi-automatic report generation.
Report templates define how the report will look and what information it will contain.
Retrieval
AXIOM Sensis XP (VC11)
Transferring data from a remote database onto your local system.
AXA5-200.640.07.01.02
443 / 456
System Administration
Review waveform card
RIS
Tab card on the Dialog Monitor for displaying and evaluating acquired events.
Radiology Information System
Role
Concept of the AXIOM Sensis XP Information System user management for efficient handling of access rights to program functions.
Scheduler database
Database of the AXIOM Sensis XP Acquisition System for preregistered patients.
Scope
Attribute of information system database tables (groups).
Groups with scope “patient” contain patient-related data (applicable to all studies
of this patient); groups with scope “study” contain data that refer to individual
studies only.
Security Manager
SQL
AXIOM Sensis XP Information System configuration platform for user management and auditing.
Structured Query Language
A set of commands and statements (language) defined by the DBMS software for
working with data in a database. Several different languages can be used with relational databases; the most common is SQL.
The American National Standards Institute (ANSI) and the International Standards
Organization (ISO) define software standards, including standards for the SQL language. SQL Server 2008 supports the Entry Level of SQL-92, the SQL standard published by ANSI and ISO in 1992. The dialect of SQL supported by Microsoft SQL
Server is called Transact-SQL (T-SQL). T-SQL is the primary language used by Microsoft SQL Server applications.
Statistics Manager
Software component of the AXIOM Sensis XP Information System for the creation
of all types of statistical reports.
Statistics Manager
database
Local database for statistical queries.
Study
A study is an examination that is performed in order to clarify a specific diagnostic
problem.
Study type
A study type represents a typical examination that is frequently performed in your
cath lab in order to clarify a specific diagnostic problem.
Study types help to streamline data input and report output.
444 / 456
AXA5-200.640.07.01.02
System Administration
Glossary
syngo Dynamics
Siemens PACS and reporting system that can be used both as a network archive
and for DICOM image review and reporting in conjunction with an AXIOM Sensis
XP Information System.
Tag
Concept used in report template creation. Placeholder for information to be read
from the database during semi-automatic report generation.
Tag-picker window
Tailor
Use case
User account
User-friendly tag selection window of the Report Composer.
Synonym for DB Manager.
Concept of the AXIOM Sensis XP Information System user management for granting access rights to program functions representing a program function “unit”.
Concept of the AXIOM Sensis XP Information System user management for controlling access rights to patient data and program functions.
Only registered users are permitted to access AXIOM Sensis XP Information System application programs.
User group
Concept of the AXIOM Sensis XP Information System user management for efficient handling of access rights to patient data.
Waveforms
All signals (ECG, ICEG or pressure signals) are graphically displayed as waveforms.
Each waveform is a horizontal tracing which displays a signal as its amplitude varies over time.
Windows backup utility
AXIOM Sensis XP (VC11)
Windows utility functions used by the Backup Manager.
AXA5-200.640.07.01.02
445 / 456
System Administration
446 / 456
AXA5-200.640.07.01.02
System Administration
Index
”a” wave 416, 420
”v” wave 416, 420
A
Ablation curve image (report
templates) 172
Access rights
to patient data 64, 132
to program functions 66, 139
ACK 256
ACKP03 258, 267
Acquisition system
configuration 18
dictionaries 86
main database 19
scheduler database 19
Active version (report template) 188
Administrative_team (user groups) 137
Administrator (role) 140
ADTA01 250
ADTA011 253
ADTA03 252
ADTA04 250
ADTA05 252
ADTA08 248, 249, 252
ADTA23 253
ADTA39 253
ADTA40 253
ADTA44 253
ADTA46 253
ADTA47 254
ADTA49 254
Anatomical sites 328
calculation algorithms 329
new region 330
new site 329
new subregion 330
preconfigured sites 331
Arterial pressure
DP 419
mean pressure 419
quality assessment 419
SP 419
ASCII flat file 52
cost/charge output 397
data export 222
data import 233
inbound messages 268
outbound messages 271
syntax 268, 272
Atrial pressures 420
Audit log 67
archiving 150
AXIOM Sensis XP (VC11)
exporting 150
querying 149
Audit trail 148
Auditing 67, 148
audit everything 148
use cases 148
Automatic value (dictionary) 94
AUTOTIME 104
AV O2 Diff 427
AXIOM Sensis (directory) 133
AXIOM Sensis Configuration Panel 18
AXIOM_Sensis_EP_Hemo (role) 140
B
Backup 67
on tape 70
options 353
protocol 368
scheduling 359
server 70
strategy 70, 353
to backup server 354
to tape 355
Backup Manager
Backup (tab card) 358
database 358
email notification 361
immediate backup 358
include in backup 358
login 357
Notification (tab card) 361
protocol 368
Restore (tab card) 364
scheduling backups 359
View Log 362
Backup server
Configure Network backup 354
Backup strategies
5-day rotation 71
grandparent - parent - child 71
parent - child 71
rotation schemes 356
simple rotation 71
Bar code reader
assigning bar codes 325
communication port 350
configuration 323, 350
enabling dictionaries 324
installing device 350
supported models 323
BAT transfer method) 208
Batch files 54
Beat selection
for pressure analysis 417
Begin diastolic pressure (BDP) 415
Billing configuration 383
AXA5-200.640.07.01.02
Body surface area (BSA) 415
C
Calculation
cardiac index 433
flow 433
regurgitation 434
resistance ratios 434
resistances 433
stroke volume 433
valve area 432
work and power 432
Cardiac output
calculation methods 430
CARTO mapping system image 172
Cath dictionaries 85
Cath groups 101
Cath_lab_manager (role) 140
Cathcor
directory 133
Cathcor.clu 108
Change MIS_ADMIN password (dialog
box) 153
Charge calculation 383
Clusters 35
cluster types 106
configuration workflow 107
definition file 108
editing with DB Manager 106
examples 112
excluding fields from OR
clusters 119
excluding system groups from
reports 113
formatting in report templates 166
HIS transfer 116
HL7 DFTP03 117, 118
included groups 112
including/excluding fields 115
input clusters 114
mandatory fields 112
output clusters 36, 106
output report clusters 36, 106
patient-related data input 114
predefined output report
clusters 164
PRICALC 392
printing cathcor.clu 111
QWS’s disabled groups 119
requested fields 112
syntax 111
system clusters 112
system groups 116
tag syntax (report templates) 181
tags in report templates 164
Code 92
Code length 92
447 / 456
System Administration
Code type 92
Coding scheme
DFTP03 226
ORUR01 229
Coding schemes (HL7) 222
Comma-separated lists (report
templates) 168
Comment text dictionaries 94
Communication 15, 21, 46
Dräger patient monitors 46
HIS/RIS, CIS 49
material management system 57
syngo Dynamics 56
Communication Manager
Application (menu) 191
ASCII flat file 268
basic procedures 191
BAT 208
Config (tab card) 193
content 206
Create DICOM reports 204
Create HIS output file 198
Create HL7 messages 200
Create XML reports 203
data export to HIS/CIS 222
data import to HIS/CIS 233
defining transfer jobs 193
distribution method 207
email reports 238
FAX 208
fax reports 235
FileCopy 209
FTP 209
HL7 210
job description 195
job name 195
job parameters 195
job type 195
Log (tab card) 244
login 192
max. retry 213
NOSEND 213
on failure 213
on success 213
pending jobs 242
predefined transfer jobs 193, 214
PRINTER 211
Queue (tab card) 242
report distribution 214
retry interval 213
Run user-defined BAT file (no output
file) 198
Run user-defined BAT file (output
file) 195
SMTP 212
Study Types (tab card) 310
Transfer HIS output file, reports,
images and waveforms 205
transfer method 208
448 / 456
transfer parameters 195
transfer reports (DOC, RTF, PDF) 203
trigger 207
viewing export log 244
viewing export queue 242
Computer Configuration
Bar Code Reader (tab card) 350
Server (tab card) 349
server connection 349
Condition
derived data in report 179
Configuration (acquisition system) 18
Configuration Manager
Add Dictionary (dialog box) 324
Add Export Mapping (dialog
box) 315
Add Import Mapping (dialog
box) 316
Dictionaries (tab card) 321
editing dictionaries 321
Export Bar Codes 326
HL7 export mapping (dictionary
code) 316
HL7 export mapping (identifier and
text) 316
HL7 import mapping (dictionary
code) 317
HL7 Mapping (tab card) 314
Import Bar Codes 326
Infinity Vital Signs (tab card) 343
Installed Applications (tab card) 320
login 305
new study type 311
Restore All Factory Settings 309
scanning bar codes 325
Service Logbook (tab card) 319
Sites (tab card) 328
structuring dictionaries 321
System Parameters (tab card) 306
Configuration tools 28, 29
Connectivity 15
Consistency check (database) 121
Copyright 14
Coronary Tree Illustrator 21, 41
Coronary Tree Image (report
templates) 172
Cost control 383
Cost/charge control
cost preview template 393
modifying groups/dictionaries 388
output as ASCII flat file 397
output as HL7 message 396
output in study report 394
PRICALC (cluster) 392
PRICESUM (group) 387
REFPRICE (group) 385
Create DICOM reports 204
Create HIS output file 198
AXA5-200.640.07.01.02
Create HL7 DFT message (transfer
job) 226
Create HL7 messages 200
Create HL7 ORU message (transfer
job) 229
Create XML reports 203
CTI (Coronary Tree Image) 172
D
Data exchange
acquisition and information
database 24
Data export
ASCII flat file (HIS) 222
coding schemes (HL7) 222
DFTP03 message output cluster 226
DICOM reports 54
Export Engine 55
export jobs 53
export queue 55
HIS output 53
HL7 messages 54
HL7 standard 222
mapping fields (HL7) 223, 229
ORUR01 message output cluster 229
output cluster 53
output clusters 222
report distribution 214
report transfer 54
to HIS/CIS 222
Transfer Agent 55
XML reports 54
Data flow 23
Data import
ASCII flat file 52, 233
from HIS/CIS 233
HL7 50
HL7 Listener 245
HL7 standard 233
Data input
by study type 38
Data protection 15
Data transfer
ASCII flat file communication 268
configuring HL7 port 245
content 206
defining jobs 193
distribution method 207
HIS/CIS 222, 233
HL7 mapping 314
HL7 messages 250
job description 195
job name 195
job parameters 195
job type 195
max. retry 213
on failure 213
System Administration
Index
on success 213
pending jobs 242
predefined jobs 193, 214
report distribution 214
retry interval 213
settings 195
transfer method 208
trigger 207
viewing export log 244
viewing export queue 242
Database
backup 68
clusters 35
customizing 78
dictionaries 33
fields 32
groups 31
Inventory Manager database 28
key terms 30
release unused space 151
reorganizing 151
Statistics Manager database 28
tailoring 78
Database overview 24
Database table (group) 31
DB Manager 125
acquisition system dictionaries 86
automatic values dictionaries 93
basic procedures 74
Cluster (menu) 106
cluster definition files 108
clusters (examples) 112
comment text dictionary 94
database consistency check 121
database maintenance 123
deleting dictionaries 85
Dic (menu) 78
dictionaries (examples) 92
dictionary definition files 79
Documentation Tool dictionaries 88
editing clusters 106
editing dictionaries 78
editing groups 97
eXit (menu) 121
files on floppy 123
Group (menu) 97
hierarchical dictionary 93
Ix (menu) 126
log files 123
login 76
marking dictionaries 85
new dictionary 83
new field 99
new group 99
printing cathcor.clu 111
printing dictionaries 85
printing group list 101
Procedure (menu) 126
recompiling the database 120
AXIOM Sensis XP (VC11)
renaming fields 100
reserved words 125
rEset (menu) 126
restoring cathcor.clu 110
restoring dictionary 82
restoring rep.grp 101
Run (menu) 120
service functions 125
syntax for cathcor.clu 111
syntax for dictionaries 90
syntax for groups 102
user interface 74
Util (menu) 123
viewing cath dictionaries 85
viewing cath groups 101
Derived data
report templates 179
tag syntax 183
Derived parameters 432
DFTP03 226, 257, 266, 267
coding scheme 226
message output cluster 226
Diastolic filling duration (DFD) 416
Diastolic filling period (DFP) 416
Diastolic mean gradients 424
Diastolic pressure difference 416
DICOM compliance 14
DICOM Image (report templates) 172
DICOM reports 54
Dictionaries
editing in Configuration
Manager 321
enabling for bar codes 324
scanning bar codes 325
Dictionaries (pick lists) 33
a_asit.udi 88
a_site.udi 88
a_view.udi 88
acquisition system 86
admin.udi 88
aetiol.udi 88
automatic values 93
backlib.udi 88
c_acc.udi 89
c_ahas.udi 89
c_cflo.udi 89
c_curv.udi 89
c_dom.udi 89
c_ecc.udi 89
c_ext.udi 89
c_fill.udi 89
c_gra.udi 89
c_graf.udi 89
c_int.udi 89
c_shap.udi 89
c_sit.udi 89
c_tex1.udi 89
c_tex2.udi 89
AXA5-200.640.07.01.02
c_vflo.udi 89
cath dictionaries 85
cathet.udi 88
catlib.udi 88
clusts.udi 88
comlib.udi 88
comment text dictionary 94
compli.udi 88
congen.udi 89
contr.udi 89
corlib.udi 89
ctrsit.udi 89
definition files 79
deleting 85
diagno.udi 89
Documentation Tool 88
ecclib.udi 89
editing with DB Manager 78
emeth.udi 89
epcom.udi 89
eplib.udi 89
epproc.udi 89
esite.udi 89
examples 92
fcolib.udi 89
hetext.udi 89
hierarchical dictionary 93
iesite.udi 89
interv.udi 89, 96
marking 85
medica.udi 90
nc_100.udi ... nc_204.udi 86
nc_ad.udi 88
nc_ist.udi 88
nc_map.udi 90, 96
nc_ref.udi 88
nc_req.udi 88
nc_sty.udi 90
nc_typ.udi 90
nc_wrd.udi 88
new dictionary 83
overview 86
pnname.udi 90, 96
prclib.udi 90
printing 85
proced.udi 90
reclib.udi 90
report.udi 90
reslib.udi 90
restoring 82
sever.udi 90
staff.udi 90
standard dictionary 92
suppl.udi 90
syntax 90
valsta.udi 90
Directories 63, 132
AXIOM Sensis 133
Cathcor 133
449 / 456
System Administration
default directory 146
editing 134
new directory 133
Documentation Tool
dictionaries 88
Dongle
Report Workstation (RWS) 400
dP/dt 421
dP/dt max 415
Dräger Infinity 46
gateway 46
E
Editing
clusters 106
data transfer jobs 193
dictionaries (pick lists) 78
directories 134
free text in report templates 186
groups (database tables) 97
report templates 160
roles 141
study types 310
user accounts 147
user groups 138
Email notification (Backup
Manager) 361
Email reports (configuration
example) 238
End diastolic pressure (EDP) 415
Exam_room_team (user group) 137
Excluding
all system groups from report 165
fields from O clusters 115
fields from OR clusters 119
system groups from reports 113
Export Bar Codes 326
Export Engine 55, 233
Export log 244
Export queue 55, 242
Exporting
audit log 150
EXSYSGRP (system cluster) 113
F
FAX (transfer method) 208
Fax reports (configuration example) 236
FFR (fractional flow reserve) 425
Fields 32
inserting in templates 169
mandatory 112
renaming 100
requested 112
tag syntax (report templates) 183
450 / 456
tags in report templates 169
FileCopy (transfer method) 209
Float values (output in reports) 105
Floating license
Report Workstation (RWS) 400
Floppy disk
exchange database definition 123
Formatting
clusters in report templates 166
groups in report templates 168
report templates 162
FTP (transfer method) 209
G
Gradients 423
Graphical reports 41
Group type 32
Groups (database tables) 31
automatic time entry 104
customizable groups 31
editing with DB Manager 97
field type 105
formatting in templates 168
in report templates 167
new field 99
new group 99
non-customizable groups 31
patient scope 105
PRICESUM 387
printing 101
range control 105
REFPRICE 385
renaming fields 100
rep.grp 97
scope 32, 105
study scope 105
syntax 102
tag syntax (report templates) 182
viewing cath groups 101
H
Health Level Seven (HL7) 50
ACK message 256
ACKP03 message 258, 267
ADTA01 message 51, 250
ADTA011 message 253
ADTA03 message 51, 252
ADTA04 message 51, 250
ADTA05 message 51, 252
ADTA08 message 51, 248, 249, 252
ADTA11 message 51
ADTA23 message 51, 253
ADTA39 message 51, 253
ADTA40 message 51, 253
ADTA44 message 52, 253
AXA5-200.640.07.01.02
ADTA46 message 51, 253
ADTA47 message 51, 254
ADTA49 message 52, 254
coding scheme 226, 229
coding schemes 222
communication port 248
cost/charge output 396
data export 222
data import 233
DFTP03
message 54, 60, 226, 257, 266, 26
7
DFTP03 message output
cluster 117, 118, 226
element length 258
logging messages 249
mapping 314
mapping fields 223, 229
message specifications 250
message types 51
MFKM01 message 257
MFN message 59
MFNM12 message 257
ORMO01 message 52, 254
ORUR01 message 54, 229, 259
ORUR01 message output cluster 229
received messages 247
test message 249
VistA support 248
Heart Picture Illustrator 21, 41
Heart Picture Image (report
templates) 172
Hemodynamics
calculation methods 415
Hierarchical dictionary flag 93
HIS output 53
cluster definition 116
HL7 (Health Level Seven) 50
HL7 (transfer method) 210
HL7 Listener 233, 245
HL7 messages 54
HL7 port (HL7 Listener) 248
HL7.config 318
HPI (Heart Picture Image) 172
I
Import Bar Codes 326
Import preregistered patients via ASCII
flat file (transfer job) 233
Including
all system groups from report 165
fields in clusters 115
Infinity Vital Signs
configure data import 343
Information system concepts
backup and restore 67
System Administration
Index
communication 21, 46
interfaces 46
reporting 21, 40
security 61
study types 38
Information system network 20
Input clusters 36, 106, 114
Installed applications 320
Interfaces 46
Inventory Manager 21
database 28
networking 377
Inventory Manager Configuration
accumulated cost calculation 379
Column Headers (tab card) 382
configuring column labels 382
Connection (tab card) 380
cost calculation 382
database connection 380
iws_db.mdb 377
location of database 377
login 376
mapping table 380
network inventory
management 377
period management 379
setting Order IDs 379
Setup (tab card) 377, 378
user interface settings 378
Inventory_manager (role) 140
iws_db.mdb 377
K
Key terms
database 30
reporting 42
security 62
L
Language (user interface) 14
Line break (dictionary definition) 94
Lock/unlock sections (report
templates) 186
Log files (DB Manager) 123
Log messages (HL7 Listener) 249
LV (RV) mean diastolic pressure 416
LV (RV) mean systolic pressure 416
M
Main database 19
MANDACLU (system cluster) 113
Mandatory fields 112
Mapping fields (HL7) 223, 229
AXIOM Sensis XP (VC11)
Mapping system image (report
templates) 172
Marking (dictionaries) 85
Material management 57
Mean diastolic gradient 416
Mean pressure (M) 416
Mean systolic gradient 416
Membership lists (user accounts) 146
Meta tags 43
MFKM01 257
MFNM12 257
Microsoft® Word 44
MIS_ADMIN (user account) 77, 153
Multi-line fields (report templates) 169
N
Networking
inventory management 377
NOSEND (transfer method) 213
Notepad 75
Nurse (role) 140
O
Operator (role) 140
ORMO01 254
ORUR01 229, 259
coding scheme 229
message output cluster 229
Output clusters 36, 106
DFTP03 message 226
HIS transfer 116
HL7 DFTP03 117, 118
in data export 222
including system group 116
including/excluding fields 115
ORUR01 message 229
QWS’s disabled groups 119
Output report clusters 36, 106
excluding fields 119
predefined clusters 164
Oxygen content 426
Oxygen saturation 426
P
Password
change admin password 153
Patient (scope) 32, 105, 114
Patient Browser
main database 19
scheduler database 19
Patient monitors 46
pcAnywhere 411
AXA5-200.640.07.01.02
PCW 420
Permissions 64
inheriting 136
priority 135
user group 135
user level 135
Pick lists (dictionaries) 33
Predefined blocks
Ablation Curve Image 172
Coronary Tree Image 172
DICOM Image 172
Heart Picture Image 172
Mapping System Image 172
tag syntax (report templates) 183
tags in report templates 171
vital signs 171
waveform images 172
X-ray images 172
Pressure differences 425
Pressure signals
sites 328
Previewing
study reports 187
Print reports when closing study
(transfer job) 220
PRINTER (transfer method) 211
Printing
cathcor.clu 111
dictionaries 85
group list 101
Protocol (backup) 368
Q
QSight 57, 241
Querying
audit log 149
QWS
output cluster 119
R
Range control 105
Received messages (HL7 Listener) 247
Recompiling the database 120
Release unused space (database) 151
Remote access to server 411
Renaming (fields) 100
Reorganizing (database) 151
rep.grp 97
Report
output of decimals 105
Report (scope) 32
Report Composer 21
Application (menu) 157
basic procedures 156
451 / 456
System Administration
cluster tags 164
derived data 179
Edit (menu) 157
field tags 169
Flowsheet (T) 160
formatting clusters 166
formatting templates 162
formatting vital signs graphs 179
Insert Cluster (dialog box) 165
Insert Group (dialog box) 168
inserting a vital signs graph 175
inserting an image 173
lock/unlock sections 186
login 159
Open Template (dialog box) 161
predefined blocks 171
report preview 187
resizing images 175
resizing vital signs graphs 178
Save Template (dialog box) 189
scale settings for vital signs
graphs 176
section breaks 186
Select Study (dialog box) 188
Set Active Template Versions (dialog
box) 190
tag picker window 156
tag syntax 181
template versions 188
user interface 156
Report Generator 21
Report template
referential marker 181
Report templates 44
Ablation 161
ablation curve image 172
active version 188
association to study type 45
cluster tags 164
comma-separated lists 168
Coronary Tree Image 172
derived data 179
derived data by condition 179
DICOM Image 172
editing 160
excluding fields from cluster 166
field tags 169
Flowsheet (C) 160
font settings 163
formatting 162
free text input 186
groups 167
header/footer 162
Heart Picture Image 172
Hemodynamics (1), (2), (3) 160
including system groups 165
inserting sections 186
lock/unlock sections 186
mapping system image 172
452 / 456
multi-line fields 169
page layout 163
patient data 170
predefined blocks 171
predefined output report
clusters 164
report preview 187
save local copy 161
saving templates 188
single-line fields 169
study data 170
Summary 161
Table AutoFormats 168
table styles 168
tag syntax 181
versions 161, 188
vital signs 171
Waveform 161
waveform images 172
X-ray images 172
Report Workstation (RWS)
automatic update 409
dongle 400
firewall settings 406
floating license 400
installation with dongle 402
installation with floating license 404
license options 399
manual update 410
prerequisites for installation 401
server connection 408
Reporting 21, 40
*.dot file 44
by study type 38
Coronary Tree Illustrator 41
graphical reports 41
Heart Picture Illustrator 41
key terms 42
Report Composer 40
Report Generator 40
study types and templates 45
tags 43
template file 44
template formatting 44
Word functions 44
Reports
configuring distribution 214
configuring email transfer 238
configuring fax transfer 235
excluding system groups 113
templates for auto-create 313
REQCLU (system cluster) 113
Requested fields 112
Reserved words 125
Restore 67
database backup 363
import file from server 364, 367
AXA5-200.640.07.01.02
Restore SIS database and Server system
environment 364
Restore Wizard 364, 366
Restoring
cathcor.clu 110
last dictionary version 82
last rep.grp version 101
Roles 65, 139
Administrator 140
AXIOM_Sensis_EP_Hemo 140
Cath_lab_manager 140
editing 141
Inventory_manager 140
new role 140
Nurse 140
Operator 140
Statistics_manager 140
Transcriber 140
Run user-defined BAT file (no output
file) 198
Run user-defined BAT file (output
file) 195
S
Scheduler database 19
Scheduling (backups) 359
Scope 32, 105, 181
Screen saver 62
Section breaks (report templates) 186
Security 61
access to patient data 64
access to program functions 66
auditing 67
directories 63
key terms 62
permissions 64
roles 65
tracing user activities 67
use cases 65
user accounts 63
user groups 64
Security Manager
Application (menu) 130
Audit (tab card) 148
Audit log (tab card) 149
auditing 148
basic procedures 130
change admin password 153
directories 132
Directory (tab card) 133
Group (tab card) 136
Logged in (tab card) 152
login 131
new directory 133
new role 140
new user 146
new user group 137
System Administration
Index
permissions 135
predefined directories 133
predefined roles 140
predefined user groups 137
query audit log 149
Role (tab card) 139
roles 139
Save Audit Log (tab card) 150
set up audit trail 148
Table (tab card) 132
use cases 142
User (tab card) 145
user accounts 145
user groups 136
user management 131
user-defined directories 134
Server
backup server 70
computer name 349
connection 349
remote access 411
Shunt
left-to-right calculation 428
right-to-left calculation 429
Shunt detection
calculation method 427
Single-line fields (report templates) 169
Site Configuration Wizard 354
Sites
calculation algorithms 329
editing in Configuration
Manager 328
new region 330
new site 329
new subregion 330
preconfigured anatomical sites 331
SMTP (transfer method) 212
Software 14
SQL Server Master database 365
SQL Server name 349
Starting scripts 54
Statistics Manager 21
cluster definition 119
database 28
Statistics Manager Configuration
Chart (tab card) 374
Database Server (tab card) 372
default fields 373
Query (tab card) 373
Report (tab card) 375
SQL Log 373
starting 372
Statistics_manager (role) 140
Stored SQL procedures 126
Study (scope) 32, 105
Study report template 44
Study types 38
AXIOM Sensis XP (VC11)
associated input clusters 312
associated report templates 312
available input clusters 312
available report templates 312
editing 310
synchronization with HIS/RIS,
CIS 310
syngo Dynamics integration 56
Syntax
ASCII flat file inbound 268
ASCII flat file outbound 272
clusters 111
dictionaries 90
groups 102
tags in report templates 181
System (scope) 32
System administration
scope of applicability 11
System clusters 106, 112
System communication 15
System database
release unused space 151
reorganizing 151
System documentation
Addenda 13
Online help 13
Operator Manual 12
System Administration Manual 12
System Owner Manual 12
System groups
_ABNORM (Vessel
Abnormalities) 303
_CORONRY (Coronaries) 302
_E_MARKE (Mark Event) 301
_EN2STU (Encounter To Study) 301
_ESTC12 (Stim Cont) 295
_ESTC22 (Stim Cont Off) 295
_ESTD12 (Stim dynamic on) 295
_ESTDY2 (Stim dynamic off) 296
_ESTEX2 (Stim Extra) 295
_FFR (FFR) 277
_GFTARGT (Graft Target) 302
_GRAFDES (Graft Description) 302
_INTRVEN (Intervention) 302
_ITEMUSG (Item Usage) 301
_LESION (Lesion) 302
_M_FFR (Manual FFR) 277
_VESLINF (Vessel Findings) 303
_VMMUSG (Material Usage) 301
ABLGRIMG (Ablation Graph
Images) 297
ACQNAME (ACQ unit computer
name) 276
ALDRSCRE (Aldrete Score) 291
AM (Study measurem.-Area) 283
C_CE (Collateral Entry) 300
C_DE (Dominance Entry) 299
C_GE (Graft Entry) 300
AXA5-200.640.07.01.02
C_HET (Coronary Comments) 299
C_HEX (Coronary variables) 298
C_LE (Lesion Entry) 299
CF (Cardiac output - Fick) 279
CHPD (CHP Diagnoses) 301
CN (Conditions) 276
CO (Cardiac output) 279
CP (Derived parameters) 279
E_ABLAT1 (Ablation On) 296
E_ABLAT2 (Ablation Off) 296
E_ABLAT3 (Ablation Summary) 296
E_BRADY1 (Bradycardia on) 297
E_BRADY2 (Bradycardia off) 297
E_ECG12 (Ecg12Lead) 292
E_INTERV (Interval) 292
E_RECOFF (Recording off) 292
E_RECON (Recording on) 292
E_SNPSHT (Snapshot) 292
E_STIMC1 (Stim Cont On) 294
E_STIMC2 (Stim Cont Off) 294
E_STIMD1 (Stim dynamic on) 294
E_STIMDY (Stim dynamic off) 294
E_STIMEX (Stim Extra) 293
E_TACHY1 (Tachycardia on) 297
E_TACHY2 (Tachycardia off) 297
E_WAVEF (Waveform) 292
EXPPATH (Exported paths) 300
GM (Study measurem.-Grads) 282
GS (Study Summary-Gradient) 283
HL7DATA (Extra HL7 Data) 300
IBP 291
ID (Investigation data) 276
including in output cluster 116
including in report template 165
INFVS (Infinity Vital Signs) 291
IV (Interventions) 276
LCF (Log CO-Fick) 285
LCI (Log Condition) 284
LCO (Log CO) 285
LP1 (Log Single Pressures) 286
LP2 (Log Pullback Pressures) 287
LP3 (Log Valve Gradients) 287
LP4 (Log Special Gradients) 287
LP5 (Log Ventricular Data) 288
LP6 (Log SpO2 and NIBP values) 288
LPA (Log study-area) 288
LPI (Log Study-Intervention) 288
LPM (Time measurements) 289
LPV (Log Pressure Seq.) 286
LSA (Log Saturations) 286
LSY (Log Study-Meas. Serie) 289
MPSYSIMG (Mapping System
Images) 297
NIBP 291
PATCHGS (Patient record
changes) 273
PATIENT (Patient data) 273
PD (Demographic data) 275
PE (Extended HIS date) 276
453 / 456
System Administration
PE (Preregistration date) 276
PI (Case identification) 275
predefined blocks in templates 171
PV (Pressure Values) 276
REC (Case recording) 292
RESP 291
SA (Saturations) 277
SG (Special gradients) 278
SH (Shunts) 281
SM (Study measurem.-single S.) 282
SPO2 (Spo2) 291
SS (Study Sum.- Single Sites) 283
STUDY (Study information) 274
STUDYPIC (Study Pictures) 300
STUDYWF (Study waveforms) 300
T_APLAST (Angioplasty timer) 289
T_CNTDWN (Count down timer) 289
T_CNTUP (Count up timer) 289
T_VPLAST (Valvuloplasty timer) 289
TS (Sample Acquisition times) 284
UN (Units) 276
V_SIGNS (Vital signs) 291
VD (Ventricular data) 277
VG (Valve gradients) 278
VS (Study Summary - 284
XRAY (X-ray scene) 289
XRAYA (X-ray scene) 290
XRAYASUM (Accum. X-ray data) 290
XRAYBSUM (Accum. X-ray data) 291
XRAYSUM (Accum. X-ray data) 290
System messages 15
System parameters
ACQ_CATHETERS 307
ACQ_DRUGS 307
ACQ_TEXTNOTES 307
PATH_AUDIT 307
PREREG_EXPIRED 307
PREREG_EXPIRED_OUTPAT 307
REPORT_AUTOCREATE 307
REPORT_DICOM_HOST 308
REPORT_DICOM_MATCHCRT 308
REPORT_WATERMARK 308
restoring factory settings 309
STUDY_ID_AUTOMATIC 308
STUDY_TIMEOUT 308
STUDY_TYPE_DEFAULT 308
WF_PIC_EXPIRED 309
Systolic ejection duration (SED) 416
Systolic ejection period (SEP) 416
Systolic mean gradients 423
Systolic pressure (SP) 415
Systolic pressure difference (peak
gradient) 416
T
Tag picker (window) 156
Tags 43
454 / 456
cluster 164
derived data 179
fields 169
images 173
predefined blocks 171
syntax 181
vital signs graph 175
Tape (backup) 70
TCP/IP
HL7 Listener 247
Template 44
Test message (HL7 Listener) 249
Third party software 14
Time
automatic time entry 104
Time reference 416
Transcriber (role) 140
Transfer Agent 55
Transfer DICOM reports back to
recording application (transfer job) 214
Transfer DICOM reports over DICOM
network to fix remote node (transfer
job) 218
Transfer HIS output file (transfer
job) 223
Transfer HIS output file, reports, images
and waveforms 205
Transfer HIS output file, reports, images
and waveforms (transfer job) 225
Transfer material usage to material
management system (transfer job) 241
Transfer reports (DOC, RTF, PDF) 54, 203
Truncation length (dictionary) 92
U
Upgrade (menu) 125
Use cases 65
ADM_RunAdmin 142
ADM_RunBackup 142
auditing 148
BR_ChangeStudyState 142
BR_Configuration 142
BR_DeletePatStudRep 142
BR_DeletePreregPatStud 142
BR_EditPatient 142
BR_EditStudy 142
BR_Merge 142
BR_PreregInsertUpdate 142
BR_ResetExpiration 142
BR_SearchPatients 142
BR_StartBrowser 142
BR_UnlockStudy 142
BR_ViewPatient 142
BR_ViewPrereg 142
BR_ViewReport 142
BR_ViewStudy 142
AXA5-200.640.07.01.02
CN_CloseExamination 142
CN_SendClinicalData 142
CN_StartExamination 142
CN_VitalSignsAlarms 143
DE_EditDictionaries 143
DE_StartDataEntry 143
DE_UpdateData 143
RE_CreateReport 143
RE_CreateTemplate 143
RE_EditReport 143
RE_EmailReport 143
RE_ExportReport 143
RE_FaxReport 143
RE_PrintReport 143
RE_ViewReport 143
SICT_RunSICT 143
SOP_CHPStandard 143
SOP_CTIAdmin 143
SOP_CTRStandard 143
SOP_IWS... 143
SOP_QWS... 144
User accounts 63, 145
default directory 146
editing 147
logged-on users 152
member of 146
MIS_ADMIN 153
new user 146
User groups 64, 136
Administrative_team 137
editing 138
Exam_room_team 137
new user group 137
User interface
languages 14
User management 131
access to patient data 132
access to program functions 139
directories 132
permissions 135
roles 139
use cases 142
user accounts 145
user groups 136
V
Venous pressures 420
Ventricular pressure
BDP 418
EDP 418
SP 418
Ventricular pressures
quality assessment 418
Versions
report templates 188
Viewing
cath dictionaries 85
System Administration
Index
cath groups 101
export log 244
export queue 242
VistA support (HL7 Listener) 248
Vital signs (report templates) 171
W
Waveform images (report templates) 172
Windows Backup 364, 366
Word dot file 44
X
XML reports 54
X-ray images (report templates) 172
AXIOM Sensis XP (VC11)
AXA5-200.640.07.01.02
455 / 456
System Administration
456 / 456
AXA5-200.640.07.01.02
System Administration