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

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

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

as well as a guide for third-party systems to interface with Vision Series RIS.0 HL7 Interface Guide contains the procedures for configuring the HL7 component of the Vision Series RIS application. 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. AMICAS. Proprietary and Confidential v . Inc.0 HL7 Interface Guide Preface The Vision Series RIS 5.Vision Series RIS 5.

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

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

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

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

0 HL7 Interface Guide HL7 Support Tables – Definition 2.0 Administration Guide.Vision Series RIS 5. Inc. 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. see the Vision Series RIS 5. Proprietary and Confidential 5 . AMICAS.

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

Proprietary and Confidential 7 . <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. “P” Production Environment “2. Message unique identifier for the ADT message which will be Rejected if field is empty. Inc.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.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. Register or update a patient. echoed back in the MSA_2 of the acknowledgment message.Vision Series RIS 5.

HL7 Field Name. the data must be in the PID 2 field. this is rejected if the PID 2 and 3 fields are empty. “1” 1 Set ID . 3 Patient ID (Internal ID) R C 20 CX If the unique ID is not PMIS and this field is empty. Inc. Rejection Rules. Length. Patient SS Number <#########> Patient Name <last name^ first name^ middle name> Excess length will be truncated. Opt. The RIS Req column designates which fields are required by Vision Series RIS.0 HL7 Interface Guide Inbound Messages 3.ADT ^A01 .Patient ID O 4 SI If the unique ID is not PMIS.3 PID (Patient Identification Definition Segment) . 6 7 O O R XPN TS Rejected if field is empty and if not at least <yyyymmdd>. 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.Vision Series RIS 5.1. Data Type. 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.ADT^A08 The following table lists each Patient Identification Definition segment and their Seq. 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. 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. Proprietary and Confidential 8 .

Alphanumeric. reject if blank is used as the unique and PID 3 must be NULL ID. If the PMIS unique ID. guarantors and insureds.Home O 12 XTN 14 Phone Number . then PID_3 Jacket if you do not wish to Number must be modify the jacket. Country does not update.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. 18 Patient Account Number O C 20 CX AMICAS.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.Business O 12 XTN 15 Language . 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 . Inc. NULL on the inbound message if the patient jacket should not be changed. Proprietary and Confidential 9 . The patient PMIS must be unique to all patients.Vision Series RIS 5.

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.ADT^A08 The following table lists each Guarantor segment and their Seq.ADT ^A01 .Vision Series RIS 5. No validation is performed for length or duplicates. "1" Set ID . Data Type. Inc. HL7 Field Name. 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. The RIS Req column designates which fields are required by Vision Series RIS. Patient Date of Death <yyyymmdd> 3.GT1 R 4 AMICAS.Patient B 16 ST Rejected if not 9 sequential numbers.1. Rejection Rules. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. 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>. Proprietary and Confidential 10 . Length. 19 SSN Number .4 GT1 (Guarantor Segment) . Opt.

guarantors and insureds.Vision Series RIS 5. Inc.7 then it will be read from GT1-7. <yyyymmdd> Rejected if format is not at least <yyyymmdd>. 4 Guarantor Spouse Name O XPN 5 Guarantor Address O 151 total 60 40 40 2 9 XAD 6 Guarantor Ph Num . 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.. Suffix does not update. Guarantor Spouse Name Guarantor Address <address 1^ address 2^ city^ state (standard abbreviation only)^ zip (alphanumeric with no validation)> Excess length will be truncated.1 GT1-7. it will associate the patient as the guarantor. reject if blank.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. number must be unique to all patients.Home O 12 XTN 7 Guarantor Ph Num Business O C 12 XTN If not found in GT1-7. Proprietary and Confidential 11 . Guarantor Name <last name^ first name^ middle name> Excess length will be truncated. 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. Alphanumeric. The if the PMIS code does not guarantor PMIS match.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. Country does not update.

11 Guarantor Relationship O C 80 CE Rejected if the field is empty or if the relationship code does not match. Proprietary and Confidential 12 . Inc. “1” is the default. 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.Vision Series RIS 5. 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. 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. reject if blank. 10 Guarantor Type O 2 IS Required if GT1-3 is other than the patient. special characters.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. No validation is performed for length or duplicates.

Vision Series RIS 5. 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. Proprietary and Confidential 13 .) 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.

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

it will associate the patient as the insured. 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. Middle and Last are sent through standard charge out. the First. 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. Excess length will be truncated.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. Patient name is used if this field is left blank. Inc.Vision Series RIS 5. Proprietary and Confidential 15 . Though RIS only displays First and Last.

Inc.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. 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. 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. 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. Country does not update. 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.R.Vision Series RIS 5. Proprietary and Confidential 16 . reject if blank.

The insured PMIS number must be unique to all patients.Vision Series RIS 5. HL7 Field Name. reject configured to accept if blank. The RIS Req column designates which fields are required by Vision Series RIS.1. Rejection Rules. the Insured. Length. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. guarantors and insureds. Inc. Data Type.ADT ^A01 .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.6 IN2 (Insurance Segment) . Opt. 49 Insured’s ID Number O C 12 CX 3.ADT^A08 The following table lists each Insurance segment and their Seq. 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. Alphanumeric.0 HL7 Interface Guide Inbound Messages IN1 Seq 40 41 42 HL7 Field Name Room Rate . Proprietary and Confidential 17 .

reject <SS Number format if blank. #########> 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. Inc.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 18 .

Proprietary and Confidential 19 .Vision Series RIS 5.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. 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. Patients will be identified by using either the PMIS code or the Patient Jacket number. Patient Demographics will not be modified using a merge message. Proprietary and Confidential 20 .2 ADT^A34 or ADT^A40 – HL7 Message Merge Type 3.2. The following table lists each supported message segment and their description: Message Segment MSH Segment Description Message Header AMICAS.1 Message Definition These messages will allow the RIS to merge two patients.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. Inc. Contact Reason Insurance Co.Vision Series RIS 5.

Current date/time <yyyymmddhhmmss> Rejected if field is empty. Opt.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. The RIS Req column designates which fields are required by Vision Series RIS. 3. Length. Rejection Rules.3” HL7 version number Rejected if field is empty.Vision Series RIS 5. Proprietary and Confidential 21 . Data Type. Inc. <yyyymmddhhmmss> “P” “2.2. Rejected if field is empty. Rejection Rules Vision Series Data Mapping/ Comments "|" "^~\&" <Sending Application> <Sending Facility> <Receiving Application> AMICAS. 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” System date/time. Rejected if field is empty. 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. HL7 Field Name.2 MSH (Message Header Segment) – ADT^A34 or ADT^A40 The following table lists each Message Header segment and their Seq.

