Vision Series RIS 5.

0 HL7 Interface Guide

Vision Series RIS 5.0 HL7 Interface Guide

Copyright 2007-2009 AMICAS, Inc. All rights reserved.
Use, duplication, or disclosure by licensee is subject to restrictions as set forth in the AMICAS, Inc. contract. Information contained in this document is subject to change without notice and does not represent a commitment on the part of AMICAS, Inc. The software and processes described in this document are furnished under the contract or nondisclosure agreement. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the purchaser’s personal use without the written permission of AMICAS, Inc. This document contains proprietary information of AMICAS, Inc. The contents are exempt from disclosure to the public under the Freedom of Information Act 35, U.S.C. 552 (6)(4) and unlawful disclosure thereof is a violation of the Trade Secrets Act, 18 U.S.C. 1905. Public disclosure of any information contained herein shall not be made without prior written permission of AMICAS, Inc. AMICAS is a registered trademark or trademark of AMICAS, Inc. All other names and products are trademarks or registered trademarks of their respective companies. RESTRICTED RIGHTS LEGEND: Use, duplication or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. AMICAS, Inc.

Date 3/28/08 8/29/08 10/31/08 11/24/08 06/05/09 08/18/09

Revision A B B.1 C D D.1

Description Initial Release for 5.0 Maintenance Release 1 Maintenance Release 1, Critical Update 1 Maintenance Release 2 Maintenance Release 4 Maintenance Release 4, Critical Update 1

AMICAS, Inc. Proprietary and Confidential

Vision Series RIS 5.0 HL7 Interface Guide

Table of Contents
Preface ......................................................................................................................................................... v 1. HL7 Overview...................................................................................................................................... 1 1.1 Messages ............................................................................................................................... 1 1.2 Segments ............................................................................................................................... 1 1.3 Fields ...................................................................................................................................... 1 1.3.1 Sequence........................................................................................................................ 1 1.3.2 Field Name ..................................................................................................................... 2 1.3.3 Length ............................................................................................................................. 2 1.3.4 Optionality....................................................................................................................... 2 1.4 MSH-9 – Message Types....................................................................................................... 2 1.5 Message Delimiters............................................................................................................... 2 1.6 Message Details .................................................................................................................... 3 1.7 Warning to the Reader ..........................................................................................................4 HL7 Support Tables – Definition....................................................................................................... 5 Inbound Messages ............................................................................................................................. 6 3.1 ADT^A01, A02, A03, A04, A05, A06, A07 or ADT^A08 – Registering / Updating a Patient 6 3.1.1 Message Definition ......................................................................................................... 6 3.1.2 MSH (Message Header Segment) - ADT ^A01 - ADT^A08 ........................................... 6 3.1.3 PID (Patient Identification Definition Segment) - ADT ^A01 - ADT^A08 ........................ 8 3.1.4 GT1 (Guarantor Segment) - ADT ^A01 - ADT^A08 ..................................................... 10 3.1.5 IN1 (Insurance Segment) - ADT ^A01 - ADT^A08 ....................................................... 14 3.1.6 IN2 (Insurance Segment) - ADT ^A01 - ADT^A08 ....................................................... 17 3.2 ADT^A34 or ADT^A40 – HL7 Message Merge Type ........................................................ 20 3.2.1 Message Definition .......................................................................................................20 3.2.2 MSH (Message Header Segment) – ADT^A34 or ADT^A40 ....................................... 21 3.2.3 EVN (Event Type Segment) - ADT^A34 or ADT^A40 .................................................. 22 3.2.4 PID (Patient Identification Definition Segment) - ADT ^A34 or ADT^A40 .................... 22 3.2.5 MRG (Patient Merge Information Segment) - ADT^A34 or ADT^40 ............................ 24 3.3 BAR^P05 – Billing Account Update Message Type......................................................... 25 3.3.1 Message Definition .......................................................................................................25 3.3.2 MSH (Message Header Segment) – BAR^P05............................................................ 25 3.3.3 EVN (Event Type Segment) – BAR^P05...................................................................... 26 3.3.4 PID (Patient Identification Definition Segment) – BAR^P05......................................... 28 3.3.5 PV1 (Patient Visit Segment) – BAR^P05 ..................................................................... 30 3.4 MFN - Master File Update Message Type.......................................................................... 33 3.4.1 Message Definition .......................................................................................................33 3.4.2 MSH (Message Header Segment) – MFN.................................................................... 34 3.4.3 MFI (Message File Identification Segment) – MFN ...................................................... 35 3.4.4 MFE (Message File Entry Segment) – MFN................................................................. 36 3.4.5 ZL7 (Insurance Data to Post Segment) – MFN ............................................................ 37 3.5 ORM^O01 – Order Message Type...................................................................................... 38 3.5.1 Message Definition .......................................................................................................38 3.5.2 MSH (Message Header Segment) – ORM^O01 .......................................................... 38 3.5.3 PID (Patient Identification Definition Segment) - ORM^O01 ........................................ 39 3.5.4 PV1 (Patient Visit Segment) – ORM^O01 .................................................................... 42 3.5.5 NTE (Notes and Comments Segment) – ORM^O01.................................................... 45 3.5.6 ORC (Common Order Segment) - ORM^O01.............................................................. 46 3.5.7 OBR (Observation Request Segment) – ORM^O01 .................................................... 48 3.5.8 OBX (Observation Result Segment) - ORM^O01 ........................................................ 52 3.6 ORR^O02 - General Order Acknowledgment Message Type ......................................... 53

2. 3.

AMICAS, Inc. Proprietary and Confidential

ii

..................1 Definition...4 MFE (Message File Entry Segment) – MFN...ADT^A08.. 68 4.......................................................... 60 3...................... 92 4.2 MSH (Message Header Segment) ..............2 MSH (Message Header Segment) ......................1 Message Definition ........................................................2 MSH (Message Header Segment) ..........ORM^O01 ............ 103 4.............................ADT^A08...........................56 3............................. 104 AMICAS....ORR^O02 ....................................... 81 4............3.................................................................... 87 4.............ORM^O01 .....................4....................................... 80 4..........................................7...................5 MRG (Patient Merge Information Segment) ........... 66 4............................3 ADT^A08 – Update Patient Information .................................5........................5..6.......1 Definition.. 75 4......ACK ....102 4.3 PID (Patient Identification Definition Segment) ................................3............6.. 74 4.................................7 OBX (Observation/Result Segment) ............................6............1 Message Definition ..............6.............................4....5...............................................................5 PID (Patient Identification Definition Segment) – ORR^O02.......8.............................ORR^O02.............ORM^O01 .......... 71 4....Results Message Type............ 83 4..........................................5..... 63 3....................ORU^R01.........................4................. 56 3.. 66 4..................................................3........................................ 84 4.7..................................ORU^R01. 55 3............................53 3.................................................. Inc...........ADT^A08 .2 MSH (Message Header Segment) ............................7........................... 58 3..........ORU^R01..................................................5 ZL7 (Insurance Data to Post Segment) – MFN ...............................................................1 Definition..............................7..................................8. 57 3..6 OBR (Order Detail /Observation Request) ....................................... 88 4..................5 OBX (Observation/Result Segment) .............................4 OBR (Observation Request Segment) .. 78 4.................. Proprietary and Confidential iii . 94 4..................................................... 3...1 Definition.......................................................................................3 MFI (Message File Identification Segment) – MFN .................2 MSH (Message Header Segment) .....................................ORU^R01...................ADT^A34............5 ORC (Common Order Segment) ............ 77 4.6... 56 3...............3 MSA (Message Acknowledgment Segment) ..................................5......3 EVN (Event Type Segment) .........................7.................................................................5 ORC (Common Order Segment) ..........7.............6.............ORU^R01 ......ORM^O01..........2 MSH (Message Header Segment) ...................................................... 81 4......8 ORU^R01 – HL7 HTML Result Message Type ...........7........................... 64 3...........................................2 Trigger Points and Trigger Events .........5 MFN ..3 PID (Patient Identification Definition Segment) .....6..ADT^A34 ..................................................................................4 ADT^A34 – Merge Patient Information (Patient ID Only).................................7..............................................................3 PID (Patient Identification Definition Segment) .......1 Definition....................................8....7.............. 102 4...........................ORU^R01 . 73 4... 73 4............................8.... 91 4.............0 HL7 Interface Guide 4......................1 Message Definition ....................ORU^R01..........1 Interface Monitor ..................... 101 4. 64 3.....................ORU^R01.............. 93 4..............4 ORC (Common Order Segment) ........................................... 79 4.....8................................... 54 3.....77 4.........4 PV1 (Patient Visit Segment) ............................ORM^O01..... 66 4............................................ORU^R01 ....................6..................4 PV1 (Patient Visit Segment) ....4....................Master File Update Message Type...........................ADT^A34........ 73 4..........................................2 MSH (Message Header Segment) – MFN.........4 PV1 (Patient Visit Segment) ...............ACK..........................................................................4...............2.......6......3 PID (Patient Identification Definition Segment) .................... 54 3....7 ORU^R01 ................................66 4....7.................................................................. 69 4...........ORU^R01 .....................................7 ORU^R01 – Results Message Type ......ORU^R01.............................................................................................4 PID (Patient Identification Definition Segment) .......................7..............................8........... 98 4.ORU^R01..................................................................................................... 81 4........................................1 Definition.........................1 Definition...................................................................................... 82 4...3 PID (Patient Identification Definition Segment) .6 ORM^O01 – Order Message Type............ 68 4. 65 Outbound Messages ....3........................................ 76 4............2 MSH (Message Header Segment) ..................6........8 ACK – Acknowledgment Message Type .............. 91 4.................2 MSA (Message Acknowledgment Segment) – ORR^O02 ....... 64 3...............................7........ 96 4.....Vision Series RIS 5.....................................................................................3 MSH (Message Header Segment) ....ADT^A34.......... 68 4.............6.6 OBR (Order Detail /Observation Request) .............................................

