Ankit Kumar Agarwal
Ankit Kumar agarwal is a Wharton Graduate and working as “Director of IT” with NewWave Telecom and Technologies Inc. Ankit is passionate about bringing impactful changes in people’s life and writes blogs to educate people and promote digital Health.
What is G10
ONC G10 refers to the “G10 Health IT Modules and Their Interfaces” project, which is a project funded by the Office of the National Coordinator for Health Information Technology (ONC). The project aims to develop a set of standardized health IT modules and their interfaces, with the goal of improving interoperability and the exchange of electronic health information.
The ONC G10 project is focused on developing a set of modular, interoperable health IT components that can be used to build and deploy health IT systems, such as electronic health records (EHRs) and health information exchanges (HIEs). The project is intended to provide a foundation for the development of interoperable health IT systems, and it is designed to be flexible and scalable so that it can be adapted to meet the needs of different organizations and systems.
Overall, the ONC G10 project is a key initiative aimed at improving interoperability and the exchange of electronic health information, and it is expected to have a significant impact on the development and deployment of health IT systems.
ONC G10 Certification
The ONC Certification (g)(10) Standardized API Test Kit is a testing tool for Health Level 7 (HL7®) Fast Healthcare Interoperability Resources (FHIR®) services seeking to meet the requirements of the Standardized API for Patient and Population Services criterion § 170.315(g)(10) in the 2015 Edition Cures Update.
G10 Certification Requirements
Privacy and Security: This certification criterion was adopted in § 170.315(g)(10). As a result, an ONC Authorized Certification Body (ONC-ACB) must ensure that a product presented for certification to this criterion includes the privacy and security criteria (adopted in § 170.315(d)) within the overall scope of the certificate issued to the product.
- The privacy and security criteria (adopted in § 170.315(d)) do not need to be explicitly tested with this specific criterion unless it is the only criterion for which certification is requested.
- As a general rule, a product presented for certification only needs to be tested once to each applicable privacy and security criterion (adopted in § 170.315(d)) so long as the health IT developer attests that such privacy and security capabilities apply to the full scope of capabilities included in the requested certification.
Design and Performance: The following design and performance certification criteria (adopted in § 170.315(g)) must also be certified in order for the product to be certified.
- When a single quality management system (QMS) is used, the QMS only needs to be identified once. Otherwise, when different QMS are used, each QMS needs to be separately identified for every capability to which it was applied.
- When a single accessibility-centered design standard is used, the standard only needs to be identified once. Otherwise, the accessibility-centered design standards need to be identified for every capability to which they were applied; or, alternatively, the developer must state that no accessibility-centered design was used.
G10 Certification Component
Some of the key components of the G10 Certification include:
- Standalone Patient App – Full Access
- SMART on FHIR Discovery
- Standalone Launch with Patient Scope
- OpenID Connect
- Token Refresh
- Unrestricted Resource Type Access
Path to G10 Certification
Healthcare organizations can either use Drummond’s ONC-approved G10 FHIR API+ certification program giving FHIR implementers comprehensive development, testing and certification tools to meet ONC and CMS FHIR requirements and recommendations or they can use Inferno G10 FHIR API Certification tool kit. Both of these options have its Pros and Cons and each entity has to decide their path forward accordingly based on their priorities.
*This article is Peer Reviewed by the Distilinfo Editorial team prior to the publication.*