3 EVN (Event Type Segment) .Vision Series RIS 5. 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. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. “1” 1 2 Set ID . and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Opt. Data Type.0 HL7 Interface Guide Inbound Messages 20 Alternate Character Set Handling Scheme O 20 ID 3. Length. The RIS Req column designates which fields are required by Vision Series RIS. Proprietary and Confidential 22 . The RIS Req column designates which fields are required by Vision Series RIS. HL7 Field Name. Data Type. Rejection Rules. PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PID segment per message.2. HL7 Field Name.Patient ID Patient ID (External ID) O O 4 20 SI CX AMICAS.ADT^A34 or ADT^A40 The following table lists each Event Type segment and their Seq. Rejection Rules.2.ADT ^A34 or ADT^A40 The following table lists each Patient Identification Definition segment and their Seq. Opt.4 PID (Patient Identification Definition Segment) . Inc. Length.

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. SSN. O.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.Business O 12 XTN 15 16 17 Language . M. Proprietary and Confidential 23 . 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>. RIS Internal ID Patient Unique Identifier <Defined Unique ID> 3 Patient ID (Internal ID) R R 20 CX Rejected if field is empty. Patient Marital Status <PMIS code for Marital Status Code> AMICAS. Patient DOB <yyyymmdd> Patient Gender (F. 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 Ethnicity <PMIS code or ethnicity code> Patient Address <address 1^address 2^city^ state^zip^country> Country Code <Country field> Patient Home Phone. Rejected if the field is empty or if the gender code does not match this field.Patient Marital Status Religion O O O 60 80 80 CE IS IS Rejected if the martial status code does not match this field.Home O 40 XTN 14 Phone Number . Inc.Vision Series RIS 5. Fax. U) <PMIS code or gender code? Patient Alias <Alias field> Rejected if the race code does not match this field. Jacket.

Proprietary and Confidential 24 .Vision Series RIS 5. Opt. Rejection Rules.ADT^A34 or ADT^40 The following table lists each Patient Merge Information segment and their Seq. HL7 Field Name. Inc.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. Data Type.2. Patient Date of Death <yyyymmdd> 3.External O 20 CX 5 6 7 Prior Visit Number Prior Alternate Visit ID Prior Patient Name O O O 20 20 48 AMICAS. <Patient File PMIS> Rejected if not 9 sequential numbers. 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 . Length. Patient Social Security Number <#########> 19 SSN Number .Internal R 20 CX 2 Prior Alternate Patient ID O 20 CX 3 Prior Patient Account Number O 20 CX 4 Prior Patient ID .5 MRG (Patient Merge Information Segment) . reject if blank and PID 3 must be NULL.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>.

Proprietary and Confidential 25 . Data Type.3 onward. the P01 (add account) event should not longer be used for updating an existing account with financial information.Vision Series RIS 5. Rejected if not acceptable sending application. The RIS Req column designates which fields are required by Vision Series RIS.3.3. From Standard Version 2. 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.3 BAR^P05 – Billing Account Update Message Type 3. Update of the Patient Demographics will not be done from this message type. Opt.0 HL7 Interface Guide Inbound Messages 3. Rejection Rules. HL7 Field Name. An ADT message must be used to update the Patient Demographics.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.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 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. 3. Length. "|" Must always be "^~\&". 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. Inc.

Proprietary and Confidential 26 . Unique Message Identifier “P” “2. Data Type. “2.3 EVN (Event Type Segment) – BAR^P05 The following table lists each Event Type segment and their Seq. or <yymmddhhmmss> 8 Security O 40 ST Rejected if the value is not a defined message type (ORM^O01).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.2” or 2. Rejected if not “2.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. If it is a define message type. “2. Length.3”. Rejected if not “P”.1”.0”. Rejection Rules. Opt. 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. The RIS Req column designates which fields are required by Vision Series RIS.3. Rejected if field is empty.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. then the “BAR^P05” appropriate specification and logic will be applied to the message. HL7 Field Name. Inc.

Inc. Proprietary and Confidential 27 .Vision Series RIS 5.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.

Opt.Vision Series RIS 5. PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PID segment per message. PID 3. 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. AMICAS.3.1. the data must be in the PID 2 field. Rejection Rules.0 HL7 Interface Guide Inbound Messages 3. Inc. Length. Rejected if the field is empty or if the gender code does not match this field. HL7 Field Name. Proprietary and Confidential 28 .4 PID (Patient Identification Definition Segment) – BAR^P05 The following table lists each Patient Identification Definition segment and their Seq. Patient Jacket Number Patient Name <last name^ first name^ middle name> Excess length will be truncated. If the unique ID is not PMIS and this field is empty. 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. this is rejected if the PID 2 and 3 fields are empty. “1” 1 Set ID . Data Type. 6 7 X O XPN TS Rejected if field is empty and if not at least <yyyymmdd>. 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.Patient ID R 4 SI If the unique ID is not PMIS. 2 Patient ID (External ID) X C 20 CX Patient Unique Identifier <Internal Patient ID Number> Patient Internal ID from RIS.

<Patient File PMIS> Patient Social Security Number <#########> Numeric with no special characters. 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.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. reject if blank Identifier and PID 3 must be NULL.Vision Series RIS 5.Business O 12 XTN 15 Language . Proprietary and Confidential 29 . Country does not update. 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. 19 SSN Number . Inc.Patient X 60 CE Rejected if the martial status code does not match this field. No validation is performed for length or duplicates. 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 .Patient O 16 ST Rejected if not 9 sequential numbers.Home O 12 XTN 14 Phone Number .

Rejection Rules.Vision Series RIS 5. “1” Appointment Code.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>. PV1 Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PV1 Segment per message. 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. 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. 1 Set ID – PV1 O 4 SI 2 Patient Class O R 1 IS Reject if empty or the PMIS code does not match. Proprietary and Confidential 30 .5 PV1 (Patient Visit Segment) – BAR^P05 The following table lists each Patient Visit segment and their Seq. Data Type. Opt. HL7 Field Name. Displayed in RIS separated by a space colon (“ :”).3. Inc. Patient Date of Death <yyyymmdd> 3. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Length. The RIS Req column designates which fields are required by Vision Series RIS.

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. 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. A tilde (~) separates referring from any/all cc physicians. Proprietary and Confidential 31 . <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.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.

Proprietary and Confidential 32 .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. Inc.Vision Series RIS 5.

transmits update information to other systems (usually to the "owning" system). workstations.0 HL7 Interface Guide Inbound Messages 3. adds. deletes.4. updates) to this file are made available to various other applications on a routine basis.Vision Series RIS 5. 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. terminals. as well as providing for a delayed application acknowledgment mode.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. and the recordlevel key identifying the entry in the master file. These files are called master files. etc. printers. The changes (e. 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 Master File Entry (MFE) segment carries the record-level event code (such as add. Inc. Proprietary and Confidential 33 . 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.) 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.g.g. etc. For each record being changed.. In many implementations.4 MFN . update. The MFN message supports the distribution of changes to various master files between systems in either online or batch modes. The Master File Acknowledgment (MFA) segment returns record-specific acknowledgment information. AMICAS.Master File Update Message Type 3.). one application system will "own" a particular master file such as the staff and practitioner master file. The MFN message supports this common case. but also supports the situation where an application not "owning" a particular master file. These messages use the MSH segment to pass the basic event code (master files notification or acknowledgment).. and allows the use of either original or enhanced acknowledgment modes. 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. the initial and requested dates for the event. for review and possible inclusion.

Rejected if field is empty. “2.0 HL7 Interface Guide Inbound Messages 3. then the appropriate specification and logic will be applied to the message. 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”.4.2” or 2. “2. Opt.Vision Series RIS 5. The RIS Req column designates which fields are required by Vision Series RIS. Length.2 MSH (Message Header Segment) – MFN The following table lists each Message Header segment and their Seq. Must always be "^~\&". "|" 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. 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 "|". and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Inc. Rejection Rules. Proprietary and Confidential 34 . HL7 Field Name. “2.3”.0”. If it is a define message type.3” HL7 version number AMICAS.1”. 8 Security O 40 ST Rejected if the value is not a defined message type (ORM^O01). Data Type. “P” or “T” Rejected if not “2. Rejected if not acceptable sending application.

