About MEDITECH Reports

 

View John Sharpe's profile on LinkedInI'm your host, John Sharpe, a MEDITECH Consultant living in Spokane, WA. Read more ...

Connect ...

Expand your network by connecting on these social media sites:

Sign up for the MEDITECH Reports Blog; details to attend MEDITECH workshops are sent out 1 week in advance to all MEDITECH Report blog subscribers.

These MEDITECH Workshops are sponsored by Donna Carroll at the MEDITECH Community Bulletin

MEDITECH NPR & RW RESOURCES:

Ascii Table: For NPR Report Writer
Loop Builder: For NPR Macros
Key Codes: For CDS Attributes
List Builder: For NPR Macros
MT Report Names: For NPR Reports
MT Structure Viewer: For Physicals
Strings: Format & Sort

HIT Topics

MEDITECH Reports

Current Articles | RSS Feed RSS Feed

MEDITECH Pharmacy ( PHA ) Rules & Line Checks

 

I was working with a friend on a MEDITECH PHA rule today when it hit me. Pharmacy Rules and NPR Line Checks are very similiar.

You can use a Line Check (LC) to print or not print a report line. But LCs are often used to just run a macro or a piece of code and still print the report line. When the LC returns NIL as "", the line will not print. Any value other than NIL "" will allow it to print. Typically programmers return 1 to allow the line to print.

Often the LC will look like this when you just want to run some code, and have the line print:

LC=%APP.DPM.zcus.report.name.M.macro.name(""),1

A PHA rule can be used in the same way when you don't actually want to run the rule in a traditional sense. If your rule uses a keyword that runs code or a macro it must evaluate to a non-nil value for the drug order to go thru. If you just want to run some code and not affect the outcome of the order; then end your code with ,1 which returns the non-nil value. As you can see this is very similiar to the LC example from NPR above.

Want an alert when the next post is published? Click the phone and Subscribe to the MEDITECH Reports Blog!

Subscribe to the Meditech Blog     

                                                                                                                                                                                                          

Comments

Currently, there are no comments. Be the first to post one!
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics