Supporting Clinical Data in Health Cloud

Health Cloud has two data models that support storing clinical data.

• The packaged EHR data model: A set of custom objects that are part of the Health Cloud managed package.
• The Clinical data model: A set of standard objects built on the Salesforce platform.

The EHR data model and the Clinical data model are built to align with the Fast Healthcare Interoperability Resources (FHIR) specification. These data models support easier and more straightforward clinical data integration from other source systems. When devising an implementation strategy, you or your integration partner map messages from the electronic health records system to the correct Health Cloud object.

Health Cloud uses the following standard and custom objects to manage patient data.

Account

In Health Cloud, the account record for a patient is a person account, not an account representing a business or an organization. Contacts and accounts that represent caregivers or external healthcare providers are associated with the account through the patient care plan (case record).

Contact

In the Salesforce data model, contacts are the people associated with the patient, such as family members and specialists who are outside of your organization. A contact must be related to an account. When you set up and use Salesforce Experience Cloud, the Contact object supports communication within the private patient site. Care team members are added as either external contacts without site access or as Salesforce users and contacts, which give them access to the patient site.

User

Health Cloud includes internal Salesforce users and Experience Cloud users. Each user type has different access to records and functions. Internal users have access to patient data, when granted. Experience Cloud users don’t have access to patient data.

Case Team Member

A patient care team member is part of the team that works on tasks in the patient’s care plan. In Health Cloud, care team members can be family members and healthcare providers from outside of your organization. They can also be internal Salesforce users, like the primary care physician. When Digital Experiences is enabled, care team members with access to the site use Case Feed to collaborate around the patient and the care plan. Care team members who are only contacts can’t log in to Salesforce, so they don’t have access to Chatter in the case feed or to the patient care plan.

Case Team Role

The Case Team Role object represents a role for a member of the patient care team, such as Caregiver or Physiotherapist. Care coordinators assign roles when they add a member to the private patient site. The case team role also controls access to the case and the care plan, and controls visibility of the user in the site.

Case

In Health Cloud, the care plan a record type of Case. The case permission controls access to the elements of the care plan, to the care team (Case Team), and to the communication within the patient’s Experience site. All care team members are associated with the patient’s contact record through the Case object.

Problem

Each care plan has a list of clinical or non-clinical health issues that must be addressed. The conditions, problems, concerns, and diagnoses that are managed and mitigated by this plan are represented in the Care Plan Problem custom object.

Goal

Represents the intended objectives of carrying out a care plan.

Task

Represents an activity, such as making a phone call, completing a survey, attending a medical appointment, or other to-do items. Tasks can be directly related to a goal or problem on the care plan, or even directly to the care plan itself.

Custom objects in the EHR Data Model

The custom objects that hold patient data that comes from the EHR system of record. For example, EhrCondition__c represents detailed information about conditions, problems, and diagnoses recognized by a clinician. Data is replicated into these custom objects from EHR or other clinical systems with read-only access. And because this data in Health Cloud is view only, the source system remains the system of record. The packaged EHR data model is succeeded by the standard objects in the newer Clinical data model, which is built to align with a newer version of FHIR. So we recommend that you build your integration using the standard objects in the Clinical data model.

Standard objects in the Clinical data model

Similar to the packaged EHR data model, these standard objects hold patient data that comes from external EHR source systems. For example, HealthCondition represents detailed information about conditions, problems, and diagnoses recognized by a clinician. Objects in this data model are built to align with FHIR R4, specifically FHIR v4.0.1. All clinical data related feature development in Health Cloud is to be built on these objects, not the older objects in the packaged EHR data model. So we recommend that you build your integration using the standard objects in the Clinical data model.