HI Bill I would love any info you can give me about what you learn at that meeting. I think I will pray for you at that that meeting, you may need it!
So far I have; 1) a column for the date and time modified and who modifies that record 2) several levels of passwords to keep staff out of the areas they do not need access to I still need to find an easy way to save the old record before it was changed so I have an audit trail. Triggers seem to be the way to go but I haven't used them, so I am a little lost as where to start. Thanks for your help, I am looking forward to hear what you learn at your meeting Marc I am attending a conference later in > January including a HIPAA session. If you want, I'll > report when I'm > back from the conference, hosted by the Society of > Actuaries. (I can > hardly wait. I hear they are a really fun bunch. > <g>) > > So far, based on requirements of our health care > industry customers, > we have revised all printed reports so that SSN > almost never prints > with a customer name. We have stopped emailing any > reports from the > R:Base application, even with passworded PKZIPPED > files containing > the reports, because that is not good enough for > HIPAA, unless the > email is encrypted also. Instead, we use 128-bit > encryption on SSL > web servers or SSL ftp servers. > > Our application has role-based security, where every > user has to log in > with username and password, and is prevented from > access to any > functionality that is not required by their role. > > Bill > > On Thu, 9 Jan 2003 05:39:56 -0800 (PST), marc > schluter wrote: > > >I have aprox 30 doctors offices using my app to > bill > >patients and insurance. Some have asked if my > >software is HIPAA compliant. As far as I can tell > >there is very little I have to do on my end to be > >ready for HIPAA. > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
