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.

commenters reasoned that because a Complete EHR or EHR Module must be tested and<br />

certified to be in compliance with 42 CFR 493.1291(c)(1) through (7) that <strong>certification</strong><br />

should replace any requirement for the laboratory to confirm that the information has<br />

been properly transmitted and meets the CLIA requirements. These commenters also<br />

asserted that a laboratory should be relieved <strong>of</strong> any further regulatory responsibility under<br />

42 CFR 493.1291(c)(1) through (7) for the display <strong>of</strong> the required report information to<br />

the physician or subsequent viewers <strong>of</strong> the information if the Certified EHR Technology<br />

has been implemented by an eligible pr<strong>of</strong>essional or eligible hospital. One commenter<br />

reiterated the point by stating that because Certified EHR Technology would be required<br />

to display the required CLIA report elements, laboratories should not be unfairly held<br />

accountable for any elements that may be removed or altered by other parties from the<br />

test report before received by the physician.<br />

Response. While we can understand the c<strong>onc</strong>ern expressed by these commenters,<br />

we reiterate that the scope <strong>of</strong> our authority under this <strong>final</strong> rule only applies to<br />

capabilities that Certified EHR Technology must include. As a result, we cannot provide<br />

the regulatory relief that these commenters seek.<br />

Comments on 170.302(g)(4)<br />

Comments. A couple <strong>of</strong> commenters questioned whether we intended for the<br />

“updates” to be manual updates <strong>of</strong> electronic records. If that were true, some<br />

commenters were c<strong>onc</strong>erned that would create workflow problems and reduce the<br />

availability <strong>of</strong> results. Other commenters suggested that either the user be able to create<br />

an additional record, rather than be permitted to change the “<strong>of</strong>ficial” record or that an<br />

adequate audit trail be preserved <strong>of</strong> the existing data and any updates, since an update<br />

Page 71 <strong>of</strong> 228

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

Saved successfully!

Ooh no, something went wrong!