834 Transaction Set Listing

008020X318 Plan Member Reporting
Usage
Repeats

ISA - INTERCHANGE CONTROL HEADER

X12 Name:
Interchange Control Header
X12 Purpose:
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
  1. For compliant implementations under this implementation guide, ISA13, the Interchange Control Number, must be a positive unsigned number. Therefore, the ISA segment can be considered a fixed record length segment.
  2. The first element separator defines the element separator to be used through the entire interchange.
  3. Spaces in the example interchanges are represented by "." for clarity.
  4. The ISA segment terminator defines the segment terminator used throughout the entire interchange.
  5. All positions within each of the data elements must be filled.
TR3 Example:
ISA✱00✱..........✱01✱SECRET....✱ZZ✱SENDERS.ID.....✱ZZ✱RECEIVERS.ID...✱030101✱1253✱^✱00802✱000000905✱0✱T✱:~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
I01
Authorization Information Qualifier
M 1
ID
2
Code identifying the type of information in the Authorization Information
CODE
DEFINITION
00
No Authorization Information Present (No Meaningful Information in I02)
03
Additional Data Identification
Required
2
I02
Authorization Information
M 1
AN
10
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
This element is fixed in length with identical minimum and maximum lengths. Spaces are inserted to meet the minimum length in an AN data element. With the associated code 00 in ISA01 or ISA03, an all space value indicates no information.
Required
3
I03
Security Information Qualifier
M 1
ID
2
Code identifying the type of information in the Security Information
CODE
DEFINITION
00
No Security Information Present (No Meaningful Information in I04)
01
Password
Required
4
I04
Security Information
M 1
AN
10
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
This element is fixed in length with identical minimum and maximum lengths. Spaces are inserted to meet the minimum length in an AN data element. With the associated code 00 in ISA01 or ISA03, an all space value indicates no information.
Required
5
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Sender in ISA06.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
CODE SOURCE: 121: Health Industry Number
27
Carrier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
28
Fiscal Intermediary Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
29
Medicare Provider and Supplier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
6
I06
Interchange Sender ID
M 1
AN
15
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Required
7
I05
Interchange ID Qualifier
M 1
ID
2
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
This ID qualifies the Receiver in ISA08.
CODE
DEFINITION
01
Duns (Dun & Bradstreet)
14
Duns Plus Suffix
20
Health Industry Number (HIN)
CODE SOURCE: 121: Health Industry Number
27
Carrier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
28
Fiscal Intermediary Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
29
Medicare Provider and Supplier Identification Number as assigned by Centers for Medicare & Medicaid Services (CMS)
30
U.S. Federal Tax Identification Number
33
National Association of Insurance Commissioners Company Code (NAIC)
ZZ
Mutually Defined
Required
8
I07
Interchange Receiver ID
M 1
AN
15
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Required
9
I08
Interchange Date
M 1
DT
6
Date of the interchange
The date format is YYMMDD.
Required
10
I09
Interchange Time
M 1
TM
4
Time of the interchange
The time format is HHMM.
Required
11
I65
Repetition Separator
M 1
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
Required
12
I11
Interchange Control Version Number Code
M 1
ID
5
Code specifying the version number of the interchange control segments, the version of the data elements within the control segments, and the code values within those data elements.
INDUSTRY NAME: Interchange Control Version Number
CODE
DEFINITION
00802
00802 Standards Approved for Publication by ASC X12 Procedures Review Board through December 2020
Required
13
I12
Interchange Control Number
M 1
N
9
A control number assigned by the interchange sender
  1. The Interchange Control Number, ISA13, must be identical to the associated Interchange Trailer IEA02.
  2. Must be a positive unsigned number and must be identical to the value in IEA02.
Required
14
I13
Acknowledgment Requested Code
M 1
ID
1
Code indicating sender's request for an interchange acknowledgment
INDUSTRY NAME: Acknowledgment Requested
X12.5 - Interchange Control Structure provides the purpose of the TA1 segment. The X12 Acknowledgment Reference Model provides considerable information about the TA1 segment.
CODE
DEFINITION
0
No Interchange Acknowledgment Requested
Use when the interchange contains ONLY acknowledgment Functional Groups (e.g. 999 or 824) or a TA1.
1
Interchange Acknowledgment Requested (TA1)
Use when batch process requires the return of a TA1 for the interchange.
2
Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors"
Use when the transaction is for real-time processing.
3
Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors" or "Accepted but Errors are Noted"
Use when batch processing requires the return of a TA1 for the interchange only when errors are noted.
Required
15
I14
Interchange Usage Indicator Code
M 1
ID
1
Code indicating whether data enclosed by this interchange envelope is test, production or information
INDUSTRY NAME: Interchange Usage Indicator
CODE
DEFINITION
I
Information
Use when the interchange contains ONLY a TA1.
P
Production Data
T
Test Data
Required
16
I15
Component Element Separator
M 1
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

GS*BE - FUNCTIONAL GROUP HEADER

X12 Name:
Functional Group Header
X12 Purpose:
To indicate the beginning of a functional group and to provide control information
X12 Comments:
A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
GS✱XX✱SENDER CODE✱RECEIVER CODE✱19991231✱0802✱1✱X✱008020X318~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
479
Functional Identifier Code
M 1
ID
2
Code identifying a group of application related transaction sets
This is the 2-character Functional Identifier Code assigned to each transaction set by X12. The specific code for a transaction set defined by this implementation guide is presented in Section 1.2, Version Information.
CODE
DEFINITION
BE
Benefit Enrollment and Maintenance (834)
Required
2
142
Application Sender's Code
M 1
AN
2/15
Code identifying party sending transmission; codes agreed to by trading partners
Use this code to identify the unit sending the information.
Required
3
124
Application Receiver's Code
M 1
AN
2/15
Code identifying party receiving transmission; codes agreed to by trading partners
Use this code to identify the unit receiving the information.
Required
4
373
Date
M 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: GS04 is the group date.
Use this date for the functional group creation date.
Required
5
337
Time
M 1
TM
4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
SEMANTIC: GS05 is the group time.
Use this time for the creation time. The recommended format is HHMM.
Required
6
28
Group Control Number
M 1
N
1/9
Assigned number originated and maintained by the sender
SEMANTIC: The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02.
For implementations compliant with this guide, GS06 must be unique within a single transmission (that is, within a single ISA to IEA enveloping structure). The authors recommend that GS06 be unique within all transmissions over a period of time to be determined by the sender.
Required
7
455
Responsible Agency Code
M 1
ID
1/2
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
CODE
DEFINITION
X
Accredited Standards Committee X12
Required
8
480
Version / Release / Industry Identifier Code
M 1
AN
1/12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
INDUSTRY NAME: Version, Release, or Industry Identifier Code
This is the unique Version/Release/Industry Identifier Code assigned to an implementation by X12N. The specific code for a transaction set defined by this implementation guide is presented in Section 1.2, Version Information.
CODE SOURCE 881: Version / Release / Industry Identifier Code
CODE
DEFINITION
008020X318
Plan Member Reporting

ST*834 - TRANSACTION SET HEADER

X12 Name:
Transaction Set Header
X12 Purpose:
To indicate the start of a transaction set and to assign a control number
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
ST✱834✱0002✱008020X318~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
143
Transaction Set Identifier Code
M 1
ID
3
Code identifying a Transaction Set
SEMANTIC: The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
CODE
DEFINITION
834
Benefit Enrollment and Maintenance
Required
2
329
Transaction Set Control Number
M 1
AN
4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
The Transaction Set Control Numbers in ST02 and SE02 must be identical and must be a numeric value. The number (i.e. numeric value) is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the numeric value 0001 and increment from there. The Transaction Set Control Number also aids in error resolution research.
Required
3
1705
Implementation Convention Reference
O 1
AN
1/35
Reference assigned to identify Implementation Convention
SEMANTIC: The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08.
  1. This element must be populated with the guide identifier named in Section 1.2.
  2. This field contains the same value as GS08. Some translator products strip off the ISA and GS segments prior to application (STSE) processing. Providing the information from the GS08 at this level will ensure that the appropriate application mapping is utilized at translation time.
CODE
DEFINITION
008020X318
Plan Member Reporting

BGN - BEGINNING SEGMENT

X12 Name:
Beginning Segment
X12 Purpose:
To indicate the beginning of a transaction set
X12 Syntax:
C0504
If BGN05 is present, then BGN04 is required.
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
BGN✱00✱11227✱20150920✱1200✱ES✱✱2~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
353
Transaction Set Purpose Code
M 1
ID
2
Code identifying purpose of transaction set
CODE
DEFINITION
00
Original
Use when the transaction set is being sent for the first time.

If the original transaction set has already been processed, an incoming transaction set using this code may be rejected by the Information Receiver. The rejection must be reported to the sender.

Use when the original transaction set was incorrect and a new corrected transaction set is being sent. This transaction set then can be pended by the Information Receiver for review.
15
Re-Submission
Use when the original transaction set was incorrect and a new corrected transaction set is being sent. This transaction set then can be pended by the Information Receiver for review.
Required
2
127
Reference Identification
M 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: BGN02 is the transaction set reference number.
INDUSTRY NAME: Transaction Set Reference Number
  1. This element is the transaction set reference number assigned by the Information Source. It uniquely identifies this occurrence of the transaction set for future reference.
  2. Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Required
3
373
Date
M 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: BGN03 is the transaction set date.
INDUSTRY NAME: Transaction Set Creation Date
This element identifies the date that the submitter created the file.
Required
4
337
Time
X 1
TM
4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
SEMANTIC: BGN04 is the transaction set time.
SEGMENT SYNTAX: C0504
INDUSTRY NAME: Transaction Set Creation Time
This element identifies the time that the submitter created the transaction set.
Required
5
623
Time Code
O 1
ID
2
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
SEMANTIC: BGN05 is the transaction set time qualifier.
SEGMENT SYNTAX: C0504
INDUSTRY NAME: Time Zone Code
This element reflects the time zone of the submitter.
CODE SOURCE 94: International Organization for Standardization (Date and Time)
CODE
DEFINITION
01
Equivalent to ISO P01
02
Equivalent to ISO P02
03
Equivalent to ISO P03
04
Equivalent to ISO P04
05
Equivalent to ISO P05
06
Equivalent to ISO P06
07
Equivalent to ISO P07
08
Equivalent to ISO P08
09
Equivalent to ISO P09
10
Equivalent to ISO P10
11
Equivalent to ISO P11
12
Equivalent to ISO P12
13
Equivalent to ISO M12
14
Equivalent to ISO M11
15
Equivalent to ISO M10
16
Equivalent to ISO M09
17
Equivalent to ISO M08
18
Equivalent to ISO M07
19
Equivalent to ISO M06
20
Equivalent to ISO M05
21
Equivalent to ISO M04
22
Equivalent to ISO M03
23
Equivalent to ISO M02
24
Equivalent to ISO M01
AD
Alaska Daylight Time
AS
Alaska Standard Time
AT
Alaska Time
CD
Central Daylight Time
CS
Central Standard Time
CT
Central Time
ED
Eastern Daylight Time
ES
Eastern Standard Time
ET
Eastern Time
GM
Greenwich Mean Time
HD
Hawaii-Aleutian Daylight Time
HS
Hawaii-Aleutian Standard Time
HT
Hawaii-Aleutian Time
LT
Local Time
MD
Mountain Daylight Time
MS
Mountain Standard Time
MT
Mountain Time
ND
Newfoundland Daylight Time
NS
Newfoundland Standard Time
NT
Newfoundland Time
PD
Pacific Daylight Time
PS
Pacific Standard Time
PT
Pacific Time
TD
Atlantic Daylight Time
TS
Atlantic Standard Time
TT
Atlantic Time
UT
Universal Time Coordinate
Situational
6
127
Reference Identification
O 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.
SITUATIONAL RULE: Required when there is a previously sent transaction set to cross-reference. If not required by this implementation guide, do not send.
INDUSTRY NAME: Original Transaction Set Reference Number
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
7
640
Transaction Type Code
O 1
ID
2
Required
8
306
Action Code
O 1
ID
1/2
Code indicating type of action
CODE
DEFINITION
2
Change (Update)
Use when identifying a transaction set of additions, terminations, cancelations, reinstatements and changes.
4
Verify
Use when identifying a full member reporting transaction set to verify that the Submitter/Information Source and Information Receiver systems are synchronized.
RX
Replace
Use when identifying a full member reporting transaction set to be used to identify additions, terminations, cancelations, reinstatements and changes that need to be applied to the Information Receiver's system.
Not Used
9
786
Security Level Code
O 1
ID
2

DTP*007 - FILE EFFECTIVE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
DTP✱007✱D8✱20171001~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
007
Effective
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

N1*41 - SUBMITTER NAME

