Clinical Data Model

Patient data and healthcare records are very important in the healthcare industry. Without accurate information, performing and managing care becomes extremely 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 is 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. 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 Data Model org pref.

And here’s the list of Health Cloud 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.EndDate
• Contact.MaritalStatus
• Contact.Gender
• Contact.DeceasedDate
• Contact.SequenceInMultipleBirth