# Create or Update Batch FeeSchedProcedureGroupAdjust

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

Endpoint: PUT /fee-schedule-procedure-group-adjustments-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Request fields (application/json):

  - `feeSchedProcedureGroupAdjust_Key` (integer, required)
    Unique identifier assigned to the procedure group adjustment.  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.

  - `adjust_Pct` (number,null)
    Percentage that the service line will be adjusted after it has been priced by the ‘Fee Schedule’.

  - `adjust_Repeat` (integer,null)
    Number of times the associated rule will be applied before moving onto the next sequence.

  - `adjust_Rule` (string,null)
    [doesn't exist]

  - `adjust_Seq` (integer, required)
    Sequential identifier that determines the order of adjudication for each rule. (Seq. 01 will be applied first and so forth.)  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.

  - `effective_Date` (string, required)
    Date when the adjustment will begin/began applying to claims. This date will be compared to the date of service on the claim.

  - `entry_Date` (string)
    User that first added the record to the system.

  - `entry_User` (string,null)
    Date when the record was first added to the system.

  - `fee_Sched` (string, required)
    Unique name given to the Fee Scheudle.

  - `procedure_Code1` (boolean, required)
    Identifies which procedure code field within the claim that adjudication should attempt to match.  Note: The database will apply a default value of False 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 False to meet the API requirements and ensure that the functionality occurs as expected.

  - `procedure_Code2` (boolean, required)
    Identifies which procedure code field within the claim that adjudication should attempt to match.  Note: The database will apply a default value of False 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 False to meet the API requirements and ensure that the functionality occurs as expected.

  - `procedure_Group` (integer, required)
    Identifies the procedure group to which the associated rule will be applied.  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.

  - `update_Date` (string)
    User that last updated the record in the system.

  - `update_User` (string,null)
    Date when the record was last updated 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