All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
If you don't have too many printers to designate, you might consider this:
On the CDS have the last query say: Print To: Lookup of printer names
Make a copy of the NPR or each printer
On the selects:
xx.printer Q
"MAL1" MAL1 is the name of the printer
In Edit Field attributes enter:
xx.printer DAT=FREE
JFY=L
LEN=1
[EMAIL PROTECTED]"NURNAMEPRINTERQUERY"]
The CDS will only print if the name of the printer query is MAL1
You can repeat this for several printers without a problem
Attach each NPR to the nursing intervention.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Alan Miller
Sent: Monday, August 28, 2006 7:24 AM
To: Mitchell Lawrence; [email protected]
Subject: RE: [MEDITECH-L] NUR.PC.WORK.zcus.prt... printing problems
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
Mitch,
Thanks for your input. I agree that user education is important and
that a minimum expectation should be for users to know what their
printer name is. But with NUR.PC.WORK.zcus.prt... reports the "Print
On" prompt doesn't show. Everything is determined beforehand within the
intervention dictionary, so the printer name must be hardcoded for "a
valid printer". Not a viable option for this function, unless you want
all output to always go to the same place. Not good for us.
Alan
>>> "Lawrence, Mitchell" <[EMAIL PROTECTED]>
08/25/2006 08:51 >>>
All messages should be posted in plain text. HTML will be converted
to
attachments. The meditech-l web site is MTUsers.com
======================================
Sounds as if you are trying to programmatically solve a user education
problem. Often, that is a futile endeavor.
They could use the valid printer option and just know where to print
before hand.
Thank you,
Mitch Lawrence
Senior Applications Analyst - Advanced Report Writer
General Financials Support
CHRISTUS Information Management
Tel: 361.881.3408 Fax: 361.888.6117
Mob: 361.549.8456 AIM: a1d13 MSN: [EMAIL PROTECTED]
[EMAIL PROTECTED]
If someone has "Made your day", send them a Spirit Buck!
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alan Miller
Sent: Wednesday, August 23, 2006 3:49 PM
To: Meditech-L
Subject: [MEDITECH-L] NUR.PC.WORK.zcus.prt... printing problems
All messages should be posted in plain text. HTML will be converted
to
attachments. The meditech-l web site is MTUsers.com
======================================
We're Magic 5.5 and need some help with NUR.PC.WORK reports, more
specifically where the output goes.
On page 2 of the intervention dictionary, one can select from a set of
4 choices:
* a valid printer
* HERE (for the user's location)
* PAT (for the patient's location)
* PATP (for the patient's permanent location)
We can't find one that makes everyone happy -
* a valid printer: these interventions get performed all over the
place, so we don't want to go chasing after a piece of paper in a
distant location.
* HERE (for the user's location): this won't work for our COWS, as
they don't know where "HERE" is. Our COWS are set up generically, so
they can be used in any location. They get turned over (sometimes
literally) often, switched from floor to floor, borrowed by other
departments, etc., so they don't have a default printer set.
* PAT (for the patient's location): many of our outpatients don't
even have real locations, so nothing prints at all with this option.
* PATP (for the patient's permanent location): see "a valid printer"
above.
We tried to insert code into a start macro for the report that would
"hijack" the output to another printer based on the user's location.
It
works OK with a regular report run manually, but not with intervention
reports (NUR.PC.WORK.zcus.prt...). Evidently the intervention process
closes down the hijack attempt before it can process and reverts back
to
the output specified in the dictionary.
For now, we have set up dual output to "PAT" and also "a valid
printer". The COW pokes get their output via PAT, and the DaySurgery
folks get theirs (and everyone else's) on their local printer. There
must be a better way.... We'd appreciate any L-workarounds or
L-insights.
TIA,
Alan Miller, RPH
Catawba Valley Medical Center
Hickory, NC 28602
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
