adam121 - Fotolia

Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

Voluntary ONC certification requires API-related access

APIs are useful in improving EHR interoperability. From that perspective, electronic medical records that are certified by the ONC must adhere to API criteria.

This article can also be found in the Premium Editorial Download: Pulse: APIs and the cloud help cure health IT interoperability ills:

Uncle Sam wants you to use APIs in healthcare. Doing so would make you a patriot, an All-American and a more effective health IT professional.

The U.S. Office of the National Coordinator for Health IT (ONC) oversees a voluntary certification program for electronic health record (EHR) technology, conducted through third-party evaluators. As part of ONC certification for EHR systems, any APIs used in that technology must provide application- or consumer-level access to the Common Clinical Data Set, a list that includes basic patient information -- such as name, medications and lab results. The ONC certification provisions set baseline requirements for certified healthcare providers and vendors regarding access to various data requests via APIs.

APIs are in the spotlight for their ability to promote interoperability among EHRs. Our September issue of Pulse examines how APIs blend with interoperability, and we also delve into how cloud-based EHRs might have an advantage over on-premises systems, as hospitals push for greater data exchange among EHR vendors.

At the end of the interoperability rainbow is the notion that once EHRs can exchange clinical information with each other, we're one step closer to having a healthcare system that serves patients whether for a routine visit at their hometown physician's office or for an unexpected trip to an emergency room while traveling cross-country on vacation.

Though voluntary, ONC certification is a serious undertaking for vendors. Failure to live up to certification conditions can result in expensive fines.

Earlier this year, EHR seller EClinicalWorks entered into a False Claims Act settlement with the U.S. Department of Justice over allegations that the company's software did not meet criteria for a certified EHR, according to the government. The settlement cost EClinicalWorks $155 million in penalties, although the vendor admitted no wrongdoing. The case is extreme but still worth noting, as the Department of Justice takes a closer look at potential healthcare fraud.

With that in mind, developers seeking certification for APIs must submit full documentation to ONC, including programming information and syntax. Those are marching orders we can all salute.

Next Steps

Donald Rucker named new national coordinator for health IT

Information blocking plays a big part in interoperability pitfalls

ONC tweaks its interoperability plans

This was last published in September 2017

Dig Deeper on Electronic health record system (EHR) certification

PRO+

Content

Find more PRO+ content and other member only offers, here.

Join the conversation

1 comment

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

If your company has undergone ONC certification, how difficult was the process?
Cancel

-ADS BY GOOGLE

SearchCompliance

SearchCIO

SearchCloudComputing

SearchMobileComputing

SearchSecurity

SearchStorage

Close