Difference between revisions of "Performance Quality Report"

From IHE Wiki
Jump to navigation Jump to search
Line 13: Line 13:
 
===Project Scope===
 
===Project Scope===
 
Three inpatient measure sets (Specification links above):
 
Three inpatient measure sets (Specification links above):
* Active Version of Stroke measures 1, 2, 3, 5, 8, and 10 as of 21 Nov 2008
+
*Active Version of Stroke measures 1, 2, 3, 5, 8, and 10 as of 21 Nov 2008
<br>("Missing” numbers have not been approved to be included in the measure set):
+
("Missing” numbers have not been approved to be included in the measure set):
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/STK%201%20(KK)%2011-20-08.doc STK-1]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/STK%201%20(KK)%2011-20-08.doc STK-1]
 
***
 
***
 
[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_1%20(5).pdf STK-1 Algorithm]
 
[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_1%20(5).pdf STK-1 Algorithm]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/STK%202%20(KK)%2011-17-08.doc STK-2]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/STK%202%20(KK)%2011-17-08.doc STK-2]
***
+
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_2%20(2).pdf STK-2 Algorithm]
[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_2%20(2).pdf STK-2 Algorithm]
 
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/STK%203%20(KK)%2011-17-08.doc STK-3]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/STK%203%20(KK)%2011-17-08.doc STK-3]
 
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_3%20(2).pdf STK-3 Algorithm]
 
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_3%20(2).pdf STK-3 Algorithm]
Line 28: Line 27:
 
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_8%20(2).pdf STK-8 Algorithm]
 
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_8%20(2).pdf STK-8 Algorithm]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/STK%2010%20%20(KK)%2011-20-08.doc STK-10]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/STK%2010%20%20(KK)%2011-20-08.doc STK-10]
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_10%20(2).pdf STK-10 Algorithm]<br>
+
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20Stroke%20Measures/Stk_10%20(2).pdf STK-10 Algorithm]
  
 
* Active versions of Venous Thromboembolism (VTE) Measures:
 
* Active versions of Venous Thromboembolism (VTE) Measures:
Line 42: Line 41:
 
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20VTE%20Measures/VTE-5.pdf VTE-5 Algorithm]
 
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20VTE%20Measures/VTE-5.pdf VTE-5 Algorithm]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20VTE%20Measures/VTE6_111208.doc VTE-6]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20VTE%20Measures/VTE6_111208.doc VTE-6]
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20VTE%20Measures/VTE-6.pdf VTE-6 Algorithm]<br>
+
***[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20VTE%20Measures/VTE-6.pdf VTE-6 Algorithm]
[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20VTE%20Measures/DD_111908REVised.doc VTE Specifications & Exclusions]
+
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20VTE%20Measures/DD_111908REVised.doc VTE Specifications & Exclusions]
  
* Active Versions of Emergency Department (ED) Measures<br>
+
* Active Versions of Emergency Department (ED) Measures
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20ED%20Measures/ed-1%20measure.pdf ED-1]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20ED%20Measures/ed-1%20measure.pdf ED-1]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20ED%20Measures/ed-2%20measure.pdf ED-2]
 
**[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Performance%20Quality%20Report%20Documents/Draft%20ED%20Measures/ed-2%20measure.pdf ED-2]

Revision as of 16:33, 8 December 2008

Current work

Performance Quality Report Detailed Profile Proposal
Schema to Represent Measure Specifications
Health Quality Measures Format (HQMF) Reference Guide
Health Quality Measure Format (HQMF) Issues Log

Discussion on various sections and comments, tasks

Conference Call
Topic: QRPH Tech: Discussion, Performance Quality Report Profile
Date: Friday, December 5, 2008
Time: 2:00 PM, Central Standard Time

Project Scope

Three inpatient measure sets (Specification links above):

  • Active Version of Stroke measures 1, 2, 3, 5, 8, and 10 as of 21 Nov 2008

("Missing” numbers have not been approved to be included in the measure set):

STK-1 Algorithm

Project Facts and Proposals per December 5, 2008 Discussion

  1. The current measures are endorsed by the National Quality Forum (NQF). The Joint Commission updates their measures every six months and the next update is due for publication in March (or at least submission for publication). Therefore, work on the ‘current’ measures will be outdated somewhat by publication. We should use the most updated version.
  2. Many of the data elements in the measures will require judgment calls with respect to whether EHR-available data are useful and sufficient to express the intent of the element and the context intended by the measure developer. For the output of the effort to have a specified measure that has the same meaning as the manual version, measure developers must participate. Patty Craig represents The Joint Commission and is seeking an additional resource from the measure development area. The Oklahoma Foundation for Medical Care (OFMC) is a partner in the measure development and a request for their participation is in progress.
  3. Some of the data elements in the measures will not have clear EHR or electronic codified data concepts. To accommodate such items, we propose that the measure specification be included as content within a Retrieve Form for Data Capture (RFD – an ITI Profile) as output of a Form Manager. The EHRs, as Form Receivers, will auto fill what is possible and enable human filling of information not in codified standard form. The completed form can be returned then as a constrained structured document (i.e., QRDA with Schematron testing). This last (return) step requires further analysis with respect to scope.
  4. The project will encode a measure within an existing structure. Inclusion of the implementation in an EHR which and subsequent production of a patient-level aggregate patient report using HL7 Quality Reporting Document Architecture (QRDA) is part of the roadmap but potentially out of scope for this Performance Quality Report Profile in 2009. Since QRDA is a draft standard for trial use (DSTU) in HL7, a profile may not be necessary for testing and such testing can occur in the US domain through the Healthcare Information Technology Standards Panel <HITSP>. HITSP expects to use a patient-level QRDA report (Category I). To be determined is the extent to which an aggregate report (Categories II and III) will be used. Note that QRDA includes schematron rules so that in such testing the completeness, terminology and structure of the QRDA can be validated before submission to an external performance monitoring organization.
  5. Successful final output is a fully specified measure set (3 of them) in electronic format that can be used by an EHR, an HIE, or some coordinator of clinical and administrative data. A statistical analysis step would help to validate that the calculated aggregate results are the same or better than the data currently submitted using manual processes.

Next Steps

  • IHE QRPH Planning / Technical Committee Call Dec 22, 2008 to determine final go-forward status for profiles and white papers.

Previous work (versions)

Related materials