X12 Name:
Party Identification
X12 Purpose:
To identify a party by type of organization, name, and code
X12 Syntax:
  1. R0203
    At least one of N102 or N103 is required.
  2. P0304
    If either N103 or N104 is present, then the other is required.
  3. C0703
    If N107 is present, then N103 is required.
X12 Set Notes:
NOTE: At least one iteration of loop 1000 is required to identify the sender or receiver.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
The submitter is the entity responsible for the creation and formatting of this transaction.
TR3 Example:
N1✱41✱ABCSUBMITTER✱46✱12356799~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
41
Submitter
Required
2
93
Name
X 1
AN
1/60
Free-form name
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Submitter Name
Required
3
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: R0203, P0304, C0703
CODE
DEFINITION
46
Electronic Transmitter Identification Number (ETIN)
FI
Federal Taxpayer's Identification Number
Required
4
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
COMMENT: This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
SEGMENT SYNTAX: P0304
INDUSTRY NAME: Submitter Identifier
Not Used
5
706
Entity Relationship Code
O 1
ID
2
Not Used
6
98
Entity Identifier Code
O 1
ID
2/3
Not Used
7
C076
Composite Identification Codes
O 1

N1*40 - RECEIVER NAME

X12 Name:
Party Identification
X12 Purpose:
To identify a party by type of organization, name, and code
X12 Syntax:
  1. R0203
    At least one of N102 or N103 is required.
  2. P0304
    If either N103 or N104 is present, then the other is required.
  3. C0703
    If N107 is present, then N103 is required.
X12 Set Notes:
NOTE: At least one iteration of loop 1000 is required to identify the sender or receiver.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This loop identifies the Information Receiver of this transaction set.
TR3 Example:
N1✱40✱XYZ RECEIVER✱FI✱123567999~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
40
Receiver
Required
2
93
Name
X 1
AN
1/60
Free-form name
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Receiver Name
Required
3
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: R0203, P0304, C0703
CODE
DEFINITION
46
Electronic Transmitter Identification Number (ETIN)
FI
Federal Taxpayer's Identification Number
Required
4
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
COMMENT: This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
SEGMENT SYNTAX: P0304
INDUSTRY NAME: Receiver Identifier
Not Used
5
706
Entity Relationship Code
O 1
ID
2
Not Used
6
98
Entity Identifier Code
O 1
ID
2/3
Not Used
7
C076
Composite Identification Codes
O 1

N1*ACV - INFORMATION SOURCE

X12 Name:
Party Identification
X12 Purpose:
To identify a party by type of organization, name, and code
X12 Syntax:
  1. R0203
    At least one of N102 or N103 is required.
  2. P0304
    If either N103 or N104 is present, then the other is required.
  3. C0703
    If N107 is present, then N103 is required.
X12 Set Notes:
NOTE: At least one iteration of loop 1000 is required to identify the sender or receiver.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the information source is different from the submitter. If not required by this implementation guide, do not send.
TR3 Notes:
See section 1.5 for definition of Information Source.
TR3 Example:
N1✱ACV✱ABC INFORMATION SOURCE✱FI✱123356799~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
ACV
Information Source
Required
2
93
Name
X 1
AN
1/60
Free-form name
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Information Source Name
Required
3
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: R0203, P0304, C0703
CODE
DEFINITION
46
Electronic Transmitter Identification Number (ETIN)
94
Code assigned by the organization that is the ultimate destination of the transaction set
FI
Federal Taxpayer's Identification Number
Required
4
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
COMMENT: This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
SEGMENT SYNTAX: P0304
INDUSTRY NAME: Information Source Identifier
Not Used
5
706
Entity Relationship Code
O 1
ID
2
Not Used
6
98
Entity Identifier Code
O 1
ID
2/3
Not Used
7
C076
Composite Identification Codes
O 1

INS - MEMBER LEVEL DETAIL

X12 Name:
Insured Benefit
X12 Purpose:
To provide benefit, characteristics, and identification information on insured entities.
X12 Syntax:
P1112
If either INS11 or INS12 is present, then the other is required.
X12 Set Notes:
NOTE: A Subscriber is a person who elects the benefits and is affiliated with the employer or the insurer. A Dependent is a person who is affiliated with the subscriber, such as a spouse, child, etc., and is therefore entitled to benefits. Subscriber information must come before dependent information. The INS segment is used to note if information being submitted is subscriber information or dependent information.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
INS✱Y✱18✱021✱28✱A✱✱✱FT~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1073
Yes/No Condition or Response Code
M 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: INS01 indicates status of the insured. A "Y" value indicates the insured is a subscriber: an "N" value indicates the insured is a dependent.
INDUSTRY NAME: Subscriber Indicator
CODE
DEFINITION
N
No
Y
Yes
Required
2
1069
Individual Relationship Code
M 1
ID
2
Code indicating the relationship between two individuals or entities
  1. The value 18 must be used for the subscriber.
  2. For dependents, this value identifies their relationship to the subscriber. For example, a daughter would be value 19.
CODE
DEFINITION
01
Spouse
03
Father or Mother
04
Grandfather or Grandmother
05
Grandson or Granddaughter
06
Uncle or Aunt
07
Nephew or Niece
08
Cousin
09
Adopted Child
10
Foster Child
11
Son-in-law or Daughter-in-law
12
Brother-in-law or Sister-in-law
13
Mother-in-law or Father-in-law
14
Brother or Sister
15
Ward
16
Stepparent
17
Stepson or Stepdaughter
18
Self
19
Child
23
Sponsored Dependent
Use when reporting a dependent over the age of majority (not a minor).
24
Dependent of a Minor Dependent
25
Ex-spouse
26
Guardian
31
Court Appointed Guardian
38
Collateral Dependent
Use when reporting a relative related by blood or marriage who resides in the home and is dependent on the insured for a major portion of their support.
53
Life Partner
60
Annuitant
D2
Trustee
G8
Other Relationship
G9
Other Relative
Required
3
875
Maintenance Type Code
O 1
ID
3
Code identifying the specific type of item maintenance
CODE
DEFINITION
001
Change
Use when indicating a change to an existing subscriber/dependent record.
021
Addition
Use when adding a subscriber or dependent.
024
Cancellation or Termination
Use when indicating a termination of benefit coverage.
025
Reinstatement
Use when reinstating a cancelled or terminated subscriber/dependent record.
030
Audit or Compare
Use when sending a full file (BGN08 = `4') to verify that the Information Source and Information Receiver databases are synchronized. See section 1.4.6, Update, Versus Full File Audits, Versus Full File Replacements, for additional information.
123
Canceled by Administrator
Use when indicating cancellation of benefit coverage.
Situational
4
1203
Maintenance Reason Code
O 1
ID
2/3
Code identifying the reason for the maintenance change
SITUATIONAL RULE: Required when INS03 is `001', `021', or `024'. If not required by this implementation guide, do not send.
CODE
DEFINITION
01
Divorce
02
Birth
03
Death
04
Retirement
05
Adoption
07
Termination of Benefits
08
Termination of Employment
09
Consolidation Omnibus Budget Reconciliation Act (COBRA)
10
Consolidation Omnibus Budget Reconciliation Act (COBRA) Premium Paid
11
Surviving Spouse
15
Primary Care Provider (PCP) Change
20
Active
21
Disability
22
Plan Change
Use when a member changes from one Plan to a different Plan. This is not intended to identify changes to a Plan.
25
Change in Identifying Data Elements
Use when a change has been made to the primary elements that identify a member. Such primary elements include the following: first name, last name, Social Security Number, date of birth, and employee identification number.
27
Pre-Enrollment
Use when reporting newborns as specified in the Trading Partner Agreement.
28
Initial Enrollment
Use when it is the first time the member selected coverage with the Plan.
29
Benefit Selection
Use when a member changes benefits within a Plan.
31
Legal Separation
32
Marriage
33
Personnel Data
Use when any data change that is not included in any of the other allowed codes. An example would be change in Coordination of Benefits information.
41
Re-enrollment
43
Change of Location
Use when indicating a change of address.
59
Non Payment
AL
Algorithm Assigned Benefit Selection
EC
Member Benefit Selection
Use when reporting the initial and subsequent enrollment when an insurance carrier needs to recognize that a member made an explicit plan choice.
XN
Notification Only
Use when no other value applies.
XT
Transfer
Use when a member has an organizational change (i.e. a location change within the organization) with no change in benefits or plan.
Required
5
1216
Benefit Status Code
O 1
ID
1
Code identifying the type of coverage under which benefits are paid
CODE
DEFINITION
A
Active
C
Consolidated Omnibus Budget Reconciliation Act (COBRA)
S
Surviving Insured
T
Tax Equity and Fiscal Responsibility Act (TEFRA)
Situational
6
C052
Medicare Status Code
O 1
To provide Medicare coverage and associated reason for Medicare eligibility
SITUATIONAL RULE: Required when a member is currently enrolled in Medicare or has terminated or changed their Medicare enrollment. If not required by this implementation guide, do not send.
Required
6-1
1218
Medicare Plan Code
M 1
ID
1
Code identifying the Medicare Plan
CODE
DEFINITION
A
Medicare Part A
B
Medicare Part B
C
Medicare Part A and B
D
Medicare
E
No Medicare
Not Used
6-2
1701
Eligibility Reason Code
O 1
ID
1
Not Used
6-3
1701
Eligibility Reason Code
O 1
ID
1
Not Used
6-4
1701
Eligibility Reason Code
O 1
ID
1
Situational
7
1219
Consolidated Omnibus Budget Reconciliation Act (COBRA) Qualifying
O 1
ID
1/2
Code identifying a qualifying event which results in loss of coverage for a Qualified Beneficiary
SITUATIONAL RULE: Required when INS05 is equal to `C'. If not required by this implementation guide, do not send.
INDUSTRY NAME: Consolidated Omnibus Budget Reconciliation Act (COBRA) Qualifying Event Code
CODE
DEFINITION
1
Termination of Employment
2
Reduction of work hours
3
Medicare
4
Death
5
Divorce
6
Separation
7
Ineligible Child
8
Bankruptcy of Retiree's Former Employer (26 U.S.C. 4980B(f)(3)(F))
9
Layoff
10
Leave of Absence
ZZ
Mutually Defined
Use when established by the Trading Partner Agreement.
Situational
8
584
Employment Status Code
O 1
ID
2
Code indicating the general employment status of an employee/claimant
SITUATIONAL RULE: Required when INS01 equals Y. If not required by this implementation guide, do not send.
If the subscriber is enrolled in a non-employment based program such as Medicare or Medicaid then this data element will contain the status of the subscriber in that program. Codes for non-employment based programs will be limited to `CA' (Non-applicable Employment Status Category) and `TE' (Terminated).
CODE
DEFINITION
AC
Active
Use when subscriber is in an employment based program and other codes listed do not apply.
AO
Active Military - Overseas
AU
Active Military - USA
CA
Non-applicable Employment Status Category
Use when the subscriber is in a non-employment based program.
FT
Full-time
Full time active employee
L1
Leave of Absence
PT
Part-time
Part time active employee
RT
Retired
TE
Terminated
Situational
9
1220
Student Status Code
O 1
ID
1
Code indicating the student status of the patient if 19 years of age or older, not handicapped and not the insured
SITUATIONAL RULE: Required when describing a non-spouse dependent who is identified in the Information Source system as a student. If not required by this implementation guide, do not send.
CODE
DEFINITION
F
Full-time
N
Not a Student
Use when dependent was previously reported as a student and is no longer identified as a student.
P
Part-time
Situational
10
1073
Yes/No Condition or Response Code
O 1
ID
1
Code indicating a Yes or No condition or response
SEMANTIC: INS10 is the handicapped status indicator. A "Y" value indicates an individual is handicapped; an "N" value indicates an individual is not handicapped.
SITUATIONAL RULE: Required when the member is handicapped or to correct a previous report of handicapped status. If not required by this implementation guide, do not send.
INDUSTRY NAME: Handicap Indicator
See section 1.5 for definitions of "handicap" and "disability".
CODE
DEFINITION
N
No
Y
Yes
Situational
11
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P1112
SITUATIONAL RULE: Required when INS12 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
12
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: INS12 is the date of death.
SEGMENT SYNTAX: P1112
SITUATIONAL RULE: Required when the member is deceased. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Individual Death Date
This is the date of death for the member and does not replace the use of the termination date in Loop 2300.
Situational
13
1165
Confidentiality Code
O 1
ID
1
Code indicating the access to insured information
SITUATIONAL RULE: Required when the member has restricted the access to their information or the access restriction has changed (see section 1.4.8 for further information). If not required by this implementation guide, do not send.
CODE
DEFINITION
O
Other Restrictions
Use when the member has been identified as at risk (see section 1.4.8 for more information).
R
Restricted Access
U
Unrestricted Access
Use when there is a change in the member's access restriction.
Not Used
14
19
City Name
O 1
AN
2/30
Not Used
15
156
State or Province Code
O 1
ID
2
Not Used
16
26
Country Code
O 1
ID
2/3
Situational
17
1470
Number
O 1
N
1/9
A generic number
SEMANTIC: INS17 is the number assigned to each family member born with the same birth date. This number identifies birth sequence for multiple births allowing proper tracking and response of benefits for each dependent (i.e., twins, triplets, etc.).
SITUATIONAL RULE: Required when reporting family members with the same birth date if a birth sequence number is needed for proper reporting, tracking or response to benefits. If not required by this implementation guide, do not send.
INDUSTRY NAME: Birth Sequence Number
Not Used
18
1792
Changed Identifying Information Code
O 20
ID
1/2
Not Used
19
1793
Provider Network Status Information Code
O 1
ID
1/2

REF*0F - SUBSCRIBER IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
X12 Set Notes:
NOTE: The REF segment is required to link the dependent(s) to the subscriber.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
This segment must contain a unique SUBSCRIBER identification number. This identifier is used for linking the subscriber with dependents as required under many policies.
TR3 Example:
REF✱0F✱920399398~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
0F
Subscriber Number
Use when established by the Trading Partner Agreement
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Subscriber Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF - MEMBER TAXPAYER IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
X12 Set Notes:
NOTE: The REF segment is required to link the dependent(s) to the subscriber.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when the Member's Taxpayer Identifier (social security number or ITIN) is allowed to be used for this purpose under applicable law or regulation.

AND

The Member's Taxpayer Identifier (social security number or ITIN) is available in the Information Source's system.
If not required by this implementation guide, do not send.
TR3 Example:
REF✱SY✱111002222~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
SY
Social Security Number
TJ
Federal Taxpayer's Identification Number
Use when reporting Individual Taxpayer Identification Number (ITIN).
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF - MEMBER SUPPLEMENTAL IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
X12 Set Notes:
NOTE: The REF segment is required to link the dependent(s) to the subscriber.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
11
Situational Rule:
Required when sending additional identifying information on the member. If not required by this implementation guide, do not send.
TR3 Example:
REF✱17✱920399398~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
17
Client Reporting Category
Use when established by the Trading Partner Agreement.
23
Client Number
Use when passing a payer specific identifier for a member.
3H
Case Number
6O
Cross Reference Number
Use when further identification of a member is required for reporting, indexing, or other purpose as mutually agreed upon between the submitter and receiver of the transaction set.
ABB
Personal ID Number
DX
Department/Agency Number
Use when members in a coverage group are set up as different departments or divisions under the terms of the insurance policy.
F6
Health Insurance Claim (HIC) Number
Use when reporting Medicare eligibility for a member.
NQ
Medicaid Recipient Identification Number
Q4
Prior Identifier Number
Use when passing the Identifier Number under which the member had previous coverage with the payer. This could be the result of a change in employment or coverage that resulted in a new ID number being assigned but left the member covered by the same payer.
QQ
Unit Number
Use when members in a coverage group are set up as different units under the terms of the insurance policy. Units may exist within another grouping such as division or department.
ZZ
Mutually Defined
Use when established by the Trading Partner Agreement.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Member Supplemental Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

REF*PID - MEMBER PROGRAM/PLAN IDENTIFIER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
X12 Set Notes:
NOTE: The REF segment is required to link the dependent(s) to the subscriber.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by terms of the trading partner agreement. If not required by this implementation guide, do not send.
TR3 Example:
REF✱PID✱ABC123~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
PID
Program Identification Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Member Program/Plan Identifier
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP - MEMBER LEVEL DATES

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
13
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Notes:
  1. This loop is used to report eligibility dates. Use Loop 2300 to report coverage dates.
  2. When an end date is reported, it represents that day through 11:59 pm.
TR3 Example:
DTP✱356✱D8✱20150705~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
286
Retirement
296
Initial Disability Period Return To Work
297
Initial Disability Period Last Day Worked
301
Consolidated Omnibus Budget Reconciliation Act (COBRA) Qualifying Event
336
Employment Begin
337
Employment End
338
Medicare Begin
339
Medicare End
356
Eligibility Begin
Use when reporting the date a member could elect to enroll or begin benefits in any health care plan with this Information Source. The actual begin date of coverage is conveyed in the DTP segment in Loop 2300.
357
Eligibility End
Use when member's eligibility has been terminated. The eligibility end date represents the last date of eligibility. For example, if a date of 02/28/2017 is passed then eligibility for this individual will be through 11:59 p.m. on 02/28/2017. See section 1.4.5 for further information on termination.
394
Rehire
473
Medicaid Begin
474
Medicaid End
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP*303 - MEMBER LEVEL MAINTENANCE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when reporting the effective date of a change to an existing member's information. If not required by this implementation guide, do not send.
TR3 Notes:
The use of this segment is intended to convey member level changes. The DTP segments in Loop 2300 are to be used to convey changes in coverage only.
TR3 Example:
DTP✱303✱D8✱20170705~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
303
Maintenance Effective
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP*393 - MEMBER LEVEL PLAN PARTICIPATION SUSPENSION DATES

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the member has been suspended from plan participation. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱393✱D8✱20150701~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
393
Plan Participation Suspension
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

NM1 - MEMBER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱IL✱1✱SMITH✱JOHN✱M✱✱SR✱34✱123456789~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
74
Corrected Insured
Use when correcting member information previously sent in NM1 or DMG in Loop 2100A.
IL
Insured or Subscriber
Use when code values `74' and `PJ' do not apply.
PJ
Party to Receive Correspondence
Use when access to an individual's information must be limited due to their status of At Risk.
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Member Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 is equal to "1" (person) and the person has a middle name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Middle Name
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
SITUATIONAL RULE: Required when person has a prefix. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when person has a suffix. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Name Suffix
Required
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
34
Social Security Number
The Social Security Number must be a string of exactly nine numbers with no separators. For example, sending "111002222" would be valid, while sending "111-00-2222 would be invalid".
MI
Member Identification Number
TA
Taxpayer ID Number
Use when reporting Individual Taxpayer Identification Number (ITIN).
ZZ
Mutually Defined
Use when established by the Trading Partner Agreement and the other code values are not applicable.
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Member Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

PER*IP - MEMBER COMMUNICATIONS NUMBERS

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number always includes the area code and phone number using the format AAABBBCCCC, where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534)224-2525 would be represented as 5342242525).
TR3 Example:
PER✱IP✱✱HP✱8015554321~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IP
Insured Party
Not Used
2
93
Name
O 1
AN
1/60
Required
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
EM
Electronic Mail
OT
Other Residential Telephone Number
Use when reporting a TTY communication number.
TE
Telephone
Use when identifying the primary phone number.
WP
Work Phone Number
Required
4
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
Situational
5
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a value is being reported in the PER06 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
AP
Alternate Telephone
Use when reporting the phone number for the individual's alternative contact.
EM
Electronic Mail
EX
Telephone Extension
OT
Other Residential Telephone Number
Use when reporting a TTY communication number.
WP
Work Phone Number
Situational
6
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when additional communication numbers are available. If not required by this implementation guide, do not send.
Situational
7
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a value is being reported in the PER08 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
AP
Alternate Telephone
Use when reporting the phone number for the individual's alternative contact.
EM
Electronic Mail
EX
Telephone Extension
OT
Other Residential Telephone Number
Use when reporting a TTY communication number.
WP
Work Phone Number
Situational
8
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when additional communication numbers are available. If not required by this implementation guide, do not send.
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

