Incoming Results from Lab

Instruments - Stainer Status
Updates Interface Reference
Guide (AIK 80)
 
 
Version: May 2022
 
Last Updated: May 06, 2022
 
 
To see the most up-to-date documentation for your system along with profile variable and error help text, use the
Reference Guide Viewer in Hyperspace (search: Reference Guide Viewer). These PDFs are intended as a backup only.
 
To access the table of contents, use the bookmarks feature within your PDF reader.
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
  
Summary
Incoming Results from Lab Instruments - Stainer Status Updates
This interface is used to receive slide status update messages when a stainer reaches certain points in the staining
process.

In the Foundation System

This interface is configured in the Foundation System as interfaces 334359-Incoming Results to Beaker from Stainer
and 1469334359 - Incoming Results to Beaker from Stainer - Ventana. Work with your Bridges TS to move these
records into your system.
 

Additional Documentation
Outgoing Orders to Lab Instruments - Slide Orders Interface
For information on sending orders to your stainer, or other slide instruments, refer to the Outgoing Orders to Lab
Instruments - Slide Orders Interface Reference Guide (AIK 79).

Incoming Results from Lab Instrument Interfaces

For information on receiving laboratory result messages on AIK 80, refer to the appropriate guide for POC or non-
POC results.
• Incoming Results from Lab Instruments Interface Reference Guide (AIK 80)
• Incoming Results from Lab Instruments - Point-of-Care (POC) Devices Interface Reference Guide (AIK 80)

Message Specifications
OUL^R21 Unsolicited Laboratory Observation Message
Message Format for Event Type R21
Segment Description

MSH Message Header

PID Patient Identification

PV1 Patient Visit

ORC Order Common

OBR Observation Reports

ORL^O22 - Incoming Stainer Order Acknowledgement

Message Format for Event Type ORL^O22
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Segment Description

MSH Message Header

MSA Message Acknowledgement

PID Patient Information

PV1 Patient Visit Information

ORC Common Order

OBR Observation Request

Setup
Communication Methods
Epic recommends using the Incoming TCP/IP Using Database Servers communication method.
Other supported communication methods include:
• Incoming TCP/IP Using Interconnect
• HL7v2 File Listener Using Interconnect
• Flat File Conversion Using Database Server
 

File Status Updates from Stainers

The Incoming Results from Lab Instruments interface receives a status update message when a stainer reaches
certain points in the staining process. To file these status updates, add message (AIM) 383-In - OUL^R21 (Unsolicited
Laboratory Result) to your interface specification record. When filing updates, OBR-7 is used as a time stamp for
when the status being received occurred.
Additionally, create a general table based on table specification 151000-Container Status Event Table and map stainer
statuses you receive from your stainers to the corresponding Beaker events. You'll set this table in profile variable
STAIN_STATUS_TBL (6866).
To complete the outgoing orders setup required for stainer integration, refer to the Outgoing Orders to Lab
Instruments - Slide Orders Interface Reference Guide (AIK 79)
Application Configuration:
Refer to the Interface with Slide Stainers topic.

Profile Variables
• STAIN_STATUS_TBL [6866]
Errors
• INVALID STAIN STATUS [30105]
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 • STAIN STATUS TABLE NOT FOUND [30106]
Format Example - Stain Start Status Update
MSH|^~\&|VENDOR|APLab|LIS||201301011355||OUL^R21||P|2.4|
PID|||MRN1234||LastName^FirstName^MiddleInitial||19800101|M|
ORC|SC||VendorSlideID||CM|E||||||||||||^MethodID|||||||STAINING
OBR|1||VendorSlideID|SlideProtocol^StatusUpdate|||20090313142100||||||||||||12345^2|
12345^1|12345^A|

Format Example - Stain Complete Status Update

MSH|^~\&|VENDOR|APLab|LIS||201301011355||OUL^R21||P|2.4|
PID|||MRN1234||LastName^FirstName^MiddleInitial||19800101|M|
ORC|SC||VendorSlideID||IP|||||||||||||^MethodID|||||||STAINED
OBR|||VendorSlideID|SlideProtocol^StatusUpdate|||20090313142100||||||||||||Slide-Info||
Slide-SpecID|
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
  suggestion 
 Supported Segments and Fields

Fields in gray are not supported by this interface.

Message Types: IN - O22 (LABORATORY ORDER RESPONSE MESSAGE)

MSH - Message Header
Element Name Type Usage Notes
2 - Encoding ST Required Value is typically: ^~\&
Characters
3 - Sending — — Format: Free text
Application
4 - Sending Facility HD Optional Format: Free text
5 - Receiving HD Optional Format: Free text
Application
Format: Free text
6 - Receiving Facility HD Optional Free text
7 - Date/Time of DTM Optional Format: Standard HL7 date/time format
Message
8 - Security ST Optional —
9 - Message Type MSG Required Format: <Message type>^<Trigger event>
Example: ORM^O01
10 - Message Control ST Optional Value to be returned in MSA-2 in the Acknowledgment message
ID
11 - Processing ID PT Required Values:
• D: Debugging
• P: Production
• T: Training
12 - Version ID VID Required HL7 version number. For example, 2.5.
13 - Sequence NM Optional Optional field used in sequence number protocol. By default, Epic does
Number not use sequence number protocol.
14 - Continuation ST Optional In conjunction with the HL7 DSC segment, this field is used to identify
Pointer continuations of messages. It allows large messages to be broken into
multiple smaller messages, which is necessary under certain
implementation limitations.
MSH-14 contains the identifier matching the value sent in the DSC
segment in a previous message, identifying the current message as a
continuation of the previous.
15 - Accept ID Optional This field identifies the conditions under which Accept Acknowledgments
Acknowledgment must be returned in response to a message. This field is required for
Type enhanced acknowledgment mode. If null, acknowledgments are sent in
original acknowledgment mode.
Values:
• AL: Always
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Element Name Type Usage Notes
• ER: Error/reject conditions only
• NE: Never
• SU: Successful completion only
16 - Application ID Optional —
Acknowledgment
Type
17 - Country Code ID Optional —
18 - Character Set ID Optional —
19 - Not Supported — — —
20 - Not Supported — — —
21 - Conformance EI Optional —
Statement ID
22 - Sending XON Optional —
Responsible
Organization
23 - Receiving XON Optional —
Responsible
Organization

MSH-2 - Encoding Characters

