Bill, I think your OE to Mox/E-Mail idea has merit. I think it would work ( based on my limited knowledge as well). I think they would have to watch the number of "Sent Messages" in the SYSOP Mox account, and purge it on a regular basis. Using that approach however, each Mox/Mail message could be deleted as the process has been completed, thereby making a pretty solid message queue.
Paul -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Palmer Sent: Thursday, April 29, 2004 11:18 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Talk] Accessing a Meditech Background job. A couple of ideas come to mind based on limited knowledge. It would be helpful to know exactly which OE routine they are using but if they are using what Meditech calls a "remote printer" it is setup with a tcp/ip address and port number. They could create a listener with that ip address and port number and capture the print information. Another thought again based on limited knowledge in some cases rather than print to a printer messages can be sent to a mail recipient which could be remote recipient and smtp could be used to capture that. Bill Palmer Financial Coordinator, Information Sys Mid-Columbia Medical Center The Dalles, OR 97058 541-296-7417 >>> [EMAIL PROTECTED] 04/29/04 11:01AM >>> I have a request from a Meditech customer that's sort of "beyond my pay grade"... "They want to know how to write a script to capture the information contained in an Meditech OE Background job. Here are the details: They've setup a bogus printer, this bogus printer receives misc messages. Based on what the msg says they want to perform an action, for example they might want to write the data to a web application, update a pt registration, etc. "How would they go about capturing the information in that background job? She said that they cannot print this info to an actual file. I've search Talk and the website, but couldn't find anything." Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com <http://www.bostonworkstation.com/>
