Ok, was that enough abbreviations in the title of a post? Well, if you care about this post, you’ll probably recognize all of the abbreviations.
In a post I did on EMR and HIPAA about SureScripts as an ePrescribing ATCB, there was a comment made that possibly some of the ATCB were “in bed” with ONC in order to get their EHR certification body status. In response to the comment, Mark Joyce from SLI Global Solutions (an ATCB) provided some good insight into the process and costs associated with becoming an ATCB that can certify EHR software.
As the team lead for SLI’s application to the ONC I can assure you that our company has no political connections, traded favors or made contributions that won us our certification by the ONC. It was 10 weeks of grueling research by two independent companies (one company focusing on testing and the other certification) that resulted in a 1200 page application.
The application was in two parts: part one required both companies to expand and/or create a Quality Management System for the new process. It’s no easy task to develop both a 17025 and a Guide 65 conformant QMS. Part two required the applicant to have a thorough understanding of EHR architectures as well the NIST testing procedures and tools.
It was evident by the followup questions from the ONC that the application had been very carefully reviewed.
Obtaining certification from the ONC was no easy task. I am proud to be a part of our companies significant investment in the ATCB testing and certification process.
Yes, becoming an ONC-ATCB is definitely not a walk in the park to achieve. Anyone that says otherwise, likely hasn’t ever been through the process.