Introduction to Information Systems Database Assignment
DATABASE ASSIGNMENT
Description of the information direction job
A regular infirmary manages around a few hundred patients at any point of clip. This shows that the infirmary staffs need to enter every individual patient & A ; apos ; s personal specifics such as their names, NRIC, day of the month of birth, points that are issued to them, the intervention the patients are undergoing and the physicians whom the patients are assigned to. In the past, I had a impermanent function at the enrollment counter at Singapore General Hospital. At that clip, acquiring clasp of information was a fuss because the information was stored in assorted booklets, which was clip devouring to seek for information. Furthermore, there is ever a high volume of patients & A ; apos ; records each twenty-four hours.
Hence, I set up the Patient Admission and Treatment System.
Key Objectives of the Undertaking
The aim of this database undertaking is to unify the different information sing patients into a individual database to help the infirmary enrollment staff so as to cut down the clip taken to seek for the patient & A ; apos ; s different information. I will be utilizing the Microsoft Access which is a DBMS ( Data Base Management System ) that supports simple database construction dwelling of tabular arraies.
Use Case Diagram and Class Diagram
The usage instance diagram shows the usage instances and their histrions, which is show onFigure 1below.
The category diagram shows entity categories and their relationships, which is shown onFigure 2below.
Data Standardization
Get downing 0NF:
PATIENT (PatientNRIC, PatientName, PatientDOB, PatientReligion, PatientRace, PatientGender, PatientWardRm, PatientWardType, [ ItemIssedNo, ItemIssedDescription ] , [ TreatmentStrDate, TreatmentEndDate, TreatmentType, TreatmentSession ] , [ DocRemark ]
DOCTOR (DocID, DocName, DocContactNo )
1NF: After Removing Repeating Groups
PATIENT (PatientNRIC, PatientName, PatientDOB, PatientReligion, PatientRace, PatientGender, PatientWardRm, PatientWardType )
ITEMS ISSUED (PatientNRIC,ItemIssedNo, ItemIssedDescription )
TREATMENT (PatientNRIC,TreatmentStrDate, TreatmentEndDate, TreatmentType, TreatmentSession )
PATIENT STATUS (PatientNRIC,TreatmentStrDate,DocID, DocName, DocContactNo, DocRemark )
DOCTOR (DocID, DocName, DocContactNo )
2NF: After Removing Partial Key Dependency
PATIENT (PatientNRIC, PatientName, PatientDOB, PatientReligion, PatientRace, PatientGender, PatientWardRm, PatientWardType )
ITEMS ISSUED (PatientNRIC,ItemIssedNo, ItemIssedDescription, ItemIssedQty )
TREATMENT (PatientNRIC,TreatmentStrDate, TreatmentEndDate, TreatmentType, TreatmentSession )
PATIENT STATUS (PatientNRIC,TreatmentStrDate,DocID, DocRemark )
DOC TO PAT (DocID, DocName )
DOCTOR (DocID, DocName, DocContactNo )
3NF: After Removing Non-Key Dependence
There is no non-key dependence found, so the2NFproperties are in3NF.
Optimizing the 3NF Relationss
For optimizing, the3NFinformation entities that have the same primary keys have to be merged, by uniting their non-key properties.
PATIENT (PatientNRIC, PatientName, PatientDOB, PatientReligion, PatientRace, PatientGender, PatientWardRm, PatientWardType )
ITEMS ISSUED (PatientNRIC,ItemIssedNo, ItemIssedDescription )
TREATMENT (PatientNRIC,TreatmentStrDate, TreatmentEndDate, TreatmentType, TreatmentSession )
PATIENT STATUS (PatientNRIC,TreatmentStrDate,DocID, DocRemark )
DOCTOR (DocID, DocName, DocContactNo )
Figure 3below shows the normalised informations theoretical account after optimizing.
Making Tables for each Entity Type
Once the information entities are normalised and optimised, tabular arraies will be created for these informations entities with the several information constituents. Under the design position, different informations types with be assign to different informations constituents.Figure 3andFigure 4shows the screenshot of the Datasheet View and Design View for Patient tabular array severally.
Primary Keys and Relationships links for tabular arraies
When all the tabular arraies are created, primary keys are defined for the several tabular arraies based on the normalised informations theoretical account. The relationships between the different tabular arraies are so linked to one another.Figure 5below shows the relationships between the tabular arraies.
The Referential unity options for the relationships have been selected and enforced.Figure 6on the right shows a screenshot of the options selected when associating the relationships.
Development of Data Entry Forms
Forms are created for identifying in, redacting, or exposing in a tabular arraies or questions. The Patient Form includes characteristics that enable the infirmary staffs to add, salvage, hunt, cancel the patients & A ; apos ; informations into the database easy. There is besides a & A ; apos ; Close Form & A ; apos ; button to shut the signifier. The Patient Form is shown onFigure 7on the right.
ThePatient Status Formenables the physicians to redact or update any comments of any patient & A ; apos ; s that they have examined. The similar buttons and maps are created as good. This is shown onFigure 8on the right.
Development of Database Queries
Questions point out how informations from bing database objects is merged to bring forth the desired informations. ThePatient Treatment Queryis the combination of informations constituents from two different tabular arraies, the Patient and Treatment tabular arraies. It is created to do it convenient for the physicians to mention to the type of intervention of their patients and when is the intervention scheduled. This is shown onFigure 9on the right.
ThePatient Status Queryis the combination of informations constituents from three tabular arraies, the Patient, Treatment and Patient Status tabular arraies. It is created to demo the continuance the patient will be admitted and the comments of the patient. This reduces the clip taken for the infirmary staffs to entree the patients & A ; apos ; records. This is shown onFigure 10on the following page.
Development of Database Reports
Reports present information extracted from tabular arraies or questions in a organized and systematic mode. ThePatient Treatment Reportis created by pull outing information from the Patient and Treatment tabular arraies. This study may be requested by the Hospital Executive Officer to reexamine the current activities running in the infirmary and to make up one’s mind if more physicians are needed if there is an addition in the figure of patients. ThePatient Treatment Reportis show onFigure 11below.
ThePatient Status Reportis created by pull outing information from the Patient, Patient Status and Treatment tabular arraies. This study will be of good mention to look into if the patient & A ; apos ; s household make up one’s mind to upgrade or downgrade the patient & A ; apos ; s ward, and besides let the physicians to make up one’s mind if the comments should be updated. ThePatient Status Reportis shown onFigure 12below.
Operation of the Model
The Patient Admission and Treatment System is a simple and the layout is user-friendly. It is divided into three subdivisions: signifiers, questions and studies. This is for easy pilotage for the infirmary staffs as they merely have to snap on the buttons and the window for the several subdivision will start out for them to entree records or for mention. An issue button is besides added if the enrollment staffs want to go out the database. This is shown onFigure 12on the right.
Restrictions, Challenges and Decision
The challenges faced were foremost about the standardization of the information entities, but I figured out after larning from some on-line pictures. Second was the type of questions that should be created which took me quite some clip to see. Last, for the signifiers, I really created a clean signifier and added each constituent one by one. I so realised that there is a much faster manner to make the signifiers with constituents already add, which was by utilizing the signifier ace.
In decision, a database is used to hive away information in a topographic point link many different entities as together to increase efficiency and cut down on mistakes and disparities. Hence, it is ever important to get down with standardization to cut down indistinguishable and inaccurate informations.
UOL Student No. : 111101580 Page1of6
