Certified Technology
Certification Seals
These are the current seals being use on certified technology by the ACTBs.
Read our posts on some history and identifying seals.
2014 Edition Certification
On September 4, 2012 the ONC issued the Health Information Technology: Standards, Implementation Specifications, and Certification Criteria for Electronic Health Record Technology, 2014 Edition; Revisions to the Permanent Certification Program for Health Information Technology Final Rule. The rule has changed the name of the Permanent Certification Program to the ONC HIT Certification Program. The ONC HIT Certification Program became fully operational on October 4, 2012. ONC will continue to manage the overall program. The 2014 Edition Test Method was formally approved by the ONC on December 14, 2012 and is now effective for use in the ONC HIT Certification Program. The notice was published in the Federal Register on Jan. 2, 2013.
Permanent Certification Program
On January 3, 2011 the ONC issued the Final Rule to establish the permanent certification program for health information technology. The rule was officially published in the Federal Register on January 7, 2011.
Temporary Certification Program
On June 18, 2010 the ONC issued Final Rule to Establish the Temporary Certification Program for Electronic Health Record Technology. The rules were officially published in the Federal Register on June 24th. While this Final Rule comes from the ONC’s previous Notice of Proposed Rulemaking (NPRM) it only covers the Temporary Certification program. The IFR for the permanent program is expected by the end of the year.
Certified Products
On October 1st the first products were certified by ONC-ATCBs. Complete products lists can be view on the ONC or ATCB web sites.
- ONC Certified HIT Product List (CHPL)
- CCHIT (Certification Commission For Health Information Technology)
- Drummond Group
- InfoGard
- ICSA Labs
- SLI Global Solutions
- Surescripts
Certification Numbers
During attestation, CMS requires each eligible professional, eligible hospital and critical access hospital to provide a CMS EHR Certification Number that identifies the certified EHR technology being used to demonstrate meaningful use. This unique CMS EHR Certification Number can be obtained by entering the certified EHR technology product information in the Certified Health IT Product List (CHPL) on the ONC website. Only a CMS EHR Certification Number obtained through the CHPL will be accepted at attestation.
Steps to obtain a CMS EHR Certification Number:
- Go to the ONC CHPL website: http://healthit.hhs.gov/chpl
- Select your practice type by selecting the Ambulatory or Inpatient buttons.
- Search for EHR Products by browsing all products, searching by product name or searching by criteria met.
- Add product(s) to your cart to determine if your product(s) meet 100% of the CMS required criteria.
- Request a CMS EHR Certification Number for CMS attestation.
NOTE: The “Get CMS EHR Certification ID” button will not be activated until the products in your cart meet 100% of the CMS required criteria. If the EHR product(s) do not meet 100% of the CMS required criteria to demonstrate Meaningful Use, a CMS EHR Certification ID will not be issued.
6.The CMS EHR Certification ID contains 15 alphanumeric characters.
Resource Links
- Final Rule for the Establishment of the Permanent Certification Program for Health Information Technology
- Proposed Rule for the Proposed Establishment of Certification Programs for Health Information Technology – Federal Register Vol 75, Page 11327
- Final Rule for the Establishment of the Temporary Certification Program for HIT – Federal Register Vol 75, Page 36157
- HHS and ONC Press Release
- ONC-ATCB page on ONC site
- More information on ATCBs on HITECH Answers
- ONC’s Certification Program page
- NIST Test Method for Health Information Technology: Initial Set of Standards, Implementation Specifications,and Certification Criteria for EHR Technology (45 CFR Part 170 Subpart C)
- NIST Approved Test Procedures Version 1.1









Providers working towards HIE and interoperability face the challenge of bringing connectivity to scale to take advantage of the data being generated by EHR adoption. This paper seeks to demonstrate that connectivity at scale can be accomplished. 









Connect With Us