Certified Health IT Topics

Some regulatory certifications or registrations to products or services referenced on this website are held by Cerner Corporation. Cerner Corporation is a wholly-owned subsidiary of Oracle. Cerner Corporation is an ONC-certified health IT developer and a registered medical device manufacturer in the United States and other jurisdictions worldwide.


ONC Certified Health IT

Cerner Corporation is proud to offer health IT products certified under the Office of the National Coordinator for Health Information Technology (ONC) Health IT Certification Program. Provided below is key information about Cerner certified software.

Costs and fees information

Linked below is a list of the Cerner Certified Health IT Modules and the respective cost and fee information for each. Also included are the specific certified criteria for each Certified Health IT Module, certification dates, certified software versions, unique certification numbers, and significant implementation details.

Download the Cerner-provided Certified Health IT Costs Information (PDF)

Certified API technology fees

APIs unlock opportunities for healthcare organizations to transform care delivery and operational efficiency. Oracle Health APIs are cloud-based, allowing for rapid, agile deployment of future updates or enhancements. Learn more about the tools and resources available to connect apps and devices to the Oracle Health Millennium Platform by visiting, the Oracle Health Developer Program. For information on certified API access and fees for app developers and see API Access and Fees.

Millennium Certified APIs

Standard (standalone environment) healthcare provider implementation categories are separated into similarly situated tiers of S/M/L/XL based on the volume of patient records in the system. Pricing and tiering are calculated and charged per the Oracle Health Millennium Platform production environment. Please note that actual contracted amounts may vary from those shown in the table by up to $8 based on rounding applied for fee calculations.

  • Small (S) = 0 to 2 million patient records
  • Medium (M) = 2 to 10 million patient records
  • Large (L) = 10 to 20 million patient records
  • Extra large (XL) = More than 20 million patient records

In addition to the fees outlined in the table below, a one-time setup fee of $10,000 also applies for first-time implementations covering one production environment and one nonproduction environment. A one-time $5,000 fee applies for each additional nonproduction environment setup requested. No additional charges apply related to ongoing use of the certified API technology.

Healthcare provider category

Annual fee—single patient API

Annual fee—bulk data API
Standard—S (standalone environment) $15,000 $7,000
Standard—M (standalone environment) $20,000 $10,500
Standard—L (standalone environment) $25,000 $17,500
Standard—XL (standalone environment) $30,000 $28,000
CommunityWorks (shared environment) $3,000 $1,500
Continuum ASP (shared environment) $1,500 $1,000

Soarian Clinicals Certified APIs

Cerner does not charge healthcare providers for access and use of the APIs, with the exception of a one-time setup service fee of $28,935 for the first environment and $9,720 for each additional environment.

Artificial Intelligence and Machine Learning Development Practices

At Oracle Health, we believe artificial intelligence (AI) and machine learning (ML) technology offer unmatched potential for transforming health IT and the healthcare industry in positive ways. Ensuring that such technology is developed, implemented, and maintained in a thoughtful and responsible way is essential to achieving AI’s potential benefits in healthcare. To support this critical principle, Oracle Health has established an internal assessment and review process for all AI and ML technology incorporated into its healthcare products, applications, and services.

Download the Oracle Health Summary of AI and ML Development Practices

Electronic Health Information (EHI) Export

Cerner’s certified health IT modules which store electronic health information (EHI) support the ability to export that EHI in an electronic and computable format. This includes both a single patient export capability intended for fulfilling a patient’s right of access request and a patient population export intended for the purpose of facilitating data transitions when providers switch health IT systems.

Provided below are the data format specifications for the various EHI Export capabilities across applicable certified health IT modules. These specifications should be used to assist in interpreting and processing EHI received as part of an EHI export operation.

Please note that the specifications provided include all schema and data formats available in the most current release of the applicable product(s). Individual implementations may have slight variations in available schema and data formats depending on the specific release of each relevant product that is currently active.


Millennium

