Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Hospital Database Management System
Transcript of Hospital Database Management System
• All patients must have insurance policy to be treated at the hospital.
• A patient may undergo many treatments at the hospital.
• A patient may or may not receive prescriptions from doctors at the hospital.
• All patients have to put a preferred pharmacy in hospital record forms.
• All nurses and doctors have supervisors.
• Patients will receive each treatment cost under individual payments.
• Patients can make payments in multiple installments.
• Nurses are assigned to a ward during their shift.
• Inpatients are checked-in to a room within an appropriate ward.
• All doctors at the hospital specialize in a certain medical field.
Our project will address the issue of updating a hospital system from a paper based to a relational database. This database will contain customer demographics, billing and insurance information, as well as their medical history. This database will allow administrators to easily track both inpatient and outpatient records and keep them up to date without information overlap. Administrators will be able to check which room an in-patient is currently occupying, and doctors will effortlessly be able to identify their patients from the pool, and determine which nurses are assigned to assist them on a specified date and shift. By implementing this database, this hospital will be able to update and check medical records, bill patients and check-in patients to wards and rooms and match them to their appropriate doctor.
The need for this hospital database system rose because:
paper filing systems are unreliable and not secure
information can get lost in a filing system
there are many repetitive data redundancies
Joel Ball, Farhin Hasan, Alycia Rajendran, Zeeshan Faisal Khan, & Faisal Khan
This database combines several critical areas, but we have left out several fields to keep it simple. For example, our billing tables have been very simplified. We did not address meal options or prescription administration by nurses for in-patients. Patients will have individual bills for each time they undergo treatment at the hospital, which may lead to multiple bills existing at a given time. Our database also does not allow a patient to interact with the user interface to check/alter their appointment dates. They would need to call the hospital to do so. Any updates to records are manual so new data may become mixed with prior admissions information into the system and become invalid.