Hello All,
I have some database design questions and hopefully someone can point me in a good direction. I�ll try to be brief.
I work at a Children�s Center and I�m trying to improve/re-write our client tracking system which is now a hodge-podge of databases and redundant data entry. I need to track different types of changes or movements by clients so we know how and what to bill at the end of the month.
There is a master Clients database and here are the types of changes I need to track.
1)Admission and Discharges to our Center (usually just 2 dates, but can happen more than once)
2)Placement changes within our Center (for example from one
Foster Home to Another), effective date, destination.
3)Temporary Absences (for example, Home Visits, Respite Care, Hospital, Runaway), from_date, to_date, where.
4)Level of Care Changes (this affects our billing rate), effective date, LOC
Does this look like a logical breakdown of relational databases? I'm thinking there must be a better way.
The object of the exercise is to at least print out a list of changes with which to update a utilization database (or ideally update a utilization database from the above �transaction� databases) for a month of service.
Any tips on how to organize this would be much appreciated. Thanks.
John
I have some database design questions and hopefully someone can point me in a good direction. I�ll try to be brief.
I work at a Children�s Center and I�m trying to improve/re-write our client tracking system which is now a hodge-podge of databases and redundant data entry. I need to track different types of changes or movements by clients so we know how and what to bill at the end of the month.
There is a master Clients database and here are the types of changes I need to track.
1)Admission and Discharges to our Center (usually just 2 dates, but can happen more than once)
2)Placement changes within our Center (for example from one
Foster Home to Another), effective date, destination.
3)Temporary Absences (for example, Home Visits, Respite Care, Hospital, Runaway), from_date, to_date, where.
4)Level of Care Changes (this affects our billing rate), effective date, LOC
Does this look like a logical breakdown of relational databases? I'm thinking there must be a better way.
The object of the exercise is to at least print out a list of changes with which to update a utilization database (or ideally update a utilization database from the above �transaction� databases) for a month of service.
Any tips on how to organize this would be much appreciated. Thanks.
John
Comment