# Create or Update Batch CareCaseClinicalTrial Create or Update multiple CareCaseClinicalTrial at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /care-case-clinical-trials-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Request fields (application/json): - `careCaseClinicalTrial_Key` (integer, required) Identifier for the Clinical Trial Note: The database will apply a default value of 0 for this field if a value is not provided. This field is also marked as NOT NULL in the database and therefore required by the API. If you do not have a value for this field, supply the database default value of 0 to meet the API requirements and ensure that the functionality occurs as expected. - `careCaseClinicalTrialArm_ID` (string,null) User Managed field that ties to the Clinical Trial Arm in the system - `careCaseClinicalTrialReason_ID` (string,null) User Managed field that ties to the Clinical Trial Reason in the system. - `careCaseClinicalTrialStudyPhase_ID` (string,null) User Managed field that ties to the Study Phase in the system - `case_Key` (integer,null) Identifier of the case. - `comment` (string,null) User Managed field that displays the Comment of this Clinical Trial - `disease` (string,null) User Managed field that displays the Disease of this Clinical Trial - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `inclusionExclusion` (string,null) User Managed field that displays the Inclusion Exclusion of this Clinical Trial - `location` (string,null) User Managed field that displays the Location of this Clinical Trial - `protocol_Number` (string,null) User Managed field that displays the Protocol Number of this Clinical Trial - `study_Drug` (string,null) User Managed field that displays the Study Drug of this Clinical Trial - `study_Length` (string,null) User Managed field that displays the Study Length of this Clinical Trial - `study_Title` (string,null) User Managed field that displays the Study Title of this Clinical Trial - `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 - `website` (string,null) User Managed field that displays the Website of this Clinical Trial ## 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` (string,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