There is a published 824 IG for insurance transactions, including healthcare, based on version 4050 or 4060. A TR3 based on version 5010 is in process.
For healthcare, it is going to be as good as the input it receives from users. The 999 is a fairly new transaction, hence it does not have a widespread use in insurance (including healthcare and P&C) yet. However, anyone responding to an implementation guide or TR3, will be much better off using the 999 over the 997. X12C is working together with X12N to produce implementation guides for the 997 and 999, and to recommend against using the 997 when responding to an implementation guide. While it does not help someone responding to a transaction set (e.g. 850 to/from Walmart), it should be very helpful to anyone using an implementation guide or TR3 in any industry (healthcare is not the only industry developing TR3's). A better approach in that case will be3 TA1, 999, 824, and appropriate application response transactions. Keep in mind, as of now limitations of both 997 and 999 include the inability to reject part of a transaction set. Ruben -----Original Message----- From: Rachel Foerster [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 15, 2005 11:00 AM To: 'EDI-L Mailing List' Subject: RE: [EDI-L] Re: Rejected Sets in 997 Except, William, that the healthcare 824 TR3 implementation guide is not yet a done deal.....plus, some of the comments posted to the health care list about it indicate there may be challenges, if not barriers, to effectively using it to report comprehensively. And of course I know that the 997 is for X12 syntax errors only. The 999, as Ruben Zaggai mentions, can be used for both syntax and IG error reporting, but the 999 is not in wide spread use in healthcare and I don't believe there is a healthcare implementation guide for it. As for the other transaction sets, they are for application error reporting, as you know, and do not report X12 syntax errors. Quite frankly, a good implementation approach would be to use the TA1, 997, 824, and appropriate application response transactions in a comprehensive architecture. Rachel _____ From: William J. Kammerer [mailto:[EMAIL PROTECTED] Sent: Monday, February 14, 2005 7:19 PM To: EDI-L Mailing List Subject: Re: [EDI-L] Re: Rejected Sets in 997 Rachel, maybe "Geo" is using the 864 Text Message to inform his trading partner of *semantic* errors in the received transaction set. The 997 can be used only - aside from positively acknowledging receipt - to report X12 syntax errors. There is no capability in the 997 to report implementation guide (IG) or data content errors. The 824 Application Advice as used in Healthcare might be a better choice, but the 864 is common enough (even in Healthcare!). William J. Kammerer Novannet Columbus, OH 43221-3859 . USA +1 (614) 487-0320 ----- Original Message ----- From: "Rachel Foerster" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, 14 February, 2005 05:44 PM Subject: RE: [EDI-L] Re: Rejected Sets in 997 Not true, Geo - the 997 can notify the trading partner that there are errors, what the errors are, what segment or data element is in error, return the bad data element to the originator, and indicate whether the receiver is accepting the functional group with errors or rejecting it. If you haven't looked at the full 997 specification, you should do so. Pay particular attention to the AK3/AK4 segments. Rachel _____ From: georgeopenx1 [mailto:[EMAIL PROTECTED] Sent: Monday, February 14, 2005 11:56 AM To: [email protected] Subject: [EDI-L] Re: Rejected Sets in 997 Rachel, 997 only notifies trading partners something is wrong. Normally, we use 864 for the exact error descciption. Also, ear to ear communication is a fast way to pin and correct errors sometimes. Thanks, Geo . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Sponsor ADVERTISEMENT <http://us.ard.yahoo.com/SIG=129ovvlv3/M=298184.6018725.7038619.3001176/D=gr oups/S=1705005582:HM/EXP=1108516764/A=2532114/R=2/SIG=12kf3477g/*http://clk. atdmt.com/NFX/go/yhxxxnfx0020000014nfx/direct/01/&time=1108430364855677> <http://us.adserver.yahoo.com/l?M=298184.6018725.7038619.3001176/D=groups/S= :HM/A=2532114/rand=483764855> _____ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> . [Non-text portions of this message have been removed] . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Sponsor ADVERTISEMENT <http://us.ard.yahoo.com/SIG=1299pg5mu/M=298184.6018725.7038619.3001176/D=gr oups/S=1705005582:HM/EXP=1108571431/A=2532114/R=2/SIG=12kniv4et/*http:/clk.a tdmt.com/NFX/go/yhxxxnfx0020000014nfx/direct/01/&time=1108485031229181> <http://view.atdmt.com/NFX/view/yhxxxnfx0020000014nfx/direct/01/&time=110848 5031229181> <http://us.adserver.yahoo.com/l?M=298184.6018725.7038619.3001176/D=groups/S= :HM/A=2532114/rand=212224354> _____ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of <http://docs.yahoo.com/info/terms/> Service. [Non-text portions of this message have been removed] . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
