For once, I think i've got you! At a previous assignment (now located in Chennai, which is not a county in New Jersey), we had a home-grown application running Mercator on a mainframe. Three output cards - data validation, translated data, and error report. If the data failed validation, you didn't create the output and produced the error report. If the data was good, you create the (very fast) output and no error report. We had to parse the input file - an ugly, poorly designed cobol copybook structure - and pretend to create the output fields and see if they were compliant. And we had to write a whole bunch of code to emmulate what the translator did normally if it was used in a normal fashion.
Data sent to the network is validated and bounced back if it fails compliance, instead of being delivered. And the bank had no facility to do anything with fails other than report that they happened - no repairs, no resends. So our mission was to never create data that would fail at the network. Now, you reply "why not change the process?" Gee, that's too easy. Effecting change in a large organization - especially a multi-national bank - is very difficult if not totally impossible. So the data mapping had to be done to fit the cobol programs. HIPPA or SWIFT, it doesn't matter. Meanwhile, three kids in India are doing my job, and i'm still on vacation. I just picked up a job application this morning at Starbucks with my coffee. They have real good benefits :) It's just like that great christmas job at the mall - whatever they pay you tends to get spent in the store, even after the generous discount. I have no use for the clothes, but I can definitely go for the discounted latte. I've also explored some work at home jobs, stuffing envelopes for a major bank ... that was one job that they couldn't outsource because "they" didn't want to do it. William J. Kammerer wrote: >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. > > > -- %%%%%%%%%%%%% cut here %%%%%%%%%%%%%%% Brian Lehrhoff ([EMAIL PROTECTED]) Messaging Consultant 201-913-4506 %%%%%%%%%%%%% cut here %%%%%%%%%%%%%%% ------------------------ 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/
