Michael, Much appraciated. I will keep you in mind. You are absolutley right my database is relational but am parsing the hierarchical 835 into XML that I then put into my relational database. You might ask why I put it into XML and that is because ColdFusion gets along better with XML than a flat file that I would have to parse over and over. the XML file as well as the Flat 835 file will be saved by client so if ever I have to read it the parsing will not have to be done again. But it is good to know that someone has the solution if I cant find it myself. Guillermo
----- Original Message ---- From: Michael Mattias/LS <[EMAIL PROTECTED]> To: EDI-L <[email protected]> Sent: Saturday, August 16, 2008 6:38:55 AM Subject: Re: [EDI-L] Newbie needing to learn 837 parsing 8/16/08 >I am working on a project but need to learn how to parse an 837 file. I > can parse all kinds of documents but this is the first time I have come > across this EDI/X12 thing. Not a bad standard to be honest. But here is > the thing I have to not use a third party to parse, I will program a > parser in ColdFusion. But what I need is to learn how to read the "EDI > Transaction Set 837 Implementation Guide". Does anybody know of a book > that will help or a tutorial maybe? I have looked but all I get is > people who want to sell me their parser. I dont need someones code I > just need to understand this document to where I can write the parser. > any help woould be appreciated. Having written an '837' parser and API myself (but not recalling the chance to sell it to you), I'll tell you one thing you need to do this is a good understanding of hierarchical database design, and specifically how the ANSI ASC X12 standard uses ''envelopes" and "loops" to implement a hierachical model. If you've worked with ANSI ASC X12 data before you probably already have this understanding; if not, I'm not sure where/how you can pick it up, since 'relational' rather than 'hierachical' data management is generally what has been taught in the schools for a number of years, and is the model used by most popular data management systems. But assuming you do understand hierarchical data management, the key is keeping track of which loop you are in as you parse each each transaction set. It will also help a lot - in fact may be a requirement - that you understand healthcare industry terminology. The X096/X097/X098 Implementation Guides are thick; but they *are* well-written. However, they do presuppose at least a basic familiarity with the healthcare industry. Good luck; but if you do get stuck I have some very nice and potentially quite useful software products I'd be willing to license to you. Michael C. Mattias Tal Systems Inc. Racine WI [EMAIL PROTECTED] .com www.talsystems. com [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/
