Health Cloud For AIPsWebinar

January 19, 2017

john.hogan@salesforce.com

John HoganSenior ISV Technical Evangelist

Agenda• (Re) Introduction to Health Cloud

• A Quick Tour

• Configurability / Customization

• Architectural Considerations

• Best Practices

• Roadmap

• Resources

Forward-Looking Statements

Statement under the Private Securities Litigation Reform Act of 1995:

This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.

The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.

Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

(Re) Introduction to Health Cloud

Healthcare is ShiftingToward the Patient

Regulation Expectations

Clinical Innovation

Affordable Care Act (ACA)

$17BChronic Care Management (CCM)

Medicare bonus estimate for 2015

78% unsatisfied with U.S. healthcare system*

71% of millennials expect to usea mobile app to manage health**

*Deloitte Survey of US Health Consumers**Salesforce Connected Patient Report

Future of Healthcare: Deeper Relationships

ConnectedHealth Professionals

ConnectedFamilies

ConnectedApps & Products

ConnectedCare Coordinators

ConnectedPatients

Systems ofRecord

Electronic Health Records

Patient Relationship ManagementPatient ViewProfile & journey

Care Team ProductivityCollaboration, insight

New Era in Healthcare: EHR + Patient RelationshipManagement

Medication Diagnostics ImagingClinicalRevenue Cycle

Patient EngagementMobile, social, innovation

Perspective for PartnersWith the release of Health Cloud, partners have the opportunity to develop applications that align with Salesforce’s goal of empowering healthcare professionals to deliver more personal, targeted care.

Health Cloud provides caregivers:• A Complete View of the Patient: Comprehensive patient care timeline with

integrated EMR and device data• Smarter Patient Management: Engage with patients and the entire care team in

real time• Proactive Patient Engagement: Allow patients to manage personal health care

goals, collaborate with their complete care team, and access resources and education

Transforming Healthcare with our Partner Innovations

Engagement

Population Analytics

Campaigns

Network ManagementEncounters

Benefits & Payment

Care Plan ProtocolsEducation

Compliance

Gaps in Care

P4P

HCC

Onboarding

Outreach

Wellness

Assessments

Clinical Guidelines

Patient Smart Lists

Referrals

Scheduling

Analytics

Provider Match

Ride to Health

IoT

Biometrics

Telehealth

Encounter Notes

Patient education Wellness

Behavioral Health

Health Vault

Prevention

Reminders

Surveys

Collaboration

RCM

Benefits Plans

Eligibility

Payment Alternatives

Forms

A Quick Tour

Customization / Configurability

Health Cloud is a Managed Package

• Fully upgradeable• Intellectual property (IP) protection for

Apex, Visualforce Component, and Custom Setting

• Versioning support for API accessible components

• Branch and patch a previous version• Push patch updates to subscribers• Unique naming of all components to ensure

conflict-free installs (Namespace)

Managed Package HC Release Schedule• Aligned with Core Releases, 3x per year• Two or three staggered releases• Minor Releases as required

Managed Package

+ Required for ISV Technologies• Push upgrades• License Management• Support Features• Usage Metrics• Trials• AppExchange Listing

What is/isn’t Customizable?

o Today Pageo Patient List Viewso Patient Record - Timeline & Care Plano Care Plan Problem and Goal Creation/Edit Layouto Patient Record - Detailso Patient Record - Collaborationo Patient Record - Patient Generated Data

Health Cloud Customization Color KeyWhat is/isn’t customizable?

Not Customizable

Configurable (Data Records / Fields)

Configurable (Order/Placement)

All information is in the “notes” section on every slide.

Today Page

Patient List Views

Patient Record - Timeline & Care Plan

Care Plan Problem and Goal Creation/Edit Layout

Patient Record - Details

Patient Record - Collaboration

Patient Record - Patient Generated Data

Health Cloud Configurability Top Items“Health Cloud – Admin” app: Access to Configuration Tools, and tab access to EHR_ Objects

Timeline View Configurations● Add Event type to Timeline● Add Custom Event Icon

Patient Card Configurations● Add Patient Data to Patient Card● Order Patient Data

Filter Criteria● Manage Health Cloud List Views● Delete List Views

General Setup Information: License and Permission SetsHealth Cloud Requires Service Cloud Feature Licenses and Permission Sets

When creating new users, you need to make sure they have “Service Cloud User” User permission, as well as the appropriate Health Cloud Permission Set.

Architectural Considerations

Individual Data Model

• Individual: A “virtual” object to represent an “Individual” in the “real world”, composed of two Standard Objects – Account and Contact

• Both Objects connected through a common Individual ID Field

• As Individual includes an Account and a Contact:• Account supports the transactions

• Contact supports the communities/communication

• This is NOT a Salesforce Person Account

Individual Data Model

Individual A

Account(RT = Individual)

Contact(RT = Individual)

Individual ID

Individual B

Account(RT = Individual)

Contact(RT = Individual)

Individual ID

Organization X

Account(RT = organization)

Household Y

Account(RT = household)

C2C__c• Role: SPOUSE• Start date• End date

A2C• Role: SECONDARY• Start date• End date

A2C__c• Role: PRIMARY• Start date• End date

A2C__c• Role: EMPLOYEE• Start date• End date