N3 - MEMBER RESIDENCE STREET ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the member is the subscriber or when a dependent has a different address from the subscriber. If not required by this implementation guide, do not send.
TR3 Example:
N3✱50 ORCHARD STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Member Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required if a second address line exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Address Line

N4 - MEMBER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when sending subscribers, or when dependent has a different address. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Member City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member State Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Postal Zone or Zip Code
Use 9 digit Zip code for U.S. addresses when available in Information Source's system.
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Situational
5
309
Location Qualifier
X 1
ID
1/2
Code identifying type of location
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when N406 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
60
Area
CY
County/Parish
ZZ
Mutually Defined
Use when address reported is not to be used. (For example Member is homeless or At Risk and true physical address cannot be reported).
Situational
6
310
Location Identifier
O 1
AN
1/30
Code which identifies a specific location
SEGMENT SYNTAX: C0605
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

DMG*D8 - MEMBER DEMOGRAPHICS

X12 Name:
Demographic Information
X12 Purpose:
To supply demographic information
X12 Syntax:
  1. P0102
    If either DMG01 or DMG02 is present, then the other is required.
  2. P1011
    If either DMG10 or DMG11 is present, then the other is required.
  3. C1105
    If DMG11 is present, then DMG05 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
DMG✱D8✱19750915✱F✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0102
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
2
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
INDUSTRY NAME: Member Birth Date
Required
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
CODE
DEFINITION
F
Female
M
Male
U
Unknown
Use when the gender is unknown or when it can not be sent due to reporting restrictions.
Situational
4
1067
Marital Status Code
O 1
ID
1
Code specifying the marital status of a person
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
CODE
DEFINITION
B
Registered Domestic Partner
D
Divorced
I
Single
M
Married
R
Unreported
S
Separated
U
Unmarried (Single or Divorced or Widowed)
This code should be used if the previous status is unknown.
W
Widowed
X
Legally Separated
Situational
5
C056
Composite Race or Ethnicity Information
X 25
To send general and detailed information on race or ethnicity
X12 COMPOSITE SYNTAX NOTES: P0203
If either C05602 or C05603 is present, then the other is required.
X12 COMPOSITE SEMANTIC NOTES: C056-02 and C056-03 are used to specify detailed information about race or ethnicity.
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
Race or Ethnicity information is reported in either DMG05-01 or DMG05-02 and DMG05-03.
Situational
5-1
1109
Race or Ethnicity Code
O 1
ID
1
Code indicating the racial or ethnic background of a person; it is normally self-reported; Under certain circumstances this information is collected for United States Government statistical purposes
SITUATIONAL RULE: Required when reporting the Race or Ethnicity code from the DMG05-01 list of code values. If not required by this implementation guide, do not send.
CODE
DEFINITION
7
Not Provided
8
Not Applicable
A
Asian or Pacific Islander
B
Black
C
Caucasian
D
Subcontinent Asian American
E
Other Race or Ethnicity
F
Asian Pacific American
G
Native American
H
Hispanic
I
American Indian or Alaskan Native
J
Native Hawaiian
N
Black (Non-Hispanic)
O
White (Non-Hispanic)
P
Pacific Islander
Z
Mutually Defined
Situational
5-2
1270
Code List Qualifier Code
X 1
ID
1/3
Code identifying a specific industry code list
COMPOSITE SYNTAX: P0203
SITUATIONAL RULE: Required when the Classification of Race or Ethnicity code set is being used to report Race or Ethnicity data. If not required by this implementation guide, do not send.
CODE
DEFINITION
RET
Classification of Race or Ethnicity
CODE SOURCE: 859: Classification of Race or Ethnicity
Situational
5-3
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: P0203
SITUATIONAL RULE: Required when reporting the Race or Ethnicity code obtained from the Classification of Race or Ethnicity code. If not required by this implementation guide, do not send.
INDUSTRY NAME: Race or Ethnicity Code
CODE SOURCE 859: Classification of Race or Ethnicity
Situational
6
1066
Citizenship Status Code
O 1
ID
1/2
Code indicating citizenship status
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
U.S. Citizen
2
Non-Resident Alien
3
Resident Alien
4
Illegal Alien
5
Alien
6
U.S. Citizen - Non-Resident
7
U.S. Citizen - Resident
Not Used
7
26
Country Code
O 1
ID
2/3
Not Used
8
659
Basis of Verification Code
O 1
ID
1/2
Not Used
9
380
Quantity
O 1
R
1/15
Not Used
10
1270
Code List Qualifier Code
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30
Not Used
12
26
Country Code
O 1
ID
2/3

EC - EMPLOYMENT CLASS

