Salesforce Health Cloud Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Health Cloud Developer Guide
Health Cloud Data Model
Advanced Therapy Management
Adverse Events
Assessment Generation
Benefits Verification
Care Program Management
Claims
Clinical Data Model
Predecessors to Code Sets and Code Set Bundles in Health Cloud
Coverage Requirement Discovery
Crisis Support Center Management
Documentation Templates and Rules
Disease Surveillance
Electronic Signatures
Engagement Interaction
FHIR Subscription
Financial Assistance Program
Health Assessments
Health Insurance
Home Health
Integrated Care Management
Intelligent Appointment Management
Intelligent Document Automation
Intelligent Sales
Medication Management
Patient Program Outcome Management
Participant Management
Patient Segmentation
Pharmacy Benefits Verification
Provider Network Management
Provider Relationship Management
Remote Monitoring and Device Registration
Social Determinants
Timeline
Unified Health Scoring
Utilization Management
CareDiagnosis
CareProcessingError
CareRequest
CareRequestDrug
CareRequestExchangeInfo
CareRequestExtension
CareRequestItem
CareRequestReviewer
CareRequestSupportingCntnt
TrackedCommunication
TrackedCommunicationDetail
Health Cloud Associated Objects
Health Cloud Fields on Standard Objects
Working With Electronic Health Records
Emergency Response Management
Apex Reference
Health Cloud Business APIs
Health Cloud Tooling API Objects
Health Cloud Standard Invocable Actions
Metadata Types
API End-of-Life Policy
PDF

CareProcessingError

Stores information on processing errors sent from payer to provider on a member’s authorization request. This object is available in API version 58.0 and later.

Supported Calls

create(), delete(), describeLayout(), describeSObjects(), getDeleted(), getUpdated(), query(), retrieve(), search(), undelete(), update(), upsert()

Fields

Field Details
ActionCodeId
Type
reference
Properties
Create, Filter, Group, Nillable, Sort, Update
Description
The code that's associated with the resolution of the error that occurred when processing an authorization request.
This field is a polymorphic relationship field.
Relationship Name
ActionCode
Relationship Type
Lookup
Refers To
CodeSet, CodeSetBundle
Description
Type
string
Properties
Create, Filter, Group, Sort, Update
Description
The description of the error.
ErrorCodeId
Type
reference
Properties
Create, Filter, Group, Sort, Update
Description
The code that's associated with the error that occurred when processing an authorization request.
This field is a polymorphic relationship field.
Relationship Name
ErrorCode
Relationship Type
Lookup
Refers To
CodeSet, CodeSetBundle
LastModifiedById
Type
dateTime
Properties
Filter, Nillable, Sort
Description
The ID of the user who last updated the record.
LastModifiedDate
Type
dateTime
Properties
Filter, Nillable, Sort
Description
The most recent date on which a user updated the record.
Name
Type
string
Properties
Autonumber, Defaulted on create, Filter, idLookup, Sort
Description
The name of the care processing error.
OwnerId
Type
reference
Properties
Create, Defaulted on create, Filter, Group, Sort, Update
Description
The ID of the user who owns this record.
This field is a polymorphic relationship field.
Relationship Name
Owner
Relationship Type
Lookup
Refers To
Group, User
ReferenceObjectId
Type
reference
Properties
Create, Filter, Group, Sort, Update
Description
The object that's associated with the error.
This field is a polymorphic relationship field.
Relationship Name
ReferenceObject
Relationship Type
Lookup
Refers To
CareDiagnosis, CareRequest, CareRequestDrug, CareRequestItem

Usage

When payer receives an authorization request from the provider, they review and validate the request details. If an error occurs during the request processing, payer must create appropriate care processing error records with reference to the care request record. This error information is sent to the provider as part of the request response. Alternatively, payers can also automate the record creation by configuring a flow that’s triggered whenever an authorization request is received in the payer system. The flow validates the care request record, identifies any error, and creates appropriate care processing error records to be sent to the provider.

Associated Objects

This object has the following associated objects. If the API version isn’t specified, they’re available in the same API versions as this object. Otherwise, they’re available in the specified API version and later.

CareProcessingErrorChangeEvent (API Version 63.0)
Change events are available for the object.
CareProcessingErrorFeed
Feed tracking is available for the object.
CareProcessingErrorHistory
History is available for tracked fields of the object.
CareProcessingErrorShare
Sharing is available for the object.