Healthcare IT selection starts with defining how an organization will use the technology, not with comparing feature lists. The Office of the National Coordinator for Health Information Technology (ONC) states that organizations must determine their needs and goals before beginning the selection process [1]. This article explains how to use primary documentation—the Certified Health IT Product List, US Core FHIR implementation guidance, and SAFER Guides—to structure an evaluation. It focuses on concrete workflows and device-category distinctions rather than generic buying advice. A hypothetical evaluation example illustrates how a procurement team might apply these documents. The article does not provide patient advice, clinical efficacy conclusions, or a ranking of vendors. Unknowns are identified where the source material does not establish a fact.
Certification as a Baseline, Not a Differentiator
The ONC Health IT Certification Program confirms that certified health information technology meets technological capability, functionality, and security requirements adopted by the U.S. Department of Health and Human Services [5]. Developers certify Health IT Modules by demonstrating conformance to certification criteria using test procedures, tools, and data approved by the National Coordinator [5]. The Certified Health IT Product List (CHPL) is the comprehensive list of products successfully tested by an Accredited Testing Laboratory and certified by an ONC-Authorized Certification Body [1]. The CHPL User Guide describes how organizations can search for and compare health IT products and identify products that do not meet certification criteria [1].
Certification is a floor, not a ranking. Two products can both appear on the CHPL while differing in the specific modules certified, the criteria met, and the certification dates. The ONC also maintains ongoing Conditions and Maintenance of Certification requirements, meaning certification in a controlled testing environment does not automatically guarantee production behavior [5]. A procurement team should therefore treat CHPL presence as a screening step. The next stage is to examine which criteria a module actually satisfies and whether those criteria match the organization's defined use cases. The source material does not provide a method for scoring one certified product above another.
API Capability and the Standards-Based Distinction
Hospital API use is common but not uniform. A 2024 American Hospital Association IT Supplement analysis found that approximately 9 in 10 hospitals enabled patient access to health information via an API, unchanged from 2022, and increasingly via standards-based APIs [2]. However, most hospitals integrated data from and provided data to third-party technology for various clinical and administrative use cases mostly via non-standards-based approaches [2]. The ONC data brief notes that non-standards-based methods involve manual effort and limit automation of tasks [2].
The distinction matters for evaluation. The ONC requires the Health Level Seven (HL7) Fast Healthcare Interoperability Resources (FHIR) and ONC United States Core Data for Interoperability (USCDI) standards for the Standardized API for Patient and Population Services certification criterion [2]. Large, system-affiliated hospitals using a market-leading EHR more often reported use of standards-based APIs to enable patient access and patient generated health data submission [2]. A buyer should ask whether a product supports FHIR-based patient access or only proprietary interfaces. The data brief does not establish that standards-based APIs produce better clinical outcomes; it documents adoption patterns.
Checking API Capability in the CHPL
A procurement team can use the CHPL User Guide to search for certified modules and compare their certification criteria [1]. For API capability, the team should identify whether the module is certified to the Standardized API for Patient and Population Services criterion, which requires HL7 FHIR and USCDI standards [2]. The team can then request the module's US Core CapabilityStatement to verify which profiles and RESTful interactions are supported [3]. This documentation check does not replace live testing, but it narrows the field before a pilot.
US Core Profiles and the Two Implementation Modes
US Core establishes a floor of standards for patient data access. The implementation guide describes two ways to implement US Core: Profile Only Support, where systems support only the US Core Profiles to represent clinical information, and Profile Support plus Interaction Support, where systems support both the profile content structure and the RESTful interactions defined for a resource [3]. The guide uses the terms US Core Responder, Server, and EHR interchangeably, but states these are not meant to limit the actor to electronic health record systems; health information exchanges, care coordination platforms, and population health systems can use the same technology [3].
This device-category distinction is important for procurement. A care coordination platform that supports US Core profiles but not the full RESTful interaction set may be adequate for read-only data display but insufficient for bidirectional workflows. The US Core guide includes profiles for Condition, Coverage, Device, and DiagnosticReport, among others [3]. Each profile page documents required FHIR RESTful search and read operations [3]. An evaluation team can use these capability statements to test whether a product can perform the specific interactions the organization needs. The guide does not rank implementation modes by safety or quality.
SAFER Guides as Workflow Evaluation Tools
The 2025 SAFER Guides consist of eight guides organized into three groups: Foundational Guides, Infrastructure Guides, and Clinical Process Guides [7]. The guides identify recommended practices to optimize the safety and safe use of EHRs [7]. The Contingency Planning guide addresses planned or unplanned EHR unavailability, preparing clinicians and support staff to minimize the impact of outages [1]. The System Management guide covers configuration, validation, and maintenance of EHR hardware, software, and system-to-system APIs, including the physical environment and testing of technically complex components [7].
SAFER Guides are not product certifications. They are organizational self-assessment tools that map responsibilities and practices. The Organizational Responsibilities guide identifies individual and organizational activities, processes, and tasks to help optimize safety [1]. The High Priority Practices guide helps organizations identify fundamental practices when introducing new or upgraded technology [1]. A procurement team can use these guides to evaluate whether a vendor's implementation methodology supports the practices the organization must adopt. The guides do not provide a score that can be compared across vendors.
A Hypothetical Evaluation Workflow
Consider a mid-sized specialty clinic evaluating two certified EHR modules for a new ambulatory site. The clinic's defined use case is bidirectional data exchange with a regional health information exchange and patient access via a portal. The evaluation team first checks the CHPL for both modules and confirms certification status [1]. It then reviews the US Core capability statements for each module to determine whether they support Profile Only or Profile plus Interaction Support [3]. The team asks each vendor to demonstrate a FHIR RESTful search for a Condition resource and a DiagnosticReport resource [3].
The team also reviews the SAFER Contingency Planning guide to assess how each vendor's implementation plan addresses EHR unavailability [1]. It uses the System Management guide to evaluate configuration and API testing practices [7]. This hypothetical workflow is a suggestion, not a tested methodology. The source documents do not provide a template for combining these checks into a weighted score. The clinic must decide which practices are mandatory based on its own risk assessment. The evaluation does not establish which module is safer or more effective.
Sources & references
- Selecting or Upgrading Health IT - ONC - Office of the National Coordinator for Health Information Technology · healthit.gov
- Hospital Use of APIs to Enable Data Sharing between EHRs and Third-Party Technology - ONC Health IT Research & Analysis · healthit.gov
- Home - US Core Implementation Guide v9.0.0 · www.hl7.org
- Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide · nvlpubs.nist.gov
- Certification of Health IT - ONC - Office of the National Coordinator for Health Information Technology · healthit.gov
- Using Health IT - ONC - Office of the National Coordinator for Health Information Technology · healthit.gov
- SAFER Guides - ONC - Office of the National Coordinator for Health Information Technology · www.healthit.gov