Value is typically: ^~\&
The interface supports the truncation control character \P\ in a limited capacity. The interface can be configured
to accept this control character and translate it to a fifth character in the Encoding Characters field (MSH-2). If
the incoming MSH-2 does not contain a character, the interface uses the HL7 default fifth character, a pound
sign ("#").
 
Epic's support for \P\ is limited and is not intended to meet HL7 2.7 or draft 2.8 specifications. Accordingly, keep
the following in mind:
• The interface does not remove explicitly set truncation characters from the ends of fields. These characters
proceed to normal interface message processing.
• The interface unescapes \P\ regardless of where it appears in the message. The HL7 specification indicates
\P\ should appear only at the end of a subcomponent, but the interface does not have special handling to
account for inappropriate placement of \P\.
Errors
• REQUIRED HL7 CONTROL CHARACTER MISSING [110]
• DUPLICATE HL7 CONTROL CHARACTERS RECEIVED [111]
• MESSAGE NOT ACK'D SUCCESSFULLY [100000]
• REQUIRED HL7 CONTROL CHARACTER MISSING FROM ACK [121]
• DUPLICATE HL7 CONTROL CHARACTERS RECEIVED ON ACK [122]
MSH-4 - Sending Facility
Format: Free text
For R01 messages, this field should contain a middle tier (MAC) record ID.
Errors
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 • NO MAC RECORD FOUND [2948]
• MIDDLE TIER MAC REQUIRED [2949]
• INACTIVE MIDDLE TIER MAC [3158]
Build
• Middle tier (MAC) record
MSH-5 - Receiving Application
Format: Free text
Errors
• FAILED TO RESOLVE TO AN ORDER FILING CONTEXT [4517]
• CANNOT FILE NON-PARTICIPATING SUBMITTER ORDER [4518]
• CANNOT FILE NON-PARTICIPATING SUBMITTER ORDERS IN EMR MODE [4519]
• USING ORDER_FILING_CONTEXT DEFAULT [1387]
MSH-9 - Message Type
Format: <Message type>^<Trigger event>
Example: ORM^O01
Errors
• MESSAGE NOT DEFINED [100310]
MSH-12 - Version ID
HL7 version number. For example, 2.5.
To ignore the version check, add "*" to your interface specification.
MSH-14 - Continuation Pointer
In conjunction with the HL7 DSC segment, this field is used to identify continuations of messages. It allows large
messages to be broken into multiple smaller messages, which is necessary under certain implementation
limitations.
MSH-14 contains the identifier matching the value sent in the DSC segment in a previous message, identifying
the current message as a continuation of the previous.
Configuration pointers are only processed by incoming TCP/IP using database servers connections when
receiving a message. They cannot be tested by modifying and resubmitting messages or loading messages
from a flat file.

Profile Variables
• IGN_CONT_POINTER [1442]
MSA - Message Acknowledgment
Element Name Type Usage Notes
1 - Acknowledgment ID Required Indicates successful/not successful processing of message
Code
Format: Code
Original Mode Values:
• AA - Application Accept
• AE - Application Error
• AR - Application Reject
Enhanced Mode Values:
• CA - Commit Accept
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Element Name Type Usage Notes
• CE - Commit Error
• CR - Commit Reject
2 - Message Control ST Required Message control ID of the message sent by the original sending system
ID
Format: Text
3 - Text Message ST Optional Optional field that can contain an error message
Format: Text

PID - Patient Identification

Segment-Level Summary
If patient information is not received in the PID segment, patient lookup can be skipped using
INSTRUMENT_IGNORE_PID (9520).
In this case, the interface files the result to the visit and patient found using the visit identifier in the message.
Note that if the PID segment is ignored, patient information in PID cannot be compared against the patient
found in the database using the visit identifier. Because of this, Epic recommends receiving patient information
in messages to ensure that the patient information and the visit identifier identify the same patient.
This interface is not allowed to create patients if a patient cannot be found by either the patient identifier or
visit identifier.
Profile Variables
• INSTRUMENT_IGNORE_PID [9520]

Element Name Type Usage Notes

1 - Not Supported — — —
2 - Patient ID CX Optional This field is only used for backwards compatibility.
3 - Patient Identifier CX Required Format: <Patient ID>^^^<assigning authority>^<ID Type>
List
The patient identifier list can contain values for the national identifier
formatted as follows. The assigning authority and ID Type for the national
identifier are set in NAT_ID_ASSIGNING_AUTHORITY (1062) and
NAT_IDENTIFIER_ID_TYPE (1163) respectively.
<National identifier>^^^<Assigning Authority>^<ID Type>

4 - Alternate Patient CX Optional —

ID
5 - Patient Name XPN Required —
6 - Mother's Maiden ST Optional —
Name
7 - Date/Time of Birth DTM Optional Only date of birth is supported. Used only for validation purposes.
8 - Sex IS Optional —
9 - Not Supported — — —
10 - Race CWE Optional —
11 - Patient Address XAD Optional —
12 - County Code IS Optional This field is for backwards compatibility only.
13 - Phone Number – XTN Optional Four formats are accepted. If the equipment type is not specified it
Home defaults to the home phone.
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Element Name Type Usage Notes
Format: [nnn](nnn)nnn-nnnn^<Telecommunication use
code>^<Telecommunication equipment type>^<E-mail
address>^<Country code>^<Area/city code>^<Local
number>^<Extension>^<Any text>^<Extension prefix>^<Speed dial
code>^<Unformatted telephone number>
E-mail addresses as well as confidential and temporary contact numbers
are not supported.
14 - Phone Number – XTN Optional (nnn)nnn-nnnnx<extension>
Work
or
^^^^^<City/area code>^<Number>^<Extension>
or
#<text>
15 - Primary CWE Optional Formats:
Language
• <Language>
• <Language>^^^^^^^^
16 - Marital Status CWE Optional —
17 - Religion CWE Optional —
18 - Patient Visit CX Optional Configurable; Can be used to locate the visit to which the message should
Number be associated.
19 - SSN Number – ST Optional Used for validation. Numeric with or without dashes.
Patient
National identifier can also be received in PID-3.
20 - Not Supported — — —
21 - Not Supported — — —
22 - Ethnic Group CWE Optional This field is only used for R30 messages.