..........................10 ACK – Acknowledgment Message Type ........................................ Proprietary and Confidential iv ......... Inc...............................................................................................................9..113 4.................................ACK ......8..............Vision Series RIS 5....................ORM^O01 ......9 IN1 (Insurance Segment) ............ORM^O01 .10..............ORM^O01 ........11 PR1 (Procedure Segment) ........................ 126 4...................................2 MSH (Message Header Segment) ...................ORU^R01 ........5 PV2 (Patient Visit Segment) ..............................................6 GT1 (Guarantor Segment) ........116 4............3 PID (Patient Identification Definition Segment) ..2 MSH (Message Header Segment) ................ORM^O01 ........113 4..ORM^O01 .......... 137 AMICAS...........................................ORU^R01 ..........................118 4................ORM^O01...................................................9................6 OBR (Order Detail /Observation Request) ...........130 4... 132 Appendix A: Data Types.10.......8.............9................... 114 4............ 115 4.................ORM^O01......8....................................... 112 4.........9.....8 DB1 (Disability Segment) ............ORU^R01 ..........9...............................................................129 4..........) ....4 PV1 (Patient Visit Segment) ...............1 Definition..................................... 124 4........5 ORC (Common Order Segment) .....ORM^O01 ...........7 ACC (Accident Segment) ..............................9.............................ORM^O01...........9..............9..............................8........10 IN2 (Insurance Segment) .........................................................9.130 4....9..................................... 107 4............... 105 4.............................4 PV1 (Patient Visit Segment) ..... 120 4.......................................................0 HL7 Interface Guide 4...9........ACK ..................................... 109 4.1 Definition... 123 4.......131 Glossary .........3 MSA (Message Acknowledgment Seg................... 123 4...................................................................................7 OBX (Observation/Result Segment) ..........................................ORU^R01...........................................10....130 4...................................9 ORM^O01 – HL7 Batch Charge Out Message Type.........ORM^O01 ...................................................................................

Purpose and Audience This document is intended to serve as a procedure manual for the technical staff responsible for setting up the Vision Series RIS application.Vision Series RIS 5. AMICAS.0 HL7 Interface Guide Preface The Vision Series RIS 5. Inc.0 HL7 Interface Guide contains the procedures for configuring the HL7 component of the Vision Series RIS application. as well as a guide for third-party systems to interface with Vision Series RIS. Proprietary and Confidential v .

HL7 Overview 1. The difference appears when the contents of a message will be used to update a record in a database rather than create a new one. For Example: MSH-1. Each message consists of a group of segments in a defined sequence. however a message type may be associated with more than one trigger event. Each message has a message type (three-character code) that defines its type.2 Segments A segment is a logical grouping of data fields. (i. These triggers represent actions such as a patient is admitted or an order is placed. Inc.1 Messages Within the HL7 protocol.3.3 Fields A field is a string of characters. they are sent as character strings. the following information is specified about each field.. Only the HL7 fields that are used exclusively are listed in this document. the ADT message may contain the following segments:     Message Header (MSH) Event Type (EVN) Patient ID (PID) Patient Visit (PV1) Each segment is identified by a unique three-character code known as the Segment ID.1 Sequence The sequence is the position of the data field within the segment. For example. MSH-9. 1. They may occur only once in a message or they may be allowed to repeat. 1. Proprietary and Confidential 1 . A message is the atomic unit of data transferred between systems. 1. The real-world event that initiates an exchange of messages is called a trigger event. The same trigger event code may not be associated with more than one message type. data is broken up into groups called messages. When fields are transmitted. you need to send a space. Each segment is given a name. HL7 data fields may take on the null value. If you want to remove a value.e.0 HL7 Interface Guide HL7 Overview 1. AMICAS. which is transmitted as two double quote marks (“”). Sending the null value. Segments of a message may be required or optional. If no value is sent.Vision Series RIS 5. Except where noted. Refer to the Glossary for message type definitions. is different from omitting an optional data field. it is omitted) the old value should remain unchanged. A null value will be ignored. In defining a segment.

This MSH-9 data field contains two components: 1.3 Length The length is designated by HL7 or the system.5 Message Delimiters Message delimiters are special characters used in constructing a message. component separator. In the segment attribute tables this information is provided in the column labeled HL7 Field Name. 2. AMICAS. An alphanumeric trigger event type.1. The Vision Series RIS application allows the user to configure optional demographic data to be required in the System Properties. 1.Vision Series RIS 5. and escape character. In the segment attribute tables this information is provided in the column labeled Opt (beginning in Subsection 3.1. In the segment attribute tables this information is in a column labeled Len (beginning in Subsection 3.3.3. The designations for both Inbound and Outbound Messages are:     R = this designation means required. These constraints are imposed specifically upon manual data entry and editing of patient data and will not be enforced upon data received through the inbound interface. field separator. optional. 1. B = this designation means backward compatibility with previous versions of HL7. Inc. segment terminator.2). They are the segment initiator. or conditional in a segment. 1.2).4 MSH-9 – Message Types Each HL7 message header has a message type (MSH-sequence 9) that defines the purpose of the message. A three-character message type code. Proprietary and Confidential 2 . 1. 1. O = this designation means optional. whichever is the smallest.2) this information is provided in the column labeled Seq.4 Optionality Optionality designates if the field is required.1. C = this designation means conditional (as described in the Comments column beginning in Subsection 3.0 HL7 Interface Guide HL7 Overview In the segment attribute tables (beginning in Subsection 3.2 Field Name The field name is the descriptive name for the data item. The escape character is only used in charge out.3.2). repetition separator. subcomponent separator.1.

Messages are terminated by an end block character sequence of <1C><0D> hex.0 HL7 Interface Guide HL7 Overview The segment terminator is always a carriage return (in ASCII. Separates multiple occurrences of a field where allowed. this character may be omitted. which is the first field after the segment ID. it must be present if subcomponents are used in the message. Terminates a message record. This value cannot be changed by implementers. Separates two adjacent data fields within a segment.6 Message Details    A message is a unit of data transferred between two systems. with the field delimiter in the 4th character position. Terminates a segment record. HL7 recommends the following suggested values: Delimiter Message Initiator Message Terminator Suggested Value Vertical Tabulation File separator <CR> carriage return <CR> carriage return Hex Value 0B 1C 0D 0D Usage Initiates a message record. Messages are prefixed with a character of <0B> hex. Separates adjacent components of data fields where allowed. and the other delimiters occurring as in the field called Encoding Characters. a hex 0D). The delimiter values used in the MSH segment are the delimiter values used throughout the entire message. HL7 data will be received via TCP/IP socket or shared folder. this character may be omitted. However. It also separates the Segment ID from the first data field in each segment.Vision Series RIS 5. All messages sent or received via Vision Series RIS will be constructed according to the Minimal Lower Layer Protocol (MLLP). The message is wrapped between 0B and 1C 0D. The other delimiters are defined in the MSH segment. to parse the message. In the absence of other considerations. All acknowledgment messages from the remote server will need to follow the same format. Segment Terminator Field Separator | (pipe) 7C Component Separator ^ (carat) 5E Subcomponent Separator & (ampersand) 26 Repetition Separator ~ (tilde) 7E Escape Character \ (backslash) 5C 1. the subset of the possible delimiters may be limited by negotiations between applications. The escape character is for use with any field represented by an ST. Separates adjacent subcomponents of data fields where allowed. Inc. AMICAS. At any given site. This implies that the receiving applications will use the agreed upon delimiters. or for use with the data (fourth) component of the ED data type If no escape characters are used in a message. Proprietary and Confidential 3 . TX or FT data type. If there are no subcomponents. Segments are terminated with a character of <0D> hex. as they appear in the Message Header segment (MSH).

Transmitted fields should be sent as character strings. In order to designate a change. but were not expected. the specifications in this document take precedence. For general information on HL7 messages. segment and field definitions used by this interface are based on the HL7 2.7 Warning to the Reader Message. The old value will remain unchanged. Inc.   1. rather than treat such a circumstance with an error.0 HL7 Interface Guide HL7 Overview  An empty string or NULL will be treated as an ignore field. The filler could ignore data fields that are present. A data field is a string of characters that are of variable length and separated by delimiters as listed below.3 standard and where possible match those specifications.Vision Series RIS 5. HL7 messages consist of data fields.org. please consult the HL7 Version 2. Proprietary and Confidential 4 .hl7. However. differences exist and thus the reader is cautioned: where the specifications differ between the HL7 standard and this document. AMICAS. This means that it will not be used to update the database.3 Standard available through www. it should be represented by pipes || with at least one space in between.

AMICAS.0 HL7 Interface Guide HL7 Support Tables – Definition 2. Inc. Proprietary and Confidential 5 .0 Administration Guide.Vision Series RIS 5. see the Vision Series RIS 5. HL7 Support Tables – Definition You must synchronize Vision Series RIS with a receiving system by configuring the PMIS for the following Support Tables: Support Table Gender Martial Status Ethnicity Relationship Type Code Location Referring Physician Reason Exam Code Insurance Interface All interfaces All interfaces All interfaces All interfaces Inbound Order Entry Inbound Order Entry Inbound Order Entry Inbound Order Entry Inbound ADT and MFN For more information on Support Tables.

Opt.1 ADT^A01. Proprietary and Confidential 6 .ADT ^A01 . 3. The RIS Req column designates which fields are required by Vision Series RIS.Vision Series RIS 5. Length. A05.2 MSH (Message Header Segment) . HL7 Field Name. A03.1. version 2.3 for electronic data exchange. Inbound Messages The AMICAS interface will be a one-way (unidirectional) inbound data transfer.ADT^A08 The following table lists each Message Header segment and their Seq. A02.1 Message Definition Vision Series RIS shall receive the patient message event type ADT^A01 through ADT^A08 which will create or update patient demographics. Rejection Rules. 3. The following inbound interfaces are supported:        ADT BAR MFN ORM ORR ORU ACK See the Glossary for definitions of each interface. The following table lists each supported message segment and their description: Message Segment MSH PID GT1 IN1 IN2 Segment Description Message Header Patient Identification Guarantor Insurance Insurance Refer to the Glossary for the complete message segment definitions. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. AMICAS.0 HL7 Interface Guide Inbound Messages 3. A04.1. Data Type. A06. A07 or ADT^A08 – Registering / Updating a Patient 3. All message types will be treated the same. Inc. Messages received shall conform to the Health Level Seven (HL7) Standard.

Vision Series RIS 5. “P” Production Environment “2. <yyyymmddhhmmss> 4 5 6 7 8 Sending Facility Receiving Application Receiving Facility Date/time of Message Security O O O O O 180 180 180 26 40 HD HD HD TS ST 9 Message Type R R 7 CM “ADT^A04” or “ADT^A08” Rejected if field is empty. Inc. Register or update a patient. echoed back in the MSA_2 of the acknowledgment message. Message unique identifier for the ADT message which will be Rejected if field is empty.3” HL7 version number 10 Message Control ID R R 20 ST 11 Processing ID R 3 PT 12 13 14 15 16 17 18 19 20 Version ID Sequence Number Continuation Pointer Accept Acknowledgement Type Application Acknowledgement Type Country Code Character Set Principal Language Of Message Alternate Character Set Handling Scheme R O O O O O O O O 8 15 180 2 2 2 16 60 20 ID NM ST ID ID ID ID CE ID AMICAS. Proprietary and Confidential 7 .0 HL7 Interface Guide Inbound Messages MSH Seq 1 2 3 HL7 Field Name Field Separator Encoding Characters Sending Application Opt R R O RIS Req Length 1 4 180 Data Type ST ST HD Rejection Rules Vision Series Data Mapping/ Comments "|" "^~\&” <name of the originating application> <name of the originating facility> <name of the receiving application> <name of the receiving facility> Current date/time.

Proprietary and Confidential 8 . Length. The RIS Req column designates which fields are required by Vision Series RIS. PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PID segment per message. 3 Patient ID (Internal ID) R C 20 CX If the unique ID is not PMIS and this field is empty.ADT ^A01 .1. the data must be in the PID 2 field. Opt. 4 Alternate Patient ID B 20 CX 5 Patient Name last name first name middle initial Mother’s Maiden Name Date of Birth R R 90 total 30 30 30 48 XPN Rejected if field is empty. this is rejected if the PID 2 and 3 fields are empty. Inc.Vision Series RIS 5. Patient SS Number <#########> Patient Name <last name^ first name^ middle name> Excess length will be truncated.ADT^A08 The following table lists each Patient Identification Definition segment and their Seq. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Will not be set if PMIS code does not match Patient DOB <yyyymmdd> Patient Gender <PMIS code only> (reference the RIS Gender support table) 26 8 Sex O 1 ST 9 Patient Alias O 48 XPN Patient Ethnicity <PMIS code only> (reference the RIS Ethnicity support table) 10 Race O 1 IS AMICAS. HL7 Field Name. 2 Patient ID (External ID) B C 20 CX Patient Unique Identifier <Internal Patient ID Number> Patient Jacket Number <Jacket Number> This field is required if the interface is using the jacket number as the unique identifier. Data Type.0 HL7 Interface Guide Inbound Messages 3. Rejection Rules.3 PID (Patient Identification Definition Segment) .Patient ID O 4 SI If the unique ID is not PMIS. “1” 1 Set ID . 6 7 O O R XPN TS Rejected if field is empty and if not at least <yyyymmdd>.

Vision Series RIS 5. 11 Patient Address O 151 total 60 40 40 2 9 XAD 12 County Code B 4 IS Patient Home Phone – numeric only <area code and phone number> Patient Work Phone – numeric only <area code and phone number> 13 Phone Number . NULL on the inbound message if the patient jacket should not be changed. reject if blank is used as the unique and PID 3 must be NULL ID. Country does not update. Alphanumeric. 18 Patient Account Number O C 20 CX AMICAS. guarantors and insureds.0 HL7 Interface Guide Inbound Messages PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Patient Address <address 1^ address 2^ city^ state (standard abbreviation only)^ zip (alphanumeric with no validation) Excess length will be truncated.Home O 12 XTN 14 Phone Number .Business O 12 XTN 15 Language . Proprietary and Confidential 9 . The patient PMIS must be unique to all patients. Inc.Patient O 60 CE Patient Marital Status <PMIS code only> (reference the RIS Marital Status support table) 16 Marital Status O 1 IS 17 Religion O 3 IS Patient Unique Identifier <Patient File PMIS> This field is required if the interface is configured to use the patient PMIS number as the unique If the PMIS is used as the identifier. then PID_3 Jacket if you do not wish to Number must be modify the jacket. If the PMIS unique ID.

Vision Series RIS 5. Data Type. Length.ADT ^A01 . GT1 Seq 1 HL7 Field Name Opt RIS Req Length Data Type SI Rejection Rules Vision Series Data Mapping/ Comments One GT1 segment per message.Patient B 16 ST Rejected if not 9 sequential numbers. Inc. 20 21 22 23 24 25 26 27 28 29 30 Drivers License NumberPatient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator O O O O O O O O O O O 25 20 3 60 2 2 4 60 80 26 1 CM CX IS ST ID NM IS CE CE TS ID Reject if not at least <yyyymmdd>. No validation is performed for length or duplicates. Rejection Rules. Proprietary and Confidential 10 .4 GT1 (Guarantor Segment) . and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. "1" Set ID .0 HL7 Interface Guide Inbound Messages PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Patient Social Security Number <#########> Numeric with no special characters. 19 SSN Number .ADT^A08 The following table lists each Guarantor segment and their Seq.GT1 R 4 AMICAS. Opt. The RIS Req column designates which fields are required by Vision Series RIS.1. HL7 Field Name. Patient Date of Death <yyyymmdd> 3.

0 HL7 Interface Guide Inbound Messages GT1 Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments 2 Guarantor Number O C 59 CX Guarantor Unique Identifier <Guarantor PMIS> This field is required if If this field is the the interface is guarantor’s ID then configured to accept rejected if field is empty or guarantors. Inc. Guarantor Name <last name^ first name^ middle name> Excess length will be truncated. reject if blank.Vision Series RIS 5. Guarantor Spouse Name Guarantor Address <address 1^ address 2^ city^ state (standard abbreviation only)^ zip (alphanumeric with no validation)> Excess length will be truncated. Suffix does not update. Will be ignored if code does not match Guarantor Gender <PMIS code only> (reference the RIS Gender support table) 9 Guarantor Administrative Sex O O 1 ST AMICAS. The if the PMIS code does not guarantor PMIS match. Country does not update. guarantors and insureds. Alphanumeric. number must be unique to all patients. 4 Guarantor Spouse Name O XPN 5 Guarantor Address O 151 total 60 40 40 2 9 XAD 6 Guarantor Ph Num .Home O 12 XTN 7 Guarantor Ph Num Business O C 12 XTN If not found in GT1-7..7 then it will be read from GT1-7.1 GT1-7. Proprietary and Confidential 11 .7 <^^^^^^area code and phone number> 8 Guarantor Date/Time Of Birth O R 26 TS If this field is configured to identify the guarantor or if Guarantor DOB GT1-3 is other than the patient. it will associate the patient as the guarantor. Guarantor Home Phone – numeric only <area code and phone number> Guarantor Work Phone – numeric only 3 Guarantor Name R R 90 total 30 30 30 48 XPN If this field is blank. <yyyymmdd> Rejected if format is not at least <yyyymmdd>.

Email <(Area Code)Phone Number^Fax Number^Email Address> 17 Guarantor Employer Address O 106 XAD 18 Guarantor Employer Phone Number O 40 XTN 19 20 21 22 23 24 25 26 Guarantor Employee ID Number Guarantor Employment Status Guarantor Organization Name Guarantor Billing Hold Flag Guarantor Credit Rating Code Guarantor Death Date And Time Guarantor Death Flag Guarantor Charge Adjustment Code O O O O O O O O 20 2 130 1 80 26 1 80 CX IS XON ID CE TS ID CE AMICAS. 10 Guarantor Type O 2 IS Required if GT1-3 is other than the patient. 11 Guarantor Relationship O C 80 CE Rejected if the field is empty or if the relationship code does not match.Vision Series RIS 5. special characters. Guarantor Relationship – Patient relation to Guarantor <PMIS code only> (reference the RIS Relationship support table) 12 Guarantor SSN O C 11 ST Guarantor SS Number <#########> If this field is configured to Numeric with no identify the guarantor. Fax. No validation is performed for length or duplicates. 13 14 15 16 Guarantor Date – Begin Guarantor Date – End Guarantor Priority Guarantor Employer Name O O O O 8 8 2 130 DT DT NM XPN Guarantor Employer Name <Employer Name> Guarantor Employer Address <Address 1^^City^State^Zip> Employer Phone.0 HL7 Interface Guide Inbound Messages GT1 Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Guarantor Qualifier “1” if person and “2” if non-person. reject if blank. Proprietary and Confidential 12 . “1” is the default. Inc.

AMICAS.0 HL7 Interface Guide Inbound Messages GT1 Seq 27 28 HL7 Field Name Guarantor Household Annual Income Guarantor Household Size Opt O O RIS Req Length 10 3 Data Type CP NM Rejection Rules Vision Series Data Mapping/ Comments 29 Guarantor Employer ID Number O 20 CX Guarantor Employer ID <PMIS code only> (Reference the RIS Employer support table.) 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 Guarantor Marital Status Code Guarantor Hire Effective Date Employment Stop Date Living Dependency Ambulatory Status Citizenship Primary Language Living Arrangement Publicity Code Protection Indicator Student Indicator Religion Mother’s Maiden Name Nationality Ethnic Group Contact Person’s Name Contact Person’s Telephone Number Contact Reason Contact Relationship Job Title Job Code/Class Guarantor Employer’s Organization Name Handicap Job Status Guarantor Financial Class O O O O O O O O O O O O O O O O O O O O O O O O O 80 8 8 2 2 80 60 2 80 1 2 80 48 80 80 48 40 80 2 20 20 130 2 2 50 CE DT DT IS IS CE CE IS CE ID IS CE XPN CE CE XPN XTN CE IS ST JCC XON IS IS FC Guarantor Ethnicity <PMIS code only> (reference the RIS Ethnicity support table) 55 Guarantor Race O 1 IS Will be ignored if code does not match. Inc.Vision Series RIS 5. Proprietary and Confidential 13 .

This field will determine insurance ranking for the patient. Data Type. and Mapping/Comments: Information provided will not update the insurance support tables. If using SelfPay.IN1 R R 4 SI Rejected if field is empty. 4 5 Insurance Company Name Insurance Company Address O O 130 106 XON XAD AMICAS. No limit. then reject. Any field name that has a blank cell in the Rejection Rules column does not have any rejections. The RIS Req column designates which fields are required by Vision Series RIS. HL7 Field Name.Vision Series RIS 5.ADT^A08 The following table lists each Insurance segment and their Seq. Opt. Length.0 HL7 Interface Guide Inbound Messages 3. Proprietary and Confidential 14 . Insurance Coverage Plan Code <Plan Code> Insurance Company ID <Insurance Coverage Plan PMIS code> 2 Insurance Plan ID R C 60 CE Refer to IN1-3 if blank 3 Insurance Company ID R R 59 CX (reference the RIS Insurance Coverage If IN1-2 is blank and IN1support table. Inc. 1 Set ID . Rejection Rules. a Self-Pay Insurance Coverage and PMIS is required in the support table. May send 2 and not 1.ADT ^A01 . Segments can be sent non-sequential. etc.) 3 does not match.5 IN1 (Insurance Segment) . The ADT will fail if this PMIS code is invalid. IN1 Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Insurance Patient Plan Rank <sequence identifier> 1 = primary 2 = secondary.1.

Though RIS only displays First and Last. Patient name is used if this field is left blank. it will associate the patient as the insured. Proprietary and Confidential 15 . Excess length will be truncated. Required if IN1-16 is other than the patient. 16 Name Of Insured O 0 90 total 30 30 30 XPN If this field is blank.0 HL7 Interface Guide Inbound Messages IN1 Seq 6 7 8 9 10 11 12 HL7 Field Name Insurance Co Contact Person Insurance Co Phone Number Group Number Group Name Insured’s Group Emp ID Insured’s Group Emp Name Plan Effective Date Opt O O O O O O O RIS Req Length 48 40 12 130 12 130 8 Data Type XPN XTN ST XON CX XON DT Rejection Rules Vision Series Data Mapping/ Comments Member Number <Member Number> Plan Effective Start Date <yyyymmdd> Plan Expiration Date <yyyymmdd> 13 14 Plan Expiration Date Authorization Information O O 8 55 DT CM 15 Plan Type O 3 IS Insurance Coverage Type <Coverage Type Name> Insured Name <last name^first name^ middle name> Suffix does not update. Middle and Last are sent through standard charge out.Vision Series RIS 5. 17 Insured’s Relationship To Patient O C 80 CE Rejected if the field is empty or if the relationship code does not match Patient Relation to Insured <PMIS code only> (reference the RIS Relationship support table) AMICAS. Inc. the First.

Country does not update. reject if blank. Proprietary and Confidential 16 . 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 Assignment Of Benefits Coordination Of Benefits Coord Of Ben.0 HL7 Interface Guide Inbound Messages IN1 Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Required if IN1-16 is provided or If this field is configured to identify the insured. Day Company Plan Code O O O O O O O O O O O O O O O O 2 2 2 1 8 1 8 2 15 26 60 2 2 4 4 8 IS IS ST ID DT ID DT IS ST TS XCN IS IS NM NM IS Policy Number 36 Policy Number O 15 ST <Policy Number> Alphanumeric 37 38 39 Policy Deductible Policy Limit – Amount Policy Limit – Days O B O 12 12 4 CP CP NM AMICAS. Inc. Priority Notice Of Admission Flag Notice Of Admission Date Report Of Eligibility Flag Report Of Eligibility Date Release Information Code Pre-Admit Cert (PAC) Verification Date/Time Verification By Type Of Agreement Code Billing Status Lifetime Reserve Days Delay Before L.R.Vision Series RIS 5. Vision Series Data Mapping/ Comments Insured DOB <yyyymmdd> Insured Address 18 Insured’s Date Of Birth O C 26 TS 19 Insured’s Address O 151 total 60 40 40 2 9 <address 1^address 2^city^ XAD state (standard abbreviation only)^zip (alphanumeric with no validation)> Excess length will be truncated.

The RIS Req column designates which fields are required by Vision Series RIS. Data Type. reject configured to accept if blank. Proprietary and Confidential 17 .ADT ^A01 .Vision Series RIS 5.0 HL7 Interface Guide Inbound Messages IN1 Seq 40 41 42 HL7 Field Name Room Rate . Alphanumeric. HL7 Field Name. Opt.ADT^A08 The following table lists each Insurance segment and their Seq. Length. Rejection Rules. guarantors and insureds.1. Inc. 49 Insured’s ID Number O C 12 CX 3. the Insured.6 IN2 (Insurance Segment) . and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.Semi-Private Room Rate – Private Insured’s Employment Status Opt B B O RIS Req Length 12 12 60 Data Type CP CP CE Rejection Rules Vision Series Data Mapping/ Comments Insured Gender 43 Insured’s Administrative Sex O O 1 IS Will be ignored if code does not match <PMIS code only> (reference the RIS Gender support table) Insured’s Employer Address <Address 1^^City^ State^Zip> 44 Insured’s Employer’s Address O 151 XAD 45 46 47 48 Verification Status Prior Insurance Plan ID Coverage Type Handicap O O O O 2 8 3 2 ST IS IS IS Insured Unique Identifier <Insured PMIS code only> This field is required if If this field is configured to the interface is identify the insured. IN2 Seq 1 HL7 Field Name Insured's Employee ID Opt O RIS Req Length 59 Data Type CX Rejection Rules Vision Series Data Mapping/ Comments AMICAS. The insured PMIS number must be unique to all patients.

reject <SS Number format if blank. Inc. Proprietary and Confidential 18 . #########> Insured's Employer Name and ID <Employer Name^PMIS or Unique Identification Number> 3 Insured's Employer Name and ID O 130 XCN 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Employer Information Data Mail Claim Party Medicare Health Ins Card Number Medicaid Case Name Medicaid Case Number Military Sponsor Name Military ID Number Dependent Of Military Recipient Military Organization Military Station Military Service Military Rank/Grade Military Status Military Retire Date Military Non-Avail Cert On File Baby Coverage Combine Baby Bill Blood Deductible Special Coverage Approval Name Special Coverage Approval Title Non-Covered Insurance Code Payor ID Payor Subscriber ID Eligibility Source O O O O O O O O O O O O O O O O O O O O O O O O 1 1 15 48 15 48 20 80 25 25 14 2 3 8 1 1 1 1 48 30 8 59 59 1 IS IS ST XPN ST XPN ST CE ST ST IS IS IS DT ID ID ID ST XPN ST IS CX CX IS AMICAS.0 HL7 Interface Guide Inbound Messages IN2 Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments 2 Insured's Social Security Number O C 11 ST If this field is configured to Insured's SS Number identify the insured.Vision Series RIS 5.

Proprietary and Confidential 19 . Inc.0 HL7 Interface Guide Inbound Messages IN2 Seq 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 HL7 Field Name Room Coverage Type/Amount Policy Type/Coverage Daily Deductible Living Dependency Ambulatory Status Citizenship Primary Language Living Arrangement Publicity Code Protection Indicator Student Indicator Religion Mother's Maiden Name Nationality Ethnic Group Marital Status Insured's Employment Start Date Employment Stop Date Job Title Job Code/Class Opt O O O O O O O O O O O O O O O O O O O O RIS Req Length 25 25 25 2 2 80 60 2 80 1 2 80 48 80 80 80 8 8 20 20 Data Type CM CM CM IS IS CE CE IS CE ID IS CE XPN CE CE CE DT DT ST JCC Rejection Rules Vision Series Data Mapping/ Comments 48 Job Status O 2 IS Insured's Employment Status <PMIS Code or Employment Status Code> 49 50 51 52 53 54 Employer Contact Person Name Employer Contact Person Phone Number Employer Contact Reason Insured Contact Person Name Insured Contact Person's Phone Number Employer Contact Person Reason O O O O O O 48 40 2 48 40 2 XPN XTN IS XPN XTN IS AMICAS.Vision Series RIS 5.

The following table lists each supported message segment and their description: Message Segment MSH Segment Description Message Header AMICAS.Vision Series RIS 5.1 Message Definition These messages will allow the RIS to merge two patients. Patients will be identified by using either the PMIS code or the Patient Jacket number. Contact Reason Insurance Co.0 HL7 Interface Guide Inbound Messages IN2 Seq 55 56 57 58 59 60 61 62 HL7 Field Name Relationship To The Patient Start Date Relationship To The Patient Stop Date Insurance Co.2 ADT^A34 or ADT^A40 – HL7 Message Merge Type 3. Proprietary and Confidential 20 . Patient Demographics will not be modified using a merge message. Inc. Contact Phone Number Policy Scope Policy Source Patient Member Number Guarantor's Relationship To Insured Insured's Phone Number Home Insured's Employer Phone Number Military Handicapped Program Suspend Flag Copay Limit Flag Stoploss Limit Flag Insured Organization Name and ID Insured Employer Organization Name and ID Race HCFA Patient's Relationship to Insured Opt O O O O O O O O RIS Req Length 8 8 2 40 2 2 60 80 Data Type DT DT IS XTN IS IS CX CE Rejection Rules Vision Series Data Mapping/ Comments 63 O 40 XTN Insured Phone Number <(Area Code)Phone Number> 64 65 66 67 68 69 70 71 72 O O O O O O O O O 40 60 1 1 1 130 130 80 60 XTN CE ID ID ID XON XON CE CE 3.2.

Opt. MSH Seq 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgement Type Application Acknowledgement Type Country Code Character Set Principal Language Of Message Opt R R O O O O O O R R R R O O O O O O O R R R R R RIS Req Length 1 4 180 180 180 180 26 40 7 20 3 60 15 180 2 2 2 16 60 Data Type ST ST HD HD HD HD TS ST CM ST PT ID NM ST ID ID ID ID CE “AL” “NE” Rejected if field is empty. Rejection Rules.Vision Series RIS 5. Data Type.2. 3.0 HL7 Interface Guide Inbound Messages Message Segment EVN PID MRG Segment Description Event Type Segment Patient Identification Patient Merge Information See the Glossary for definitions of each interface. Rejected if field is empty. Length. “ADT^A34” or “ADT^A40” System date/time. Proprietary and Confidential 21 . The RIS Req column designates which fields are required by Vision Series RIS. Rejection Rules Vision Series Data Mapping/ Comments "|" "^~\&" <Sending Application> <Sending Facility> <Receiving Application> AMICAS.3” HL7 version number Rejected if field is empty. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. HL7 Field Name. Inc. Rejected if field is empty. <yyyymmddhhmmss> “P” “2. Current date/time <yyyymmddhhmmss> Rejected if field is empty.2 MSH (Message Header Segment) – ADT^A34 or ADT^A40 The following table lists each Message Header segment and their Seq.

Rejection Rules. Length. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Opt.Patient ID Patient ID (External ID) O O 4 20 SI CX AMICAS. “1” 1 2 Set ID . Data Type.4 PID (Patient Identification Definition Segment) . Proprietary and Confidential 22 . The RIS Req column designates which fields are required by Vision Series RIS. Data Type. Rejection Rules. HL7 Field Name. Opt. EVNSeq 1 2 3 4 HL7 Field Name Event Type Code Recorded Date/Time Date/Time Planned Event Event Reason Code Opt O O O O RIS Req Length 3 26 26 3 Data Type ID TS TS IS Rejection Rules Vision Series Data Mapping/ Comments “A34” or “A40” Current Date/Time <yyyymmddhhmmss> Operator ID & Name 5 Operator ID O 60 XCN <User ID^User Name (FML)> Current Date/Time <yyyymmddhhmmss> 6 Event Occurred O 26 TS 3.2. HL7 Field Name.ADT^A34 or ADT^A40 The following table lists each Event Type segment and their Seq.Vision Series RIS 5.2. Length. The RIS Req column designates which fields are required by Vision Series RIS.3 EVN (Event Type Segment) . PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PID segment per message. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.ADT ^A34 or ADT^A40 The following table lists each Patient Identification Definition segment and their Seq.0 HL7 Interface Guide Inbound Messages 20 Alternate Character Set Handling Scheme O 20 ID 3. Inc.

U) <PMIS code or gender code? Patient Alias <Alias field> Rejected if the race code does not match this field.Home O 40 XTN 14 Phone Number . M.Vision Series RIS 5. Patient Ethnicity <PMIS code or ethnicity code> Patient Address <address 1^address 2^city^ state^zip^country> Country Code <Country field> Patient Home Phone. Fax. O. 4 Alternate Patient ID Patient Name last name first name middle initial Mother’s Maiden Name Date of Birth O 20 CX 5 R R 48 XPN Rejected if field is empty or if suffix code does not match this field. RIS Internal ID Patient Unique Identifier <Defined Unique ID> 3 Patient ID (Internal ID) R R 20 CX Rejected if field is empty.Business O 12 XTN 15 16 17 Language . Jacket. Patient Name <last name^ first name^ middle name^suffix> 6 7 O O R 48 26 XPN TS Rejected if field is empty and if not at least <yyyymmdd>. Inc. Patient Marital Status <PMIS code for Marital Status Code> AMICAS. Patient DOB <yyyymmdd> Patient Gender (F.0 HL7 Interface Guide Inbound Messages PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Patient Unique Identifier <Defined Unique ID> PMIS. SSN. Email <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Patient Work Phone <(Area Code)Phone Number^Additional text in phone number field> 8 Sex O R 1 ST 9 Patient Alias O 48 XPN 10 Race O 80 IS 11 Patient Address O 106 XAD 12 County Code B 4 IS 13 Phone Number .Patient Marital Status Religion O O O 60 80 80 CE IS IS Rejected if the martial status code does not match this field. Rejected if the field is empty or if the gender code does not match this field. Proprietary and Confidential 23 .

Inc.ADT^A34 or ADT^40 The following table lists each Patient Merge Information segment and their Seq. Data Type.2. Opt.Vision Series RIS 5.Patient B 16 ST 20 21 22 23 24 25 26 27 28 29 30 Drivers License NumberPatient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator O O O O O O O O O O O 25 20 80 60 1 2 80 60 80 26 1 CM CX IS ST ID NM IS CE CE TS ID Reject if not at least <yyyymmdd>.External O 20 CX 5 6 7 Prior Visit Number Prior Alternate Visit ID Prior Patient Name O O O 20 20 48 AMICAS. reject if blank and PID 3 must be NULL. Proprietary and Confidential 24 .Internal R 20 CX 2 Prior Alternate Patient ID O 20 CX 3 Prior Patient Account Number O 20 CX 4 Prior Patient ID . Length. Patient Social Security Number <#########> 19 SSN Number . Rejection Rules. HL7 Field Name. <Patient File PMIS> Rejected if not 9 sequential numbers.5 MRG (Patient Merge Information Segment) . Patient Date of Death <yyyymmdd> 3. and Mapping/Comments: MRG Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Patient Unique Identifier <Defined Unique ID> Patient Unique Identifier <Defined Unique ID> Prior Patient PMIS <Patient File PMIS> Prior Patient Unique Identifier <Internal Patient ID Number> 1 Prior Patient ID .0 HL7 Interface Guide Inbound Messages PID Seq 18 HL7 Field Name Opt RIS Req C Length Data Type CX Rejection Rules Vision Series Data Mapping/ Comments Patient Account Number O 20 If the PMIS is used as the Patient PMIS unique ID.

3 onward.3 BAR^P05 – Billing Account Update Message Type 3. Rejected if not acceptable sending application. Vision Series Data Mapping/ Comments "^~\&" <Sending Application> <Sending Facility> <Receiving Application> <Interface Engine Name for new customers> or <AMICAS RIS for existing customers> 6 Receiving Facility O 180 HD AMICAS. Update of the Patient Demographics will not be done from this message type. the P01 (add account) event should not longer be used for updating an existing account with financial information. Proprietary and Confidential 25 . The following table lists each supported message segment and their description: Message Segment MSH EVN PID PV1 Segment Description Message Header Event Type Patient Identification Patient Visit See the Glossary for definitions of each interface. Length. From Standard Version 2. HL7 Field Name.2 MSH (Message Header Segment) – BAR^P05 The following table lists each Message Header segment and their Seq. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. 3. Rejection Rules. Data Type.3. The RIS Req column designates which fields are required by Vision Series RIS.3. "|" Must always be "^~\&". Inc.Vision Series RIS 5. Opt. MSH Seq 1 2 3 4 5 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Opt R R O O O Req by RIS R R R Length 1 4 180 180 180 Data Type ST ST HD HD HD Rejection Rules Must always be pipe "|". but only for creating a new financial account.0 HL7 Interface Guide Inbound Messages 3. An ADT message must be used to update the Patient Demographics.1 Message Definition The financial system sends the patient’s billing/accounts information to the Vision Series RIS The P05 event is sent when an existing account is being updated with financial information.

The RIS Req column designates which fields are required by Vision Series RIS. then the “BAR^P05” appropriate specification and logic will be applied to the message.0 HL7 Interface Guide Inbound Messages MSH Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments 7 Date/time of Message O R 26 TS Current date/time <yyyymmddhhmmss>or Rejected if field is <yymmddhhmmssss>or empty or date/time is in <yyymmddhhmmssss> the incorrect format. Rejected if not “P”. Unique Message Identifier “P” “2. Length. Rejected if field is empty. Proprietary and Confidential 26 .1”. HL7 Field Name. Rejection Rules.3” HL7 version number 9 Message Type R R 7 CM 10 11 12 13 14 15 16 17 18 19 20 Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgement Type Application Acknowledgement Type Country Code Character Set Principal Language Of Message Alternate Character Set Handling Scheme O R R O O O O O O O O R R R 20 3 60 15 180 2 2 2 16 60 20 ST PT ID NM ST ID ID ID ID CE ID “AL” 3. Opt.3. EVNSeq 1 HL7 Field Name Event Type Code Opt O RIS Req Length 3 Data Type ID Rejection Rules Vision Series Data Mapping/ Comments AMICAS. “2. “2. Data Type. or <yymmddhhmmss> 8 Security O 40 ST Rejected if the value is not a defined message type (ORM^O01).Vision Series RIS 5. Rejected if not “2.3 EVN (Event Type Segment) – BAR^P05 The following table lists each Event Type segment and their Seq.2” or 2.3”. If it is a define message type.0”. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Inc.

0 HL7 Interface Guide Inbound Messages EVNSeq HL7 Field Name Opt RIS Req Length Data Type TS TS IS Rejection Rules Vision Series Data Mapping/ Comments Current Date/Time <yyyymmddhhmmss> 2 3 4 Recorded Date/Time Date/Time Planned Event Event Reason Code O O O 26 26 3 Operator ID & Name 5 Operator ID O 250 XCN <User ID^User Name (FML)> Current Date/Time <yyyymmddhhmmss> 6 7 Event Occurred Event Facility O O 26 241 TS HD AMICAS.Vision Series RIS 5. Inc. Proprietary and Confidential 27 .

Opt. Patient Jacket Number Patient Name <last name^ first name^ middle name> Excess length will be truncated.0 HL7 Interface Guide Inbound Messages 3.4 PID (Patient Identification Definition Segment) – BAR^P05 The following table lists each Patient Identification Definition segment and their Seq. Proprietary and Confidential 28 . Rejected if the field is empty or if the gender code does not match this field. 6 7 X O XPN TS Rejected if field is empty and if not at least <yyyymmdd>. “1” 1 Set ID . Rejection Rules.Patient ID R 4 SI If the unique ID is not PMIS. 3 Patient ID (Internal ID) R C 20 CX 4 Alternate Patient ID Patient Name last name first name middle initial Mother’s Maiden Name Date of Birth X 20 90 total 30 30 30 48 R 26 CX 5 R R XPN Rejected if field is empty or if suffix code does not match this field.1. 2 Patient ID (External ID) X C 20 CX Patient Unique Identifier <Internal Patient ID Number> Patient Internal ID from RIS. AMICAS. Data Type. this is rejected if the PID 2 and 3 fields are empty. The RIS Req column designates which fields are required by Vision Series RIS. Length. PID 3. If the unique ID is not PMIS and this field is empty. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Inc. Patient DOB <yyyymmdd> Patient Gender <PMIS code only> (reference the RIS Gender support table) Patient Alias <Alias field> Patient Ethnicity <PMIS code only> (reference the RIS Ethnicity support table) 8 Sex O R 1 ST 9 Patient Alias X 48 XPN 10 Race O 1 IS Rejected if the race code does not match this field. HL7 Field Name. the data must be in the PID 2 field.3. PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PID segment per message.Vision Series RIS 5.

No validation is performed for length or duplicates. <Patient File PMIS> Patient Social Security Number <#########> Numeric with no special characters.Business O 12 XTN 15 Language . Country does not update. 19 SSN Number . Patient Marital Status <PMIS code only> (reference the RIS Marital Status support table) 16 Marital Status O 1 IS 17 18 Religion Patient Account Number X O C 3 20 IS CX If the PMIS is used as the Patient Unique unique ID. Inc. Country Code <Country field> Patient Home Phone – numeric only <area code and phone number> Patient Work Phone – numeric only <area code and phone number> 11 Patient Address O 151 total 60 40 40 2 9 XAD 12 County Code X 4 IS 13 Phone Number .Vision Series RIS 5.Patient X 60 CE Rejected if the martial status code does not match this field. reject if blank Identifier and PID 3 must be NULL.0 HL7 Interface Guide Inbound Messages PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Patient Address <address 1^ address 2^ city^ state (standard abbreviation only)^ zip (alphanumeric with no validation) Excess length will be truncated.Patient O 16 ST Rejected if not 9 sequential numbers. Proprietary and Confidential 29 . 20 21 22 23 24 25 26 Drivers License NumberPatient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship X X X X X X X 25 20 3 60 2 2 4 CM CX IS ST ID NM IS AMICAS.Home O 12 XTN 14 Phone Number .

0 HL7 Interface Guide Inbound Messages PID Seq 27 28 29 30 HL7 Field Name Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator Opt X X O O RIS Req Length 60 80 26 1 Data Type CE CE TS ID Rejection Rules Vision Series Data Mapping/ Comments Reject if not at least <yyyymmdd>. Length. 1 Set ID – PV1 O 4 SI 2 Patient Class O R 1 IS Reject if empty or the PMIS code does not match. Patient Date of Death <yyyymmdd> 3. Data Type. The RIS Req column designates which fields are required by Vision Series RIS. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Displayed in RIS separated by a space colon (“ :”).Vision Series RIS 5. Inc. Opt. “1” Appointment Code. Rejection Rules. Proprietary and Confidential 30 .3. HL7 Field Name.5 PV1 (Patient Visit Segment) – BAR^P05 The following table lists each Patient Visit segment and their Seq. PV1 Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PV1 Segment per message. 3 Assigned Patient Location O 80 PL 4 5 6 Admission Type Pre-admit Number Prior Patient Location O O O 2 20 80 IS CX PL AMICAS. for example: O = Outpatient I = Inpatient <PMIS Code or Service Type> Patient location <point of care or nursing station>^<room>^<bed> All other PV1-3 sub components will be ignored.

Pregnancy Indicator <B6 if flag Y else other> 19 20 21 22 Visit Number Financial Class Charge Price Indicator Courtesy Code O O O O 20 50 2 2 CX CM IS IS AMICAS.Vision Series RIS 5. Proprietary and Confidential 31 . 8 Referring Doctor O R 60 XCN 9 Consulting Doctor O R 60 XCN 10 11 12 13 14 15 16 17 18 Hospital Service Temporary Location Preadmit Test Indicator Readmission Indicator Admit Source Ambulatory Status VIP Indicator Admitting doctor Patient Type O O O O O O O O O 3 80 2 2 3 2 2 60 2 IS PL IS IS IS IS IS XCN IS Service Type <PMIS Code for Service Type Code> Visit Number will populate the Order Number field.0 HL7 Interface Guide Inbound Messages PV1 Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Attending (referring) Provider. Inc. <Physician Location PMIS Code or Physician Location Unique Identifier^Last Name^First^Middle Name^Suffix^~PMIS^Last Name^First Name^Middle Name^Suffix> Referring (cc) Provider <Physician Location PMIS Code or Physician Location Unique Identifier ^Last Name^First^Middle Name^Suffix^~PMIS^Last Name^First Name^Middle Name^Suffix> Consulting (cc) Provider <Physician Location PMIS Code or Physician Location Unique Identifier ^Last Name^First^ Middle Name^Suffix^ ~PMIS^Last Name^ First Name^Middle Name^Suffix> 7 Attending Doctor O R 60 XCN Reject if empty or PMIS code does not match. A tilde (~) separates referring from any/all cc physicians.

Vision Series RIS 5.0 HL7 Interface Guide Inbound Messages PV1 Seq 23 24 25 26 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 HL7 Field Name Credit Rating Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount Bad Debt Recovery Amount Delete Account Indicator Delete Account Date Discharge Disposition Discharged to Location Diet Type Servicing Facility Bed Status Account Status Pending Location Prior Temporary Location Admit Date/Time Discharge Date/Time Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID Visit Indicator Other Healthcare Provider Opt O O O O O O R O O R O O O O O O O B O O O O O O O O O O O O Req by RIS Length 2 2 8 12 3 2 1 8 10 12 12 1 8 3 25 80 2 1 2 80 80 26 26 12 12 12 12 20 1 60 Data Type IS IS DT NM NM IS IS DT IS NM NM IS DT IS CM IS IS IS IS PL PL TS TS NM NM NM NM CX IS XCN Rejection Rules Vision Series Data Mapping/ Comments Collection Indicator <Y> or <N> Collection Balance Admit Date <yyyymmdd> Discharge Date <yyyymmdd> Patient Account Balance Patient Weight <Patient Weight> AMICAS. Proprietary and Confidential 32 . Inc.

Master File Update Message Type 3. Some common examples of master files in the healthcare environment include:           staff and health practitioner master file system user (and password) master file location (census and clinic) master file device type and location (e.0 HL7 Interface Guide Inbound Messages 3. In many implementations. etc. as well as providing for a delayed application acknowledgment mode. updates) to this file are made available to various other applications on a routine basis. Inc. printers. The Master File Acknowledgment (MFA) segment returns record-specific acknowledgment information. the initial and requested dates for the event. For each record being changed. transmits update information to other systems (usually to the "owning" system).4. The following table lists each supported message segment and their description: Message Segment MSH MFI MFE ZL7 Segment Description Message Header Master File Identification Master File Entry Insurance Data to Post See the Glossary for definitions of each interface.1 Message Definition In an open-architecture healthcare environment there is often a set of common reference files used by one or more application systems. the Master File Entry (MFE) segment carries the record-level event code (such as add. etc. for review and possible inclusion. The Master Files Notification (MFN) message provides a way of maintaining this synchronization by specifying a standard for the transmission of this data between applications.4 MFN . These files are called master files. The changes (e. The MFN message supports this common case.g. The Master File Identification (MFI) segment identifies the master file being updated as well as the initial and requested dates for file-level events (such as replace file).. Proprietary and Confidential 33 .g.. workstations. but also supports the situation where an application not "owning" a particular master file. adds. update. terminals. and allows the use of either original or enhanced acknowledgment modes. one application system will "own" a particular master file such as the staff and practitioner master file.Vision Series RIS 5.) lab test definition file exam code (radiology) definition file charge master file patient status master patient type master service item master file These common reference files need to be synchronized across the various applications at a given site. AMICAS. These messages use the MSH segment to pass the basic event code (master files notification or acknowledgment). and the recordlevel key identifying the entry in the master file. The MFN message supports the distribution of changes to various master files between systems in either online or batch modes.). deletes.

MSH Seq 1 2 3 4 5 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Opt R R O O O Req by RIS R R R Length 1 4 180 180 180 Data Type ST ST HD HD HD Rejection Rules Must always be pipe "|". Data Type.1”.2 MSH (Message Header Segment) – MFN The following table lists each Message Header segment and their Seq.3”. “2. “2. The RIS Req column designates which fields are required by Vision Series RIS. 8 Security O 40 ST Rejected if the value is not a defined message type (ORM^O01). Inc. Length. “2.4.2” or 2.0 HL7 Interface Guide Inbound Messages 3. Must always be "^~\&". Opt. Rejection Rules.3” HL7 version number AMICAS. Proprietary and Confidential 34 . Rejected if field is empty. “P” or “T” Rejected if not “2.Vision Series RIS 5. 9 Message Type R R 7 CM “MFN” 10 11 12 13 14 15 16 Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgement Type Application Acknowledgement Type O R R O O O O R R R 20 3 60 15 180 2 2 ST PT ID NM ST ID ID Unique Message Identifier Rejected if not “P” or “T”. then the appropriate specification and logic will be applied to the message. "|" Vision Series Data Mapping/ Comments "^~\&" <Sending Application> <Sending Facility> <Receiving Application> <Interface Engine Name for new customers> or <AMICAS RIS for existing customers> Current date/time <yyyymmddhhmmss>or <yymmddhhmmssss>or <yyymmddhhmmssss> or <yymmddhhmmss> 6 Receiving Facility O 180 HD 7 Date/time of Message O R 26 TS Rejected if field is empty or date/time is in the incorrect format. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Rejected if not acceptable sending application. If it is a define message type.0”. HL7 Field Name.

4.3 MFI (Message File Identification Segment) – MFN The following table lists each Message Header segment and their Seq. a.Vision Series RIS 5. Rejection Rules. Proprietary and Confidential 35 . Length. HL7 Table: Master File Identifier Codes Value CDM CLN CMA CMB Description Charge Description Master File Clinic Master File Clinical Study with Phases and Scheduled Master File Clinical Study without Phases but with Scheduled Master File Procedure Master File Comment CPT AMICAS. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. The RIS Req column designates which fields are required by Vision Series RIS. Data Type. Opt. 1 Message File Identifier R 250 CE 2 3 4 5 6 Master File Application Identifier File-Level Event Code Entered Date/Time Effective Date/Time Response Level Code O R O O R 180 3 26 26 2 HD ID TS TS ID UPD <yyyymmddhhmmss> <yyyymmddhhmmss> AL Always sends an ACK. MFI Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments INS <INS^Insurance Master File> Note: See HL7 Table: Master File Identifier Codes. HL7 Field Name. Inc.0 HL7 Interface Guide Inbound Messages MSH Seq 17 18 19 20 HL7 Field Name Country Code Character Set Principal Language Of Message Alternate Character Set Handling Scheme Opt O O O O Req by RIS Length 2 16 60 20 Data Type ID ID CE ID Rejection Rules Vision Series Data Mapping/ Comments 3.

MAC Note: See HL7 Table: Actions Performed on Master Files. The RIS Req column designates which fields are required by Vision Series RIS.4 MFE (Message File Entry Segment) – MFN The following table lists each Message Header segment and their Seq. Length. Proprietary and Confidential 36 . MFE Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments MAD. <yyyymmddhhmmss> <yyyymmddhhmmss> 1 Record-Level Event Code R 3 ID 2 3 MFN Control ID Effective Date/Time C O 20 26 ST TS AMICAS. 3.Vision Series RIS 5. Rejection Rules. MDC. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Inc. MUP. MDL. HL7 Field Name.0 HL7 Interface Guide Inbound Messages Value DEP DXC INS INV LOC MOD OMA OMB OMC OMD OME PHY PRA STF ZIP Description Procedure Category Code Master File Diagnosis Code Master Record Insurance Master File Inventory Master File Location Master file CPT Code Modifier Master File Numerical Observation Master File Categorical Observation Master File Observation Batteries Master File Calculated Observations Master File Other Observation/Service Item Master File Physician Master File Practitioner Master File Staff Master File Zip Code Master File Comment AMICAS currently updates this file.4. Data Type. Opt.

but do not delete it from the database. MFN Seq HL7 Field Name Opt Req by Length RIS Data Type Rejection Rules Vision Series Data Mapping/ Comments Location <PMIS^Name^ Address1& Address2&City& State& ZipCode^Phone&&&Email&&&fax^ Contact^^Plan Insurance Type Code^^^> 1 Location R 400 CE AMICAS.4. The RIS Req column designates which fields are required by Vision Series RIS. Inc.Vision Series RIS 5. Discontinue using the record in the master file. Delete the record from the master file. 4 Primary Key Value – MFE R 200 Varies a.5 ZL7 (Insurance Data to Post Segment) – MFN The following table lists each Message Header segment and their Seq. Reactivate the deactivated record. Rejection Rules. DX and ZIP use Code all others use the PMIS Code.0 HL7 Interface Guide Inbound Messages MFE Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments <Identifier -Location PMIS> This is the search key for the PMIS Code depending upon the support table. Proprietary and Confidential 37 . Deactivate. Update the record for the master file. HL7 Table: Actions Performed on Master Files Value MAD MDL MUP MDC Description Add the record to the master file. Data Type. Length. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. MAC 3. HL7 Field Name. Opt.

Proprietary and Confidential 38 . This includes placing new orders.2 MSH (Message Header Segment) – ORM^O01 The following table lists each Message Header segment and their Seq. etc. cancellations. The RIS Req column designates which fields are required by Vision Series RIS. The trigger event for this message is any change to an order. updates. Data Type.5. HL7 Field Name. The following table lists each supported message segment and their description: Message Segment MSH PID PVI NTE ORC OBR OBX Segment Description Message Header Patient Identification Patient Visit Notes Common Order Observation Request Observation Result See the Glossary for definitions of each interface. "|" Must always be "^~\&". Such changes include submission of new orders.1 Message Definition Per HL7. Rejected if not acceptable sending application. patient and non-patient specific orders. Rejection Rules. Vision Series Data Mapping/ Comments "^~\&" <Sending Application> <Sending Facility> <Receiving Application> <Interface Engine Name for new customers> or <AMICAS RIS for existing customers> 6 Receiving Facility O 180 HD AMICAS. holding orders.5.0 HL7 Interface Guide Inbound Messages 3. 3. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.5 ORM^O01 – Order Message Type 3. Length. etc. discontinuing orders. canceling existing orders.Vision Series RIS 5. Inc. the function of this message is to initiate the transmission of information about an order. MSH Seq 1 2 3 4 5 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Opt R R O O O Req by RIS R R R Length 1 4 180 180 180 Data Type ST ST HD HD HD Rejection Rules Must always be pipe "|". Opt.

3” HL7 version number 9 Message Type O R 13 CM 10 11 12 13 14 15 16 17 18 19 20 Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgement Type Application Acknowledgement Type Country Code Character Set Principal Language Of Message Alternate Character Set Handling Scheme R R R O O O O O O O O R R R 20 3 60 15 180 2 2 2 16 60 20 ST PT ID NM ST ID ID ID ID CE ID 3. then the “ORM^O01” appropriate specification and logic will be applied to the message. Length.3 PID (Patient Identification Definition Segment) . Opt. AMICAS.0 HL7 Interface Guide Inbound Messages MSH Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments 7 Date/time of Message O R 26 TS Current date/time <yyyymmddhhmmss>or Rejected if field is <yymmddhhmmssss>or empty or date/time is in <yyymmddhhmmssss> the incorrect format.5. “2. “2. Rejected if field is empty. Inc.1”. Unique Message Identifier “P” or “T” “2.Vision Series RIS 5. HL7 Field Name.ORM^O01 The following table lists each Patient Identification Definition segment and their Seq. Rejected if not “P” or “T”. Rejected if not “2.0”. If it is a define message type.3”. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. The RIS Req column designates which fields are required by Vision Series RIS. Rejection Rules.2” or 2. or <yymmddhhmmss> 8 Security O 40 ST Rejected if the value is not a defined message type (ORM^O01). Data Type. Proprietary and Confidential 39 .

MSA6 = [Field] [Field Name] [error] Reject if not formatted correctly. MSA1 = [ACK Code]. Country does not update. 8 Administrative Sex O O 1 ST 9 Patient Alias O 48 XPN 10 Race O 250 IS 11 Patient Address O 250 XAD AMICAS. Proprietary and Confidential 40 . Patient DOB <yyyy^mm^dd> or <yyyymmdd> Patient Gender <PMIS code only> (reference the Gender support table) Patient Alias <Alias field> Patient Ethnicity Rejected if the ethnicity <PMIS code only> code does not match this (reference the RIS field. Rejected if the gender code does not match. Ethnicity support table) Patient Address <address 1^ address 2^ city^ state (standard abbreviation only)^ zip (alphanumeric with no validation) Excess length will be truncated. MSA6 = [Field] [Field Name] [error] Reject if empty. not formatted correctly or the suffix code does not match. Inc.Patient ID O R 4 SI 2 Patient ID (External ID) B 20 CX Reject if empty. MSA6 = [Field] [Field Name] [error] Patient Identifier Number <Patient Identifier Number> 3 Patient Identifier List R R 250 CX 4 Alternate Patient ID . MSA1 = [ACK Code].PID C 20 CX 5 Patient Name last name first name middle name suffix prefix Mother’s Maiden Name Date/Time of Birth R R 250 XPN <last name^first name^ middle name^suffix^prefix> 6 7 O O R 48 26 XPN TS Rejected if field is empty and if not formatted correctly. MSA1 = [ACK Code].0 HL7 Interface Guide Inbound Messages PID Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Rejected if not empty or “1”. MSA6 = [Field] [Field Name] [error] Vision Series Data Mapping/ Comments One PID segment per message. MSA1 = [ACK Code].Vision Series RIS 5. “1” 1 Set ID .

Alphanumeric. Patient Social Security Number <nnnnnnnnn> or <nnn-nnn-nnn> Numeric with no special characters. If the PMIS is used as the unique ID. MSA6 = [Field] [Field Name] [error] AMICAS. MSA1 = [ACK Code].Home O 250 XTN 14 Phone Number .Business O 250 XTN 15 Language . then PID_3 Jacket Number must be NULL on the inbound message. Inc. 18 Patient Account Number O C 250 CX Rejected if not formatted correctly. No validation is performed for length or duplicates. The patient PMIS must be unique to all patients.0 HL7 Interface Guide Inbound Messages PID Seq 12 HL7 Field Name Opt Req by RIS Length Data Type IS Rejection Rules Vision Series Data Mapping/ Comments Country Code <Country field> <home phone number^fax number^^email address> Patient Work Phone – numeric only <area code and phone number> County Code B 4 13 Phone Number . guarantors and insureds. MSA1 = [ACK Code].Patient O 60 CE Patient Marital Status <PMIS code> or <Jacket Number> or <SSN> (reference the RIS Marital Status support table) 16 Marital Status O 250 IS Rejected if the marital status code does not match this field. MSA6 = [Field] [Field Name] [error] 19 SSN Number .Patient B C 16 ST Rejected if formatted correctly.Vision Series RIS 5. Proprietary and Confidential 41 . 17 Religion O 3 IS Patient Unique Identifier <Patient File PMIS> or <Jacket Number> or <SSN> This field is required if the interface is configured to use the patient PMIS number as the unique identifier.

and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.5. The RIS Req column designates which fields are required by Vision Series RIS. then Global Service Type will be selected by default. PV1 Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PV1 Segment per message. Length. Rejection Rules. 1 Set ID – PV1 O 4 SI 2 Patient Class R R 1 IS Reject if empty or the PMIS code does not match. If the PV1 segment is missing. “1” Patient type.Vision Series RIS 5. Proprietary and Confidential 42 . Inc. Opt. HL7 Field Name. AMICAS.16 will be used for the referring physician. the value in OBR. for example: E = Emergency Room O = Outpatient I = Inpatient If PV1 is not included. Data Type.4 PV1 (Patient Visit Segment) – ORM^O01 The following table lists each Patient Visit segment and their Seq.0 HL7 Interface Guide Inbound Messages PID Seq 20 21 22 23 24 25 26 27 28 HL7 Field Name Drivers License NumberPatient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veterans Military Status Nationality Opt O O O O O O O O O Req by RIS Length 25 20 3 60 2 2 4 60 80 Data Type CM CX IS ST ID NM IS CE CE Rejection Rules Vision Series Data Mapping/ Comments 29 Patient Death Date/Time O 26 TS Patient Death Date and Time <yyyy^mm^dd> or <yyyymmdd> 30 Patient Death Indicator O 1 ID 3.

8 Referring Doctor O R 60 XCN AMICAS. Physician matching will occur only on PMIS.8. Physician Referring (cc) Provider matching will occur only <Physician Location on PMIS. 7 Attending Doctor O R 60 XCN Attending (referring) Provider. Displayed in RIS separated by a space colon (“ :”).7 will be ~PMIS^Last Name^ used as the referring physician and PV1. Inc.7 will be Unique Identifier ^Last used as the referring Name^First^ physician and PV1. If the PV1 First Name^Middle segment is not found Name^Suffix> then the value in OBR16 will be used as the referring physician. A Tilde (~) separates reffering from any/all cc physicians. PV1. The first name is also required if RIS creates the physician record from the message. Reject if the PMIS or Last Name empty. Proprietary and Confidential 43 .0 HL7 Interface Guide Inbound Messages PV1 Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Patient location <point of care or nursing station>^<room>^<bed> All other PV1-3 sub components will be ignored.Vision Series RIS 5. If the PV1 segment is not found then the value in OBR16 will be used as the referring physician.7 and Middle Name^Suffix^ PV1. The first name is also required if RIS creates the physician record from the message. <Physician Location If the PV1 segment has PMIS Code or a value for PV1.8 will First Name^Middle Name^Suffix> be used as the CC physician.8 will Middle Name^Suffix^ be used as the CC ~PMIS^Last Name^ physician. 3 Assigned Patient Location O 80 PL 4 5 6 Admission Type Pre-admit Number Prior Patient Location O O O 2 20 80 IS CX PL Reject if the PMIS or Last Name empty. PMIS Code or Physician Location If the PV1 segment has a Unique Identifier ^Last Name^First^ value for PV1. PV1.7 and Physician Location PV1.8.

PV1-9 will be used as the CC physician. Pregnancy Indicator <B6 if flag Y else other> 16 17 18 VIP Indicator Admitting doctor Patient Type O O O 2 60 2 IS XCN IS 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Visit Number Financial Class Charge Price Indicator Courtesy Code Credit Rating Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount Bad Debt Recovery Amount Delete Account Indicator O O O O O O O O O O O O O O O O 20 50 2 2 2 2 8 12 3 2 1 8 10 12 12 1 CX CM IS IS IS IS DT NM NM IS IS DT IS NM NM IS AMICAS. Vision Series Data Mapping/ Comments Consulting (cc) Provider <Physician Location PMIS Code or Physician Location Unique Identifier ^Last Name^First^ Middle Name^Suffix^ ~PMIS^Last Name^ First Name^Middle Name^Suffix> 9 Consulting Doctor O R 60 XCN 10 11 12 13 14 15 Hospital Service Temporary Location Preadmit Test Indicator Readmission Indicator Admit Source Ambulatory Status O O O O O O 3 80 2 2 3 2 IS PL IS IS IS IS Reject if empty or PMIS code does not match last name. Proprietary and Confidential 44 . Inc. The first name is also required if RIS creates the physician record from the message. Physician matching will occur only on PMIS.0 HL7 Interface Guide Inbound Messages PV1 Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Reject if the PMIS or Last Name is empty.Vision Series RIS 5. Service Type <PMIS Code for Service Type Code> Visit Number will populate the Order Number field.

and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Data Type.5 NTE (Notes and Comments Segment) – ORM^O01 The following table lists each Patient Visit segment and their Seq.5. <^^^code ^^^^^ description> 43 44 45 46 47 48 49 50 51 52 Prior Temporary Location Admit Date/Time Discharge Date/Time Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID Visit Indicator Other Healthcare Provider O O O O O O O O O O 80 26 26 12 12 12 12 20 1 60 PL TS TS NM NM NM NM CX IS XCN Patient Weight <Patient Weight> Admit Date <yyyymmdd> Discharge Date <yyyymmdd> 3. Length. Location to schedule the exam. “1” <comment text> NTE following the PID will be a Patient comment. Proprietary and Confidential 45 . Opt. Rejection Rules. The RIS Req column designates which fields are required by Vision Series RIS. 1 Set ID – OBR O 4 SI 3 Comment 64k FT AMICAS. Inc.Vision Series RIS 5.0 HL7 Interface Guide Inbound Messages PV1 Seq 35 36 37 38 39 40 41 HL7 Field Name Delete Account Date Discharge Disposition Discharged to Location Diet Type Servicing Facility Bed Status Account Status Opt O O O O O B O Req by RIS Length 8 3 25 2 2 1 2 Data Type DT IS CM IS IS IS IS Rejection Rules Vision Series Data Mapping/ Comments 42 Pending Location O 80 PL Rejected if empty and schedule directly is selected and always schedule to is empty. HL7 Field Name. NTE Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PV1 Segment per message.

6 ORC (Common Order Segment) . Opt.0 HL7 Interface Guide Inbound Messages 3. Inc. Data Type. Length.ORM^O01 The following table lists each Common Order segment and their Seq. 3 4 Filler Order Number Placer Group Number C O 16 22 EI EI Blank if New Order 5 Order Status O 2 ID “CM” if Order sent at Tech End “CA” if Cancel Order “XO” if Change Order 6 Response Flag Quantity/Timing quantity interval duration start date/time end date/time Priority condition text conjunction order sequencing Parent Date/Time of Transaction O 1 ID Scheduled Exam Date/Time O 200 TQ <^^^yyyymmddhhmm^ ^s> if urgent or <R> if not urgent 7 8 9 O O 200 26 CM TS Current Date/Time <yyyymmddhhmmss> AMICAS.5.Vision Series RIS 5. HL7 Field Name. Proprietary and Confidential 46 . Rejection Rules. and Mapping/Comments: ORC Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments NW = New Order CA = Cancel Order XO = Change/ Update Order DC = Canceled Order (discontinued) HD = Hold Order IP = In Process Order SC = Scheduled Order RL = Release Hold Order RP = Order Replace 2 Placer Order Number C 16 EI Accession Number <Accession Number> Accession Number <Accession Number> 1 Order Control R 2 ID Rejected if not a valid code.

it will force the appointment to a resource.0 HL7 Interface Guide Inbound Messages ORC Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments User ID & Name <User ID^Last Name^First Name^^> 10 Entered By O 250 XCN Do not store in our database.Vision Series RIS 5. it will force the appointment to a resource. SC / blank SC / SC SC / IP SC / CM Order or Scheduled if schedule directly is selected Scheduled Check in Check out Order or Scheduled if schedule directly is selected Scheduled Check in Ended Schedules in the first available resource. it will force the appointment to a resource. Always force the appointment . if no openings. if no openings. Inc. This is for information purposes only. if no openings. Proprietary and Confidential 47 . Always force the appointment – this will not show in the appointment book since the procedure was not performed at the location If no NW or SC is received to create the order. Schedules in the first available resource. Schedules in the first available resource. it will force the appointment to a resource. The following table lists the valid ORC-1 / 5 pairs and what happens to the message: ORC-1 / ORC-5 RIS Visit Status ORM^001 Messages: NW / blank Order or Scheduled if schedule directly is selected NW / SC NW / IP NW / CM Scheduled Check in Check out RIS Exam Status Comments Order or Scheduled if schedule directly is selected Scheduled Check in Ended Schedules in the first available resource. all message types below are rejected CA / CA CA / DC Cancel Cancel Whatever the status is Whatever the status is Whatever the status is Whatever the status is Whatever the status is Whatever the status is Whatever the status is Whatever the status is See comments Can cancel all orders and appointments unless there is a report attached Can cancel all orders and appointments unless there is a report attached Can cancel all orders and appointments unless there is a report attached Can cancel all orders and appointments unless there is a report attached Can cancel all orders and appointments unless there is a report attached Can cancel all orders and appointments unless there is a report attached Can cancel all orders and appointments unless there is a report attached Can cancel all orders and appointments unless there is a report attached This will only update orders that are configured to automatically DC / DC DC / CA Cancel Cancel OC / CA OC / DC Cancel Cancel OD / CA OD / DC Cancel Cancel XO / XO See comments AMICAS. if no openings.this will not show in the appointment book since the procedure was not performed at the location.

order must be at a schedule status. Inc. O 4 AMICAS. otherwise NACK with error message order must be canceled this message will be seen in the monitor. Data Type. Length. then sending an XO/XO will take it to the next step which will be checkin. otherwise NACK with error message order must be canceled. checkin or inProcess. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. HL7 Field Name. OBR2 is blank. The RIS Req column designates which fields are required by Vision Series RIS. this message will be seen in the monitor. HIS will return an ORR^O02 with ORC-1 = NA.5. Opt. sending this will move it to checkin This will only update orders that are configured to automatically schedule.3 will have the RIS accession number 3. order must be at either schedule. Rejection Rules. the order will move through the RIS workflow. and OBR-3 = accession #. since we do not process HL7 messages in advanced mode only supported for orders that have not been scheduled.0 HL7 Interface Guide Inbound Messages ORC-1 / ORC-5 RIS Visit Status RIS Exam Status Comments schedule. OBR-2 has order number and OBR. if order is at the status of schedule. checkout This will only update orders that are configured to automatically schedule. Inprocess.7 OBR (Observation Request Segment) – ORM^O01 The following table lists each Observation Request segment and their Seq. Proprietary and Confidential 48 . then if we continue sending this status. since we do not process HL7 messages in advanced mode Release an order on hold in the work queue XO / IP Check in Check in XO / CM Check out Ended XX / XO XX / IP XX / CM OH / HD See comments Check in Check out Order hold See comments Check in Ended Order HD / HD Order hold Order RL / ORC-5 ignored OE / ORC-5 ignored Order Hold Order Order Hold Order Release an order on hold in the work queue ORR^002 Message: NA / ORC-5 Any status ignored Any status The only reason for this message is to add the Order Number. this will take the order to a checkout status See XO/XO See XO/IP See XO/CM only supported for orders that have not been scheduled. And patient account number Logic: An order created in RIS will send an ORM^001 with ORC-1 = SN. OBR Seq 1 HL7 Field Name Set ID Observation Request Opt Req by RIS Length Data Type SI Rejection Rules Vision Series Data Mapping/ Comments Sequence number for one or more OBR Segments per message.Vision Series RIS 5.

5 6 Priority Requested Date/Time B B O 2 26 ID TS Date/time the order was started. Specimen Rec'd Date/Time Specimen Source Source Code Additives Source Description Body Site O O O O O O C 26 20 60 1 60 300 26 TS CQ XCN ID CE ST TS 15 O 300 CM AMICAS. Proprietary and Confidential 49 . 4. 3 Filler Order Number C 22 EI <exam being ordered or canceled> Optionally. 8 9 10 11 12 13 14 Obs End Date/Time Collection Volume Collector Identifier Specimen Action Code Danger Code Relevant Clinical Info.3 = Modifier 4 Universal Service ID identifier text R R 250 CE Rejected if field is empty or code does not match. 2 Placer Order Number C R 22 EI Rejected if field is empty or code does not match. <yyyymmddhhmmss> or <yyyy^mm^dd^hh^mm^ss> 7 Observation Date/Time C 26 TS Rejected if not formatted correctly.1 = Code 4. this can be followed by two carets (^^) to include a modifier. Inc.2 = Description 4.Vision Series RIS 5.0 HL7 Interface Guide Inbound Messages OBR Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments <order number from the external system> A value that uniquely identifies the procedure to the host system for this patient.

17 Order Callback Phone No. Proprietary and Confidential 50 . Vision Series Data Mapping/ Comments Ordering (referring) provider. PV1. 18 19 20 21 O O O O 60 60 60 60 ST ST ST ST Rejected if not formatted correctly. <Physician Location PMIS Code or Physician Location Unique Identifier 16 Ordering Provider O O 250 XCN ^ Last Name ^ First Name ^ Middle Name ^ Suffix ^ If the PV1 segment has a value for PV1.Date/Time Charge To Practice O 40 XTN A definable field that the placing (ordering) system can use.8.7 and PMIS ^ Last Name ^ First Name ^ Middle Name ^ PV1. 22 C O 26 TS Date/time of order or status change. Placer Field 1 Placer Field 2 Filler Field 1 Filler Field 2 Result Rpt/Status Change .0 HL7 Interface Guide Inbound Messages OBR Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Reject if the PMIS or Last Name empty. The first name is also required if RIS creates the physician record from the message. <yyyymmddhhmmss> or <yyyy^mm^dd^hh^mm^ss> 23 O 40 CM AMICAS. Inc.7 will be Suffix ^> used as the referring physician and PV1.8 will be used as the CC physician. If the PV1 segment is not found then the value in OBR-16 will be used as the referring physician. Physician matching will occur only on PMIS. Tilde (~) separates referring from any or all CC physicians.Vision Series RIS 5. A definable field that the filling (RIS) system can use.

Reading Radiologist <PMIS Code or Unique ID^Last Name^First Name^Middle^Suffix> Dictated Date and Time <^^yyyymmddhhmmss> 31 Reason For Study O 250 CE Reject if empty or if schedule directly is selected and always schedule to is empty. only one appointment reason is allowed per order. If not match. Proprietary and Confidential 51 . 32 Principal Result Interpreter Assistant Result Interpreter O R 200 CM Reject if empty or if PMIS codes does not match. “P” for Preliminary “F” for Final “A” for Addendum 25 26 Result Status Parent Result C O R 1 400 ID CM 27 Quantity/Timing O 200 TQ Can identify quantity of this exam to be ordered.Vision Series RIS 5. 28 29 30 Result Copies To Parent Number Transportation Mode O O O C 150 200 20 XCN CM ID <reason code ^ reason text> If code. 33 O R 200 CM AMICAS. R (Routine). Note that. Rejected if not P. then try to match. F or A. Inc. use the reason text in the Other Reason field. the exam will be scheduled in the first available resource during the given appt time or it will be forced into the timeslot on the appointment book if the given time is not available. <quantity ^ ^ ^ start_date/time ^ end_date/time ^ priority> Priority = S (STAT) or A (ASAP) will se the urgent flag otherwise normal priority. in a multiple OBR segment. start and end date/time and priority.0 HL7 Interface Guide Inbound Messages OBR Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Schedule Resource <Resource Category Code> Note: If OBR-24 does 24 Diagnostic Serv Sect ID O 10 ID not match an active resource for the provided exam.

and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Inc. The RIS Req column designates which fields are required by Vision Series RIS. Opt. 3 Observation Identifier R 80 CE 4 Observation Sub-ID C 20 ST AMICAS. Proprietary and Confidential 52 . <yyyymmddhhmmss> or <yyyy^mm^dd^hh^mm^ss> 37 38 39 40 41 42 43 44 45 Number of Sample Containers Transport Logistics of Collected Samples Collector’s Comment Transport Arrangement Responsibility Transport Arranged Escort Required Planned Patient Transport Comment Procedure Code Procedure Code Modifier O O O O O O O O O 4 60 200 60 30 1 200 80 80 NM CE CE CE ID ID CE CE CE 3. Length. Rejection Rules.8 OBX (Observation Result Segment) .0 HL7 Interface Guide Inbound Messages OBR Seq 34 HL7 Field Name Technician Opt O Req by RIS Length 200 Data Type CM Rejection Rules Vision Series Data Mapping/ Comments Transcriptionist ID <PMIS Code or Unique ID^Last Name^First name^Middle^Suffix> 35 Transcriptionist O 200 CM 36 Scheduled Date/Time O R 26 TS Reject if not formatted correctly. Schedule date/time of the exam.5. 1 Set ID – OBR O 4 SI 2 Value Type C 3 ID Treated as a lead in to an order comment.Vision Series RIS 5.ORM^O01 The following table lists each Observation/Result segment and their Seq. Data Type. Likely to be combined with OBX – 5. OBX Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Sequence number for one or more OBX segments per message. HL7 Field Name.

AMICAS. For example. will concatenate with OBX-3. 5 Observation Value C 4k * 6 7 8 9 10 11 12 13 14 15 16 17 Units References Range Abnormal Flags Probability Nature of Abnormal Test Observation Result Status Date Of Last Obs Normal Values User Defined Access Checks Date-Time of the Observation Producer’s ID Responsible Observer Observation Method O O O O O R O O O O O O C R 60 60 5 5 2 1 26 20 26 60 80 60 CE ST ID NM ID ID TS ST TS CE XCN CE 3.1 Message Definition The function of this message is to respond to an ORM message. a response ORR might include only the MSH and MSA.General Order Acknowledgment Message Type 3.Vision Series RIS 5. If OBX-3 is sent. However.0 HL7 Interface Guide Inbound Messages OBX Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Treated as an order comment. particularly in case of an error response. Proprietary and Confidential 53 . In ORR the PID and ORC segments are optional.6. The following table lists each supported message segment and their description: Message Segment MSA MSH ORC PID Segment Description Message Acknowledgment Message Header Common Order Patient Identification See the Glossary for definitions of each interface.6 ORR^O02 . Inc. ORC segments are always required in ORR when an order detail segment is present. An ORR message is the application acknowledgment to an ORM message.

Inc.6.ORR^O02 The following table lists each Message Header segment and their Seq. "|" Vision Series Data Mapping/ Comments "^~\&" 3 4 5 Sending Application Sending Facility Receiving Application O O O R 180 180 180 HD HD HD <Sending Application> <Sending Facility> <Receiving Application> <Interface Engine Name for new customers> or <AMICAS RIS for existing customers> 6 Receiving Facility O 180 HD AMICAS. Length. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. The RIS Req column designates which fields are required by Vision Series RIS. MSA Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules If the code is not AA then no updates will occur. HL7 Field Name. MSH Seq 1 2 HL7 Field Name Field Separator Encoding Characters Opt R R Req by Length RIS R R 1 4 Data Type ST ST Rejection Rules Must always be pipe "|". Rejection Rules. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. The RIS Req column designates which fields are required by Vision Series RIS. Rejection Rules. HL7 Field Name. Rejected if not acceptable sending application.0 HL7 Interface Guide Inbound Messages 3.6. Length. Must always be "^~\&". Data Type. Opt. Vision Series Data Mapping/ Comments “AA” if Accepted “AE” if Error “AR” if Rejected If the code is equal to AE or AR then the reason for its failure will be in this field 1 Acknowledgment Code R R 2 ID 3 Text Message O 80 ST 3.2 MSA (Message Acknowledgment Segment) – ORR^O02 The following table lists each Observation/Result segment and their Seq.Vision Series RIS 5. Opt.3 MSH (Message Header Segment) . Proprietary and Confidential 54 . Data Type.

Opt. “ORM^O01” then the appropriate specification and logic will be applied to the message. AMICAS. and Mapping/Comments: ORC Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Trigger event identifier for orders. 8 Security O 40 ST Rejected if the value is not a defined message type (ORM^O01). Rejected if not “2. Rejected if field is empty. Unique Message Identifier “P” or “T” “2. Data Type. NA =Number Assigned 1 Order Control R R 2 ID Rejected if not a valid code. Length. HL7 Field Name.3”.4 ORC (Common Order Segment) .3” HL7 version number 9 Message Type O R 13 CM 10 11 12 13 14 15 16 17 18 19 20 Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgement Type Application Acknowledgement Type Country Code Character Set Principal Language Of Message Alternate Character Set Handling Scheme R R R O O O O O O O O R R R 20 3 60 15 180 2 2 2 16 60 20 ST PT ID NM ST ID ID ID ID CE ID 3. “2.2” or 2.0”.Vision Series RIS 5. Rejected if not “P” or “T”.ORR^O02 The following table lists each Common Order segment and their Seq. “2.0 HL7 Interface Guide Inbound Messages MSH Seq HL7 Field Name Opt Req by Length RIS Data Type Rejection Rules Vision Series Data Mapping/ Comments Current date/time <yyyymmddhhmmss>or <yymmddhhmmssss>or <yyymmddhhmmssss> or <yymmddhhmmss> 7 Date/time of Message O R 26 TS Rejected if field is empty or date/time is in the incorrect format. Rejection Rules. NA is the only valid code. Proprietary and Confidential 55 . If it is a define message type.6. Inc.1”.

5 PID (Patient Identification Definition Segment) – ORR^O02 The following table lists each Patient Identification Definition segment and their Seq. Rejected if empty. Opt.Vision Series RIS 5. The Patient MRN.7 ORU^R01 . Length. AMICAS. Patient ID (Internal ID) Patient Name Patient Account Number R R O R 22 90 22 3. version 2.1 Message Definition Vision Series RIS will receive the patient message event type ORU^R01 which will create or update patient reports.Results Message Type 3. Patient Account Number.0 HL7 Interface Guide Inbound Messages ORC Seq 2 3 HL7 Field Name Opt Req by RIS R R Length Data Type EI EI Rejection Rules Vision Series Data Mapping/ Comments Order number from placer. Accession number.7. PID Seq 3 5 18 HL7 Field Name Opt RIS Req Length Data Type CX XPN CX Rejected if empty. 3. The AMICAS interface will be a one-way (unidirectional) data transfer. Rejection Rules. Data Type. The RIS Req column designates which fields are required by Vision Series RIS. Rejection Rules Vision Series Data Mapping/ Comments Patient Internal ID. etc Patient Name.3 for electronic data exchange. Message received shall conform to the Health Level Seven (HL7) Standard. HL7 Field Name. Inc. Placer Order Number Filler Order Number C C 22 16 Rejected if empty. Jacket. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.6. The following table lists each supported message segment and their description: Message Segment MSH PID OBR OBX Segment Description Message Header Patient Identification Observation Request Observation/Result See the Glossary for definitions of each interface. Proprietary and Confidential 56 .

3” HL7 version number AMICAS.ORU^R01 The following table lists each Message Header segment and their Seq. Proprietary and Confidential 57 . Data Type.Vision Series RIS 5. “ORU^R01” Unique Message Identifier “P” “2. Current date/time <yyyymmddhhmmss> R R 7 20 3 60 15 180 2 2 2 16 60 20 Rejected if field is empty. Rejection Rules. <Sending Application> <Sending Facility> R 180 180 Rejected if field is empty. Rejected if field is empty. The RIS Req column designates which fields are required by Vision Series RIS.7. HL7 Field Name.2 MSH (Message Header Segment) . <Receiving Application> R 26 40 Rejected if field is empty. Opt. Inc. MSH Seq 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgement Type Application Acknowledgement Type Country Code Character Set Principal Language Of Message Alternate Character Set Handling Scheme Opt R R O O O O O O R R R R O O O O O O O O RIS Req Length 1 4 Data Type ST ST HD HD HD HD TS ST CM ST PT ID NM ST ID ID ID ID CE ID Rejection Rules Vision Series Data Mapping/ Comments "|" "^~\&" R 180 180 Rejected if field is empty. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.0 HL7 Interface Guide Inbound Messages 3. Length.

7. Length.Patient ID Patient ID (External ID) O B 4 20 SI CX Rejected if PID 3 does not match this field. Patient Gender <PMIS code only> (reference the RIS Gender support table) Patient Alias <Alias field> Rejected if the race code does not match this field. then reject. 3 Patient ID (Internal ID) R R 20 CX Patient Identifier Number <Patient Identifier Number> 4 Alternate Patient ID Patient Name last name first name middle initial Mother’s Maiden Name Date of Birth B 20 CX <last name^first name^ middle name> 5 R 48 XPN 6 7 O O R 48 26 XPN TS Rejected if field is empty Patient DOB and if not at least <yyyymmdd> <yyyymmdd>. Inc. If this field is empty then refer to PID 2.Vision Series RIS 5. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Rejected if the field is empty or if the gender code does not match this field. The RIS Req column designates which fields are required by Vision Series RIS.3 PID (Patient Identification Definition Segment) . “1” 1 2 Set ID . HL7 Field Name.0 HL7 Interface Guide Inbound Messages 3. Patient Ethnicity <PMIS code only> (reference the RIS Ethnicity support table) Patient Address <address 1^ address 2^ city^ state (standard abbreviation only)^ zip (alphanumeric with no validation)> 8 Sex O R 1 ST 9 Patient Alias O 48 XPN 10 Race O 1 IS 11 Patient Address O 151 60 40 40 2 9 XAD AMICAS. Data Type. If PID 2 is empty or does not match.ORU^R01 The following table lists each Patient Identification Definition segment and their Seq. Proprietary and Confidential 58 . PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PID segment per message. Opt. Rejection Rules.

Proprietary and Confidential 59 .Patient B 16 ST Rejected if not 9 sequential numbers. The patient PMIS must be unique to all patients. 19 SSN Number . AMICAS. No validation is performed for length or duplicates. If the PMIS is used as the unique ID. then PID_3 Jacket Number must be NULL on the inbound message.Home O 12 XTN 14 Phone Number Business Language . reject if blank and PID 3 must be NULL. 17 Religion O 3 IS Patient Unique Identifier <Patient File PMIS> This field is required if the interface is configured to use the patient PMIS number as the unique identifier. 12 County Code B 4 IS Country Code <Country field> Patient Home Phone – numeric only <area code and phone number> Patient Work Phone – numeric only <area code and phone number> 13 Phone Number .Vision Series RIS 5.Patient O 12 XTN 15 O 60 CE Patient Marital Status <PMIS code only> (reference the RIS Marital Status support table) 16 Marital Status O 1 IS Rejected if the martial status code does not match this field. Patient Social Security Number <#########> Numeric with no special characters. Country does not update.0 HL7 Interface Guide Inbound Messages PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Excess length will be truncated. Inc. Alphanumeric. 18 Patient Account Number O C 20 CX If the PMIS is used as the unique ID. guarantors and insureds.

4 OBR (Observation Request Segment) . Proprietary and Confidential 60 . Inc. HL7 Field Name. Data Type. Patient Date of Death <yyyymmdd> 3.7.Vision Series RIS 5. Rejection Rules. Accession Number <Accession Number> AMICAS. OBR Seq 1 HL7 Field Name Set ID Observation Request Placer Order Number Filler Order Number Universal Service ID identifier text Priority Requested Date/Time Observation Date/Time Obs End Date/Time Collection Volume Collector Identifier Specimen Action Code Opt RIS Req Length Data Type SI Rejection Rules Vision Series Data Mapping/ Comments Sequence number for one or more OBR Segments per Message O 4 2 3 4 5 6 7 8 9 10 11 C C R B B C O O O O R 16 22 200 2 26 26 26 20 60 1 EI EI CE ID TS TS TS CQ XCN ID Rejected if field is empty or does not match. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Opt. Length. The RIS Req column designates which fields are required by Vision Series RIS.ORU^R01 The following table lists each Observation Request segment and their Seq.0 HL7 Interface Guide Inbound Messages PID Seq 20 21 22 23 24 25 26 27 28 29 30 HL7 Field Name Drivers License NumberPatient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator Opt O O O O O O O O O O O RIS Req Length 25 20 3 60 2 2 4 60 80 26 1 Data Type CM CX IS ST ID NM IS CE CE TS ID Rejection Rules Vision Series Data Mapping/ Comments Reject if not at least <yyyymmdd>.

default to N.0 HL7 Interface Guide Inbound Messages OBR Seq 12 HL7 Field Name Danger Code Opt O RIS Req Length 60 Data Type CE Rejection Rules Vision Series Data Mapping/ Comments 13 Relevant Clinical Info. Bi-rad PMIS^ N (New) C (Compare Film) F (Need Film)^ Recall PMIS code If an invalid date is applied. O 300 ST Updates information for mammography procedures.1 has a value and recall flags are set then 13. Placer Field 1 Placer Field 2 Filler Field 1 Filler Field 2 Result Rpt/Status Change . Tilde (~) separates referring from any or all CC physicians. biopsy If 13.Vision Series RIS 5. Ordering Provider physician ID family name given name middle initial or name <Physician Location PMIS Code or Physician Location Unique Identifier ^ Last Name ^ First Name ^ Middle Name ^ Suffix ^ .3 is for the patient's required and the mammography message will be procedure(s) rejected.2 is associated with the not populated it will report. Proprietary and Confidential 61 .Date/Time Charge To Practice O O O O O C O 40 60 60 60 60 26 40 XTN ST ST ST ST TS CM AMICAS. The assessment. the current date will serve as the approval date. If 13.PMIS ^ Last Name ^ First Name ^ Middle Name ^ Suffix ^> 16 O 80 XCN 17 18 19 20 21 22 23 Order Callback Phone No. Inc. Approval Date <yyyymmdd> 14 Specimen Rec'd Date/Time Specimen Source Source Code Additives Source Description Body Site C 26 TS 15 O 300 CM Ordering (referring) provider.

0 HL7 Interface Guide Inbound Messages OBR Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Schedule Resource 24 Diagnostic Serv Sect ID O 10 ID <Resource Category Title> Rejected if not P. Proprietary and Confidential 62 .Vision Series RIS 5. Inc. Reading Radiologist <PMIS Code or Unique ID^Last Name^First Name^Middle^Suffix> Dictated Date and Time <^^yyyymmddhhmmss> 32 O R 200 CM 33 34 O O R 200 200 CM CM 35 Transcriptionist O 200 CM Transcriptionist ID <PMIS Code or Unique ID^Last Name^First name^Middle^Suffix> 36 37 38 39 40 41 42 43 44 45 Scheduled Date/Time Number of Sample Containers Transport Logistics of Collected Samples Collector’s Comment Transport Arrangement Responsibility Transport Arranged Escort Required Planned Patient Transport Comment Procedure Code Procedure Code Modifier O O O O O O O O O O 26 4 60 200 60 30 1 200 80 80 TS NM CE CE CE ID ID CE CE CE AMICAS. “P” for Preliminary If it is an A or a P “F” for Final and OBX 11 is an S. “A” for Addendum the report will be placed on hold. 25 Result Status C R 1 ID 26 27 28 29 30 31 Parent Result Quantity/Timing Result Copies To Parent Number Transportation Mode Reason For Study Principal Result Interpreter Assistant Result Interpreter Technician O O O O O O 400 200 150 200 20 300 CM TQ XCN CM ID CE Reject if empty or if PMIS codes does not match. F or A.

HL7 Field Name. “F” Final If OBX 11 is an S.ORU^R01 The following table lists each Observation/Result segment and their Seq. Also reject if this field does not coincide “P” Preliminary with OBR 25. Rejection Rules. Length. “S” Partial Results OBR 25 must be a P or an A. Proprietary and Confidential 63 . Data Type.Observation Simple Value Type Observation Identifier Observation Sub-ID O 4 SI 2 3 4 C R C 3 80 20 ID CE ST Line(s) of text from report. The RIS Req column designates which fields are required by Vision Series RIS. Opt. Approving Radiologist <PMIS Code or Unique ID^Last Name^First Name^Middle^Suffix> 16 Responsible Observer O C 80 XCN 17 Observation Method O 60 CE AMICAS. Inc. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.5 OBX (Observation/Result Segment) . Tildes (~) and carats (^) are recognized as carriage returns. OBX Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments Sequence number for one or more OBX segments per message. 1 Set ID . 11 Observation Result Status R R 1 ID 12 13 14 15 Date Of Last Obs Normal Values User Defined Access Checks Date-Time of the Observation Producer’s ID O O O O 26 20 26 60 TS ST TS CE Reject if the field is empty and if OBX 11 is “F”.7.0 HL7 Interface Guide Inbound Messages 3. 5 Observation Value C 65536 * 6 7 8 9 10 Units References Range Abnormal Flags Probability Nature of Abnormal Test O O O O O 60 60 5 5 2 CE ST ID NM ID Rejected if not “P” or “F”.Vision Series RIS 5.

0 HL7 Interface Guide Inbound Messages 3. Rejection Rules. Opt. Vision Series RIS will send an error response. Vision Series RIS will send a successful response.3” HL7 version number AMICAS.8. The RIS Req column designates which fields are required by Vision Series RIS. the message will be sent to a process which will update the database and Vision Series RIS will generate a functional response message. When Vision Series RIS receives an HL7 message. The following table lists each supported message segment and their description: Message Segment MSH MSA Segment Description Message Header Message Acknowledgment See the Glossary for definitions of each interface. If an error occurs during processing. MSHSeq 1 2 3 4 5 6 7 8 9 10 11 12 13 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Message Control ID Processing ID Version ID Sequence Number Opt R R O O O O O O R R R R O RIS Length Req 1 4 180 180 180 180 26 40 13 20 3 60 15 Data Type ST ST HD HD HD HD TS ST CM ST PT ID NM Rejection Rules Vision Series Data Mapping/ Comments "|" "^~\&" ”Vision Series RIS” Current date/time <yyyymmddhhmmss> “ACK” System Date/Time <yyyymmddhhmmss> “P” “2.ACK The following table lists each Message Header segment and their Seq. a reject message is constructed and returned to the placer.1 Definition The HL7 Acknowledgment Message Type.8.2 MSH (Message Header Segment) . Length. Data Type. it will validate the message syntactically. If validation does not fail. 3. ACK is sent from Vision Series RIS with a success or error message via the interface.8 ACK – Acknowledgment Message Type 3. HL7 Field Name. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.Vision Series RIS 5. Inc. If it processes correctly. If validation fails. Proprietary and Confidential 64 .

Vision Series RIS 5.0 HL7 Interface Guide Inbound Messages MSHSeq 14 15 16 17 18 19 20 HL7 Field Name Continuation Pointer Accept Acknowledgment Type Application Acknowledgment Type Country Code Character Set Principal Language Of Message Alternate Character Set Handling Scheme Opt O O O O O O O RIS Length Req 180 2 2 2 16 60 20 Data Type ST ID ID ID ID CE ID Rejection Rules Vision Series Data Mapping/ Comments "AL" 3. Rejection Rules. Data Type. If MSA_1 is AA this field will be empty.3 MSA (Message Acknowledgment Segment) . MSH_10. Opt. MSA Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments “AA” if Accepted “AE” if Error “AR” if Rejected Unique identifier echoed back from the received HL7 message. Length. Proprietary and Confidential 65 .8.ACK The following table lists each Observation/Result segment and their Seq. The RIS Req column designates which fields are required by Vision Series RIS. HL7 Field Name. otherwise this will contain text. 1 Acknowledgment Code R 2 ID 2 Message Control ID R 20 ST 3 Text Message O 80 ST 4 5 6 Expected Sequence Number Delayed Acknowledgment Type Error Condition O B O 15 1 100 NM ID CE AMICAS. Inc. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.

AMICAS. 4.2 Trigger Points and Trigger Events 4. The following outbound interfaces are supported:       ADT MFN ORM ORU ORM (Charge Out) ACK See the Glossary for definitions of each interface.Vision Series RIS 5. All outbound messages will fail if the jacket number is empty. The results report (Transcription Report) will be sent for each preliminary and/or approved report. version 2. Inc.2. 4. The trigger event is only sent if the corresponding trigger event is sent. The monitor page displays each of the messages sent and the status of each message.1 Definition A trigger point is a location in the workflow in which a trigger event will occur.3 for electronic data exchange. Outbound Messages The AMICAS interface will be a one-way (unidirectional) outbound data transfer. A trigger event is an event which initiates the flow of information among application systems. Proprietary and Confidential 66 . This page also provides the ability to resend a message. Patient demographic and appointment information will be sent from Vision Series RIS at several points within the application workflow.1 Interface Monitor A distribution entry is created for each message and is monitored through the HL7 Interface Monitor page. Messages sent shall conform to the Health Level Seven (HL7) Standard. as shown below. The HL7 Message Type is appended in parentheses to the transmission mode (Online-socket (ORM^O01)) in the Patient Files: Audit Trail window.0 HL7 Interface Guide Outbound Messages 4.

 New orders (O01) sent for added procedures/exams.0 HL7 Interface Guide Outbound Messages The following table lists each workflow item and their associated trigger events: Workflow/ Workflow Event Schedule Trigger Event     Check-In/Out New orders (O01) sent at time of scheduling visits if schedule trigger set.  Cancel orders (O01) sent on canceled procedures/exams. Inc. Completed orders (O01) added check-in films.Vision Series RIS 5. Cancel orders (O01) sent on canceled procedures. Patient Information Update (O01) sent for changes to demographic registration data. Proprietary and Confidential 67 .  Cancel orders (O01) sent on deleted procedures. Tech Entry  Change orders (O01) sent when all procedures are started on the same exam. If the interface is not configured for Multi-OBR. Change orders (O01) sent for changed procedures. Patient Information Update (A08) sent for demographic registration data change. Results sent for approved reports or addendums. cancel orders AMICAS. Patient File and/or Patient History      New orders (O01) sent for added procedures or visits. Completed orders (O01) added for outside reads. Reschedule orders (O01) will send cancel message followed by new order message. Cancel orders (O01) sent at time of canceling visits.  Change orders (O01) sent for changed procedures/exams. If the interface is configured for Multi-OBR.  New orders (O01) sent for added procedures.  Completed orders (O01) sent for procedures in a Check Out status. cancel orders (O01) are sent for each cancelled or deleted procedure.  Patient Information Update (A08) sent for demographic registration data change.  Completed orders (O01) sent for procedures in an Ended status.  New orders (O01) sent at the time patient checks-in if schedule trigger is not set. cancel orders (O01) are sent for each cancelled or deleted exam. If the interface is configured for Multi-OBR. Results (R01) sent for preliminary reports or addendums. otherwise a change order is sent when the patient is checked-in. new orders (O01) are sent for each for each added exam. new orders (O01) are sent for each added procedure. Merge patient (A34) sent when merge occurs.  If the interface is configured for Multi-OBR set for the Exam level. If the interface is not configured for Multi-OBR. Transcription   Report Review Film Canceling/ Deleting an Exam or Procedure Adding an Exam or Procedure       Replacing an Exam Canceling a Visit Cancel orders (O01) are sent followed by New Orders (O01) when replacing an exam.

and Mapping/Comments: MSH Seq 1 2 3 4 5 6 7 8 9 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Opt R R O O O O O O R Length 1 4 180 180 180 180 26 40 7 Data Type ST ST HD HD HD HD TS ST CM “ADT^A08” Current date/time <yyyymmddhhmmss> "|" "^~\&" ”Vision SeriesRIS” <Corporation Name> “PACS” Vision Series Data Mapping/ Comments AMICAS. HL7 Field Name. This trigger event is used when any patient information has changed when no other trigger event has occurred. Rejection Rules.3. but it can also be used for demographic information only.2 MSH (Message Header Segment) .0 HL7 Interface Guide Outbound Messages Workflow/ Workflow Event Trigger Event (O01) are sent for each cancelled exam. Data Type.Vision Series RIS 5. The A08 event can include information specific to an episode of care. Inc. 4.1 Definition Vision Series RIS shall send the patient message event type ADT^A08 which will update patient information. Length. Proprietary and Confidential 68 . Opt.3 ADT^A08 – Update Patient Information 4.3. cancel orders (O01) are sent for each cancelled procedure. 4. Do not send any guarantor or insured updates.  If the interface is configured for Multi-OBR set to the Visit level. The following table lists each supported message segment and their description: Message Segment MSH PID PV1 Segment Description Message Header Patient Identification Patient Class See the Glossary for definitions of each interface.ADT^A08 The following table lists each Message Header segment and their Seq.

Opt. “1” Patient Unique Identifier <Internal Patient ID Number> Patient Unique Identifier 3 Patient ID (Internal ID) R 20 CX <Internal Generated Patient ID. Rejection Rules. HL7 Field Name.Patient ID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID segment per message.3” HL7 version number 16 17 18 19 20 O O O O O 2 2 16 60 20 ID ID ID CE ID "NE" 4. Proprietary and Confidential 69 . PMIS or Social Security> Patient Unique Identifier <Jacket. PMIS or Social Security > 2 Patient ID (External ID) O 20 CX 4 Alternate Patient ID Patient Name O 20 CX 5 last name first name middle initial R 48 XPN Patient Name <last name^first^middle^suffix> AMICAS.0 HL7 Interface Guide Outbound Messages MSH Seq 10 11 12 13 14 15 HL7 Field Name Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgment Type Application Acknowledgment Type Country Code Character Set Principal Language of Message Alternate Character Set Handling Scheme Opt O R R O O O Length 20 3 60 15 180 2 Data Type ST PT ID NM ST ID "AL" Vision Series Data Mapping/ Comments System date/time <yyyymmddhhmmss> “P” “2. Jacket.3. and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID .3 PID (Patient Identification Definition Segment) .Vision Series RIS 5.ADT^A08 The following table lists each Patient Identification Definition segment and their Seq. Data Type. Inc. Length.

M.Patient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order O O O O O O O 16 25 20 80 60 2 1 ST CM CX IS ST ID NM AMICAS.Vision Series RIS 5.Patient Driver’s Lic Num . O. Inc. Email 13 Phone Number . Proprietary and Confidential 70 .Date portion only <yyyymmdd> Patient Gender (F.Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 16 17 18 Language .Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number . U) <PMIS Code or Gender Code> Patient Alias <Alias field> Patient Ethnicity <PMIS code or Ethnicity Code> Patient Address 8 Sex O 1 ST 9 Patient Alias O 48 XPN 10 Race O 80 IS 11 Patient Address O 106 XAD <Address 1^Address 2^ City^State^Zip^Country> 12 County Code B 4 IS County Code <County Field> Patient Home Phone.Patient Marital Status Religion Patient Account Number O O O O 60 80 80 20 CE IS IS CX Patient Unique Identifier <PMIS> Patient SS Number <SS Number> Patient Marital Status <PMIS Code for Marital Status Code> 19 20 21 22 23 24 25 SSN Number . Fax.0 HL7 Interface Guide Outbound Messages PID Seq 6 7 HL7 Field Name Mother’s Maiden Name Date of Birth Opt O O Length 48 26 Data Type XPN TS Vision Series Data Mapping/ Comments Patient DOB .

Rejection Rules.4 PV1 (Patient Visit Segment) .3. Data Type. Inc. “1” Service Type <PMIS Code for Service Type Code> Patient Location 3 Assigned Patient Location O 80 PL <Location Name^^^PMIS Code^^^^^Location Name> 2 Patient Class R 1 IS 4 5 6 7 Admission Type Preadmit Number Prior Patient Location Attending Doctor O O O O 2 20 80 60 IS CX PL XCN Rank 1 Physician 8 Referring Doctor O 60 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Additional Physicians <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> 9 Consulting Doctor O 60 XCN 10 11 12 13 Hospital Service Temporary Location Preadmit Test Indicator Readmission Indicator O O O O 3 80 2 2 IS PL IS IS AMICAS. and Mapping/Comments: PV1 Seq 1 HL7 Field Name Set ID – PV1 Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PV1 Segment per message.Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages PID Seq 26 27 28 29 30 HL7 Field Name Citizenship Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator Opt O O O O O Length 80 60 80 26 1 Data Type IS CE CE TS ID Vision Series Data Mapping/ Comments Patient Date of Death <yyyymmdd> 4. Proprietary and Confidential 71 . HL7 Field Name. Opt.ADT^A08 The following table lists each Patient Visit segment and their Seq. Length.

Vision Series RIS 5. Proprietary and Confidential 72 .0 HL7 Interface Guide Outbound Messages PV1 Seq 14 15 16 17 18 HL7 Field Name Admit Source Ambulatory Status VIP Indicator Admitting doctor Patient Type Opt O O O O O Length 3 2 2 60 2 Data Type IS IS IS XCN IS Vision Series Data Mapping/ Comments Pregnancy Indicator <B6 if flag Y else other> Service Type <PMIS Code for Service Type Code> Unique Visit Number <System Generated Number> 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 Visit Number Financial Class Charge Price Indicator Courtesy Code Credit Rating Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount Bad Debt Recovery Amount Delete Account Indicator Delete Account Date Discharge Disposition Discharged to Location Diet Type Servicing Facility Bed Status Account Status Pending Location O O O O O O O O O O O O O O O O O O O O O B O O 20 50 2 2 2 2 8 12 3 2 1 8 10 12 12 1 8 3 25 80 2 1 2 80 CX CM IS IS IS IS DT NM NM IS IS DT IS NM NM IS DT IS CM IS IS IS IS PL AMICAS. Inc.

Proprietary and Confidential 73 . 4. Rejection Rules.4.ADT^A34 The following table lists each Message Header segment and their Seq.4 ADT^A34 – Merge Patient Information (Patient ID Only) 4. Length.Vision Series RIS 5.2 MSH (Message Header Segment) .1 Definition Vision Series RIS shall send the patient message event type ADT^A34 which will merge patient information. Opt.4. This merge is done to change patient identifiers on all of the patient’s incorrect accounts. Data Type. The following table lists each supported message segment and their description: Message Segment MSH EVN PID MRG Segment Description Message Header Event Type Patient Identification Merge Information See the Glossary for definitions of each interface. An A34 event is used to signal a merge of records for a patient that was incorrectly created under two different identifiers. Inc. and Mapping/Comments: MSH Seq 1 2 HL7 Field Name Field Separator Encoding Characters Opt R R Length 1 4 Data Type ST ST "|" "^~\&" Vision Series Data Mapping/ Comments AMICAS. HL7 Field Name.0 HL7 Interface Guide Outbound Messages PV1 Seq 43 44 HL7 Field Name Prior Temporary Location Admit Date/Time Opt O O Length 80 26 Data Type PL TS Vision Series Data Mapping/ Comments Admit Date <yyyymmdd> Discharge Date <yyyymmdd> 45 46 47 48 49 50 51 52 Discharge Date/Time Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID Visit Indicator Other Healthcare Provider O O O O O O O O 26 12 12 12 12 20 1 60 TS NM NM NM NM CX IS XCN <Order Number> Patient Weight <Patient Weight> 4.

Inc. Proprietary and Confidential 74 . Length.Vision Series RIS 5. HL7 Field Name. Opt. and Mapping/Comments: EVN Seq 1 2 3 HL7 Field Name Event Type Code Recorded Date/Time Date/Time Planned Event Opt B R O Length 3 26 26 Data Type ID TS TS “A34” Current Date/Time <yyyymmddhhmmss> Vision Series Data Mapping/ Comments AMICAS. Data Type. Rejection Rules.3 EVN (Event Type Segment) .3” HL7 version number 16 17 18 19 20 O O O O O 2 2 16 60 20 ID ID ID CE ID "NE" 4.ADT^A34 The following table lists each Event Type segment and their Seq.0 HL7 Interface Guide Outbound Messages MSH Seq 3 4 5 6 7 8 9 10 11 12 13 14 15 HL7 Field Name Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgment Type Application Acknowledgment Type Country Code Character Set Principal Language of Message Alternate Character Set Handling Scheme Opt O O O O O O R R R R O O O Length 180 180 180 180 26 40 7 20 3 60 15 180 2 Data Type HD HD HD HD TS ST CM ST PT ID NM ST ID "AL" Vision Series Data Mapping/ Comments ”Vision SeriesRIS” <Corporation Name> “PACS” Current date/time <yyyymmddhhmmss> “ADT^A34” System date/time <yyyymmddhhmmss> “P” “2.4.

Proprietary and Confidential 75 .ADT^A34 The following table lists each Patient Identification Definition segment and their Seq. Inc.Date portion only <yyyymmdd> Patient Gender (F.Patient ID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID segment per message. HL7 Field Name. and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID . PMIS or Social Security > 2 Patient ID (External ID) B 20 CX 8 Sex O 1 ST 9 Patient Alias O 48 XPN 10 Race O 80 IS AMICAS. Rejection Rules.4.Vision Series RIS 5. Length. Opt. O.U) <PMIS code or Gender Code> Patient Alias <Alias field> Patient Ethnicity <PMIS code or Ethnicity Code> R 48 XPN Patient Name <last name^first^middle^suffix> B 20 CX Patient Unique Identifier <Jacket.4 PID (Patient Identification Definition Segment) .0 HL7 Interface Guide Outbound Messages EVN Seq 4 5 HL7 Field Name Event Reason Code Operator ID Opt O O Length 3 60 Data Type IS XCN Vision Series Data Mapping/ Comments Operator ID & Name <User ID^User Name (FML)> Current Date/Time <yyyymmddhhmmss> 6 Event Occurred O 26 TS 4. “1” Patient Unique Identifier <Internal Patient ID Number> Patient Unique Identifier 3 Patient ID (Internal ID) R 20 CX Destination Patient Identifier <Defined Unique ID> 4 Alternate Patient ID Patient Name 5 last name first name middle initial 6 7 Mother’s Maiden Name Date of Birth O O 48 26 XPN TS Patient DOB . M. Data Type.

5 MRG (Patient Merge Information Segment) . Length. Inc. Opt. Data Type. Proprietary and Confidential 76 .Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 16 17 18 Language . Fax.ADT^A34 The following table lists each Patient Merge Information segment and their Seq. Email 13 Phone Number .Patient Marital Status Religion Patient Account Number O O O O 60 80 80 20 CE IS IS CX Patient Unique Identifier <PMIS> Patient SS Number <SS Number> Patient Marital Status <PMIS Code for Marital Status Code> 19 20 21 22 23 24 25 26 27 28 29 30 SSN Number .Patient Driver’s Lic Num .Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number .Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages PID Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments Patient Address 11 Patient Address O 106 XAD <Address 1^Address 2^ City^State^Zip^Country> 12 County Code B 4 IS County Code <County Field> Patient Home Phone. Rejection Rules. HL7 Field Name.4.Patient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator B O O O O O O O O O O O 16 25 20 80 60 1 2 80 60 80 26 1 ST CM CX IS ST ID NM IS CE CE TS ID Patient Date of Death <yyyymmdd> 4. and Mapping/Comments: AMICAS.

transmits update information to other systems (usually to the "owning" system). updates) to this file are made available to various other applications on a routine basis. Proprietary and Confidential 77 .0 HL7 Interface Guide Outbound Messages MRG Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments Patient Unique Identifier 1 Prior Patient ID . The changes (e. etc. but also supports the situation where an application not "owning" a particular master file.1 Message Definition In an open-architecture healthcare environment there is often a set of common reference files used by one or more application systems. These files are called master files. The Master Files Notification (MFN) message provides a way of maintaining this synchronization by specifying a standard for the transmission of this data between applications.Master File Update Message Type 4. deletes.g. one application system will "own" a particular master file such as the staff and practitioner master file.g. Some common examples of master files in the healthcare environment include:           staff and health practitioner master file system user (and password) master file location (census and clinic) master file device type and location (e..Vision Series RIS 5. In many implementations. Inc.) lab test definition file exam code (radiology) definition file charge master file patient status master patient type master service item master file These common reference files need to be synchronized across the various applications at a given site. printers.. The MFN message supports this common case.5. for review and possible inclusion.Internal R 20 CX Source Patient Identifier <Defined Unique ID> Patient Unique Identifier <Defined Unique ID> Prior Patient PMIS <Patient File PMIS> Prior Patient Unique Identifier <Internal Patient ID Number> 2 Prior Alternate Patient ID Prior Patient Account Number Prior Patient ID .5 MFN .External Prior Visit Number Prior Alternate Visit ID Prior Patient Name O 20 CX 3 O 20 CX 4 5 6 7 O O O O 20 20 20 48 CX 4. terminals. workstations. adds. AMICAS.

MSH Seq 1 2 3 4 5 6 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Opt R R O O O O Length 1 4 180 180 180 180 Data Type ST ST HD HD HD HD "|" "^~\&" Vision Series Data Mapping/ Comments <Sending Application> <Sending Facility> <Receiving Application> <Interface Engine Name for new customers> or <AMICAS RIS for existing customers> Current date/time <yyyymmddhhmmss>or <yymmddhhmmssss>or <yyymmddhhmmssss> or <yymmddhhmmss> 7 Date/time of Message O 26 TS 8 9 10 11 Security Message Type Message Control ID Processing ID O R O R 40 7 20 3 ST CM ST PT “ORM^O01” Unique Message Identifier “P” or “T” AMICAS. etc.5. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. update. 4. the initial and requested dates for the event. the Master File Entry (MFE) segment carries the record-level event code (such as add. Rejection Rules. Length. The Master File Identification (MFI) segment identifies the master file being updated as well as the initial and requested dates for file-level events (such as replace file). The following table lists each supported message segment and their description: Message Segment MSH MFI MFE ZL7 Segment Description Message Header Master File Identification Master File Entry Insurance Data to Post See the Glossary for definitions of each interface.Vision Series RIS 5. and allows the use of either original or enhanced acknowledgment modes. and the recordlevel key identifying the entry in the master file. Inc. HL7 Field Name.2 MSH (Message Header Segment) – MFN The following table lists each Message Header segment and their Seq. as well as providing for a delayed application acknowledgment mode. Data Type.0 HL7 Interface Guide Outbound Messages The MFN message supports the distribution of changes to various master files between systems in either online or batch modes. Opt. Proprietary and Confidential 78 .). For each record being changed. These messages use the MSH segment to pass the basic event code (master files notification or acknowledgment). The Master File Acknowledgment (MFA) segment returns record-specific acknowledgment information. The RIS Req column designates which fields are required by Vision Series RIS.

MFI Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments INS <INS^Insurance Master File> Note: See HL7 Table: Master File Identifier Codes. Opt. Data Type. 1 Message File Identifier R 250 CE 2 3 4 5 6 Master File Application Identifier File-Level Event Code Entered Date/Time Effective Date/Time Response Level Code O R O O R 180 3 26 26 2 HD ID TS TS ID UPD <yyyymmddhhmmss> <yyyymmddhhmmss> AL Always sends an ACK. Proprietary and Confidential 79 . Inc.5. HL7 Field Name. Rejection Rules. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.3 MFI (Message File Identification Segment) – MFN The following table lists each Message Header segment and their Seq. Length.3” HL7 version number 4.Vision Series RIS 5. The RIS Req column designates which fields are required by Vision Series RIS. HL7 Table: Master File Identifier Codes Value CDM CLN CMA Description Charge Description Master File Clinic Master File Clinical Study with Phases and Scheduled Master File Comment AMICAS. a.0 HL7 Interface Guide Outbound Messages MSH Seq 12 13 14 15 16 17 18 19 20 HL7 Field Name Version ID Sequence Number Continuation Pointer Accept Acknowledgement Type Application Acknowledgement Type Country Code Character Set Principal Language Of Message Alternate Character Set Handling Scheme Opt R O O O O O O O O Length 60 15 180 2 2 2 16 60 20 Data Type ID NM ST ID ID ID ID CE ID Vision Series Data Mapping/ Comments “2.

Data Type. Opt.5. <yyyymmddhhmmss> <yyyymmddhhmmss> AMICAS. MAC Note: See HL7 Table: Actions Performed on Master Files. MDL. 4.Vision Series RIS 5. Proprietary and Confidential 80 . Length. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. MDC.0 HL7 Interface Guide Outbound Messages Value CMB Description Clinical Study without Phases but with Scheduled Master File Procedure Master File Procedure Category Code Master File Diagnosis Code Master Record Insurance Master File Inventory Master File Location Master file CPT Code Modifier Master File Numerical Observation Master File Categorical Observation Master File Observation Batteries Master File Calculated Observations Master File Other Observation/Service Item Master File Physician Master File Practitioner Master File Staff Master File Zip Code Master File Comment CPT DEP DXC INS INV LOC MOD OMA OMB OMC OMD OME PHY PRA STF ZIP AMICAS currently updates this file. MFE Seq 1 2 3 HL7 Field Name Record-Level Event Code MFN Control ID Effective Date/Time Opt R C O Length 3 20 26 Data Type ID ST TS Vision Series Data Mapping/ Comments MAD. Inc. HL7 Field Name. MUP. The RIS Req column designates which fields are required by Vision Series RIS. Rejection Rules.4 MFE (Message File Entry Segment) – MFN The following table lists each Message Header segment and their Seq.

and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Data Type. Delete the record from the master file. MAC 4. Proprietary and Confidential 81 .1 Definition Vision Series RIS sends the order message event type ORM^O01 which contains patient orders. Opt.5 ZL7 (Insurance Data to Post Segment) – MFN The following table lists each Message Header segment and their Seq.0 HL7 Interface Guide Outbound Messages MFE Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments <Identifier -Location PMIS> 4 Primary Key Value – MFE R 200 Varies This is the search key for the PMIS Code depending upon the support table. MFE Seq HL7 Field Name Data Opt Length Typ e Vision Series Data Mapping/ Comments 1 Location R 400 Location CE <PMIS^Name^Address1& Address2&City&State&ZipCode^Phone&&&Email&&&fax^Contact^^Plan Insurance Type Code^^^> 4. The RIS Req column designates which fields are required by Vision Series RIS.Vision Series RIS 5. Length. HL7 Field Name. Orders are associated with a particular patient and usually contain a set of one or more procedures to be performed on a patient. Discontinue using the record in the master file. HL7 Table: Actions Performed on Master Files Value MAD MDL MUP MDC Description Add the record to the master file. a. Update the record for the master file. Deactivate.5. Reactivate the deactivated record. The function of this message is to initiate the transmission of information about an order. but do not delete it from the database. Supported order messages include the Common Order Segment (ORC) and the Observation Request Segment (OBR). DX and ZIP use Code all others use the PMIS Code. Inc.6. AMICAS. Rejection Rules.6 ORM^O01 – Order Message Type 4.

Data Type.2 MSH (Message Header Segment) .0 HL7 Interface Guide Outbound Messages The following table lists each supported message segment and their description: Message Segment MSH PID PV1 ORC OBR Segment Description Message Header Patient Identification Patient Visit (optional) Common Order Order Detail /Observation Request See the Glossary for definitions of each interface.3” HL7 version number Current date/time <yyyymmddhhmmss> "|" "^~\&" ”Vision SeriesRIS” <Corporation Name> “PACS” Vision Series Data Mapping/ Comments 16 O 2 ID "NE" AMICAS.ORM^O01 The following table lists each Message Header segment and their Seq. and Mapping/Comments: MSH Seq 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgment Type Application Acknowledgment Type Opt R R O O O O O O R R R R O O O Length 1 4 180 180 180 180 26 40 7 20 3 60 15 180 2 Data Type ST ST HD HD HD HD TS ST CM ST PT ID NM ST ID "AL" “ORM^O01” System date/time <yyyymmddhhmmss> “P” “2. Inc.6. HL7 Field Name. Proprietary and Confidential 82 . Opt. Rejection Rules.Vision Series RIS 5. Length. 4.

“1” Patient Unique Identifier <Internal Patient ID Number> Patient Unique Identifier 3 Patient ID (Internal ID) R 20 CX <Internal Generated Patient ID.6. Length.3 PID (Patient Identification Definition Segment) . Rejection Rules.Vision Series RIS 5.Date portion only (YYYYMMDD) Patient Gender (F. PMIS or Social Security > Patient Name <last name^first^middle^suffix> 2 Patient ID (External ID) B 20 CX 4 Alternate Patient ID Patient Name last name first name middle initial Mother’s Maiden Name Date of Birth Sex B 20 CX 5 R 48 XPN 6 7 8 O O O 48 26 1 XPN TS ST Patient DOB . and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID .ORM^O01 The following table lists each Patient Identification Definition segment and their Seq. Opt. HL7 Field Name. U) <PMIS code or Gender Code> Patient Alias <Alias field> Patient Ethnicity <PMIS code or Ethnicity Code> Patient Address 9 Patient Alias O 48 XPN 10 Race O 80 IS 11 Patient Address O 106 XAD <Address 1^Address 2^City^State^Zip^Country> County Code <County Field> 12 County Code B 4 IS AMICAS. Proprietary and Confidential 83 . Jacket.0 HL7 Interface Guide Outbound Messages MSH Seq 17 18 19 20 HL7 Field Name Country Code Character Set Principal Language of Message Alternate Character Set Handling Scheme Opt O O O O Length 2 16 60 20 Data Type ID ID CE ID Vision Series Data Mapping/ Comments 4.Patient ID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID segment per message. M. PMIS or Social Security> Patient Unique Identifier <Jacket. Inc. Data Type. O.

4 PV1 (Patient Visit Segment) .Patient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator B O O O O O O O O O O O 16 25 20 80 60 1 2 80 60 80 26 1 ST CM CX IS ST ID NM IS CE CE TS ID Patient Date of Death <yyyymmdd> 4.Patient Driver’s Lic Num .Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 16 17 18 Language . Data Type. Email 13 Phone Number .Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number .Patient Marital Status Religion Patient Account Number O O O O 60 80 80 20 CE IS IS CX Patient Unique Identifier <PMIS> Patient SS Number <SS Number> Patient Marital Status <PMIS Code for Marital Status Code> 19 20 21 22 23 24 25 26 27 28 29 30 SSN Number . and Mapping/Comments: PV1 Seq 1 HL7 Field Name Set ID – PV1 Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PV1 segment per message. “1” AMICAS.ORM^O01 The following table lists each Patient Visit segment and their Seq.0 HL7 Interface Guide Outbound Messages PID Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments Patient Home Phone. Opt. Rejection Rules. HL7 Field Name. Fax.Vision Series RIS 5. Proprietary and Confidential 84 . Inc.6. Length.

Inc.0 HL7 Interface Guide Outbound Messages PV1 Seq 2 HL7 Field Name Patient Class Opt R Length 1 Data Type IS Vision Series Data Mapping/ Comments Service Type <PMIS Code for Service Type Code> Patient Location 3 Assigned Patient Location O 80 PL < Location Name ^^^PMIS Code^^^^^Location Name> 4 5 6 7 Admission Type Preadmit Number Prior Patient Location Attending Doctor O O O O 2 20 80 60 IS CX PL XCN Rank 1 Physician 8 Referring Doctor O 60 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Additional Physicians <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> 9 Consulting Doctor O 60 XCN 10 11 12 13 14 15 16 17 18 Hospital Service Temporary Location Preadmit Test Indicator Readmission Indicator Admit Source Ambulatory Status VIP Indicator Admitting doctor Patient Type O O O O O O O O O 3 80 2 2 3 2 2 60 2 IS PL IS IS IS IS IS XCN IS Service Type <PMIS Code for Service Type Code> Unique Visit Number <System Generated Number> Pregnancy Indicator <B6 if flag Y else other> 19 20 21 22 23 Visit Number Financial Class Charge Price Indicator Courtesy Code Credit Rating O O O O O 20 50 2 2 2 CX CM IS IS IS AMICAS. Proprietary and Confidential 85 .Vision Series RIS 5.

Inc.Vision Series RIS 5. Proprietary and Confidential 86 .0 HL7 Interface Guide Outbound Messages PV1 Seq 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 HL7 Field Name Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount Bad Debt Recovery Amount Delete Account Indicator Delete Account Date Discharge Disposition Discharged to Location Diet Type Servicing Facility Bed Status Account Status Pending Location Prior Temporary Location Admit Date/Time Opt O O O O O O O O O O O O O O O O B O O O O Length 2 8 12 3 2 1 8 10 12 12 1 8 3 25 80 2 1 2 80 80 26 Data Type IS DT NM NM IS IS DT IS NM NM IS DT IS CM IS IS IS IS PL PL TS Vision Series Data Mapping/ Comments Admit Date <yyyymmdd> Discharge Date <yyyymmdd> 45 46 47 48 49 50 51 52 Discharge Date/Time Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID Visit Indicator Other Healthcare Provider O O O O O O O O 26 12 12 12 12 20 1 60 TS NM NM NM NM CX IS XCN <Order Number> Patient Weight <Patient Weight> AMICAS.

Inc. Proprietary and Confidential 87 . Opt.Vision Series RIS 5. Data Type. Length. or Unique Group Number for Exam level or Unique Group Number for Visit level <Group Order Number> Blank if New Order 5 Order Status O 2 ID “CM” if Order sent at Tech End “CA” if Cancel Order “XO” if Change Order 6 Response Flag Quantity/Timing quantity interval duration start date/time end date/time Priority condition text conjunction order sequencing Parent Date/Time of Transaction O 1 ID 3 Filler Order Number C 16 EI Scheduled Exam Date/Time O 200 TQ <^^^yyyymmddhhmm^^s> if urgent or <R> if not urgent 7 8 9 O O 200 26 CM TS Current Date/Time <yyyymmddhhmmss> User ID & Name 10 Entered By O 120 XCN <User ID^Last Name^First Name^Middle^Suffix> 11 Verified By O 120 XCN AMICAS. Rejection Rules. HL7 Field Name.0 HL7 Interface Guide Outbound Messages 4.5 ORC (Common Order Segment) . and Mapping/Comments: ORC Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments “NW” if New Order 1 Order Control R 2 ID “CA” if Cancel Order “XO” if Change Order 2 Placer Order Number C 16 EI Accession Number <Accession Number> Accession Number <Accession Number> Group Number for grouping procedures 4 Placer Group Number O 22 EI Blank if no grouping.ORM^O01 The following table lists each Common Order segment and their Seq.6.

Opt.0 HL7 Interface Guide Outbound Messages ORC Seq HL7 Field Name Ordering Provider physician id family name given name middle initial or name Enterer’s Location Opt Length Data Type Vision Series Data Mapping/ Comments Rank 1 Physician 12 O 120 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Location ID & Name ^^^<PMIS^^^^^Location Name> Rank 1 Physician Phone # & Fax # <Phone Number^Fax Number> 13 O 80 PL 14 15 16 Call Back Phone Number Order Effective Date/Time Order Control Reason O O O 40 26 200 XTN TS CE Reason <Reason or Free Text if Other Reason> Rank 1 Physician Location <PMIS or Unique ID^Phy Location Name> 17 18 19 20 21 22 23 24 Entering Organization Entering Device Action By Advanced Beneficiary Notice Code Ordering Facility Name Ordering Facility Address Ordering Facility Phone Number Ordering Provider Address O O O O O O O O 60 60 120 40 60 106 48 106 CE CE XCN CE XON XAD XTN XAD 4. Proprietary and Confidential 88 . and Mapping/Comments: OBR Seq 1 HL7 Field Name Set ID Observation Request Placer Order Number Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One OBR Segment per Message “1” Accession Number <Accession Number> Accession Number <Accession Number> 2 C 16 EI 3 Filler Order Number C 16 EI AMICAS. Data Type. Length. Inc.Vision Series RIS 5. HL7 Field Name.ORM^O01 The following table lists each Order Detail/Observation Request segment and their Seq.6.6 OBR (Order Detail /Observation Request) . Rejection Rules.

O 80 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Rank 1 Physician Phone number and Fax number <Phone Number^Fax Number> 17 Order Callback Phone No. O 300 ST <Visit Comment~Visit Comment^Patient Comments~Patient Comments^Exam Comments~Exam Comments^Schedule Comments> 14 Specimen Rec'd Date/Time Specimen Source Source Code Additives Source Description Body Site C 26 TS 15 O 300 CM 16 Ordering Provider physician ID family name given name middle initial or name Ordering (referring) provider. Proprietary and Confidential 89 .Vision Series RIS 5. O 40 XTN AMICAS. Inc.0 HL7 Interface Guide Outbound Messages OBR Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments Procedure Code Procedure Description 4 Universal Service ID identifier text R 200 CE Exam Code Exam Description <Procedure Code^Procedure Description^Exam Code^Exam Description> 5 6 Priority Requested Date/Time B B 2 26 ID TS Scheduled Date/Time ^^^<yyyymmddhhmmss^^s> Scheduled Date/Time ^^^<yyyymmddhhmmss^^s> 7 8 9 10 11 12 Observation Date/Time Obs End Date/Time Collection Volume Collector Identifier Specimen Action Code Danger Code C O O O O O 26 26 20 60 1 60 TS TS CQ XCN ID CE Comments 13 Relevant Clinical Info. Tilde (~) separates referring from any or all CC physicians.

Vision Series RIS 5. Proprietary and Confidential 90 .0 HL7 Interface Guide Outbound Messages OBR Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments Group Number for grouping procedures 18 Placer Field 1 O 60 ST Blank if no grouping. Inc. or Unique Group Number for Exam level or Unique Group Number for Visit level <Group Order Number> Procedure Category & Resource 19 Placer Field 2 O 60 ST <Procedure Category Description^Resource Category Title> 20 21 22 23 24 25 26 Filler Field 1 Filler Field 2 Result Rpt/Status Change Date/Time Charge To Practice Diagnostic Serv Sect Id Result Status Parent Result Quantity/Timing quantity interval duration start date/time end date/time priority condition text conjunction order sequencing O O C O O C O 60 60 26 40 10 1 400 ST ST TS CM ID ID CM Schedule Resource <Resource Category Title> Application Entity Title <Modality Name> Scheduled Date/Time O 200 TQ ^^^<yyyymmddhhmmss^^s> if urgent else <R> 27 Additional Physicians <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> 28 Result Copies To O 150 XCN 28 29 30 Result Copies To Parent Number Transportation Mode O O O 150 200 20 XCN CM ID Reason for Visit 31 Reason For Study O 300 CE <Reason or Free form if Other Reason^ Reason or Free form if Other Reason> 32 Principal Result Interpreter O 200 CM AMICAS.

7.7 ORU^R01 – Results Message Type 4. The following table lists each supported message segment and their description: Message Segment MSH PID PV1 ORC OBR OBX Segment Description Message Header Patient Identification Patient Visit Common Order (optional) Order Detail /Observation Request Observation Results (may have repetitions) See the Glossary for definitions of each interface. Proprietary and Confidential 91 .Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages OBR Seq 33 34 35 36 37 38 39 40 41 42 43 44 45 HL7 Field Name Assistant Result Interpreter Technician Transcriptionist Scheduled Date/Time Number of Sample Containers Transport Logistics of Collected Sample Collector’s Comment Transport Arrangement Responsibility Transport Arranged Escort Required Planned Patient Transport Comment Procedure Code Procedure Code Modifier Opt O O O O O O O O O O O O O Length 200 200 200 26 4 60 200 60 30 1 200 80 80 Data Type CM CM CM TS NM CE CE CE ID ID CE CE CE Vision Series Data Mapping/ Comments Scheduled Date/Time ^^^<yyyymmddhhmmss^^s> 4. The HL7 message will consist of the following message segments.1 Definition Vision Series RIS sends the order message event type ORU^R01 which is the Observational Report Unsolicited. Inc. final or addendum reports based upon a trigger define in Vision Series RIS. The ORU will send preliminary. AMICAS.

Opt.3” HL7 version number Current date/time <yyyymmddhhmmss> "|" "^~\&" ”Vision SeriesRIS” <Corporation Name> “PACS” Vision Series Data Mapping/ Comments "NE" AMICAS.2 MSH (Message Header Segment) . and Mapping/Comments: MSH Seq 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgment Type Application Acknowledgment Type Country Code Character Set Principal Language of Message Alternate Character Set Handling Scheme Opt R R O O O O O O R O R R O O O O O O O O Length 1 4 180 180 180 180 26 40 7 20 3 60 15 180 2 2 2 16 60 20 Data Type ST ST HD HD HD HD TS ST CM ST PT ID NM ST ID ID ID ID CE ID "AL" “ORU^R01” System date/time <yyyymmddhhmmss> “P” “2. Proprietary and Confidential 92 . Length. Inc. HL7 Field Name. Rejection Rules. Data Type.7.Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages 4.ORU^R01 The following table lists each Message Header segment and their Seq.

0 HL7 Interface Guide Outbound Messages 4.Patient O 60 CE AMICAS. HL7 Field Name.Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 Language . Opt. Data Type.7.Vision Series RIS 5.Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number . O. Inc.Patient ID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID segment per message “1” Patient Unique Identifier <Internal Patient ID Number> Patient Unique Identifier 3 Patient ID (Internal ID) R 20 CX <Internal Generated Patient ID.Date portion only (YYYYMMDD) Patient Gender (F.ORU^R01 The following table lists each Patient Identification Definition segment and their Seq. Length. PMIS or Social Security> Patient Unique Identifier <Jacket. Proprietary and Confidential 93 .3 PID (Patient Identification Definition Segment) . U) <PMIS code or Gender Code> Patient Alias <Alias field> Patient Ethnicity <PMIS code or Ethnicity Code> Patient Address 8 Sex O 1 ST 9 Patient Alias O 48 XPN 10 Race O 80 IS 11 Patient Address O 106 XAD <Address 1^Address 2^ City^State^Zip^Country> County Code <County Field> Patient Home Phone. M. PMIS or Social Security > Patient Name <lastname^first^middle^suffix> 2 Patient ID (External ID) B 20 CX 4 Alternate Patient ID Patient Name last name first name middle initial Mother’s Maiden Name Date of Birth B 20 CX 5 R 48 XPN 6 7 O O 48 26 XPN TS Patient DOB . and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID . Rejection Rules. Fax. Email 12 County Code B 4 IS 13 Phone Number . Jacket.

7. Length. Data Type. Inc.Vision Series RIS 5. Proprietary and Confidential 94 . Opt.Patient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator B O O O O O O O O O O O 16 25 20 80 60 1 2 80 60 80 26 1 ST CM CX IS ST ID NM IS CE CE TS ID Patient Date of Death <yyyymmdd> 4. and Mapping/Comments: PV1 Seq 1 HL7 Field Name Set ID – PV1 Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PV1 Segment per Message “1” Service Type <PMIS Code for Service Type Code> Patient Location 3 Assigned Patient Location O 80 PL < Location Name ^^^PMIS Code^^^^^Location Name> 2 Patient Class R 1 IS 4 5 Admission Type Preadmit Number O O 2 20 IS CX AMICAS. HL7 Field Name. Rejection Rules.Patient Driver’s Lic Num .ORU^R01 The following table lists each Patient Visit segment and their Seq.0 HL7 Interface Guide Outbound Messages PID Seq 16 17 18 HL7 Field Name Marital Status Religion Patient Account Number Opt O O O Length 80 80 20 Data Type IS IS CX Vision Series Data Mapping/ Comments Patient Marital Status <PMIS Code for Marital Status Code> Patient Unique Identifier <PMIS> Patient SS Number <SS Number> 19 20 21 22 23 24 25 26 27 28 29 30 SSN Number .4 PV1 (Patient Visit Segment) .

Inc.Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages PV1 Seq 6 7 HL7 Field Name Prior Patient Location Attending Doctor Opt O O Length 80 60 Data Type PL XCN Vision Series Data Mapping/ Comments Rank 1 Physician 8 Referring Doctor O 60 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Additional Physicians <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> 9 Consulting Doctor O 60 XCN 10 11 12 13 14 15 16 17 18 Hospital Service Temporary Location Preadmit Test Indicator Readmission Indicator Admit Source Ambulatory Status VIP Indicator Admitting doctor Patient Type O O O O O O O O O 3 80 2 2 3 2 2 60 2 IS PL IS IS IS IS IS XCN IS Service Type <PMIS Code for Service Type Code> Unique Visit Number <System Generated Number> Pregnancy Indicator <B6> if flag <Y> else other 19 20 21 22 23 24 25 26 27 28 29 Visit Number Financial Class Charge Price Indicator Courtesy Code Credit Rating Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code O O O O O O O O O O O 20 50 2 2 2 2 8 12 3 2 1 CX CM IS IS IS IS DT NM NM IS IS AMICAS. Proprietary and Confidential 95 .

Inc. Data Type. Proprietary and Confidential 96 .7. Opt. Rejection Rules.0 HL7 Interface Guide Outbound Messages PV1 Seq 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 HL7 Field Name Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount Bad Debt Recovery Amount Delete Account Indicator Delete Account Date Discharge Disposition Discharged to Location Diet Type Servicing Facility Bed Status Account Status Pending Location Prior Temporary Location Admit Date/Time Opt O O O O O O O O O O B O O O O Length 8 10 12 12 1 8 3 25 80 2 1 2 80 80 26 Data Type DT IS NM NM IS DT IS CM IS IS IS IS PL PL TS Vision Series Data Mapping/ Comments Admit Date <yyyymmdd> Discharge Date <yyyymmdd> 45 46 47 48 49 50 51 52 Discharge Date/Time Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID Visit Indicator Other Healthcare Provider O O O O O O O O 26 12 12 12 12 20 1 60 TS NM NM NM NM CX IS XCN Patient Weight <Patient Weight> 4.Vision Series RIS 5. and Mapping/Comments: ORC Seq 1 HL7 Field Name Order Control Opt R Length 2 Data Type ID “RE” Vision Series Data Mapping/ Comments AMICAS. Length.5 ORC (Common Order Segment) . HL7 Field Name.ORU^R01 The following table lists each Common Order segment and their Seq.

Proprietary and Confidential 97 .Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages ORC Seq 2 HL7 Field Name Placer Order Number Opt C Length 16 Data Type EI Vision Series Data Mapping/ Comments Accession Number <Accession Number> Accession Number <Accession Number> 3 4 5 6 Filler Order Number Placer Group Number Order Status Response Flag Quantity/Timing quantity interval duration start date/time end date/time Priority condition text conjunction order sequencing Parent Date/Time of Transaction C O O O 16 22 2 1 EI EI ID ID “CM” Complete order Scheduled Exam Date/Time O 200 TQ <yyyymmddhhmm^s> if urgent or <R> if not urgent 7 8 9 O O 200 26 CM TS Current Date/Time <yyyymmddhhmmss> User ID & Name 10 Entered By O 120 XCN <User ID^Last Name^First Name^Middle^ Suffix> 11 Verified By Ordering Provider physician id family name given name middle initial or name Enterer’s Location O 120 XCN Rank 1 Physician 12 O 120 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Location ID & Name <^^^PMIS Code^^^^^Location Name> Rank 1 Physician Phone # & Fax # <Phone Number^Fax Number> 13 O 80 PL 14 15 Call Back Phone Number Order Effective Date/Time O O 40 26 XTN TS Reason 16 Order Control Reason O 200 CE <Reason> or <Free Text if Other Reason^Reason> Rank 1 Physician Location <PMIS> or <Unique ID^Phy Location Name> 17 18 Entering Organization Entering Device O O 60 60 CE CE AMICAS. Inc.

HL7 Field Name. Inc. Data Type. Length. Proprietary and Confidential 98 . Rejection Rules. and Mapping/Comments: OBR Seq 1 HL7 Field Name Set ID Observation Request Placer Order Number Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One OBR Segment per Message “1” Accession Number <Accession Number> Accession Number <Accession Number> Procedure Code Procedure Description 4 Universal Service ID identifier text R 200 CE Exam Code Exam Description <Procedure Code^Procedure Description^Exam Code^Exam Description> 5 6 Priority Requested Date/Time B B 2 26 ID TS Scheduled date/time <yyyymmddhhmm> Scheduled date/time <yyyymmddhhmm> 2 C 16 EI 3 Filler Order Number C 16 EI 7 8 9 10 11 12 Observation Date/Time Obs End Date/Time Collection Volume Collector Identifier Specimen Action Code Danger Code C O O O O O 26 26 20 60 1 60 TS TS CQ XCN ID CE AMICAS. Opt.0 HL7 Interface Guide Outbound Messages ORC Seq 19 20 21 22 23 24 HL7 Field Name Action By Advanced Beneficiary Notice Code Ordering Facility Name Ordering Facility Address Ordering Facility Phone Number Ordering Provider Address Opt O O O O O O Length 120 40 60 106 48 106 Data Type XCN CE XON XAD XTN XAD Vision Series Data Mapping/ Comments 4.Vision Series RIS 5.7.6 OBR (Order Detail /Observation Request) .ORU^R01 The following table lists each Order Detail/Observation Request segment and their Seq.

Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages OBR Seq 13 HL7 Field Name Opt Length Data Type ST Vision Series Data Mapping/ Comments Comments Relevant Clinical Info. Proprietary and Confidential 99 . Tilde (~) separates referring from any or all CC physicians. or Unique Group Number for Exam level or Unique Group Number for Visit level <Group Order Number> Procedure Category & Resource 19 Placer Field 2 O 60 ST <Procedure Category Description^Resource Category Title> 16 O 80 XCN 17 Order Callback Phone No. Inc. O 300 <Patient Comments^Visit Comments^Exam Comments^Schedule Comments> 14 Specimen Rec'd Date/Time Specimen Source Source Code Additives Source Description Body Site C 26 TS 15 O 300 CM Ordering (referring) provider. O 40 XTN 20 21 22 23 24 Filler Field 1 Filler Field 2 Result Rpt/Status Change Date/Time Charge To Practice Diagnostic Serv Sect Id O O C O O 60 60 26 40 10 ST ST TS CM ID Schedule Resource <Resource Category Title> Application Entity Title <Modality Name> AMICAS. Ordering Provider physician ID family name given name middle initial or name <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Rank 1 Physician Phone # & Fax # <Phone Number^Fax Number> Group Number for grouping procedures 18 Placer Field 1 O 60 ST Blank if no grouping.

If Report Deleted HL7 trigger point has been selected: “A” if Addendum “C” for Correction 26 Parent Result Quantity/Timing quantity interval duration start date/time end date/time priority condition text conjunction order sequencing priority condition text conjunction order sequencing O 400 CM Scheduled Date/Time O 200 TQ ^^^<yyyymmddhhmmss^^s> if urgent else <R> 27 Additional Physicians <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> <Parent Report Id>^<Child Report Id> 28 Result Copies To O 150 XCN 29 30 Parent Number Transportation Mode O O 200 20 CM ID Reason for Visit 31 Reason For Study O 300 CE <Reason or Free form if Other Reason^Reason or Free form if Other Reason> Dictating Radiologist 32 Principal Result Interpreter O 200 CM <PMIS Code or Unique ID^Last Name^First Name^Middle^Suffix> Approving Radiologist 33 Assistant Result Interpreter O 200 CM <PMIS Code or Unique ID^Last Name^First Name^Middle^Suffix> AMICAS. Inc. Proprietary and Confidential 100 .Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages OBR Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments “F” for Final “A” for Addendum “P” for Preliminary 25 Result Status C 1 ID Final is not appended to the addendum.

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

OBR Seq 34

HL7 Field Name

Opt

Length

Data Type CM

Vision Series Data Mapping/ Comments Technologist

Technician

O

200

<PMIS Code or Unique ID^Last Name^First name^Middle^Suffix> Transcriptionist

35

Transcriptionist

O

200

CM

<PMIS Code or Unique ID^Last Name^First name^Middle^Suffix> Scheduled Date/Time <yyyymmddhhmmss>

36 37 38 39 40 41 42 43 44 45

Scheduled Date/Time Number of Sample Containers Transport Logistics of Collected Sample Collector’s Comment Transport Arrangement Responsibility Transport Arranged Escort Required Planned Patient Transport Comment Procedure Code Procedure Code Modifier

O O O O O O O O O O

26 4 60 200 60 30 1 200 80 80

TS NM CE CE CE ID ID CE CE CE

4.7.7 OBX (Observation/Result Segment) - ORU^R01
The following table lists each Observation/Result segment and their Seq, HL7 Field Name, Opt, Length, Data Type, Rejection Rules, and Mapping/Comments:
OBX Seq 1 2 3 4 5 6 7 8 9 10 HL7 Field Name Set ID - Observation Simple Value Type Observation Identifier Observation Sub-ID Observation Value Units References Range Abnormal Flags Probability Nature of Abnormal Test Opt O C R C C O O O O O Length 4 3 80 20 65536 60 60 5 5 2 Data Type SI ID CE ST * CE ST ID NM ID Vision Series Data Mapping/ Comments Sequence number 'TX' Accession Number <Accession Number> '1' Line of text from report.

AMICAS, Inc. Proprietary and Confidential

101

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

OBX Seq

HL7 Field Name

Opt

Length

Data Type

Vision Series Data Mapping/ Comments “P” if Preliminary Report “F” if Approved/Final

11

Observe Result Status

R

1

ID

If Report Deleted HL7 trigger point has been selected: “C” for Correction “D” for Delete “W” for Wrong

12 13 14 15 16 17

Date Of Last Obs Normal Values User Defined Access Checks Date-Time of the Observation Producer’s ID Responsible Observer Observation Method

O O O O O O

26 20 26 60 80 60

TS ST TS CE XCN CE Transcribed Date/Time <yyyymmddhhmm>

4.8 ORU^R01 – HL7 HTML Result Message Type
4.8.1 Definition
This is an HTML version of the order results message type. It allows the same report in Vision Series RIS to be viewed in other AMICAS products. Vision Series RIS sends the order message event type ORU^R01 which is the Observational Report Unsolicited. The ORU will send preliminary, final or addendum reports based upon a trigger define in Vision Series RIS. The HL7 message will consist of the following message segments. OBX 2 Formatted Text OBX 5 is an Html report representation The following table lists each supported message segment and their description:
Message Segment MSH PID PV1 ORC OBR OBX Segment Description Message Header Patient Identification Patient Visit Common Order (optional) Order Detail /Observation Request Observation Results (may have repetitions)

AMICAS, Inc. Proprietary and Confidential

102

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

See the Glossary for definitions of each interface.

4.8.2 MSH (Message Header Segment) - ORU^R01
The following table lists each Message Header segment and their Seq, HL7 Field Name, Opt, Length, Data Type, Rejection Rules, and Mapping/Comments:
MSH Seq 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgment Type Application Acknowledgment Type Country Code Character Set Principal Language of Message Alternate Character Set Handling Scheme Opt R R O O O O O O R O R R O O O O O O O O Length 1 4 180 180 180 180 26 40 7 20 3 60 15 180 2 2 2 16 60 20 Data Type ST ST HD HD HD HD TS ST CM ST PT ID NM ST ID ID ID ID CE ID "AL" “ORU^R01” System date/time <yyyymmddhhmmss> “P” “2.3” HL7 version number Current date/time <yyyymmddhhmmss> "|" "^~\&" ”Vision SeriesRIS” <Corporation Name> “PACS” Vision Series Data Mapping/ Comments

"NE"

AMICAS, Inc. Proprietary and Confidential

103

Rejection Rules.0 HL7 Interface Guide Outbound Messages 4. Jacket.Date portion only (YYYYMMDD) Patient Gender (F.ORU^R01 The following table lists each Patient Identification Definition segment and their Seq. PMIS or Social Security > Patient Name <lastname^first^middle^suffix> 2 Patient ID (External ID) B 20 CX 4 Alternate Patient ID Patient Name last name first name middle initial Mother’s Maiden Name Date of Birth B 20 CX 5 R 48 XPN 6 7 O O 48 26 XPN TS Patient DOB . O. Proprietary and Confidential 104 . M. Inc. Fax. Data Type.Patient O 60 CE AMICAS.8. HL7 Field Name. Email 12 County Code B 4 IS 13 Phone Number .3 PID (Patient Identification Definition Segment) . Opt.Vision Series RIS 5. and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID .Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number .Patient ID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID segment per message “1” Patient Unique Identifier <Internal Patient ID Number> Patient Unique Identifier 3 Patient ID (Internal ID) R 20 CX <Internal Generated Patient ID. U) <PMIS code or Gender Code> Patient Alias <Alias field> Patient Ethnicity <PMIS code or Ethnicity Code> Patient Address 8 Sex O 1 ST 9 Patient Alias O 48 XPN 10 Race O 80 IS 11 Patient Address O 106 XAD <Address 1^Address 2^ City^State^Zip^Country> County Code <County Field> Patient Home Phone. PMIS or Social Security> Patient Unique Identifier <Jacket. Length.Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 Language .

8.Patient Mother’s Identifier Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veterans Military Status Nationality Patient Death Date/Time Patient Death Indicator B O O O O O O O O O O O 16 25 20 80 60 1 2 80 60 80 26 1 ST CM CX IS ST ID NM IS CE CE TS ID Patient Date of Death <yyyymmdd> 4.4 PV1 (Patient Visit Segment) . Rejection Rules. and Mapping/Comments: PV1 Seq 1 HL7 Field Name Set ID – PV1 Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PV1 Segment per Message “1” Service Type <PMIS Code for Service Type Code> Patient Location 3 Assigned Patient Location O 80 PL < Location Name ^^^PMIS Code^^^^^Location Name> 2 Patient Class R 1 IS 4 5 Admission Type Preadmit Number O O 2 20 IS CX AMICAS.0 HL7 Interface Guide Outbound Messages PID Seq 16 17 18 HL7 Field Name Marital Status Religion Patient Account Number Opt O O O Length 80 80 20 Data Type IS IS CX Vision Series Data Mapping/ Comments Patient Marital Status <PMIS Code for Marital Status Code> Patient Unique Identifier <PMIS> Patient SS Number <SS Number> 19 20 21 22 23 24 25 26 27 28 29 30 SSN Number . Opt. Length.Vision Series RIS 5. Proprietary and Confidential 105 . Inc.Patient Driver’s Lic Num . Data Type.ORU^R01 The following table lists each Patient Visit segment and their Seq. HL7 Field Name.

0 HL7 Interface Guide Outbound Messages PV1 Seq 6 7 HL7 Field Name Prior Patient Location Attending Doctor Opt O O Length 80 60 Data Type PL XCN Vision Series Data Mapping/ Comments Rank 1 Physician 8 Referring Doctor O 60 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Additional Physicians <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> 9 Consulting Doctor O 60 XCN 10 11 12 13 14 15 16 17 18 Hospital Service Temporary Location Preadmit Test Indicator Readmission Indicator Admit Source Ambulatory Status VIP Indicator Admitting doctor Patient Type O O O O O O O O O 3 80 2 2 3 2 2 60 2 IS PL IS IS IS IS IS XCN IS Service Type <PMIS Code for Service Type Code> Unique Visit Number <System Generated Number> Pregnancy Indicator <B6> if flag <Y> else other 19 20 21 22 23 24 25 26 27 28 29 Visit Number Financial Class Charge Price Indicator Courtesy Code Credit Rating Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code O O O O O O O O O O O 20 50 2 2 2 2 8 12 3 2 1 CX CM IS IS IS IS DT NM NM IS IS AMICAS. Proprietary and Confidential 106 .Vision Series RIS 5. Inc.

5 ORC (Common Order Segment) .Vision Series RIS 5. Length. Inc. and Mapping/Comments: ORC Seq 1 HL7 Field Name Order Control Opt R Length 2 Data Type ID “RE” Vision Series Data Mapping/ Comments AMICAS.0 HL7 Interface Guide Outbound Messages PV1 Seq 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 HL7 Field Name Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount Bad Debt Recovery Amount Delete Account Indicator Delete Account Date Discharge Disposition Discharged to Location Diet Type Servicing Facility Bed Status Account Status Pending Location Prior Temporary Location Admit Date/Time Opt O O O O O O O O O O B O O O O Length 8 10 12 12 1 8 3 25 80 2 1 2 80 80 26 Data Type DT IS NM NM IS DT IS CM IS IS IS IS PL PL TS Vision Series Data Mapping/ Comments Admit Date <yyyymmdd> Discharge Date <yyyymmdd> 45 46 47 48 49 50 51 52 Discharge Date/Time Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID Visit Indicator Other Healthcare Provider O O O O O O O O 26 12 12 12 12 20 1 60 TS NM NM NM NM CX IS XCN Patient Weight <Patient Weight> 4. Data Type.8. Rejection Rules. Opt. HL7 Field Name.ORU^R01 The following table lists each Common Order segment and their Seq. Proprietary and Confidential 107 .

0 HL7 Interface Guide Outbound Messages ORC Seq 2 HL7 Field Name Placer Order Number Opt C Length 16 Data Type EI Vision Series Data Mapping/ Comments Accession Number <Accession Number> Accession Number <Accession Number> 3 4 5 6 Filler Order Number Placer Group Number Order Status Response Flag Quantity/Timing quantity interval duration start date/time end date/time Priority condition text conjunction order sequencing Parent Date/Time of Transaction C O O O 16 22 2 1 EI EI ID ID “CM” Complete order Scheduled Exam Date/Time O 200 TQ <yyyymmddhhmm^s> if urgent or <R> if not urgent 7 8 9 O O 200 26 CM TS Current Date/Time <yyyymmddhhmmss> User ID & Name 10 Entered By O 120 XCN <User ID^Last Name^First Name^Middle^ Suffix> 11 Verified By Ordering Provider physician id family name given name middle initial or name Enterer’s Location O 120 XCN Rank 1 Physician 12 O 120 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Location ID & Name <^^^PMIS Code^^^^^Location Name> Rank 1 Physician Phone # & Fax # <Phone Number^Fax Number> 13 O 80 PL 14 15 Call Back Phone Number Order Effective Date/Time O O 40 26 XTN TS Reason 16 Order Control Reason O 200 CE <Reason> or <Free Text if Other Reason^Reason> Rank 1 Physician Location <PMIS> or <Unique ID^Phy Location Name> 17 18 Entering Organization Entering Device O O 60 60 CE CE AMICAS. Proprietary and Confidential 108 .Vision Series RIS 5. Inc.

Inc.8. Rejection Rules. Data Type. Opt.ORU^R01 The following table lists each Order Detail/Observation Request segment and their Seq.Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages ORC Seq 19 20 21 22 23 24 HL7 Field Name Action By Advanced Beneficiary Notice Code Ordering Facility Name Ordering Facility Address Ordering Facility Phone Number Ordering Provider Address Opt O O O O O O Length 120 40 60 106 48 106 Data Type XCN CE XON XAD XTN XAD Vision Series Data Mapping/ Comments 4. and Mapping/Comments: OBR Seq 1 HL7 Field Name Set ID Observation Request Placer Order Number Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One OBR Segment per Message “1” Accession Number <Accession Number> Accession Number <Accession Number> Procedure Code Procedure Description 4 Universal Service ID identifier text R 200 CE Exam Code Exam Description <Procedure Code^Procedure Description^Exam Code^Exam Description> 5 6 Priority Requested Date/Time B B 2 26 ID TS Scheduled date/time <yyyymmddhhmm> Scheduled date/time <yyyymmddhhmm> 2 C 16 EI 3 Filler Order Number C 16 EI 7 8 9 10 11 12 Observation Date/Time Obs End Date/Time Collection Volume Collector Identifier Specimen Action Code Danger Code C O O O O O 26 26 20 60 1 60 TS TS CQ XCN ID CE AMICAS. Proprietary and Confidential 109 . Length.6 OBR (Order Detail /Observation Request) . HL7 Field Name.

or Unique Group Number for Exam level or Unique Group Number for Visit level <Group Order Number> Procedure Category & Resource 19 Placer Field 2 O 60 ST <Procedure Category Description^Resource Category Title> 20 21 22 23 24 Filler Field 1 Filler Field 2 Result Rpt/Status Change Date/Time Charge To Practice Diagnostic Serv Sect Id O O C O O 60 60 26 40 10 ST ST TS CM ID Schedule Resource <Resource Category Title> Application Entity Title <Modality Name> AMICAS. Inc. Tilde (~) separates referring from any or all CC physicians. O 300 <Patient Comments^Visit Comments^Exam Comments^Schedule Comments> 14 Specimen Rec'd Date/Time Specimen Source Source Code Additives Source Description Body Site C 26 TS 15 O 300 CM 16 Ordering Provider physician ID family name given name middle initial or name Ordering (referring) provider.0 HL7 Interface Guide Outbound Messages OBR Seq 13 HL7 Field Name Opt Length Data Type ST Vision Series Data Mapping/ Comments Comments Relevant Clinical Info.Vision Series RIS 5. Proprietary and Confidential 110 . O 40 XTN 18 Placer Field 1 O 60 ST Blank if no grouping. O 80 XCN <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> Rank 1 Physician Phone # & Fax # <Phone Number^Fax Number> Group Number for grouping procedures 17 Order Callback Phone No.

Proprietary and Confidential 111 .Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages OBR Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments “F” for Final “A” for Addendum “P” for Preliminary 25 Result Status C 1 ID Final is not appended to the addendum. If Report Deleted HL7 trigger point has been selected: “A” if Addendum “C” for Correction 26 Parent Result Quantity/Timing quantity interval duration start date/time end date/time priority condition text conjunction order sequencing priority condition text conjunction order sequencing O 400 CM Scheduled Date/Time O 200 TQ ^^^<yyyymmddhhmmss^^s> if urgent else <R> 27 Additional Physicians <Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix^~ Physician Identifier (configurable to Location PMIS Code or RIS Unique Identifier and/or NPI)^LastName^First^Middle Name^Suffix> <Parent Report Id>^<Child Report Id> 28 Result Copies To O 150 XCN 29 30 Parent Number Transportation Mode O O 200 20 CM ID Reason for Visit 31 Reason For Study O 300 CE <Reason or Free form if Other Reason^Reason or Free form if Other Reason> Dictating Radiologist 32 Principal Result Interpreter O 200 CM <PMIS Code or Unique ID^Last Name^First Name^Middle^Suffix> Approving Radiologist 33 Assistant Result Interpreter O 200 CM <PMIS Code or Unique ID^Last Name^First Name^Middle^Suffix> AMICAS. Inc.

The report will keep the same formatting as displayed in RIS.8. Inc. Data Type. Length.7 OBX (Observation/Result Segment) . HL7 Field Name. Proprietary and Confidential 112 . Opt.Observation Simple Formatted Text Observation Identifier Observation Sub-ID HTML Report Representation Units References Range Abnormal Flags Opt O C R C C O O O Length 4 2 80 20 65536 60 60 5 Data Type SI ID CE ST * CE ST ID Vision Series Data Mapping/ Comments Sequence number 'FT' Accession Number <Accession Number> '1' An HTML representation of the report in Vision Series RIS. and Mapping/Comments: OBX Seq 1 2 3 4 5 6 7 8 HL7 Field Name Set ID .0 HL7 Interface Guide Outbound Messages OBR Seq 34 HL7 Field Name Opt Length Data Type CM Vision Series Data Mapping/ Comments Technologist Technician O 200 <PMIS Code or Unique ID^Last Name^First name^Middle^Suffix> Transcriptionist 35 Transcriptionist O 200 CM <PMIS Code or Unique ID^Last Name^First name^Middle^Suffix> Scheduled Date/Time <yyyymmddhhmmss> 36 37 38 39 40 41 42 43 44 45 Scheduled Date/Time Number of Sample Containers Transport Logistics of Collected Sample Collector’s Comment Transport Arrangement Responsibility Transport Arranged Escort Required Planned Patient Transport Comment Procedure Code Procedure Code Modifier O O O O O O O O O O 26 4 60 200 60 30 1 200 80 80 TS NM CE CE CE ID ID CE CE CE 4.ORU^R01 The following table lists each Observation/Result segment and their Seq. Rejection Rules. AMICAS.Vision Series RIS 5.

9. Proprietary and Confidential 113 .0 HL7 Interface Guide Outbound Messages OBX Seq 9 10 HL7 Field Name Probability Nature of Abnormal Test Opt O O Length 5 2 Data Type NM ID Vision Series Data Mapping/ Comments “P” if Preliminary Report “F” if Approved/Final 11 Observe Result Status R 1 ID If Report Deleted HL7 trigger point has been selected: “C” for Correction “D” for Delete “W” for Wrong 12 13 14 15 16 17 Date Of Last Obs Normal Values User Defined Access Checks Date-Time of the Observation Producer’s ID Responsible Observer Observation Method O O O O O O 26 20 26 60 80 60 TS ST TS CE XCN CE Transcribed Date/Time <yyyymmddhhmm> 4. The following table lists each supported message segment and their description: Message Segment MSH PID PV1 PV2 GT1 ACC DB1 IN1 Segment Description Message Header Patient Identification Patient Visit Patient Visit Guarantor Accident Disability Insurance AMICAS. The function of this message is to initiate the transmission of information about procedures qualifying for charges.1 Definition Vision Series RIS uses the order message event type ORM^O01 to send the Charge Out information to the billing system.9 ORM^O01 – HL7 Batch Charge Out Message Type 4. The message is triggered to be sent once a charge out is done.Vision Series RIS 5. The receiving billing system can pick up the message and continue with the charge out process. Inc.

4. Inc.Vision Series RIS 5. Proprietary and Confidential 114 . Rejection Rules. HL7 Field Name.ORM^O01 The following table lists each Message Header segment and their Seq.2 MSH (Message Header Segment) . Length.Currently "2. Data Type.3"> Order Message Type "ORM^O01" Message Unique Identifier <System Generated Number> Date and Time of File Creation <yyyymmddhhmmss> "MSH" "^~\&" "Vision Series RIS" Corporation Name <Corporation Name> "Billing System" Vision Series Data Mapping/ Comments AMICAS. Opt.0 HL7 Interface Guide Outbound Messages Message Segment IN2 PR1 Segment Description Insurance Procedure See the Glossary for definitions of each interface. and Mapping/Comments: MSH Seq 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/Time of Message Security Message Type Message Control ID Processing ID Version ID Sequence Number Continuation Pointer Accept Acknowledgment Type Application Acknowledgment Type Country Code ID Character Set Principal Language of Message Alternate Character Set Handling Scheme Opt R R O O O O O O R R R R O O O O O O O O Length 4 4 180 180 180 180 26 40 7 20 3 60 15 180 2 2 2 16 60 20 Data Type ST ST HD HD HD HD TS ST CM ST PT VID NM ST ID ID ID ID CE ID HL7 Version <Version Number .9.

and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID .0 HL7 Interface Guide Outbound Messages 4. Rejection Rules. Fax. Length. Inc.3 PID (Patient Identification Definition Segment) .ORM^O01 The following table lists each Patient Identification Definition segment and their Seq. HL7 Field Name.PID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID Segment per Message "1" Patient Unique Identifier <Jacket> Patient Unique Identifier <Jacket> Patient Unique Identifier <Social Security > Patient Name <Last Name^First^Middle^Suffix> 2 Patient ID External B 20 CX 3 Patient ID Internal R 20 CX 4 Alternate Patient ID B 20 CX 5 6 7 8 9 10 Patient Name Mother Maiden Name Date Of Birth Sex Patient Alias Race R O O O O O 48 48 26 1 48 80 XPN XPN TS ST XPN IS Patient DOB <yyyymmdd> Patient Gender <PMIS code or Gender Code> Patient Alias <Alias field> Patient Ethnicity <PMIS code or Ethnicity Code> Patient Address <Address 1^Address 2^City^State^Zip^ Country> County Code <County Field> Patient Home Phone. Data Type.Vision Series RIS 5. Proprietary and Confidential 115 . Email <(Area Code)Phone Number^(Fax Area Code) Fax Number^Email Address> Work Phone <(Area Code)Phone Number> 11 Patient Address O 106 XAD 12 County Code B 4 IS 13 Home Phone O 40 XTN 14 15 16 17 18 Business Phone Patient Language Marital Status Religion Patient Account Number O O O O O 40 60 80 80 20 XTN CE IS IS CX Patient Marital Status <PMIS code for Martial Status Code> Patient Unique Identifier <PMIS> AMICAS. Opt.9.

PV1 Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PV1 Segment per Message "1" Service Type <PMIS Code for Service Type Code> Patient Location <Location PMIS or Unique Identification Number^Location Name> 2 Patient Class R 1 IS 3 4 5 6 Assigned Patient Location Admission Type Preadmit Number Prior Patient Location O O O O 80 2 20 80 PL IS CX PL Attending (referring) Provider. Length. 7 Attending Doctor O 60 XCN <Physician Location PMIS Code or Physician Location Unique Identifier^Last Name^First^Middle Name^Suffix^~PMIS^ Last Name^First Name^Middle Name^ Suffix> AMICAS. A Tilde (~) separates referring from any/all cc physicians.0 HL7 Interface Guide Outbound Messages PID Seq 19 20 21 22 23 24 25 26 27 28 29 30 HL7 Field Name Patient SSN Drivers License Number Mother ID Ethnic Group Birth Place Multiple Birth Indicator Birth Order Citizenship Veteran’s Military Status Nationality Patient Death Date and Time Patient Death Indicator Opt B O O O O O O O O O O O Length 16 25 20 80 60 1 2 80 60 80 26 1 Data Type ST CM CX IS ST ID NM IS CE CE TS ID Vision Series Data Mapping/ Comments Patient SS Number <SS Number format ###-##-####> Patient PMIS Number Patient Date of Death <yyyymmdd> 4. HL7 Field Name.Vision Series RIS 5. Rejection Rules.4 PV1 (Patient Visit Segment) . Inc. and Mapping/Comments: PV1 Seq 1 HL7 Field Name Set . Data Type.ORM^O01 The following table lists each Patient Visit segment and their Seq. Opt.9. Proprietary and Confidential 116 .

Proprietary and Confidential 117 .Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages PV1 Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments Rank 1 Physician <Physician Location PMIS Code or Physician Location Unique Identifier ^Last Name^First^Middle^Suffix ^^^^^^^^^^^^National Provider Identification> Additional Physicians <Physician Location PMIS Code or Physician Location Unique Identifier ^Last Name^First^Middle^Suffix~PMIS Code or Unique Identification Number^Last Name^First^Middle^Suffix~(additional physicians)> 8 Referring Doctor O 60 XCN 9 Consulting Doctor O 60 XCN 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Hospital Service Temporary Location Preadmit Test Indicator Re-admission Indicator Admit Source Ambulatory Status VIP Indicator Admitting Doctor Patient Type Visit Number Financial Class Charge Price Indicator Courtesy Code Credit Rating Contract Code Contract Effective Date Contract Amount Contract Period Interest Code Transfer to Bad Debt Code Transfer to Bad Debt Date Bad Debt Agency Code Bad Debt Transfer Amount O O O O O O O O O O O O O O O O O O O O O O O 3 80 2 2 3 2 2 60 2 20 50 2 2 2 2 8 12 3 2 1 8 10 12 IS PL IS IS IS IS IS XCN IS CX CM IS IS IS IS DT NM NM IS IS DT IS NM Service Type <PMIS code for Service Type Code> Unique Visit Number <System Generated Number> <Room Number> AMICAS. Inc.

5 PV2 (Patient Visit Segment) . HL7 Field Name.9. Length. Inc. Rejection Rules. Schedule & Visit) <(comment type)^(comment free text)> Vision Series Data Mapping/ Comments AMICAS. Proprietary and Confidential 118 . Data Type. Opt.0 HL7 Interface Guide Outbound Messages PV1 Seq 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 HL7 Field Name Bad Debt Recovery Amount Delete Account Indicator Delete Account Date Discharge Disposition Discharged to Location Diet Type Servicing Facility Bed Status Account Status Pending Location Prior Temporary Location Admit Date/Time Discharge Date/Time Current Patient Balance Total Charges Total Adjustments Total Payments Alternate Visit ID Visit Indicator Other Healthcare Provider Opt O O O O O O O B O O O O O O O O O O O O Length 12 1 8 3 25 80 2 1 2 80 80 26 26 12 12 12 12 20 1 60 Data Type NM IS DT IS CM IS IS IS IS PL PL TS TS NM NM NM NM CX IS XCN Vision Series Data Mapping/ Comments Admit Date <yyyymmdd> Discharge Date <yyyymmdd> <Order Number> (specific to a visit) <Patient Weight> 4.ORM^O01 The following table lists each Patient Visit segment and their Seq.Vision Series RIS 5. and Mapping/Comments: PV2 Seq 1 2 3 4 5 HL7 Field Name Prior Pending Location Accommodation Code Admit Reason Transfer Reason Patient Valuables Opt C O O O O Length 80 250 250 250 25 Data Type PL CE CE CE ST Comments (Patient.

Proprietary and Confidential 119 . Inc.0 HL7 Interface Guide Outbound Messages PV2 Seq 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 HL7 Field Name Patient Valuables Location Visit User Code Expected Admit Date/Time Expected Discharge Date/Time Estimated Length of Inpatient Stay Actual Length of Inpatient Stay Visit Description Referral Source Code Previous Service Date Employment Illness Related Indicator Purge Status Code Purge Status Date Special Program Code Retention Indicator Expected Number of Insurance Plans Visit Publicity Code Visit Protection Indicator Clinic Organization Name Patient Status Code Visit Priority Code Previous Treatment Date Expected Discharge Disposition Signature on File Date Opt O O O O O O O O O O O O O O O O O O O O O O O Length 25 2 26 26 3 3 50 250 8 1 1 8 2 1 1 1 1 250 2 1 8 2 8 Data Type ST IS TS TS NM NM ST XCN DT ID IS DT Vision Series Data Mapping/ Comments Visit Reason <Visit Reason> Onset Date Questionnaire Response Date <yyyymmdd> Special Program Code IS <Special Program Code> ID NM IS ID XON IS IS ST IS DT Similar Onset Date Questionnaire Response Date <yyyymmdd> 30 31 Patient Charge Adjustment Code Recurring Service Code O O 250 2 CE IS Pregnancy Indicator <Y> 29 First Similar Illness Date O 8 DT AMICAS.Vision Series RIS 5.

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

PV2 Seq 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47

HL7 Field Name Billing Media Code Expected Surgery Date and Time Military Partnership Code Military Non-Availability Code Newborn Baby Indicator Baby Detained Indicator Mode of Arrival Code Recreational Drug Use Code Admission Level of Care Code Precaution Code Patient Condition Code Living Will Code Organ Donor Code Advance Directive Code Patient Status Effective Date Expected LOA Return Date/Time

Opt O O O O O O

Length 1 26 1 1 1 1 250 250 250 250 250 2 2 250 8 26

Data Type ID TS ID ID ID ID

Vision Series Data Mapping/ Comments

LMP Questionnaire Response

4.9.6 GT1 (Guarantor Segment) - ORM^O01
The following table lists each Guarantor segment and their Seq, HL7 Field Name, Opt, Length, Data Type, Rejection Rules, and Mapping/Comments:
GT1 Seq 1 HL7 Field Name Set ID - GT1 Opt R Length 4 Data Type SI Vision Series Data Mapping/ Comments One GT1 Segment per Message "1" Guarantor PMIS <PMIS Code> Guarantor Name <Last Name^First^Middle^Suffix>

2

Guarantor Number

O

59

CX

3 4 5 6

Guarantor Name Guarantor Spouse Name Guarantor Address Guarantor Ph Num - Home

R O O O

48 48 106 40

XPN XPN XAD XTN

Guarantor Address <Address 1^^City^State^Zip^Country> Guarantor Home Phone <(Area Code)Phone Number^^>

AMICAS, Inc. Proprietary and Confidential

120

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

GT1 Seq 7 8 9 10 11 12 13 14 15 16 17

HL7 Field Name Guarantor Ph Num Business Guarantor Date/Time Of Birth Guarantor Administrative Sex Guarantor Type Guarantor Relationship Guarantor SSN Guarantor Date - Begin Guarantor Date - End Guarantor Priority Guarantor Employer Name Guarantor Employer Address Guarantor Employer Phone Number Guarantor Employee ID Number Guarantor Employment Status Guarantor Organization Name Guarantor Billing Hold Flag Guarantor Credit Rating Code Guarantor Death Date And Time Guarantor Death Flag Guarantor Charge Adjustment Code Guarantor Household Annual Income Guarantor Household Size Guarantor Employer ID Number Guarantor Marital Status Code

Opt O O O O O O O O O O O

Length 40 26 1 2 120 11 8 8 2 130 106

Data Type XTN TS ST IS CE ST DT DT NM XPN XAD

Vision Series Data Mapping/ Comments Guarantor Work Phone <(Area Code)Phone Number> Guarantor DOB <yyyymmdd> Guarantor Gender <PMIS code or Gender Code> Guarantor Qualifier <"1" if person> Guarantor Relationship to Patient <PMIS code or Relationship Code> Guarantor SS Number <SS Number format ###-##-####>

Guarantor Employer Name <Employer Name> Guarantor Employer Address <Address 1^^City^State^Zip> Employer Phone, Fax, Email <(Area Code)Phone Number^Fax Number^Email Address>

18

O

40

XTN

19 20 21 22 23 24 25 26 27 28 29 30

O O O O O O O O O O O O

20 2 130 1 80 26 1 80 10 3 20 80

CX IS XON ID CE TS ID CE CP NM CX CE Guarantor Employer ID <PMIS or Unique Identification Number>

AMICAS, Inc. Proprietary and Confidential

121

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

GT1 Seq 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55

HL7 Field Name Guarantor Hire Effective Date Employment Stop Date Living Dependency Ambulatory Status Citizenship Primary Language Living Arrangement Publicity Code Protection Indicator Student Indicator Religion Mother’s Maiden Name Nationality Ethnic Group Contact Person’s Name Contact Person’s Telephone Number Contact Reason Contact Relationship Job Title Job Code/Class Guarantor Employer’s Organization Name Handicap Job Status Guarantor Financial Class Guarantor Race

Opt O O O O O O O O O O O O O O O O O O O O O O O O O

Length 8 8 2 2 80 60 2 80 1 2 80 48 80 80 48 40 80 2 20 20 130 2 2 50 80

Data Type DT DT IS IS CE CE IS CE ID IS CE XPN CE CE XPN XTN CE IS ST JCC XON IS IS FC IS

Vision Series Data Mapping/ Comments

Guarantor Ethnicity <PMIS Code or Ethnicity Code>

AMICAS, Inc. Proprietary and Confidential

122

8 DB1 (Disability Segment) . Rejection Rules. Opt. HL7 Field Name.7 ACC (Accident Segment) .0 HL7 Interface Guide Outbound Messages 4. and Mapping/Comments: ACC Seq 1 HL7 Field Name Accident Date/Time Opt O Length 26 Data Type TS Vision Series Data Mapping/ Comments Accident Date <yyyymmdd> Accident Code <PMIS Code> 2 3 4 5 6 7 8 9 10 Accident Code Accident Location Auto Accident State Accident Job Related Indicator Accident Death Indicator Entered By Accident Description Brought In By Police Notified Indicator O O O O O 60 25 60 1 12 250 25 80 1 CE ST CE ID ID Accident State <State> Accident Type <Accident Type> 4. Length. Opt. Data Type.DB1 Disabled Person Code Disabled Person Identifier Disability Indicator Opt R O O O Length 4 2 32 1 Data Type SI IS CX ID Disability Start Date Questionnaire Response <yyyymmdd> Disability End Date Questionnaire Response <yyyymmdd> Disability Return to Work Date Disability Work Return Date Questionnaire Response <yyyymmdd> Vision Series Data Mapping/ Comments One Disability Segment per Message "1" 5 Disability Start Date O 8 DT 6 Disability End Date O 8 DT 7 O 8 DT AMICAS.ORM^O01 The following table lists each Accident segment and their Seq. HL7 Field Name.9.ORM^O01 The following table lists each Disability segment and their Seq. Length.9. Rejection Rules.Vision Series RIS 5. and Mapping/Comments: DB1 Seq 1 2 3 4 HL7 Field Name Set ID . Inc. Data Type. Proprietary and Confidential 123 .

0 HL7 Interface Guide Outbound Messages DB1 Seq 8 HL7 Field Name Disability Unable to Work Date Opt O Length 8 Data Type DT Vision Series Data Mapping/ Comments Last Worked Date Questionnaire Response <yyyymmdd> 4.IN1 R 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Insurance Plan ID Insurance Company ID Insurance Company Name Insurance Company Address Insurance Co Contact Person Insurance Co Phone Number Group Number Group Name Insured’s Group Emp ID Insured’s Group Emp Name Plan Effective Date Plan Expiration Date Authorization Information Plan Type Name Of Insured R R O O O O O O O O O O O O O 60 59 130 106 48 40 12 130 12 130 8 8 55 3 48 CE CX XON XAD XPN XTN ST XON CX XON DT DT CM IS XPN Effective Plan Start Date <yyyymmdd> Effective Plan End Date <yyyymmdd> Authorization. and Mapping/Comments: IN1 Seq 1 HL7 Field Name Opt Length Data Type SI Vision Series Data Mapping/ Comments Number sequentially increased for each insurance segment provided <sequence identifier> Insurance Carrier Code <Insurance Carrier Code> Insurance Coverage Plan Code <Coverage Plan Code> Insurance Name <Insurance Carrier Name> Insurance Address <Address 1^Address 2^City^State^Zip> Insurance Contact Name <Contact Name> Insurance Phone Number <(Area Code)Phone Number> Group Number <Group Number> Group or Plan Name <Coverage Plan Name> Member Number <Member Number> Set ID . Opt. Length.9. Proprietary and Confidential 124 . Data Type. Rejection Rules.9 IN1 (Insurance Segment) .ORM^O01 The following table lists each Insurance segment and their Seq.Vision Series RIS 5. Identifier <Authorization^^G1> Insurance Plan Type <Plan Type Name> Insured Name <Last Name^First^Middle^Suffix> AMICAS. Date. Inc. HL7 Field Name.

Days Room Rate . N.Private Insured’s Employment Status Insured’s Administrative Sex Opt O O O O O O O O O O O O O O O O O O O O O B O B B O O Length 80 26 106 2 2 2 1 8 1 8 2 15 26 60 2 2 4 4 8 15 12 12 4 12 12 60 1 Data Type CE TS XAD IS IS ST ID DT ID DT IS ST TS XCN IS IS NM NM IS ST CP CP NM CP CP CE IS Vision Series Data Mapping/ Comments Insured Relationship & Qualifier <PMIS Code for Relationship^ "1"=person> Insured DOB <yyyymmdd> Insured Address <Address 1^^City^State^Zip^Country> Release Information <Y. or empty> Policy Number <Policy Number> Insured's Employment Status <PMIS Code or Employment Status Code> Insured's Gender <PMIS Code or Gender Code> AMICAS.Semi-Private Room Rate .0 HL7 Interface Guide Outbound Messages IN1 Seq 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 HL7 Field Name Insured’s Relationship To Patient Insured’s Date Of Birth Insured’s Address Assignment Of Benefits Coordination Of Benefits Coord Of Ben. Proprietary and Confidential 125 .R. Day Company Plan Code Policy Number Policy Deductible Policy Limit .Amount Policy Limit . Priority Notice Of Admission Flag Notice Of Admission Date Report Of Eligibility Flag Report Of Eligibility Date Release Information Code Pre-Admit Cert (PAC) Verification Date/Time Verification By Type Of Agreement Code Billing Status Lifetime Reserve Days Delay Before L. Inc.Vision Series RIS 5.

HL7 Field Name.9.10 IN2 (Insurance Segment) . Opt. Rejection Rules. Data Type. and Mapping/Comments: IN2 Seq 1 2 HL7 Field Name Insured's Employee ID Insured's Social Security Number Insured's Employer Name and ID Employer Information Data Mail Claim Party Medicare Health Ins Card Number Medicaid Case Name Medicaid Case Number Military Sponsor Name Military ID Number Dependent Of Military Recipient Military Organization Military Station Military Service Military Rank/Grade Military Status Military Retire Date Military Non-Avail Cert On File Opt O O Length 59 11 Data Type CX ST Insured's SS Number <SS Number format ###-##-####> Insured's Employer Name and ID <Employer Name^PMIS or Unique Identification Number> Vision Series Data Mapping/ Comments 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 O O O O O O O O O O O O O O O O 130 1 1 15 48 15 48 20 80 25 25 14 2 3 8 1 XCN IS IS ST XPN ST XPN ST CE ST ST IS IS IS DT ID AMICAS. Proprietary and Confidential 126 .ORM^O01 The following table lists each Insurance segment and their Seq. Inc.Vision Series RIS 5.0 HL7 Interface Guide Outbound Messages IN1 Seq 44 45 46 47 48 49 HL7 Field Name Insured’s Employer’s Address Verification Status Prior Insurance Plan ID Coverage Type Handicap Insured’s ID Number Opt O O O O O O Length 106 2 8 3 2 12 Data Type XAD ST IS IS IS CX Vision Series Data Mapping/ Comments Insured's Employer Address <Address 1^^City^State^Zip> Insured's SS Number <SS Number format ###-##-####> 4. Length.

Proprietary and Confidential 127 .0 HL7 Interface Guide Outbound Messages IN2 Seq 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 HL7 Field Name Baby Coverage Combine Baby Bill Blood Deductible Special Coverage Approval Name Special Coverage Approval Title Non-Covered Insurance Code Payor ID Payor Subscriber ID Eligibility Source Room Coverage Type/Amount Policy Type/Coverage Daily Deductible Living Dependency Ambulatory Status Citizenship Primary Language Living Arrangement Publicity Code Protection Indicator Student Indicator Religion Mother's Maiden Name Nationality Ethnic Group Marital Status Insured's Employment Start Date Employment Stop Date Job Title Job Code/Class Opt O O O O O O O O O O O O O O O O O O O O O O O O O O O O O Length 1 1 1 48 30 8 59 59 1 25 25 25 2 2 80 60 2 80 1 2 80 48 80 80 80 8 8 20 20 Data Type ID ID ST XPN ST IS CX CX IS CM CM CM IS IS CE CE IS CE ID IS CE XPN CE CE CE DT DT ST JCC Vision Series Data Mapping/ Comments Insured's Marital Status <PMIS Code or Marital Status Code> AMICAS.Vision Series RIS 5. Inc.

Vision Series RIS 5. Contact Reason Insurance Co.0 HL7 Interface Guide Outbound Messages IN2 Seq 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 HL7 Field Name Job Status Employer Contact Person Name Employer Contact Person Phone Number Employer Contact Reason Insured Contact Person Name Insured Contact Person's Phone Number Employer Contact Person Reason Relationship To The Patient Start Date Relationship To The Patient Stop Date Insurance Co. Proprietary and Confidential 128 . Contact Phone Number Policy Scope Policy Source Patient Member Number Guarantor's Relationship To Insured Insured's Phone Number Home Insured's Employer Phone Number Military Handicapped Program Suspend Flag Copay Limit Flag Stoploss Limit Flag Insured Organization Name and ID Insured Employer Organization Name and ID Race HCFA Patient's Relationship to Insured Opt O O O O O O O O O O O O O O O O O O O O O O O O O Length 2 48 40 2 48 40 2 8 8 2 40 2 2 60 80 40 40 60 1 1 1 130 130 80 60 Data Type IS XPN XTN IS XPN XTN IS DT DT IS XTN IS IS CX CE XTN XTN CE ID ID ID XON XON CE CE Vision Series Data Mapping/ Comments Insured's Employment Status <PMIS Code or Employment Status Code> Insured Phone Number <(Area Code)Phone Number> AMICAS. Inc.

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

4.9.11

PR1 (Procedure Segment) - ORM^O01
The following table lists each Procedure segment and their Seq, HL7 Field Name, Opt, Length, Data Type, Rejection Rules, and Mapping/Comments:
PR1 Seq 1 HL7 Field Name Opt Length Data Type SI Vision Series Data Mapping/ Comments Number sequentially increased for each procedure segment provided <sequence identifier>

Set - PR1

R (B) R

4

2

Procedure Coding Method

2

IS Procedure Code, Unit Value and Accession Number <Procedure Code^Unit^Accession Number> Procedure Code Description and Resource Category <Procedure Code Description^Resource Category> Procedure Schedule Date and Time <yyyymmddhhmm>

3

Procedure Code

R

80

CE

4

Procedure Description

B

40

ST

5 6 7 8 9 10 11

Procedure Date/Time Procedure Functional Type Procedure Minutes Anesthesiologist Anesthesia Code Anesthesia Minutes Surgeon

R R O B O O B

26 2 4 120 2 4 120

TS IS NM XCN IS NM XCN

Technologist PMIS <PMIS Code> Dictating Radiologist <PMIS code or Unique Identification Number^Last Name^First^Middle^Suffix>

12 13 14 15

Procedure Practitioner Consent Code Procedure Priority Associated Diagnosis Code

B O O O

230 60 2 80

XCN CE NM CE

Diagnosis Codes <Diagnosis Code 1~Diagnosis Code 2~(all diagnoses)> Procedure Modifier Rank 1 <Procedure Modifier 1~Modifier 2~Modifier 3~Modifier 4>

16

Procedure Code Modifier

O

80

CE

AMICAS, Inc. Proprietary and Confidential

129

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

4.10 ACK – Acknowledgment Message Type
4.10.1 Definition
The HL7 Acknowledgment Message Type, ACK will be sent by the filler to Vision Series RIS with a success or error message. Once a message is sent from Vision Series RIS (VSRIS) the filler should validate the message. If validation fails, a reject message should be constructed and returned to VSRIS. If validation does not fail, a success message should be returned to VSRIS. The following tables list each Message Type, Trigger Event Type and their descriptions:
Message Type MSH MSA Trigger Event Type A08, A34, R01 A08, A34, R01 Description Message Header Message Acknowledgment

See the Glossary for definitions of each interface.

4.10.2 MSH (Message Header Segment) - ACK
The following table lists each Message Header segment and their Seq, HL7 Field Name, Opt, Length, Data Type, Rejection Rules, and Mapping/Comments:
MSH Seq 1 2 3 4 5 6 7 8 9 HL7 Field Name Field Separator Encoding Characters Sending Application Sending Facility Receiving Application Receiving Facility Date/time of Message Security Message Type Opt R R O O O O O O R Length 1 4 180 180 180 180 26 40 7 Data Type ST ST HD HD HD HD TS ST CM “ACK” System date/time 10 Message Control ID O 20 ST <yyyymmddhhmmss> This ID is echoed back to the placer in the MSA segment. 11 12 13 14 Processing ID Version ID Sequence Number Continuation Pointer R R O O 3 60 15 180 PT VID NM ST “P” “2.3” HL7 version number Current date/time <yyyymmddhhmmss> "|" "^~\&" ”Vision Series RIS” <Corporation Name> “PACS” Vision Series Data Mapping/ Comments

AMICAS, Inc. Proprietary and Confidential

130

Vision Series RIS 5.0 HL7 Interface Guide

Outbound Messages

MSH Seq 15 16 17 18 19 20

HL7 Field Name Accept Acknowledgment Type Application Acknowledgment Type Country Code Character Set Principal Language of Message Alternate Character Set Handling Scheme

Opt O O O O O O

Length 2 2 2 16 60 20

Data Type ID ID ID ID CE ID "AL"

Vision Series Data Mapping/ Comments

4.10.3 MSA (Message Acknowledgment Seg.) - ACK
The following table lists each Message Acknowledgement segment and their Seq, HL7 Field Name, Opt, Length, Data Type, Rejection Rules, and Mapping/Comments:
MSA Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments “AA” if Accepted (Original Mode) “AE” if Error (Original Mode) 1 Acknowledgment Code R 2 ID “AR” if Rejected (Original Mode) “CA” if Accepted (Enhanced Mode) “CE” if Error (Enhanced Mode) “CR” if Rejected (Enhanced Mode) 2 3 4 5 6 Message Control ID Text Message Expected Sequence Number Delayed Acknowledgment Type Error Condition R O O B O 20 80 15 1 100 ST ST NM ID CE The MSH_10 Message Control Number is echoed back to the placer Message Text

AMICAS, Inc. Proprietary and Confidential

131

The appointment information service segment contains information about various kinds of services that can be scheduled.0 HL7 Interface Guide Glossary Glossary Term ACC ACK Definition The accident segment contains patient information relative to an accident in which the patient has been involved. The kinds of personnel described on this segment include any healthcare provider in the institution controlled by a schedule (for example: technicians. Location resources are identified with this specific segment because of the specific encoding of locations used by the HL7 specification. Services included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application. An interface engine. anesthesiologists. American Standard Code for Information Interchange. Resources not controlled by a schedule are not identified on a schedule request using this segment. nurses. Services not controlled by a schedule are not identified on a schedule request using this segment. The disability segment contains information related to the disability of a person. or other locations) that can be scheduled. Discharge and Transfer messages contain information relating to patient demographics. ADT AE AIL AIP AIS ASCII BAR Broker DB1 AMICAS. or CRNAs). The appointment information personnel resource segment contains information about the personnel types that can be scheduled. Patient Account Balance Information message type. General Acknowledgment. Application Entity. surgeons. Proprietary and Confidential 132 . This segment was created instead of adding disability attributes to each segment that contains a person (to which disability may apply). examination rooms. The ACK message is used to respond to a message indicating receipt and status (either success or failure) by the receiving system. Personnel included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application. operating rooms. Resources included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application.Vision Series RIS 5. The appointment information location resource segment contains information about location resources (meeting rooms. Inc. physicians. Personnel not controlled by a schedule are not identified on a schedule request using this segment. Admission. This message type sends data from some application (usually a Registration or an ADT system) to the patient accounting or financial system to establish an account for a patient’s billing/accounts receivable record.

Flexibility is built into the protocol to allow compatibility for specialized data sets that have facilityspecific needs. Master File Entry segment. etc. The insurance segment contains additional insurance policy coverage and benefit information necessary for proper billing and reimbursement. A 3-character code contained within each message identifies its type.). This segment returns record-specific acknowledgement information. Inc. For example. Patient Merge Information segment. Master File Identification segment. The application receiving and processing an HL7 message. Proprietary and Confidential 133 . The HL7 protocol is a collection of standard formats which specify the implementation of interfaces between different computer applications from vendors. Information System. Lower Layer Protocol. The guarantor segment contains information on the person or the organization with financial responsibility for payment of a patient account. This segment sends patient demographics to the receiving system to initiate the merging of one patient’s data into another patient’s data. This segment carries the recordlevel event code (such as Add. entering the report in received in an ORU^R01into their application or creating a record or an order based on receipt of an ORM^O01. Master File Acknowledgment segment. as well as the initial and requested dates for file-level events such as Replace File. This message type provides a way of maintaining the synchronization of data across various applications at a given site.0 HL7 Interface Guide Glossary Term EVN Filler Definition Event Type segment. This communication protocol allows healthcare institutions to exchange key sets of data amount different application systems.Vision Series RIS 5. This segment identifies the master file being updated.e. Master Files Notification message type. This segment is used to communicate necessary trigger event information to receiving applications. the ADT Message Type is used to transmit portions of a patient’s demographic data from one system to another. i. Update.. Health Level Seven (HL7) is an application protocol for electronic data exchange in health care environments. GT1 HL7 IN1 IN2 IS LLP Message Type MFA MFE MFI MFN MRG AMICAS. the initial and requested dates for the event and the record-level key identifying the entry in the master file. Each message has a message type that defines its purpose. The insurance segment contains insurance policy coverage information relating to the patient and visit.

The function of this message is to initiate the transmission of information about an order. Unsolicited Transmission of an Observation. If the filler rejects the message for any reason. Multiple OBXs may be sent in an observation report. The filler will use this segment to send an acknowledgment of success or error to placer. destination and some specifics of the syntax of a message. discontinuation. it creates an ACK message with a MSA-1 Acknowledgement Code of AR. cancellation of existing orders. source.0 HL7 Interface Guide Glossary Term MSA Definition Message Acknowledgement segment. General Order Message. It is used to transmit fields that are common to all orders. An ORR message is the application acknowledgment to an ORM message. In the reporting of clinical data. the report message includes one OBR segment. It is used to transmit information specific to an order for a diagnostic study or observation.Vision Series RIS 5. All HL7 messages start with a MSH segment. OBX is intended to cover all types of patient specific observation reports except pharmacy. Inc. General Order Acknowledgment. It is used to carry information about observations in report messages and can also be part of an observation order. this segment serves as the report header. When observations are reported. Observation Request segment. A message control segment that defines the intent. This includes placing new orders. Observation/result message. holding. If an error occurs during processing. NTE OBR OBX ORC ORM ORR ORU AMICAS. Common Order segment. the filler generates a functional response message with an MSA-1 Acknowledgment Code of AA. It is the smallest inseparable unit of a report. etc. The function of this message is to respond to an ORM message. When a set of observations is ordered. This segment is used to transmit a single observation or part of an observation. For each patient order results may be transmitted depending upon the number of observations generated by the order. This segment is required in the ORM message. Proprietary and Confidential 134 . The ORC is a common segment for all orders.   MSH Message Header segment. the filler will send an error response providing a MSA-1 Acknowledgement Code of AE and an error message in MSA-3 Text Message. Some fields only apply to the ordering message and some only apply to the reporting message. Notes and comments segment.  If the message is processed successfully. the order message contains an OBR message.

The PR1 segment is used to send the procedures for medical records encoding or for billing systems. They may occur only once in a message or they may be allowed to repeat. or AIP). AIL. The application originating the HL7 message. Radiology Information System. The PR1 segment can be used to send procedure information. Segments of a message may be required or optional.e. i. and then follow that RGS with one or more of the Appointment Information segments (AIG. or to describe some other relationship between resources. etc. AIS. X-ray with contrast. This segment is used by all applications as the primary means of communicating patient identification information. begin each group with an RGS segment. This segment can be used. The PV2 segment is a continuation of visit-specific information contained on the PV1 segment. The schedule segment contains general information about the scheduled appointment. Transmission Control Protocol/Internet Protocol. An HL7 segment is a logical grouping of data fields. Patient Visit segment. Proprietary and Confidential 135 . Inc. Each segment is identified by a unique three character code known as the Segment ID.0 HL7 Interface Guide Glossary Term PID Definition Patient Identification segment. to identify groups of resources that are used together within a scheduled event. This segment is used to communicate information on an account or visit-specific basis. Schedule Information Unsolicited messages are used to send and receive schedule information regarding patient appointments. Placer PR1 PV1 PV2 RGS RIS SCH Segment SIU TCP/IP AMICAS. if a patient’s report is signed. The procedures segment contains information relative to various types of procedures that can be performed on a patient.Vision Series RIS 5. an ORU^R01 message is triggered to be sent to the defined filler(s). To specify related groups of resources within a message. It contains permanent patient identifying and demographic information. on a site specified basis. for example: Abdominal Ultrasound. The resource group segment is used to identify relationships between resources identified for a scheduled event.

Unique Identifier. For example. The real-world event is called the trigger event. UID AMICAS.0 HL7 Interface Guide Glossary Term Trigger Event Definition The event that initiates an exchange of messages is called a trigger event.Vision Series RIS 5. The same trigger event code may not be associated with more than one message type. the trigger event “a patient is scheduled” may cause the need for data about that patient to be sent to a number of other systems. The HL7 Standard is written from the assumption that an event in the real world of healthcare creates the need for data to flow among systems. Proprietary and Confidential 136 . There is a one-to-many relationship between message types and trigger event codes. Inc.

Vision Series RIS 5.S[S[S[S]]]]]]]][+/-ZZZZ] ^ <degree of precision> Coded element 250 <identifier (ST)> ^ <text (ST)> ^ <name of coding system (IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (IS)> <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ < assigning authority (HD)> ^ <identifier type code (ID)> ^ < assigning facility (HD) ^ <effective date (DT)> ^ <expiration date (DT)> CX Extended composite ID with check digit 250 AMICAS.0 HL7 Interface Guide Appendix A: Data Types Appendix A: Data Types Data Type Category Alphanumeric ST TX FT Numerical CQ NM SI Identifier ID IS HD EI Coded values for HL7 tables Coded value for userdefined tables Hierarchic designator Entity identifier <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)> <entity identifier (ST)> ^ <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)> <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ < location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)> <processing ID (ID)> ^ <processing mode (ID)> Composite quantity with units Numeric Sequence ID <quantity (NM)> ^ <units (CE)> String Text data Formatting text 199 65536 65536 Data Type Name Length Notes/Format PL PT Date/Time DT TS Code Values CE Person location Processing type Date Time stamp YYYY[MM[DD]] YYYY[MM[DD[HHMM[SS[. Proprietary and Confidential 137 . Inc.

<street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code (ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)> ^ <county/parish code (IS)> ^ <census tract (IS)> In Version 2..0 HL7 Interface Guide Appendix A: Data Types Data Type Category Data Type Name Length Notes/Format <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e. MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code (ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> XCN Extended Composite ID Number and Name 250 Generic CM Composite No new CMs are allowed after HL7 Version 2.g. JR or III) (ST)> ^ <prefix (e. [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)> XAD Extended address 250 XPN Extended person name 250 XON Extended composite name and ID number for organizations 250 XTN Extended telecommunications number 250 Time Series <quantity (CQ)> ^ <interval (*)> ^ <duration (*)> ^ <start date/time (TS)> ^ <end date/time (TS)> ^ <priority (ID)> ^ <condition (ST)> ^ <text (TX)> ^ <conjunction (ID)> ^ <order sequencing (*)> TQ Timing/quantity AMICAS..Vision Series RIS 5. DR) (ST)> ^ <degree (e. Inc. replaces the PN data type.2.g.g. Proprietary and Confidential 138 . replaces the AD data type.3 and later.. <family name (FN)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.3 and later..g.3. Demographics In Version 2. replaces the TN data type. MD) (IS)> ^ <name type code (ID) > <organization name (ST)> ^ <organization name type code (IS)> ^ <ID number (NM)> ^ <check digit (NM)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility ID (HD)> In Version 2. JR or III) (ST)> ^ <prefix (e. DR) (ST)> ^ <degree (e.g. The CM data type is maintained strictly for backward compatibility and may not be used for the definition of new fields...g.

Sign up to vote on this title
UsefulNot useful