X12 Name:
Employment Class
X12 Purpose:
To provide class of employment information
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
>1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
EC✱04✱06✱07~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1176
Employment Class Code
O 1
ID
2/3
Code indicating category of employee
CODE
DEFINITION
01
Union
02
Non-Union
03
Executive
04
Non-Executive
05
Management
06
Non-Management
07
Hourly
08
Salaried
09
Administrative
10
Non-Administrative
11
Exempt
12
Non-Exempt
17
Highly Compensated
18
Key-Employee
19
Bargaining
20
Non-Bargaining
21
Owner
22
President
23
Vice President
Situational
2
1176
Employment Class Code
O 1
ID
2/3
Code indicating category of employee
SITUATIONAL RULE: Required if further classification information is needed. If not required by this implementation guide, do not send.
CODE
DEFINITION
01
Union
02
Non-Union
03
Executive
04
Non-Executive
05
Management
06
Non-Management
07
Hourly
08
Salaried
09
Administrative
10
Non-Administrative
11
Exempt
12
Non-Exempt
17
Highly Compensated
18
Key-Employee
19
Bargaining
20
Non-Bargaining
21
Owner
22
President
23
Vice President
Situational
3
1176
Employment Class Code
O 1
ID
2/3
Code indicating category of employee
SITUATIONAL RULE: Required if further classification information is needed. If not required by this implementation guide, do not send.
CODE
DEFINITION
01
Union
02
Non-Union
03
Executive
04
Non-Executive
05
Management
06
Non-Management
07
Hourly
08
Salaried
09
Administrative
10
Non-Administrative
11
Exempt
12
Non-Exempt
17
Highly Compensated
18
Key-Employee
19
Bargaining
20
Non-Bargaining
21
Owner
22
President
23
Vice President
Not Used
4
954
Percentage as Decimal
O 1
R
1/10
Not Used
5
1201
Information Status Code
O 1
ID
1
Not Used
6
1149
Occupation Code
O 1
ID
4/6

ICM - MEMBER INCOME

X12 Name:
Individual Income
X12 Purpose:
To supply information to determine benefit eligibility, deductibles, and retirement and investment contributions
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
ICM✱1✱40000✱40~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
594
Frequency Code
M 1
ID
1
Code indicating frequency or type of activities or actions being reported
SEMANTIC: ICM01 is the frequency at which an individual's wages are paid.
CODE
DEFINITION
1
Weekly
2
Biweekly
3
Semimonthly
4
Monthly
6
Daily
7
Annual
8
Two Calendar Months
9
Lump-Sum Separation Allowance
B
Year-to-Date
C
Single
H
Hourly
Q
Quarterly
S
Semiannual
U
Unknown
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
SEMANTIC: ICM02 is the yearly wages amount.
INDUSTRY NAME: Wage Amount
Refer to Appendix B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount for more information about this data element length.
Situational
3
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: ICM03 is the weekly hours.
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
INDUSTRY NAME: Work Hours Count
Situational
4
310
Location Identifier
O 1
AN
1/30
Code which identifies a specific location
SEMANTIC: ICM04 is the employer location qualifier such as a department number.
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
INDUSTRY NAME: Location Identification Code
Situational
5
1214
Salary Grade
O 1
AN
1/5
The salary grade code assigned by the employer
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
INDUSTRY NAME: Salary Grade Code
Not Used
6
100
Currency Code
O 1
ID
3

HLH - MEMBER HEALTH INFORMATION

X12 Name:
Health Information
X12 Purpose:
To provide health information
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
HLH✱T~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
C061
Member Health and Treatment Information
O 10
To identify member health and treatment information
X12 COMPOSITE SYNTAX NOTES:
  1. L030405
    If C06103 is present, then at least one of C06104 or C06105 are required.
  2. C0403
    If C06104 is present, then C06103 is required.
  3. C0503
    If C06105 is present, then C06103 is required.
X12 COMPOSITE SEMANTIC NOTES:
  1. C061-04 is the beginning date related to the type of date identified in C061-03.
  2. C061-05 is the end date related to the type of date identified in C061-03.
Required
1-1
1212
Health-Related Code
O 1
ID
1
Code indicating a specific health situation
INDUSTRY NAME: Health Related Code
CODE
DEFINITION
N
None
S
Substance Abuse
T
Tobacco Use
U
Unknown
Not Used
1-2
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
1-3
374
Date/Time Qualifier
X 1
ID
3
Not Used
1-4
373
Date
X 1
DT
8
Not Used
1-5
373
Date
X 1
DT
8
Not Used
2
65
Height
O 1
R
1/8
Not Used
3
81
Weight
O 1
R
1/10
Not Used
4
81
Weight
O 1
R
1/10
Not Used
5
352
Description
O 1
AN
1/80
Not Used
6
1213
Current Health Condition Code
O 1
ID
1
Not Used
7
352
Description
O 1
AN
1/80

LUI*LE - MEMBER LANGUAGE

X12 Name:
Language Use
X12 Purpose:
To specify language, type of usage, and proficiency or fluency
X12 Syntax:
  1. P0102
    If either LUI01 or LUI02 is present, then the other is required.
  2. L040203
    If LUI04 is present, then at least one of LUI02 or LUI03 are required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
>1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
LUI✱LE✱SPA✱✱8~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when a value is being reported in the LUI02 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
LE
ISO 639 Language Codes
CODE SOURCE: 102: Languages
Situational
2
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEMANTIC: LUI02 is the language code.
SEGMENT SYNTAX: P0102, L040203
SITUATIONAL RULE: Required when the information source is able to code the language identification. If not required by this implementation guide, do not send.
INDUSTRY NAME: Language Code
Situational
3
352
Description
X 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEMANTIC: LUI03 is the name of the language.
SEGMENT SYNTAX: L040203
SITUATIONAL RULE: Required when the information source is unable to code the necessary language identification in LUI01 and LUI02. If not required by this implementation guide, do not send.
INDUSTRY NAME: Language Description
Situational
4
1303
Use of Language Indicator Code
O 1
ID
1/2
Code indicating the use of a language
SEGMENT SYNTAX: L040203
SITUATIONAL RULE: Required when available in the information source's system. If not required by this implementation guide, do not send.
INDUSTRY NAME: Language Use Indicator
CODE
DEFINITION
5
Language Reading
6
Language Writing
7
Language Speaking
8
Native Language
Not Used
5
1476
Language Proficiency Indicator Code
O 1
ID
1

NM1*70 - PREVIOUSLY SUBMITTED MEMBER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when NM101 in Loop 2100A is equal to `74'. If not required by this implementation guide, do not send.
TR3 Notes:
This segment is used when updating previously submitted member information.
TR3 Example:
NM1✱70✱1✱SMYTH✱JON~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
70
Prior Incorrect Insured
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Previously Submitted Member Last Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when the person has a first name which was previously submitted. If not required by this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when the person has a middle name which was previously submitted. If not required by this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Middle Name
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
SITUATIONAL RULE: Required when the person has a prefix which was previously submitted. If not required by this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when the person has a suffix which was previously submitted. If not required by this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when a value is being reported in the NM109 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
34
Social Security Number
MI
Member Identification Number
TA
Taxpayer ID Number
Use when reporting Individual Taxpayer Identification Number (ITIN).
ZZ
Mutually Defined
Use when established by the Trading Partner Agreement and the other code values are not applicable.
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when the member's identifier was previously submitted. If not required by this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Identifier
NM109 is the identifier that was previously submitted.
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

DMG*D8 - PREVIOUSLY SUBMITTED MEMBER DEMOGRAPHICS

X12 Name:
Demographic Information
X12 Purpose:
To supply demographic information
X12 Syntax:
  1. P0102
    If either DMG01 or DMG02 is present, then the other is required.
  2. P1011
    If either DMG10 or DMG11 is present, then the other is required.
  3. C1105
    If DMG11 is present, then DMG05 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when there is a change to the previously submitted demographic information. If not required by this implementation guide, do not send.
TR3 Notes:
This segment is used to change or correct demographic information. Only send the information that is being changed or corrected.
TR3 Example:
DMG✱D8✱19750915✱F✱M~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Situational
1
1250
Date Time Period Format Qualifier
X 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when DMG02 is used. If not required by this implementation guide, do not send.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Situational
2
1251
Date Time Period
X 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
SEMANTIC: DMG02 is the date of birth.
SEGMENT SYNTAX: P0102
SITUATIONAL RULE: Required when the member's birth date is being corrected. If not required by this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Birth Date
Situational
3
1068
Gender Code
O 1
ID
1
Code indicating the sex of the individual
SITUATIONAL RULE: Required when the members gender is being corrected. If not required by this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Gender
CODE
DEFINITION
F
Female
M
Male
U
Unknown
Situational
4
1067
Marital Status Code
O 1
ID
1
Code specifying the marital status of a person
SITUATIONAL RULE: Required when the members Marital Status Code is being corrected. If not required this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Marital Status
CODE
DEFINITION
B
Registered Domestic Partner
D
Divorced
I
Single
M
Married
R
Unreported
S
Separated
U
Unmarried (Single or Divorced or Widowed)
W
Widowed
X
Legally Separated
Situational
5
C056
Composite Race or Ethnicity Information
X 25
To send general and detailed information on race or ethnicity
X12 COMPOSITE SYNTAX NOTES: P0203
If either C05602 or C05603 is present, then the other is required.
X12 COMPOSITE SEMANTIC NOTES: C056-02 and C056-03 are used to specify detailed information about race or ethnicity.
SITUATIONAL RULE: Required when the member's Race or Ethnicity is being corrected. If not required this implementation guide, do not send.
Situational
5-1
1109
Race or Ethnicity Code
O 1
ID
1
Code indicating the racial or ethnic background of a person; it is normally self-reported; Under certain circumstances this information is collected for United States Government statistical purposes
SITUATIONAL RULE: Required when the member's Race or Ethnicity is being corrected. If not required this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Race or Ethnicity Code
CODE
DEFINITION
7
Not Provided
8
Not Applicable
A
Asian or Pacific Islander
B
Black
C
Caucasian
D
Subcontinent Asian American
E
Other Race or Ethnicity
F
Asian Pacific American
G
Native American
H
Hispanic
I
American Indian or Alaskan Native
J
Native Hawaiian
N
Black (Non-Hispanic)
O
White (Non-Hispanic)
P
Pacific Islander
Z
Mutually Defined
Situational
5-2
1270
Code List Qualifier Code
X 1
ID
1/3
Code identifying a specific industry code list
COMPOSITE SYNTAX: P0203
SITUATIONAL RULE: Required when the member's Race or Ethnicity is being corrected. If not required this implementation guide, do not send.
CODE
DEFINITION
RET
Classification of Race or Ethnicity
CODE SOURCE: 859: Classification of Race or Ethnicity
Situational
5-3
1271
Industry Code
X 1
AN
1/30
Code indicating a code from a specific industry code list
COMPOSITE SYNTAX: P0203
SITUATIONAL RULE: Required when the member's Race or Ethnicity is being corrected. If not required this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Race or Ethnicity Code
Situational
6
1066
Citizenship Status Code
O 1
ID
1/2
Code indicating citizenship status
SITUATIONAL RULE: Required when the member's citizenship is being corrected. If not required this implementation guide, do not send.
INDUSTRY NAME: Previously Submitted Member Citizenship Status Code
CODE
DEFINITION
1
U.S. Citizen
2
Non-Resident Alien
3
Resident Alien
4
Illegal Alien
5
Alien
6
U.S. Citizen - Non-Resident
7
U.S. Citizen - Resident
Not Used
7
26
Country Code
O 1
ID
2/3
Not Used
8
659
Basis of Verification Code
O 1
ID
1/2
Not Used
9
380
Quantity
O 1
R
1/15
Not Used
10
1270
Code List Qualifier Code
X 1
ID
1/3
Not Used
11
1271
Industry Code
X 1
AN
1/30
Not Used
12
26
Country Code
O 1
ID
2/3

NM1*31 - MEMBER MAILING ADDRESS

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when the member mailing address is different from the residence address sent in Loop 2100A or when the dependent's mailing address is different from the Subscriber's. If not required by this implementation guide, do not send.
TR3 Example:
NM1✱31✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
31
Postal Mailing Address
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Not Used
3
1035
Name Last or Organization Name
X 1
AN
1/80
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Not Used
8
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
9
67
Identification Code
X 1
AN
2/80
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - MEMBER MAILING STREET ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N3✱P.O. Box 1234~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Member Mailing Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required if a second address line exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Mailing Address Line

N4 - MEMBER MAILING CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Member Mailing City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Mailing State Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Mailing Postal Zone or ZIP Code
Use 9 digit Zip code for U.S. addresses when available in Information Source's system.
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Mailing Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Mailing Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

NM1*36 - MEMBER EMPLOYER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Notes:
This segment is not used to collect Coordination of Benefits (COB) information. COB information must be passed in Loop 2320.
TR3 Example:
NM1✱36✱2✱ABC CORP.~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
36
Employer
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Member Employer Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM102 is equal to `1' (Person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Employer First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required if supplied by the member and NM102 equals `1'. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Employer Middle Name
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
SITUATIONAL RULE: Required if supplied by the member and NM102 equals `1'. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Employer Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required if supplied by the member and NM102 equals `1'. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Employer Name Suffix
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when a value is being reported in the NM109 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
24
Employer's Identification Number
34
Social Security Number
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Employer Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

