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

Head Start for your NPR Report

 

I have an ABS report that was looping thru the abs.pat.abs.status.x index.

The physical structure for that index looks like this:

?DZS["FINAL",1]
?DZS["IN PROCESS",100]
?DZS["NONE",125]

The report criteria require records where the status is not equal to "FINAL". So the natural thing for some of us is to put this in our page 2 SELECT:

abs.status NE "FINAL"

The problem is, the NPR report writer will loop thru all the "FINAL" records even though it just wants the "IN PROCESS" & "NONE" records in the index.

What you want to do is set your SELECT like this:

abs.status GT "FINAL"

Now the report writer starts looking in the index at the "IN PROCESS" records and skips all the "FINAL" records in that index.

The proof is in the pudding (object code):

IF{"FINAL"'=D(127)}^dzS,
DO{+?DZS[dzS]^dzS&'/R.LIMIT ""^dz,
DO{+?DZS[dzS,dz]^dz&'/R.LIMIT

This approach will not work in all situations; but that's why you are writing the NPR report and its not writing itself.

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