This document discusses Cerner's efforts to build an open platform for healthcare applications and data sharing using FHIR and SMART on FHIR standards. It provides an overview of Cerner's APIs and developer tools including documentation, code repositories, and a validation process for apps. The goal is to create an ecosystem where independent developers can build apps and extensions that integrate with Cerner's EHR system to extend its functionality and drive innovation.

1. FHIR® is the registered trademark of HL7 and is used with the permission of HL7. The Flame Design mark is the registered trademark of HL7 and is used with the permission of HL7.
Amsterdam, 15-17 November | @fhir_furore | #fhirdevdays17 | www.fhirdevdays.com
Building on Cerner with SMART on FHIR
Kevin Shekleton & Yegor Hanov, Cerner

2. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.

3. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.

4. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
3
Cerner Today

5. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
4
APIs have transformed many other industries
We believe they can do the
same for health care!
• Application Programming Interfaces
(APIs):
• Allow technical solutions to talk to one
another in the same language
• Easily expose services to make them
available inside and outside an
organization
• Cerner’s open platforms expose
standards that make it possible to
connect apps and easily transfer
discrete data.

6. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
5
EHR as Open Platform
• EHR becomes a Platform
• User and patient management
• Core transactional services (orders, documentation, etc.)
• Common workflow orchestration (admission, discharge, etc.)
• Legal record
• Use the “Public API” to extend EHR functionality
• No single vendor can supply every needed function
• Innovation moves faster at the edge
• Niche workflows and local use cases solved efficiently
• A new ecosystem for developers and researchers

7. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
6
Open Platforms Vision
Cerner is accelerating health care
innovation by enabling a broad
community to amplify the power of its
open platforms

8. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
7
Mobility
Desktop Patient
ProviderInternet
Cerner Ignite APIs for Millennium
Ignite APIs
for Millennium
Platform

9. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
8
Ignite APIs
for Millennium
Benefits of a cloud-based API
• Centrally Managed Security (internet, authentication and authorization)
• Consistent API experience for all clients
• Rapid, agile deployment of updates and enhancements of FHIR standard
• Centralized ontology mapping
• Flexibility – scale capacity to meet application demand (predictable costs)

10. ”
“
© Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
9
Health IT platforms must be open…. The quality
of being open is what allows independent
developers to build apps and extensions that
work with existing health IT platforms.
Neal Patterson
Testimony to U.S. Senate Committee on Health,
Education, Labor and Pensions, June 10, 2015
Founder and CEO, Cerner Corporation

11. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
Cerner Open Developer Experience: code.cerner.com

13. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
Principles of Open Ecosystem
Access
Trust
Opportunity

14. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
13
App Validation
The Functional Review
focuses on the app
interaction with the API to
ensure optimal exchange
of data sets as well as
seamless integration into
EMR workflow.
Functional
The UX Review ensures that
the experience of the app
meets Cerner’s standards of
being valuable, effective,
trustworthy, safe, and clear.
UX
The Technical Requirements
Review documents the
technical requirements of your
app. The Operational Review
ensures apps are
operationally mature prior to
implementation.
Operational/Technical
The Security Review
provides an assessment
of any potential security
flaws in your app.
Security

15. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
code.cerner.com/apps

16. Cerner’s App Validation Program ensures apps are production ready, that they
fit within the provider’s workflow, and that they integrate well with the way our
clients manage data. As developers complete the steps of the program,
Cerner’s goal is to ensure that the app can be integrated quickly and easily into
client domains and works consistently.

17. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
16
EHR Integration

18. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
17
EHR Integration

19. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
18
Unique Users (Production)

20. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
19
App Launches (Production)

21. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
20
how it works for developers
Here are the steps to go from idea to reality.
Engage with the Cerner Open
Developer Experience
• Go to code.cerner.com and
hit the “Start Coding” button
• Browse developer
documentation
• Experiment with the API
using our open sandbox
• Join the discussion on our
developer Google Group
Join the code Developer
Program & get validated
• App Companies can sign
up to get their apps
validated for production
access to Ignite APIs
• Validation process ensures
quality across multiple
dimensions: Security,
Functional, Operations, and
User Experience
Market your app through
Cerner’s App Gallery
• Apps from the code
Developer Program are
given visibility in a gallery
on code.cerner.com
• Presence in the gallery
helps create Trust and
Opportunity with potential
clients
developer perspective

22. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
21
Engage with Cerner’s development team
Open platforms
development team
650+
developers
Active
Google Group
+ =

23. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
Cerner ❤ open source
github.com/cerner Apache licensed

24. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
23
ASCVD Risk Calculator SMART app
• Developed with cardiologists at
Duke University
• Responsive, accessible design
• Completely free & open source!

25. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
24
Related github.com/cerner npm packages
cerner-smart-embeddable-lib
Allows your HTML SMART app to run as an MPage component
fhir-client-cerner-additions
Augments fhir-client.js to allow your HTML SMART app to run
within an embedded IE browser in a native Windows application.
Works with non-Cerner EHRs too!

26. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
25
Developer documentation - fhir.cerner.com

27. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
26
Developer documentation - fhir.cerner.com

28. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
27
Resource Availability (as of 11/15/17)

29. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
28
code Console
• Self-service developer console
• FHIR Sandboxes
• Open
• Secure (OAuth 2)
• Launch your SMART apps
• Provider apps
• Patient apps

30. © Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
29
Exercises – Let’s code!
http://engineering.cerner.com/smart-on-fhir-tutorial
• Create your own SMART app
• Register your app with Cerner’s Sandbox
• Launch your app with Cerner’s Sandbox
• Register & launch the same app with other Sandboxes
Tutorial covers both provider & patient SMART apps!

31. Together we can accomplish
great things