NM1 - RESPONSIBLE PERSON

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required to identify the person(s), other than the subscriber, who are responsible for the member. If not required by this implementation guide, do not send.
TR3 Example:
NM1✱QD✱1✱CASE✱JOHN~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
6Y
Case Manager
E1
Person or Other Entity Legally Responsible for a Child
Use when identifying a legal indemnity situation.
This code is used when a Qualified Medical Child Support Order (QMSCO) is present.
EI
Executor of Estate
Use when the subscriber is deceased and the executor/responsible party is other than a surviving spouse.
EXS
Ex-spouse
Use when identifying a separated spouse under a separation agreement, or that the member is the divorced spouse and self responsible. This is NOT USED to identify the custodial parent for dependent children after a divorce.
GB
Other Insured
GD
Guardian
J6
Power of Attorney
LR
Legal Representative
QD
Responsible Party
S1
Parent
S3
Custodial Parent
TZ
Significant Other
X4
Spouse
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Responsible Person Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM102 is equal to "1" (person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 is equal to "1" (person) and the person has a middle name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person Middle Name
Situational
6
1038
Name Prefix
O 1
AN
1/10
Prefix to individual name
SITUATIONAL RULE: Required when person has a prefix. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person Name Prefix
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when person has a suffix. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person Suffix Name
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when a value is being reported in the NM109 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
34
Social Security Number
ZZ
Mutually Defined
Use when established by the Trading Partner Agreement and the other code values are not applicable.
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

PER*RP - RESPONSIBLE PERSON COMMUNICATIONS NUMBERS

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number always includes the area code and phone number using the format AAABBBCCCC, where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534)224-2525 would be represented as 5342242525).
TR3 Example:
PER✱RP✱✱HP✱8015554321~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
RP
Responsible Person
Not Used
2
93
Name
O 1
AN
1/60
Required
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
CP
Cellular Phone
EM
Electronic Mail
HP
Home Phone Number
TE
Telephone
WP
Work Phone Number
Required
4
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
Situational
5
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a value is being reported in the PER06 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
AP
Alternate Telephone
CP
Cellular Phone
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
HP
Home Phone Number
TE
Telephone
WP
Work Phone Number
Situational
6
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when additional communication numbers are available. If not required by this implementation guide, do not send.
Situational
7
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a value is being reported in the PER08 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
AP
Alternate Telephone
CP
Cellular Phone
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
HP
Home Phone Number
TE
Telephone
WP
Work Phone Number
Situational
8
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when additional communication numbers are available. If not required by this implementation guide, do not send.
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

N3 - RESPONSIBLE PERSON STREET ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
N3✱50 ORCHARD STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Responsible Person Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required if a second address line exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person Address Line

N4 - RESPONSIBLE PERSON CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when N3 segment is sent. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Responsible Person City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person State Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Responsible Person Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

DSB - DISABILITY INFORMATION

X12 Name:
Disability Information
X12 Purpose:
To supply disability information
X12 Syntax:
P0708
If either DSB07 or DSB08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when disability information about a member is added or changed. If not required by this implementation guide, do not send.
TR3 Notes:
If disability was previously reported in error, see section 1.4.9 for instructions on how to correct.
TR3 Example:
DSB✱2✱✱✱✱✱✱DC✱N189~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1146
Disability Type Code
M 1
ID
1
Code identifying the disability status of the individual
CODE
DEFINITION
1
Short Term Disability
2
Long Term Disability
3
Permanent or Total Disability
4
No Disability
5
Partial Disability
Not Used
2
380
Quantity
O 1
R
1/15
Not Used
3
1149
Occupation Code
O 1
ID
4/6
Not Used
4
1154
Work Intensity Code
O 1
ID
1
Not Used
5
1161
Product Option Code
O 1
ID
1/2
Not Used
6
782
Monetary Amount
O 1
R
1/18
Situational
7
235
Product/Service ID Qualifier
X 1
ID
2
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a value is being reported in the DSB08 element. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Type Code
CODE
DEFINITION
DC
International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
CODE SOURCE: 897: International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)
Situational
8
1137
Medical Code Value
X 1
AN
1/15
Code value for describing a medical condition or procedure
SEMANTIC: DSB08 is the functional status code for the disability.
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
INDUSTRY NAME: Diagnosis Code

