10.08.2013 Views

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

that the PQRI 2009 Registry XML specification, a more recent version <strong>of</strong> the standards<br />

we adopted in the Interim Final Rule is a suitable replacement for 2008 version, and<br />

accordingly, we have adopted the 2009 version in its place. We believe this revision<br />

should assuage some commenters’ c<strong>onc</strong>erns about the obsolescence <strong>of</strong> the adopted<br />

standard and reduce c<strong>onc</strong>erns that a wholly different standard would be adopted in the<br />

near future. If adopting a different standard for Certified EHR Technology becomes<br />

necessary, we would do so only after engaging in subsequent rulemaking.<br />

Comments. A few commenters stated that many <strong>of</strong> the clinical quality measures<br />

proposed by CMS do not have electronic specifications and contended that it would be<br />

difficult for any vendor to have embedded these measures in their EHR products in a<br />

timely manner. But, these same commenters stated that when the specifications become<br />

available, that HHS should ensure through the <strong>certification</strong> process that the products are<br />

capable <strong>of</strong> generating accurate data. Many commenters expressed c<strong>onc</strong>erns that the<br />

<strong>certification</strong> criterion was too vague or too broad (because it implicitly referenced all <strong>of</strong><br />

the quality measures CMS had proposed). Some <strong>of</strong> the commenters recommended that<br />

this <strong>certification</strong> criterion be removed, while others recommended that it focus on a<br />

subset <strong>of</strong> measures in order to constrain the amount <strong>of</strong> electronic measure specifications a<br />

Complete EHR or EHR Module developer would need to address in order to be certified.<br />

At least one <strong>of</strong> these latter commenters indicated that our adopted <strong>certification</strong> criteria<br />

created uncertainty for Complete EHR and EHR Module Developers. This commenter<br />

asked that we clarify what clinical quality measures would need to be tested in order to<br />

satisfy this <strong>certification</strong> criterion and if there would be a baseline for eligible hospital<br />

measures as well as some identified core set <strong>of</strong> measures for eligible pr<strong>of</strong>essionals.<br />

Page 79 <strong>of</strong> 228

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

Saved successfully!

Ooh no, something went wrong!