The RIS Req column designates which fields are required by Vision Series RIS. Proprietary and Confidential 35 . Inc.4. HL7 Field Name. Length.Vision Series RIS 5. 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. Data Type. 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. a. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Rejection Rules. 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. Opt.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.3 MFI (Message File Identification Segment) – MFN The following table lists each Message Header segment and their Seq.

The RIS Req column designates which fields are required by Vision Series RIS. Proprietary and Confidential 36 . Opt.4. MDC. Rejection Rules. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. 3.Vision Series RIS 5. HL7 Field Name. Data Type.4 MFE (Message File Entry Segment) – MFN The following table lists each Message Header segment and their Seq. <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. MUP.MAC Note: See HL7 Table: Actions Performed on Master Files. MFE Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments MAD. Length.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. MDL. Inc.

5 ZL7 (Insurance Data to Post Segment) – MFN The following table lists each Message Header segment and their Seq. 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.4. 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. Delete the record from the master file. but do not delete it from the database. Data Type. 4 Primary Key Value – MFE R 200 Varies a. Opt. Deactivate. Proprietary and Confidential 37 . MAC 3. Discontinue using the record in the master file. The RIS Req column designates which fields are required by Vision Series RIS. Inc. HL7 Field Name. DX and ZIP use Code all others use the PMIS Code.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. Reactivate the deactivated record. Rejection Rules.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. Length.

cancellations. HL7 Field Name.1 Message Definition Per HL7. etc. Data Type. Inc. 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. "|" Must always be "^~\&".0 HL7 Interface Guide Inbound Messages 3. Rejection Rules. discontinuing orders.2 MSH (Message Header Segment) – ORM^O01 The following table lists each Message Header segment and their Seq.5. patient and non-patient specific orders. canceling existing orders. Such changes include submission of new orders. the function of this message is to initiate the transmission of information about an order. Rejected if not acceptable sending application. 3.5 ORM^O01 – Order Message Type 3. 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.5. Length. holding orders. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. 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 "|". Proprietary and Confidential 38 . 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. etc. This includes placing new orders.Vision Series RIS 5. Opt.

“2. Length. If it is a define message type. Proprietary and Confidential 39 .3 PID (Patient Identification Definition Segment) .5. Opt. Rejected if not “P” or “T”.3”.1”.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.2” or 2. Rejected if field is empty.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.0”. Rejection Rules. AMICAS. Unique Message Identifier “P” or “T” “2. “2. Inc.ORM^O01 The following table lists each Patient Identification Definition segment and their Seq. or <yymmddhhmmss> 8 Security O 40 ST Rejected if the value is not a defined message type (ORM^O01). then the “ORM^O01” appropriate specification and logic will be applied to the message.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. HL7 Field Name. Rejected if not “2. Data Type. The RIS Req column designates which fields are required by Vision Series RIS.

Proprietary and Confidential 40 . MSA1 = [ACK Code]. Rejected if the gender code does not match.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”.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. not formatted correctly or the suffix code does not match.Patient ID O R 4 SI 2 Patient ID (External ID) B 20 CX Reject if empty. MSA6 = [Field] [Field Name] [error] Vision Series Data Mapping/ Comments One PID segment per message.Vision Series RIS 5. 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. MSA1 = [ACK Code]. MSA1 = [ACK Code]. Inc. MSA6 = [Field] [Field Name] [error] Reject if empty. MSA6 = [Field] [Field Name] [error] Reject if not formatted correctly. 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]. 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. Ethnicity support table) Patient Address <address 1^ address 2^ city^ state (standard abbreviation only)^ zip (alphanumeric with no validation) Excess length will be truncated. “1” 1 Set ID .

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.Vision Series RIS 5. guarantors and insureds. Alphanumeric.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. The patient PMIS must be unique to all patients.Patient B C 16 ST Rejected if formatted correctly. Proprietary and Confidential 41 . MSA1 = [ACK Code]. Inc. Patient Social Security Number <nnnnnnnnn> or <nnn-nnn-nnn> Numeric with no special characters.Business O 250 XTN 15 Language . then PID_3 Jacket Number must be NULL on the inbound message. If the PMIS is used as the unique ID. No validation is performed for length or duplicates. MSA1 = [ACK Code]. MSA6 = [Field] [Field Name] [error] 19 SSN Number .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 . 18 Patient Account Number O C 250 CX Rejected if not formatted correctly. MSA6 = [Field] [Field Name] [error] AMICAS.Home O 250 XTN 14 Phone Number .

If the PV1 segment is missing.Vision Series RIS 5. Rejection Rules. then Global Service Type will be selected by default. Data Type. “1” Patient type. Length. The RIS Req column designates which fields are required by Vision Series RIS.4 PV1 (Patient Visit Segment) – ORM^O01 The following table lists each Patient Visit segment and their Seq. Opt. AMICAS.5. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Inc.16 will be used for the referring physician. PV1 Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PV1 Segment per message. the value in OBR.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. 1 Set ID – PV1 O 4 SI 2 Patient Class R R 1 IS Reject if empty or the PMIS code does not match. Proprietary and Confidential 42 . for example: E = Emergency Room O = Outpatient I = Inpatient If PV1 is not included. HL7 Field Name.

Physician matching will occur only on PMIS. PMIS Code or Physician Location If the PV1 segment has a Unique Identifier ^Last Name^First^ value for PV1. The first name is also required if RIS creates the physician record from the message.7 and Physician Location PV1. Inc. 8 Referring Doctor O R 60 XCN AMICAS. Proprietary and Confidential 43 . PV1.7 will be Unique Identifier ^Last used as the referring Name^First^ physician and PV1. If the PV1 segment is not found then the value in OBR16 will be used as the referring physician.Vision Series RIS 5.8. If the PV1 First Name^Middle segment is not found Name^Suffix> then the value in OBR16 will be used as the referring physician.7 and Middle Name^Suffix^ PV1. Physician Referring (cc) Provider matching will occur only <Physician Location on PMIS. A Tilde (~) separates reffering from any/all cc physicians. Reject if the PMIS or Last Name empty. PV1.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. Displayed in RIS separated by a space colon (“ :”).8 will First Name^Middle Name^Suffix> be used as the CC 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. <Physician Location If the PV1 segment has PMIS Code or a value for PV1.8. The first name is also required if RIS creates the physician record from the message.7 will be ~PMIS^Last Name^ used as the referring physician and PV1. 7 Attending Doctor O R 60 XCN Attending (referring) Provider.8 will Middle Name^Suffix^ be used as the CC ~PMIS^Last Name^ physician.

PV1-9 will be used as the CC physician. Inc.Vision Series RIS 5. Proprietary and Confidential 44 . Service Type <PMIS Code for Service Type Code> Visit Number will populate the Order Number field. Physician matching will occur only on PMIS. The first name is also required if RIS creates the physician record from the message. 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. 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.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.

