HL7 Interface Specification Merge LabAccess v. 3.6



Similar documents
Generic EHR HL7 Interface Specification Abraxas v. 4

HL7 Interface Specification Merge Eye Station v. 11.3

HL7 Conformance Statement

ELR Clarification Document for EHR Technology Certification

HL7 Fundamentals. Presented by: Dana McDonough, Carolina Velasquez, & Bing Chen. August 2014

HL7 Interface Specification. HL7 Interface 1.2

ImagePilot. HL7 Conformance Statement. Manufacturer: 1 Sakura-machi, Hino-shi Tokyo , Japan

JiveX Enterprise PACS Solutions. JiveX HL7 Gateway Conformance Statement - HL7. Version: As of

HL7 Interface Specifications

ELR Clarification Document for EHR Technology Certification V1.1

Philips Innovation Campus Bangalore India. Issued by:

HL7 EHR to PowerSoftMD Visit Import Specifications

HL7 Conformance Statement

HL7 Conformance Statement RadCentre. Release

20/20 Integration Guide

Interfacing Boot Camp

AIDA compact NEO HL7 Interface Description

RamSoft PACS 3.0 HL7 Conformance Statement

Merge Healthcare Virtualization

HL7 Customization Guide

Message Specifications Guide

Masimo Patient Safetynet HL7 Interface Specifications

ZAN HL7 Interface. Installation and Specifications Manual Part Number : *************ENG Version / Revision : A

How To Get A Medical Record On A Medical Device

DIAGNOSTIC TEXT AND OTHER TRANSCRIBED REPORTS MESSAGE SPECIFICATION

Connecticut Department of Public Health Electronic Laboratory Reporting HL7 v2.5.1 Message Validation Tool User Guide

DICOM Conformance Statement Merge Eye Care PACS v. 4.0

Overview. LATITUDE Patient Management. EMR Integration Testing Scenarios

LIS Interfaces: Basics, Implementation and Pitfalls

D* SEE SAP DIR DIGITAL SIGNATURE LOG FOR APPROVER NAME AND DATE OF APPROVAL

Introduction to Epic Bridges. Empowering Extraordinary Patient Care

UHIN STANDARDS COMMITTEE Version 2.0 Radiology Report Standard

HL7 Format and Electronic Sharing

HL7 ADT, ORM and ORU & DICOM tag agreement with RIS, PACS and VNA

HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA

Notes Interface Specification HL7 format

A method for handling multi-institutional HL7 data on Hadoop in the cloud

Additional Information Message Implementation Guide

LIS Interfaces: Basics, Implementation, and Pitfalls

Quickly and easily connect your Imaging System with Practice Fusion s Electronic Health Record (EHR) System. HL7 Results Specification

HealthLink Messaging Technology

Bi-Directional Interface between EMR and Quest Diagnostics Microsoft.NET with SQL Server Reporting Services solution for Healthcare Company

Meaningful Use Business Process Mapping Questionnaire. Meaningful Use Business Process Mapping Questionnaire. Contact Information

Interoperability and Integrating the Healthcare Enterprise

IHE Radiology Technical Framework Volume 3 (IHE RAD TF-3)

HL7 Interconnection Guide v1.1

Implementation Guide for Transmission of. Microbiology Result Messages. as Public Health Information using. Version of the

EHR-Laboratory Interoperability and Connectivity Specification (ELINCS) Version 0.2 DRAFT

RelayClinical Service Feature Guide RelayClinical Notify

Deployment Planner. inexx Novo Grid Practice Agent HW Requirements.pdf

ShadowLink 2. Overview. May 4, ONLINE SUPPORT emdat.com/ticket/ PHONE SUPPORT (608) ext. 1

Implementation Guide

IHE Patient Care Device Technical Framework Supplement. Medical Equipment Management Device Management Communication (MEMDMC) Trial Implementation

PMS / EMR Message Specification (Version 2.3.1) (ADT, AL1, OBX, SIU, DFT, PPR (PRB), ORM, VXU)

The Benefits of Using InterSystems Ensemble within the Saint Pierre Hospital

CLIA and EHRs CLIA. Judith Yost Director, Division of Laboratory Services

A Development of HL7 Middleware for Medical Device Communication

HL7 Conformance Checking with Corepoint Integration Engine

IHE Radiology (RAD) Technical Framework. Volume 2 IHE RAD TF-2 Transactions

IHE Radiology Technical Framework Supplement. Clinical Decision Support Order Appropriateness Tracking (CDS-OAT) Trial Implementation

1. What is your name? Last name First name Middle Initial Degree(s)

Welch Allyn Connectivity Server

Oracle SOA Suite 11g Oracle SOA Suite 11g HL7 Inbound Example Functional ACK Addendum

