Having Problems
Home FAQ Who Are We? Email List Schema Getting Started Having Problems Resources What Program

 

[Under Construction]

Up

Fields don't match.
Patient.PatientID field is called Patient.PatientID#.
Need to run the NEWDODA command. Click on Start | Run to open the Run dialog box. 

Type "c:\mpn\eclipse32.exe newdoda"  in the Open text box and click on "OK" This starts the process. Eclipse will open and you will get a message box as each table is initialized.


Opening the CPT table in Access shows all the data as "#deleted".
No resolution at this time. This problem has been duplicated at HNA. The current suggestion is to upgrade to Access 2000. Note: The CPT table data is viewable under Crystal Reports. Any input from Access users would be appreciated!

Can't find User Defined Payment Types.
Can't find User Defined Adjustment Types.
If your looking for these then you are probably working with the ACCOUNTS table. The Schema gives us the following data to be present in the EntryType field:
 

EntryType   

 [I] Determines the type of entry. Possible values are as follows:

1 Service
2 Sales tax
3 Interest
4 Late charge
55 Payor payment
56 Cash payment
57 Check payment
58 Credit card payment
59-108 User defined payments
109 Payor write-off
110 Patient write-off
111-160 User defined write-offs (adjustments)

Values of 59-108 and 111-160 correspond with the text strings that the user programs in the File | File Maintenance | Transaction Codes menu selections. These text strings are stored in the Accounts.dat file, but are not available through the ODBC interface. This leaves us with two choices. One, only us the EntryType codes in your reports or Two, hard code the text strings in your reports. 
 
If you plan on your reports to be used by multiple sites, then you may just have to live with only the EntryType codes. Else, you could write a bunch of code to request the user to copy and paste the strings into a data file for use at each location. 

If you are using your reports at only one site, then it's easy enough to hard code the strings into your report or application. Here is an example of Visual Basic code used for Crystal Reports:

dim i
i={Account.EntryType}-108
formula=Choose(i,"Payor write-off","Patient write-off","Patient Hardship","Insurance Company Denied","Professional Courtesy","Complimentary ExaminationScreening Certificate","Screening Certificate","Birthday Visit","Gift Certificate","Family Plan Visit","Wellness Plan Visit","Child Visit","Cifa-Cash Alternative","Complimentary Food Drive","Valentine Day Fund Raiser","Coll. Agency Fee","Fund Raiser")


Use this code to create a formula field and then drop that formula field onto your report.


Bills show to be Settled, but PatientOwes and PayorOwes are not zero.
The first issue is that the "Settled" field is not automatically populated. To someone who uses the system as a collector, this is obvious. To others it is not. A user can set a bill to a Settled status when there is still money owed, or two much money paid. In fact a good exercise in system cleanliness is to check for bills that are marked Settled, but the balances are not zero.
 
The second part of this equation has to do with how to determine if a bill is paid in full. As related by HNA's Tech Support, the PatientOwes and PayorOwes field are populated when the bill is created. These fields are not updated to zero when the bill is settled. The Schema tells us the field are:

PatientOwes   

 [F] Total amount owed by patient.

PayorOwes   

 [F] Total amount owed by the insurance company.

 
In reality a better description for these would be "Original total amount owed by patient" and "Original total amount owed by patient" 

In a well maintained system, to determine the amount owed on a bill, first use the Settled field to determine of the bill is outstanding or not. If the bill is outstanding, then substract the PayorPayments from the PayorOwes field and PatientPayments from the PatientOwes field to find the true values for what the Patient and Payor owes.
 
 

 

Send mail to feedback@huntfamily.com with questions or comments about this web site.
Last modified: March 15, 2001