DTP*360 - DISABILITY ELIGIBILITY BEGIN DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when reporting a disabled member (DSB01 is `1', `2', `3' or `5') and the disability begin date is known by the sender.
Or
Required when disability begin date changes for a previously reported member, and the disability begin date is known by the sender.

If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment is used to send the first date of disability.
  2. If disability was previously reported in error, see section 1.4.9 for instructions on how to correct.
TR3 Example:
DTP✱360✱D8✱19961001~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
360
Initial Disability Period Start
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP*361 - DISABILITY ELIGIBILITY END DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when reporting a disabled member (DSB01 is `1', `2', `3' or `5') and the disability end date is known by the sender.
Or
Required when disability end date changes for a previously reported member, and the disability end date is known by the sender.
Or
Required when DSB01 is equal to 4 and member is no longer on disability and the disability end date is known by the sender.

If not required by this implementation guide, do not send.
TR3 Notes:
  1. This segment is used to send the last date of disability.
  2. If disability was previously reported in error, see section 1.4.9 for instructions on how to correct.
TR3 Example:
DTP✱361✱D8✱20170701~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
361
Initial Disability Period End
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

HD - BENEFIT COVERAGE

X12 Name:
Health Coverage
X12 Purpose:
To provide information on health coverage
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
Refer to section 1.4.4 "Termination" for additional information relative to reporting termination of a member's coverage.
TR3 Example:
HD✱021✱✱HLT✱PLAN A BCD✱FAM~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
875
Maintenance Type Code
M 1
ID
3
Code identifying the specific type of item maintenance
Required to identify the specific type of item maintenance.
CODE
DEFINITION
001
Change
002
Delete
Use when reporting deletion of an incorrect coverage record.
021
Addition
024
Cancellation or Termination
Use when reporting a cancelation/termination of coverage.
025
Reinstatement
026
Correction
Use when reporting correction to previously reported information.
030
Audit or Compare
ZZZ
Mutually Defined
Use when established by the Trading Partner Agreement.
Not Used
2
1203
Maintenance Reason Code
O 1
ID
2/3
Required
3
1205
Insurance Line Code
O 1
ID
2/3
Code identifying a group of insurance products
CODE
DEFINITION
AG
Preventative Care/Wellness
AH
24 Hour Care
AJ
Medicare Risk
AK
Mental Health
DCP
Dental Capitation
Use when identifying a dental managed care organization (DMO).
DEN
Dental
EPO
Exclusive Provider Organization
FAC
Facility
HE
Hearing
HLT
Health
Use when reporting hospital or professional coverage.
HMO
Health Maintenance Organization
LTC
Long-Term Care
LTD
Long-Term Disability
MM
Major Medical
MOD
Mail Order Drug
PDG
Prescription Drug
POS
Point of Service
PPO
Preferred Provider Organization
PRA
Practitioners
STD
Short-Term Disability
UR
Utilization Review
VIS
Vision
Situational
4
1204
Plan Coverage Description
O 1
AN
1/50
A description or number that identifies the plan or coverage
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
INDUSTRY NAME: Benefit Coverage Description
Situational
5
1207
Coverage Level Code
O 1
ID
3
Code indicating the level of coverage being provided for this insured
SITUATIONAL RULE: Required when member is subscriber. If not required by this implementation guide, do not send.
See section 1.4.7, Coverage Levels and Dependents, for additional information.
CODE
DEFINITION
CHD
Children Only
DEP
Dependents Only
E1D
Employee and One Dependent
Use when the dependent is a non-spouse dependent. This code is not used for identification of Employee and Spouse. See code ESP.
E2D
Employee and Two Dependents
E3D
Employee and Three Dependents
E5D
Employee and One or More Dependents
E6D
Employee and Two or More Dependents
E7D
Employee and Three or More Dependents
E8D
Employee and Four or More Dependents
E9D
Employee and Five or More Dependents
ECH
Employee and Children
EMP
Employee Only
ESP
Employee and Spouse
FAM
Family
IND
Individual
S1C
Subscriber and 1 child
S5C
Subscriber and 1 or more children
S6C
Subscriber and 2 or more children
SPC
Spouse and Children
SPO
Spouse Only
SS1
Subscriber, spouse, and 1 child
SS5
Subscriber, spouse, and 1 or more children
SS6
Subscriber, spouse, and 2 or more children
SSP
Subscriber and spouse
TWO
Two Party
Not Used
6
609
Count
O 1
N
1/9
Not Used
7
609
Count
O 1
N
1/9
Not Used
8
1209
Underwriting Decision Code
O 1
ID
1
Not Used
9
1073
Yes/No Condition or Response Code
O 1
ID
1
Not Used
10
1211
Drug House Code
O 1
ID
2/3
Not Used
11
1073
Yes/No Condition or Response Code
O 1
ID
1

DTP*300 - ENROLLMENT SIGNATURE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱300✱D8✱20161001~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
300
Enrollment Signature Date
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP - PREMIUM PAYMENT DATES

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱343✱D8✱20161001~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
343
Premium Paid to Date End
543
Last Premium Paid Date
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP*303 - MAINTENANCE EFFECTIVE DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
DTP✱303✱D8✱20161001~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
303
Maintenance Effective
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP - BENEFIT DATES

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
2
TR3 Notes:
The Benefit Begin Date must always be reported. The Benefit End date is only reported when there is an end date or benefit was reported in error.
TR3 Example:
DTP✱348✱D8✱20161001~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
348
Benefit Begin
349
Benefit End
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

DTP*695 - PREVIOUS PERIOD DATES

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱695✱RD8✱20151001-20151231~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
695
Previous Period
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times

AMT - HEALTH COVERAGE POLICY AMOUNT

X12 Name:
Monetary Amount Information
X12 Purpose:
To indicate the total monetary amount
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
5
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
AMT✱C1✱20~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
522
Amount Qualifier Code
M 1
ID
1/3
Code specifying the amount qualifier
CODE
DEFINITION
B9
Co-insurance - Actual
C1
Co-Payment Amount
D2
Deductible Amount
P3
Premium Amount
ZZ
Mutually Defined
Use when established by the Trading Partner Agreement.
Required
2
782
Monetary Amount
M 1
R
1/18
Monetary amount
Not Used
3
478
Credit/Debit Flag Code
O 1
ID
1

REF - BENEFIT COVERAGE POLICY RELATED INFORMATION

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
14
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
REF✱1L✱123456~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
17
Client Reporting Category
1L
Group or Policy Number
Use when a group number that applies to this individual's participation in the coverage passed in this HD loop is required by the terms of the Trading Partner Agreement.
9V
Payment Category
CE
Class of Contract Code
E8
Service Contract (Coverage) Number
M7
Medical Assistance Category
PID
Program Identification Number
RB
Rate code number
X9
Internal Control Number
XM
Issuer Number
XX1
Special Program Code
XX2
Service Area Code
ZX
County Code
ZZ
Mutually Defined
Use when established by the Trading Partner Agreement.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

IDC - IDENTIFICATION CARD

X12 Name:
Identification Card
X12 Purpose:
To provide notification to produce replacement identification card(s)
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
5
Situational Rule:
Required when requesting the production of an identification card as allowed under the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
IDC✱12345✱H~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1204
Plan Coverage Description
M 1
AN
1/50
A description or number that identifies the plan or coverage
If no additional information is needed, this element will be sent as a single zero.
Required
2
1215
Identification Card Type Code
M 1
ID
1
Code identifying the type of identification card
This code is used to identify that the card issued will be specific to the coverage identified in the related HD segment.
CODE
DEFINITION
D
Dental Insurance
E
Hearing Benefit
H
Health Insurance
P
Prescription Drug Service Drug Insurance
V
Vision Benefit
Situational
3
380
Quantity
O 1
R
1/15
Numeric value of quantity
SEMANTIC: IDC03 is the number of cards being requested.
SITUATIONAL RULE: Required if the number of card requests is greater than 1. If not required by this implementation guide, do not send.
INDUSTRY NAME: Identification Card Count
Only integer values are to be sent.
Situational
4
306
Action Code
O 1
ID
1/2
Code indicating type of action
SEMANTIC: IDC04 is the reason for the card being requested, i.e., add or a change.
SITUATIONAL RULE: Required if the sender knows the reason for the card request. If not required by this implementation guide, do not send.
CODE
DEFINITION
1
Add
2
Change (Update)
RX
Replace
Use when requesting replacement cards with no change to data.

LX - PROVIDER INFORMATION

X12 Name:
Transaction Set Line Number
X12 Purpose:
To reference a line number in a transaction set
X12 Set Notes:
NOTE: Loop 2310 contains information about the primary care providers for the subscriber or the dependent, and about the beneficiaries of any employer-sponsored life insurance for the subscriber.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when information about the primary care or other provider (for example pharmacy) chosen by the enrollee is available in the information source system. If not required by this implementation guide, do not send.
TR3 Notes:
The LX segment must begin with one and is incremented by one for each additional health care service provider reported.
TR3 Example:
LX✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
554
Assigned Number
M 1
N
1/9
Number assigned for differentiation within a transaction set
This is a sequential number representing the number of loops for this insured person. Begin with 1 for each insured person.

NM1 - PROVIDER NAME

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
X12 Set Notes:
NOTE: Either NM1 or N1 will be included depending on whether an individual or organization is being specified.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
NM1✱P3✱1✱SMITH✱JOHN✱✱✱✱SV✱25341234567~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
3D
Obstetrics and Gynecology Facility
Use when an Obstetrician/Gynecologist is chosen.
80
Hospital
OD
Doctor of Optometry
P3
Primary Care Provider
Use when reporting a primary care physician related to the benefit coverage reported in HD03.
QA
Pharmacy
QN
Dentist
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
1
Person
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
INDUSTRY NAME: Provider Last or Organization Name
Situational
4
1036
Name First
O 1
AN
1/35
Individual first name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the person has a first name. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider First Name
Situational
5
1037
Name Middle
O 1
AN
1/25
Individual middle name or initial
SITUATIONAL RULE: Required when NM102 = 1 (person) and the person has a middle name or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider Middle Name
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Situational
7
1039
Name Suffix
O 1
AN
1/10
Suffix to individual name
SITUATIONAL RULE: Required when NM102 = 1 (person) and the person has a name suffix or initial of the person is needed to identify the individual. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider Name Suffix
Required
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
CODE
DEFINITION
24
Employer's Identification Number
34
Social Security Number
FI
Federal Taxpayer's Identification Number
PC
Provider Commercial Number
SV
Service Provider Number
Use when submitting a provider number assigned by the payer.
XX
Standard Unique Health Identifier for Health Care Providers (NPI)
CODE SOURCE: 537: National Provider Identifier (NPI)
Required
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
INDUSTRY NAME: Provider Identifier
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - PROVIDER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
2
Situational Rule:
Required when the location of the named provider needs to be reported based on the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
N3✱50 ORCHARD STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
INDUSTRY NAME: Provider Address Line
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required if a second address line exists. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider Address Line

N4 - PROVIDER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the location of the named provider needs to be reported based on the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
INDUSTRY NAME: Provider City Name
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider State Code
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider Postal Zone or ZIP Code
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider Country Code
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
INDUSTRY NAME: Provider Country Subdivision Code
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

PER*IC - PROVIDER COMMUNICATIONS NUMBERS

X12 Name:
Administrative Communications Contact
X12 Purpose:
To identify a person or office to whom administrative communications should be directed
X12 Syntax:
  1. P0304
    If either PER03 or PER04 is present, then the other is required.
  2. P0506
    If either PER05 or PER06 is present, then the other is required.
  3. P0708
    If either PER07 or PER08 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Notes:
When the communication number represents a telephone number in the United States and other countries using the North American Dialing Plan (for voice, data, fax, etc.), the communication number always includes the area code and phone number using the format AAABBBCCCC, where AAA is the area code, BBB is the telephone number prefix, and CCCC is the telephone number (e.g. (534)224-2525 would be represented as 5342242525).
TR3 Example:
PER✱IC✱✱WP✱80155504321~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
366
Contact Function Code
M 1
ID
2
Code identifying the major duty or responsibility of the person or group named
CODE
DEFINITION
IC
Information Contact
Not Used
2
93
Name
O 1
AN
1/60
Required
3
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0304
CODE
DEFINITION
EM
Electronic Mail
FX
Facsimile
WP
Work Phone Number
Required
4
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0304
Situational
5
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when a value is being reported in the PER06 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
WP
Work Phone Number
Situational
6
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0506
SITUATIONAL RULE: Required when additional communication numbers are available. If not required by this implementation guide, do not send.
Situational
7
365
Communication Number Qualifier
X 1
ID
2
Code identifying the type of communication number
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when a value is being reported in the PER08 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
EM
Electronic Mail
EX
Telephone Extension
FX
Facsimile
WP
Work Phone Number
Situational
8
364
Communication Number
X 1
AN
1/2048
Complete communications number including country or area code when applicable
SEGMENT SYNTAX: P0708
SITUATIONAL RULE: Required when additional communication numbers are available. If not required by this implementation guide, do not send.
Not Used
9
443
Contact Inquiry Reference
O 1
AN
1/20

PRV*OT - PROVIDER TAXONOMY INFORMATION

X12 Name:
Provider Information
X12 Purpose:
To specify the identifying characteristics of a provider
X12 Syntax:
P0203
If either PRV02 or PRV03 is present, then the other is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
PRV✱OT✱PXC✱2086H0002X~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1221
Provider Code
M 1
ID
1/3
Code identifying the type of provider
CODE
DEFINITION
OT
Other Physician
Required
2
128
Reference Identification Qualifier
X 1
ID
2/3
Code identifying the Reference Identification
SEGMENT SYNTAX: P0203
CODE
DEFINITION
PXC
Health Care Provider Taxonomy Code
CODE SOURCE: 682: Health Care Provider Taxonomy
Required
3
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: P0203
INDUSTRY NAME: Provider Taxonomy Code
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
4
156
State or Province Code
O 1
ID
2
Not Used
5
C035
Provider Specialty Information
O 1
Not Used
6
1223
Provider Organization Code
O 1
ID
3

PLA - PROVIDER CHANGE REASON

X12 Name:
Place or Location
X12 Purpose:
To indicate action to be taken for the location specified and to qualify the location specified
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
TR3 Notes:
If there is no change for this provider loop, use value ND in PLA01 and report the initial effective date in PLA03.
TR3 Example:
PLA✱2✱P3✱20150628~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
306
Action Code
M 1
ID
1/2
Code indicating type of action
CODE
DEFINITION
1
Add
2
Change (Update)
3
Delete
ND
No Change
Required
2
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
3D
Obstetrics and Gynecology Facility
Use when an Obstetrician/Gynecologist is chosen
80
Hospital
OD
Doctor of Optometry
P3
Primary Care Provider
Use when reporting a primary care physician related to the benefit coverage reported in HD03.
QA
Pharmacy
QN
Dentist
Required
3
373
Date
M 1
DT
8
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
SEMANTIC: PLA03 is the effective date for the action identified in PLA01.
INDUSTRY NAME: Provider Effective Date
This is the effective date of the change of health care service provider
Not Used
4
337
Time
O 1
TM
4/8
Not Used
5
1203
Maintenance Reason Code
O 1
ID
2/3

COB - COORDINATION OF BENEFITS

X12 Name:
Coordination of Benefits
X12 Purpose:
To supply information on coordination of benefits
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement and the information source has information related to a member's separate policy or group number with similar coverage to the HD03 (Insurance Coverage Line) in Loop 2300. It not required by this implementation guide, do not send.
TR3 Notes:
If using this loop, the Information Source must identify their sequence as well as other payers' sequences.
TR3 Example:
COB✱P✱✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
1138
Payer Responsibility Sequence Number Code
O 1
ID
1
Code identifying the insurance carrier's level of responsibility for a payment of a claim
CODE
DEFINITION
P
Primary
S
Secondary
T
Tertiary
U
Unknown
Not Used
2
127
Reference Identification
O 1
AN
1/80
Required
3
1143
Coordination of Benefits Code
O 1
ID
1
Code identifying whether there is a coordination of benefits
CODE
DEFINITION
1
Coordination of Benefits
6
No Coordination of Benefits
Use when the payer related to this iteration of Loop ID 2320 is the Information Source for this transaction.
Not Used
4
1365
Service Type Code
O 9
ID
1/2

REF - ADDITIONAL COORDINATION OF BENEFITS IDENTIFIERS

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
4
Situational Rule:
Required when available in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Example:
REF✱6P✱AZ12345~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
1W
Member Identification Number
60
Account Suffix Code
6P
Group Number
A6
Provider Identifier
SY
Social Security Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*344 - COORDINATION OF BENEFITS BEGIN DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱344✱D8✱20150401~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
344
Coordination of Benefits Begin
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Coordination of Benefits Begin Date

DTP*345 - COORDINATION OF BENEFITS END DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when available in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Example:
DTP✱345✱D8✱20150401~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
345
Coordination of Benefits End
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Coordination of Benefits End Date

NM1 - COORDINATION OF BENEFITS RELATED PAYER

X12 Name:
Individual or Organizational Name
X12 Purpose:
To supply the full name of an individual or organizational entity
X12 Syntax:
  1. P0809
    If either NM108 or NM109 is present, then the other is required.
  2. C1110
    If NM111 is present, then NM110 is required.
  3. C1203
    If NM112 is present, then NM103 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement and available in the Information Source's system. If not required by this implementation guide, do not send.
TR3 Example:
NM1✱IN✱2✱ABC INSURANCE CO~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
36
Employer
GW
Group
IN
Insurer
PR
Payer
Required
2
1065
Entity Type Qualifier
M 1
ID
1
Code identifying the type of entity
SEMANTIC: NM102 qualifies NM103.
CODE
DEFINITION
2
Non-Person Entity
Required
3
1035
Name Last or Organization Name
X 1
AN
1/80
Individual last name or organizational name
SEGMENT SYNTAX: C1203
Not Used
4
1036
Name First
O 1
AN
1/35
Not Used
5
1037
Name Middle
O 1
AN
1/25
Not Used
6
1038
Name Prefix
O 1
AN
1/10
Not Used
7
1039
Name Suffix
O 1
AN
1/10
Situational
8
66
Identification Code Qualifier
X 1
ID
1/2
Code specifying the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when a value is being reported in the NM109 element. If not required by this implementation guide, do not send.
CODE
DEFINITION
24
Employer's Identification Number
FI
Federal Taxpayer's Identification Number
NI
National Association of Insurance Commissioners (NAIC) Identification
XV
Standard Unique Health Plan Identifier (HPID)
Use when reporting Health Plan ID (HPID) or Other Entity Identifier (OEID).
CODE SOURCE: 540: Health Plan Identifier (HPID)
Situational
9
67
Identification Code
X 1
AN
2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0809
SITUATIONAL RULE: Required when supplied by the employee to the sponsor. If not required by this implementation guide, do not send.
Not Used
10
706
Entity Relationship Code
X 1
ID
2
Not Used
11
98
Entity Identifier Code
O 1
ID
2/3
Not Used
12
1035
Name Last or Organization Name
O 1
AN
1/80

N3 - COORDINATION OF BENEFITS RELATED PAYER ADDRESS

X12 Name:
Party Location
X12 Purpose:
To specify the location of the named party
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement and available in the information source's system. If not required by this implementation guide, do not send.
TR3 Example:
N3✱50 ORCHARD STREET~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
166
Address Information
M 1
AN
1/55
Address information
Situational
2
166
Address Information
O 1
AN
1/55
Address information
SITUATIONAL RULE: Required if a second address line exists. If not required by this implementation guide, do not send.

N4 - COORDINATION OF BENEFITS RELATED PAYER CITY, STATE, ZIP CODE

X12 Name:
Geographic Location
X12 Purpose:
To specify the geographic place of the named party
X12 Syntax:
  1. E0207
    Only one of N402 or N407 may be present.
  2. E0308
    Only one of N403 or N408 may be present.
  3. C0605
    If N406 is present, then N405 is required.
  4. C0704
    If N407 is present, then N404 is required.
Loop:
Loop Usage:
Situational
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when N3 segment is sent. If not required by this implementation guide, do not send.
TR3 Example:
N4✱KANSAS CITY✱MO✱64108~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
19
City Name
O 1
AN
2/30
Free-form text for city name
COMMENT: A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Situational
2
156
State or Province Code
X 1
ID
2
Code specifying the Standard State/Province as defined by appropriate government agency
SEGMENT SYNTAX: E0207
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada. If not required by this implementation guide, do not send.
CODE SOURCE 22: States and Provinces
Situational
3
116
Postal Code
X 1
ID
3/15
Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)
COMMENT: N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
SEGMENT SYNTAX: E0308
SITUATIONAL RULE: Required when the address is in the United States of America, including its territories, or Canada, or when a postal code exists for the country in N404. If not required by this implementation guide, do not send.
  • CODE SOURCE 51: ZIP Code
  • CODE SOURCE 932: Universal Postal Codes
Situational
4
26
Country Code
X 1
ID
2/3
Code identifying the country
SEGMENT SYNTAX: C0704
SITUATIONAL RULE: Required when the address is outside the United States of America. If not required by this implementation guide, do not send.
Use the alpha-2 country codes from Part 1 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
5
309
Location Qualifier
X 1
ID
1/2
Not Used
6
310
Location Identifier
O 1
AN
1/30
Situational
7
1715
Country Subdivision Code
X 1
ID
1/3
Code identifying the country subdivision
SEGMENT SYNTAX: E0207, C0704
SITUATIONAL RULE: Required when the address is not in the United States of America, including its territories, or Canada, and the country in N404 has administrative subdivisions such as but not limited to states, provinces, cantons, etc. If not required by this implementation guide, do not send.
Use the country subdivision codes from Part 2 of ISO 3166.
CODE SOURCE 5: Countries, Currencies and Funds
Not Used
8
1702
Postal Code-Formatted
X 1
AN
3/20

