Skip to main content
Skip to footer

API Access and Fees

Learn more about the applicable fees and process for accessing Cerner Ignite APIs.

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 healthcare. Cerner Ignite APIs are cloud-based allowing for rapid, agile deployment of future updates or enhancements. It also simplifies implementation of the APIs for healthcare providers because the ontology mapping process is centralized, which requires less effort than when performed on a per-deployment basis. For information on fees for healthcare providers seeking to deploy Cerner certified API technology, please see the Certified API Technology Fees section at Cerner.com/certified-health-it.

Available options

Learn more about the available API options and requirements below.

Provided below is a comprehensive listing of Cerner Ignite consumer access APIs for Millennium and Soarian Clinicals, which are available free of charge. These bundles include our APIs currently certified under the ONC’s 2015 Edition Health IT Certification Program which are highlighted in the tables below by indication of their U.S. Core Data for Interoperability (USCDI) Version 1 data element mappings. All consumer access API resources listed are currently available for read operations only.

Ignite APIs for Millennium (Consumer Access)

DSTU2 APIs

 R4 Resource

 USCDI V1 Mappings
Appointment Appointment
AllergyIntolerance AllergyIntolerance Allergies and Intolerances
Binary Binary Full Common Clinical Data Set (CCDS) via Continuity of Care Document (CCD) template
Conformance Metadata Capability Statement
CarePlan CarePlan  Assessment and Plan of Treatment
CareTeam Care Team
Condition Condition  Problems; Health Concerns
Contract Consent
Device Device UDI(s) for a Patient's Implantable Device(s)
DiagnosticReport DiagnosticReport
DocumentReference DocumentReference Full Common Clinical Data Set (CCDS) via Continuity of Care Document (CCD) template
Encounter Encounter
Goal Goal Goals
Immunization Immunization Immunizations
Location
MedicationAdministration MedicationAdministration
MedicationOrder MedicationRequest Medications
MedicationStatement
Observation Observation Laboratory Tests and Values/Results; Smoking Status; Vital Signs
Operation Definition Operation Definition
Organization
Patient Patient Patient Demographics
Person Person
Practitioner Practitioner 
Procedure Procedure  Procedures
ProcedureRequest ServiceRequest
RelatedPerson RelatedPerson 
Schedule Schedule 
Slot Slot
StructureDefinition StructureDefinition

 

Ignite APIs for Soarian Clinicals (Consumer Access)

 DSTU2 Resource

USCDI v1 Mappings

 AllergyIntolerance  Allergies and Intolerances
 CarePlan 

Assessment and Plan of Treatment

 Condition  Problems; Health Concerns
 Device UDI(s) for a Patient's Implantable Device(s)
 DocumentReference   Full Common Clinical Data Set (CCDS) via Continuity of Care Document (CCD) template
 Goal  Goals 
 Immunization Immunizations
 MedicationStatement Medications
 Observation Smoking Status; Vital Signs
 Patient PatientDemographics
 Procedure Procedures

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

Value-Added Services & Fees

The following information applies to consumer access app developers connecting with Cerner Ignite APIs for Millennium. Value-added services for app developers are not currently offered for Cerner Ignite APIs for Soarian Clinicals.

Overview

Cerner will provide optional value-added services for both third-party developers as well as healthcare providers developing their own consumer access apps. This section lists the specific services and associated fees charged by Cerner for the value-added services for Cerner Ignite APIs for Millennium.

Services

  • Security – Cerner will perform a security assessment for the third-party app which includes a security scan, security policy review, and a threat model review of the app.
  • Functional Review – Cerner will perform a functional review of the third-party app, which focuses on validating that the app integrates well with Cerner Ignite APIs for Millennium. The Cerner team will also validate that 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 internal logic and capabilities of 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 assist with 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 in the app gallery on code.cerner.com, access to our brand guidelines and code validation logo, as well as other opportunities, would be discussed upon the completion of the validation program.

Fees

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

Provided below is a comprehensive listing of Cerner provider access Ignite APIs for Millennium, which are available to access free of charge. Provider access apps are applications that are authenticating on behalf of a system or a provider user as documented at https://fhir.cerner.com/authorization/.

Ignite APIs for Millennium (Provider Access)

DSTU2 APIs  Supported Actions

 R4 Resource

 Supported Actions  USCDI V1 Mappings
    Account read; search
AllergyIntolerance read; search; create; update AllergyIntolerance   Allergies and Intolerances
 Appointment read; search; create; update Appointment    
     Basic create  