Linked below is the EHI Export format specifications and complementary user instructions for the following Cerner Millennium certified HIT modules which store EHI: Millennium (Clinical), Millennium (CQMs), Millennium (Health Care Surveys), Millennium (Immunizations), PowerChart Touch, Patient Portal.

The documentation includes format specifications for four independent storage locations where relevant data is maintained. Please note that data from the Oracle Health Multimedia Storage location is maintained and exported in the original format that the data has been stored in. This may include file types ranging from audio files, text files, and patient photos to PDFs and Digital Imaging and Communications in Medicine (DICOM).

EHI Export Type

Data Overview and Instructions

Data Format Specifications
Single Patient Export Single Patient EHI Export Data Overview and User Instructions (PDF) Single Patient EHI Export Data Format Specifications (ZIP)
Patient Population Export Patient Population EHI Export Data Overview and User Instructions (PDF) Patient Population EHI Export Data Format Specifications (ZIP)

Health Data Intelligence (HDI)

Linked below is the EHI Export format specifications and complementary user instructions for the Health Data Intelligence: eCQMs certified health IT module. The export supports all data for the HDI Longitudinal Record, which represents the full data set for the product of which the identified certified health IT module is a part.

EHI Export Type

Data Overview and Instructions

Data Format Specifications
Single Patient and Patient Population Exports Health Data Intelligence EHI Export Data Overview and User Instructions (PDF) Health Data Intelligence EHI Export Data Format Specifications (PDF)

Soarian Clinicals

Linked below is a list of the EHI Export format specifications for both Soarian Clinicals and Pharmacy/Med Administrative Check. The zip file contains the latest exception pack (EP) updates currently available for an innovation update (IU).

Soarian Clinicals EHI Specifications

Update

RxMAK EHI Specifications
Soarian Clinicals EHI Export 4.5.200 (ZIP) 4.5.200 Pharmacy Med Administration Check EHI Export 4.5.200 (PDF)
Soarian Clinicals EHI Export 4.6.100 (ZIP) 4.6.100 Pharmacy Med Administration Check EHI Export 4.6.100 (PDF)
Soarian Clinicals EHI Export 4.7.100 (ZIP) 4.7.100 Pharmacy Med Administration Check EHI Export 4.7.100 (PDF)

Novius Lab

Linked below is the EHI Export format specifications file for NOVIUS Lab

NOVIUS Lab EHI Specifications

Version
NOVIUS Lab EHI Export (PDF) 27.2.5

Soarian Document Management

Linked below are the EHI Export format specifications files for Soarian Document Management

Soarian Document Management EHI Specifications

Version
DM_Single Patient Export (PDF) 25.4 SP6 U5
DM_Patient Population Export (PDF) 25.4 SP6 U5

Patient Portal - MMD

Linked below are the EHI Export format specifications files for Patient Portal - MMD

Patient Portal – MMD EHI Specifications

Version
Patient Portal - MMD Single Patient Export (PDF) 8.1
Patient Portal - MMD Patient Population Export (PDF) 8.1

Real World Testing

As part of the Conditions and Maintenance of Certification introduced with the 21st Century Cures Act Final Rule, the Office of the National Coordinator for Health IT adopted an annual requirement for developers of certified health IT to demonstrate the successful interoperability of their certified software in real-world use. Real World Testing is demonstrated through annual Real World Testing plans outlining how the certified developer will be demonstrating the successful interoperability for each pertinent certified capability, and the corresponding Real World Testing results. Provided below are the Cerner annual Real World Testing plans and results organized by calendar year.

Standards Version Advancement Process

Under the ONC’s Standards Version Advancement Process (SVAP), developers of certified health IT are permitted to voluntarily certify to newer versions of adopted standards that have been approved by the National Coordinator via the SVAP. Provided below is a listing of the National Coordinator–approved newer versions of adopted standards that Cerner has (or intends to) voluntarily certified to, organized by calendar year.

Calendar year

Certification criterion

NC-approved new standard version

Health IT module(s) and version(s)

Advance notification of intent
2021 170.315(c)(3) CQM-report CMS Implementation Guide for Quality Reporting Document Architecture: Category I; Hospital Quality Reporting; Implementation Guide for 2021 (PDF)