PID-2 - Patient ID
This field is only used for backwards compatibility.
Database Location
• PATIENT ID (I EPT .1)
PID-3 - Patient Identifier List
Format: <Patient ID>^^^<assigning authority>^<ID Type>
The patient identifier list can contain values for the national identifier formatted as follows. The assigning
authority and ID Type for the national identifier are set in NAT_ID_ASSIGNING_AUTHORITY (1062) and
NAT_IDENTIFIER_ID_TYPE (1163) respectively.
<National identifier>^^^<Assigning Authority>^<ID Type>
To avoid unintentionally filing data to the incorrect patient, this interface requires patient validation to be
configured. If you don't configure patient validation, this interface fails to start. For more information about
patient validation including instructions on how to turn on the feature, refer to the Patient Validation and
Duplicate Prevention and Requisition Grouper Validation topics.
Patient lookup fails if an ID Type of "DL" is the only ID and ID type received in PID-3 because "DL" is reserved
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 for driver's license numbers, and this interface doesn't support filing driver's license.

Profile Variables
• PAT_LOOKUP [3]
• HL7_PAT_ID [378]
• DEFAULT_ID_TYPE [776]
• REQUIRE_RQG_VALIDATION [5087]
• REQUISITION_LOOKUP [25942]
• CLINLAB_EPT_RQG_LOOKUP [35942]
• NAT_ID_ASSIGNING_AUTHORITY [1062]
• NAT_IDENTIFIER_ID_TYPE [1163]
Errors
• PATIENT ID NOT FOUND [530]
• EPT OR RQG RECORD DOES NOT MATCH RECORD ON SPECIMEN [2891]
• RQG NOT FOUND [3926]
• MULTIPLE PATIENTS IDENTIFIED [6135]
• MULTIPLE RECORDS FOUND DURING LOOKUP [25007]
Build
• Identity ID Types (IIT records)
Database Location
• SOCIAL SECURITY NUMBER (I EPT 160)
PID-4 - Alternate Patient ID
Database Location
• EXTERNAL GROUP ID (I EPT 7196)
PID-5 - Patient Name
The patient's name can be used to help validate that the message is for the correct patient.
Profile Variables
• PAT_NAME_TYPE_TBL [2802]
• NAME_ACADEMIC_TBL [2182]
• NAME_SUFFIX_TBL [652]
• NAME_TITLE_TBL [3404]
• USE_LEGAL_NAME_AS_VALIDATION_DISPLAY_NAME [5931]
Errors
• TABLE MAPPING ERROR FOR NAME TITLE [7674]
• NAME SUFFIX COULD NOT BE MAPPED [775]
• ACADEMIC NAME COULD NOT BE MAPPED [776]
Database Location
• PATIENT NAME (I EPT .2)
• TITLE (I EPT 121)
• SUFFIX (I EPT 122)
• ACADEMIC (I EPT 124)
PID-6 - Mother's Maiden Name
Profile Variables
• ESC_CHK [436]
Database Location
• MOTHER'S MAIDEN NAME (I EPT 360)
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 PID-7 - Date/Time of Birth
Only date of birth is supported. Used only for validation purposes.
Only date of birth is supported.
Database Location
• DATE OF BIRTH (I EPT 110)
PID-8 - Sex
Errors
• INCOMING TABLE VALUE COULD NOT BE MAPPED [40000]
Database Location
• LEGAL SEX (I EPT 130)
PID-10 - Race
This field can only be used for Identity Duplicate Checking.
Profile Variables
• RACE_TABLE [326]
• RACE_ITEM [1254]
Errors
• INCOMING TABLE VALUE COULD NOT BE MAPPED [40000]
Database Location
• ETHNIC GROUP (I EPT 135)
• PATIENT RACE (I EPT 145)
PID-11 - Patient Address
Permanent Address
• Street
• Dwelling Number
• City
• State
• ZIP/Postal code
• Country County
Confidential Address
• Street
• Dwelling Number
• City
• State
• ZIP/Postal code
• Country
• Start Date
• End Date
Temporary Address
• Street
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 • Dwelling Number
• City
• State
• ZIP/Postal code
• Country
• Start Date
• End Date
Format:
<Street 1>^<Street 2/House Number>^<City>^<State>^<ZIP code>^<Country>^<Address
Type>^^<County>^^^^<Start Date>^<End Date>
This field can repeat, with permanent, confidential, and temporary addresses sent in separate repetitions. The
different addresses are denoted by a flag in the <Address Type> piece of the field (piece 7)
ZIP/postal code is required to be in the U.S. or Canadian format unless the interface is configured to receive
international formats.
Profile Variables
• INTER_ZIP [558]
• COUNTRY_TABLE [602]
• STATE_TABLE [735]
• COUNTY_TABLE [3031]
• ADDRESS_TYPE_TBL [2776]
Errors
• ADDRESS TYPE COULD NOT BE MAPPED [748]
Database Location
• ADDRESS (I EPT 50)
• CITY (I EPT 60)
• STATE (I EPT 70)
• COUNTY OF RESIDENCE (I EPT 75)
• COUNTRY (I EPT 78)
• ZIP CODE (I EPT 80)
• HOUSE NUMBER (I EPT 82)
• ADDRESS START DATE (I EPT 84)
• CONFIDENTIAL ADDRESS (I EPT 550)
• CONFIDENTIAL CITY (I EPT 555)
• CONFIDENTIAL STATE (I EPT 560)
• CONFIDENTIAL ZIP CODE (I EPT 575)
• CONFIDENTIAL COUNTRY (I EPT 570)
• CONFIDENTIAL HOUSE NUMBER (I EPT 571)
• CONFIDENTIAL START DATE (I EPT 600)
• PATIENT TEMPORARY ADDRESS (I EPT 5430)
• PATIENT TEMPORARY CITY (I EPT 5431)
• PATIENT TEMPORARY STATE (I EPT 5432)
• PATIENT TEMPORARY ZIP (I EPT 5434)
• PATIENT TEMPORARY COUNTRY (I EPT 5433)
• PATIENT TEMPORARY HOUSE NUMBER (I EPT 5442)
• PATIENT TEMPORARY ADDRESS START DATE (I EPT 5437)
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 • PATIENT TEMPORARY ADDRESS END DATE (I EPT 5438)
PID-12 - County Code
This field is for backwards compatibility only.
Profile Variables
• COUNTY_TABLE [3031]
Errors
• TABLE MAPPING ERROR FOR COUNTY [7455]
PID-13 - Phone Number – Home
Four formats are accepted. If the equipment type is not specified it defaults to the home phone.
Format: [nnn](nnn)nnn-nnnn^<Telecommunication use code>^<Telecommunication equipment type>^<E-
mail address>^<Country code>^<Area/city code>^<Local number>^<Extension>^<Any text>^<Extension
prefix>^<Speed dial code>^<Unformatted telephone number>
E-mail addresses as well as confidential and temporary contact numbers are not supported.
Profile Variables
• PHONE_CODE_TBL [9252]
• COMM_EQUIP_TYPE_TBL [10278]
Errors
• INVALID PHONE NUMBER [210]
• INVALID EMAIL ADDRESS [215]
• INVALID PHONE NUMBER: PATIENT PHONE [224]
• PHONE CODE COULD NOT BE MAPPED [774]
Database Location
• OTHER COMMUNICATION DEVICES (I EPT 94)
• PHONE 1 (I EPT 90)
• OTHER COMMUNICATION NUMBERS (I EPT 98)
PID-14 - Phone Number – Work
(nnn)nnn-nnnnx<extension>
or
^^^^^<City/area code>^<Number>^<Extension>
or
#<text>
Three formats are accepted.
[nnn](nnn)nnn-nnnn^^^^^^^<Extension>
^^^^<Country code>^<City/area code>^<Number>^<Extension>
#<text>
Errors
• INVALID PHONE NUMBER [210]
• INVALID PHONE NUMBER: PATIENT PHONE [224]
Database Location
• OTHER COMMUNICATION DEVICES (I EPT 94)
• OTHER COMMUNICATION NUMBERS (I EPT 98)
• WORK PHONE (I EPT 5170)
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 PID-15 - Primary Language
Formats:
• <Language>
• <Language>^^^^^^^^
This field can only be used for Identity Duplicate Checking.
The first component is used. All others are ignored.
Profile Variables
• LANGUAGE_TABLE [2562]
Errors
• PATIENT LANGUAGE COULD NOT BE MAPPED [2099]
• TABLE MAPPING ERROR FOR LANGUAGE [7675]
Database Location
• LANGUAGE (I EPT 155)
• LANGUAGE-SPOKEN (MR) (I EPT 146)
PID-16 - Marital Status
Profile Variables
• MARITAL_TABLE [327]
Errors
• TABLE MAPPING ERROR FOR MARITAL STATUS [7456]
Database Location
• MARITAL STATUS (I EPT 140)
PID-17 - Religion
Profile Variables
• RELIGION_TABLE [2561]
Errors
• TABLE MAPPING ERROR FOR RELIGION [7457]
Database Location
• RELIGION (I EPT 150)
PID-18 - Patient Visit Number
Configurable; Can be used to locate the visit to which the message should be associated.
Profile Variables
• ENCOUNTER_KEY [61]
• ACCOUNT_ID_LOOKUP [2481]
• ACCOUNT_ID_TYPE_DEFAULT [2484]
• ACCOUNT_ITEM [868]
Database Location
• SOCIAL SECURITY NUMBER (I EPT 160)
• CONTACT SERIAL NUMBER (I EPT 8)
• BILLING NUMBER (I EPT 17)
• VISIT HOSPITAL ACCOUNT (I EPT 2500)
PID-19 - SSN Number – Patient
Used for validation. Numeric with or without dashes.
National identifier can also be received in PID-3.
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Profile Variables
• NAT_ID_BYPASS_FORMATTING [666]
Errors
• INVALID NATIONAL IDENTIFIER FORMAT [91524]
Database Location
• SOCIAL SECURITY NUMBER (I EPT 160)
PID-22 - Ethnic Group
This field is only used for R30 messages.
This field can only be used for Identity Duplicate Checking.
Profile Variables
• ETHNIC_GROUP_TABLE [1252]
• ETHNIC_GROUP_LOCATION [2728]
Errors
• INCOMING TABLE VALUE COULD NOT BE MAPPED [40000]
Database Location
• ETHNIC GROUP (I EPT 135)
• ETHNIC BACKGROUND (I EPT 134)
ORC - Order Common
Segment-Level Summary
Most of the information on the optional ORC segment is ignored by the Incoming Lab Instrument Results
Interface to Clinical Lab. Note that most of the information sent in this segment is also duplicated in the OBR
segment.