Household Z

Account(RT = household)

A2A__c• Role: EXTENDED• Start date• End date

Individual Data Model - APIs

• Batch and Real Time creation of Individuals in Salesforce

• createIndividuals()• getIndividuals()

Industries REST API Developer Guide: https://resources.docs.salesforce.com/sfdc/pdf/api_rest_industries.pdf

Health Cloud Data Model

EMR_xxEMR_xx

EHR_xx__c

Goals__c

Tasks(RT = CarePlan)

Case(RT = CarePlan)

Account(RT = Individual)• Care Plan• ExternalId#

Individual A

Individual ID

Contact(RT = Individual)

Case TeamProblems__c

Protocols(internal articles)

Educational(public articles)

Knowledge

Case Feed

EMR_xxEMR_xx

EHR Systems

Integration Middleware

Data Model Additions: Spring ‘17

Individual**

Program Patient Affiliation

(Start Date, End Date, Provider)

Account(RT: Individual)

Contact

Individual id

* Existing Objects** Existing Objects - Fields Added

ProviderProgram(RT: Risk, CCM)

Program Patient Summary

EHR Practitioner*

Contact-Contact*

Users*

Condition to HCC Code Mapping

EHR Care Plan Participant

EHR Practitioner Identity

EHR Practitioner Qualification

EHR Related Person

EHR Encounter Participant

EHR Encounter Accomodation

EHR Care Plan Activity

EHR Care Plan Goal

EHR Care Plan Concern

EHR Vaccination Protocol

Clinical Data Model – Summary

EHR Allergy Intolerance

EHR Related Observation

EHR Encounter

EHR Virtual Device Channel

EHR Care Plan

EHR Patient Contact

EHR Medication Statement

EHR Immunization

Modeled after: http://hl7.org/fhir/resourcelist.html

EHR Observation

EHR Dosage Instruction

EHR Medication Prescription

EHR Patient Care Provider

EHR Virtual Device

EHR Device

EHR Condition Related Item

EHR Condition

EHR Practitioner Role

EHR Patient

EHR Practitioner

Account(RT = Individual)

Individual A

Contact(RT = Individual)

Best Practices

Patient Account Record is “Primary Record” for Health Cloud

• Lookup relationship from EHR_ Objects• Only Account Tasks show on Timeline• Care Plan also creates Tasks on Account

Use the Individual Virtual Object

Any functional downsides for “patching together” a Patient, or Individual?• Current code does not enforce that an Individual is not based on a Record

Type• Patient blindly goes by “Primary Contact” populated and “Care Plan“

populated• Future iterations of the Health Cloud will depend on and leverage the

Individual model. It is strongly recommended that Partners use the Individual data model to represent a person (e.g. Physician, HCP, Specialist)

Individual is both an Account and Contact – NOT a Person Account

Use the Individual Virtual ObjectIndividual Record Types

Health Cloud adds an “Individual” Record Type to both Account and Contact

• Health Cloud is designed to accommodate additional Record Types – set up/coordinated with both Account and Contact, as required by Partner extensions.

Master Detail/Lookups, EHR_ to Contact

Creating a lookup from the EHR_Encounters to Contact ● SOQL Error on Patient Card● Apex Controller Issue

Creating a lookup to BOTH Account and Contact on any object, add it as an Event type to the Timeline● Timeline goes blank● Event must be deleted or the contact lookup relationship removed

Why would you create this type of relationship? • To have related lists show on the Contact Detail, less clicks to get to related lists

This causes issues:

Leverage Care Plans and Care Plan TemplatesA “Care Plan” is a common theme, don’t rebuild it

Goals__c

Tasks(RT = CarePlan)

Case(RT = CarePlan)

Problems__c

CarePlanTemplateGoal__c

CarePlanTemplate_Task__c

CarePlanTemplate__c

CarePlanTemplateProblem__c

Roadmap

Health Cloud Roadmap

Engagement

• Patient Card• Patient Care Plan• Health Timeline View• Care Team Network Map

• Communities• Care Team List• Task List• Private Messaging (Inbox)• Clinical Surveys

Intelligence

• Analytics – Risk Scoring Advanced Filtering

• Packaged Reports and Dashboards• Procedure in Data Model• Clinical Surveys

Productivity• ‘Today’ Overview Page• Patient Segmentation• Collaboration

• Care Plan Templates and Customization• List View Improvements

• Multiple Care Plans + Care Teams• Field Service Integration

Platform• Industries Individual/Person Objects• Clinical Data Model and EHR

Integration

• Salesforce Shield Availability• Localization (English UK, Dutch, German,

Spanish (EU and MX), Portuguese, French)

• Lightning Service Desk Integration• Care Plan – Configurable Page Layouts

and Record Types• CTI Support

Spring’16 (Launch)Care coordination framework

Summer’16 & Winter ’17Market availability and care plan customization

Future ThemesEnd to end patient experience

Resources

Health Cloud Resources for Partners

Health Cloud For Partners Chatter Group● Technical & Product Resources and

Information● Learning Path● Org Access

● Sales Enablement Resources

Partner Community

p.force.com/healthcloud● Media● What You Need to Know● Resources● FAQs

HiMSS: February 19 -23, 2017 in Orlando, Florida

Thank you