LS - ADDITIONAL REPORTING CATEGORIES

X12 Name:
Loop Header
X12 Purpose:
To indicate that the next segment begins a loop
X12 Comments:
See Figures Appendix for an explanation of the use of the LS and LE segments.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when needed to provide additional reporting categories about the member. If not required by this implementation guide, do not send.
TR3 Example:
LS✱2700~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
447
Loop Identifier Code
M 1
AN
1/6
The loop ID number given on the transaction set diagram is the value for this data element in segments LS and LE
Use the value 2700.

LX - MEMBER REPORTING CATEGORIES

X12 Name:
Transaction Set Line Number
X12 Purpose:
To reference a line number in a transaction set
Loop:
Loop Usage:
Situational
Segment Usage:
Required
Segment Repeat:
1
Situational Rule:
Required when needed to provide additional reporting categories about the member. If not required by this implementation guide, do not send.
TR3 Example:
LX✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
554
Assigned Number
M 1
N
1/9
Number assigned for differentiation within a transaction set
Use this sequential non-negative integer for LX loops for this member's additional reporting categories.

N1*IAE - REPORTING CATEGORY

X12 Name:
Party Identification
X12 Purpose:
To identify a party by type of organization, name, and code
X12 Syntax:
  1. R0203
    At least one of N102 or N103 is required.
  2. P0304
    If either N103 or N104 is present, then the other is required.
  3. C0703
    If N107 is present, then N103 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
N1✱IAE✱SOUTHEASTERN UNION~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
98
Entity Identifier Code
M 1
ID
2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE
DEFINITION
IAE
Member
Required
2
93
Name
X 1
AN
1/60
Free-form name
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Member Reporting Category Name
Not Used
3
66
Identification Code Qualifier
X 1
ID
1/2
Not Used
4
67
Identification Code
X 1
AN
2/80
Not Used
5
706
Entity Relationship Code
O 1
ID
2
Not Used
6
98
Entity Identifier Code
O 1
ID
2/3
Not Used
7
C076
Composite Identification Codes
O 1

REF - REPORTING CATEGORY REFERENCE

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
REF✱26✱442✱LOCAL UNION~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
00
Contracting District Number
17
Client Reporting Category
18
Plan Number
19
Division Identifier
26
Union Number
3H
Case Number
3L
Branch Identifier
6M
Application Number
9V
Payment Category
9X
Account Category
GE
Geographic Number
LU
Location Number
PID
Program Identification Number
XX1
Special Program Code
XX2
Service Area Code
YY
Geographic Key
ZZ
Mutually Defined
Use when established by the Trading Partner Agreement.
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Member Reporting Category Reference ID
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Situational
3
352
Description
X 1
AN
1/80
A free-form description to clarify the related data elements and their content
SEGMENT SYNTAX: R0203
SITUATIONAL RULE: Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
INDUSTRY NAME: Member Reporting Category Reference ID
Not Used
4
C040
Reference Identifier
O 1

REF*F8 - MEMBER RECORD CONTROL NUMBER

X12 Name:
Reference Information
X12 Purpose:
To specify identifying information
X12 Syntax:
R0203
At least one of REF02 or REF03 is required.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Notes:
Used when a trading partner must assign a unique number (not PHI or PII) to a member's record for reporting.
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
128
Reference Identification Qualifier
M 1
ID
2/3
Code identifying the Reference Identification
CODE
DEFINITION
F8
Original Reference Number
Required
2
127
Reference Identification
X 1
AN
1/80
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEGMENT SYNTAX: R0203
Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
Not Used
3
352
Description
X 1
AN
1/80
Not Used
4
C040
Reference Identifier
O 1

DTP*007 - REPORTING CATEGORY DATE

X12 Name:
Date or Time or Period
X12 Purpose:
To specify any or all of a date, a time, or a time period
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when specified by the terms of the Trading Partner Agreement. If not required by this implementation guide, do not send.
TR3 Notes:
Use this segment to associate a date or date range with a reporting category.
TR3 Example:
DTP✱007✱RD8✱20150101-20150531~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
374
Date/Time Qualifier
M 1
ID
3
Code specifying type of date or time, or both date and time
INDUSTRY NAME: Date Time Qualifier
CODE
DEFINITION
007
Effective
Required
2
1250
Date Time Period Format Qualifier
M 1
ID
2/3
Code indicating the date format, time format, or date and time format
SEMANTIC: DTP02 is the date or time or period format that will appear in DTP03.
CODE
DEFINITION
D8
Date Expressed in Format CCYYMMDD
RD8
Range of Dates Expressed in Format CCYYMMDD-CCYYMMDD
A range of dates expressed in the format CCYYMMDD-CCYYMMDD where CCYY is the numerical expression of the century CC and year YY. MM is the numerical expression of the month within the year, and DD is the numerical expression of the day within the year; the first occurrence of CCYYMMDD is the beginning date and the second occurrence is the ending date.
Required
3
1251
Date Time Period
M 1
AN
1/35
Expression of a date, a time, or range of dates, times or dates and times
INDUSTRY NAME: Member Reporting Category Effective Date(s)

LE - ADDITIONAL REPORTING CATEGORIES LOOP TERMINATION

X12 Name:
Loop Trailer
X12 Purpose:
To indicate that the loop immediately preceding this segment is complete
X12 Comments:
See Figures Appendix for an explanation of the use of the LE and LS segments.
Loop:
Loop Usage:
Required
Segment Usage:
Situational
Segment Repeat:
1
Situational Rule:
Required when the LS segment in position 6880 is sent. If not required by this implementation guide, do not send.
TR3 Example:
LE✱2700~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
447
Loop Identifier Code
M 1
AN
1/6
The loop ID number given on the transaction set diagram is the value for this data element in segments LS and LE
Use the value 2700.

SE - TRANSACTION SET TRAILER

X12 Name:
Transaction Set Trailer
X12 Purpose:
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
X12 Comments:
SE is the last segment of each transaction set.
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
SE✱39✱0002~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
96
Number of Included Segments
M 1
N
1/10
Total number of segments included in a transaction set including ST and SE segments
INDUSTRY NAME: Transaction Segment Count
Required
2
329
Transaction Set Control Number
M 1
AN
4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
The Transaction Set Control Number in ST02 and SE02 must be identical.

GE - FUNCTIONAL GROUP TRAILER

X12 Name:
Functional Group Trailer
X12 Purpose:
To indicate the end of a functional group and to provide control information
X12 Comments:
The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header.
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
GE✱1✱1~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
97
Number of Transaction Sets Included
M 1
N
1/6
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Required
2
28
Group Control Number
M 1
N
1/9
Assigned number originated and maintained by the sender
SEMANTIC: The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06.

IEA - INTERCHANGE CONTROL TRAILER

X12 Name:
Interchange Control Trailer
X12 Purpose:
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Segment Usage:
Required
Segment Repeat:
1
TR3 Example:
IEA✱1✱000000905~
USAGE
SEQ
D.E. NUM
NAME
ATTRIBUTES
Required
1
I16
Number of Included Functional Groups
M 1
N
1/5
A count of the number of functional groups included in an interchange
Required
2
I12
Interchange Control Number
M 1
N
9
A control number assigned by the interchange sender
The Value in IEA02 must be identical to the value in ISA13.
logo

834 Plan Member Reporting (008020X318)

JANUARY 2022

Copyright © 2008-22, X12 Incorporated, Format © 2008-22 Washington Publishing Company. Exclusively published by the Washington Publishing Company. No part of this publication may be distributed, posted, reproduced, stored in a retrieval system, or transmitted in any form or by any means without the prior written permission of the copyright owner.

All rights reserved.

Abstract

The Plan Member Reporting implementation guide describes the use of the X12 834 transaction set for reporting plan members and member related information, which may or may not be available on a claim transaction, to All Payers Claims Databases for the purpose of enhancing health data reporting.

Preface

X12 standards are developed to identify the broadest data requirements for a transaction set. Type 3 Technical Reports (TR3), also known as implementation guides, define the explicit data requirements for a specific business purpose. Trading partners who implement according to the instructions in this TR3 can exchange data consistently with multiple trading partners.

As X12 does not define transport requirements, trading partners define their specific transport requirements separately.

1.1 Implementation Purpose and Scope

For the health care industry to achieve the potential administrative cost savings with Electronic Data Interchange (EDI), standards have been developed and need to be implemented consistently by all organizations. To facilitate a smooth transition into the EDI environment, uniform implementation is critical.

The purpose of this implementation guide is to provide standardized data requirements and content to users of Version 008020 of X12, Member Reporting (834). The 834 is used to transfer member information from a submitter of insurance coverage, benefits, or policy to a receiver.

This exchange may be performed directly or via transmission intermediaries, such as clearinghouses and value added networks. For further clarification on definitions of the participants, see X12 Wordbook for definitions.

This document provides a definitive statement of what trading partners must be able to support in this implementation of the 834.

1.2 Version Information

This implementation guide is based on the October 2020 X12 standards, referred to as Version 8, Release 2 (008020).

The unique Version/Release/Industry Identifier Code for transaction sets that are defined by this implementation guide is 008020X318.

The two-character Functional Identifier Code for the transaction set included in this implementation guide:

  • BE  Benefit Enrollment and Maintenance (834)

The Version/Release/Industry Identifier Code and the applicable Functional Identifier Code must be transmitted in the Functional Group Header (GS segment) that begins a functional group of these transaction sets. For more information, see the descriptions of GS01 and GS08 in Appendix C EDI Control Directory.

1.3.1 Batch and Real-Time Usage

There are multiple methods available for sending and receiving business transactions electronically. Two common modes for EDI transactions are batch and real-time.

Batch - In a batch mode the sender does not remain connected while the receiver processes the transactions. Processing is usually completed according to a set schedule. If there is an associated business response transaction (such as a 271 Response to a 270 Request for Eligibility), the receiver creates the response transaction and stores it for future delivery or transmits the response transaction back to the sender of the original transaction. The sender of the original transmission reconnects at a later time and picks up the response transaction. Note: The sender of the original transmission may not always be the entity that picks up the response transaction at a later time (e.g. Provider submitting through a clearinghouse.)

Real-Time - In real-time mode the sender remains connected while the receiver processes the transactions and returns a response transaction to the sender. This implementation guide does not set specific response time parameters for implementers.

This implementation guide is intended to support use in batch mode. This implementation guide is not intended to support use in real-time mode. A statement that the transaction is not intended to support a specific mode does not preclude its use in that mode between willing trading partners.

1.3.2 Other Usage Limitations

There are no other usage limitations.

1.4.1 Health Care Transaction Flow

Each X12 implementation guide explains how to use X12 transaction sets to meet a single defined business purpose. The diagrams found at https://www.x12.org/flow depict the business functions supported by the X12 health care implementation guides.

1.4.2 Information Flows

Figure 1.1 - Health Care

Health Care

Transaction sets included in the information flow diagram:

  • 834: Benefit Enrollment and Maintenance

1.4.3 Location of Insurance Benefit Identifiers

In this implementation of the 834 the Benefit Identifiers, such as policy numbers and group numbers, are reported in the REF segment at the Benefit Coverage level (Loop 2300).

1.4.4 Linking a Dependent to a Subscriber

Subscribers and dependents are sent as separate occurrences of Loop 2000. The initial reporting of benefit coverage for the subscriber must be sent before sending the initial benefit coverage for any of the subscriber's dependents. The reporting of a dependent may follow the reporting of the subscriber's benefit coverage in the same transmission, or it may be sent separately in a later transmission.

Information Sources use various means to link dependents to the subscriber. To allow linking between subscribers and dependents without making assumptions about the receiving system, the subscriber's unique identifier is sent in the Subscriber Identifier REF in Loop 2000 for both the subscriber and the dependents.

1.4.5 Cancellation

A benefit coverage cancellation, INS03 = 123 (Canceled by Administrator) in Loop 2000, is used to indicate that there should have been no coverage for the individual. This could be as a result of enrollment file corrections, choice on the part of the member or other file reconciliation.

1.4.6 Termination

A termination date passed at the INS level for an individual (that is, a termination date passed in the DTP segment in Loop 2000) indicates that all coverages for that individual are to be terminated in the receiver's system on the indicated date.

A termination date passed at the HD level (that is, a termination date passed in the DTP segment in Loop 2300 of any coverage type) applies to a specific benefit coverage, not the entire contract (or member).

1.4.7 Updates, Versus Full File Audits, Versus Full File Replacements

The 834 transaction can be used to provide either updates, full file audits, or full file replacements.