Element Name Type Usage Notes

1 - Order Control ID Required Supported Codes:
• RE - Observations to Follow
2 - Not Supported — — —
3 - Filler Order — Optional When integrating with stainer instruments, this field contains the vendor-
Number specified identifier.
4 - Not Supported — — —
5 - Not Supported — — —
6 - Not Supported — — —
7 - Not Supported — — —
8 - Not Supported — — —
9 - Not Supported — — —
10 - Not Supported — — —
11 - Not Supported — — —
12 - Not Supported — — —
13 - Not Supported — — —
14 - Not Supported — — —
15 - Not Supported — — —
16 - Not Supported — — —
17 - Not Supported — — —
18 - Entering Device CWE Optional —
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Element Name Type Usage Notes
19 - Not Supported — — —
20 - Not Supported — — —
21 - Not Supported — — —
22 - Not Supported — — —
23 - Not Supported — — —
24 - Not Supported — — —
25 - Stainer Order — — Stain Status
Status

ORC-1 - Order Control

Supported Codes:
• RE - Observations to Follow
Errors
• ORDER ALREADY EXISTS, NA MESSAGE WILL NOT BE SENT [2829]
• ORDER ALREADY EXISTS, BUT NA MESSAGE WILL BE SENT FOR SN [2871]
• UNEXPECTED CONTROL CODE [2912]
• CONTROL CODE NOT SUPPORTED [2967]
• INVALID ORDER CONTROL CODE [6123]
• INVALID STATUS FOR CONTROL CODE [6171]
ORC-18 - Entering Device
The second component of this field can contain the instrument messaging identifier (I MAC 51270). For stainer
status messages this is required as there is no OBX segment to pull the instrument messaging identifier from.
Errors
• NO METHOD MAC FOUND FROM MESSAGING IDENTIFIER [2953]
• METHOD MAC WAS INACTIVE [2985]
ORC-25 - Stainer Order Status
Stain Status
This field contains the status that will be used to log an event in Beaker. STAIN_STATUS_TBL (6866) is used to
map these status to events that will be logged to the specimen in Beaker.
Profile Variables
• STAIN_STATUS_TBL [6866]
Errors
• STAIN STATUS TABLE NOT FOUND [30106]
• INVALID STAIN STATUS [30105]
OBR - Observation Reports
Segment-Level Summary
The OBR segment is used to send information specific to each test order.

Element Name Type Usage Notes

