834 Transaction Set Listing
008020X346 Health Insurance Exchange: Enrollment- Loop 1000A - SUBMITTER NAMERequired1
- Loop 1000B - RECEIVER NAMERequired1
- Loop 1000C - QHP ISSUERRequired1
- Loop 1000D - SPONSOR NAMESituational1
- Loop 1000E - SPONSOR/EMPLOYER GROUP SETUP - NAMESituational>1
- Loop 1100EA - SPONSOR/EMPLOYER GROUP INFORMATIONRequired1
- Loop 1100EB - SPONSOR/EMPLOYER GROUP OTHER LOCATION INFORMATIONSituational9
- Loop 2000 - ENROLLEE LEVEL DETAILRequired>1
- Loop 2100A - ENROLLEE NAMERequired1
- Loop 2100B - INCORRECT ENROLLEE NAMESituational1
- Loop 2100C - ENROLLEE MAILING ADDRESSSituational1
- Loop 2100D - ENROLLEE EMPLOYERSituational3
- Loop 2100E - CUSTODIAL PARENTSituational1
- Loop 2100F - RESPONSIBLE PERSONSituational13
- Loop 2100G - DROP OFF LOCATIONSituational1
- Loop 2100H - SPONSOR NAMESituational1
- Loop 2100I - APTC CONTRIBUTOR/TAX PAYER NAMESituational1
- Loop 2200 - DISABILITY INFORMATIONSituational4
- Loop 2300 - HEALTH COVERAGESituational99
- Loop 2310 - PROVIDER INFORMATIONSituational10
- Loop 2320 - COORDINATION OF BENEFITSSituational5
- Loop 2330 - COORDINATION OF BENEFITS RELATED ENTITYSituational1
- Loop 2700A - AGENT/BROKER REPORTINGSituational>1
- Loop 2750A - AGENT/BROKER NAMERequired1
- Loop 2700B - NAVIGATOR REPORTINGSituational>1
- Loop 2750B - NAVIGATOR NAMERequired1
- Loop 2700C - ENROLLEE REPORTING CATEGORIESSituational>1
- Loop 2750C - REPORTING CATEGORYRequired1
ISA - INTERCHANGE CONTROL HEADER
- 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.
- The first element separator defines the element separator to be used through the entire interchange.
- Spaces in the example interchanges are represented by "." for clarity.
- The ISA segment terminator defines the segment terminator used throughout the entire interchange.
- All positions within each of the data elements must be filled.
- The Interchange Control Number, ISA13, must be identical to the associated Interchange Trailer IEA02.
- Must be a positive unsigned number and must be identical to the value in IEA02.
GS*BE - FUNCTIONAL GROUP HEADER
ST*834 - TRANSACTION SET HEADER
- This element must be populated with the guide identifier named in Section 1.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.
BGN - BEGINNING SEGMENT
If BGN05 is present, then BGN04 is required.
The "00" indicates the first time the transaction is sent.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
- This element is the transaction set reference number assigned by the sender's application. It uniquely identifies this occurrence of the transaction for future reference.
REF*38 - EXCHANGE ASSIGNED QUALIFIED HEALTH PLAN IDENTIFIER
At least one of REF02 or REF03 is required.
REF*TV - ISSUER ASSIGNED QUALIFIED HEALTH PLAN IDENTIFIER
At least one of REF02 or REF03 is required.
If not required by this implementation guide, do not send.
- Traditionally, this identifier represents a combination of the plan/product selected and the employer. In this implementation, the QHP identifier is the same for all employer groups within the SHOP market.
- The QHP identified at this level may be overridden at the enrollee level when necessary.
REF*18 - EXCHANGE ASSIGNED EMPLOYER GROUP IDENTIFIER
At least one of REF02 or REF03 is required.
REF*1L - ISSUER ASSIGNED EMPLOYER GROUP IDENTIFIER
At least one of REF02 or REF03 is required.
all enrollees within this transaction apply to a single employer group,
the issuer has assigned an identifier to that employer group,
and the identifier is known to the submitter.
If not required by this implementation guide, do not send.
DTP*007 - FILE EFFECTIVE DATE
QTY*TO - TRANSACTION SET CONTROL TOTALS
- R0204
At least one of QTY02 or QTY04 is required. - E0204
Only one of QTY02 or QTY04 may be present.
- The Transaction Set Totals for Dependents and Subscribers reported in QTY segments at this level must add up to the Total reported in this segment.
- The Transaction Set Total is a sum of all INS segments included in this transaction (ST/SE).
- Since an individual member's record may be transmitted more than once within the ST-SE, the quantity in QTY02 when QTY01 = TO, does not necessarily reflect a count of unique member records.
QTY*DT - DEPENDENT RECORD COUNT
- R0204
At least one of QTY02 or QTY04 is required. - E0204
Only one of QTY02 or QTY04 may be present.
QTY*ET - SUBSCRIBER RECORD COUNT
- R0204
At least one of QTY02 or QTY04 is required. - E0204
Only one of QTY02 or QTY04 may be present.
If not required by this implementation guide, do not send.
N1*41 - SUBMITTER NAME
- R0203
At least one of N102 or N103 is required. - P0304
If either N103 or N104 is present, then the other is required. - C0703
If N107 is present, then N103 is required.
N1*40 - RECEIVER NAME
- R0203
At least one of N102 or N103 is required. - P0304
If either N103 or N104 is present, then the other is required. - C0703
If N107 is present, then N103 is required.
N1*IN - QHP ISSUER
- R0203
At least one of N102 or N103 is required. - P0304
If either N103 or N104 is present, then the other is required. - C0703
If N107 is present, then N103 is required.
N1*P5 - SPONSOR NAME
- R0203
At least one of N102 or N103 is required. - P0304
If either N103 or N104 is present, then the other is required. - C0703
If N107 is present, then N103 is required.
- This loop identifies the sponsor. See section 1.5 for the definition of Sponsor.
- SHOP related transactions will identify the employer as the sponsor.
N1*62 - SPONSOR/EMPLOYER GROUP SETUP - NAME
- R0203
At least one of N102 or N103 is required. - P0304
If either N103 or N104 is present, then the other is required. - C0703
If N107 is present, then N103 is required.
- When this loop is used, it is preferred this transaction (ST/SE) be limited to enrollees that are part of this employer group. If this option is not selected, the design and intent is issuers will be able to know which enrollees are linked to this employer group using the Exchange Assigned Employer Group Identifier reported in this loop to the Exchange Assigned Employer Group Identifier reported in Loop 2000.
- In this context, initial enrollment means the first time an exchange presents an employer group to an issuer.
N3 - PRIMARY BILLING ADDRESS
N4 - PRIMARY BILLING CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
PER*AJ - PRIMARY CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
PER*AL - ALTERNATE CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
ACT - SPONSOR/EMPLOYER GROUP INFORMATION
- P0304
If either ACT03 or ACT04 is present, then the other is required. - C0506
If ACT05 is present, then ACT06 is required. - C0705
If ACT07 is present, then ACT05 is required.
REF*18 - EXCHANGE ASSIGNED EMPLOYER GROUP IDENTIFIER
At least one of REF02 or REF03 is required.
REF*QQ - EMPLOYER SIZE
At least one of REF02 or REF03 is required.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
- Report the total number of full-time employees.
REF - EMPLOYER CLASSIFICATION
At least one of REF02 or REF03 is required.
REF*DU - EMPLOYER DEPENDENT INFORMATION
At least one of REF02 or REF03 is required.
- Populate with 'YES' to denote that dependent coverage is offered.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
N3 - ALTERNATE BILLING ADDRESS
N4 - ALTERNATE BILLING CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
PER*BI - ALTERNATE BILLING CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
DTP*AB4 - EMPLOYER WAITING PERIOD
AMT - EMPLOYER CONTRIBUTION
ACT - SPONSOR/EMPLOYER GROUP OTHER LOCATION INFORMATION
- P0304
If either ACT03 or ACT04 is present, then the other is required. - C0506
If ACT05 is present, then ACT06 is required. - C0705
If ACT07 is present, then ACT05 is required.
N3 - SPONSOR/EMPLOYER GROUP OTHER LOCATION STREET ADDRESS
N4 - SPONSOR/EMPLOYER GROUP OTHER LOCATION CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
PER*1I - SPONSOR/EMPLOYER GROUP OTHER LOCATION CONTACT INFORMATION
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
INS - ENROLLEE LEVEL DETAIL
If either INS11 or INS12 is present, then the other is required.
- The value 18 must be used for the subscriber.
- For dependents, this value identifies their relationship to the subscriber. For example, a daughter would be value 19.
Use this code, in conjunction with DMG05, when the change reason is allowable due to the special enrollment period "An Indian, as defined by section 4 of the Indian Health Care Improvement Act, may enroll in a QHP or change from one QHP to another one time per month". See section 1.4.6 - Qualifying Events for more information.
REF*38 - EXCHANGE ASSIGNED QUALIFIED HEALTH PLAN IDENTIFIER
At least one of REF02 or REF03 is required.
If not required by this implementation guide, do not send.
REF*TV - ISSUER ASSIGNED QUALIFIED HEALTH PLAN IDENTIFIER
At least one of REF02 or REF03 is required.
If not required by this implementation guide, do not send.
REF*38 - COVERAGE SPECIFIC EXCHANGE ASSIGNED QUALIFIED HEALTH PLAN IDENTIFIER
At least one of REF02 or REF03 is required.
REF*TV - COVERAGE SPECIFIC ISSUER ASSIGNED QUALIFIED HEALTH PLAN IDENTIFIER
At least one of REF02 or REF03 is required.
REF*18 - EXCHANGE ASSIGNED EMPLOYER GROUP IDENTIFIER
At least one of REF02 or REF03 is required.
REF*1L - ISSUER ASSIGNED EMPLOYER GROUP IDENTIFIER
At least one of REF02 or REF03 is required.
REF*18 - COVERAGE SPECIFIC EXCHANGE ASSIGNED EMPLOYER GROUP IDENTIFIER
At least one of REF02 or REF03 is required.
REF*1L - COVERAGE SPECIFIC ISSUER ASSIGNED EMPLOYER GROUP IDENTIFIER
At least one of REF02 or REF03 is required.
and one or more of the specific coverages identified in Loop ID 2300 belong to a different employer group than reported as either the enrollee or header level employer group,
and the issuer assigned identifier is known by the submitter.
If not required by this implementation guide, do not send.
REF*POL - EXCHANGE ASSIGNED POLICY IDENTIFIER
At least one of REF02 or REF03 is required.
REF*AZ - ISSUER ASSIGNED POLICY IDENTIFIER
At least one of REF02 or REF03 is required.
REF*WH - EXCHANGE ASSIGNED SUBSCRIBER IDENTIFIER
At least one of REF02 or REF03 is required.
REF*0F - ISSUER ASSIGNED SUBSCRIBER IDENTIFIER
At least one of REF02 or REF03 is required.
REF*6O - EXCHANGE ASSIGNED DEPENDENT IDENTIFIER
At least one of REF02 or REF03 is required.
an exchange has assigned an identifier to the dependent named in Loop 2100A,
and that identifier is known to the submitter,
and the identifier is permitted for use under applicable regulation.
If not required by this implementation guide, do not send.
REF*1W - ISSUER ASSIGNED DEPENDENT IDENTIFIER
At least one of REF02 or REF03 is required.
REF*4A - EXCHANGE ASSIGNED APTC CONTRIBUTOR/TAX PAYER IDENTIFIER
At least one of REF02 or REF03 is required.
• an exchange has assigned an identifier to the ATPC contributor named in Loop 2100I,
• and the identifier is known to the submitter,
• and the identifier is permitted for use under applicable regulation.
If not required by this implementation guide, do not send.
REF*23 - ISSUER ASSIGNED APTC CONTRIBUTOR/TAX PAYER IDENTIFIER
At least one of REF02 or REF03 is required.
If not required by this implementation guide, do not send.
REF - ENROLLEE SUPPLEMENTAL IDENTIFIER
At least one of REF02 or REF03 is required.
REF*01 - ACH BANK INFORMATION
At least one of REF02 or REF03 is required.
- P0304
If either C04003 or C04004 is present, then the other is required. - P0506
If either C04005 or C04006 is present, then the other is required.
REF*PSM - CREDIT/DEBIT CARD INFORMATION
At least one of REF02 or REF03 is required.
- P0304
If either C04003 or C04004 is present, then the other is required. - P0506
If either C04005 or C04006 is present, then the other is required.
DTP - ENROLLEE LEVEL DATES
OR
Required when this transaction is reporting a change to an enrollee's record, and one of the dates defined by the date qualifiers and code notes available in DTP01 have changed.
If not required by this implementation guide, do not send.
- While many of the dates listed for DTP01 are related to termination, the only code that is used to actually terminate an Enrollee is 357 (Eligibility End). Similarly, the Eligibility Begin Date (code 356) is the date the individual is eligible for coverage, not the date coverage is effective.
- For new enrollments or reconciliation, all dates that apply to the particular insurance contract are to be sent.
- For updates, all dates that apply to the particular insurance contract which have changed are to be sent.
DTP*903 - ONLINE APPLICATION DATE/TIME
DTP*196 - INDIAN TRIBAL STATUS EFFECTIVE DATE
DTP*771 - TOBACCO STATUS EFFECTIVE DATE
DTP*ABW - CREDIT CARD EXPIRATION DATE
NM1 - ENROLLEE NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
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.
PER*IP - ENROLLEE COMMUNICATIONS NUMBERS
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
If not required by this implementation guide, do not send.
- 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).
- Send communication information in the order of preference when contacting the member.
N3 - ENROLLEE RESIDENCE STREET ADDRESS
N4 - ENROLLEE CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
DMG*D8 - ENROLLEE DEMOGRAPHICS
- P0102
If either DMG01 or DMG02 is present, then the other is required. - P1011
If either DMG10 or DMG11 is present, then the other is required. - C1105
If DMG11 is present, then DMG05 is required.
If either C05602 or C05603 is present, then the other is required.
EC - EMPLOYMENT CLASS
HLH - ENROLLEE HEALTH INFORMATION
Or
Required on an enrollment update when an enrollee's medical information has changed and is available.
If not required by this implementation guide, do not send.
- L030405
If C06103 is present, then at least one of C06104 or C06105 are required. - C0403
If C06104 is present, then C06103 is required. - C0503
If C06105 is present, then C06103 is required.
- C061-04 is the beginning date related to the type of date identified in C061-03.
- C061-05 is the end date related to the type of date identified in C061-03.
HI - ENROLLMENT AMOUNT INFORMATION
If not required by this implementation guide, do not send.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
- P0304
If either C02203 or C02204 is present, then the other is required. - E0809
Only one of C02208 or C02209 may be present.
- C022-01 qualifies C022-02, C022-04, C022-05, C022-06, C022-08 and C022-10.
- If C022-08 is used, then C022-02 represents the beginning value in a range of codes.
- C022-03 is the date format that will appear in C022-04.
- C022-07 qualifies C022-01.
- C022-08 represents the ending value in a range of codes.
- C022-09 is a value from Code Source 959 for the Present on Admission Indicator.
- C022-10 is the attribute of the code in C022-02 from the same code list.
LUI - ENROLLEE LANGUAGE
- P0102
If either LUI01 or LUI02 is present, then the other is required. - L040203
If LUI04 is present, then at least one of LUI02 or LUI03 are required.
NM1*70 - INCORRECT ENROLLEE NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
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.
DMG*D8 - INCORRECT ENROLLEE DEMOGRAPHICS
- P0102
If either DMG01 or DMG02 is present, then the other is required. - P1011
If either DMG10 or DMG11 is present, then the other is required. - C1105
If DMG11 is present, then DMG05 is required.
If not required by this implementation guide, do not send.
If either C05602 or C05603 is present, then the other is required.
NM1*31 - ENROLLEE MAILING ADDRESS
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
N3 - ENROLLEE MAIL STREET ADDRESS
N4 - ENROLLEE MAIL CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
NM1*36 - ENROLLEE EMPLOYER
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
If not required by this implementation guide, do not send.
PER*EP - ENROLLEE EMPLOYER COMMUNICATIONS NUMBERS
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
If not required by this implementation guide, do not send.
- 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).
- Send communication information in the order of preference when contacting the member.
N3 - ENROLLEE EMPLOYER STREET ADDRESS
If not required by this implementation guide, do not send.
N4 - ENROLLEE EMPLOYER CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
If not required by this implementation guide, do not send.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
NM1*S3 - CUSTODIAL PARENT
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
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.
PER*PQ - CUSTODIAL PARENT COMMUNICATIONS NUMBERS
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
If not required by this implementation guide, do not send.
- 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).
- Send communication information in the order of preference when contacting the member.
N3 - CUSTODIAL PARENT STREET ADDRESS
If not required by this implementation guide, do not send.
N4 - CUSTODIAL PARENT CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
If not required by this implementation guide, do not send.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
NM1 - RESPONSIBLE PERSON
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
This code is used when a Qualified Medical Child Support Order (QMSCO) is present.
PER*RP - RESPONSIBLE PERSON COMMUNICATIONS NUMBERS
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
If not required by this implementation guide, do not send.
- 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).
- Send communication information in the order of preference when contacting the member.
N3 - RESPONSIBLE PERSON STREET ADDRESS
If not required by this implementation guide, do not send.
N4 - RESPONSIBLE PERSON CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
If not required by this implementation guide, do not send.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
NM1*45 - DROP OFF LOCATION
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
N3 - DROP OFF LOCATION STREET ADDRESS
N4 - DROP OFF LOCATION CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
NM1 - SPONSOR NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
this enrollment is from a SHOP exchange.
OR
the enrollment is from an Individual Market Exchange, and the exchange is able to determine the entity responsible for payment.
If not required by this implementation guide, do not send.
- This loop identifies the sponsor. See section 1.5 for the definition of Sponsor.
- When the exchange cannot determine a sponsor (the entity responsible for premium payment) in the individual market, the contact person must be reported in the subscriber PER.
NM1*2C - APTC CONTRIBUTOR/TAX PAYER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
PER*IC - APTC CONTRIBUTOR/TAX PAYER COMMUNICATION NUMBERS
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
- 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).
- Send communication information in the order of preference when contacting the member.
N3 - APTC CONTRIBUTOR/TAX PAYER STREET ADDRESS
N4 - APTC CONTRIBUTOR/TAX PAYER CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
DSB - DISABILITY INFORMATION
If either DSB07 or DSB08 is present, then the other is required.
If not required by this implementation guide, do not send.
DTP - DISABILITY ELIGIBILITY DATES
If not required by this implementation guide, do not send.
HD - HEALTH COVERAGE
DTP - HEALTH COVERAGE DATES
DTP*903 - ONLINE APPLICATION DATE/TIME
REF - HEALTH COVERAGE POLICY NUMBER
At least one of REF02 or REF03 is required.
If not required by this implementation guide, do not send.
REF*QQ - PRIOR COVERAGE MONTHS
At least one of REF02 or REF03 is required.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
- This field will contain the number of months of prior health insurance coverage that meets the portability requirements of the HIPAA certification requirements. To be sent on new enrollments when available.
- Report as a left-justified integer with no leading zeroes.
LX - PROVIDER INFORMATION
If not required by this implementation guide, do not send.
- Use one iteration of the loop to identify each applicable health care service provider.
- The primary care provider effective date is defaulted to the effective date of the product identified in the DTP segment of the 2300 loop. When an enrollee switches from one primary care provider to another through the sponsor, the new provider must be listed with the effective date of change.
NM1 - PROVIDER NAME
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
N3 - PROVIDER ADDRESS
If not required by this implementation guide, do not send.
N4 - PROVIDER CITY, STATE, ZIP CODE
- E0207
Only one of N402 or N407 may be present. - E0308
Only one of N403 or N408 may be present. - C0605
If N406 is present, then N405 is required. - C0704
If N407 is present, then N404 is required.
If not required by this implementation guide, do not send.
- CODE SOURCE 51: ZIP Code
- CODE SOURCE 932: Universal Postal Codes
PER*IC - PROVIDER COMMUNICATIONS NUMBERS
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
If not required by this implementation guide, do not send.
- 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).
- Send communication information in the order of preference when contacting the member.
PLA*2 - PROVIDER CHANGE REASON
If not required by this implementation guide, do not send.
COB - COORDINATION OF BENEFITS
REF*1W - COORDINATION OF BENEFITS ENROLLEE IDENTIFIER
At least one of REF02 or REF03 is required.
When sending the Social Security Number as the enrollee ID, it 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.
REF*6P - COORDINATION OF BENEFITS PAYER GROUP IDENTIFIER
At least one of REF02 or REF03 is required.
DTP*344 - COORDINATION OF BENEFITS ELIGIBILITY BEGIN DATE
DTP*345 - COORDINATION OF BENEFITS ELIGIBILITY END DATE
NM1*IN - COORDINATION OF BENEFITS RELATED ENTITY
- P0809
If either NM108 or NM109 is present, then the other is required. - C1110
If NM111 is present, then NM110 is required. - C1203
If NM112 is present, then NM103 is required.
If not required by this implementation guide, do not send.
PER*CN - ADMINISTRATIVE COMMUNICATIONS CONTACT
- P0304
If either PER03 or PER04 is present, then the other is required. - P0506
If either PER05 or PER06 is present, then the other is required. - P0708
If either PER07 or PER08 is present, then the other is required.
If not required by this implementation guide, do not send.
LS - ADDITIONAL REPORTING CATEGORIES
If not required by this implementation guide, do not send.
LX - AGENT/BROKER REPORTING
N1*AG - AGENT/BROKER NAME
- R0203
At least one of N102 or N103 is required. - P0304
If either N103 or N104 is present, then the other is required. - C0703
If N107 is present, then N103 is required.
REF*0B - AGENT/BROKER LICENSE NUMBER
At least one of REF02 or REF03 is required.
Use code source 22.
DTP*007 - AGENT/BROKER RELATIONSHIP DATES
- Use this segment to associate a date or date range with a reporting category.
- Date ranges are reported with the first occurrence of CCYYMMDD as the beginning date and the second occurrence as the ending date.
LX - NAVIGATOR REPORTING
N1*ZZ - NAVIGATOR NAME
- R0203
At least one of N102 or N103 is required. - P0304
If either N103 or N104 is present, then the other is required. - C0703
If N107 is present, then N103 is required.
REF - NAVIGATOR IDENTIFIER
At least one of REF02 or REF03 is required.
Use code source 22.
DTP*007 - NAVIGATOR RELATIONSHIP DATE
LX - ENROLLEE REPORTING CATEGORIES
If not required by this implementation guide, do not send.
N1*75 - REPORTING CATEGORY
- R0203
At least one of N102 or N103 is required. - P0304
If either N103 or N104 is present, then the other is required. - C0703
If N107 is present, then N103 is required.
REF*ZZ - REPORTING CATEGORY REFERENCE
At least one of REF02 or REF03 is required.
- This element defines the data to be reported in REF03 and, when applicable, related dates in the DTP segment. Codification and Definitions can be found on the CMS Health Insurance Exchange website.
- Refer to Appendix B.1.1.2.1 Maximum Length of Data Element 127 Reference Identification for more information about this data element length.
DTP*007 - REPORTING CATEGORY DATE
- Use this segment to associate a date or date range with a reporting category.
- Date ranges are reported with the first occurrence of CCYYMMDD as the beginning date and the second occurrence as the ending date.
LE - ADDITIONAL REPORTING CATEGORIES LOOP TERMINATION
SE - TRANSACTION SET TRAILER
GE - FUNCTIONAL GROUP TRAILER
IEA - INTERCHANGE CONTROL TRAILER
| | 834 Health Insurance Exchange: Enrollment (008020X346)OCTOBER 2021 Copyright © 2008-21, X12 Incorporated, Format © 2008-21 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 Health Insurance Exchange: Enrollment Technical Report Type 3 describes the use of the X12 Health Care Enrollment (834) transaction set for:
|
PrefaceX12 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 ScopeFor 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 define the transaction set used to transfer enrollment information from a Health Insurance Exchange (HIX) to a Qualified Health Plan Issuer (issuer).This implementation guide will also be used for periodic reconciliation of data between an HIX and an issuer. The intent of this implementation guide is to meet the health care industry's specific need for the initial enrollment, enrollment response, subsequent maintenance, and periodic data reconciliation/verification of consumers who are enrolled in health insurance exchange products. This implementation guide specifically addresses the enrollment and maintenance of HIX products only. |
1.2 Version InformationThis 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 008020X346. The two-character Functional Identifier Code for the transaction set included in this implementation guide:
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 UsageThere 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 was based on requirements for batch mode. Willing trading partners may use batch or real-time mode. |
1.3.2 Other Usage LimitationsThere are no other usage limitations. Any response back to the Sponsor from the received transaction is outside the scope of the 834 and is the responsibility of the sponsor and payer. |
1.4.1 Health Care Transaction FlowEach 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 Health Insurance ExchangesThis Technical Report Type 3 (TR3) defines the transaction used to transmit enrollment data between Health Insurance Exchanges and insurance issuers. This TR3 supports a different enrollment process than the process used outside of Exchanges and the transaction is not interchangeable with the one defined by the Benefit Enrollment and Maintenance (834) 008020X333 TR3. Benefit Enrollment and Maintenance (834) 008020X333 The sponsor executes a contract with the health plan and receives guidance from the health plan before submitting 834 transactions to the health plan. Often, the health plan provides the sponsor with a "companion document" to describe the plan-specific enrollment parameters that the sponsor is to convey to the plan in the 834. Health Insurance Exchange Enrollment (834) 008020X346 The employers providing coverage through the Exchange will not have communicated with the insurance issuer in advance of the Exchange transmitting the 834 to the issuer. Neither the employers nor the Exchange will use the companion document published by the issuer. The Exchange will not tailor content to any particular issuer, but will transmit exactly the same enrollment parameters to every issuer. Trading Partner agreements and companion documents will typically be created by the Exchange. |
1.4.3 Identifier usageHow to identify an individual and their associated plan/product/policy/group information has been a major issue in creating this implementation guide. It became clear early on the various terms are not synonymous across the industry. Because of this, the following is provided for the purposes of level setting. The first step is to understand and accept the following scenario. In traditional group scenarios, the employer contracts with the issuer prior to any individuals being enrolled. That is not the case for Health Insurance Exchange (HIX) enrollments. In this process, the issuer provides the HIX with a list of the Qualified Health Plans (QHP) they will offer through the HIX. The HIX is then the direct point of contact for consumers. As a result, policy identifiers may not have been assigned by the issuer at the time of enrollment. The HIX will have an identifier they assign to the consumer/employee selection of a QHP which will be provided in the initial enrollment. The issuer will then have the ability to assign their traditional Policy/Group Numbers back to the HIX as part of the enrollment response. The following section demonstrates how this and other like situations, translate into identifier usage throughout this implementation guide. |
1.4.3.1Â Exchange assigned identifiers vs Issuer assigned identifiersWithin the relationship between exchanges and issuers, there are many possible identifiers that may be used. The topic of identifiers is a critical consideration due to the necessity of establishing and maintaining reliable linkages between transactions. These transactions include:
This is not an exhaustive list of the possible business processes affected. It simply represents the most pervasive at the time of this writing. The following represents a list of the various identifiers and the assumed usage. |
1.4.3.1.1 QHP IdentifierThis implementation guide assumes separate and distinct identifiers will be assigned to each of the QHP metal level offered by an issuer. The QHP identifier presents a couple of different possibilities. Since the issuer is advising the exchange of the QHPs offered, it is presumable the process of establishing said offering could include the mutual agreement as to how that QHP will be identified. If so, that could be the sole identifier used to represent a QHP in the transactions. Because that is not confirmed, allowances are made for both exchange assigned and issuer assigned identifiers. If a single QHP identifier is used by both the issuer and the exchange, use the exchange assigned segments. The purpose of the QHP identifier is more informational than as a linkage, but may be helpful depending upon an entities database structure and implementation. QHP identifiers may be reported for the transaction header, Loop ID 2000 (Enrollee Level Detail), or Loop ID 2300 (Health Coverage).
|
1.4.3.1.2 Employer Group IdentifierThe Employer Group Identifier is intended to represent the traditional view of group or policy numbers. Like the QHP identifier, the transaction supports identification of the employer group at the header, enrollee, or coverage levels.
|
1.4.3.1.3Â Policy IdentifierFor the purposes of this implementation, the context of this identifier may be different for some implementers. The best analogy is an auto insurance policy. Meaning it doesn't matter how many cars (people) are covered, or how many drivers there are, a single payment is made for the collective policy. For clarity, this is more at the, for lack of a better term, family unit level. Employer groups are a totally different entity. Since there is no means for both the exchange and the issuer to be aware of this entity at the time of initial enrollment, it is assumed both entities will assign a policy identifier as it is the first level some payments (i.e. APTCs) may be made.
|
1.4.3.1.4 Subscriber IdentifierImplementation may show the subscriber identifier and the policy identifier represent the same collective of enrollees. However, the policy identifier may represent a more reliable linkage between transactions because scenarios have been identified in the business process where the individual named as the subscriber by the exchange may change. Meanwhile the overall "policy" entity remains. Since there is no means for both the exchange and the issuer to be aware of the subscriber at the time of initial enrollment, it is assumed both entities will assign an identifier. The subscriber identifier is assigned at the member level and is required regardless of whether the enrollee presented is the actual subscriber or a dependent.
|
1.4.3.1.5 Dependent IdentifierLike the subscriber, there is no means for both the exchange and the issuer to be aware of the dependent at the time of initial enrollment, it is assumed both entities will assign an identifier. The dependent identifier is assigned at the member level.
|
1.4.3.1.6 Custodial Parent IdentifierAlthough the custodial parent is also not known to either the exchange or the issuer, the only identifier available is the social security number. The social security number will be available to the issuer only when collected by the exchange and applicable privacy regulations permit usage.
|
1.4.3.1.7 Responsible Person IdentifierAs with the custodial parent, the responsible person(s) is also not known to either the exchange or the issuer, and the only identifier available is the social security number. The social security number will be available to the issuer only when collected by the exchange and applicable privacy regulations permit usage.
|
1.4.3.1.8 APTC Contributor/Tax Payer IdentifierThe role of APTC Contributor/Tax Payer is new to this implementation of the 834. The purpose of this loop is to provide a means for an exchange to explicitly identify a "non-enrollee" APTC contribution. In other words, scenarios have been identified where a policy can receive APTC payment from an individual who is not enrolling in that policy. The most commonly presented example is a child/children only policy where the parent purchasing the policy qualifies for APTC and wishes to use those dollars for that policy. During the development of this implementation guide, the manner in which these amounts would be reported in the 834, and subsequently in the 820, have ranged from identifying the contributing individual (also referred to as "tax payer") to all APTC amounts will be attributed to the subscriber regardless of whom they are actually credited to. As a result, this loop and associated identifiers may never be used, but are included to ensure the final policy can be supported regardless of the outcome. Since this has the potential of being used as a key between the 834 and 820 transactions, both exchange and issuer assigned identifiers are allowed for in addition to social security number.
|
1.4.4 ReconciliationThe regulations for the establishment of exchanges and Qualified Health Plans require that QHP Issuers reconcile enrollment files with an Exchange at least once a month. Frequency of and the data reconciled may vary from exchange to exchange, depending on the unique needs of the exchange. Reconciliation of enrollment data is key to minimizing enrollment discrepancies between exchanges and issuers, regardless of the trigger for any discrepancy, including but not limited to triggers such as changes in enrollee eligibility, changes in QHP enrollment and changes as a result of special qualifying events. The details for conducting reconciliation will typically be defined within the trading partner agreement of an Exchange and QHP Issuers. |
1.4.5 Relationship between the HI (Enrollment Amount Information) and HD (Health Coverage)The amount recorded in Loop ID 2100A HI Segment (Enrollment Information) applies to coverage sent in Loop ID 2300 (Health Coverage). In instances where there are multiple coverages sent by repeating the Loop ID 2300 but the amount in the Loop ID 2100A (Enrollee Name) applies only to one specific coverage, a linkage must be made between the Loop ID 2100A HI Segment and the applicable Loop ID 2300 HD. The Loop ID 2100A HI Segment (Enrollment Amount Information) records several amounts that comprise the premium (e.g., the APTC and the personal responsibility amount) and any related subsidy payments to the issuer (i.e., the CSR). In the Loop ID 2300 (Health Coverage) there is the capacity for multiple coverages, i.e. repeats of the Loop ID 2300. The pointer in the Loop ID 2100A HI Segment is the sixth position of the composite, which records a sequence number that is then reported in the Loop ID 2300 HD06 Segment (Health Coverage Sequence) to indicate where that amount should be applied / accounted. |
1.4.6 Qualifying EventsWithin the regulations, there are nine categories of "Qualifying Events" or maintenance reasons. The maintenance reason code is reported in INS04. This section is not intended to be limiting in the codes used for each of the defined qualifying events. Rather, the intent is to provide guidance for those times when the category is known, but the user is not clear which code relates. The following text is excerpted from the regulation with code possibilities inserted. (d) Special enrollment periods. The Exchange must allow qualified individuals and enrollees to enroll in or change from one QHP to another as a result of the following triggering events: (1) A qualified individual or dependent loses minimum essential coverage; 60  Coverage Placed Elsewhere (2) A qualified individual gains a dependent or becomes a dependent through marriage, birth, adoption or placement for adoption; 02  Birth (3) An individual, who was not previously a citizen, national, or lawfully present individual gains such status; 33  Personnel Data (4) A qualified individual's enrollment or non-enrollment in a QHP is unintentional, inadvertent, or erroneous and is the result of the error, misrepresentation, or inaction of an officer, employee, or agent of the Exchange or HHS, or its instrumentalities as evaluated and determined by the Exchange. In such cases, the Exchange may take such action as may be necessary to correct or eliminate the effects of such error, misrepresentation, or inaction; 70  Misrepresented Information (5) An enrollee adequately demonstrates to the Exchange that the QHP in which he or she is enrolled substantially violated a material provision of its contract in relation to the enrollee; 64  Underwriting Reason (6) An individual is determined newly eligible or newly ineligible for advance payments of the premium tax credit or has a change in eligibility for cost-sharing reductions, regardless of whether such individual is already enrolled in a QHP. The Exchange must permit individuals whose existing coverage through an eligible employer-sponsored plan will no longer be affordable or provide minimum value for his or her employer's upcoming plan year to access this special enrollment period prior to the end of his or her coverage through such eligible employer sponsored plan; 86  Change in Insured Information (7) A qualified individual or enrollee gains access to new QHPs as a result of a permanent move; AH  Patient Moved to New Location (8) An Indian, as defined by section 4 of the Indian Health Care Improvement Act, may enroll in a QHP or change from one QHP to another one time per month; and 22  Plan Change (9) A qualified individual or enrollee demonstrates to the Exchange, in accordance with guidelines issued by HHS, that the individual meets other exceptional circumstances as the Exchange may provide. ZZ  Mutually Defined (e) Loss of minimum essential coverage. Loss of minimum essential coverage includes those circumstances described in 26 CFR 54.9801-6(a)(3)(i) through (iii). Loss of coverage does not include termination or loss due to – |
1.5 Business TerminologyTo 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 AcknowledgmentsThe 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 TransactionsThere are no transactions related to the transactions described in this implementation guide. |
1.8 Trading Partner AgreementsTrading 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 ComplianceThere 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 RequirementsA 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 RegulationsThis 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 RequirementsX12 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.1 Presentation ExamplesThe 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 Figure 2.2 - Transaction Set Key - Standard Figure 2.3 - Segment Key - Implementation Figure 2.4 - Segment Key - Diagram Figure 2.5 - Segment Key - Element Summary |
2.2.1 Industry UsageIndustry 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).
|
2.2.1.1 Determining Transaction Compliance with Industry Usage RequirementsA 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.
|
2.2.2 LoopsLoop requirements depend on the context or location of the loop within the transaction. See Appendix B for more information on loops.
|
3. ExamplesBusiness 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 SourcesPrior 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 StandardsThis 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:
The following guideline is useful to interpret, understand, and use this technical report:
The following reference model is useful to interpret, understand, and use this technical report:
All of the documents above are available online using links to X12's Online Viewer. | ||||
| Â | ||||
B.1.1.1 Transmission Control SchematicRefer 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 | ||||
| Â | ||||
B.1.1.2 Constraints applicable to the suite of TR3sRefer 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 IdentificationThe 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 AmountFor 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
| ||||
| Â | ||||
B.1.1.3 DecimalWhile the X12 standard supports usage of exponential notation, this guide prohibits that usage. | ||||
Appendix D. Change SummaryThis Implementation Guide (008020X346) defines the X12 requirements for the Health Insurance Exchange: Enrollment. It is based on version/release/subrelease 008020 of the X12 standards. |