Mapping legacy clinical data to standard FHIR-aligned target objects

Key Takeaway

Legacy clinical data goes through a middleware integration solution into FHIR-aligned standard objects. Many of those objects exist only after the "FHIR-Aligned Clinical Data Model" org pref is enabled.

Agentforce Health stores clinical data from EHR and other clinical systems in a set of standard objects called the clinical data model. The model is built to align with the HL7 FHIR R4 standard (FHIR v4.0.1). Migrating legacy clinical data means mapping each source record and field to the right standard object and field. You also need to know where the Salesforce version of FHIR differs from the specification, because those differences change how the data maps.

What the clinical data model covers

The clinical data model has standard objects for clinical data such as conditions, medications, encounters, immunizations and procedures. Besides aligning with FHIR v4.0.1, the model supports many HL7 v2.3 message types. The model is available in Enterprise and Unlimited Editions with Agentforce Health.

Salesforce Accredited Agentforce Health Professional Study Guide

Checklist progressProgress

0/167Learned

Checklist progressProgress

0/167Learned

Given customer requirements, determine how to create the solution for Agentforce Health features according to best practices

0/2

Given customer requirements, understand how to model patients, providers, healthcare facilities, etc., using the appropriate Agentforce Health objects

0/14

Given customer requirements, determine how to create the proper application solution design leveraging Agentforce Health best practices

0/5

Given customer requirements, determine when to use specific Agentforce Health capabilities

0/8

Given customer requirements, determine how to create the design solution for a specific Agentforce Health vertical to meet those requirements

0/6

Given the business processes/requirements, determine how to create the solution design utilizing best practices and Agentforce Health modules

0/5

Given a customer's business objectives and goals, define success-metrics/KPIs and configure Salesforce to enable reporting on these metrics

0/5

Given a customer's security/compliance requirements, design and implement the appropriate organizational security and data access considerations

0/8

Given a customer's external systems and data requirements, determine the optimal integration strategy for the customer's Salesforce org

0/7

Given a customer's business requirements, design the future state business processes

0/4

Given the data requirements, create a migration strategy considering the legacy /future state system landscape ensuring accuracy and integrity

0/9

Systems of record across the legacy and future-state health landscape

Learn this concept

Migration strategy, historical data scope and go-live cutover

Learn this concept

Mapping legacy clinical data to standard FHIR-aligned target objects

Learn this concept

Data cleansing and duplicate prevention for patient and provider loads

Learn this concept

External IDs and upsert for retaining legacy identifiers

Learn this concept

Load sequencing for provider, facility, and clinical record relationships

Learn this concept

Choosing a data load tool for health data volume and complexity

Learn this concept

Integrity controls during bulk legacy loads

Learn this concept

Trial loads, validation, and reconciliation before production migration

Learn this concept

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Salesforce Accredited Agentforce Health Professional studiers.

Go to Discord

Mapping legacy clinical data to standard FHIR-aligned target objects