Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
AdverseEvent
The AdverseEvent FHIR resource maps to the
AdverseEvent objects in Salesforce.
FHIR V4.0 - Clinical Data Model Mapping
Here’s how the fields defined by FHIR for adverseEvent map to the fields in Salesforce.
| AdverseEvent Resource | Salesforce Field | Type | Salesforce Cardinality | Notes |
|---|---|---|---|---|
| status | AdverseEventEntry.Status | Dynamic Enum | 1.1 | While FHIR defines adverseEventEntry.status as a code set, the Salesforce implementation of AdverseEventEntry.Status is text. |
| actuality | AdverseEventEntry.Type | Dynamic Enum | 1.1 | While FHIR defines adverseEventEntry.actuality as a code set, the Salesforce implementation of AdverseEventEntry.type is dynamic enum. |
| category | AdverseEventEntry.Category | Picklist (Multi-Select) | 0.M | While FHIR defines adverseEventEntry.category as a code set bundle, the Salesforce implementation of AdverseEventEntry.Category is picklist (Multi-Select). |
| code | AdverseEventEntry.EventCode | Lookup: Code Set, Code Set Bundle | 0.1 | While FHIR defines adverseEventEntry.eventCode as a code set bundle, the Salesforce implementation of AdverseEventEntry.EventCode is a lookup. |
| subject | AdverseEventEntry.Subject | Polymorphic Lookup: CareProgramEnrollee, Account, TeamMember, CareProgramGroup, Team, HealthCareProvider | 1.1 | N/A |
| encounter | AdverseEventEntry.ClinicalEncounter | Lookup: Clinical Encounter | 0.1 | N/A |
| cause | AdverseEventEntry.CauseStartDateTime | Date/Time | 0.1 | Since Salesforce doesn’t natively support the period data type, adverseEvent.cause is flattened into a set of cause start date time and cause end date time fields. |
| AdverseEventEntry.CauseEndDateTime | Date/Time | 0.1 | ||
| effect | AdverseEventEntry.EventStartDateTime | Date/Time | 0.1 | Since Salesforce doesn’t natively support the period data type, adverseEvent.effect is flattened into a set of event start date time and event end date time fields. |
| AdverseEventEntry.EventEndDateTime | Date/Time | 0.1 | ||
| detected | AdverseEventEntry.DetectedDate | Date/Time | 0.1 | N/A |
| recordedDate | AdverseEventEntry.RecordedDate | Date/Time | 0.1 | N/A |
| resultingEffect | AdverseEventResultingEffect.Effect | Lookup: Health Condition, Care Observation | 1.1 | While FHIR defines adverseEventResultingEffect.resultingEffect as a zero-to-many resource, the Salesforce implementation of AdverseEventResultingEffect.Effect is one-to-many. |
| location | AdverseEventEntry.Location | Lookup: Healthcare Facility, Care Program Site | 0.1 | N/A |
| seriousness | AdverseEventEntry.Severity | Picklist | 0.1 | While FHIR defines adverseEventEntry.Severity as a code set bundle, the Salesforce implementation of AdverseEventEntry.Severity is picklist. |
| outcome | AdverseEventOutcome.OutcomeCode | Lookup: Code Set, Code Set Bundle | 1.1 | While FHIR defines adverseEventOutcome.outcome as a CodeSetBundle, the Salesforce implementation of AdverseEventOutcome.OutcomeCode is a lookup. |
| recorder | AdverseEventEntry.RecordedBy | Lookup: Account Care Program Enrollee | 1.1 | While FHIR defines adverseEventOutcome.recorder as a zero-to-many resource, the Salesforce implementation of AdverseEventOutcome.RecordedBy is one-to-one. |
| participant.function | AdverseEventParty.Role | Dynamic Enum | 0.1 | N/A |
| participant.actor | AdverseEventParty.Party | Lookup: Account, Contact, Care Program Enrollee, Healthcare Facility, Care Registered Device, Healthcare Practitioner Facility | 1.1 | N/A |
| expectedInResearchStudy | AdverseEventEntry.Expected | Boolean | 0.1 | N/A |
| suspectEntity.instance | AdverseEventCause.Cause | Lookup: Patient Immunization, Medication, Medication Statement, Research Study, Patient Medical Procedure, Care Registered Device | 1.1 | While FHIR defines adverseEventCause.suspectEntity.instance as a CodeSetBundle, the Salesforce implementation of AdverseEventCause.Cause is a lookup. |
| suspectEntity.causality.assessmentMethod | AdverseEventCause.AssessmentMethodCode | Lookup: CodeSet, CodeSetBundle | 0.1 | N/A |
| suspectEntity.causality.entityRelatedness | AdverseEventCause.Probability | Dynamic Enum | 0.1 | N/A |
| suspectEntity.causality.author | AdverseEventCause.AuthoredBy | Polymorphic Lookup: Account, Contact, User, HealthcareFacility, HealthcarePractitionerFacility, ResearchStudyParticipant | 0.1 | N/A |
| contributingFactor.item | AdverseEventContributingFactor.ContributingFactor | Polymorphic Lookup: HealthCondition, CareObservation, AllergyIntolerance, PatientImmunization, CareRegisteredDevice, Medication, MedicationStatement, DiagnosticSummary, PatientMedicalProcedure, MedicationAdministration | 1.M | While FHIR defines adverseEventContributingFactor.contributingFactor.item as a zero-to-many resource, the Salesforce implementation of AdverseEventContributingFactor.ContributingFactor is one-to-many. |
| preventiveAction.item | AdverseEventAction.ActionCode | Polymorphic Lookup: CodeSet, CodeSetBundle | 0.1 | While FHIR defines adverseEventAction.preventiveAction.item as a one-to-one resource, the Salesforce implementation of AdverseEventAction.ActionCode is zero-to-one. |
| mitigatingAction.item | AdverseEventAction.ActionCode | Polymorphic Lookup: CodeSet, CodeSetBundle | 0.1 | While FHIR defines adverseEventAction.mitigatingAction.item as a one-to-one resource, the Salesforce implementation of AdverseEventAction.ActionCode is zero-to-one. |
| supportingInfo.item | AdverseEventSupportingInformation.SupportingInformation | Polymorphic Lookup: HealthCondition, CareObservation, AllergyIntolerance, PatientImmunization, DiagnosticSummary, Medication, MedicationStatement | 1.1 | N/A |