IMHO, it is not justified.

 

While we aren't MAGIC, we deal with a NUI of sorts in Meditech C/S. If
your scripts are built well, you will have no issues.

 

 

Thank you,

Mitch Lawrence

Lead Applications Analyst

Technical Support - NPR/Automation

CHRISTUS Information Management

*: [email protected]
<mailto:[email protected]> 

 

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

________________________________

From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, February 11, 2009 12:43 PM
To: [email protected]
Subject: [talkbws] Meditech Workstation 4.x

 

Good Afternoon All:

          I would like those of you who use MEDITECH MAGIC to comment on
scripting with Workstation 4.x.  I have personally refrained from
scripting with Workstation 4.x because I didn't want to deal with pop-up
boxes and other Workstation 4.x nuances.  It seems as if these nuances
made my scripts less reliable.  So, what do other MEDITECH MAGIC
scripters think of Workstation 4.x?  I'm asking because others in IT
have an initiative to remove Workstation 3.x from every end users PC,
including the end users that run scripts.  Is my poor attitude about
scripting with Workstation 4.x justified?

 

Thanks,


 

 Jared Parish 

 

Whatever it takes!  

Integration Analyst
 

 

CareTech Solutions, Inc
901 Wilshire Drive
Troy, MI 48084
United States 

[email protected]
www.caretechsolutions.com 

 

Ph: 419.429.6476
Fax: 419.423.5540 

 

--- 
To post a message to this list, send mail to: [email protected] 

You are currently subscribed as: [email protected] 

Unsubscribe in the customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk
.aspx 
--- 
To post a message to this list, send mail to: [email protected] 

You are currently subscribed as: [email protected] 

Unsubscribe in the customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk
.aspx 

<<image002.jpg>>

<<image003.jpg>>

Reply via email to