---
schema_version: "1"
id: ac1cfbcd46eabe2073833e54f971465cc918d894fd10962723f7e37dd6ae9b5b
title: Care Services Review and Response
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/health_cloud_object_reference/hc_care_services_review_intro.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/hc_care_services_review_intro.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: a6af45d463e8bcf03236357d0eafbcb23cfa4cc1ddd68a8f6e54cbd1cee6ec4a
description: These RESTful APIs support data elements required for ANSI X12 278 format Health Care Services Review and Response. Also referred to as ANSI 278 Authorization APIs, they enable payer organizations to electronically receive prior authorization requests and referral requests from providers. Other users of these APIs can be healthcare providers, payers, plan sponsors, or other entities involved in health care services review, such as clearinghouses.
---
# Care Services Review and Response

These RESTful APIs support data elements required for ANSI X12 278 format Health Care Services Review and Response. Also referred to as ANSI 278 Authorization APIs, they enable payer organizations to electronically receive prior authorization requests and referral requests from providers. Other users of these APIs can be healthcare providers, payers, plan sponsors, or other entities involved in health care services review, such as clearinghouses.

  
<table class="permTable sort_table" border="0" summary="Permissions needed for the documented functionality" width="100%">


        <thead class="thead sorted" align="left">
          <tr>
            <th class="permTableHeader  " colspan="2" id="d335520e43">User Permissions Needed</th>

            <th class="permTableHeader  " colspan="2" id="d335520e46"></th>

          </tr>

        </thead>

        <tbody class="tbody">
          <tr>
            <td class="permRowLeft" headers="d335520e43" data-title="User Permissions Needed">To access care services APIs</td>

            <td class="permRowRight" headers="d335520e46" data-title="">Health Cloud Utilization Management Permission Set</td>

          </tr>

        </tbody>

      </table>

These APIs facilitate communication between two parties for the following cases:

- Appeals
- Drug Requests
- Admissions
- Healthcare Service Requests
- Referrals
- Complaints
- Grievances

[Care Services Review Requests (PATCH)](https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/hc_resource_care_services_review.htm#connect_resources_create_update_care_services_review "Update care services review requests or update existing requests.")

Depending on the type of care service review request (drug request, prior authorization, and so on), and the content of the request body, this API creates one or more records for Case, CareRequest, CareRequestExtension, CareRequestDrug, CareRequestItem, or CareRequestDiagnosis..

The following diagram shows what happens when you make a POST request to this API, to create a care services review request.

![Diagram explaining what happens when a care services review request is triggered.](https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/dev_guides/healthcare_api/images/hc_care_services_diagram.png)

[Care Services Review Requests (GET)](https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/hc_resource_care_services_review.htm#connect_resources_get_care_services "Get details of existing care services review requests.")

You can get Care Services Review Response for one or more care service review requests, by either using their Salesforce IDs or external source system IDs. Use section query parameter to have granular filters. Some examples of valid values in section are, Subscriber, Patient, CareDiagnoses, CareRequestItems, CareRequestDrugs, TransportLocations, CareRequest, or CareRequestCase.

- **[Care Services Review Resources](https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/hc_resource_care_services_review.htm#hc_resource_care_services_review)**  
    Use these resources to create or update care services review requests, or get information about the status of existing requests.

#### See Also

- [_Salesforce Help_: Handle Care Requests with Utilization Management](https://help.salesforce.com/articleView?id=utilization_management.htm&language=en_US "Salesforce Help: Handle Care Requests with Utilization
    Management - HTML (New Window)")
- [_Salesforce Help_: What is a Care Request?](https://help.salesforce.com/articleView?id=care_request.htm&language=en_US "Salesforce Help: What is a Care Request? - HTML (New Window)")
- [_Salsforce Help_: How Are Care Requests Reviewed?](https://help.salesforce.com/articleView?id=utilization_management_types.htm&language=en_US "Salsforce Help: How Are Care Requests Reviewed? - HTML (New Window)")
- [ANSI X12 278 - Request for Review and Response Examples](http://www.x12.org/examples/005010X217/ "ANSI X12 278 - Request for Review and Response Examples - HTML (New Window)")
- [_Salesforce Help_: Enable Person Accounts](https://help.salesforce.com/articleView?id=account_person_enable.htm&language=en_US "Salesforce Help: Enable Person Accounts - HTML (New Window)")