+01 (909) 494-2134 This email address is being protected from spambots. You need JavaScript enabled to view it.

x12 834 Benefit Enrollment and Maintenance

834 Specifications

 The x12 Transaction Set contains the format and establishes the data contents of the Benefit Enrollment and Maintenance Transaction Set (834) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to establish communication between the sponsor of the insurance product and the payer. Such transaction(s) may or may not take place through a third party administrator (TPA). For the purpose of this standard, the sponsor is the party or entity that ultimately pays for the coverage, benefit or product. A sponsor can be an employer, union, government agency, association, or insurance agency. The payer refers to an entity that pays claims, administers the insurance product or benefit, or both. A payer can be an insurance company, health maintenance organization (HMO), preferred provider organization (PPO), government agency (Medicare, Medicaid, Champus, etc.), or an entity that may be contracted by one of these former groups. For the purpose of the 834 transaction set, a third party administrator (TPA) can be contracted by a sponsor to handle data gathering from those covered by the sponsor if the sponsor does not elect to perform this function itself.

 The EDI 834 transaction set represents a Benefit Enrollment and Maintenance document. It is used by employers, as well as unions, government agencies or insurance agencies, to enroll members in a healthcare benefit plan. The 834 has been specified by HIPAA 5010 standards for the electronic exchange of member enrollment information, including benefits, plan subscription and employee demographic information.

The 834 transaction may be used for any of the following functions relative to health plans:

⇰ New enrollments
⇰ Changes in a member’s enrollment
⇰ Reinstatement of a member’s enrollment
⇰ Disenrollment of members (i.e., termination of plan membership)

 The information is submitted, typically by the employer, to healthcare payer organizations who are responsible for payment of health claims and administering insurance and/or benefits. This may include insurance companies, healthcare professional organizations such as HMOs or PPOs, government agencies such as Medicare and Medicaid.

A typical 834 document may include the following information:

⇰ Subscriber name and identification
⇰ Plan network identification
⇰ Subscriber eligibility and/or benefit information
⇰ Product/service identification

 The recipient of an 834 transaction must respond with a 999 Implementation Acknowledgement, which confirms that the file was received and provides feedback on the acceptance of the document.

834 Example

ISA*00* *00* *12*ABCCOM *01*999999999 *101127*1719*U*00400*000003438*0*P~
GS*PO*4405197800*999999999*20101127*1719*1421*X*004010~
ST*834*0179~
BGN*00*1*20050315*110650****4~
REF*38*SAMPLE_POLICY_NUMBER~
DTP*303*D8*20080321~
N1*P5*COMPAN_NAME*FI*000000000~
INS*Y*18*030*20*A~
REF*0F*SUBSCRIBER_NUMBER~
NM1*IL*1*JOHN DOE*R***34*1*0000000~
PER*IP**HP*2138051111~
N3*123 SAMPLE RD~
N4*CITY*ST*12345~
DMG*D8*19690101 *F~
HD*030~
DTP*348*D8*20080101~
REF*1L*INDIV_POLICY_NO~
SE*16*0179~
GE*1*1421~
IEA*1*000003438~

Address

   Global EDI Management Services
   1900 W Redlands Blvd #13035
     San Bernardino CA 92423

    (909) 494-2134
    contactus@gedims.com
   Mo-Fr: 07.00 - 17.00 PST


If you need data translation! then you've reached your destination.

Latest News

With many years of experience and successful EDI implementations under our belt, GEDIMS has developed a methodology that will keep your business on the right track.

Written on 16 January 2018


Electronic data interchange and file translation services for all businesses, we will reduce your manual data entry and increase productivity.

Written on 14 November 2017