Addendum Workflow

If you notice that your documentation has missing or incorrect information, the therapist will need to complete an addendum in the WebPT EMR to update the patient’s record. 

Basic Workflow

WebPT EMR
  1. Navigate to the patient’s chart and open the Records screen for the corresponding case.
  2. Use the drop-down for the record you need to addend and select Add Addendum.
  3. Make the necessary changes to the documentation and then move to the Plan (Daily Note) or Billing (Evaluation) tab to finalize.
  4. Finalize the note using the appropriate option. Note: Click here to learn more about adding addendums in the WebPT EMR. 

Addendum Records Entry Example

  • Daily Note: Original DOS of October 22, 2019
  • Addendum: Added on October 28, 2019, and updated DOS to October 21, 2019

WebPT Billing

After a therapist finalizes and rebills an addendum to a note, there are a few scenarios that can happen within Billing:

  1. If a charge/unit has been removed or reduced and the insurance payment has not been posted, then the system will automatically update and the changes can be seen on the individual session within Billing. 
  2. If a charge/unit has been removed or reduced and the payment has been posted, then it will go into Charge Updates. The Biller will then review if the charge has been submitted to insurance and make any manual changes. 
  3. If a charge/unit has been added, the update will go into Charge Updates to be reviewed and manually worked.

Corrected Claim Requirements

If any of the following information is updated on a note, a Corrected Claim will need to be submitted.

  • Date of Service
  • CPT Codes
  • Modifiers
  • Units
  • Billing Provider
  • Referring Physician
  • Diagnosis

Important Notes

  • The provider that completed the original note should complete the addendum unless the other provider actually rendered the services.
  • Do not select Finalize & Rebill unless billable information has been updated.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.