# Update FeeSchedDetail

Updates a specific FeeSchedDetail.

Endpoint: PUT /fee-schedule-details/{feeSchedDetailKey}
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Path parameters:

  - `feeSchedDetailKey` (integer, required)
    FeeSchedDetail Key

## Request fields (application/json):

  - `feeSchedDetail_Key` (integer, required)
    Unique identifier for each Detail record on this Fee Schedule.  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.

  - `allowed_Over_Billed` (boolean, required)
    This option allows the ‘Fee Schedule’ to price above the billed amount.  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.

  - `always_Use_Rate` (boolean, required)
    This field is currently informational only.  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.

  - `billed_Pct` (number,null)
    Price based upon a percentage of the billed amount that will be applied to the matching claim detail record through the ‘Fee Schedule’.

  - `diag_Code` (string,null)
    Requires a matching diagnosis code on the claim for adjudication matching. Start of a range of diagnosis codes when combined with 'Diag Thru'.

  - `diag_Code_Thru` (string,null)
    End of the diagnosis range when combined with ‘Diag.’.

  - `diagnostic_Code_Type` (string, required)
    Indicates the ICD version associated with the selected Diagnosis Codes.

  - `drug_Code` (string,null)
    This will require a matching ‘Drug Code’ within a claim line during adjudication.

  - `effective_Date` (string, required)
    Date when the schedule should begin 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.

  - `ex_Code` (string,null)
    Applies the provided Ex Code to any claim that has been repriced by this ‘Fee Schedule Fee’.

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

  - `from_Age` (integer,null)
    Starting point for the range of acceptable ages for the Fee Schedule.

  - `from_Units` (integer,null)
    Starting point for the range of acceptable number of units within a claim for matching during adjudication.

  - `modifier` (string,null)
    Modifiers applicable to codes can be entered. Each of the modifiers can be applied to a single code or multiple codes in the line. Modifier payment reductions can be set up in ‘Fee Schedule Configuration’ and can be applied each time the modifier is included on a claim.

  - `modifier2` (string,null)
    Modifiers applicable to codes can be entered. Each of the modifiers can be applied to a single code or multiple codes in the line. Modifier payment reductions can be set up in ‘Fee Schedule Configuration’ and can be applied each time the modifier is included on a claim.

  - `modifier3` (string,null)
    Modifiers applicable to codes can be entered. Each of the modifiers can be applied to a single code or multiple codes in the line. Modifier payment reductions can be set up in ‘Fee Schedule Configuration’ and can be applied each time the modifier is included on a claim.

  - `modifier4` (string,null)
    Modifiers applicable to codes can be entered. Each of the modifiers can be applied to a single code or multiple codes in the line. Modifier payment reductions can be set up in ‘Fee Schedule Configuration’ and can be applied each time the modifier is included on a claim.

  - `no_UC_Percent` (number,null)
    Price based upon a percentage of the billed amount that is used for Out of Network claims that could not be matched with a usual and customary rate.

  - `place_Of_Service` (string,null)
    Requires a matching place of service on the claim for adjudication matching. Start of a range of PoS when combined with 'PoS Thru'.

  - `place_Of_Service_Thru` (string,null)
    End of the PoS range when combined with ‘PoS’.

  - `price` (number,null)
    Price that will be applied to the matching claim detail record through the ‘Fee Schedule’. This will be multiplied by the number of units within the claim.

  - `procedure_Cluster` (string,null)
    This allows the price to be applied to all procedures within a selected procedure cluster.

  - `procedure_Code` (string, required)
    This section can contain CPT, HCPC, or revenue codes. Every line requires the first procedure code field to be completed, even when using a procedure cluster. Note: If entering a range of codes, the fee entered on that line will apply to all codes in the range.

  - `procedure_Code2` (string,null)
    This section can contain CPT, HCPC, or revenue codes. This field is compared to the 'Procedure Code 2' field on the claim's detail line.

  - `procedure_Code_Thru` (string,null)
    This section can contain CPT, HCPC, or Revenue codes. Every line requires the first procedure code field to be completed, even when using a procedure cluster. Note: If entering a range of codes, the fee entered on that line will apply to all codes in the range.

  - `provider_Type` (string,null)
    Requires a matching Provider type on the claim for adjudication matching.

  - `rvS_Units` (number,null)
    This field is currently informational only.

  - `specialty_Code` (string,null)
    Requires a matching specialty code on the claim for adjudication matching.

  - `thru_Age` (integer,null)
    Ending point for the range of acceptable ages for the Fee Schedule.

  - `thru_Units` (integer,null)
    Ending point for the range of acceptable number of units within a claim for matching during adjudication.

  - `type_Of_Service` (string,null)
    No longer in use.

  - `uC_Claim_Type` (string,null)
    Allows the User to select an existing rate group to base their pricing upon. For instance, if you are building a ‘Fee Schedule’ that uses a percentage of Medicare rates. These rate groups need to be provided by the User and uploaded by VBA.

  - `uC_Percent` (number,null)
    The desired percentage applied from the selected rate group to the matching claim.

  - `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 200 fields (text/plain):

  - `data` (object)

  - `data.feeSchedDetail_Key` (integer, required)
    Unique identifier for each Detail record on this Fee Schedule.  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.

  - `data.allowed_Over_Billed` (boolean, required)
    This option allows the ‘Fee Schedule’ to price above the billed amount.  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.

  - `data.always_Use_Rate` (boolean, required)
    This field is currently informational only.  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.

  - `data.billed_Pct` (number,null)
    Price based upon a percentage of the billed amount that will be applied to the matching claim detail record through the ‘Fee Schedule’.

  - `data.diag_Code` (string,null)
    Requires a matching diagnosis code on the claim for adjudication matching. Start of a range of diagnosis codes when combined with 'Diag Thru'.

  - `data.diag_Code_Thru` (string,null)
    End of the diagnosis range when combined with ‘Diag.’.

  - `data.diagnostic_Code_Type` (string, required)
    Indicates the ICD version associated with the selected Diagnosis Codes.

  - `data.drug_Code` (string,null)
    This will require a matching ‘Drug Code’ within a claim line during adjudication.

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

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

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

  - `data.ex_Code` (string,null)
    Applies the provided Ex Code to any claim that has been repriced by this ‘Fee Schedule Fee’.

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

  - `data.from_Age` (integer,null)
    Starting point for the range of acceptable ages for the Fee Schedule.

  - `data.from_Units` (integer,null)
    Starting point for the range of acceptable number of units within a claim for matching during adjudication.

  - `data.modifier` (string,null)
    Modifiers applicable to codes can be entered. Each of the modifiers can be applied to a single code or multiple codes in the line. Modifier payment reductions can be set up in ‘Fee Schedule Configuration’ and can be applied each time the modifier is included on a claim.

  - `data.modifier2` (string,null)
    Modifiers applicable to codes can be entered. Each of the modifiers can be applied to a single code or multiple codes in the line. Modifier payment reductions can be set up in ‘Fee Schedule Configuration’ and can be applied each time the modifier is included on a claim.

  - `data.modifier3` (string,null)
    Modifiers applicable to codes can be entered. Each of the modifiers can be applied to a single code or multiple codes in the line. Modifier payment reductions can be set up in ‘Fee Schedule Configuration’ and can be applied each time the modifier is included on a claim.

  - `data.modifier4` (string,null)
    Modifiers applicable to codes can be entered. Each of the modifiers can be applied to a single code or multiple codes in the line. Modifier payment reductions can be set up in ‘Fee Schedule Configuration’ and can be applied each time the modifier is included on a claim.

  - `data.no_UC_Percent` (number,null)
    Price based upon a percentage of the billed amount that is used for Out of Network claims that could not be matched with a usual and customary rate.

  - `data.place_Of_Service` (string,null)
    Requires a matching place of service on the claim for adjudication matching. Start of a range of PoS when combined with 'PoS Thru'.

  - `data.place_Of_Service_Thru` (string,null)
    End of the PoS range when combined with ‘PoS’.

  - `data.price` (number,null)
    Price that will be applied to the matching claim detail record through the ‘Fee Schedule’. This will be multiplied by the number of units within the claim.

  - `data.procedure_Cluster` (string,null)
    This allows the price to be applied to all procedures within a selected procedure cluster.

  - `data.procedure_Code` (string, required)
    This section can contain CPT, HCPC, or revenue codes. Every line requires the first procedure code field to be completed, even when using a procedure cluster. Note: If entering a range of codes, the fee entered on that line will apply to all codes in the range.

  - `data.procedure_Code2` (string,null)
    This section can contain CPT, HCPC, or revenue codes. This field is compared to the 'Procedure Code 2' field on the claim's detail line.

  - `data.procedure_Code_Thru` (string,null)
    This section can contain CPT, HCPC, or Revenue codes. Every line requires the first procedure code field to be completed, even when using a procedure cluster. Note: If entering a range of codes, the fee entered on that line will apply to all codes in the range.

  - `data.provider_Type` (string,null)
    Requires a matching Provider type on the claim for adjudication matching.

  - `data.rvS_Units` (number,null)
    This field is currently informational only.

  - `data.specialty_Code` (string,null)
    Requires a matching specialty code on the claim for adjudication matching.

  - `data.thru_Age` (integer,null)
    Ending point for the range of acceptable ages for the Fee Schedule.

  - `data.thru_Units` (integer,null)
    Ending point for the range of acceptable number of units within a claim for matching during adjudication.

  - `data.type_Of_Service` (string,null)
    No longer in use.

  - `data.uC_Claim_Type` (string,null)
    Allows the User to select an existing rate group to base their pricing upon. For instance, if you are building a ‘Fee Schedule’ that uses a percentage of Medicare rates. These rate groups need to be provided by the User and uploaded by VBA.

  - `data.uC_Percent` (number,null)
    The desired percentage applied from the selected rate group to the matching claim.

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

  - `data.update_User` (string,null)
    Date when the record was last updated in the system.

  - `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