Reduces development time by 90%

Generic Interface System

7. Observation Reporting

HL7 & KMEHR. A comparison. Medical informatics AJ 2013/2014. Authors: Tessa Borloo Nele Pien

STEP 2 IMPLEMENTATION: HIE TOOLS USER GUIDE HIE TOOLS USER GUIDE

Connex Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software -

Design of Internet Protocols:

MHS EMR Program. EMR HIE Integration Toolkit

Conformance Testing of Healthcare Data Exchange Standards for EHR Certification

Michigan Pulse Oximetry Screening for Critical Congenital Heart Disease

Test Procedure for (b)(6) Transmission of electronic laboratory tests and values/results to ambulatory providers inpatient setting only

Medicalis Workflow HL7 to SQL Specification

Medical device security

HIE Ready 2.0 SPECIFICATIONS MATRIX. Product Name: Version Number: Preferred Message and Trigger

Clinical Document Exchange Integration Guide - Outbound

Michigan Care Improvement Registry HL Specification for Vaccination Messages. Document Description

New Jersey Department of Health. Electronic Laboratory Reporting On-Boarding Manual. Version 1.4

Location of digital signatures in healthcare messaging

PARCA Certified PACS Interface Analyst (CPIA) Requirements

Text Integration Utilities (TIU) Generic HL7 Interface Handbook

Investor Presentation. June 2014

Patient Demographics Query (PDQ)

DICOM, HL7, RIS, PACS

LATITUDE Patient Management. Purpose. Objectives

NURSING INFORMATICS. Nikole L. Farmer, MSN, RN, PMP September 6, 2014

MOSAIQ External Systems Interfaces (ESI) Product Offerings

How To Use An Electronic Data Exchange (Edi)

Transcription:

HL7 Interface Specification Merge LabAccess v. 3.6 Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 USA 877.44.MERGE

12 Merge Healthcare. The information contained herein is confidential and is the sole property of Merge Healthcare. None of the information may be reproduced, copied, and/or re-distributed electronically, manually, or otherwise to any person without advance written permission from Merge Healthcare, except as may be expressly authorized by contracts or other agreements between Merge Healthcare and its customer. Merge Healthcare and AMICAS are registered trademarks and VERICIS, RadSuite, Abraxas, and iconnect are also trademarks of Merge Healthcare. Other trademarks or service marks referred to herein are the property of their respective owners. Doc # Revision Date Description LNK-383 1 10/29/12 Initial release for 3.6.

Introduction Purpose This document presumes the reader has a working knowledge of the HL7 Version 2.3* interface specification. The HL7 specification is available through: Health Level Seven 3300 Washtenaw Ave. Suite 227 Ann Arbor, MI 48104-4250 Office: (313) 677-7777 FAX: (313) 677-6622 For questions specific to the enclosed documentation, please contact Merge Healthcare Technical Assistance at 877-44-MERGE. * PID-35 and PID-36 are compliant with the HL7 Version 2.4 interface specification. 1 of 12

HL7 Messages Orders The following describes the message structure for the Merge LabAccess HL7 Orders interface. ORM event O01 - general order message: MSH PID [{NTE}] [PV1] [ORC] { OBR } NOTE: Any segments not listed are ignored. Data Exchange Method HL7 Orders files are expected to be written to the computer where Merge LabAccess is installed at the following path: C:\LabAccess\HL7Files\Orders Any changes to this path must be approved in writing by Merge Healthcare. NOTE: File IO is the preferred method of data exchange. Socket connections are also available if the host vendor does not support a File IO. Table 1: MSH Segment (Required) Field # Field name Length Notes Required 1 Field Separator 1 ' ' R 2 Encoding Characters 4 Example: ^~\& If data is sent that contains the encoding characters the escape sequence must be supported. Since some user data may contain these special delimiter characters HL7 has a system for escaping them. See Note 1. 2 of 12

Table 1: MSH Segment (Required) Field # Field name Length Notes Required 9 Message Type 3^3 "ORM^O01" R 10 Message Control ID Unique sequential number; returned in acknowledgement 15 Accept Acknowledgement Type 2 "NE" or "AL. AL value will send ACK. Table 2: PID Segment (Required) Field # Field name Length Notes Required 1 Set ID 4 Sequential number starting at '1' 2 Patient ID (external) Used as displayed patient ID if the host's "Use PID.2 as Patient ID" parameter is set to "true". If parameter is set to "false", the PID.2 value (if any) will be stored by LabAccess and returned in PID.2 with results output. 3 Patient ID (internal) Used as displayed patient ID if the host's "Use PID.2 as Patient ID" parameter is set to "false". If parameter is set to "true", the PID.3 value (if any) will be stored by LabAccess and returned in PID.3 with results output. *C *C 5 Patient Name 30^30^ 30 Last name^first name^ middle name 7 Date/Time of Birth 14 8 Sex 1 'M', 'F', 'U', or 'O' 35 Species 40 Must have a value if PID-36 has a value 36 Breed 40 Table 3: PV1 Segment Field # Field name Format Notes Required 1 Set ID 1 '1' 2 Patient Class 1 'R' 7 Attending Doctor ^^ Code^ Last Name^First Name. Saved as ordering doctor if OBR.16 is NOT present. See Note 2. 3 of 12

