I did not even think of that - I will now 
 
Thanks for the knowledge!
 
Brian Stevenson - Systems Administrator
University Health System - Business Information Systems
4502 Medical Drive - San Antonio, Texas 78229
Office: (210) 358 - 9282
Pager: (210) 756 - 0582
Fax: (210) 358 - 9287
 


  _____  

        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Walker, Reese
        Sent: Friday, October 12, 2007 8:28 AM
        To: [email protected]
        Subject: RE: [Talk] I have two questions...
        
        

        That actually makes better since than anything so far because
when I am watching it, it is obviously unlocked.  Seeing that I am using
a VM Workstation, I can completely disable the screen saver.  I will see
how well it works this weekend.

         

        Thanks,

         

        Reese

         

        Reese E. Walker
        Financial Systems Analyst
        Phoebe Putney Memorial Hospital
        Phone: (229) 312-4259

        
  _____  


        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shirley Hammack
        Sent: Friday, October 12, 2007 9:08 AM
        To: [email protected]
        Subject: RE: [Talk] I have two questions...

         

        Reese, at my previous hospital I had a problem like this.  It
was because when our screen savers came on they automatically locked the
computer screen.  There were certain things that caused our BWS scripts
to stop under a locked screen.   Just a thought.

         

        Shirley Hammack

        I.T.  Financial Analyst

        Duncan Regional Hospital

        580-251-8939

         

        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Walker, Reese
        Sent: Friday, October 12, 2007 7:31 AM
        To: [email protected]
        Subject: RE: [Talk] I have two questions...

         

        I am still working on this script and everything seems to work
perfect when I am watching it run, but at 5AM every morning when it is
scheduled to run, something always seems to be causing it to hang?  What
is the best way for me to "capture" what could be causing this?  I even
got up one morning to watch it and it actually worked that day, which is
the only day it has worked on its own?

         

        Thanks,

         

        Reese

         

        Reese E. Walker
        Financial Systems Analyst
        Phoebe Putney Memorial Hospital
        Phone: (229) 312-4259

        
  _____  


        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Walker, Reese
        Sent: Tuesday, October 09, 2007 9:47 AM
        To: [email protected]
        Subject: [Talk] I have two questions...

         

        1)       I am running a script to download some reports in STAR.
Right now I have a one minute wait step after I accept the download
screen b/c it could take a few seconds to as long a minute depending on
the size of the reports for that day.  How do I build the step to say
wait until "Report Successfully Downloaded" is splashed on the screen to
go to the next step?

        2)       I saw on a video that in order to use the scheduler BWS
has to be opened, so what I am currently doing is using a windows
scheduled task to open BWS about 5 minutes before I want to script to
run and then using the schedule in the BWS to actually kick off the
script.  Is there a better way to do this? Surly I can save a runtime
only script and set a windows scheduled task to kick it off, but so far
it only opens the program but doesn't run the script.

         

        I realize my questions are elementary, but I am still learning
and any help is greatly appreciated.

         

        Thanks,

         

        Reese

         

        Reese E. Walker
        Financial Systems Analyst
        Phoebe Putney Memorial Hospital
        Albany, GA. 31702
        Phone: (229) 312-4259
        Pager: (229) 431-7658
        Fax: (229) 312-4316

         

        
  _____  


         

        
        Disclaimer:
        The HIPAA Final Privacy Rule requires covered entities to
safeguard
        certain Protected Health Information (PHI) related to a person's
        healthcare. Information being faxed to you may include PHI after
        appropriate authorization from the patient or under
circumstances
        that do not require patient authorization. You, the recipient,
are
        obligated to maintain PHI in a safe and secure manner. You may
not
        re-disclose without additional patient consent or as required by
        law. Unauthorized re-disclosure or failure to safeguard PHI
could
        subject you to penalties described in federal (HIPAA) and state
        law. If you the reader of this message are not the intended
        recipient, or the employee or agent responsible to deliver it to
        the intended recipient, please notify us immediately and destroy
        the related message.

         


"CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it
are the property of DRH and/or its affiliates, are confidential, and are
intended solely for the use of the individual or entity to whom this
e-mail is addressed. If you are not one of the named recipient(s) or
otherwise have reason to believe that you have received this message in
error, please notify 580.251.8773 and delete this message immediately
from your computer. Any other use, retention, dissemination, forwarding,
printing, or copying of this e-mail is strictly prohibited."

         

        
  _____  


        


        
        Disclaimer:
        The HIPAA Final Privacy Rule requires covered entities to
safeguard
        certain Protected Health Information (PHI) related to a person's
        healthcare. Information being faxed to you may include PHI after
        appropriate authorization from the patient or under
circumstances
        that do not require patient authorization. You, the recipient,
are
        obligated to maintain PHI in a safe and secure manner. You may
not
        re-disclose without additional patient consent or as required by
        law. Unauthorized re-disclosure or failure to safeguard PHI
could
        subject you to penalties described in federal (HIPAA) and state
        law. If you the reader of this message are not the intended
        recipient, or the employee or agent responsible to deliver it to
        the intended recipient, please notify us immediately and destroy
        the related message.
        




-----------------------------------------
CONFIDENTIALITY NOTICE: This communication is intended only for the
use of the individual or entity to which it is addressed and may
contain information that is privileged, confidential, and exempt
from disclosure under applicable law.  If you are not the intended
recipient, you are notified that any use, dissemination,
forwarding, distribution, or copying of the communication is
strictly prohibited.  Please notify the sender immediately by
e-mail if you have received this by mistake and delete this e-mail
from your system. (University Health System)
BEGIN:VCARD
VERSION:2.1
N:Stevenson;Brian
FN:Brian Stevenson
ORG:University Health System;Business Information Systems
TITLE:Systems Administrator
TEL;WORK;VOICE:(210) 358-9282
TEL;CELL;VOICE:(210) 410-0526
TEL;PAGER;VOICE:(210) 756-0582
TEL;WORK;FAX:(210) 358-9287
ADR;WORK:;Business Center;355-2 Spencer Lane;San Antonio;Texas;78201;United States of America
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Business Center=0D=0A355-2 Spencer Lane=0D=0ASan Antonio, Texas 78201=0D=0AU=
nited States of America
ADR;HOME:;;;;;;United States of America
LABEL;HOME:United States of America
ADR;POSTAL:;;;;;;United States of America
LABEL;POSTAL:United States of America
URL;WORK:http://www.universityhealthsystem.com
EMAIL;PREF;EX:/o=UHS/ou=First Administrative Group/cn=Recipients/cn=BLS90720
REV:20070328T174621Z
END:VCARD

Reply via email to