For the health care folks here you should look at both the 999 Implementation Guide TR3 - reports both X12 syntax and implementation guide errors. There is also a health care-specific TR3 for the 824 Application Guide. All X12 TR3s can be purchased from DISA at www.disa.org. I know, I know!! They cost money - just wait 'til you see the price tag for the v5010 TR3s being proposed for adoption under HIPAA rule making - final rule could hit the Federal Register before January 20th.
Also, the CORE Operating rules require CORE-certified entities to support the TA1 and 997 - all CORE rules are available for download - at NO cost - at www.caqh.org. Rachel Foerster From: [email protected] [mailto:[email protected]] On Behalf Of Pete Austin Sent: Thursday, January 08, 2009 11:53 PM To: Matt Shults Cc: Earl Wertheimer; [email protected] Subject: Re: [EDI-L] <TECH> How to responde to severly mal-formed EDI files when we cannot gen a 997 On other suggestion. The 824 gives you some additional options. Of course, if they couldn't create the document correctly in the first place, the chances that they could read an 824 is pretty slim.... On Thu, Jan 8, 2009 at 4:46 PM, Matt Shults <[email protected] <mailto:matrixeyes%40yahoo.com> > wrote: > The ISA and GS are good but things go south rapidly on the first ST, > segments out of order, HL loops all fouled up -- the partner has had a > history of intermittant data quality, but recently had some personnel > turnover and something was changed on their side. One suspects if they have > a tool they are mis-using it. > > As I say we handle it now with a simple automated email, but I was thinking > it would be nice to provide > some more technical feedback like a 997. > > I since heard back from the vendor went back, and tried saving the 997 > anyway, all I got was a mal-formed 997 since the framework was never able to > finish parsing the doc. I could put more work into it but I think the > automated email notification combined with the missing 997 will have to > suffice. > > Some very good feedback, I thank you all! > > Matt > > > > ------------------------------ > *From:* Pete Austin <[email protected] <mailto:paustin%40axiom-systems.com> > > *To:* Earl Wertheimer <[email protected] <mailto:earlw%40spe-edi.com> > > *Cc:* Matt Shults <[email protected] <mailto:matrixeyes%40yahoo.com> >; [email protected] <mailto:EDI-L%40yahoogroups.com> > *Sent:* Thursday, January 8, 2009 12:31:53 PM > *Subject:* Re: [EDI-L] <TECH> How to responde to severly mal-formed EDI > files when we cannot gen a 997 > > > Actually, you raise an excellent point. However a 997 *is* made to notate > an invalid X12 transaction - that is its entire reason. Take a look at the > AK segments and their codesets. > > However, some data is just really really bad. Hard to keep it all out. > There are compliance validators that can help keep your translator > insulated, but outside Healthcare (and its HIPAA regulations) they are not > well utilized. > > Thanks, > Pete > > -- > Pete Austin, PMP > Vice President, eCommerce Services > AXIOM Systems, Inc. > The Managed Care Systems Experts > 241 E. Fourth Street, Suite 200 > Frederick, MD 21701 > www.axiom-systems.com > 240 605 6939 cell > [email protected] <mailto:paustin%40axiom-systems.com> > > > On Thu, Jan 8, 2009 at 2:40 PM, Earl Wertheimer <[email protected] <mailto:earlw%40spe-edi.com> > wrote: > >> Matt >> >> If it's malformed, not readable and not a regular thing, you can ignore it >> or >> do what you are doing. >> >> The entire point of the 997 is to acknowledge receipt of a valid X12 >> document >> (and optionally, indicate a problem). >> >> If it's invalid, you shouldn't be sending back a 997. >> >> If they don't get back your 997 in a reasonable amount of time, then they >> should be asking about it, or resending the document... >> >> It's _really_ rare to see an invalid document... Are you sure that it's >> not >> something on your side? >> >> >> >> >> >> >> To: [email protected] <mailto:EDI-L%40yahoogroups.com> >> From: Matt Shults <[email protected] <mailto:matrixeyes%40yahoo.com> > >> Date sent: Thu, 8 Jan 2009 11:27:58 -0800 (PST) >> Subject: [EDI-L] <TECH> How to responde to severly >> mal-formed EDI files >> when we cannot gen a 997 >> >> > We use a product from EDIdEV which is a programmer framework tool for >> > EDI. When we receive an inbound file that is so mal-formed, the >> > framework throws a general error and is not able to generate a 997. >> > Right now we catch that and send an email to the TP technical contact >> > about the file. >> > >> > I'm wondering is there a better approach? If we were to fabricate a 997 >> for such a situation I'm not even sure what we would populate it with since >> we can't parse a single transaction. >> > >> > Thanks! >> > Matt Shults >> > <TECH> >> > >> > >> > >> > >> > ------------------------------------ >> > >> > ... >> > Please use the following Message Identifiers as your subject prefix: >> <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> >> > >> > Job postings are welcome, but for job postings or requests for work: >> <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links >> > >> > >> > >> > >> > __________ Information from ESET NOD32 Antivirus, version of virus >> signature database 3751 (20090108) __________ >> > >> > The message was checked by ESET NOD32 Antivirus. >> > >> > http://www.eset.com >> > >> > >> > >> >> Earl Wertheimer >> [email protected] <mailto:earlw%40spe-edi.com> >> http://www.spe-edi.com >> >> >> ------------------------------------ >> >> ... >> Please use the following Message Identifiers as your subject prefix: >> <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> >> >> Job postings are welcome, but for job postings or requests for work: >> <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links >> >> >> >> > > [Non-text portions of this message have been removed] [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> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[email protected] mailto:[email protected] <*> 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/
