Important Changes for X12 Version 5010 HIPAA Transactions

In my last blog I discussed the final rule adopting X12 Version 5010 for HIPAA transactions.  There are key differences that should be noted besides the many changes to segments and elements.  Three of the important changes for version 005010 are Version/industry group ID (GS08), ST03 element, and the 999 Implementation Acknowledgment.  The three sections to follow will address each of these areas.

1. Version/industry group ID GS08 changes

Message ID Group codes version 004010/ industry identifier version 005010/ industry identifier
270 HS 004010X092A1 005010X279
271 HB 004010X092A1 005010X279
276 HR 004010X093A1 005010X212
277 HN 004010X093A1 005010X212
278 HI 004010X094A1 005010X217
820 RA 004010X061A1 005010X218
834 BE 004010X095A1 005010X220
835 HP 004010X091A1 005010X221
837Prof HC 004010X098A1 005010X222
837Inst HC 004010X096A1 005010X223A1
837Dent HC 004010X097A1 005010X224A1

2. ST03 added

The ST03 element was added to all of the above transactions.  This element contains the same value as GS08.  Some EDI translation products omit the ISA and GS segments (envelopes) prior to application (ST-SE) processing.  By providing the information from GS08 at this level, it will ensure that the appropriate application mapping is used at translation time.

3. 999 Implementation Acknowledgment

The 999 Implementation Acknowledgment transaction is an EDI response message to confirm a file was received and could be properly read by the translator. The 999 can also report on exactly what syntax-related issue caused the errors on the original document.  It can notify the sender whether the document was accepted or rejected.  While the 999 will acknowledge receipt of the sent document, it does not guarantee that the transaction will be put in use by the business process.  For example, just because an acknowledgment is sent does not guarantee a “Claim” will be processed through the adjudication system.

999 Acknowledgment result types:

A – Accepted
R – Rejected
E – Accepted with errors

999 Acknowledgment sample data:


AK1: This segment refers to the (GS) group level of the original document

AK101 is equal to GS01 from the original document.  For example, for a Claim, AK101= ‘HC’; for an Eligibility Inquiry, AK101 = ‘HS’
AK102 is equal to GS06 from the original document (Group Control Number)
is equal to GS08 from the original document (EDI Implementation Version)

AK2: This segment refers to the (ST) Transaction Set level of the document

AK201 is equal to ST01 from the original document.  For example, for a Claim, AK201= ‘837’; for an Eligibility Inquiry, AK201 = ‘270’
AK202 is equal to ST02 from the original document (Transaction Set Control Number)
AK203 is equal to ST03 from the original document (EDI Implementation Version)

IK3: This segment reports errors in a data segment and identifies the location of the data segment

IK301 contains the segment name that has the error.  For example, the segment name is ‘CLM’
IK302 contains the numerical count position of this data segment from the start of the transaction set.  For example, the erroneous ‘CLM’ segment is in the 120th position
contains the loop ID where the error occurred.
contains the error code and it states the specific error.  For example, the code ‘8’ states “Segment Has Data Element Errors”

IK4: This segment reports errors in a data element and identifies the location of the data element

IK401 contains the data element position in the segment that is in error.  For example, the error is in position 2; CLM-02
IK402 contains the data element reference number, CLM-02 = ‘782’
IK403 contains the error code and states the specific error.  For the example, the code ‘I12’ states “Implementation Pattern Match Failure”; IK404 contains a copy of the bad data element data.

IK5: This segment reports errors in a transaction set

IK501 indicates states whether the whole document is ‘A’ (Accepted), ‘R’ (Rejected) or ‘E’ (Accepted with errors).  Other codes such as ‘M’, ‘W’ or ‘X’ are available but are rarely used (for security decryption purposes).  For example, IK501 = ‘E’ that means the claim was accepted with errors
IK502 is not used in the example above
IK506 is to report an error code for the full transaction.  IK502 sample error codes include:
1-Transaction Set Not Supported
2-Transaction Set Trailer Missing
3-Transaction Set Control Number in Header and Trailer Do Not Match

20 thoughts on “Important Changes for X12 Version 5010 HIPAA Transactions

  1. stephen lang

    Where can I find a list of the IK304 error codes and their text? I am trying to find the meaning of code I6 in that slot.


  2. Tracey

    Trying to determine for our physicians, if in the eligibility portion of 5010, payers will be required to identify copay, coinsurance and deductible for providers.

  3. Froilan

    I am testing the 5010 transactions and I’ve received this 999 file. Below are the errors I received:


    Where can I find the meaning if error code 5 in IK5 segment?


  4. Lawrence Harris

    I am receiving a 999 with the following error. Specifically the position in IK401 is 3::1 and I don’t see any information on what the ::1 means? The full set is:


    The corresponding segment is:


    There is no N in field 3, UN and MJ are the only two valid values. Can someone enlighten me on what the ::2 means?

    Thanks, Lawrence

  5. Mary


    Trying to figure out why I am receiving this rejection – Help!

  6. Keith

    I am receiving this message from my 999. If I am interpreting this correctly it appears to be indicating there is a problem w/the 9th element of the N4 segment in the 2010 loop.


    I have a couple of issues w/this: 1) the N4 element does not have 9 elements, only 7 and 2)the 2010 loop has several N4 segments and this does not appear to specify which one.

    Thanks, -Keith

  7. Linda


    The 9 is telling you that it is the 9th segment in the message ( ST-SE). Please see description for IK302:

    IK302 contains the numerical count position of this data segment from the start of the transaction set.

  8. Linda



    (composite element) IK401-01 value “3” indicates the data element position
    (composite element) IK401-03 value of “2” indicates repeating data element position

    IK402 value “355” indicates the data element reference number

    IK403 value “4 indicates the error code “Data element too short”

    IK404 value of “N” is a copy of the bad data


  9. Sam


    Can any one help me out in this, What is basically not required.



  10. Ted Wade

    Looking for a source of the all of the 5010 transaction sets and guides. In earlier version good layouts of segment and details items cross references with unique segmentids were provided which i have not been able to locate in current sources.

  11. Hiep

    I got the 999 acknowledgment file back as below for an 837 import, however it’s missing the ik5 segment in this file. How can I get the ik5 segment to shows up in the 999 acknowledgment file? Any idea, advise that you may have would be greatly appreciated!
    Thank you!

    Biztalk 2010 CU5

    999 Acknowledgment files:

    ISA*00* *00* *ZZ*XCLR48 *ZZ*XCLR00 *130103*1030*^*00501*000000017*0*T*>

    ISA*00* *00* *ZZ*48145 *ZZ*617591011CFSP *130122*1148*^*00501*000000092*0*T*>

  12. steve lang


    getting this from MA medicaid


    Cannot figure out what the 7 means.

    This is data sent, F8 is what their specs required, number is original claim no they requested:



Leave a Reply

Your email address will not be published. Required fields are marked *