Permissions for deleting Accounts Receivable records and viewing the Claims Accounting screen

In the Provider Administrator portal, you can use the BriteCore permissions framework to make the Claims Accounting screen read-only for selected roles and to remove all Delete buttons from all Policies Accounts Receivable records.

To remove Delete buttons from Payment records, set the read permission to None on either of these permission paths:

  • Britecore/policies/accounting/deleteRecord: This hides all Delete buttons.
  • Britecore/policies/accounting/deletePayment: This hides the Delete button only on the Payment records.

The purpose of these permission rules is to allow access to a specific Billing user who knows how and when to use these Delete buttons.

  • Access the relevant screens as a user assigned to that Permission Level and verify that specified Delete buttons are not available for Accounts Receivable records and that the Delete button on the Claims Accounting screen is read only. 
    Note: Independently test for both deleteRecord and deletePayment.

    Figure 3: View of the Accounts Receivable Account History table where the Delete button is visible.
    Figure 4: View of the Accounts Receivable Account History table where the Delete button is hidden.
    Figure 5: View of the Claims Accounting screen, when the permission is set to read-only. Notice the highlighted areas are grayed out.
  • BriteCore staff can read PR 11418 for more information.

     

     

    1. Navigate to Settings > System Wide > Permissions.
    2. Create the permission by selecting the user, select the edit pencil button.
      Figure 1: The edit pencil icon. When you select the icon, you can add rules or permissions to the identified user.
    3. Assign restriction permission paths.
      Figure 2: View of how you would configure permissions to hide the Delete buttons on the Accounts Receivable screen and change the Claims Accounting screen to read-only.
    4. Access the relevant screens as a user assigned to that Permission Level and verify that specified Delete buttons are not available for Accounts Receivable records and that the Delete button on the Claims Accounting screen is read only. 
      Note: Independently test for both deleteRecord and deletePayment.

      Figure 3: View of the Accounts Receivable Account History table where the Delete button is visible.
      Figure 4: View of the Accounts Receivable Account History table where the Delete button is hidden.
      Figure 5: View of the Claims Accounting screen, when the permission is set to read-only. Notice the highlighted areas are grayed out.

    BriteCore staff can read PR 11418 for more information.