Agentforce Health Developer Guide

Agentforce Health Developer Guide
Health Cloud Data Model
Health Cloud Associated Objects
Health Cloud Fields on Standard Objects
Health Cloud Platform Events
Working With Electronic Health Records
Emergency Response Management
Apex Reference
Health Cloud Business APIs
REST Reference
Resources
Appointment Management
Assessment Previous Responses
Book Slot Chain (POST)
Care Services Review and Response
Contact Encounter (POST)
Care Program Enrollments (POST)
Census Bulk Upload Status (GET)
Document AI Automation
Digital Verification (POST)
Guest Referral
Identity Verification
Build Identity Verification Context
Identity Verification
Identity Verification Search
Insurance Product Comparison (POST)
Benefit Verification
Intelligent Appointment Management Operations
Intelligent Document Management
Medication Statements
Omniscript
Patients (GET, POST, PUT)
Providers
Referral Management
Unified Health Scoring
Visits (POST)
Work Type Lead Time (POST)
Quotas and Allocations
Request Bodies
Response Bodies
Health Cloud Tooling API Objects
Health Cloud Standard Invocable Actions
Metadata Types
Health Cloud FHIR APIs
MuleSoft Direct Integrations
API End-of-Life Policy
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Identity Verification

Use these resources to verify the caller's identity. For example, the call center agent can ask the person to confirm their social security number, birth date, insurance details, or driver’s license number.

The person contacting the call center could be a patient, a parent or guardian if the patient’s a minor, the authorized representative of a patient, or a provider. No matter who the caller is, if they want sensitive information, an agent must verify the caller’s identity first. If the inquiry concerns information in the public domain (for example, the location of a hospital), then verification isn’t required.

Available resources are:

Resource Description
/connect/identity-verification/build-context/${processDefinitionName} Build the context required to perform identity verification.
/connect/identity-verification/verification Verify the caller's identity.
/connect/identity-verification/search Search the Salesforce record to verify a caller’s identity.