Showing posts with label cypress. Show all posts
Showing posts with label cypress. Show all posts

June 4, 2013

The Four Different Types of Clinical Quality Measures

Clinical Quality Measures (CQMs) have been a significant part of my work for the past 3 years.  My first foray into the CQM space was with the popHealth project, which is a reference implementation of the CQM logic that a provider or EHR vendor could use or incorporate into a software project.  popHealth was entirely focused on a family of CQMs called "proportion-based".

While the "proportion-based" CQMs get the majority of the attention with the healthcare community, it was not until a year working on popHealth that I discovered that there are a total of four different types of CQMs that affect how the CQM logic is implemented and reported.

The four different classifications of CQM logic are:

Proportion

  • This is the type of CQM that most individuals are familiar with when referring to the Meaningful Use program.  
  • These types of CQMs are routinely referred to as the "Numerator/Denominator" CQMs.  I recently wrote about the exception and exclusion logic, but it is worth noting that those CQM reporting characteristics are only applied to proportion-based CQMs.
  • Usually, the proportion-based CQMs are a positive measurement of quality, meaning that usually, the higher the value of the Numerator/Denominator proportion, the better you are doing as a healthcare provider
  • Example: "What percentage of women over the age of 45 and under the age of 65, who have had an outpatient encounter in the past 2 years, have had a mammography screening?"

Continuous Variable

  • These CQMs are usually applied in the hospital CQM domain.  
  • These types of CQMs measure the average time 
  • Example: "What is the average time for Emergency Department (ED) admission until either Discharge or Admission to Inpatient Hospitalization?"

Episode of Care 

  • These CQMs assess each distinct ‘encounter’ between a patient and a provider, during a a measurement period.
  • A single patient can contribute to numerous considerations of the CQM result if they had numerous encounters
  • Examples: "Did the provider measure the patient’s blood pressure during a particular episode?" or "Were heart attack patients discharged with an Rx for Aspirin during a particular episode?"

Longitudinal

  • These CQMs take into account complete patient record with focus on a ‘measurement period’
  • Examples: "Have patients who turned 2 years old during the measurement period received all required vaccinations on schedule?" or "Have diabetic patients received 2 foot exams during the measurement period?"


This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. © Rob McCready, 2013.
Creative Commons License

May 24, 2013

Meaningful Use Stage 2 XML Standards for Clinical Quality Measure Reporting

When implementing an EHR system, or EHR module, that supports the Meaningful Use Stage 2 program for Clinical Quality Measure (CQM) support, there are three HL7 XML standards that you need to be aware of:

  • HQMF
  • QRDA Category 1
  • QRDA Category 3 

The HQMF XML standard defines the data elements referenced by the logic, and associates them to value sets using object identifiers (OIDs).  For those really interested in using the HQMF, you can download the HQMF files for all the Meaningful Use Stage 2 Clinical Quality Measures from the CMS site here.

The QRDA Category 1 XML standard is what is used for expressing patient-level data as inputs to a Clinical Quality Measure calculator, such as popHealth, as part of the Meaningful Use Stage 2 program.  This XML standard allows for EHRs to express the clinical results of individual patients based on the CQM that an EHR system was queried about.  The reports that determine the data to include in the QRDA Category 1 XML are tightly coupled to the HQMF definition of the measure.  I have shared high-level information about the QRDA Category 1 specification, as well as an example of what the QRDA Category 1 XML should look like.

Lastly, the QRDA Category 3 XML standard is what is used to express the summary results of a CQM.  It is unfortunate that the QRDA Category 1 and Category 3 are worded so similarly, yet have significantly different roles in this landscape.  The QRDA Category 3 is the artifact that needs to be generated for expressing summary/aggregate report numbers.  For instance, if the CQM report where created to assess the mammography screening results of women between the ages of 45 and 65 years old, and the result were 73% of that population met that criteria, the QRDA Category 3 XML could express the 73% performance rate, as well as counts associated with the initial patient population, the denominator, the numerator , the exception, and exclusion populations.  You can view an illustration of these different CQM logical families for the proportion-based CQMs here.

Below is an illustration that details the use of these various HL7 XML standards when reporting on Meaningful Use Stage 2 Clinical Quality Measures.
Landscape of Meaningful Use Stage 2 Clinical Quality Measure XML Standards
Landscape of Meaningful Use Stage 2 Clinical Quality Measure XML Standards

Hopefully this is helpful.  If not, let me know!

This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. © Rob McCready, 2013.
Creative Commons License

May 17, 2013

Designing Logos for a Portfolio of Healthcare Projects

Over the past three years, I have been involved with numerous open source healthcare projects, ranging from large reference implementations of Clinical Quality Measures, certification and testing tools adopted by the federal government, a small research project assessing CQM complexity/cost/tractability, this blog, and other ideas that failed to launch.

What I have been endorsing throughout the course of the past three years has been to establish a common "brand" that could be applied to various open source healthcare projects, but still provide a unique look and feel for each individual project.  

The design approach that organically evolved was to develop logos followed the following rules:
  • Use only circles
  • The circles may come in different sizes and arrangements
  • Limiting the logos to a pallet of only two colors
  • Color opacity could be changed
You can see the portfolio of these project logos below:
Portfolio of logos for open source healthcare projects I have worked on
Portfolio of logos for open source healthcare projects I have worked on
Since I am a "left brain" engineer at heart, the various arrangements of the circles has been an easier task than color selection.  I have often struggled with finding the magic combination of colors for anything from these logos to our interior design of our hours.

The best resource that I have found been able to identify is ColorLovers.com.  For those not familiar with the site, it is an evolving resource for palettes and colors that users can share, rank and comment on.

When I had to select to colors, I went to the filter for "most loved" colors of all time, and tried to identify pallets where instead of 5 colors, there were 2 colors used in the pallet.  Hopefully this is a helpful trick.

This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. © Rob McCready, 2013.
Creative Commons License