1 - Not Supported — — —
2 - Not Supported — — —
3 - Not Supported — — —
4 - Not Supported — — —
5 - Not Supported — — —
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Element Name Type Usage Notes
6 - Not Supported — — —
7 - Observation Date/ DTM Optional —
Time
8 - Not Supported — — —
9 - Not Supported — — —
10 - Not Supported — — —
11 - Not Supported — — —
12 - Not Supported — — —
13 - Not Supported — — —
14 - Not Supported — — —
15 - Not Supported — — —
16 - Not Supported — — —
17 - Not Supported — — —
18 - Not Supported — — —
19 - Placer Field 2 ST Optional When integrating with stainer instruments, this field contains the slide or
container ID.
20 - Not Supported — — —
21 - Filler Field 2 ST Optional This field contains the specimen information.

OBR-7 - Observation Date/Time

Stainer Order Status Date/Time
For information about filing status updates from stainers, refer to the File Status Updates from Stainers topic.
Errors
• INVALID DATE [504]
• COLLECTION TIME OCCURS IN THE FUTURE [864]
• COLLECTION TIME IS OLDER THAN 14 DAYS [865]
• MULTIPLE COLLECTION DATES AND TIMES RECEIVED [866]
• CANNOT UPDATE COLLECTION DATE AND TIME [867]
Database Location
• EVENT INSTANT (I OVC 51064)
OBR-19 - Placer Field 2
When integrating with stainer instruments, this field contains the slide or container ID.
This field contains the container ID which is the Beaker Identity ID for the contain and a trailing container
identified.
Errors
• MISSING CONTAINER ID [30102]
OBR-21 - Filler Field 2
This field contains the specimen information.
This field can contain the specimen ID and trailing specimen identifier.
 
 
 
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
   Message Types: IN - R21 (UNSOLICITED LABORATORY RESULT)
MSH - Message Header
Element Name Type Usage Notes
2 - Encoding ST Required Value is typically: ^~\&
Characters
3 - Sending — — Format: Free text
Application
4 - Sending Facility HD Optional Format: Free text
5 - Receiving HD Optional Format: Free text
Application
Format: Free text
6 - Receiving Facility HD Optional Free text
7 - Date/Time of DTM Optional Format: Standard HL7 date/time format
Message
8 - Security ST Optional —
9 - Message Type MSG Required Format: <Message type>^<Trigger event>
Example: ORM^O01
10 - Message Control ST Optional Value to be returned in MSA-2 in the Acknowledgment message
ID
11 - Processing ID PT Required Values:
• D: Debugging
• P: Production
• T: Training
12 - Version ID VID Required HL7 version number. For example, 2.5.
13 - Sequence NM Optional Optional field used in sequence number protocol. By default, Epic does
Number not use sequence number protocol.
14 - Continuation ST Optional In conjunction with the HL7 DSC segment, this field is used to identify
Pointer continuations of messages. It allows large messages to be broken into
multiple smaller messages, which is necessary under certain
implementation limitations.
MSH-14 contains the identifier matching the value sent in the DSC
segment in a previous message, identifying the current message as a
continuation of the previous.
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Element Name Type Usage Notes
15 - Accept ID Optional This field identifies the conditions under which Accept Acknowledgments
Acknowledgment must be returned in response to a message. This field is required for
Type enhanced acknowledgment mode. If null, acknowledgments are sent in
original acknowledgment mode.
Values:
• AL: Always
• ER: Error/reject conditions only
• NE: Never
• SU: Successful completion only
16 - Application ID Optional —
Acknowledgment
Type
17 - Country Code ID Optional —
18 - Character Set ID Optional —
19 - Not Supported — — —
20 - Not Supported — — —
21 - Conformance EI Optional —
Statement ID
22 - Sending XON Optional —
Responsible
Organization
23 - Receiving XON Optional —
Responsible
Organization

MSH-2 - Encoding Characters

Value is typically: ^~\&
The interface supports the truncation control character \P\ in a limited capacity. The interface can be configured
to accept this control character and translate it to a fifth character in the Encoding Characters field (MSH-2). If
the incoming MSH-2 does not contain a character, the interface uses the HL7 default fifth character, a pound
sign ("#").
 
Epic's support for \P\ is limited and is not intended to meet HL7 2.7 or draft 2.8 specifications. Accordingly, keep
the following in mind:
• The interface does not remove explicitly set truncation characters from the ends of fields. These characters
proceed to normal interface message processing.
• The interface unescapes \P\ regardless of where it appears in the message. The HL7 specification indicates
\P\ should appear only at the end of a subcomponent, but the interface does not have special handling to
account for inappropriate placement of \P\.
Errors
• REQUIRED HL7 CONTROL CHARACTER MISSING [110]
• DUPLICATE HL7 CONTROL CHARACTERS RECEIVED [111]
• MESSAGE NOT ACK'D SUCCESSFULLY [100000]
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 • REQUIRED HL7 CONTROL CHARACTER MISSING FROM ACK [121]
• DUPLICATE HL7 CONTROL CHARACTERS RECEIVED ON ACK [122]
MSH-4 - Sending Facility
Format: Free text
For R01 messages, this field should contain a middle tier (MAC) record ID.
Errors
• NO MAC RECORD FOUND [2948]
• MIDDLE TIER MAC REQUIRED [2949]
• INACTIVE MIDDLE TIER MAC [3158]
Build
• Middle tier (MAC) record
MSH-5 - Receiving Application
Format: Free text
Errors
• FAILED TO RESOLVE TO AN ORDER FILING CONTEXT [4517]
• CANNOT FILE NON-PARTICIPATING SUBMITTER ORDER [4518]
• CANNOT FILE NON-PARTICIPATING SUBMITTER ORDERS IN EMR MODE [4519]
• USING ORDER_FILING_CONTEXT DEFAULT [1387]
MSH-9 - Message Type
Format: <Message type>^<Trigger event>
Example: ORM^O01
Errors
• MESSAGE NOT DEFINED [100310]
MSH-12 - Version ID
HL7 version number. For example, 2.5.
To ignore the version check, add "*" to your interface specification.
MSH-14 - Continuation Pointer
In conjunction with the HL7 DSC segment, this field is used to identify continuations of messages. It allows large
messages to be broken into multiple smaller messages, which is necessary under certain implementation
limitations.
MSH-14 contains the identifier matching the value sent in the DSC segment in a previous message, identifying
the current message as a continuation of the previous.
Configuration pointers are only processed by incoming TCP/IP using database servers connections when
receiving a message. They cannot be tested by modifying and resubmitting messages or loading messages
from a flat file.

