Clinical objects for conditions, medications and diagnostic results
Key Takeaway
Each kind of clinical fact has its own object: Health Condition for diagnoses, Medication Request for prescriptions, Medication Statement for medication history and Diagnostic Summary for test findings.
The clinical data model is a set of standard Agentforce Health objects that store a patient's clinical data from an EHR, such as conditions, medications and test results. A consultant needs to know which object holds each kind of clinical fact and how those objects link back to the patient's visit.
What the clinical data model holds
The data reaches these objects from external EHR systems through integration. The patient is represented as a person account.
The objects align with the FHIR R4 (v4.0.1) healthcare standard, so data from different providers and systems maps into the same objects. They also support many HL7 v2.3 message types, so each EHR message can be mapped to the correct object.
The clinical data model supports most FHIR R4 attributes but leaves out some that typical users don't need. Identifier and Code Set have extra attributes beyond their FHIR R4 versions, so they can be reused across the Salesforce platform.
Starting with Spring '23, new customers can't create records in the older packaged EHR objects that have a counterpart standard object in the clinical data model. All future development is built on the clinical data model, so new designs should use the standard clinical objects.