Patient Responsibility

Patient Responsibility

Patient Not Responsible

A Patient can be marked as not Responsible in Insurance Management, on the Patient or Encounter Dashboard, Patient Demographics, and on the Insurance in the Insurance Library.

  • If the Patient is marked not responsible on the Insurance Profile, the Patient will not be financially responsible and will not receive a Statement for any of the Encounters.

  • When an Insurance is marked as Patient Not Responsible, the Patients will not be financially Responsible if their Insurance Profile contains this Payer.

Patient/Encounter Dashboard

Make a Patient/Guarantor not Responsible on Patient/Encounter Dashboard
  1. On the Patient or Encounter Dashboard, select Insurance Management.

  1. On the Insurance Profile to change, select Default or Active.

  1. In the Patient column, select Not Responsible from the dropdown.

  2. Select Save[F2].

 

Insurance Library

Make Patients not Responsible in the Insurance Library for a Specific Insurance

Patients with this insurance in their Insurance Profile will not be responsible for any remaining balance, and as a result, will not receive a statement.

  1. From Libraries on the Left Side Menu, select the Insurances button.

  1. Select the Insurance ID.

  2. Select the Modify link.

  1. In the Insurance Settings panel, deselect the Patient Responsible checkbox.

  2. Select Save [F2].


Patient Demographics

Make a Patient not Responsible in Patient Demographics
  1. On the Patient Dashboard, select the Modify link.

  2. In the Claim panel, select Hold Statement for the Statement field.

  3. Select Save [F2].

Encounter Level

Patient Not Responsible on the Encounter Level

An Encounter cannot be marked as Patient Not Responsible but can be put On Hold.

  • This process is Encounter specific.

  • Patient balances on this Encounter will not appear on Statements.

 Modify the Encounter 

  1. From the Encounter Dashboard, select the Modify button.

  2. In the Claim panel, select Hold Statement for the Statement field.

  3. Select Save [F2].

Patient Responsible

Make the Patient Responsible on the Encounter Level

The Encounter is not receiving a Statement because it was put On Hold on the Modify Charge screen, but you now want the Encounter to become Patient Responsibility and for the Guarantor to receive a Statement. This action affects only this Encounter.

  1. On the Encounter Dashboard, select the Modify button.

  1. In the Claim panel, select a Statement Profile for the Statement field.

  1. Select Save [F2].


 


    • Related Articles

    • Patient Responsibility Estimator (PRE)

      Patient Responsibility Estimator (PRE) The Patient Responsibility Estimator is a Premium Add-On to your PM system. Contact our Sales Department for more information. The Estimation is most accurate when all Fee Schedules have been loaded into the PM. ...
    • Encounter Dashboard Overview

      Access the Encounter Dashboard Select the Encounter Number link on the Patient Dashboard, or Enter an e + Encounter number (e12345) in the Navigation Shortcut box. You can go to the Patient Dashboard from the Encounter Dashboard by selecting the ...
    • Add/Modify Insurance Profiles on an Existing Patient

      From the Patient Dashboard, select Insurance Management in the Active Policies panel. Select Add New Insurance Profile. Default is automatically checked. If this is not a default insurance, see Default and Active Insurances for more information. ...
    • Move Existing Encounters to a New Insurance/Self-Pay Profile

      Move Existing Encounters to a New Insurance/Self-Pay Profile When a new Insurance or Self Pay Profile is added, you may need to move some of the existing Encounters to the new Profile. This most often occurs when a claim is denied for not being ...
    • Make a Patient Inactive

      Make a Patient Inactive When a Patient is marked as Inactive, new Charges and Appointments cannot be added for that Patient. But, from a billing perspective, existing claims can be batched and sent, and statements will continue to be batched and sent ...