Gathering EHR integration and interoperability requirements
Key Takeaway
During discovery, capture the exact HL7 version each partner system uses: one path on a newer HL7v2 version can accept older HL7v2 messages, but HL7v3 needs its own path.
Agentforce Health often needs to exchange patient, clinical, and coverage data with Electronic Health Record (EHR) systems and payer systems. During discovery, you find out which systems, standards, and workflows the customer must connect, so the design uses the right FHIR R4-aligned data model and the right prebuilt integration tools.
What interoperability depends on
Interoperability matters because a patient's care journey takes them to many providers and hospitals at different times. Interoperability depends on two things: APIs that move data between applications, and shared industry standards for how records are structured, stored, and transferred.
Salesforce supports common APIs such as REST, SOAP, Bulk, and Streaming. Salesforce also has API-enabled fields for synchronous or asynchronous flows.
For reuse, the recommended direction is away from point-to-point integration and toward orchestration services that use APIs to bring data, devices, and applications together.