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:

Previous Posts

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

MT Resources

Blog Roll

Archives

MEDITECH Reports

Current Articles | RSS Feed RSS Feed

MEDITECH Report Designer Represents a Major Step

Posted by John Sharpe on Wed, May 26, 2010 @ 01:33 AM
 

Eric's musings on the iPad reminds me of my recent trip to Framingham, for MEDITECH 6.0 Report Designer training.

The MEDITECH Report Designer is different than the NPR Report Writer.

And while some report writers may feel frustrated using the new 6.0 Report Designer, others will feel right at home.

MEDITECH's design of the new Report Designer seems right in step with Apple's choice to trade power and flexibility for simplicity.

With Iatric's release of the Iatric Data Access Driver (iDAD rhymes with iPAD), maybe there's a way to have all 3: power, flexibility and simplicity ... all at one time. I for one, am looking forward to learning more about this new release by Iatric Systems.

If you have thoughts or questions about MEDITECH Report Writing or 6.0, drop in on us at the MEDITECH KE.


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

Subscribe to the Meditech Blog     

                                                                                                                                                                                                          

Tags: 

Comments

I have worked with NPR for many years and with Data Search (DSR) before that and have been working with the Report Designer a lot in recent months. 
 
 
 
I agree that the design for the Report Writer is very good and I think that someday it may be very, very good. 
 
 
 
Now, however, it is absolutely maddening to work with because there is no documentation available and there are a lot of bugs in the module.
Posted @ Thursday, July 08, 2010 5:21 PM by Jim Morrow
Has a method for naming rules in the Report Designer sort of become self evident? Or have you come up with something that works well?  
 
 
 
Posted @ Thursday, July 08, 2010 5:57 PM by John Sharpe
We do not have very many reports that are working yet so naming has not been an issue. If we reach a point where we think that we will develop many reports we will address this. 
 
 
 
I would welcome any help on finding documentation for this module since there is none on the Meditech site nor is there any in the module itself. 
 
Posted @ Friday, July 09, 2010 2:27 PM by Jim Morrow
I expect MEDITECH will respond to customer need by implementing a new naming convention, allowing longer rule name length, and adding optional Read, Write Role Based Security as users experience issues with overwriting, naming and grouping rules. Time will tell where the problems are, and where MEDITECH's focus will be to make rules easier to use.
Posted @ Friday, July 09, 2010 3:54 PM by John Sharpe
In regard to the naming rule, in MEDITECH C/S 5.5 and then 5.64 we had a naming convention for reports in place as we had reports across multiple hospitals and tried to standardize as much as possible. If that is what you are referring to please respond and I can expand or maybe we can touch base.
Posted @ Tuesday, August 17, 2010 4:49 PM by Karen
I'm referring to the naming convention for rules in 6.0 Report Designer; the rules (logic instead of a macro) are stored outside the report. So you have report names and rule names.
Posted @ Wednesday, August 18, 2010 11:54 AM by John Sharpe
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

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