Length. HL7 Field Name. Data Type. The RIS Req column designates which fields are required by Vision Series RIS.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. Proprietary and Confidential 45 .5 NTE (Notes and Comments Segment) – ORM^O01 The following table lists each Patient Visit segment and their Seq. Inc. “1” <comment text> NTE following the PID will be a Patient comment.5. Location to schedule the exam. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Rejection Rules. NTE Seq HL7 Field Name Opt Req by RIS Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PV1 Segment per message. <^^^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.Vision Series RIS 5. 1 Set ID – OBR O 4 SI 3 Comment 64k FT AMICAS. Opt.

Proprietary and Confidential 46 . Inc. 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. HL7 Field Name.0 HL7 Interface Guide Inbound Messages 3.ORM^O01 The following table lists each Common Order segment and their Seq. Length.5. 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. Rejection Rules. Opt.Vision Series RIS 5.6 ORC (Common Order Segment) . Data Type.

if no openings. Schedules in the first available resource.Vision Series RIS 5. Proprietary and Confidential 47 . 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 – 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. if no openings. This is for information purposes only. Schedules in the first available resource. it will force the appointment to a resource. it will force the appointment to a resource. Inc. 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.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. Always force the appointment . if no openings.this will not show in the appointment book since the procedure was not performed at the location. 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. if no openings.

otherwise NACK with error message order must be canceled. then if we continue sending this status. order must be at a schedule status. HIS will return an ORR^O02 with ORC-1 = NA. 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 OBR-3 = accession #. Rejection Rules.7 OBR (Observation Request Segment) – ORM^O01 The following table lists each Observation Request segment and their Seq. HL7 Field Name. Data Type. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Proprietary and Confidential 48 .5. And patient account number Logic: An order created in RIS will send an ORM^001 with ORC-1 = SN. 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.3 will have the RIS accession number 3. then sending an XO/XO will take it to the next step which will be checkin. OBR-2 has order number and OBR.Vision Series RIS 5. 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. if order is at the status of schedule. the order will move through the RIS workflow. checkin or inProcess. sending this will move it to checkin This will only update orders that are configured to automatically schedule. checkout This will only update orders that are configured to automatically schedule. Inc. The RIS Req column designates which fields are required by Vision Series RIS. this message will be seen in the monitor. Length. 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. Inprocess. order must be at either schedule. OBR2 is blank. O 4 AMICAS. Opt. otherwise NACK with error message order must be canceled this message will be seen in the monitor.

Vision Series RIS 5. this can be followed by two carets (^^) to include a modifier.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. 4. 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. <yyyymmddhhmmss> or <yyyy^mm^dd^hh^mm^ss> 7 Observation Date/Time C 26 TS Rejected if not formatted correctly.1 = Code 4. 5 6 Priority Requested Date/Time B B O 2 26 ID TS Date/time the order was started.3 = Modifier 4 Universal Service ID identifier text R R 250 CE Rejected if field is empty or code does not match. Inc. Proprietary and Confidential 49 . 8 9 10 11 12 13 14 Obs End Date/Time Collection Volume Collector Identifier Specimen Action Code Danger Code Relevant Clinical Info.2 = Description 4. 3 Filler Order Number C 22 EI <exam being ordered or canceled> Optionally. 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> 23 O 40 CM AMICAS. Tilde (~) separates referring from any or all CC physicians.7 and PMIS ^ Last Name ^ First Name ^ Middle Name ^ PV1. Placer Field 1 Placer Field 2 Filler Field 1 Filler Field 2 Result Rpt/Status Change . Inc. Vision Series Data Mapping/ Comments Ordering (referring) provider. A definable field that the filling (RIS) system can use. Proprietary and Confidential 50 . <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.8 will be used as the CC physician.Vision Series RIS 5. If the PV1 segment is not found then the value in OBR-16 will be used as the referring physician.Date/Time Charge To Practice O 40 XTN A definable field that the placing (ordering) system can use. PV1.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. Physician matching will occur only on PMIS.8. 17 Order Callback Phone No. The first name is also required if RIS creates the physician record from the message. 18 19 20 21 O O O O 60 60 60 60 ST ST ST ST Rejected if not formatted correctly.7 will be Suffix ^> used as the referring physician and PV1. 22 C O 26 TS Date/time of order or status change.

32 Principal Result Interpreter Assistant Result Interpreter O R 200 CM Reject if empty or if PMIS codes does not match. F or A. Note that. “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. in a multiple OBR segment. only one appointment reason is allowed per order.Vision Series RIS 5. Inc. 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. then try to match. If not match. use the reason text in the Other Reason field. Rejected if not P. <quantity ^ ^ ^ start_date/time ^ end_date/time ^ priority> Priority = S (STAT) or A (ASAP) will se the urgent flag otherwise normal priority. R (Routine).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. start and end date/time and priority. 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. 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. Proprietary and Confidential 51 .

HL7 Field Name. The RIS Req column designates which fields are required by Vision Series RIS.Vision Series RIS 5.8 OBX (Observation Result Segment) . Likely to be combined with OBX – 5. Inc. Data Type. Rejection Rules.5. Schedule date/time of the exam. 1 Set ID – OBR O 4 SI 2 Value Type C 3 ID Treated as a lead in to an order comment. Length. 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 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. 3 Observation Identifier R 80 CE 4 Observation Sub-ID C 20 ST AMICAS.ORM^O01 The following table lists each Observation/Result segment and their Seq. Proprietary and Confidential 52 . 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. Opt. <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.

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. Inc. 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.6 ORR^O02 .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. In ORR the PID and ORC segments are optional.General Order Acknowledgment Message Type 3. will concatenate with OBX-3. If OBX-3 is sent.Vision Series RIS 5. AMICAS. ORC segments are always required in ORR when an order detail segment is present.1 Message Definition The function of this message is to respond to an ORM message. particularly in case of an error response. For example. An ORR message is the application acknowledgment to an ORM message. Proprietary and Confidential 53 . However.6. a response ORR might include only the MSH and MSA.

The RIS Req column designates which fields are required by Vision Series RIS. Data Type. Length. Length.2 MSA (Message Acknowledgment Segment) – ORR^O02 The following table lists each Observation/Result segment and their Seq. 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. Rejection Rules.ORR^O02 The following table lists each Message Header segment and their Seq.6. "|" 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. MSA Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules If the code is not AA then no updates will occur. Opt. HL7 Field Name.Vision Series RIS 5. Data Type. Proprietary and Confidential 54 . and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections.6. Must always be "^~\&". Opt. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Inc. Rejection Rules. The RIS Req column designates which fields are required by Vision Series RIS. 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 "|".3 MSH (Message Header Segment) .0 HL7 Interface Guide Inbound Messages 3. HL7 Field Name. Rejected if not acceptable sending application.

Opt. 8 Security O 40 ST Rejected if the value is not a defined message type (ORM^O01).Vision Series RIS 5. HL7 Field Name. Length. Data Type.1”. “ORM^O01” then the appropriate specification and logic will be applied to the message.0”.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. AMICAS.ORR^O02 The following table lists each Common Order segment and their Seq. 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. NA is the only valid code. Proprietary and Confidential 55 .6. “2.3”. Unique Message Identifier “P” or “T” “2. Rejected if not “P” or “T”.4 ORC (Common Order Segment) . “2. NA =Number Assigned 1 Order Control R R 2 ID Rejected if not a valid code. Rejected if field is empty. Rejected if not “2. Rejection Rules.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” or 2. Inc. If it is a define message type.

