Hey guys!
We are on our way of restructuring our application that uses single database (SQL Server) which contains huge data - Hospital System. The system features Patients Services (Billing, Lab Exams, HMOs, etc.), A/Rs, A/Ps, Inventory & Warehousing, HR/Payroll & Financial Accounting and are fully integrated into one application.
Now we have a table called 'datacenter' which contains general information of different entities: patients, guarantors, employees, suppliers, doctors. The table does not contain information exclusive only for particular entity like for instance doctor's license number - obviously this info should be in doctors table only. In other words, this table (datacenter) contains informations which are common to the entities mentioned i.e. fullname, email, addresses, etc.
Our plan now is to split the database into 3. This is in line with our plan to also split the system into 3 ( Hospital System, HR & Payroll, Financial Accounting) so we could have option to sell them separately if need be depending on the need of the hospital. Now in your opinion, is it still advisable to keep the datacenter table? Our concerns are the following: communication of the databases which shares common data, connection strings, sql statements, maintenance, etc.
Your idea and comments is highly appreciated in advance!
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."