Profile Variables
• IGN_CONT_POINTER [1442]
PID - Patient Identification
Segment-Level Summary
If patient information is not received in the PID segment, patient lookup can be skipped using
INSTRUMENT_IGNORE_PID (9520).
In this case, the interface files the result to the visit and patient found using the visit identifier in the message.
Note that if the PID segment is ignored, patient information in PID cannot be compared against the patient
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 found in the database using the visit identifier. Because of this, Epic recommends receiving patient information
in messages to ensure that the patient information and the visit identifier identify the same patient.
This interface is not allowed to create patients if a patient cannot be found by either the patient identifier or
visit identifier.
Profile Variables
• INSTRUMENT_IGNORE_PID [9520]

Element Name Type Usage Notes

1 - Not Supported — — —
2 - Patient ID CX Optional This field is only used for backwards compatibility.
3 - Patient Identifier CX Required Format: <Patient ID>^^^<assigning authority>^<ID Type>
List
The patient identifier list can contain values for the national identifier
formatted as follows. The assigning authority and ID Type for the national
identifier are set in NAT_ID_ASSIGNING_AUTHORITY (1062) and
NAT_IDENTIFIER_ID_TYPE (1163) respectively.
<National identifier>^^^<Assigning Authority>^<ID Type>

4 - Alternate Patient CX Optional —

ID
5 - Patient Name XPN Required —
6 - Mother's Maiden ST Optional —
Name
7 - Date/Time of Birth DTM Optional Only date of birth is supported. Used only for validation purposes.
8 - Sex IS Optional —
9 - Not Supported — — —
10 - Race CWE Optional —
11 - Patient Address XAD Optional —
12 - County Code IS Optional This field is for backwards compatibility only.
13 - Phone Number – XTN Optional Four formats are accepted. If the equipment type is not specified it
Home defaults to the home phone.
Format: [nnn](nnn)nnn-nnnn^<Telecommunication use
code>^<Telecommunication equipment type>^<E-mail
address>^<Country code>^<Area/city code>^<Local
number>^<Extension>^<Any text>^<Extension prefix>^<Speed dial
code>^<Unformatted telephone number>
E-mail addresses as well as confidential and temporary contact numbers
are not supported.
14 - Phone Number – XTN Optional (nnn)nnn-nnnnx<extension>
Work
or
^^^^^<City/area code>^<Number>^<Extension>
or
#<text>
15 - Primary CWE Optional Formats:
Language
• <Language>
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Element Name Type Usage Notes
• <Language>^^^^^^^^
16 - Marital Status CWE Optional —
17 - Religion CWE Optional —
18 - Patient Visit CX Optional Configurable; Can be used to locate the visit to which the message should
Number be associated.
19 - SSN Number – ST Optional Used for validation. Numeric with or without dashes.
Patient
National identifier can also be received in PID-3.
20 - Not Supported — — —
21 - Not Supported — — —
22 - Ethnic Group CWE Optional This field is only used for R30 messages.

PID-2 - Patient ID
This field is only used for backwards compatibility.
Database Location
• PATIENT ID (I EPT .1)
PID-3 - Patient Identifier List
Format: <Patient ID>^^^<assigning authority>^<ID Type>
The patient identifier list can contain values for the national identifier formatted as follows. The assigning
authority and ID Type for the national identifier are set in NAT_ID_ASSIGNING_AUTHORITY (1062) and
NAT_IDENTIFIER_ID_TYPE (1163) respectively.
<National identifier>^^^<Assigning Authority>^<ID Type>
To avoid unintentionally filing data to the incorrect patient, this interface requires patient validation to be
configured. If you don't configure patient validation, this interface fails to start. For more information about
patient validation including instructions on how to turn on the feature, refer to the Patient Validation and
Duplicate Prevention and Requisition Grouper Validation topics.
Patient lookup fails if an ID Type of "DL" is the only ID and ID type received in PID-3 because "DL" is reserved
for driver's license numbers, and this interface doesn't support filing driver's license.

