Searching for non-duplicated information

[Kathie via AccessMonster.com]

Hello,
I have a database that imports monthly files generated out of a medical
system for specific services on clients. The first service for this patient
is not something I need to create an invoice/payment from, but subsequent
services for that same patient I do. My first problem is the person who
determined the import did not select to import a unique key that was a
required field. They did include the SSN, but it is sometimes null so.... I
am basically trying to create a search capacity on multiple fields. I have
a MONTHLY_IMPORTS table. What I would like to do is evaluate MONTHLY_IMPORTS
against HISTORICAL_DATA and update MONTHLY_IMPORTS as MA_PAID, where services
code = "XYZ" then I would append all records from MONTHLY_IMPORTS to
HISTRICAL_DATA and those marked as MA_PAID would be excluded from processing.
The fields I would need to look at to base this on is: SSN, DOB, Type of
insurance coverage (as I need to evaluate only those on MA) and Service Code.

Does anyone have any idea on how to do this?

Problem 2: Since SSN is not a required field, thus I do not have any unique
key for each patient (can't even create a compound as names can change, DOB
could be the same, etc.) I basically have all this information in one table.
In short - I would have to modify the export file layout to include chart no
(which is required) then have the MONTHLY_IMPORTS table appended across
multiple tables, such as patient table to include name, demographic info, and
then a service table - is there any other way to achieve migrating this
debacle that I am trying to fix to a relational database? (I love when non-
technical people design technical export specifications!)

Thanks all,
Kathie

 

[Guest]

I would not save the SSN in any Access database unless you are absolutely
sure that the data is 100% secure (which is almost impossible with Access).
You are leaving yourself open to lawsuits in the case of identity theft. You
should bring this to your manager's attention. Employees should have employee
identification numbers (EIN) unrelated to their SSN.

-Dorian

 

[kathieglassel via AccessMonster.com]

Unfortunately it is a STATE requirement. This data is contractually required.
I have NTFS limiting access that only two persons can enter into the secured
server. I am not relying on MS Access, but server management. I know that MS
Access is not truly a secured platform.

I would not save the SSN in any Access database unless you are absolutely
sure that the data is 100% secure (which is almost impossible with Access).
You are leaving yourself open to lawsuits in the case of identity theft. You
should bring this to your manager's attention. Employees should have employee
identification numbers (EIN) unrelated to their SSN.

-Dorian

Hello,
I have a database that imports monthly files generated out of a medical

[quoted text clipped - 25 lines]

Thanks all,
Kathie