Accession number.Vision Series RIS 5. 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.Results Message Type 3.7 ORU^R01 . Proprietary and Confidential 56 .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.3 for electronic data exchange. version 2. Length.5 PID (Patient Identification Definition Segment) – ORR^O02 The following table lists each Patient Identification Definition segment and their Seq. The AMICAS interface will be a one-way (unidirectional) data transfer. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Placer Order Number Filler Order Number C C 22 16 Rejected if empty. Inc.7.6. AMICAS. Rejected if empty. Patient ID (Internal ID) Patient Name Patient Account Number R R O R 22 90 22 3. Patient Account Number. Opt. Rejection Rules Vision Series Data Mapping/ Comments Patient Internal ID. Message received shall conform to the Health Level Seven (HL7) Standard. Data Type. The Patient MRN. Jacket. 3. PID Seq 3 5 18 HL7 Field Name Opt RIS Req Length Data Type CX XPN CX Rejected if empty. Rejection Rules. HL7 Field Name.1 Message Definition Vision Series RIS will receive the patient message event type ORU^R01 which will create or update patient reports. The RIS Req column designates which fields are required by Vision Series RIS. etc Patient Name.

<Receiving Application> R 26 40 Rejected if field is empty. The RIS Req column designates which fields are required by Vision Series RIS. 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. Length. 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.7. Opt. <Sending Application> <Sending Facility> R 180 180 Rejected if field is empty. “ORU^R01” Unique Message Identifier “P” “2. Proprietary and Confidential 57 .ORU^R01 The following table lists each Message Header segment and their Seq.0 HL7 Interface Guide Inbound Messages 3.3” HL7 version number AMICAS. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Data Type.2 MSH (Message Header Segment) . Rejected if field is empty. HL7 Field Name. Inc.Vision Series RIS 5.

then reject. HL7 Field Name. If PID 2 is empty or does not match. 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>. Data Type. Rejection Rules. 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.ORU^R01 The following table lists each Patient Identification Definition segment and their Seq. Inc. Opt. Rejected if the field is empty or if the gender code does not match this field. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. 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.Patient ID Patient ID (External ID) O B 4 20 SI CX Rejected if PID 3 does not match this field. PID Seq HL7 Field Name Opt RIS Req Length Data Type Rejection Rules Vision Series Data Mapping/ Comments One PID segment per message.3 PID (Patient Identification Definition Segment) . “1” 1 2 Set ID .0 HL7 Interface Guide Inbound Messages 3. The RIS Req column designates which fields are required by Vision Series RIS.7. If this field is empty then refer to PID 2. Proprietary and Confidential 58 . Length.Vision Series RIS 5.

Patient B 16 ST Rejected if not 9 sequential numbers.Home O 12 XTN 14 Phone Number Business Language . AMICAS. Alphanumeric. If the PMIS is used as the unique ID. The patient PMIS must be unique to all patients. reject if blank and PID 3 must be NULL.Vision Series RIS 5. Inc. guarantors and insureds. Patient Social Security Number <#########> Numeric with no special characters. 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. Proprietary and Confidential 59 . Country does not update. 18 Patient Account Number O C 20 CX If the PMIS is used as the unique ID. then PID_3 Jacket Number must be NULL on the inbound message. 19 SSN Number .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. No validation is performed for length or duplicates. 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 .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.

7. Proprietary and Confidential 60 . Rejection Rules.Vision Series RIS 5. Patient Date of Death <yyyymmdd> 3. Inc.4 OBR (Observation Request Segment) .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>. HL7 Field Name. Accession Number <Accession Number> AMICAS. The RIS Req column designates which fields are required by Vision Series RIS. 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. Data Type. Length. Opt.ORU^R01 The following table lists each Observation Request 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.

Tilde (~) separates referring from any or all CC physicians.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. biopsy If 13. the current date will serve as the approval date.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. O 300 ST Updates information for mammography procedures. 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 ^ . Bi-rad PMIS^ N (New) C (Compare Film) F (Need Film)^ Recall PMIS code If an invalid date is applied.PMIS ^ Last Name ^ First Name ^ Middle Name ^ Suffix ^> 16 O 80 XCN 17 18 19 20 21 22 23 Order Callback Phone No.Vision Series RIS 5. The assessment. Placer Field 1 Placer Field 2 Filler Field 1 Filler Field 2 Result Rpt/Status Change . default to N. If 13. Inc.2 is associated with the not populated it will report. Proprietary and Confidential 61 .3 is for the patient's required and the mammography message will be procedure(s) rejected.1 has a value and recall flags are set then 13. 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.

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. 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.Vision Series RIS 5. F or A. Inc. Proprietary and Confidential 62 . “A” for Addendum the report will be placed on hold.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. “P” for Preliminary If it is an A or a P “F” for Final and OBX 11 is an S.

HL7 Field Name. 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.ORU^R01 The following table lists each Observation/Result segment and their Seq. “S” Partial Results OBR 25 must be a P or an A. The RIS Req column designates which fields are required by Vision Series RIS. Rejection Rules. Proprietary and Confidential 63 . 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”. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Data Type. Also reject if this field does not coincide “P” Preliminary with OBR 25. 1 Set ID . Length. “F” Final If OBX 11 is an S. Inc.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.Vision Series RIS 5.7.5 OBX (Observation/Result Segment) . 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. Tildes (~) and carats (^) are recognized as carriage returns. 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”.0 HL7 Interface Guide Inbound Messages 3. Opt.

ACK The following table lists each Message Header segment and their Seq. 3.8.3” HL7 version number AMICAS. HL7 Field Name. If validation fails.8. ACK is sent from Vision Series RIS with a success or error message via the interface.1 Definition The HL7 Acknowledgment Message Type. the message will be sent to a process which will update the database and Vision Series RIS will generate a functional response message. If validation does not fail.2 MSH (Message Header Segment) . 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. Vision Series RIS will send an error response. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. If an error occurs during processing. Proprietary and Confidential 64 . The RIS Req column designates which fields are required by Vision Series RIS.Vision Series RIS 5. Length. If it processes correctly. Rejection Rules.0 HL7 Interface Guide Inbound Messages 3. Opt. Vision Series RIS will send a successful response. a reject message is constructed and returned to the placer. it will validate the message syntactically. Data Type.8 ACK – Acknowledgment Message Type 3. 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. When Vision Series RIS receives an HL7 message. Inc.

Opt. MSH_10. 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.ACK The following table lists each Observation/Result segment and their Seq. Proprietary and Confidential 65 . Length.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. 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. HL7 Field Name.Vision Series RIS 5.3 MSA (Message Acknowledgment Segment) . 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. Inc. otherwise this will contain text. Data Type.8. If MSA_1 is AA this field will be empty.

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

