Tricks of the Trade: Data Repository (DR) Monitoring for Client Server 5.6

By: John Sharpe, President, Comstock Software, Inc.

As your clinicians and financial office come to rely upon DR reports, your IT department will be dedicating time each day to monitoring your DR system.   Without monitoring, loading of the data can stop due to a load error on a by transfer job / table basis.  Without current data, your phone will be ringing.  One way to be proactive is to routinely review your MEDITECH Database Logs.

Your typical DBA / SQL report writer / programmer type will be more comfortable writing SQL scripts than with navigating MEDITECH menus.  MEDITECH stores DR load error information in your SysDrConnection tables.  Depending upon how your system is configured, there can be more than one table at a time.

Wouldn’t it be nice to query all of these tables at once?  And, instead of seeing all that detail, there might be specific details which are important to know, such as which applications have the highest number of load errors.

Head over to the MEDITECH Open Source Repository for DR.  Get the code now and share with your favorite report writing guru.

If you’d like to contribute to this repository; get involved, be part of something you can benefit from and refer back to over the course of your career.

-->Email code changes and open source contributions to John at jsharpe@comstock-software.com.

***

Questions regarding reports and your 5.6 upgrade?
  Email them to John at jsharpe@comstock-software.com.

John Sharpe is President & MEDITECH Solutions Developer at Comstock Software, Inc. Learn more about NPR Report Writing at the MEDITECH NPR Report Writing Blog.