---
schema_version: "1"
id: ab03bf093e73c4530795d2c5f5dd7bf2da2a7a982be31451b44ab28dbdb939cc
title: Clinical Data Model
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/life_sciences_dev_guide/hc_clinical_data_model.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/hc_clinical_data_model.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 5fbced23f4c041a1ac315dea819dac17d6d06e37154cd0db418e82385fb182aa
description: Patient data and healthcare records are important in the healthcare industry. Without accurate information, performing and managing care becomes difficult. These records are readily available if a patient seeks care from the same provider every time. However, in reality, a patient’s healthcare journey takes them to multiple providers and hospitals at different times. Because the patient’s health hinges on the accuracy of their medical records, it’s crucial for the systems used by different providers and hospitals to be interoperable. And to make this interoperability possible, it’s vital to have some industry-recognized standards for how these records are structured, stored, and transferred. That’s where the standards defined by Health Level 7 (HL7) come in.
---
# Clinical Data Model

Patient data and healthcare records are important in the healthcare industry. Without accurate information, performing and managing care becomes difficult. These records are readily available if a patient seeks care from the same provider every time. However, in reality, a patient’s healthcare journey takes them to multiple providers and hospitals at different times. Because the patient’s health hinges on the accuracy of their medical records, it’s crucial for the systems used by different providers and hospitals to be interoperable. And to make this interoperability possible, it’s vital to have some industry-recognized standards for how these records are structured, stored, and transferred. That’s where the standards defined by Health Level 7 (HL7) come in.

<table class="editionTable" border="0" summary="Salesforce editions needed for the documented functionality" width="100%"><tbody class="tbody"><tr><td class="subHead">Available in: <strong class="ph b">Enterprise</strong> and <strong class="ph b">Unlimited</strong> Editions</td></tr></tbody></table>

  

Two standards defined by HL7 for this purpose are the Fast Health Interoperability Resources (FHIR) v4.0 and HL7 (the standard) 2.3. The Clinical Data Model is built from the ground up to align with FHIR v4.0, and also supports many of the HL7 v2.3 message types.

To enable these objects in your org, go to **FHIR R4 Support Settings** in **Setup** and enable the **FHIR-Aligned Clinical Data Model** org pref.

![Note](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/images/icon_note.png)

#### Note

Some of these objects are available in your org even before enabling this org pref because they’re part of other data models in Health Cloud and Life Sciences Cloud.

![Note](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/images/icon_note.png)

#### Note

To use the Clinical Data Model objects on an Experience Cloud site, community users need the FHIR R4 for Experience Cloud Sites permission set.

Here’s the list of objects that need the org pref to be enabled versus a list of objects that don’t require the org pref.

<table class="featureTable sort_table" summary="">


        <thead class="thead sorted" align="left">
          <tr>
            <th class="featureTableHeader  " id="d33738e89">Org Pref Required</th>

            <th class="featureTableHeader  " id="d33738e92">Org Pref Not Required</th>

          </tr>

        </thead>

        <tbody class="tbody">
          <tr>
            <td class="entry" headers="d33738e89" data-title="Org Pref Required">
              <ul class="ul bulletList">
                <li class="li">AllergyIntolerance</li>

                <li class="li">CarePerformer</li>

                <li class="li">ClinicalAlert</li>

                <li class="li">ClinicalEncounter</li>

                <li class="li">ClinicalEncounterDiagnosis</li>

                <li class="li">ClinicalEncounterFacility</li>

                <li class="li">ClinicalEncounterIdentifier</li>

                <li class="li">ClinicalEncounterProvider</li>

                <li class="li">ClinicalEncounterReason</li>

                <li class="li">ClinicalEncounterSvcRequest</li>

                <li class="li">ClinicalServiceRequest</li>

                <li class="li">ClinicalServiceRequestDetail</li>

                <li class="li">DiagnosticSummary</li>

                <li class="li">HealthCondition</li>

                <li class="li">MedicationRequest</li>

                <li class="li">MedicationStatement</li>

                <li class="li">PatientHealthReaction</li>

                <li class="li">PatientImmunization</li>

                <li class="li">PatientMedicalProcedure</li>

                <li class="li">PatientMedicalProcedureDetail</li>

                <li class="li">PatientMedicationDosage</li>

              </ul>

            </td>

            <td class="entry" headers="d33738e92" data-title="Org Pref Not Required">
              <ul class="ul bulletList">
                <li class="li">CareObservation</li>

                <li class="li">CareObservationComponent</li>

                <li class="li">CareObservationDetail</li>

                <li class="li">CareProviderFacilitySpecialty</li>

                <li class="li">CodeSet</li>

                <li class="li">CodeSetBundle</li>

                <li class="li">HealthcareFacility</li>

                <li class="li">HealthcarePractitionerFacility</li>

                <li class="li">HealthcareProvider</li>

                <li class="li">HealthPlanFacilityNetwork</li>

                <li class="li">HealthPlanFormularyItem</li>

                <li class="li">Identifier</li>

                <li class="li">Medication</li>

                <li class="li">Medication Administration</li>

                <li class="li">Medication Administration Detail</li>

                <li class="li">OpportunityProductCategory</li>

                <li class="li">PersonLanguage</li>

                <li class="li">PersonName</li>

                <li class="li">Problem Definition Relationship</li>

                <li class="li">Specimen</li>

              </ul>

            </td>

          </tr>

        </tbody>

      </table>

And here’s the list of fields added to standard objects when you enable this org pref.

- ContactPointPhone.PreferenceRank
- ContactPointPhone.UsageType
- ContactPointEmail.PreferenceRank
- ContactPointEmail.UsageType
- ContactPointAddress.PreferenceRank
- ContactPointAddress.UsageType
- Account.IsActive
- Account.EffectiveDate
- Account.SourceSystemIdentifier
- Account.SourceSystemModifiedDate
- Account.EndDate
- Contact.MaritalStatus
- Contact.Gender
- Contact.DeceasedDate
- Contact.SequenceInMultipleBirth

![Note](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/images/icon_note.png)

#### Note

- Starting with the Spring ’23 release, new customers won’t be able to create records in the packaged EHR objects that have counterpart standard objects in the FHIR R4-aligned data model.
- All future development will be built on the FHIR R4-aligned data model. The packaged objects in the EHR data model won’t be used for future development.