Patient File and/or Patient History      New orders (O01) sent for added procedures or visits. cancel orders (O01) are sent for each cancelled or deleted procedure. Change orders (O01) sent for changed procedures. Completed orders (O01) added for outside reads. 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.Vision Series RIS 5.  Cancel orders (O01) sent on deleted procedures. Inc. Proprietary and Confidential 67 . cancel orders AMICAS. Tech Entry  Change orders (O01) sent when all procedures are started on the same exam. Cancel orders (O01) sent at time of canceling visits. Merge patient (A34) sent when merge occurs. Reschedule orders (O01) will send cancel message followed by new order message. Completed orders (O01) added check-in films.  Patient Information Update (A08) sent for demographic registration data change.  New orders (O01) sent for added procedures. If the interface is configured for Multi-OBR.  Completed orders (O01) sent for procedures in a Check Out status.  New orders (O01) sent for added procedures/exams. Results sent for approved reports or addendums. Patient Information Update (A08) sent for demographic registration data change. If the interface is configured for Multi-OBR.  Change orders (O01) sent for changed procedures/exams. new orders (O01) are sent for each for each added exam.  Cancel orders (O01) sent on canceled procedures/exams.  New orders (O01) sent at the time patient checks-in if schedule trigger is not set. Cancel orders (O01) sent on canceled procedures. Patient Information Update (O01) sent for changes to demographic registration data.  Completed orders (O01) sent for procedures in an Ended status.  If the interface is configured for Multi-OBR set for the Exam level. If the interface is not configured for Multi-OBR. new orders (O01) are sent for each added procedure.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. otherwise a change order is sent when the patient is checked-in. If the interface is not configured for Multi-OBR. Results (R01) sent for preliminary reports or addendums. cancel orders (O01) are sent for each cancelled or deleted exam.

2 MSH (Message Header Segment) . HL7 Field Name. cancel orders (O01) are sent for each cancelled procedure. but it can also be used for demographic information only. The A08 event can include information specific to an episode of care. Proprietary and Confidential 68 .3.  If the interface is configured for Multi-OBR set to the Visit level. 4. 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.3 ADT^A08 – Update Patient Information 4. Inc. Length.3. 4. This trigger event is used when any patient information has changed when no other trigger event has occurred. Rejection Rules.ADT^A08 The following table lists each Message Header segment and their Seq. Data Type.0 HL7 Interface Guide Outbound Messages Workflow/ Workflow Event Trigger Event (O01) are sent for each cancelled exam. 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.Vision Series RIS 5. Opt. Do not send any guarantor or insured updates.1 Definition Vision Series RIS shall send the patient message event type ADT^A08 which will update patient information.

Data Type.3 PID (Patient Identification Definition Segment) .Vision Series RIS 5. Rejection Rules.Patient ID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID segment per message.ADT^A08 The following table lists each Patient Identification Definition segment and their Seq. Proprietary and Confidential 69 .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. “1” Patient Unique Identifier <Internal Patient ID Number> Patient Unique Identifier 3 Patient ID (Internal ID) R 20 CX <Internal Generated Patient ID. Length. PMIS or Social Security> Patient Unique Identifier <Jacket. Opt. HL7 Field Name.3. 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. and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID . Inc.

M.Patient Driver’s Lic Num . Inc.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.Date portion only <yyyymmdd> Patient Gender (F. 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.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 .Vision Series RIS 5.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 . Email 13 Phone Number . O. Proprietary and Confidential 70 .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 . Fax.

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.3. HL7 Field Name. Proprietary and Confidential 71 . Rejection Rules. Inc.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. “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.ADT^A08 The following table lists each Patient Visit segment and their Seq. Length.Vision Series RIS 5. Opt.4 PV1 (Patient Visit Segment) . Data Type.

Inc. 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.Vision Series RIS 5.

An A34 event is used to signal a merge of records for a patient that was incorrectly created under two different identifiers.4.4. 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. 4. 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. Proprietary and Confidential 73 .1 Definition Vision Series RIS shall send the patient message event type ADT^A34 which will merge patient information.4 ADT^A34 – Merge Patient Information (Patient ID Only) 4.Vision Series RIS 5.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. This merge is done to change patient identifiers on all of the patient’s incorrect accounts. Length.2 MSH (Message Header Segment) . Data Type. Opt.ADT^A34 The following table lists each Message Header segment and their Seq. Rejection Rules.

Proprietary and Confidential 74 . Rejection Rules. Opt.3 EVN (Event Type Segment) . Data Type. Inc.Vision Series RIS 5.4.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. Length. HL7 Field Name. 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.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.

Opt.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. Length. HL7 Field Name. Proprietary and Confidential 75 . 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.ADT^A34 The following table lists each Patient Identification Definition segment and their Seq. O.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. and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID . Rejection Rules. Data Type.Date portion only <yyyymmdd> Patient Gender (F. “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.Patient ID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID segment per message.Vision Series RIS 5.4. Inc.4 PID (Patient Identification Definition Segment) .

Email 13 Phone Number . Opt.Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 16 17 18 Language . and Mapping/Comments: AMICAS. Data Type.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. Inc. Fax.Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number .Patient Driver’s Lic Num .Vision Series RIS 5.ADT^A34 The following table lists each Patient Merge Information segment and their Seq.4.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.5 MRG (Patient Merge Information Segment) . Length. HL7 Field Name. Proprietary and Confidential 76 . Rejection Rules.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 .

The MFN message supports this common case.) 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 Master Files Notification (MFN) message provides a way of maintaining this synchronization by specifying a standard for the transmission of this data between applications.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. but also supports the situation where an application not "owning" a particular master file.Vision Series RIS 5. etc. Proprietary and Confidential 77 . AMICAS.g. These files are called master files.5. terminals. transmits update information to other systems (usually to the "owning" system).Master File Update Message Type 4.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 .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 .5 MFN . one application system will "own" a particular master file such as the staff and practitioner master file. Inc. updates) to this file are made available to various other applications on a routine basis.g. In many implementations..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. workstations. The changes (e. deletes. for review and possible inclusion. adds. 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.

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. 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). Opt. The RIS Req column designates which fields are required by Vision Series RIS. Proprietary and Confidential 78 . Inc. Length.2 MSH (Message Header Segment) – MFN The following table lists each Message Header segment and their Seq.5. Data Type. and allows the use of either original or enhanced acknowledgment modes. the Master File Entry (MFE) segment carries the record-level event code (such as add. Rejection Rules. the initial and requested dates for the event.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. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. as well as providing for a delayed application acknowledgment mode. The Master File Acknowledgment (MFA) segment returns record-specific acknowledgment information. HL7 Field Name. 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. For each record being changed. update. etc. 4. These messages use the MSH segment to pass the basic event code (master files notification or acknowledgment).Vision Series RIS 5.). and the recordlevel key identifying the entry in the master file.

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. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. a. The RIS Req column designates which fields are required by Vision Series RIS.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.Vision Series RIS 5. Rejection Rules.3 MFI (Message File Identification Segment) – MFN The following table lists each Message Header segment and their Seq.5. Length. 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. Opt. Inc. Proprietary and Confidential 79 . HL7 Field Name.3” HL7 version number 4. Data Type. 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.

Vision Series RIS 5.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. HL7 Field Name. Length. Opt. Proprietary and Confidential 80 . <yyyymmddhhmmss> <yyyymmddhhmmss> AMICAS. Inc. Rejection Rules. MAC Note: See HL7 Table: Actions Performed on Master Files. 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. MDC.4 MFE (Message File Entry Segment) – MFN The following table lists each Message Header segment and their Seq. The RIS Req column designates which fields are required by Vision Series RIS. 4.5. MUP. Data Type. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. MDL.

