Salesforce Health Cloud Developer Guide
jNewer Version Available
Condition
The Condition FHIR resource maps to the HealthCondition object in Salesforce.
FHIR V4.0 - Clinical Data Model Mapping
Here’s how the fields defined by FHIR for Condition map to the fields in Salesforce.
| Condition Resource | Salesforce Field | Type | Salesforce Cardinality | Notes |
|---|---|---|---|---|
| identifier | Identifier | Object | 0.M | The identifier information for a health condition is represented as Identifier records that reference the health condition record using their Identifier.ParentRecordId field. |
| clinicalStatus | HealthCondition.ConditionStatus | Picklist | 0.1 | While FHIR defines Condition.clinicalStatus as a code set bundle, the Salesforce implementation of HealthCondition.ConditionStatus is picklist. |
| verificationStatus | HealthCondition.DiagnosticStatus | Picklist | 0.1 | While FHIR defines condition.verificationStatus as a code set bundle, the Salesforce implementation of HealthCondition.DiagnosticStatus is picklist. |
| category | HealthCondition.Type | Picklist | 0.1 | While FHIR defines Condition.category as a zero-to-many code set bundle, the Salesforce implementation of HealthCondition.Categories is a zero-to-one picklist. |
| severity | HealthCondition.Severity | Picklist | 0.1 | While FHIR defines condition.severity as a code set bundle, the Salesforce implementation of HealthCondition.Severity is picklist. |
| code | HealthCondition.ConditionCodeId | Lookup: CodeSetBundle | 1.1 | While FHIR defines condition.code as a zero-to-one resource, the Salesforce implementation is a one-to-one field. |
| bodySite | HealthCondition.SiteId | Lookup: CodeSetBundle | 0.1 | While FHIR defines Condition.bodySite as a zero-to-many resource, the Salesforce implementation of HealthCondition.Site is a zero-to-one reference. |
| subject | HealthCondition.PatientId | Master-Detail Reference: Account | 1.1 | The Salesforce implementation of Condition.subject doesn’t support groups. |
| encounter | HealthCondition.ClinicalEncounterId | Lookup: Encounter | 0.1 | N/A |
| onset.onsetDateTime | HealthCondition.OnsetStartDateTime | DateTime | 0.1 | HealthCondition.OnsetStartDateTime is used as both the equivalent of condition.onset.onsetDateTime and the start date of condition.onset.onsetPeriod |
| onset.onsetAge | N/A | N/A | N/A | Not supported |
| onset.onsetPeriod | HealthCondition.OnsetStartDateTime | DateTime | 0.1 | Since Salesforce doesn’t natively support the period data type, condition.onset.onsetPeriod is flattened into a set of start date and end date fields. The start date field is also used as the equivalent of condition.onset.onsetDateTime |
| HealthCondition.OnsetEndDateTime | DateTime | 0.1 | ||
| onset.onsetRange | N/A | N/A | N/A | Not supported |
| onset.onsetString | N/A | N/A | N/A | Not supported |
| abatement.abatementDateTime | HealthCondition.AbatementStartDateTime | DateTime | 0.1 | HealthCondition.AbatementStartDateTime is used as both the equivalent of condition.abatement.abatementDateTime and the start date of condition.abatement.abatementPeriod |
| abatement.abatementAge | N/A | N/A | N/A | Not supported |
| abatement.abatementPeriod | HealthCondition.AbatementStartDateTime | DateTime | 0.1 | Since Salesforce doesn’t natively support the period data type, condition.abatement.abatementPeriod is flattened into a set of start date and end date fields. The start date field is also used as the equivalent of condition.abatement.abatementDateTime |
| HealthCondition.AbatementEndDateTime | DateTime | 0.1 | ||
| onset.abatementRange | N/A | N/A | N/A | Not supported |
| onset.abatementString | N/A | N/A | N/A | Not supported |
| recordedDate | HealthCondition.RecordCreationDateTime | DateTime | 0.1 | N/A |
| recorder | HealthCondition.RecordCreatorId | Polymorphic Lookup: Account, Healthcare Provider | 0.1 | N/A |
| asserter | HealthCondition.AssertionSourceId | Polymorphic Lookup: Account, Healthcare Provider | 0.1 | N/A |
| stage | HealthCondition.StageId | Lookup: CodeSetBundle | 0.1 | The child resources of condition.stage is combined into a single code set bundle reference field. While FHIR defines condition.stage as a zero-to-many resource, the Salesforce implementation is a zero-to-one field. |
| evidence | N/A | N/A | N/A | Not supported |
| note | N/A | N/A | N/A | Not supported |