ZAN HL7 Interface. Installation and Specifications Manual Part Number : *************ENG Version / Revision : A
|
|
- Irma Ramsey
- 8 years ago
- Views:
Transcription
1 Installation and Specifications Manual Part Number : *************ENG Version / Revision : A
2 Disclaimer Information in this manual is subject to change without notice and does not represent a commitment on the part of nspire Health. The software described in this document is furnished under a license agreement. The software may be used or copied only in accordance with the terms of the agreement. It is against the law to copy the software on any medium except as specifically allowed in the license or nondisclosure agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of nspire Health. The software is provided "as is" without warranty of any kind, either expressed or implied including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Some states do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. This warranty gives you specific legal rights and you may also have other rights which vary from state to state. nspire Health does not warrant that the functions contained in the system will meet your requirements or that the operation of the system will be uninterrupted or error free. In no event will nspire Health be liable to you for any damages, including any lost profits, lost savings or other incidental or consequential damages arising out of the use or inability to use such system even if nspire Health or an authorised nspire Health dealer or distributor has been advised of the possibility of such damages, or for any claim by any other party. In the event you should have any claim, whether based on the license agreement, express or implied warranty or otherwise, you agree to accept refund of your money in full satisfaction of your claim. Some states do not allow the limitation or exclusion or liability for incidental or consequential damages so the above limitation or exclusion may not apply to you. Manufactured for Authorized Representative nspire Health Inc 1830 lefthand Circle, Longmont, Colorado, 80501, USA nspire Health Ltd Unit 10, Hartforde Court John Tate Road Hertford, SG13 7NW U.K. nspire Health GmbH, Schlimpfhofer Strasse 14 D Oberthulba Germany Tel: sales@nspirehealth.com Tel: (+44) (0) info@nspirehealth.com Tel: (+49) (+49) zan@nspirehealth.com All brand and product names mentioned in this document are trademarks and/or registered trademarks of their respective holders.
3 Thank you for purchasing the ZAN HL7 interface. The product complies to the newest state of technical development. In order to improve the lifetime of this product, only materials of extremely high quality are used. All materials are environmentally safe and can be recycled. The manual provides instructions for installing and operating ZAN HL7 interface. The instructions in this manual assume the user is familiar with the intended use and application of pulmonary-laboratory systems. Your nspire Health-Team nspire Health GmbH Schlimpfhofer Str Oberthulba/Germany Tel Fax
4 Content Table of Contents 1 SPECIFICATION AND DESCIPTION ABOUT THIS CHAPTER SYSTEM REQUIREMENTS PRODUCT OVERVIEW MESSAGING Definition Messages Overview Messages supported by ZAN NETWORKING SYSTEM ARCHITECTURE Overall Architecture Interface HIS ZanHL7 Service WORKFLOW Patient Information Observation Request Messages (ORM) Measurement and Observation Results MESSAGE AND SEGMENT DESCRIPTIONS Message Descriptions Segment Descriptions APPENDIX ZANHL7 SERVICE INSTALLATION CONFIGURATION OF THE ZAN WORKSTATIONS HIS Interface Waiting Room Options TECHNICAL DESCRIPTION OF THE CONFIGURATION Directory structure (ZanHL7 Service) ZanHL7.cfg (ZanHL7 Service) wingpi.cfg (ZAN Workstations) HL7 TCPIP INSTALLATION CONFIGURATION Architecture (HL7TCPIP) hl7tcpip.cfg (HL7TCPIP) Part No ************ENG.A
5 1 Specification and Desciption 1.1 About this chapter This chapter describes specification and use of the ZAN HL7 software. Specification and Desciption For a description of installation and configuration, cf. document HL7Install.doc. This product is fully integrated with the Microsoft Windows 2000/XP operating systems. This manual does not attempt to be a comprehensive guide for the operating system features. Please refer to your Microsoft Windows documentation for details on these features. 1.2 System Requirements The computer requirements for running the ZAN HL7 Server software are the follow: Intel Pentium III based PC. Microsoft Windows 2000 or higher 1.3 Product Overview ZAN HL7 is a set of components that enables ZAN applications to exchange medical information with hospital information systems (HIS). Overall Architecture WS HIS ZAN HL7 Service ZAN Database ZAN Waiting Room WS WS WS The ZAN HL7 Server is implemented as a Windows Service. This Service can run on one of the Hospital Servers. Normally it is installed on the same PC as the ZAN database and the ZAN waiting room. The HL7 Service communicates between the Hospital Information System (HIS) on the one end, and the PFT laboratory WS (Work-Stations) and all other WS which work with the ZAN software on the other end Part No ************ENG.A
6 Specification and Desciption 1.4 Messaging Definition A message is the atomic unit of data transferred between systems. It is comprised of a group of segments in a defined sequence. Each message has a message type that defines its purpose. For example the ADT Message type is used to transmit portions of a patient s Patient Administration (ADT) data from one system to another. A three-character code contained within each message identifies its type. 1 Message Segment : : Segment A segment is a logical grouping of data fields. Segments of a message may be required or optional. They may occur only once in a message or they may be allowed to repeat. Each segment is given a name. For example, the ADT message may contain the following segments: Message Header (MSH), Event Type (EVN), Patient ID (PID), and Patient Visit (PV1). Each segment is identified by a unique three-character code known as the Segment ID. 1 Segment ID Field 1 : : Field N A field is a string of characters. It consists of one or more components. Field Component 1 : : Component N 1 Health Level Seven, Version 2.3.1, Chapter Part No ************ENG.A
7 Specification and Desciption Example of a HL7 message ORU message (Observation Result Unsolicited) MSH ^~\& ZAN PCS ORU^R01 P 2.4 PID SmiBil Smith^Bill OBR ECG OBX ST Befund Here is the interpretation.^second statement line. R Messages Overview HL7 messages can be classified according to their direction. Incoming messages: HIS ZAN Outgoing messages: ZAN HIS Bidirectional messages: ZAN HIS ZAN Incoming messages are used to send information from the HIS to the client. This information can be: Patient information (patient identification, visit information) Observation request Recognized incoming message types are: ADT, ORM All messages of other types are ignored. Outgoing messages are used to send information from the client to the HIS. This information can be: Observation results (plain text) Medical document (pdf) Outgoing message types are: ORU, MDM Bi-directional messages are used for queries from the client to the HIS. If the HIS supports queries, clients can query the HIS for full patient information given the patient ID number. Bi-directional message types are: QRY/ADR Messages supported by ZAN ADT (Admission, Discharge, Transfer) The Patient Administration transaction set provides for the transmission of new or updated demographic and visit information about patients. Since virtually any system attached to the network requires information about patients, the Patient Administration transaction set is one of the most commonly used. Generally, information is entered into a Patient Administration system and passed to the nursing, ancillary and financial systems either in the form of an unsolicited update or a response to a recordoriented query. 2 2 Health Level Seven, Version 2.3.1, Chapter Part No ************ENG.A
8 Specification and Desciption ADT messages are sent from the HIS to the clients as trigger events. From all possible ADT trigger events, ZAN uses only a subset. All other ADT events are ignored. ZAN uses those ADT trigger events that contain information needed to update its database. ADT trigger events processed by ZanHL7: ADT^A01 admit/visit notification An A01 event is intended to be used for Admitted patients only. An A01 event is sent as a result of a patient undergoing the admission process which assigns the patient to a bed. It signals the beginning of a patient s stay in a healthcare facility. Normally, this information is entered in the primary Patient Administration system and broadcast to the nursing units and ancillary systems. ADT^A02 Transfer a patient An A02 event is issued as a result of the patient changing his or her assigned physical location. ADT^A03 Discharge/end visit An A03 event signals the end of a patient s stay in a healthcare facility. It signals that the patient s status has changed to discharged and that a discharge date has been recorded. The patient is no longer in the facility. When ZAN receives an ADT^A03 message for a patient who was not undergoing any measurements in ZAN systems, this patient is removed from the ZAN database. ADT^A04 Register a patient An A04 event signals that the patient has arrived or checked in as a one-time, or recurring outpatient, and is not assigned to a bed. One example might be its use to signal the beginning of a visit to the Emergency Room. ADT^A08 Update patient information This trigger event is used when any patient information has changed but when no other trigger event has occurred. For example, an A08 event can be used to notify the receiving systems of a change of address or a name change. ADT^A18 Merge patient information The A18 event is used to merge current and previous patient identification numbers. This procedure is required, for example, when a previous patient is registered under a new patient identification number because of an error, or because there was insufficient time to determine the actual patient identification number. The merge event occurs when a decision is made to combine the information under either the new or the old identifier(s) ORM^O01 (general order message) The function of this message is to initiate the transmission of information about an order. This includes placing new orders, cancellation of existing orders, changes in existing orders. The trigger event for this message is any change to an order. Such changes include submission of new orders, cancellations, updates. ZanHL7 uses ORM messages to get information about: - Observation Requests (e.g. CPX, Bodyplethysmography etc.) - Patient information (patient identification, visit information) 5-33 Part No ************ENG.A
9 Specification and Desciption Every ORM message will be processed, the patient information will be read and the patient stored in the ZAN waiting room. The patients from the waiting room are available on every workstation on which the ZAN GPI 3.00 software is installed ORU^R01 (Observational Results Unsolicited) A common use of these transaction sets will be to transmit observations and results of diagnostic studies from the producing system to the ordering system (e.g., HIS order entry, physician s office system). These transaction sets carry information that is reported as text, numeric or categorical values. These messages do not carry the images themselves. The unsolicited mode is used to transmit the values of new observations. It is the mode used by producing services to return the values of observations requested by an ordering system. 3 ZanHL7 uses ORU messages to transmit observation results in alpha-numeric format. Observation results can be observation results as individual numeric values observation results as tabular data observation remarks (annotations, interpretation etc.) MDM^T02 (Medical Document Management) The main purpose of the medical record is to produce an accurate, legal, and legible document that serves as a comprehensive account of healthcare services provided to a patient. The MDM message is similar to the ORU message in that both message types are used to send observation results to the HIS. Whereas ORU messages contain the results data in alpha-numeric format included in the message, MDM messages contain a link to a comprehensive document such as a Word document, an HTML-webfile, an image file, a PDF document, etc. The MDM message type requires 2 additional components: Report-Server PDF converter o Report-Server This is the ZAN Report Server. This component creates HTML files (observation reports) from print jobs. o PDF converter This component converts HTML files (produced by the Report-Server) to PDF files. For every measurement type (Spirometry, Bodyplethysmography, CO-Diffusion, CPX etc.) one or more print templates can be defined. A configuration file defines, what measurement type to assign to what print template(s). Workflow: New measurement completed on any workstation. 3 Health Level Seven, Version 2.3.1, Chapter Part No ************ENG.A
10 Specification and Desciption Store patient file in ZAN database. This simultaneously triggers a data export to the HIS through HL7. Creation of ZAN report (HTML file) by Report-Server. Conversion of ZAN report to PDF file. Creation of MDM message with link to PDF file by ZanHL7 Service. Send message and PDF file to HIS QRY^Q01 / ADR^A19 The following trigger event is served by QRY (a query from another system) and ADR (a response from an Patient Administration system.) An application determines a need for Patient Administration data about a patient and sends a query to the Patient Administration system. The Who Filter in the QRD identifies the patient ID number upon which the query is defined. The HIS responds with an ADR message containing patient administration data. Workflow: Any workstation queries for patient administration data given the patient ID number. ZanHL7 Service converts this request to an HL7 message and sends it to the HIS. If patient administration data is found in HIS for the requested patient ID number, the HIS sends an ADR message to ZanHL7 Service. ZanHL7 Service sends the data back to the workstation that requested the data. The workstation displays the data (and updates the ZAN database if necessary). If patient administration data is not found in HIS for the requested patient ID number, the HIS sends a failure notification to ZanHL7 Service. ZanHL7 Service transfers this failure notification back to the workstation that requested the data. Technical information: ADR^A19 must contain the message-control-id of the QRY^Q01 message. a) Either ADR^A19 and QRY^Q01 have the same message-control-id (MSH-10) OR b) ADR^A19 has a MSA segment with the message-control-id of the QRQ^Q01 message in the MSA- 2 field. Examples a) b) MSH ^~\& MICQRY SAP QRY^Q P 2.2 QRD R I ^RD MA106 DEM MSH ^~\& SAP MICQRY ADR^A P 2.2 QRD R I ^RD MA106 DEM MSH ^~\& SAP MICQRY ADR^A P 2.2 MSA AA P QRD R I ^RD MA106 DEM 7-33 Part No ************ENG.A
11 Specification and Desciption 1.5 Networking The network communication between HIS and ZanHL7 Service can be based on the TCP/IP protocol. file-based using a shared directory. Required components: a. ZanHL7 Service (base component) + HL7TCPIP Service (additional component). b. ZanHL7 Service (base component) only. Recommendation: Wherever possible, the file-based version is the preferred solution. 1.6 System Architecture Overall Architecture HIS ZAN HL7 Service ZAN Database WS WS ZAN Waiting Room WS WS 8-33 Part No ************ENG.A
12 Specification and Desciption The ZAN HL7 Server is implemented as a Windows Service. This Service can run on one of the Hospital Servers. Normally it is installed on the same PC as the ZAN database and the ZAN waiting room. The HL7 Service communicates between the Hospital Information System (HIS) on the one end, and the PFT laboratory WS (Work-Stations) and all other WS running ZAN software on the other end Interface HIS ZanHL7 Service The interface between HIS and the ZanHL7 Service can be a. TCP/IP based or b. file-based. For the TCP/IP based version, an additional component is necessary (HL7TCPIP Service). This bi-directional service converts HL7 message files to network messages and vice versa. Some HIS don't support file-based message transfer. In this case you need the HL7TCPIP message converter. We recommend to use the file-based interface wherever possible TCPIP Based HIS TCP/IP HL7TCP/IP Service File Interface ZanHL7 Service File Based File Interface HIS ZANHL7 Service 9-33 Part No ************ENG.A
13 Specification and Desciption ZANHL7 Service 1. Incoming HL7 messages (HIS ZAN) ZanHL7Service.exe accepts HL7 messages from the HIS through the HIS\Out directory. ZanHL7Service.exe interprets the HL7 message and performs an action depending on the message type. Typically this action is a database action (new or update recordset), or a message sent to ZAN applications (e.g. new waiting room file). 2. Outgoing HL7 messages (ZAN HIS) ZanHL7Service.exe accepts messages from ZAN applications through the GPI\Out directory (e.g. query for patient information given the patient ID number). ZanHL7Service.exe interprets the message, converts it to an HL7 message and writes it to the HIS\In directory. In the TCP/IP based version, HL7TCPIP opens this message and sends it to the HIS. In the file-based version, the HIS opens this message file, performs the appropriate action, and deletes the file. 1.7 Workflow The exact workflow depends upon the capabilities of the hospital information system and the needs and definitions in a special medical environment. Usually measurements begin with the selection of a patient or the selection of an observation request for a patient. This can be done in different ways (cf. below). In very rare cases, patient information must be entered manually, e.g. in cases of emergency, unexpected measurements, or network failure, where patient information is not yet available through the HIS. After the measurements are completed, usually some kind of results report is sent back to the HIS. This can also be configured in different ways Patient Information Patient information can be sent from the HIS to ZAN applications in 3 different ways Observation Request Messages (ORM) Observation requests are created in the HIS and sent to ZAN applications as HL7 ORM messages. These observation requests show up in ZAN applications in the waiting room. Observation request messages contain full patient information. This is the preferred way of receiving patient information Patient Administration Messages (ADT) ADT messages are sent from the HIS to ZAN applications whenever patient information changes. This results in an update or new entry inside the ZAN database. The disadvantage of this procedure is that ADT messages fill up the database very quickly with lots of patient information, many of these patients never being tested in ZAN. The other disadvantage is that there is no list of patients that need to be tested (observation requests) Part No ************ENG.A
14 Specification and Desciption Patient Query (QRY) When the patient ID number is known and the HIS supports queries, patient information can also be received through a patient query. The user enters the patient ID in a ZAN workstation, sends the query to the HIS, and the HIS responds with the full patient information. This method can be combined with both ORM or ADT Measurement and Observation Results Once the patient information is available, the measurements can be performed in the ZAN system in the usual way (cf. manuals of ZAN applications). After some or all measurements are completed, the user stores the patient file (including all his/her measurements) to the archive (cf. manual of ZAN wingpi). At this moment, the observation results will be created and sent to the HIS. 1.8 Message and Segment Descriptions Message Descriptions Incoming messages The following section describes required and option segments for incoming HL7 messages. Required segments are put in plain text. Ex: MSH Optional segments are put in brackets. Ex: [PV1] ADT ADT^A01 ADT^A02 ADT^A03 ADT^A04 ADT^A08 ADT^A18 ADT^A19 ADR^A19 MSH, PID, PV1 MSH, PID, PV1 MSH, PID MSH, PID, [PV1] MSH, PID, PV1 MSH, PID, MRG MSH, [MSA], PID, [PV1], [STF] MSH, [MSA], PID, [PV1], [STF] Part No ************ENG.A
15 Specification and Desciption ORM^O01 MSH, PID, PV Outgoing messages The following section describes the segments in ZAN generated HL7 messages. ORU MDM QRY MSH, PID, PV1, ORC, (OBR, OBX) n MSH, EVN, PID, PV1, TXA MSH, QRD Part No ************ENG.A
16 Specification and Desciption Segment Descriptions For outgoing messages, the remarks column contains the content of the field, filled in by the ZAN HL7 application. This is indicated by the word (outgoing). MSH SEQ LEN OPT ELEMENT NAME REMARKS 1 1 R Field Separator 2 4 R Encoding Characters ^~\& 3 15 O Sending Application ZAN (outgoing) 4 20 O Sending Facility ZAN (outgoing) 5 30 O Receiving Application configurable (outgoing) 6 30 O Receiving Facility 7 26 O Date/Time Of Message 8 40 O Security 9 7 R Message Type R Message Control ID a random number (outgoing) 11 3 R Processing ID P (outgoing) 12 8 R Version ID 2.4 (outgoing) O Sequence Number O Continuation Pointer 15 2 O Accept Acknowledgment Type 16 2 O Application Acknowledgment Type 17 2 O Country Code EVN SEQ LEN OPT ELEMENT NAME REMARKS 1 3 B Event Type Code 2 26 R Recorded Date/Time PID SEQ LEN OPT ELEMENT NAME REMARKS 1 4 O Set ID - PID 3 20 R Patient Identifier List R Patient Last Name O Patient First Name 7 26 R Date/Time of Birth 8 1 R Sex male: M, m female: F, f, W, w O Patient Address O Phone Number - Home O Marital Status O Birth Place 24 1 O Multiple Birth Indicator Part No ************ENG.A
17 Specification and Desciption PV1 SEQ LEN OPT ELEMENT NAME REMARKS 1 4 O Set ID - PV O Assigned Patient Location 6 80 O Prior Patient Location 12 1 O Preadmit Test Indicator R Visit Number O Servicing Facility O Admit Date/Time TXA SEQ LEN OPT ELEMENT NAME REMARKS 1 4 R Set ID- TXA Message Control ID (outgoing) 2 30 R Document Type CN (outgoing) 4 26 O Activity Date/Time R Unique Document Number Document Number^ZAN (outgoing) O Unique Document File Name Document File Name (outgoing) ORC SEQ LEN OPT ELEMENT NAME REMARKS 1 2 O Order Control 2 75 R Placer Order Number 3 75 O Filler Order Number 9 26 O Date/Time of Transaction O Entered By O Ordering Provider O Enterer s Location O Order Effective Date/Time Part No ************ENG.A
18 Specification and Desciption OBR SEQ LEN OPT ELEMENT NAME REMARKS 1 4 O Set ID - OBR 2 75 C Placer Order Number 3 75 C Filler Order Number R Universal Service ID 5 2 B Priority 6 26 B Requested Date/time 7 26 C Observation Date/Time # 8 26 O Observation End Date/Time # 9 20 O Collection Volume * O Collector Identifier * 11 1 O Specimen Action Code * O Danger Code O Relevant Clinical Info C Specimen Received Date/Time * O Specimen Source * O Ordering Provider O Order Callback Phone Number O Placer Field O Placer Field O Filler Field O Filler Field C Results Rpt/Status Chng - Date/Time O Charge to Practice O Diagnostic Serv Sect ID 25 1 C Result Status O Parent Result O Quantity/Timing O Result Copies To O Parent O Transportation Mode O Reason for Study O Principal Result Interpreter O Assistant Result Interpreter O Technician O Transcriptionist O Scheduled Date/Time O Number of Sample Containers * O Transport Logistics of Collected Sample * O Collector s Comment * O Transport Arrangement Responsibility O Transport Arranged 42 1 O Escort Required O Planned Patient Transport Comment O Ordering Facility Name O Ordering Facility Address O Ordering Facility Phone Number O Ordering Provider Address Part No ************ENG.A
19 Specification and Desciption OBX SEQ LEN OPT ELEMENT NAME REMARKS 1 10 O Set ID - OBX 2 3 C Value Type R Observation Identifier 4 20 C Observation Sub-ID C Observation Value 6 60 O Units 7 60 O References Range 8 5 O Abnormal Flags 9 5 O Probability 10 2 O Nature of Abnormal Test 11 1 R Observ Result Status O Date Last Obs Normal Values O User Defined Access Checks O Date/Time of the Observation O Producer's ID O Responsible Observer O Observation Method QRD SEQ LEN OPT ELEMENT NAME REMARKS 1 26 R Query Date/Time 2 1 R Query Format Code R (outgoing) 3 1 R Query Priority I (outgoing) 4 10 R Query ID Message Control ID (outgoing) 7 10 R Quantity Limited Request 1^RD (outgoing) 8 60 R Who Subject Filter Patient ID Number (outgoing) 9 60 R What Subject Filter DEM (outgoing) MRG SEQ LEN OPT ELEMENT NAME REMARKS 1 20 R Prior Patient Identifier List Prior Patient ID 2 20 O Prior Alternate Patient ID 3 20 O Prior Patient Account Number 4 20 O Prior Patient ID 5 20 O Prior Visit Number 6 20 O Prior Alternate Visit ID 7 48 O Prior Patient Name MSA SEQ LEN OPT ELEMENT NAME REMARKS 1 2 R Acknowledgment Code 2 20 O Message Control ID 3 80 R Text Message 4 15 O Expected Sequence Number 5 1 O Delayed Acknowledgment Type O Error Condition Part No ************ENG.A
20 Specification and Desciption STF SEQ LEN OPT ELEMENT NAME REMARKS 1 60 R Primary Key Value - STF 2 60 O Staff ID Code 3 48 O Staff Name 4 2 O Staff Type 5 1 O Sex O Phone O Office/Home Address 1.9 Appendix What are visit numbers? A patient being "admitted" is undergoing the admission process which assigns the patient to a bed. This is the beginning of a patient s stay in a healthcare facility. The span from the account s start until its end is called a visit. A hierarchy of identifiers exists between person, patient, account, and visit. The hierarchy is as follows: Level 4 - Person (identified by PID-2-patient ID) Level 3 - Patient (identified by PID-3-patient identifier list) Level 2 - Account (identified by PID-18-patient account number) Level 1 - Visit (identified by PV1-19-visit number) The visit-level identifier PV1-19-visit number is the lowest level identifier and is considered subordinate to the account-level identifier PID-18-patient account number. This means that visit identifiers are defined within the context of an account identifier, and implies that visit identifiers are unique within account identifiers. Similarly, account identifiers are subordinate to, and unique within, patient identifiers; patient identifiers are subordinate to, and unique within, person identifiers. Conversely, the person-level identifier PID-2-patient ID is the highest level identifier and is considered superior to the patient-level identifiers, which are superior to the account-level identifier, which is superior to any visit-level identifiers. 4 4 Health Level Seven, Version 2.3.1, Chapter Part No ************ENG.A
21 Installation 2 ZanHL7 Service 2.1 Installation 1. Go to the server where you want to install the HL7 Service, and run the application ZANHL7Install.exe 2. Accept the default installation path, unless you have a reason to install in a different folder. 3. Configure the HL7 base component Part No ************ENG.A
22 Installation 3.1. ZAN Patient ID-Nr The ZAN Patient ID-Nr can be created in different ways: - automatically using last name, first name and birthday to create a 12 sign ID-Nr. - automatically counting 1,2,3, - manually In a HIS environment, every patient has 2 ID numbers: the ZAN Id-Nr and the HIS Id-Nr. These ID numbers can be the same or they can be different. Available options: - Use HIS Id-Nr If you select this option, ZAN Id-Nr. and HIS Id-Nr will be the same. This is only possible when the HIS Id-Nr. has 12 signs or less. - Create ZAN Id-Nr If you select this option, ZAN will create its own Id-Nr using the method wingpi.cfg. Both Id numbers are visible in the patient pane of wingpi. The preferred option is: Use HIS Id-Nr wherever possible Directories - Interface to HIS This is the directory that ZanHL7 shares with the Hospital Information System. Both applications need read/write access to this directory. If you also use ZANHL7TCPIP, ZanHL7 shares this directory with ZANHL7TCPIP. - Interface to GPI This is the directory that ZanHL7 shares with the ZAN workstations. ZanHL7 and all ZAN workstations need read/write access to this directory. - Database This is the ZAN database directory. ZanHL7 and all ZAN workstations share this database. The database directory must be configured when using the ADT option. - Waiting Room This is the ZAN waiting room directory. ZanHL7 and all ZAN workstations share the waiting room. The waiting room directory must be configured when using the ORM option Messages Here you can enable or disable the available message types of the ZanHL7 Service. Some message types have a details button. - ADT details Check or uncheck the used ADT trigger events. - MDM details ZAN Report-Server: Enter or browse for the ZAN Report-Server application. Medical Documents Path: Enter or browse for the folder the ZanHL7 shares with the HIS for export of medical documents. 4. Autorun Normally the ZanHL7 Service should start up with the PC. This can be achieved in 2 ways: Part No ************ENG.A
23 Installation 4.1. Run ZanHL7 as a Windows Service - To install ZanHL7Service.exe as a Windows Service, you can use the file "ZanHL7 Service Install.bat" in the ZANHL7 folder. When you run this file, ZanHL7Service.exe will be installed as a Windows Service. - After installing ZanHL7Service.exe as a Windows Service, open the services administration window and edit the properties of ZAN HL7 Service: Change the start type to "automatic" Part No ************ENG.A
24 Installation In the logon tab you can select the account under which the service will run. Be sure that this account has read/write access privileges for the ZANHL7\HIS folder and subfolders! 4.2. Run ZanHL7 as a Windows Application If for any reason you don't want to run ZanHL7 as a Windows Service, you can also run it as a windows application. In this case create a shortcut to "ZANHL7\ZanHL7Service.exe debug" in your startup folder. Be sure that this account has read/write access privileges for the ZANHL7\HIS folder and subfolders! The disadvantage of running ZanHL7 as a Windows application is that the application will only run when this user is logged on. 2.2 Configuration of the ZAN Workstations Go to every workstation with ZAN software and activate HL7. To do this, open wingpi and click on the Setup button. In the ZAN Settings program, open menu System-HL7: Part No ************ENG.A
25 Installation Configure HL7 in this dialog: HIS Interface This is the interface directory that all workstations share with the ZanHL7 service. It should be located on the PC where ZanHL7 service is running. All workstations and the ZanHL7 service need read/write access privileges for this folder and subfolders! Waiting Room The waiting room must be enabled when ORM messages are used. This directory is shared from all workstations and the ZanHL7 service. It should be located on the PC where ZanHL7 service is running. All workstations and the ZanHL7 service need read/write access privileges for this folder! Options Show HIS Patient-ID and Visit Number Patient ID number in HIS and ZAN can differ (cf. 1.1 Installation chapter 3.1: ZAN Patient ID-Nr). Also some HIS support HL7 visit numbers, others don't. When this option is enabled, HIS Patient Ids and Visit Numbers will be visible in the patient pane in wingpi Part No ************ENG.A
26 Installation Query for patients through HIS Check this option if you want to use queries. The HIS must support queries and the QRY message type must be enabled in the ZanHL7 service. With Queries you can search for patient information in the HIS given the patient Id number. This is described in the ZanHL7 guide chapter Enable ORU messages Check this option if you want to export observation results (ORU) to the HIS. The ORU message type must be enabled in the ZanHL7 service (cf. 1.1 Installation chapter 3.3: Messages) Enable MDM messages Check this option if you want to export medical documents (MDM) to the HIS. The MDM message type must be enabled in the ZanHL7 service (cf. 1.1 Installation chapter 3.3: Messages). 2.3 Technical Description of the Configuration Directory structure (ZanHL7 Service) This installation program ZanHL7Install.exe will create this directory structure on the server: Part No ************ENG.A
27 Installation The folder ZANHL7 is the main folder. Content: - ZanHL7Service.exe - ZanHL7.dll, ZanHL7BDE.dll (Extensions to ZanHL7Service.exe) - ZanHL7.cfg (Configuration file) The folder GPI is the file interface to the ZAN workstations. The ZanHL7 Service and all workstations need read/write access to this folder and subfolders. - GPI-In is used for messages from ZanHL7 to the workstations. - GPI-Out is used for messages from workstations to ZanHL7. The folder HIS is the file interface to a) the Hospital Information System OR b) the ZanHL7TCPIP service, if installed. The ZanHL7 Service and the HIS (or ZanHL7TCPIP) need read/write access to this folder and subfolders. - HIS-In is used for HL7 messages from ZanHL7 to the HIS (or ZanHL7TCPIP). - HIS-Out is used for HL7 messages from HIS (or ZanHL7TCPIP) to ZanHL7. - HIS-Delayed stores messages that cannot be handled immediately (e.g. because the patient is opened on a workstation) temporarily. - HIS-Unhandled saves all HL7 messages that could not be handled by ZanHL7 for any reason. All unhandled messages have an entry with detailed description in the log file ZANHL7\ZanHL7.log Part No ************ENG.A
28 2.3.2 ZanHL7.cfg (ZanHL7 Service) Installation Normally you need not edit the ZanHL7.cfg configuration file. Most entries can be edited through the configuration tool config.exe (cf. 1.1 Installation chapter 3: cf. 1.1 Installation chapter 3.1: ZAN Patient ID-Nr). The following is a technical description for extended needs. [system] Server= Defines special HIS (e.g. Siemens-Medico, SAP, ). Unless you have a special HIS, use UNDEF. [ZID] Configuration of Patient ID numbers ZID= In a HIS environment, every patient has 2 ID numbers: the ZAN Id-Nr and the HIS Id-Nr. These ID numbers can be the same or they can be different. Available options: ZID=LID ZAN Id-Nr. will be copied from the HIS Id-Nr. This is only possible when the HIS Id-Nr. has 12 signs or less! ZID=AUTO The ZAN Id-Nr will be created automatically using last name, first name and birthday to create a 12 sign ID-Nr. FillZero=YES NO If ZID=AUTO and FillZero=YES, the ZAN Id-Nr will be padded with zeros to the left. ZeroCount=0 12 If ZID=AUTO and FillZero=YES, the ZAN Id-Nr will be padded with ZeroCount zeros to the left. UpperCase=YES NO Makes ZAN Id-Nrs upper case. [HIS] Configuration of the interface to HIS Dir_In= Used for HL7 messages from ZanHL7 to the HIS (or ZanHL7TCPIP). Dir_Out= Part No ************ENG.A
29 Installation Used for HL7 messages from HIS (or ZanHL7TCPIP) to ZanHL7. Dir_Unhandled= All HL7 messages that could not be handled by ZanHL7 for any reason are saved to this folder. Dir_Delayed= All messages that cannot be handled immediately (e.g. because the patient is opened on a workstation) are temporarily stored in this folder. Messages= Enabled message types in ZanHL7 service. [ADT] Configuration of ADT messages Messages=A01,A04,A08,A18,A19 If [HIS] Messages contains the ADT message type, [ADT] Messages defines the ADT trigger events. [MDM] Configuration of MDM messages ReportConfig= Special Report.cfg that defines report templates. ReportPath= Directory in which the ZAN Report-Server is located. ReportServer= File name of the ZAN Report-Server. MedDocPath= Directory for Medical Documents. ZanHL7 service and HIS both need read/write access to this directory. MedDocFileNameType= Naming convention of the PDF file. 0=increasing number, 1=LID_YYYYMMDD_HHMM (patient id + date) 2= increasing number_ztmname (ztmname from ZanHL7Report.cfg [Names]) ORC=YES NO Part No ************ENG.A
30 Installation Defines whether a ORC segment should be added (exports Placer Order Number). [GPI] Configuration of the interface to workstations ZanHL7 and all ZAN workstations need read/write access to these directories. Dir_In= Used for messages from ZanHL7 to the workstations. Dir_Out= Used for messages from workstations to ZanHL7. Archiv=C:\ZAN\GPI200\Archiv The ZAN database directory. Wartezimmer=C:\ZAN\GPI200\WARTEN The ZAN waiting room directory wingpi.cfg (ZAN Workstations) Normally you need not edit the wingpi.cfg configuration file. Most entries can be edited through ZAN Settings program (cf. 1.2). The following is a technical description for extended needs. [HL7] Enable=YES NO Enable/Disable HL7 in wingpi. InPath=C:\ZANHL7\GPI\In Used for messages from ZanHL7 service to ZAN workstations. OutPath=C:\ZANHL7\GPI\Out Used for messages from ZAN workstation to ZanHL7 service. ShowLIDCN=YES Visibility of HIS Patient Ids and Visit Numbers in the patient pane in wingpi (cf ). Query=YES NO Support for patient queries (cf ) QueryEx=YES NO Support for extended patient queries: update patient information in wingpi from HIS query result Part No ************ENG.A
31 Installation QueryFillZero=YES NO Pad patient ID numbers with ZeroCount zeros to the left in the query definition that will be sent to the HIS. ORU=YES NO Enable/Disable ORU messages in wingpi. MDM=YES NO Enable/Disable MDM messages in wingpi. [idnr] Section for patient ID number definitions autoid=on OFF Defines creation of ZAN ID numbers: automatic or manual entry. Should be OFF when using HL7. FillZero=YES NO Pad ZAN ID numbers with zeros to the left. ZeroCount=12 If FillZero=YES, the ZAN Id-Nr will be padded with ZeroCount zeros to the left. SearchCaseSensitive=YES NO Patient query from ID-Nr in HIS case sensitive/insensitive Part No ************ENG.A
32 Installation 3 HL7 TCPIP 3.1 Installation 1. Assure that you have already installed the HL7 Service (cf. Chapter 1: ZanHL7 Service). 2. Go to the server where you have installed the HL7 Service, and run the application HL7TCPIPInstall.exe 3. Accept the default installation path, unless you have a reason to install in a different folder. 4. Configure the HL7 TCP/IP interface Part No ************ENG.A
33 Installation 4.1. ZAN HL7 Service - HIS directory This is the directory that ZANHL7TCPIP shares with ZanHL7 Service for message exchange Components ZANHL7TCPIP consists of 2 components: - Query (QRY) - Listener (ADT, ORM) Each component has its own TCP/IP connection. Each TCP/IP connection needs configuration: Client-/Server-mode, Port (Socket), IP-Address. 5. Autorun Normally the HL7 TCPIP Service should start up with the PC. This can be achieved in 2 ways: 5.1. Run HL7 TCPIP as a Windows Service - To install HL7TCPIPService.exe as a Windows Service, you can use the file "HL7TCPIP Service Install.bat" in the ZANHL7 folder. When you run this file, HL7TCPIPService.exe will be installed as a Windows Service. - After installing HL7TCPIPService.exe as a Windows Service, open the services administration window and edit the properties of ZAN HL7 TCPIP Service: Part No ************ENG.A
34 Installation Change the start type to "automatic". In the logon tab you can select the account under which the service will run. Be sure that this account has read/write access privileges for the ZANHL7\HIS folder and subfolders! Part No ************ENG.A
35 Installation 5.2. Run HL7 TCPIP as a Windows Application If for any reason you don't want to run HL7 TCPIP as a Windows Service, you can run the windows application instead. In this case create a shortcut to ZANHL7\ HL7TCPIP.exe in your startup folder. HL7TCPIP.exe is a pure Windows application that creates an icon in the taskbar. Be sure that this account has read/write access privileges for the ZANHL7\HIS folder and subfolders! The disadvantage of running HL7 TCPIP as a Windows application is that the application will only run when this user is logged on. 3.2 Configuration Architecture (HL7TCPIP) TCPIP Service ZANHL7 Service HIS OutPath InPath hl7tcpip.cfg (HL7TCPIP) Normally you need not edit the hl7tcpip.cfg configuration file. Most entries can be edited through the configuration tool hl7tcpipconfig.exe. The following is a technical description for extended needs. [System] TempPath=c:\ZANHL7\temp Directory for temporary files. InPath=c:\ZANHL7\HIS\Out Directory for incoming HL7 messages from HIS to ZanHL7. OutPath=c:\ZANHL7\HIS\In Directory for outgoing HL7 messages from ZanHL7 to HIS. [HL7] StartCharacters=11 LLM delimiters start HL7 message Part No ************ENG.A
36 Installation EndCharacters=28,13 LLM delimiters end HL7 message [Query] Handler for QRY messages (with ADT or ADR responses) [Listener] Handler for unsolicited messages (e.g. ADT) [Query] and [Listener] Mode=0 1 0 = TCPIP Client 1 = TCPIP Server PermanentConnection=YES NO Defines whether connection is opened permanently or only when needed. ReadTimeout=5000 Timeout for message reading (ms). -1 = no timeout (infinite) Port=3000 Socket number IPAdress= IP address Part No ************ENG.A
HL7 Conformance Statement
HL7 Conformance Statement Product Image-Arena 4.3 Product No.: T.08.0122 Effective Date: 2010-04-30 Benjamin Wagner Document 04 rev.: D32.0083-04 Image-Arena 4.3 HL7 conformance statement Table of contents
More informationJiveX Enterprise PACS Solutions. JiveX HL7 Gateway Conformance Statement - HL7. Version: 4.7.1 As of 2015-05-20
JiveX Enterprise PACS Solutions JiveX HL7 Gateway Conformance Statement - HL7 Version: 4.7.1 As of 2015-05-20 VISUS Technology Transfer GmbH Universitätsstr. 136 D-44799 Bochum Germany Phone: +49 (0) 234
More informationImagePilot. HL7 Conformance Statement. Manufacturer: 1 Sakura-machi, Hino-shi Tokyo 191-8511, Japan
ImagePilot HL7 Conformance Statement Manufacturer: 1 Sakura-machi, Hino-shi Tokyo 191-8511, Japan Revision History Date Version Description August 28, 2009 Rev. 1.0 April 1, 2010 Rev. 1.1 Values that
More informationHL7 Conformance Statement RadCentre. Release 2015.01
HL7 Conformance Statement Release 2015.01 Editing The editing is done by i-slutins Health GmbH. If you have any suggestions for improvement or requests for modification etc, please let us know. You can
More informationHL7 Interface Specifications
HL7 Interface Specifications V2.2 Ifa systems AG ifa united i-tech Inc. Augustinusstr. 11b 1850 SE 17th Street, Ste. 107 50226 Frechen Fort Lauderdale, FL 33316 Germany USA Tel.: +49-2234-933670 Tel.:
More informationHL7 Interface Specification Merge Eye Station v. 11.3
HL7 Interface Specification Merge Eye Station v. 11.3 Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 USA 877.44.MERGE 2012 Merge Healthcare. The information contained herein is confidential
More informationHL7 Interface Specification. HL7 Interface 1.2
Interface Specification Interface 1.2 May 2004 Interface 1.2 Specification TABLE OF CONTENTS 1 INTRODUCTION... 3 1.1 Purpose...3 1.2 Related Documents...3 2 IMPLEMENTATION... 4 3 COMMUNICATION PROFILE...
More informationAIDA compact NEO HL7 Interface Description
AIDA compact NEO HL7 Interface Description sion : BA Circulation : 1 ated UNG Proved A.Hau Approved HWS PRODUCT INFO OR1 e 2010-03-04 Date Date artment SEPS Department PM OR1 Department SEPS ition SW Dev.
More informationCopyright 1982 2009 Swearingen Software, Inc. All rights reserved.
Swearingen Software HL7 Inbound & Outbound Specs 2009 Copyright 1982 2009 Swearingen Software, Inc. All rights reserved. Swearingen Software, Inc. 6950 Empire Central Drive Houston, TX 77040 Table of Contents
More informationPhilips Innovation Campus 560045 Bangalore India. Issued by:
Issued by: PHILIPS HEALTHCARE Patient Care and Clinical Informatics Interoperability Competence Center Philips Innovation Campus 560045 Bangalore India E-mail: hl7@philips.com Internet: http://www.healthcare.philips.com/connectivity
More informationHL7 Interface Specification Merge LabAccess v. 3.6
HL7 Interface Specification Merge LabAccess v. 3.6 Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 USA 877.44.MERGE 12 Merge Healthcare. The information contained herein is confidential and
More informationHL7 Conformance Statement
HL7 Conformance Statement Release VA20B (2014-03-28) ITH icoserve technology for healthcare GmbH Innrain 98, 6020 Innsbruck, Austria +43 512 89059-0 www.ith-icoserve.com Any printout or copy of this document
More informationRamSoft PACS 3.0 HL7 Conformance Statement
. RamSoft Inc. RamSoft Inc. 16 Four Seasons Place, Suite 215 Toronto, ON M9B 6E5, CANADA RamSoft PACS 3.0 HL7 Conformance Statement.......... January 27, 2003 ...2 General...3 General message format...3
More informationEmpowered by Innovation. Setting Up and Using Fax Mail. P/N 1770087 July 2006 Printed in U.S.A.
Empowered by Innovation Setting Up and Using Fax Mail P/N 1770087 July 2006 Printed in U.S.A. This manual has been developed by NEC Unified Solutions, Inc. It is intended for the use of its customers and
More informationGeneric EHR HL7 Interface Specification Abraxas v. 4
Generic EHR HL7 Interface Specification Abraxas v. 4 Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 USA 877.44.MERGE 2012 Merge Healthcare. The information contained herein is confidential
More informationHow To Get A Medical Record On A Medical Device
9. Medical Records/Information Management (Document Management) Chapter Chair/Editor: Chapter Chair/Editor: Wayne R. Tracy, MS Health Patterns, LLC Michelle L. Dougherty, RHIA American Health Information
More informationOracle SOA Suite 11g Oracle SOA Suite 11g HL7 Inbound Example
Oracle SOA Suite 11g Oracle SOA Suite 11g HL7 Inbound Example michael.czapski@oracle.com June 2010 Table of Contents Introduction... 1 Pre-requisites... 1 Prepare HL7 Data... 1 Obtain and Explore the HL7
More informationHL7 Customization Guide
HL7 Customization Guide Table of Contents Intended Audience... 3 1. Overview... 3 1.1 Introduction... 3 1.2 HL7 Overview... 3 1.3 Report Formats... 4 1.4 Interface Workflow... 5 1.5 Integration Steps...
More informationUX Mail Fax Features. Empowered by Innovation. P/N 0913251 Rev 1, September 15, 2008 Printed in U.S.A. V4.21
Empowered by Innovation UX Mail Fax Features P/N 0913251 Rev 1, September 15, 2008 Printed in U.S.A. V4.21 For additional resources, visit UX5000 on the web at http://www.necux5000.com. This manual has
More informationNCD ThinPATH Load Balancing Startup Guide
NCD ThinPATH Load Balancing Startup Guide Copyright Copyright 1999 by Network Computing Devices, Inc. (NCD).The information contained in this document is subject to change without notice. Network Computing
More informationWA Manager Alarming System Management Software Windows 98, NT, XP, 2000 User Guide
WA Manager Alarming System Management Software Windows 98, NT, XP, 2000 User Guide Version 2.1, 4/2010 Disclaimer While every effort has been made to ensure that the information in this guide is accurate
More informationDell Statistica 13.0. Statistica Enterprise Installation Instructions
Dell Statistica 13.0 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or
More informationHL7 Fundamentals. Presented by: Dana McDonough, Carolina Velasquez, & Bing Chen. August 2014
HL7 Fundamentals Presented by: Dana McDonough, Carolina Velasquez, & Bing Chen August 2014 Today s Presenters: Dana McDonough Associate Technical Consultant Allscripts and Epic data conversions EHR Reporting
More informationFOR WINDOWS FILE SERVERS
Quest ChangeAuditor FOR WINDOWS FILE SERVERS 5.1 User Guide Copyright Quest Software, Inc. 2010. All rights reserved. This guide contains proprietary information protected by copyright. The software described
More informationQuick Start Program Advanced Manual ContactWise 9.0
Quick Start Program Advanced Manual ContactWise 9.0 Copyright 2010 GroupLink Corporation. All Rights Reserved. ContactWise is a registered trademark of GroupLink Corporation. All other trademarks are the
More informationRelayClinical Service Feature Guide RelayClinical Notify
RelayClinical Service Feature Guide RelayClinical Notify Release 15.11 November 2015 Health Connections Brought to Life Table of Contents Overview... 3 Benefits... 3 Models... 3 Alternate Deployment Option...
More informationNCD ThinPATH Load Balancing Startup Guide versions 2.0.7 and 2.8.1
NCD ThinPATH Load Balancing Startup Guide versions 2.0.7 and 2.8.1 Copyright Copyright 2003 by Network Computing Devices, Inc. (NCD).The information contained in this document is subject to change without
More informationHow To Set Up A Xerox Econcierge Powered By Xerx Account
Xerox econcierge Account Setup Guide Xerox econcierge Account Setup Guide The free Xerox econcierge service provides the quickest, easiest way for your customers to order printer supplies for all their
More information9. Medical Records/Information Management
9. Medical Records/Information Management (Document Management) Chapter Chair/Editor: Chapter Chair/Editor: Wayne Tracy, MS SpaceLabs Medical Mary D. Brandt, MBA, RRA, CHE American Health Information Management
More informationNetwork Scanner Tool R3.1. User s Guide Version 3.0.04
Network Scanner Tool R3.1 User s Guide Version 3.0.04 Copyright 2000-2004 by Sharp Corporation. All rights reserved. Reproduction, adaptation or translation without prior written permission is prohibited,
More informationHL7 Interconnection Guide v1.1
HL7 Interconnection Guide v1.1 Copyright Universal Research Solutions, LLC. 1 Contents Introduction... 3 Recommended Interconnection Plan... 3 VPN Connectivity... 3 Communication Protocol... 4 TCP/IP &
More informationSymantec Enterprise Vault
Symantec Enterprise Vault Guide for Microsoft Outlook 2010/2013 Users 10.0 Light Outlook Add-In Symantec Enterprise Vault: Guide for Microsoft Outlook 2010/2013 Users The software described in this book
More informationRemark FTP Utility. For Remark Office OMR. User s Guide
Remark FTP Utility For Remark Office OMR User s Guide Remark Products Group 301 Lindenwood Drive, Suite 100 Malvern, PA 19355-1772 USA www.gravic.com Disclaimer The information contained in this document
More informationFor Active Directory Installation Guide
For Active Directory Installation Guide Version 2.5.2 April 2010 Copyright 2010 Legal Notices makes no representations or warranties with respect to the contents or use of this documentation, and specifically
More informationMicrosoft Dynamics GP. Engineering Data Management Integration Administrator s Guide
Microsoft Dynamics GP Engineering Data Management Integration Administrator s Guide Copyright Copyright 2007 Microsoft Corporation. All rights reserved. Complying with all applicable copyright laws is
More informationNetBak Replicator 4.0 User Manual Version 1.0
NetBak Replicator 4.0 User Manual Version 1.0 Copyright 2012. QNAP Systems, Inc. All Rights Reserved. 1 NetBak Replicator 1. Notice... 3 2. Install NetBak Replicator Software... 4 2.1 System Requirements...
More informationMOSAIQ External Systems Interfaces (ESI) Product Offerings
MOSAIQ External Systems Interfaces (ESI) Product Offerings (Current as of MOSAIQ 2.60) Elekta offers a broad range of external systems interfaces to connect oncology clinician and administrative personnel
More informationMobileStatus Server Installation and Configuration Guide
MobileStatus Server Installation and Configuration Guide Guide to installing and configuring the MobileStatus Server for Ventelo Mobilstatus Version 1.2 June 2010 www.blueposition.com All company names,
More informationDell InTrust 11.0. Preparing for Auditing Microsoft SQL Server
2014 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement.
More informationSHARP Digital Signage Software Pro PN-SS05 OPERATION MANUAL
SHARP Digital Signage Software Pro PN-SS05 Version 4.1 OPERATION MANUAL Contents Introduction... 2 Precautions on Use...2 Trademarks...2 How to Read this Manual...3 Definitions...3 Installing/Launching...
More informationShadowLink 2. Overview. May 4, 2015. ONLINE SUPPORT emdat.com/ticket/ PHONE SUPPORT (608) 270-6400 ext. 1
ShadowLink 2 Overview May 4, 2015 ONLINE SUPPORT emdat.com/ticket/ PHONE SUPPORT (608) 270-6400 ext. 1 1 Interfacing with Emdat ShadowLink is an Emdat developed product that securely moves data between
More informationTroubleshooting File and Printer Sharing in Microsoft Windows XP
Operating System Troubleshooting File and Printer Sharing in Microsoft Windows XP Microsoft Corporation Published: November 2003 Updated: August 2004 Abstract File and printer sharing for Microsoft Windows
More informationLPR for Windows 95 TCP/IP Printing User s Guide
LPR for Windows 95 TCP/IP Printing User s Guide First Edition Printed in Taiwan, R.O.C. RECYCLABLE Copyright Statement Trademarks Limited Warranty Copyright 1997 D-Link Corporation No part of this publication
More informationAudit Management Reference
www.novell.com/documentation Audit Management Reference ZENworks 11 Support Pack 3 February 2014 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of
More informationFile Management Utility User Guide
File Management Utility User Guide Legal Notes Unauthorized reproduction of all or part of this guide is prohibited. The information in this guide is subject to change without notice. We cannot be held
More informationTASKE Call Center Management Tools
TASKE Call Center Management Tools Version 7 Integrating and Configuring Blue Pumpkin PrimeTime and PrimeTime Skills TASKE Technology Inc. Copyright 2000, TASKE Technology Inc. All rights reserved. Printed
More informationAsset Inventory Reference
www.novell.com/documentation Asset Inventory Reference ZENworks 11 Support Pack 3 July 2014 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this
More informationHP IMC Firewall Manager
HP IMC Firewall Manager Configuration Guide Part number: 5998-2267 Document version: 6PW102-20120420 Legal and notice information Copyright 2012 Hewlett-Packard Development Company, L.P. No part of this
More informationSymantec Enterprise Vault
Symantec Enterprise Vault Guide for Microsoft Outlook 2010/2013 Users 10.0 Full Outlook Add-In Symantec Enterprise Vault: Guide for Microsoft Outlook 2010/2013 Users The software described in this book
More informationProlific USB to SATA Bridge Controller Backup Software User s Manual
Prolific USB to SATA Bridge Controller Backup Software User s Manual For Windows XP/Vista/7 For Software version 3.9.2.00 (6/28/2011) Contents About Prolific Backup Software System Requirements Using the
More informationUFR II Driver Guide. UFR II Driver Ver. 2.20 ENG
UFR II Driver Guide UFR II Driver Ver. 2.20 Please read this guide before operating this product. After you finish reading this guide, store it in a safe place for future reference. ENG 0 Ot UFR II Driver
More informationSymantec Enterprise Vault
Symantec Enterprise Vault Guide for Microsoft Outlook 2010/2013 Users 10.0 Full Outlook Add-In Symantec Enterprise Vault: Guide for Microsoft Outlook 2010/2013 Users The software described in this book
More informationPulse Redundancy. User Guide
Pulse Redundancy User Guide August 2014 Copyright The information in this document is subject to change without prior notice and does not represent a commitment on the part of AFCON Control and Automation
More informationUser Guidance. CimTrak Integrity & Compliance Suite 2.0.6.19
CimTrak Integrity & Compliance Suite 2.0.6.19 Master Repository Management Console File System Agent Network Device Agent Command Line Utility Ping Utility Proxy Utility FTP Repository Interface User Guidance
More informationActive Directory Change Notifier Quick Start Guide
Active Directory Change Notifier Quick Start Guide Software version 3.0 Mar 2014 Copyright 2014 CionSystems Inc., All Rights Reserved Page 1 2014 CionSystems Inc. ALL RIGHTS RESERVED. This guide may not
More informationBLUECIELO MERIDIAN ASSET MANAGEMENT MODULE 2014
BLUECIELO MERIDIAN ASSET MANAGEMENT MODULE 2014 User's Guide Manual BlueCielo ECM Solutions bluecieloecm.com December 09 2014 LEGAL NOTICE 2014 BlueCielo ECM Solutions B. V. Polarisavenue 1 2132 JH Hoofddorp
More informationWindows Peer-to-Peer Network Configuration Guide
Windows Peer-to-Peer Network Configuration Guide Windows Peer-to-Peer Network Configuration Guide for CCC Pathways Copyright 2008 by CCC Information Services Inc. All rights reserved. No part of this publication
More informationGUIDE. Web Client Application. Model: ER 4.0. Release 4.0.00 / Version No.: 1.01
8e6R Enterprise Reporter USER GUIDE Web Client Application Model: ER 4.0 Release 4.0.00 / Version No.: 1.01 ii 8E6 TECHNOLOGIES, ENTERPRISE REPORTER WEB CLIENT USER GUIDE 8E6 ENTERPRISE REPORTER WEB CLIENT
More informationSpotlight Management Pack for SCOM
Spotlight Management Pack for SCOM User Guide January 2015 The is used to display data from alarms raised by Spotlight on SQL Server Enterprise in SCOM (System Center Operations Manager). About System
More informationManual Password Depot Server 8
Manual Password Depot Server 8 Table of Contents Introduction 4 Installation and running 6 Installation as Windows service or as Windows application... 6 Control Panel... 6 Control Panel 8 Control Panel...
More informationemail-lead Grabber Business 2010 User Guide
email-lead Grabber Business 2010 User Guide Copyright and Trademark Information in this documentation is subject to change without notice. The software described in this manual is furnished under a license
More informationsimplify printing TX Guide v. 1. make IT simple Tricerat, Inc. 11500 Cronridge Drive Suite 100 Owings Mills, MD 21117 201, All rights Reserved
simplify printing TX Guide v. 1. Tricerat, Inc. 11500 Cronridge Drive Suite 100 Owings Mills, MD 21117 make IT simple 201, All rights Reserved Release Info Copyright Limit of Liability Trademarks Customer
More informationAllworx OfficeSafe Operations Guide Release 6.0
Allworx OfficeSafe Operations Guide Release 6.0 No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopy,
More informationDell Enterprise Reporter 2.5. Configuration Manager User Guide
Dell Enterprise Reporter 2.5 2014 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license
More informationSOFTWARE MANUAL UNIOPC
SOFTWARE MANUAL UNIOPC The information in this document reflects products at the date of printing. Unitronics reserves the right, subject to all applicable laws, at any time, at its sole discretion, and
More informationATX Document Manager. User Guide
ATX Document Manager User Guide ATX DOCUMENT MANAGER User Guide 2010 CCH Small Firm Services. All rights reserved. 6 Mathis Drive NW Rome, GA 30165 No part of this manuscript may be copied, photocopied,
More informationA Presentation of TeachUcomp Incorporated. Copyright TeachUcomp, Inc. 2013. Mastering Outlook Made Easy for Lawyers CPE Edition v.2.
A Presentation of TeachUcomp Incorporated. Copyright TeachUcomp, Inc. 2013 Mastering Outlook Made Easy for Lawyers CPE Edition v.2.0 TeachUcomp, Inc. it s all about you Copyright: Copyright 2013 by TeachUcomp,
More informationHow to Obtain an OPC License--5. Creating a System Code 5 Entering an Authorization Code 6. Getting Started with SNMP Editor--7
Contents Introduction--1 Product definition 1 Implementing SNMP 2 Integrating SNMP into the user interface 3 Components of OPC SNMP Gateway 4 How to Obtain an OPC License--5 Creating a System Code 5 Entering
More informationWhatsUp Event Alarm v10.x Listener Console User Guide
WhatsUp Event Alarm v10.x Listener Console User Guide Contents WhatsUp Event Alarm Listener Console Overview Firewall Considerations... 6 Using the WhatsUp Event Alarm Listener Console... 7 Event Alarm
More informationHIE Ready 2.0 SPECIFICATIONS MATRIX. Product Name: Version Number: Preferred Message and Trigger
HIE Ready 2.0 SPECIFICATIONS MATRIX Entity Name: Street Address: City, State, Zip: Point of Contact Name: E-mail & Phone: Alternate Contact Name: Alternate E-mail & Phone: Product Name: Version Number:
More informationQuest ChangeAuditor 5.1 FOR ACTIVE DIRECTORY. User Guide
Quest ChangeAuditor FOR ACTIVE DIRECTORY 5.1 User Guide Copyright Quest Software, Inc. 2010. All rights reserved. This guide contains proprietary information protected by copyright. The software described
More informationLegal Notes. Regarding Trademarks. 2012 KYOCERA Document Solutions Inc.
Legal Notes Unauthorized reproduction of all or part of this guide is prohibited. The information in this guide is subject to change without notice. We cannot be held liable for any problems arising from
More informationServer Manager. Open Text Web Solutions Management Server 10.0
Server Manager Open Text Web Solutions Management Server 10.0 Copyright 2009 Open Text Corporation. All rights reserved. Documentation 01/2009 - Management Server 10.0 This documentation contains information
More information8.7. Resource Kit User Guide
8.7 Resource Kit User Guide 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This document contains proprietary information protected by copyright. The software described in this document is furnished under
More information20/20 Integration Guide
20/20 Integration Guide March 15 2013 A guide to Modality Work List and Spectacle-Link Overview Within medical imaging there are two common interfaces or integrations that most practices find helpful if
More informationHP A-IMC Firewall Manager
HP A-IMC Firewall Manager Configuration Guide Part number: 5998-2267 Document version: 6PW101-20110805 Legal and notice information Copyright 2011 Hewlett-Packard Development Company, L.P. No part of this
More informationivms-5200 Professional Web Manager User Manual
ivms-5200 Professional Web Manager User Manual UD.6L0202D1651A01 Hikvision ivms-5200 Professional Web Manager User Manual This manual, as well as the software described in it, is furnished under license
More informationDell InTrust 11.0 Best Practices Report Pack
Complete Product Name with Trademarks Version Dell InTrust 11.0 Best Practices Report Pack November 2014 Contents About this Document Auditing Domain Controllers Auditing Exchange Servers Auditing File
More information4.0. Offline Folder Wizard. User Guide
4.0 Offline Folder Wizard User Guide Copyright Quest Software, Inc. 2007. All rights reserved. This guide contains proprietary information, which is protected by copyright. The software described in this
More informationDell InTrust 11.0. Real-Time Monitoring Guide
Dell InTrust 11.0 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure
More informationUser Guide. DocAve Lotus Notes Migrator for Microsoft Exchange 1.1. Using the DocAve Notes Migrator for Exchange to Perform a Basic Migration
User Guide DocAve Lotus Notes Migrator for Microsoft Exchange 1.1 Using the DocAve Notes Migrator for Exchange to Perform a Basic Migration This document is intended for anyone wishing to familiarize themselves
More informationRSM Web Gateway RSM Web Client INSTALLATION AND ADMINISTRATION GUIDE
RSM Web Gateway RSM Web Client INSTALLATION AND ADMINISTRATION GUIDE Installation and Administration Guide RSM Web Client and RSM Web Gateway 17 August, 2004 Page 1 Copyright Notice 2004 Sony Corporation.
More informationOracle SOA Suite 11g Oracle SOA Suite 11g HL7 Inbound Example Functional ACK Addendum
Oracle SOA Suite 11g Oracle SOA Suite 11g HL7 Inbound Example Functional ACK Addendum michael@czapski.id.au June 2010 Table of Contents Introduction... 1 Pre-requisites... 1 HL7 v2 Receiver Solution...
More informationMasimo Patient Safetynet HL7 Interface Specifications
TECHNICAL BULLETIN Masimo Patient Safetynet HL7 Interface Specifications Version 1.0 August 2013 CAUTION: Federal law restricts this device to sale by or on the order of a physician. For professional use.
More informationVERITAS Backup Exec TM 10.0 for Windows Servers
VERITAS Backup Exec TM 10.0 for Windows Servers Quick Installation Guide N134418 July 2004 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software
More informationformerly Help Desk Authority 9.1.2 Quick Start Guide
formerly Help Desk Authority 9.1.2 Quick Start Guide 2 Contacting Quest Software Email: Mail: Web site: info@quest.com Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA www.quest.com
More informationM86 Authenticator USER GUIDE. Software Version: 2.0.10 Document Version: 04.26.11
M86 Authenticator USER GUIDE Software Version: 2.0.10 Document Version: 04.26.11 M86 AUTHENTICATOR USER GUIDE 2011 M86 Security All rights reserved. 828 W. Taft Ave., Orange, CA 92865, USA Version 1.01,
More informationEMC Documentum Content Services for SAP iviews for Related Content
EMC Documentum Content Services for SAP iviews for Related Content Version 6.0 Administration Guide P/N 300 005 446 Rev A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748 9103 1 508 435 1000
More informationGetting Started with IntelleView POS Administrator Software
Getting Started with IntelleView POS Administrator Software Administrator s Guide for Software Version 1.2 About this Guide This administrator s guide explains how to start using your IntelleView POS (IntelleView)
More informationDell InTrust 11.0. Preparing for Auditing and Monitoring Microsoft IIS
Preparing for Auditing and Monitoring Microsoft IIS 2014 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished
More informationXcalibur. Foundation. Administrator Guide. Software Version 3.0
Xcalibur Foundation Administrator Guide Software Version 3.0 XCALI-97520 Revision A May 2013 2013 Thermo Fisher Scientific Inc. All rights reserved. LCquan, Watson LIMS, and Web Access are trademarks,
More informationCOMSPHERE 6700 SERIES NETWORK MANAGEMENT SYSTEM
COMSPHERE 6700 SERIES NETWORK MANAGEMENT SYSTEM SECURITY MANAGER FEATURE SUPPLEMENT Document No. 6700-A2-GB41-30 February 1998 Copyright 1998 Paradyne Corporation. All rights reserved. Printed in U.S.A.
More informationHyperFS PC Client Tools
SAN Management Software HyperFS PC Client Tools This guide provides step-by-step instructions for setup, configuration, and maintenance of the Rorke Data HyperFS SAN Management Software Ver 2.1 May 11,
More informationAdministration and Business Collaboration. User Manual
Administration and Business Collaboration User Manual Copyright 2007 by Eurekify Ltd., 8 Hasadna Street Raanana 43651, ISRAEL. All Rights Reserved. This document maybe used in its complete form only and
More informationCentral Management System (CMS) USER MANUAL
Central Management System (CMS) USER MANUAL LEGAL INFORMATION Reproduction, transfer, distribution or storage of part or all of the contents in this document in any form without the prior written permission
More informationEmail Data Protection. Administrator Guide
Email Data Protection Administrator Guide Email Data Protection Administrator Guide Documentation version: 1.0 Legal Notice Legal Notice Copyright 2015 Symantec Corporation. All rights reserved. Symantec,
More informationScan to SMB(PC) Set up Guide
Scan to SMB(PC) Set up Guide Regarding Trade Names Windows is a registered trademark of Microsoft Corporation in the U.S.A. and/or other countries. Windows XP and Windows Vista are trademarks of Microsoft
More informationAccounting Manager. User Guide A31003-P1030-U114-2-7619
Accounting Manager User Guide A31003-P1030-U114-2-7619 Our Quality and Environmental Management Systems are implemented according to the requirements of the ISO9001 and ISO14001 standards and are certified
More informationAdministration Guide. Novell Storage Manager 3.1.1 for Active Directory. Novell Storage Manager 3.1.1 for Active Directory Administration Guide
Novell Storage Manager 3.1.1 for Active Directory Administration Guide www.novell.com/documentation Administration Guide Novell Storage Manager 3.1.1 for Active Directory October 17, 2013 Legal Notices
More informationSample- for evaluation purposes only! Advanced Outlook. TeachUcomp, Inc. A Presentation of TeachUcomp Incorporated. Copyright TeachUcomp, Inc.
A Presentation of TeachUcomp Incorporated. Copyright TeachUcomp, Inc. 2012 Advanced Outlook TeachUcomp, Inc. it s all about you Copyright: TeachUcomp, Inc. Phone: (877) 925-8080 Web: http://www.teachucomp.com
More information