We’re pleased to offer several MEDITECH Report Writing webinars this summer, free to hospital employees. Register to attend any or all these presentations from the comfort of your own office on the dates noted below. Scroll down for registration links and a description of each webinar:
Teach a man to fish… One of my staff needed to create a custom lookup in a MEDITECH NPR report to show the "mapped from" and "mapped to" values for a particular BAR.CLAIM map, and he asked me, “Have you ever done that?”
At International MUSE in May, our report writing educational sessions were a hit once again. We presented two sessions:
To address HIPAA, MEDITECH added logging of access to PHI via reports and all applications, and added that level of detail to MIS user activity logs. So, if you run an NPR, RD, or standard report and the report contains PHI, the run user and the set of patients in the output is logged. MEDITECH has a field in their “programmer” NPR Report Writer routine where they can defeat logging, and that makes sense for big exports where the run user just set up the scheduled report run, but otherwise MEDITECH has fairly comprehensive tracking of access to PHI via most reports.
But what about Data Repository (DR) reports?
What's in a name?
In teaching NPR, RD, and SQL from DR, a big chunk of my time is spent helping students figure out where data is kept (for example, which segment in NPR), and then what field names are called. MEDITECH segment structures and field names are built “by hand” by the application developer, which results in some unfortunate inconsistencies that make our Report Writing lives harder. This post examines MEDITECH field naming across applications, identifies some various “gotchas” to be aware of, and provides some tips for how to overcome those challenges.
Recently a MEDITECH hospital wanted to export a handful of MOX databases, since they were migrating away from MOX. I have done a few of these in the past on rare occasions (on a “per database” basis), and most of the programming time was spent on mapping and cleanup — not on the actual extraction of the data itself.
In this blog post, I’ll discuss how I figured out how to write a generic export in an NPR report, so savvy NPR programmers can do this for themselves in the future.
A MEDITECH 6.0 customer recently requested our help to speed up a report she was using to find all accounts with a final abstract date of T-1. Her report, using the “abs.status.x” index was taking several hours to compile, and this was causing issues for some outside vendor.
In an earlier blog tip I showed how to add an “Echo Name” feature to a MAGIC NPR report, but I did not show a method to do the same thing for Client/Server because I assumed I’d need to use the %NPR.UI programs to write data to the screen and fight the Syntax Checker, which attempts to block any calls to %NPR.
Welcome to our Report Writing Blog!
Welcome to the Iatric Systems Report Writing Blog. This blog will be the new home to our monthly SQL/SSRS/Data Repository Tips, MEDITECH NPR Report Writer Tips, and Report Writing Tips for other platforms (Cerner, CPSI, Epic, McKesson), as well as a venue for sharing other report writing news and views.
MEDITECH MAGIC or Client/Server – Force a report to PREVIEW and show bar codes for scanning
A MEDITECH MAGIC customer recently asked us to produce a report that could show bar codes on the screen of all current ER Patients to allow Nurses to scan an account number code and then any supplies issued to the patient.
Comments