Doctor Database | |
Home |
Russell Yanofsky (rey4@columbia.edu) Project SpecificationWe were so enchanted by the doctor's office example from homework 1 that we've decided to implement it for out database project. We want to make a an internal web site that could be used in a doctors office by doctors & their staff to keep track of patient appointments and patient information. Three obvious entities would be patients, doctors, and appointments. For each appointment we want to keep track of referrals to and from other doctors and practices. For instance if one of our doctors decides to refer a patient to a specialist after an appointment, that information would be stored. And if an appointment was a result of a referral from another doctor that information would be stored as well. To do this we would add a table of referrals and a table of information about other practices. For billing purposes, there would be a table of services that hold prices (or just descriptions) of appointments, procedures, tests and so on. As in the example, we will let doctors enter in specific diagnoses about patients for each appointment, and we will have tables to keep track of insurance companies and policies. The main parts of the interface will a page to add, edit and display appointments, a page to enter information about patients, and a simple table editor that will allow changes to the doctors, practices, services, and insurance tables. Since this information will be change less often, it does not need a more complicated interface. |