Mmmm, well, not quite. (Apologies, for I seem to be in nit-pick mode. 8-) )
I would make the distinction between translation and parsing. Parsing might be described as the pleasant stroll through the EDI data, used to isolate the components (ie., elements, segments, etc.) Translation is the transformation of the EDI data into some other (app. appropriate?) form. The first phase of the translation would, of course, be the parsing of the EDI data. The big question then becomes, how distinct is the parsing phase from the rest of the process? If the parsing is sufficiently isolated, it might be called more than once with considerably less impact than would be multiple calls to translation. (Necessary disclaimer: your mileage and experience will likely vary.) Best regards, Bill Chessman Inovis(tm) -----Original Message----- From: William J. Kammerer [mailto:[EMAIL PROTECTED] Sent: Friday, September 17, 2004 2:32 PM To: 'EDI-L Mailing List' Subject: Re: [EDI-L] Level 5....??? How do you perform "[c]ompliance checking [of EDI data]... before any translation takes place?" That itself would require translation of EDI data! If you're translating twice, you're undoubtedly doing something terribly wrong. Why not just translate the EDI transaction set *once* and be done with it? After translation, the resultant claims can be examined for both HIPAA compliance and business suitability. William J. Kammerer Novannet, LLC. Columbus, OH 43221-3859 . USA +1 (614) 487-0320 ----- Original Message ----- From: "John Murray" <[EMAIL PROTECTED]> To: "'Bonnie A. Boucher'" <[EMAIL PROTECTED]>; "'EDI-L Mailing List'" <[EMAIL PROTECTED]> Sent: Friday, 17 September, 2004 12:22 PM Subject: RE: [EDI-L] Level 5....??? Bonnie, Let me add to what William said about not sticking code set validation in the translation map. WEDI SNIP also recommends (and I wholeheartedly agree) that compliance checking and translation should be treated as two distinct and separate operations. Compliance checking should be a front-end process that is carried out before any translation takes place. This offers several benefits. HIPAA compliance is a regulatory process, while translation is a business process, By combining the logic for both into your mapping you are then forced to modify both should either process change, whereas by keeping them separate you only have to change the appropriate one if the requirements (ie: HIPAA regs or your business process) change. This simplifies maintenance and reduces the likelihood that Murphy's law will take a hand. Regards, John Murray 703-369-7421 -----Original Message----- From: Bonnie A. Boucher [mailto:[EMAIL PROTECTED] Sent: Friday, September 17, 2004 11:01 AM To: EDI-L Mailing List Subject: Re: [EDI-L] Level 5....??? Thank you William & John. My EDI background is Transportation, which I thought was pretty straight forward, and then I jumped into the Healthcare industry and am now dealing with HIPAA and there are times when I feel like my head is spinning. I appreciate your help! Thanks, Bonnie . 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 ------------------------ Yahoo! Groups Sponsor --------------------~--> $9.95 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/OIFolB/TM --------------------------------------------------------------------~-> . 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/