Table 3: PV1 Segment Field # Field name Format Notes Required 8 Referring Doctor ^^ 9 Consulting Doctor ^^ 17 Admitting Doctor ^^ Code^ Last Name^First Name Code^ Last Name^First Name Code^ Last Name^First Name 19 Visit Number Visit Number Table 4: ORC Segment Field # Field name Format Notes Required 1 Order Control 2 NW 4 Placer Group Number 25 Saved as LabAccess Lab Number if parameter "Use OBR.2 as group" is set to "false". 12 Ordering Provider ^^ Code^Last Name^First Name Table 5: OBR Segment (Required) Field # Field name Format Notes Required 1 Set ID 3 Sequential number starting at '1' 2 Placer Order Number 25 Saved as LabAccess Lab Number if parameter "Use OBR.2 as group" is set to "true". If parameter is set to "false", save as placer order number. R 4 Test ID Test Code R 6 Order Date/Time 14 7 Draw Date/Time 14 16 Ordering Provider ^^ Code^Last Name^First Name; saved as ordering provider. If not present, PV1.7 is saved as ordering provider. See Note 2. 4 of 12

Note 1: Escape Sequence Table: Character Type Escape Sequence & Subcomponent separator \T\ ^ Component separator \S\ Field separator \F\ ~ Repeat separator \R\ \ Escape character \E\ Note 2: Doctor Code will be created if it does not exist in the system. 5 of 12

Results The following describes the protocol for the Merge LabAccess Results HL7 format. ORU event R01 - transmission of results; supported for output only. MSH PID [PV1] { [ORC] OBR { OBX [{NTE}] } } Data Exchange Method HL7 Results files MUST be written to the Merge LabAccess computer C Drive to the following path: C:\LabAccess\HL7Files\Results with the.out extension. NOTE: File IO is the preferred method of data exchange. Socket connections are also available if the host vendor does not support a File IO. Table 6: MSH Segment Field # Field name Length Notes 1 Field Separator 1 ' ' 2 Encoding Characters 4 '^~\&' If data is sent that contains the encoding characters the escape sequence must be supported. Since some user data may contain these special delimiter characters HL7 has a system for escaping them. See Note 1. 3 Sending Application 12 LabAccess 4 Sending Facility 30 Merge 5 Receiving Application 30 Test 6 of 12

Table 6: MSH Segment Field # Field name Length Notes 6 Receiving Facility Receiver 7 Date-Time of Message 14 Date/time output file was created 9 Message Type 3^3 "ORU^R01" 10 Message Control ID 10 sequential number 11 Processing ID 1 'P' = production, 'T' = test 12 Version ID 3 "2.3" 15 Accept Acknowledgement Type 16 Application Acknowledgement Type 2 "NE 2 "NE" Table 7: PID Segment Field # Field name Length Notes 1 Set ID 4 Sequential number starting at '1' 2 Patient ID (Internal) Patient ID 3 Patient ID (External) Patient ID 5 Patient Name 30^30^ 30 Last name^first name^ middle name 7 Date of Birth 8 Only sent if entered 8 Sex 1 Only sent if entered 'M', or 'F', 'U' or 'O' 35 Species 40 Must have a value if PID-36 has a value 36 Breed 40 Table 8: PV1 Segment Field # Field name Format Notes 1 Set ID 1 '1' 2 Patient Class 1 'R' 7 Attending Doctor ^^ Code^ Last Name^First Name. LabAccess ordering doctor 8 Referring Doctor ^^ Code^ Last Name^First Name; output if received with Order 7 of 12

Table 8: PV1 Segment Field # Field name Format Notes 9 Consulting Doctor ^^ 17 Admitting Doctor ^^ Code^ Last Name^First Name; output if received with Order Code^ Last Name^First Name; output if received with Order 19 Visit Number Visit Number Table 9: NTE Segment Field # Field name Length Notes 1 Set ID 2 Sequential number starting at '1' 3 Comment 80 Text comment Table 10: ORC Segment Field # Field name Format Notes 1 Order Control 2 'RE' 2 Placer Order Number 25 Order number. LabAccess Accession Results Only. Placer Order Number if insert from Orders interface. 3 Filler Order Number 25 Order number. LabAccess Accession with Results Only. Placer Order number if insert from Orders interface. 4 Placer Group Number 25 Returned if parameter "Use OBR.2 as group" is set to "false". 9 Date/Time of Transaction 14 12 Ordering Provider ^^ Code^Last Name^First Name Table 11: OBR Segment Field # Field name Format Notes 1 Set ID 2 Sequential number starting at '1' 2 Placer Test Number 25 Accession number - Placer order number if received with Orders interface, otherwise, LabAccess Accession number. 3 Filler Order Number 25 Accession number - Placer order number if received with Orders interface, otherwise, LabAccess Accession number. 4 Test ID 8 Test Code 8 of 12

