ehr onc final certification - Department of Health Care Services

ehr onc final certification - Department of Health Care Services ehr onc final certification - Department of Health Care Services

dhss.alaska.gov
from dhss.alaska.gov More from this publisher
10.08.2013 Views

Architecture (QRDA) and the PQRI XML Registry specification in this rulemaking and move to a single standard in the next rulemaking. Other commenters recommended that QRDA not be adopted in this rulemaking. Several commenters suggested that an implementation specification for eligible hospitals be created if we intend to continue to require that quality measure be reported in the PQRI Registry XML format. One commenter expressed a concern that if the PQRI 2008 Registry XML standard is maintained as the adopted standard that there is a danger that the certification Complete EHR and EHR Module developers obtain may become obsolete before Stage 1 has run its course. Finally, a couple of commenters suggested that ONC consider deferring the naming of a standard for submission of clinical quality measures until Stage 2 and instead only require what is necessary to support clinical quality measure submission in Stage 1. Response. Many commenters misinterpreted our intent with respect to the adoption of the PQRI 2008 Registry XML specification as the standard for electronically submitting quality reporting data to CMS. Presently, CMS requires the submission of aggregate, summary level data for the purposes of meaningful use and not data at the patient-specific level. It is our understanding that the PQRI 2008 Registry XML specification is capable of serving as the “envelope” for aggregate, summary level data. Accordingly, we do not believe that, as some commenters suggested, an eligible hospital’s familiarity with the PQRI program is relevant to the adoption of this standard for this specified purpose. Nor do we believe that a specific implementation of this standard is necessary for hospital settings as the standard’s purpose and the type of data it will transmit to CMS will be the same – aggregate, summary level data. Through recent discussions with CMS since the publication of the Interim Final Rule we have determined Page 78 of 228

that the PQRI 2009 Registry XML specification, a more recent version of the standards we adopted in the Interim Final Rule is a suitable replacement for 2008 version, and accordingly, we have adopted the 2009 version in its place. We believe this revision should assuage some commenters’ concerns about the obsolescence of the adopted standard and reduce concerns that a wholly different standard would be adopted in the near future. If adopting a different standard for Certified EHR Technology becomes necessary, we would do so only after engaging in subsequent rulemaking. Comments. A few commenters stated that many of the clinical quality measures proposed by CMS do not have electronic specifications and contended that it would be difficult for any vendor to have embedded these measures in their EHR products in a timely manner. But, these same commenters stated that when the specifications become available, that HHS should ensure through the certification process that the products are capable of generating accurate data. Many commenters expressed concerns that the certification criterion was too vague or too broad (because it implicitly referenced all of the quality measures CMS had proposed). Some of the commenters recommended that this certification criterion be removed, while others recommended that it focus on a subset of measures in order to constrain the amount of electronic measure specifications a Complete EHR or EHR Module developer would need to address in order to be certified. At least one of these latter commenters indicated that our adopted certification criteria created uncertainty for Complete EHR and EHR Module Developers. This commenter asked that we clarify what clinical quality measures would need to be tested in order to satisfy this certification criterion and if there would be a baseline for eligible hospital measures as well as some identified core set of measures for eligible professionals. Page 79 of 228

Architecture (QRDA) and the PQRI XML Registry specification in this rulemaking and<br />

move to a single standard in the next rulemaking. Other commenters recommended that<br />

QRDA not be adopted in this rulemaking. Several commenters suggested that an<br />

implementation specification for eligible hospitals be created if we intend to continue to<br />

require that quality measure be reported in the PQRI Registry XML format. One<br />

commenter expressed a c<strong>onc</strong>ern that if the PQRI 2008 Registry XML standard is<br />

maintained as the adopted standard that there is a danger that the <strong>certification</strong> Complete<br />

EHR and EHR Module developers obtain may become obsolete before Stage 1 has run its<br />

course. Finally, a couple <strong>of</strong> commenters suggested that ONC consider deferring the<br />

naming <strong>of</strong> a standard for submission <strong>of</strong> clinical quality measures until Stage 2 and instead<br />

only require what is necessary to support clinical quality measure submission in Stage 1.<br />

Response. Many commenters misinterpreted our intent with respect to the<br />

adoption <strong>of</strong> the PQRI 2008 Registry XML specification as the standard for electronically<br />

submitting quality reporting data to CMS. Presently, CMS requires the submission <strong>of</strong><br />

aggregate, summary level data for the purposes <strong>of</strong> meaningful use and not data at the<br />

patient-specific level. It is our understanding that the PQRI 2008 Registry XML<br />

specification is capable <strong>of</strong> serving as the “envelope” for aggregate, summary level data.<br />

Accordingly, we do not believe that, as some commenters suggested, an eligible<br />

hospital’s familiarity with the PQRI program is relevant to the adoption <strong>of</strong> this standard<br />

for this specified purpose. Nor do we believe that a specific implementation <strong>of</strong> this<br />

standard is necessary for hospital settings as the standard’s purpose and the type <strong>of</strong> data it<br />

will transmit to CMS will be the same – aggregate, summary level data. Through recent<br />

discussions with CMS since the publication <strong>of</strong> the Interim Final Rule we have determined<br />

Page 78 <strong>of</strong> 228

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!