Migrating reports to the 6.1 platform from MAGIC, C/S, or 6.0 involves a complete re-write of any reports that use data from the modules that move to the M/AT environment. Instead of the few tweaks a hospital may need after NPR reports are batch converted during an upgrade from MAGIC to C/S, when a hospital converts to 6.1, you will need to write new reports with the “Report Designer” tool, or with SQL out of your Data Repository.

Joe Cocuzzo will discuss 6.1 reports migration approaches, strategies, and pitfalls including:

• How to create your “must have” list of reports (and why the “make departments responsible for that list” strategy will fail)
• When to use Report Designer vs. SQL
• How to use SQL and SSRS (or other SQL reporting tools) to create, control, maintain and distribute reports
• Why to consider more than “what we are running now” when you migrate to new and different applications

Don’t overlook the need to review standard reports in the new platform. They often have changed in M/AT, and the new version on the new platform might not suit your end users’ workflow.

As much as you were let down by “Init Report from Standard” in NPR, there is absolutely no equivalent for your M/AT standard reports. They are not written with the RD tool, and any modification of a standard M/AT report must either be done by MEDITECH as a custom, or written from scratch in RD.

The tendency to leave reporting needs until the last minute (or even post-go-live!) is hard to resist. Attend this session to learn how to avoid falling into that trap. Be aware of the trend and try to minimize it, or at least be strategic about what you defer, decline to convert, or replace.