Technically speaking, MEDITECH's Data Repository is a typical relational database, in that it stores data in tables, uses primary key columns for referential integrity, and is interacted with using off-the-shelf tools like Microsoft SQL Server Management Studio. But there are several aspects that make it unique – and challenging to work with – all of which are important to understand if you’re a data analyst or report writer at a MEDITECH hospital.

CMS recently published the CY 2020 Quality Payment Program (QPP) Final Rule which included numerous updates to the Merit-based Incentive Payment System (MIPS) for 2019, 2020 and 2021 reporting.

One of my favorite features of SQL Server Reporting Services is the ability to provide a parameter with multiple values. This is a great way to give your users flexibility at runtime by allowing them to select one, two, several, or all values from a given list. It even has a built-in way to easily select and de-select all the possible values. A common scenario that would benefit from this is when you are going to publish a single report that could potentially be used by multiple locations or departments.

How do I find data in the MEDITECH Data Repository?

Many new DR report writers have a challenging time locating data in the DR because they're unfamiliar with the database table and column naming conventions. Luckily for those users, MEDITECH has provided tools within each application as well as system level tables for both the NPR and M-AT platforms that help to identify table and column data.

Knowing which tables to use is one of the biggest challenges when writing DR reports. Understanding those tables, and the relationships between them is part of that challenge. Primary keys are a critical part of any database, but especially so in the DR, since they are the only definition we have for how to correctly and quickly get information.

CMS recently released the FY 2020 Inpatient Prospective Payment Systems (IPPS) Final Rule which continues to focus on transforming the healthcare delivery system to provide patients with better care. To this end, CMS has finalized changes to the Hospital Inpatient Quality Reporting (IQR) program and Medicare & Medicaid Promoting Interoperability (PI) program for eligible hospitals and critical access hospitals (CAHs).  (For the full text of the final rule, see the Federal Register.)

As report writers and analysts, we sometimes have to ask: how do I go about optimizing data retrieval from the MEDITECH Data Repository? When is it appropriate to construct a data mart and what should I consider?  Before we explore the answer, let's first, define a few terms (thanks to Technopedia and Wikipedia):

Whether you’re GPSing around traffic, going through a drive-thru, or using ALT+TAB to switch between open windows, life demands shortcuts. You know the adage – work smarter, not harder. Working with SQL Server is no different - if you’re a busy developer or DBA, you likely spend part of your day writing TSQL code in Management Studio. Fortunately, Microsoft has built in features we can use to make our jobs a bit easier. Here are a few recommended shortcuts and other tips to help save you time and keystrokes.

CMS recently published the FY 2020 proposed rule for the Inpatient Prospective Payment Systems (IPPS) which continue to focus on transforming the healthcare delivery system to provide patients with better care. To this end, CMS has proposed changes to the Hospital Inpatient Quality Reporting (IQR) program and Medicare & Medicaid Promoting Interoperability (PI) program for eligible hospitals and critical access hospitals (CAHs).  (For the full text of the rule, see the Federal Register.)

As an experienced Data Repository report writer, it’s easy to take for granted how much knowledge someone may have about MEDITECH, or assume that hospital IT staff simply know certain things. This was glaringly apparent to me when teaching an introductory DR report writing class recently. Having taught the class for 8+ years, I was presented with a novel situation: the hospital was a brand-new MEDITECH 6.1 client, having switched from another system entirely. 

Not only is it possible to access DR data across SQL servers, but it’s also possible to combine data from different sources in the same query. If there is such a thing as the holy grail of DR reporting, this may be it. Not only is it possible to access data across SQL servers, but it’s also possible to combine data from different sources in the same query. Normally this is straightforward, but the DR adds an extra challenge because of an atypical server-wide setting: the server collation.