Tony, Great info. Can you explain how one would go about doing that?
Claudine :) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Anthony Schmidt Sent: Wednesday, July 31, 2002 10:17 AM To: [EMAIL PROTECTED] Subject: RE: HIPAA Help Dave: If you run your R:Base applications on a W2K Terminal Server you can set an "Idle Session Limit" which can disconnect/end Idle terminal sessions. In addition, you can run your password control through the network and only permit access to your R:Base applications if the user has entered a correct network user name and password. Tony Anthony Schmidt, JD President The Computery Ltd. One East Main Street Bay Shore, NY 11706 631-665-8100 Voice 631-969-5988 Fax [EMAIL PROTECTED] htttp:\\www.computeryltd.com [EMAIL PROTECTED] 07/31/2002 09:29 AM Please respond to rbase-l To: <[EMAIL PROTECTED]> cc: (bcc: Anthony Schmidt/BayShore/SGU_LN) Subject: RE: HIPAA Help Marc - I've been to (too many) workshops on the EDI and confidentiality requirements. I have a summary in PDF format I can send you, but nothing beats reading federal laws <g>. Contact me at [EMAIL PROTECTED] if you want any of the summary material. For everyone else: One of the requirements is for the system to automatically log off unattended workstations after a period of inactivity. From previous discussions I know we can do this from the R>, but not if there is a form on screen. This is the only argument against forms-based menu systems I can imagine. However, any other menu presentation method involves a command file hanging there awaiting a response, and I've not been able to get an application to time out. Is this a reason to use CONNECT...DISCONNECT at the application menu level (i.e., present menu, leave on screen, disconnect, WHILE loop to count time elapsed, issue an EXIT if no response received)? tia Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of marc schluter Sent: Wednesday, July 31, 2002 8:52 AM To: [EMAIL PROTECTED] Subject: Re: HIPAA Help Thanks Bill I have been looking at that site and a few others. I was hoping for a simple 1,2,3 and avoid going through everything page by page. One thing I have found out is I will need a better password system. All I use now is an owner password which only I know and a generic password that allows the doctors and users get access to the tables and forms. One web site suggested that the user be allowed to change their passowrd every month. Thanks marc --- Bill Downall <[EMAIL PROTECTED]> wrote: > I know you may be looking for a quick solution, and > this is not that. > > http://www.hhs.gov/ocr/hipaa/ > > You can download the 400 page PDF document on the > National > Standards to Protect the Privacy of Personal Health Information, as > well as proposed changes, etc. It also has links to other > sites. > > Bill > > On Tue, 30 Jul 2002 05:38:44 -0700 (PDT), marc > schluter wrote: > > >I am trying to find out what changes I need to make > to > >my billing software to make it HIPAA compliant. > > > > > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO > rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE > rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
