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.

Interim Final Rule’s preamble that discussed our approach to minimum code set<br />

standards.<br />

“We have implemented this approach by preceding references to specific adopted<br />

standards with the phrase, ‘at a minimum.’ In those instances, the <strong>certification</strong><br />

criterion requires compliance with the version <strong>of</strong> the code set that has been<br />

adopted through incorporation by reference, or any subsequently released version<br />

<strong>of</strong> the code set. This approach will permit Complete EHRs and EHR Modules to<br />

be tested and certified, to, ‘at a minimum,’ the version <strong>of</strong> the standard that has<br />

been adopted or a more current or subsequently released version.”<br />

We would note that consistent with this approach the Secretary has proactively<br />

identified and deemed acceptable newer versions <strong>of</strong> the following adopted “minimum<br />

standard” code sets:<br />

1) LOINC version 2.3, released on February 26, 2010; and<br />

2) CVX – Vaccines Administered, March 17, 2010.<br />

We are consequently using this opportunity to inform Complete EHR and EHR<br />

Module developers, prospective ONC-Authorized Testing and Certification Bodies, and<br />

the rest <strong>of</strong> the public <strong>of</strong> the Secretary’s recognition <strong>of</strong> these newer versions <strong>of</strong> certain<br />

adopted “minimum standard” code sets. We reiterate that use <strong>of</strong> these newer versions is<br />

voluntary. We also note in accordance with 45 CFR 170.455(b)(2) that Certified EHR<br />

Technology may be upgraded to comply with these newer versions at any time without<br />

adversely affecting the <strong>certification</strong> status <strong>of</strong> the Certified EHR Technology.<br />

• Optional Standards, Implementation Specifications, and Certification Criteria.<br />

We believe that additional flexibility and specificity can be introduced into this<br />

and future cycles <strong>of</strong> rulemaking through the adoption and designation <strong>of</strong><br />

“optional” standards, implementation specifications, and <strong>certification</strong> criteria.<br />

Optional standards, implementation specifications, and <strong>certification</strong> criteria would<br />

Page 40 <strong>of</strong> 228

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

Saved successfully!

Ooh no, something went wrong!