Professional Documents
Culture Documents
Adt Specification and Sample Messages
Adt Specification and Sample Messages
Adt Specification and Sample Messages
Thank you for reviewing the athenahealth native HL7 data structure. This document identifies the data
athenahealth capture by default and the fields/components in which they are expected (inbound
messages to athena) and sent (outbound messages from athena). On the 'Outbound Patients',
'Outbound Appointments', and 'Inbound Charges' tabs, note that the first component of a field is
denoted with a null value in the 'Component' column, and a row with "1" in the 'Component' column
would actually be the second component of that field.
Example: PID.10 is for Patient Race and is identified as PID10.0 = Race ID, PID10.1 = Race ID Name.
PID||||||||||RACEID^RACEIDNAME|
Version: 16.7
Last Updated: 7/25/2016
Table of Contents
Outbound Patients Provides the layout of the HL7 message type(s) that athena uses
by default to send New Patient and Patient Update messages.
Inbound Patients Provides the layout of the HL7 message type(s) that athena
expects by default to receive New Patient and Patient Update
messages.
Inbound Admit & Discharge Provides the layout of the HL7 message type(s) that athena
expects by default to process Admit and Discharge events into
athenaNet.
Message Layout by Category For each of the message categories that athena supports, this
tab provides a quick reference segment breakdown - required
segments, optional segments, repeatable segments, and the
expected ordering of the segments.
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
h this ID to an NPI in the appropriate client's tablespace. If that match fails it will attempt to match to an athenaNet provider ID, and if that
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
arator, respectively.
Net provider ID, and if that also fails then a mapping task will be triggered to associate the foreign ID to an athenaNet provider ID.
athenaNet provider ID.
Table of Contents
MSG Category Direction MSG TYPE Segment = Field (0.0)
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 MSH
ADT IN A01-A03, A04-A07 EVN
ADT IN A01-A03, A04-A07 EVN
ADT IN A01-A03, A04-A07 EVN
ADT IN A01-A03, A04-A07 EVN
ADT IN A01-A03, A04-A07 EVN
ADT IN A01-A03, A04-A07 EVN
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A04,A08,A28,A31 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PID
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV1
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 PV2
ADT IN A01-A03, A04-A07 GT1
ADT IN A01-A03, A04-A07 IN1
ADT IN A01-A03, A04-A07 IN2
ADT IN A01-A03, A04-A07 IN3
In the MSH
athena segment
expects the HL7
only, the pipe delimiter
recommended values of
'|' thatThese
^~\&. immediately
are the
follows
component the 'MSH'
separator,
segment
repititionheader is
separator,
Field Component athena Field / Expected Value
considered Notes
the first field
escape character, and
1 0 Field Separator of the segment.
subcomponent
2 0 ^~\& separator, respectively.
3 0 Sending Application Source_Vendor
4 0 Sending Facility Source_Vendor
Standard Format (e.g.
5 0 Receiving Application 'ATHENANET')
6 0 athenaNet Context ID
6 1 Context Name
7 0 Message Timestamp Standard Format
8 0 ** NOT USED **
9 0 Message Category Standard Format
9 1 Message Type Standard Format
10 0 Message ID Standard Format
11 0 Processing ID Standard Format
12 0 HL7 Version Standard Format
13 0 ** NOT USED **
14 0 ** NOT USED **
15 0 ** NOT USED **
16 0 ** NOT USED **
17 0 ** NOT USED **
18 0 ** NOT USED **
19 0 ** NOT USED **
20 0 ** NOT USED **
1 0 Event Type (Message TypeStandard Format
2 0 Recorded/Creation Date Standard Format
3 0 ** NOT USED **
4 0 ** NOT USED **
5 0 ** NOT USED **
6 0 ** NOT USED **
1 0 Set ID - PID External vendor patient
2 0 CUSTOM.PID2DATA id,
It isMRN
used or other
for
Sent to patientmatc
backagreed
mutually athena if
2 1 ** NOT USED ** Authority
the other used toupon
vendor's
ID, oftenthe
identify used for
source
3 0 External Patient ID (Sendesytem
patient
system
ismatching.
storing
which
it. New
generates
patients to athena
3 2 Patient ID Assigning Authothis
would ID not
number
have this
4 0 athenaNet Patient ID filled.
5 0 Patient's Last Name Standard Format
5 1 Patient's First Name Standard Format
5 2 Patient's Middle Initial
5 3 Patient's Name Suffix Standard Format
6 0 ** NOT USED **
7 0 Patient's Date of Birth
8 0 Patient's Sex Male/Female
9 0 ** NOT USED ** Must be mapped to
10 0 Patient's Race Code athena global value
Please be aware if you
update a patient’s email
address in Quickview,
they’ll
"Foreign need to re-
Value"
10 1 Patient's Race Name register to your
associated with mapping
organization’s Patient
11 0 Address Line 1 Portal at the new email
11 1 Address Line 2 address and will not be
11 2 Patient's Address City able to access that
Patient Portal using the
11 3 Patient's Address State athenahealth account
11 4 Patient's Address Zip associated with the
previous email address.
11 5 Patient's Address CountryAn Name
email#########,
invitation to
Format:
12 0 ** NOT USED ** the Patient Portal###-
(###)###-####, is
Format: #########,
automatically sent to the
13 0 Patient's Phone Number ###-####
(###)###-####, ###-
new email address when
13 1 Patient's Phone Number -###-####
an
Format: #########,for
email is updated
13 2 Patient's Email an existing portal###-
(###)###-####, user
14 0 Patient's Phone Number ###-####
Must be mapped to
15 0 Patient's Primary Langua athena
"ForeignGlobal
Value"value
15 1 Patient's Primary Langua associated
Must be mapped with mapping
to
16 0 Patient's Marital Status C athena
"Foreign Value"value
Global
16 1 Patient's Marital Status I associated with mapping
17 0 ** NOT USED **
18 0 Visit Number
19 0 Patient's SSN
20 0 PATIENT.LICENSESTATEID/ PATIENT.LICENSENUMBE
21 0 ** NOT USED ** Must be mapped to
22 0 Patient's Ethnic Group ID athena
"ForeignGlobal
Value"value
22 1 Patient's Ethnic Group N associated with mapping
1 0 Set ID - PV1 the athenaNet MX
2 0 Patient Class engine will try to match
3 0 Rounding Department this ID to an NPI in the
appropriate client's
3 1 Room Number tablespace. If that match
3 2 Bed Number fails it will attempt
the athenaNet MX to
match
engine to an athenaNet
will try to match
3 3 Patient's Primary Department
providerName ID,
4 0 this ID
VISIT.ADMISSIONTYPEID also fails thento an and
NPI if
inthat
the
appropriate client's a mapping
5 0 ** NOT USED ** task will be triggered
tablespace. to
If that match
associate the foreign
fails it will attempt to ID
6 0 ** NOT USED ** to an athenaNet
match to an athenaNet
7 0 Primary Provider's ID provider
provider ID. ID, and if that
7 1 Attending Provider's Last Name
also fails then a mapping
7 2 Attending Provider's First task
Name will be triggered to
associate the foreign ID
7 3 Primary Provider's MiddletoInitial
an athenaNet
8 0 Referring Provider's ID provider ID.
8 1 Referring Provider's Last Name
8 2 Referring Provider's First Name
8 3 Referring Provider's Middle Initial
9 0 ** NOT USED **
10 0 ** NOT USED **
11 0 ** NOT USED **
12 0 ** NOT USED **
13 0 ** NOT USED **
14 0 VISIT.ADMISSIONSOURCEID
15 0 ** NOT USED **
16 0 ** NOT USED **
17 0 Admitting Provider
18 0 VISIT.LEVELOFCAREID
19 0 ** NOT USED **
20 0 ** NOT USED **
21 0 ** NOT USED **
22 0 ** NOT USED **
23 0 ** NOT USED **
24 0 ** NOT USED **
25 0 ** NOT USED **
26 0 ** NOT USED **
27 0 ** NOT USED **
28 0 ** NOT USED **
29 0 ** NOT USED **
30 0 ** NOT USED **
31 0 ** NOT USED **
32 0 ** NOT USED **
33 0 ** NOT USED **
34 0 ** NOT USED **
35 0 ** NOT USED **
36 0 VISIT.DISCHARGEDISPOSITIONID
37 0 ** NOT USED **
38 0 ** NOT USED **
39 0 ** NOT USED **
40 0 ** NOT USED **
44 0 Admit Date
45 0 Discharge Date
1 0 SET ID - PV2
2 0 VISIT.ACCOMMODATIONID
3 0 Admit Reason
4 0 Transfer Reason
5 0 ** NOT USED **
6 0 ** NOT USED **
7 0 ** NOT USED **
8 0 ** NOT USED **
9 0 ** NOT USED **
10 0 ** NOT USED **
11 0 ** NOT USED **
12 0 Visit Description
13 0 ** NOT USED **
14 0 ** NOT USED **
15 0 ** NOT USED **
16 0 ** NOT USED **
17 0 ** NOT USED **
18 0 ** NOT USED **
19 0 ** NOT USED **
20 0 ** NOT USED **
21 0 ** NOT USED **
22 0 ** NOT USED **
23 0 ** NOT USED **
24 0 ** NOT USED **
25 0 ** NOT USED **
26 0 ** NOT USED **
27 0 ** NOT USED **
28 0 ** NOT USED **
29 0 ** NOT USED **
30 0 ** NOT USED **
## 0 Segment Not Used
## 0 Segment Not Used
## 0 Segment Not Used
## 0 Segment Not Used
Expected by Default
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Table of Contents
ADT^A28 New Patient Message
MSH|^~\&|ATHENANET|99999^MA - athenahealth Testing^1^Test Clinic|TestInterface||201505181454||ADT^A28|211M900
EVN|A28|201505180254|||username
PID||123456|123456|123456|PATIENTLASTNAME^PATIENTFIRSTNAME||19900101|M|||^^^^^UNITED STATES||(111)111-1
PV1|||2^TEST DEPARTMENT^^TEST DEPARTMENT||||12345678^SEUSS^DOCTOR||||||||||12345678^SEUSS^DOCTOR
GT1|1||PATIENT^TEST||^^^^^UNITED STATES|(111)111-1111||19880601|||Self
GENCY CONTACT|(EChomephone||PARENT
9||||||||||12345|||||||M
mail.com^NET^^Patientemail@email.com~(222)222-2222^ORN^CP^^1^222^2222222|(333)333-3333^WPN^PH^^1^333^3333333|eng^
3^3333333|eng^English|S|||000000000||ATHENA|2186-5^Not Hispanic or Latino
If applicable
If applicable
If applicable
Not required for the interface to process, but will be processed by default if present
Not required for the interface to process, but will be processed by default if present
Not required for the interface to process, but will be processed by default if present
Not required for the interface to process, but will be processed by default if present
Not required for the interface to process, but will be processed by default if present
Not required for the interface to process, but can be processed
Table of Contents
Legend:
Red Fill Required Segment
Yellow Fill Optional Segment []
Blue Fill Required and Repeatable Segment {}
Green Fill Optional and Repeatable Segment [{}]
Updated (6/19/17)
ADT (A04/A08/A28/A31) Category Message Layout
Segment Definition
MSH Message Header
[ EVN ] Event Type
PID Patient Identification
[ PD1 ] Additional Demographics
[ { NK1 } ] Next of Kin /Associated Parties
PV1 Patient Visit
[ PV2 ] Patient Visit - Additional Info.
[ { DB1 } ] Disability Information
[ { OBX } ] Observation/Result
[ { AL1 } ] Allergy Information
[ { DG1 } ] Diagnosis Information
[ DRG ] Diagnosis Related Group
[{
PR1 Procedures
[ { ROL } ] Role
}]
[ { GT1 } ] Guarantor
[{
IN1 Insurance
[ IN2 ] Insurance Additional Info.
[ { IN3 } ] Insurance Additional Info - Cert.
[ ACC ] Accident Information
}]
[ UB1 ] Universal Bill Information
[ UB2 ] Universal Bill 92 Information
15.5 5/8/2015
15.5 5/13/2015
15.5 5/18/2015
15.8 8/15/2015
15.12 12/11/2015
16.7 7/25/2016
3/8/2017
Changes
Initial formatting and layout design. Previously this document was in MS Word.
> Changed the 'Read Me' tab to 'Table of Contents' and added the table of contents.
> Split the 'Message Breakdown' tab into three tabs: Outbound Patients; Outbound
Appointments, and Inbound Charges, and corrected some issues in the 'athena Field'
columns.
> Updated the 'Message Layout by Category' tab.
> Added the 'Minimum Requirements - Inbound' tab.
> Removed ORU specification. Lab result messages are currently available in another
document.