CMS Implementation Guide for Quality Reporting Document Architecture: Category III; Eligible Clinicians and Eligible Professionals Programs; Implementation Guide for 2021 (PDF) 		PowerChart (CQMs) v2015.01 & v2018

FirstNet (CQMs) v2015.01 & v2018

Soarian Clinicals v2015 (EH only)		 2021 SVAP Notification - 170.315(c)(3) (PDF)
2022 170.315(c)(3) CQM-report CMS Implementation Guide for Quality Reporting Document Architecture: Category I; Hospital Quality Reporting; Implementation Guide for 2022 (PDF)

CMS Implementation Guide for Quality Reporting Document Architecture: Category III; Eligible Clinicians and Eligible Professionals Programs; Implementation Guide for 2022 (PDF)		 Millennium (CQMs) v2015.01 & v2018

Soarian Clinicals v2015 (EH only) 		2022 SVAP Notification - 170.315(c)(3) (PDF)
2022 170.315(b)(1) Transitions of care

170.315(h)(1) Direct Project 		Applicability Statement for Secure Health Transport Version 1.3, May 2021 (Direct) PowerChart (Clinical) v2015.01 & v2018

FirstNet (Clinical) v2015.01 & v2018

Soarian Clinicals v2015 		2022 SVAP Notification - 170.315(b)(1) and (h)(1) (PDF)
2023 170.315(c)(1) CQM-record and export

170.315(c)(2) CQM-import 		HL7® CDA® R2 Implementation Guide: Quality Reporting Document Architecture - Category I (QRDA I); Release 1, STU Release 5.3 with errata - US Realm, December 2022 Millennium (CQMs) v2018

Soarian Clinicals v2015 (EH only) 		2023 SVAP Notification – 170.315(c)(1)-(3) (PDF)
2023 170.315(c)(3) CQM-report

170.315(c)(2) CQM-import 		CMS Implementation Guide for Quality Reporting Document Architecture: Category I; Hospital Quality Reporting; Implementation Guide for 2023 (March 2023) (PDF)

CMS Implementation Guide for Quality Reporting Document Architecture: Category III; Eligible Clinicians and Eligible Professionals Programs; Implementation Guide for 2023 (December 2022) (PDF) 		Millennium (CQMs) v2018

Soarian Clinicals v2015 (EH only) 		2023 SVAP Notification – 170.315(c)(1)-(3) (PDF)
2024 170.315(c)(3) CQM-report CMS Implementation Guide for Quality Reporting Document Architecture Category I Hospital Quality Reporting; Implementation Guide for 2024 (Updated August 2023) (PDF)

CMS Implementation Guide for Quality Reporting Document Architecture Category III Eligible Clinicians Programs; Implementation Guide for 2024 (Updated November 2023) (PDF) 		Millennium (CQMs) v2018 & v2024

Soarian Clinicals v2015 (EH only) 		2024 SVAP Notification – 170.315(c)(3) (PDF)
2025 170.315(E)(1) View, Download, and Transmit to 3rd Party Web Content Accessibility Guidelines (WCAG) 2.2, October 5, 2023 (available 8/19/2024)

Patient Portal - version 2 (CHPL publication pending) 2025 SVAP Notification – 170.315(e)(1) (PDF)

Multifactor authentication use cases

Some Cerner Certified Health IT Modules support multifactor authentication (MFA) using industry-recognized standards for specific use cases. Linked below is additional documentation outlining those MFA use cases and supplemental information related to its implementation and use.

Download the Cerner multifactor authentication use cases documentation (PDF)

Where to find more information about the Cerner certifications

To obtain more information about how Cerner products meet the ONC certification standards, please email us at ocregulatorycompliance_us@oracle.com. For direct access to Cerner’s published certifications, please see ONC’s Certified Health IT Product List (search for “Cerner”).

Get started with Oracle Health


Contact Oracle Health

Talk to a team member about Oracle solutions for healthcare.

Contact Oracle Health today