Employees working the front desk of an office need to know how much to collect from a patient at the time of visit, Things that maybe considered when deciding how much the patient owes could be:
- Does the patient have remaining deductible balance that would need to be fulfilled regardless of their copay amount?
- Does the patient have a co-insurance percentage? If so, what is the resulting amount due based on this percentage?
- Does the patient have any unpaid balance or amounts that should be been added into the balance from previous visits?
The “Due Today” feature of the PM performs these calculations and simplifies this task for the end user. It can calculate how much the patient owes quickly and reliably. Optionally, it can also assign the patient’s responsibility automatically.
DUE TODAY FUNCTION
Due today on a patients account.
Under the Insurance Tab of the Patient’s file, choosing the Co-Pay data
type, the data entry for the Copay, Co-Insurance (Copay Pct), and the Deductible Balance are shown
Next to each of the data entry fields are check boxes, which will enable or disable the amount from being included in the Due Today calculation. The Co-Insurance (Copay Pct) and Copay fields are not mutually exclusive. They could be enabled at the same time. This example shows that both the deductible balance (2145.00) and the fixed copay (10.00) should be considered when performing the due today calculation. Notice that the patient balance does not show any posted responsibility yet:
You can click The “Due Today “amount shown which will display a breakdown of why the Due Today is the amount of 98.00. Clicking on the “Due Today: $98.00” will display a breakdown window like this:
Since the amount of the deductible balance is higher than the copay, the system knows that the patient
will be responsible for the entire amount of the services, as part of the deductible balance. Had the deductible balance been a smaller amount than the copay, such as a deductible balance of 5.00, then
the Copay would be displayed like this:
0 Comments