Performance Measurement Data Element Structured for EHR Extraction: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
FEisenberg (talk | contribs)
No edit summary
FEisenberg (talk | contribs)
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:
'''White paper:  Performance Measurement Data Element Structured for EHR Extraction'''
'''White paper:  Performance Measurement Data Element Structured for EHR Extraction'''
<br>
<br>
* [ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/2_JUN_2008_IHE_QRPH_White_Paper_version15.doc June 2, 2008] --- clean, edited version June 2, 2008 with few edits pending for June 3, 2008
* Tuesday, July 22, comment resolution was completed.  Detailed comments are located at:
 
** Comments and resolution: [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/ihe_qrph_public_comment_July_2008%255B1%255D%5B1%5D.doc Comment resolution]
** Clean version: [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/CLEAN%20IHE_QRPH_Whitepaper_Perfomance_Measure_Data_Element_Structured_for_EHR_Extraction_2008-07-22_Comment_resolution.doc White Paper]
** Track changes version: [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/COMMENT%20IHE_QRPH_Whitepaper_Perfomance_Measure_Data_Element_Structured_for_EHR_Extraction_2008-07-22_Comment_resolution.doc Track Changes Version]


==Discussion on various sections and comments, tasks==
==Discussion on various sections and comments, tasks==
* 18 June 2008 [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/Public%20Comment/IHE_QRPH_Whitepaper_Perfomance_Measure_Data_Element_Structured_for_EHR_Extraction_2008-06-1108-06-06.pdf Version 1.0 for Public Comment]
* 14 May 2008 [[QRPH_Technical_Committee_Minutes_2008-05-14]]
* 14 May 2008 [[QRPH_Technical_Committee_Minutes_2008-05-14]]
* 1 May 2008 [[QRPH_Technical_Committee_Minutes_2008-05-01]]
* 1 May 2008 [[QRPH_Technical_Committee_Minutes_2008-05-01]]
Line 12: Line 15:


==Previous work (versions)==
==Previous work (versions)==
* [ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/30_5_2008_IHE_QRPH_White_Paper_version1%5B1%5D.doc May 30, 2008]  
* [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/2_JUN_2008_IHE_QRPH_White_Paper_version15.doc June 2, 2008]
* [ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/27_5_2008_IHE_QRPH_White_Paper_version1%5B1%5D.doc May 27, 2008]
* [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/30_5_2008_IHE_QRPH_White_Paper_version1%5B1%5D.doc May 30, 2008]
* [ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/21_5_2008_IHE_QRPH_White_Paper_version1%5B1%5D.doc May 21, 2008]
* [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/27_5_2008_IHE_QRPH_White_Paper_version1%5B1%5D.doc May 27, 2008]
* [ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/20_5_2008_IHE_QRPH_White_Paper.doc May 20, 2008]
* [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/21_5_2008_IHE_QRPH_White_Paper_version1%5B1%5D.doc May 21, 2008]
* [ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/18_5_2008_IHE_QRPH_White_Paper.doc May 17, 2008]
[ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/IHE_QRPH_White_Paper_Performance_Measure_Data_Element_Structured_for_EHR_Extraction_2008_04_26.doc April 26, 2008]  
*[ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/26_04_2008_IHE_QRPH_White_Paper_Performance_Measure_Data_Element_Structured_for_EHR_Extraction.doc April 26, 2008]
*[ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/IHE_QRPH_White_Paper_Performance_Measure_Data_Element_Structured_for_EHR_Extraction_2008_04_23.doc April 23, 2008]
* [ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/IHE_QRPH_White_Paper_Performance_Measure_Data_Element_Structured_for_EHR_Extraction_2008_04_22.doc April 22, 2008]
* [ftp://ftp.ihe.net/Quality/Technical_Comittee/2008/IHE_QRPH_White_Paper_Performance_Measure_Data_Element_Structured_for_EHR_Extraction_2008_04_03a.doc April 3, 2008]


==Related materials==
==Related materials==

Latest revision as of 11:37, 28 July 2008

Current work

White paper: Performance Measurement Data Element Structured for EHR Extraction

Discussion on various sections and comments, tasks

Previous work (versions)

April 26, 2008

Related materials

Comments from Vassil Peytchev on Collaborative for Performance Measure Integration with EHR Systems

  • The goal of the Collaborative is to create a standardized way to communicate performance measures using structured, encoded performance measure information, which can be also used within EHR applications.

There are three levels of performance measures representation:

  • Performance measure description
  • Performance measure template
  • Performance measure machine processable information

This holds a resemblance to the levels of a CDA document:

  • Level 1 - Unstructured text
  • Level 2 - Structured text
  • Level 3 - Discrete data

The CDA is patient-centric, so it is not directly applicable here.

  • However, HL7 just published a draft for the SDA (Structured Document Architecture) which is not patient-centric, and can be directly applicable for this use. The Structured Document committee of HL7 is also working on a Quality Reporting Document Architecture (QRDA).
  • These intersecting activities strongly suggest that collaboration is the best way forward given the emphasis on HL7 CDA and CCD-based (and therefore HL7 V3 based) specifications throughout the US (HISTP, CCHIT), and internationally (IHE).

The Collaborative can consider the following notes about the Performance Measure Integration specifications:

  • The use of HL7 V3 data types when applicable. This will make the XML representation (of codes in particular)uniform across a variety of data exchange requirements.
  • Make use of the IHE processes. The IHE SVS profile, for example, will use a very similar structure to the CodeGroup and Code structure to represent contents of general value sets (using HL7 v3 datatypes).
  • Consider the use of the HL7 SDA as a basis for a performance measure description. This will allow for a future expandability of the format.
  • Reconsider the use of XML in the template for logical expressions.

A transformation of the XML content to a more readable form would be preferred.