# Create or Update Batch CareCase

Create or Update multiple CareCase at once.  If the entity exists, it will be updated.  If the entity does not exist, it will be created.

Endpoint: PUT /care-plans/{carePlanKey}/cases-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

  - `vbasoftware-database` (string, required)
    Target database

## Path parameters:

  - `carePlanKey` (integer, required)
    CarePlan Key

## Request fields (application/json):

  - `case_Key` (integer, required)
    Identifier of the case.

  - `appointment_Date` (string,null)
    User Managed field: Date of next Appointment

  - `assessment_Date` (string,null)
    User managed field: Date when the case was assessed.

  - `carePlan_Key` (integer, required)
    Identifies the type care associated with the case.

  - `case_Assign_Type` (string,null)
    Who or what Entity the Case was assigned to.

  - `case_End_Date` (string,null)
    Day when the case ended.

  - `case_ID` (string,null)
    Identifier of the case.

  - `case_Priority` (integer,null)
    Identifies the priority of the case. 'Case Priorities' are configured within 'Care Management Configuration'.

  - `case_Reason` (string,null)
    Identifies the reason of the case. 'Case Reasons' are configured within 'Care Management Configuration'.

  - `case_Score` (number,null)
    User Managed field used when Auto Assigning cases.

  - `case_Start_Date` (string,null)
    Day when the case began.

  - `case_Status` (string,null)
    Identifies the status of the case. 'Case Statuses' are configured within 'Care Management Configuration'.

  - `division_ID` (string,null)
    ID of the Division associated with the case.

  - `do_Not_Contact` (boolean, required)
    User Managed field for whether or not to contact member.

  - `eligibility_Verified` (string,null)
    User Managed field: Date elegibility verified

  - `eligibility_Verified_Comment` (string,null)
    User Managed field: Comment about Eligibility verification.

  - `case_Close_Reason` (string,null)
    The identifier of the case close reason.

  - `entry_Date` (string)
    Date record was first added to the system

  - `entry_User` (string,null)
    User that first added the record to the system

  - `group_ID` (string,null)
    ID of the Group associated with the case.

  - `member_Seq` (string,null)
    Sequential identifier of the Member associated with the case.

  - `provider_ID` (string,null)
    ID of the Provider associated with the case.

  - `subscriber_ID` (string,null)
    ID of the Subscriber associated with the case.

  - `update_Date` (string)
    Date the record was last updated in the system

  - `update_User` (string,null)
    User that last updated the record in the system

## Response 207 fields (text/plain):

  - `data` (array,null)

  - `data.id` (array, required)
    List of key/value pairs that represent the unique id for the entity operation.

  - `data.id.key` (string,null)

  - `data.id.value` (any,null)

  - `data.status` (integer, required)
    http status of the operation (eg, 200, 201, 500)

  - `data.body` (string, required)
    operation message (eg, Updated, Created, Error message)

  - `error` (object)

  - `error.detail` (string,null)
    A human-readable explanation specific to this occurrence of the problem.

  - `error.instance` (string,null)
    A URI reference that identifies the specific occurrence of the problem.It may
or may not yield further information if dereferenced.

  - `error.status` (integer)
    The HTTP status code([RFC7231], Section 6) generated by the origin server for
this occurrence of the problem.

  - `error.title` (string,null)
    A short, human-readable summary of the problem type.It SHOULD NOT change from
occurrence to occurrence of the problem, except for purposes of localization(e.g.,
using proactive content negotiation; see[RFC7231], Section 3.4).

  - `error.type` (string,null)
    A URI reference [RFC3986] that identifies the problem type. This specification
encourages that, when dereferenced, it provide human-readable documentation for
the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member
is not present, its value is assumed to be "about:blank".

  - `debug` (object)

  - `debug.activityID` (string, required)


## Response 401 fields