Profile Variables
• PAT_LOOKUP [3]
• HL7_PAT_ID [378]
• DEFAULT_ID_TYPE [776]
• REQUIRE_RQG_VALIDATION [5087]
• REQUISITION_LOOKUP [25942]
• CLINLAB_EPT_RQG_LOOKUP [35942]
• NAT_ID_ASSIGNING_AUTHORITY [1062]
• NAT_IDENTIFIER_ID_TYPE [1163]
Errors
• PATIENT ID NOT FOUND [530]
• EPT OR RQG RECORD DOES NOT MATCH RECORD ON SPECIMEN [2891]
• RQG NOT FOUND [3926]
• MULTIPLE PATIENTS IDENTIFIED [6135]
• MULTIPLE RECORDS FOUND DURING LOOKUP [25007]
Build
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 • Identity ID Types (IIT records)
Database Location
• SOCIAL SECURITY NUMBER (I EPT 160)
PID-4 - Alternate Patient ID
Database Location
• EXTERNAL GROUP ID (I EPT 7196)
PID-5 - Patient Name
The patient's name can be used to help validate that the message is for the correct patient.
Profile Variables
• PAT_NAME_TYPE_TBL [2802]
• NAME_ACADEMIC_TBL [2182]
• NAME_SUFFIX_TBL [652]
• NAME_TITLE_TBL [3404]
• USE_LEGAL_NAME_AS_VALIDATION_DISPLAY_NAME [5931]
Errors
• TABLE MAPPING ERROR FOR NAME TITLE [7674]
• NAME SUFFIX COULD NOT BE MAPPED [775]
• ACADEMIC NAME COULD NOT BE MAPPED [776]
Database Location
• PATIENT NAME (I EPT .2)
• TITLE (I EPT 121)
• SUFFIX (I EPT 122)
• ACADEMIC (I EPT 124)
PID-6 - Mother's Maiden Name
Profile Variables
• ESC_CHK [436]
Database Location
• MOTHER'S MAIDEN NAME (I EPT 360)
PID-7 - Date/Time of Birth
Only date of birth is supported. Used only for validation purposes.
Only date of birth is supported.
Database Location
• DATE OF BIRTH (I EPT 110)
PID-8 - Sex
Errors
• INCOMING TABLE VALUE COULD NOT BE MAPPED [40000]
Database Location
• LEGAL SEX (I EPT 130)
PID-10 - Race
This field can only be used for Identity Duplicate Checking.
Profile Variables
• RACE_TABLE [326]
• RACE_ITEM [1254]
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Errors
• INCOMING TABLE VALUE COULD NOT BE MAPPED [40000]
Database Location
• ETHNIC GROUP (I EPT 135)
• PATIENT RACE (I EPT 145)
PID-11 - Patient Address
Permanent Address
• Street
• Dwelling Number
• City
• State
• ZIP/Postal code
• Country County
Confidential Address
• Street
• Dwelling Number
• City
• State
• ZIP/Postal code
• Country
• Start Date
• End Date
Temporary Address
• Street
• Dwelling Number
• City
• State
• ZIP/Postal code
• Country
• Start Date
• End Date
Format:
<Street 1>^<Street 2/House Number>^<City>^<State>^<ZIP code>^<Country>^<Address
Type>^^<County>^^^^<Start Date>^<End Date>
This field can repeat, with permanent, confidential, and temporary addresses sent in separate repetitions. The
different addresses are denoted by a flag in the <Address Type> piece of the field (piece 7)
ZIP/postal code is required to be in the U.S. or Canadian format unless the interface is configured to receive
international formats.
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Profile Variables
• INTER_ZIP [558]
• COUNTRY_TABLE [602]
• STATE_TABLE [735]
• COUNTY_TABLE [3031]
• ADDRESS_TYPE_TBL [2776]
Errors
• ADDRESS TYPE COULD NOT BE MAPPED [748]
Database Location
• ADDRESS (I EPT 50)
• CITY (I EPT 60)
• STATE (I EPT 70)
• COUNTY OF RESIDENCE (I EPT 75)
• COUNTRY (I EPT 78)
• ZIP CODE (I EPT 80)
• HOUSE NUMBER (I EPT 82)
• ADDRESS START DATE (I EPT 84)
• CONFIDENTIAL ADDRESS (I EPT 550)
• CONFIDENTIAL CITY (I EPT 555)
• CONFIDENTIAL STATE (I EPT 560)
• CONFIDENTIAL ZIP CODE (I EPT 575)
• CONFIDENTIAL COUNTRY (I EPT 570)
• CONFIDENTIAL HOUSE NUMBER (I EPT 571)
• CONFIDENTIAL START DATE (I EPT 600)
• PATIENT TEMPORARY ADDRESS (I EPT 5430)
• PATIENT TEMPORARY CITY (I EPT 5431)
• PATIENT TEMPORARY STATE (I EPT 5432)
• PATIENT TEMPORARY ZIP (I EPT 5434)
• PATIENT TEMPORARY COUNTRY (I EPT 5433)
• PATIENT TEMPORARY HOUSE NUMBER (I EPT 5442)
• PATIENT TEMPORARY ADDRESS START DATE (I EPT 5437)
• PATIENT TEMPORARY ADDRESS END DATE (I EPT 5438)
PID-12 - County Code
This field is for backwards compatibility only.
Profile Variables
• COUNTY_TABLE [3031]
Errors
• TABLE MAPPING ERROR FOR COUNTY [7455]
PID-13 - Phone Number – Home
Four formats are accepted. If the equipment type is not specified it defaults to the home phone.
Format: [nnn](nnn)nnn-nnnn^<Telecommunication use code>^<Telecommunication equipment type>^<E-
mail address>^<Country code>^<Area/city code>^<Local number>^<Extension>^<Any text>^<Extension
prefix>^<Speed dial code>^<Unformatted telephone number>
E-mail addresses as well as confidential and temporary contact numbers are not supported.
Profile Variables
• PHONE_CODE_TBL [9252]
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526

• COMM_EQUIP_TYPE_TBL [10278]
 Errors
• INVALID PHONE NUMBER [210]
• INVALID EMAIL ADDRESS [215]
• INVALID PHONE NUMBER: PATIENT PHONE [224]
• PHONE CODE COULD NOT BE MAPPED [774]
Database Location
• OTHER COMMUNICATION DEVICES (I EPT 94)
• PHONE 1 (I EPT 90)
• OTHER COMMUNICATION NUMBERS (I EPT 98)
PID-14 - Phone Number – Work
(nnn)nnn-nnnnx<extension>
or
^^^^^<City/area code>^<Number>^<Extension>
or
#<text>
Three formats are accepted.
[nnn](nnn)nnn-nnnn^^^^^^^<Extension>
^^^^<Country code>^<City/area code>^<Number>^<Extension>
#<text>
Errors
• INVALID PHONE NUMBER [210]
• INVALID PHONE NUMBER: PATIENT PHONE [224]
Database Location
• OTHER COMMUNICATION DEVICES (I EPT 94)
• OTHER COMMUNICATION NUMBERS (I EPT 98)
• WORK PHONE (I EPT 5170)
PID-15 - Primary Language
Formats:
• <Language>
• <Language>^^^^^^^^
This field can only be used for Identity Duplicate Checking.
The first component is used. All others are ignored.
Profile Variables
• LANGUAGE_TABLE [2562]
Errors
• PATIENT LANGUAGE COULD NOT BE MAPPED [2099]
• TABLE MAPPING ERROR FOR LANGUAGE [7675]
Database Location
• LANGUAGE (I EPT 155)
• LANGUAGE-SPOKEN (MR) (I EPT 146)
PID-16 - Marital Status
Profile Variables
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 • MARITAL_TABLE [327]
Errors
• TABLE MAPPING ERROR FOR MARITAL STATUS [7456]
Database Location
• MARITAL STATUS (I EPT 140)
PID-17 - Religion
Profile Variables
• RELIGION_TABLE [2561]
Errors
• TABLE MAPPING ERROR FOR RELIGION [7457]
Database Location
• RELIGION (I EPT 150)
PID-18 - Patient Visit Number
Configurable; Can be used to locate the visit to which the message should be associated.
Profile Variables
• ENCOUNTER_KEY [61]
• ACCOUNT_ID_LOOKUP [2481]
• ACCOUNT_ID_TYPE_DEFAULT [2484]
• ACCOUNT_ITEM [868]
Database Location
• SOCIAL SECURITY NUMBER (I EPT 160)
• CONTACT SERIAL NUMBER (I EPT 8)
• BILLING NUMBER (I EPT 17)
• VISIT HOSPITAL ACCOUNT (I EPT 2500)
PID-19 - SSN Number – Patient
Used for validation. Numeric with or without dashes.
National identifier can also be received in PID-3.
Profile Variables
• NAT_ID_BYPASS_FORMATTING [666]
Errors
• INVALID NATIONAL IDENTIFIER FORMAT [91524]
Database Location
• SOCIAL SECURITY NUMBER (I EPT 160)
PID-22 - Ethnic Group
This field is only used for R30 messages.
This field can only be used for Identity Duplicate Checking.
Profile Variables
• ETHNIC_GROUP_TABLE [1252]
• ETHNIC_GROUP_LOCATION [2728]
Errors
• INCOMING TABLE VALUE COULD NOT BE MAPPED [40000]
Database Location
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526

