Would someone please explain this last comment, "Unless you have a process by which to "swap" out the local and state codes to HIPAA standards. I hold a patent on this." Provide an example.
-----Original Message----- From: Michelle Shores [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 03, 2001 2:44 PM To: [EMAIL PROTECTED] Subject: RE: Question on Legacy Systems Michelle Shores, EMSi, Inc. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 03, 2001 1:02 PM To: [EMAIL PROTECTED] Subject: RE: Question on Legacy Systems Nothing says we have to modify our legacy systems, so the approach of developing methods to receive and send compliant transactions is what is needed. But it is not merely a matter of translating formats. The code sets are likely to cause major issues if you use any local codes or if your system requires data that are not included in the HIPAA transactions data model. Since you may not depart from the contents of the standard when there is a standard for the transaction, you may be pressed to find ways to acquire data in a HIPAA transaction that your legacy system expects to process. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Smith Sent: Wednesday, October 03, 2001 5:01 AM To: [EMAIL PROTECTED] Subject: Re: Question on Legacy Systems Although I don't recall where I saw it, I have also read something on the fact HIPAA does not require that you modify your legacy system. You are only required to be in position to send and receive standard transactions. After you receive the transaction, you can translate the transaction into whatever format you need for your legacy processing. You do, however, have to maintain the capability of recreating the standard transaction. Cindy Nielsen wrote: > We are currently planning to replace our legacy A/R Clinical applications with a new software. Due to the size of our corporation it is going to take quite some time to implement this new system. We are in project planning phases right now > > My question is on our legacy systems. I was in a meeting not long ago and one of the other providers commented that we do not need to worry about getting our legacy system compliant by October 2002. They stated somewhere in the transactions standards there is a clause on legacy systems. I have read through the transaction standards this a.m. and cannot find anything that specific so I am not sure where they are getting this information. > > The way I interpret the rule is having new or old software doesn't make any difference. By the compliance date we have to have a method in place to convert the data from the old system into the correct X!@ formats if we do electronic transactions (which we do). > > Am I understanding this correctly? > > Any thoughts would be much appreciated! > > Thank you. > > Cindy M. Nielsen > Department Director, Information Security > Good Samaritan Central Office > Phone: 605-362-3252 > Fax: 605-362-3991 > email [EMAIL PROTECTED] > > ********************************************************************** > To be removed from this list, send a message to: [EMAIL PROTECTED] > Please note that it may take up to 72 hours to process your request. ********************************************************************** To be removed from this list, send a message to: [EMAIL PROTECTED] Please note that it may take up to 72 hours to process your request. ********************************************************************** To be removed from this list, send a message to: [EMAIL PROTECTED] Please note that it may take up to 72 hours to process your request. ********************************************************************** To be removed from this list, send a message to: [EMAIL PROTECTED] Please note that it may take up to 72 hours to process your request.