Binary read
Binary read Full Common Clinical Data Set (CCDS) via Continuity of Care Document (CCD) template
Conformance  read CapabilityStatement  read  
CarePlan read; search CarePlan  read; search Assessment and Plan of Treatment
  CareTeam read; search Care Team
Condition read; search; create; update Condition  read; search; create; update

Problems; Health Concerns

Contract read; search Consent read; search 
    Coverage  search; create; patch; delete  
Device read; search  Device read; search  UDI(s) for a Patient's Implantable Device(s)
DiagnosticReport search DiagnosticReport search
DocumentReference read; search; create  DocumentReference read; search; create; update  Full Common Clinical Data Set (CCDS) via Continuity of Care Document (CCD) template
Encounter read; search Encounter read; search; create; patch 
    FinancialTransaction create   
Goal read; search Goal read; search  Goals
Immunization read; search  Immunization read; search; create; update  Immunizations
  Location read; search 
MedicationAdministration read; search MedicationAdministration read; search
MedicationOrder read; search MedicationRequest
read; search; create; patch Medications
MedicationStatement read; search; create; update
     NutritionOrder read; search   
Observation search Observation read; search; create; update  Laboratory Tests and Values/Results; Smoking Status; Vital Signs
OperationDefinition  read OperationDefinition read
  Organization read; search; create 
Patient read; search; create  Patient read; search; create; patch  Patient Demographics
Person read; search Person read; search 
Practitioner read; search  Practitioner  read; search; create 
Procedure read; search  Procedure  read; search; create  Procedures
ProcedureRequest read; search ServiceRequest read; search
    Provenance read; search; create  Provenance 
RelatedPerson read; search RelatedPerson  read; search; create; patch
Schedule read; search Schedule  read; search
Slot read; search Slot read; search 
StructureDefinition  read StructureDefinition read 

Value-Added Services & Fees

The following information applies to provider access app developers connecting with Cerner Ignite APIs for Millennium. Value-added services for app developers are not offered for Ignite APIs for Soarian Clinicals.

Overview

Cerner will provide optional value-added services for both third-party developers as well as healthcare providers developing their own provider access apps. This section lists the specific services and associated fees charged by Cerner for access to value-added services for Cerner Ignite APIs for Millennium. Under the standard value-added services tier, all identified services are available for U.S. Core Data for Interoperability (USCDI) V1 API resources. With the advanced tier, those same services (along with additional marketing and UX opportunities outlined below) are available for the comprehensive scope of provider facing API resources identified above.

Services

  • Security – Cerner will perform a security assessment for the third-party app which includes a security scan, security policy review, 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 internal logic and capabilities of 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 in the app gallery on code.cerner.com, access to our brand guidelines and code validation logo, as well as other opportunities, would be discussed upon the completion of the validation program.
  • User Experience Review* – Cerner will perform a user experience review of the third-party app, which focuses on user interface patterns, accessibility standards, and intuitive features.

*Services available to advanced tier only.

Fees

  • Pricing for the services listed are $15,000 annually per enrolled app for standard tier services scope and $25,000 annually per enrolled app for the advanced tier services scope. Additionally, a $3,000 annual fee is applicable per client production domain connection for each enrolled app. Pricing will be reviewed periodically and is subject to change. Updates will be posted to this site.

Is your consumer access 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 the Cerner 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 attributes of the app registered with Cerner. If updates to the attributes of your app are needed post-registration, please email the Soarian Clinicals API Request or Millennium API request mailboxes. 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 healthcare provider clients to view and obtain information about it. In order for your app to be connected to a healthcare provider system, a client representative will need to contact Cerner to request the connection. You may send them this link which includes directions for logging a request to Cerner via eService, 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 access app developers connecting with Cerner Ignite APIs for Millennium. Provider access apps are applications that are authenticating on behalf of a system or a provider user as documented at https://fhir.cerner.com/authorization/. At this time, Ignite APIs for Soarian Clinicals are not available for provider apps.

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® (EHR platform) and/or HealtheIntent (population health platform) documentation
 Documented a GAP analysis for your app against Cerner 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  the Cerner open sandbox

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

To validate that your app provides our clients with a great, high-quality experience, Cerner recommends opting into our validation process, which is furnished as part of the value-added services outlined under the Cerner Ignite APIs access and fees for provider access app developers tab above. Developers who wish to forgo the validation process may still connect and access all API resources identified in that tab but will not have access to the code validation logo and related Cerner marketing opportunities, nor the range of value-added services provided for seamless integration. The following flowchart shows the overall validation process:

000_10721_ClientFacing_Themes_Icons-EmergingTrends_fixed

Find safe and secure apps that integrate with Cerner