1 Definition Vision Series RIS sends the order message event type ORM^O01 which contains patient orders.5 ZL7 (Insurance Data to Post Segment) – MFN The following table lists each Message Header segment and their Seq. Proprietary and Confidential 81 .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. Rejection Rules.5. DX and ZIP use Code all others use the PMIS Code. Delete the record from the master file. Opt. MAC 4. 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 function of this message is to initiate the transmission of information about an order. a. HL7 Table: Actions Performed on Master Files Value MAD MDL MUP MDC Description Add the record to the master file. HL7 Field Name. Reactivate the deactivated record. Supported order messages include the Common Order Segment (ORC) and the Observation Request Segment (OBR). Inc. Length.Vision Series RIS 5. Data Type. Orders are associated with a particular patient and usually contain a set of one or more procedures to be performed on a patient. Deactivate. but do not delete it from the database. Update the record for the master file. and Mapping/Comments: Any field name that has a blank cell in the Rejection Rules column does not have any rejections. Discontinue using the record in the master file. AMICAS.6. The RIS Req column designates which fields are required by Vision Series RIS.6 ORM^O01 – Order Message Type 4.

Length.ORM^O01 The following table lists each Message Header segment and their Seq. Data Type. 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.2 MSH (Message Header Segment) .Vision Series RIS 5. HL7 Field Name. Opt. Proprietary and Confidential 82 . Rejection Rules.3” HL7 version number Current date/time <yyyymmddhhmmss> "|" "^~\&" ”Vision SeriesRIS” <Corporation Name> “PACS” Vision Series Data Mapping/ Comments 16 O 2 ID "NE" AMICAS. 4.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.