Table 11: OBR Segment Field # Field name Format Notes 6 Order Date/Time 14 7 Observation Date/Time 14 8 Observation Date/Time 14 14 Specimen Received Date/ Time 14 16 Ordering Provider ^^ Code^Last Name^First Name; saved as ordering provider. 25 Result Status 1 'F' = final results Table 12: OBX Segment Field # Field name Format Notes 1 Set ID 1 Sequential number starting at '1' 2 Value Type 2 "NM", "ST", TX, or "FT" 3 Result code 8 5 Observation Value 500 Numeric, or alpha 6 Units 10 Units 7 Reference Range 17 Reference range for numeric procedure 8 Abnormal Flags 2 'L' = below low normal; 'H' = above high normal; 'LL' = below lower panic limits; 'HH' = above upper panic limits; 'N' = normal; 'A' = abnormal (non-numeric result); 'AA' = very abnormal (nonnumeric result) 11 Result Status 1 'F' = final result 14 Result date/time 14 Date/time that result was generated (not when result was verified) 16 Accepting Tech 4 Accepting Tech 9 of 12

Note 1: Escape Sequence Table: Character Type Escape Sequence & Subcomponent separator \T\ ^ Component separator \S\ Field separator \F\ ~ Repeat separator \R\ \ Escape character \E\ 10 of 12

HL7 Example Message Formats Order Example MSH ^~\& ORM^O01 PID 1 12345678901234561 989978 TEST^FIRST^M 19990101 M OBR 1 1609908 GLU^GLU Result Example From Results Only Interface MSH ^~\& LabAccess Main Lab Test Receiver 08100811 ORU^R01 1 P 2.3 NE NE PID 1 1234567890 1234567890 PATIENT^TEST^A 19651212 F NTE 1 THIS IS A COMMENT FOR TEST PATIENT PV1 1 1234567890^TEST^DOCTOR^^^^^L ^^^^^^^L ^^^^^^^L ^^^^^^^L ORC RE 2 2 0810081150 ADMIN 1234567890^TEST^DOCTOR^^^^^L OBR 1 2 2 LYTES 0 0810081150 0810081151 0810081151 0810081150 1234567 890^TEST^DOCTOR^^^^^L F OBX 1 NM NA 150 mmol/l 135-145 H F 0810081151 ADMIN NTE 1 Result rechecked. OBX 2 NM K 4.5 mmol/l 3.5-5.5 F 0810081151 ADMIN OBX 3 NM CL 100 mmol/l 95-110 F 0810081151 ADMIN From Results and Orders Interface MSH ^~\& LabAccess Main Lab Test Receiver 0810081217 ORU^R01 3 P 2.3 NE NE PID 1 12345.0 12345.0 Lst0000^First^J 0711 M NTE 1 PV1 1 2222^SMITH^JACK^^^^^L 3333^JONES^ROBERT^^^^^L ^^^^^^^L ^^^^^^^L 10102 ORC RE 123459 123459 081008121515 2222^SMITH^JACK^^^^^L OBR 1 123459 123459 GLU 0 081008121515 081008121611 081008121611 081008121515 2222^SMITH^JACK^^^^^L F OBX 1 NM GLU 100 75-100 F 081008121611 ADMIN ORC RE 123459 123459 081008121515 ^^^^^^^L OBR 2 123459 123459 LYTES 0 081008121515 081008121634 081008121634 0810081215 15 2222^SMITH^JACK^^^^^L F OBX 1 NM NA 155 mmol/l 135-145 H F 081008121634 ADMIN NTE 1 Result rechecked. OBX 2 NM K 4.5 mmol/l 3.5-5.5 F 081008121634 ADMIN OBX 3 NM CL 100 mmol/l 95-110 F 081008121634 ADMIN 11 of 12

Available Host Interfaces Vendor Orders Results ADT AiMed X Allegiance MD X X Allscripts X X Centricity X X eclincal X X InteliChart X X Medicat X X MediSoft X Misys X X Office Ally EHR X X Onco EMR X X X Praxis X Praxis X Raintree EMR X X Stratus X 12 of 12