Benefits Verification Request

This is what a Verify Benefits request looks like.

Properties 
NameTypeDescriptionRequired or OptionalAvailable Version
encounterDateStringEncounter Date 53.0
memberAccountIdStringMember Account Id 53.0
memberPlanIdStringMember Plan Id 53.0
providerNpiStringProvider Npi 53.0
providerOrganizationNameStringProvider Organization Name 53.0
providerTypeStringProvider Type 53.0
serviceTypeCodesString[]Service Type Codes 53.0

See Also

Life Sciences Cloud Developer Guide
Life Sciences Cloud Data Models
Life Sciences Cloud Standard Objects
Life Sciences Cloud Associated Objects
Life Sciences Cloud Fields on Standard Objects
StandardValueSet Names and Standard Picklist Fields
Life Sciences Cloud Platform Events
Working With Electronic Health Records
Life Sciences Cloud Business APIs
Resources
Account Management
Account Manual Alignment
Account User Territory Information (POST)
Advanced Provider Search
Book Slot Chain (POST)
Contact Encounter (POST)
Content Management
Care Program Enrollments (POST)
Digital Verification (POST)
Download Provider (POST)
Benefit Verification
Benefits Verification (POST)
Benefits Verification Input
Benefits Verification Request
Benefits Verification Output
Benefits Verification Response
Intelligent Document Management
Patients (GET, POST, PUT)
Provider Engagement Action Plan Status
Provider Search
Providers
Sample Limits Validation (POST)
Visits (POST)
Waterfall Download (POST)
Work Type Lead Time (POST)
Request Bodies
Response Bodies
Apex Reference
Life Sciences Cloud Standard Invocable Actions
Life Sciences Cloud Tooling API Objects
Life Sciences Cloud Metadata Types
API End-of-Life Policy
Previous Versions