Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

The 997 Acknowlegement

Status
Not open for further replies.

DonPedro05

Technical User
Nov 9, 2001
8
US
I am in the health care industry. Clients pass to us 834 transaction sets. We are new to the HIPAA EDI process. I am wondering if there are any instances where the AK901 or AK501 fields will read "E"? What instances?

Thanks,
Pete
 
No. I still haven't found any examples.

Thanks,
- PETE
 
yes. if there was an error in the Group you will have an E in the AK901. It will show in the AK501 for an error in the transaction.
 
Hello gibson153,

I have couple of questions here :

1) Will 997 will be sent for every interchange?
2) If any of the transactions have been rejected in a functional group of ISA, then will whole ISA be rejected or just the transaction? In that case how the 997 will be sent.

Thanks in advance,
Ramu
 
A 997 can be generated for each interchange. A compliance error (e.g. missing required information, indicator w/out data, missing segments, etc.) at the detail segment level will only cause the functional group to be rejected, not the whole interchange...unless, of course, you send only one functional group!

I am still looking for someone to provide me with an example of what type of error produces an "E" in AK501.

Thanks,
- PETE
 
Actually to acknowledge at the interchange you would receive a TA1 (the interchange equivalent of the 997). Other wise you will receive a 997 with the AK1 and AK9 acknowledging the group control number, and the AK2 and AK5 acknowledging the transacition control number. The AK3 and AK4 will privide the error detail of the segment and field that was non compliant and should provide the error detail you are requesting. I will see if I can find a good example for you twomorrow (12/12/01)
 
I found an example where a data element field was too long. This data was still able to be exported to the application without any problems. It was just noted as non compliant. That is an example of why you would receive and E (accepted with errors) as apposed to an R (rejected).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top