How do I know it's right?

One of the challenges in writing reports from MEDITECH Data Repository (or any system for that matter) is knowing for certain that you got it right. That not only means the data are accurate, but the person requesting the report is satisfied with the result too.

Electronic Case Reporting (eCR) enables automatic, real-time exchange of case information with Public Health Agencies (PHAs).

When data is recorded in the EHR, it is checked against a trigger table to determine whether there is a reportable condition — and if so, an electronic Initial Case Report (eICR) is sent to the PHAs.

Power BI is the latest enterprise business intelligence platform from Microsoft. With Power BI's beautiful and dynamic data visualization tools, unlock the informatics potential of MEDITECH Data Repository in ways not before possible. 

In our first Power BI blog, we introduced the Power BI platform and reviewed the desktop applications and cloud-based tools we can use to develop and share reports and dashboards. In this blog, we’ll look more specifically at the ins and outs of using Power BI with MEDITECH Data Repository.

MEDITECH’s Data Repository has come a long way since its inception over twenty years ago. In the early days of DR, usable front-end reporting tools were few and far between: Microsoft Access and Crystal Reports were common choices for many hospitals. Fast forward to 2021 however, and DR is an integral part of the MEDITECH EHR and report developers have a variety of tools to use: the ubiquitous SQL Server Reporting Services (SSRS) from Microsoft; MEDITECH’s BCA with MicroStrategy; and third-party software like Tableau and Qlik, among others.

CMS recently published the FY 2022 Inpatient Prospective Payment System (IPPS) Final Rule which includes several proposed changes to the Hospital Inpatient Quality Reporting (IQR) Program and Medicare Promoting Interoperability Program for eligible hospitals and critical access hospitals (CAHs). For the full text of the rule, see the Federal Register.

CMS recently published the CY 2022 Quality Payment Program (QPP) proposed rules which include many changes to the Merit Based Incentive Payment System (MIPS) for 2022 and subsequent reporting years. The full text of the rule can be viewed on the Federal Register.

In part 1 of this blog, we covered at a high level the basics of T-SQL user defined functions. In part 2 we’ll explore the advantages of leveraging functions, and when to do so.

I recently had a student from one of our online training sessions email me a few days after class, asking why I recommend always using the SourceID column as part of every TSQL join. They sent two queries to demonstrate why they felt they shouldn’t use SourceID.

CMS recently published the FY 2022 Inpatient Prospective Payment System (IPPS) Proposed Rule which includes several proposed changes to the Hospital Inpatient Quality Reporting (IQR) Program and Medicare Promoting Interoperability Program for eligible hospitals and critical access hospitals (CAHs). For the full text of the rule, see the Federal Register.

So, in plain English, what is a T-SQL user-defined function? A function is a SQL query saved as a database object, which leverages and outputs data to serve a focused purpose. Once a function is created it easily can be utilized at any time by anyone with proper access. Measured creation and execution of functions will greatly streamline data production from your T-SQL environment, allowing technology to do what it’s supposed to - make our lives easier! Let’s start with a simple example to better explain why we should be using functions and illustrate different types.

Background

Anderson Healthcare has served the Illinois communities of Madison and Macoupin counties since 1977 and continues its commitment to providing residents with the highest quality of advanced medical care. A 154-bed inpatient hospital, critical access hospital, rehab institute, surgery center and outpatient acute care facility offer patients cutting-edge medical diagnostics that are not often found in a local community setting using the MEDITECH Expanse electronic health record platform.