Systems of record across the legacy and future-state health landscape
Key Takeaway
Know which system owns each kind of data. When several EHRs feed one Agentforce Health view, keep the data accurate by mapping EHR messages to Clinical data model objects, using code sets for shared definitions, and running identity resolution on duplicate patient records.
Patient data is usually spread across EHRs and other clinical systems. A migration plan for Agentforce Health has to show which system owns each kind of data and how Agentforce Health will get it. The plan matters because inconsistent data across systems costs time and money. Inconsistent data also erodes user trust, which can lead to adoption issues.
Four roles a system can play
Organizations use a system of record for compliance, auditing, and historical data accuracy.
A system of reference matters most when different systems of record own different pieces of data. A system of record is where data is created and officially kept, but a system of reference is where users go to access the authoritative data.
A clinic's lab system creates test results and keeps the official version, so it is the system of record for results. The clinic's scheduling system plays the same role for appointments. Staff don't want to check two systems, so the clinic gives them a system of reference: one place to look up authoritative results and appointments.
Two other roles complete the picture. A system of intelligence supports decisions with AI, machine learning, and analytics. A system of engagement is an access point that interacts directly with users, such as in customer or employee interactions.