Cerner Application Approval Process

[Paul Kruger]

What is the process regarding getting a Cerner FHIR Program approved?

[Jenni Syed (Cerner)]

Hi Paul,

The very high level process is documented here: https://code.cerner.com/millennium#howitworks and some of the validation is also mentioned here: http://fhir.cerner.com/smart/#authorization-model

Note: some of the technical guidance called out in that SMART doc would be covered in validation as well.

See the discussion here for a bit more context: https://groups.google.com/d/msg/cerner-fhir-developers/r3MH9wbUIsk/-vk_aO3eAAAJ

Note: this is assuming that you're asking about an application that a practitioner is using (based on previous conversations).

~ Jenni  

[Paul Kruger]

Jenni,

Quite a number of questions.  Referencing the document you sent https://code.cerner.com/millennium#howitworks, it says I need to join the developer program.  I understood previously that that was not required?  Additionally, step three simply states "The validation process has four main categories: security, functionality, technical conformance, and operational capacity." 

Is joining the developer program required?
How does one kick off the validation process? 
What security requirements must be met? 
What functional requirements are you looking for?
Technical conformance to what standard?
How is Operational Capacity Evaluated?

Paul

[Yegor Hanov (Cerner)]

Hi, Paul!

 

You are not required to join the developer program to use our tools and Sandbox API for experimentation and proof-of-concept application development.  Participation in the developer program is required for developers of provider-facing SMART apps before they can market those apps to Cerner EMR clients.  Participation in the developer program for developers of direct-to-consumer SMART apps will be optional.

 

Once you join the developer program, we will work with you to get your application ready for validation and subsequent deployment to clients.  The goal of the developer program is to ensure that apps are production ready, that they fit seamlessly into provider’s workflow, and that they integrate well with the way our clients manage data. As we go through the steps of the program, our goal is to ensure that the app can be integrated quickly and easily into client domains and works consistently.

 

Different parts of the validation process (security, ops, technical, etc.) are structured to ensure we meet the goals of the program.  There is a questionnaire involved with each part to gather basic things we need to work together such as support contacts, business contacts, release policy, patching policy, etc.  Some sections of the process will involve us reviewing the interaction of the app with the API and with the EMR workflow and providing feedback on potential improvements.  We also put in quite a bit of efforts in making sure both parties know the specific process steps for successfully deploying application into live client environments.

 

Without going into too much detail, the process overall is intended to be streamlined as much as we can make it while ensuring that we create the best possible integrated solutions for our mutual clients. 

Yegor (Cerner)