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] On Thu, Jan 8, 2009 at 2:40 PM, Earl Wertheimer <[email protected]> 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] > From: Matt Shults <[email protected]> > 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] > 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] ------------------------------------ ... 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/
