I want in on this data station webinar!  ;-)

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Warycha
Sent: Monday, January 29, 2007 7:17 AM
To: [email protected]
Subject: RE: [Talk] Random Errors

 

Tom  thanks

Please count me in

 

 

 

Steve Warycha

St. John's Riverside Hospital

967 North Broadway

Yonkers NY 10701

Phone (914) 964-4578

Fax:(914) 964-4310

Email: [EMAIL PROTECTED]

* There is no right way to do a wrong thing * 

 

        -----Original Message-----
        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thom C.Blackwell
        Sent: Friday, January 26, 2007 3:27 PM
        To: [email protected]
        Subject: RE: [Talk] Random Errors

        Greetings,

        Ah, the DataStation's reporting will do this for you if you add
Record# field to the report.

        So if you just wanted a report that had Record numbers displayed
that had errors. Add the Status and Record# fields. Make sure Status is
the first one in the list. Set the Filter to be = Error (or whatever you
are using to mark the Status with.

         

        Several DataStation reporting related questions today. I believe
a mini webinar on this topic is warranted!

         

        How about Wed.  next week  (Jan 31) at 1:00 Eastern - first 25
people who respond back will receive invites :-)  - If I get more - or
lots of "I can't go's" -  I'll schedule another one.

         

        Regards,

        Thom

         

        Thom C. Blackwell

        Product Manager

        Boston Software Systems

        (866) 653-5105 ex 807

        www.bossoft.com

         

        LEGAL NOTICE Unless expressly stated otherwise, this message is
confidential and may be privileged. It is intended for the addressee(s)
only. Access to this E-mail by anyone else is unauthorized. If you are
not an addressee, any disclosure or copying of the contents of this
E-mail or any action taken (or not taken) in reliance on it is
unauthorized and may be unlawful. If you are not an addressee, please
inform the sender immediately, then delete this message and empty from
your trash.

         

        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gary Williams
        Sent: Friday, January 26, 2007 3:10 PM
        To: [email protected]
        Subject: Re: [Talk] Random Errors

         

        I will try that. I kept trying if statements. sometimes you just
need pointed in the right direction.

         

        One other question, when the error happens whats the best way to
save the record number so that i can e-mail the errors to the
transcriptionist supervisor.

                ----- Original Message ----- 

                From: Lawrence, Mitchell
<mailto:[EMAIL PROTECTED]>  

                To: [email protected] 

                Sent: Friday, January 26, 2007 1:49 PM

                Subject: RE: [Talk] Random Errors

                 

                Code for the error message, then code the steps to back
out. BWS will see the error message and you can create an autopause rule
for it.

                 

                Thank you,

                Mitch Lawrence

                Senior Applications Analyst - Advanced Report Writer

                General Financials Support

                CHRISTUS Information Management

                ': 361.881.3408  7: 361.888.6117

                *: 361.549.8456  )AIM: a1d13  )MSN: [EMAIL PROTECTED]

                *: [EMAIL PROTECTED]

                 

                 

                Send a "thank you"
<http://intranet.christushealth.org/spiritBuck/>  to someone!

                
________________________________


                From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gary Williams
                Sent: Friday, January 26, 2007 1:45 PM
                To: [email protected]
                Subject: [Talk] Random Errors

                 

                I am in the process of writing a rules based script and
have hit an error that I am stumped on.

                Our Transcriptionists have decided to add their own
codes to meditech for a few procedures. The problem is that meditech
does not like the codes and kicks up a yellow error box at the botton of
the meditech workstation screen (ver 3.26). This only happens in maybe
one in every 50 records or so.

                 

                What's the best way to have the script see the error,
back out and then continue with the next record. I have had boston
training but very little vb yet.

                 

                Thanks for any ideas,

                Gary

                Data Tech

                Memorial Hospital

                Belleville, IL

Attachment: image001.gif
Description: image001.gif

Reply via email to