An update is either an "add", "terminate", "cancel", "reinstatement" or "change" request. The transaction only contains information about the changed members. This is identified in BGN08 by a code value of '2' (Change (Update)).

A full file audit lists all current members, whether involved in a change or not. The full file audit is intended to identify all active members, at a given point in time and may or may not include terminated members based on the Trading Partner Agreement. This type of transaction is identified by a BGN08 code value of '4' (Verify). In addition, INS03 in Loop 2000 and HD01 in Loop 2300 must be set to a value of '030' (Audit or Compare).

A full file replacement identified in BGN08 by a code value of 'RX' (Replace) is intended to identify all active members, at a given point in time and may or may not include terminated members based on the Trading Partner Agreement.

1.4.8 Coverage Levels and Dependents

Differences exist in how Information Sources manage dependents. Some Information Sources identify a coverage level (HD05) for the subscriber which defines the coverage for eligible dependents as well. Other Information Sources have detailed information on each dependent in order to maintain their databases. Still other Information Sources maintain both types of information.

The Trading Partner Agreement between the Information Source and Information Receiver must identify the member reporting requirements for this transaction.

1.4.9 Information Related to Individuals At Risk

In certain instances reporting of addresses and other individual related information is restricted by regulation or policy to protect the individual. In order to ensure that the Information Receiver can receive and process this information correctly and protect the individual's information, this transaction utilizes the value of 'O' (Other) in INS13 (Confidentiality Code) in Loop 2000 to identify the member as an At Risk individual. The value of 'PJ' (Party to Receive Correspondence) in NM101 (Entity Identifier Code) of loop 2100A is the indication that the address in this loop may not be an actual address associated to the individual. Further restrictions may be defined in the Trading Partner Agreement to facilitate reporting information related to these individuals.

An example of this scenario can be found at the external website at http://examples.x12.org.

1.4.10 Information Related to Disability Reporting

When the member status meets the definition of disability in X12 Wordbook, then the DSB segment in Loop 2200 is used to report the disability type and the associated dates.

The value in DSB01 in Loop 2200 is used in conjunction with a begin date in the DTP segment, when appropriate, to report a member's disability status.

When disability status ends, a value of '4' (No Disability) is sent in DSB01 and the disability end date is sent in DTP03 (Disability End Date).

If a disability status was reported in error, a value of "4" (No Disability) is used in DSB01 and no DTP segment is sent.

1.5 Business Terminology

To ensure consistent use of terms, definitions, and acronyms across X12 products, X12 maintains the Wordbook, a comprehensive corporate glossary. The included terms are either proprietary to X12, cite definitions published by another authority, or represent common terms and definitions that are relevant to X12's work. The terms and definitions defined in the Wordbook are used in X12 work products when applicable, without modification or revision. The Wordbook can be referenced online at wordbook.x12.org.

1.6 Transaction Acknowledgments

The purpose of transaction acknowledgments is to report to the sender whether the transaction being acknowledged was accepted or rejected.

The X12 Technical Report Type 2, Acknowledgment Reference Model provides guidance on several control structures and transaction set standards intended to augment EDI auditing and control systems.

1.7 Related Transactions

There are no transactions related to the transaction described in this implementation guide.

1.8 Trading Partner Agreements

Trading partner agreements are used to establish and document the relationship between trading partners. A trading partner agreement must not override the specifications in this implementation guide if a transmission is reported in GS08 to be a product of this implementation guide.

1.9 Transaction Compliance

There are three types of compliance that may be relevant to a transmitted transaction.

Compliance with implementation guide requirements

Compliance with state and federal regulation

Compliance with trading partner contractual agreements

1.9.1 Transaction Compliance with Implementation Guide Requirements

A transaction complies with X12 implementation guide requirements if the transaction satisfies all format and content rules and constraints specified in the applicable X12 standards and the implementation guide (also known as a TR3) itself.

Should additional clarification of an X12 implementation guide requirement be desired, two options are available.

X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that are not TR3-compliant based on its own business process.

A receiver may specify its business rules in a trading partner agreement or companion document. As stated in §1.8, these documents do not override TR3 requirements, nor change how transaction compliance with this TR3 is determined.

1.9.2 Transaction Compliance with State and Federal Regulations

This implementation guide has been developed for use as an insurance industry implementation guide. At the time of publication it has not been adopted as a state or federal standard. Should this implementation guide be adopted as a standard, the adopting authority will establish compliance dates for its use by impacted entities.

X12 is not the authority for determining compliance with regulatory requirements that might further constrain implementation guide requirements. Questions of compliance for regulatory requirements should be directed to the governing authority.

X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that do not comply with applicable regulatory requirements as specified by the applicable regulation(s) or governing authority.

1.9.3 Transaction Compliance with Contractual Requirements

X12 is not the authority for determining compliance with contractual requirements that might further constrain implementation guide requirements. Questions of compliance for contractual requirements should be directed to the contracting entity.

X12 does not specify the business rules that the receiving entity must use to decide when to accept or reject a transaction. The receiver will handle transactions that do not comply with contractual requirements as specified by the applicable contract or contracting entity.

2. Transaction Set

NOTE
See X12 documents X12.5, X12.6, and X12.59 to review transaction set structure, including descriptions of segments, levels, and loops.

2.1 Presentation Examples

The X12 standards are generic. For example, multiple trading communities use the same PER segment to specify administrative communication contacts. Each community decides which elements to use and which code values in those elements are applicable.

This implementation guide uses a format that depicts both the generalized standard and the insurance industry-specific implementation. In this implementation guide, IMPLEMENTATION specifies the requirements for this implementation. X12 STANDARD is included as a reference only.

The transaction set presentation is comprised of two main sections with subsections within the main sections:

Transaction Set Listing

There are two sub-sections under this general title. The first sub-section concerns this implementation of a generic X12 transaction set. The second sub-section concerns the generic X12 standard itself.

This section lists the levels, loops, and segments contained in this implementation. It also serves as an index to the segment detail.

This section is included as a reference.

Segment Detail

There are three sub-sections under this general title. This section repeats once for each segment used in this implementation providing segment specific detail and X12 standard detail.

This section is included as a reference.

This section is included as a reference. It provides a pictorial view of the standard and shows which elements are used in this implementation.

This section specifies the implementation details of each data element.

These illustrations (Figures 2.1 through 2.5) are examples and are not extracted from the Section 2 detail in this implementation guide. Annotated illustrations, presented below in the same order they appear in this implementation guide, describe the format of the transaction set that follows.

Figure 2.1 - Transaction Set Key - Implementation

Transaction Set Key - Implementation

Figure 2.2 - Transaction Set Key - Standard

Transaction Set Key - Standard

Figure 2.3 - Segment Key - Implementation

Segment Key - Implementation

Figure 2.4 - Segment Key - Diagram

Segment Key - Diagram

Figure 2.5 - Segment Key - Element Summary

Segment Key - Element Summary

2.2.1 Industry Usage

Industry Usage describes when loops, segments, and elements are to be sent when complying with this implementation guide. The three choices for Usage are required, not used, and situational. To avoid confusion, these are named differently than the X12 standard Condition Designators (mandatory, optional, and relational).

Required  

This loop/segment/element must always be sent.

Required segments in Situational loops only occur when the loop is used.

Required elements in Situational segments only occur when the segment is used.

Required component elements in Situational composite elements only occur when the composite element is used.

Not Used  

This element must never be sent.

Situational  

Use of this loop/segment/element varies, depending on data content and business context as described in the defining rule. The defining rule is documented in a Situational Rule attached to the item.

There are two forms of Situational Rules.

"Required when <explicit condition statement>. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver."

The data qualified by such a situational rule cannot be required, requested or rejected by the receiver when the condition is not applicable. Transmission of this data is solely at the sender's discretion when the stated condition does not apply.

"Required when <explicit condition statement>. If not required by this implementation guide, do not send."

The data qualified by such a situational rule must not be sent except as described in the explicit condition statement.

2.2.1.1 Determining Transaction Compliance with Industry Usage Requirements

A transmitted transaction complies with the governing implementation guide when it satisfies the requirements as defined within the implementation guide. Specifically, the presence or absence of an item (loop, segment, or element) complies with the industry usage specified by this implementation guide according to the following table.

Industry Usage

Business
Condition
is

Item
is

Transaction
Complies with
Implementation
Guide?

Required

N/A

Sent

Yes

Not Sent

No

Not Used

N/A

Sent

No

Not Sent

Yes

Situational (Required when <explicit condition statement>. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.)

True

Sent

Yes

Not Sent

No

Not True

Sent

Yes

Not Sent

Yes

Situational (Required when <explicit condition statement>. If not required by this implementation guide, do not send.)

True

Sent

Yes

Not Sent

No

Not True

Sent

No

Not Sent

Yes

2.2.2 Loops

Loop requirements depend on the context or location of the loop within the transaction. See Appendix B for more information on loops.

  • A nested loop can be used only when the associated higher level loop is used.
  • The usage of a loop is the same as the usage of its beginning segment.
    • If a loop's beginning segment is Required, the loop is Required and must occur at least once unless it is nested in a loop that is not being used.
    • If a loop's beginning segment is Situational, the loop is Situational.
  • Subsequent segments within a loop can be sent only when the beginning segment is used.
  • Required segments in Situational loops occur only when the loop is used.

3. Examples

Business scenario examples for use of this transaction can be found on the X12 Examples website at http://examples.x12.org. The X12 Examples website provides convenient access to examples of X12 transaction transmissions, including the data stream and a description of the associated scenario.

 

Appendix A. External Code Sources

Prior to this publication, X12 TR3s contained a subset of the overall Code Source Directory, formerly known as Appendix A of X12.3. External code lists are not part of the X12 standard and are provided for information purposes only. The full listing is available in Glass, X12's On-Line viewer.

Read more about Glass here: https://glasshelp.x12.org/.

Where an external code source is referenced in this publication, the implementer is required to use only the codes from that list. Codes must be reported as listed in the code source (e.g. with leading zeroes). Implementers must follow the instructions for code use that are supplied by the code set owner.

 

B.1.1 X12 Referenced and Related Standards

This technical report is based on the X12 EDI standard which comprises a series of interdependent publications. Implementers are advised to consult these publications when using this technical report.

The following standards are required to interpret, understand, and use this technical report:

  • X12.5 - Interchange Control Structure
  • X12.6 - Application Control Structure

The following guideline is useful to interpret, understand, and use this technical report:

  • Compliance in X12

The following reference model is useful to interpret, understand, and use this technical report:

  • Acknowledgment Reference Model

All of the documents above are available online using links to X12's Online Viewer.

 

B.1.1.1 Transmission Control Schematic

Refer to X12.5 - Interchange Control Structures, Section 3.5 - Order of Control Segments, and Chapter 5 Interchange Segment Specifications.

Similar transaction sets, called "functional groups," can be sent together within a transmission. Each functional group is prefaced by a group start segment; and a functional group is terminated by a group end segment. One or more functional groups are prefaced by an interchange header and followed by an interchange trailer. Figure B.1 - Transmission Control Schematic, illustrates this interchange control.

Figure B.1 - Transmission Control Schematic

Transmission Control Schematic

 

B.1.1.2 Constraints applicable to the suite of TR3s

Refer to X12.6 - Application Control Structure, Section 3.2.8 - Minimums/Maximums.

Data element minimum and maximum lengths are set by the X12 standard. This implementation guide may further restrict minimum and maximum lengths within the bounds set by the standard. Such restrictions may occur implicitly by virtue of the allowed qualifier for the data element, or they may be stated explicitly in a note attached to the element or in the general limitations below.

 

B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification

The current X12 standard allows a maximum length greater than 50 characters for data element 127. For implementations governed by this implementation guide, unless another value is specified in an attached note, the maximum length of each occurrence of this data element is constrained to 50 characters.

 

B.1.1.2.2 Maximum Length of Data Element 782 Monetary Amount

For implementations governed by this implementation guide, unless another value is specified for an instance of Data Element 782 within Section 2 (Transaction Set), each occurrence of Data Element 782 (Monetary Amount) will be limited to a maximum length of 10 characters including reported or implied places for cents (implied value of 00 after the decimal point). Note that the decimal point and leading sign, if sent, are not part of the character count.

EXAMPLE

  • The following transmitted value represents the largest positive dollar amount that can be sent: 99999999.99
  • The following transmitted value is the longest string of characters that can be sent representing whole dollars. 99999999
  • The following transmitted value is the longest string of characters that can be sent representing negative dollars and cents. -99999999.99
  • The following transmitted value is the longest string of characters that can be sent representing negative whole dollars. -99999999
 

B.1.1.3 Decimal

While the X12 standard supports usage of exponential notation, this guide prohibits that usage.

Appendix D. Change Summary

This Implementation Guide (008020X318) defines the X12 requirements for the Plan Member Reporting. It is based on version/release/subrelease 008020 of the X12 standards.