Examine the Clinical Data Model
- Describe the Health Cloud packaged clinical data model.
- Explain the purpose of different objects used in the packaged clinical data model.
The packaged clinical data model captures information from electronic health records (EHR) and the problems, goals, and tasks associated with a care plan. Clinical data is critical to planning, executing, and managing coordinated care plans for patients. The packaged clinical data model, also known as the EHR data model, has more than 30 EHR objects based on the FHIR® (Fast Healthcare Interoperability Resources) standard, providing full visibility into patient history, from inside Health Cloud.
Health Cloud also offers a FHIR-aligned clinical data model. Built on the core Salesforce platform, the FHIR-aligned clinical data model is a successor to the packaged EHR data model. The implementation of the FHIR-aligned data model aligns with FHIR v4.0.1 and supports many of the FHIR R4 attributes. For more details, go to Interoperability and the Clinical Data Model Trailhead module.
This diagram illustrates the packaged clinical data model. For more details on each object in the packaged clinical data model, see the Salesforce Health Cloud Developer Guide.
Explore the Clinical Data Model
Charles has a care plan (Case) in Health Cloud focused on addressing his lower back pain. Charles’s doctor, care coordinator, wife, and other caregivers are part of his care team (Case Team), along with Charles himself. Other users (with appropriate permissions) can easily view Charles’s EHR data and his medical history within Health Cloud, giving them a 360-degree view of the patient.
Charles has reported that his back pain is keeping him awake at night (Care Plan Problem). That’s a significant issue that the care team would like to solve for Charles. His care coordinator sets a goal to reduce Charles’s overnight pain (Care Plan Goal). Charles’s doctor recommends that he does some stretching exercises before bedtime (Task) to help alleviate his pain so he can get some sound sleep.
This diagram shows how Charles’s lower back pain condition maps with the packaged clinical data model in Health Cloud.
And here’s a look at the records, objects, and relationships in the packaged clinical data model based on Charles’s lower back pain condition.
|Type of Record||Object Relationships|
|Charles’s Back Pain Care Plan (Case)||Charles Green—Patient (Person Account)|
|Charles’s Back Pain Care Team (Case Team)||Charles’s Back Pain Care Plan (Case)|
|Pain Disrupts Sleep (Care Plan Problem)||Charles’s Back Pain Care Plan (Case)|
|Reduction in Overnight Pain (Care Plan Goal)||Charles’s Back Pain Care Plan (Case)|
|Reduction in Overnight Pain (Care Plan Goal)||Pain Disrupts Sleep (Care Plan Problem)|
|Evening Stretching Routine (Task)||Reduction in Overnight Pain (Care Plan Goal)|
|Flu Shot—Oct 2019 (EHR Immunization)||Charles Green (Person Account)|
|Specialist—Ortho (EHR Encounter)||Charles Green (Person Account)|
|Diabetes Diagnosis (EHR Condition)||Charles Green (Person Account)|
|…additional EHR objects||Charles Green (Person Account)|
Now you’ve learned about the Health Cloud packaged clinical data model, including care plans, care plan problems, care plan goals, tasks, care teams, and information captured from electronic health records. Next, look at the health insurance and claims data model for insights on Charles’s insurance information, claims information, preauthorizations, and coverage benefits.