HELP!

[John]

I currently have a table with about 80 fields. It
contains patient information for hospital billing. I
import the information weekly to the table and designed
the table based on the import file. Most of the records
in the table contain duplicate data with the exception of
a transaction code and transaction date.
I would like to have one record for each patient in the
main table but have the many different transaction codes
separate so I don't have so much repeated info in the main
table. I am thinking that this is a one-to-many
relationship.
How can I split this up and still be able to continue to
import the text file without breaking up the text file.
There is too much information on the text file to be able
to break it up.
If you would like to see a blank copy of the table I could
send it.

Thank you in advance!

John
(e-mail address removed)

 

[John]

I am doing work with denial management and usually have
accounts that are repeated but with different denial
codes. The import file has 80 fields in it. The info
ranges from patient info to insurance info to payment
info. My problem is I have multiple accts that are taking
up space and each has a different denial code. Some pat.
I have one acct, others could have 10 of the same acct
number. Other times I have the same patient name but
different account numbers. I have built a table that has
all of the denial codes and descriptions in it. I just
don't know what to do from here. I have one huge table
and any money I track is incorrect because of the repeated
accts.
What advice do you have that could help?

John