Vision Series RIS 5.6.Patient ID Opt O Length 4 Data Type SI Vision Series Data Mapping/ Comments One PID segment per message.3 PID (Patient Identification Definition Segment) . 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 . PMIS or Social Security> Patient Unique Identifier <Jacket. Proprietary and Confidential 83 . and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID . Jacket.ORM^O01 The following table lists each Patient Identification Definition segment and their Seq.Date portion only (YYYYMMDD) Patient Gender (F.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. “1” Patient Unique Identifier <Internal Patient ID Number> Patient Unique Identifier 3 Patient ID (Internal ID) R 20 CX <Internal Generated Patient ID. O. Data Type. 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. Inc. HL7 Field Name. Length. Opt. M. Rejection Rules.

Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 16 17 18 Language . Proprietary and Confidential 84 . Opt. Inc.4 PV1 (Patient Visit Segment) . Rejection Rules.Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number . HL7 Field Name.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. “1” AMICAS.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 . Email 13 Phone Number .ORM^O01 The following table lists each Patient Visit segment and their Seq.Vision Series RIS 5.Patient Driver’s Lic Num .0 HL7 Interface Guide Outbound Messages PID Seq HL7 Field Name Opt Length Data Type Vision Series Data Mapping/ Comments Patient Home Phone. 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. Data Type.6. Fax. Length.

Proprietary and Confidential 85 . Inc.Vision Series RIS 5.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.

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.Vision Series RIS 5. Inc. Proprietary and Confidential 86 .

Vision Series RIS 5. HL7 Field Name. Data Type. Length.5 ORC (Common Order Segment) . Inc.0 HL7 Interface Guide Outbound Messages 4.6. Rejection Rules. Proprietary and Confidential 87 . 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. 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.ORM^O01 The following table lists each Common Order segment and their Seq. Opt.

Proprietary and Confidential 88 . Opt. Length. HL7 Field Name.Vision Series RIS 5. 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.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.ORM^O01 The following table lists each Order Detail/Observation Request segment and their Seq. Inc.6 OBR (Order Detail /Observation Request) . Data Type. Rejection Rules.6.

O 40 XTN AMICAS.Vision Series RIS 5. 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.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. 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. Inc. Proprietary and Confidential 89 .

Vision Series RIS 5.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. Proprietary and Confidential 90 . 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.

Inc. final or addendum reports based upon a trigger define in Vision Series RIS. 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.1 Definition Vision Series RIS sends the order message event type ORU^R01 which is the Observational Report Unsolicited. AMICAS.7 ORU^R01 – Results Message Type 4.7. The ORU will send preliminary.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. Proprietary and Confidential 91 . The HL7 message will consist of the following message segments.

0 HL7 Interface Guide Outbound Messages 4.7.3” HL7 version number Current date/time <yyyymmddhhmmss> "|" "^~\&" ”Vision SeriesRIS” <Corporation Name> “PACS” Vision Series Data Mapping/ Comments "NE" AMICAS.Vision Series RIS 5. Length. HL7 Field Name. Proprietary and Confidential 92 . Opt.2 MSH (Message Header Segment) . Data Type. Rejection Rules. Inc. 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.ORU^R01 The following table lists each Message Header segment and their Seq.

Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 Language . Inc. Fax.7.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. Length. and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID . Opt. O. Email 12 County Code B 4 IS 13 Phone Number .ORU^R01 The following table lists each Patient Identification Definition segment and their Seq.0 HL7 Interface Guide Outbound Messages 4.Date portion only (YYYYMMDD) Patient Gender (F.Vision Series RIS 5.3 PID (Patient Identification Definition Segment) . 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 . Proprietary and Confidential 93 . Data Type.Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number . PMIS or Social Security> Patient Unique Identifier <Jacket. 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. HL7 Field Name.Patient O 60 CE AMICAS. Rejection Rules. M. Jacket.

Inc.Patient Driver’s Lic Num . HL7 Field Name.4 PV1 (Patient Visit Segment) .Vision Series RIS 5. Proprietary and Confidential 94 . Length.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 .7. Data Type.ORU^R01 The following table lists each Patient Visit segment and their Seq. 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. Rejection Rules. 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.

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 .Vision Series RIS 5. Inc.

Data Type. Rejection Rules.7.5 ORC (Common Order Segment) . Length. 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.ORU^R01 The following table lists each Common Order segment and their Seq.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. Inc. Proprietary and Confidential 96 . HL7 Field Name. Opt.

Vision Series RIS 5. Proprietary and Confidential 97 . Inc.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 98 .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.7. HL7 Field Name.ORU^R01 The following table lists each Order Detail/Observation Request segment and their Seq. Inc. Rejection Rules.6 OBR (Order Detail /Observation Request) . Length. Opt.Vision Series RIS 5. 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. Data Type.

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. 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. 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. 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. Inc. Tilde (~) separates referring from any or all CC physicians. Proprietary and Confidential 99 . 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.

Inc.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.Vision Series RIS 5. Proprietary and Confidential 100 .

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.Business O 40 XTN <(Area Code)Phone Number^Additional text in phone number field> 15 Language . Proprietary and Confidential 104 . Jacket. Fax. 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. HL7 Field Name. Data Type.8. Email 12 County Code B 4 IS 13 Phone Number .3 PID (Patient Identification Definition Segment) .Vision Series RIS 5. O. PMIS or Social Security> Patient Unique Identifier <Jacket.ORU^R01 The following table lists each Patient Identification Definition segment and their Seq.Date portion only (YYYYMMDD) Patient Gender (F. Opt. 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.Patient O 60 CE AMICAS. Length.Home O 40 XTN <(Area Code)Phone Number^Additional text in phone number field^Fax Number^Email Address> Work Phone 14 Phone Number . and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID . 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 . M.0 HL7 Interface Guide Outbound Messages 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.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 . Inc. Length.Vision Series RIS 5. HL7 Field Name.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.8. Data Type. Proprietary and Confidential 105 . Rejection Rules.4 PV1 (Patient Visit Segment) .ORU^R01 The following table lists each Patient Visit segment and their Seq. Opt.Patient Driver’s Lic Num .

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

ORU^R01 The following table lists each Common Order segment and their Seq. Opt.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. Length. 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. Inc.Vision Series RIS 5. HL7 Field Name.5 ORC (Common Order Segment) . Data Type.8. Rejection Rules. 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. Inc. Proprietary and Confidential 108 .Vision Series RIS 5.

Length. 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.ORU^R01 The following table lists each Order Detail/Observation Request segment and their Seq. Proprietary and Confidential 109 .Vision Series RIS 5.6 OBR (Order Detail /Observation Request) . HL7 Field Name.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. Opt. Data Type. Inc.8.

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. 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. Tilde (~) separates referring from any or all CC physicians. 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. Inc. Proprietary and Confidential 110 .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.

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.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. Proprietary and Confidential 111 .

AMICAS. Data Type.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. Length. The report will keep the same formatting as displayed in RIS. Inc.7 OBX (Observation/Result Segment) .ORU^R01 The following table lists each Observation/Result segment and their Seq. and Mapping/Comments: OBX Seq 1 2 3 4 5 6 7 8 HL7 Field Name Set ID . Proprietary and Confidential 112 .8.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. Rejection Rules. Opt. HL7 Field Name.Vision Series RIS 5.

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. The receiving billing system can pick up the message and continue with the charge out process.9 ORM^O01 – HL7 Batch Charge Out Message Type 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.9.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.Vision Series RIS 5. The message is triggered to be sent once a charge out is done. Inc. Proprietary and Confidential 113 .

4.9.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. Rejection Rules.Currently "2.2 MSH (Message Header Segment) . Data Type. Length. 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 .ORM^O01 The following table lists each Message Header segment and their Seq. Proprietary and Confidential 114 .0 HL7 Interface Guide Outbound Messages Message Segment IN2 PR1 Segment Description Insurance Procedure See the Glossary for definitions of each interface.Vision Series RIS 5. Opt. Inc. HL7 Field Name.

3 PID (Patient Identification Definition Segment) .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. and Mapping/Comments: PID Seq 1 HL7 Field Name Set ID . Inc.9.0 HL7 Interface Guide Outbound Messages 4. Fax. Opt. Length. HL7 Field Name.ORM^O01 The following table lists each Patient Identification Definition segment and their Seq. Rejection Rules.Vision Series RIS 5. 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. Proprietary and Confidential 115 . Data Type.

Rejection Rules. and Mapping/Comments: PV1 Seq 1 HL7 Field Name Set .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.4 PV1 (Patient Visit Segment) . Inc. HL7 Field Name. A Tilde (~) separates referring from any/all cc physicians.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.Vision Series RIS 5. Data Type. Opt. Proprietary and Confidential 116 .9. 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.ORM^O01 The following table lists each Patient Visit segment and their Seq.

Vision Series RIS 5. Inc.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. Proprietary and Confidential 117 .

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. Inc.Vision Series RIS 5. Schedule & Visit) <(comment type)^(comment free text)> Vision Series Data Mapping/ Comments AMICAS. Proprietary and Confidential 118 . HL7 Field Name. Rejection Rules. Length. 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.5 PV2 (Patient Visit Segment) . Opt.ORM^O01 The following table lists each Patient Visit segment and their Seq.9. Data Type.

Proprietary and Confidential 119 .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. Inc.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

Rejection Rules. Opt. Data Type. Rejection Rules. Opt. and Mapping/Comments: DB1 Seq 1 2 3 4 HL7 Field Name Set ID .9.9. Proprietary and Confidential 123 . Length.ORM^O01 The following table lists each Accident segment and their Seq. Length.7 ACC (Accident Segment) .ORM^O01 The following table lists each Disability segment and their Seq.Vision Series RIS 5. HL7 Field Name.8 DB1 (Disability Segment) . Data Type. Inc.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. 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.0 HL7 Interface Guide Outbound Messages 4. HL7 Field Name.

Data Type. Inc.9 IN1 (Insurance Segment) . Date. 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.Vision Series RIS 5.ORM^O01 The following table lists each Insurance segment and their Seq. Length. HL7 Field Name.9.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.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. Identifier <Authorization^^G1> Insurance Plan Type <Plan Type Name> Insured Name <Last Name^First^Middle^Suffix> AMICAS. Proprietary and Confidential 124 . Rejection Rules.

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. Day Company Plan Code Policy Number Policy Deductible Policy Limit .Amount Policy Limit .Vision Series RIS 5. 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. Inc.Days Room Rate . Proprietary and Confidential 125 . N.R.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.

Proprietary and Confidential 126 . Data Type.10 IN2 (Insurance Segment) . Opt.ORM^O01 The following table lists each Insurance segment and their Seq.Vision Series RIS 5. 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. HL7 Field Name. Length. Inc. Rejection Rules.9.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.

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

Proprietary and Confidential 128 .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. 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. Contact Reason Insurance Co.Vision Series RIS 5. 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

Discharge and Transfer messages contain information relating to patient demographics. Personnel included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application. Location resources are identified with this specific segment because of the specific encoding of locations used by the HL7 specification. The ACK message is used to respond to a message indicating receipt and status (either success or failure) by the receiving system. anesthesiologists. American Standard Code for Information Interchange. The appointment information service segment contains information about various kinds of services that can be scheduled. Services not controlled by a schedule are not identified on a schedule request using this segment. Proprietary and Confidential 132 . operating rooms. 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. ADT AE AIL AIP AIS ASCII BAR Broker DB1 AMICAS.Vision Series RIS 5. Personnel not controlled by a schedule are not identified on a schedule request using this segment. or CRNAs). An interface engine. The kinds of personnel described on this segment include any healthcare provider in the institution controlled by a schedule (for example: technicians. This segment was created instead of adding disability attributes to each segment that contains a person (to which disability may apply).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 appointment information location resource segment contains information about location resources (meeting rooms. General Acknowledgment. The disability segment contains information related to the disability of a person. Admission. or other locations) that can be scheduled. Inc. The appointment information personnel resource segment contains information about the personnel types that can be scheduled. physicians. surgeons. Resources not controlled by a schedule are not identified on a schedule request using this segment. nurses. Resources included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application. Patient Account Balance Information message type. examination rooms. Application Entity. Services included in a transaction using this segment are assumed to be controlled by a schedule on a schedule filler application.

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

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

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

Proprietary and Confidential 136 . The real-world event is called the trigger event. There is a one-to-many relationship between message types and trigger event codes.Vision Series RIS 5. Inc. UID AMICAS. 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. Unique Identifier. 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.0 HL7 Interface Guide Glossary Term Trigger Event Definition The 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. For example.

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.Vision Series RIS 5.

Proprietary and Confidential 138 . <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.Vision Series RIS 5. JR or III) (ST)> ^ <prefix (e...g.. replaces the TN data type.3 and later.3. <family name (FN)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.. replaces the PN data type.g. DR) (ST)> ^ <degree (e. DR) (ST)> ^ <degree (e.3 and later. Demographics In Version 2.g. [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. Inc.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.g.2.. replaces the AD data type..g. 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. JR or III) (ST)> ^ <prefix (e. 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.g. The CM data type is maintained strictly for backward compatibility and may not be used for the definition of new fields.

Sign up to vote on this title
UsefulNot useful