HL7 Implementation for

Athena Technologies

Overview

This document describes the specific details of the HL7 implementation at Athena Technologies. This includes descriptions of how HL7 fields are used within the context of TMC systems.

General Interface Description

This section applies to all systems.

Separators

DelimiterValue
Segment Terminator<cr>
Field Separator|
Component Separator^
Sub-Component Separator&
Repetition SeparatorCollection of segments

Data Type Descriptions

These are restrictions on the contents of the data field. There are a number of data type defined by HL7. For a complete breakdown see Data Type Descriptions.

External Systems

For each external system, the list of the possible HL7 event types is listed. If a system requires additions to the standard messages, those enhancements should be added to the Message and/or Segment definitions in the later sections.

ADT System

The ADT system supports origination of the following message types:

ADT EventHL7 Event
adtCancelAdmissionA11
adtChangeAdmitDateA08
adtCorrectDischargeA08
adtDrConsultA08
adtErBedRevisionA20
adtErDrRevisionA08
adtErPatStatusTransferA06 (OP to IP), A07 (IP to OP)
adtErRegistrationA04
adtErRegRevisionA08
adtFcEffDateChange ?
adtIpAdmissionA01
adtIpDischargeA03
adtIpDrRevisionA08
adtIpRevisionA08
adtMedRecRevisionA08
adtOpBedRevisionA20
adtOpDrRevisionA08
adtOpErProcCodes?
adtOpErServiceChange?
adtOpPatStatusTransfer A06 (OP to IP), A07 (IP to OP)
adtOpRegistrationA04
adtOpRevisionA08
adtPatStatusTransferA06 (OP to IP), A07 (IP to OP)
adtPatTransferA02
adtPurgePatient A23
adtSspAdmissionA01
adtSspDischargeA03

Lab System

The Lab system supports origination of the following message types:

Lab EventHL7 Event
Lab resultORU (Unsolicited observation)

Elcomp

Radiology

Message Definition

This section lists all the HL7 messages as implemented by TMC and the data warehouse. Additional segments added to messages should be named "Zxx" to comply with HL7 standards.

Segment Definition

This section lists and defines the segments that may be used in the messages listed in the previous section. The segment definition provides detailed information about the fields contained in each segment. This definition identifies optional fields that will be used in each message, the characteristics of each field used, and the name of the variable assigned to the corresponding data in each application.

The segment checklist includes the following definitions:

Segment Name

Item Number

Name

Required/Optional Indicator. Required fields are marked with an 'R.' A blank line is provided to

indicate optional fields which will be included in the segment.

Data Type

Field Length

- Maximum Length Used

- Maximum Length Specified by Standard

Repetitions. If repetitions are allowed, a line is provided to indicate the number of repetitions

used in the interface.

Sender System's Variable Name

Receiver System's Variable Name

Notes. If the field uses a table, the table number is provided in parentheses.

A blank field line is included at the bottom of each segment to define any site-specific 'Z' fields being used.


For more Information please e-mail Eric Washburn.
Copyright 1996, Athena Technologies. All rights reserved.