Skip to main content
Skip to footer

API Access and Fees

Learn more about the applicable fees and process for accessing Cerner’s Certified APIs.

The 21st Century Cures Act of 2016 (Cures Act) placed an even larger focus on APIs and their potential to help transform the health care industry. The Office of the National Coordinator of Health IT (ONC) has been working over the last several years to adopt new regulations and requirements implementing provisions of the Cures Act, the culmination of which we saw published on May 1, 2020 as the 21st Century Cures Act: Interoperability, Information Blocking, and ONC’s Certification of Health IT Program Final Rule. This rule expanded the scope of API capabilities under the ONC’s HIT Certification Program and established new conditions for certified HIT developers to abide by in furnishing their Certified API Technology, while also delivering new compliance requirements around information blocking.

Access to Certified APIs for patient access app developers

Application programming interfaces (APIs) spur innovation and collaboration among a broader community of developers, enabling the creation of new technology that unlocks opportunities to advance health care. Cerner's APIs are cloud-based allowing for rapid, agile deployment of future updates or enhancements. It also simplifies implementation because the ontology mapping process is centralized, which reduces additional resourcing pressure required when mapping on a per-deployment basis.

Provided below is a comprehensive listing of Cerner’s Millennium and Soarian Clinicals patient access APIs, which are available free of charge. These bundles include our APIs currently certified under the ONC’s 2015 Edition Health IT Certification Program and are highlighted in the tables below by indication of their Common Clinical Data Set (CCDS) data element mappings.

Millennium APIs

 Generally Available FHIR DSTU2 APIs

 Common Clinical Data Set (CCDS) Mappings

 AllergyIntolerance (read) Medication Allergies
 Binary (read) Full Common Clinical Data Set (CCDS) via Continuity of Care Document (CCD) template
 CarePlan (read)

Assessment and Plan of Treatment; Care Team Member(s)

 Condition (read) Problems; Health Concerns
 Contract (read)
 Device (read) Unique Device Identifier(s) for a Patient's Implantable Device(s) 
 DocumentReference (read) Full Common Clinical Data Set (CCDS) via Continuity of Care Document (CCD) template
 Goal (read) Goals 
 Immunization (read) Immunizations
 MedicationStatement (read) Medications
 Observation (read) Laboratory Tests and Values/Results; Smoking Status; Vital Signs
 Patient (read) Patient Name, Sex, Date of Birth, Race, Ethnicity, Preferred Language
 Person (read)
 Practitioner (read)  
 Procedure (read) Procedures
 RelatedPerson (read)
 launch
 profile (or fhirUser)
 openid
 online_access

 launch/patient

 offline_access

For Cerner’s full set of available Millennium APIs beyond the free certified patient access APIs outlined above, click here.

Soarian Clinicals APIs

 Generally Available FHIR DSTU2 APIs

Common Clinical Data Set (CCDS) Mappings

 AllergyIntolerance (read) Medication Allergies
 CarePlan (read)

Assessment and Plan of Treatment

 Condition (read) Problems; Health Concerns
 Device (read) Unique Device Identifier(s) for a Patient's Implantable Device(s)
 DocumentReference (read) Full Common Clinical Data Set (CCDS) via Continuity of Care Document (CCD) template
 Goal (read) Goals 
 Immunization (read) Immunizations
 MedicationStatement (read) Medications
 Observation (read) Smoking Status; Vital Signs
 Patient (read) Patient Name, Sex, Date of Birth, Race, Ethnicity, Preferred Language
 Procedure (read) Procedures

Note – Additional development is underway for both Millennium and Soarian Clinicals APIs to support U.S. Core Data for Interoperability (USCDI) V1 data elements in alignment with the API standards adopted in ONC’s  Cures Act final rule. API resources tables will be updated accordingly once that development and certification are completed.

The following information applies to patient-facing app developers connecting with Millennium certified API technology. Value-added services for app developers are not offered for Soarian Clinicals certified API technology.

Overview

Cerner will provide optional value-added services for both third-party developers as well as health systems developing their own patient access apps. This section lists the specific services and associated fees charged by Cerner for access to value-added services for certified API technology (Cerner Ignite APIs).

Services

  • Security – Cerner will perform a security assessment for the third-party app which includes a security scan, security policy, and a threat model review of the app.
  • Functional Review – Cerner will perform a functional review of the third-party app, which focuses on ensuring the app integrates well with Cerner’s certified APIs. The Cerner team will ensure the app consumes the appropriate API resources, responds well to EHR-specific events, and fits into the overall flow of the data integration. The functional review does NOT include an assessment of the efficacy and value of the algorithms internal to the app.
  • Operational Review – The operational review is to align our teams for activities that take place after the third-party app is validated – including ongoing maintenance and support. During the review, Cerner will gather and document information needed to ensure timely and accurate resolution to potential issues after the app deploys to a production environment.
  • Marketing – Marketing services are contingent on third-party apps completing the validation process. Services, including providing the app developer a dedicated landing page, access to our brand guidelines and code validation logo, as well as other opportunities, will be discussed upon the completion of the validation program.

Fees

  • Pricing for the services listed above is $12,500 annually. Pricing will be reviewed periodically and is subject to change. Updates will be posted to this site.
     
 

Is your patient app ready for production? Before submitting your registration request, please ensure you have completed the following:

 Reviewed Cerner Terms of Use.
 Reviewed our API Access Agreement.
 Reviewed our Millennium or Soarian Clinicals API documentation.
 Tested in Cerner's Millennium sandbox or Soarian Clinicals sandbox.(recommended, but not required) 

After completing the above activities, please submit your registration request here.

Once your registration request has been submitted and your app is production-ready, you will no longer be able to modify the app. If updates to your app are needed post-registration, please email Soarian Clinicals API Request or Millennium API request. We recommend you create a separate developer instance of your app to continue modifications and testing in the public sandbox before requesting changes to the production app.

Following registration, the app will be published on our internal portal for Cerner health care provider clients to view and obtain information. In order for your app to be connected to a health care provider system, a client representative will need to contact Cerner via eService to request the connection. (You may send them this link and they will have access to the site.) Or, you can email Soarian Clinicals API Request or Millennium API request to submit a request on their behalf.

The following information applies to provider-facing app developers connecting with Millennium APIs, which currently is outside the scope of certified APIs. At this time, Soarian Clinicals APIs are not available for provider apps.

Is your provider app ready for production? Before submitting your registration request, please ensure you have completed the following:

 Reviewed Cerner Terms of Use.
 Reviewed our API Access Agreement.
 Reviewed our Millennium (EHR platform) and/or HealtheIntentSM (population health platform) documentation.
 Documented a GAP analysis for your app against Cerner's Smart on FHIR documentation.
 Reviewed our FAQs page to fully understand the process and all technical, security and validation requirements.
 Developed a working app demo, integrating directly with Cerner’s open sandbox.

After completing the above activities, please submit your registration request here.

The validation process is a set of activities which verifies that your app provides our clients with a great, high-quality experience. The following flowchart shows the overall validation process:

Validated apps represent a commitment between Cerner and your company to ensure that we give our clients high-quality apps that are secure and reliable.

000_10721_ClientFacing_Themes_Icons-EmergingTrends_fixed

Find safe and secure apps that integrate with Cerner