EHR clinical data integration into the FHIR-aligned clinical data model
Key Takeaway
Use middleware to convert HL7 v2.3 and FHIR R4 messages from the EHR, then map them into the standard objects of the FHIR R4-aligned clinical data model. A many-valued attribute, such as several providers on one encounter, is stored as child records that each reference the parent encounter.
Clinical data from an electronic health record (EHR) or other clinical system is critical to planning, running and managing coordinated care plans for patients. Examples are encounters, conditions, medications and allergies. Agentforce Health stores this data in the clinical data model, which is built to align with the FHIR R4 standard. EHR messages can then be mapped into standard Salesforce objects and fields instead of custom structures. A middleware layer converts the messages, and the consultant's design work is deciding which object each EHR message lands in.
The standards behind the model
Health Level Seven (HL7) sets industry standards for how providers structure, store and transfer medical records, so systems at different providers and facilities can work together. HL7 defines two such standards. FHIR (Fast Healthcare Interoperability Resources) is an open API standard for exchanging healthcare information. The other standard is the HL7 messaging standard.
The clinical data model is built to align with FHIR R4, specifically FHIR v4.0.1. The model also supports many HL7 v2.3 message types. HL7 v2.3 is the predecessor of FHIR, so a model that aligns with FHIR is also compatible with HL7 v2.3.