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.

y the <strong>certification</strong> criteria for a Complete EHR. In other words, we would call HIT<br />

tested and certified to one <strong>certification</strong> criterion an “EHR Module” and HIT tested and<br />

certified to nine <strong>certification</strong> criteria an “EHR Module,” where ten <strong>certification</strong> criteria<br />

are required for a Complete EHR. We have not made any changes to the definition <strong>of</strong><br />

EHR Module as a result <strong>of</strong> these comments or the comments addressed below.<br />

Comment. One commenter asked whether we meant to include in the definition<br />

<strong>of</strong> EHR Module “interfaces” that perform data mapping or transformation. The<br />

commenter raised this question while noting that some organizations use multiple<br />

interfaces to interconnect their HIT systems and that it would be an arduous task for these<br />

organizations to ensure that all individual interfaces are certified. Another commenter<br />

sought clarification regarding what we meant when we stated as an example in the<br />

Interim Final Rule that EHR Modules could be “an interface or other s<strong>of</strong>tware program<br />

that provides the capability to exchange electronic health information.”<br />

Response. As discussed above, to meet the definition <strong>of</strong> EHR Module, HIT<br />

would need to provide a capability that could be tested and certified to at least one<br />

<strong>certification</strong> criterion. If a <strong>certification</strong> criterion has therefore been adopted that requires<br />

a particular capability for exchanging electronic health information, an interface or other<br />

s<strong>of</strong>tware program that provides that capability could be tested and certified as an EHR<br />

Module. In many circumstances, an interface or program may provide valuable<br />

functionality, but not a capability for which a <strong>certification</strong> criterion has been adopted.<br />

For example, s<strong>of</strong>tware implemented by an eligible pr<strong>of</strong>essional that performs data<br />

translation or mapping between two databases or data sets may provide critical<br />

functionality, yet that s<strong>of</strong>tware would not constitute an EHR Module. Similarly,<br />

Page 27 <strong>of</strong> 228

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

Saved successfully!

Ooh no, something went wrong!