• ETHNIC GROUP (I EPT 135)

 • ETHNIC BACKGROUND (I EPT 134)
ORC - Order Common
Segment-Level Summary
Most of the information on the optional ORC segment is ignored by the Incoming Lab Instrument Results
Interface to Clinical Lab. Note that most of the information sent in this segment is also duplicated in the OBR
segment.

Element Name Type Usage Notes

1 - Order Control ID Required Supported Codes:
• RE - Observations to Follow
2 - Not Supported — — —
3 - Filler Order — Optional When integrating with stainer instruments, this field contains the vendor-
Number specified identifier.
4 - Not Supported — — —
5 - Not Supported — — —
6 - Not Supported — — —
7 - Not Supported — — —
8 - Not Supported — — —
9 - Not Supported — — —
10 - Not Supported — — —
11 - Not Supported — — —
12 - Not Supported — — —
13 - Not Supported — — —
14 - Not Supported — — —
15 - Not Supported — — —
16 - Not Supported — — —
17 - Not Supported — — —
18 - Entering Device CWE Optional —
19 - Not Supported — — —
20 - Not Supported — — —
21 - Not Supported — — —
22 - Not Supported — — —
23 - Not Supported — — —
24 - Not Supported — — —
25 - Stainer Order — — Stain Status
Status

ORC-1 - Order Control

Supported Codes:
• RE - Observations to Follow
Errors
• ORDER ALREADY EXISTS, NA MESSAGE WILL NOT BE SENT [2829]
• ORDER ALREADY EXISTS, BUT NA MESSAGE WILL BE SENT FOR SN [2871]
• UNEXPECTED CONTROL CODE [2912]
• CONTROL CODE NOT SUPPORTED [2967]
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 • INVALID ORDER CONTROL CODE [6123]
• INVALID STATUS FOR CONTROL CODE [6171]
ORC-18 - Entering Device
The second component of this field can contain the instrument messaging identifier (I MAC 51270). For stainer
status messages this is required as there is no OBX segment to pull the instrument messaging identifier from.
Errors
• NO METHOD MAC FOUND FROM MESSAGING IDENTIFIER [2953]
• METHOD MAC WAS INACTIVE [2985]
ORC-25 - Stainer Order Status
Stain Status
This field contains the status that will be used to log an event in Beaker. STAIN_STATUS_TBL (6866) is used to
map these status to events that will be logged to the specimen in Beaker.
Profile Variables
• STAIN_STATUS_TBL [6866]
Errors
• STAIN STATUS TABLE NOT FOUND [30106]
• INVALID STAIN STATUS [30105]
OBR - Observation Reports
Segment-Level Summary
The OBR segment is used to send information specific to each test order.

Element Name Type Usage Notes

1 - Not Supported — — —
2 - Not Supported — — —
3 - Not Supported — — —
4 - Not Supported — — —
5 - Not Supported — — —
6 - Not Supported — — —
7 - Observation Date/ DTM Optional —
Time
8 - Not Supported — — —
9 - Not Supported — — —
10 - Not Supported — — —
11 - Not Supported — — —
12 - Not Supported — — —
13 - Not Supported — — —
14 - Not Supported — — —
15 - Not Supported — — —
16 - Not Supported — — —
17 - Not Supported — — —
18 - Not Supported — — —
19 - Placer Field 2 ST Optional When integrating with stainer instruments, this field contains the slide or
container ID.
20 - Not Supported — — —
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
 Element Name Type Usage Notes
21 - Filler Field 2 ST Optional This field contains the specimen information.

OBR-7 - Observation Date/Time

Stainer Order Status Date/Time
For information about filing status updates from stainers, refer to the File Status Updates from Stainers topic.
Errors
• INVALID DATE [504]
• COLLECTION TIME OCCURS IN THE FUTURE [864]
• COLLECTION TIME IS OLDER THAN 14 DAYS [865]
• MULTIPLE COLLECTION DATES AND TIMES RECEIVED [866]
• CANNOT UPDATE COLLECTION DATE AND TIME [867]
Database Location
• EVENT INSTANT (I OVC 51064)
OBR-19 - Placer Field 2
When integrating with stainer instruments, this field contains the slide or container ID.
This field contains the container ID which is the Beaker Identity ID for the contain and a trailing container
identified.
Errors
• MISSING CONTAINER ID [30102]
OBR-21 - Filler Field 2
This field contains the specimen information.
This field can contain the specimen ID and trailing specimen identifier.
 
 
 
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526
   2022 Epic Systems Corporation. All rights reserved. PROPRIETARY INFORMATION - This item and its contents may not
©
be accessed, used, modified, reproduced, performed, displayed, distributed or disclosed unless and only to the extent
expressly authorized by an agreement with Epic. This item is a Commercial Item, as that term is defined at 48 C.F.R. Sec.
2.101. It contains trade secrets and commercial information that are confidential, privileged and exempt from disclosure
under the Freedom of Information Act and prohibited from disclosure under the Trade Secrets Act. After Visit Summary,
Analyst, App Orchard, ASAP, Beacon, Beaker, BedTime, Bones, Break-the-Glass, Caboodle, Cadence, Canto, Care
Everywhere, Charge Router, Chronicles, Clarity, Cogito ergo sum, Cohort, Colleague, Community Connect, Cupid, Epic,
EpicCare, EpicCare Link, Epicenter, Epic Earth, EpicLink, EpicWeb, Garden Plot, Good Better Best, Grand Central, Haiku,
Happy Together, Healthy Planet, Hyperspace, Kaleidoscope, Kit, Limerick, Lucy, Lumens, MyChart, OpTime, OutReach,
Patients Like Mine, Phoenix, Powered by Epic, Prelude, Radar, Radiant, Resolute, Revenue Guardian, Rover, Share
Everywhere, SmartForms, Sonnet, Stork, System Pulse, Tapestry, Trove, Welcome, Willow, Wisdom, and With the Patient at
Heart are registered trademarks, trademarks, or service marks of Epic Systems Corporation in the United States of America
and/or other countries. Other company, product, and service names referenced herein may be trademarks or service marks
of their respective owners. Patents Notice: [Link]/patents.
EpicUUID: 57C9C77A-6F0B-4423-807A-D59F3DF1B526