---
schema_version: "1"
id: e4afcd84fd3ea89710f649358ea8a2f0e419cc2eb5bda54f8c81cb1afd5800b5
title: The Clinical Data Model and FHIR
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/admin_clinical_data_model_fhir.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.admin_clinical_data_model_fhir.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6ba8ad07d2df7458705920b26927475fd287523f45524a0655001ef537b15dcb
description: The clinical data model is built to align with the Fast Healthcare Interoperability Resources (FHIR) specification, which is an open API standard for the exchange of healthcare information. The FHIR standard is defined by Health Level 7 (HL7), the organization that also defined the HL7 messaging standard.
products:
  - Health
release: "264"
---
# The Clinical Data Model and FHIR

The clinical data model is built to align with the Fast Healthcare Interoperability Resources (FHIR) specification, which is an open API standard for the exchange of healthcare information. The FHIR standard is defined by Health Level 7 (HL7), the organization that also defined the HL7 messaging standard.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: Lightning Experience</p>
            <p style="margin-bottom:0;">Available in: <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions with Health
              Cloud</p>
          </td>

        </tr>
      </tbody>
    </table>

The standard objects in the clinical data model store all sorts of clinical data, including conditions, medications, encounters, immunizations, procedures, and so on. To use the FHIR-aligned clinical data model, you must have Health Cloud. The Health Cloud implementation of FHIR aligns with FHIR v4.0.1.

To verify the FHIR (Fast Healthcare Interoperability Resources) R4-aligned clinical data model for Health Cloud is enabled in your org, search for and then select **FHIR R4 Support Settings** under Health Cloud in Setup. If the **FHIR-Aligned Data Model** setting is not enabled for your org, enable it now.

From the FHIR R4 Support Settings page, you can also enable **Adverse Events** to give users access to the Adverse Events features and objects. Adverse Events helps you to manage and document any unfavorable or unintended signs, symptoms, or diseases that occur as a result of an intervention, such as medical care or research, that impacts a patient or group of patients or participants. These events can include a wide range of physical or psychological effects that vary from mild discomfort to serious health complications.

## The FHIR-Aligned Clinical Data Model

Health Cloud’s clinical data model maps closely to the FHIR R4 specification, but with a few minor differences.

- The clinical data model supports most of the FHIR R4 attributes, except certain instances that aren’t relevant for the typical Health Cloud user.
- Entities like Identifier and Code Set have more attributes than their FHIR R4 counterparts. These extra fields increase data usability across the Salesforce platform and support specific needs of certain features in Health Cloud.
- FHIR R4 typically defines zero-to-one, zero-to-many, one-to-one, or one-to-many values for each attribute. However, the Salesforce platform doesn’t support one-to-many and zero-to-many values for a field, except in multi-select picklists. Instead, Salesforce uses child objects that can create multiple records that all reference the same parent record to achieve this type of logical zero/one-to-many values. For instance, an encounter can have multiple providers participating in it. To support this scenario, Salesforce has the Clinical Encounter Provider child object. This child object has records representing each provider in an encounter, and each of these records references the record of the encounter that these providers were a part of.

#### See Also

- [Developer Guide: Clinical Data Model](https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/hc_clinical_data_model.htm)
- [Developer Guide: Adverse Events](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/lsc_adverse_event.htm)
- [Developer Guide: Mapping FHIR R4 to Salesforce Standard Objects](https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/map_fhir_overview.htm)
- [Understand Which FHIR Objects Need Custom Report Types](https://help.salesforce.com/s/articleView?id=ind.hc_understand_which_fhir_objects_need_custom_rt.htm&release=264.0.0&type=5 "To report on Health Cloud data stored in some FHIR objects, create custom report types.")