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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

longitudinal care, or whether the EHR Module could be designed to provide those<br />

capabilities through its interaction with a device or devices at the enterprise level).<br />

Comment. One comment stated that this criterion should include a provision to<br />

include the ability to transmit this information to public health entities as required by law.<br />

Response. Nothing we adopt in this <strong>final</strong> rule precludes such a capability from<br />

being included in a Complete EHR or EHR Module. That is not, however, currently a<br />

necessary requirement for <strong>certification</strong>.<br />

Comments. One commenter stated that it would need to perform extensive<br />

reprogramming to accommodate the standard we adopted if it meant modifying<br />

underlying medication databases. This commenter suggested that this standard as it<br />

applied to the maintenance <strong>of</strong> medication lists be deferred. Along those lines, a couple <strong>of</strong><br />

commenters stated that more clarification was needed with respect to whether RxNorm<br />

identifiers needed to be stored internally within Certified EHR Technology or only<br />

needed to be used upon the electronic exchange <strong>of</strong> health information. Other commenters<br />

expressly stated that the mapping <strong>of</strong> the vocabulary be limited to instances where the<br />

electronic exchange <strong>of</strong> health information would take place.<br />

Response. We understand these commenters’ c<strong>onc</strong>erns and agree that it would be<br />

premature to require the use <strong>of</strong> the adopted standard in this context. In that regard, we<br />

seek to clarify for commenters our intention, which was solely to associate this adopted<br />

standard (as some commenters suggested) with the <strong>certification</strong> criteria that require the<br />

capability to electronically exchange health information. We recognize that continuing to<br />

associate this standard with the adopted <strong>certification</strong> criterion could potentially impose a<br />

significant burden on the industry, which we did not intend. Accordingly, we have<br />

Page 59 <strong>of</strong> 228

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

Saved successfully!

Ooh no, something went wrong!