The clinical data model
Health Cloud aligns to HL7 FHIR R4. Core object mapping:
| FHIR resource | Health Cloud object |
|---|---|
| Patient | Account (Person Account) / Individual |
| Practitioner | User + HealthcareProvider |
| Encounter | ClinicalEncounter |
| Observation | ClinicalServiceRequest + Observation |
| Condition | HealthCondition |
| MedicationRequest | MedicationStatement |
| CarePlan | CarePlan + CarePlanGoal + CareBarrier |
FHIR integration pattern
EHR (Epic / Cerner / Athena)
├─ FHIR API (R4)
└─► MuleSoft FHIR Accelerator
├─► Health Cloud ingest (Bulk FHIR)
└─► Data Cloud (unified patient index)
└─► Segmentation → Marketing Cloud (patient outreach)
Bulk FHIR ($export) is the batch path — 24h refresh. Use CDS Hooks + SMART on FHIR for real-time chart integration.
Consent management
Every write must honor Consent records — HIPAA + state laws + Common Rule for research.
Consent
Purpose: TREATMENT | PAYMENT | OPERATIONS | RESEARCH | MARKETING
Status: Active
Scope: Patient A, Data category = Behavioral Health
Effective: 2026-01-15 → 2027-01-15
Enforce with a Consent-aware Apex service layer — never let a Flow write without checking.
Care plans that actually get used
Model evidence-based care pathways as Care Plan Templates. On enrollment, the template instantiates goals + tasks per patient:
Template: Type 2 Diabetes Management
Goal: A1c < 7.0 within 6 months
Task: Weekly glucose upload (patient app)
Task: Quarterly A1c lab
Task: Nutrition consult (30d, 90d)
Barrier: Food insecurity → route to social work
Population health
Combine with Data Cloud for cohort analytics:
SELECT p.Id, MAX(o.EffectiveDate) AS last_a1c, MAX(o.Value) AS a1c
FROM Patient__dlm p
JOIN Observation__dlm o ON o.PatientId = p.Id AND o.Code = 'LOINC:4548-4'
WHERE o.Value > 8.0
GROUP BY p.Id
Push high-risk cohort to Care Manager task queue via a Data Action.
Interoperability standards
- US Core Data for Interoperability (USCDI v3) — minimum data set
- SMART on FHIR — auth for third-party apps at the point of care
- CDS Hooks — decision support pop-ups in the EHR chart
- CARIN Blue Button — patient data export
Security & compliance
- Business Associate Agreement (BAA) — required before touching PHI
- Shield Platform Encryption on all PHI fields
- Field Audit Trail (10y) on Diagnosis, Medication, Consent
- Break-the-glass workflow for emergent access, logged to SIEM
Health CloudHealthcareFHIR